title: Commission Implementing Regulation (EU) 2016/799 of 18 March 2016 implementing Regulation (EU) No 165/2014 of the European Parliament and of the Council laying down the requirements for the construction, testing, installation, operation and repair of tachographs and their components (Text with EEA relevance)

text:
                  26.5.2016

                  EN

                  Official Journal of the European Union

                  L 139/1

            COMMISSION IMPLEMENTING REGULATION (EU) 2016/799
      of 18 March 2016
      implementing Regulation (EU) No 165/2014 of the European Parliament and of the Council laying down the requirements for the construction, testing, installation, operation and repair of tachographs and their components
      (Text with EEA relevance)
      THE EUROPEAN COMMISSION,
      Having regard to the Treaty on the Functioning of the European Union,
      Having regard to Regulation (EU) No 165/2014 of the European Parliament and of the Council of 4 February 2014 on tachographs in road transport (1), and in particular Articles 11 and 12(7) thereof,
      Whereas:

                  (1)

                  Regulation (EU) No 165/2014 has introduced second-generation digital tachographs called smart tachographs, which include a connection to the global navigation satellite system (‘GNSS’) facility, a remote early detection communication facility, and an interface with intelligent transport systems. The specifications for the technical requirements for the construction of smart tachographs should be set up.

                  (2)

                  The remote early detection facility established by Article 9(4) of Regulation (EU) No 165/2014 should transmit to a roadside control officer the data of the digital tachograph and the information concerning the weights and weight per axles of the complete vehicle combination (tractor and trailers or semi-trailers), in accordance with Directive 96/53/EC of the European Parliament and of the Council (2). That should enable an effective and quick check of vehicles by the control authorities, with fewer electronic devices in the vehicle cab.

                  (3)

                  In accordance with Directive 96/53/EC, the remote early detection facility should use the CEN DSRC standards (3) referred to in that Directive, at the frequency band of 5 795-5 805 MHz. As that frequency band is used for electronic tolling as well, and in order to avoid interference between tolling and control applications, control officers should not use the remote early detection facility on a toll plaza.

                  (4)

                  New security mechanisms for maintaining the level of security of the digital tachograph should be introduced with the smart tachograph to address current security vulnerabilities. One of such vulnerabilities is the absence of expiry dates of digital certificates. In order to comply with the best practices in security matters, it is recommended that the use of digital certificates without expiry dates should be avoided. The normal operation validity period of vehicle units should be 15 years, starting on the issuing date of the vehicle unit digital certificates. Vehicle units should be replaced after that validity period.

                  (5)

                  The provision of secured and reliable positioning information is an essential element of the effective operation of smart tachographs. Therefore, it is appropriate to ensure their compatibility with the added value services provided by the Galileo programme as set out in Regulation (EU) No 1285/2013 of the European Parliament and of the Council (4) in order to improve the security of the smart tachograph.

                  (6)

                  In accordance with Articles 8(1), 9(1) and 10(1) and (2) of Regulation (EU) No 165/2014, the security mechanisms introduced by that Regulation should apply 36 months after the entry into force of the necessary implementing acts in order to allow the manufacturers to develop the new generation of smart tachographs, and receive their type-approval certificates from the competent authorities.

                  (7)

                  In accordance with Regulation (EU) No 165/2014, vehicles registered for the first time in a Member State 36 months after the entry into force of this Commission Regulation, should be equipped with a smart tachograph compliant with the requirements of this Commission Regulation. In any case, all vehicles operating in a Member State other than their Member State of registration should be equipped with a compliant smart tachograph 15 years after the date of application of those requirements.

                  (8)

                  Commission Regulation (EC) No 68/2009 (5) allowed, during a transitional period expiring on 31 December 2013, the use of an adaptor to make possible the installation of tachographs in M1 and N1 type vehicles. Due to technical difficulties related to finding an alternative to the use of the adaptor, the experts of the automotive and tachograph industry, together with the Commission, concluded that no alternative solution to the adaptor was feasible without entailing high costs for industry, which would be disproportionate to the size of the market. Therefore, the use of the adaptor in M1 and N1 type vehicles should be allowed indefinitely.

                  (9)

                  The measures provided for in this Regulation are in accordance with the opinion of the Committee referred to in Article 42(3) of Regulation (EU) No 165/2014,

            HAS ADOPTED THIS REGULATION:
      Article 1
      Subject matter and scope
      1.   This Regulation lays down the provisions necessary for the uniform application of the following aspects regarding tachographs:

                  (a)

                  recording of the position of the vehicle at certain points during the daily working period of the driver;

                  (b)

                  remote early detection of possible manipulation or misuse of smart tachographs;

                  (c)

                  interface with intelligent transport systems;

                  (d)

                  the administrative and technical requirements for the type-approval procedures of tachographs, including the security mechanisms.

            2.   The construction, testing, installation, inspection, operation and repair of smart tachographs and their components, shall comply with the technical requirements set out in Annex 1C to this Regulation.
      3.   Tachographs other than smart tachographs shall continue, as regards construction, testing, installation, inspection, operation and repair, to comply with the requirements of either Annex 1 or Annex 1B to Council Regulation (EEC) No 3821/85 (6), as applicable.
      4.   Pursuant to Article 10d of Directive 96/53/EC, the remote early detection facility shall also transmit the weight data provided by an internal on-board weighing system, for the purpose of early fraud detection.
      Article 2
      Definitions
      For the purposes of this Regulation, the definitions laid down in Article 2 of Regulation (EU) No 165/2014 shall apply.
      In addition, the following definitions shall apply:

                  (1)

                  ‘digital tachograph’ or ‘first generation tachograph’ means a digital tachograph other than a smart tachograph;

                  (2)

                  ‘external GNSS facility’ means a facility which contains the GNSS receiver when the vehicle unit is not a single unit, as well as other components needed to protect the communication of data about position to the rest of the vehicle unit;

                  (3)

                  ‘information folder’ means the complete folder, in electronic or paper form, containing all the information supplied by the manufacturer or its agent to the type-approval authority for the purpose of the type-approval of a tachograph or a component thereof, including the certificates referred to in Article 12(3) of Regulation (EU) No 165/2014, the performance of the tests defined in Annex 1C to this Regulation, as well as drawings, photographs, and other relevant documents;

                  (4)

                  ‘information package’ means the information folder, in electronic or paper form, accompanied by any other documents added by the type-approval authority to the information folder in the course of carrying out their functions including, at the end of the type-approval process, the EC type-approval certificate of the tachograph or a component thereof;

                  (5)

                  ‘index to the information package’ means the document listing the numbered contents of the information package identifying all the relevant parts of this package. The format of that document shall distinguish the successive steps in the EC type-approval process, including the dates of any revisions and updating of that package;

                  (6)

                  ‘remote early detection facility’ means the equipment of the vehicle unit which is used to perform targeted roadside checks;

                  (7)

                  ‘smart tachograph’ or ‘second generation tachograph’ means a digital tachograph complying with Articles 8, 9 and 10 of Regulation (EU) No 165/2014 as well as with Annex 1C to this Regulation;

                  (8)

                  ‘tachograph component’ or ‘component’ means any of the following elements: the vehicle unit, the motion sensor, the tachograph card, the record sheet, the external GNSS facility and the remote early detection facility;

                  (9)

                  ‘type-approval authority’ means the authority of a Member State competent to carry out the type-approval of the tachograph or of its components, the authorisation process, the issuing and, if appropriate, withdrawing of type-approval certificates, acting as the contact point for the type-approval authorities of other Member States and ensuring that the manufacturers meet their obligations relating to the conformity with the requirement of this Regulation.

            Article 3
      Location-based services
      1.   Manufacturers shall ensure that smart tachographs are compatible with the positioning services provided by the Galileo and the European Geostationary Navigation Overlay Service (‘EGNOS’) systems.
      2.   In addition to the systems referred to in paragraph 1, manufacturers may also choose to ensure compatibility with other satellite navigation systems.
      Article 4
      Procedure for type-approval of a tachograph and tachograph components
      1.   A manufacturer or its agent shall submit an application for type-approval of a tachograph or any of its components, or group of components, to the type-approval authorities designated by each Member State. It shall consist of an information folder containing the information for each of the components concerned including, where applicable, the type-approval certificates of other components necessary to complete the tachograph, as well as any other relevant documents.
      2.   A Member State shall grant type-approval to any tachograph, component or group of components that conforms to the administrative and technical requirements referred to in Article 1(2) or (3), as applicable. In that case, the type-approval authority shall issue to the applicant a type-approval certificate that shall conform to the model laid down in Annex II to this Regulation.
      3.   The type-approval authority may request the manufacturer or its agent to supply any additional information.
      4.   The manufacturer or its agent shall make available to the type-approval authorities, as well as to the entities responsible for issuing the certificates referred to in Article 12(3) of Regulation (EU) No 165/2014, as many tachographs or tachograph components as are necessary to enable the type-approval procedure to be conducted satisfactorily.
      5.   Where the manufacturer or its agent seeks a type-approval of certain components or groups of components of a tachograph, he shall provide the type-approval authorities with the other components, already type-approved, as well as other parts necessary for the construction of the complete tachograph, in order for those authorities to conduct the necessary tests.
      Article 5
      Modifications to type-approvals
      1.   The manufacturer or its agent shall inform without delay the type-approval authorities that granted the original type-approval, about any modification in software or hardware of the tachograph or in the nature of the materials used for its manufacture which are recorded in the information package and shall submit an application for the modification of the type-approval.
      2.   The type-approval authorities may revise or extend an existing type-approval, or issue a new type-approval according to the nature and characteristics of the modifications.
      A ‘revision’ shall be made where the type-approval authority considers that the modifications in software or hardware of the tachograph or in the nature of materials used for its manufacture are minor. In such cases, the type-approval authority shall issue the revised documents of the information package, indicating the nature of the modifications made and the date of their approval. An updated version of the information package in a consolidated form, accompanied by a detailed description of the modifications made, shall be sufficient to meet this requirement.
      An ‘extension’ shall be made where the type-approval authority considers that the modifications in software or hardware of the tachograph or in the nature of materials used for its manufacture are substantial. In such cases, it may request that new tests be conducted and inform the manufacturer or its agent accordingly. If those tests prove satisfactory, the type-approval authority shall issue a revised type-approval certificate containing a number referring to the extension granted. The type-approval certificate shall mention the reason of the extension and its date of issue.
      3.   The index to the information package shall indicate the date of the most recent extension or revision of the type-approval, or the date of the most recent consolidation of the updated version of the type-approval.
      4.   A new type-approval shall be necessary when the requested modifications to the type-approved tachograph or its components would lead to the issuance of a new security or interoperability certificate.
      Article 6
      Entry into force
      This Regulation shall enter into force on the twentieth day following that of its publication in the Official Journal of the European Union.
      It shall apply from 2 March 2016.
      However, the Annexes shall apply from 2 March 2019 with the exception of Appendix 16 which shall apply from 2 March 2016.

         This Regulation shall be binding in its entirety and directly applicable in all Member States.
         Done at Brussels, 18 March 2016.

               For the Commission

               The President

            Jean-Claude JUNCKER

         (1)  OJ L 60, 28.2.2014, p.1.

         (2)  Council Directive 96/53/EC of 25 July 1996 laying down for certain road vehicles circulating within the Community the maximum authorized dimensions in national and international traffic and the maximum authorized weights in international traffic (OJ L 235, 17.9.1996, p.59)

         (3)  Dedicated Short Range Communications standards of the European Standardisation Committee (CEN) EN 12253, EN 12795, EN 12834, EN 13372 and ISO 14906.

         (4)  Regulation (EU) No 1285/2013 of the European Parliament and of the Council of 11 December 2013 on the implementation and exploitation of European satellite navigation systems and repealing Council Regulation (EC) No 876/2002 and Regulation (EC) No 683/2008 of the European Parliament and of the Council (OJ L 347, 20.12.2013, p. 1).

         (5)  Commission Regulation (EC) No 68/2009 of 23 January 2009 adapting for the ninth time to technical progress Council Regulation (EEC) No 3821/85 on recording equipment in road transport (OJ L 21, 24.1.2009, p.3).

         (6)  Council Regulation (EEC) No 3821/85 of 20 December 1985 on recording equipment in road transport (OJ L 370, 31.12.1985, p.8).

         ANNEX I C

            Requirements for construction, testing, installation, and inspection

         INTRODUCTION
                  12

                     1.

                  DEFINITIONS
                  13

                     2.

                  GENERAL CHARACTERISTICS AND FUNCTIONS OF THE RECORDING EQUIPMENT
                  19

                     2.1

                  General characteristics
                  19

                     2.2

                  Functions
                  20

                     2.3

                  Modes of operation
                  21

                     2.4

                  Security
                  22

                     3.

                  CONSTRUCTION AND FUNCTIONAL REQUIREMENTS FOR RECORDING EQUIPMENT
                  22

                     3.1

                  Monitoring cards insertion and withdrawal
                  22

                     3.2

                  Speed, position and distance measurement
                  23

                     3.2.1

                  Measurement of distance travelled
                  23

                     3.2.2

                  Measurement of speed
                  23

                     3.2.3

                  Measurement of position
                  24

                     3.3

                  Time measurement
                  24

                     3.4

                  Monitoring driver activities
                  24

                     3.5

                  Monitoring driving status
                  25

                     3.6

                  Driver's entries
                  25

                     3.6.1

                  Entry of places where daily work periods begin and/or end
                  25

                     3.6.2

                  Manual entry of driver activities and driver consent for ITS interface
                  25

                     3.6.3

                  Entry of specific conditions
                  27

                     3.7

                  Company locks management
                  27

                     3.8

                  Monitoring control activities
                  28

                     3.9

                  Detection of events and/or faults
                  28

                     3.9.1

                  ‘Insertion of a non-valid card’ event
                  28

                     3.9.2

                  ‘Card conflict’ event
                  28

                     3.9.3

                  ‘Time overlap’ event
                  28

                     3.9.4

                  ‘Driving without an appropriate card’ event
                  29

                     3.9.5

                  ‘Card insertion while driving’ event
                  29

                     3.9.6

                  ‘Last card session not correctly closed’ event
                  29

                     3.9.7

                  ‘Over speeding’ event
                  29

                     3.9.8

                  ‘Power supply interruption’ event
                  29

                     3.9.9

                  ‘Communication error with the remote communication facility’ event
                  29

                     3.9.10

                  ‘Absence of position information from GNSS receiver’ event
                  29

                     3.9.11

                  ‘Communication error with the external GNSS facility’ event
                  30

                     3.9.12

                  ‘Motion data error’ event
                  30

                     3.9.13

                  ‘Vehicle motion conflict’ event
                  30

                     3.9.14

                  ‘Security breach attempt’ event
                  30

                     3.9.15

                  ‘Time conflict’ event
                  30

                     3.9.16

                  ‘Card’ fault
                  30

                     3.9.17

                  ‘Recording equipment’ fault
                  30

                     3.10

                  Built-in and self-tests
                  31

                     3.11

                  Reading from data memory
                  31

                     3.12

                  Recording and storing in the data memory
                  31

                     3.12.1

                  Equipment identification data
                  32

                     3.12.1.1

                  Vehicle unit identification data
                  32

                     3.12.1.2

                  Motion sensor identification data
                  32

                     3.12.1.3

                  Global Navigation Satellite Systems identification data
                  33

                     3.12.2

                  Keys and certificates
                  33

                     3.12.3

                  Driver or workshop card insertion and withdrawal data
                  33

                     3.12.4

                  Driver activity data
                  34

                     3.12.5

                  Places and positions where daily work periods begin, end, and/or where 3 hours' continuous driving time is reached
                  34

                     3.12.6

                  Odometer data
                  35

                     3.12.7

                  Detailed speed data
                  35

                     3.12.8

                  Events data
                  35

                     3.12.9

                  Faults data
                  37

                     3.12.10

                  Calibration data
                  38

                     3.12.11

                  Time adjustment data
                  39

                     3.12.12

                  Control activity data
                  39

                     3.12.13

                  Company locks data
                  39

                     3.12.14

                  Download activity data
                  39

                     3.12.15

                  Specific conditions data
                  40

                     3.12.16

                  Tachograph card data
                  40

                     3.13

                  Reading from tachograph cards
                  40

                     3.14

                  Recording and storing on tachograph cards
                  40

                     3.14.1

                  Recording and storing in first generation tachograph cards
                  40

                     3.14.2

                  Recording and storing in second generation tachograph cards
                  41

                     3.15

                  Displaying
                  41

                     3.15.1

                  Default display
                  42

                     3.15.2

                  Warning display
                  43

                     3.15.3

                  Menu access
                  43

                     3.15.4

                  Other displays
                  43

                     3.16

                  Printing
                  43

                     3.17

                  Warnings
                  44

                     3.18

                  Data downloading to external media
                  45

                     3.19

                  Remote communication for targeted roadside checks
                  45

                     3.20

                  Output data to additional external devices
                  46

                     3.21

                  Calibration
                  47

                     3.22

                  Roadside calibration checking
                  47

                     3.23

                  Time adjustment
                  48

                     3.24

                  Performance characteristics
                  48

                     3.25

                  Materials
                  48

                     3.26

                  Markings
                  49

                     4.

                  CONSTRUCTION AND FUNCTIONAL REQUIREMENTS FOR TACHOGRAPH CARDS
                  49

                     4.1

                  Visible data
                  49

                     4.2

                  Security
                  52

                     4.3

                  Standards
                  53

                     4.4

                  Environmental and electrical specifications
                  53

                     4.5

                  Data storage
                  53

                     4.5.1

                  Elementary files for identification and card management
                  54

                     4.5.2

                  IC card identification
                  54

                     4.5.2.1

                  Chip identification
                  54

                     4.5.2.2

                  DIR (only present in second generation tachograph cards)
                  54

                     4.5.2.3

                  ATR information (conditional, only present in second generation tachograph cards)
                  54

                     4.5.2.4

                  Extended length information (conditional, only present in second generation tachograph cards)
                  55

                     4.5.3

                  Driver card
                  55

                     4.5.3.1

                  Tachograph application (accessible to first and second generation vehicle units)
                  55

                     4.5.3.1.1

                  Application identification
                  55

                     4.5.3.1.2

                  Key and certificates
                  55

                     4.5.3.1.3

                  Card identification
                  55

                     4.5.3.1.4

                  Card holder identification
                  55

                     4.5.3.1.5

                  Card download
                  55

                     4.5.3.1.6

                  Driving licence information
                  55

                     4.5.3.1.7

                  Events data
                  56

                     4.5.3.1.8

                  Faults data
                  56

                     4.5.3.1.9

                  Driver activity data
                  57

                     4.5.3.1.10

                  Vehicles used data
                  57

                     4.5.3.1.11

                  Places where daily work periods start and/or end
                  58

                     4.5.3.1.12

                  Card session data
                  58

                     4.5.3.1.13

                  Control activity data
                  58

                     4.5.3.1.14

                  Specific conditions data
                  58

                     4.5.3.2

                  Tachograph generation 2 application (not accessible to first generation vehicle unit)
                  59

                     4.5.3.2.1

                  Application identification
                  59

                     4.5.3.2.2

                  Keys and certificates
                  59

                     4.5.3.2.3

                  Card identification
                  59

                     4.5.3.2.4

                  Card holder identification
                  59

                     4.5.3.2.5

                  Card download
                  59

                     4.5.3.2.6

                  Driving licence information
                  59

                     4.5.3.2.7

                  Events data
                  59

                     4.5.3.2.8

                  Faults data
                  60

                     4.5.3.2.9

                  Driver activity data
                  61

                     4.5.3.2.10

                  Vehicles used data
                  61

                     4.5.3.2.11

                  Places and positions where daily work periods start and/or end
                  62

                     4.5.3.2.12

                  Card session data
                  62

                     4.5.3.2.13

                  Control activity data
                  62

                     4.5.3.2.14

                  Specific conditions data
                  63

                     4.5.3.2.15

                  Vehicle units used data
                  63

                     4.5.3.2.16

                  Three hours' continuous driving places data
                  63

                     4.5.4

                  Workshop card
                  63

                     4.5.4.1

                  Tachograph application (accessible to first and second generation vehicle units)
                  63

                     4.5.4.1.1

                  Application identification
                  63

                     4.5.4.1.2

                  Keys and certificates
                  63

                     4.5.4.1.3

                  Card identification
                  64

                     4.5.4.1.4

                  Card holder identification
                  64

                     4.5.4.1.5

                  Card download
                  64

                     4.5.4.1.6

                  Calibration and time adjustment data
                  64

                     4.5.4.1.7

                  Events and faults data
                  65

                     4.5.4.1.8

                  Driver activity data
                  65

                     4.5.4.1.9

                  Vehicles used data
                  65

                     4.5.4.1.10

                  Daily work periods start and/or end data
                  65

                     4.5.4.1.11

                  Card session data
                  65

                     4.5.4.1.12

                  Control activity data
                  65

                     4.5.4.1.13

                  Specific conditions data
                  65

                     4.5.4.2

                  Tachograph generation 2 application (not accessible to first generation vehicle unit)
                  65

                     4.5.4.2.1

                  Application identification
                  65

                     4.5.4.2.2

                  Keys and certificates
                  66

                     4.5.4.2.3

                  Card identification
                  66

                     4.5.4.2.4

                  Card holder identification
                  66

                     4.5.4.2.5

                  Card download
                  66

                     4.5.4.2.6

                  Calibration and time adjustment data
                  66

                     4.5.4.2.7

                  Events and faults data
                  67

                     4.5.4.2.8

                  Driver activity data
                  67

                     4.5.4.2.9

                  Vehicles used data
                  67

                     4.5.4.2.10

                  Daily work periods start and/or end data
                  67

                     4.5.4.2.11

                  Card session data
                  67

                     4.5.4.2.12

                  Control activity data
                  67

                     4.5.4.2.13

                  Vehicle units used data
                  67

                     4.5.4.2.14

                  Three hours' continuous driving places data
                  68

                     4.5.4.2.15

                  Specific conditions data
                  68

                     4.5.5

                  Control card
                  68

                     4.5.5.1

                  Tachograph application (accessible to first and second generation vehicle units)
                  68

                     4.5.5.1.1

                  Application identification
                  68

                     4.5.5.1.2

                  Keys and certificates
                  68

                     4.5.5.1.3

                  Card identification
                  68

                     4.5.5.1.4

                  Card holder identification
                  68

                     4.5.5.1.5

                  Control activity data
                  69

                     4.5.5.2

                  Tachograph G2 application (not accessible to first generation vehicle unit)
                  69

                     4.5.5.2.1

                  Application identification
                  69

                     4.5.5.2.2

                  Keys and certificates
                  69

                     4.5.5.2.3

                  Card identification
                  69

                     4.5.5.2.4

                  Card holder identification
                  69

                     4.5.5.2.5

                  Control activity data
                  70

                     4.5.6

                  Company card
                  70

                     4.5.6.1

                  Tachograph application (accessible to first and second generation vehicle units)
                  70

                     4.5.6.1.1

                  Application identification
                  70

                     4.5.6.1.2

                  Keys and certificates
                  70

                     4.5.6.1.3

                  Card identification
                  70

                     4.5.6.1.4

                  Card holder identification
                  70

                     4.5.6.1.5

                  Company activity data
                  70

                     4.5.6.2

                  Tachograph G2 application (not accessible to first generation vehicle unit)
                  71

                     4.5.6.2.1

                  Application identification
                  71

                     4.5.6.2.2

                  Keys and certificates
                  71

                     4.5.6.2.3

                  Card identification
                  71

                     4.5.6.2.4

                  Card holder identification
                  71

                     4.5.6.2.5

                  Company activity data
                  71

                     5.

                  INSTALLATION OF RECORDING EQUIPMENT
                  72

                     5.1

                  Installation
                  72

                     5.2

                  Installation plaque
                  73

                     5.3

                  Sealing
                  74

                     6.

                  CHECKS, INSPECTIONS AND REPAIRS
                  74

                     6.1

                  Approval of fitters, workshops and vehicle manufacturers
                  74

                     6.2

                  Check of new or repaired instruments
                  75

                     6.3

                  Installation inspection
                  75

                     6.4

                  Periodic inspections
                  75

                     6.5

                  Measurement of errors
                  76

                     6.6

                  Repairs
                  76

                     7.

                  CARD ISSUING
                  76

                     8.

                  TYPE-APPROVAL OF RECORDING EQUIPMENT AND TACHOGRAPH CARDS
                  77

                     8.1

                  General points
                  77

                     8.2

                  Security certificate
                  78

                     8.3

                  Functional certificate
                  78

                     8.4

                  Interoperability certificate
                  78

                     8.5

                  Type-approval certificate
                  79

                     8.6

                  Exceptional procedure: first interoperability certificates for 2nd generation recording equipment and tachograph cards
                  80
               INTRODUCTION
         The first generation digital tachograph system has been deployed since 1 May 2006. It may be used until its end of life for domestic transportation. For international transportation, instead, 15 years after the entry into force of this Commission Regulation, all vehicles shall be equipped with a compliant second generation smart tachograph, introduced by this Regulation.
         This Annex contains second generation recording equipment and tachograph cards requirements. Starting from its introduction date, second generation recording equipment shall be installed in vehicles registered for the first time, and second generation tachograph cards shall be issued.
         In order to foster a smooth introduction of the second generation tachograph system:

                     —

                     second generation tachograph cards shall be designed to be also used in first generation vehicle units,

                     —

                     replacement of valid first generation tachograph cards at the introduction date shall not be requested.

               This will allow drivers to keep their unique driver card and use both systems with it.
         Second generation recording equipment shall however only be calibrated using second generation workshop cards.
         This Annex contains all requirements related to the interoperability between the first and the second generation tachograph system.
         Appendix 15 contains additional details about how the coexistence of the two systems shall be managed.
         List of Appendixes

                     App 1:

                  DATA DICTIONARY

                     App 2:

                  TACHOGRAPH CARDS SPECIFICATION

                     App 3:

                  PICTOGRAMS

                     App 4:

                  PRINTOUTS

                     App 5:

                  DISPLAY

                     App 6:

                  FRONT CONNECTOR FOR CALIBRATION AND DOWNLOAD

                     App 7:

                  DATA DOWNLOADING PROTOCOLS

                     App 8:

                  CALIBRATION PROTOCOL

                     App 9:

                  TYPE-APPROVAL AND LIST OF MINIMUM REQUIRED TESTS

                     App 10:

                  SECURITY REQUIREMENTS

                     App 11:

                  COMMON SECURITY MECHANISMS

                     App 12:

                  POSITIONING BASED ON GLOBAL NAVIGATION SATELLITE SYSTEM (GNSS)

                     App 13:

                  ITS INTERFACE

                     App 14:

                  REMOTE COMMUNICATION FUNCTION

                     App 15:

                  MIGRATION: MANAGING THE COEXISTENCE OF EQUIPMENT GENERATIONS

                     App 16:

                  ADAPTOR FOR M1 AND N1 CATEGORY VEHICLES

               1.   DEFINITIONS
         In this Annex:

                     (a)

                     ‘activation’ means:
                     the phase in which the tachograph becomes fully operational and implements all functions, including security functions, through the use of a workshop card;

                     (b)

                     ‘authentication’ means:
                     a function intended to establish and verify a claimed identity;

                     (c)

                     ‘authenticity’ means:
                     the property that information is coming from a party whose identity can be verified;

                     (d)

                     ‘built-in test (BIT)’ means:
                     tests run at request, triggered by the operator or by external equipment;

                     (e)

                     ‘calendar day’ means:
                     a day ranging from 00:00 hours to 24:00 hours. All calendar days relate to UTC time (Universal Time Coordinated);

                     (f)

                     ‘calibration’ of a smart tachograph means:
                     updating or confirming vehicle parameters to be held in the data memory. Vehicle parameters include vehicle identification (VIN, VRN and registering Member State) and vehicle characteristics (w, k, l, tyre size, speed-limiting device setting (if applicable), current UTC time, current odometer value); during the calibration of a recording equipment, the types and identifiers of all type-approval relevant seals in place shall also be stored in the data memory;
                     any update or confirmation of UTC time only, shall be considered as a time adjustment and not as a calibration, provided it does not contradict Requirement 409;
                     calibrating recording equipment requires the use of a workshop card;

                     (g)

                     ‘card number’ means:
                     a 16-alphanumerical character number that uniquely identifies a tachograph card within a Member State. The card number includes a card consecutive index (if applicable), a card replacement index and a card renewal index;
                     a card is therefore uniquely identified by the code of the issuing Member State and the card number;

                     (h)

                     ‘card consecutive index’ means:
                     the 14th alphanumerical character of a card number that is used to differentiate the different cards issued to a company, a workshop or a control authority entitled to be issued several tachograph cards. The company, the workshop or the control authority is uniquely identified by the 13 first characters of the card number;

                     (i)

                     ‘card renewal index’ means:
                     the 16th alphanumerical character of a card number which is incremented each time a tachograph card is renewed;

                     (j)

                     ‘card replacement index’ means:
                     the 15th alpha-numerical character of a card number which is incremented each time a tachograph card is replaced;

                     (k)

                     ‘characteristic coefficient of the vehicle’ means:
                     the numerical characteristic giving the value of the output signal emitted by the part of the vehicle linking it with the recording equipment (gearbox output shaft or axle) while the vehicle travels a distance of one kilometre under standard test conditions as defined under requirement 414. The characteristic coefficient is expressed in impulses per kilometre (w = … imp/km);

                     (l)

                     ‘company card’ means:
                     a tachograph card issued by the authorities of a Member State to a transport undertaking needing to operate vehicles fitted with a tachograph, which identifies the transport undertaking and allows for the displaying, downloading and printing of the data, stored in the tachograph, which have been locked by that transport undertaking;

                     (m)

                     ‘constant of the recording equipment’ means:
                     the numerical characteristic giving the value of the input signal required to show and record a distance travelled of one kilometre; this constant shall be expressed in impulses per kilometre (k = … imp/km);

                     (n)

                     ‘continuous driving time’ is computed within the recording equipment as (1):
                     the continuous driving time is computed as the current accumulated driving times of a particular driver, since the end of his last AVAILABILITY or BREAK/REST or UNKNOWN (2) period of 45 minutes or more (this period may have been split according to Regulation (EC) No 561/2006 of the European Parliament and of the Council (3)). The computations involved take into account, as needed, past activities stored on the driver card. When the driver has not inserted his card, the computations involved are based on the data memory recordings related to the current period where no card was inserted and related to the relevant slot;

                     (o)

                     ‘control card’ means:
                     a tachograph card issued by the authorities of a Member State to a national competent control authority which identifies the control body and, optionally, the control officer, and which allows access to the data stored in the data memory or in the driver cards and, optionally, in the workshop cards for reading, printing and/or downloading;
                     It shall also give access to the roadside calibration checking function and to data on the remote early detection communication reader;

                     (p)

                     ‘cumulative break time’ is computed within the recording equipment as (1):
                     the cumulative break from driving time is computed as the current accumulated AVAILABILITY or BREAK/REST or UNKNOWN (2) times of 15 minutes or more of a particular driver, since the end of his last AVAILABILITY or BREAK/REST or UNKNOWN (2) period of 45 minutes or more (this period may have been split according to Regulation (EC) No 561/2006).
                     The computations involved take into account, as needed, past activities stored on the driver card. Unknown periods of negative duration (start of unknown period > end of unknown period) due to time overlaps between two different sets of recording equipment, are not taken into account for the computation.
                     When the driver has not inserted his card, the computations involved are based on the data memory recordings related to the current period where no card was inserted and related to the relevant slot;

                     (q)

                     ‘data memory’ means:
                     an electronic data storage device built into the recording equipment;

                     (r)

                     ‘digital signature’ means:
                     data appended to, or a cryptographic transformation of, a block of data that allows the recipient of the block of data to prove the authenticity and integrity of the block of data;

                     (s)

                     ‘downloading’ means:
                     the copying, together with the digital signature, of a part, or of a complete set, of data files recorded in the data memory of the vehicle unit or in the memory of a tachograph card, provided that this process does not alter or delete any stored data;
                     manufacturers of smart tachograph vehicle units and manufacturers of equipment designed and intended to download data files shall take all reasonable steps to ensure that the downloading of such data can be performed with the minimum delay by transport undertakings or drivers;
                     The downloading of the detailed speed file may not be necessary to establish compliance with Regulation (EC) No 561/2006, but may be used for other purposes such as accident investigation;

                     (t)

                     ‘driver card’ means:
                     a tachograph card, issued by the authorities of a Member State to a particular driver, which identifies the driver and allows for the storage of driver activity data;

                     (u)

                     ‘effective circumference of the wheels’ means:
                     the average of the distances travelled by each of the wheels moving the vehicle (driving wheels) in the course of one complete rotation. The measurement of these distances shall be made under standard test conditions as defined under requirement 414 and is expressed in the form ‘l = … mm’. Vehicle manufacturers may replace the measurement of these distances by a theoretical calculation which takes into account the distribution of the weight on the axles, vehicle unladen in normal running order (4). The methods for such theoretical calculation are subject to approval by a competent Member State authority and can take place only before tachograph activation;

                     (v)

                     ‘event’ means:
                     an abnormal operation detected by the smart tachograph which may result from a fraud attempt;

                     (w)

                     ‘external GNSS facility’ means
                     a facility which contains the GNSS receiver when the vehicle unit is not a single unit as well as other components needed to protect the communication of position data to the rest of the vehicle unit;

                     (x)

                     ‘fault’ means:
                     abnormal operation detected by the smart tachograph which may come from an equipment malfunction or failure;

                     (y)

                     ‘GNSS receiver’ means:
                     an electronic device that receives and digitally processes the signals from one or more Global Navigation Satellite System(s) (GNSS in English) in order to provide position, speed and time information;

                     (z)

                     ‘installation’ means:
                     the mounting of a tachograph in a vehicle;

                     (aa)

                     ‘interoperability’ means:
                     the capacity of systems and the underlying business processes to exchange data and to share information;

                     (bb)

                     ‘interface’ means:
                     a facility between systems which provides the media through which they can connect and interact;

                     (cc)

                     ‘position’ means:
                     geographical coordinates of the vehicle at a given time;

                     (dd)

                     ‘motion sensor’ means:
                     a part of the tachograph, providing a signal representative of vehicle speed and/or distance travelled;

                     (ee)

                     ‘non-valid card’ means:
                     a card detected as faulty, or which initial authentication failed, or whose start of validity date is not yet reached, or whose expiry date has passed;

                     (ff)

                     ‘open standard’ means:
                     a standard set out in a standard specification document available freely or at a nominal charge which it is permissible to copy, distribute or use for no fee or for a nominal fee;

                     (gg)

                     ‘out of scope’ means:
                     when the use of the recording equipment is not required, according to the provisions of Regulation (EC) No 561/2006;

                     (hh)

                     ‘over speeding’ means:
                     exceeding the authorised speed of the vehicle, defined as any period of more than 60 seconds during which the vehicle's measured speed exceeds the limit for setting the speed limitation device laid down in Council Directive 92/6/EEC (5), as last amended;

                     (ii)

                     ‘periodic inspection’ means:
                     a set of operations performed to check that the tachograph works properly, that its settings correspond to the vehicle parameters, and that no manipulation devices are attached to the tachograph;

                     (jj)

                     ‘printer’ means:
                     component of the recording equipment which provides printouts of stored data;

                     (kk)

                     ‘remote early detection communication’ means:
                     communication between the remote early detection communication facility and the remote early detection communication reader during targeted roadside checks with the aim of remotely detecting possible manipulation or misuse of recording equipment;

                     (ll)

                     ‘remote communication facility’ means:
                     the equipment of the vehicle unit which is used to perform targeted roadside checks;

                     (mm)

                     ‘remote early detection communication reader’ means:
                     the system used by control officers for targeted roadside checks.

                     (nn)

                     ‘renewal’ means:
                     issue of a new tachograph card when an existing card reaches its expiry date, or is malfunctioning and has been returned to the issuing authority. Renewal always implies the certainty that two valid cards do not coexist;

                     (oo)

                     ‘repair’ means:
                     any repair of a motion sensor or of a vehicle unit or of a cable that requires the disconnection of its power supply, or its disconnection from other tachograph components, or the opening of the motion sensor or vehicle unit;

                     (pp)

                     ‘card replacement’ means:
                     issue of a tachograph card in replacement of an existing card, which has been declared lost, stolen or malfunctioning and has not been returned to the issuing authority. Replacement always implies a risk that two valid cards may coexist;

                     (qq)

                     ‘security certification’ means:
                     process to certify, by a common criteria certification body, that the recording equipment (or component) or the tachograph card under investigation fulfils the security requirements defined in the relative protection profiles;

                     (rr)

                     ‘self test’ means:
                     tests run cyclically and automatically by the recording equipment to detect faults;

                     (ss)

                     ‘time measurement’ means:
                     a permanent digital record of the coordinated universal date and time (UTC);

                     (tt)

                     ‘time adjustment’ means:
                     an automatic adjustment of current time at regular intervals and within a maximum tolerance of one minute, or an adjustment performed during calibration;

                     (uu)

                     ‘tyre size’ means:
                     the designation of the dimensions of the tyres (external driving wheels) in accordance with Council Directive 92/23/EEC (6) as last amended;

                     (vv)

                     ‘vehicle identification’ means:
                     numbers identifying the vehicle: vehicle registration number (VRN) with indication of the registering Member State and vehicle identification number (VIN) (7);

                     (ww)

                     for computing sake in the recording equipment ‘week’ means:
                     the period between 00:00 hours UTC on Monday and 24:00 UTC on Sunday;

                     (xx)

                     ‘workshop card’ means:
                     a tachograph card issued by the authorities of a Member State to designated staff of a tachograph manufacturer, a fitter, a vehicle manufacturer or a workshop, approved by that Member State, which identifies the cardholder and allows for the testing, calibration and activation of tachographs, and/or downloading from them;

                     (yy)

                     ‘adaptor’ means:
                     a device, providing a signal permanently representative of vehicle speed and/or distance travelled, other than the one used for the independent movement detection, and which is:

                                 —

                                 installed and used only in M1 and N1 type vehicles (as defined in Annex II to Directive 2007/46/EC of the European Parliament and of the Council (8), as last amended) put into service since 1 May 2006,

                                 —

                                 installed where it is not mechanically possible to install any other type of existing motion sensor which is otherwise compliant with the provisions of this Annex and its Appendixes 1 to 15,

                                 —

                                 installed between the vehicle unit and where the speed/distance impulses are generated by integrated sensors or alternative interfaces,

                                 —

                                 seen from a vehicle unit, the adaptor behaviour is the same as if a motion sensor, compliant with the provisions of this Annex and its Appendixes 1 to 16, was connected to the vehicle unit;

                           use of such an adaptor in those vehicles described above shall allow for the installation and correct use of a vehicle unit compliant with all the requirements of this Annex,
                     for those vehicles, the smart tachograph includes cables, an adaptor, and a vehicle unit;

                     (zz)

                     ‘data integrity’ means:
                     the accuracy and consistency of stored data, indicated by an absence of any alteration in data between two updates of a data record. Integrity implies that the data is an exact copy of the original version, e.g. that it has not been corrupted in the process of being written to, and read back from, a tachograph card or a dedicated equipment or during transmission via any communications channel;

                     (aaa)

                     ‘data privacy’ means:
                     the overall technical measures taken to ensure the proper implementation of the principles laid down in Directive 95/46/EC of the European Parliament and of the Council (9) as well as of those laid down in Directive 2002/58/EC of the European Parliament and of the Council (10);

                     (bbb)

                     ‘smart tachograph’ system means:
                     the recording equipment, tachograph cards and the set of all directly or indirectly interacting equipment during their construction, installation, use, testing and control, such as cards, remote communication reader and any other equipment for data downloading, data analysis, calibration, generating, managing or introducing security elements, etc.;

                     (ccc)

                     ‘introduction date’:
                     36 months after the entry into force of the detailed provisions referred to in Article 11 of Regulation (EU) No 165/2014 of the European Parliament and of the Council (11)

                     This is the date after which vehicles registered for the first time:

                                 —

                                    shall be fitted with a tachograph connected to a positioning service based on a satellite navigation system,

                                 —

                                    shall be able to communicate data for targeted roadside checks to competent control authorities while the vehicle is in motion,

                                 —

                                    and may be equipped with standardised interfaces allowing the data recorded or produced by tachographs to be used in operational mode, by an external device.

                     (ddd)

                     ‘protection profile’ means:
                     a document used as part of certification process according Common Criteria, providing implementation independent specification of information assurance security requirements;

                     (eee)

                     ‘GNSS accuracy’:
                     in the context of recording the position from a Global Navigation Satellite System (GNSS) with tachographs, means the value of the horizontal dilution of precision (HDOP) calculated as the minimum of the HDOP values collected on the available GNSS systems.

               2.   GENERAL CHARACTERISTICS AND FUNCTIONS OF THE RECORDING EQUIPMENT
         2.1   General characteristics

         The purpose of the recording equipment is to record, store, display, print, and output data related to driver activities.
         Any vehicle fitted with the recording equipment complying with the provisions of this Annex, must include a speed display and an odometer. These functions may be included within the recording equipment.

                     (1)

                     The recording equipment includes cables, a motion sensor, and a vehicle unit.

                     (2)

                     The interface between motion sensors and vehicle units shall comply with the requirements specified in Appendix 11.

                     (3)

                     The vehicle unit shall be connected to global navigation satellite system(s), as specified in Appendix 12.

                     (4)

                     The vehicle unit shall communicate with remote early detection communication readers, as specified in Appendix 14.

                     (5)

                     The vehicle unit may include an ITS interface, which is specified in Appendix 13
                     The recording equipment may be connected to other facilities through additional interfaces and/or through the optional ITS interface.

                     (6)

                     Any inclusion in or connection to the recording equipment of any function, device, or devices, approved or otherwise, shall not interfere with, or be capable of interfering with, the proper and secure operation of the recording equipment and the provisions of this Regulation.
                     Recording equipment users identify themselves to the equipment via tachograph cards.

                     (7)

                     The recording equipment provides selective access rights to data and functions according to user's type and/or identity.

               The recording equipment records and stores data in its data memory, in the remote communication facility and in tachograph cards.
         This is done in accordance with Directive 95/46/EC of 24 October 1995 on the protection of individuals with regard to the processing of personal data and on the free movement of such data (12), with Directive 2002/58/EC of 12 July 2002 concerning the processing of personal data and the protection of privacy in the electronic communications sector (13) and in compliance with Article 7 of Regulation (EU) No. 165/2014.
         2.2   Functions

                     (8)

                     The recording equipment shall ensure the following functions:

                                 —

                                 monitoring cards insertions and withdrawals,

                                 —

                                 speed, distance and position measurement,

                                 —

                                 time measurement,

                                 —

                                 monitoring driver activities,

                                 —

                                 monitoring driving status,

                                 —

                                 drivers manual entries:

                                             —

                                             entry of places where daily work periods begin and/or end,

                                             —

                                             manual entry of driver activities,

                                             —

                                             entry of specific conditions,

                                 —

                                 company locks management,

                                 —

                                 monitoring control activities,

                                 —

                                 detection of events and/or faults,

                                 —

                                 built-in and self-tests,

                                 —

                                 reading from data memory,

                                 —

                                 recording and storing in data memory,

                                 —

                                 reading from tachograph cards,

                                 —

                                 recording and storing in tachograph cards,

                                 —

                                 displaying,

                                 —

                                 printing,

                                 —

                                 warning,

                                 —

                                 data downloading to external media,

                                 —

                                 remote communication for targeted roadside checks,

                                 —

                                 output data to additional facilities,

                                 —

                                 calibration,

                                 —

                                 roadside calibration check,

                                 —

                                 time adjustment.

               2.3   Modes of operation

                     (9)

                     The recording equipment shall possess four modes of operation:

                                 —

                                 operational mode,

                                 —

                                 control mode,

                                 —

                                 calibration mode,

                                 —

                                 company mode.

                     (10)

                     The recording equipment shall switch to the following mode of operation according to the valid tachograph cards inserted into the card interface devices. In order to determine the mode of operation, the tachograph card generation is irrelevant, provided the inserted card is valid. A first generation workshop card shall always be considered as non-valid when it is inserted in a second generation VU.

                                 Mode of operation

                                 Driver slot

                                 No card

                                 Driver card

                                 Control card

                                 Workshop card

                                 Company card

                                 Co-driver slot

                                 No card

                                 Operational

                                 Operational

                                 Control

                                 Calibration

                                 Company

                                 Driver card

                                 Operational

                                 Operational

                                 Control

                                 Calibration

                                 Company

                                 Control card

                                 Control

                                 Control

                                 Control (*)

                                 Operational

                                 Operational

                                 Workshop card

                                 Calibration

                                 Calibration

                                 Operational

                                 Calibration (*)

                                 Operational

                                 Company card

                                 Company

                                 Company

                                 Operational

                                 Operational

                                 Company (*)

                     (11)

                     The recording equipment shall ignore non-valid cards inserted, except displaying, printing or downloading data held on an expired card which shall be possible.

                     (12)

                     All functions listed in 2.2. shall work in any mode of operation with the following exceptions:

                                 —

                                 the calibration function is accessible in the calibration mode only,

                                 —

                                 the roadside calibration checking function is accessible in the control mode only,

                                 —

                                 the company locks management function is accessible in the company mode only,

                                 —

                                 the monitoring of control activities function is operational in the control mode only,

                                 —

                                 The downloading function is not accessible in the operational mode (except as provided for in requirement 193), and except downloading a driver card when no other card type is inserted into the VU.

                     (13)

                     The recording equipment can output any data to display, printer or external interfaces with the following exceptions:

                                 —

                                 in the operational mode, any personal identification (surname and first name(s)) not corresponding to a tachograph card inserted shall be blanked and any card number not corresponding to a tachograph card inserted shall be partially blanked (every odd character — from left to right — shall be blanked),

                                 —

                                 in the company mode, driver related data (requirements 102, 105 and 108) can be output only for periods where no lock exists or no other company holds a lock (as identified by the first 13 digits of the company card number),

                                 —

                                 when no card is inserted in the recording equipment, driver related data can be output only for the current and 8 previous calendar days,

                                 —

                                 personal data originating from the VU shall not be output through ITS interface of the VU unless the consent of the driver to whom the data relates is verified,

                                 —

                                 the vehicle units have a normal operations validity period of 15 years, starting with the vehicle unit certificates issuing date, but vehicle units can be used for additional 3 months, for data downloading only.

               2.4   Security

         The system security aims at protecting the data memory in such a way as to prevent unauthorised access to and manipulation of the data and detecting any such attempts, protecting the integrity and authenticity of data exchanged between the motion sensor and the vehicle unit, protecting the integrity and authenticity of data exchanged between the recording equipment and the tachograph cards, protecting the integrity and authenticity of data exchanged between the recording equipment and the external GNSS facility, protecting the confidentiality, integrity and authenticity of data exchanged through the remote early detection communication for control purposes, and verifying the integrity and authenticity of data downloaded.

                     (14)

                     In order to achieve the system security, the following components shall meet the security requirements specified in their Protection Profiles, as required in Appendix 10:

                                 —

                                 vehicle unit,

                                 —

                                 tachograph card,

                                 —

                                 motion sensor,

                                 —

                                 external GNSS facility (this Profile is only needed and applicable for the external GNSS variant).

               3.   CONSTRUCTION AND FUNCTIONAL REQUIREMENTS FOR RECORDING EQUIPMENT
         3.1   Monitoring cards insertion and withdrawal

                     (15)

                     The recording equipment shall monitor the card interface devices to detect card insertions and withdrawals.

                     (16)

                     Upon card insertion the recording equipment shall detect whether the card inserted is a valid tachograph card and in such a case identify the card type and the card generation.
                     If a card with the same card number and a higher renewal index has already been inserted in the recording equipment, the card shall be declared as non-valid.
                     If a card with the same card number and renewal index but with a higher replacement index has already been inserted in the recording equipment, the card shall be declared as non-valid.

                     (17)

                     First generation tachograph cards shall be considered as non-valid by the recording equipment, after the possibility of using first generation tachograph cards has been suppressed by a workshop, in compliance with Appendix 15 (req. MIG003).

                     (18)

                     First generation workshop cards which are inserted in the second generation recording equipment shall be considered as non-valid.

                     (19)

                     The recording equipment shall be so designed that the tachograph cards are locked in position on their proper insertion into the card interface devices.

                     (20)

                     The release of tachograph cards may function only when the vehicle is stopped and after the relevant data have been stored on the cards. The release of the card shall require positive action by the user.

               3.2   Speed, position and distance measurement

                     (21)

                     The motion sensor (possibly embedded in the adaptor) is the main source for speed and distance measurement.

                     (22)

                     This function shall continuously measure and be able to provide the odometer value corresponding to the total distance travelled by the vehicle using the pulses provided by the motion sensor.

                     (23)

                     This function shall continuously measure and be able to provide the speed of the vehicle using the pulses provided by the motion sensor.

                     (24)

                     The speed measurement function shall also provide the information whether the vehicle is moving or stopped. The vehicle shall be considered as moving as soon as the function detects more than 1 imp/sec for at least 5 seconds from the motion sensor, otherwise the vehicle shall be considered as stopped.

                     (25)

                     Devices displaying speed (speedometer) and total distance travelled (odometer) installed in any vehicle fitted with a recording equipment complying with the provisions of this Regulation, shall comply with the requirements relating to maximum tolerances (see 3.2.1 and 3.2.2) laid down in this Annex.

                     (26)

                     To detect manipulation of motion data, information from the motion sensor shall be corroborated by vehicle motion information derived from the GNSS receiver and optionally by other source(s) independent from the motion sensor.

                     (27)

                     This function shall measure the position of the vehicle in order to allow for the automatic recording of:

                                 —

                                 positions where the driver and/or the co-driver begins his daily work period;

                                 —

                                 positions where the continuous driving time of the driver reaches a multiple of three hours;

                                 —

                                 positions where the driver and/or the co-driver ends his daily work period.

               3.2.1   Measurement of distance travelled

                     (28)

                     The distance travelled may be measured either:

                                 —

                                 so as to cumulate both forward and reverse movements, or

                                 —

                                 so as to include only forward movement.

                     (29)

                     The recording equipment shall measure distance from 0 to 9 999 999,9 km.

                     (30)

                     Distance measured shall be within the following tolerances (distances of at least 1 000 m.):

                                 —

                                 ± 1 % before installation,

                                 —

                                 ± 2 % on installation and periodic inspection,

                                 —

                                 ± 4 % in use.

                     (31)

                     Distance measured shall have a resolution better than or equal to 0,1 km.

               3.2.2   Measurement of speed

                     (32)

                     The recording equipment shall measure speed from 0 to 220 km/h.

                     (33)

                     To ensure a maximum tolerance on speed displayed of ± 6 km/h in use, and taking into account:

                                 —

                                 a ± 2 km/h tolerance for input variations (tyre variations, …),

                                 —

                                 a ± 1 km/h tolerance in measurements made during installation or periodic inspections,

                           the recording equipment shall, for speeds between 20 and 180 km/h, and for characteristic coefficients of the vehicle between 4 000 and 25 000 imp/km, measure the speed with a tolerance of ± 1 km/h (at constant speed).

                        Note: The resolution of data storage brings an additional tolerance of ± 0,5 km/h to speed stored by the recording equipment.

                     (34)

                     The speed shall be measured correctly within the normal tolerances within 2 seconds of the end of a speed change when the speed has changed at a rate up to 2 m/s2.

                     (35)

                     Speed measurement shall have a resolution better than or equal to 1 km/h.

               3.2.3   Measurement of position

                     (36)

                     The recording equipment shall measure the absolute position of the vehicle using the GNSS receiver.

                     (37)

                     The absolute position is measured in geographical coordinates of latitude and longitude in degrees and minutes with a resolution of 1/10 of a minute.

               3.3   Time measurement

                     (38)

                     The time measurement function shall measure permanently and digitally provide UTC date and time.

                     (39)

                     UTC date and time shall be used for dating data inside the recording equipment (recordings, data exchange) and for all printouts specified in Appendix 4 ‘Printouts’.

                     (40)

                     In order to visualise the local time, it shall be possible to change the offset of the time displayed, in half hour steps. No other offsets than negative or positive multiples of half hours shall be allowed;

                     (41)

                     Time drift shall be within ± 2 seconds per day in type approval conditions, in the absence of any time adjustment.

                     (42)

                     Time measured shall have a resolution better than or equal to 1 second.

                     (43)

                     Time measurement shall not be affected by an external power supply cut-off of less than 12 months in type approval conditions.

               3.4   Monitoring driver activities

                     (44)

                     This function shall permanently and separately monitor the activities of one driver and one co-driver.

                     (45)

                     Driver activity shall be DRIVING, WORK, AVAILABILITY or BREAK/REST.

                     (46)

                     It shall be possible for the driver and/or the co-driver to manually select WORK, AVAILABILITY or BREAK/REST.

                     (47)

                     When the vehicle is moving, DRIVING shall be selected automatically for the driver and AVAILABILITY shall be selected automatically for the co-driver.

                     (48)

                     When the vehicle stops, WORK shall be selected automatically for the driver.

                     (49)

                     The first change of activity to REST or AVAILABILITY arising within 120 seconds of the automatic change to WORK due to the vehicle stop shall be assumed to have happened at the time of vehicle stop (therefore possibly cancelling the change to WORK).

                     (50)

                     This function shall output activity changes to the recording functions at a resolution of one minute.

                     (51)

                     Given a calendar minute, if DRIVING is registered as the activity of both the immediately preceding and the immediately succeeding minute, the whole minute shall be regarded as DRIVING.

                     (52)

                     Given a calendar minute that is not regarded as DRIVING according to requirement 051, the whole minute shall be regarded to be of the same type of activity as the longest continuous activity within the minute (or the latest of the equally long activities).

                     (53)

                     This function shall also permanently monitor the continuous driving time and the cumulative break time of the driver.

               3.5   Monitoring driving status

                     (54)

                     This function shall permanently and automatically monitor the driving status.

                     (55)

                     The driving status CREW shall be selected when two valid driver cards are inserted in the equipment, the driving status SINGLE shall be selected in any other case.

               3.6   Driver's entries

         3.6.1   Entry of places where daily work periods begin and/or end

                     (56)

                     This function shall allow for the entry of places where, according to the driver and/or the co-driver, his daily work periods begin and/or end.

                     (57)

                     Places are defined as the country and, in addition where applicable, the region, which are entered or confirmed manually.

                     (58)

                     At the time of a driver card withdrawal, the recording equipment shall prompt the (co-)driver to enter a ‘place where the daily work period ends’.

                     (59)

                     The driver shall then enter the current place of the vehicle, which shall be considered as a temporary entry.

                     (60)

                     It shall be possible to input places where daily work periods begin and/or end through commands in the menus. If more than one such input is done within one calendar minute, only the last begin place input and the last end place input done within that time shall be kept recorded.

               3.6.2   Manual entry of driver activities and driver consent for ITS interface

                     (61)

                     Upon driver (or workshop) card insertion, and only at this time, the recording equipment shall allow manual entries of activities. Manual entries of activities shall be performed using local time and date values of the time zone (UTC offset) currently set for the vehicle unit.
                     At driver or workshop card insertion the cardholder shall be reminded of:

                                 —

                                 the date and time of his last card withdrawal;

                                 —

                                 optionally: the local time offset currently set for the vehicle unit.

                           At the first insertion of a given driver card or workshop card currently unknown to the vehicle unit, the cardholder shall be invited to express his consent for tachograph related personal data output through the optional ITS interface.
                     At any moment, the driver (resp. workshop) consent can be enabled or disabled through commands in the menu, provided the driver (resp. workshop) card is inserted.
                     It shall be possible to input activities with the following restrictions:

                                 —

                                 Activity type shall be WORK, AVAILABILITY or BREAK/REST;

                                 —

                                 Start and end times for each activity shall be within the period of the last card withdrawal — current insertion only;

                                 —

                                 Activities shall not be allowed to overlap mutually in time.

                           It shall be possible to make manual entries, if required, at the first insertion of a previously unused driver (or workshop) card.
                     The procedure for manual entries of activities shall include as many consecutive steps as necessary to set a type, a start time and an end time for each activity. For any part of the time period between last card withdrawal and current card insertion, the cardholder shall have the option not to declare any activity.
                     During the manual entries associated with card insertion and if applicable, the card holder shall have the opportunity to input:

                                 —

                                 a place where a previous daily work period ended, associated to the relevant time (thus overwriting the entry made at the last card withdrawal),

                                 —

                                 a place where the current daily work period begins, associated to the relevant time.

                           If the card holder doesn't enter any place where the work period begins or ended, during the manual entries associated with card insertion, this shall be considered as a declaration that his work period has not changed since the last card withdrawal. The next entry of a place where a previous daily work period ends shall then overwrite the temporary entry made at the last card withdrawal.
                     If a place is entered, it shall be recorded in the relevant tachograph card.
                     Manual entries shall be interrupted if:

                                 —

                                 the card is withdrawn or,

                                 —

                                 the vehicle is moving and the card is in the driver slot.

                           Additional interruptions are allowed, e.g. a timeout after a certain period of user inactivity. If manual entries are interrupted, the recording equipment shall validate any complete place and activity entries (having either unambiguous place and time, or activity type, begin time and end time) already made.
                     If a second driver or workshop card is inserted while manual entries of activities are in progress for a previously inserted card, the manual entries for this previous card shall be allowed to be completed before manual entries start for the second card.
                     The cardholder shall have the option to insert manual entries according to the following minimum procedure:

                                 —

                                 Enter activities manually, in chronological order, for the period last card withdrawal — current insertion.

                                 —

                                 Begin time of the first activity shall be set to card withdrawal time. For each subsequent entry, the start time shall be preset to immediately follow the end time of the previous entry. Activity type and end time shall be selected for each activity.

                           The procedure shall end when the end time of a manually entered activity equals the card insertion time. The recording equipment may then optionally allow the card holder to modify any activity manually entered, until validation by selection of a specific command. Thereafter, any such modification shall be forbidden.

               3.6.3   Entry of specific conditions

                     (62)

                     The recording equipment shall allow the driver to enter, in real time, the following two specific conditions:

                                 —

                                 ‘OUT OF SCOPE’ (begin, end)

                                 —

                                 ‘FERRY / TRAIN CROSSING’ (begin, end).

                           A ‘FERRY / TRAIN CROSSING’ may not occur if an ‘OUT OF SCOPE’ condition is opened.
                     An opened ‘OUT OF SCOPE’ condition must be automatically closed, by the recording equipment, if a driver card is inserted or withdrawn.
                     An opened ‘OUT OF SCOPE’ condition shall inhibit the following events and warnings:

                                 —

                                 Driving without an appropriate card,

                                 —

                                 Warnings associated with continuous driving time.

                           The FERRY / TRAIN CROSSING begin flag shall be set before shutting down the engine on the ferry/train.
                     An opened FERRY / TRAIN CROSSING must end when any of following options occurs:

                                 —

                                 The driver manually ends the FERRY/TRAIN CROSSING

                                 —

                                 The driver ejects his card

                           An opened FERRY/TRAIN CROSSING shall end when it is no longer valid based on the rules stated in Regulation (EC) No. 561/2006.

               3.7   Company locks management

                     (63)

                     This function shall allow the management of the locks placed by a company to restrict data access in company mode to itself.

                     (64)

                     Company locks consist in a start date/time (lock-in) and an end date/time (lock-out) associated with the identification of the company as denoted by the company card number (at lock-in).

                     (65)

                     Locks may be turned ‘in’ or ‘out’ in real time only.

                     (66)

                     Locking-out shall only be possible for the company whose lock is ‘in’ (as identified by the first 13 digits of the company card number), or,

                     (67)

                     Locking-out shall be automatic if another company locks in.

                     (68)

                     In the case where a company locks in and where the previous lock was for the same company, then it will be assumed that the previous lock has not been turned ‘out’ and is still ‘in’.

               3.8   Monitoring control activities

                     (69)

                     This function shall monitor DISPLAYING, PRINTING, VU and card DOWNLOADING, and ROADSIDE CALIBRATION check activities carried while in control mode.

                     (70)

                     This function shall also monitor OVER SPEEDING CONTROL activities while in control mode. An over speeding control is deemed to have happened when, in control mode, the ‘over speeding’ printout has been sent to the printer or to the display, or when ‘events and faults’ data have been downloaded from the VU data memory.

               3.9   Detection of events and/or faults

                     (71)

                     This function shall detect the following events and/or faults:

               3.9.1   ‘Insertion of a non-valid card’ event

                     (72)

                     This event shall be triggered at the insertion of any non-valid card, at the insertion of a driver card already replaced and/or when an inserted valid card expires.

               3.9.2   ‘Card conflict’ event

                     (73)

                     This event shall be triggered when any of the valid cards combination noted X in the following table arises:

                                 Card conflict

                                 Driver slot

                                 No card

                                 Driver card

                                 Control card

                                 Workshop card

                                 Company card

                                 Co-driver slot

                                 No card

                                 Driver card

                                 X

                                 Control card

                                 X

                                 X

                                 X

                                 Workshop card

                                 X

                                 X

                                 X

                                 X

                                 Company card

                                 X

                                 X

                                 X

               3.9.3   ‘Time overlap’ event

                     (74)

                     This event shall be triggered when the date / time of last withdrawal of a driver card, as read from the card, is later than the current date / time of the recording equipment in which the card is inserted.

               3.9.4   ‘Driving without an appropriate card’ event

                     (75)

                     This event shall be triggered for any valid tachograph cards combination noted X in the following table, when driver activity changes to DRIVING, or when there is a change of the mode of operation while driver activity is DRIVING:

                                 Driving without an appropriate card

                                 Driver slot

                                 No (or non-valid) card

                                 Driver card

                                 Control card

                                 Workshop card

                                 Company card

                                 Co-driver slot

                                 No (or non-valid) card

                                 X

                                 X

                                 X

                                 Driver card

                                 X

                                 X

                                 X

                                 X

                                 Control card

                                 X

                                 X

                                 X

                                 X

                                 X

                                 Workshop card

                                 X

                                 X

                                 X

                                 X

                                 Company card

                                 X

                                 X

                                 X

                                 X

                                 X

               3.9.5   ‘Card insertion while driving’ event

                     (76)

                     This event shall be triggered when a tachograph card is inserted in any slot, while driver activity is DRIVING.

               3.9.6   ‘Last card session not correctly closed’ event

                     (77)

                     This event shall be triggered when at card insertion the recording equipment detects that, despite the provisions laid down in paragraph 3.1., the previous card session has not been correctly closed (the card has been withdrawn before all relevant data have been stored on the card). This event shall be triggered by driver and workshop cards only.

               3.9.7   ‘Over speeding’ event

                     (78)

                     This event shall be triggered for each over speeding.

               3.9.8   ‘Power supply interruption’ event

                     (79)

                     This event shall be triggered, while not in calibration or control mode, in case of any interruption exceeding 200 milliseconds of the power supply of the motion sensor and/or of the vehicle unit. The interruption threshold shall be defined by the manufacturer. The drop in power supply due to the starting of the engine of the vehicle shall not trigger this event.

               3.9.9   ‘Communication error with the remote communication facility’ event

                     (80)

                     This event shall be triggered, while not in calibration mode, when the remote communication facility does not acknowledge the successful reception of remote communication data sent from the vehicle unit for more than three attempts.

               3.9.10   ‘Absence of position information from GNSS receiver’ event

                     (81)

                     This event shall be triggered, while not in calibration mode, in case of absence of position information originating from the GNSS receiver (whether internal or external) for more than three hours of accumulated driving time.

               3.9.11   ‘Communication error with the external GNSS facility’ event

                     (82)

                     This event shall be triggered, while not in calibration mode, in case of interruption of the communication between the external GNSS facility and the vehicle unit for more than 20 continuous minutes, when the vehicle is moving.

               3.9.12   ‘Motion data error’ event

                     (83)

                     This event shall be triggered, while not in calibration mode, in case of interruption of the normal data flow between the motion sensor and the vehicle unit and/or in case of data integrity or data authentication error during data exchange between the motion sensor and the vehicle unit.

               3.9.13   ‘Vehicle motion conflict’ event

                     (84)

                     This event shall be triggered, while not in calibration mode, in case motion information calculated from the motion sensor is contradicted by motion information calculated from the internal GNSS receiver or from the external GNSS facility and optionally by other independent sources, as specified in Appendix 12. This event shall not be triggered during a ferry/train crossing, an OUT OF SCOPE condition, or when the position information from the GNSS receiver is not available.

               3.9.14   ‘Security breach attempt’ event

                     (85)

                     This event shall be triggered for any other event affecting the security of the motion sensor and/or of the vehicle unit and/or the external GNSS facility as required in Appendix 10, while not in calibration mode.

               3.9.15   ‘Time conflict’ event

                     (86)

                     This event shall be triggered, while not in calibration mode, when the VU detects a discrepancy of more than 1 minute between the time of the vehicle unit's time measurement function and the time originating from the GNSS receiver. This event is recorded together with the internal clock value of the vehicle unit and comes together with an automatic time adjustment. After a time conflict event has been triggered, the VU will not generate other time conflict events for the next 12 hours. This event shall not be triggered in cases no valid GNSS signal was detectable by the GNSS receiver within the last 30 days. However, when the position information from the GNSS receiver is available again, the automatic time adjustment shall be done.

               3.9.16   ‘Card’ fault

                     (87)

                     This fault shall be triggered when a tachograph card failure occurs during operation.

               3.9.17   ‘Recording equipment’ fault

                     (88)

                     This fault shall be triggered for any of these failures, while not in calibration mode:

                                 —

                                 VU internal fault

                                 —

                                 Printer fault

                                 —

                                 Display fault

                                 —

                                 Downloading fault

                                 —

                                 Sensor fault

                                 —

                                 GNSS receiver or external GNSS facility fault

                                 —

                                 Remote Communication facility fault

               3.10   Built-in and self-tests

                     (89)

                     The recording equipment shall self-detect faults through self-tests and built-in-tests, according to the following table:

                                 Sub-assembly to test

                                 Self-test

                                 Built-in-test

                                 Software

                                 Integrity

                                 Data memory

                                 Access

                                 Access, data integrity

                                 Card interface devices

                                 Access

                                 Access

                                 Keyboard

                                 Manual check

                                 Printer

                                 (up to manufacturer)

                                 Printout

                                 Display

                                 Visual check

                                 Downloading
                                 (performed only during downloading)

                                 Proper operation

                                 Sensor

                                 Proper operation

                                 Proper operation

                                 Remote communication facility

                                 Proper operation

                                 Proper operation

                                 GNSS facility

                                 Proper operation

                                 Proper operation

               3.11   Reading from data memory

                     (90)

                     The recording equipment shall be able to read any data stored in its data memory.

               3.12   Recording and storing in the data memory

         For the purpose of this paragraph,

                     —

                     ‘365 days’ is defined as 365 calendar days of average drivers' activity in a vehicle. The average activity per day in a vehicle is defined as at least 6 drivers or co-drivers, 6 card insertion withdrawal cycles, and 256 activity changes. ‘365 days’ therefore include at least 2 190 (co-)drivers, 2 190 card insertion withdrawal cycles, and 93 440 activity changes,

                     —

                     the average number of positions per day is defined as at least 6 positions where the daily work period begins, 6 positions when the driver's continuous driving time reaches a multiple of three hours, and 6 positions where the daily work period ends, so that ‘365 days’ include at least 6 570 positions,

                     —

                     times are recorded with a resolution of one minute, unless otherwise specified,

                     —

                     odometer values are recorded with a resolution of one kilometre,

                     —

                     speeds are recorded with a resolution of 1 km/h,

                     —

                     positions (latitudes and longitudes) are recorded in degrees and minutes, with a resolution of 1/10 of minute, with the associated GNSS accuracy and acquisition time.

                     (91)

                     Data stored into the data memory shall not be affected by an external power supply cut-off of less than twelve months in type approval conditions. In addition, data stored in the external remote communication facility, as defined in Appendix 14, shall not be affected by power-supply cut-off of less than 28 days.

                     (92)

                     The recording equipment shall be able to record and store implicitly or explicitly in its data memory the following:

               3.12.1   Equipment identification data

         3.12.1.1   Vehicle unit identification data

                     (93)

                     The recording equipment shall be able to store in its data memory the following vehicle unit identification data:

                                 —

                                 name of the manufacturer,

                                 —

                                 address of the manufacturer,

                                 —

                                 part number,

                                 —

                                 serial number,

                                 —

                                 VU generation,

                                 —

                                 ability to use first generation tachograph cards,

                                 —

                                 software version number,

                                 —

                                 software version installation date,

                                 —

                                 year of equipment manufacture,

                                 —

                                 approval number,

                     (94)

                     Vehicle unit identification data are recorded and stored once and for all by the vehicle unit manufacturer, except the software related data and the approval number which may be changed in case of software upgrade and the ability to use first generation tachograph cards.

               3.12.1.2   Motion sensor identification data

                     (95)

                     The motion sensor shall be able to store in its memory the following identification data:

                                 —

                                 name of the manufacturer,

                                 —

                                 serial number,

                                 —

                                 approval number,

                                 —

                                 embedded security component identifier (e.g. internal chip/processor part number),

                                 —

                                 operating system identifier (e.g. software version number).

                     (96)

                     Motion sensor identification data are recorded and stored once and for all in the motion sensor, by the motion sensor manufacturer.

                     (97)

                     The vehicle unit shall be able to record and store in its data memory the following data related to the 20 most recent pairing of motion sensors (if several pairings happen within one calendar day, only the first and the last one of the day shall be stored):
                     The following data shall be recorded for each of these pairings:

                                 —

                                 motion sensor identification data:

                                             —

                                             serial number

                                             —

                                             approval number

                                 —

                                 motion sensor pairing data:

                                             —

                                             pairing date.

               3.12.1.3   Global Navigation Satellite Systems identification data

                     (98)

                     The external GNSS facility shall be able to store in its memory the following identification data:

                                 —

                                 name of the manufacturer,

                                 —

                                 serial number,

                                 —

                                 approval number,

                                 —

                                 embedded security component identifier (e.g. internal chip/processor part number),

                                 —

                                 operating system identifier (e.g. software version number).

                     (99)

                     The identification data are recorded and stored once and for all in the external GNSS facility, by the external GNSS facility manufacturer.

                     (100)

                     The vehicle unit shall be able to record and store in its data memory the following data related to the 20 most recent couplings of external GNSS facilities (if several couplings happen within one calendar day, only the first and the last one of the day shall be stored).
                     The following data shall be recorded for each of these couplings:

                                 —

                                 external GNSS facility identification data:

                                             —

                                             serial number,

                                             —

                                             approval number,

                                 —

                                 external GNSS facility coupling data:

                                             —

                                             coupling date

               3.12.2   Keys and certificates

                     (101)

                     The recording equipment shall be able to store a number of cryptographic keys and certificates, as specified in Appendix 11 part A and part B.

               3.12.3   Driver or workshop card insertion and withdrawal data

                     (102)

                     For each insertion and withdrawal cycle of a driver or workshop card in the equipment, the recording equipment shall record and store in its data memory:

                                 —

                                 the card holder's surname and first name(s) as stored in the card,

                                 —

                                 the card's number, issuing Member State and expiry date as stored in the card,

                                 —

                                 the card generation,

                                 —

                                 the insertion date and time,

                                 —

                                 the vehicle odometer value at card insertion,

                                 —

                                 the slot in which the card is inserted,

                                 —

                                 the withdrawal date and time,

                                 —

                                 the vehicle odometer value at card withdrawal,

                                 —

                                 the following information about the previous vehicle used by the driver, as stored in the card:

                                             —

                                             VRN and registering Member State,

                                             —

                                             VU generation (when available),

                                             —

                                             card withdrawal date and time,

                                 —

                                 a flag indicating whether, at card insertion, the card holder has manually entered activities or not.

                     (103)

                     The data memory shall be able to hold these data for at least 365 days.

                     (104)

                     When storage capacity is exhausted, new data shall replace oldest data.

               3.12.4   Driver activity data

                     (105)

                     The recording equipment shall record and store in its data memory whenever there is a change of activity for the driver and/or the co-driver, and/or whenever there is a change of driving status, and/or whenever there is an insertion or withdrawal of a driver or workshop card:

                                 —

                                 the driving status (CREW, SINGLE),

                                 —

                                 the slot (DRIVER, CO-DRIVER),

                                 —

                                 the card status in the relevant slot (INSERTED, NOT INSERTED),

                                 —

                                 the activity (DRIVING, AVAILABILITY, WORK, BREAK/REST),

                                 —

                                 the date and time of the change.

                           INSERTED means that a valid driver or workshop card is inserted in the slot. NOT INSERTED means the opposite i.e. no valid driver or workshop card is inserted in the slot (e.g. a company card is inserted or no card is inserted)
                     Activity data manually entered by a driver are not recorded in the data memory.

                     (106)

                     The data memory shall be able to hold driver activity data for at least 365 days.

                     (107)

                     When storage capacity is exhausted, new data shall replace oldest data.

               3.12.5   Places and positions where daily work periods begin, end, and/or where 3 hours' continuous driving time is reached

                     (108)

                     The recording equipment shall record and store in its data memory:

                                 —

                                 places and positions where the driver and/or the co-driver begins his daily work period;

                                 —

                                 positions where the continuous driving time of the driver reaches a multiple of three hours;

                                 —

                                 places and positions where the driver and/or the co-driver ends his daily work period.

                     (109)

                     When the position of the vehicle is not available from the GNSS receiver at these times, the recording equipment shall use the latest available position, and the related date and time.

                     (110)

                     Together with each place or position, the recording equipment shall record and store in its data memory:

                                 —

                                 the (co-)driver card number and card issuing Member State,

                                 —

                                 the card generation,

                                 —

                                 the date and time of the entry,

                                 —

                                 the type of entry (begin, end or 3 hours continuous driving time),

                                 —

                                 the related GNSS accuracy, date and time if applicable;

                                 —

                                 the vehicle odometer value.

                     (111)

                     The data memory shall be able to hold places and positions where daily work periods begin, end and/or where 3 hours continuous driving time is reached for at least 365 days.

                     (112)

                     When storage capacity is exhausted, new data shall replace oldest data.

               3.12.6   Odometer data

                     (113)

                     The recording equipment shall record in its data memory the vehicle odometer value and the corresponding date at midnight every calendar day.

                     (114)

                     The data memory shall be able to store midnight odometer values for at least 365 calendar days.

                     (115)

                     When storage capacity is exhausted, new data shall replace oldest data.

               3.12.7   Detailed speed data

                     (116)

                     The recording equipment shall record and store in its data memory the instantaneous speed of the vehicle and the corresponding date and time at every second of at least the last 24 hours that the vehicle has been driven.

               3.12.8   Events data

         For the purpose of this subparagraph, time shall be recorded with a resolution of 1 second.

                     (117)

                     The recording equipment shall record and store in its data memory the following data for each event detected according to the following storage rules:

                                 Event

                                 Storage rules

                                 Data to be recorded per event

                                 Insertion of a non-valid card

                                             —

                                             the 10 most recent events.

                                             —

                                             date and time of event,

                                             —

                                             card(s) type, number, issuing Member State and generation of the card creating the event.

                                             —

                                             number of similar events that day

                                 Card conflict

                                             —

                                             the 10 most recent events.

                                             —

                                             date and time of beginning of event,

                                             —

                                             date and time of end of event,

                                             —

                                             card(s) type, number, issuing Member State and generation of the two cards creating the conflict.

                                 Driving without an appropriate card

                                             —

                                             the longest event for each of the 10 last days of occurrence,

                                             —

                                             the 5 longest events over the last 365 days.

                                             —

                                             date and time of beginning of event,

                                             —

                                             date and time of end of event,

                                             —

                                             card(s) type, number, issuing Member State and generation of any card inserted at beginning and/or end of the event,

                                             —

                                             number of similar events that day.

                                 Card insertion while driving

                                             —

                                             the last event for each of the 10 last days of occurrence,

                                             —

                                             date and time of the event,

                                             —

                                             card(s) type, number, issuing Member State and generation,

                                             —

                                             number of similar events that day

                                 Last card session not correctly closed

                                             —

                                             the 10 most recent events.

                                             —

                                             date and time of card insertion,

                                             —

                                             card(s) type, number, issuing Member State and generation,

                                             —

                                             last session data as read from the card:

                                                         —

                                                         date and time of card insertion,

                                                         —

                                                         VRN, Member State of registration and VU generation.

                                 Over speeding (1)

                                             —

                                             the most serious event for each of the 10 last days of occurrence (i.e. the one with the highest average speed),

                                             —

                                             the 5 most serious events over the last 365 days.

                                             —

                                             the first event having occurred after the last calibration

                                             —

                                             date and time of beginning of event,

                                             —

                                             date and time of end of event,

                                             —

                                             maximum speed measured during the event,

                                             —

                                             arithmetic average speed measured during the event,

                                             —

                                             card type, number, issuing Member State and generation of the driver card (if applicable),

                                             —

                                             number of similar events that day.

                                 Power supply interruption (2)

                                             —

                                             the longest event for each of the 10 last days of occurrence,

                                             —

                                             the 5 longest events over the last 365 days.

                                             —

                                             date and time of beginning of event,

                                             —

                                             date and time of end of event,

                                             —

                                             card(s) type, number, issuing Member State and generation of any card inserted at beginning and/or end of the event,

                                             —

                                             number of similar events that day.

                                 Communication error with the remote communication facility

                                             —

                                             the longest event for each of the 10 last days of occurrence,

                                             —

                                             the 5 longest events over the last 365 days.

                                             —

                                             date and time of beginning of event,

                                             —

                                             date and time of end of event,

                                             —

                                             card(s) type, number, issuing Member State and generation of any card inserted at beginning and/or end of the event,

                                             —

                                             number of similar events that day.

                                 Absence of position information from GNSS receiver

                                             —

                                             the longest event for each of the 10 last days of occurrence,

                                             —

                                             the 5 longest events over the last 365 days.

                                             —

                                             date and time of beginning of event,

                                             —

                                             date and time of end of event,

                                             —

                                             card(s) type, number, issuing Member State and generation of any card inserted at beginning and/or end of the event,

                                             —

                                             number of similar events that day.

                                 Motion data error

                                             —

                                             the longest event for each of the 10 last days of occurrence,

                                             —

                                             the 5 longest events over the last 365 days.

                                             —

                                             date and time of beginning of event,

                                             —

                                             date and time of end of event,

                                             —

                                             card(s) type, number, issuing Member State and generation of any card inserted at beginning and/or end of the event,

                                             —

                                             number of similar events that day.

                                 Vehicle motion conflict

                                             —

                                             the longest event for each of the 10 last days of occurrence,

                                             —

                                             the 5 longest events over the last 365 days.

                                             —

                                             date and time of beginning of event,

                                             —

                                             date and time of end of event,

                                             —

                                             card(s) type, number, issuing Member State and generation of any card inserted at beginning and/or end of the event,

                                             —

                                             number of similar events that day.

                                 Security breach attempt

                                             —

                                             the 10 most recent events per type of event.

                                             —

                                             date and time of beginning of event,

                                             —

                                             date and time of end of event (if relevant),

                                             —

                                             card(s) type, number, issuing Member State and generation of any card inserted at beginning and/or end of the event,

                                             —

                                             type of event.

                                 Time conflict

                                             —

                                             the longest event for each of the 10 last days of occurrence,

                                             —

                                             the 5 longest events over the last 365 days.

                                             —

                                             recording equipment date and time

                                             —

                                             GNSS date and time,

                                             —

                                             card(s) type, number, issuing Member State and generation of any card inserted at beginning and/or end of the event,

                                             —

                                             number of similar events that day.

                                 (1)

                                 The recording equipment shall also record and store in its data memory:

                                             —

                                             the date and time of the last OVER SPEEDING CONTROL,

                                             —

                                             the date and time of the first over speeding following this OVER SPEEDING CONTROL,

                                             —

                                             the number of over speeding events since the last OVER SPEEDING CONTROL.

                                 (2)

                                 These data may be recorded at power supply reconnection only, times may be known with an accuracy to the minute.

               3.12.9   Faults data

         For the purpose of this subparagraph, time shall be recorded with a resolution of 1 second.

                     (118)

                     The recording equipment shall attempt to record and store in its data memory the following data for each fault detected according to the following storage rules:

                                 Fault

                                 Storage rules

                                 Data to be recorded per fault

                                 Card fault

                                             —

                                             the 10 most recent driver card faults.

                                             —

                                             date and time of beginning of fault,

                                             —

                                             date and time of end of fault,

                                             —

                                             card(s) type, number, issuing Member State and generation.

                                 Recording equipment faults

                                             —

                                             the 10 most recent faults for each type of fault,

                                             —

                                             the first fault after the last calibration.

                                             —

                                             date and time of beginning of fault,

                                             —

                                             date and time of end of fault,

                                             —

                                             type of fault,

                                             —

                                             card(s) type, number and issuing Member State and generation of any card inserted at beginning and/or end of the fault.

               3.12.10   Calibration data

                     (119)

                     The recording equipment shall record and store in its data memory data relevant to:

                                 —

                                 known calibration parameters at the moment of activation,

                                 —

                                 its very first calibration following its activation,

                                 —

                                 its first calibration in the current vehicle (as identified by its VIN),

                                 —

                                 the 20 most recent calibrations (if several calibrations happen within one calendar day, only the first and the last one of the day shall be stored).

                     (120)

                     The following data shall be recorded for each of these calibrations:

                                 —

                                 purpose of calibration (activation, first installation, installation, periodic inspection),

                                 —

                                 workshop name and address,

                                 —

                                 workshop card number, card issuing Member State and card expiry date,

                                 —

                                 vehicle identification,

                                 —

                                 parameters updated or confirmed: w, k, l, tyre size, speed limiting device setting, odometer (old and new values), date and time (old and new values),

                                 —

                                 the types and identifiers of all the seals in place.

                     (121)

                     In addition, the recording equipment shall record and store in its data memory its ability to use first generation tachograph cards (still activated or not).

                     (122)

                     The motion sensor shall record and store in its memory the following motion sensor installation data:

                                 —

                                 first pairing with a VU (date, time, VU approval number, VU serial number),

                                 —

                                 last pairing with a VU (date, time, VU approval number, VU serial number).

                     (123)

                     The external GNSS facility shall record and store in its memory the following external GNSS facility installation data:

                                 —

                                 first coupling with a VU (date, time, VU approval number, VU serial number),

                                 —

                                 last coupling with a VU (date, time, VU approval number, VU serial number).

               3.12.11   Time adjustment data

                     (124)

                     The recording equipment shall record and store in its data memory data relevant to time adjustments performed in calibration mode outside the frame of a regular calibration (def. f)):

                                 —

                                 the most recent time adjustment,

                                 —

                                 the 5 largest time adjustments.

                     (125)

                     The following data shall be recorded for each of these time adjustments:

                                 —

                                 date and time, old value,

                                 —

                                 date and time, new value,

                                 —

                                 workshop name and address,

                                 —

                                 workshop card number, card issuing Member State, card generation and card expiry date.

               3.12.12   Control activity data

                     (126)

                     The recording equipment shall record and store in its data memory the following data relevant to the 20 most recent control activities:

                                 —

                                 date and time of the control,

                                 —

                                 control card number, card issuing Member State and card generation,

                                 —

                                 type of the control (displaying and/or printing and/or VU downloading and/or card downloading and/or roadside calibration checking).

                     (127)

                     In case of downloading, the dates of the oldest and of the most recent days downloaded shall also be recorded.

               3.12.13   Company locks data

                     (128)

                     The recording equipment shall record and store in its data memory the following data relevant to the 255 most recent company locks:

                                 —

                                 lock-in date and time,

                                 —

                                 lock-out date and time,

                                 —

                                 company card number, card issuing Member State and card generation,

                                 —

                                 company name and address.

                           Data previously locked by a lock removed from memory due to the limit above, shall be treated as not locked.

               3.12.14   Download activity data

                     (129)

                     The recording equipment shall record and store in its data memory the following data relevant to the last data memory downloading to external media while in company or in calibration mode:

                                 —

                                 date and time of downloading,

                                 —

                                 company or workshop card number, card issuing Member State and card generation,

                                 —

                                 company or workshop name.

               3.12.15   Specific conditions data

                     (130)

                     The recording equipment shall record in its data memory the following data relevant to specific conditions:

                                 —

                                 date and time of the entry,

                                 —

                                 type of specific condition.

                     (131)

                     The data memory shall be able to hold specific conditions data for at least 365 days (with the assumption that on average, 1 condition is opened and closed per day). When storage capacity is exhausted, new data shall replace oldest data.

               3.12.16   Tachograph card data

                     (132)

                     The recording equipment shall be able to store the following data related to the different tachograph cards in which had been used in the VU:

                                 —

                                 the tachograph card number and its serial number,

                                 —

                                 the manufacturer of the tachograph card,

                                 —

                                 the tachograph card type,

                                 —

                                 the tachograph card version.

                     (133)

                     The recording equipment shall be able to store at least 88 such records.

               3.13   Reading from tachograph cards

                     (134)

                     The recording equipment shall be able to read from first and second generation tachograph cards, where applicable, the necessary data:

                                 —

                                 to identify the card type, the card holder, the previously used vehicle, the date and time of the last card withdrawal and the activity selected at that time,

                                 —

                                 to check that last card session was correctly closed,

                                 —

                                 to compute the driver's continuous driving time, cumulative break time and cumulated driving times for the previous and the current week,

                                 —

                                 to print requested printouts related to data recorded on a driver card,

                                 —

                                 to download a driver card to external media.

                           This requirement only applies to first generation tachograph cards if their use has not been suppressed by a workshop.

                     (135)

                     In case of a reading error, the recording equipment shall try again, three times maximum, the same read command, and then if still unsuccessful, declare the card faulty and non-valid.

               3.14   Recording and storing on tachograph cards

         3.14.1   Recording and storing in first generation tachograph cards

                     (136)

                     Provided first generation tachograph cards use has not been suppressed by a workshop, the recording equipment shall record and store data exactly in the same way as a first generation recording equipment would do.

                     (137)

                     The recording equipment shall set the ‘card session data’ in the driver or workshop card right after the card insertion.

                     (138)

                     The recording equipment shall update data stored on valid driver, workshop, company and/or control cards with all necessary data relevant to the period while the card is inserted and relevant to the card holder. Data stored on these cards are specified in Chapter 4.

                     (139)

                     The recording equipment shall update driver activity and places data (as specified in 4.5.3.1.9 and 4.5.3.1.11), stored on valid driver and/or workshop cards, with activity and places data manually entered by the cardholder.

                     (140)

                     All events not defined for the first generation recording equipment, shall not be stored on the driver and workshop cards.

                     (141)

                     Tachograph cards data update shall be such that, when needed and taking into account card actual storage capacity, most recent data replace oldest data.

                     (142)

                     In the case of a writing error, the recording equipment shall try again, three times maximum, the same write command and then if still unsuccessful, declare the card faulty and non-valid.

                     (143)

                     Before releasing a driver card and after all relevant data have been stored on the card, the recording equipment shall reset the ‘card session data’.

               3.14.2   Recording and storing in second generation tachograph cards

                     (144)

                     Second generation tachograph cards shall contain 2 different card applications, the first of which shall be exactly the same as the TACHO application of first generation tachograph cards, and the second the ‘TACHO_G2’ application, as specified in Chapter 4 and Appendix 2.

                     (145)

                     The recording equipment shall set the ‘card session data’ in the driver or workshop card right after the card insertion.

                     (146)

                     The recording equipment shall update data stored on the 2 card applications of valid driver, workshop, company and/or control cards with all necessary data relevant to the period while the card is inserted and relevant to the card holder. Data stored on these cards are specified in Chapter 4.

                     (147)

                     The recording equipment shall update driver activity places and positions data (as specified in 4.5.3.1.9, 4.5.3.1.11, 4.5.3.2.9 and 4.5.3.2.11), stored on valid driver and/or workshop cards, with activity and places data manually entered by the cardholder.

                     (148)

                     Tachograph cards data update shall be such that, when needed and taking into account card actual storage capacity, most recent data replace oldest data.

                     (149)

                     In the case of a writing error, the recording equipment shall try again, three times maximum, the same write command and then if still unsuccessful, declare the card faulty and non-valid.

                     (150)

                     Before releasing a driver card and after all relevant data have been stored on the 2 card applications of the card, the recording equipment shall reset the ‘card session data’.

               3.15   Displaying

                     (151)

                     The display shall include at least 20 characters.

                     (152)

                     The minimum character size shall be 5 mm high and 3.5 mm wide.

                     (153)

                     The display shall support the characters specified in Appendix 1 Chapter 4 ‘Character sets’. The display may use simplified glyphs (e.g. accented characters may be displayed without accent, or lower case letters may be shown as upper case letters).

                     (154)

                     The display shall be provided with adequate non-dazzling lighting.

                     (155)

                     Indications shall be visible from outside the recording equipment.

                     (156)

                     The recording equipment shall be able to display:

                                 —

                                 default data,

                                 —

                                 data related to warnings,

                                 —

                                 data related to menu access,

                                 —

                                 other data requested by a user.

                           Additional information may be displayed by the recording equipment, provided that it is clearly distinguishable from information required above.

                     (157)

                     The display of the recording equipment shall use the pictograms or pictograms combinations listed in Appendix 3. Additional pictograms or pictograms combinations may also be provided by the display, if clearly distinguishable from the aforementioned pictograms or pictograms combinations.

                     (158)

                     The display shall always be ON when the vehicle is moving.

                     (159)

                     The recording equipment may include a manual or automatic feature to turn the display OFF when the vehicle is not moving.
                     Displaying format is specified in Appendix 5.

               3.15.1   Default display

                     (160)

                     When no other information needs to be displayed, the recording equipment shall display, by default, the following:

                                 —

                                 the local time (as a result of UTC time + offset as set by the driver),

                                 —

                                 the mode of operation,

                                 —

                                 the current activity of the driver and the current activity of the co-driver,

                                 —

                                 information related to the driver:

                                 —

                                 if his current activity is DRIVING, his current continuous driving time and his current cumulative break time,

                                 —

                                 if his current activity is not DRIVING, the current duration of this activity (since it was selected) and his current cumulative break time.

                     (161)

                     Display of data related to each driver shall be clear, plain and unambiguous. In the case where the information related to the driver and the co-driver cannot be displayed at the same time, the recording equipment shall display by default the information related to the driver and shall allow the user to display the information related to the co-driver.

                     (162)

                     In the case where the display width does not allow displaying by default the mode of operation, the recording equipment shall briefly display the new mode of operation when it changes.

                     (163)

                     The recording equipment shall briefly display the card holder name at card insertion.

                     (164)

                     When an ‘OUT OF SCOPE’ or FERRY/TRAIN condition is opened, then the default display must show using the relevant pictogram that the particular condition is opened (it is acceptable that the driver's current activity may not be shown at the same time).

               3.15.2   Warning display

                     (165)

                     The recording equipment shall display warning information using primarily the pictograms of Appendix 3, completed where needed by additional numerically coded information. A literal description of the warning may also be added in the driver's preferred language.

               3.15.3   Menu access

                     (166)

                     The recording equipment shall provide necessary commands through an appropriate menu structure.

               3.15.4   Other displays

                     (167)

                     It shall be possible to display selectively on request:

                                 —

                                 the UTC date and time, and local time offset,

                                 —

                                 the content of any of the six printouts under the same formats as the printouts themselves,

                                 —

                                 the continuous driving time and cumulative break time of the driver,

                                 —

                                 the continuous driving time and cumulative break time of the co-driver,

                                 —

                                 the cumulated driving time of the driver for the previous and the current week,

                                 —

                                 the cumulated driving time of the co-driver for the previous and the current week,

                           optional:

                                 —

                                 the current duration of co-driver activity (since it was selected),

                                 —

                                 the cumulated driving time of the driver for current week,

                                 —

                                 the cumulated driving time of the co-driver for the current daily work period,

                                 —

                                 the cumulated driving time of the driver for the current daily work period.

                     (168)

                     Printout content display shall be sequential, line by line. If the display width is less than 24 characters the user shall be provided with the complete information through an appropriate mean (several lines, scrolling, …).
                     Printout lines devoted to hand-written information may be omitted for display.

               3.16   Printing

                     (169)

                     The recording equipment shall be able to print information from its data memory and/or from tachograph cards in accordance with the seven following printouts:

                                 —

                                 driver activities from card daily printout,

                                 —

                                 driver activities from Vehicle Unit daily printout,

                                 —

                                 events and faults from card printout,

                                 —

                                 events and faults from Vehicle Unit printout,

                                 —

                                 technical data printout,

                                 —

                                 over speeding printout.

                                 —

                                 tachograph card data history for a given VU (see chapter 3.12.16)

                           The detailed format and content of these printouts are specified in Appendix 4.
                     Additional data may be provided at the end of the printouts.
                     Additional printouts may also be provided by the recording equipment, if clearly distinguishable from the seven aforementioned printouts.

                     (170)

                     The ‘driver activities from card daily printout’ and ‘Events and faults from card printout’ shall be available only when a driver card or a workshop card is inserted in the recording equipment. The recording equipment shall update data stored on the relevant card before starting printing.

                     (171)

                     In order to produce the ‘driver activities from card daily printout’ or the ‘events and faults from card printout’, the recording equipment shall:

                                 —

                                 either automatically select the driver card or the workshop card if one only of these cards is inserted,

                                 —

                                 or provide a command to select the source card or select the card in the driver slot if two of these cards are inserted in the recording equipment.

                     (172)

                     The printer shall be able to print 24 characters per line.

                     (173)

                     The minimum character size shall be 2.1 mm high and 1.5 mm wide.

                     (174)

                     The printer shall support the characters specified in Appendix 1 Chapter 4 ‘Character sets’.

                     (175)

                     Printers shall be so designed as to produce these printouts with a degree of definition likely to avoid any ambiguity when they are read.

                     (176)

                     Printouts shall retain their dimensions and recordings under normal conditions of humidity (10-90 %) and temperature.

                     (177)

                     The type approved paper used by the recording equipment shall bear the relevant type approval mark and an indication of the type(s) of recording equipment with which it may be used.

                     (178)

                     Printouts shall remain clearly legible and identifiable under normal conditions of storage, in terms of light intensity, humidity and temperature, for at least two years.

                     (179)

                     Printouts shall conform at least to the test specifications defined in Appendix 9.

                     (180)

                     It shall also be possible to add hand-written notes, such as the driver's signature, to these documents.

                     (181)

                     The recording equipment shall manage ‘paper out’ events while printing by, once paper has been re-loaded, restarting printing from printout beginning or by continuing printing and providing an unambiguous reference to previously printed part.

               3.17   Warnings

                     (182)

                     The recording equipment shall warn the driver when detecting any event and/or fault.

                     (183)

                     Warning of a power supply interruption event may be delayed until the power supply is reconnected.

                     (184)

                     The recording equipment shall warn the driver 15 minutes before and at the time of exceeding the maximum allowed continuous driving time.

                     (185)

                     Warnings shall be visual. Audible warnings may also be provided in addition to visual warnings.

                     (186)

                     Visual warnings shall be clearly recognisable by the user, shall be situated in the driver's field of vision and shall be clearly legible both by day and by night.

                     (187)

                     Visual warnings may be built into the recording equipment and/or remote from the recording equipment.

                     (188)

                     In the latter case it shall bear a ‘T’ symbol.

                     (189)

                     Warnings shall have a duration of at least 30 seconds, unless acknowledged by the user by hitting one or more specific keys of the recording equipment. This first acknowledgement shall not erase warning cause display referred to in next paragraph.

                     (190)

                     Warning cause shall be displayed on the recording equipment and remain visible until acknowledged by the user using a specific key or command of the recording equipment.

                     (191)

                     Additional warnings may be provided, as long as they do not confuse drivers in relation to previously defined ones.

               3.18   Data downloading to external media

                     (192)

                     The recording equipment shall be able to download on request data from its data memory or from a driver card to external storage media via the calibration/downloading connector. The recording equipment shall update data stored on the relevant card before starting downloading.

                     (193)

                     In addition and as an optional feature, the recording equipment may, in any mode of operation, download data through any another means to a company authenticated through this channel. In such a case, company mode data access rights shall apply to this download.

                     (194)

                     Downloading shall not alter or delete any stored data.

                     (195)

                     The calibration/downloading connector electrical interface is specified in Appendix 6.

                     (196)

                     Downloading protocols are specified in Appendix 7.

               3.19   Remote communication for targeted roadside checks

                     (197)

                     When the ignition is on, the Vehicle Unit shall store every 60 seconds in the remote communication facility the most recent data necessary for the purpose of targeted roadside checks. Such data shall be encrypted and signed as specified in Appendix 11 and Appendix 14.

                     (198)

                     Data to be checked remotely shall be available to remote communication readers through wireless communication, as specified in Appendix 14.

                     (199)

                     Data necessary for the purpose of targeted roadside checks shall be related to:

                                 —

                                 the latest security breach attempt,

                                 —

                                 the longest power supply interruption,

                                 —

                                 sensor fault,

                                 —

                                 motion data error,

                                 —

                                 vehicle motion conflict,

                                 —

                                 driving without a valid card,

                                 —

                                 card insertion while driving,

                                 —

                                 time adjustment data,

                                 —

                                 calibration data including the dates of the two latest stored calibration records,

                                 —

                                 vehicle registration number,

                                 —

                                 speed recorded by the tachograph.

               3.20   Output data to additional external devices

                     (200)

                     The recording equipment may also be equipped with standardised interfaces allowing the data recorded or produced by tachograph to be used in operational or calibration mode, by an external facility.
                     In Appendix 13, an optional ITS interface is specified and standardized. Other similar interfaces may co-exist, provided they fully comply with the requirements of Appendix 13 in term of minimum list of data, security and driver consent.
                     The following requirements apply to ITS data made available through that interface:

                                 —

                                 these data are a set of selected existing data from the tachograph data dictionary (Appendix 1),

                                 —

                                 a subset of these selected data are marked ‘personal data’,

                                 —

                                 the subset of ‘personal data’ is only available if the verifiable consent of the driver, accepting his personal data can leave the vehicle network, is enabled,

                                 —

                                 At any moment, the driver consent can be enabled or disabled through commands in the menu, provided the driver card is inserted,

                                 —

                                 the set and subset of data will be broadcasted via Bluetooth wireless protocol in the radius of the vehicle cab, with a refresh rate of 1 minute,

                                 —

                                 the pairing of the external device with the ITS interface will be protected by a dedicated and random PIN of at least 4 digits, recorded in and available through the display of each vehicle unit,

                                 —

                                 in any circumstances, the presence of the ITS interface cannot disturb or affect the correct functioning and the security of the vehicle unit.

                           Other data may also be output in addition to the set of selected existing data, considered as the minimum list, provided they cannot be considered as personal data.
                     The recording equipment shall notify other external facilities about the consent of the driver.
                     When the ignition of the vehicle is ON, these data shall be permanently broadcasted.

                     (201)

                     The serial link interface as specified in Annex 1B to Regulation (EEC) No. 3821/85, as last amended, can continue to equip tachographs for back compatibility. Anyhow, the driver consent is still required in case personal data are transmitted.

               3.21   Calibration

                     (202)

                     The calibration function shall allow:

                                 —

                                 to automatically pair the motion sensor with the VU,

                                 —

                                 to automatically couple the external GNSS facility with the VU if applicable,

                                 —

                                 to digitally adapt the constant of the recording equipment (k) to the characteristic coefficient of the vehicle (w),

                                 —

                                 to adjust the current time within the validity period of the inserted workshop card,

                                 —

                                 to adjust the current odometer value,

                                 —

                                 to update motion sensor identification data stored in the data memory,

                                 —

                                 to update, if applicable, external GNSS facility identification data stored in the data memory,

                                 —

                                 to update the types and identifiers of all the seals in place,

                                 —

                                 to update or confirm other parameters known to the recording equipment: vehicle identification, w, l, tyre size and speed limiting device setting if applicable.

                     (203)

                     In addition, the calibration function shall allow to supress the use of first generation tachograph cards in the recording equipment, provided the conditions specified in Appendix 15 are met.

                     (204)

                     Pairing the motion sensor to the VU shall consist, at least, in:

                                 —

                                 updating motion sensor installation data held by the motion sensor (as needed),

                                 —

                                 copying from the motion sensor to the VU data memory the necessary motion sensor identification data.

                     (205)

                     Coupling the external GNSS facility to the VU shall consist, at least, in:

                                 —

                                 updating external GNSS facility installation data held by the external GNSS facility (as needed),

                                 —

                                 copying from the external GNSS facility to the VU data memory the necessary external GNSS facility identification data including the serial number of the external GNSS facility,

                           The coupling shall be followed by the verification of the GNSS position information.

                     (206)

                     The calibration function shall be able to input necessary data through the calibration/downloading connector in accordance with the calibration protocol defined in Appendix 8. The calibration function may also input necessary data through other means.

               3.22   Roadside calibration checking

                     (207)

                     The roadside calibration checking function shall allow reading the motion sensor serial number (possibly embedded in the adaptor) and the external GNSS facility serial number (when applicable), connected to the vehicle unit, at the time of the request.

                     (208)

                     This reading shall at least be possible on the vehicle unit display through commands in the menus.

                     (209)

                     The roadside calibration checking function shall also allow controlling the selection of the I/O mode of the calibration I/O signal line specified in Appendix 6, via the K-line interface. This shall be done through the ECUAdjustmentSession, as specified in Appendix 8, section 7 Control of Test Pulses — Input output control functional unit.

               3.23   Time adjustment

                     (210)

                     The time adjustment function shall allow for automatically adjusting the current time. Two time sources are used in the recording equipment for time adjustment: 1) the internal VU clock, 2) the GNSS receiver.

                     (211)

                     The time setting of the VU internal clock shall be automatically re-adjusted at intervals of 12 hours maximum. When this delay has expired and the GNSS signal is not available, the time setting shall be done as soon as the VU can access a valid time provided by GNSS receiver, according to the vehicle ignition conditions. The time reference for the automatic time setting of the VU internal clock shall be derived from the GNSS receiver. A time conflict event shall be triggered if the current time deviates more than one (1) minute from the time information provided by the GNSS receiver.

                     (212)

                     The time adjustment function shall also allow for triggered adjustment of the current time, in calibration mode.

               3.24   Performance characteristics

                     (213)

                     The Vehicle Unit shall be fully operational in the temperature range – 20 °C to 70 °C, the external GNSS facility in the temperature range – 20 °C to 70 °C, and the motion sensor in the temperature range – 40 °C to 135 °C. Data memory content shall be preserved at temperatures down to – 40 °C.

                     (214)

                     The tachograph shall be fully operational in the humidity range 10 % to 90 %.

                     (215)

                     The seals used in the smart tachograph shall withstand the same conditions than those applicable to the tachograph components to which they are affixed.

                     (216)

                     The recording equipment shall be protected against over-voltage, inversion of its power supply polarity, and short circuits.

                     (217)

                     Motion sensors shall either:

                                 —

                                 react to a magnetic field disturbing vehicle motion detection. In such circumstances, the vehicle unit will record and store a sensor fault (requirement 88) or,

                                 —

                                 have a sensing element that is protected from, or immune to, magnetic fields.

                     (218)

                     The recording equipment and the external GNSS facility shall conform to international regulation UN ECE R10 and shall be protected against electrostatic discharges and transients.

               3.25   Materials

                     (219)

                     All the constituent parts of the recording equipment shall be made of materials of sufficient stability and mechanical strength and with stable electrical and magnetic characteristics.

                     (220)

                     For normal conditions of use, all the internal parts of the equipment shall be protected against damp and dust.

                     (221)

                     The Vehicle Unit and the external GNSS facility shall meet the protection grade IP 40 and the motion sensor shall meet the protection grade IP 64, as per standard IEC 60529:1989 including A1:1999 and A2:2013.

                     (222)

                     The recording equipment shall conform to applicable technical specifications related to ergonomic design.

                     (223)

                     The recording equipment shall be protected against accidental damage.

               3.26   Markings

                     (224)

                     If the recording equipment displays the vehicle odometer value and speed, the following details shall appear on its display:

                                 —

                                 near the figure indicating the distance, the unit of measurement of distance, indicated by the abbreviation ‘km’,

                                 —

                                 near the figure showing the speed, the entry ‘km/h’.

                           The recording equipment may also be switched to display the speed in miles per hour, in which case the unit of measurement of speed shall be shown by the abbreviation ‘mph’. The recording equipment may also be switched to display the distance in miles, in which case the unit of measurement of distance shall be shown by the abbreviation ‘mi’.

                     (225)

                     A descriptive plaque shall be affixed to each separate component of the recording equipment and shall show the following details:

                                 —

                                 name and address of the equipment manufacturer,

                                 —

                                 manufacturer's part number and year of manufacture of the equipment,

                                 —

                                 equipment serial number,

                                 —

                                 approval mark for the equipment type.

                     (226)

                     When physical space is not sufficient to show all above mentioned details, the descriptive plaque shall show at least: the manufacturer's name or logo, and the equipment's part number.

               4.   CONSTRUCTION AND FUNCTIONAL REQUIREMENTS FOR TACHOGRAPH CARDS
         4.1   Visible data

         The front page shall contain:

                     (227)

                     the words ‘Driver card’ or ‘Control card’ or ‘Workshop card’ or ‘Company card’ printed in capital letters in the official language or languages of the Member State issuing the card, according to the type of the card.

                     (228)

                     the name of the Member State issuing the card (optional);

                     (229)

                     the distinguishing sign of the Member State issuing the card, printed in negative in a blue rectangle and encircled by 12 yellow stars. The distinguishing signs shall be as follows:

                                 B
                                 BG
                                 CZ
                                 CY

                                 Belgium
                                 Bulgaria
                                 Czech Republic
                                 Cyprus

                                 LV
                                 L
                                 LT
                                 M

                                 Latvia
                                 Luxembourg
                                 Lithuania
                                 Malta

                                 DK

                                 Denmark

                                 NL

                                 The Netherlands

                                 D
                                 EST

                                 Germany
                                 Estonia

                                 A
                                 PL

                                 Austria
                                 Poland

                                 GR

                                 Greece

                                 P
                                 RO
                                 SK
                                 SLO

                                 Portugal
                                 Romania
                                 Slovakia
                                 Slovenia

                                 E

                                 Spain

                                 FIN

                                 Finland

                                 F
                                 HR
                                 H

                                 France
                                 Croatia
                                 Hungary

                                 S

                                 Sweden

                                 IRL

                                 Ireland

                                 UK

                                 The United Kingdom

                                 I

                                 Italy

                     (230)

                     information specific to the card issued, numbered as follows:

                                 Driver card

                                 Control Card

                                 Company or Workshop card

                                 1.

                                 surname of the driver

                                 control body name

                                 company or workshop name

                                 2.

                                 first name(s) of the driver

                                 surname of the controller
                                 (if applicable)

                                 surname of card holder
                                 (if applicable)

                                 3.

                                 birth date of the driver

                                 first name(s) of the controller
                                 (if applicable)

                                 first name(s) of card holder
                                 (if applicable)

                                 4.a

                                 card start of validity date

                                 4.b

                                 card expiry date

                                 4.c

                                 the name of the issuing authority (may be printed on reverse page)

                                 4.d

                                 a different number from the one under heading 5, for administrative purposes (optional)

                                 5. a

                                 Driving licence number
                                 (at the date of issue of the driver card)

                                 —

                                 —

                                 5. b

                                 Card number

                                 6.

                                 Photograph of the driver

                                 photograph of the controller (optional)

                                 photograph of the fitter (optional)-

                                 7.

                                 Signature of the holder (optional)

                                 8.

                                 Normal place of residence, or postal address of the holder (optional).

                                 Postal address of control body

                                 postal address of company or workshop

                     (231)

                     dates shall be written using a ‘dd/mm/yyyy’ or ‘dd.mm.yyyy’ format (day, month, year).

               The reverse page shall contain:

                     (232)

                     an explanation of the numbered items which appear on the front page of the card;

                     (233)

                     with the specific written agreement of the holder, information which is not related to the administration of the card may also be added, such addition will not alter in any way the use of the model as a tachograph card.

                     (234)

                     Tachograph cards shall be printed with the following background predominant colours:
                     —   driver card: white,
                     —   control card: blue,
                     —   workshop card: red,
                     —   company card: yellow.

                     (235)

                     Tachograph cards shall bear at least the following features for protection of the card body against counterfeiting and tampering:

                                 —

                                 a security design background with fine guilloche patterns and rainbow printing,

                                 —

                                 in the area of the photograph, the security design background and the photograph shall overlap,

                                 —

                                 at least one two-coloured microprint line.

                     (236)

                     After consulting the Commission, Member States may add colours or markings, such as national symbols and security features, without prejudice to the other provisions of this Annex.

                     (237)

                     Temporary cards referred to in Article 26.4 of Regulation (EU) No. 165/2014 shall comply with the provisions of this Annex.

               4.2   Security

         The system security aims at protecting integrity and authenticity of data exchanged between the cards and the recording equipment, protecting the integrity and authenticity of data downloaded from the cards, allowing certain write operations onto the cards to recording equipment only, decrypting certain data, ruling out any possibility of falsification of data stored in the cards, preventing tampering and detecting any attempt of that kind.

                     (238)

                     In order to achieve the system security, the tachograph cards shall meet the security requirements defined in Appendixes 10 and 11.

                     (239)

                     Tachograph cards shall be readable by other equipment such as personal computers.

               4.3   Standards

                     (240)

                     Tachograph cards shall comply with the following standards:

                                 —

                                 ISO/IEC 7810 Identification cards — Physical characteristics,

                                 —

                                 ISO/IEC 7816 Identification cards — Integrated circuit cards:

                                             —

                                             Part 1: Physical characteristics,

                                             —

                                             Part 2: Dimensions and position of the contacts (ISO/IEC 7816-2:2007),

                                             —

                                             Part 3: Electrical interface and transmission protocols (ISO/IEC 7816-3:2006),

                                             —

                                             Part 4: Organisation, security and commands for interchange (ISO/IEC 7816-4:2013 + Cor 1:2014),

                                             —

                                             Part 6: Interindustry data elements for interchange (ISO/IEC 7816-6:2004 + Cor 1:2006),

                                             —

                                             Part 8: Commands for security operations (ISO/IEC 7816-8:2004).

                                 —

                                 Tachograph cards shall be tested in accordance to ISO/IEC 10373-3:2010 Identification cards — Test methods — Part 3: Integrated circuit cards with contacts and related interface devices.

               4.4   Environmental and electrical specifications

                     (241)

                     Tachograph cards shall be capable of operating correctly in all the climatic conditions normally encountered in Community territory and at least in the temperature range – 25 °C to + 70 °C with occasional peaks of up to + 85 °C, ‘occasional’ meaning not more than 4 hours each time and not over 100 times during the life time of the card.

                     (242)

                     Tachograph cards shall be capable of operating correctly in the humidity range 10 % to 90 %.

                     (243)

                     Tachograph cards shall be capable of operating correctly for a five-year period if used within the environmental and electrical specifications.

                     (244)

                     During operation, tachograph cards shall conform to ECE R10, related to electromagnetic compatibility, and shall be protected against electrostatic discharges.

               4.5   Data storage

         For the purpose of this paragraph,

                     —

                     times are recorded with a resolution of one minute, unless otherwise specified,

                     —

                     odometer values are recorded with a resolution of one kilometre,

                     —

                     speeds are recorded with a resolution of 1 km/h,

                     —

                     positions (latitudes and longitudes) are recorded in degrees and minutes with a resolution of 1/10 of minute.

               The tachograph cards functions, commands and logical structures, fulfilling data storage requirements are specified in Appendix 2.
         If not otherwise specified, data storage on tachograph cards shall be organized in such a way, that new data replaces stored oldest data in case the foreseen memory size for the particular records is exhausted.

                     (245)

                     This paragraph specifies minimum storage capacity for the various application data files. Tachograph cards shall be able to indicate to the recording equipment the actual storage capacity of these data files.

                     (246)

                     Any additional data that may be stored on tachograph cards, related to other applications possibly borne by the card, shall be stored in accordance with Directive 95/46/EC and with Directive 2002/58/EC and in compliance with Article 7 of Regulation (EU) No. 165/2014.

                     (247)

                     Each Master File (MF) of any tachograph card shall contain up to five Elementary Files (EF) for card management, application and chip identifications, and two Dedicated Files (DF):

                                 —

                                 DF Tachograph, which contains the application accessible to first generation vehicle units, which is also present in first generation tachograph cards,

                                 —

                                 DF Tachograph_G2, which contains the application only accessible to second generation vehicle units, which is only present in second generation tachograph cards.

                           The full details of the tachograph cards structure are specified in Appendix 2.

               4.5.1   Elementary files for identification and card management

         4.5.2   IC card identification

                     (248)

                     Tachograph cards shall be able to store the following smart card identification data:

                                 —

                                 clock stop,

                                 —

                                 card serial number (including manufacturing references),

                                 —

                                 card type approval number,

                                 —

                                 card personaliser identification (ID),

                                 —

                                 embedder ID,

                                 —

                                 IC identifier.

               4.5.2.1   Chip identification

                     (249)

                     Tachograph cards shall be able to store the following Integrated Circuit (IC) identification data:

                                 —

                                 IC serial number,

                                 —

                                 IC manufacturing references.

               4.5.2.2   DIR (only present in second generation tachograph cards)

                     (250)

                     Tachograph cards shall be able to store the application identification data objects specified in Appendix 2.

               4.5.2.3   ATR information (conditional, only present in second generation tachograph cards)

                     (251)

                     Tachograph cards shall be able to store the following extended length information data object:

                                 —

                                 in the case the tachograph card supports extended length fields, the extended length information data object specified in Appendix 2.

               4.5.2.4   Extended length information (conditional, only present in second generation tachograph cards)

                     (252)

                     Tachograph cards shall be able to store the following extended length information data objects:

                                 —

                                 in the case the tachograph card supports extended length fields, the extended length information data objects specified in Appendix 2.

               4.5.3   Driver card

         4.5.3.1   Tachograph application (accessible to first and second generation vehicle units)

         4.5.3.1.1   Application identification

                     (253)

                     The driver card shall be able to store the following application identification data:

                                 —

                                 tachograph application identification,

                                 —

                                 type of tachograph card identification.

               4.5.3.1.2   Key and certificates

                     (254)

                     The driver card shall be able to store a number of cryptographic keys and certificates, as specified in Appendix 11 part A.

               4.5.3.1.3   Card identification

                     (255)

                     The driver card shall be able to store the following card identification data:

                                 —

                                 card number,

                                 —

                                 issuing Member State, issuing authority name, issue date,

                                 —

                                 card beginning of validity date, card expiry date.

               4.5.3.1.4   Card holder identification

                     (256)

                     The driver card shall be able to store the following card holder identification data:

                                 —

                                 surname of the holder,

                                 —

                                 first name(s) of the holder,

                                 —

                                 date of birth,

                                 —

                                 preferred language.

               4.5.3.1.5   Card download

                     (257)

                     The driver card shall be able to store the following data related to card download:

                                 —

                                 date and time of last card download (for other purposes than control).

                     (258)

                     The driver card shall be able to hold one such record.

               4.5.3.1.6   Driving licence information

                     (259)

                     The driver card shall be able to store the following driving licence data:

                                 —

                                 issuing Member State, issuing authority name,

                                 —

                                 driving licence number (at the date of the issue of the card).

               4.5.3.1.7   Events data
         For the purpose of this subparagraph, time shall be stored with a resolution of 1 second.

                     (260)

                     The driver card shall be able to store data related to the following events detected by the recording equipment while the card was inserted:

                                 —

                                 Time overlap (where this card is the cause of the event),

                                 —

                                 Card insertion while driving (where this card is the subject of the event),

                                 —

                                 Last card session not correctly closed (where this card is the subject of the event),

                                 —

                                 Power supply interruption,

                                 —

                                 Motion data error,

                                 —

                                 Security breach attempts.

                     (261)

                     The driver card shall be able to store the following data for these events:

                                 —

                                 Event code,

                                 —

                                 Date and time of beginning of the event (or of card insertion if the event was on-going at that time),

                                 —

                                 Date and time of end of the event (or of card withdrawal if the event was on-going at that time),

                                 —

                                 VRN and registering Member State of vehicle in which the event happened.

                           Note: For the ‘Time overlap’ event:

                                 —

                                 Date and time of beginning of the event shall correspond to the date and time of the card withdrawal from the previous vehicle,

                                 —

                                 Date and time of end of the event shall correspond to the date and time of card insertion in current vehicle,

                                 —

                                 Vehicle data shall correspond to the current vehicle raising the event.

                           Note: For the ‘Last card session not correctly closed’ event:

                                 —

                                 date and time of beginning of event shall correspond to the card insertion date and time of the session not correctly closed,

                                 —

                                 date and time of end of event shall correspond to the card insertion date and time of the session during which the event was detected (current session),

                                 —

                                 Vehicle data shall correspond to the vehicle in which the session was not correctly closed.

                     (262)

                     The driver card shall be able to store data for the six most recent events of each type (i.e. 36 events).

               4.5.3.1.8   Faults data
         For the purpose of this subparagraph, time shall be recorded with a resolution of 1 second.

                     (263)

                     The driver card shall be able to store data related to the following faults detected by the recording equipment while the card was inserted:

                                 —

                                 Card fault (where this card is the subject of the event),

                                 —

                                 Recording equipment fault.

                     (264)

                     The driver card shall be able to store the following data for these faults:

                                 —

                                 Fault code,

                                 —

                                 Date and time of beginning of the fault (or of card insertion if the fault was on-going at that time),

                                 —

                                 Date and time of end of the fault (or of card withdrawal if the fault was on-going at that time),

                                 —

                                 VRN and registering Member State of vehicle in which the fault happened.

                     (265)

                     The driver card shall be able to store data for the twelve most recent faults of each type (i.e. 24 faults).

               4.5.3.1.9   Driver activity data

                     (266)

                     The driver card shall be able to store, for each calendar day where the card has been used or for which the driver has entered activities manually, the following data:

                                 —

                                 the date,

                                 —

                                 a daily presence counter (increased by one for each of these calendar days),

                                 —

                                 the total distance travelled by the driver during this day,

                                 —

                                 a driver status at 00:00,

                                 —

                                 whenever the driver has changed of activity, and/or has changed of driving status, and/or has inserted or withdrawn his card:

                                             —

                                             the driving status (CREW, SINGLE),

                                             —

                                             the slot (DRIVER, CO-DRIVER),

                                             —

                                             the card status (INSERTED, NOT INSERTED),

                                             —

                                             the activity (DRIVING, AVAILABILITY, WORK, BREAK/REST),

                                             —

                                             the time of the change.

                     (267)

                     The driver card memory shall be able to hold driver activity data for at least 28 days (the average activity of a driver is defined as 93 activity changes per day).

                     (268)

                     The data listed under requirements 261, 264 and 266 shall be stored in a way allowing the retrieval of activities in the order of their occurrence, even in case of a time overlap situation.

               4.5.3.1.10   Vehicles used data

                     (269)

                     The driver card shall be able to store, for each calendar day where the card has been used, and for each period of use of a given vehicle that day (a period of use includes all consecutive insertion / withdrawal cycle of the card in the vehicle, as seen from the card point of view), the following data:

                                 —

                                 date and time of first use of the vehicle (i.e. first card insertion for this period of use of the vehicle, or 00h00 if the period of use is on-going at that time),

                                 —

                                 vehicle odometer value at that time,

                                 —

                                 date and time of last use of the vehicle, (i.e. last card withdrawal for this period of use of the vehicle, or 23h59 if the period of use is on-going at that time),

                                 —

                                 vehicle odometer value at that time,

                                 —

                                 VRN and registering Member State of the vehicle.

                     (270)

                     The driver card shall be able to store at least 84 such records.

               4.5.3.1.11   Places where daily work periods start and/or end

                     (271)

                     The driver card shall be able to store the following data related to places where daily work periods begin and/or end, entered by the driver:

                                 —

                                 the date and time of the entry (or the date/time related to the entry if the entry is made during the manual entry procedure),

                                 —

                                 the type of entry (begin or end, condition of entry),

                                 —

                                 the country and region entered,

                                 —

                                 the vehicle odometer value.

                     (272)

                     The driver card memory shall be able to hold at least 42 pairs of such records.

               4.5.3.1.12   Card session data

                     (273)

                     The driver card shall be able to store data related to the vehicle which opened its current session:

                                 —

                                 date and time the session was opened (i.e. card insertion) with a resolution of one second,

                                 —

                                 VRN and registering Member State.

               4.5.3.1.13   Control activity data

                     (274)

                     The driver card shall be able to store the following data related to control activities:

                                 —

                                 date and time of the control,

                                 —

                                 control card number and card issuing Member State,

                                 —

                                 type of the control (displaying and/or printing and/or VU downloading and/or card downloading (see note)),

                                 —

                                 Period downloaded, in case of downloading,

                                 —

                                 VRN and registering Member State of the vehicle in which the control happened.

                           Note: card downloading will only be recorded if performed through a recording equipment.

                     (275)

                     The driver card shall be able to hold one such record.

               4.5.3.1.14   Specific conditions data

                     (276)

                     The driver card shall be able to store the following data related to specific conditions entered while the card was inserted (whatever the slot):

                                 —

                                 Date and time of the entry,

                                 —

                                 Type of specific condition.

                     (277)

                     The driver card shall be able to store at least 56 such records.

               4.5.3.2   Tachograph generation 2 application (not accessible to first generation vehicle unit)

         4.5.3.2.1   Application identification

                     (278)

                     The driver card shall be able to store the following application identification data:

                                 —

                                 tachograph application identification,

                                 —

                                 type of tachograph card identification.

               4.5.3.2.2   Keys and certificates

                     (279)

                     The driver card shall be able to store a number of cryptographic keys and certificates, as specified in Appendix 11 part B.

               4.5.3.2.3   Card identification

                     (280)

                     The driver card shall be able to store the following card identification data:

                                 —

                                 card number,

                                 —

                                 issuing Member State, issuing authority name, issue date,

                                 —

                                 card beginning of validity date, card expiry date.

               4.5.3.2.4   Card holder identification

                     (281)

                     The driver card shall be able to store the following card holder identification data:

                                 —

                                 surname of the holder,

                                 —

                                 first name(s) of the holder,

                                 —

                                 date of birth,

                                 —

                                 preferred language.

               4.5.3.2.5   Card download

                     (282)

                     The driver card shall be able to store the following data related to card download:

                                 —

                                 date and time of last card download (for other purposes than control).

                     (283)

                     The driver card shall be able to hold one such record.

               4.5.3.2.6   Driving licence information

                     (284)

                     The driver card shall be able to store the following driving licence data:

                                 —

                                 issuing Member State, issuing authority name,

                                 —

                                 driving licence number (at the date of the issue of the card).

               4.5.3.2.7   Events data
         For the purpose of this subparagraph, time shall be stored with a resolution of 1 second.

                     (285)

                     The driver card shall be able to store data related to the following events detected by the recording equipment while the card was inserted:

                                 —

                                 Time overlap (where this card is the cause of the event),

                                 —

                                 Card insertion while driving (where this card is the subject of the event),

                                 —

                                 Last card session not correctly closed (where this card is the subject of the event),

                                 —

                                 Power supply interruption,

                                 —

                                 Communication error with the remote communication facility,

                                 —

                                 Absence of position information from GNSS receiver event,

                                 —

                                 Communication error with the external GNSS facility

                                 —

                                 Motion data error,

                                 —

                                 Vehicle motion conflict,

                                 —

                                 Security breach attempts,

                                 —

                                 Time conflict.

                     (286)

                     The driver card shall be able to store the following data for these events:

                                 —

                                 Event code,

                                 —

                                 Date and time of beginning of the event (or of card insertion if the event was on-going at that time),

                                 —

                                 Date and time of end of the event (or of card withdrawal if the event was on-going at that time),

                                 —

                                 VRN and registering Member State of vehicle in which the event happened.

                           Note: For the ‘Time overlap’ event:

                                 —

                                 Date and time of beginning of the event shall correspond to the date and time of the card withdrawal from the previous vehicle,

                                 —

                                 Date and time of end of the event shall correspond to the date and time of card insertion in current vehicle,

                                 —

                                 Vehicle data shall correspond to the current vehicle raising the event.

                           Note: For the ‘Last card session not correctly closed’ event:

                                 —

                                 date and time of beginning of event shall correspond to the card insertion date and time of the session not correctly closed,

                                 —

                                 date and time of end of event shall correspond to the card insertion date and time of the session during which the event was detected (current session),

                                 —

                                 Vehicle data shall correspond to the vehicle in which the session was not correctly closed.

                     (287)

                     The driver card shall be able to store data for the six most recent events of each type (i.e. 66 events).

               4.5.3.2.8   Faults data
         For the purpose of this subparagraph, time shall be recorded with a resolution of 1 second.

                     (288)

                     The driver card shall be able to store data related to the following faults detected by the recording equipment while the card was inserted:

                                 —

                                 Card fault (where this card is the subject of the event),

                                 —

                                 Recording equipment fault.

                     (289)

                     The driver card shall be able to store the following data for these faults:

                                 —

                                 Fault code,

                                 —

                                 Date and time of beginning of the fault (or of card insertion if the fault was on-going at that time),

                                 —

                                 Date and time of end of the fault (or of card withdrawal if the fault was on-going at that time),

                                 —

                                 VRN and registering Member State of vehicle in which the fault happened.

                     (290)

                     The driver card shall be able to store data for the twelve most recent faults of each type (i.e. 24 faults).

               4.5.3.2.9   Driver activity data

                     (291)

                     The driver card shall be able to store, for each calendar day where the card has been used or for which the driver has entered activities manually, the following data:

                                 —

                                 the date,

                                 —

                                 a daily presence counter (increased by one for each of these calendar days),

                                 —

                                 the total distance travelled by the driver during this day,

                                 —

                                 a driver status at 00:00,

                                 —

                                 whenever the driver has changed of activity, and/or has changed of driving status, and/or has inserted or withdrawn his card:

                                             —

                                             the driving status (CREW, SINGLE)

                                             —

                                             the slot (DRIVER, CO-DRIVER),

                                             —

                                             the card status (INSERTED, NOT INSERTED),

                                             —

                                             the activity (DRIVING, AVAILABILITY, WORK, BREAK/REST).

                                             —

                                             the time of the change,

                     (292)

                     The driver card memory shall be able to hold driver activity data for at least 28 days (the average activity of a driver is defined as 93 activity changes per day).

                     (293)

                     The data listed under requirements 286, 289 and 291 shall be stored in a way allowing the retrieval of activities in the order of their occurrence, even in case of a time overlap situation.

               4.5.3.2.10   Vehicles used data

                     (294)

                     The driver card shall be able to store, for each calendar day where the card has been used, and for each period of use of a given vehicle that day (a period of use includes all consecutive insertion / withdrawal cycle of the card in the vehicle, as seen from the card point of view), the following data:

                                 —

                                 date and time of first use of the vehicle (i.e. first card insertion for this period of use of the vehicle, or 00h00 if the period of use is on-going at that time),

                                 —

                                 vehicle odometer value at that first use time,

                                 —

                                 date and time of last use of the vehicle, (i.e. last card withdrawal for this period of use of the vehicle, or 23h59 if the period of use is on-going at that time),

                                 —

                                 vehicle odometer value at that last use time,

                                 —

                                 VRN and registering Member State of the vehicle,

                                 —

                                 VIN of the vehicle.

                     (295)

                     The driver card shall be able to store at least 84 such records.

               4.5.3.2.11   Places and positions where daily work periods start and/or end

                     (296)

                     The driver card shall be able to store the following data related to places where daily work periods begin and/or end, entered by the driver:

                                 —

                                 the date and time of the entry (or the date/time related to the entry if the entry is made during the manual entry procedure),

                                 —

                                 the type of entry (begin or end, condition of entry),

                                 —

                                 the country and region entered,

                                 —

                                 the vehicle odometer value,

                                 —

                                 the vehicle position,

                                 —

                                 the GNSS accuracy, date and time when the position was determined.

                     (297)

                     The driver card memory shall be able to hold at least 84 pairs of such records.

               4.5.3.2.12   Card session data

                     (298)

                     The driver card shall be able to store data related to the vehicle which opened its current session:

                                 —

                                 date and time the session was opened (i.e. card insertion) with a resolution of one second,

                                 —

                                 VRN and registering Member State.

               4.5.3.2.13   Control activity data

                     (299)

                     The driver card shall be able to store the following data related to control activities:

                                 —

                                 date and time of the control,

                                 —

                                 control card number and card issuing Member State,

                                 —

                                 type of the control (displaying and/or printing and/or VU downloading and/or card downloading (see note)),

                                 —

                                 Period downloaded, in case of downloading,

                                 —

                                 VRN and registering Member State of the vehicle in which the control happened.

                           Note: security requirements imply that card downloading will only be recorded if performed through a recording equipment.

                     (300)

                     The driver card shall be able to hold one such record.

               4.5.3.2.14   Specific conditions data

                     (301)

                     The driver card shall be able to store the following data related to specific conditions entered while the card was inserted (whatever the slot):

                                 —

                                 Date and time of the entry,

                                 —

                                 Type of specific condition.

                     (302)

                     The driver card shall be able to store at least 56 such records.

               4.5.3.2.15   Vehicle units used data

                     (303)

                     The driver card shall be able to store the following data related to the different vehicle units in which the card was used:

                                 —

                                 the date and time of the beginning of the period of use of the vehicle unit (i.e. first card insertion in the vehicle unit for the period),

                                 —

                                 the manufacturer of the vehicle unit,

                                 —

                                 the vehicle unit type,

                                 —

                                 the vehicle unit software version number.

                     (304)

                     The driver card shall be able to store at least 84 such records.

               4.5.3.2.16   Three hours' continuous driving places data

                     (305)

                     The driver card shall be able to store the following data related to the position of the vehicle where the continuous driving time of the driver reaches a multiple of three hours:

                                 —

                                 the date and time when the continuous driving time of the card holder reaches a multiple of three hours,

                                 —

                                 the position of the vehicle.

                                 —

                                 the GNSS accuracy, date and time when the position was determined.

                     (306)

                     The driver card shall be able to store at least 252 such records.

               4.5.4   Workshop card

         4.5.4.1   Tachograph application (accessible to first and second generation vehicle units)

         4.5.4.1.1   Application identification

                     (307)

                     The workshop card shall be able to store the following application identification data:

                                 —

                                 tachograph application identification,

                                 —

                                 type of tachograph card identification.

               4.5.4.1.2   Keys and certificates

                     (308)

                     The workshop card shall be able to store a number of cryptographic keys and certificates, as specified in Appendix 11 part A.

                     (309)

                     The workshop card shall be able to store a Personal Identification Number (PIN code).

               4.5.4.1.3   Card identification

                     (310)

                     The workshop card shall be able to store the following card identification data:

                                 —

                                 card number,

                                 —

                                 issuing Member State, issuing authority name, issue date,

                                 —

                                 card beginning of validity date, card expiry date.

               4.5.4.1.4   Card holder identification

                     (311)

                     The workshop card shall be able to store the following card holder identification data:

                                 —

                                 workshop name,

                                 —

                                 workshop address,

                                 —

                                 surname of the holder,

                                 —

                                 first name(s) of the holder,

                                 —

                                 preferred language.

               4.5.4.1.5   Card download

                     (312)

                     The workshop card shall be able to store a card download data record in the same manner as a driver card.

               4.5.4.1.6   Calibration and time adjustment data

                     (313)

                     The workshop card shall be able to hold records of calibrations and/or time adjustments performed while the card is inserted in a recording equipment.

                     (314)

                     Each calibration record shall be able to hold the following data:

                                 —

                                 Purpose of calibration (activation, first installation, installation, periodic inspection,),

                                 —

                                 Vehicle identification,

                                 —

                                 Parameters updated or confirmed (w, k, l, tyre size, speed limiting device setting, odometer (new and old values), date and time (new and old values)),

                                 —

                                 Recording equipment identification (VU part number, VU serial number, motion sensor serial number).

                     (315)

                     The workshop card shall be able to store at least 88 such records.

                     (316)

                     The workshop card shall hold a counter indicating the total number of calibrations performed with the card.

                     (317)

                     The workshop card shall hold a counter indicating the number of calibrations performed since its last download.

               4.5.4.1.7   Events and faults data

                     (318)

                     The workshop card shall be able to store events and faults data records in the same manner as a driver card.

                     (319)

                     The workshop card shall be able to store data for the three most recent events of each type (i.e. 18 events) and the six most recent faults of each type (i.e. 12 faults).

               4.5.4.1.8   Driver activity data

                     (320)

                     The workshop card shall be able to store driver activity data in the same manner as a driver card.

                     (321)

                     The workshop card shall be able to hold driver activity data for at least 1 day of average driver activity.

               4.5.4.1.9   Vehicles used data

                     (322)

                     The workshop card shall be able to store vehicles used data records in the same manner as a driver card.

                     (323)

                     The workshop card shall be able to store at least 4 such records.

               4.5.4.1.10   Daily work periods start and/or end data

                     (324)

                     The workshop card shall be able to store daily works period start and/or end data records in the same manner as a driver card.

                     (325)

                     The workshop card shall be able to hold at least 3 pairs of such records.

               4.5.4.1.11   Card session data

                     (326)

                     The workshop card shall be able to store a card session data record in the same manner as a driver card.

               4.5.4.1.12   Control activity data

                     (327)

                     The workshop card shall be able to store a control activity data record in the same manner as a driver card.

               4.5.4.1.13   Specific conditions data

                     (328)

                     The workshop card shall be able to store data relevant to specific conditions in the same manner as the driver card.

                     (329)

                     The workshop card shall be able to store at least 2 such records.

               4.5.4.2   Tachograph generation 2 application (not accessible to first generation vehicle unit)

         4.5.4.2.1   Application identification

                     (330)

                     The workshop card shall be able to store the following application identification data:

                                 —

                                 tachograph application identification,

                                 —

                                 type of tachograph card identification.

               4.5.4.2.2   Keys and certificates

                     (331)

                     The workshop card shall be able to store a number of cryptographic keys and certificates, as specified in Appendix 11 part B.

                     (332)

                     The workshop card shall be able to store a Personal Identification Number (PIN code).

               4.5.4.2.3   Card identification

                     (333)

                     The workshop card shall be able to store the following card identification data:

                                 —

                                 card number,

                                 —

                                 issuing Member State, issuing authority name, issue date,

                                 —

                                 card beginning of validity date, card expiry date.

               4.5.4.2.4   Card holder identification

                     (334)

                     The workshop card shall be able to store the following card holder identification data:

                                 —

                                 workshop name,

                                 —

                                 workshop address,

                                 —

                                 surname of the holder,

                                 —

                                 first name(s) of the holder,

                                 —

                                 preferred language.

               4.5.4.2.5   Card download

                     (335)

                     The workshop card shall be able to store a card download data record in the same manner as a driver card.

               4.5.4.2.6   Calibration and time adjustment data

                     (336)

                     The workshop card shall be able to hold records of calibrations and/or time adjustments performed while the card is inserted in a recording equipment.

                     (337)

                     Each calibration record shall be able to hold the following data:

                                 —

                                 purpose of calibration (activation, first installation, installation, periodic inspection,),

                                 —

                                 vehicle identification,

                                 —

                                 parameters updated or confirmed (w, k, l, tyre size, speed limiting device setting, odometer (new and old values), date and time (new and old values),

                                 —

                                 recording equipment identification (VU part number, VU serial number, motion sensor serial number, remote communication facility serial number and external GNSS facility serial number, if applicable),

                                 —

                                 seal type and identifier of all seals in place,

                                 —

                                 ability of the VU to use first generation tachograph cards (enabled or not).

                     (338)

                     The workshop card shall be able to store at least 88 such records.

                     (339)

                     The workshop card shall hold a counter indicating the total number of calibrations performed with the card.

                     (340)

                     The workshop card shall hold a counter indicating the number of calibrations performed since its last download.

               4.5.4.2.7   Events and faults data

                     (341)

                     The workshop card shall be able to store events and faults data records in the same manner as a driver card.

                     (342)

                     The workshop card shall be able to store data for the three most recent events of each type (i.e. 33 events) and the six most recent faults of each type (i.e. 12 faults).

               4.5.4.2.8   Driver activity data

                     (343)

                     The workshop card shall be able to store driver activity data in the same manner as a driver card.

                     (344)

                     The workshop card shall be able to hold driver activity data for at least 1 day of average driver activity.

               4.5.4.2.9   Vehicles used data

                     (345)

                     The workshop card shall be able to store vehicles used data records in the same manner as a driver card.

                     (346)

                     The workshop card shall be able to store at least 4 such records.

               4.5.4.2.10   Daily work periods start and/or end data

                     (347)

                     The workshop card shall be able to store daily works period start and/or end data records in the same manner as a driver card.

                     (348)

                     The workshop card shall be able to hold at least 3 pairs of such records.

               4.5.4.2.11   Card session data

                     (349)

                     The workshop card shall be able to store a card session data record in the same manner as a driver card.

               4.5.4.2.12   Control activity data

                     (350)

                     The workshop card shall be able to store a control activity data record in the same manner as a driver card.

               4.5.4.2.13   Vehicle units used data

                     (351)

                     The workshop card shall be able to store the following data related to the different vehicle units in which the card was used:

                                 —

                                 the date and time of the beginning of the period of use of the vehicle unit (i.e. first card insertion in the vehicle unit for the period),

                                 —

                                 the manufacturer of the vehicle unit,

                                 —

                                 the vehicle unit type,

                                 —

                                 the vehicle unit software version number.

                     (352)

                     The workshop card shall be able to store at least 4 such records.

               4.5.4.2.14   Three hours' continuous driving places data

                     (353)

                     The workshop card shall be able to store the following data related to the position of the vehicle where the continuous driving time of the driver reaches a multiple of three hours:

                                 —

                                 the date and time when the continuous driving time of the card holder reaches a multiple of three hours,

                                 —

                                 the position of the vehicle,

                                 —

                                 the GNSS accuracy, date and time when the position was determined.

                     (354)

                     The workshop card shall be able to store at least 18 such records.

               4.5.4.2.15   Specific conditions data

                     (355)

                     The workshop card shall be able to store data relevant to specific conditions in the same manner as the driver card.

                     (356)

                     The workshop card shall be able to store at least 2 such records.

               4.5.5   Control card

         4.5.5.1   Tachograph application (accessible to first and second generation vehicle units)

         4.5.5.1.1   Application identification

                     (357)

                     The control card shall be able to store the following application identification data:

                                 —

                                 tachograph application identification,

                                 —

                                 type of tachograph card identification.

               4.5.5.1.2   Keys and certificates

                     (358)

                     The control card shall be able to store a number of cryptographic keys and certificates, as specified in Appendix 11 part A.

               4.5.5.1.3   Card identification

                     (359)

                     The control card shall be able to store the following card identification data:

                                 —

                                 card number,

                                 —

                                 issuing Member State, issuing authority name, issue date,

                                 —

                                 card beginning of validity date, card expiry date (if any).

               4.5.5.1.4   Card holder identification

                     (360)

                     The control card shall be able to store the following card holder identification data:

                                 —

                                 control body name,

                                 —

                                 control body address,

                                 —

                                 surname of the holder,

                                 —

                                 first name(s) of the holder,

                                 —

                                 preferred language.

               4.5.5.1.5   Control activity data

                     (361)

                     The control card shall be able to store the following control activity data:

                                 —

                                 date and time of the control,

                                 —

                                 type of the control (displaying and/or printing and/or VU downloading and/or card downloading and/or roadside calibration checking),

                                 —

                                 period downloaded (if any),

                                 —

                                 VRN and Member State registering authority of the controlled vehicle,

                                 —

                                 card number and card issuing Member State of the driver card controlled.

                     (362)

                     The control card shall be able to hold at least 230 such records.

               4.5.5.2   Tachograph G2 application (not accessible to first generation vehicle unit)

         4.5.5.2.1   Application identification

                     (363)

                     The control card shall be able to store the following application identification data:

                                 —

                                 tachograph application identification,

                                 —

                                 type of tachograph card identification.

               4.5.5.2.2   Keys and certificates

                     (364)

                     The control card shall be able to store a number of cryptographic keys and certificates, as specified in Appendix 11 part B.

               4.5.5.2.3   Card identification

                     (365)

                     The control card shall be able to store the following card identification data:

                                 —

                                 card number,

                                 —

                                 issuing Member State, issuing authority name, issue date,

                                 —

                                 card beginning of validity date, card expiry date (if any).

               4.5.5.2.4   Card holder identification

                     (366)

                     The control card shall be able to store the following card holder identification data:

                                 —

                                 control body name,

                                 —

                                 control body address,

                                 —

                                 surname of the holder,

                                 —

                                 first name(s) of the holder,

                                 —

                                 preferred language.

               4.5.5.2.5   Control activity data

                     (367)

                     The control card shall be able to store the following control activity data:

                                 —

                                 date and time of the control,

                                 —

                                 type of the control (displaying and/or printing and/or VU downloading and/or card downloading and/or roadside calibration checking)

                                 —

                                 period downloaded (if any),

                                 —

                                 VRN and Member State registering authority of the controlled vehicle,

                                 —

                                 card number and card issuing Member State of the driver card controlled.

                     (368)

                     The control card shall be able to hold at least 230 such records.

               4.5.6   Company card

         4.5.6.1   Tachograph application (accessible to first and second generation vehicle units)

         4.5.6.1.1   Application identification

                     (369)

                     The company card shall be able to store the following application identification data:

                                 —

                                 tachograph application identification,

                                 —

                                 type of tachograph card identification.

               4.5.6.1.2   Keys and Certificates

                     (370)

                     The company card shall be able to store a number of cryptographic keys and certificates, as specified in Appendix 11 part A.

               4.5.6.1.3   Card identification

                     (371)

                     The company card shall be able to store the following card identification data:

                                 —

                                 card number,

                                 —

                                 issuing Member State, issuing authority name, issue date,

                                 —

                                 card beginning of validity date, card expiry date (if any).

               4.5.6.1.4   Card holder identification

                     (372)

                     The company card shall be able to store the following card holder identification data:

                                 —

                                 company name,

                                 —

                                 company address.

               4.5.6.1.5   Company activity data

                     (373)

                     The company card shall be able to store the following company activity data:

                                 —

                                 date and time of the activity,

                                 —

                                 type of the activity (VU locking in and/or out, and/or VU downloading and/or card downloading)

                                 —

                                 period downloaded (if any),

                                 —

                                 VRN and Member State registering authority of vehicle,

                                 —

                                 card number and card issuing Member State (in case of card downloading).

                     (374)

                     The company card shall be able to hold at least 230 such records.

               4.5.6.2   Tachograph G2 application (not accessible to first generation vehicle unit)

         4.5.6.2.1   Application identification

                     (375)

                     The company card shall be able to store the following application identification data:

                                 —

                                 tachograph application identification,

                                 —

                                 type of tachograph card identification.

               4.5.6.2.2   Keys and certificates

                     (376)

                     The company card shall be able to store a number of cryptographic keys and certificates, as specified in Appendix 11 part B.

               4.5.6.2.3   Card identification

                     (377)

                     The company card shall be able to store the following card identification data:

                                 —

                                 card number,

                                 —

                                 issuing Member State, issuing authority name, issue date,

                                 —

                                 card beginning of validity date, card expiry date (if any).

               4.5.6.2.4   Card holder identification

                     (378)

                     The company card shall be able to store the following card holder identification data:

                                 —

                                 company name,

                                 —

                                 company address.

               4.5.6.2.5   Company activity data

                     (379)

                     The company card shall be able to store the following company activity data:

                                 —

                                 date and time of the activity,

                                 —

                                 type of the activity (VU locking in and/or out, and/or VU downloading and/or card downloading)

                                 —

                                 period downloaded (if any),

                                 —

                                 VRN and Member State registering authority of vehicle,

                                 —

                                 card number and card issuing Member State (in case of card downloading).

                     (380)

                     The company card shall be able to hold at least 230 such records.

               5.   INSTALLATION OF RECORDING EQUIPMENT
         5.1   Installation

                     (381)

                     New recording equipment shall be delivered non-activated to fitters or vehicle manufacturers, with all calibration parameters, as listed in Chapter 3.21, set to appropriate and valid default values. Where no particular value is appropriate, literal parameters shall be set to strings of ‘?’ and numeric parameters shall be set to ‘0’. Delivery of security relevant parts of the recording equipment can be restricted if required during security certification.

                     (382)

                     Before its activation, the recording equipment shall give access to the calibration function even if not in calibration mode.

                     (383)

                     Before its activation, the recording equipment shall neither record nor store data referred by points 3.12.3, 3.12.9 and 3.12.12 to 3.12.15 inclusive.

                     (384)

                     During installation, vehicle manufacturers shall pre-set all known parameters.

                     (385)

                     Vehicle manufacturers or fitters shall activate the installed recording equipment at the latest before the vehicle is used in scope of Regulation (EC) No 561/2006.

                     (386)

                     The activation of the recording equipment shall be triggered automatically by the first insertion of a valid workshop card in either of its card interface devices.

                     (387)

                     Specific pairing operations required between the motion sensor and the vehicle unit, if any, shall take place automatically before or during activation.

                     (388)

                     In a similar way, specific coupling operations between the external GNSS facility and the vehicle unit, if any, shall take place automatically before or during activation.

                     (389)

                     After its activation, the recording equipment shall fully enforce functions and data access rights.

                     (390)

                     After its activation, the recording equipment shall communicate to the remote communication facility the secured data necessary for the purpose of targeted roadside checks.

                     (391)

                     The recording and storing functions of the recording equipment shall be fully operational after its activation.

                     (392)

                     Installation shall be followed by a calibration. The first calibration may not necessarily include entry of the vehicle registration number (VRN), when it is not known by the approved workshop having to undertake this calibration. In these circumstances, it shall be possible, for the vehicle owner, and at this time only, to enter the VRN using his Company Card prior to using the vehicle in scope of Regulation (EC) No 561/2006 (e.g by using commands through an appropriate menu structure of the vehicle unit's man-machine interface.) (14). Any update or confirmation of this entry shall only be possible using a Workshop Card.

                     (393)

                     The installation of an external GNSS facility requires the coupling with the vehicle unit and the subsequent verification of the GNSS position information.

                     (394)

                     The recording equipment must be positioned in the vehicle in such a way as to allow the driver to access the necessary functions from his seat.

               5.2   Installation plaque

                     (395)

                     After the recording equipment has been checked on installation, an installation plaque, engraved or printed in a permanent way, which is clearly visible and easily accessible shall be affixed onto the recording equipment. In cases where this is not possible, the plaque shall be affixed to the vehicle's ‘B’ pillar so that it is clearly visible. For vehicles that do not have a ‘B’ pillar, the installation plaque should be affixed to the doorframe on the driver's side of the vehicle and be clearly visible in all cases.
                     After every inspection by an approved fitter or workshop, a new plaque shall be affixed in place of the previous one.

                     (396)

                     The plaque shall bear at least the following details:

                                 —

                                 name, address or trade name of the approved fitter or workshop,

                                 —

                                 characteristic coefficient of the vehicle, in the form ‘w = … imp/km’,

                                 —

                                 constant of the recording equipment, in the form ‘k = … imp/km’,

                                 —

                                 effective circumference of the wheel tyres in the form ‘l = … mm’,

                                 —

                                 tyre size,

                                 —

                                 the date on which the characteristic coefficient of the vehicle and the effective circumference of the wheel tyres were measured,

                                 —

                                 the vehicle identification number,

                                 —

                                 the presence (or not) of an external GNSS facility,

                                 —

                                 the serial number of the external GNSS facility,

                                 —

                                 the serial number of the remote communication device,

                                 —

                                 the serial number of all the seals in place,

                                 —

                                 the part of the vehicle where the adaptor, if any, is installed,

                                 —

                                 the part of the vehicle where the motion sensor is installed, if not connected to the gear-box or an adaptor is not being used,

                                 —

                                 a description of the colour of the cable between the adaptor and that part of the vehicle providing its incoming impulses,

                                 —

                                 the serial number of the embedded motion sensor of the adaptor.

                     (397)

                     For M1 and N1 vehicles only, and which are fitted with an adaptor in conformity with Commission Regulation (EC) No 68/2009 (15) as last amended and where it is not possible to include all the information necessary, as described in Requirement 396, a second, additional, plaque may be used. In such cases, this additional plaque shall contain at least the last four indents described in Requirement 396.
                     This second, additional plaque, if used, shall be affixed next to or beside the first primary plaque described in Requirement 396, and shall have the same protection level. Furthermore the secondary plaque shall also bear the name, address or trade name of the approved fitter or workshop that carried out the installation, and the date of installation.

               5.3   Sealing

                     (398)

                     The following parts shall be sealed:

                                 —

                                 Any connection which, if disconnected, would cause undetectable alterations to be made or undetectable data loss (this may e.g. apply for the motion sensor fitting on the gearbox, the adaptor for M1/N1 vehicles, the external GNSS connection or the vehicle unit);

                                 —

                                 The installation plaque, unless it is attached in such a way that it cannot be removed without the markings thereon being destroyed.

                     (399)

                     The seals mentioned above may be removed:

                                 —

                                 In case of emergency,

                                 —

                                 To install, to adjust or to repair a speed limitation device or any other device contributing to road safety, provided that the recording equipment continues to function reliably and correctly and is resealed by an approved fitter or workshop (in accordance with Chapter 6) immediately after fitting the speed limitation device or any other device contributing to road safety or within seven days in other cases.

                     (400)

                     On each occasion that these seals are broken a written statement giving the reasons for such action shall be prepared and made available to the competent authority.

                     (401)

                     Seals shall hold an identification number, allocated by its manufacturer. This number shall be unique and distinct from any other seal number allocated by any other seals manufacturer.
                     This unique identification number is defined as: MMNNNNNN by non-removable marking, with MM as unique manufacturer identification (database registration to be managed by EC) and NNNNNN seal alpha-numeric number, unique in the manufacturer domain.

                     (402)

                     The seals shall have a free space where approved fitters, workshops or vehicle manufacturers can add a special mark according the Article 22(3) of Regulation (EU) No 165/2014.
                     This mark shall not cover the seal identification number.

                     (403)

                     Seals manufacturers shall be registered in a dedicated database and shall make their identification seals numbers public through a procedure to be established by the European Commission.

                     (404)

                     Approved workshops and vehicle manufacturers shall, in the frame of Regulation (EU) No 165/2014, only use seals from those of the seals manufacturers listed in the data base mentioned above.

                     (405)

                     Seal manufacturers and their distributors shall maintain full traceability records of the seals sold to be used in the frame of Regulation (EU) No 165/2014 and shall be prepared to produce them to competent national authorities whenever need be.

                     (406)

                     Seals unique identification numbers shall be visible on the installation plaque.

               6.   CHECKS, INSPECTIONS AND REPAIRS
         Requirements on the circumstances in which seals may be removed, as referred to in Article 22(5) of Regulation (EU) No 165/2014, are defined in Chapter 5.3 of this annex.
         6.1   Approval of fitters, workshops and vehicle manufacturers

         The Member States approve, regularly control and certify the bodies to carry out:

                     —

                     installations,

                     —

                     checks,

                     —

                     inspections,

                     —

                     repairs.

               Workshop cards shall be issued only to fitters and/or workshops approved for the activation and/or the calibration of recording equipment in conformity with this annex and, unless duly justified:

                     —

                     who are not eligible for a company card;

                     —

                     and whose other professional activities do not present a potential compromise of the overall security of the system as required in Appendix 10.

               6.2   Check of new or repaired instruments

                     (407)

                     Every individual device, whether new or repaired, shall be checked in respect of its proper operation and the accuracy of its reading and recordings, within the limits laid down in Chapter 3.2.1, 3.2.2, 3.2.3 and 3.3 by means of sealing in accordance with Chapter 5.3 and calibration.

               6.3   Installation inspection

                     (408)

                     When being fitted to a vehicle, the whole installation (including the recording equipment) shall comply with the provisions relating to maximum tolerances laid down in Chapter 3.2.1, 3.2.2, 3.2.3 and 3.3.

               6.4   Periodic inspections

                     (409)

                     Periodic inspections of the equipment fitted to the vehicles shall take place after any repair of the equipment, or after any alteration of the characteristic coefficient of the vehicle or of the effective circumference of the tyres, or after equipment UTC time is wrong by more than 20 minutes, or when the VRN has changed, and at least once within two years (24 months) of the last inspection.

                     (410)

                     These inspections shall include the following checks:

                                 —

                                 that the recording equipment is working properly, including the data storage in tachograph cards function and the communication with remote communication readers,

                                 —

                                 that compliance with the provisions of chapter 3.2.1 and 3.2.2 on the maximum tolerances on installation is ensured,

                                 —

                                 that compliance with the provisions of chapter 3.2.3 and 3.3 is ensured,

                                 —

                                 that the recording equipment carries the type approval mark,

                                 —

                                 that the installation plaque, as defined by Requirement 396, and the descriptive plaque, as defined by Requirement 225, are affixed,

                                 —

                                 the tyre size and the actual circumference of the tyres,

                                 —

                                 that there are no manipulation devices attached to the equipment,

                                 —

                                 that seals are correctly placed, in good state, that their identification numbers are valid (referenced seal manufacturer in the EC database) and that their identification numbers correspond to the installation plaque markings (see requirement 401).

                     (411)

                     If one of the events listed in Chapter 3.9 (Detection of Events and/or Faults) is found to have occurred since the last inspection and is considered by tachograph manufacturers and/or national authorities as potentially putting the security of the equipment at risk, the workshop shall:

                                 a.

                                 make a comparison between the motion sensor identification data of the motion sensor plugged into the gearbox with that of the paired motion sensor registered in the vehicle unit;

                                 b.

                                 check if the information recorded on the installation plaque matches with the information contained within the vehicle unit record;

                                 c.

                                 check if the motion sensor serial number and approval number, if printed on the body of the motion sensor, matches the information stored in the recording equipment data memory;

                                 d.

                                 compare identification data marked on the descriptive plaque of the external GNSS facility, if any, to the ones stored in the vehicle unit data memory;

                     (412)

                     Workshops shall keep traces in their inspection reports of any findings concerning broken seals or manipulations devices. These reports shall be kept by workshops for at least 2 years and made available to the Competent Authority whenever requested to do so.

                     (413)

                     These inspections shall include a calibration and a preventive replacement of the seals whose fitting is under the responsibility of workshops.

               6.5   Measurement of errors

                     (414)

                     The measurement of errors on installation and during use shall be carried out under the following conditions, which are to be regarded as constituting standard test conditions:

                                 —

                                 vehicle unladen, in normal running order,

                                 —

                                 tyre pressures in accordance with the manufacturer's instructions,

                                 —

                                 tyre wear, within the limits allowed by national law,

                                 —

                                 vehicle movement:

                                 —

                                 the vehicle shall advance under its own engine power in a straight line on level ground and at a speed of 50 ± 5 km/h. The measuring distance shall be at least 1 000 m.

                                 —

                                 provided that it is of comparable accuracy, alternative methods, such as a suitable test bench, may also be used for the test.

               6.6   Repairs

                     (415)

                     Workshops shall be able to download data from the recording equipment to give the data back to the appropriate transport company.

                     (416)

                     Approved workshops shall issue to transport companies a certificate of data un-downloadability where the malfunction of the recording equipment prevents previously recorded data to be downloaded, even after repair by this workshop. The workshops will keep a copy of each issued certificate for at least two years.

               7.   CARD ISSUING
         The card issuing processes set-up by the Member States shall conform to the following:

                     (417)

                     The card number of the first issue of a tachograph card to an applicant shall have a consecutive index (if applicable) and a replacement index and a renewal index set to “0”.

                     (418)

                     The card numbers of all non-personal tachograph cards issued to a single control body or a single workshop or a single transport company shall have the same first 13 digits, and shall all have a different consecutive index.

                     (419)

                     A tachograph card issued in replacement of an existing tachograph card shall have the same card number than the replaced one except the replacement index which shall be raised by “1” (in the order 0, …, 9, A, …, Z).

                     (420)

                     A tachograph card issued in replacement of an existing tachograph card shall have the same card expiry date as the replaced one.

                     (421)

                     A tachograph card issued in renewal of an existing tachograph card shall have the same card number as the renewed one except the replacement index which shall be reset to “0” and the renewal index which shall be raised by “1” (in the order 0, …, 9, A, …, Z).

                     (422)

                     The exchange of an existing tachograph card, in order to modify administrative data, shall follow the rules of the renewal if within the same Member State, or the rules of a first issue if performed by another Member State.

                     (423)

                     The ‘card holder surname’ for non-personal workshop or control cards shall be filled with workshop or control body name or with the fitter or control officer's name would Member States so decide.

                     (424)

                     Member States shall exchange data electronically in order to ensure the uniqueness of driver cards that they issue in accordance with Article 31 of Regulation (EU) No 165/2014.

               8.   TYPE-APPROVAL OF RECORDING EQUIPMENT AND TACHOGRAPH CARDS
         8.1   General points

         For the purpose of this chapter, the words ‘recording equipment’ mean ‘recording equipment or its components’. No type approval is required for the cable(s) linking the motion sensor to the VU, the external GNSS facility to the VU or the remote communication facility to the VU. The paper, for use by the recording equipment, shall be considered as a component of the recording equipment.
         Any manufacturer may ask for type approval of its component with any type of motion sensor, external GNSS facility and vice versa, provided each component complies with the requirements of this annex. Alternately, manufacturers may also ask for type approval of recording equipment.

                     (425)

                     Recording equipment shall be submitted for approval complete with any integrated additional devices.

                     (426)

                     Type approval of recording equipment and of tachograph cards shall include security related tests, functional tests and interoperability tests. Positive results to each of these tests are stated by an appropriate certificate.

                     (427)

                     Member States type approval authorities will not grant a type approval certificate as long as they do not hold:

                                 —

                                 a security certificate,

                                 —

                                 a functional certificate,

                                 —

                                 and an interoperability certificate

                           for the recording equipment or the tachograph card, subject of the request for type approval.

                     (428)

                     Any modification in software or hardware of the equipment or in the nature of materials used for its manufacture shall, before being used, be notified to the authority which granted type-approval for the equipment. This authority shall confirm to the manufacturer the extension of the type approval, or may require an update or a confirmation of the relevant functional, security and/or interoperability certificates.

                     (429)

                     Procedures to upgrade in-situ recording equipment software shall be approved by the authority which granted type approval for the recording equipment. Software upgrade must not alter nor delete any driver activity data stored in the recording equipment. Software may be upgraded only under the responsibility of the equipment manufacturer.

                     (430)

                     Type approval of software modifications aimed to upgrade a previously type approved recording equipment may not be refused if such modifications only apply to functions not specified in this Annex. Software upgrade of a recording equipment may exclude the introduction of new character sets, if not technically feasible.

               8.2   Security certificate

                     (431)

                     The security certificate is delivered in accordance with the provisions of Appendix 10 of this Annex. Recording equipment components to be certified are vehicle unit, motion sensor, external GNSS facility and tachograph cards.

                     (432)

                     In the exceptional circumstance that the security certification authorities refuse to certify new equipment on the ground of obsolescence of the security mechanisms, type approval shall continue to be granted only in these specific and exceptional circumstances, and when no alternative solution, compliant with the Regulation, exists.

                     (433)

                     In this circumstance the Member State concerned shall, without delay, inform the European Commission, which shall, within twelve calendar months of the grant of the type approval, launch a procedure to ensure that the level of security is restored to its original levels.

               8.3   Functional certificate

                     (434)

                     Each candidate for type approval shall provide the Member State's type approval authority with all the material and documentation that the authority deems necessary.

                     (435)

                     Manufacturers shall provide the relevant samples of type approval candidate products and associated documentation required by laboratories appointed to perform functional tests, and within one month of the request being made. Any costs resulting from this request shall be borne by the requesting entity. Laboratories shall treat all commercially sensitive information in confidence.

                     (436)

                     A functional certificate shall be delivered to the manufacturer only after all functional tests specified in Appendix 9, at least, have been successfully passed.

                     (437)

                     The type approval authority delivers the functional certificate. This certificate shall indicate, in addition to the name of its beneficiary and the identification of the model, a detailed list of the tests performed and the results obtained.

                     (438)

                     The functional certificate of any recording equipment component shall also indicate the type approval numbers of the other type approved compatible recording equipment components tested for its certification.

                     (439)

                     The functional certificate of any recording equipment component shall also indicate the ISO or CEN standard against which the functional interface has been certified.

               8.4   Interoperability certificate

                     (440)

                     Interoperability tests are carried out by a single laboratory under the authority and responsibility of the European Commission.

                     (441)

                     The laboratory shall register interoperability test requests introduced by manufacturers in the chronological order of their arrival.

                     (442)

                     Requests will be officially registered only when the laboratory is in possession of:

                                 —

                                 the entire set of material and documents necessary for such interoperability tests,

                                 —

                                 the corresponding security certificate,

                                 —

                                 the corresponding functional certificate,

                           The date of the registration of the request shall be notified to the manufacturer.

                     (443)

                     No interoperability tests shall be carried out by the laboratory, for recording equipment or tachograph cards that have not been granted a security certificate and a functional certificate, except in the exceptional circumstances described in Requirement 432.

                     (444)

                     Any manufacturer requesting interoperability tests shall commit to leave to the laboratory in charge of these tests the entire set of material and documents which he provided to carry out the tests.

                     (445)

                     The interoperability tests shall be carried out, in accordance with the provisions of Appendix 9 of this Annex, with respectively all the types of recording equipment or tachograph cards:

                                 —

                                 for which type approval is still valid or,

                                 —

                                 for which type approval is pending and that have a valid interoperability certificate.

                     (446)

                     The interoperability tests shall cover all generations of recording equipment or tachograph cards still in use.

                     (447)

                     The interoperability certificate shall be delivered by the laboratory to the manufacturer only after all required interoperability tests have been successfully passed.

                     (448)

                     If the interoperability tests are not successful with one or more of the recording equipment or tachograph card(s), the interoperability certificate shall not be delivered, until the requesting manufacturer has realised the necessary modifications and has succeeded the interoperability tests. The laboratory shall identify the cause of the problem with the help of the manufacturers concerned by this interoperability fault and shall attempt to help the requesting manufacturer in finding a technical solution. In the case where the manufacturer has modified its product, it is the manufacturer's responsibility to ascertain from the relevant authorities that the security certificate and the functional certificates are still valid.

                     (449)

                     The interoperability certificate is valid for six months. It is revoked at the end of this period if the manufacturer has not received a corresponding type approval certificate. It is forwarded by the manufacturer to the type approval authority of the Member State who has delivered the functional certificate.

                     (450)

                     Any element that could be at the origin of an interoperability fault shall not be used for profit or to lead to a dominant position.

               8.5   Type-approval certificate

                     (451)

                     The type approval authority of the Member State may deliver the type approval certificate as soon as it holds the three required certificates.

                     (452)

                     The type approval certificate of any recording equipment component shall also indicate the type approval numbers of the other type approved interoperable recording equipment.

                     (453)

                     The type approval certificate shall be copied by the type approval authority to the laboratory in charge of the interoperability tests at the time of deliverance to the manufacturer.

                     (454)

                     The laboratory competent for interoperability tests shall run a public web site on which will be updated the list of recording equipment or tachograph cards models:

                                 —

                                 for which a request for interoperability tests have been registered,

                                 —

                                 having received an interoperability certificate (even provisional),

                                 —

                                 having received a type approval certificate.

               8.6   Exceptional procedure: first interoperability certificates for 2nd generation recording equipment and tachograph cards

                     (455)

                     Until four months after a first couple of 2nd generation recording equipment and 2nd generation tachograph cards (driver, workshop, control and company cards) have been certified to be interoperable, any interoperability certificate delivered (including the first ones), regarding requests registered during this period, shall be considered provisional.

                     (456)

                     If at the end of this period, all products concerned are mutually interoperable, all corresponding interoperability certificates shall become definitive.

                     (457)

                     If during this period, interoperability faults are found, the laboratory in charge of interoperability tests shall identify the causes of the problems with the help of all manufacturers involved and shall invite them to realize the necessary modifications.

                     (458)

                     If at the end of this period, interoperability problems still remain, the laboratory in charge of interoperability tests, with the collaboration of the manufacturers concerned and with the type approval authorities who delivered the corresponding functional certificates shall find out the causes of the interoperability faults and establish which modifications should be made by each of the manufacturers concerned. The search for technical solutions shall last for a maximum of two months, after which, if no common solution is found, the Commission, after having consulted the laboratory in charge of interoperability tests, shall decide which equipment(s) and cards get a definitive interoperability certificate and state the reasons why.

                     (459)

                     Any request for interoperability tests, registered by the laboratory between the end of the four month period after the first provisional interoperability certificate has been delivered and the date of the decision by the Commission referred to in requirement 455, shall be postponed until the initial interoperability problems have been solved. Those requests are then processed in the chronological order of their registration.

            (1)  This way of computing the continuous driving time and the cumulative break time serves in the recording equipment for computing the continuous driving time warning. It does not prejudge the legal interpretation to be made of these times. Alternative ways of computing the continuous driving time and the cumulative break time may be used to replace these definitions if they have been made obsolete by updates in other relevant legislation.

            (2)  UNKNOWN periods correspond to periods where the driver card was not inserted in the recording equipment and for which no manual entry of driver activities was made.

            (3)  Regulation (EC) No 561/2006 of the European Parliament and of the Council of 15 March 2006 on the harmonisation of certain social legislation relating to road transport and amending Council Regulations (EEC) No 3821/85 and (EC) No 2135/98 and repealing Council Regulation (EEC) No 3820/85 (OJ L 102, 11.4.2006, p. 1).

            (4)  Commission Regulation (EU) No 1230/2012 of 12 December 2012 implementing Regulation (EC) No 661/2009 of the European Parliament and of the Council with regard to type-approval requirements for masses and dimensions of motor vehicles and their trailers and amending Directive 2007/46/EC of the European Parliament and of the Council (OJ L 353, 21.12.2012, p. 31) as last amended.

            (5)  Council Directive 92/6/EEC of 10 February 1992 on the installation and use of speed limitation devices for certain categories of motor vehicles in the Community (OJ L 57, 2.3.1992, p. 27).

            (6)  Council Directive 92/23/EEC of 31 March 1992 relating to tyres for motor vehicles and their trailers and to their fitting (OJ L 129, 14.5.1992, p. 95).

            (7)  Council Directive 76/114/EEC of 18 December 1975 on the approximation of the laws of the Member States relating to statutory plates and inscriptions for motor vehicles and their trailers, and their location and method of attachment (OJ L 24, 30.1.1976, p. 1).

            (8)  Directive 2007/46/EC of the European Parliament and of the Council of 5 September 2007 establishing a framework for the approval of motor vehicles and their trailers, and of systems, components and separate technical units intended for such vehicles (Framework Directive) (OJ L 263, 9.10.2007, p. 1).

            (9)  Directive 95/46/EC of the European Parliament and of the Council of 24 October 1995 on the protection of individuals with regard to the processing of personal data and on the free movement of such data (OJ L 281, 23.11.1995, p. 31).

            (10)  Directive 2002/58/EC of the European Parliament and of the Council of 12 July 2002 concerning the processing of personal data and the protection of privacy in the electronic communications sector (Directive on privacy and electronic communications) (OJ L 201, 31.7.2002, p. 37).

            (11)  Regulation (EU) No 165/2014 of the European Parliament and of the Council of 4 February 2014 on tachographs in road transport, repealing Council Regulation (EEC) No 3821/85 on recording equipment in road transport and amending Regulation (EC) No 561/2006 of the European Parliament and of the Council on the harmonisation of certain social legislation relating to road transport (OJ L 60, 28.2.2014, p. 1).

            (12)  OJ L 281, 23.11.1995, p.31.

            (13)  OJ L 201, 31.7.2002, p.37

            (*)  In these situations the recording equipment shall use only the tachograph card inserted in the driver slot.

            (14)  OJ L 102, 11.4.2006, p.1

            (15)  Commission Regulation (EC) No 68/2009 of 23 January 2009 adapting for the ninth time to technical progress Council Regulation (EEC) No 3821/85 on recording equipment in road transport (OJ L 21, 24.1.2009, p. 3).

            Appendix 1

               DATA DICTIONARY

            TABLE OF CONTENT

                        1.

                     INTRODUCTION
                     88

                        1.1.

                     Approach for definitions of data types
                     88

                        1.2.

                     References
                     88

                        2.

                     DATA TYPE DEFINITIONS
                     89

                        2.1.

                     ActivityChangeInfo
                     89

                        2.2.

                     Address
                     90

                        2.3.

                     AESKey
                     91

                        2.4.

                     AES128Key
                     91

                        2.5.

                     AES192Key
                     91

                        2.6.

                     AES256Key
                     92

                        2.7.

                     BCDString
                     92

                        2.8.

                     CalibrationPurpose
                     92

                        2.9.

                     CardActivityDailyRecord
                     93

                        2.10.

                     CardActivityLengthRange
                     93

                        2.11.

                     CardApprovalNumber
                     93

                        2.12.

                     CardCertificate
                     94

                        2.13.

                     CardChipIdentification
                     94

                        2.14.

                     CardConsecutiveIndex
                     94

                        2.15.

                     CardControlActivityDataRecord
                     94

                        2.16.

                     CardCurrentUse
                     95

                        2.17.

                     CardDriverActivity
                     95

                        2.18.

                     CardDrivingLicenceInformation
                     95

                        2.19.

                     CardEventData
                     96

                        2.20.

                     CardEventRecord
                     96

                        2.21.

                     CardFaultData
                     96

                        2.22.

                     CardFaultRecord
                     97

                        2.23.

                     CardIccIdentification
                     97

                        2.24.

                     CardIdentification
                     97

                        2.25.

                     CardMACertificate
                     98

                        2.26.

                     CardNumber
                     98

                        2.27.

                     CardPlaceDailyWorkPeriod
                     99

                        2.28.

                     CardPrivateKey
                     99

                        2.29.

                     CardPublicKey
                     99

                        2.30.

                     CardRenewalIndex
                     99

                        2.31.

                     CardReplacementIndex
                     99

                        2.32.

                     CardSignCertificate
                     100

                        2.33.

                     CardSlotNumber
                     100

                        2.34.

                     CardSlotsStatus
                     100

                        2.35.

                     CardSlotsStatusRecordArray
                     100

                        2.36.

                     CardStructureVersion
                     101

                        2.37.

                     CardVehicleRecord
                     101

                        2.38.

                     CardVehiclesUsed
                     102

                        2.39.

                     CardVehicleUnitRecord
                     102

                        2.40.

                     CardVehicleUnitsUsed
                     102

                        2.41.

                     Certificate
                     103

                        2.42.

                     CertificateContent
                     103

                        2.43.

                     CertificateHolderAuthorisation
                     104

                        2.44.

                     CertificateRequestID
                     104

                        2.45.

                     CertificationAuthorityKID
                     104

                        2.46.

                     CompanyActivityData
                     105

                        2.47.

                     CompanyActivityType
                     106

                        2.48.

                     CompanyCardApplicationIdentification
                     106

                        2.49.

                     CompanyCardHolderIdentification
                     106

                        2.50.

                     ControlCardApplicationIdentification
                     106

                        2.51.

                     ControlCardControlActivityData
                     107

                        2.52.

                     ControlCardHolderIdentification
                     107

                        2.53.

                     ControlType
                     108

                        2.54.

                     CurrentDateTime
                     109

                        2.55.

                     CurrentDateTimeRecordArray
                     109

                        2.56.

                     DailyPresenceCounter
                     109

                        2.57.

                     Datef
                     109

                        2.58.

                     DateOfDayDownloaded
                     110

                        2.59.

                     DateOfDayDownloadedRecordArray
                     110

                        2.60.

                     Distance
                     110

                        2.61.

                     DriverCardApplicationIdentification
                     110

                        2.62.

                     DriverCardHolderIdentification
                     111

                        2.63.

                     DSRCSecurityData
                     112

                        2.64.

                     EGFCertificate
                     112

                        2.65.

                     EmbedderIcAssemblerId
                     112

                        2.66.

                     EntryTypeDailyWorkPeriod
                     113

                        2.67.

                     EquipmentType
                     113

                        2.68.

                     EuropeanPublicKey
                     114

                        2.69.

                     EventFaultRecordPurpose
                     114

                        2.70.

                     EventFaultType
                     114

                        2.71.

                     ExtendedSealIdentifier
                     115

                        2.72.

                     ExtendedSerialNumber
                     116

                        2.73.

                     FullCardNumber
                     116

                        2.74.

                     FullCardNumberAndGeneration
                     117

                        2.75.

                     Generation
                     117

                        2.76.

                     GeoCoordinates
                     117

                        2.77.

                     GNSSAccuracy
                     118

                        2.78.

                     GNSSContinuousDriving
                     118

                        2.79.

                     GNSSContinuousDrivingRecord
                     118

                        2.80.

                     GNSSPlaceRecord
                     118

                        2.81.

                     HighResOdometer
                     119

                        2.82.

                     HighResTripDistance
                     119

                        2.83.

                     HolderName
                     119

                        2.84.

                     InternalGNSSReceiver
                     119

                        2.85.

                     K-ConstantOfRecordingEquipment
                     119

                        2.86.

                     KeyIdentifier
                     120

                        2.87.

                     KMWCKey
                     120

                        2.88.

                     Language
                     120

                        2.89.

                     LastCardDownload
                     120

                        2.90.

                     LinkCertificate
                     120

                        2.91.

                     L-TyreCircumference
                     121

                        2.92.

                     MAC
                     121

                        2.93.

                     ManualInputFlag
                     121

                        2.94.

                     ManufacturerCode
                     121

                        2.95.

                     ManufacturerSpecificEventFaultData
                     121

                        2.96.

                     MemberStateCertificate
                     122

                        2.97.

                     MemberStateCertificateRecordArray
                     122

                        2.98.

                     MemberStatePublicKey
                     122

                        2.99.

                     Name
                     122

                        2.100.

                     NationAlpha
                     123

                        2.101.

                     NationNumeric
                     123

                        2.102.

                     NoOfCalibrationRecords
                     123

                        2.103.

                     NoOfCalibrationsSinceDownload
                     123

                        2.104.

                     NoOfCardPlaceRecords
                     123

                        2.105.

                     NoOfCardVehicleRecords
                     124

                        2.106.

                     NoOfCardVehicleUnitRecords
                     124

                        2.107.

                     NoOfCompanyActivityRecords
                     124

                        2.108.

                     NoOfControlActivityRecords
                     124

                        2.109.

                     NoOfEventsPerType
                     124

                        2.110.

                     NoOfFaultsPerType
                     124

                        2.111.

                     NoOfGNSSCDRecords
                     124

                        2.112.

                     NoOfSpecificConditionRecords
                     125

                        2.113.

                     OdometerShort
                     125

                        2.114.

                     OdometerValueMidnight
                     125

                        2.115.

                     OdometerValueMidnightRecordArray
                     125

                        2.116.

                     OverspeedNumber
                     125

                        2.117.

                     PlaceRecord
                     126

                        2.118.

                     PreviousVehicleInfo
                     126

                        2.119.

                     PublicKey
                     127

                        2.120.

                     RecordType
                     127

                        2.121.

                     RegionAlpha
                     128

                        2.122.

                     RegionNumeric
                     128

                        2.123.

                     RemoteCommunicationModuleSerialNumber
                     129

                        2.124.

                     RSAKeyModulus
                     129

                        2.125.

                     RSAKeyPrivateExponent
                     129

                        2.126.

                     RSAKeyPublicExponent
                     129

                        2.127.

                     RtmData
                     129

                        2.128.

                     SealDataCard
                     129

                        2.129.

                     SealDataVu
                     130

                        2.130.

                     SealRecord
                     130

                        2.131.

                     SensorApprovalNumber
                     130

                        2.132.

                     SensorExternalGNSSApprovalNumber
                     131

                        2.133.

                     SensorExternalGNSSCoupledRecord
                     131

                        2.134.

                     SensorExternalGNSSIdentification
                     131

                        2.135.

                     SensorExternalGNSSInstallation
                     132

                        2.136.

                     SensorExternalGNSSOSIdentifier
                     132

                        2.137.

                     SensorExternalGNSSSCIdentifier
                     132

                        2.138.

                     SensorGNSSCouplingDate
                     133

                        2.139.

                     SensorGNSSSerialNumber
                     133

                        2.140.

                     SensorIdentification
                     133

                        2.141.

                     SensorInstallation
                     133

                        2.142.

                     SensorInstallationSecData
                     134

                        2.143.

                     SensorOSIdentifier
                     134

                        2.144.

                     SensorPaired
                     134

                        2.145.

                     SensorPairedRecord
                     135

                        2.146.

                     SensorPairingDate
                     135

                        2.147.

                     SensorSCIdentifier
                     135

                        2.148.

                     SensorSerialNumber
                     135

                        2.149.

                     Signature
                     135

                        2.150.

                     SignatureRecordArray
                     136

                        2.151.

                     SimilarEventsNumber
                     136

                        2.152.

                     SpecificConditionRecord
                     136

                        2.153.

                     SpecificConditions
                     136

                        2.154.

                     SpecificConditionType
                     137

                        2.155.

                     Speed
                     137

                        2.156.

                     SpeedAuthorised
                     137

                        2.157.

                     SpeedAverage
                     138

                        2.158.

                     SpeedMax
                     138

                        2.159.

                     TachographPayload
                     138

                        2.160.

                     TachographPayloadEncrypted
                     138

                        2.161.

                     TDesSessionKey
                     138

                        2.162.

                     TimeReal
                     139

                        2.163.

                     TyreSize
                     139

                        2.164.

                     VehicleIdentificationNumber
                     139

                        2.165.

                     VehicleIdentificationNumberRecordArray
                     139

                        2.166.

                     VehicleRegistrationIdentification
                     139

                        2.167.

                     VehicleRegistrationNumber
                     140

                        2.168.

                     VehicleRegistrationNumberRecordArray
                     140

                        2.169.

                     VuAbility
                     140

                        2.170.

                     VuActivityDailyData
                     141

                        2.171.

                     VuActivityDailyRecordArray
                     141

                        2.172.

                     VuApprovalNumber
                     141

                        2.173.

                     VuCalibrationData
                     142

                        2.174.

                     VuCalibrationRecord
                     142

                        2.175.

                     VuCalibrationRecordArray
                     143

                        2.176.

                     VuCardIWData
                     144

                        2.177.

                     VuCardIWRecord
                     144

                        2.178.

                     VuCardIWRecordArray
                     145

                        2.179.

                     VuCardRecord
                     145

                        2.180.

                     VuCardRecordArray
                     146

                        2.181.

                     VuCertificate
                     146

                        2.182.

                     VuCertificateRecordArray
                     146

                        2.183.

                     VuCompanyLocksData
                     147

                        2.184.

                     VuCompanyLocksRecord
                     147

                        2.185.

                     VuCompanyLocksRecordArray
                     148

                        2.186.

                     VuControlActivityData
                     148

                        2.187.

                     VuControlActivityRecord
                     148

                        2.188.

                     VuControlActivityRecordArray
                     149

                        2.189.

                     VuDataBlockCounter
                     149

                        2.190.

                     VuDetailedSpeedBlock
                     149

                        2.191.

                     VuDetailedSpeedBlockRecordArray
                     150

                        2.192.

                     VuDetailedSpeedData
                     150

                        2.193.

                     VuDownloadablePeriod
                     150

                        2.194.

                     VuDownloadablePeriodRecordArray
                     151

                        2.195.

                     VuDownloadActivityData
                     151

                        2.196.

                     VuDownloadActivityDataRecordArray
                     151

                        2.197.

                     VuEventData
                     152

                        2.198.

                     VuEventRecord
                     152

                        2.199.

                     VuEventRecordArray
                     153

                        2.200.

                     VuFaultData
                     154

                        2.201.

                     VuFaultRecord
                     154

                        2.202.

                     VuFaultRecordArray
                     155

                        2.203.

                     VuGNSSCDRecord
                     155

                        2.204.

                     VuGNSSCDRecordArray
                     156

                        2.205.

                     VuIdentification
                     156

                        2.206.

                     VuIdentificationRecordArray
                     157

                        2.207.

                     VuITSConsentRecord
                     157

                        2.208.

                     VuITSConsentRecordArray
                     158

                        2.209.

                     VuManufacturerAddress
                     158

                        2.210.

                     VuManufacturerName
                     158

                        2.211.

                     VuManufacturingDate
                     158

                        2.212.

                     VuOverSpeedingControlData
                     159

                        2.213.

                     VuOverSpeedingControlDataRecordArray
                     159

                        2.214.

                     VuOverSpeedingEventData
                     159

                        2.215.

                     VuOverSpeedingEventRecord
                     159

                        2.216.

                     VuOverSpeedingEventRecordArray
                     160

                        2.217.

                     VuPartNumber
                     161

                        2.218.

                     VuPlaceDailyWorkPeriodData
                     161

                        2.219.

                     VuPlaceDailyWorkPeriodRecord
                     161

                        2.220.

                     VuPlaceDailyWorkPeriodRecordArray
                     162

                        2.221.

                     VuPrivateKey
                     162

                        2.222.

                     VuPublicKey
                     162

                        2.223.

                     VuSerialNumber
                     162

                        2.224.

                     VuSoftInstallationDate
                     162

                        2.225.

                     VuSoftwareIdentification
                     163

                        2.226.

                     VuSoftwareVersion
                     163

                        2.227.

                     VuSpecificConditionData
                     163

                        2.228.

                     VuSpecificConditionRecordArray
                     163

                        2.229.

                     VuTimeAdjustmentData
                     164

                        2.230.

                     VuTimeAdjustmentGNSSRecord
                     164

                        2.231.

                     VuTimeAdjustmentGNSSRecordArray
                     164

                        2.232.

                     VuTimeAdjustmentRecord
                     165

                        2.233.

                     VuTimeAdjustmentRecordArray
                     165

                        2.234.

                     WorkshopCardApplicationIdentification
                     166

                        2.235.

                     WorkshopCardCalibrationData
                     166

                        2.236.

                     WorkshopCardCalibrationRecord
                     167

                        2.237.

                     WorkshopCardHolderIdentification
                     168

                        2.238.

                     WorkshopCardPIN
                     168

                        2.239.

                     W-VehicleCharacteristicConstant
                     169

                        2.240.

                     VuPowerSupplyInterruptionRecord
                     169

                        2.241.

                     VuPowerSupplyInterruptionRecordArray
                     169

                        2.242.

                     VuSensorExternalGNSSCoupledRecordArray
                     170

                        2.243.

                     VuSensorPairedRecordArray
                     170

                        3.

                     VALUE AND SIZE RANGE DEFINITIONS
                     171

                        4.

                     CHARACTER SETS
                     171

                        5.

                     ENCODING
                     171

                        6.

                     OBJECT IDENTIFIERS UND APPLICATION IDENTIFIERS
                     171

                        6.1.

                     Object Identifiers
                     171

                        6.2.

                     Application Identifiers
                     172
                  1.   INTRODUCTION
            This appendix specifies data formats, data elements, and data structures for use within the recording equipment and tachograph cards.
            1.1.   Approach for definitions of data types

            This appendix uses Abstract Syntax Notation One (ASN.1) to define data types. This enables simple and structured data to be defined without implying any specific transfer syntax (encoding rules) which will be application and environment dependent.
            ASN.1 type naming conventions are done in accordance with ISO/IEC 8824-1. This implies that:

                        —

                        where possible, the meaning of the data type is implied through the names being selected,

                        —

                        where a data type is a composition of other data types, the data type name is still a single sequence of alphabetical characters commencing with a capital letter, however capitals are used within the name to impart the corresponding meaning,

                        —

                        in general, the data types names are related to the name of the data types from which they are constructed, the equipment in which data is stored and the function related to the data.

                  If an ASN.1 type is already defined as part of another standard and if it is relevant for usage in the recording equipment, then this ASN.1 type will be defined in this appendix.
            To enable several types of encoding rules, some ASN.1 types in this appendix are constrained by value range identifiers. The value range identifiers are defined in paragraph 3 and Appendix 2.
            1.2.   References

            The following references are used in this Appendix:

                        ISO 639

                        Code for the representation of names of languages. First Edition: 1988.

                        ISO 3166

                        Codes for the representation of names of countries and their subdivisions — Part 1: Country codes, 2013

                        ISO 3779

                        Road vehicles — Vehicle identification number (VIN) — Content and structure. 2009

                        ISO/IEC 7816-5

                        Identification cards — Integrated circuit cards — Part 5: Registration of application providers.
                        Second edition: 2004.

                        ISO/IEC 7816-6

                        Identification cards — Integrated circuit cards — Part 6: Interindustry data elements for interchange, 2004 + Technical Corrigendum 1: 2006

                        ISO/IEC 8824-1

                        Information technology — Abstract Syntax Notation One (ASN.1): Specification of basic notation. 2008 + Technical Corrigendum 1: 2012 and Technical Corrigendum 2: 2014.

                        ISO/IEC 8825-2

                        Information technology — ASN.1 encoding rules: Specification of Packed Encoding Rules (PER). 2008.

                        ISO/IEC 8859-1

                        Information technology — 8 bit single-byte coded graphic character sets — Part 1: Latin alphabet No.1. First edition: 1998.

                        ISO/IEC 8859-7

                        Information technology — 8 bit single-byte coded graphic character sets — Part 7: Latin/Greek alphabet. 2003.

                        ISO 16844-3

                        Road vehicles — Tachograph systems — Motion Sensor Interface. 2004 + Technical Corrigendum 1: 2006..

                        TR-03110-3

                        BSI / ANSSI Technical Guideline TR-03110-3, Advanced Security Mechanisms for Machine Readable Travel Documents and eIDAS Token — Part 3 Common Specifications, version 2.20, 3. February 2015

                  2.   DATA TYPE DEFINITIONS
            For any of the following data types, the default value for an ‘unknown’ or a ‘not applicable’ content will consist in filling the data element with ‘FF’ bytes.
            All data types are used for Generation 1 and Generation 2 applications unless otherwise specified.
            2.1.   ActivityChangeInfo

            This data type enables to code, within a two bytes word, a slot status at 00:00 and/or a driver status at 00:00 and/or changes of activity and/or changes of driving status and/or changes of card status for a driver or a co-driver. This data type is related to Annex 1C requirements 105, 266, 291, 320, 321, 343, and 344.

            Text of image

               ActivityChangeInfo ::= OCTET STRING (SIZE(2))

               Value assignment — Octet Aligned: ‘scpaattttttttttt’B (16 bits)
            For Data Memory recordings (or slot status):

                        ‘s’B

                        Slot:

                                    ‘0’B: DRIVER,

                                    ‘1’B: CO-DRIVER,

                        ‘c’B

                        Driving status:

                                    ‘0’B: SINGLE,

                                    ‘1’B: CREW,

                        ‘p’B

                        Driver (or workshop) card status in the relevant slot:

                                    ‘0’B: INSERTED, a card is inserted,

                                    ‘1’B: NOT INSERTED, no card is inserted (or a card is withdrawn),

                        ‘aa’B

                        Activity:

                                    ‘00’B: BREAK/REST,

                                    ‘01’B: AVAILABILITY,

                                    ‘10’B: WORK,

                                    ‘11’B: DRIVING,

                        ‘ttttttttttt’B

                        Time of the change: Number of minutes since 00h00 on the given day.

                  For Driver (or Workshop) card recordings (and driver status):

                        ‘s’B

                        Slot (not relevant when ‘p’=1 except note below):

                                    ‘0’B: DRIVER,

                                    ‘1’B: CO-DRIVER,

                        ‘c’B

                        Driving status (case ‘p’=0) or
                        Following activity status (case ‘p’=1):

                                    ‘0’B: SINGLE,

                                    ‘0’B: UNKNOWN

                                    ‘1’B: CREW,

                                    ‘1’B: KNOWN (=manually entered)

                        ‘p’B

                        Card status:

                                    ‘0’B: INSERTED, the card is inserted in a recording equipment,

                                    ‘1’B: NOT INSERTED, the card is not inserted (or the card is withdrawn),

                        ‘aa’B

                        Activity (not relevant when ‘p’=1 and ‘c’=0 except note below):

                                    ‘00’B: BREAK/REST,

                                    ‘01’B: AVAILABILITY,

                                    ‘10’B: WORK,

                                    ‘11’B: DRIVING,

                        ‘ttttttttttt’B

                        Time of the change: Number of minutes since 00h00 on the given day.

               Note for the case ‘card withdrawal’:

            When the card is withdrawn:

                        —

                        ‘s’ is relevant and indicates the slot from which the card is withdrawn,

                        —

                        ‘c’ must be set to 0,

                        —

                        ‘p’ must be set to 1,

                        —

                        ‘aa’ must code the current activity selected at that time,

                  As a result of a manual entry, the bits ‘c’ and ‘aa’ of the word (stored in a card) may be overwritten later to reflect the entry.
            2.2.   Address

            An address.

            Text of image

               Address ::= SEQUENCE {
               codePage INTEGER (0..255),
               address OCTET STRING (SIZE(35))
               }

               codePage specifies a character set defined in Chapter 4,

               address is an address encoded using the specified character set.
            2.3.   AESKey

               Generation 2:

            An AES key with a length of 128, 192 or 256 bits.

            Text of image

               AESKey ::= CHOICE {
               aes128Key AES128Key,
               aes192Key AES192Key,
               aes256Key AES256Key
               }

               Value assignment: not further specified.
            2.4.   AES128Key

               Generation 2:

            An AES128 key.

            Text of image

               AES128Key ::= SEQUENCE {
               length INTEGER(0..255),
               aes128Key OCTET STRING (SIZE(16))
               }

               length denotes the length of the AES128 key in octets.

               aes128Key is an AES key with a length of 128 bits.

               Value assignment:

            The length shall have the value 16.
            2.5.   AES192Key

               Generation 2:

            An AES192 key.

            Text of image

               AES192Key ::= SEQUENCE {
               length INTEGER(0..255),
               aes192Key OCTET STRING (SIZE(24))
               }

               length denotes the length of the AES192 key in octets.

               aes192Key is an AES key with a length of 192 bits.

               Value assignment:

            The length shall have the value 24.
            2.6.   AES256Key

               Generation 2:

            An AES256 key.

            Text of image

               AES256Key ::= SEQUENCE {
               length INTEGER(0..255),
               aes256Key OCTET STRING (SIZE(32))
               }

               length denotes the length of the AES256 key in octets.

               aes256Key is an AES key with a length of 256 bits.

               Value assignment:

            The length shall have the value 32.
            2.7.   BCDString

            BCDString is applied for Binary Code Decimal (BCD) representation. This data type is used to represent one decimal digit in one semi octet (4 bits). BCDString is based on the ISO/IEC 8824-1 ‘CharacterStringType’.

            Text of image

               BCDString ::= CHARACTER STRING (WITH COMPONENTS {
               identification ( WITH COMPONENTS {
               fixed PRESENT }) })

            BCDString uses an ‘hstring’ notation. The leftmost hexadecimal digit shall be the most significant semi octet of the first octet. To produce a multiple of octets, zero trailing semi octets shall be inserted, as needed, from the leftmost semi octet position in the first octet.
            Permitted digits are: 0, 1, .. 9.
            2.8.   CalibrationPurpose

            Code explaining why a set of calibration parameters was recorded. This data type is related to Annex 1B requirements 097 and 098 and Annex 1C requirements 119.

            Text of image

               CalibrationPurpose ::= OCTET STRING (SIZE(1))

               Value assignment:

                        Generation 1:

                                    ‘00’H

                                    reserved value,

                                    ‘01’H

                                    activation: recording of calibration parameters known, at the moment of the VU activation,

                                    ‘02’H

                                    first installation: first calibration of the VU after its activation,

                                    ‘03’H

                                    installation: first calibration of the VU in the current vehicle,

                                    ‘04’H

                                    periodic inspection.

                        Generation 2:
                        In addition to generation 1 the following values are used:

                                    ‘05’H

                                    entry of VRN by company,

                                    ‘06’H

                                    time adjustment without calibration,

                                    ‘07’H to ‘7F’H

                                    RFU,

                                    ‘80’H to ‘FF’H

                                    Manufacturer specific.

                  2.9.   CardActivityDailyRecord

            Information, stored in a card, related to the driver activities for a particular calendar day. This data type is related to Annex 1C requirements 266, 291, 320 and 343.

            Text of image

               CardActivityDailyRecord ::= SEQUENCE {
               activityPreviousRecordLength INTEGER(0..CardActivityLengthRange),
               activityRecordLength INTEGER(0..CardActivityLengthRange),
               activityRecordDate TimeReal,
               activityDailyPresenceCounter DailyPresenceCounter,
               activityDayDistance Distance,
               activityChangeInfo SET SIZE(1..1440) OF ActivityChangeInfo
               }

               activityPreviousRecordLength is the total length in bytes of the previous daily record. The maximum value is given by the length of the OCTET STRING containing these records (see CardActivityLengthRange Appendix 2 paragraph 4). When this record is the oldest daily record, the value of activityPreviousRecordLength must be set to 0.

               activityRecordLength is the total length in bytes of this record. The maximum value is given by the length of the OCTET STRING containing these records.

               activityRecordDate is the date of the record.

               activityDailyPresenceCounter is the daily presence counter for the card this day.

               activityDayDistance is the total distance travelled this day.

               activityChangeInfo is the set of ActivityChangeInfo data for the driver this day. It may contain at maximum 1440 values (one activity change per minute). This set always includes the activityChangeInfo coding the driver status at 00:00.
            2.10.   CardActivityLengthRange

            Number of bytes in a driver or a workshop card, available to store driver activity records.

            Text of image

               CardActivityLengthRange ::= INTEGER(0..216-1)

               Value assignment: see Appendix 2.
            2.11.   CardApprovalNumber

            Type approval number of the card.

            Text of image

               CardApprovalNumber ::= IA5String(SIZE(8))

               Value assignment:

            The approval number shall be provided as published on the corresponding European Commission web site, i.e. for example including hyphens if any. The approval number shall be left-aligned.
            2.12.   CardCertificate

            Generation 1:
            Certificate of the public key of a card.

            Text of image

               CardCertificate ::= Certificate

            2.13.   CardChipIdentification

            Information, stored in a card, related to the identification of the card's Integrated Circuit (IC) (Annex 1C requirement 249). The icSerialNumber together with the icManufacturingReferences identifies the card chip uniquely. The icSerialNumber alone does not uniquely identify the card chip.

            Text of image

               CardChipIdentification ::= SEQUENCE {
               icSerialNumber OCTET STRING (SIZE(4)),
               icManufacturingReferences OCTET STRING (SIZE(4))
               }

               icSerialNumber is the IC serial number.

               icManufacturingReferences is the IC manufacturer specific identifier.
            2.14.   CardConsecutiveIndex

            A card consecutive index (definition h)).

            Text of image

               CardConsecutiveIndex ::= IA5String(SIZE(1))

               Value assignment: (see Annex 1C chapter 7)
            Order for increase: ‘0, …, 9, A, …, Z, a, …, z’
            2.15.   CardControlActivityDataRecord

            Information, stored in a driver or workshop card, related to the last control the driver has been subject to (Annex 1C requirements 274, 299, 327, and 350).

            Text of image

               CardControlActivityDataRecord ::= SEQUENCE {
               controlType ControlType,
               controlTime TimeReal,
               controlCardNumber FullCardNumber,
               controlVehicleRegistration VehicleRegistrationIdentification,
               controlDownloadPeriodBegin TimeReal,
               controlDownloadPeriodEnd TimeReal
               }

               controlType is the type of the control.

               controlTime is the date and time of the control.

               controlCardNumber is the FullCardNumber of the control officer having performed the control.

               controlVehicleRegistration is the VRN and registering Member State of the vehicle in which the control happened.

               controlDownloadPeriodBegin and controlDownloadPeriodEnd is the period downloaded, in case of downloading.
            2.16.   CardCurrentUse

            Information about the actual usage of the card (Annex 1C requirement 273, 298, 326, and 349).

            Text of image

               CardCurrentUse ::= SEQUENCE {
               sessionOpenTime TimeReal,
               sessionOpenVehicle VehicleRegistrationIdentification
               }

               sessionOpenTime is the time when the card is inserted for the current usage. This element is set to zero at card removal.

               sessionOpenVehicle is the identification of the currently used vehicle, set at card insertion. This element is set to zero at card removal.
            2.17.   CardDriverActivity

            Information, stored in a driver or a workshop card, related to the activities of the driver (Annex 1C requirements 267, 268, 292, 293, 321 and 344).

            Text of image

               CardDriverActivity ::= SEQUENCE {
               activityPointerOldestDayRecord INTEGER(0.. CardActivityLengthRange-1),
               activityPointerNewestRecord INTEGER(0.. CardActivityLengthRange-1),
               activityDailyRecords OCTET STRING
               (SIZE(CardActivityLengthRange))
               }

               activityPointerOldestDayRecord is the specification of the begin of the storage place (number of bytes from the beginning of the string) of the oldest complete day record in the activityDailyRecords string. The maximum value is given by the length of the string.

               activityPointerNewestRecord is the specification of the begin of the storage place (number of bytes from the beginning of the string) of the most recent day record in the activityDailyRecords string. The maximum value is given by the length of the string.

               activityDailyRecords is the space available to store the driver activity data (data structure: CardActivityDailyRecord) for each calendar day where the card has been used.

               Value assignment: this octet string is cyclically filled with records of CardActivityDailyRecord. At the first use storing is started at the first byte of the string. All new records are appended at the end of the previous one. When the string is full, storing continues at the first byte of the string independently of a break being inside a data element. Before placing new activity data in the string (enlarging current activityDailyRecord, or placing a new activityDailyRecord) that replaces older activity data, activityPointerOldestDayRecord must be updated to reflect the new location of the oldest complete day record, and activityPreviousRecordLength of this (new) oldest complete day record must be reset to 0.
            2.18.   CardDrivingLicenceInformation

            Information, stored in a driver card, related to the card holder driver licence data (Annex 1C requirement 259 and 284).

            Text of image

               CardDrivingLicenceInformation ::= SEQUENCE {
               drivingLicenceIssuingAuthority Name,
               drivingLicenceIssuingNation NationNumeric,
               drivingLicenceNumber IA5String(SIZE(16))
               }

               drivingLicenceIssuingAuthority is the authority responsible for issuing the driving licence.

               drivingLicenceIssuingNation is the nationality of the authority that issued the driving licence.

               drivingLicenceNumber is the number of the driving licence.
            2.19.   CardEventData

            Information, stored in a driver or workshop card, related to the events associated with the card holder (Annex 1C requirements 260, 285, 318 and 341).

            Text of image

               CardEventData ::= SEQUENCE SIZE(6) OF {
               cardEventRecords SET SIZE(NoOfEventsPerType) OF
               CardEventRecord
               }

               CardEventData is a sequence, ordered by ascending value of EventFaultType, of cardEventRecords (except security breach attempts related records which are gathered in the last set of the sequence).

               cardEventRecords is a set of event records of a given event type (or category for security breach attempts events).
            2.20.   CardEventRecord

            Information, stored in a driver or a workshop card, related to an event associated to the card holder (Annex 1C requirements 261, 286, 318 and 341).

            Text of image

               CardEventRecord ::= SEQUENCE {
               eventType EventFaultType,
               eventBeginTime TimeReal,
               eventEndTime TimeReal,
               eventVehicleRegistration VehicleRegistrationIdentification
               }

               eventType is the type of the event.

               eventBeginTime is the date and time of beginning of event.

               eventEndTime is the date and time of end of event.

               eventVehicleRegistration is the VRN and registering Member State of vehicle in which the event happened.
            2.21.   CardFaultData

            Information, stored in a driver or a workshop card, related to the faults associated to the card holder (Annex 1C requirements 263, 288, 318, and 341).

            Text of image

               CardFaultData ::= SEQUENCE SIZE(2) OF {
               cardFaultRecords SET SIZE(NoOfFaultsPerType) OF
               CardFaultRecord
               }

               CardFaultData is a sequence of Recording Equipment faults set of records followed by card faults set of records.

               cardFaultRecords is a set of fault records of a given fault category (Recording Equipment or card).
            2.22.   CardFaultRecord

            Information, stored in a driver or a workshop card, related to a fault associated to the card holder (Annex 1C requirement 264, 289, 318, and 341).

            Text of image

               CardFaultRecord ::= SEQUENCE {
               faultType EventFaultType,
               faultBeginTime TimeReal,
               faultEndTime TimeReal,
               faultVehicleRegistration VehicleRegistrationIdentification
               }

               faultType is the type of the fault.

               faultBeginTime is the date and time of beginning of fault.

               faultEndTime is the date and time of end of fault.

               faultVehicleRegistration is the VRN and registering Member State of vehicle in which the fault happened.
            2.23.   CardIccIdentification

            Information, stored in a card, related to the identification of the integrated circuit (IC) card (Annex 1C requirement 248).

            Text of image

               CardIccIdentification ::= SEQUENCE {
               clockStop OCTET STRING (SIZE(1)),
               cardExtendedSerialNumber ExtendedSerialNumber,
               cardApprovalNumber CardApprovalNumber,
               cardPersonaliserID ManufacturerCode,
               embedderIcAssemblerId EmbedderIcAssemblerId,
               icIdentifier OCTET STRING (SIZE(2))
               }

               clockStop is the Clockstop mode as defined in appendix 2.

               cardExtendedSerialNumber is the IC card unique serial number as further specified by the ExtendedSerialNumber data type.

               cardApprovalNumber is the type approval number of the card.

               cardPersonaliserID is the card personaliser ID encoded as ManufacturerCode.

               embedderIcAssemblerId provides information about the embedder/IC assembler.

               icIdentifier is the Identifier of the IC on the card and its IC manufacturer as defined in ISO/IEC 7816-6.
            2.24.   CardIdentification

            Information, stored in a card, related to the identification of the card (Annex 1C requirements 255, 280, 310, 333, 359, 365, 371, and 377).

            Text of image

               CardIdentification ::= SEQUENCE {
               cardIssuingMemberState NationNumeric,
               cardNumber CardNumber,
               cardIssuingAuthorityName Name,
               cardIssueDate TimeReal,
               cardValidityBegin TimeReal,
               cardExpiryDate TimeReal
               }

               cardIssuingMemberState is the code of the Member State issuing the card.

               cardNumber is the card number of the card.

               cardIssuingAuthorityName is the name of the authority having issued the Card.

               cardIssueDate is the issue date of the Card to the current holder.

               cardValidityBegin is the first date of validity of the card.

               cardExpiryDate is the date when the validity of the card ends.
            2.25.   CardMACertificate

            Generation 2:
            Certificate of the card public key for mutual authentication with a VU. The structure of this certificate is specified in Appendix 11.

            Text of image

               CardMACertificate ::= Certificate

            2.26.   CardNumber

            A card number as defined by definition g).

            Text of image

               CardNumber ::= CHOICE {
               SEQUENCE {
               driverIdentification IA5String(SIZE(14)),
               cardReplacementIndex CardReplacementIndex,
               cardRenewalIndex CardRenewalIndex
               },
               SEQUENCE {
               ownerIdentification IA5String(SIZE(13)),
               cardConsecutiveIndex CardConsecutiveIndex,
               cardReplacementIndex CardReplacementIndex,
               cardRenewalIndex CardRenewalIndex
               }
               }

               driverIdentification is the unique identification of a driver in a Member State.

               ownerIdentification is the unique identification of a company or a workshop or a control body within a member state.

               cardConsecutiveIndex is the card consecutive index.

               cardReplacementIndex is the card replacement index.

               cardRenewalIndex is the card renewal index.
            The first sequence of the choice is suitable to code a driver card number, the second sequence of the choice is suitable to code workshop, control, and company card numbers.
            2.27.   CardPlaceDailyWorkPeriod

            Information, stored in a driver or a workshop card, related to the places where daily work periods begin and/or end (Annex 1C requirements 272, 297, 325, and 348).

            Text of image

               CardPlaceDailyWorkPeriod ::= SEQUENCE {
               placePointerNewestRecord INTEGER(0 .. NoOfCardPlaceRecords-1),
               placeRecords SET SIZE(NoOfCardPlaceRecords) OF PlaceRecord
               }

               placePointerNewestRecord is the index of the last updated place record.

               Value assignment: Number corresponding to the numerator of the place record, beginning with ‘0’ for the first occurrence of the place records in the structure.

               placeRecords is the set of records containing the information related to the places entered.
            2.28.   CardPrivateKey

            Generation 1:
            The private key of a card.

            Text of image

               CardPrivateKey ::= RSAKeyPrivateExponent

            2.29.   CardPublicKey

            The public key of a card.

            Text of image

               CardPublicKey ::= PublicKey

            2.30.   CardRenewalIndex

            A card renewal index (definition i)).

            Text of image

               CardRenewalIndex ::= IA5String(SIZE(1))

               Value assignment: (see this Annex chapter VII).

                        ‘0’

                        First issue.

                  Order for increase: ‘0, …, 9, A, …, Z’
            2.31.   CardReplacementIndex

            A card replacement index (definition j)).

            Text of image

               CardReplacementIndex ::= IA5String(SIZE(1))

               Value assignment: (see this Annex chapter VII).

                        ‘0’

                        Original card.

                  Order for increase: ‘0, …, 9, A, …, Z’
            2.32.   CardSignCertificate

            Generation 2:
            Certificate of the card public key for signature. The structure of this certificate is specified in Appendix 11.

            Text of image

               CardSignCertificate ::= Certificate

            2.33.   CardSlotNumber

            Code to distinguish between the two slots of a Vehicle Unit.

            Text of image

               CardSlotNumber ::= INTEGER {
               driverSlot (0),
               co-driverSlot (1)
               }

               Value assignment: not further specified.
            2.34.   CardSlotsStatus

            Code indicating the type of cards inserted in the two slots of the vehicle unit.

            Text of image

               CardSlotsStatus ::= OCTET STRING (SIZE(1))

               Value assignment — Octet Aligned: ‘ccccdddd’B

                        ‘cccc’B

                        Identification of the type of card inserted in the co-driver slot,

                        ‘dddd’B

                        Identification of the type of card inserted in the driver slot,

                  with the following identification codes:

                        ‘0000’B

                        no card is inserted,

                        ‘0001’B

                        a driver card is inserted,

                        ‘0010’B

                        a workshop card is inserted,

                        ‘0011’B

                        a control card is inserted,

                        ‘0100’B

                        a company card is inserted.

                  2.35.   CardSlotsStatusRecordArray

            Generation 2:
            The CardSlotsStatus plus metadata as used in the download protocol.

            Text of image

               CardSlotsStatusRecordArray ::= SEQUENCE {
               recordType RecordType,
               recordSize INTEGER(1..65535),
               noOfRecords INTEGER(0..65535),
               records SET SIZE(noOfRecords) OF CardSlotsStatus
               }

               recordType denotes the type of the record (CardSlotsStatus). Value Assignment: See RecordType

               recordSize is the size of the CardSlotsStatus in bytes.

               noOfRecords is the number of records in the set records.

               records is the set of CardSlotsStatus records.
            2.36.   CardStructureVersion

            Code indicating the version of the implemented structure in a tachograph card.

            Text of image

               CardStructureVersion ::= OCTET STRING (SIZE(2))

               Value assignment: ‘aabb’H:

                        ‘aa’H

                        Index for changes of the structure.

                                    ‘00’H for Generation 1 applications

                                    ‘01’H for Generation 2 applications

                        ‘bb’H

                        Index for changes concerning the use of the data elements defined for the structure given by the high byte.

                                    ‘00’H for this version of Generation 1 applications

                                    ‘00’H for this version of Generation 2 applications

                  2.37.   CardVehicleRecord

            Information, stored in a driver or workshop card, related to a period of use of a vehicle during a calendar day (Annex 1C requirements 269, 294, 322, and 345).

                        Generation 1:
                        Text of image

                           CardVehicleRecord ::= SEQUENCE {
                           vehicleOdometerBegin OdometerShort,
                           vehicleOdometerEnd OdometerShort,
                           vehicleFirstUse TimeReal,
                           vehicleLastUse TimeReal,
                           vehicleRegistration VehicleRegistrationIdentification,
                           vuDataBlockCounter VuDataBlockCounter
                           }

                           vehicleOdometerBegin is the vehicle odometer value at the beginning of the period of use of the vehicle.

                           vehicleOdometerEnd is the vehicle odometer value at the end of the period of use of the vehicle.

                           vehicleFirstUse is the date and time of the beginning of the period of use of the vehicle.

                           vehicleLastUse is the date and time of the end of the period of use of the vehicle.

                           vehicleRegistration is the VRN and the registering Member State of the vehicle.

                           vuDataBlockCounter is the value of the VuDataBlockCounter at last extraction of the period of use of the vehicle.

                        Generation 2:
                        Text of image

                           CardVehicleRecord ::= SEQUENCE {
                           vehicleOdometerBegin OdometerShort,
                           vehicleOdometerEnd OdometerShort,
                           vehicleFirstUse TimeReal,
                           vehicleLastUse TimeReal,
                           vehicleRegistration VehicleRegistrationIdentification,
                           vuDataBlockCounter VuDataBlockCounter,
                           vehicleIdentificationNumber VehicleIdentificationNumber
                           }

                        In addition to generation 1 the following data element is used:

                           VehicleIdentificationNumber is the vehicle identification number referring to the vehicle as a whole.

                  2.38.   CardVehiclesUsed

            Information, stored in a driver or workshop card, related to the vehicles used by the card holder (Annex 1C requirements 270, 295, 323, and 346).

            Text of image

               CardVehiclesUsed := SEQUENCE {
               vehiclePointerNewestRecord INTEGER(0..NoOfCardVehicleRecords-1),
               cardVehicleRecords SET SIZE(NoOfCardVehicleRecords) OF CardVehicleRecord
               }

               vehiclePointerNewestRecord is the index of the last updated vehicle record.

               Value assignment: Number corresponding to the numerator of the vehicle record, beginning with ‘0’ for the first occurrence of the vehicle records in the structure.

               cardVehicleRecords is the set of records containing information on vehicles used.
            2.39.   CardVehicleUnitRecord

            Generation 2:
            Information, stored in a driver or workshop card, related to a vehicle unit that was used (Annex 1C requirement 303 and 351).

            Text of image

               CardVehicleUnitRecord ::= SEQUENCE {
               timeStamp TimeReal,
               manufacturerCode ManufacturerCode,
               deviceID INTEGER(0..255),
               vuSoftwareVersion VuSoftwareVersion
               }

               timeStamp is the beginning of the period of use of the vehicle unit (i.e. first card insertion in the vehicle unit for the period).

               manufacturerCode identifies the manufacturer of the Vehicle Unit.

               deviceID identifies the Vehicle Unit type of a manufacturer. The value is manufacturer specific.

               vuSoftwareVersion is the software version number of the Vehicle Unit.
            2.40.   CardVehicleUnitsUsed

            Generation 2:
            Information, stored in a driver or workshop card, related to the vehicle units used by the card holder (Annex 1C requirement 306 and 352).

            Text of image

               CardVehicleUnitsUsed := SEQUENCE {
               vehicleUnitPointerNewestRecord INTEGER(0..NoOfCardVehicleUnitRecords-1),
               cardVehicleUnitRecords SET SIZE(NoOfCardVehicleUnitRecords) OF CardVehicleUnitRecord
               }

               vehicleUnitPointerNewestRecord is the index of the last updated vehicle unit record.

               Value assignment: Number corresponding to the numerator of the vehicle unit record, beginning with ‘0’ for the first occurrence of the vehicle unit records in the structure.

               cardVehicleUnitRecords is the set of records containing information on vehicle units used.
            2.41.   Certificate

            The certificate of a public key issued by a Certification Authority.

                        Generation 1:
                        Text of image

                           Certificate ::= OCTET STRING (SIZE(194))

                           Value assignment: digital signature with partial recovery of a CertificateContent according to Appendix 11 common security mechanisms: Signature (128 bytes) || Public Key remainder (58 bytes) || Certification Authority Reference (8 bytes).

                        Generation 2:
                        Text of image

                           Certificate ::= OCTET STRING (SIZE(204..341))

                        Value assignment: See Appendix 11

                  2.42.   CertificateContent

            Generation 1:
            The (clear) content of the certificate of a public key according to Appendix 11 common security mechanisms.

            Text of image

               CertificateContent ::= SEQUENCE {
               certificateProfileIdentifier INTEGER(0..255),
               certificationAuthorityReference KeyIdentifier,
               certificateHolderAuthorisation CertificateHolderAuthorisation,
               certificateEndOfValidity TimeReal,
               certificateHolderReference KeyIdentifier,
               publicKey PublicKey
               }

               certificateProfileIdentifier is the version of the corresponding certificate.

               Value assignment: ‘01h’ for this version.

               certificationAuthorityReference identifies the Certification Authority issuing the certificate. It also references the Public Key of this Certification Authority.

               certificateHolderAuthorisation identifies the rights of the certificate holder.

               certificateEndOfValidity is the date when the certificate expires administratively.

               certificateHolderReference identifies the certificate holder. It also references his Public Key.

               publicKey is the public key that is certified by this certificate.
            2.43.   CertificateHolderAuthorisation

            Identification of the rights of a certificate holder.

            Text of image

               CertificateHolderAuthorisation ::= SEQUENCE {
               tachographApplicationID OCTET STRING(SIZE(6))
               equipmentType EquipmentType
               }

                        Generation 1:

                                       tachographApplicationID is the application identifier for the tachograph application.

                                       Value assignment: ‘FFh’ ‘54h’ ‘41h’ ‘43h’ ‘48h’ ‘4Fh’. This AID is a proprietary non registered application identifier in accordance with ISO/IEC 7816-5.

                                       equipmentType is the identification of the type of equipment to which the certificate is intended.

                                       Value assignment: in accordance with EquipmentType data type. 0 if certificate is the one of a Member State.

                        Generation 2:

                                       tachographApplicationID denotes the 6 most significant bytes of the generation 2 tachograph card application identifier (AID). The AID for the tachograph card application is specified in chapter 6.2.

                                       Value assignment:‘FF 53 4D 52 44 54’.

                                       equipmentType is the identification of the type of equipment as specified for generation 2 to which the certificate is intended.

                                       Value assignment: in accordance with EquipmentType data type.

                  2.44.   CertificateRequestID

            Unique identification of a certificate request. It can also be used as a Vehicle Unit Public Key Identifier if the serial number of the vehicle Unit to which the key is intended is not known at certificate generation time.

            Text of image

               CertificateRequestID ::= SEQUENCE{
               requestSerialNumber INTEGER(0..232-1),
               requestMonthYear BCDString(SIZE(2)),
               crIdentifier OCTET STRING(SIZE(1)),
               manufacturerCode ManufacturerCode
               }

               requestSerialNumber is a serial number for the certificate request, unique for the manufacturer and the month below.

               requestMonthYear is the identification of the month and the year of the certificate request.

               Value assignment: BCD coding of Month (two digits) and Year (two last digits).

               crIdentifier: is an identifier to distinguish a certificate request from an extended serial number.

               Value assignment: ‘FFh’.

               manufacturerCode: is the numerical code of the manufacturer requesting the certificate.
            2.45.   CertificationAuthorityKID

            Identifier of the Public Key of a Certification Authority (a Member State or the European Certification Authority).

            Text of image

               CertificationAuthorityKID ::= SEQUENCE{
               nationNumeric NationNumeric,
               nationAlpha NationAlpha,
               keySerialNumber INTEGER(0..255),
               additionalInfo OCTET STRING(SIZE(2)),
               caIdentifier OCTET STRING(SIZE(1))
               }

               nationNumeric is the numerical nation code of the Certification Authority.

               nationAlpha is the alphanumerical nation code of the Certification Authority.

               keySerialNumber is a serial number to distinguish the different keys of the Certification Authority in the case keys are changed.

               additionalInfo is a two byte field for additional coding (Certification Authority specific).

               caIdentifier is an identifier to distinguish a Certification Authority Key Identifier from other Key Identifiers.

               Value assignment: ‘01h’.
            2.46.   CompanyActivityData

            Information, stored in a company card, related to activities performed with the card (Annex 1C requirement 373 and 379).

            Text of image

               CompanyActivityData ::= SEQUENCE {
               companyPointerNewestRecord INTEGER(0..NoOfCompanyActivityRecords-1),
               companyActivityRecords SET SIZE(NoOfCompanyActivityRecords) OF
               companyActivityRecord SEQUENCE {
               companyActivityType CompanyActivityType,
               companyActivityTime TimeReal,
               cardNumberInformation FullCardNumber,
               vehicleRegistrationInformation VehicleRegistrationIdentification,
               downloadPeriodBegin TimeReal,
               downloadPeriodEnd TimeReal
               }
               }

               companyPointerNewestRecord is the index of the last updated companyActivityRecord.

               Value assignment: Number corresponding to the numerator of the company activity record, beginning with ‘0’ for the first occurrence of the company activity record in the structure.

               companyActivityRecords is the set of all company activity records.

               companyActivityRecord is the sequence of information related to one company activity.

               companyActivityType is the type of the company activity.

               companyActivityTime is the date and time of the company activity.

               cardNumberInformation is the card number and the card issuing Member State of the card downloaded, if any.

               vehicleRegistrationInformation is the VRN and registering Member State of the vehicle downloaded or locked in or out.

               downloadPeriodBegin and downloadPeriodEnd is the period downloaded from the VU, if any.
            2.47.   CompanyActivityType

            Code indicating an activity carried out by a company using its company card.

            Text of image

               CompanyActivityType ::= INTEGER {
               card downloading (1),
               VU downloading (2),
               VU lock-in (3),
               VU lock-out (4)
               }

            2.48.   CompanyCardApplicationIdentification

            Information, stored in a company card related to the identification of the application of the card (Annex 1C requirement 369 and 375).

            Text of image

               CompanyCardApplicationIdentification ::= SEQUENCE {
               typeOfTachographCardId EquipmentType,
               cardStructureVersion CardStructureVersion,
               noOfCompanyActivityRecords NoOfCompanyActivityRecords
               }

               typeOfTachographCardId is specifying the implemented type of card.

               cardStructureVersion is specifying the the version of the structure that is implemented in the card.

               noOfCompanyActivityRecords is the number of company activity records the card can store.
            2.49.   CompanyCardHolderIdentification

            Information, stored in a company card, related to the cardholder identification (Annex 1C requirement 372 and 378).

            Text of image

               CompanyCardHolderIdentification ::= SEQUENCE {
               companyName Name,
               companyAddress Address,
               cardHolderPreferredLanguage Language
               }

               companyName is the name of the holder company.

               companyAddress is the address of the holder company.

               cardHolderPreferredLanguage is the preferred language of the card holder.
            2.50.   ControlCardApplicationIdentification

            Information, stored in a control card related to the identification of the application of the card (Annex 1C requirement 357 and 363).

            Text of image

               ControlCardApplicationIdentification ::= SEQUENCE {
               typeOfTachographCardId EquipmentType,
               cardStructureVersion CardStructureVersion,
               noOfControlActivityRecords NoOfControlActivityRecords
               }

               typeOfTachographCardId is specifying the implemented type of card.

               cardStructureVersion is specifying the version of the structure that is implemented in the card.

               noOfControlActivityRecords is the number of control activity records the card can store.
            2.51.   ControlCardControlActivityData

            Information, stored in a control card, related to control activity performed with the card (Annex 1C requirement 361 and 367).

            Text of image

               ControlCardControlActivityData ::= SEQUENCE {
               controlPointerNewestRecord INTEGER(0.. NoOfControlActivityRecords-1),
               controlActivityRecords SET SIZE(NoOfControlActivityRecords) OF
               controlActivityRecord SEQUENCE {
               controlType ControlType,
               controlTime TimeReal,
               controlledCardNumber FullCardNumber,
               controlledVehicleRegistration VehicleRegistrationIdentification,
               controlDownloadPeriodBegin TimeReal,
               controlDownloadPeriodEnd TimeReal
               }
               }

               controlPointerNewestRecord is the index of the last updated control activity record.

               Value assignment: Number corresponding to the numerator of the control activity record, beginning with ‘0’ for the first occurrence of the control activity record in the structure.

               controlActivityRecords is the set of all control activity records.

               controlActivityRecord is the sequence of information related to one control.

               controlType is the type of the control.

               controlTime is the date and time of the control.

               controlledCardNumber is the card number and the card issuing Member State of the card controlled.

               controlledVehicleRegistration is the VRN and registering Member State of the vehicle in which the control happened.

               controlDownloadPeriodBegin and controlDownloadPeriodEnd is the period eventually downloaded.
            2.52.   ControlCardHolderIdentification

            Information, stored in a control card, related to the identification of the cardholder (Annex 1C requirement 360 and 366).

            Text of image

               ControlCardHolderIdentification ::= SEQUENCE {
               controlBodyName Name,
               controlBodyAddress Address,
               cardHolderName HolderName,
               cardHolderPreferredLanguage Language
               }

               controlBodyName is the name of the control body of the card holder.

               controlBodyAddress is the address of the control body of the card holder.

               cardHolderName is the name and first name(s) of the holder of the Control Card.

               cardHolderPreferredLanguage is the preferred language of the card holder.
            2.53.   ControlType

            Code indicating the activities carried out during a control. This data type is related to Annex 1C requirements 126, 274, 299, 327, and 350.

            Text of image

               ControlType ::= OCTET STRING (SIZE(1))

                        Generation 1:

                           Value assignment — Octet aligned: ‘cvpdxxxx’B (8 bits)

                                    ‘c’B

                                    card downloading:

                                                ‘0’B: card not downloaded during this control activity,

                                                ‘1’B: card downloaded during this control activity

                                    ‘v’B

                                    VU downloading:

                                                ‘0’B: VU not downloaded during this control activity,

                                                ‘1’B: VU downloaded during this control activity

                                    ‘p’B

                                    printing:

                                                ‘0’B: no printing done during this control activity,

                                                ‘1’B: printing done during this control activity

                                    ‘d’B

                                    display:

                                                ‘0’B: no display used during this control activity,

                                                ‘1’B: display used during this control activity

                                    ‘xxxx’B

                                    Not used.

                        Generation 2:

                           Value assignment — Octet aligned: ‘cvpdexxx’B (8 bits)

                                    ‘c’B

                                    card downloading:

                                                ‘0’B: card not downloaded during this control activity,

                                                ‘1’B: card downloaded during this control activity

                                    ‘v’B

                                    VU downloading:

                                                ‘0’B: VU not downloaded during this control activity,

                                                ‘1’B: VU downloaded during this control activity

                                    ‘p’B

                                    printing:

                                                ‘0’B: no printing done during this control activity,

                                                ‘1’B: printing done during this control activity

                                    ‘d’B

                                    display:

                                                ‘0’B: no display used during this control activity,

                                                ‘1’B: display used during this control activity

                                    ‘e’B

                                    roadside calibration checking:

                                                ‘0’B: calibration parameters not checked during this control activity,

                                                ‘1’B: calibration parameters checked during this control activity

                                    ‘xxx’B

                                    RFU.

                  2.54.   CurrentDateTime

            The current date and time of the recording equipment.

            Text of image

               CurrentDateTime ::= TimeReal

               Value assignment: not further specified.
            2.55.   CurrentDateTimeRecordArray

            Generation 2:
            The current date and time plus metadata as used in the download protocol.

            Text of image

               CurrentDateTimeRecordArray ::= SEQUENCE {
               recordType RecordType,
               recordSize INTEGER(1..65535),
               noOfRecords INTEGER(0..65535),
               records SET SIZE(noOfRecords) OF CurrentDateTime
               }

               recordType denotes the type of the record (CurrentDateTime). Value Assignment: See RecordType

               recordSize is the size of the CurrentDateTime in bytes.

               noOfRecords is the number of records in the set records.

               records is a set of current date and time records.
            2.56.   DailyPresenceCounter

            Counter, stored in a driver or workshop card, increased by one for each calendar day the card has been inserted in a VU. This data type is related to Annex 1C requirements 266, 299, 320, and 343.

            Text of image

               DailyPresenceCounter ::= BCDString(SIZE(2))

               Value assignment: Consecutive Number with maximum value = 9 999, starting again with 0. At the time of first issuing of the card the number is set to 0.
            2.57.   Datef

            Date expressed in a readily printable numeric format.

            Text of image

               Datef ::= SEQUENCE {
               year BCDString(SIZE(2)),
               month BCDString(SIZE(1)),
               day BCDString(SIZE(1))
               }

            Value assignment:

                        yyyy

                        Year

                        mm

                        Month

                        dd

                        Day

                        ‘00000000’H

                        denotes explicitly no date.

                  2.58.   DateOfDayDownloaded

            Generation 2:
            The date and time of the download.

            Text of image

               DateOfDayDownloaded ::= TimeReal

               Value assignment: not further specified.
            2.59.   DateOfDayDownloadedRecordArray

            Generation 2:
            The date and time of the download plus metadata as used in the download protocol.

            Text of image

               DateofDayDownloadedRecordArray ::= SEQUENCE {
               recordType RecordType,
               recordSize INTEGER(1..65535),
               noOfRecords INTEGER(0..65535),
               records SET SIZE(noOfRecords) OF
               DateOfDayDownloaded
               }

               recordType denotes the type of the record (DateOfDayDownloaded). Value Assignment: See RecordType

               recordSize is the size of the CurrentDateTime in bytes.

               noOfRecords is the number of records in the set records.

               records is the set of date and time of the download records.
            2.60.   Distance

            A distance travelled (result of the calculation of the difference between two vehicle's odometer values in kilometers).

            Text of image

               Distance ::= INTEGER(0..216-1)

               Value assignment: Unsigned binary. Value in km in the operational range 0 to 9 999 km.
            2.61.   DriverCardApplicationIdentification

            Information, stored in a driver card related to the identification of the application of the card (Annex 1C requirement 253 and 278).

                        Generation 1:
                        Text of image

                           DriverCardApplicationIdentification ::= SEQUENCE {
                           typeOfTachographCardId EquipmentType,
                           cardStructureVersion CardStructureVersion,
                           noOfEventsPerType NoOfEventsPerType,
                           noOfFaultsPerType NoOfFaultsPerType,
                           activityStructureLength CardActivityLengthRange,
                           noOfCardVehicleRecords NoOfCardVehicleRecords,
                           noOfCardPlaceRecords NoOfCardPlaceRecords
                           }

                           typeOfTachographCardId is specifying the implemented type of card.

                           cardStructureVersion is specifying the the version of the structure that is implemented in the card.

                           noOfEventsPerType is the number of events per type of event the card can record.

                           noOfFaultsPerType is the number of faults per type of fault the card can record.

                           activityStructureLength indicates the number of bytes available for storing activity records.

                           noOfCardVehicleRecords is the number of vehicle records the card can contain.

                           noOfCardPlaceRecords is the number of places the card can record.

                        Generation 2:
                        Text of image

                           DriverCardApplicationIdentification ::= SEQUENCE {
                           typeOfTachographCardId EquipmentType,
                           cardStructureVersion CardStructureVersion,
                           noOfEventsPerType NoOfEventsPerType,
                           noOfFaultsPerType NoOfFaultsPerType,
                           activityStructureLength CardActivityLengthRange,
                           noOfCardVehicleRecords NoOfCardVehicleRecords,
                           noOfCardPlaceRecords NoOfCardPlaceRecords,
                           noOfGNSSCDRecords NoOfGNSSCDRecords,
                           noOfSpecificConditionRecords NoOfSpecificConditionRecords
                           }

                        In addition to generation 1 the following data elements are used:

                                       noOfGNSSCDRecords is the number of GNSS continuous driving records the card can store.

                                       noOfSpecificConditionRecords is the number of specific condition records the card can store.

                  2.62.   DriverCardHolderIdentification

            Information, stored in a driver card, related to the identification of the cardholder (Annex 1C requirement 256 and 281).

            Text of image

               DriverCardHolderIdentification ::= SEQUENCE {
               cardHolderName HolderName,
               cardHolderBirthDate Datef,
               cardHolderPreferredLanguage Language
               }

               cardHolderName is the name and first name(s) of the holder of the Driver Card.

               cardHolderBirthDate is the date of birth of the holder of the Driver Card.

               cardHolderPreferredLanguage is the preferred language of the card holder.
            2.63.   DSRCSecurityData

            Generation 2:
            The plain text information and the MAC to be transmitted via DSRC from the tachograph to the Remote Interrogator (RI), see Appendix 11 Part B chapter 13 for details.

            Text of image

               DSRCSecurityData ::= SEQUENCE {
               tagLenthPlainText OCTET STRING(SIZE(2)),
               currentDateTime CurrentDateTime,
               counter INTEGER(0..224-1),
               vuSerialNumber VuSerialNumber,
               dSRCMKVersionNumber INTEGER(SIZE(1)),
               tagLengthMac OCTET STRING(SIZE(2)),
               mac MAC
               }

               tagLength is part of the DER-TLV encoding and shall be set to ‘81 10’ (see Appendix 11 Part B chapter 13).

               currentDateTime is the current date and time of the vehicle unit.

               counter enumerates the RTM messages.

               vuSerialNumber is the serial number of the vehicle unit.

               dSRCMKVersionNumber is the version number of the DSRC Master Key from which the VU specific DSRC keys were derived.

               tagLengthMac is the tag and length of the MAC data object as part of the DER-TLV encoding. The tag shall be set to ‘8E’, the length shall encode the length of the MAC in octets (see Appendix 11 Part B chapter 13).

               mac is the MAC calculated over the RTM message (see Appendix 11 Part B chapter 13).
            2.64.   EGFCertificate

            Generation 2:
            Certificate of the external GNSS facility public key for mutual authentication with a VU. The structure of this certificate is specified in Appendix 11.

            Text of image

               EGFCertificate ::= Certificate

            2.65.   EmbedderIcAssemblerId

            Provides information about the IC embedder.

            Text of image

               EmbedderIcAssemblerId ::= SEQUENCE{
               countryCode IA5String(SIZE(2)),
               moduleEmbedder BCDString(SIZE(2)),
               manufacturerInformation OCTET STRING(SIZE(1))
               }

               countryCode is the 2 letter country code of the module embedder according to ISO 3166.

               moduleEmbedder identifies the module embedder.

               manufacturerInformation for manufacturer internal usage.
            2.66.   EntryTypeDailyWorkPeriod

            Code to distinguish between begin and end for an entry of a daily work period place and condition of the entry.

                        Generation 1
                        Text of image

                           EntryTypeDailyWorkPeriod ::= INTEGER {
                           Begin, related time = card insertion time or time of entry (0),
                           End, related time = card withdrawal time or time of entry (1),
                           Begin, related time manually entered (start time) (2),
                           End, related time manually entered (end of work period) (3),
                           Begin, related time assumed by VU (4),
                           End, related time assumed by VU (5)
                           }

                           Value assignment: according to ISO/IEC8824-1.

                        Generation 2
                        Text of image

                           EntryTypeDailyWorkPeriod ::= INTEGER {
                           Begin, related time = card insertion time or time of entry (0),
                           End, related time = card withdrawal time or time of entry (1),
                           Begin, related time manually entered (start time) (2),
                           End, related time manually entered (end of work period) (3),
                           Begin, related time assumed by VU (4),
                           End, related time assumed by VU (5),
                           Begin, related time based on GNSS data (6),
                           End related time based on GNSS data (7)
                           }

                           Value assignment: according to ISO/IEC8824-1.

                  2.67.   EquipmentType

            Code to distinguish different types of equipment for the tachograph application.

            Text of image

               EquipmentType ::= INTEGER(0..255)

                        Generation 1:
                        Text of image

                           --Reserved (0),
                           --Driver Card (1),
                           --Workshop Card (2),
                           --Control Card (3),
                           --Company Card (4),
                           --Manufacturing Card (5),
                           --Vehicle Unit (6),
                           --Motion Sensor (7),
                           --RFU (8..255)

                           Value assignment: According to ISO/IEC8824-1.
                        Value 0 is reserved for the purpose of designating a Member State or Europe in the CHA field of certificates.

                        Generation 2:
                        The same values as in generation 1 are used with the following additions:
                        Text of image

                           --GNSS Facility (8),
                           --Remote Communication Module (9),
                           --ITS interface module (10),
                           --Plaque (11), -- may be used in SealRecord
                           --M1/N1 Adapter (12), -- may be used in SealRecord
                           --European Root CA (ERCA) (13),
                           --Member State CA (MSCA) (14),
                           --External GNSS connection (15), -- may be used in SealRecord
                           --Unused (16), -- used in SealDataVu
                           --RFU (17..255)

                           Note: The generation 2 values for the Plaque, Adapter and the External GNSS connection as well as the generation 1 values for the Vehicle Unit and Motion Sensor may be used in SealRecord, i.e. if applicable.

                  2.68.   EuropeanPublicKey

            Generation 1:
            The European public key.

            Text of image

               EuropeanPublicKey ::= PublicKey

            2.69.   EventFaultRecordPurpose

            Code explaining why an event or a fault has been recorded.

            Text of image

               EventFaultRecordPurpose ::= OCTET STRING (SIZE(1))

               Value assignment:

                        one of the 10 most recent (or last) events or faults
                        the longest event for one of the last 10 days of occurrence
                        one of the 5 longest events over the last 365 days
                        the last event for one of the last 10 days of occurrence
                        the most serious event for one of the last 10 days of occurrence
                        one of the 5 most serious events over the last 365 days
                        the first event or fault having occurred after the last calibration
                        an active/on-going event or fault
                        RFU
                        manufacturer specific

                  2.70.   EventFaultType

            Code qualifying an event or a fault.

            Text of image

               EventFaultType ::= OCTET STRING (SIZE(1))

               Value assignment:

                        Generation 1:

                                    General events,
                                    No further details,
                                    Insertion of a non valid card,
                                    Card conflict,
                                    Time overlap,
                                    Driving without an appropriate card,
                                    Card insertion while driving,
                                    Last card session not correctly closed,
                                    Over speeding,
                                    Power supply interruption,
                                    Motion data error,
                                    Vehicle Motion Conflict,
                                    RFU,

                                    Vehicle unit related security breach attempt events,
                                    No further details,
                                    Motion sensor authentication failure,
                                    Tachograph card authentication failure,
                                    Unauthorised change of motion sensor,
                                    Card data input integrity error
                                    Stored user data integrity error,
                                    Internal data transfer error,
                                    Unauthorised case opening,
                                    Hardware sabotage,
                                    RFU,

                                    Sensor related security breach attempt events,
                                    No further details,
                                    Authentication failure,
                                    Stored data integrity error,
                                    Internal data transfer error,
                                    Unauthorised case opening,
                                    Hardware sabotage,
                                    RFU,

                                    Recording equipment faults,
                                    No further details,
                                    VU internal fault,
                                    Printer fault,
                                    Display fault,
                                    Downloading fault,
                                    Sensor fault,
                                    RFU,

                                    Card faults,
                                    No further details,
                                    RFU,

                                    RFU,

                                    Manufacturer specific.

                        Generation 2:
                        The same values as in generation 1 are used with the following additions:

                                    Time conflict (GNSS versus VU internal clock),
                                    RFU,

                                    GNSS related faults,
                                    No further details,
                                    Internal GNSS receiver fault,
                                    External GNSS receiver fault,
                                    External GNSS communication fault,
                                    No GNSS position data,
                                    Tamper detection of GNSS,
                                    External GNSS facility certificate expired,
                                    RFU,

                                    Remote Communication Module related faults,
                                    No further details,
                                    Remote Communication Module fault,
                                    Remote Communication Module communication fault,
                                    RFU,

                                    ITS interface faults,
                                    No further details,
                                    RFU.

                  2.71.   ExtendedSealIdentifier

            Generation 2:
            The extended seal identifier uniquely identifies a seal (Annex 1C requirement 401).

            Text of image

               ExtendedSealIdentifier ::= SEQUENCE{
               manufacturerCode OCTET STRING (SIZE(2)),
               sealIdentifier OCTET STRING (SIZE(6))
               }

               manufacturerCode is a code of the manufacturer of the seal.

               sealIdentifier is an identifier for the seal which is unique for the manufacturer.
            2.72.   ExtendedSerialNumber

            Unique identification of an equipment. It can also be used as an equipment Public Key Identifier.

                        Generation 1:
                        Text of image

                           ExtendedSerialNumber ::= SEQUENCE{
                           serialNumber INTEGER(0..232-1),
                           monthYear BCDString(SIZE(2)),
                           type OCTET STRING(SIZE(1)),
                           manufacturerCode ManufacturerCode
                           }

                           serialNumber is a serial number for the equipment, unique for the manufacturer, the equipment's type and the month and year below.

                           monthYear is the identification of the month and the year of manufacturing (or of serial number assignment).

                           Value assignment: BCD coding of Month (two digits) and Year (two last digits).

                           type is an identifier of the type of equipment.

                           Value assignment: manufacturer specific, with ‘FFh’ reserved value.

                           manufacturerCode: is the numerical code identifying a manufacturer of type approved equipment.

                        Generation 2:
                        Text of image

                           ExtendedSerialNumber ::= SEQUENCE{
                           serialNumber INTEGER(0..232-1),
                           monthYear BCDString(SIZE(2)),
                           type EquipmentType,
                           manufacturerCode ManufacturerCode
                           }

                           serialNumber see Generation 1

                           monthYear see Generation 1

                           type indicates the type of equipment

                           manufacturerCode: see Generation 1.

                  2.73.   FullCardNumber

            Code fully identifying a tachograph card.

            Text of image

               FullCardNumber ::= SEQUENCE {
               cardType EquipmentType,
               cardIssuingMemberState NationNumeric,
               cardNumber CardNumber
               }

               cardType is the type of the tachograph card.

               cardIssuingMemberState is the code of the Member State having issued the card.

               cardNumber is the card number.
            2.74.   FullCardNumberAndGeneration

            Generation 2:
            Code fully identifying a tachograph card and its generation.

            Text of image

               FullCardNumberAndGeneration ::= SEQUENCE {
               fullCardNumber FullCardNumber,
               generation Generation
               }

               fullcardNumber identifies the tachograph card.

               generation indicates the generation of the tachograph card used.
            2.75.   Generation

            Generation 2:
            Indicates the generation of tachograph used.

            Text of image

               Generation ::= INTEGER(0..255)

               Value assignment:

                        ‘00’H

                        RFU

                        ‘01’H

                        Generation 1

                        ‘02’H

                        Generation 2

                        ‘03’H .. ‘FF’H

                        RFU

                  2.76.   GeoCoordinates

            Generation 2:
            The geo-coordinates are encoded as integers. These integers are multiples of the ±DDMM.M encoding for the latitude and ±DDDMM.M for the longitude. Here ±DD respectively ±DDD denotes the degrees and MM.M the minutes.

            Text of image

               GeoCoordinates ::= SEQUENCE {
               latitude INTEGER(-90000..90001),
               longitude INTEGER(-180000..180001)
               }

               latitude is encoded as a multiple (factor 10) of the ±DDMM.M representation.

               longitude is encoded as a multiple (factor 10) of the ±DDDMM.M representation.
            2.77.   GNSSAccuracy

            Generation 2:
            The accuracy of the GNSS position data (definition eee)). This accuracy is encoded as integer and is a multiple (factor 10) of the X.Y value provided by the GSA NMEA sentence.

            Text of image

               GNSSAccuracy ::= INTEGER(1..100)

            2.78.   GNSSContinuousDriving

            Generation 2:
            Information, stored in a driver or workshop card, related to the GNSS position of the vehicle if the continuous driving time of the driver reaches a multiple of three hours (Annex 1C requirement 306 and 354).

            Text of image

               GNSSContinuousDriving := SEQUENCE {
               gnssCDPointerNewestRecord INTEGER(0..NoOfGNSSCDRecords -1),
               gnssContinuousDrivingRecords SET SIZE(NoOfGNSSCDRecords) OF GNSSContinuousDrivingRecord
               }

               gnssCDPointerNewestRecord is the index of the last updated GNSS continuous driving record.

               Value assignment: Number corresponding to the numerator of the GNSS continuous driving record, beginning with ‘0’ for the first occurrence of the GNSS continuous driving record in the structure.

               gnssContinuousDrivingRecords is the set of records containing the date and time the continuous driving reaches a multiple of three hours and information on the position of the vehicle.
            2.79.   GNSSContinuousDrivingRecord

            Generation 2:
            Information, stored in a driver or workshop card, related to the GNSS position of the vehicle if the continuous driving time of the driver reaches a multiple of three hours (Annex 1C requirement 305 and 353).

            Text of image

               GNSSContinuousDrivingRecord ::= SEQUENCE {
               timeStamp TimeReal,
               gnssPlaceRecord GNSSPlaceRecord
               }

               timeStamp is the date and time when the continuous driving time of the card holder reaches a multiple of three hours.

               gnssPlaceRecord contains information related to the position of the vehicle.
            2.80.   GNSSPlaceRecord

            Generation 2:
            Information related to the GNSS position of the vehicle (Annex 1C requirements 108, 109, 110, 296, 305, 347, and 353).

            Text of image

               GNSSPlaceRecord ::= SEQUENCE {
               timeStamp TimeReal,
               gnssAccuracy GNSSAccuracy,
               geoCoordinates GeoCoordinates
               }

               timeStamp is the date and time when the GNSS position of the vehicle was determined.

               gnssAccuracy is the accuracy of the GNSS position data.

               geoCoordinates is the recorded location using GNSS.
            2.81.   HighResOdometer

            Odometer value of the vehicle: Accumulated distance travelled by the vehicle during its operation.

            Text of image

               HighResOdometer ::= INTEGER(0..232-1)

               Value assignment: Unsigned binary. Value in 1/200 km in the operating range 0 to 21 055 406 km.
            2.82.   HighResTripDistance

            A distance travelled during all or part of a journey.

            Text of image

               HighResTripDistance ::= INTEGER(0..232-1)

               Value assignment: Unsigned binary. Value in 1/200 km in the operating range 0 to 21 055 406 km.
            2.83.   HolderName

            The surname and first name(s) of a card holder.

            Text of image

               HolderName ::= SEQUENCE {
               holderSurname Name,
               holderFirstNames Name
               }

               holderSurname is the surname (family name) of the holder. This surname does not include titles.

               Value assignment: When a card is not personal, holderSurname contains the same information as companyName or workshopName or controlBodyName.

               holderFirstNames is the first name(s) and initials of the holder.
            2.84.   InternalGNSSReceiver

            Generation 2:
            Information if the GNSS receiver is internal or external to the vehicle unit. True means that the GNSS receiver is internal to the VU. False means that the GNSS receiver is external.

            Text of image

               InternalGNSSReceiver ::= BOOLEAN

            2.85.   K-ConstantOfRecordingEquipment

            Constant of the recording equipment (definition m)).

            Text of image

               K-ConstantOfRecordingEquipment ::= INTEGER(0..216-1)

               Value assignment: Pulses per kilometer in the operating range 0 to 64 255 pulses/km.
            2.86.   KeyIdentifier

            A unique identifier of a Public Key used to reference and select the key. It also identifies the holder of the key.

            Text of image

               KeyIdentifier ::= CHOICE {
               extendedSerialNumber ExtendedSerialNumber,
               certificateRequestID CertificateRequestID,
               certificationAuthorityKID CertificationAuthorityKID
               }

            The first choice is suitable to reference the public key of a Vehicle Unit or of a tachograph card.
            The second choice is suitable to reference the public key of a Vehicle Unit (in the case the serial number of the Vehicle Unit cannot be known at certificate generation time).
            The third choice is suitable to reference the public key of a Member State.
            2.87.   KMWCKey

            Generation 2:
            AES key and its associated key version used for VU — Motion Sensor pairing. For details see Appendix 11.

            Text of image

               KMWCKey ::= SEQUENCE {
               kMWCKey AESKey,
               keyVersion INTEGER (SIZE(1))
               }

               kMWCKey is the length of the AES key concatenated with the key which is used for VU — Motion Sensor pairing.

               keyVersion denotes the key version of the AES key.
            2.88.   Language

            Code identifying a language.

            Text of image

               Language ::= IA5String(SIZE(2))

               Value assignment: Two-letter lower-case coding according to ISO 639.
            2.89.   LastCardDownload

            Date and time, stored on a driver card, of last card download (for other purposes than control) Annex 1C requirement 257 and 282. This date is updateable by a VU or any card reader.

            Text of image

               LastCardDownload ::= TimeReal

               Value assignment: not further specified.
            2.90.   LinkCertificate

            Generation 2:
            The link certificate between European Root CA key pairs.

            Text of image

               LinkCertificate ::= Certificate

            2.91.   L-TyreCircumference

            Effective circumference of the wheel tyres (definition u)).

            Text of image

               L-TyreCircumference ::= INTEGER(0.. 216-1)

               Value assignment: Unsigned binary, value in 1/8 mm in the operating range 0 to 8 031 mm.
            2.92.   MAC

            Generation 2:
            A cryptographic checksum of 8, 12 or 16 bytes length corresponding to the cipher suites specified in Appendix 11.

            Text of image

               MAC ::= CHOICE {
               mac8 OCTET STRING (SIZE(8)),
               mac12 OCTET STRING (SIZE(12)),
               mac16 OCTET STRING (SIZE(12))
               }

            2.93.   ManualInputFlag

            Code identifying whether a cardholder has manually entered driver activities at card insertion or not (Annex 1B requirement 081 and Annex 1C requirement 102).

            Text of image

               ManualInputFlag ::= INTEGER {
               noEntry (0)
               manualEntries (1)
               }

               Value assignment: not further specified.
            2.94.   ManufacturerCode

            Code identifying a manufacturer of type approved equipment.

            Text of image

               ManufacturerCode ::= INTEGER(0..255)

            The laboratory competent for interoperability tests maintains and publishes the list of manufacturer codes on its web site (Annex 1C requirement 454).
            ManufacturerCodes are provisionally assigned to developers of tachograph equipment on application to the laboratory competent for interoperability tests.
            2.95.   ManufacturerSpecificEventFaultData

            Generation 2:
            Manufacturer specific error codes simplify the error analysis and maintenance of vehicle units.

            Text of image

               ManufacturerSpecificEventFaultData ::= SEQUENCE {
               manufacturerCode ManufacturerCode,
               manufacturerSpecificErrorCode OCTET STRING(SIZE(3))
               }

               manufacturerCode identifies the manufacturer of the Vehicle Unit.

               manufacturerSpecificErrorCode is an error code specific to the manufacturer.
            2.96.   MemberStateCertificate

            The certificate of the public key of a member state issued by the European certification authority.

            Text of image

               MemberStateCertificate ::= Certificate

            2.97.   MemberStateCertificateRecordArray

            Generation 2:
            The member state certificate plus metadata as used in the download protocol.

            Text of image

               MemberStateCertificateRecordArray ::= SEQUENCE {
               recordType RecordType,
               recordSize INTEGER(1..65535),
               noOfRecords INTEGER(0..65535),
               records SET SIZE(noOfRecords) OF
               MemberStateCertificate
               }

               recordType denotes the type of the record (MemberStateCertificate). Value Assignment: See RecordType

               recordSize is the size of the MemberStateCertificate in bytes.

               noOfRecords is the number of records in the set records. The value shall be set to 1 as the certficates may have different lengths.

               records is the set of member state certificates.
            2.98.   MemberStatePublicKey

            Generation 1:
            The public key of a Member State.

            Text of image

               MemberStatePublicKey ::= PublicKey

            2.99.   Name

            A name.

            Text of image

               Name ::= SEQUENCE {
               codePage INTEGER (0..255),
               name OCTET STRING (SIZE(35))
               }

               codePage specifies a character set defined in Chapter 4,

               name is a name encoded using the specified character set.
            2.100.   NationAlpha

            Alphabetic reference to a country shall be in accordance with the distinguishing signs used on vehicles in international traffic (United Nations Vienna Convention on Road Traffic, 1968).

            Text of image

               NationAlpha ::= IA5String(SIZE(3))

            The Nation Alpha and Numeric codes shall be held on a list maintained on the website of the laboratory appointed to carry out interoperability testing, as set out in Annex 1C requirement 440.
            2.101.   NationNumeric

            Numerical reference to a country.

            Text of image

               NationNumeric ::= INTEGER(0 .. 255)

               Value assignment: see data type 2.100 (NationAlpha).
            Any amendment or updating of the Nation Alpha or Numeric specification described in the above paragraph shall only be made out after the appointed laboratory has obtained the views of type approved digital and smart tachograph vehicle unit manufacturers.
            2.102.   NoOfCalibrationRecords

            Number of calibration records, a workshop card can store.

                        Generation 1:
                        Text of image

                           NoOfCalibrationRecords ::= INTEGER(0..255)

                           Value assignment: see Appendix 2.

                        Generation 2:
                        Text of image

                           NoOfCalibrationRecords ::= INTEGER(0..216-1)

                           Value assignment: see Appendix 2.

                  2.103.   NoOfCalibrationsSinceDownload

            Counter indicating the number of calibrations performed with a workshop card since its last download (Annex 1C requirement 317 and 340).

            Text of image

               NoOfCalibrationsSinceDownload ::= INTEGER(0..216-1)

               Value assignment: Not specified further.
            2.104.   NoOfCardPlaceRecords

            Number of place records a driver or workshop card can store.

                        Generation 1:
                        Text of image

                           NoOfCardPlaceRecords ::= INTEGER(0..255)

                           Value assignment: see Appendix 2.

                        Generation 2:
                        Text of image

                           NoOfCardPlaceRecords ::= INTEGER(0..216-1)

                           Value assignment: see Appendix 2.

                  2.105.   NoOfCardVehicleRecords

            Number of vehicles used records a driver or workshop card can store.

            Text of image

               NoOfCardVehicleRecords ::= INTEGER(0.. 216-1)

               Value assignment: see Appendix 2.
            2.106.   NoOfCardVehicleUnitRecords

            Generation 2:
            Number of vehicle units used records a driver or workshop card can store.

            Text of image

               NoOfCardVehicleUnitRecords ::= INTEGER(0.. 216-1)

               Value assignment: see Appendix 2.
            2.107.   NoOfCompanyActivityRecords

            Number of company activity records, a company card can store.

            Text of image

               NoOfCompanyActivityRecords ::= INTEGER(0.. 216-1)

               Value assignment: see Appendix 2.
            2.108.   NoOfControlActivityRecords

            Number of control activity records, a control card can store.

            Text of image

               NoOfControlActivityRecords ::= INTEGER(0.. 216-1)

               Value assignment: see Appendix 2.
            2.109.   NoOfEventsPerType

            Number of events per type of event a card can store.

            Text of image

               NoOfEventsPerType ::= INTEGER(0..255)

               Value assignment: see Appendix 2.
            2.110.   NoOfFaultsPerType

            Number of faults per type of fault a card can store.

            Text of image

               NoOfFaultsPerType ::= INTEGER(0..255)

               Value assignment: see Appendix 2.
            2.111.   NoOfGNSSCDRecords

            Generation 2:
            Number of GNSS continuous driving records a card can store.

            Text of image

               NoOfGNSSCDRecords ::= INTEGER(0..216-1)

               Value assignment: see Appendix 2.
            2.112.   NoOfSpecificConditionRecords

            Generation 2:
            Number of specific condition records a card can store.

            Text of image

               NoOfSpecificConditionRecords ::= INTEGER(0..216-1)

               Value assignment: see Appendix 2.
            2.113.   OdometerShort

            Odometer value of the vehicle in a short form.

            Text of image

               OdometerShort ::= INTEGER(0..224-1)

               Value assignment: Unsigned binary. Value in km in the operating range 0 to 9 999 999 km.
            2.114.   OdometerValueMidnight

            The vehicle's odometer value at midnight on a given day (Annex 1B requirement 090 and Annex 1C requirement 113).

            Text of image

               OdometerValueMidnight ::= OdometerShort

               Value assignment: not further specified.
            2.115.   OdometerValueMidnightRecordArray

            Generation 2:
            The OdometerValueMidnight plus metadata used in the download protocol.

            Text of image

               OdometerValueMidnightRecordArray ::= SEQUENCE {
               recordType RecordType,
               recordSize INTEGER(1..65535),
               noOfRecords INTEGER(0..65535),
               records SET SIZE(noOfRecords) OF
               OdometerValueMidnight
               }

               recordType denotes the type of the record (OdometerValueMidnight). Value Assignment: See RecordType

               recordSize is the size of the OdometerValueMidnight in bytes.

               noOfRecords is the number of records in the set records.

               records is the set of OdometerValueMidnight records.
            2.116.   OverspeedNumber

            Number of over speeding events since the last over speeding control.

            Text of image

               OverspeedNumber ::= INTEGER(0..255)

               Value assignment: 0 means that no over speeding event has occurred since the last over speeding control, 1 means that one over speeding event has occurred since the last over speeding control …255 means that 255 or more over speeding events have occurred since the last over speeding control.
            2.117.   PlaceRecord

            Information related to a place where a daily work period begins or ends (Annex 1C requirements 108, 271, 296, 324, and 347).

                        Generation 1:
                        Text of image

                           PlaceRecord ::= SEQUENCE {
                           entryTime TimeReal,
                           entryTypeDailyWorkPeriod EntryTypeDailyWorkPeriod,
                           dailyWorkPeriodCountry NationNumeric,
                           dailyWorkPeriodRegion RegionNumeric,
                           vehicleOdometerValue OdometerShort
                           }

                           entryTime is a date and time related to the entry.

                           entryTypeDailyWorkPeriod is the type of entry.

                           dailyWorkPeriodCountry is the country entered.

                           dailyWorkPeriodRegion is the region entered.

                           vehicleOdometerValue is the odometer value at the time of place entry.

                        Generation 2:
                        Text of image

                           PlaceRecord ::= SEQUENCE {
                           entryTime TimeReal,
                           entryTypeDailyWorkPeriod EntryTypeDailyWorkPeriod,
                           dailyWorkPeriodCountry NationNumeric,
                           dailyWorkPeriodRegion RegionNumeric,
                           vehicleOdometerValue OdometerShort,
                           entryGNSSPlaceRecord GNSSPlaceRecord
                           }

                        In addition to Generation 1 the following component is used:

                           entryGNSSPlaceRecord is the recorded location and time.

                  2.118.   PreviousVehicleInfo

            Information related to the vehicle previously used by a driver when inserting his card in a vehicle unit (Annex 1B requirement 081 and Annex 1C requirement 102).

                        Generation 1:
                        Text of image

                           PreviousVehicleInfo ::= SEQUENCE {
                           vehicleRegistrationIdentification VehicleRegistrationIdentification,
                           cardWithdrawalTime TimeReal
                           }

                           vehicleRegistrationIdentification is the VRN and the registering Member State of the vehicle.

                           cardWithdrawalTime is the card withdrawal date and time.

                        Generation 2:
                        Text of image

                           PreviousVehicleInfo ::= SEQUENCE {
                           vehicleRegistrationIdentification VehicleRegistrationIdentification,
                           cardWithdrawalTime TimeReal,
                           vuGeneration Generation
                           }

                        In addition to generation 1 the following data element is used:

                           vuGeneration identifies the generation of the vehicle unit.

                  2.119.   PublicKey

            Generation 1:
            A public RSA key.

            Text of image

               PublicKey ::= SEQUENCE {
               rsaKeyModulus RSAKeyModulus,
               rsaKeyPublicExponent RSAKeyPublicExponent
               }

               rsaKeyModulus is the Modulus of the key pair.

               rsaKeyPublicExponent is the public exponent of the key pair.
            2.120.   RecordType

            Generation 2:
            Reference to a record type. This data type is used in RecordArrays.

            Text of image

               RecordType ::= OCTET STRING(SIZE(1))

               Value assignment:

                        ActivityChangeInfo,
                        CardSlotsStatus,
                        CurrentDateTime,
                        MemberStateCertificate,
                        OdometerValueMidnight,
                        DateOfDayDownloaded,
                        SensorPaired,
                        Signature,
                        SpecificConditionRecord,
                        VehicleIdentificationNumber,
                        VehicleRegistrationNumber,
                        VuCalibrationRecord,
                        VuCardIWRecord,
                        VuCardRecord,
                        VuCertificate,
                        VuCompanyLocksRecord,
                        VuControlActivityRecord,
                        VuDetailedSpeedBlock,
                        VuDownloadablePeriod,
                        VuDownloadActivityData,
                        VuEventRecord,
                        VuGNSSCDRecord,
                        VuITSConsentRecord,
                        VuFaultRecord,
                        VuIdentification,
                        VuOverSpeedingControlData,
                        VuOverSpeedingEventRecord,
                        VuPlaceDailyWorkPeriodRecord,
                        VuTimeAdjustmentGNSSRecord,
                        VuTimeAdjustmentRecord,
                        VuPowerSupplyInterruptionRecord,
                        SensorPairedRecord,
                        SensorExternalGNSSCoupledRecord,
                        RFU,
                        Manufacturer specific.

                  2.121.   RegionAlpha

            Alphabetic reference to a region within a specified country.

            Text of image

               RegionAlpha ::= IA5STRING(SIZE(3))

                        Generation 1:

                           Value assignment:

                        Text of image

                           ‘ ’ No information available,
                           Spain:
                           ‘AN ’ Andalucía,
                           ‘AR ’ Aragón,
                           ‘AST’ Asturias,
                           ‘C ’ Cantabria,
                           ‘CAT’ Cataluña,
                           ‘CL ’ Castilla-León,
                           ‘CM ’ Castilla-La-Mancha,
                           ‘CV’ Valencia,
                           ‘EXT’ Extremadura,
                           ‘G ’ Galicia,
                           ‘IB ’ Baleares,
                           ‘IC ’ Canarias,
                           ‘LR ’ La Rioja,
                           ‘M ’ Madrid,
                           ‘MU ’ Murcia,
                           ‘NA ’ Navarra,
                           ‘PV ’ País Vasco

                        Generation 2:
                        The RegionAlpha codes shall be held on a list maintained on the website of the laboratory appointed to carry out interoperability testing.

                  2.122.   RegionNumeric

            Numerical reference to a region within a specified country.

            Text of image

               RegionNumeric ::= OCTET STRING (SIZE(1))

                        Generation 1:

                           Value assignment:

                        Text of image

                           ‘00’H No information available,
                           Spain:
                           ‘01’H Andalucía,
                           ‘02’H Aragón,
                           ‘03’H Asturias,
                           ‘04’H Cantabria,
                           ‘05’H Cataluña,
                           ‘06’H Castilla-León,
                           ‘07’H Castilla-La-Mancha,
                           ‘08’H Valencia,
                           ‘09’H Extremadura,
                           ‘0A’H Galicia,
                           ‘0B’H Baleares,
                           ‘0C’H Canarias,
                           ‘0D’H La Rioja,
                           ‘0E’H Madrid,
                           ‘0F’H Murcia,
                           ‘10’H Navarra,
                           ‘11’H País Vasco

                        Generation 2:
                        The RegionNumeric codes shall be held on a list maintained on the website of the laboratory appointed to carry out interoperability testing.

                  2.123.   RemoteCommunicationModuleSerialNumber

            Generation 2:
            Serial number of the Remote Communication Module.

            Text of image

               RemoteCommunicationModuleSerialNumber ::= ExtendedSerialNumber

            2.124.   RSAKeyModulus

            Generation 1:
            The modulus of a RSA key pair.

            Text of image

               RSAKeyModulus ::= OCTET STRING (SIZE(128))

               Value assignment: Unspecified.
            2.125.   RSAKeyPrivateExponent

            Generation 1:
            The private exponent of a RSA key pair.

            Text of image

               RSAKeyPrivateExponent ::= OCTET STRING (SIZE(128))

               Value assignment: Unspecified.
            2.126.   RSAKeyPublicExponent

            Generation1:
            The public exponent of a RSA key pair.

            Text of image

               RSAKeyPublicExponent ::= OCTET STRING (SIZE(8))

               Value assignment: Unspecified.
            2.127.   RtmData

            Generation2:
            For the definition of this data type see Appendix 14.
            2.128.   SealDataCard

            Generation 2:
            This data type stores information about the seals that are attached to the different components of a vehicle and is intended for storage on a card. This data type is related to Annex 1C requirement 337.

            Text of image

               SealDataCard ::= SEQUENCE {
               noOfSealRecords INTEGER(1..5),
               sealRecords SET SIZE(noOfSealRecords) OF SealRecord
               }

               noOfSealRecords is the number of records in sealRecords.

               sealRecords is a set of seal records.
            2.129.   SealDataVu

            Generation 2:
            This data type stores information about the seals that are attached to the different components of a vehicle and is intended for storage in a Vehicle Unit.

            Text of image

               SealDataVu ::= SEQUENCE SIZE(5) OF {
               sealRecords SealRecord
               }

               sealRecords is a set of seal records. If there are less than 5 seals available the value of the EquipmentType in all unused sealRecords shall be set to 16, i.e. unused.
            2.130.   SealRecord

            Generation 2:
            This data type stores information about a seal that is attached to a component. This data type is related to Annex 1C requirement 337.

            Text of image

               SealRecord ::= SEQUENCE {
               equipmentType EquipmentType,
               extendedSealIdentifier ExtendedSealIdentifier
               }

               equipmentType identifies the type of equipment the seal is attached to.

               extendedSealIdentifier is the identifier of the seal attached to the equipment.
            2.131.   SensorApprovalNumber

            Type approval number of the sensor.

                        Generation 1:
                        Text of image

                           SensorApprovalNumber ::= IA5String(SIZE(8))

                           Value assignment: Unspecified.

                        Generation 2:
                        Text of image

                           SensorApprovalNumber ::= IA5String(SIZE(16))

                           Value assignment:

                        The approval number shall be provided as published on the corresponding European Commission web site, i.e. for example including hyphens if any. The approval number shall be left-aligned.

                  2.132.   SensorExternalGNSSApprovalNumber

            Generation 2:
            Type approval number of the external GNSS facility.

            Text of image

               SensorExternalGNSSApprovalNumber ::= IA5String(SIZE(16))

               Value assignment:

            The approval number shall be provided as published on the corresponding European Commission web site, i.e. for example including hyphens if any. The approval number shall be left-aligned.
            2.133.   SensorExternalGNSSCoupledRecord

            Generation 2:
            Information, stored in a vehicle unit, related to the identification of the external GNSS facility coupled with the vehicle unit (Annex 1C requirement 100).

            Text of image

               SensorExternalGNSSCoupledRecord ::= SEQUENCE {
               sensorSerialNumber SensorGNSSSerialNumber,
               sensorApprovalNumber SensorExternalGNSSApprovalNumber,
               sensorCouplingDate SensorGNSSCouplingDate
               }

               sensorSerialNumber is the serial number of the external GNSS facility coupled with the vehicle unit.

               sensorApprovalNumber is the approval number of this external GNSS facility.

               sensorCouplingDate is a date of coupling of this external GNSS facility with the vehicle unit.
            2.134.   SensorExternalGNSSIdentification

            Generation 2:
            Information related to the identification of the external GNSS facility (Annex 1C requirement 98).

            Text of image

               SensorExternalGNSSIdentification ::= SEQUENCE {
               sensorSerialNumber SensorGNSSSerialNumber,
               sensorApprovalNumber SensorExternalGNSSApprovalNumber,
               sensorSCIdentifier SensorExternalGNSSSCIdentifier,
               sensorOSIdentifier SensorExternalGNSSOSIdentifier
               }

               sensorSerialNumber is the extended serial number of the external GNSS facility.

               sensorApprovalNumber is the approval number of the external GNSS facility.

               sensorSCIdentifier is the identifier of the security component of the external GNSS facility.

               sensorOSIdentifier is the identifier of the operating system of the external GNSS facility.
            2.135.   SensorExternalGNSSInstallation

            Generation 2:
            Information, stored in an external GNSS facility, related to the installation of the external GNSS sensor (Annex 1C requirement 123).

            Text of image

               SensorExternalGNSSInstallation ::= SEQUENCE {
               sensorCouplingDateFirst SensorGNSSCouplingDate,
               firstVuApprovalNumber VuApprovalNumber,
               firstVuSerialNumber VuSerialNumber,
               sensorCouplingDateCurrent SensorGNSSCouplingDate,
               currentVuApprovalNumber VuApprovalNumber,
               currentVUSerialNumber VuSerialNumber
               }

               sensorCouplingDateFirst is the date of the first coupling of external GNSS facility with a vehicle unit.

               firstVuApprovalNumber is the approval number of the first vehicle unit coupled with the external GNSS facility.

               firstVuSerialNumber is the serial number of the first vehicle unit paired with the external GNSS facility.

               sensorCouplingDateCurrent is the date of the current coupling of external GNSS facility with a vehicle unit.

               currentVuApprovalNumber is the approval number of the vehicle unit currently coupled with the external GNSS facility.

               currentVUSerialNumber is the serial number of the vehicle unit currently coupled with the external GNSS facility.
            2.136.   SensorExternalGNSSOSIdentifier

            Generation 2:
            Identifier of the operating system of the external GNSS facility.

            Text of image

               SensorOSIdentifier ::= IA5String(SIZE(2))

               Value assignment: manufacturer specific.
            2.137.   SensorExternalGNSSSCIdentifier

            Generation 2:
            This type is used e.g. to identify the cryptographic module of the external GNSS facility.
            Identifier of the security component of the external GNSS facility.

            Text of image

               SensorExternalGNSSSCIdentifier ::= IA5String(SIZE(8))

               Value assignment: component manufacturer specific.
            2.138.   SensorGNSSCouplingDate

            Generation 2:
            Date of a coupling of the external GNSS facility with a vehicle unit.

            Text of image

               SensorGNSSCouplingDate ::= TimeReal

               Value assignment: Unspecified.
            2.139.   SensorGNSSSerialNumber

            Generation 2:
            This type is used to store the serial number of the GNSS receiver both when it is inside the VU and when it is outside the VU.
            Serial number of the GNSS receiver.

            Text of image

               SensorGNSSSerialNumber ::= ExtendedSerialNumber

            2.140.   SensorIdentification

            Information, stored in a motion sensor, related to the identification of the motion sensor (Annex 1B requirement 077 and Annex 1C requirement 95).

            Text of image

               SensorIdentification ::= SEQUENCE {
               sensorSerialNumber SensorSerialNumber,
               sensorApprovalNumber SensorApprovalNumber,
               sensorSCIdentifier SensorSCIdentifier,
               sensorOSIdentifier SensorOSIdentifier
               }

               sensorSerialNumber is the extended serial number of the motion sensor (includes part number and manufacturer code).

               sensorApprovalNumber is the approval number of the motion sensor.

               sensorSCIdentifier is the identifier of the security component of the motion sensor.

               sensorOSIdentifier is the identifier of the operating system of the motion sensor.
            2.141.   SensorInstallation

            Information, stored in a motion sensor, related to the installation of the motion sensor (Annex 1B requirement 099 and Annex 1C requirement 122).

            Text of image

               SensorInstallation ::= SEQUENCE {
               sensorPairingDateFirst SensorPairingDate,
               firstVuApprovalNumber VuApprovalNumber,
               firstVuSerialNumber VuSerialNumber,
               sensorPairingDateCurrent SensorPairingDate,
               currentVuApprovalNumber VuApprovalNumber,
               currentVUSerialNumber VuSerialNumber
               }

               sensorPairingDateFirst is the date of the first pairing of the motion sensor with a vehicle unit.

               firstVuApprovalNumber is the approval number of the first vehicle unit paired with the motion sensor.

               firstVuSerialNumber is the serial number of the first vehicle unit paired with the motion sensor.

               sensorPairingDateCurrent is the date of the current pairing of the motion sensor with the vehicle unit.

               currentVuApprovalNumber is the approval number of the vehicle unit currently paired with the motion sensor.

               currentVUSerialNumber is the serial number of the vehicle unit currently paired with the motion sensor.
            2.142.   SensorInstallationSecData

            Information, stored in a workshop card, related to the security data needed for pairing motion sensors to vehicle units (Annex 1C requirement 308 and 331).

                        Generation 1:
                        Text of image

                           SensorInstallationSecData ::= TdesSessionKey

                           Value assignment: in accordance with ISO 16844-3.

                        Generation 2:
                        As described in Appendix 11 a workshop card shall store up to three keys for VU Motion Sensor pairing. These keys have different key versions.
                        Text of image

                           SensorInstallationSecData ::= SEQUENCE {
                           kMWCKey1 KMWCKey,
                           kMWCKey2 KMWCKey OPTIONAL,
                           kMWCKey3 KMWCKey OPTIONAL
                           }

                  2.143.   SensorOSIdentifier

            Identifier of the operating system of the motion sensor.

            Text of image

               SensorOSIdentifier ::= IA5String(SIZE(2))

               Value assignment: manufacturer specific.
            2.144.   SensorPaired

            Generation 1:
            Information, stored in a vehicle unit, related to the identification of the motion sensor paired with the vehicle unit (Annex 1B requirement 079).

            Text of image

               SensorPaired ::= SEQUENCE {
               sensorSerialNumber SensorSerialNumber,
               sensorApprovalNumber SensorApprovalNumber,
               sensorPairingDateFirst SensorPairingDate
               }

               sensorSerialNumber is the serial number of the motion sensor currently paired with the vehicle unit.

               sensorApprovalNumber is the approval number of the motion sensor currently paired with the vehicle unit.

               sensorPairingDateFirst is the date of the first pairing with a vehicle unit of the motion sensor currently paired with the vehicle unit.
            2.145.   SensorPairedRecord

            Generation 2:
            Information, stored in a vehicle unit, related to the identification of a motion sensor paired with the vehicle unit (Annex 1C requirement 97).

            Text of image

               SensorPairedRecord ::= SEQUENCE {
               sensorSerialNumber SensorSerialNumber,
               sensorApprovalNumber SensorApprovalNumber,
               sensorPairingDate SensorPairingDate
               }

               sensorSerialNumber is the serial number of a motion sensor paired with the vehicle unit.

               sensorApprovalNumber is the approval number of this motion sensor.

               sensorPairingDate is a date of pairing of this motion sensor with the vehicle unit.
            2.146.   SensorPairingDate

            Date of a pairing of the motion sensor with a vehicle unit.

            Text of image

               SensorPairingDate ::= TimeReal

               Value assignment: Unspecified.
            2.147.   SensorSCIdentifier

            Identifier of the security component of the motion sensor.

            Text of image

               SensorSCIdentifier ::= IA5String(SIZE(8))

               Value assignment: component manufacturer specific.
            2.148.   SensorSerialNumber

            Serial number of the motion sensor.

            Text of image

               SensorSerialNumber ::= ExtendedSerialNumber

            2.149.   Signature

            A digital signature.

                        Generation 1:
                        Text of image

                           Signature ::= OCTET STRING (SIZE(128))

                           Value assignment: in accordance with Appendix 11 Common security mechanisms.

                        Generation 2:
                        Text of image

                           Signature ::= OCTET STRING (SIZE(64..132))

                           Value assignment: in accordance with Appendix 11 Common security mechanisms.

                  2.150.   SignatureRecordArray

            Generation 2:
            A set of signatures plus metadata used in the download protocol.

            Text of image

               SignatureRecordArray ::= SEQUENCE {
               recordType RecordType,
               recordSize INTEGER(1..65535),
               noOfRecords INTEGER(0..65535),
               records SET SIZE(noOfRecords) OF Signature
               }

               recordType denotes the type of the record (Signature). Value Assignment: See RecordType

               recordSize is the size of the Signature in bytes.

               noOfRecords is the number of records in the set records. The value shall be set to 1 as the signatures may have different lengths.

               records is the set of signatures.
            2.151.   SimilarEventsNumber

            The number of similar events for one given day (Annex 1B requirement 094 and Annex 1C requirement 117).

            Text of image

               SimilarEventsNumber ::= INTEGER(0..255)

               Value assignment: 0 is not used, 1 means that only one event of that type has occurred and has been stored on that day, 2 means that 2 events of that type has occurred on that day (one only has been stored), …255 means that 255 or more events of that type have occurred on that day.
            2.152.   SpecificConditionRecord

            Information, stored in a driver card, a workshop card or a vehicle unit, related to a specific condition (requirements Annex 1C 130, 276, 301, 328, and 355).

            Text of image

               SpecificConditionRecord ::= SEQUENCE {
               entryTime TimeReal,
               specificConditionType SpecificConditionType
               }

               entryTime is the date and time of the entry.

               specificConditionType is the code identifying the specific condition.
            2.153.   SpecificConditions

            Information, stored in a driver card, a workshop card or a vehicle unit, related to a specific condition (Annex 1C requirement 131, 277, 302, 329, and 356).
            Generation 2:

            Text of image

               SpecificConditions := SEQUENCE {
               conditionPointerNewestRecord INTEGER(0..NoOfSpecificConditionRecords-1),
               specificConditionRecords SET SIZE(NoOfSpecificConditionRecords) OF SpecificConditionRecord
               }

               conditionPointerNewestRecord is the index of the last updated specific condition record.

               Value assignment: Number corresponding to the numerator of the specific condition record, beginning with ‘0’ for the first occurrence of the specific condition record in the structure.

               specificConditionRecords is the set of records containing information on the specific conditions recorded.
            2.154.   SpecificConditionType

            Code identifying a specific condition (Annex 1B requirements 050b, 105a, 212a and 230a and Annex 1C requirements 62).

            Text of image

               SpecificConditionType ::= INTEGER(0..255)

                        Generation 1:

                           Value assignment:

                                    ‘00’H

                                    RFU

                                    ‘01’H

                                    Out of scope — Begin

                                    ‘02’H

                                    Out of scope — End

                                    ‘03’H

                                    Ferry / Train crossing

                                    ‘04’H .. ‘FF’H

                                    RFU

                        Generation 2:

                           Value assignment:

                                    ‘00’H

                                    RFU

                                    ‘01’H

                                    Out of scope — Begin

                                    ‘02’H

                                    Out of scope — End

                                    ‘03’H

                                    Ferry / Train crossing — Begin

                                    ‘04’H

                                    Ferry / Train crossing — End

                                    ‘05’H .. ‘FF’H

                                    RFU

                  2.155.   Speed

            Speed of the vehicle (km/h).

            Text of image

               Speed ::= INTEGER(0..255)

               Value assignment: kilometers per hour in the operational range 0 to 220 km/h.
            2.156.   SpeedAuthorised

            Maximum authorised Speed of the vehicle (definition hh)).

            Text of image

               SpeedAuthorised ::= Speed

            2.157.   SpeedAverage

            Average speed in a previously defined duration (km/h).

            Text of image

               SpeedAverage ::= Speed

            2.158.   SpeedMax

            Maximum speed measured in a previously defined duration.

            Text of image

               SpeedMax ::= Speed

            2.159.   TachographPayload

            Generation 2:
            For the definition of this data type see Appendix 14.
            2.160.   TachographPayloadEncrypted

            Generation 2:
            The DER-TLV encrypted tachograph payload, i.e. the data sent encrypted in the RTM message. For the encryption see Appendix 11 Part B chapter 13.

            Text of image

               TachographPayloadEncrypted ::= SEQUENCE {
               tag OCTET STRING(SIZE(1)),
               length OCTET STRING(SIZE(1..2)),
               paddingContentIndicatorByte OCTET STRING(SIZE(1)),
               encryptedData OCTET STRING(SIZE(16..192))
               }

               tag is part of the DER-TLV encoding and shall be set to ‘87’ (see Appendix 11 Part B chapter 13).

               length is part of the DER-TLV encoding and shall encode the length of the following paddingContentIndicatorByte and the encryptedData.

               paddingContentIndicatorByte shall be set to ‘00’.

               encryptedData is encrypted tachographPayload as specified in Appendix 11 Part B chapter 13. The length of this data in octests shall always be a multiple of 16.
            2.161.   TDesSessionKey

            Generation 1:
            A triple DES session key.

            Text of image

               TDesSessionKey ::= SEQUENCE {
               tDesKeyA OCTET STRING (SIZE(8)),
               tDesKeyB OCTET STRING (SIZE(8))
               }

               Value assignment: not further specified.
            2.162.   TimeReal

            Code for a combined date and time field, where the date and time are expressed as seconds past 00h.00m.00s. on 1 January 1970 GMT.

            Text of image

               TimeReal{INTEGER:TimeRealRange} ::= INTEGER(0..TimeRealRange)

               Value assignment — Octet Aligned: Number of seconds since midnight 1 January 1970 GMT.
            The max. possible date/time is in the year 2106.
            2.163.   TyreSize

            Designation of tyre dimensions.

            Text of image

               TyreSize ::= IA5String(SIZE(15))

               Value assignment: in accordance with Directive 92/23 (EEC) 31/03/92 O.J. L129 p.95.
            2.164.   VehicleIdentificationNumber

            Vehicle Identification Number (VIN) referring to the vehicle as a whole, normally chassis serial number or frame number.

            Text of image

               VehicleIdentificationNumber ::= IA5String(SIZE(17))

               Value assignment: As defined in ISO 3779.
            2.165.   VehicleIdentificationNumberRecordArray

            Generation 2:
            The Vehicle Idenification Number plus metadata as used in the download protocol.

            Text of image

               VehicleIdentificationNumberRecordArray ::= SEQUENCE {
               recordType RecordType,
               recordSize INTEGER(1..65535),
               noOfRecords INTEGER(0..65535),
               records SET SIZE(noOfRecords) OF VehicleIdentificationNumber
               }

               recordType denotes the type of the record (VehicleIdentificationNumber). Value Assignment: See RecordType

               recordSize is the size of the VehicleIdentificationNumber in bytes.

               noOfRecords is the number of records in the set records.

               records is the set of vehicle identification numbers.
            2.166.   VehicleRegistrationIdentification

            Identification of a vehicle, unique for Europe (VRN and Member State).

            Text of image

               VehicleRegistrationIdentification ::= SEQUENCE {
               vehicleRegistrationNation NationNumeric,
               vehicleRegistrationNumber VehicleRegistrationNumber
               }

               vehicleRegistrationNation is the nation where the vehicle is registered.

               vehicleRegistrationNumber is the registration number of the vehicle (VRN).
            2.167.   VehicleRegistrationNumber

            Registration number of the vehicle (VRN). The registration number is assigned by the vehicle licensing authority.

            Text of image

               VehicleRegistrationNumber ::= SEQUENCE {
               codePage INTEGER (0..255),
               vehicleRegNumber OCTET STRING (SIZE(13))
               }

               codePage specifies a character set defined in Chapter 4,

               vehicleRegNumber is a VRN encoded using the specified character set.

               Value assignment: Country specific.
            2.168.   VehicleRegistrationNumberRecordArray

            Generation 2:
            The Vehicle Registration Number plus metadata as used in the download protocol.

            Text of image

               VehicleRegistrationNumberRecordArray ::= SEQUENCE {
               recordType RecordType,
               recordSize INTEGER(1..65535),
               noOfRecords INTEGER(0..65535),
               records SET SIZE(noOfRecords) OF VehicleRegistrationNumber
               }

               recordType denotes the type of the record (VehicleRegistrationNumber). Value Assignment: See RecordType

               recordSize is the size of the VehicleRegistrationNumber in bytes.

               noOfRecords is the number of records in the set records.

               records is the set of vehicle registration numbers.
            2.169.   VuAbility

            Generation 2:
            Information stored in a VU on the ability of the VU to use generation 1 tachograph cards or not (Annex 1C requirement 121).

            Text of image

               VuAbility ::= OCTET STRING (SIZE(1))

               Value assignment — Octet Aligned:‘xxxxxxxa’B (8 bits)
            For the ability to support of generation 1:

                        ‘a’B

                        Ability to support generation 1 tachograph cards:

                                    ‘0’ B Generation 1 is supported,

                                    ‘1’B Generation1 is not supported,

                        ‘xxxxxxx’B

                        RFU

                  2.170.   VuActivityDailyData

            Generation 1:
            Information, stored in a VU, related to changes of activity and/or changes of driving status and/or changes of card status for a given calendar day (Annex 1B requirement 084 and Annex 1C requirement 105, 106, 107) and to slots status at 00:00 that day.

            Text of image

               VuActivityDailyData ::= SEQUENCE {
               noOfActivityChanges INTEGER SIZE(0..1440),
               activityChangeInfos SET SIZE(noOfActivityChanges) OF ActivityChangeInfo
               }

               noOfActivityChanges is the number of ActivityChangeInfo words in the activityChangeInfos set.

               activityChangeInfos is the set of ActivityChangeInfo words stored in the VU for the day. It always includes two ActivityChangeInfo words giving the status of the two slots at 00:00 that day.
            2.171.   VuActivityDailyRecordArray

            Generation 2:
            Information, stored in a VU, related to changes of activity and/or changes of driving status and/or changes of card status for a given calendar day (Annex 1C requirement 105, 106, 107) and to slots status at 00:00 that day.

            Text of image

               VuActivityDailyRecordArray ::= SEQUENCE {
               recordType RecordType,
               recordSize INTEGER(1..65535),
               noOfRecords INTEGER(0..65535),
               records SET SIZE(noOfRecords) OF ActivityChangeInfo
               }

               recordType denotes the type of the record (ActivityChangeInfo). Value Assignment: See RecordType

               recordSize is the size of the ActivityChangeInfo in bytes.

               noOfRecords is the number of records in the set records.

               records is the set of ActivityChangeInfo words stored in the VU for the day. It always includes two ActivityChangeInfo words giving the status of the two slots at 00:00 that day.
            2.172.   VuApprovalNumber

            Type approval number of the vehicle unit.

                        Generation 1:
                        Text of image

                           VuApprovalNumber ::= IA5String(SIZE(8))

                           Value assignment: Unspecified.

                        Generation 2:
                        Text of image

                           VuApprovalNumber ::= IA5String(SIZE(16))

                           Value assignment:

                        The approval number shall be provided as published on the corresponding European Commission web site, i.e. for example including hyphens if any. The approval number shall be left-aligned.

                  2.173.   VuCalibrationData

            Generation 1:
            Information, stored in a vehicle unit, related to the calibrations of the recording equipment (Annex 1B requirement 098).

            Text of image

               VuCalibrationData ::= SEQUENCE {
               noOfVuCalibrationRecords INTEGER(0..255),
               vuCalibrationRecords SET SIZE(noOfVuCalibrationRecords) OF VuCalibrationRecord
               }

               noOfVuCalibrationRecords is the number of records contained in the vuCalibrationRecords set.

               vuCalibrationRecords is the set of calibration records.
            2.174.   VuCalibrationRecord

            Information, stored in a vehicle unit, related a calibration of the recording equipment (Annex 1B requirement 098 and Annex 1C requirement 119 and 120).

                        Generation 1:
                        Text of image

                           VuCalibrationRecord ::= SEQUENCE {
                           calibrationPurpose CalibrationPurpose,
                           workshopName Name,
                           workshopAddress Address,
                           workshopCardNumber FullCardNumber,
                           workshopCardExpiryDate TimeReal,
                           vehicleIdentificationNumber VehicleIdentificationNumber,
                           vehicleRegistrationIdentification VehicleRegistrationIdentification,
                           wVehicleCharacteristicConstant W-VehicleCharacteristicConstant,
                           kConstantOfRecordingEquipment K-ConstantOfRecordingEquipment,
                           lTyreCircumference L-TyreCircumference,
                           tyreSize TyreSize,
                           authorisedSpeed SpeedAuthorised,
                           oldOdometerValue OdometerShort,
                           newOdometerValue OdometerShort,
                           oldTimeValue TimeReal,
                           newTimeValue TimeReal,
                           nextCalibrationDate TimeReal
                           }

                           calibrationPurpose is the purpose of the calibration.

                           workshopName, workshopAddress are the workshop name and address.

                           workshopCardNumber identifies the workshop card used during the calibration.

                           workshopCardExpiryDate is the card expiry date.

                           vehicleIdentificationNumber is the VIN.

                           vehicleRegistrationIdentification contains the VRN and registering Member State.

                           wVehicleCharacteristicConstant is the characteristic coefficient of the vehicle.

                           kConstantOfRecordingEquipment is the constant of the recording equipment.

                           lTyreCircumference is the effective circumference of the wheel tyres.

                           tyreSize is the designation of the dimension of the tyres mounted on the vehicle

                           authorisedSpeed is the authorised speed of the vehicle.

                           oldOdometerValue, newOdometerValue are the old and new values of the odometer.

                           oldTimeValue, newTimeValue are the old and new values of date and time.

                           nextCalibrationDate is the date of the next calibration of the type specified in CalibrationPurpose to be carried out by the authorised inspection authority.

                        Generation 2:
                        Text of image

                           VuCalibrationRecord ::= SEQUENCE {
                           calibrationPurpose CalibrationPurpose,
                           workshopName Name,
                           workshopAddress Address,
                           workshopCardNumber FullCardNumber,
                           workshopCardExpiryDate TimeReal,
                           vehicleIdentificationNumber VehicleIdentificationNumber,
                           vehicleRegistrationIdentification VehicleRegistrationIdentification,
                           wVehicleCharacteristicConstant W-VehicleCharacteristicConstant,
                           kConstantOfRecordingEquipment K-ConstantOfRecordingEquipment,
                           lTyreCircumference L-TyreCircumference,
                           tyreSize TyreSize,
                           authorisedSpeed SpeedAuthorised,
                           oldOdometerValue OdometerShort,
                           newOdometerValue OdometerShort,
                           oldTimeValue TimeReal,
                           newTimeValue TimeReal,
                           nextCalibrationDate TimeReal,
                           sealDataVu SealDataVu
                           }

                        In addition to generation 1 the following data element is used:

                           sealDataVu gives information about the seals that are attached to different components of the vehicle.

                  2.175.   VuCalibrationRecordArray

            Generation 2:
            Information, stored in a vehicle unit, related to the calibrations of the recording equipment (Annex 1C requirement 119 and 120).

            Text of image

               VuCalibrationRecordArray ::= SEQUENCE {
               recordType RecordType,
               recordSize INTEGER(1..65535),
               noOfRecords INTEGER(0..65535),
               records SET SIZE(noOfRecords) OF
               VuCalibrationRecord
               }

               recordType denotes the type of the record (VuCalibrationRecord). Value Assignment: See RecordType

               recordSize is the size of the VuCalibrationRecord in bytes.

               noOfRecords is the number of records in the set records.

               records is the set of calibration records.
            2.176.   VuCardIWData

            Generation 1:
            Information, stored in a vehicle unit, related to insertion and withdrawal cycles of driver cards or of workshop cards in the vehicle unit (Annex 1B requirement 081 and Annex 1C requirement 103).

            Text of image

               VuCardIWData ::= SEQUENCE {
               noOfIWRecords INTEGER(0..216-1),
               vuCardIWRecords SET SIZE(noOfIWRecords) OF VuCardIWRecord
               }

               noOfIWRecords is the number of records in the set vuCardIWRecords.

               vuCardIWRecords is a set of records related to card insertion withdrawal cycles.
            2.177.   VuCardIWRecord

            Information, stored in a vehicle unit, related to an insertion and withdrawal cycle of a driver card or of a workshop card in the vehicle unit (Annex 1B requirement 081 and Annex 1C requirement 102).

                        Generation 1:
                        Text of image

                           VuCardIWRecord ::= SEQUENCE {
                           cardHolderName HolderName,
                           fullCardNumber FullCardNumber,
                           cardExpiryDate TimeReal,
                           cardInsertionTime TimeReal,
                           vehicleOdometerValueAtInsertion OdometerShort,
                           cardSlotNumber CardSlotNumber,
                           cardWithdrawalTime TimeReal,
                           vehicleOdometerValueAtWithdrawal OdometerShort,
                           previousVehicleInfo PreviousVehicleInfo,
                           manualInputFlag ManualInputFlag
                           }

                           cardHolderName is the driver or workshop card holder's surname and first names as stored in the card.

                           fullCardNumber is the type of card, its issuing Member State and its card number as stored in the card.

                           cardExpiryDate is the card's expiry date as stored in the card.

                           cardInsertionTime is the insertion date and time.

                           vehicleOdometerValueAtInsertion is the vehicle odometer value at card insertion.

                           cardSlotNumber is the slot in which the card is inserted.

                           cardWithdrawalTime is the withdrawal date and time.

                           vehicleOdometerValueAtWithdrawal is the vehicle odometer value at card withdrawal.

                           previousVehicleInfo contains information about the previous vehicle used by the driver, as stored in the card.

                           manualInputFlag is a flag identifying if the cardholder has manually entered driver activities at card insertion.

                        Generation 2:
                        Text of image

                           VuCardIWRecord ::= SEQUENCE {
                           cardHolderName HolderName,
                           fullCardNumberAndGeneration FullCardNumberAndGeneration,
                           cardExpiryDate TimeReal,
                           cardInsertionTime TimeReal,
                           vehicleOdometerValueAtInsertion OdometerShort,
                           cardSlotNumber CardSlotNumber,
                           cardWithdrawalTime TimeReal,
                           vehicleOdometerValueAtWithdrawal OdometerShort,
                           previousVehicleInfo PreviousVehicleInfo,
                           manualInputFlag ManualInputFlag
                           }

                        Instead of fullCardNumber the generation 2 data structure makes use of the following data element.

                           fullCardNumberAndGeneration is the type of card, its issuing Member State, its card number and generation as stored in the card.

                  2.178.   VuCardIWRecordArray

            Generation 2:
            Information, stored in a vehicle unit, related to insertion and withdrawal cycles of driver cards or of workshop cards in the vehicle unit (Annex 1C requirement 103).

            Text of image

               VuCardIWRecordArray ::= SEQUENCE {
               recordType RecordType,
               recordSize INTEGER(1..65535),
               noOfRecords INTEGER(0..65535),
               records SET SIZE(noOfRecords) OF VuCardIWRecord
               }

               recordType denotes the type of the record (VuCardIWRecord). Value Assignment: See RecordType

               recordSize is the size of the VuCardIWRecord in bytes.

               noOfRecords is the number of records in the set records.

               records is a set of records related to card insertion withdrawal cycles.
            2.179.   VuCardRecord

            Generation 2:
            Information, stored in a vehicle unit, about a tachograph card used (Annex 1C requirement 132).

            Text of image

               VuCardRecord ::= SEQUENCE {
               cardExtendedSerialNumber ExtendedSerialNumber,
               cardPersonaliserID OCTET STRING(SIZE(1)),
               typeofTachographCardID EquipmentType,
               cardStructureVersion CardStructureVersion,
               cardNumber CardNumber
               }

               cardExtendedSerialNumber as read from the file EF_ICC under the MF of the card.

               cardPersonaliserID as read from the file EF_ICC under the MF of the card.

               typeOfTachographCardId as read from the file EF_Application_Identification under the DF_Tachograph_G2

               cardStructureVersion as read from the file EF_Application_Identification under the DF_Tachograph_G2.

               cardNumber as read from the file EF_Identification under the DF_Tachograph_G2.
            2.180.   VuCardRecordArray

            Generation 2:
            Information stored in a vehicle unit about the tachograph cards used with this VU. This information is intended for the analysis of VU — card problems (Annex 1C requirement 132).

            Text of image

               VuCardRecordArray ::= SEQUENCE {
               recordType RecordType,
               recordSize INTEGER(1..65535),
               noOfRecords INTEGER(0..65535),
               records SET SIZE(noOfRecords) OF VuCardRecord
               }

               recordType denotes the type of the record (VuCardRecord). Value Assignment: See RecordType

               recordSize is the size of the VuCardRecord in bytes.

               noOfRecords is the number of records in the set records.

               records is a set of records related to the tachograph cards used with the VU.
            2.181.   VuCertificate

            Certificate of the public key of a vehicle unit.

            Text of image

               VuCertificate ::= Certificate

            2.182.   VuCertificateRecordArray

            Generation 2:
            The VU certificate plus metadata as used in the download protocol.

            Text of image

               VuCertificateRecordArray ::= SEQUENCE {
               recordType RecordType,
               recordSize INTEGER(1..65535),
               noOfRecords INTEGER(0..65535),
               records SET SIZE(noOfRecords) OF VuCertificate
               }

               recordType denotes the type of the record (VuCertificate). Value Assignment: See RecordType

               recordSize is the size of the VuCertificate in bytes.

               noOfRecords is the number of records in the set records. The value shall be set to 1 as the certificates may have different lengths.

               records is a set of VU certificates.
            2.183.   VuCompanyLocksData

            Generation 1:
            Information, stored in a vehicle unit, related to company locks (Annex 1B requirement 104).

            Text of image

               VuCompanyLocksData ::= SEQUENCE {
               noOfLocks INTEGER(0..255),
               vuCompanyLocksRecords SET SIZE(noOfLocks) OF VuCompanyLocksRecord
               }

               noOfLocks is the number of locks listed in vuCompanyLocksRecords.

               vuCompanyLocksRecords is the set of company locks records.
            2.184.   VuCompanyLocksRecord

            Information, stored in a vehicle unit, related to one company lock (Annex 1B requirement 104 and Annex 1C requirement 128).

                        Generation 1:
                        Text of image

                           VuCompanyLocksRecord ::= SEQUENCE {
                           lockInTime TimeReal,
                           lockOutTime TimeReal,
                           companyName Name,
                           companyAddress Address,
                           companyCardNumber FullCardNumber
                           }

                           lockInTime, lockOutTime are the date and time of lock-in and lock-out.

                           companyName, companyAddress are the company name and address related with the lock-in.

                           companyCardNumber identifies the card used at lock-in.

                        Generation 2:
                        Text of image

                           VuCompanyLocksRecord ::= SEQUENCE {
                           lockInTime TimeReal,
                           lockOutTime TimeReal,
                           companyName Name,
                           companyAddress Address,
                           companyCardNumberAndGeneration FullCardNumberAndGeneration
                           }

                        Instead of companyCardNumber the generation 2 data structure makes use of the following data element.

                           companyCardNumberAndGeneration identifies the card including its generation used at lock-in.

                  2.185.   VuCompanyLocksRecordArray

            Generation 2:
            Information, stored in a vehicle unit, related to company locks (Annex 1C requirement 128).

            Text of image

               VuCompanyLocksRecordArray ::= SEQUENCE {
               recordType RecordType,
               recordSize INTEGER(1..65535),
               noOfRecords INTEGER(0..65535),
               records SET SIZE(noOfRecords) OF
               VuCompanyLocksRecord
               }

               recordType denotes the type of the record (VuCompanyLocksRecord). Value Assignment: See RecordType

               recordSize is the size of the VuCompanyLocksRecord in bytes.

               noOfRecords is the number of records in the set records. Value 0..255.

               records is the set of company locks records.
            2.186.   VuControlActivityData

            Generation 1:
            Information, stored in a vehicle unit, related to controls performed using this VU (Annex 1B requirement 102).

            Text of image

               VuControlActivityData ::= SEQUENCE {
               noOfControls INTEGER(0..20),
               vuControlActivityRecords SET SIZE(noOfControls) OF VuControlActivityRecord
               }

               noOfControls is the number of controls listed in vuControlActivityRecords.

               vuControlActivityRecords is the set of control activity records.
            2.187.   VuControlActivityRecord

            Information, stored in a vehicle unit, related to a control performed using this VU (Annex 1B requirement 102 and Annex 1C requirement 126).

                        Generation 1:
                        Text of image

                           VuControlActivityRecord ::= SEQUENCE {
                           controlType ControlType,
                           controlTime TimeReal,
                           controlCardNumber FullCardNumber,
                           downloadPeriodBeginTime TimeReal,
                           downloadPeriodEndTime TimeReal
                           }

                           controlType is the type of the control.

                           controlTime is the date and time of the control.

                           controlCardNumber identifies the control card used for the control.

                           downloadPeriodBeginTime is the begin time of the downloaded period, in case of downloading.

                           downloadPeriodEndTime is the end time of the downloaded period, in case of downloading.

                        Generation 2:
                        Text of image

                           VuControlActivityRecord ::= SEQUENCE {
                           controlType ControlType,
                           controlTime TimeReal,
                           controlCardNumberAndGeneration FullCardNumberAndGeneration,
                           downloadPeriodBeginTime TimeReal,
                           downloadPeriodEndTime TimeReal
                           }

                        Instead of controlCardNumber the generation 2 data structure makes use of the following data element.

                           controlCardNumberAndGeneration identifies the control card including its generation used for the control.

                  2.188.   VuControlActivityRecordArray

            Generation 2:
            Information, stored in a vehicle unit, related to controls performed using this VU (Annex 1C requirement 126).

            Text of image

               VuControlActivityRecordArray ::= SEQUENCE {
               recordType RecordType,
               recordSize INTEGER(1..65535),
               noOfRecords INTEGER(0..65535),
               records SET SIZE(noOfRecords) OF VuControlActivityRecord
               }

               recordType denotes the type of the record (VuControlActivityRecord). Value Assignment: See RecordType

               recordSize is the size of the VuControlActivityRecord in bytes.

               noOfRecords is the number of records in the set records.

               records is the set of VU control activity records.
            2.189.   VuDataBlockCounter

            Counter, stored in a card, identifying sequentially the insertion withdrawal cycles of the card in vehicle units.

            Text of image

               VuDataBlockCounter ::= BCDString(SIZE(2))

               Value assignment: Consecutive Number with max, value 9 999, starting again with 0.
            2.190.   VuDetailedSpeedBlock

            Information, stored in a vehicle unit, related to the vehicle's detailed speed for a minute during which the vehicle has been moving (Annnex 1B requirement 093 and Annex 1C requirement 116).

            Text of image

               VuDetailedSpeedBlock ::= SEQUENCE {
               speedBlockBeginDate TimeReal,
               speedsPerSecond SEQUENCE SIZE(60) OF Speed
               }

               speedBlockBeginDate is the date and time of the first speed value within the block.

               speedsPerSecond is the chronological sequence of measured speeds every seconds for the minute starting at speedBlockBeginDate (included).
            2.191.   VuDetailedSpeedBlockRecordArray

            Generation 2:
            Information, stored in a vehicle unit, related to the detailed speed of the vehicle.

            Text of image

               VuDetailedSpeedBlockRecordArray ::= SEQUENCE {
               recordType RecordType,
               recordSize INTEGER(1..65535),
               noOfRecords INTEGER(0..65535),
               records SET SIZE(noOfRecords) OF
               VuDetailedSpeedBlock
               }

               recordType denotes the type of the record (VuDetailedSpeedBlock). Value Assignment: See RecordType

               recordSize is the size of the VuDetailedSpeedBlock in bytes.

               noOfRecords is the number of records in the set records.

               records is the set of detailed speed blocks.
            2.192.   VuDetailedSpeedData

            Generation 1:
            Information, stored in a vehicle unit, related to the detailed speed of the vehicle.

            Text of image

               VuDetailedSpeedData ::= SEQUENCE {
               noOfSpeedBlocks INTEGER(0..216-1),
               vuDetailedSpeedBlocks SET SIZE(noOfSpeedBlocks) OF VuDetailedSpeedBlock
               }

               noOfSpeedBlocks is the number of speed blocks in the vuDetailedSpeedBlocks set.

               vuDetailedSpeedBlocks is the set of detailed speed blocks.
            2.193.   VuDownloadablePeriod

            Oldest and latest dates for which a vehicle unit holds data related to drivers activities (Annex 1B requirements 081, 084 or 087 and Annex 1C requirements 102, 105, 108).

            Text of image

               VuDownloadablePeriod ::= SEQUENCE {
               minDownloadableTime TimeReal
               maxDownloadableTime TimeReal
               }

               minDownloadableTime is the oldest card insertion or activity change or place entry date and time stored in the VU.

               maxDownloadableTime is the latest card withdrawal or activity change or place entry date and time stored in the VU.
            2.194.   VuDownloadablePeriodRecordArray

            Generation 2:
            The VUDownloadablePeriod plus metadata used in the download protocol.

            Text of image

               VuDownloadablePeriodRecordArray ::= SEQUENCE {
               recordType RecordType,
               recordSize INTEGER(1..65535),
               noOfRecords INTEGER(0..65535),
               records SET SIZE(noOfRecords) OF
               VuDownloadablePeriod
               }

               recordType denotes the type of the record (VuDownloadablePeriod). Value Assignment: See RecordType

               recordSize is the size of the VuDownloadablePeriod in bytes.

               noOfRecords is the number of records in the set records.

               records is the set of VuDownloadablePeriod records.
            2.195.   VuDownloadActivityData

            Information, stored in a vehicle unit, related to its last download (Annex 1B requirement 105 and Annex 1C requirement 129).

                        Generation 1:
                        Text of image

                           VuDownloadActivityData ::= SEQUENCE {
                           downloadingTime TimeReal,
                           fullCardNumber FullCardNumber,
                           companyOrWorkshopName Name
                           }

                           downloadingTime is the date and time of downloading.

                           fullCardNumber identifies the card used to authorise the download.

                           companyOrWorkshopName is the company or workshop name.

                        Generation 2:
                        Text of image

                           VuDownloadActivityData ::= SEQUENCE {
                           downloadingTime TimeReal,
                           fullCardNumberAndGeneration FullCardNumberAndGeneration,
                           companyOrWorkshopName Name
                           }

                        Instead of fullCardNumber the generation 2 data structure makes use of the following data element.

                           fullCardNumberAndGeneration identifies the card including its generation used to authorise the download.

                  2.196.   VuDownloadActivityDataRecordArray

            Generation 2:
            Information related to the last VU download (Annex 1C requirement 129).

            Text of image

               VuDownloadActivityDataRecordArray ::= SEQUENCE {
               recordType RecordType,
               recordSize INTEGER(1..65535),
               noOfRecords INTEGER(0..65535),
               records SET SIZE(noOfRecords) OF VuDownloadActivityData
               }

               recordType denotes the type of the record (VuDownloadActivityData). Value Assignment: See RecordType

               recordSize is the size of the VuDownloadActivityData in bytes.

               noOfRecords is the number of records in the set records.

               records is the set of download activity data records.
            2.197.   VuEventData

            Generation 1:
            Information, stored in a vehicle unit, related to events (Annex 1B requirement 094 except over speeding event).

            Text of image

               VuEventData ::= SEQUENCE {
               noOfVuEvents INTEGER(0..255),
               vuEventRecords SET SIZE(noOfVuEvents) OF VuEventRecord
               }

               noOfVuEvents is the number of events listed in the vuEventRecords set.

               vuEventRecords is a set of events records.
            2.198.   VuEventRecord

            Information, stored in a vehicle unit, related to an event (Annex 1B requirement 094 and Annex 1C requirement 117 except over speeding event).

                        Generation 1:
                        Text of image

                           VuEventRecord ::= SEQUENCE {
                           eventType EventFaultType,
                           eventRecordPurpose EventFaultRecordPurpose,
                           eventBeginTime TimeReal,
                           eventEndTime TimeReal,
                           cardNumberDriverSlotBegin FullCardNumber,
                           cardNumberCodriverSlotBegin FullCardNumber,
                           cardNumberDriverSlotEnd FullCardNumber,
                           cardNumberCodriverSlotEnd FullCardNumber,
                           similarEventsNumber SimilarEventsNumber
                           }

                           eventType is the type of the event.

                           eventRecordPurpose is the purpose for which this event has been recorded.

                           eventBeginTime is the date and time of beginning of event.

                           eventEndTime is the date and time of end of event.

                           cardNumberDriverSlotBegin identifies the card inserted in the driver slot at the beginning of the event.

                           cardNumberCodriverSlotBegin identifies the card inserted in the co-driver slot at the beginning of the event.

                           cardNumberDriverSlotEnd identifies the card inserted in the driver slot at the end of the event.

                           cardNumberCodriverSlotEnd identifies the card inserted in the co-driver slot at the end of the event.

                           similarEventsNumber is the number of similar events that day.
                        This sequence can be used for all events other than over speeding events.

                        Generation 2:
                        Text of image

                           VuEventRecord ::= SEQUENCE {
                           eventType EventFaultType,
                           eventRecordPurpose EventFaultRecordPurpose,
                           eventBeginTime TimeReal,
                           eventEndTime TimeReal,
                           cardNumberAndGenDriverSlotBegin FullCardNumberAndGeneration,
                           cardNumberAndGenCodriverSlotBegin FullCardNumberAndGeneration,
                           cardNumberAndGenDriverSlotEnd FullCardNumberAndGeneration,
                           cardNumberAndGenCodriverSlotEnd FullCardNumberAndGeneration,
                           similarEventsNumber SimilarEventsNumber,
                           manufacturerSpecificEventFaultData ManufacturerSpecificEventFaultData
                           }

                        In addition to generation 1 the following data elements are used:

                           manufacturerSpecificEventFaultData contains additional, manufacturer specific information about the event.
                        Instead of cardNumberDriverSlotBegin, cardNumberCodriverSlotBegin, cardNumberDriverSlotEnd, and cardNumberCodriverSlotEnd the generation 2 data structure makes use of the following data elements:

                                       cardNumberAndGenDriverSlotBegin identifies the card including its generation which is inserted in the driver slot at the beginning of the event.

                                       cardNumberAndGenCodriverSlotBegin identifies the card including its generation which is inserted in the co-driver slot at the beginning of the event.

                                       cardNumberAndGenDriverSlotEnd identifies the card including its generation which is inserted in the driver slot at the end of the event.

                                       cardNumberAndGenCodriverSlotEnd identifies the card including its generation which is inserted in the co-driver slot at the end of the event.

                              If the event is a time conflict the eventBeginTime and eventEndTime are to be interpreted as follows:

                                       eventBeginTime is the recording equipment date and time.

                                       eventEndTime is the GNSS date and time.

                  2.199.   VuEventRecordArray

            Generation 2:
            Information, stored in a vehicle unit, related to events (Annex 1C requirement 117 except over speeding event).

            Text of image

               VuEventRecordArray ::= SEQUENCE {
               recordType RecordType,
               recordSize INTEGER(1..65535),
               noOfRecords INTEGER(0..65535),
               records SET SIZE(noOfRecords) OF VuEventRecord
               }

               recordType denotes the type of the record (VuEventRecord). Value Assignment: See RecordType

               recordSize is the size of the VuEventRecord in bytes.

               noOfRecords is the number of records in the set records.

               records is a set of events records.
            2.200.   VuFaultData

            Generation 1:
            Information, stored in a vehicle unit, related to faults (Annex 1B requirement 096).

            Text of image

               VuFaultData ::= SEQUENCE {
               noOfVuFaults INTEGER(0..255),
               vuFaultRecords SET SIZE(noOfVuFaults) OF VuFaultRecord
               }

               noOfVuFaults is the number of faults listed in the vuFaultRecords set.

               vuFaultRecords is a set of faults records.
            2.201.   VuFaultRecord

            Information, stored in a vehicle unit, related to a fault (Annex 1B requirement 096 and Annex 1C requirement 118).

                        Generation 1:
                        Text of image

                           VuFaultRecord ::= SEQUENCE {
                           faultType EventFaultType,
                           faultRecordPurpose EventFaultRecordPurpose,
                           faultBeginTime TimeReal,
                           faultEndTime TimeReal,
                           cardNumberDriverSlotBegin FullCardNumber,
                           cardNumberCodriverSlotBegin FullCardNumber,
                           cardNumberDriverSlotEnd FullCardNumber,
                           cardNumberCodriverSlotEnd FullCardNumber
                           }

                           faultType is the type of recording equipment fault.

                           faultRecordPurpose is the purpose for which this fault has been recorded.

                           faultBeginTime is the date and time of beginning of fault.

                           faultEndTime is the date and time of end of fault.

                           cardNumberDriverSlotBegin identifies the card inserted in the driver slot at the beginning of the fault.

                           cardNumberCodriverSlotBegin identifies the card inserted in the co-driver slot at the beginning of the fault.

                           cardNumberDriverSlotEnd identifies the card inserted in the driver slot at the end of the fault.

                           cardNumberCodriverSlotEnd identifies the card inserted in the co-driver slot at the end of the fault.

                        Generation 2:
                        Text of image

                           VuFaultRecord ::= SEQUENCE {
                           faultType EventFaultType,
                           faultRecordPurpose EventFaultRecordPurpose,
                           faultBeginTime TimeReal,
                           faultEndTime TimeReal,
                           cardNumberAndGenDriverSlotBegin FullCardNumberAndGeneration,
                           cardNumberAndGenCodriverSlotBegin FullCardNumberAndGeneration,
                           cardNumberAndGenDriverSlotEnd FullCardNumberAndGeneration,
                           cardNumberAndGenCodriverSlotEnd FullCardNumberAndGeneration,
                           manufacturerSpecificEventFaultData ManufacturerSpecificEventFaultData
                           }

                        In addition to generation 1 the following data element is used:

                           manufacturerSpecificEventFaultData contains additional, manufacturer specific information about the fault.
                        Instead of cardNumberDriverSlotBegin, cardNumberCodriverSlotBegin, cardNumberDriverSlotEnd, and cardNumberCodriverSlotEnd the generation 2 data structure makes use of the following data elements:

                                       cardNumberAndGenDriverSlotBegin identifies the card including its generation which is inserted in the driver slot at the beginning of the fault.

                                       cardNumberAndGenCodriverSlotBegin identifies the card including its generation which is inserted in the co-driver slot at the beginning of the fault.

                                       cardNumberAndGenDriverSlotEnd identifies the card including its generation which is inserted in the driver slot at the end of the fault.

                                       cardNumberAndGenCodriverSlotEnd identifies the card including its generation which is inserted in the co-driver slot at the end of the fault.

                  2.202.   VuFaultRecordArray

            Generation 2:
            Information, stored in a vehicle unit, related to faults (Annex 1C requirement 118).

            Text of image

               VuFaultRecordArray ::= SEQUENCE {
               recordType RecordType,
               recordSize INTEGER(1..65535),
               noOfRecords INTEGER(0..65535),
               records SET SIZE(noOfRecords) OF VuFaultRecord
               }

               recordType denotes the type of the record (VuFaultRecord). Value Assignment: See RecordType

               recordSize is the size of the VuFaultRecord in bytes.

               noOfRecords is the number of records in the set records.

               records is a set of faults records.
            2.203.   VuGNSSCDRecord

            Generation 2:
            Information, stored in a vehicle unit, related to the GNSS position of the vehicle if the continuous driving time of the driver reaches a multiple of three hours (Annex 1C requirement 108, 110).

            Text of image

               VuGNSSCDRecord ::= SEQUENCE {
               timeStamp TimeReal,
               cardNumberAndGenDriverSlot FullCardNumberAndGeneration,
               cardNumberAndGenCodriverSlot FullCardNumberAndGeneration,
               gnssPlaceRecord GNSSPlaceRecord
               }

               timeStamp is the date and time when the continuous driving time of the card holder reaches a multiple of three hours.

               cardNumberAndGenDriverSlot identifies the card including its generation which is inserted in the driver slot.

               cardNumberAndGenCodriverSlot identifies the card including its generation which is inserted in the co-driver slot.

               gnssPlaceRecord contains information related to the position of the vehicle.
            2.204.   VuGNSSCDRecordArray

            Generation 2:
            Information, stored in a vehicle unit, related to the GNSS position of the vehicle if the continuous driving time of the driver reaches a multiple of three hours (Annex 1C requirement 108 and 110).

            Text of image

               VuGNSSCDRecordArray ::= SEQUENCE {
               recordType RecordType,
               recordSize INTEGER(1..65535),
               noOfRecords INTEGER(0..65535),
               records SET SIZE(noOfRecords) OF VuGNSSCDRecord
               }

               recordType denotes the type of the record (VuGNSSCDRecord). Value Assignment: See RecordType

               recordSize is the size of the VuGNSSCDRecord in bytes.

               noOfRecords is the number of records in the set records.

               records is a set of GNSS continuous driving records.
            2.205.   VuIdentification

            Information, stored in a vehicle unit, related to the identification of the vehicle unit (Annex 1B requirement 075 and Annex 1C requirement 93 and 121).

                        Generation 1:
                        Text of image

                           VuIdentification ::= SEQUENCE {
                           vuManufacturerName VuManufacturerName,
                           vuManufacturerAddress VuManufacturerAddress,
                           vuPartNumber VuPartNumber,
                           vuSerialNumber VuSerialNumber,
                           vuSoftwareIdentification VuSoftwareIdentification,
                           vuManufacturingDate VuManufacturingDate,
                           vuApprovalNumber VuApprovalNumber
                           }

                           vuManufacturerName is the name of the manufacturer of the vehicle unit.

                           vuManufacturerAddress is the address of the manufacturer of the vehicle unit.

                           vuPartNumber is the part number of the vehicle unit.

                           vuSerialNumber is the serial number of the vehicle unit.

                           vuSoftwareIdentification identifies the software implemented in the vehicle unit.

                           vuManufacturingDate is the manufacturing date of the vehicle unit.

                           vuApprovalNumber is the type approval number of the vehicle unit.

                        Generation 2:
                        Text of image

                           VuIdentification ::= SEQUENCE {
                           vuManufacturerName VuManufacturerName,
                           vuManufacturerAddress VuManufacturerAddress,
                           vuPartNumber VuPartNumber,
                           vuSerialNumber VuSerialNumber,
                           vuSoftwareIdentification VuSoftwareIdentification,
                           vuManufacturingDate VuManufacturingDate,
                           vuApprovalNumber VuApprovalNumber,
                           vuGeneration Generation,
                           vuAbility VuAbility
                           }

                        In addition to generation 1 the following data element are used:

                                       vuGeneration identifies the generation of the vehicle unit.

                                       vuAbility provides information whether the VU supports generation 1 tachograph cards or not.

                  2.206.   VuIdentificationRecordArray

            Generation 2:
            The VuIdentification plus metadata used in the download protocol.

            Text of image

               VuIdentificationRecordArray ::= SEQUENCE {
               recordType RecordType,
               recordSize INTEGER(1..65535),
               noOfRecords INTEGER(0..65535),
               records SET SIZE(noOfRecords) OF VuIdentification
               }

               recordType denotes the type of the record (VuIdentification). Value Assignment: See RecordType

               recordSize is the size of the VuIdentification in bytes.

               noOfRecords is the number of records in the set records.

               records is a set of VuIdentification records.
            2.207.   VuITSConsentRecord

            Generation 2:
            Information stored in a vehicle unit, related to the consent of a driver to use Intelligent Transport Systems.

            Text of image

               VuITSConsentRecord ::= SEQUENCE {
               cardNumberAndGen FullCardNumberAndGeneration,
               consent BOOLEAN
               }

               cardNumberAndGen identifies the card including its generation. This must be a driver card or a workshop card.

               consent is a flag which indicates whether the driver has given his consent on the usage of Intelligent Transport Systems with this vehicle / vehicle unit.

               Value assignment:

                        TRUE

                        indicates the driver's consent to use Intelligent Transport Systems

                        FALSE

                        indicates the driver's denial to use Intelligent Transport Systems

                  2.208.   VuITSConsentRecordArray

            Generation 2:
            Information, stored in a vehicle unit, related to drivers' consent on the usage of Intelligent Transport Systems (Annex 1C requirement 200).

            Text of image

               VuITSConsentRecordArray ::= SEQUENCE {
               recordType RecordType,
               recordSize INTEGER(1..65535),
               noOfRecords INTEGER(0..65535),
               records SET SIZE(noOfRecords) OF VuITSConsentRecord
               }

               recordType denotes the type of the record (VuITSConsentRecord). Value Assignment: See RecordType

               recordSize is the size of the VuITSConsentRecord in bytes.

               noOfRecords is the number of records in the set records.

               records is the set of ITS consent records.
            2.209.   VuManufacturerAddress

            Address of the manufacturer of the vehicle unit.

            Text of image

               VuManufacturerAddress ::= Address

               Value assignment: Unspecified.
            2.210.   VuManufacturerName

            Name of the manufacturer of the vehicle unit.

            Text of image

               VuManufacturerName ::= Name

               Value assignment: Unspecified.
            2.211.   VuManufacturingDate

            Date of manufacture of the vehicle unit.

            Text of image

               VuManufacturingDate ::= TimeReal

               Value assignment: Unspecified.
            2.212.   VuOverSpeedingControlData

            Information, stored in a vehicle unit, related to over speeding events since the last over speeding control (Annex 1B requirement 095 and Annex 1C requirement 117).

            Text of image

               VuOverSpeedingControlData ::= SEQUENCE {
               lastOverspeedControlTime TimeReal,
               firstOverspeedSince TimeReal,
               numberOfOverspeedSince OverspeedNumber
               }

               lastOverspeedControlTime is the date and time of the last over speeding control.

               firstOverspeedSince is the date and time of the first over speeding following this over speeding control.

               numberOfOverspeedSince is the number of over speeding events since the last over speeding control.
            2.213.   VuOverSpeedingControlDataRecordArray

            Generation 2:
            The VuOverSpeedingControlData plus metadata used in the download protocol.

            Text of image

               VuOverSpeedingControlDataRecordArray ::= SEQUENCE {
               recordType RecordType,
               recordSize INTEGER(1..65535),
               noOfRecords INTEGER(0..65535),
               records SET SIZE(noOfRecords) OF VuOverSpeedingControlData
               }

               recordType denotes the type of the record (VuOverSpeedingControlData). Value Assignment: See RecordType

               recordSize is the size of the VuOverSpeedingControlData in bytes.

               noOfRecords is the number of records in the set records.

               records is a set of over speeding control data records.
            2.214.   VuOverSpeedingEventData

            Generation 1:
            Information, stored in a vehicle unit, related to over speeding events (Annex 1B requirement 094).

            Text of image

               VuOverSpeedingEventData ::= SEQUENCE {
               noOfVuOverSpeedingEvents INTEGER(0..255),
               vuOverSpeedingEventRecords SET SIZE(noOfVuOverSpeedingEvents) OF VuOverSpeedingEventRecord
               }

               noOfVuOverSpeedingEvents is the number of events listed in the vuOverSpeedingEventRecords set.

               vuOverSpeedingEventRecords is a set of over speeding events records.
            2.215.   VuOverSpeedingEventRecord

                        Generation 1:
                        Information, stored in a vehicle unit, related to over speeding events (Annex 1B requirement 094 and Annex 1C requirement 117).
                        Text of image

                           VuOverSpeedingEventRecord ::= SEQUENCE {
                           eventType EventFaultType,
                           eventRecordPurpose EventFaultRecordPurpose,
                           eventBeginTime TimeReal,
                           eventEndTime TimeReal,
                           maxSpeedValue SpeedMax,
                           averageSpeedValue SpeedAverage,
                           cardNumberDriverSlotBegin FullCardNumber,
                           similarEventsNumber SimilarEventsNumber
                           }

                           eventType is the type of the event.

                           eventRecordPurpose is the purpose for which this event has been recorded.

                           eventBeginTime is the date and time of beginning of event.

                           eventEndTime is the date and time of end of event.

                           maxSpeedValue is the maximum speed measured during the event.

                           averageSpeedValue is the arithmetic average speed measured during the event.

                           cardNumberDriverSlotBegin identifies the card inserted in the driver slot at the beginning of the event.

                           similarEventsNumber is the number of similar events that day.

                        Generation 2:
                        Information, stored in a vehicle unit, related to over speeding events (Annex 1B requirement 094 and Annex 1C requirement 117).
                        Text of image

                           VuOverSpeedingEventRecord ::= SEQUENCE {
                           eventType EventFaultType,
                           eventRecordPurpose EventFaultRecordPurpose,
                           eventBeginTime TimeReal,
                           eventEndTime TimeReal,
                           maxSpeedValue SpeedMax,
                           averageSpeedValue SpeedAverage,
                           cardNumberAndGenDriverSlotBegin FullCardNumberAndGeneration,
                           similarEventsNumber SimilarEventsNumber
                           }

                        Instead of cardNumberDriverSlotBegin, the generation 2 data structure makes use of the following data element:

                           cardNumberAndGenDriverSlotBegin identifies the card including its generation which is inserted in the driver slot at the beginning of the event.

                  2.216.   VuOverSpeedingEventRecordArray

            Generation 2:
            Information, stored in a vehicle unit, related to over speeding events (Annex 1C requirement 117).

            Text of image

               VuOverSpeedingEventRecordArray ::= SEQUENCE {
               recordType RecordType,
               recordSize INTEGER(1..65535),
               noOfRecords INTEGER(0..65535),
               records SET SIZE(noOfRecords) OF VuOverSpeedingEventRecord
               }

               recordType denotes the type of the record (VuOverSpeedingEventRecord). Value Assignment: See RecordType

               recordSize is the size of the VuOverSpeedingEventRecord in bytes.

               noOfRecords is the number of records in the set records.

               records is a set of over speeding events records.
            2.217.   VuPartNumber

            Part number of the vehicle unit.

            Text of image

               VuPartNumber ::= IA5String(SIZE(16))

               Value assignment: VU manufacturer specific.
            2.218.   VuPlaceDailyWorkPeriodData

            Generation 1:
            Information, stored in a vehicle unit, related to places where drivers begin or end a daily work period (Annex 1B requirement 087 and Annex 1C requirement 108 and 110).

            Text of image

               VuPlaceDailyWorkPeriodData ::= SEQUENCE {
               noOfPlaceRecords INTEGER(0..255),
               vuPlaceDailyWorkPeriodRecords SET SIZE(noOfPlaceRecords) OF VuPlaceDailyWorkPeriodRecord
               }

               noOfPlaceRecords is the number of records listed in the vuPlaceDailyWorkPeriodRecords set.

               vuPlaceDailyWorkPeriodRecords is a set of place related records.
            2.219.   VuPlaceDailyWorkPeriodRecord

                        Generation 1:
                        Information, stored in a vehicle unit, related to a place where a driver begins or ends a daily work period (Annex 1B requirement 087 and Annex 1C requirement 108 and 110).
                        Text of image

                           VuPlaceDailyWorkPeriodRecord ::= SEQUENCE {
                           fullCardNumber FullCardNumber,
                           placeRecord PlaceRecord
                           }

                           fullCardNumber is the driver's card type, card issuing Member State and card number.

                           placeRecord contains the information related to the place entered.

                        Generation 2:
                        Information, stored in a vehicle unit, related to a place where a driver begins or ends a daily work period (Annex 1B requirement 087 and Annex 1C requirement 108 and 110).
                        Text of image

                           VuPlaceDailyWorkPeriodRecord ::= SEQUENCE {
                           fullCardNumberAndGeneration FullCardNumberAndGeneration,
                           placeRecord PlaceRecord
                           }

                        Instead of fullCardNumber, the generation 2 data structure makes use of the following data element:

                           fullCardNumberAndGeneration is the type of card, its issuing Member State, its card number and generation as stored in the card.

                  2.220.   VuPlaceDailyWorkPeriodRecordArray

            Generation 2:
            Information, stored in a vehicle unit, related to places where drivers begin or end a daily work period (Annex 1C requirement 108 and 110).

            Text of image

               VuPlaceDailyWorkPeriodRecordArray ::= SEQUENCE {
               recordType RecordType,
               recordSize INTEGER(1..65535),
               noOfRecords INTEGER(0..65535),
               records SET SIZE(noOfRecords) OF VuPlaceDailyWorkPeriodRecord
               }

               recordType denotes the type of the record (VuPlaceDailyWorkPeriodRecord). Value Assignment: See RecordType

               recordSize is the size of the VuPlaceDailyWorkPeriodRecord in bytes.

               noOfRecords is the number of records in the set records.

               records is a set of place related records.
            2.221.   VuPrivateKey

            Generation 1:
            The private key of a vehicle unit.

            Text of image

               VuPrivateKey ::= RSAKeyPrivateExponent

            2.222.   VuPublicKey

            Generation 1:
            The public key of a vehicle unit.

            Text of image

               VuPublicKey ::= PublicKey

            2.223.   VuSerialNumber

            Serial number of the vehicle unit (Annex 1B requirement 075 and Annex 1C requirement 93).

            Text of image

               VuSerialNumber ::= ExtendedSerialNumber

            2.224.   VuSoftInstallationDate

            Date of installation of the vehicle unit software version.

            Text of image

               VuSoftInstallationDate ::= TimeReal

               Value assignment: Unspecified.
            2.225.   VuSoftwareIdentification

            Information, stored in a vehicle unit, related to the software installed.

            Text of image

               VuSoftwareIdentification ::= SEQUENCE {
               vuSoftwareVersion VuSoftwareVersion,
               vuSoftInstallationDate VuSoftInstallationDate
               }

               vuSoftwareVersion is the software version number of the Vehicle Unit.

               vuSoftInstallationDate is the software version installation date.
            2.226.   VuSoftwareVersion

            Software version number of the vehicle unit.

            Text of image

               VuSoftwareVersion ::= IA5String(SIZE(4))

               Value assignment: Unspecified.
            2.227.   VuSpecificConditionData

            Generation 1:
            Information, stored in a vehicle unit, related to specific conditions.

            Text of image

               VuSpecificConditionData ::= SEQUENCE {
               noOfSpecificConditionRecords INTEGER(0..216-1)
               specificConditionRecords SET SIZE (noOfSpecificConditionRecords) OF SpecificConditionRecord
               }

               noOfSpecificConditionRecords is the number of records listed in the specificConditionRecords set.

               specificConditionRecords is a set of specific conditions related records.
            2.228.   VuSpecificConditionRecordArray

            Generation 2:
            Information, stored in a vehicle unit, related to specific conditions (Annex 1C requirement 130).

            Text of image

               VuSpecificConditionRecordArray ::= SEQUENCE {
               recordType RecordType,
               recordSize INTEGER(1..65535),
               noOfRecords INTEGER(0..65535),
               records SET SIZE(noOfRecords) OF SpecificConditionRecord
               }

               recordType denotes the type of the record (SpecificConditionRecord). Value Assignment: See RecordType

               recordSize is the size of the SpecificConditionRecord in bytes.

               noOfRecords is the number of records in the set records.

               records is a set of specific conditions related records.
            2.229.   VuTimeAdjustmentData

            Generation 1:
            Information, stored in a vehicle unit, related to time adjustments performed outside the frame of a regular calibration (Annex 1B requirement 101).

            Text of image

               VuTimeAdjustmentData ::= SEQUENCE {
               noOfVuTimeAdjRecords INTEGER(0..6),
               vuTimeAdjustmentRecords SET SIZE(noOfVuTimeAdjRecords) OF VuTimeAdjustmentRecord
               }

               noOfVuTimeAdjRecords is the number of records in vuTimeAdjustmentRecords.

               vuTimeAdjustmentRecords is a set of time adjustment records.
            2.230.   VuTimeAdjustmentGNSSRecord

            Generation 2:
            Information, stored in a vehicle unit, related to a time adjustment based on time data from GNSS (Annex 1C requirement 124 and 125).

            Text of image

               VuTimeAdjustmentGNSSRecord ::= SEQUENCE {
               oldTimeValue TimeReal,
               newTimeValue TimeReal
               }

               oldTimeValue, newTimeValue are the old and new values of date and time.
            2.231.   VuTimeAdjustmentGNSSRecordArray

            Generation 2:
            Information, stored in a vehicle unit, related to to a time adjustment performed bybased on time data from GNSS (Annex 1C requirement 124 and 125).

            Text of image

               VuTimeAdjustmentGNSSRecordArray ::= SEQUENCE {
               recordType RecordType,
               recordSize INTEGER(1..65535),
               noOfRecords INTEGER(0..65535),
               records SET SIZE(noOfRecords) OF VuTimeAdjustmentGNSSRecord
               }

               recordType denotes the type of the record (VuTimeAdjustmentGNSSRecord). Value Assignment: See RecordType

               recordSize is the size of the VuTimeAdjustmentGNSSRecord in bytes.

               noOfRecords is the number of records in the set records.

               records is a set of GNSS time adjustment records.
            2.232.   VuTimeAdjustmentRecord

            Information, stored in a vehicle unit, related a time adjustment performed outside the frame of a regular calibration (Annex 1B requirement 101 and Annex 1C requirement 124 and 125).

                        Generation 1:
                        Text of image

                           VuTimeAdjustmentRecord ::= SEQUENCE {
                           oldTimeValue TimeReal,
                           newTimeValue TimeReal,
                           workshopName Name,
                           workshopAddress Address,
                           workshopCardNumber FullCardNumber
                           }

                           oldTimeValue, newTimeValue are the old and new values of date and time.

                           workshopName, workshopAddress are the workshop name and address.

                           workshopCardNumber identifies the workshop card used to perform the time adjustment.

                        Generation 2:
                        Text of image

                           VuTimeAdjustmentRecord ::= SEQUENCE {
                           oldTimeValue TimeReal,
                           newTimeValue TimeReal,
                           workshopName Name,
                           workshopAddress Address,
                           workshopCardNumberAndGeneration FullCardNumberAndGeneration
                           }

                        Instead of workshopCardNumber the generation 2 data structure makes use of the following data element.

                           workshopCardNumberAndGeneration identifies the workshop card including its generation used to perform the time adjustment.

                  2.233.   VuTimeAdjustmentRecordArray

            Generation 2:
            Information, stored in a vehicle unit, related to time adjustments performed outside the frame of a regular calibration (Annex 1C requirement 124 and 125).

            Text of image

               VuTimeAdjustmentRecordArray ::= SEQUENCE {
               recordType RecordType,
               recordSize INTEGER(1..65535),
               noOfRecords INTEGER(0..65535),
               records SET SIZE(noOfRecords) OF
               VuTimeAdjustmentRecord
               }

               recordType denotes the type of the record (VuTimeAdjustmentRecord). Value Assignment: See RecordType

               recordSize is the size of the VuTimeAdjustmentRecord in bytes.

               noOfRecords is the number of records in the set records.

               records is a set of time adjustment records.
            2.234.   WorkshopCardApplicationIdentification

            Information, stored in a workshop card related to the identification of the application of the card (Annex 1C requirement 307 and 330).

                        Generation 1:
                        Text of image

                           WorkshopCardApplicationIdentification ::= SEQUENCE {
                           typeOfTachographCardId EquipmentType,
                           cardStructureVersion CardStructureVersion,
                           noOfEventsPerType NoOfEventsPerType,
                           noOfFaultsPerType NoOfFaultsPerType,
                           activityStructureLength CardActivityLengthRange,
                           noOfCardVehicleRecords NoOfCardVehicleRecords,
                           noOfCardPlaceRecords NoOfCardPlaceRecords,
                           noOfCalibrationRecords NoOfCalibrationRecords
                           }

                           typeOfTachographCardId is specifying the implemented type of card.

                           cardStructureVersion is specifying the the version of the structure that is implemented in the card.

                           noOfEventsPerType is the number of events per type of event the card can record.

                           noOfFaultsPerType is the number of faults per type of fault the card can record.

                           activityStructureLength indicates the number of bytes available for storing activity records.

                           noOfCardVehicleRecords is the number of vehicle records the card can contain.

                           noOfCardPlaceRecords is the number of places the card can record.

                           noOfCalibrationRecords is the number of calibration records the card can store.

                        Generation 2:
                        Text of image

                           WorkshopCardApplicationIdentification ::= SEQUENCE {
                           typeOfTachographCardId EquipmentType,
                           cardStructureVersion CardStructureVersion,
                           noOfEventsPerType NoOfEventsPerType,
                           noOfFaultsPerType NoOfFaultsPerType,
                           activityStructureLength CardActivityLengthRange,
                           noOfCardVehicleRecords NoOfCardVehicleRecords,
                           noOfCardPlaceRecords NoOfCardPlaceRecords,
                           noOfCalibrationRecords NoOfCalibrationRecords,
                           noOfGNSSCDRecords NoOfGNSSCDRecords,
                           noOfSpecificConditionRecords NoOfSpecificConditionRecords
                           }

                        In addition to generation 1 the following data elements are used:

                                       noOfGNSSCDRecords is the number of GNSS continuous driving records the card can store.

                                       noOfSpecificConditionRecords is the number of specific condition records the card can store.

                  2.235.   WorkshopCardCalibrationData

            Information, stored in a workshop card, related to workshop activity performed with the card (Annex 1C requirements 314, 316, 337, and 339).

            Text of image

               WorkshopCardCalibrationData ::= SEQUENCE {
               calibrationTotalNumber INTEGER(0 .. 216-1),
               calibrationPointerNewestRecord INTEGER(0 .. NoOfCalibrationRecords-1),
               calibrationRecords SET SIZE(NoOfCalibrationRecords) OF WorkshopCardCalibrationRecord
               }

               calibrationTotalNumber is the total number of calibrations performed with the card.

               calibrationPointerNewestRecord is the index of the last updated calibration record.

               Value assignment: Number corresponding to the numerator of the calibration record, beginning with ‘0’ for the first occurrence of the calibration records in the structure.

               calibrationRecords is the set of records containing calibration and/or time adjustment information.
            2.236.   WorkshopCardCalibrationRecord

            Information, stored in a workshop card, related to a calibration performed with the card (Annex 1C requirement 314 and 337).

                        Generation 1:
                        Text of image

                           WorkshopCardCalibrationRecord ::= SEQUENCE {
                           calibrationPurpose CalibrationPurpose,
                           vehicleIdentificationNumber VehicleIdentificationNumber,
                           vehicleRegistration VehicleRegistrationIdentification,
                           wVehicleCharacteristicConstant W-VehicleCharacteristicConstant,
                           kConstantOfRecordingEquipment K-ConstantOfRecordingEquipment,
                           lTyreCircumference L-TyreCircumference,
                           tyreSize TyreSize,
                           authorisedSpeed SpeedAuthorised,
                           oldOdometerValue OdometerShort,
                           newOdometerValue OdometerShort,
                           oldTimeValue TimeReal,
                           newTimeValue TimeReal,
                           nextCalibrationDate TimeReal,
                           vuPartNumber VuPartNumber,
                           vuSerialNumber VuSerialNumber,
                           sensorSerialNumber SensorSerialNumber
                           }

                           calibrationPurpose is the purpose of the calibration.

                           vehicleIdentificationNumber is the VIN.

                           vehicleRegistration contains the VRN and registering Member State.

                           wVehicleCharacteristicConstant is the characteristic coefficient of the vehicle.

                           kConstantOfRecordingEquipment is the constant of the recording equipment.

                           lTyreCircumference is the effective circumference of the wheel tyres.

                           tyreSize is the designation of the dimensions of the tyres mounted on the vehicle.

                           authorisedSpeed is the maximum authorised speed of the vehicle.

                           oldOdometerValue, newOdometerValue are the old and new values of the odometer.

                           oldTimeValue, newTimeValue are the old and new values of date and time.

                           nextCalibrationDate is the date of the next calibration of the type specified in CalibrationPurpose to be carried out by the authorised inspection authority.

                           vuPartNumber, vuSerialNumber and sensorSerialNumber are the data elements for recording equipment identification.

                        Generation 2:
                        Text of image

                           WorkshopCardCalibrationRecord ::= SEQUENCE {
                           calibrationPurpose CalibrationPurpose,
                           vehicleIdentificationNumber VehicleIdentificationNumber,
                           vehicleRegistration VehicleRegistrationIdentification,
                           wVehicleCharacteristicConstant W-VehicleCharacteristicConstant,
                           kConstantOfRecordingEquipment K-ConstantOfRecordingEquipment,
                           lTyreCircumference L-TyreCircumference,
                           tyreSize TyreSize,
                           authorisedSpeed SpeedAuthorised,
                           oldOdometerValue OdometerShort,
                           newOdometerValue OdometerShort,
                           oldTimeValue TimeReal,
                           newTimeValue TimeReal,
                           nextCalibrationDate TimeReal,
                           vuPartNumber VuPartNumber,
                           vuSerialNumber VuSerialNumber,
                           sensorSerialNumber SensorSerialNumber,
                           sensorGNSSSerialNumber SensorGNSSSerialNumber,
                           rcmSerialNumber RemoteCommunicationModuleSerialNumber,
                           sealDataCard SealDataCard
                           }

                        In addition to generation 1 the following data elements are used:

                                       sensorGNSSSerialNumber which identifies an external GNSS facility.

                                       rcmSerialNumber which identifies a Remote Communication Module.

                                       sealDataCard gives information about the seals that are attached to different components of the vehicle.

                  2.237.   WorkshopCardHolderIdentification

            Information, stored in a workshop card, related to the identification of the cardholder (Annex 1C requirement 311 and 334).

            Text of image

               WorkshopCardHolderIdentification ::= SEQUENCE {
               workshopName Name,
               workshopAddress Address,
               cardHolderName HolderName,
               cardHolderPreferredLanguage Language
               }

               workshopName is name of the workshop of the card holder.

               workshopAddress is the address of the workshop of the card holder.

               cardHolderName is the name and first name(s) of the holder (e.g. the name of the mechanic).

               cardHolderPreferredLanguage is the preferred language of the card holder.
            2.238.   WorkshopCardPIN

            Personal identification number of the Workshop Card (Annex 1C requirement 309 and 332).

            Text of image

               WorkshopCardPIN ::= IA5String(SIZE(8))

               Value assignment: The PIN known to the cardholder, right padded with ‘FF’ bytes up to 8 bytes.
            2.239.   W-VehicleCharacteristicConstant

            Characteristic coefficient of the vehicle (definition k)).

            Text of image

               W-VehicleCharacteristicConstant ::= INTEGER(0..216-1))

               Value assignment: Impulses per kilometer in the operating range 0 to 64 255 pulses/km.
            2.240.   VuPowerSupplyInterruptionRecord

            Generation 2:
            Information, stored in a vehicle unit, related to Power Supply Interruption events (Annex 1C requirement 117).

            Text of image

               VuPowerSupplyInterruptionRecord ::= SEQUENCE {
               eventType EventFaultType,
               eventRecordPurpose EventFaultRecordPurpose,
               eventBeginTime TimeReal,
               eventEndTime TimeReal,
               cardNumberAndGenDriverSlotBegin FullCardNumberAndGeneration,
               cardNumberAndGenDriverSlotEnd FullCardNumberAndGeneration,
               cardNumberAndGenCodriverSlotBegin FullCardNumberAndGeneration,
               cardNumberAndGenCodriverSlotEnd FullCardNumberAndGeneration,
               similarEventsNumber SimilarEventsNumber
               }

               eventType is the type of the event.

               eventRecordPurpose is the purpose for which this event has been recorded.

               eventBeginTime is the date and time of beginning of event.

               eventEndTime is the date and time of end of event.

               cardNumberAndGenDriverSlotBegin identifies the card including its generation inserted in the driver slot at the beginning of the event.

               cardNumberAndGenDriverSlotEnd identifies the card including its generation inserted in the driver slot at the end of the event.

               cardNumberAndGenCodriverSlotBegin identifies the card including its generation inserted in the co-driver slot at the beginning of the event.

               cardNumberAndGenCodriverSlotEnd identifies the card including its generation inserted in the co-driver slot at the end of the event.

               similarEventsNumber is the number of similar events that day.
            2.241.   VuPowerSupplyInterruptionRecordArray

            Generation 2:
            Information, stored in a vehicle unit, related to Power Supply Interruption events (Annex 1C requirement 117).

            Text of image

               VuPowerSupplyInterruptionRecordArray ::= SEQUENCE {
               recordType RecordType,
               recordSize INTEGER(1..65535),
               noOfRecords INTEGER(0..65535),
               records SET SIZE(noOfRecords) OF VuPowerSupplyInterruptionRecord
               }

               recordType denotes the type of the record (VuPowerSupplyInterruptionRecord). Value Assignment: See RecordType

               recordSize is the size of the VuPowerSupplyInterruptionRecord in bytes.

               noOfRecords is the number of records in the set records.

               records is a set of power supply interruption events records.
            2.242.   VuSensorExternalGNSSCoupledRecordArray

            Generation 2:
            A set of SensorExternalGNSSCoupledRecord plus metadata used in the download protocol.

            Text of image

               VuSensorExternalGNSSCoupledRecordArray ::= SEQUENCE {
               recordType RecordType,
               recordSize INTEGER(1..65535),
               noOfRecords INTEGER(0..65535),
               records SET SIZE(noOfRecords) OF SensorExternalGNSSCoupledRecord
               }

               recordType denotes the type of the record (SensorExternalGNSSCoupledRecord). Value Assignment: See RecordType

               recordSize is the size of the SensorExternalGNSSCoupledRecord in bytes.

               noOfRecords is the number of records in the set records.

               records is a set of Sensor External GNSS Coupled records.
            2.243.   VuSensorPairedRecordArray

            Generation 2:
            A set of SensorPairedRecord plus metadata used in the download protocol.

            Text of image

               VuSensorPairedRecordArray ::= SEQUENCE {
               recordType RecordType,
               recordSize INTEGER(1..65535),
               noOfRecords INTEGER(0..65535),
               records SET SIZE(noOfRecords) OF SensorPairedRecord
               }

               recordType denotes the type of the record (SensorPairedRecord). Value Assignment: See RecordType

               recordSize is the size of the SensorPairedRecord in bytes.

               noOfRecords is the number of records in the set records.

               records is a set of sensor paired records.
            3.   VALUE AND SIZE RANGE DEFINITIONS
            Definition of variable values used for definitions in paragraph 2.

            Text of image

               TimeRealRange ::= 232-1

            4.   CHARACTER SETS
            IA5Strings use the ASCII characters as defined by ISO/IEC 8824-1. For readability and for easy referencing the value assignment is given below. The ISO/IEC 8824-1 supersedes this informative note in case of discrepancy.

            Text of image

               ! " # $ % & ' ( ) * + , - . / 0 1 2 3 4 5 6 7 8 9 : ; < = > ?
               @ A B C D E F G H I J K L M N O P Q R S T U V W X Y Z [ \ ] ^ _
               ` a b c d e f g h i j k l m n o p q r s t u v w x y z { | } ~

                        Other character strings (Address, Name, VehicleRegistrationNumber) use, in addition, characters from the decimal character code range 161 — 255 of the following 8-bit, standard character sets, specified by the Code Page number:
                        Standard Character Set

                        Code Page
                        (Decimal)

                        ISO/IEC 8859-1 Latin-1 Western European

                        1

                        ISO/IEC 8859-2 Latin-2 Central European

                        2

                        ISO/IEC 8859-3 Latin-3 South European

                        3

                        ISO/IEC 8859-5 Latin / Cyrillic

                        5

                        ISO/IEC 8859-7 Latin / Greek

                        7

                        ISO/IEC 8859-9 Latin-5 Turkish

                        9

                        ISO/IEC 8859-13 Latin-7 Baltic Rim

                        13

                        ISO/IEC 8859-15 Latin-9

                        15

                        ISO/IEC 8859-16 Latin-10 South Eastern European

                        16

                        KOI8-R Latin / Cyrillic

                        80

                        KOI8-U Latin / Cyrillic

                        85

                  5.   ENCODING
            When encoded with ASN.1 encoding rules, all data types defined shall be encoded according to ISO/IEC 8825-2, aligned variant.
            6.   OBJECT IDENTIFIERS UND APPLICATION IDENTIFIERS
            6.1.   Object Identifiers

            The Object Identifiers (OIDs) listed in this chapter are only relevant for generation 2. These OIDs are specified in TR-03110-3 and repeated here for the sake of completeness. These OIDs are contained in the subtree of bsi-de:

            Text of image

               bsi-de OBJECT IDENTIFIER ::= {
               itu-t(0) identified-organization(4) etsi(0)
               reserved(127) etsi-identified-organization(0) 7
               }

               VU Authentication protocol identifiers

            Text of image

               id-TA OBJECT IDENTIFIER ::= {bsi-de protocols(2) smartcard(2) 2}
               id-TA-ECDSA OBJECT IDENTIFIER ::= {id-TA 2}
               id-TA-ECDSA-SHA-256 OBJECT IDENTIFIER ::= {id-TA-ECDSA 3}
               id-TA-ECDSA-SHA-384 OBJECT IDENTIFIER ::= {id-TA-ECDSA 4}
               id-TA-ECDSA-SHA-512 OBJECT IDENTIFIER ::= {id-TA-ECDSA 5}

            Example: Suppose VU Authentication is to be done with SHA-384, then the object identifier to use is (in ASN.1 notation) Text of image

               bsi-de protocols(2) smartcard(2) 2 2 4
            . The value of this object identifier in dot notation is Text of image

               0.4.0.127.0.7.2.2.2.2.4
            .

                        Dot notation

                        Byte notation

                        ‘04 00 7F 00 07 02 02 02 02 03’

                        ‘04 00 7F 00 07 02 02 02 02 04’

                        ‘04 00 7F 00 07 02 02 02 02 05’

               Chip Authentication protocol identifiers

            Text of image

               id-CA OBJECT IDENTIFIER ::= {bsi-de protocols(2) smartcard(2) 3}
               id-CA-ECDH OBJECT IDENTIFIER ::= {id-CA 2}
               id-CA-ECDH-AES-CBC-CMAC-128 OBJECT IDENTIFIER ::= {id-CA-ECDH 2}
               id-CA-ECDH-AES-CBC-CMAC-192 OBJECT IDENTIFIER ::= {id-CA-ECDH 3}
               id-CA-ECDH-AES-CBC-CMAC-256 OBJECT IDENTIFIER ::= {id-CA-ECDH 4}

            Example: Suppose Chip Authentication is to be done by using the ECDH algorithm, resulting in an AES session key length of 128 bits. This session key will subsequently be used in the CBC mode of operation to ensure data confidentiality and with the CMAC algorithm to ensure data authenticity. Therefore, the object identifier to use is (in ASN.1 notation) Text of image

               bsi-de protocols(2) smartcard(2) 3 2 2
            . The value of this object identifier in dot notation is Text of image

               0.4.0.127.0.7.2.2.3.2.2
            .

                        Dot notation

                        Byte notation

                        ‘04 00 7F 00 07 02 02 03 02 02’

                        ‘04 00 7F 00 07 02 02 03 02 03’

                        ‘04 00 7F 00 07 02 02 03 02 04’

                  6.2.   Application Identifiers

            Generation 2:
            The Application Identifier (AID) for the External GNSS Facility (Generation 2) is given by ‘FF 44 54 45 47 4D’. This is a proprietary AID according to ISO/IEC 7816-4.

               Note: The last 5 bytes encode DTEGM for smart Tachograph External GNSS Facility.
            The Application Identifier for the generation 2 tachograph card application is given by ‘FF 53 4D 52 44 54’. This is a proprietary AID according to ISO/IEC 7816-4.

            Appendix 2

               TACHOGRAPH CARDS SPECIFICATION

            TABLE OF CONTENT

                        1.

                     INTRODUCTION
                     175

                        1.1.

                     Abbreviations
                     175

                        1.2.

                     References
                     176

                        2.

                     ELECTRICAL AND PHYSICAL CHARACTERISTICS
                     176

                        2.1.

                     Supply Voltage and Current Consumption
                     177

                        2.2.

                     Programming Voltage Vpp

                     177

                        2.3.

                     Clock generation and Frequency
                     177

                        2.4.

                     I/O Contact
                     177

                        2.5.

                     States of the Card
                     177

                        3.

                     HARDWARE AND COMMUNICATION
                     177

                        3.1.

                     Introduction
                     177

                        3.2.

                     Transmission Protocol
                     178

                        3.2.1

                     Protocols
                     178

                        3.2.2

                     ATR
                     179

                        3.2.3

                     PTS
                     179

                        3.3.

                     Access Rules
                     180

                        3.4.

                     Commands and error codes overview
                     183

                        3.5.

                     Command descriptions
                     185

                        3.5.1

                     SELECT
                     186

                        3.5.2

                     READ BINARY
                     187

                        3.5.3

                     UPDATE BINARY
                     194

                        3.5.4

                     GET CHALLENGE
                     200

                        3.5.5

                     VERIFY
                     200

                        3.5.6

                     GET RESPONSE
                     202

                        3.5.7

                     PSO: VERIFY CERTIFICATE
                     202

                        3.5.8

                     INTERNAL AUTHENTICATE
                     204

                        3.5.9

                     EXTERNAL AUTHENTICATE
                     205

                        3.5.10

                     GENERAL AUTHENTICATE
                     206

                        3.5.11

                     MANAGE SECURITY ENVIRONMENT
                     207

                        3.5.12

                     PSO: HASH
                     210

                        3.5.13

                     PERFORM HASH OF FILE
                     211

                        3.5.14

                     PSO: COMPUTE DIGITAL SIGNATURE
                     212

                        3.5.15

                     PSO: VERIFY DIGITAL SIGNATURE
                     213

                        3.5.16

                     PROCESS DSRC MESSAGE
                     214

                        4.

                     TACHOGRAPH CARDS STRUCTURE
                     216

                        4.1.

                     Master File MF
                     216

                        4.2.

                     Driver card applications
                     217

                        4.2.1

                     Driver card application generation 1
                     217

                        4.2.2

                     Driver card application generation 2
                     221

                        4.3.

                     Workshop card applications
                     224

                        4.3.1

                     Workshop card application generation 1
                     224

                        4.3.2

                     Workshop card application generation 2
                     228

                        4.4.

                     Control card applications
                     233

                        4.4.1

                     Control Card application generation 1
                     233

                        4.4.2

                     Control card application generation 2
                     235

                        4.5.

                     Company card applications
                     237

                        4.5.1

                     Company card application generation 1
                     237

                        4.5.2

                     Company card application generation 2
                     238
                  1.   INTRODUCTION
            1.1.   Abbreviations

            For the purpose of this appendix, the following abbreviations apply.

                        AC

                        Access conditions

                        AES

                        Advanced Encryption Standard

                        AID

                        Application Identifier

                        ALW

                        Always

                        APDU

                        Application Protocol Data Unit (structure of a command)

                        ATR

                        Answer To Reset

                        AUT

                        Authenticated.

                        C6, C7

                        Contacts No 6 and 7 of the card as described in ISO/IEC 7816-2

                        cc

                        clock cycles

                        CHV

                        Card holder Verification Information

                        CLA

                        Class byte of an APDU command

                        DSRC

                        Dedicated Short Range Communication

                        DF

                        Dedicated File. A DF can contain other files (EF or DF)

                        ECC

                        Elliptic Curve Cryptography

                        EF

                        Elementary File

                        etu

                        elementary time unit

                        G1

                        Generation 1

                        G2

                        Generation 2

                        IC

                        Integrated Circuit

                        ICC

                        Integrated Circuit Card

                        ID

                        Identifier

                        IFD

                        Interface Device

                        IFS

                        Information Field Size

                        IFSC

                        Information Field Size for the card

                        IFSD

                        Information Field Size Device (for the Terminal)

                        INS

                        Instruction byte of an APDU command

                        Lc

                        Length of the input data for a APDU command

                        Le

                        Length of the expected data (output data for a command)

                        MF

                        Master File (root DF)

                        NAD

                        Node Address used in T=1 protocol

                        NEV

                        Never

                        P1-P2

                        Parameter bytes

                        PIN

                        Personal Identification Number

                        PRO SM

                        Protected with secure messaging

                        PTS

                        Protocol Transmission Selection

                        RFU

                        Reserved for Future Use

                        RST

                        Reset (of the card)

                        SFID

                        Short EF Identifier

                        SM

                        Secure Messaging

                        SW1-SW2

                        Status bytes

                        TS

                        Initial ATR character

                        VPP

                        Programming Voltage

                        VU

                        Vehicle Unit

                        XXh

                        Value XX in hexadecimal notation

                        ‘XXh’

                        Value XX in hexadecimal notation

                        ||

                        Concatenation symbol 03||04=0304

                  1.2.   References

            The following references are used in this Appendix:

                        ISO/IEC 7816-2

                        Identification cards — Integrated circuit cards — Part 2: Dimensions and location of the contacts. ISO/IEC 7816-2:2007.

                        ISO/IEC 7816-3

                        Identification cards — Integrated circuit cards — Part 3: Electrical interface and transmission protocols. ISO/IEC 7816-3:2006.

                        ISO/IEC 7816-4

                        Identification cards — Integrated circuit cards — Part 4: Organization, security and commands for interchange. ISO/IEC 7816-4:2013 + Cor 1: 2014.

                        ISO/IEC 7816-6

                        Identification cards — Integrated circuit cards — Part 6: Interindustry data elements for interchange. ISO/IEC 7816-6:2004 + Cor 1: 2006.

                        ISO/IEC 7816-8

                        Identification cards — Integrated circuit cards — Part 8: Commands for security operations. ISO/IEC 7816-8:2004.

                        ISO/IEC 9797-2

                        Information technology — Security techniques — Message Authentication Codes (MACs) — Part 2: Mechanisms using a dedicated hash-function. ISO/IEC 9797-2:2011

                  2.   ELECTRICAL AND PHYSICAL CHARACTERISTICS

                        TCS_01

                        All electronic signals shall be in accordance with ISO/IEC 7816-3 unless specified otherwise.

                        TCS_02

                        The location and dimensions of the card contacts shall comply with the ISO/IEC 7816-2.

                  2.1.   Supply Voltage and Current Consumption

                        TCS_03

                        The card shall work according to specifications within the consumption limits specified in ISO/IEC 7816-3.

                        TCS_04

                        The card shall work with Vcc = 3V (± 0,3V) or with Vcc = 5V (± 0,5V).
                        Voltage selection shall be performed according to ISO/IEC 7816-3.

                  2.2.   Programming Voltage Vpp

                        TCS_05

                        The card shall not require a programming voltage at pin C6. It is expected that pin C6 is not connected in an IFD. Contact C6 may be connected to Vcc in the card but shall not be connected to ground. This voltage should not be interpreted in any case.

                  2.3.   Clock generation and Frequency

                        TCS_06

                        The card shall operate within a frequency range of 1 to 5 MHz and may support higher frequencies. Within one card session the clock frequency may vary ± 2 %. The clock frequency is generated by the Vehicle Unit and not the card itself. The duty cycle may vary between 40 and 60 %.

                        TCS_07

                        Under conditions contained into the card file EF ICC, the external clock can be stopped. The first byte of the EF ICC file body codes the Clockstop mode conditions:

                                    Low

                                    High

                                    Bit 3

                                    Bit 2

                                    Bit 1

                                    0

                                    0

                                    1

                                    Clockstop allowed, no preferred level

                                    0

                                    1

                                    1

                                    Clockstop allowed, high level preferred

                                    1

                                    0

                                    1

                                    Clockstop allowed, low level preferred

                                    0

                                    0

                                    0

                                    Clockstop not allowed

                                    0

                                    1

                                    0

                                    Clockstop only allowed on high level

                                    1

                                    0

                                    0

                                    Clockstop only allowed on low level

                              Bits 4 to 8 are not used.

                  2.4.   I/O Contact

                        TCS_08

                        The I/O contact C7 is used to receive data from and to transmit data to the IFD. During operation only either the card or the IFD shall be in transmit mode. Should both units be in transmit mode no damage shall occur to the card. Unless transmitting, the card shall enter the reception mode.

                  2.5.   States of the Card

                        TCS_09

                        The card works in two states while the supply voltage is applied:

                                    Operation state while executing commands or interfacing with Digital Unit,

                                    Idle state at all other times; in this state all data shall be retained by the card.

                  3.   HARDWARE AND COMMUNICATION
            3.1.   Introduction

            This paragraph describes the minimum functionality required by Tachograph cards and VUs to ensure correct operation and interoperability.
            Tachograph cards are as compliant as possible with the available ISO/IEC applicable norms (especially ISO/IEC 7816). However, commands and protocols are fully described in order to specify some restricted usage or some differences if they exist. The commands specified are fully compliant with the referred norms except where indicated.
            3.2.   Transmission Protocol

                        TCS_10

                        The Transmission protocol shall be compliant with ISO/IEC 7816-3 for T = 0 and T = 1. In particular, the VU shall recognise waiting time extensions sent by the card.

                  3.2.1   Protocols

                        TCS_11

                        The card shall provide both protocol T=0 and protocol T=1. In addition the card may support further contact-oriented protocols.

                        TCS_12

                           T=0 is the default protocol, a PTS command is therefore necessary to change the protocol to T=1.

                        TCS_13

                        Devices shall support direct convention in both protocols: the direct convention is hence mandatory for the card.

                        TCS_14

                        The Information Field Size Card byte shall be presented at the ATR in character TA3. This value shall be at least ‘F0h’ (=240 bytes).

                  The following restrictions apply to the protocols:

                        TCS_15

                        T=0

                                    —

                                    The interface device shall support an answer on I/O after the rising edge of the signal on RST from 400 cc.

                                    —

                                    The interface device shall be able to read characters separated with 12 etu.

                                    —

                                    The interface device shall read an erroneous character and its repetition if separated with 13 etu. If an erroneous character is detected, the Error signal on I/O can occur between 1 etu and 2 etu. The device shall support a 1 etu delay.

                                    —

                                    The interface device shall accept a 33 bytes ATR (TS+32)

                                    —

                                    If TC1 is present in the ATR, the Extra Guard Time shall be present for characters sent by the interface device although characters sent by the card can still be separated with 12 etu. This is also true for the ACK character sent by the card after a P3 character emitted by the interface device.

                                    —

                                    The interface device shall take into account a NUL character emitted by the card.

                                    —

                                    The interface device shall accept the complementary mode for ACK.

                                    —

                                    The get-response command cannot be used in chaining mode to get a data which length could exceed 255 bytes.

                        TCS_16

                        T=1

                                    —

                                    NAD byte: not used (NAD shall be set to ‘00’).

                                    —

                                    S-block ABORT: not used.

                                    —

                                    S-block VPP state error: not used.

                                    —

                                    The total chaining length for a data field will not exceed 255 bytes (to be ensured by the IFD).

                                    —

                                    The Information Field Size Device (IFSD) shall be indicated by the IFD immediately after the ATR: the IFD shall transmit the S-Block IFS request after the ATR and the card shall send back S-Block IFS. The recommended value for IFSD is 254 bytes.

                                    —

                                    The card will not ask for an IFS readjustment.

                  3.2.2   ATR

                        TCS_17

                        The device checks ATR bytes, according to ISO/IEC 7816-3. No verification shall be done on ATR Historical Characters.
                        Example of Basic Biprotocol ATR according to ISO/IEC 7816-3

                                    Character

                                    Value

                                    Remarks

                                    TS

                                    ‘3Bh’

                                    Indicates direct convention.

                                    T0

                                    ‘85h’

                                    TD1 present; 5 historical bytes are presents.

                                    TD1

                                    ‘80h’

                                    TD2 present; T=0 to be used

                                    TD2

                                    ‘11h’

                                    TA3 present; T=1 to be used

                                    TA3

                                    ‘XXh’ (at least ‘F0h’)

                                    Information Field Size Card ( IFSC)

                                    TH1 to TH5

                                    ‘XXh’

                                    Historical characters

                                    TCK

                                    ‘XXh’

                                    Check Character (exclusive OR)

                        TCS_18

                        After the Answer To Reset (ATR), the Master File (MF) is implicitly selected and becomes the Current Directory.

                  3.2.3   PTS

                        TCS_19

                        The default Protocol is T=0. To set the T=1 protocol, a PTS (also known as PPS) must be sent to the card by the device.

                        TCS_20

                        As both T=0 and T=1 protocols are mandatory for the card, the basic PTS for protocol switching is mandatory for the card.
                        The PTS can be used, as indicated in ISO/IEC 7816-3, to switch to higher baud rates than the default one proposed by the card in the ATR if any (TA(1) byte).
                        Higher baud rates are optional for the card.

                        TCS_21

                        If no other baud rate than the default one are supported (or if the selected baud rate is not supported), the card shall respond to the PTS correctly according to ISO/IEC 7816-3 by omitting the PPS1 byte.
                        Examples of basic PTS for protocol selection are the following:

                                    Character

                                    Value

                                    Remarks

                                    PPSS

                                    ‘FFh’

                                    The Initiate Character.

                                    PPS0

                                    ‘00h’ or ‘01h’

                                    PPS1 to PPS3 are not present; ‘00h’ to select T0, ‘01h’ to select T1.

                                    PK

                                    ‘XXh’

                                                Check Character

                                                :

                                                ‘XXh’ = ‘FFh’ if PPS0 = ‘00h’,
                                                ‘XXh’ = ‘FEh’ if PPS0 = ‘01h’.

                  3.3.   Access Rules

                        TCS_22

                        An access rule specifies for an access mode, i.e. command, the corresponding security conditions. If these security conditions are fulfilled the corresponding command is processed.

                        TCS_23

                        The following security conditions are used for the tachograph card:

                                    Abbreviation

                                    Meaning

                                    ALW

                                    The action is always possible and can be executed without any restriction. Command and response APDU are sent in plain text, i.e. without secure messaging.

                                    NEV

                                    The action is never possible.

                                    PLAIN-C

                                    The command APDU is sent in plain, i.e. without secure messaging.

                                    PWD

                                    The action may only be executed if the workshop card PIN has been successfully verified, i.e. if the card internal security status ‘PIN_Verified’ is set. The command must be sent without secure messaging.

                                    EXT-AUT-G1

                                    The action may only be executed if the External Authenticate command for the generation 1 authentication (see also Appendix 11 Part A) has been successfully performed.

                                    SM-MAC-G1

                                    The APDU (command and response) must be applied with generation 1 secure messaging in authentication-only mode (see Appendix 11 Part A).

                                    SM-C-MAC-G1

                                    The command APDU must be applied with generation 1 secure messaging in authentication only mode (see Appendix 11 Part A).

                                    SM-R-ENC-G1

                                    The response APDU must be applied with generation 1 secure messaging in encryption mode (see Appendix 11 Part A), i.e. no message authentication code is returned.

                                    SM-R-ENC-MAC-G1

                                    The response APDU must be applied with generation 1 secure messaging in encrypt-then-authenticate mode (see Appendix 11 Part A).

                                    SM-MAC-G2

                                    The APDU (command and response) must be applied with generation 2 secure messaging in authentication-only mode (see Appendix 11 Part B).

                                    SM-C-MAC-G2

                                    The command APDU must be applied with generation 2 secure messaging in authentication only mode (see Appendix 11 Part B).

                                    SM-R-ENC-MAC-G2

                                    The response APDU must be applied with generation 2 secure messaging in encrypt-then-authenticate mode (see Appendix 11 Part B).

                        TCS_24

                        These security conditions can be linked in the following ways:

                              AND
                           : All security conditions must be fulfilled

                              OR
                           : At least one security condition must be fulfilled
                        The access rules for the file system, i.e. the SELECT, READ BINARY and UPDATE BINARY command, are specified in chapter 4. The access rules for the remaining commands are specified in the following tables.

                        TCS_25

                        In the DF Tachograph G1 application the following access rules are used:

                                    Command

                                    Driver Card

                                    Workshop Card

                                    Control Card

                                    Company Card

                                    External Authenticate

                                                —

                                                For generation 1 authentication

                                    ALW

                                    ALW

                                    ALW

                                    ALW

                                                —

                                                For generation 2 authentication

                                    ALW

                                    PWD

                                    ALW

                                    ALW

                                    Internal Authenticate

                                    ALW

                                    PWD

                                    ALW

                                    ALW

                                    General Authenticate

                                    ALW

                                    ALW

                                    ALW

                                    ALW

                                    Get Challenge

                                    ALW

                                    ALW

                                    ALW

                                    ALW

                                    MSE:SET AT

                                    ALW

                                    ALW

                                    ALW

                                    ALW

                                    MSE:SET DST

                                    ALW

                                    ALW

                                    ALW

                                    ALW

                                    Process DSRC Message

                                    Not applicable

                                    Not applicable

                                    Not applicable

                                    Not applicable

                                    PSO: Compute Digital Signature

                                    ALW OR
                                    SM-MAC-G2

                                    ALW OR
                                    SM-MAC-G2

                                    Not applicable

                                    Not applicable

                                    PSO: Hash

                                    Not applicable

                                    Not applicable

                                    ALW

                                    Not applicable

                                    PSO: Hash of File

                                    ALW OR
                                    SM-MAC-G2

                                    ALW OR
                                    SM-MAC-G2

                                    Not applicable

                                    Not applicable

                                    PSO: Verify Certificate

                                    ALW

                                    ALW

                                    ALW

                                    ALW

                                    PSO: Verify Digital Signature

                                    Not applicable

                                    Not applicable

                                    ALW

                                    Not applicable

                                    Verify

                                    Not applicable

                                    ALW

                                    Not applicable

                                    Not applicable

                        TCS_26

                        In the DF Tachograph_G2 application the following access rules are used:

                                    Command

                                    Driver Card

                                    Workshop Card

                                    Control Card

                                    Company Card

                                    External Authenticate

                                                —

                                                For generation 1 authentication

                                    Not applicable

                                    Not applicable

                                    Not applicable

                                    Not applicable

                                                —

                                                For generation 2 authentication

                                    ALW

                                    PWD

                                    ALW

                                    ALW

                                    Internal Authenticate

                                    Not applicable

                                    Not applicable

                                    Not applicable

                                    Not applicable

                                    General Authenticate

                                    ALW

                                    ALW

                                    ALW

                                    ALW

                                    Get Challenge

                                    ALW

                                    ALW

                                    ALW

                                    ALW

                                    MSE:SET AT

                                    ALW

                                    ALW

                                    ALW

                                    ALW

                                    MSE:SET DST

                                    ALW

                                    ALW

                                    ALW

                                    ALW

                                    Process DSRC Message

                                    Not applicable

                                    ALW

                                    ALW

                                    Not applicable

                                    PSO: Compute Digital Signature

                                    ALW OR
                                    SM-MAC-G2

                                    ALW OR
                                    SM-MAC-G2

                                    Not applicable

                                    Not applicable

                                    PSO: Hash

                                    Not applicable

                                    Not applicable

                                    ALW

                                    Not applicable

                                    PSO: Hash of File

                                    ALW OR
                                    SM-MAC-G2

                                    ALW OR
                                    SM-MAC-G2

                                    Not applicable

                                    Not applicable

                                    PSO: Verify Certificate

                                    ALW

                                    ALW

                                    ALW

                                    ALW

                                    PSO: Verify Digital Signature

                                    Not applicable

                                    Not applicable

                                    ALW

                                    Not applicable

                                    Verify

                                    Not applicable

                                    ALW

                                    Not applicable

                                    Not applicable

                        TCS_27

                        In the MF the following access rules are used:

                                    Command

                                    Driver Card

                                    Workshop Card

                                    Control Card

                                    Company Card

                                    External Authenticate

                                                —

                                                For generation 1 authentication

                                    Not applicable

                                    Not applicable

                                    Not applicable

                                    Not applicable

                                                —

                                                For generation 2 authentication

                                    ALW

                                    PWD

                                    ALW

                                    ALW

                                    Internal Authenticate

                                    Not applicable

                                    Not applicable

                                    Not applicable

                                    Not applicable

                                    General Authenticate

                                    ALW

                                    ALW

                                    ALW

                                    ALW

                                    Get Challenge

                                    ALW

                                    ALW

                                    ALW

                                    ALW

                                    MSE:SET AT

                                    ALW

                                    ALW

                                    ALW

                                    ALW

                                    MSE:SET DST

                                    ALW

                                    ALW

                                    ALW

                                    ALW

                                    Process DSRC Message

                                    Not applicable

                                    Not applicable

                                    Not applicable

                                    Not applicable

                                    PSO: Compute Digital Signature

                                    Not applicable

                                    Not applicable

                                    Not applicable

                                    Not applicable

                                    PSO: Hash

                                    Not applicable

                                    Not applicable

                                    Not applicable

                                    Not applicable

                                    PSO: Hash of File

                                    Not applicable

                                    Not applicable

                                    Not applicable

                                    Not applicable

                                    PSO: Verify Certificate

                                    ALW

                                    ALW

                                    ALW

                                    ALW

                                    Verify

                                    Not applicable

                                    ALW

                                    Not applicable

                                    Not applicable

                        TCS_28

                        A tachograph card may or may not accept a command with a higher level of security than the one specified in the security conditions. I.e. if the security condition is ALW (or PLAIN-C) the card may accept a command with secure messaging (encryption and / or authentication mode). If the security condition requires secure messaging with authentication mode, the tachograph card may accept a command with secure messaging of the same generation in authentication and encryption mode.

                           Note: The command descriptions provide more information on the support of the commands for the different tachograph card types and the different DFs.

                  3.4.   Commands and error codes overview

            Commands and file organisation are deduced from and complies with ISO/IEC 7816-4.
            This section describes the following APDU command-response pairs. The command variants which are supported by a generation 1 and 2 application are specified in the corresponding command descriptions.

                        Command

                        INS

                        SELECT

                        ‘A4h’

                        READ BINARY

                        ‘B0h’, ‘B1h’

                        UPDATE BINARY

                        ‘D6h’, ‘D7h’

                        GET CHALLENGE

                        ‘84h’

                        VERIFY

                        ‘20h’

                        GET RESPONSE

                        ‘C0h’

                        PERFORM SECURITY OPERATION

                        ‘2Ah’

                                    —

                                    VERIFY CERTIFICATE

                                    —

                                    COMPUTE DIGITAL SIGNATURE

                                    —

                                    VERIFY DIGITAL SIGNATURE

                                    —

                                    HASH

                                    —

                                    PERFORM HASH OF FILE

                                    —

                                    PROCESS DSRC MESSAGE

                        INTERNAL AUTHENTICATE

                        ‘88h’

                        EXTERNAL AUTHENTICATE

                        ‘82h’

                        MANAGE SECURITY ENVIRONMENT

                        ‘22h’

                                    —

                                    SET DIGITAL SIGNATURE TEMPLATE

                                    —

                                    SET AUTHENTICATION TEMPLATE

                        GENERAL AUTHENTICATE

                        ‘86h’

                        TCS_29

                        The status words SW1 SW2 are returned in any response message and denote the processing state of the command.

                                    SW1

                                    SW2

                                    Meaning

                                    90

                                    00

                                    Normal processing.

                                    61

                                    XX

                                    Normal processing. XX = number of response bytes available.

                                    62

                                    81

                                    Warning processing. Part of returned data may be corrupted

                                    63

                                    00

                                    Authentication failed (Warning)

                                    63

                                    CX

                                    Wrong CHV (PIN). Remaining attempts counter provided by ‘X’.

                                    64

                                    00

                                    Execution error — State of non-volatile memory unchanged. Integrity error.

                                    65

                                    00

                                    Execution error — State of non-volatile memory changed

                                    65

                                    81

                                    Execution error — State of non-volatile memory changed — Memory failure

                                    66

                                    88

                                                Security error

                                                :

                                                wrong cryptographic checksum (during Secure Messaging) or
                                                wrong certificate (during certificate verification) or
                                                wrong cryptogram (during external authentication) or
                                                wrong signature (during signature verification)

                                    67

                                    00

                                    Wrong length (wrong Lc or Le)

                                    68

                                    82

                                    Secure messaging not supported

                                    68

                                    83

                                    Last command of the chain expected

                                    69

                                    00

                                    Forbidden command (no response available in T=0)

                                    69

                                    82

                                    Security status not satisfied.

                                    69

                                    83

                                    Authentication method blocked.

                                    69

                                    85

                                    Conditions of use not satisfied.

                                    69

                                    86

                                    Command not allowed (no current EF).

                                    69

                                    87

                                    Expected Secure Messaging Data Objects missing

                                    69

                                    88

                                    Incorrect Secure Messaging Data Objects

                                    6A

                                    80

                                    Incorrect parameters in data field

                                    6A

                                    82

                                    File not found.

                                    6A

                                    86

                                    Wrong parameters P1-P2.

                                    6A

                                    88

                                    Referenced data not found.

                                    6B

                                    00

                                    Wrong parameters (offset outside the EF).

                                    6C

                                    XX

                                    Wrong length, SW2 indicates the exact length. No data field is returned.

                                    6D

                                    00

                                    Instruction code not supported or invalid.

                                    6E

                                    00

                                    Class not supported.

                                    6F

                                    00

                                    Other checking errors

                        TCS_30

                        If more than one error condition is fulfilled in one command APDU the card may return any of the appropriate status words.

                  3.5.   Command descriptions

            The mandatory commands for the Tachograph cards are described in this chapter.
            Additional relevant details, related to cryptographic operations involved, are given in Appendix 11 Common security mechanisms for Tachograph Generation 1 and Generation 2.
            All commands are described independently of the used protocol (T=0 or T=1). The APDU bytes CLA, INS, P1, P2, Lc and Le are always indicated. If Lc or Le is not needed for the described command, the associated length, value and description are empty.

                        TCS_31

                        If both length bytes (Lc and Le) are requested, the described command has to be split in two parts if the IFD is using protocol T=0: the IFD sends the command as described with P3=Lc + data and then sends a GET RESPONSE (see § 3.5.6) command with P3=Le.

                        TCS_32

                        If both length bytes are requested, and Le=0 (secure messaging):

                                    —

                                    When using protocol T=1, the card shall answer to Le=0 by sending all available output data.

                                    —

                                    When using protocol T=0, the IFD shall send the first command with P3=Lc + data, the card shall answer (to this implicit Le=0) by the Status bytes ‘61La’, where La is the number of response bytes available. The IFD shall then generate a GET RESPONSE command with P3 = La to read the data.

                        TCS_33

                        A tachograph card may support extended length fields according to ISO/IEC 7816-4 as an optional feature. A tachograph card that supports extended length fields shall

                                    —

                                    Indicate the extended length field support in the ATR

                                    —

                                    Provide the supported buffer sizes by means of the extended length information in the EF ATR/INFO see TCS_146.

                                    —

                                    Indicate whether it supports extended length fields for T = 1 and / or T = 0 in the EF Extended Length, see TCS_147.

                                    —

                                    Support extended length fields for the tachograph application generation 1 and 2.

                           Notes:

                        All commands are specified for short length fields. The usage of extended length APDUs is clear from ISO/IEC 7816-4.
                        In general the commands are specified for the plain mode, i.e. without secure messaging, as the secure messaging layer is specified in Appendix 11. It is clear from the access rules for a command whether the command shall support secure messaging or not and whether the command shall support generation 1 and / or generation 2 secure messaging. Some command variants are described with secure messaging to illustrate the usage of secure messaging.

                        TCS_34

                        The VU shall perform the complete generation 2 VU — card mutual authentication protocol for a session including the certificate verification (if required) either in the DF Tachograph, the DF Tachograph_G2 or the MF.

                  3.5.1   SELECT

            This command is compliant with ISO/IEC 7816-4, but has a restricted usage compared to the command defined in the norm.
            The SELECT command is used:

                        —

                        to select an application DF (selection by name must be used)

                        —

                        to select an elementary file corresponding to the submitted file ID

                  3.5.1.1   Selection by name (AID)

            This command allows selecting an application DF in the card.

                        TCS_35

                        This command can be performed from anywhere in the file structure (after the ATR or at any time).

                        TCS_36

                        The selection of an application resets the current security environment. After performing the application selection, no current public key is selected anymore. The EXT-AUT-G1 access condition is also lost. If the command was performed without secure messaging, the former secure messaging session keys are no longer available.

                        TCS_37

                        Command Message

                                    Byte

                                    Length

                                    Value

                                    Description

                                    CLA

                                    1

                                    ‘00h’

                                    INS

                                    1

                                    ‘A4h’

                                    P1

                                    1

                                    ‘04h’

                                    Selection by name (AID)

                                    P2

                                    1

                                    ‘0Ch’

                                    No response expected

                                    Lc

                                    1

                                    ‘NNh’

                                    Number of bytes sent to the card (length of the AID):
                                    ‘06h’ for the Tachograph application

                                    #6-#(5+NN)

                                    NN

                                    ‘XX..XXh’

                                    AID: ‘FF 54 41 43 48 4F’ for the Generation 1 tachograph application
                                    AID: ‘FF 53 4D 52 44 54’ for the Generation 2 tachograph application

                              No response to the SELECT command is needed (Le absent in T=1, or no response asked in T=0).

                        TCS_38

                        Response Message (no response asked)

                                    Byte

                                    Length

                                    Value

                                    Description

                                    SW

                                    2

                                    ‘XXXXh’

                                    Status Words (SW1,SW2)

                                    —

                                    If the command is successful, the card returns ‘9000’.

                                    —

                                    If the application corresponding with the AID is not found, the processing state returned is ‘6A82’.

                                    —

                                    In T=1, if the byte Le is present, the state returned is ‘6700’.

                                    —

                                    In T=0, if a response is asked after the SELECT command, the state returned is ‘6900’.

                                    —

                                    If the selected application is considered corrupted (integrity error is detected within the file attributes), the processing state returned is ‘6400’ or ‘6581’.

                  3.5.1.2   Selection of an Elementary File using its File Identifier

                        TCS_39

                        Command Message

                        TCS_40

                        A tachograph card shall support the generation 2 secure messaging as specified in Appendix 11 Part B for this command variant.

                                    Byte

                                    Length

                                    Value

                                    Description

                                    CLA

                                    1

                                    ‘00h’

                                    INS

                                    1

                                    ‘A4h’

                                    P1

                                    1

                                    ‘02h’

                                    Selection of an EF under the current DF

                                    P2

                                    1

                                    ‘0Ch’

                                    No response expected

                                    Lc

                                    1

                                    ‘02h’

                                    Number of bytes sent to the card

                                    #6-#7

                                    2

                                    ‘XXXXh’

                                    File Identifier

                              No response to the SELECT command is needed (Le absent in T=1, or no response asked in T=0).

                        TCS_41

                        Response Message (no response asked)

                                    Byte

                                    Length

                                    Value

                                    Description

                                    SW

                                    2

                                    ‘XXXXh’

                                    Status Words (SW1,SW2)

                                    —

                                    If the command is successful, the card returns ‘9000’.

                                    —

                                    If the file corresponding with the file identifier is not found, the processing state returned is ‘6A82’.

                                    —

                                    In T=1, if the byte Le is present, the state returned is ‘6700’.

                                    —

                                    In T=0, if a response is asked after the SELECT command, the state returned is ‘6900’.

                                    —

                                    If the selected file is considered corrupted (integrity error is detected within the file attributes), the processing state returned is ‘6400’ or ‘6581’.

                  3.5.2   READ BINARY

            This command is compliant with ISO/IEC 7816-4, but has a restricted usage compared to the command defined in the norm.
            The READ BINARY command is used to read data from a transparent file.
            The response of the card consists of returning the data read, optionally encapsulated in a secure messaging structure.
            3.5.2.1   Command with offset in P1-P2

            This command enables the IFD to read data from the EF currently selected, without secure messaging.

               Note: This command without secure messaging can only be used to read a file that supports the ALW security condition for the Read access mode.

                        TCS_42

                        Command Message

                                    Byte

                                    Length

                                    Value

                                    Description

                                    CLA

                                    1

                                    ‘00h’

                                    INS

                                    1

                                    ‘B0h’

                                    Read Binary

                                    P1

                                    1

                                    ‘XXh’

                                    Offset in bytes from the beginning of the file: Most Significant Byte

                                    P2

                                    1

                                    ‘XXh’

                                    Offset in bytes from the beginning of the file: Least Significant Byte

                                    Le

                                    1

                                    ‘XXh’

                                    Length of data expected. Number of Bytes to be read.

                           Note: bit 8 of P1 must be set to 0.

                        TCS_43

                        Response Message

                                    Byte

                                    Length

                                    Value

                                    Description

                                    #1-#X

                                    X

                                    ‘XX..XXh’

                                    Data read

                                    SW

                                    2

                                    ‘XXXXh’

                                    Status Words (SW1,SW2)

                                    —

                                    If the command is successful, the card returns ‘9000’.

                                    —

                                    If no EF is selected, the processing state returned is ‘6986’.

                                    —

                                    If the security conditions of the selected file are not satisfied, the command is interrupted with ‘6982’.

                                    —

                                    If the Offset is not compatible with the size of the EF (Offset > EF size), the processing state returned is ‘6B00’.

                                    —

                                    If the size of the data to be read is not compatible with the size of the EF (Offset + Le > EF size) the processing state returned is ‘6700’ or ‘6Cxx’ where ‘xx’ indicates the exact length.

                                    —

                                    If an integrity error is detected within the file attributes, the card shall consider the file as corrupted and unrecoverable, the processing state returned is ‘6400’ or ‘6581’.

                                    —

                                    If an integrity error is detected within the stored data, the card shall return the demanded data, and the processing state returned is ‘6281’.

                  3.5.2.1.1   Command with secure messaging (examples)

            This command enables the IFD to read data from the EF currently selected with secure messaging, in order to verify the integrity of the data received and to protect the confidentiality of the data if the security condition SM-R-ENC-MAC-G1 (generation 1) or SM-R-ENC-MAC-G2 (generation 2) is applied.

                        TCS_44

                        Command Message

                                    Byte

                                    Length

                                    Value

                                    Description

                                    CLA

                                    1

                                    ‘0Ch’

                                    Secure Messaging asked

                                    INS

                                    1

                                    ‘B0h’

                                    Read Binary

                                    P1

                                    1

                                    ‘XXh’

                                    P1 ( offset in bytes from the beginning of the file): Most Significant Byte

                                    P2

                                    1

                                    ‘XXh’

                                    P2 ( offset in bytes from the beginning of the file): Least Significant Byte

                                    Lc

                                    1

                                    ‘XXh’

                                    Length of input data for secure messaging

                                    #6

                                    1

                                    ‘97h’

                                    TLE: Tag for expected length specification.

                                    #7

                                    1

                                    ‘01h’

                                    LLE: Length of expected length

                                    #8

                                    1

                                    ‘NNh’

                                    Expected length specification (original Le): Number of Bytes to be read

                                    #9

                                    1

                                    ‘8Eh’

                                    TCC: Tag for cryptographic checksum

                                    #10

                                    1

                                    ‘XXh’

                                    LCC: Length of following cryptographic checksum

                                                ‘04h’ for Generation 1 secure messaging (see Appendix 11 Part A)

                                                ‘08h’, ‘0Ch’ or ‘10h’ depending on AES key length for Generation 2 secure messaging (see Appendix 11 Part B)

                                    #11-#(10+L)

                                    L

                                    ‘XX..XXh’

                                    Cryptographic checksum

                                    Le

                                    1

                                    ‘00h’

                                    As specified in ISO/IEC 7816-4

                        TCS_45

                        Response Message if SM-R-ENC-MAC-G1 (generation 1) / SM-R-ENC-MAC-G2 (generation 2) is not required and if Secure Messaging input format is correct:

                                    Byte

                                    Length

                                    Value

                                    Description

                                    #1

                                    1

                                    ‘99h’

                                    Tag for Processing Status (SW1-SW2) — optional for generation 1 secure messaging

                                    #2

                                    1

                                    ‘02h’

                                    Length of Processing Status

                                    #3 — #4

                                    2

                                    ‘XX XXh’

                                    Processing Status of the unprotected response APDU

                                    #5

                                    1

                                    ‘81h’

                                    TPV: Tag for plain value data

                                    #6

                                    L

                                    ‘NNh’ or
                                    ‘81 NNh’

                                    LPV: length of returned data (=original Le).
                                    L is 2 bytes if LPV>127 bytes.

                                    #(6+L)-#(5+L+NN)

                                    NN

                                    ‘XX..XXh’

                                    Plain Data value

                                    #(6+L+NN)

                                    1

                                    ‘8Eh’

                                    TCC: Tag for cryptographic checksum

                                    #(7+L+NN)

                                    1

                                    ‘XXh’

                                    LCC: Length of following cryptographic checksum

                                                ‘04h’ for Generation 1 secure messaging (see Appendix 11 Part A)

                                                ‘08h’, ‘0Ch’ or ‘10h’ depending on AES key length for Generation 2 secure messaging (see Appendix 11 Part B)

                                    #(8+L+NN)-#(7+M+L+NN)

                                    M

                                    ‘XX..XXh’

                                    Cryptographic checksum

                                    SW

                                    2

                                    ‘XXXXh’

                                    Status Words (SW1,SW2)

                        TCS_46

                        Response Message if SM-R-ENC-MAC-G1 (generation 1) / SM-R-ENC-MAC-G2 (generation 2) is required and if Secure Messaging input format is correct:

                                    Byte

                                    Length

                                    Value

                                    Description

                                    #1

                                    1

                                    ‘87h’

                                    TPI CG: Tag for encrypted data (cryptogram)

                                    #2

                                    L

                                    ‘MMh’ or
                                    ‘81 MMh’

                                    LPI CG: length of returned encrypted data (different of original Le of the command due to padding).
                                    L is 2 bytes if LPI CG > 127 bytes.

                                    #(2+L)-#(1+L+MM)

                                    MM

                                    ‘01XX..XXh’

                                    Encrypted Data: Padding Indicator and cryptogram

                                    #(2+L+MM)

                                    1

                                    ‘99h’

                                    Tag for Processing Status (SW1-SW2) — optional for generation 1 secure messaging

                                    #(3+L+MM)

                                    1

                                    ‘02h’

                                    Length of Processing Status

                                    #(4+L+MM) — #(5+L+MM)

                                    2

                                    ‘XX XXh’

                                    Processing Status of the unprotected response APDU

                                    #(6+L+MM)

                                    1

                                    ‘8Eh’

                                    TCC: Tag for cryptographic checksum

                                    #(7+L+MM)

                                    1

                                    ‘XXh’

                                    LCC: Length of following cryptographic checksum

                                                ‘04h’ for Generation 1 secure messaging (see Appendix 11 Part A)

                                                ‘08h’, ‘0Ch’ or ‘10h’ depending on AES key length for Generation 2 secure messaging (see Appendix 11 Part B)

                                    #(8+L+MM)-#(7+N+L+MM)

                                    N

                                    ‘XX..XXh’

                                    Cryptographic checksum

                                    SW

                                    2

                                    ‘XXXXh’

                                    Status Words (SW1,SW2)

                              The READ BINARY command may return regular processing states listed in TCS_43 under Tag ‘99h’ as described in TCS_59 using the secure messaging response structure.
                        Additionally, some errors specifically related to secure messaging can happen. In that case, the processing state is simply returned, with no secure messaging structure involved:

                        TCS_47

                        Response Message if incorrect Secure Messaging input format

                                    Byte

                                    Length

                                    Value

                                    Description

                                    SW

                                    2

                                    ‘XXXXh’

                                    Status Words (SW1,SW2)

                                    —

                                    If no current session key is available, the processing state ‘6A88’ is returned. It happens either if the session key has not already been generated or if the session key validity has expired (in this case the IFD must re-run a mutual authentication process to set a new session key).

                                    —

                                    If some expected data objects (as specified above) are missing in the secure messaging format, the processing state ‘6987’ is returned: this error happens if an expected tag is missing or if the command body is not properly constructed.

                                    —

                                    If some data objects are incorrect, the processing state returned is ‘6988’: this error happens if all the required tags are present but some lengths are different from the ones expected.

                                    —

                                    If the verification of the cryptographic checksum fails, the processing state returned is ‘6688’.

                  3.5.2.2   Command with short EF (Elementary File) identifier

            This command variant enables the IFD to select an EF by means of a short EF identifier and read data from this EF.

                        TCS_48

                        A tachograph card shall support this command variant for all Elementary Files with a specified short EF identifier. These short EF identifiers are specified in chapter 4.

                        TCS_49

                        Command Message

                                    Byte

                                    Length

                                    Value

                                    Description

                                    CLA

                                    1

                                    ‘00h’

                                    INS

                                    1

                                    ‘B0h’

                                    Read Binary

                                    P1

                                    1

                                    ‘XXh’

                                    Bit 8 is set to 1
                                    Bit 7 and 6 are set to 00
                                    Bit 5 — 1 encode the short EF identifier of the corresponding EF

                                    P2

                                    1

                                    ‘XXh’

                                    Encodes an offset from 0 to 255 bytes in the EF referenced by P1

                                    Le

                                    1

                                    ‘XXh’

                                    Length of data expected. Number of Bytes to be read.

                           Note: The short EF identifiers used for the Generation 2 tachograph application are specified in chapter 4.
                        If P1 encodes a short EF identifier and the command is successful, the identified EF becomes the currently selected EF (current EF).

                        TCS_50

                        Response Message

                                    Byte

                                    Length

                                    Value

                                    Description

                                    #1-#L

                                    L

                                    ‘XX..XXh’

                                    Data read

                                    SW

                                    2

                                    ‘XXXXh’

                                    Status Words (SW1,SW2)

                                    —

                                    If the command is successful, the card returns ‘9000’.

                                    —

                                    If the file corresponding with the short EF identifier is not found, the processing state returned is ‘6A82’.

                                    —

                                    If the security conditions of the selected file are not satisfied, the command is interrupted with ‘6982’.

                                    —

                                    If the Offset is not compatible with the size of the EF (Offset > EF size), the processing state returned is ‘6B00’.

                                    —

                                    If the size of the data to be read is not compatible with the size of the EF (Offset + Le > EF size) the processing state returned is ‘6700’ or ‘6Cxx’ where ‘xx’ indicates the exact length.

                                    —

                                    If an integrity error is detected within the file attributes, the card shall consider the file as corrupted and unrecoverable, the processing state returned is ‘6400’ or ‘6581’.

                                    —

                                    If an integrity error is detected within the stored data, the card shall return the demanded data, and the processing state returned is ‘6281’.

                  3.5.2.3   Command with odd instruction byte

            This command variant enables the IFD to read data from an EF with 32 768 bytes or more.

                        TCS_51

                        A tachograph card which supports EFs with 32 768 bytes or more shall support this command variant for these EFs. A tachograph card may or may not support this command variant for other EFs with the exception of the EF Sensor_Installation_Data see TCS_156 and TCS_160.

                        TCS_52

                        Command Message

                                    Byte

                                    Length

                                    Value

                                    Description

                                    CLA

                                    1

                                    ‘00h’

                                    INS

                                    1

                                    ‘B1h’

                                    Read Binary

                                    P1

                                    1

                                    ‘00h’

                                    Current EF

                                    P2

                                    1

                                    ‘00h’

                                    Lc

                                    1

                                    ‘NNh’

                                    Lc Length of offset data object.

                                    #6-#(5+NN)

                                    NN

                                    ‘XX..XXh’

                                    Offset data object:

                                                Tag

                                                ‘54h’

                                                Length

                                                ‘01h’ or ‘02h’

                                                Value

                                                offset

                                    Le

                                    1

                                    ‘XXh’

                                    Number of Bytes to be read.

                              The IFD shall encode the offset data object's length with a minimum possible number of octets, i.e. using the length byte ‘01h’ the IFD shall encode an offset from 0 to 255 and using the length byte ‘02h’ an offset from ‘256’ up to ‘65 535’ bytes.

                        TCS_53

                        Response Message

                                    Byte

                                    Length

                                    Value

                                    Description

                                    #1-#L

                                    L

                                    ‘XX..XXh’

                                    Data read encapsulated in a discretionary data object with tag ‘53h’.

                                    SW

                                    2

                                    ‘XXXXh’

                                    Status Words (SW1,SW2)

                                    —

                                    If the command is successful, the card returns ‘9000’.

                                    —

                                    If no EF is selected, the processing state returned is ‘6986’.

                                    —

                                    If the security conditions of the selected file are not satisfied, the command is interrupted with ‘6982’.

                                    —

                                    If the Offset is not compatible with the size of the EF (Offset > EF size), the processing state returned is ‘6B00’.

                                    —

                                    If the size of the data to be read is not compatible with the size of the EF (Offset + Le > EF size) the processing state returned is ‘6700’ or ‘6Cxx’ where ‘xx’ indicates the exact length.

                                    —

                                    If an integrity error is detected within the file attributes, the card shall consider the file as corrupted and unrecoverable, the processing state returned is ‘6400’ or ‘6581’.

                                    —

                                    If an integrity error is detected within the stored data, the card shall return the demanded data, and the processing state returned is ‘6281’.

                  3.5.2.3.1   Command with secure messaging (example)

            The following example illustrates the usage of secure messaging if the security condition SM-MAC-G2 applies.

                        TCS_54

                        Command message

                                    Byte

                                    Length

                                    Value

                                    Description

                                    CLA

                                    1

                                    ‘0Ch’

                                    Secure Messaging asked

                                    INS

                                    1

                                    ‘B1h’

                                    Read Binary

                                    P1

                                    1

                                    ‘00h’

                                    Current EF

                                    P2

                                    1

                                    ‘00h’

                                    Lc

                                    1

                                    ‘XXh’

                                    Length of the secured data field

                                    #6

                                    1

                                    ‘B3h’

                                    Tag for plain value data encoded in BER-TLV

                                    #7

                                    1

                                    ‘NNh’

                                    LPV: length of transmitted data

                                    #(8)-#(7+NN)

                                    NN

                                    ‘XX..XXh’

                                    Plain Data encoded in BER-TLV, i.e. the offset data object with tag ‘54’

                                    #(8+NN)

                                    1

                                    ‘97h’

                                    TLE: Tag for expected length specification.

                                    #(9+NN)

                                    1

                                    ‘01h’

                                    LLE: Length of expected length

                                    #(10+NN)

                                    1

                                    ‘XXh’

                                    Expected length specification (original Le): Number of bytes to be read

                                    #(11+NN)

                                    1

                                    ‘8Eh’

                                    TCC: Tag for cryptographic checksum

                                    #(12+NN)

                                    1

                                    ‘XXh’

                                    LCC: Length of following cryptographic checksum
                                    ‘08h’, ‘0Ch’ or ‘10h’ depending on AES key length for Generation 2 secure messaging (see Appendix 11 Part B)

                                    #(13+NN)-#(12+M+NN)

                                    M

                                    ‘XX..XXh’

                                    Cryptographic checksum

                                    Le

                                    1

                                    ‘00h’

                                    As specified in ISO/IEC 7816-4

                        TCS_55

                        Response message if the command is successful

                                    Byte

                                    Length

                                    Value

                                    Description

                                    #1

                                    1

                                    ‘B3h’

                                    Plain Data encoded in BER-TLV

                                    #2

                                    L

                                    ‘NNh’ or
                                    ‘81 NNh’

                                    LPV: length of returned data (=original Le).
                                    L is 2 bytes if LPV>127 bytes.

                                    #(2+L)-#(1+L+NN)

                                    NN

                                    ‘XX..XXh’

                                    Plain Data value encoded in BER-TLV, i.e. data read encapsulated in a discretionary data object with tag ‘53h’.

                                    #(2+L+NN)

                                    1

                                    ‘99h’

                                    Processing Status of the unprotected response APDU

                                    #(3+L+NN)

                                    1

                                    ‘02h’

                                    Length of Processing Status

                                    #(4+L+NN) — #(5+L+NN)

                                    2

                                    ‘XX XXh’

                                    Processing Status of the unprotected response APDU

                                    #(6+L+NN)

                                    1

                                    ‘8Eh’

                                    TCC: Tag for cryptographic checksum

                                    #(7+L+NN)

                                    1

                                    ‘XXh’

                                    LCC: Length of following cryptographic checksum
                                    ‘08h’, ‘0Ch’ or ‘10h’ depending on AES key length for Generation 2 secure messaging (see Appendix 11 Part B)

                                    #(8+L+NN)-#(7+M+L+NN)

                                    M

                                    ‘XX..XXh’

                                    Cryptographic checksum

                                    SW

                                    2

                                    ‘XXXXh’

                                    Status Words (SW1,SW2)

                  3.5.3   UPDATE BINARY

            This command is compliant with ISO/IEC 7816-4, but has a restricted usage compared to the command defined in the norm.
            The UPDATE BINARY command message initiates the update (erase + write) of the bits already present in an EF binary with the bits given in the command APDU.
            3.5.3.1   Command with offset in P1-P2

            This command enables the IFD to write data into the EF currently selected, without the card verifying the integrity of data received.

               Note: This command without secure messaging can only be used to update a file that supports the ALW security condition for the Update access mode.

                        TCS_56

                        Command Message

                                    Byte

                                    Length

                                    Value

                                    Description

                                    CLA

                                    1

                                    ‘00h’

                                    INS

                                    1

                                    ‘D6h’

                                    Update Binary

                                    P1

                                    1

                                    ‘XXh’

                                    Offset in bytes from the beginning of the file: Most Significant Byte

                                    P2

                                    1

                                    ‘XXh’

                                    Offset in bytes from the beginning of the file: Least Significant Byte

                                    Lc

                                    1

                                    ‘NNh’

                                    Lc Length of data to Update. Number of bytes to be written.

                                    #6-#(5+NN)

                                    NN

                                    ‘XX..XXh’

                                    Data to be written

                           Note: bit 8 of P1 must be set to 0.

                        TCS_57

                        Response Message

                                    Byte

                                    Length

                                    Value

                                    Description

                                    SW

                                    2

                                    ‘XXXXh’

                                    Status Words (SW1,SW2)

                                    —

                                    If the command is successful, the card returns ‘9000’.

                                    —

                                    If no EF is selected, the processing state returned is ‘6986’.

                                    —

                                    If the security conditions of the selected file are not satisfied, the command is interrupted with ‘6982’.

                                    —

                                    If the Offset is not compatible with the size of the EF (Offset > EF size), the processing state returned is ‘6B00’.

                                    —

                                    If the size of the data to be written is not compatible with the size of the EF (Offset + Lc > EF size) the processing state returned is ‘6700’.

                                    —

                                    If an integrity error is detected within the file attributes, the card shall consider the file as corrupted and unrecoverable, the processing state returned is ‘6400’ or ‘6500’.

                                    —

                                    If writing is unsuccessful, the processing state returned is ‘6581’.

                  3.5.3.1.1   Command with secure messaging (examples)

            This command enables the IFD to write data into the EF currently selected, with the card verifying the integrity of data received. As no confidentiality is required, the data are not encrypted.

                        TCS_58

                        Command Message

                                    Byte

                                    Length

                                    Value

                                    Description

                                    CLA

                                    1

                                    ‘0Ch’

                                    Secure Messaging asked

                                    INS

                                    1

                                    ‘D6h’

                                    Update Binary

                                    P1

                                    1

                                    ‘XXh’

                                    Offset in bytes from the beginning of the file:
                                    Most Significant Byte

                                    P2

                                    1

                                    ‘XXh’

                                    Offset in bytes from the beginning of the file:
                                    Least Significant Byte

                                    Lc

                                    1

                                    ‘XXh’

                                    Length of the secured data field

                                    #6

                                    1

                                    ‘81h’

                                    TPV: Tag for plain value data

                                    #7

                                    L

                                    ‘NNh’ or
                                    ‘81 NNh’

                                    LPV: length of transmitted data.
                                    L is 2 bytes if LPV > 127 bytes.

                                    #(7+L)-#(6+L+NN)

                                    NN

                                    ‘XX..XXh’

                                    Plain Data value (Data to be written)

                                    #(7+L+NN)

                                    1

                                    ‘8Eh’

                                    TCC: Tag for cryptographic checksum

                                    #(8+L+NN)

                                    1

                                    ‘XXh’

                                    LCC: Length of following cryptographic checksum‘04h’ for Generation 1 secure messaging (see Appendix 11 Part A)
                                    ‘08h’, ‘0Ch’ or ‘10h’ depending on AES key length for Generation 2 secure messaging (see Appendix 11 Part B)

                                    #(9+L+NN)-#(8+M+L+NN)

                                    M

                                    ‘XX..XXh’

                                    Cryptographic checksum

                                    Le

                                    1

                                    ‘00h’

                                    As specified in ISO/IEC 7816-4

                        TCS_59

                        Response message if correct Secure Messaging input format

                                    Byte

                                    Length

                                    Value

                                    Description

                                    #1

                                    1

                                    ‘99h’

                                    TSW: Tag for Status Words (to be protected by CC)

                                    #2

                                    1

                                    ‘02h’

                                    LSW: length of returned Status Words

                                    #3-#4

                                    2

                                    ‘XXXXh’

                                    Processing Status of the unprotected response APDU

                                    #5

                                    1

                                    ‘8Eh’

                                    TCC: Tag for cryptographic checksum

                                    #6

                                    1

                                    ‘XXh’

                                    LCC: Length of following cryptographic checksum

                                                ‘04h’ for Generation 1 secure messaging (see Appendix 11 Part A)

                                                ‘08h’, ‘0Ch’ or ‘10h’ depending on AES key length for Generation 2 secure messaging (see Appendix 11 Part B)

                                    #7-#(6+L)

                                    L

                                    ‘XX..XXh’

                                    Cryptographic checksum

                                    SW

                                    2

                                    ‘XXXXh’

                                    Status Words (SW1,SW2)

                              The ‘regular’ processing states, described for the UPDATE BINARY command with no secure messaging (see §3.5.3.1), can be returned using the response message structure described above.
                        Additionally, some errors specifically related to secure messaging can happen. In that case, the processing state is simply returned, with no secure messaging structure involved:

                        TCS_60

                        Response Message if error in secure messaging

                                    Byte

                                    Length

                                    Value

                                    Description

                                    SW

                                    2

                                    ‘XXXXh’

                                    Status Words (SW1,SW2)

                                    —

                                    If no current session key is available, the processing state ‘6A88’ is returned.

                                    —

                                    If some expected data objects (as specified above) are missing in the secure messaging format, the processing state ‘6987’ is returned: this error happens if an expected tag is missing or if the command body is not properly constructed.

                                    —

                                    If some data objects are incorrect, the processing state returned is ‘6988’: this error happens if all the required tags are present but some lengths are different from the ones expected.

                                    —

                                    If the verification of the cryptographic checksum fails, the processing state returned is ‘6688’.

                  3.5.3.2   Command with short EF identifier

            This command variant enables the IFD to select an EF by means of a short EF identifier and write data from this EF.

                        TCS_61

                        A tachograph card shall support this command variant for all Elementary Files with a specified short EF identifier. These short EF identifiers are specified in chapter 4.

                        TCS_62

                        Command Message

                                    Byte

                                    Length

                                    Value

                                    Description

                                    CLA

                                    1

                                    ‘00h’

                                    INS

                                    1

                                    ‘D6h’

                                    Update Binary

                                    P1

                                    1

                                    ‘XXh’

                                    Bit 8 is set to 1
                                    Bit 7 and 6 are set to 00
                                    Bit 5 — 1 encode the short EF identifier of the corresponding EF

                                    P2

                                    1

                                    ‘XXh’

                                    Encodes an offset from 0 to 255 bytes in the EF referenced by P1

                                    Lc

                                    1

                                    ‘NNh’

                                    Lc Length of data to Update. Number of bytes to be written.

                                    #6-#(5+NN)

                                    NN

                                    ‘XX..XXh’

                                    Data to be written

                        TCS_63

                        Response Message

                                    Byte

                                    Length

                                    Value

                                    Description

                                    SW

                                    2

                                    ‘XXXXh’

                                    Status Words (SW1,SW2)

                           Note: The short EF identifiers used for the generation 2 tachograph application are specified in chapter 4.
                        If P1 encodes a short EF identifier and the command is successful, the identified EF becomes the currently selected EF (current EF).

                                    —

                                    If the command is successful, the card returns ‘9000’.

                                    —

                                    If the file corresponding with the short EF identifier is not found, the processing state returned is ‘6A82’.

                                    —

                                    If the security conditions of the selected file are not satisfied, the command is interrupted with ‘6982’.

                                    —

                                    If the Offset is not compatible with the size of the EF (Offset > EF size), the processing state returned is ‘6B00’.

                                    —

                                    If the size of the data to be written is not compatible with the size of the EF (Offset + Lc > EF size) the processing state returned is ‘6700’.

                                    —

                                    If an integrity error is detected within the file attributes, the card shall consider the file as corrupted and unrecoverable, the processing state returned is ‘6400’ or ‘6581’.

                                    —

                                    If writing is unsuccessful, the processing state returned is ‘6581’.

                  3.5.3.3   Command with odd instruction byte

            This command variant enables the IFD to write data to an EF with 32 768 bytes or more.

                        TCS_64

                        A tachograph card which supports EFs with 32 768 bytes or more shall support this command variant for these EFs. A tachograph card may or may not support this command variant for other EFs.

                        TCS_65

                        Command Message

                                    Byte

                                    Length

                                    Value

                                    Description

                                    CLA

                                    1

                                    ‘00h’

                                    INS

                                    1

                                    ‘D7h’

                                    Update Binary

                                    P1

                                    1

                                    ‘00h’

                                    Current EF

                                    P2

                                    1

                                    ‘00h’

                                    Lc

                                    1

                                    ‘NNh’

                                    Lc Length of data in the command data field

                                    #6-#(5+NN)

                                    NN

                                    ‘XX..XXh’

                                    Offset data object with tag ‘54h’ || Discretionary data object with tag ‘53h’ that encapsulates the data to be written

                              The IFD shall encode the offset data object's and the discretionary data object's length with the minimum possible number of octets, i.e. using the length byte ‘01h’ the IFD shall encode an offset / length from 0 to 255 and using the length byte ‘02h’ an offset / length from ‘256’ up to ‘65 535’ bytes.

                        TCS_66

                        Response Message

                                    Byte

                                    Length

                                    Value

                                    Description

                                    SW

                                    2

                                    ‘XXXXh’

                                    Status Words (SW1,SW2)

                                    —

                                    If the command is successful, the card returns ‘9000’.

                                    —

                                    If no EF is selected, the processing state returned is ‘6986’.

                                    —

                                    If the security conditions of the selected file are not satisfied, the command is interrupted with ‘6982’.

                                    —

                                    If the Offset is not compatible with the size of the EF (Offset > EF size), the processing state returned is ‘6B00’.

                                    —

                                    If the size of the data to be written is not compatible with the size of the EF (Offset + Lc > EF size) the processing state returned is ‘6700’.

                                    —

                                    If an integrity error is detected within the file attributes, the card shall consider the file as corrupted and unrecoverable, the processing state returned is ‘6400’ or ‘6500’.

                                    —

                                    If writing is unsuccessful, the processing state returned is ‘6581’.

                  3.5.3.3.1   Command with secure messaging (example)

            The following example illustrates the usage of secure messaging if the security condition SM-MAC-G2 applies.

                        TCS_67

                        Command message

                                    Byte

                                    Length

                                    Value

                                    Description

                                    CLA

                                    1

                                    ‘0Ch’

                                    Secure Messaging asked

                                    INS

                                    1

                                    ‘D7h’

                                    Update Binary

                                    P1

                                    1

                                    ‘00h’

                                    Current EF

                                    P2

                                    1

                                    ‘00h’

                                    Lc

                                    1

                                    ‘XXh’

                                    Length of the secured data field

                                    #6

                                    1

                                    ‘B3h’

                                    Tag for plain value data encoded in BER-TLV

                                    #7

                                    L

                                    ‘NNh’ or
                                    ‘81 NNh’

                                    LPV: length of transmitted data.
                                    L is 2 bytes if LPV > 127 bytes.

                                    #(7+L)-#(6+L+NN)

                                    NN

                                    ‘XX..XXh’

                                    Plain Data encoded in BER-TLV, i.e. offset data object with tag ‘54h’ || Discretionary data object with tag ‘53h’ that encapsulates the data to be written

                                    #(7+L+NN)

                                    1

                                    ‘8Eh’

                                    TCC: Tag for cryptographic checksum

                                    #(8+L+NN)

                                    1

                                    ‘XXh’

                                    LCC: Length of following cryptographic checksum
                                    ‘08h’, ‘0Ch’ or ‘10h’ depending on AES key length for Generation 2 secure messaging (see Appendix 11 Part B)

                                    #(9+L+NN)-#(8+M+L+NN)

                                    M

                                    ‘XX..XXh’

                                    Cryptographic checksum

                                    Le

                                    1

                                    ‘00h’

                                    As specified in ISO/IEC 7816-4

                        TCS_68

                        Response message if the command is successful

                                    Byte

                                    Length

                                    Value

                                    Description

                                    #1

                                    1

                                    ‘99h’

                                    TSW: Tag for Status Words (to be protected by CC)

                                    #2

                                    1

                                    ‘02h’

                                    LSW: length of returned Status Words

                                    #3-#4

                                    2

                                    ‘XXXXh’

                                    Processing Status of the unprotected response APDU

                                    #5

                                    1

                                    ‘8Eh’

                                    TCC: Tag for cryptographic checksum

                                    #6

                                    1

                                    ‘XXh’

                                    LCC: Length of following cryptographic checksum
                                    ‘08h’, ‘0Ch’ or ‘10h’ depending on AES key length for Generation 2 secure messaging (see Appendix 11 Part B)

                                    #7-#(6+L)

                                    L

                                    ‘XX..XXh’

                                    Cryptographic checksum

                                    SW

                                    2

                                    ‘XXXXh’

                                    Status Words (SW1,SW2)

                  3.5.4   GET CHALLENGE

            This command is compliant with ISO/IEC 7816-4, but has a restricted usage compared to the command defined in the norm.
            The GET CHALLENGE command asks the card to issue a challenge in order to use it in a security related procedure in which a cryptogram or some ciphered data are sent to the card.

                        TCS_69

                        The Challenge issued by the card is only valid for the next command, which uses a challenge, sent to the card.

                        TCS_70

                        Command Message

                                    Byte

                                    Length

                                    Value

                                    Description

                                    CLA

                                    1

                                    ‘00h’

                                    INS

                                    1

                                    ‘84h’

                                    INS

                                    P1

                                    1

                                    ‘00h’

                                    P1

                                    P2

                                    1

                                    ‘00h’

                                    P2

                                    Le

                                    1

                                    ‘08h’

                                    Le (Length of Challenge expected).

                        TCS_71

                        Response Message

                                    Byte

                                    Length

                                    Value

                                    Description

                                    #1-#8

                                    8

                                    ‘XX..XXh’

                                    Challenge

                                    SW

                                    2

                                    ‘XXXXh’

                                    Status Words (SW1,SW2)

                                    —

                                    If the command is successful, the card returns ‘9000’.

                                    —

                                    If Le is different from ‘08h’, the processing state is ‘6700’.

                                    —

                                    If parameters P1-P2 are incorrect, the processing state is ‘6A86’.

                  3.5.5   VERIFY

            This command is compliant with ISO/IEC 7816-4, but has a restricted usage compared to the command defined in the norm.
            Only the workshop card is required to support this command.
            Other types of tachograph cards may or may not implement this command, but for these cards no reference CHV is personalized. Therefore these cards cannot perform this commend successfully. For other types of tachograph cards than workshop cards the behavior, i.e. the error code returned, is out of the scope of this specification, if this command is sent.
            The Verify command initiates the comparison in the card of the CHV (PIN) data sent from the command with the reference CHV stored in the card.

                        TCS_72

                        The PIN entered by the user must be ASCI encoded and right padded with ‘FFh’ bytes up to a length of 8 bytes by the IFD, see also the data type WorkshopCardPIN in Appendix 1.

                        TCS_73

                        The tachograph applications generation 1 and 2 shall use the same reference CHV.

                        TCS_74

                        The tachograph card shall check whether the command is encoded correctly. If the command is not encoded correctly the card shall not compare the CHV values, not decrement the remaining CHV attempt counter and not reset the security status ‘PIN_Verified’, but abort the command. A command is encoded correctly, if the CLA, INS, P1, P2, Lc bytes have the specified values, Le is absent, and the command data field has the correct length.

                        TCS_75

                        If the command is successful, the remaining CHV attempt counter is reinitialised. The initial value of the remaining CHV attempt counter is 5. If the command is successful the card shall set the internal security status ‘PIN_Verified’. The card shall reset this security status, if the card is reset or if the CHV code transmitted in the command does not match the stored reference CHV.

                           Note: Using the same reference CHV and a global security status prevents that a workshop employee must re-enter the PIN after a selection of another tachograph application DF.

                        TCS_76

                        An unsuccessful comparison is recorded in the card, i.e. the remaining CHV attempts counter shall be decremented by one, in order to limit the number of further attempts of the use of the reference CHV.

                        TCS_77

                        Command Message

                                    Byte

                                    Length

                                    Value

                                    Description

                                    CLA

                                    1

                                    ‘00h’

                                    INS

                                    1

                                    ‘20h’

                                    INS

                                    P1

                                    1

                                    ‘00h’

                                    P1

                                    P2

                                    1

                                    ‘00h’

                                    P2 (the verified CHV is implicitly known)

                                    Lc

                                    1

                                    ‘08h’

                                    Length of CHV code transmitted

                                    #6-#13

                                    8

                                    ‘XX..XXh’

                                    CHV

                        TCS_78

                        Response Message

                                    Byte

                                    Length

                                    Value

                                    Description

                                    SW

                                    2

                                    ‘XXXXh’

                                    Status Words (SW1,SW2)

                                    —

                                    If the command is successful, the card returns ‘9000’.

                                    —

                                    If the reference CHV is not found, the processing state returned is ‘6A88’.

                                    —

                                    If the CHV is blocked, (the remaining attempt counter of the CHV is null), the processing state returned is ‘6983’. Once in that state, the CHV can never be successfully presented anymore.

                                    —

                                    If the comparison is unsuccessful, the remaining attempt Counter is decreased and the status ‘63CX’ is returned (X>0 and X equals the remaining CHV attempts counter.

                                    —

                                    If the reference CHV is considered corrupted, the processing state returned is ‘6400’ or ‘6581’.

                                    —

                                    If Lc is different from ‘08h’, the processing state is ‘6700’.

                  3.5.6   GET RESPONSE

            This command is compliant with ISO/IEC 7816-4.
            This command (only necessary and available for T=0 Protocol) is used to transmit prepared data from the card to the interface device (case where a command had included both Lc and Le).
            The GET RESPONSE command has to be issued immediately after the command preparing the data, otherwise, the data are lost. After the execution of the GET RESPONSE command (except if the error ‘61xx’ or ‘6Cxx’ occur, see below), the previously prepared data are no longer available.

                        TCS_79

                        Command Message

                                    Byte

                                    Length

                                    Value

                                    Description

                                    CLA

                                    1

                                    ‘00h’

                                    INS

                                    1

                                    ‘C0h’

                                    P1

                                    1

                                    ‘00h’

                                    P2

                                    1

                                    ‘00h’

                                    Le

                                    1

                                    ‘XXh’

                                    Number of bytes expected

                        TCS_80

                        Response Message

                                    Byte

                                    Length

                                    Value

                                    Description

                                    #1-#X

                                    X

                                    ‘XX..XXh’

                                    Data

                                    SW

                                    2

                                    ‘XXXXh’

                                    Status Words (SW1,SW2)

                                    —

                                    If the command is successful, the card returns ‘9000’.

                                    —

                                    If no data have been prepared by the card, the processing state returned is ‘6900’ or ‘6F00’.

                                    —

                                    If Le exceeds the number of available bytes or if Le is null, the processing state returned is ‘6Cxx’, where xx denotes the exact number of available bytes. In that case, the prepared data are still available for a subsequent GET RESPONSE command.

                                    —

                                    If Le is not null and is smaller than the number of available bytes, the required data are sent normally by the card, and the processing state returned is ‘61xx’, where ‘xx’ indicates a number of extra bytes still available by a subsequent GET RESPONSE command.

                                    —

                                    If the command is not supported (protocol T=1), the card returns ‘6D00’.

                  3.5.7   PSO: VERIFY CERTIFICATE

            This command is compliant with ISO/IEC 7816-8, but has a restricted usage compared to the command defined in the norm.
            The VERIFY CERTIFICATE command is used by the card to obtain a Public Key from the outside and to check its validity.
            3.5.7.1   Generation 1 Command — Response pair

                        TCS_81

                        This command variant is only supported by a generation 1 tachograph application.

                        TCS_82

                        When a VERIFY CERTIFICATE command is successful, the Public Key is stored for a future use in the Security environment. This key shall be explicitly set for the use in security related commands (INTERNAL AUTHENTICATE, EXTERNAL AUTHENTICATE or VERIFY CERTIFICATE) by the MSE command (see § 3.5.11) using its key identifier.

                        TCS_83

                        In any case, the VERIFY CERTIFICATE command uses the public key previously selected by the MSE command to open the certificate. This public key must be the one of a Member State or of Europe.

                        TCS_84

                        Command Message

                                    Byte

                                    Length

                                    Value

                                    Description

                                    CLA

                                    1

                                    ‘00h’

                                    INS

                                    1

                                    ‘2Ah’

                                    Perform Security Operation

                                    P1

                                    1

                                    ‘00h’

                                    P1

                                    P2

                                    1

                                    ‘AEh’

                                    P2: non BER-TLV coded data (concatenation of data elements)

                                    Lc

                                    1

                                    ‘C2h’

                                    Lc: Length of the certificate, 194 bytes

                                    #6-#199

                                    194

                                    ‘XX..XXh’

                                    Certificate: concatenation of data elements (as described in Appendix 11)

                        TCS_85

                        Response Message

                                    Byte

                                    Length

                                    Value

                                    Description

                                    SW

                                    2

                                    ‘XXXXh’

                                    Status Words (SW1,SW2)

                                    —

                                    If the command is successful, the card returns ‘9000’.

                                    —

                                    If the certificate verification fails, the processing state returned is ‘6688’. The verification and unwrapping process of the certificate is described in Appendix 11 for G1 and G2.

                                    —

                                    If no Public Key is present in the Security Environment, ‘6A88’ is returned.

                                    —

                                    If the selected public key (used to unwrap the certificate) is considered corrupted, the processing state returned is ‘6400’ or ‘6581’.

                                    —

                                 Generation 1 only: If the selected public key (used to unwrap the certificate) has a CHA.LSB (Text of image

                                       CertificateHolderAuthorisation.equipmentType
                                    ) different from ‘00’ (i.e. is not the one of a Member State or of Europe), the processing state returned is ‘6985’.

                  3.5.7.2   Generation 2 Command — Response pair

            Depending on the curve size ECC certificates may be so long that they cannot be transmitted in a single APDU. In this case command chaining according to ISO/IEC 7816-4 must be applied and the certificate transmitted in two consecutive PSO: Verify Certificate APDUs.
            The certificate structure and the domain parameters are defined in Appendix 11.

                        TCS_86

                        The command can be performed in the MF, DF Tachograph and DF Tachograph_G2, see also TCS_33.

                        TCS_87

                        Command Message

                                    Byte

                                    Length

                                    Value

                                    Description

                                    CLA

                                    1

                                    ‘X0h’

                                    CLA byte indicating command chaining:

                                                ‘00h’ the only or last command of the chain

                                                ‘10h’ not the last command of a chain

                                    INS

                                    1

                                    ‘2Ah’

                                    Perform Security Operation

                                    P1

                                    1

                                    ‘00h’

                                    P2

                                    1

                                    ‘BEh’

                                    Verify self-descriptive certificate

                                    Lc

                                    1

                                    ‘XXh’

                                    Length of the command data field, see TCS_88 and TCS_89.

                                    #6-#5+L

                                    L

                                    ‘XX..XXh’

                                    DER-TLV encoded data: ECC Certificate Body data object as first data object concatenated with the ECC Certificate Signature data object as second data object or a part of this concatenation. The tag ‘7F21’ and the corresponding length shall not be transmitted.
                                    The order of these data objects is fixed.

                        TCS_88

                        For short length APDUs the following provisions apply: The IFD shall use the minimum number of APDUs required to transmit the command payload and transmit the maximum number of bytes in the first command APDU according to the value of the Information Field Size Card Byte, see TCS_14. If the IFD behaves differently, the behavior of the card is out of scope.

                        TCS_89

                        For extended length APDUs the following provisions apply: If the certificate does not fit into a single APDU, the card shall support command chaining. The IFD shall use the minimum number of APDUs required to transmit the command payload and transmit the maximum number of bytes in the first command APDU. If the IFD behaves differently, the behavior of the card is out of scope.

                           Note: According to Appendix 11 the card stores the certificate or the relevant contents of the certificate and updates its currentAuthenticatedTime.
                        The response message structure and status words are as defined in TCS_85.

                        TCS_90

                        In addition to the error codes listed in TCS_85, the card may return the following error codes:

                                    —

                                    If the selected public key (used to unwrap the certificate) has a CHA.LSB (CertificateHolderAuthorisation.equipmentType) that is not suitable for the certificate verification according to Appendix 11, the processing state returned is ‘6985’.

                                    —

                                    If the currentAuthenticatedTime of the card is later than the Certificate Expiration Date, the processing state returned is ‘6985’.

                                    —

                                    If the last command of the chain is expected, the card returns ‘6883’.

                                    —

                                    If incorrect parameters are sent in the command data field, the card returns ‘6A80’ (also used in case the data objects are not sent in the specified order).

                  3.5.8   INTERNAL AUTHENTICATE

            This command is compliant with ISO/IEC 7816-4.

                        TCS_91

                        All tachograph cards shall support this command in the DF Tachograph generation 1. The command may or may not be accessible in the MF and / or the DF Tachograph_G2. If so, the command shall terminate with a suitable error code as the private key of the card (Card.SK) for the generation 1 authentication protocol is only accessible in the DF_Tachograph generation 1.

                  Using the INTERNAL AUTHENTICATE command, the IFD can authenticate the card. The authentication process is described in Appendix 11. It includes the following statements:

                        TCS_92

                        The INTERNAL AUTHENTICATE command uses the card Private Key (implicitly selected) to sign authentication data including K1 (first element for session key agreement) and RND1, and uses the Public Key currently selected (through the last MSE command) to encrypt the signature and form the authentication token (more details in Appendix 11).

                        TCS_93

                        Command Message

                                    Byte

                                    Length

                                    Value

                                    Description

                                    CLA

                                    1

                                    ‘00h’

                                    CLA

                                    INS

                                    1

                                    ‘88h’

                                    INS

                                    P1

                                    1

                                    ‘00h’

                                    P1

                                    P2

                                    1

                                    ‘00h’

                                    P2

                                    Lc

                                    1

                                    ‘10h’

                                    Length of data sent to the card

                                    #6 — #13

                                    8

                                    ‘XX..XXh’

                                    Challenge used to authenticate the card

                                    #14 -#21

                                    8

                                    ‘XX..XXh’

                                    VU.CHR (see Appendix 11)

                                    Le

                                    1

                                    ‘80h’

                                    Length of the data expected from the card

                        TCS_94

                        Response Message

                                    Byte

                                    Length

                                    Value

                                    Description

                                    #1-#128

                                    128

                                    ‘XX..XXh’

                                    Card authentication token (see Appendix 11)

                                    SW

                                    2

                                    ‘XXXXh’

                                    Status Words (SW1,SW2)

                                    —

                                    If the command is successful, the card returns ‘9000’.

                                    —

                                    If no Public Key is present in the Security Environment, the processing state returned is ‘6A88’.

                                    —

                                    If no Private Key is present in the Security Environment, the processing state returned is ‘6A88’.

                                    —

                                    If VU.CHR does not match the current public key identifier, the processing state returned is ‘6A88’.

                                    —

                                    If the selected private key is considered corrupted, the processing state returned is ‘6400’ or ‘6581’.

                        TCS_95

                        If the INTERNAL AUTHENTICATE command is successful, the current session key, if existing, is erased and no longer available. In order to have a new session key available, the EXTERNAL AUTHENTICATE command for the generation 1 authentication mechanism must be successfully performed.

                  3.5.9   EXTERNAL AUTHENTICATE

            This command is compliant with ISO/IEC 7816-4.
            Using the EXTERNAL AUTHENTICATE command, the card can authenticate the IFD. The authentication process is described in Appendix 11 for Tachograph G1 and G2 (VU authentication).

                        TCS_96

                        The command variant for the generation 1 mutual authentication mechanism is only supported by a generation 1 tachograph application.

                        TCS_97

                        The command variant for the second generation VU-card mutual authentication can be performed in the MF, DF Tachograph and DF Tachograph_G2, see also TCS_34.

                        TCS_98

                        Command Message

                                    Byte

                                    Length

                                    Value

                                    Description

                                    CLA

                                    1

                                    ‘00h’

                                    CLA

                                    INS

                                    1

                                    ‘82h’

                                    INS

                                    P1

                                    1

                                    ‘00h’

                                    Keys and algorithms implicitly known

                                    P2

                                    1

                                    ‘00h’

                                    Lc

                                    1

                                    ‘XXh’

                                    Lc (Length of the data sent to the card )

                                    #6-#(5+L)

                                    L

                                    ‘XX..XXh’

                                    Generation 1 authentication: Cryptogram (see Appendix 11 Part A)
                                    Generation 2 authentication: Signature generated by the IFD (see Appendix 11 Part B)

                        TCS_99

                        Response Message

                                    Byte

                                    Length

                                    Value

                                    Description

                                    SW

                                    2

                                    ‘XXXXh’

                                    Status Words (SW1,SW2)

                                    —

                                    If the command is successful, the card returns ‘9000’.

                                    —

                                    If the CHA of the currently set public key is not the concatenation of the Tachograph application AID and of a VU equipment Type, the processing state returned is ‘6F00’.

                                    —

                                    If the command is not immediately preceded with a GET CHALLENGE command, the processing state returned is ‘6985’.

                              The Generation 1 Tachograph application may return the following additional error codes:

                                    —

                                    If no Public Key is present in the Security Environment, ‘6A88’ is returned.

                                    —

                                    If no Private Key is present in the Security Environment, the processing state returned is ‘6A88’.

                                    —

                                    If the verification of the cryptogram is wrong, the processing state returned is ‘6688’.

                                    —

                                    If the selected private key is considered corrupted, the processing state returned is ‘6400’ or ‘6581’.

                              The command variant for the Generation 2 authentication may return the following additional error code:

                                    —

                                    If signature verification failed, the card returns ‘6300’.

                  3.5.10   GENERAL AUTHENTICATE

            This command is used for the generation 2 chip authentication protocol specified in Appendix 11 Part B and is compliant with ISO/IEC 7816-4.

                        TCS_100

                        The command can be performed in the MF, DF Tachograph and DF Tachograph_G2, see also TCS_34.

                        TCS_101

                        Command Message

                                    Byte

                                    Length

                                    Value

                                    Description

                                    CLA

                                    1

                                    ‘00h’

                                    INS

                                    1

                                    ‘86h’

                                    P1

                                    1

                                    ‘00h’

                                    Keys and protocol implicitly known

                                    P2

                                    1

                                    ‘00h’

                                    Lc

                                    1

                                    ‘NNh’

                                    Lc: length of subsequent data field

                                    #6-#(5+L)

                                    L

                                    ‘7Ch’ + L7C + ‘80h’ + L80 + ‘XX..XXh’

                                    DER-TLV encoded ephemeral public key value (see Appendix 11)
                                    The VU shall send the data objects in this order.

                        TCS_102

                        Response Message

                                    Byte

                                    Length

                                    Value

                                    Description

                                    #1-#L

                                    L

                                    ‘7Ch’ + L7C + ‘81h’ + ‘08h’ + ‘XX..XXh’ + ‘82h’ + L82 + ‘XX..XXh’

                                    DER-TLV encoded Dynamic Authentication Data: nonce and authentication token (see Appendix 11)

                                    SW

                                    2

                                    ‘XXXXh’

                                    Status Words (SW1,SW2)

                                    —

                                    If the command is successful, the card returns ‘9000’.

                                    —

                                    The card returns ‘6A80’ to indicate incorrect parameters in data field.

                                    —

                                    The card returns ‘6982’ if the External Authenticate command has not been performed successfully

                              The response Dynamic Authentication Data object ‘7Ch’

                                    —

                                    must be present if the operation is successful, i.e. the Status Words are ‘9000’,

                                    —

                                    must be absent in case of an execution error or checking error, i.e. if the Status Words are in the range ‘6400’ — ‘6FFF’, and

                                    —

                                    may be absent in case of a warning, i.e. if the Status Words are in the range ‘6200’ — ‘63FF’.

                  3.5.11   MANAGE SECURITY ENVIRONMENT

            This command is used to set a public key for authentication purpose.
            3.5.11.1   Generation 1 Command — Response pair

            This command is compliant with ISO/IEC 7816-4. The use of this command is restricted regarding the related standard.

                        TCS_103

                        This command is only supported by a generation 1 tachograph application.

                        TCS_104

                        The key referenced in the MSE data field remains the current public key until the next correct MSE command, a DF is selected or the card is reset.

                        TCS_105

                        If the key referenced is not (already) present into the card, the security environment remains unchanged.

                        TCS_106

                        Command Message

                                    Byte

                                    Length

                                    Value

                                    Description

                                    CLA

                                    1

                                    ‘00h’

                                    CLA

                                    INS

                                    1

                                    ‘22h’

                                    INS

                                    P1

                                    1

                                    ‘C1h’

                                    P1: referenced key valid for all cryptographic operations

                                    P2

                                    1

                                    ‘B6h’

                                    P2 (referenced data concerning Digital Signature)

                                    Lc

                                    1

                                    ‘0Ah’

                                    Lc: length of subsequent data field

                                    #6

                                    1

                                    ‘83h’

                                    Tag for referencing a public key in asymmetric cases

                                    #7

                                    1

                                    ‘08h’

                                    Length of the key reference (key identifier)

                                    #8-#15

                                    8

                                    ‘XX..XXh’

                                    Key identifier as specified in Appendix 11

                        TCS_107

                        Response Message

                                    Byte

                                    Length

                                    Value

                                    Description

                                    SW

                                    2

                                    ‘XXXXh’

                                    Status Words (SW1,SW2)

                                    —

                                    If the command is successful, the card returns ‘9000’.

                                    —

                                    If the referenced key is not present into the card, the processing state returned is ‘6A88’.

                                    —

                                    If some expected data objects are missing in the secure messaging format, the processing state ‘6987’ is returned. This can happen if the tag ‘83h’ is missing.

                                    —

                                    If some data objects are incorrect, the processing state returned is ‘6988’. This can happen if the length of the key identifier is not ‘08h’.

                                    —

                                    If the selected key is considered corrupted, the processing state returned is ‘6400’ or ‘6581’.

                  3.5.11.2   Generation 2 Command — Response pairs

            For the Generation 2 authentication the tachograph card supports the following MSE: Set command versions which are compliant with ISO/IEC 7816-4. These command versions are not supported for the Generation 1 authentication.
            3.5.11.2.1   MSE:SET AT for Chip Authentication

            The following MSE:SET AT command is used to select the parameters for the Chip Authentication that is performed by a subsequent General Authenticate command.

                        TCS_108

                        The command can be performed in the MF, DF Tachograph and DF Tachograph_G2, see also TCS_34.

                        TCS_109

                        MSE:SET AT Command Message for Chip Authentication

                                    Byte

                                    Length

                                    Value

                                    Description

                                    CLA

                                    1

                                    ‘00h’

                                    INS

                                    1

                                    ‘22h’

                                    P1

                                    1

                                    ‘41h’

                                    Set for internal authentication

                                    P2

                                    1

                                    ‘A4h’

                                    Authentication

                                    Lc

                                    1

                                    ‘NNh’

                                    Lc: length of subsequent data field

                                    #6-#(5+L)

                                    L

                                    ‘80h’ + ‘0Ah’ + ‘XX..XXh’

                                    DER-TLV encoded cryptographic mechanism reference: Object Identifier of Chip Authentication (value only, Tag ‘06h’ is omitted).
                                    See Appendix 1 for the values of object identifiers; the byte notation shall be used. See Appendix 11 for guidance on how to select one of these object identifiers.

                  3.5.11.2.2   MSE:SET AT for VU Authentication

            The following MSE:SET AT command is used to select the parameters and keys for the VU Authentication that is performed by a subsequent External Authenticate command.

                        TCS_110

                        The command can be performed in the MF, DF Tachograph and DF Tachograph_G2, see also TCS_34.

                        TCS_111

                        MSE:SET AT Command Message for VU Authentication

                                    Byte

                                    Length

                                    Value

                                    Description

                                    CLA

                                    1

                                    ‘00h’

                                    INS

                                    1

                                    ‘22h’

                                    P1

                                    1

                                    ‘81h’

                                    Set for external authentication

                                    P2

                                    1

                                    ‘A4h’

                                    Authentication

                                    Lc

                                    1

                                    ‘NNh’

                                    Lc: length of subsequent data field

                                    #6-#(5+L)

                                    L

                                    ‘80h’ + ‘0Ah’ + ‘XX..XXh’

                                    DER-TLV encoded cryptographic mechanism reference: Object Identifier of VU Authentication (value only, Tag ‘06h’ is omitted).
                                    See Appendix 1 for the values of object identifiers; the byte notation shall be used. See Appendix 11 for guidance on how to select one of these object identifiers.

                                    ‘83h’ + ‘08h’ + ‘XX..XXh’

                                    DER-TLV encoded reference of the VU public key by the Certificate Holder Reference mentioned in its certificate.

                                    ‘91h’ + L91 + ‘XX..XXh’

                                    DER-TLV encoded compressed representation of the ephemeral public key of the VU that will be used during Chip Authentication (see Appendix 11)

                  3.5.11.2.3   MSE:SET DST

            The following MSE:SET DST command is used to set a public key either

                        —

                        for the verification of a signature that is provided in a subsequent PSO: Verify Digital Signature command or

                        —

                        for the signature verification of a certificate that is provided in a subsequent PSO: Verify Certificate command

                        TCS_112

                        The command can be performed in the MF, DF Tachograph and DF Tachograph_G2, see also TCS_33.

                        TCS_113

                        MSE:SET DST Command Message

                                    Byte

                                    Length

                                    Value

                                    Description

                                    CLA

                                    1

                                    ‘00h’

                                    INS

                                    1

                                    ‘22h’

                                    P1

                                    1

                                    ‘81h’

                                    Set for verification

                                    P2

                                    1

                                    ‘B6h’

                                    Digital Signature

                                    Lc

                                    1

                                    ‘NNh’

                                    Lc: length of subsequent data field

                                    #6-#(5+L)

                                    L

                                    ‘83h’ + ‘08h’ + ‘XX...XXh’

                                    DER-TLV encoded reference of a public key, i.e. the Certificate Holder Reference in the certificate of the public key (see Appendix 11)

                  For all command versions the response message structure and status words are given by:

                        TCS_114

                        Response Message

                                    Byte

                                    Length

                                    Value

                                    Description

                                    SW

                                    2

                                    ‘XXXXh’

                                    Status Words (SW1,SW2)

                                    —

                                    If the command is successful, the card returns ‘9000’. The protocol has been selected and initialised.

                                    —

                                    ‘6A80’ indicates incorrect parameters in the command data field.

                                    —

                                    ‘6A88’ indicates that referenced data (i.e. a referenced key) is not available.

                  3.5.12   PSO: HASH

            This command is used to transfer to the card the result of a hash calculation on some data. This command is used for the verification of digital signatures. The hash value is stored temporarily for the subsequent command PSO: Verify Digital Signature
            This command is compliant with ISO/IEC 7816-8. The use of this command is restricted regarding the related standard.
            Only the control card is required to support this command in the DF Tachograph and DF Tachograph_G2.
            Other types of tachograph cards may or may not implement this command. The command may or may not be accessible in the MF.
            The control card application generation 1 supports only SHA-1.

                        TCS_115

                        The temporarily stored hash value shall be deleted if a new hash value is computed by means of the PSO: HASH command, if a DF is selected, and if the tachograph card is reset.

                        TCS_116

                        Command Message

                                    Byte

                                    Length

                                    Value

                                    Description

                                    CLA

                                    1

                                    ‘00h’

                                    CLA

                                    INS

                                    1

                                    ‘2Ah’

                                    Perform Security Operation

                                    P1

                                    1

                                    ‘90h’

                                    Return Hash code

                                    P2

                                    1

                                    ‘A0h’

                                    Tag: data field contains DOs relevant for hashing

                                    Lc

                                    1

                                    ‘XXh’

                                    Length Lc of the subsequent data field

                                    #6

                                    1

                                    ‘90h’

                                    Tag for the hash code

                                    #7

                                    1

                                    ‘XXh’

                                    Length L of the hash code:

                                                ‘14h’ in Generation 1 application (see Appendix 11 Part A)

                                                ‘20h’, ‘30h’ or ‘40h’ in Generation 2 application (see Appendix 11 Part B)

                                    #8-#(7+L)

                                    L

                                    ‘XX..XXh’

                                    Hash code

                        TCS_117

                        Response Message

                                    Byte

                                    Length

                                    Value

                                    Description

                                    SW

                                    2

                                    ‘XXXXh’

                                    Status Words (SW1,SW2)

                                    —

                                    If the command is successful, the card returns ‘9000’.

                                    —

                                    If some expected data objects (as specified above) are missing, the processing state ‘6987’ is returned. This can happen if one of the tag ‘90h’ is missing.

                                    —

                                    If some data objects are incorrect, the processing state returned is ‘6988’. This error happens if the required tag is present but with a length different from ‘14h’ for SHA-1, ‘20h’ for SHA-256, ‘30h’ for SHA-384, ‘40h’ for SHA-512 (Generation 2 application).

                  3.5.13   PERFORM HASH of FILE

            This command is not compliant with ISO/IEC 7816-8. Thus the CLA byte of this command indicates that there is a proprietary use of the PERFORM SECURITY OPERATION / HASH.
            Only the driver card and the workshop card are required to support this command in the DF Tachograph and DF Tachograph_G2.
            Other types of tachograph cards may or may not implement this command. If a company or control card implements this command, the command shall be implemented as specified in this chapter.
            The command may or may not be accessible in the MF. If so, the command shall be implemented as specified in this chapter, i.e. shall not allow the calculation of a hash value, but terminate with a suitable error code.

                        TCS_118

                        The PERFORM HASH of FILE command is used to hash the data area of the currently selected transparent EF.

                        TCS_119

                        A tachograph card shall support this command only for the EFs that are listed in chapter 4 under the DF_Tachograph and DF_Tachograph_G2 with the following exception. A tachograph card shall not support the command for the EF Sensor_Installation_Data of DF Tachograph_G2..

                        TCS_120

                        The result of the hash operation is stored temporarily in the card. It can then be used to get a digital signature of the file, using the PSO: COMPUTE DIGITAL SIGNATURE command.

                        TCS_121

                        The temporarily stored hash of file value shall be deleted if a new hash of file value is computed by means of the PSO: Hash of File command, if a DF is selected, and if the tachograph card is reset.

                        TCS_122

                        The Tachograph Generation 1 application shall support SHA-1.

                        TCS_123

                        The Tachograph Generation 2 application shall support SHA-1 and SHA-2 (256, 384 and 512 bits).

                        TCS_124

                        Command Message

                                    Byte

                                    Length

                                    Value

                                    Description

                                    CLA

                                    1

                                    ‘80h’

                                    CLA

                                    INS

                                    1

                                    ‘2Ah’

                                    Perform Security Operation

                                    P1

                                    1

                                    ‘90h’

                                    Tag: Hash

                                    P2

                                    1

                                    ‘XXh’

                                    P2: Indicates the algorithm to be used for hashing of the data of the currently selected transparent file:

                                                ‘00h’ for SHA-1

                                                ‘01h’ for SHA-256

                                                ‘02h’ for SHA-384

                                                ‘03h’ for SHA-512

                        TCS_125

                        Response Message

                                    Byte

                                    Length

                                    Value

                                    Description

                                    SW

                                    2

                                    ‘XXXXh’

                                    Status Words (SW1,SW2)

                                    —

                                    If the command is successful, the card returns ‘9000’.

                                    —

                                    If the current EF does not allow this command (EF Sensor_Installation_Data in DF Tachograph_G2), the processing state ‘6985’ is returned.

                                    —

                                    If the selected EF is considered corrupted (file attributes or stored data integrity errors), the processing state returned is ‘6400’ or ‘6581’.

                                    —

                                    If the selected file is not a transparent file or if there is no current EF, the processing state returned is ‘6986’.

                  3.5.14   PSO: COMPUTE DIGITAL SIGNATURE

            This command is used to compute the digital signature of previously computed hash code (see PERFORM HASH of FILE, §3.5.13).
            Only the driver card and the workshop card are required to support this command in the DF Tachograph and DF Tachograph_G2.
            Other types of tachograph cards may or may not implement this command, but shall not have a signature key. Therefore these cards cannot perform the command successfully, but terminate with a suitable error code.
            The command may or may not be accessible in the MF. If so, the command shall terminate with a suitable error code.
            This command is compliant with ISO/IEC 7816-8. The use of this command is restricted regarding the related standard.

                        TCS_126

                        This command shall not compute a digital signature of previously computed hash code with the PSO: HASH command.

                        TCS_127

                        The card private key is used to compute the digital signature and is implicitly known by the card.

                        TCS_128

                        The Generation 1 tachograph application performs a digital signature using a padding method compliant with PKCS1 (see Appendix 11 for details).

                        TCS_129

                        The Generation 2 tachograph application computes an elliptic curve based digital signature (see Appendix 11 for details).

                        TCS_130

                        Command Message

                                    Byte

                                    Length

                                    Value

                                    Description

                                    CLA

                                    1

                                    ‘00h’

                                    CLA

                                    INS

                                    1

                                    ‘2Ah’

                                    Perform Security Operation

                                    P1

                                    1

                                    ‘9Eh’

                                    Digital signature to be returned

                                    P2

                                    1

                                    ‘9Ah’

                                    Tag: data field contains data to be signed. As no data field is included, the data are supposed to be already present in the card (hash of file)

                                    Le

                                    1

                                    ‘NNh’

                                    Length of the expected signature

                        TCS_131

                        Response Message

                                    Byte

                                    Length

                                    Value

                                    Description

                                    #1-#L

                                    L

                                    ‘XX..XXh’

                                    Signature of the previously computed hash

                                    SW

                                    2

                                    ‘XXXXh’

                                    Status Words (SW1,SW2)

                                    —

                                    If the command is successful, the card returns ‘9000’.

                                    —

                                    If the implicitly selected private key is considered as corrupted, the processing state returned is ‘6400’ or ‘6581’.

                                    —

                                    If the hash which was computed in a previous Perform Hash of File command is not available, the processing state returned is ‘6985’.

                  3.5.15   PSO: VERIFY DIGITAL SIGNATURE

            This command is used to verify the digital signature, provided as an input, whose hash is known to the card. The signature algorithm is implicitly known by the card.
            This command is compliant with ISO/IEC 7816-8. The use of this command is restricted regarding the related standard.
            Only the control card is required to support this command in the DF Tachograph and DF Tachograph_G2.
            Other types of tachograph cards may or may not implement this command. The command may or may not be accessible in the MF.

                        TCS_132

                        The VERIFY DIGITAL SIGNATURE command always uses the public key selected by the previous Manage Security Environment MSE: Set DST command and the previous hash code entered by a PSO: HASH command.

                        TCS_133

                        Command Message

                                    Byte

                                    Length

                                    Value

                                    Description

                                    CLA

                                    1

                                    ‘00h’

                                    CLA

                                    INS

                                    1

                                    ‘2Ah’

                                    Perform Security Operation

                                    P1

                                    1

                                    ‘00h’

                                    P2

                                    1

                                    ‘A8h’

                                    Tag: data field contains DOs relevant for verification

                                    Lc

                                    1

                                    ‘83h’

                                    Length Lc of the subsequent data field

                                    6

                                    1

                                    ‘9Eh’

                                    Tag for Digital Signature

                                    #7-#8

                                    2

                                    ‘81 XXh’

                                    Length of digital signature:

                                                128 bytes coded in accordance with Appendix 11 Part A for Tachograph Generation 1 application

                                                Depending on the selected curve for Tachograph Generation 2 application (see Appendix 11 Part B)

                                    #9-#(8+L)

                                    L

                                    ‘XX..XXh’

                                    Digital signature content

                        TCS_134

                        Response Message

                                    Byte

                                    Length

                                    Value

                                    Description

                                    SW

                                    2

                                    ‘XXXXh’

                                    Status Words (SW1,SW2)

                                    —

                                    If the command is successful, the card returns ‘9000’.

                                    —

                                    If the verification of the signature fails, the processing state returned is ‘6688’. The verification process is described in Appendix 11.

                                    —

                                    If no public key is selected, the processing state returned is ‘6A88’.

                                    —

                                    If some expected data objects (as specified above) are missing, the processing state ‘6987’ is returned. This can happen if one of the required tag is missing.

                                    —

                                    If no hash code is available to process the command (as a result of a previous PSO: Hash command), the processing state returned is ‘6985’.

                                    —

                                    If some data objects are incorrect, the processing state returned is ‘6988’. This can happen if one of the required data objects length is incorrect.

                                    —

                                    If the selected public key is considered corrupted, the processing state returned is ‘6400’ or ‘6581’.

                  3.5.16   PROCESS DSRC MESSAGE

            This command is used to verify the integrity and authenticity of the DSRC message and to decipher the data communicated from a VU to a control authority or a workshop over the DSRC link. The card derives the encryption key and the MAC key used to secure the DSRC message as described in Appendix 11 Part B chapter 13.
            Only the control card and the workshop card are required to support this command in the DF Tachograph_G2.
            Other types of tachograph cards may or may not implement this command, but shall not have a DSRC master key. Therefore these cards cannot perform the command successfully, but terminate with a suitable error code.
            The command may or may not be accessible in the MF and / or the DF Tachograph. If so, the command shall terminate with a suitable error code.

                        TCS_135

                        The DSRC master key is accessible only in the DF Tachograph_G2, i.e. the control and workshop card shall support a successful execution of the command only in the DF Tachograph_G2.

                        TCS_136

                        The command shall only decrypt the DSRC data and verify the cryptographic checksum, but not interpret the input data.

                        TCS_137

                        The order of the data objects in the command data field is fixed by this specification.

                        TCS_138

                        Command Message

                                    Byte

                                    Length

                                    Value

                                    Description

                                    CLA

                                    1

                                    ‘80h’

                                    Proprietary CLA

                                    INS

                                    1

                                    ‘2Ah’

                                    Perform Security Operation

                                    P1

                                    1

                                    ‘80h’

                                    Response data: plain value

                                    P2

                                    1

                                    ‘B0h’

                                    Command data: plain value encoded in BER-TLV and including SM DOs

                                    Lc

                                    1

                                    ‘NNh’

                                    Length Lc of the subsequent data field

                                    #6-#(5+L)

                                    L

                                    ‘87h’ + L87 + ‘XX..XXh’

                                    DER-TLV encoded padding-content indicator byte followed by encrypted tachograph payload. For the padding-content indicator byte the value ‘00h’ (‘no further indication’ according to ISO/IEC 7816-4:2013 Table 52) shall be used. For the encryption mechanism see Appendix 11, Part B chapter 13.
                                    Allowed values for the length L87 are the multiples of the AES block length plus 1 for the padding-content indicator byte, i.e. from 17 bytes up to and including 193 bytes.

                                       Note: See ISO/IEC 7816-4:2013 Table 49 for the SM data object with tag ‘87h’.

                                    ‘81h’ + ‘10h’

                                    DER-TLV encoded Control Reference Template for Confidentiality nesting the concatenation of the following data elements (see Appendix 1 DSRCSecurityData and Appendix 11 Part B chapter 13):

                                                —

                                                4 byte time stamp

                                                —

                                                3 byte counter

                                                —

                                                8 byte VU serial number

                                                —

                                                1 byte DSRC master key version

                                       Note: See ISO/IEC 7816-4:2013 Table 49 for the SM data object with tag ‘81h’.

                                    ‘8Eh’ + L8E + ‘XX..XXh’

                                    DER-TLV encoded MAC over the DSRC message. For the MAC algorithm and calculation see Appendix 11, Part B chapter 13.

                                       Note: See ISO/IEC 7816-4:2013 Table 49 for the SM data object with tag ‘8Eh’.

                        TCS_139

                        Response Message

                                    Byte

                                    Length

                                    Value

                                    Description

                                    #1-#L

                                    L

                                    ‘XX..XXh’

                                    Absent (in case of an error) or deciphered data (padding removed)

                                    SW

                                    2

                                    ‘XXXXh’

                                    Status Words (SW1,SW2)

                                    —

                                    If the command is successful, the card returns ‘9000’.

                                    —

                                    ‘6A80’ indicates incorrect parameters in the command data field (also used in case the data objects are not sent in the specified order).

                                    —

                                    ‘6A88’ indicates that referenced data is not available, i.e. the referenced DSRC master key is not available.

                                    —

                                    ‘6900’ indicates that the verification of the cryptographic checksum or the decryption of the data failed

                  4.   TACHOGRAPH CARDS STRUCTURE
            This paragraph specifies the file structures of the Tachograph cards for storage of accessible data.It does not specify card manufacturer dependent internal structures, such as e.g. file headers, nor storage and handling of data elements needed for internal use only such asText of image

               EuropeanPublicKey
            ,Text of image

               CardPrivateKey
            ,Text of image

               TdesSessionKey
             orText of image

               WorkshopCardPin
            .

                        TCS_140

                        A generation 2 tachograph card shall host the Master File MF and a generation 1 and a generation 2 tachograph application of the same type (e.g. driver card applications).

                        TCS_141

                        A tachograph card shall support at least the minimum number of records specified for the corresponding applications and shall not support more records than the maximum number of records specified for the corresponding applications.
                        The maximum and minimum numbers of records are specified in this chapter for the different applications.
                        For the security conditions used in the access rules throughout this chapter please refer to chapter 3.3. In general the access mode ‘read’ denotes the READ BINARY command with even and if supported odd INS byte with the exception of the EF Sensor_Installation_Data on the workshop card, see TCS_156 and TCS_160. The access mode ‘update’ denotes the Update Binary command with even and if supported odd INS byte and the access mode ‘select’ the SELECT command.

                  4.1.   Master File MF

                        TCS_142

                        After its personalisation, the master file MF shall have the following permanent file structure and file access rules:

                           Note: The short EF identifier SFID is given as decimal number, e.g. the value 30 corresponds to 11110 in binary.
                        Text of image

                           Access rules
                           File
                           File ID
                           SFID
                           Read / Select
                           Update
                           MF
                           ‘3F00h’
                           EF
                           ICC
                           ‘0002h’
                           ALW
                           NEV
                           EF
                           IC
                           ‘0005h’
                           ALW
                           NEV
                           EF
                           DIR
                           ‘2F00h’
                           30
                           ALW
                           NEV
                           EF
                           ATR/INFO (conditional)
                           ‘2F01h’
                           29
                           ALW
                           NEV
                           EF
                           Extended_Length (conditional)
                           ‘0006h’
                           28
                           ALW
                           NEV
                           DF
                           Tachograph
                           ‘0500h’
                           SC1
                           DF
                           Tachograph_G2
                           SC1

                        The following abbreviation for the security condition is used in this table:

                                       SC1

                                    ALW OR SM-MAC-G2

                        TCS_143

                        All EF structures shall be transparent.

                        TCS_144

                        The Master File MF shall have the following data structure:
                        Text of image

                           No of Records
                           Size (bytes)
                           Default Values
                           File / Data element
                           Min
                           Max
                           MF
                           63
                           184
                           EF
                           ICC
                           25
                           25
                           CardIccIdentification
                           25
                           25
                           clockStop
                           1
                           1
                           {00}
                           cardExtendedSerialNumber
                           8
                           8
                           {00..00}
                           cardApprovalNumber
                           8
                           8
                           {20..20}
                           cardPersonaliserID
                           1
                           1
                           {00}
                           embedderIcAssemblerId
                           5
                           5
                           {00..00}
                           icIdentifier
                           2
                           2
                           {00 00}
                           EF
                           IC
                           8
                           8
                           CardChipIdentification
                           8
                           8
                           icSerialNumber
                           4
                           4
                           {00..00}
                           icManufacturingReferences
                           4
                           4
                           {00..00}
                           EF
                           DIR
                           20
                           20
                           See TCS_145
                           20
                           20
                           {00..00}
                           EF
                           ATR/INFO
                           7
                           128
                           See TCS_146
                           7
                           128
                           {00..00}
                           EF
                           EXTENDED_LENGTH
                           3
                           3
                           See TCS_147
                           3
                           3
                           {00..00}
                           DF
                           Tachograph
                           DF
                           Tachograph_G2

                        TCS_145

                        The elementary file EF DIR shall contain the following application related data objects: ‘61 08 4F 06 FF 54 41 43 48 4F 61 08 4F 06 FF 53 4D 52 44 54’

                        TCS_146

                        The elementary file EF ATR/INFO shall be present if the tachograph card indicates in its ATR that it supports extended length fields. In this case the EF ATR/INFO shall contain the extended length information data object (DO‘7F66’) as specified in ISO/IEC 7816-4:2013 clause 12.7.1.

                        TCS_147

                        The elementary file EF Extended_Length shall be present if the tachograph card indicates in its ATR that it supports extended length fields. In this case the EF shall contain the following data object: ‘02 01 xx’ where the value ‘xx’ indicates whether extended length fields are supported for the T = 1 and / or T = 0 protocol.
                        The value ‘01’ indicates extended length field support for the T = 1 protocol.
                        The value ‘10’ indicates extended length field support for the T = 0 protocol.
                        The value ‘11’ indicates extended length field support for the T = 1 and the T = 0 protocol.

                  4.2.   Driver card applications

            4.2.1   Driver card application generation 1

                        TCS_148

                        After its personalisation, the driver card application generation 1 shall have the following permanent file structure and file access rules:
                        Text of image

                           Access rules
                           File
                           File ID
                           Read
                           Select
                           Update
                           DF
                           Tachograph
                           ‘0500h’
                           SC1
                           EF
                           Application_Identification
                           ‘0501h’
                           SC2
                           SC1
                           NEV
                           EF
                           Card_Certificate
                           ‘C100h’
                           SC2
                           SC1
                           NEV
                           EF
                           CA_Certificate
                           ‘C108h’
                           SC2
                           SC1
                           NEV
                           EF
                           Identification
                           ‘0520h’
                           SC2
                           SC1
                           NEV
                           EF
                           Card_Download
                           ‘050Eh’
                           SC2
                           SC1
                           SC1
                           EF
                           Driving_Licence_Info
                           ‘0521h’
                           SC2
                           SC1
                           NEV
                           EF
                           Events_Data
                           ‘0502h’
                           SC2
                           SC1
                           SC3
                           EF
                           Faults_Data
                           ‘0503h’
                           SC2
                           SC1
                           SC3
                           EF
                           Driver_Activity_Data
                           ‘0504h’
                           SC2
                           SC1
                           SC3
                           EF
                           Vehicles_Used
                           ‘0505h’
                           SC2
                           SC1
                           SC3
                           EF
                           Places
                           ‘0506h’
                           SC2
                           SC1
                           SC3
                           EF
                           Current_Usage
                           ‘0507h’
                           SC2
                           SC1
                           SC3
                           EF
                           Control_Activity_Data
                           ‘0508h’
                           SC2
                           SC1
                           SC3
                           EF
                           Specific_Conditions
                           ‘0522h’
                           SC2
                           SC1
                           SC3

                        The following abbreviations for the security conditions are used in this table:

                                       SC1

                                    ALW OR SM-MAC-G2

                                       SC2

                                    ALW OR SM-MAC-G1 OR SM-MAC-G2

                                       SC3

                                    SM-MAC-G1 OR SM-MAC-G2

                        TCS_149

                        All EF structures shall be transparent.

                        TCS_150

                        The driver card application generation 1 shall have the following data structure:
                        Text of image

                           No of Records
                           Size (bytes)
                           Default Values
                           File / Data element
                           Min
                           Max
                           DF
                           Tachograph
                           11378
                           24926
                           EF
                           Application_Identification
                           10
                           10
                           DriverCardApplicationIdentification
                           10
                           10
                           typeOfTachographCardId
                           1
                           1
                           {00}
                           cardStructureVersion
                           2
                           2
                           {00 00}
                           noOfEventsPerType
                           1
                           1
                           {00}
                           noOfFaultsPerType
                           1
                           1
                           {00}
                           activityStructureLength
                           2
                           2
                           {00 00}
                           noOfCardVehicleRecords
                           2
                           2
                           {00 00}
                           noOfCardPlaceRecords
                           1
                           1
                           {00}
                           EF
                           Card_Certificate
                           194
                           194
                           CardCertificate
                           194
                           194
                           {00..00}
                           EF
                           CA_Certificate
                           194
                           194
                           MemberStateCertificate
                           194
                           194
                           {00..00}
                           EF
                           Identification
                           143
                           143
                           CardIdentification
                           65
                           65
                           cardIssuingMemberState
                           1
                           1
                           {00}
                           cardNumber
                           16
                           16
                           {20..20}
                           cardIssuingAuthorityName
                           36
                           36
                           {20..20}
                           cardIssueDate
                           4
                           4
                           {00..00}
                           cardValidityBegin
                           4
                           4
                           {00..00}
                           cardExpiryDate
                           4
                           4
                           {00..00}
                           DriverCardHolderIdentification
                           78
                           78
                           cardHolderName
                           72
                           72
                           holderSurname
                           36
                           36
                           {00, 20..20}
                           holderFirstNames
                           36
                           36
                           {00, 20..20}
                           cardHolderBirthDate
                           4
                           4
                           {00..00}
                           cardHolderPreferredLanguage
                           2
                           2
                           {20 20}
                           EF Card_Download
                           4
                           4
                           LastCardDownload
                           4
                           4
                           EF Driving_Licence_Info
                           Driving_Licence_Info
                           53
                           53
                           CardDrivingLicenceInformation
                           53
                           53
                           drivingLicenceIssuingAuthority
                           36
                           36
                           {00, 20..20}
                           drivingLicenceIssuingNation
                           1
                           1
                           {00}
                           drivingLicenceNumber
                           16
                           16
                           {20..20}
                           EF Events_Data
                           Events_Data
                           864
                           1728
                           CardEventData
                           864
                           1728
                           cardEventRecords
                           6
                           144
                           288
                           CardEventRecord
                           n1
                           24
                           24
                           eventType
                           1
                           1
                           {00}
                           eventBeginTime
                           4
                           4
                           {00..00}
                           eventEndTime
                           4
                           4
                           {00..00}
                           eventVehicleRegistration
                           vehicleRegistrationNation
                           1
                           1
                           {00}
                           vehicleRegistrationNumber
                           14
                           14
                           {00, 20..20}
                           EF Faults_Data
                           Faults_Data
                           576
                           1152
                           CardFaultData
                           576
                           1152
                           cardFaultRecords
                           2
                           288
                           576
                           CardFaultRecord
                           n2
                           24
                           24
                           faultType
                           1
                           1
                           {00}
                           faultBeginTime
                           4
                           4
                           {00..00}
                           faultEndTime
                           4
                           4
                           {00..00}
                           faultVehicleRegistration

                        Text of image

                           vehicleRegistrationNation
                           1
                           1
                           {00}
                           vehicleRegistrationNumber
                           14
                           14
                           {00, 20..20}
                           EF Driver_Activity_Data
                           Driver_Activity_Data
                           5548
                           13780
                           CardDriverActivity
                           5548
                           13780
                           activityPointerOldestDayRecord
                           2
                           2
                           {00 00}
                           activityPointerNewestRecord
                           2
                           2
                           {00 00}
                           activityDailyRecords
                           n6
                           5544
                           13776
                           {00..00}
                           EF Vehicles_Used
                           Vehicles_Used
                           2606
                           6202
                           CardVehiclesUsed
                           2606
                           6202
                           vehiclePointerNewestRecord
                           2
                           2
                           {00 00}
                           cardVehicleRecords
                           2604
                           6200
                           CardVehicleRecord
                           n3
                           31
                           31
                           vehicleOdometerBegin
                           3
                           3
                           {00..00}
                           vehicleOdometerEnd
                           3
                           3
                           {00..00}
                           vehicleFirstUse
                           4
                           4
                           {00..00}
                           vehicleLastUse
                           4
                           4
                           {00..00}
                           vehicleRegistration
                           vehicleRegistrationNation
                           1
                           1
                           {00}
                           vehicleRegistrationNumber
                           14
                           14
                           {00, 20..20}
                           vuDataBlockCounter
                           2
                           2
                           {00 00}
                           EF
                           Places
                           841
                           1121
                           CardPlaceDailyWorkPeriod
                           841
                           1121
                           placePointerNewestRecord
                           1
                           1
                           {00}
                           placeRecords
                           840
                           1120
                           PlaceRecord
                           n4
                           10
                           10
                           entryTime
                           4
                           4
                           {00..00}
                           entryTypeDailyWorkPeriod
                           1
                           1
                           {00}
                           dailyWorkPeriodCountry
                           1
                           1
                           {00}
                           dailyWorkPeriodRegion
                           1
                           1
                           {00}
                           vehicleOdometerValue
                           3
                           3
                           {00..00}
                           EF
                           Current_Usage
                           19
                           19
                           CardCurrentUse
                           19
                           19
                           sessionOpenTime
                           4
                           4
                           {00..00}
                           sessionOpenVehicle
                           vehicleRegistrationNation
                           1
                           1
                           {00}
                           vehicleRegistrationNumber
                           14
                           14
                           {00, 20..20}
                           EF
                           Control_Activity_Data
                           46
                           46
                           CardControlActivityDataRecord
                           46
                           46
                           controlType
                           1
                           1
                           {00}
                           controlTime
                           4
                           4
                           {00..00}
                           controlCardNumber
                           cardType
                           1
                           1
                           {00}
                           cardIssuingMemberState
                           1
                           1
                           {00}
                           cardNumber
                           16
                           16
                           {20..20}
                           controlVehicleRegistration
                           vehicleRegistrationNation
                           1
                           1
                           {00}
                           vehicleRegistrationNumber
                           14
                           14
                           {00, 20..20}
                           controlDownloadPeriodBegin
                           4
                           4
                           {00..00}
                           controlDownloadPeriodEnd
                           4
                           4
                           {00..00}
                           EF
                           Specific_Conditions
                           280
                           280
                           SpecificConditionRecord
                           56
                           5
                           5
                           entryTime
                           4
                           4
                           {00..00}
                           SpecificConditionType
                           1
                           1
                           {00}

                        TCS_151

                        The following values, used to provide sizes in the table above, are the minimum and maximum record number values the driver card data structure must use for a generation 1 application:
                        Text of image

                           Min
                           Max
                           n1
                           NoOfEventsPerType
                           6
                           12
                           n2
                           NoOfFaultsPerType
                           12
                           24
                           n3
                           NoOfCardVehicleRecords
                           84
                           200
                           n4
                           NoOfCardPlaceRecords
                           84
                           112
                           n6
                           CardActivityLengthRange
                           5 544 bytes
                           (28 days * 93 activity changes)
                           13 776 Bytes
                           (28 days * 240 activity changes)

                  4.2.2   Driver card application generation 2

                        TCS_152

                        After its personalisation, the driver card application generation 2 shall have the following permanent file structure and file access rules.

                           Note: The short EF identifier SFID is given as decimal number, e.g. the value 30 corresponds to 11110 in binary.
                        Text of image

                           Access rules
                           File
                           File ID
                           SFID
                           Read / Select
                           Update
                           DF
                           Tachograph_G2
                           SC1
                           EF
                           Application_Identification
                           ‘0501h’
                           1
                           SC1
                           NEV
                           EF
                           CardMA_Certificate
                           ‘C100h’
                           2
                           SC1
                           NEV
                           EF
                           CardSignCertificate
                           ‘C101h’
                           3
                           SC1
                           NEV
                           EF
                           CA_Certificate
                           ‘C108h’
                           4
                           SC1
                           NEV
                           EF
                           Link_Certificate
                           ‘C109h’
                           5
                           SC1
                           NEV
                           EF
                           Identification
                           ‘0520h’
                           6
                           SC1
                           NEV
                           EF
                           Card_Download
                           ‘050Eh’
                           7
                           SC1
                           SC1
                           EF
                           Driving_Licence_Info
                           ‘0521h’
                           10
                           SC1
                           NEV
                           EF
                           Events_Data
                           ‘0502h’
                           12
                           SC1
                           SM-MAC-G2
                           EF
                           Faults_Data
                           ‘0503h’
                           13
                           SC1
                           SM-MAC-G2
                           EF
                           Driver_Activity_Data
                           ‘0504h’
                           14
                           SC1
                           SM-MAC-G2
                           EF
                           Vehicles_Used
                           ‘0505h’
                           15
                           SC1
                           SM-MAC-G2
                           EF
                           Places
                           ‘0506h’
                           16
                           SC1
                           SM-MAC-G2
                           EF
                           Current_Usage
                           ‘0507h’
                           17
                           SC1
                           SM-MAC-G2
                           EF
                           Control_Activity_Data
                           ‘0508h’
                           18
                           SC1
                           SM-MAC-G2
                           EF
                           Specific_Conditions
                           ‘0522h’
                           19
                           SC1
                           SM-MAC-G2
                           EF
                           VehicleUnits_Used
                           ‘0523h’
                           20
                           SC1
                           SM-MAC-G2
                           EF
                           GNSS_Places
                           ‘0524h’
                           21
                           SC1
                           SM-MAC-G2

                        The following abbreviation for the security condition is used in this table:

                                       SC1

                                    ALW OR SM-MAC-G2

                        TCS_153

                        All EF structures shall be transparent.

                        TCS_154

                        The driver card application generation 2 shall have the following data structure:
                        Text of image

                           No of Records
                           Size (bytes)
                           Default Values
                           File / Data element
                           Min
                           Max
                           DF
                           Tachograph_G2
                           19510
                           39306
                           EF
                           Application_Identification
                           15
                           15
                           DriverCardApplicationIdentification
                           15
                           15
                           typeOfTachographCardId
                           1
                           1
                           {00}
                           cardStructureVersion
                           2
                           2
                           {00 00}
                           noOfEventsPerType
                           1
                           1
                           {00}
                           noOfFaultsPerType
                           1
                           1
                           {00}
                           activityStructureLength
                           2
                           2
                           {00 00}
                           noOfCardVehicleRecords
                           2
                           2
                           {00 00}
                           noOfCardPlaceRecords
                           2
                           2
                           {00}
                           noOfGNSSCDRecords
                           2
                           2
                           {00 00}
                           noOfSpecificConditionRecords
                           2
                           2
                           {00}
                           EF
                           CardMA_Certificate
                           204
                           341
                           CardMACertificate
                           204
                           341
                           {00..00}
                           EF
                           CardSignCertificate
                           204
                           341
                           CardSignCertificate
                           204
                           341
                           {00..00}
                           EF
                           CA_Certificate
                           204
                           341
                           MemberStateCertificate
                           204
                           341
                           {00..00}
                           EF
                           Link_Certificate
                           204
                           341
                           LinkCertificate
                           204
                           341
                           {00..00}
                           EF
                           Identification
                           143
                           143
                           CardIdentification
                           65
                           65
                           cardIssuingMemberState
                           1
                           1
                           {00}
                           cardNumber
                           16
                           16
                           {20..20}
                           cardIssuingAuthorityName
                           36
                           36
                           {20..20}
                           cardIssueDate
                           4
                           4
                           {00..00}
                           cardValidityBegin
                           4
                           4
                           {00..00}
                           cardExpiryDate
                           4
                           4
                           {00..00}
                           DriverCardHolderIdentification
                           78
                           78
                           cardHolderName
                           72
                           72
                           holderSurname
                           36
                           36
                           {00, 20..20}
                           holderFirstNames
                           36
                           36
                           {00, 20..20}
                           cardHolderBirthDate
                           4
                           4
                           {00..00}
                           cardHolderPreferredLanguage
                           2
                           2
                           {20 20}
                           EF Card_Download
                           4
                           4
                           LastCardDownload
                           4
                           4
                           EF Driving_Licence_Info
                           Driving_Licence_Info
                           53
                           53
                           CardDrivingLicenceInformation
                           53
                           53
                           drivingLicenceIssuingAuthority
                           36
                           36
                           {00, 20..20}
                           drivingLicenceIssuingNation
                           1
                           1
                           {00}
                           drivingLicenceNumber
                           16
                           16
                           {20..20}
                           EF Events_Data
                           Events_Data
                           1584
                           3168
                           CardEventData
                           1584
                           3168
                           cardEventRecords
                           11
                           144
                           288
                           CardEventRecord
                           n1
                           24
                           24
                           eventType
                           1
                           1
                           {00}
                           eventBeginTime
                           4
                           4
                           {00..00}
                           eventEndTime
                           4
                           4
                           {00..00}
                           eventVehicleRegistration
                           vehicleRegistrationNation
                           1
                           1
                           {00}
                           vehicleRegistrationNumber
                           14
                           14
                           {00, 20..20}
                           EF Faults_Data
                           Faults_Data
                           576
                           1152
                           CardFaultData
                           576
                           1152
                           cardFaultRecords
                           2
                           288
                           576
                           CardFaultRecord
                           n2
                           24
                           24

                        Text of image

                           faultType
                           1
                           1
                           {00}
                           faultBeginTime
                           4
                           4
                           {00..00}
                           faultEndTime
                           4
                           4
                           {00..00}
                           faultVehicleRegistration
                           vehicleRegistrationNation
                           1
                           1
                           {00}
                           vehicleRegistrationNumber
                           14
                           14
                           {00, 20..20}
                           EF Driver_Activity_Data
                           Driver_Activity_Data
                           5548
                           13780
                           CardDriverActivity
                           5548
                           13780
                           activityPointerOldestDayRecord
                           2
                           2
                           {00 00}
                           activityPointerNewestRecord
                           2
                           2
                           {00 00}
                           activityDailyRecords
                           n6
                           5544
                           13776
                           {00..00}
                           EF Vehicles_Used
                           Vehicles_Used
                           4034
                           9602
                           CardVehiclesUsed
                           4034
                           9602
                           vehiclePointerNewestRecord
                           2
                           2
                           {00 00}
                           cardVehicleRecords
                           4032
                           9600
                           CardVehicleRecord
                           n3
                           48
                           48
                           vehicleOdometerBegin
                           3
                           3
                           {00..00}
                           vehicleOdometerEnd
                           3
                           3
                           {00..00}
                           vehicleFirstUse
                           4
                           4
                           {00..00}
                           vehicleLastUse
                           4
                           4
                           {00..00}
                           vehicleRegistration
                           vehicleRegistrationNation
                           1
                           1
                           {00}
                           vehicleRegistrationNumber
                           14
                           14
                           {00, 20..20}
                           vuDataBlockCounter
                           2
                           2
                           {00 00}
                           vehicleIdentificationNumber
                           17
                           17
                           {20..20}
                           EF
                           Places
                           1766
                           2354
                           CardPlaceDailyWorkPeriod
                           1766
                           2354
                           placePointerNewestRecord
                           2
                           2
                           {00 00}
                           placeRecords
                           1764
                           2352
                           PlaceRecord
                           n4
                           21
                           21
                           entryTime
                           4
                           4
                           {00..00}
                           entryTypeDailyWorkPeriod
                           1
                           1
                           {00}
                           dailyWorkPeriodCountry
                           1
                           1
                           {00}
                           dailyWorkPeriodRegion
                           1
                           1
                           {00}
                           vehicleOdometerValue
                           3
                           3
                           {00..00}
                           entryGNSSPlaceRecord
                           11
                           11
                           timeStamp
                           4
                           4
                           {00..00}
                           gnssAccuracy
                           1
                           1
                           {00}
                           geoCoordinates
                           6
                           6
                           {00..00}
                           EF
                           Current_Usage
                           19
                           19
                           CardCurrentUse
                           19
                           19
                           sessionOpenTime
                           4
                           4
                           {00..00}
                           sessionOpenVehicle
                           vehicleRegistrationNation
                           1
                           1
                           {00}
                           vehicleRegistrationNumber
                           14
                           14
                           {00, 20..20}
                           EF
                           Control_Activity_Data
                           46
                           46
                           CardControlActivityDataRecord
                           46
                           46
                           controlType
                           1
                           1
                           {00}
                           controlTime
                           4
                           4
                           {00..00}
                           controlCardNumber
                           cardType
                           1
                           1
                           {00}
                           cardIssuingMemberState
                           1
                           1
                           {00}
                           cardNumber
                           16
                           16
                           {20..20}
                           controlVehicleRegistration
                           vehicleRegistrationNation
                           1
                           1
                           {00}
                           vehicleRegistrationNumber
                           14
                           14
                           {00, 20..20}
                           controlDownloadPeriodBegin
                           4
                           4
                           {00..00}
                           controlDownloadPeriodEnd
                           4
                           4
                           {00..00}

                        Text of image

                           EF
                           Specific_Conditions
                           282
                           562
                           SpecificConditions
                           282
                           562
                           conditionPointerNewestRecord
                           2
                           2
                           {00 00}
                           specificConditionRecords
                           280
                           560
                           SpecificConditionRecord
                           n9
                           5
                           5
                           entryTime
                           4
                           4
                           {00..00}
                           specificConditionType
                           1
                           1
                           {00}
                           EF
                           VehicleUnits_Used
                           842
                           2002
                           CardVehicleUnitsUsed
                           842
                           2002
                           vehicleUnitPointerNewestRecord
                           2
                           2
                           {00 00}
                           cardVehicleUnitRecords
                           840
                           2000
                           CardVehicleUnitRecord
                           n7
                           10
                           10
                           timeStamp
                           4
                           4
                           {00..00}
                           manufacturerCode
                           1
                           1
                           {00}
                           deviceID
                           1
                           1
                           {00}
                           vuSoftwareVersion
                           4
                           4
                           {00..00}
                           EF
                           GNSS_Places
                           3782
                           5042
                           GNSSContinuousDriving
                           3782
                           5042
                           gnssCDPointerNewestRecord
                           2
                           2
                           {00 00}
                           gnssContinuousDrivingRecords
                           3780
                           5040
                           {00}
                           GNSSContinuousDrivingRecord
                           n8
                           15
                           15
                           timeStamp
                           4
                           4
                           {00..00}
                           gnssPlaceRecord
                           11
                           11
                           timeStamp
                           4
                           4
                           {00..00}
                           gnssAccuracy
                           1
                           1
                           {00}
                           geoCoordinates
                           6
                           6
                           {00..00}

                        TCS_155

                        The following values, used to provide sizes in the table above, are the minimum and maximum record number values the driver card data structure must use for a generation 2 application:
                        Text of image

                           Min
                           Max
                           n1
                           NoOfEventsPerType
                           6
                           12
                           n2
                           NoOfFaultsPerType
                           12
                           24
                           n3
                           NoOfCardVehicleRecords
                           84
                           200
                           n4
                           NoOfCardPlaceRecords
                           84
                           112
                           n6
                           CardActivityLengthRange
                           5 544 bytes
                           (28 days * 93 activity changes)
                           13 776 Bytes
                           (28 days * 240 activity changes)
                           n7
                           NoOfCardVehicleUnitRecords
                           84
                           200
                           n8
                           NoOfGNSSCDRecords
                           252
                           336
                           n9
                           NoOfSpecificConditionRecords
                           56
                           112

                  4.3.   Workshop card applications

            4.3.1   Workshop card application generation 1

                        TCS_156

                        After its personalisation, the workshop card application generation 1 shall have the following permanent file structure and file access rules:
                        Text of image

                           Access rules
                           File
                           File ID
                           Read
                           Select
                           Update
                           DF Tachograph
                           ‘0500h’
                           SC1
                           EF Application_Identification
                           ‘0501h’
                           SC2
                           SC1
                           NEV
                           EF Card_Certificate
                           ‘C100h’
                           SC2
                           SC1
                           NEV
                           EF CA_Certificate
                           ‘C108h’
                           SC2
                           SC1
                           NEV
                           EF Identification
                           ‘0520h’
                           SC2
                           SC1
                           NEV
                           EF Card_Download
                           ‘0509h’
                           SC2
                           SC1
                           SC1
                           EF Calibration
                           ‘050Ah’
                           SC2
                           SC1
                           SC3
                           EF Sensor_Installation_Data
                           ‘050Bh’
                           SC4
                           SC1
                           NEV
                           EF Events_Data
                           ‘0502h’
                           SC2
                           SC1
                           SC3
                           EF Faults_Data
                           ‘0503h’
                           SC2
                           SC1
                           SC3
                           EF Driver_Activity_Data
                           ‘0504h’
                           SC2
                           SC1
                           SC3
                           EF Vehicles_Used
                           ‘0505h’
                           SC2
                           SC1
                           SC3
                           EF Places
                           ‘0506h’
                           SC2
                           SC1
                           SC3
                           EF Current_Usage
                           ‘0507h’
                           SC2
                           SC1
                           SC3
                           EF Control_Activity_Data
                           ‘0508h’
                           SC2
                           SC1
                           SC3
                           EF Specific_Conditions
                           ‘0522h’
                           SC2
                           SC1
                           SC3

                        The following abbreviations for the security conditions are used in this table:

                                       SC1

                                    ALW OR SM-MAC-G2

                                       SC2

                                    ALW OR SM-MAC-G1 OR SM-MAC-G2

                                       SC3

                                    SM-MAC-G1 OR SM-MAC-G2

                                       SC4

                                    For the READ BINARYcommand with even INS byte:

                                                (PLAIN-C AND SM-R-ENC-G1) OR (SM-C-MAC-G1 AND SM-R-ENC-MAC-G1) OR

                                                (SM-C-MAC-G2 AND SM-R-ENC-MAC-G2)

                                                For the READ BINARY command with odd INS byte (if supported): NEV

                        TCS_157

                        All EF structures shall be transparent.

                        TCS_158

                        The workshop card application generation 1 shall have the following data structure:
                        Text of image

                           No of Records
                           Size (Bytes)
                           Default Values
                           File / Data element
                           Min
                           Max
                           DF Tachograph
                           11055
                           29028
                           EF Application_Identification
                           11
                           11
                           WorkshopCardApplicationIdentification
                           11
                           11
                           typeOfTachographCardId
                           1
                           1
                           {00}
                           cardStructureVersion
                           2
                           2
                           {00 00}
                           noOfEventsPerType
                           1
                           1
                           {00}
                           noOfFaultsPerType
                           1
                           1
                           {00}
                           activityStructureLength
                           2
                           2
                           {00 00}
                           noOfCardVehicleRecords
                           2
                           2
                           {00 00}
                           noOfCardPlaceRecords
                           1
                           1
                           {00}
                           noOfCalibrationRecords
                           1
                           1
                           {00}
                           EF Card_Certificate
                           194
                           194
                           CardCertificate
                           194
                           194
                           {00..00}
                           EF CA_Certificate
                           194
                           194
                           MemberStateCertificate
                           194
                           194
                           {00..00}
                           EF Identification
                           211
                           211
                           CardIdentification
                           65
                           65
                           cardIssuingMemberState
                           1
                           1
                           {00}
                           cardNumber
                           16
                           16
                           {20..20}
                           cardIssuingAuthorityName
                           36
                           36
                           {00, 20..20}
                           cardIssueDate
                           4
                           4
                           {00..00}
                           cardValidityBegin
                           4
                           4
                           {00..00}
                           cardExpiryDate
                           4
                           4
                           {00..00}
                           WorkshopCardHolderIdentification
                           146
                           146
                           workshopName
                           36
                           36
                           {00, 20..20}
                           workshopAddress
                           36
                           36
                           {00, 20..20}
                           cardHolderName
                           holderSurname
                           36
                           36
                           {00, 20..20}
                           holderFirstNames
                           36
                           36
                           {00, 20..20}
                           cardHolderPreferredLanguage
                           2
                           2
                           {20 20}
                           EF Card_Download
                           2
                           2
                           NoOfCalibrationsSinceDownload
                           2
                           2
                           {00 00}
                           EF Calibration
                           9243
                           26778
                           WorkshopCardCalibrationData
                           9243
                           26778
                           calibrationTotalNumber
                           2
                           2
                           {00 00}
                           calibrationPointerNewestRecord
                           1
                           1
                           {00}
                           calibrationRecords
                           9240
                           26775
                           WorkshopCardCalibrationRecord
                           n5
                           105
                           105
                           calibrationPurpose
                           1
                           1
                           {00}
                           vehicleIdentificationNumber
                           17
                           17
                           {20..20}
                           vehicleRegistration
                           vehicleRegistrationNation
                           1
                           1
                           {00}
                           vehicleRegistrationNumber
                           14
                           14
                           {00, 20..20}
                           wVehicleCharacteristicConstant
                           2
                           2
                           {00 00}
                           kConstantOfRecordingEquipment
                           2
                           2
                           {00 00}
                           lTyreCircumference
                           2
                           2
                           {00 00}
                           tyreSize
                           15
                           15
                           {20..20}
                           authorisedSpeed
                           1
                           1
                           {00}
                           oldOdometerValue
                           3
                           3
                           {00..00}
                           newOdometerValue
                           3
                           3
                           {00..00}
                           oldTimeValue
                           4
                           4
                           {00..00}
                           newTimeValue
                           4
                           4
                           {00..00}
                           nextCalibrationDate
                           4
                           4
                           {00..00}
                           vuPartNumber
                           16
                           16
                           {20..20}
                           vuSerialNumber
                           8
                           8
                           {00..00}
                           sensorSerialNumber
                           8
                           8
                           {00..00}

                        Text of image

                           EF Sensor_Installation_Data
                           16
                           16
                           SensorInstallationSecData
                           16
                           16
                           {00..00}
                           EF Events_Data
                           432
                           432
                           CardEventData
                           432
                           432
                           cardEventRecords
                           6
                           72
                           72
                           CardEventRecord
                           n1
                           24
                           24
                           eventType
                           1
                           1
                           {00}
                           eventBeginTime
                           4
                           4
                           {00..00}
                           eventEndTime
                           4
                           4
                           {00..00}
                           eventVehicleRegistration
                           vehicleRegistrationNation
                           1
                           1
                           {00}
                           vehicleRegistrationNumber
                           14
                           14
                           {00, 20..20}
                           EF Faults_Data
                           288
                           288
                           CardFaultData
                           288
                           288
                           cardFaultRecords
                           2
                           144
                           144
                           CardFaultRecord
                           n2
                           24
                           24
                           faultType
                           1
                           1
                           {00}
                           faultBeginTime
                           4
                           4
                           {00..00}
                           faultEndTime
                           4
                           4
                           {00..00}
                           faultVehicleRegistration
                           vehicleRegistrationNation
                           1
                           1
                           {00}
                           vehicleRegistrationNumber
                           14
                           14
                           {00, 20..20}
                           EF Driver_Activity_Data
                           202
                           496
                           CardDriverActivity
                           202
                           496
                           activityPointerOldestDayRecord
                           2
                           2
                           {00 00}
                           activityPointerNewestRecord
                           2
                           2
                           {00 00}
                           activityDailyRecords
                           n6
                           198
                           492
                           {00..00}
                           EF Vehicles_Used
                           126
                           250
                           CardVehiclesUsed
                           126
                           250
                           vehiclePointerNewestRecord
                           2
                           2
                           {00 00}
                           cardVehicleRecords
                           124
                           248
                           CardVehicleRecord
                           n3
                           31
                           31
                           vehicleOdometerBegin
                           3
                           3
                           {00..00}
                           vehicleOdometerEnd
                           3
                           3
                           {00..00}
                           vehicleFirstUse
                           4
                           4
                           {00..00}
                           vehicleLastUse
                           4
                           4
                           {00..00}
                           vehicleRegistration
                           vehicleRegistrationNation
                           1
                           1
                           {00}
                           vehicleRegistrationNumber
                           14
                           14
                           {00, 20..20}
                           vuDataBlockCounter
                           2
                           2
                           {00 00}
                           EF Places
                           61
                           81
                           CardPlaceDailyWorkPeriod
                           61
                           81
                           placePointerNewestRecord
                           1
                           1
                           {00}
                           placeRecords
                           60
                           80
                           PlaceRecord
                           n4
                           10
                           10
                           entryTime
                           4
                           4
                           {00..00}
                           entryTypeDailyWorkPeriod
                           1
                           1
                           {00}
                           dailyWorkPeriodCountry
                           1
                           1
                           {00}
                           dailyWorkPeriodRegion
                           1
                           1
                           {00}
                           vehicleOdometerValue
                           3
                           3
                           {00..00}
                           EF Current_Usage
                           19
                           19
                           CardCurrentUse
                           19
                           19
                           sessionOpenTime
                           4
                           4
                           {00..00}
                           sessionOpenVehicle
                           vehicleRegistrationNation
                           1
                           1
                           {00}
                           vehicleRegistrationNumber
                           14
                           14
                           {00, 20..20}

                        Text of image

                           EF Control_Activity_Data
                           46
                           46
                           CardControlActivityDataRecord
                           46
                           46
                           controlType
                           1
                           1
                           {00}
                           controlTime
                           4
                           4
                           {00..00}
                           controlCardNumber
                           cardType
                           1
                           1
                           {00}
                           cardIssuingMemberState
                           1
                           1
                           {00}
                           cardNumber
                           16
                           16
                           {20..20}
                           controlVehicleRegistration
                           vehicleRegistrationNation
                           1
                           1
                           {00}
                           vehicleRegistrationNumber
                           14
                           14
                           {00, 20..20}
                           controlDownloadPeriodBegin
                           4
                           4
                           {00..00}
                           controlDownloadPeriodEnd
                           4
                           4
                           {00..00}
                           EF Specific_Conditions
                           10
                           10
                           SpecificConditionRecord
                           2
                           5
                           5
                           entryTime
                           4
                           4
                           {00..00}
                           SpecificConditionType
                           1
                           1
                           {00}

                        TCS_159

                        The following values, used to provide sizes in the table above, are the minimum and maximum record number values the workshop card data structure must use for a generation 1 application:
                        Text of image

                           Min
                           Max
                           n1
                           NoOfEventsPerType
                           3
                           3
                           n2
                           NoOfFaultsPerType
                           6
                           6
                           n3
                           NoOfCardVehicleRecords
                           4
                           8
                           n4
                           NoOfCardPlaceRecords
                           6
                           8
                           n5
                           NoOfCalibrationRecords
                           88
                           255
                           n6
                           CardActivityLengthRange
                           198 bytes (1 day *
                           93 activity changes)
                           492 bytes (1 day *
                           240 activity changes)

                  4.3.2   Workshop card application generation 2

                        TCS_160

                        After its personalisation, the workshop card application generation 2 shall have the following permanent file structure and file access rules.

                           Note: The short EF identifier SFID is given as decimal number, e.g. the value 30 corresponds to 11110 in binary.
                        Text of image

                           Access rules
                           File
                           File ID
                           SFID
                           Read
                           Select
                           Update
                           DF Tachograph_G2
                           SC1
                           SC1
                           EF Application_Identification
                           ‘0501h’
                           1
                           SC1
                           SC1
                           NEV
                           EF CardMA_Certificate
                           ‘C100h’
                           2
                           SC1
                           SC1
                           NEV
                           EF CardSignCertificate
                           ‘C101h’
                           3
                           SC1
                           SC1
                           NEV
                           EF CA_Certificate
                           ‘C108h’
                           4
                           SC1
                           SC1
                           NEV
                           EF Link_Certificate
                           ‘C109h’
                           5
                           SC1
                           SC1
                           NEV
                           EF Identification
                           ‘0520h’
                           6
                           SC1
                           SC1
                           NEV
                           EF Card_Download
                           ‘0509h’
                           7
                           SC1
                           SC1
                           SC1
                           EF Calibration
                           ‘050Ah’
                           10
                           SC1
                           SC1
                           SM-MAC-G2
                           EF Sensor_Installation_Data
                           ‘050Bh’
                           11
                           SC5
                           SM-MAC-G2
                           NEV
                           EF Events_Data
                           ‘0502h’
                           12
                           SC1
                           SC1
                           SM-MAC-G2
                           EF Faults_Data
                           ‘0503h’
                           13
                           SC1
                           SC1
                           SM-MAC-G2
                           EF Driver_Activity_Data
                           ‘0504h’
                           14
                           SC1
                           SC1
                           SM-MAC-G2
                           EF Vehicles_Used
                           ‘0505h’
                           15
                           SC1
                           SC1
                           SM-MAC-G2
                           EF Places
                           ‘0506h’
                           16
                           SC1
                           SC1
                           SM-MAC-G2
                           EF Current_Usage
                           ‘0507h’
                           17
                           SC1
                           SC1
                           SM-MAC-G2
                           EF Control_Activity_Data
                           ‘0508h’
                           18
                           SC1
                           SC1
                           SM-MAC-G2
                           EF Specific_Conditions
                           ‘0522h’
                           19
                           SC1
                           SC1
                           SM-MAC-G2
                           EF VehicleUnits_Used
                           ‘0523h’
                           20
                           SC1
                           SC1
                           SM-MAC-G2
                           EF GNSS_Places
                           ‘0524h’
                           21
                           SC1
                           SC1
                           SM-MAC-G2

                        The following abbreviations for the security conditions are used in this table:

                                       SC1

                                    ALW OR SM-MAC-G2

                                       SC5

                                    For the Read Binary command with even INS byte: SM-C-MAC-G2 AND SM-R-ENC-MAC-G2
                                    For the Read Binary command with odd INS byte (if supported): NEV

                        TCS_161

                        All EFs structures shall be transparent.

                        TCS_162

                        The workshop card application generation 2 shall have the following data structure:
                        Text of image

                           No of Records
                           Size (Bytes)
                           Default Values
                           File / Data element
                           Min
                           Max
                           DF Tachograph_G2
                           17837
                           47163
                           EF Application_Identification
                           17
                           17
                           WorkshopCardApplicationIdentification
                           17
                           17
                           typeOfTachographCardId
                           1
                           1
                           {00}
                           cardStructureVersion
                           2
                           2
                           {00 00}
                           noOfEventsPerType
                           1
                           1
                           {00}
                           noOfFaultsPerType
                           1
                           1
                           {00}
                           activityStructureLength
                           2
                           2
                           {00 00}
                           noOfCardVehicleRecords
                           2
                           2
                           {00 00}
                           noOfCardPlaceRecords
                           2
                           2
                           {00}
                           noOfCalibrationRecords
                           2
                           2
                           {00}
                           noOfGNSSCDRecords
                           2
                           2
                           {00..00}
                           noOfSpecificConditionRecords
                           2
                           2
                           {00..00}
                           EF CardMA_Certificate
                           204
                           341
                           CardMACertificate
                           204
                           341
                           {00..00}
                           EF CardSignCertificate
                           204
                           341
                           CardSignCertificate
                           204
                           341
                           {00..00}
                           EF CA_Certificate
                           204
                           341
                           MemberStateCertificate
                           204
                           341
                           {00..00}
                           EF Link_Certificate
                           204
                           341
                           LinkCertificate
                           204
                           341
                           {00..00}
                           EF Identification
                           211
                           211
                           CardIdentification
                           65
                           65
                           cardIssuingMemberState
                           1
                           1
                           {00}
                           cardNumber
                           16
                           16
                           {20..20}
                           cardIssuingAuthorityName
                           36
                           36
                           {00, 20..20}
                           cardIssueDate
                           4
                           4
                           {00..00}
                           cardValidityBegin
                           4
                           4
                           {00..00}
                           cardExpiryDate
                           4
                           4
                           {00..00}
                           WorkshopCardHolderIdentification
                           146
                           146
                           workshopName
                           36
                           36
                           {00, 20..20}
                           workshopAddress
                           36
                           36
                           {00, 20..20}
                           cardHolderName
                           holderSurname
                           36
                           36
                           {00, 20..20}
                           holderFirstNames
                           36
                           36
                           {00, 20..20}
                           cardHolderPreferredLanguage
                           2
                           2
                           {20 20}
                           EF Card_Download
                           2
                           2
                           NoOfCalibrationsSinceDownload
                           2
                           2
                           {00 00}
                           EF Calibration
                           14788
                           42844
                           WorkshopCardCalibrationData
                           14788
                           42844
                           calibrationTotalNumber
                           2
                           2
                           {00 00}
                           calibrationPointerNewestRecord
                           2
                           2
                           {00}
                           calibrationRecords
                           14784
                           42840
                           WorkshopCardCalibrationRecord
                           n5
                           168
                           168
                           calibrationPurpose
                           1
                           1
                           {00}
                           vehicleIdentificationNumber
                           17
                           17
                           {20..20}
                           vehicleRegistration
                           vehicleRegistrationNation
                           1
                           1
                           {00}
                           vehicleRegistrationNumber
                           14
                           14
                           {00, 20..20}
                           wVehicleCharacteristicConstant
                           2
                           2
                           {00 00}
                           kConstantOfRecordingEquipment
                           2
                           2
                           {00 00}
                           lTyreCircumference
                           2
                           2
                           {00 00}
                           tyreSize
                           15
                           15
                           {20..20}
                           authorisedSpeed
                           1
                           1
                           {00}
                           oldOdometerValue
                           3
                           3
                           {00..00}
                           newOdometerValue
                           3
                           3
                           {00..00}

                        Text of image

                           oldTimeValue
                           4
                           4
                           {00..00}
                           newTimeValue
                           4
                           4
                           {00..00}
                           nextCalibrationDate
                           4
                           4
                           {00..00}
                           vuPartNumber
                           16
                           16
                           {20..20}
                           vuSerialNumber
                           8
                           8
                           {00..00}
                           sensorSerialNumber
                           8
                           8
                           {00..00}
                           sensorGNSSSerialNumber
                           8
                           8
                           {00..00}
                           rcmSerialNumber
                           8
                           8
                           {00..00}
                           vuAbility
                           1
                           1
                           {00}
                           sealDataCard
                           46
                           46
                           noOfSealRecords
                           1
                           1
                           {00}
                           SealRecords
                           45
                           45
                           SealRecord
                           5
                           9
                           9
                           equipmentType
                           1
                           1
                           {00}
                           extendedSealIdentifier
                           8
                           8
                           {00..00}
                           EF Sensor_Installation_Data
                           18
                           102
                           SensorInstallationSecData
                           18
                           102
                           {00..00}
                           EF Events_Data
                           792
                           792
                           CardEventData
                           792
                           792
                           cardEventRecords
                           11
                           72
                           72
                           CardEventRecord
                           n1
                           24
                           24
                           eventType
                           1
                           1
                           {00}
                           eventBeginTime
                           4
                           4
                           {00..00}
                           eventEndTime
                           4
                           4
                           {00..00}
                           eventVehicleRegistration
                           vehicleRegistrationNation
                           1
                           1
                           {00}
                           vehicleRegistrationNumber
                           14
                           14
                           {00, 20..20}
                           EF Faults_Data
                           288
                           288
                           CardFaultData
                           288
                           288
                           cardFaultRecords
                           2
                           144
                           144
                           CardFaultRecord
                           n2
                           24
                           24
                           faultType
                           1
                           1
                           {00}
                           faultBeginTime
                           4
                           4
                           {00..00}
                           faultEndTime
                           4
                           4
                           {00..00}
                           faultVehicleRegistration
                           vehicleRegistrationNation
                           1
                           1
                           {00}
                           vehicleRegistrationNumber
                           14
                           14
                           {00, 20..20}
                           EF Driver_Activity_Data
                           202
                           496
                           CardDriverActivity
                           202
                           496
                           activityPointerOldestDayRecord
                           2
                           2
                           {00 00}
                           activityPointerNewestRecord
                           2
                           2
                           {00 00}
                           activityDailyRecords
                           n6
                           198
                           492
                           {00..00}
                           EF Vehicles_Used
                           194
                           386
                           CardVehiclesUsed
                           194
                           386
                           vehiclePointerNewestRecord
                           2
                           2
                           {00 00}
                           cardVehicleRecords
                           192
                           384
                           CardVehicleRecord
                           n3
                           48
                           48
                           vehicleOdometerBegin
                           3
                           3
                           {00..00}
                           vehicleOdometerEnd
                           3
                           3
                           {00..00}
                           vehicleFirstUse
                           4
                           4
                           {00..00}
                           vehicleLastUse
                           4
                           4
                           {00..00}
                           vehicleRegistration
                           vehicleRegistrationNation
                           1
                           1
                           {00}
                           vehicleRegistrationNumber
                           14
                           14
                           {00, 20..20}
                           vuDataBlockCounter
                           2
                           2
                           {00 00}
                           vehicleIdentificationNumber
                           17
                           17
                           {20..20}
                           EF Places
                           128
                           170

                        Text of image

                           CardPlaceDailyWorkPeriod
                           128
                           170
                           placePointerNewestRecord
                           2
                           2
                           {00 00}
                           placeRecords
                           126
                           168
                           PlaceRecord
                           n4
                           21
                           21
                           entryTime
                           4
                           4
                           {00..00}
                           entryTypeDailyWorkPeriod
                           1
                           1
                           {00}
                           dailyWorkPeriodCountry
                           1
                           1
                           {00}
                           dailyWorkPeriodRegion
                           1
                           1
                           {00}
                           vehicleOdometerValue
                           3
                           3
                           {00..00}
                           entryGNSSPlaceRecord
                           11
                           11
                           {00..00}
                           timeStamp
                           4
                           4
                           {00..00}
                           gnssAccuracy
                           1
                           1
                           {00}
                           geoCoordinates
                           6
                           6
                           {00..00}
                           EF Current_Usage
                           19
                           19
                           CardCurrentUse
                           19
                           19
                           sessionOpenTime
                           4
                           4
                           {00..00}
                           sessionOpenVehicle
                           vehicleRegistrationNation
                           1
                           1
                           {00}
                           vehicleRegistrationNumber
                           14
                           14
                           {00, 20..20}
                           EF Control_Activity_Data
                           46
                           46
                           CardControlActivityDataRecord
                           46
                           46
                           controlType
                           1
                           1
                           {00}
                           controlTime
                           4
                           4
                           {00..00}
                           controlCardNumber
                           cardType
                           1
                           1
                           {00}
                           cardIssuingMemberState
                           1
                           1
                           {00}
                           cardNumber
                           16
                           16
                           {20..20}
                           controlVehicleRegistration
                           vehicleRegistrationNation
                           1
                           1
                           {00}
                           vehicleRegistrationNumber
                           14
                           14
                           {00, 20..20}
                           controlDownloadPeriodBegin
                           4
                           4
                           {00..00}
                           controlDownloadPeriodEnd
                           4
                           4
                           {00..00}
                           EF VehicleUnits_Used
                           42
                           42
                           CardVehicleUnitsUsed
                           42
                           82
                           vehicleUnitPointerNewestRecord
                           2
                           2
                           {00 00}
                           cardVehicleUnitRecords
                           40
                           80
                           CardVehicleUnitRecord
                           n7
                           10
                           10
                           timeStamp
                           4
                           4
                           {00..00}
                           manufacturerCode
                           1
                           1
                           {00..00}
                           deviceID
                           1
                           1
                           {00..00}
                           vuSoftwareVersion
                           4
                           4
                           {00..00}
                           EF GNSS_Places
                           262
                           362
                           GNSSContinuousDriving
                           262
                           362
                           gnssCDPointerNewestRecord
                           2
                           2
                           {00 00}
                           gnssContinuousDrivingRecords
                           260
                           360
                           GNSSContinuousDrivingRecord
                           n8
                           15
                           15
                           timeStamp
                           4
                           4
                           {00..00}
                           gnssPlaceRecord
                           11
                           11
                           timeStamp
                           4
                           4
                           {00..00}
                           gnssAccuracy
                           1
                           1
                           {00}
                           geoCoordinates
                           6
                           6
                           {00..00}
                           EF Specific_Conditions
                           12
                           22
                           SpecificConditions
                           12
                           22
                           conditionPointerNewestRecord
                           2
                           2
                           {00 00}
                           specificConditionRecords
                           10
                           20
                           SpecificConditionRecord
                           n9
                           5
                           5
                           entryTime
                           4
                           4
                           {00..00}
                           specificConditionType
                           1
                           1
                           {00}

                        TCS_163

                        The following values, used to provide sizes in the table above, are the minimum and maximum record number values the workshop card data structure must use for a generation 2 application:
                        Text of image

                           Min
                           Max
                           n1
                           NoOfEventsPerType
                           3
                           3
                           n2
                           NoOfFaultsPerType
                           6
                           6
                           n3
                           NoOfCardVehicleRecords
                           4
                           8
                           n4
                           NoOfCardPlaceRecords
                           6
                           8
                           n5
                           NoOfCalibrationRecords
                           88
                           255
                           n6
                           CardActivityLengthRange
                           198 bytes (1 day *
                           93 activity changes)
                           492 bytes (1 day *
                           240 activity changes)
                           n7
                           NoOfCardVehicleUnitRecords
                           4
                           8
                           n8
                           NoOfGNSSCDRecords
                           18
                           24
                           n9
                           NoOfSpecificConditionRecords
                           2
                           4

                  4.4.   Control card applications

            4.4.1   Control Card application generation 1

                        TCS_164

                        After its personalisation, the control card application generation 1 shall have the following permanent file structure and file access rules:
                        Text of image

                           Access rules
                           File
                           File ID
                           Read
                           Select
                           Update
                           DF Tachograph
                           ‘0500h’
                           EF Application_Identification
                           ‘0501h’
                           SC2
                           SC1
                           NEV
                           EF Card_Certificate
                           ‘C100h’
                           SC2
                           SC1
                           NEV
                           EF CA_Certificate
                           ‘C108h’
                           SC2
                           SC1
                           NEV
                           EF Identification
                           ‘0520h’
                           SC6
                           SC1
                           NEV
                           EF Controller_Activity_Data
                           ‘050Ch’
                           SC2
                           SC1
                           SC3

                        The following abbreviations for the security conditions are used in this table:

                                       SC1

                                    ALW OR SM-MAC-G2

                                       SC2

                                    ALW OR SM-MAC-G1 OR SM-MAC-G2

                                       SC3

                                    SM-MAC-G1 OR SM-MAC-G2

                                       SC6

                                    EXT-AUT-G1 OR SM-MAC-G1 OR SM-MAC-G2

                        TCS_165

                        All EF structures shall be transparent.

                        TCS_166

                        The control card application generation 1 shall have the following data structure:
                        Text of image

                           No of Records
                           Size (Bytes)
                           File / Data element
                           Min
                           Max
                           DF Tachograph
                           11186
                           24526
                           EF Application_Identification
                           5
                           5
                           ControlCardApplicationIdentification
                           5
                           5
                           typeOfTachographCardId
                           1
                           1
                           {00}
                           cardStructureVersion
                           2
                           2
                           {00 00}
                           noOfControlActivityRecords
                           2
                           2
                           {00 00}
                           EF Card_Certificate
                           194
                           194
                           CardCertificate
                           194
                           194
                           {00..00}
                           EF CA_Certificate
                           194
                           194
                           MemberStateCertificate
                           194
                           194
                           {00..00}
                           EF Identification
                           211
                           211
                           CardIdentification
                           65
                           65
                           cardIssuingMemberState
                           1
                           1
                           {00}
                           cardNumber
                           16
                           16
                           {20..20}
                           cardIssuingAuthorityName
                           36
                           36
                           {00, 20..20}
                           cardIssueDate
                           4
                           4
                           {00..00}
                           cardValidityBegin
                           4
                           4
                           {00..00}
                           cardExpiryDate
                           4
                           4
                           {00..00}
                           ControlCardHolderIdentification
                           146
                           146
                           controlBodyName
                           36
                           36
                           {00, 20..20}
                           controlBodyAddress
                           36
                           36
                           {00, 20..20}
                           cardHolderName
                           holderSurname
                           36
                           36
                           {00, 20..20}
                           holderFirstNames
                           36
                           36
                           {00, 20..20}
                           cardHolderPreferredLanguage
                           2
                           2
                           {20 20}
                           EF Controller_Activity_Data
                           10582
                           23922
                           ControlCardControlActivityData
                           10582
                           23922
                           controlPointerNewestRecord
                           2
                           2
                           {00 00}
                           controlActivityRecords
                           10580
                           23920
                           controlActivityRecord
                           n7
                           46
                           46
                           controlType
                           1
                           1
                           {00}
                           controlTime
                           4
                           4
                           {00..00}
                           controlledCardNumber
                           cardType
                           1
                           1
                           {00}
                           cardIssuingMemberState
                           1
                           1
                           {00}
                           cardNumber
                           16
                           16
                           {20..20}
                           controlledVehicleRegistration
                           vehicleRegistrationNation
                           1
                           1
                           {00}
                           vehicleRegistrationNumber
                           14
                           14
                           {00, 20..20}
                           controlDownloadPeriodBegin
                           4
                           4
                           {00..00}
                           controlDownloadPeriodEnd
                           4
                           4
                           {00..00}

                        TCS_167

                        The following values, used to provide sizes in the table above, are the minimum and maximum record number values the control card data structure must use for a generation 1 application:
                        Text of image

                           Min
                           Max
                           n7
                           NoOfControlActivityRecords
                           230
                           520

                  4.4.2   Control card application generation 2

                        TCS_168

                        After its personalisation, the control card application generation 2 shall have the following permanent file structure and file access rules.

                           Note: The short EF identifier SFID is given as decimal number, e.g. the value 30 corresponds to 11110 in binary.
                        Text of image

                           Access rules
                           File
                           File ID
                           SFID
                           Read / Select
                           Update
                           DF Tachograph_G2
                           SC1
                           EF Application_Identification
                           ‘0501h’
                           1
                           SC1
                           NEV
                           EF CardMA_Certificate
                           ‘C100h’
                           2
                           SC1
                           NEV
                           EF CA_Certificate
                           ‘C108h’
                           4
                           SC1
                           NEV
                           EF Link_Certificate
                           ‘C109h’
                           5
                           SC1
                           NEV
                           EF Identification
                           ‘0520h’
                           6
                           SC1
                           NEV
                           EF Controller_Activity_Data
                           ‘050Ch’
                           14
                           SC1
                           SM-MAC-G2

                        The following abbreviation for the security condition is used in this table:

                                       SC1

                                    ALW OR SM-MAC-G2

                        TCS_169

                        All EF structures shall be transparent.

                        TCS_170

                        The control card application generation2 shall have the following data structure:
                        Text of image

                           No of Records
                           Size (Bytes)
                           File / Data element
                           Min
                           Max
                           DF Tachograph_G2
                           11410
                           25161
                           EF Application_Identification
                           5
                           5
                           ControlCardApplicationIdentification
                           5
                           5
                           typeOfTachographCardId
                           1
                           1
                           {00}
                           cardStructureVersion
                           2
                           2
                           {00 00}
                           noOfControlActivityRecords
                           2
                           2
                           {00 00}
                           EF CardMA_Certificate
                           204
                           341
                           CardMACertificate
                           204
                           341
                           {00..00}
                           EF CA_Certificate
                           204
                           341
                           MemberStateCertificate
                           204
                           341
                           {00..00}
                           EF Link_Certificate
                           204
                           341
                           LinkCertificate
                           204
                           341
                           {00..00}
                           EF Identification
                           211
                           211
                           CardIdentification
                           65
                           65
                           cardIssuingMemberState
                           1
                           1
                           {00}
                           cardNumber
                           16
                           16
                           {20..20}
                           cardIssuingAuthorityName
                           36
                           36
                           {00, 20..20}
                           cardIssueDate
                           4
                           4
                           {00..00}
                           cardValidityBegin
                           4
                           4
                           {00..00}
                           cardExpiryDate
                           4
                           4
                           {00..00}
                           ControlCardHolderIdentification
                           146
                           146
                           controlBodyName
                           36
                           36
                           {00, 20..20}
                           controlBodyAddress
                           36
                           36
                           {00, 20..20}
                           cardHolderName
                           holderSurname
                           36
                           36
                           {00, 20..20}
                           holderFirstNames
                           36
                           36
                           {00, 20..20}
                           cardHolderPreferredLanguage
                           2
                           2
                           {20 20}
                           EF Controller_Activity_Data
                           10582
                           23922
                           ControlCardControlActivityData
                           10582
                           23922
                           controlPointerNewestRecord
                           2
                           2
                           {00 00}
                           controlActivityRecords
                           10580
                           23920
                           controlActivityRecord
                           n7
                           46
                           46
                           controlType
                           1
                           1
                           {00}
                           controlTime
                           4
                           4
                           {00..00}
                           controlledCardNumber
                           cardType
                           1
                           1
                           {00}
                           cardIssuingMemberState
                           1
                           1
                           {00}
                           cardNumber
                           16
                           16
                           {20..20}
                           controlledVehicleRegistration
                           vehicleRegistrationNation
                           1
                           1
                           {00}
                           vehicleRegistrationNumber
                           14
                           14
                           {00, 20..20}
                           controlDownloadPeriodBegin
                           4
                           4
                           {00..00}
                           controlDownloadPeriodEnd
                           4
                           4
                           {00..00}

                        TCS_171

                        The following values, used to provide sizes in the table above, are the minimum and maximum record number values the control card data structure must use for a generation 2 application:
                        Text of image

                           Min
                           Max
                           n7
                           NoOfControlActivityRecords
                           230
                           520

                  4.5.   Company card applications

            4.5.1   Company card application generation 1

                        TCS_172

                        After its personalisation, the company card application generation 1 shall have the following permanent file structure and file access rules:
                        Text of image

                           Access rules
                           File
                           File ID
                           Read
                           Select
                           Update
                           DF Tachograph
                           ‘0500h’
                           SC1
                           EF Application_Identification
                           ‘0501h’
                           SC2
                           SC1
                           NEV
                           EF Card_Certificate
                           ‘C100h’
                           SC2
                           SC1
                           NEV
                           EF CA_Certificate
                           ‘C108h’
                           SC2
                           SC1
                           NEV
                           EF Identification
                           ‘0520h’
                           SC6
                           SC1
                           NEV
                           EF Company_Activity_Data
                           ‘050Dh’
                           SC2
                           SC1
                           SC3

                        The following abbreviations for the security conditions are used in this table:

                                       SC1

                                    ALW OR SM-MAC-G2

                                       SC2

                                    ALW OR SM-MAC-G1 OR SM-MAC-G2

                                       SC3

                                    SM-MAC-G1 OR SM-MAC-G2

                                       SC6

                                    EXT-AUT-G1 OR SM-MAC-G1 OR SM-MAC-G2

                        TCS_173

                        All EF structures shall be transparent.

                        TCS_174

                        The company card application generation 1 shall have the following data structure:
                        Text of image

                           File / Data element
                           No of Records
                           Size (bytes)
                           Default Values
                           Min
                           Max
                           DF Tachograph
                           11114
                           24454
                           EF Application_Identification
                           5
                           5
                           CompanyCardApplicationIdentification
                           5
                           5
                           typeOfTachographCardId
                           1
                           1
                           {00}
                           cardStructureVersion
                           2
                           2
                           {00 00}
                           noOfCompanyActivityRecords
                           2
                           2
                           {00 00}
                           EF Card_Certificate
                           194
                           194
                           CardCertificate
                           194
                           194
                           {00..00}
                           EF CA_Certificate
                           194
                           194
                           MemberStateCertificate
                           194
                           194
                           {00..00}
                           EF Identification
                           139
                           139
                           CardIdentification
                           65
                           65
                           cardIssuingMemberState
                           1
                           1
                           {00}
                           cardNumber
                           16
                           16
                           {20..20}
                           cardIssuingAuthorityName
                           36
                           36
                           {00, 20..20}
                           cardIssueDate
                           4
                           4
                           {00..00}
                           cardValidityBegin
                           4
                           4
                           {00..00}
                           cardExpiryDate
                           4
                           4
                           {00..00}
                           CompanyCardHolderIdentification
                           74
                           74
                           companyName
                           36
                           36
                           {00, 20..20}
                           companyAddress
                           36
                           36
                           {00, 20..20}
                           cardHolderPreferredLanguage
                           2
                           2
                           {20 20}
                           EF Company_Activity_Data
                           10582
                           23922
                           CompanyActivityData
                           10582
                           23922
                           companyPointerNewestRecord
                           2
                           2
                           {00 00}
                           companyActivityRecords
                           10580
                           23920
                           companyActivityRecord
                           n8
                           46
                           46
                           companyActivityType
                           1
                           1
                           {00}
                           companyActivityTime
                           4
                           4
                           {00..00}
                           cardNumberInformation
                           cardType
                           1
                           1
                           {00}
                           cardIssuingMemberState
                           1
                           1
                           {00}
                           cardNumber
                           16
                           16
                           {20..20}
                           vehicleRegistrationInformation
                           vehicleRegistrationNation
                           1
                           1
                           {00}
                           vehicleRegistrationNumber
                           14
                           14
                           {00, 20..20}
                           downloadPeriodBegin
                           4
                           4
                           {00..00}
                           downloadPeriodEnd
                           4
                           4
                           {00..00}

                        TCS_175

                        The following values, used to provide sizes in the table above, are the minimum and maximum record number values the company card data structure must use for a generation 1 application:
                        Text of image

                           Min
                           Max
                           n8
                           NoOfCompanyActivityRecords
                           230
                           520

                  4.5.2   Company card application generation 2

                        TCS_176

                        After its personalisation, the company card application generation 2 shall have the following permanent file structure and file access rules.

                           Note: The short EF identifier SFID is given as decimal number, e.g. the value 30 corresponds to 11110 in binary.
                        Text of image

                           Access rules
                           File
                           File ID
                           SFID
                           Read / Select
                           Update
                           DF Tachograph_G2
                           SC1
                           EF Application_Identification
                           ‘0501h’
                           1
                           SC1
                           NEV
                           EF CardMA_Certificate
                           ‘C100h’
                           2
                           SC1
                           NEV
                           EF CA_Certificate
                           ‘C108h’
                           4
                           SC1
                           NEV
                           EF Link_Certificate
                           ‘C109h’
                           5
                           SC1
                           NEV
                           EF Identification
                           ‘0520h’
                           6
                           SC1
                           NEV
                           EF Company_Activity_Data
                           ‘050Dh’
                           14
                           SC1
                           SM-MAC-G2

                        The following abbreviation for the security condition is used in this table:

                                       SC1

                                    ALW OR SM-MAC-G2

                        TCS_177

                        All EF structures shall be transparent.

                        TCS_178

                        The company card application generation 2 shall have the following data structure:
                        Text of image

                           File / Data element
                           No of Records
                           Size (bytes)
                           Default Values
                           Min
                           Max
                           DF Tachograph_G2
                           11338
                           25089
                           EF Application_Identification
                           5
                           5
                           CompanyCardApplicationIdentification
                           5
                           5
                           typeOfTachographCardId
                           1
                           1
                           {00}
                           cardStructureVersion
                           2
                           2
                           {00 00}
                           noOfCompanyActivityRecords
                           2
                           2
                           {00 00}
                           EF CardMA_Certificate
                           204
                           341
                           CardMACertificate
                           204
                           341
                           {00..00}
                           EF CA_Certificate
                           204
                           341
                           MemberStateCertificate
                           204
                           341
                           {00..00}
                           EF Link_Certificate
                           204
                           341
                           LinkCertificate
                           204
                           341
                           {00..00}
                           EF Identification
                           139
                           139
                           CardIdentification
                           65
                           65
                           cardIssuingMemberState
                           1
                           1
                           {00}
                           cardNumber
                           16
                           16
                           {20..20}
                           cardIssuingAuthorityName
                           36
                           36
                           {00, 20..20}
                           cardIssueDate
                           4
                           4
                           {00..00}
                           cardValidityBegin
                           4
                           4
                           {00..00}
                           cardExpiryDate
                           4
                           4
                           {00..00}
                           CompanyCardHolderIdentification
                           74
                           74
                           companyName
                           36
                           36
                           {00, 20..20}
                           companyAddress
                           36
                           36
                           {00, 20..20}
                           cardHolderPreferredLanguage
                           2
                           2
                           {20 20}
                           EF Company_Activity_Data
                           10582
                           23922
                           CompanyActivityData
                           10582
                           23922
                           companyPointerNewestRecord
                           2
                           2
                           {00 00}
                           companyActivityRecords
                           10580
                           23920
                           companyActivityRecord
                           n8
                           46
                           46
                           companyActivityType
                           1
                           1
                           {00}
                           companyActivityTime
                           4
                           4
                           {00..00}
                           cardNumberInformation
                           cardType
                           1
                           1
                           {00}
                           cardIssuingMemberState
                           1
                           1
                           {00}
                           cardNumber
                           16
                           16
                           {20..20}
                           vehicleRegistrationInformation
                           vehicleRegistrationNation
                           1
                           1
                           {00}
                           vehicleRegistrationNumber
                           14
                           14
                           {00, 20..20}
                           downloadPeriodBegin
                           4
                           4
                           {00..00}
                           downloadPeriodEnd
                           4
                           4
                           {00..00}

                        TCS_179

                        The following values, used to provide sizes in the table above, are the minimum and maximum record number values the company card data structure must use for a generation 2 application:
                        Text of image

                           Min
                           Max
                           n8
                           NoOfCompanyActivityRecords
                           230
                           520

            Appendix 3

               PICTOGRAMS

                        PIC_001

                        The tachograph may optionally use the following pictograms and pictogram combinations (or pictograms and combination similar enough to be unambiguously identifiable with these):

                                    1.

                                    BASIC PICTOGRAMS

                                                   People

                                                   Actions

                                                   Modes of operation

                                                Company

                                                Company mode

                                                Controller

                                                Control

                                                Control mode

                                                Driver

                                                Driving

                                                Operational mode

                                                Workshop/test station

                                                Inspection/calibration

                                                Calibration mode

                                                Manufacturer

                                                   Activities

                                                   Duration

                                                Available

                                                Current availability period

                                                Driving

                                                Continuous driving time

                                                Rest

                                                Current rest period

                                                Other Work

                                                Current work period

                                                Break

                                                Cumulative break time

                                                Unknown

                                                   Equipment

                                                   Functions

                                                Driver slot

                                                Co-driver slot

                                                Card

                                                Clock

                                                Display

                                                Displaying

                                                External storage

                                                Downloading

                                                Power supply

                                                Printer/printout

                                                Printing

                                                Sensor

                                                Tyre size

                                                Vehicle/vehicle unit

                                                GNSS facility

                                                Remote Detection facility

                                                ITS interface

                                                   Specific conditions

                                                Out of scope

                                                Ferry/train crossing

                                                   Miscellaneous

                                                Events

                                                Faults

                                                Start of daily work period

                                                End of daily work period

                                                Location

                                                Manual entry of driver activities

                                                Security

                                                Speed

                                                Time

                                                Total/summary

                                                   Qualifiers

                                                24h

                                                Daily

                                                Weekly

                                                Two weeks

                                                From or to

                                    2.

                                    PICTOGRAM COMBINATIONS

                                                   Miscellaneous

                                                Control place

                                                Location start of daily work period

                                                Location end of daily work period

                                                From time

                                                To time

                                                From vehicle

                                                Out of scope begin

                                                Out of scope end

                                                   Cards

                                                Driver card

                                                Company card

                                                Control card

                                                Workshop card

                                                No card

                                                   Driving

                                                Crew driving

                                                Driving time for one week

                                                Driving time for two weeks

                                                   Printouts

                                                Driver activities from card daily printout

                                                Driver activities from VU daily printout

                                                Events and faults from card printout

                                                Events and faults from VU printout

                                                Technical data printout

                                                Over speeding printout

                                                   Events

                                                Insertion of a non valid card

                                                Card conflict

                                                Time overlap

                                                Driving without an appropriate card

                                                Card insertion while driving

                                                Last card session not correctly closed

                                                Over speeding

                                                Power supply interruption

                                                Motion data error

                                                Vehicle motion conflict

                                                Security breach

                                                Time adjustment (by workshop)

                                                Over speeding control

                                                   Faults

                                                Card fault (driver slot)

                                                Card fault (co-driver slot)

                                                Display fault

                                                Downloading fault

                                                Printer fault

                                                Sensor fault

                                                VU internal fault

                                                GNSS fault

                                                Remote Detection fault

                                                   Manual entries procedure

                                                Still same daily work period ?

                                                End of previous work period ?

                                                Confirm or enter location of end of work period

                                                Enter start time

                                                Enter location of start of work period.

                           Note: Additional pictogram combinations to form printout blocks or record identifiers are defined in Appendix 4.

            Appendix 4

               PRINTOUTS

            TABLE OF CONTENT

                        1.

                     GENERALITIES
                     243

                        2.

                     DATA BLOCKS SPECIFICATION
                     243

                        3.

                     PRINTOUT SPECIFICATIONS
                     250

                        3.1.

                     Driver Activities from Card Daily Printout
                     250

                        3.2.

                     Driver Activities from VU Daily Printout
                     251

                        3.3.

                     Events and Faults from Card Printout
                     252

                        3.4.

                     Events and Faults from VU Printout
                     252

                        3.5.

                     Technical data Printout
                     253

                        3.6.

                     Over speeding Printout
                     253

                        3.7

                     History of inserted cards
                     254
                  1.   GENERALITIES
            Each printout is built up by chaining various data blocks, possibly identified with a block identifier.
            A data block contains one or more records, possibly identified with a record identifier.

                        PRT_001

                        When a block identifier immediately precedes a record identifier, the record identifier is not printed.

                        PRT_002

                        In the case where a data item is unknown, or must not be printed for data access rights reasons, spaces are printed instead.

                        PRT_003

                        If the content of a complete line is unknown, or need not to be printed, then the complete line is omitted.

                        PRT_004

                        Numerical data fields are printed right aligned, with a space separator for thousands and millions, and without leading zeros.

                        PRT_005

                        String data fields are printed left aligned and filled up with spaces to data item length, or truncated to data item length when needed (names and addresses).

                        PRT_006

                        In case of a line-break due to a long text a special character (dot at middle line-height, ‘ߦ’) should be printed as first character in the new line.

                  2.   DATA BLOCKS SPECIFICATION
            In this chapter the following format notation conventions have been used:

                        —

                        Characters printed in bold denote plain text to be printed (printing remains in normal characters),

                        —

                        Normal characters denote variables (pictograms or data) to be replaced by their values for printing,

                        —

                        Variable names have been padded with underscores to show the data item length available for the variable,

                        —

                        Dates are specified with a ‘dd/mm/yyyy’ (day, month, year) format. A ‘dd.mm.yyyy’ format may also be used,

                        —

                        The term ‘card identification’ denotes the composition of: the type of card through a card pictograms combination, the card issuing Member State code, a forward slash character and the card number with the replacement index and the renewal index separated with a space:

                                    P

                                    x

                                    x

                                    x

                                    /

                                    x

                                    x

                                    x

                                    x

                                    x

                                    x

                                    x

                                    x

                                    x

                                    x

                                    x

                                    x

                                    x

                                    x

                                    x

                                    x

                                    Card Pictogram combination

                                    Issuing Member State code

                                    First 14 characters of card number
                                    (possibly including a consecutive index)

                                    Replacement index

                                    Renewal index

                        PRT_007

                        Printouts shall use the following data blocks and/or data records, in accordance with the following meanings and formats:
                        Text of image

                           Block or record number
                           Meaning
                           Data Format
                           1
                           Date and time at which the document is printed.
                           dd/mm/yyyy hh:mm (UTC)
                           2
                           Type of printout.
                           Block identifier
                           -----------------------
                           Printout pictogram combination (see App. 3), Speed limiting device setting (Over speeding printout only)
                           Picto xxx km/h
                           3
                           Card holder identification.
                           Block identifier. P= people pictogram
                           -----------P------------
                           Card holder surname
                           P Last_Name
                           Card holder first name(s) (if any)
                           First_Name
                           Card identification
                           Card_Identification
                           Card expiry date (if any) and Card generation number (GEN 1 or GEN 2) (*)
                           dd/mm/yyyy - GEN 2
                           In the case where the card is a non-personal card, and holds no card holder surname, the company or workshop or control body name shall be printed instead.
                           (*) The card generation number can only be printed by smart tachograph.
                           4
                           Vehicle identification.
                           Block identifier
                           -----------------------
                           VIN
                           VIN
                           Registering Member State and VRN
                           Nat/VRN
                           5
                           VU identification.
                           Block identifier
                           -----------------------
                           VU manufacturer’s name
                           VU_Manufacturer
                           VU part number
                           VU generation number (*)
                           VU_Part_Number
                           GEN 2
                           (*) The card generation number can only be printed by smart tachograph.
                           6
                           Last calibration of the tachograph
                           Block identifier
                           -----------------------
                           Workshop name
                           Last_Name
                           Workshop card identification
                           Card_Identification
                           Date of the calibration
                           dd/mm/yyyy

                        Text of image

                           7
                           Last control (by a control officer)
                           Block identifier
                           -----------------------
                           Controller’s card identification
                           Card_Identification
                           Control date, time and type
                           dd/mm/yyyy hh:mm ppppp
                           Type of the control: Up to five pictograms. The type of control can be (a combination) of:
                           : Card downloading, : VU downloading, : printing, : Displaying, : Roadside calibration checking
                           8
                           Driver activities stored on a card in order of occurrence
                           Block identifier
                           -----------------------
                           Enquiry date (calendar day subject of the printout) + Daily card presence counter
                           dd/mm/yyyy xxx
                           8a
                           Out of scope condition in the beginning of this day (leave blank if no out of scope condition open)
                           ----------OUT-----------
                           8.1
                           Period during which the card was not inserted
                           8.1a
                           Record identifier (start of period)
                           --------------------
                           8.1b
                           Unknown period. Start time, duration
                           hh:mm hhhmm
                           8.1c
                           Activity manually entered.
                           Activity pictogram, start time, duration
                           A hh:mm hhhmm
                           8.2
                           Card insertion in slot S
                           Record identifier; S = Slot pictogram
                           ---------S---------
                           Vehicle registering Member State and VRN
                           Nat/VRN
                           Vehicle odometer at card insertion
                           x xxx xxx km
                           8.3
                           Activity (while card was inserted)
                           Activity pictogram, start time, duration, crew status (crew pictogram if CREW, blanks if SINGLE).
                           A hh:mm hhhmm
                           8.3a
                           Specific condition. Time of entry, specific condition pictogram (or pictogram combination).
                           hh:mm ---pppp---
                           8.4
                           Card withdrawal
                           Vehicle odometer and distance travelled since last insertion for which odometer is known
                           x xxx xxx km; x xxx km
                           9
                           Driver activities stored in a VU per slot in chronological order
                           Block identifier
                           -----------------------
                           Enquiry date (calendar day subject of the printout)
                           dd/mm/yyyy
                           Vehicle odometer at 00:00 and 24:00
                           x xxx xxx - x xxx xxx km
                           10
                           Activities carried in slot S
                           Block identifier
                           -----------S------------
                           10a
                           Out of scope condition in the beginning of this day (leave blank if no out of scope condition open)
                           ----------OUT-----------
                           10.1
                           Period where no card is inserted in slot S
                           Record identifier.
                           --------------------
                           No Card inserted
                           ---
                           Vehicle odometer at beginning of period
                           x xxx xxx km
                           10.2
                           Card insertion
                           Card insertion Record identifier
                           --------------------
                           Driver’s name
                           Last_Name

                        Text of image

                           Driver’s first name
                           First_Name
                           Driver’s Card identification
                           Card_Identification
                           Card expiry date (if any) and Card generation number (GEN 1 or GEN 2) (*)
                           dd/mm/yyyy - GEN 2
                           Registering MS and VRN of previous vehicle used
                           Nat/VRN
                           Date and time of card withdrawal from previous vehicle
                           dd/mm/yyyy hh:mm
                           Blank line
                           Vehicle odometer at card insertion, Manual entry of driver activities flag (M if yes, Blank if No).
                           If no card insertion of a driver card happened on the day for which the printout is done then for block 10.2 the odometer data reading from the last available card insertion before that day shall be used.
                           x xxx xxx km M
                           10.3
                           Activity
                           Activity pictogram, start time, duration, crew Status (crew pictogram if CREW, blanks if SINGLE).
                           A hh:mm hhhmm
                           10.3a
                           Specific condition. Time of entry, specific condition pictogram (or pictogram combination).
                           hh:mm ---pppp---
                           10.4
                           Card withdrawal or End of ‘No Card’ period
                           Vehicle odometer at card withdrawal or at end of ‘no card’ period and distance travelled since insertion, or since beginning of the ‘No Card’ period.
                           x xxx xxx km; x xxx km
                           (*) The card generation number can only be printed by smart tachograph.
                           11
                           Daily summary
                           Block identifier
                           -----------------------
                           11.1
                           VU summary of periods without card in driver slot
                           Block identifier
                           1---
                           11.2
                           VU summary of periods without card in co-driver slot
                           Block identifier
                           2---
                           11.3
                           VU daily summary per driver
                           Record identifier
                           --------------------
                           Driver’s surname
                           Last_Name
                           Driver’s first name(s)
                           First_Name
                           Driver’s card identification
                           Card_Identification
                           11.4
                           Entry of place where a daily work period begins and/or ends
                           pi=location begin / end pictogram, time, country, region,
                           pihh:mm Cou Reg
                           Odometer
                           x xxx xxx km
                           11.5
                           Entry of place where a daily work period begins and/or ends
                           and after 3 hours continuous driving time
                           hh:mm
                           Odometer
                           x xxx xxx km
                           11.6
                           Activity totals (from a card)
                           Total driving duration, distance travelled
                           hhhmm x xxx km
                           Total working and availability duration
                           hhhmm hhhmm
                           Total resting and unknown duration
                           hhhmm hhhmm
                           Total duration of crew activities
                           hhhmm
                           11.7
                           Activity totals (periods without card driver slot)
                           Total driving duration, distance travelled
                           hhhmm x xxx km
                           Total working and availability duration
                           hhhmm hhhmm
                           Total resting duration
                           hhhmm

                        Text of image

                           11.8
                           Activity totals (periods without card co-driver slot)
                           Total working and availability duration
                           hhhmm hhhmm
                           Total resting duration
                           hhhmm
                           11.9
                           Activity totals (per driver both slots included)
                           Total driving duration, distance travelled
                           hhhmm x xxx km
                           Total working and availability duration
                           hhhmm hhhmm
                           Total resting duration
                           hhhmm
                           Total duration of crew activities
                           hhhmm
                           When a daily printout is required for the current day, daily summary information is computed with available data at the time of the printout.
                           12
                           Events and/or faults stored on a card
                           12.1
                           Block identifier last 5 ‘Events and Faults’ from a card
                           ---------------------
                           12.2
                           Block identifier all recorded ‘Events’ on a card
                           ----------------------
                           12.3
                           Block identifier all recorded ‘Faults’ on a card
                           ----------------------
                           12.4
                           Event and/or Fault record
                           Record identifier
                           --------------------
                           Event/fault pictogram, record purpose, date time of start,
                           Pic (p) dd/mm/yyyy hh:mm
                           Additional event/fault code (if any), duration
                           xx hhhmm
                           Registering Member State & VRN of vehicle in which the event or fault occurred
                           Nat/VRN
                           13
                           Events and/or faults stored or on-going in a VU
                           13.1
                           Block identifier last 5 ‘Events and Faults’ from VU
                           ---------------------
                           13.2
                           Block identifier all recorded or on-going ‘Events’ in a VU
                           ----------------------
                           13.3
                           Block identifier all recorded or on-going ‘Faults’ in a VU
                           ----------------------
                           13.4
                           Event and/or fault record
                           Record identifier
                           --------------------
                           Event/fault pictogram, record purpose, date time of start,
                           Pic (p) dd/mm/yyyy hh:mm
                           Additional event/fault code (if any), No of similar events this day, duration
                           xx (xxx) hhhmm
                           Identification of the cards inserted at start or end of the event or fault (up to 4 lines without repeating twice the same card numbers)
                           Card_Identification
                           Card_Identification
                           Card_Identification
                           Card_Identification
                           Case where no card was inserted
                           Manufacturer specific data
                           ---
                           < Literal><ErrorCode>
                           The record purpose (p) is a numerical code explaining why the event or fault was recorded, coded in accordance with the data element EventFaultRecordPurpose.
                           The Literal is a tachograph manufacturer specific literal with 12 characters maximum.
                           The ErrorCode is a tachograph manufacturer specific error code with 12 characters maximum.

                        Text of image

                           14
                           VU Identification
                           Block identifier
                           -----------------------
                           VU manufacturer name
                           Name
                           VU manufacturer address
                           Address
                           VU part number
                           PartNumber
                           VU approval number
                           Apprv
                           VU serial number
                           S/N
                           VU year of manufacture
                           yyyy
                           VU software version and installation date
                           V xxxx dd/mm/yyyy
                           15
                           Sensor identification
                           Block identifier
                           -----------------------
                           15.1
                           Pairing record
                           Sensor serial number
                           S/N
                           Sensor approval number
                           Apprv
                           Sensor pairing date
                           dd/mm/yyyy hh:mm
                           16
                           GNSS identification
                           Block identifier
                           ----------------------
                           16.1 Coupling record
                           External GNSS facility serial number
                           S/N
                           External GNSS facility approval number
                           Apprv
                           External GNSS facility coupling date
                           dd/mm/yyyy hh:mm
                           17
                           Calibration data
                           Block identifier
                           -----------------------
                           17.1
                           Calibration record
                           Record identifier
                           --------------------
                           Workshop having performed the calibration
                           Workshop_name
                           Workshop address
                           Workshop_address
                           Workshop card identification
                           Card_Identification
                           Workshop card expiry date
                           dd/mm/yyyy
                           Blank line
                           Calibration date + calibration purpose
                           dd/mm/yyyy (p)
                           VIN
                           VIN
                           Registering Member State & VRN
                           Nat/VRN
                           Characteristic coefficient of vehicle
                           w xx xxx Imp/km
                           Constant of the recording equipment
                           k xx xxx Imp/km
                           Effective circumference of wheel tyres
                           l xx xxx mm
                           Size of tyres mounted
                           TyreSize
                           Speed limiting device setting
                           xxx km/h
                           Old and new odometer values
                           x xxx xxx – x xxx xxx km
                           The calibration purpose (p) is a numerical code explaining why these calibration parameters were recorded, coded in accordance with the data element CalibrationPurpose.

                        Text of image

                           18
                           Time adjustment
                           Block identifier
                           -----------------------
                           18.1
                           Time adjustment record
                           Record identifier
                           --------------------
                           Old date and time
                           dd/mm/yyyy hh:mm
                           New date and time
                           dd/mm/yyyy hh:mm
                           Workshop having performed the time adjustment
                           Workshop_name
                           Workshop address
                           Workshop_address
                           Workshop card identification
                           Card_Identification
                           Workshop card expiry date
                           dd/mm/yyyy
                           19
                           Most recent event and Fault recorded in the VU
                           Block identifier
                           ---------------------
                           Most recent event date time
                           dd/mm/yyyy hh:mm
                           Most recent fault date time
                           dd/mm/yyyy hh:mm
                           20
                           Over speeding control information
                           Block identifier
                           ----------------------
                           Date and time of last OVER SPEEDING CONTROL
                           dd/mm/yyyy hh:mm
                           Date/time of first over speeding and number of over speeding events since
                           dd/mm/yyyy hh:mm (nnn)
                           21
                           Over speeding record
                           21.1
                           Block identifier ‘First over speeding after the last calibration’
                           -----------------
                           21.2
                           Block identifier ‘The 5 most serious over the last 365 days’
                           -------(365)------
                           21.3
                           Block identifier ‘The most serious for each of the last 10 days of occurrence’
                           -------(10)-------
                           21.4
                           Record identifier
                           --------------------
                           Date time and duration
                           dd/mm/yyyy hh:mm hhhmm
                           Max and average speeds, No. of similar events this day
                           xxx km/h xxx km/h(xxx)
                           Driver’s surname
                           Last_Name
                           Driver’s first name(s)
                           First_Name
                           Driver card identification
                           Card_Identification
                           21.5
                           If no over speeding record exists in a block
                           ---
                           22
                           Hand-written information
                           Block identifier
                           ------------------------
                           22.1
                           Control Place
                           ..................
                           22.2
                           Controller’s signature
                           ..................
                           22.3
                           From time
                           ..................
                           22.4
                           To time
                           ..................
                           22.5
                           Driver’s signature
                           ..................
                           ‘Hand-written information’; Insert enough blank lines above a hand-written item, to be able to actually write the required information or to put a signature.

                        Text of image

                           23
                           Most recent cards inserted in VU
                           Block identifier
                           -------- --------
                           23.1
                           Inserted Card
                           Record identifier
                           ----
                           Type of card, Generation, Version, Manufacturer (*)
                           <gen> <version> <MC>
                           Card Identification
                           Card Serial Number
                           Date and time of last card insertion
                           Card Identification
                           Card Serial Number
                           dd/mm/yyyy hh:mm
                           (*) (everything in one line)
                           with
                           type of card: Pictogram, one character + space
                           gen: GEN1 or GEN2, 4 characters + space
                           version: up to 10 characters
                           MC: manufacturer code, 3 characters

                  3.   PRINTOUT SPECIFICATIONS
            In this chapter the following notation conventions have been used:

                        N

                        Print block or record number N

                        N

                        Print block or record number N repeated as many times as necessary

                        X/Y

                        Print blocks or records X and/or Y as needed, and repeating as many times as necessary.

                  3.1.   Driver Activities from Card Daily Printout

                        PRT_008

                        The driver activities from card daily printout shall be in accordance with the following format:

                                    1

                                    Date and time at which the document is printed

                                    2

                                    Type of printout

                                    3

                                    Controller identification (if a control card is inserted in the VU)

                                    3

                                    Driver identification (from card subject of the printout + GEN)

                                    4

                                    Vehicle identification (vehicle from which printout is taken)

                                    5

                                    VU identification (VU from which printout is taken + GEN)

                                    6

                                    Last calibration of this VU

                                    7

                                    Last control the inspected driver has been subject to

                                    8

                                    Driver activities delimiter

                                    8a

                                    Out of scope condition in the beginning of this day

                                    8.1a/8.1b/8.1c/8.2/8.3/8.3a/8.4

                                    Activities of the driver in order of occurrence

                                    11

                                    Daily summary delimiter

                                    11.4

                                    Places entered in chronological order

                                    11.5

                                    GNSS data

                                    11.6

                                    Activity totals

                                    12.1

                                    Events or faults from card delimiter

                                    12.4

                                    Event/Fault records (Last 5 events or faults stored in the card)

                                    13.1

                                    Events or faults from VU delimiter

                                    13.4

                                    Event/Fault records (Last 5 events or faults stored or on-going in the VU)

                                    22.1

                                    Control place

                                    22.2

                                    Controller's signature

                                    22.5

                                    Driver's signature

                  3.2.   Driver Activities from VU Daily Printout

                        PRT_009

                        The driver activities from VU daily printout shall be in accordance with the following format:

                                    1

                                    Date and time at which the document is printed

                                    2

                                    Type of printout

                                    3

                                    Card holder identification (for all cards inserted in VU + GEN)

                                    4

                                    Vehicle identification (vehicle from which printout is taken)

                                    5

                                    VU identification (VU from which printout is taken + GEN)

                                    6

                                    Last calibration of this VU

                                    7

                                    Last control on this tachograph

                                    9

                                    Driver activities delimiter

                                    10

                                    Driver slot delimiter (slot 1)

                                    10a

                                    Out of scope condition in the beginning of this day

                                    10.1/10.2/10.3/10.3a/10.4

                                    Activities in chronological order (driver slot)

                                    10

                                    Co-driver slot delimiter (slot 2)

                                    10a

                                    Out of scope condition in the beginning of this day

                                    10.1/10.2/10.3/10.3a/10.4

                                    Activities in chronological order (co-driver slot)

                                    11

                                    Daily summary delimiter

                                    11.1

                                    Summary of periods without card in driver slot

                                    11.4

                                    Places entered in chronological order

                                    11.5

                                    GNSS data

                                    11.6

                                    Activity totals

                                    11.2

                                    Summary of periods without card in co-driver slot

                                    11.4

                                    Places entered in chronological order

                                    11.5

                                    GNSS data

                                    11.7

                                    Activity totals

                                    11.3

                                    Summary of activities for a driver both slots included

                                    11.4

                                    Places entered by this driver in chronological order

                                    11.5

                                    GNSS data

                                    11.8

                                    Activity totals for this driver

                                    13.1

                                    Events faults delimiter

                                    12.4

                                    Event/Fault records (Last 5 events or faults stored or on-going in the VU)

                                    13.1

                                    Control place

                                    22.2

                                    Controller's signature

                                    22.3

                                    From time

                                    (space available for a driver without a card to indicate which periods are relevant to himself)

                                    22.4

                                    To time

                                    22.5

                                    Driver's signature

                  3.3.   Events and Faults from Card Printout

                        PRT_010

                        The events and faults from card printout shall be in accordance with the following format:

                                    1

                                    Date and time at which the document is printed

                                    2

                                    Type of printout

                                    3

                                    Controller identification (if a control card is inserted in the VU + GEN)

                                    3

                                    Driver identification (from card subject of the printout)

                                    4

                                    Vehicle identification (vehicle from which printout is taken)

                                    12.2

                                    Events delimiter

                                    12.4

                                    Event records (all events stored on the card)

                                    12.3

                                    Faults delimiter

                                    12.4

                                    Fault records (all faults stored on the card)

                                    22.1

                                    Control place

                                    22.2

                                    Controller's signature

                                    22.5

                                    Driver's signature

                  3.4.   Events and Faults from VU Printout

                        PRT_011

                        The events and faults from VU printout shall be in accordance with the following format:

                                    1

                                    Date and time at which the document is printed

                                    2

                                    Type of printout

                                    3

                                    Card holder identification (for all cards inserted in VU + GEN)

                                    4

                                    Vehicle identification (vehicle from which printout is taken)

                                    13.2

                                    Events delimiter

                                    13.4

                                    Event records (All Events stored or on-going in the VU)

                                    13.3

                                    Faults delimiter

                                    13.4

                                    Fault records (All Faults stored or on-going in the VU)

                                    22.1

                                    Control place

                                    22.2

                                    Controller's signature

                                    22.5

                                    Driver's signature

                  3.5.   Technical data Printout

                        PRT_012

                        The technical data printout shall be in accordance with the following format:

                                    1

                                    Date and time at which the document is printed

                                    2

                                    Type of printout

                                    3

                                    Card holder identification (for all cards inserted in VU + GEN)

                                    4

                                    Vehicle identification (vehicle from which printout is taken)

                                    14

                                    VU identification

                                    15

                                    Sensor identification

                                    15.1

                                    Sensor Pairing data (all data available in chronological order)

                                    16

                                    GNSS identification

                                    16.1

                                    External GNSS facility coupling data (all data available in chronological order)

                                    17

                                    Calibration data delimiter

                                    17.1

                                    Calibration records (all records available in chronological order)

                                    18

                                    Time adjustment delimiter

                                    18.1

                                    Time adjustment records (all records available from time adjustment and from calibration data records)

                                    19

                                    Most recent event and Fault recorded in the VU

                  3.6.   Over speeding Printout

                        PRT_013

                        The over speeding printout shall be in accordance with the following format:

                                    1

                                    Date and time at which the document is printed

                                    2

                                    Type of printout

                                    3

                                    Card holder identification (for all cards inserted in VU + GEN)

                                    4

                                    Vehicle identification (vehicle from which printout is taken)

                                    20

                                    Over speeding control information

                                    21.1

                                    Over speeding data identifier

                                    21.4/21.5

                                    First over speeding after the last calibration

                                    21.2

                                    Over speeding data identifier

                                    21.4/21.5

                                    The 5 most serious over speeding events over the last 365 days

                                    21.3

                                    Over speeding data identifier

                                    21.4/21.5

                                    The most serious over speeding for each of the last 10 days of occurrence

                                    22.1

                                    Control place

                                    22.2

                                    Controller's signature

                                    22.5

                                    Driver's signature

                  3.7.   Historic of inserted cards

                        PRT_014

                        The historic of inserted cards printout shall be in accordance with the following format:

                                    1

                                    Date and time at which the document is printed

                                    2

                                    Type of printout

                                    3

                                    Card holder identifications (of all cards inserted in the V)

                                    23

                                    Most recent card inserted in the VU

                                    23.1

                                    Inserted cards (up to 88 records)

                                    12.3

                                    Faults delimiter

            Appendix 5

               DISPLAY

            In this appendix the following format notation conventions have been used:

                        —

                        characters printed in bold denote plain text to be displayed (display remains in normal character),

                        —

                        normal characters denote variables (pictograms or data) to be replaced by their values for displaying:

                                    —

                                    :

                                    dd mm yyyy

                                    :

                                    day, month, year,

                                    —

                                    :

                                    hh

                                    :

                                    hours,

                                    —

                                    :

                                    mm

                                    :

                                    minutes,

                                    —

                                    :

                                    D

                                    :

                                    duration pictogram,

                                    —

                                    :

                                    EF

                                    :

                                    event or fault pictograms combination,

                                    —

                                    :

                                    O

                                    :

                                    mode of operation pictogram.

                        DIS_001

                        The tachograph shall display data using the following formats:

                                    Data

                                    Format

                                       Default display

                                    Local time

                                    Mode of operation

                                    Information related to the driver

                                    Information related to the co-driver

                                    Out of scope condition opened

                                       Warning display

                                    Exceeding continuous driving time

                                    Event or fault

                                       Other displays

                                    UTC date

                                    time

                                    Driver's continuous driving time and cumulative break time

                                    Co-driver's continuous driving time and cumulative break time

                                    Driver's cumulated driving time for the previous and the current week

                                    Co-driver's cumulated driving time for the previous and the current week

            Appendix 6

               FRONT CONNECTOR FOR CALIBRATION AND DOWNLOAD

            TABLE OF CONTENT

                        1.

                     HARDWARE
                     256

                        1.1.

                     Connector
                     256

                        1.2.

                     Contact allocation
                     257

                        1.3.

                     Block diagram
                     258

                        2.

                     DOWNLOADING INTERFACE
                     258

                        3.

                     CALIBRATION INTERFACE
                     259
                  1.   HARDWARE
            1.1.   Connector

                        INT_001

                        The downloading/calibration connector shall be a 6 pin connector, accessible on the front panel without the need to disconnect any part of the tachograph, and shall comply with the following drawing (all dimensions in millimetres):

                        The following diagram shows a typical 6 pin mating plug:

                  1.2.   Contact allocation

                        INT_002

                        Contacts shall be allocated in accordance with the following table:

                                    Pin

                                    Description

                                    Remark

                                    1

                                    Battery minus

                                    Connected to the battery minus of the vehicle

                                    2

                                    Data communication

                                    K-line (ISO 14230-1)

                                    3

                                    RxD — Downloading

                                    Data input to tachograph

                                    4

                                    Input/output signal

                                    Calibration

                                    5

                                    Permanent power output

                                    The voltage range is specified to be that of the vehicle power minus 3V to allow for the voltage drop across the protective circuitry
                                    Output 40 mA

                                    6

                                    TxD — Downloading

                                    Data output from tachograph

                  1.3.   Block diagram

                        INT_003

                        The block diagram shall comply with the following:

                  2.   DOWNLOADING INTERFACE

                        INT_004

                        The downloading interface shall comply to RS232 specifications.

                        INT_005

                        The downloading interface shall use one start bit, 8 data bits LSB first, one even parity bit and 1 stop bit.

               Data byte organisation

                        Start bit

                        :

                        one bit with logic level 0;

                        Data bits

                        :

                        transmitted with LSB first;

                        Parity bit

                        :

                        even parity

                        Stop bit

                        :

                        one bit with logic level 1

                  When numerical data composed by more than one byte are transmitted, the most significant byte is transmitted first and the least significant byte last.

                        INT_006

                        Transmission baud rates shall be adjustable from 9 600 bps to 115 200 bps. Transmission shall be achieved at the highest possible transmission speed, the initial baud rate after a start of communication being set at 9 600 bps.

                  3.   CALIBRATION INTERFACE

                        INT_007

                        The data communication shall comply to ISO 14230-1 Road vehicles — Diagnostic systems — Keyword protocol 2000 — Part 1: Physical layer, First edition: 1999.

                        INT_008

                        The input/output signal shall comply with the following electrical specification:

                                    Parameter

                                    Minimum

                                    Typical

                                    Maximum

                                    Remark

                                    U low (in)

                                    1,0 V

                                    I = 750 μA

                                    U high (in)

                                    4 V

                                    I = 200 μA

                                    Frequency

                                    4 kHz

                                    U low (out)

                                    1,0 V

                                    I = 1 mA

                                    U high (out)

                                    4 V

                                    I = 1 mA

                        INT_009

                        The input/output signal shall comply with the following timing diagrams:

            Appendix 7

               DATA DOWNLOADING PROTOCOLS

            TABLE OF CONTENT

                        1.

                     INTRODUCTION
                     261

                        1.1.

                     Scope
                     261

                        1.2.

                     Acronyms and notations
                     261

                        2.

                     V.U. DATA DOWNLOADING
                     262

                        2.1.

                     Download procedure
                     262

                        2.2.

                     Data download protocol
                     262

                        2.2.1

                     Message structure
                     262

                        2.2.2

                     Message types
                     264

                        2.2.2.1

                     Start Communication Request (SID 81)
                     266

                        2.2.2.2

                     Positive Response Start Communication (SID C1)
                     266

                        2.2.2.3

                     Start Diagnostic Session Request (SID 10)
                     266

                        2.2.2.4

                     Positive Response Start Diagnostic (SID 50)
                     266

                        2.2.2.5

                     Link Control Service (SID 87)
                     266

                        2.2.2.6

                     Link Control Positive Response (SID C7)
                     266

                        2.2.2.7

                     Request Upload (SID 35)
                     266

                        2.2.2.8

                     Positive Response Request Upload (SID 75)
                     266

                        2.2.2.9

                     Transfer Data Request (SID 36)
                     266

                        2.2.2.10

                     Positive Response Transfer Data (SID 76)
                     267

                        2.2.2.11

                     Request Transfer Exit (SID 37)
                     267

                        2.2.2.12

                     Positive Response Request Transfer Exit (SID 77)
                     267

                        2.2.2.13

                     Stop Communication Request (SID 82)
                     267

                        2.2.2.14

                     Positive Response Stop Communication (SID C2)
                     267

                        2.2.2.15

                     Acknowledge Sub Message (SID 83)
                     267

                        2.2.2.16

                     Negative Response (SID 7F)
                     268

                        2.2.3

                     Message flow
                     268

                        2.2.4

                     Timing
                     269

                        2.2.5

                     Error handling
                     270

                        2.2.5.1

                     Start Communication phase
                     270

                        2.2.5.2

                     Communication phase
                     270

                        2.2.6

                     Response Message content
                     272

                        2.2.6.1

                     Positive Response Transfer Data Overview
                     273

                        2.2.6.2

                     Positive Response Transfer Data Activities
                     274

                        2.2.6.3

                     Positive Response Transfer Data Events and Faults
                     275

                        2.2.6.4

                     Positive Response Transfer Data Detailed Speed
                     276

                        2.2.6.5

                     Positive Response Transfer Data Technical Data
                     276

                        2.3.

                     ESM File storage
                     277

                        3.

                     TACHOGRAPH CARDS DOWNLOADING PROTOCOL
                     277

                        3.1.

                     Scope
                     277

                        3.2.

                     Definitions
                     277

                        3.3.

                     Card Downloading
                     277

                        3.3.1

                     Initialisation sequence
                     278

                        3.3.2

                     Sequence for un-signed data files
                     278

                        3.3.3

                     Sequence for Signed data files
                     279

                        3.3.4

                     Sequence for resetting the calibration counter.
                     279

                        3.4.

                     Data storage format
                     280

                        3.4.1

                     Introduction
                     280

                        3.4.2

                     File format
                     280

                        4.

                     DOWNLOADING A TACHOGRAPH CARD VIA A VEHICLE UNIT.
                     281
                  1.   INTRODUCTION
            This appendix specifies the procedures to follow in order to perform the different types of data download to an External Storage Medium, together with the protocols that must be implemented to assure the correct data transfer and the full compatibility of the downloaded data format to allow any controller to inspect these data and be able to control their authenticity and their integrity before analysing them.
            1.1.   Scope

            Data may be downloaded to an ESM:

                        —

                        from a Vehicle Unit by an Intelligent Dedicated Equipment (IDE) connected to the VU,

                        —

                        from a tachograph card by an IDE fitted with a card interface device (IFD),

                        —

                        from a tachograph card via a vehicle unit by an IDE connected to the VU.

                  To give the possibility to verify the authenticity and integrity of downloaded data stored on an ESM, data is downloaded with a signature appended in accordance with Appendix 11 Common Security Mechanisms. The source equipment (VU or card) identification and its security certificates (Member state and equipment) are also downloaded. The verifier of the data must possess independently a trusted European public key.

                        DDP_001

                        Data downloaded during one download session must be stored in the ESM within one single file.

                  1.2.   Acronyms and notations

            The following acronyms are used in this appendix:

                           AID

                        Application Identifier

                           ATR

                        Answer To Reset

                           CS

                        Checksum byte

                           DF

                        Dedicated File

                           DS_

                        Diagnostic Session

                           EF

                        Elementary File

                           ESM

                        External Storage Medium

                           FID

                        File Identifier (File ID)

                           FMT

                        Format Byte (first byte of message header)

                           ICC

                        Integrated Circuit Card

                           IDE

                        Intelligent Dedicated Equipment: The equipment used to perform data downloading to the ESM (e.g. Personal Computer)

                           IFD

                        Interface Device

                           KWP

                        Keyword Protocol 2000

                           LEN

                        Length Byte (last byte of message header)

                           PPS

                        Protocol Parameter Selection

                           PSO

                        Perform Security Operation

                           SID

                        Service Identifier

                           SRC

                        Source byte

                           TGT

                        Target Byte

                           TLV

                        Tag Length Value

                           TREP

                        Transfer Response Parameter

                           TRTP

                        Transfer Request Parameter

                           VU

                        Vehicle Unit

                  2.   V.U. DATA DOWNLOADING
            2.1.   Download procedure

            In order to carry on a VU data download, the operator must perform the following operations:

                        —

                        Insert his tachograph card inside a card slot of the VU (*);

                        —

                        Connect the IDE to the VU download connector;

                        —

                        Establish the connection between the IDE and the VU;

                        —

                        Select on the IDE the data to download and send the request to the VU;

                        —

                        Close the download session.

                  2.2.   Data download protocol

            The protocol is structured on a master-slave basis, with the IDE playing the master role and the VU playing the slave role.
            The message structure, types and flow are principally based on the Keyword Protocol 2000 (KWP) (ISO 14230-2 Road vehicles — Diagnostic systems — Keyword protocol 2000 — Part2: Data link layer).
            The application layer is principally based on the current draft to date of ISO 14229-1 (Road vehicles — Diagnostic systems — Part 1: Diagnostic services, version 6 of 22 February 2001).
            2.2.1   Message structure

                        DDP_002

                        All the messages exchanged between the IDE and the VU are formatted with a structure consisting of three parts:

                                    —

                                    Header composed by a Format byte (FMT), a Target byte (TGT), a Source byte (SRC) and possibly a Length byte (LEN),

                                    —

                                    Data field composed by a Service Identifier byte (SID) and a variable number of data bytes, which can include an optional diagnostic session byte (DS_) or an optional transfer parameter byte (TRTP or TREP).

                                    —

                                    Checksum composed by a Checksum byte (CS).

                                    Header

                                    Data field

                                    Checksum

                                    FMT

                                    TGT

                                    SRC

                                    LEN

                                    SID

                                    DATA

                                    …

                                    …

                                    …

                                    CS

                                    4 bytes

                                    Max 255 bytes

                                    1 byte

                              The TGT and SRC byte represent the physical address of the recipient and originator of the message. Values are F0 Hex for the IDE and EE Hex for the VU.
                        The LEN byte is the length of the Data field part.
                        The Checksum byte is the 8 bit sum series modulo 256 of all the bytes of the message excluding the CS itself.
                        FMT, SID, DS_, TRTP and TREP bytes are defined later in this document.

                        DDP_003

                        In the case where the data to be carried by the message is longer than the space available in the data field part, the message is actually sent in several sub messages. Each sub message bears a header, the same SID, TREP and a 2-byte sub message counter indicating the sub message number within the total message. To enable error checking and abort the IDE acknowledges every sub message. The IDE can accept the sub message, ask for it to be re-transmitted, request the VU to start again or abort the transmission.

                        DDP_004

                        If the last sub message contains exactly 255 bytes in the data field, a final sub message with an empty (except SID TREP and sub message counter) data field must be appended to show the end of the message.

                           Example:

                                    Header

                                    SID

                                    TREP

                                    Message

                                    CS

                                    4 Bytes

                                    Longer than 255 Bytes

                              Will be transmitted as:

                                    Header

                                    SID

                                    TREP

                                    00

                                    01

                                    Sub message 1

                                    CS

                                    4 Bytes

                                    255 Bytes

                                    Header

                                    SID

                                    TREP

                                    00

                                    02

                                    Sub message 2

                                    CS

                                    4 Bytes

                                    255 Bytes

                              …

                                    Header

                                    SID

                                    TREP

                                    xx

                                    yy

                                    Sub message n

                                    CS

                                    4 Bytes

                                    Less than 255 Bytes

                              or as:

                                    Header

                                    SID

                                    TREP

                                    00

                                    01

                                    Sub message 1

                                    CS

                                    4 Bytes

                                    255 Bytes

                                    Header

                                    SID

                                    TREP

                                    00

                                    02

                                    Sub message 2

                                    CS

                                    4 Bytes

                                    255 Bytes

                              …

                                    Header

                                    SID

                                    TREP

                                    xx

                                    yy

                                    Sub message n

                                    CS

                                    4 Bytes

                                    255 Bytes

                                    Header

                                    SID

                                    TREP

                                    xx

                                    yy + 1

                                    CS

                                    4 Bytes

                                    4 bytes

                  2.2.2   Message types

            The communication protocol for data download between the VU and the IDE requires the exchange of 8 different message types.
            The following table summarises these messages.

                        Message Structure

                        Max 4 Bytes
                        Header

                        Max 255 Bytes
                        Data

                        1 Byte
                        CheckSum

                        IDE ->

                        <- VU

                        FMT

                        TGT

                        SRC

                        LEN

                        SID

                        DS_/TRTP

                        DATA

                        CS

                        Start Communication Request

                        81

                        EE

                        F0

                        81

                        E0

                        Positive Response Start Communication

                        80

                        F0

                        EE

                        03

                        C1

                        EA, 8F

                        9B

                        Start Diagnostic Session Request

                        80

                        EE

                        F0

                        02

                        10

                        81

                        F1

                        Positive Response Start Diagnostic

                        80

                        F0

                        EE

                        02

                        50

                        81

                        31

                        Link Control Service

                        Verify Baud Rate (stage 1)

                        9 600  Bd

                        80

                        EE

                        F0

                        04

                        87

                        01,01,01

                        EC

                        19 200  Bd

                        80

                        EE

                        F0

                        04

                        87

                        01,01,02

                        ED

                        38 400  Bd

                        80

                        EE

                        F0

                        04

                        87

                        01,01,03

                        EE

                        57 600  Bd

                        80

                        EE

                        F0

                        04

                        87

                        01,01,04

                        EF

                        115 200  Bd

                        80

                        EE

                        F0

                        04

                        87

                        01,01,05

                        F0

                        Positive Response Verify Baud Rate

                        80

                        F0

                        EE

                        02

                        C7

                        01

                        28

                        Transition Baud Rate (stage 2)

                        80

                        EE

                        F0

                        03

                        87

                        02,03

                        ED

                        Request Upload

                        80

                        EE

                        F0

                        0A

                        35

                        00,00,00,00,00,FF,FF,FF,FF

                        99

                        Positive Response Request Upload

                        80

                        F0

                        EE

                        03

                        75

                        00,FF

                        D5

                        Transfer Data Request

                        Overview

                        80

                        EE

                        F0

                        02

                        36

                        01

                        97

                        Activities

                        80

                        EE

                        F0

                        06

                        36

                        02

                        Date

                        CS

                        Events & Faults

                        80

                        EE

                        F0

                        02

                        36

                        03

                        99

                        Detailed Speed

                        80

                        EE

                        F0

                        02

                        36

                        04

                        9A

                        Technical Data

                        80

                        EE

                        F0

                        02

                        36

                        05

                        9B

                        Card download

                        80

                        EE

                        F0

                        02

                        36

                        06

                        Slot

                        CS

                        Positive Response Transfer Data

                        80

                        F0

                        EE

                        Len

                        76

                        TREP

                        Data

                        CS

                        Request Transfer Exit

                        80

                        EE

                        F0

                        01

                        37

                        96

                        Positive Response Request Transfer Exit

                        80

                        F0

                        EE

                        01

                        77

                        D6

                        Stop Communication Request

                        80

                        EE

                        F0

                        01

                        82

                        E1

                        Positive Response Stop Communication

                        80

                        F0

                        EE

                        01

                        C2

                        21

                        Acknowledge sub message

                        80

                        EE

                        F0

                        Len

                        83

                        Data

                        CS

                        Negative responses

                        General reject

                        80

                        F0

                        EE

                        03

                        7F

                        Sid Req

                        10

                        CS

                        Service not supported

                        80

                        F0

                        EE

                        03

                        7F

                        Sid Req

                        11

                        CS

                        Sub function not supported

                        80

                        F0

                        EE

                        03

                        7F

                        Sid Req

                        12

                        CS

                        Incorrect Message Length

                        80

                        F0

                        EE

                        03

                        7F

                        Sid Req

                        13

                        CS

                        Conditions not correct or Request sequence error

                        80

                        F0

                        EE

                        03

                        7F

                        Sid Req

                        22

                        CS

                        Request out of range

                        80

                        F0

                        EE

                        03

                        7F

                        Sid Req

                        31

                        CS

                        Upload not accepted

                        80

                        F0

                        EE

                        03

                        7F

                        Sid Req

                        50

                        CS

                        Response pending

                        80

                        F0

                        EE

                        03

                        7F

                        Sid Req

                        78

                        CS

                        Data not available

                        80

                        F0

                        EE

                        03

                        7F

                        Sid Req

                        FA

                        CS

               Notes:

                        —

                        Sid Req = the Sid of the corresponding request.

                        —

                        TREP = the TRTP of the corresponding request.

                        —

                        Dark cells denote that nothing is transmitted.

                        —

                        The term upload (as seen from the IDE) is used for compatibility with ISO 14229. It means the same as download (as seen from the VU).

                        —

                        Potential 2-byte sub message counters are not shown in this table.

                        —

                        Slot is the slot number, either “1” (card on driver slot) or “2” (card on co-driver slot)

                        —

                        In case the slot is not specified, the VU shall select slot 1 if a card is inserted in this slot and it shall select slot 2 only in case it is specifically selected by the user.

                  2.2.2.1   Start Communication Request (SID 81)

                        DDP_005

                        This message is issued by the IDE to establish the communication link with the VU. Initial communications are always performed at 9 600 baud (until baud rate is eventually changed using the appropriate Link control services).

                  2.2.2.2   Positive Response Start Communication (SID C1)

                        DDP_006

                        This message is issued by the VU to answer positively to a start communication request. It includes the 2 key bytes ‘EA’‘8F’ indicating that the unit supports protocol with header including target source and length information.

                  2.2.2.3   Start Diagnostic Session Request (SID 10)

                        DDP_007

                        The Start Diagnostic Session request message is issued by the IDE in order to request a new diagnostic session with the VU. The sub function ‘default session’ (81 Hex) indicates a standard diagnostic session is to be opened.

                  2.2.2.4   Positive Response Start Diagnostic (SID 50)

                        DDP_008

                        The Positive Response Start Diagnostic message is sent by the VU to answer positively to Diagnostic Session Request.

                  2.2.2.5   Link Control Service (SID 87)

                        DDP_052

                        The Link Control Service is used by the IDE to initiate a change in baud rate. This takes place in two steps. In step one the IDE proposes the baud rate change, indicating the new rate. On receipt of a positive message from the VU the IDE sends out confirmation of the baud rate change to the VU (step two). The IDE then changes to the new baud rate. After receipt of the confirmation the VU changes to the new baud rate

                  2.2.2.6   Link Control Positive Response (SID C7)

                        DDP_053

                        The Link Control Positive Response is issued by the VU to answer positively to Link Control Service request (step one). Note that no response is given to the confirmation request (step two).

                  2.2.2.7   Request Upload (SID 35)

                        DDP_009

                        The Request Upload message is issued by the IDE to specify to the VU that a download operation is requested. To meet the requirements of ISO14229 data is included covering address, the size and format details for the data requested. As these are not known to the IDE prior to a download, the memory address is set to 0, format is unencrypted and uncompressed and the memory size is set to the maximum.

                  2.2.2.8   Positive Response Request Upload (SID 75)

                        DDP_010

                        The Positive Response Request Upload message is sent by the VU to indicate to the IDE that the VU is ready to download data. To meet the requirements of ISO 14229 data is included in this positive response message, indicating to the IDE that further Positive Response Transfer Data messages will include 00FF hex bytes maximum.

                  2.2.2.9   Transfer Data Request (SID 36)

                        DDP_011

                        The Transfer Data Request is sent by the IDE to specify to the VU the type of data that are to be downloaded. A one byte Transfer Request Parameter (TRTP) indicates the type of transfer.
                        There are six types of data transfer:

                                    —

                                    Overview (TRTP 01),

                                    —

                                    Activities of a specified date (TRTP 02),

                                    —

                                    Events and faults (TRTP 03),

                                    —

                                    Detailed speed (TRTP 04),

                                    —

                                    Technical data (TRTP 05),

                                    —

                                    Card download (TRTP 06).

                        DDP_054

                        It is mandatory for the IDE to request the overview data transfer (TRTP 01) during a download session as this only will ensure that the VU certificates are recorded within the downloaded file (and allow for verification of digital signature).
                        In the second case (TRTP 02) the Transfer Data Request message includes the indication of the calendar day ( format) to be downloaded.

                  2.2.2.10   Positive Response Transfer Data (SID 76)

                        DDP_012

                        The Positive Response Transfer Data is sent by the VU in response to the Transfer Data Request. The message contains the requested data, with a Transfer Response Parameter (TREP) corresponding to the TRTP of the request.

                        DDP055

                        In the first case (TREP 01), the VU will send data helping the IDE operator to choose the data he wants to download further. The information contained within this message is:

                                    —

                                    Security certificates,

                                    —

                                    Vehicle identification,

                                    —

                                    VU current date and time,

                                    —

                                    Min and Max downloadable date (VU data),

                                    —

                                    Indication of cards presence in the VU,

                                    —

                                    Previous download to a company,

                                    —

                                    Company locks,

                                    —

                                    Previous controls.

                  2.2.2.11   Request Transfer Exit (SID 37)

                        DDP_013

                        The Request Transfer Exit message is sent by the IDE to inform the VU that the download session is terminated.

                  2.2.2.12   Positive Response Request Transfer Exit (SID 77)

                        DDP_014

                        The Positive Response Request Transfer Exit message is sent by the VU to acknowledge the Request Transfer Exit.

                  2.2.2.13   Stop Communication Request (SID 82)

                        DDP_015

                        The Stop Communication Request message is sent by the IDE to disconnect the communication link with the VU.

                  2.2.2.14   Positive Response Stop Communication (SID C2)

                        DDP_016

                        The Positive Response Stop Communication message is sent by the VU to acknowledge the Stop Communication Request.

                  2.2.2.15   Acknowledge Sub Message (SID 83)

                        DDP_017

                        The Acknowledge Sub Message is sent by the IDE to confirm receipt of each part of a message that is being transmitted as several sub messages. The data field contains the SID received from the VU and a 2-byte code as follows:

                                    —

                                    MsgC+1 Acknowledges correct receipt of sub message number MsgC.
                                    Request from the IDE to the VU to send next sub message

                                    —

                                    MsgC indicates a problem with the receipt of sub message number MsgC.
                                    Request from the IDE to the VU to send the sub message again.

                                    —

                                    FFFF requests termination of the message.
                                    This can be used by the IDE to end the transmission of the VU message for any reason.

                              The last sub message of a message (LEN byte < 255) may be acknowledged using any of these codes or not acknowledged.
                        The VU responses that will consist of several sub messages are:

                                    —

                                    Positive Response Transfer Data (SID 76)

                  2.2.2.16   Negative Response (SID 7F)

                        DDP_018

                        The Negative Response message is sent by the VU in response to the above request messages when the VU cannot satisfy the request. The data fields of the message contains the SID of the response (7F), the SID of the request, and a code specifying the reason of the negative response. The following codes are available:

                                    —

                                    10 general reject
                                    The action cannot be performed for a reason not covered below.

                                    —

                                    11 service not supported
                                    The SID of the request is not understood.

                                    —

                                    12 sub function not supported
                                    The DS_ or TRTP of the request is not understood, or there are no further sub messages to be transmitted.

                                    —

                                    13 incorrect message length
                                    The length of the received message is wrong.

                                    —

                                    22 conditions not correct or request sequence error
                                    The required service is not active or the sequence of request messages is not correct.

                                    —

                                    31 Request out of range
                                    The request parameter record (data field) is not valid.

                                    —

                                    50 upload not accepted
                                    The request cannot be performed (VU in a non appropriate mode of operation or internal fault of the VU).

                                    —

                                    78 response pending
                                    The action requested cannot be completed in time and the VU is not ready to accept another request.

                                    —

                                    FA data not available
                                    The data object of a data transfer request are not available in the VU (e.g. no card is inserted, …).

                  2.2.3   Message flow

            A typical message flow during a normal data download procedure is the following:

                        IDE

                        VU

                        Start Communication Request

                        ⇨

                        ⇦

                        Positive Response

                        Start Diagnostic Service Request

                        ⇨

                        ⇦

                        Positive Response

                        Request Upload

                        ⇨

                        ⇦

                        Positive Response

                        Transfer Data Request Overview

                        ⇨

                        ⇦

                        Positive Response

                        Transfer Data Request #2

                        ⇨

                        ⇦

                        Positive Response #1

                        Acknowledge Sub Message #1

                        ⇨

                        ⇦

                        Positive Response #2

                        Acknowledge Sub Message #2

                        ⇨

                        ⇦

                        Positive Response #m

                        Acknowledge Sub Message #m

                        ⇨

                        ⇦

                        Positive Response (Data Field < 255 Bytes)

                        Acknowledge Sub Message (optional)

                        ⇨

                        …

                        Transfer Data Request #n

                        ⇨

                        ⇦

                        Positive Response

                        Request Transfer Exit

                        ⇨

                        ⇦

                        Positive Response

                        Stop Communication Request

                        ⇨

                        ⇦

                        Positive Response

                  2.2.4   Timing

                        DDP_019

                        During normal operation the timing parameters shown in the following figure are relevant:

                           Figure 1

                           Message flow, timing

                        Where:

                                    P1

                                    =

                                    Inter byte time for VU response.

                                    P2

                                    =

                                    Time between end of IDE request and start of VU response, or between end of IDE acknowledge and start of next VU response.

                                    P3

                                    =

                                    Time between end of VU response and start of new IDE request, or between end of VU response and start of IDE acknowledge, or between end of IDE request and start of new IDE request if VU fails to respond.

                                    P4

                                    =

                                    Inter byte time for IDE request.

                                    P5

                                    =

                                    Extended value of P3 for card downloading.

                              The allowed values for the timing parameters are showed in the following table (KWP extended timing parameters set, used in case of physical addressing for faster communication).

                                    Timing Parameter

                                    Lower limit
                                    Value (ms)

                                    Upper limit
                                    Value (ms)

                                    P1

                                    0

                                    20

                                    P2

                                    20

                                    1 000  (**)

                                    P3

                                    10

                                    5 000

                                    P4

                                    5

                                    20

                                    P5

                                    10

                                    20 minutes

                  2.2.5   Error handling

            If an error occurs during the message exchange, the message flow scheme is modified depending on which equipment has detected the error and on the message generating the error.
            In figure 2 and figure 3 the error handling procedures for the VU and the IDE are respectively shown.
            2.2.5.1   Start Communication phase

                        DDP_020

                        If the IDE detects an error during the Start Communication phase, either by timing or by the bit stream, then it will wait for a period P3 min before issuing again the request.

                        DDP_021

                        If the VU detects an error in the sequence coming from the IDE, it shall send no response and wait for another Start Communication Request message within a period P3 max.

                  2.2.5.2   Communication phase

            Two different error handling areas can be defined:

                        1.

                           The VU detects an IDE transmission error.

                                    DDP_022

                                    For every received message the VU shall detect timing errors, byte format errors (e.g. start and stop bit violations) and frame errors (wrong number of bytes received, wrong checksum byte).

                                    DDP_023

                                    If the VU detects one of the above errors, then it sends no response and ignores the message received.

                                    DDP_024

                                    The VU may detect other errors in the format or content of the received message (e.g. message not supported) even if the message satisfies the length and checksum requirements; in such a case, the VU shall respond to the IDE with a Negative Response message specifying the nature of the error.

                           Figure 2

                           VU error handling

                        2.

                           The IDE detects a VU transmission error.

                                    DDP_025

                                    For every received message the IDE shall detect timing errors, byte format errors (e.g. start and stop bit violations) and frame errors (wrong number of bytes received, wrong checksum byte).

                                    DDP_026

                                    The IDE shall detect sequence errors, e.g. incorrect sub message counter increments in successive received messages.

                                    DDP_027

                                    If the IDE detects an error or there was no response from the VU within a P2 max period, the request message will be sent again for a maximum of three transmissions in total. For the purposes of this error detection a sub message acknowledge will be considered as a request to the VU.

                                    DDP_028

                                    The IDE shall wait at least for a period of P3 min before beginning each transmission; the wait period shall be measured from the last calculated occurrence of a stop bit after the error was detected.

                           Figure 3

                           IDE error handling

                  2.2.6   Response Message content

            This paragraph specifies the content of the data fields of the various positive response messages.
            Data elements are defined in Appendix 1 data dictionary.
            Remark: For generation 2 downloads, each top-level data element is represented by a record array, even if it contains only one record. A record array starts with a header; this header contains the record type, the record size and the number of records. Record arrays are named by ‘…RecordArray’ (with header) in the following tables.
            2.2.6.1   Positive Response Transfer Data Overview

                        DDP_029

                        The data field of the ‘Positive Response Transfer Data Overview’ message shall provide the following data in the following order under the SID 76 Hex, the TREP 01 Hex and appropriate sub message splitting and counting:
                        Data structure generation 1

                                    Data element

                                    Comment

                                    VU Security certificates

                                    Vehicle identification

                                    VU current date and time

                                    Downloadable period

                                    Type of cards inserted in the VU

                                    Previous VU download

                                    All company locks stored. If the section is empty, only noOfLocks = 0 is sent.

                                    All control records stored in the VU. If the section is empty, only noOfControls = 0 is sent

                                    RSA signature of all data (except certificates) starting from VehicleIdentificationNumber down to last byte of last VuControlActivityData.

                        Data structure generation 2

                                    Data element

                                    Comment

                                    Member state certificate

                                    VU certificate

                                    Vehicle identification

                                    Vehicle registration number

                                    VU current date and time

                                    Downloadable period

                                    Type of cards inserted in the VU

                                    Previous VU download

                                    All company locks stored. If the section is empty, an array header with noOfRecords = 0 is sent

                                    All control records stored in the VU. If the section is empty, an array header with noOfRecords = 0 is sent

                                    ECC signature of all preceding data except the certificates.

                  2.2.6.2   Positive Response Transfer Data Activities

                        DDP_030

                        The data field of the ‘Positive Response Transfer Data Activities’ message shall provide the following data in the following order under the SID 76 Hex, the TREP 02 Hex and appropriate sub message splitting and counting:
                        Data structure generation 1

                                    Data element

                                    Comment

                                    Date of day downloaded

                                    Odometer at end of downloaded day

                                    Cards insertion withdrawal cycles data.

                                                —

                                                If this section contains no available data, only noOfVuCardIWRecords = 0 is sent.

                                                —

                                                When a VuCardIWRecord lies across 00:00 (card insertion on previous day) or across 24:00 (card withdrawal the following day) it shall appear in full within the two days involved.

                                    Slots status at 00:00 and activity changes recorded for the day downloaded.

                                    Places related data recorded for the day downloaded. If the section is empty, only noOfPlaceRecords = 0 is sent.

                                    Specific conditions data recorded for the day downloaded. If the section is empty, only noOfSpecificConditionRecords=0 is sent

                                    RSA signature of all data starting from TimeReal down to last byte of last specific condition record.

                        Data structure generation 2

                                    Data element

                                    Comment

                                    Date of day downloaded

                                    Odometer at end of downloaded day

                                    Cards insertion withdrawal cycles data.

                                                —

                                                If this section contains no available data, an array header with noOfRecords = 0 is sent.

                                                —

                                                When a VuCardIWRecord lies across 00:00 (card insertion on previous day) or across 24:00 (card withdrawal the following day) it shall appear in full within the two days involved.

                                    Slots status at 00:00 and activity changes recorded for the day downloaded.

                                    Places related data recorded for the day downloaded. If the section is empty, an array header with noOfRecords = 0 is sent.

                                    GNSS positions of the vehicle if the continuous driving time of the driver reaches a multiple of three hours. If the section is empty, an array header with noOfRecords = 0 is sent.

                                    Specific conditions data recorded for the day downloaded. If the section is empty, an array header with noOfRecords =0 is sent

                                    ECC signature of all preceding data.

                  2.2.6.3   Positive Response Transfer Data Events and Faults

                        DDP_031

                        The data field of the ‘Positive Response Transfer Data Events and Faults’ message shall provide the following data in the following order under the SID 76 Hex, the TREP 03 Hex and appropriate sub message splitting and counting:
                        Data structure generation 1

                                    Data element

                                    Comment

                                    All faults stored or on-going in the VU.
                                    If the section is empty, only noOfVuFaults = 0 is sent.

                                    All events (except over speeding) stored or on-going in the VU.
                                    If the section is empty, only noOfVuEvents = 0 is sent.

                                    Data related to last over speeding control (default value if no data).

                                    All over speeding events stored in the VU.
                                    If the section is empty, only noOfVuOverSpeedingEvents = 0 is sent.

                                    All time adjustment events stored in the VU (outside the frame of a full calibration).
                                    If the section is empty, only noOfVuTimeAdjRecords = 0 is sent.

                                    RSA signature of all data starting from noOfVuFaults down to last byte of last time adjustment record

                        Data structure generation 2

                                    Data element

                                    Comment

                                    All faults stored or on-going in the VU.
                                    If the section is empty, an array header with noOfRecords = 0 is sent.

                                    All events (except over speeding) stored or on-going in the VU.
                                    If the section is empty, an array header with noOfRecords = 0 is sent.

                                    Data related to last over speeding control (default value if no data).

                                    All over speeding events stored in the VU.
                                    If the section is empty, an array header with noOfRecords = 0 is sent.

                                    All time adjustment events stored in the VU (outside the frame of a full calibration).
                                    If the section is empty, an array header with noOfRecords = 0 is sent.

                                    ECC signature of all preceding data.

                  2.2.6.4   Positive Response Transfer Data Detailed Speed

                        DDP_032

                        The data field of the ‘Positive Response Transfer Data Detailed Speed’ message shall provide the following data in the following order under the SID 76 Hex, the TREP 04 Hex and appropriate sub message splitting and counting:
                        Data structure generation 1

                                    Data element

                                    Comment

                                    All detailed speed stored in the VU (one speed block per minute during which the vehicle has been moving)
                                    60 speed values per minute (one per second).

                                    RSA signature of all data starting from noOfSpeedBlocks down to last byte of last speed block.

                        Data structure generation 2:

                                    Data element

                                    Comment

                                    All detailed speed stored in the VU (one speed block per minute during which the vehicle has been moving)
                                    60 speed values per minute (one per second).

                                    ECC signature of all preceding data.

                  2.2.6.5   Positive Response Transfer Data Technical Data

                        DDP_033

                        The data field of the ‘Positive Response Transfer Data Technical Data’ message shall provide the following data in the following order under the SID 76 Hex, the TREP 05 Hex and appropriate sub message splitting and counting:
                        Data structure generation 1

                                    Data element

                                    Comment

                                    All calibration records stored in the VU.

                                    RSA signature of all data starting from vuManufacturerName down to last byte of last VuCalibrationRecord.

                        Data structure generation 2:

                                    Data element

                                    Comment

                                    All MS pairings stored in the VU

                                    All external GNSS facility couplings stored in the VU

                                    All calibration records stored in the VU.

                                    All card insertion data stored in the VU.

                                    ECC signature of all preceding data.

                  2.3.   ESM File storage

                        DDP_034

                        When a download session has included a VU data transfer, the IDE shall store within one single physical file all data received from the VU during the download session within Positive Response Transfer Data messages. Data stored excludes message headers, sub-message counters, empty sub-messages and checksums but include the SID and TREP (of the first sub-message only if several sub-messages).

                  3.   TACHOGRAPH CARDS DOWNLOADING PROTOCOL
            3.1.   Scope

            This paragraph describes the direct card data downloading of a tachograph card to an IDE. The IDE is not part of the secure environment; therefore no authentication between the card and the IDE is performed.
            3.2.   Definitions

                           Download session

                        :

                        Each time a download of the ICC data is performed. The session covers the complete procedure from the reset of the ICC by an IFD until the deactivation of the ICC (withdraw of the card or next reset).

                           Signed Data File

                        :

                        A file from the ICC. The file is transferred to the IFD in plain text. On the ICC the file is hashed and signed and the signature is transferred to the IFD.

                  3.3.   Card Downloading

                        DDP_035

                        The download of a tachograph card includes the following steps:

                                    —

                                    Download the common information of the card in the Efs and . This information is optional and is not secured with a digital signature.

                                    —

                                    Download the EFs (or ) and . This information is not secured with a digital signature.
                                    It is mandatory to download these files for each download session.

                                    —

                                    Download the other application data EFs (within and if relevant) except EF . This information is secured with a digital signature.

                                    —

                                    It is mandatory to download at least the Efs and for each download session.

                                    —

                                    When downloading a driver card it is also mandatory to download the following EFs:

                                    —

                                    When downloading a driver card, update the date in EF ,

                                    —

                                    When downloading a workshop card, reset the calibration counter in EF .

                                    —

                                    When downloading a workshop card the shall not be downloaded.

                  3.3.1   Initialisation sequence

                        DDP_036

                        The IDE shall initiate the sequence as follows:

                                    Card

                                    Direction

                                    IDE/IFD

                                    Meaning/Remarks

                                    ⇦

                                    Hardware reset

                                       ATR

                                    ⇨

                              It is optional to use PPS to switch to a higher baud rate as long as the ICC supports it.

                  3.3.2   Sequence for un-signed data files

                        DDP_037

                        The sequence to download the EFs ICC, IC, Card_Certificate (or CardSignCertificate) and CA_Certificate is as follows:

                                    Card

                                    Direction

                                    IDE/IFD

                                    Meaning/Remarks

                                    ⇦

                                       Select File

                                    Select by File identifiers

                                       OK

                                    ⇨

                                    ⇦

                                       Read Binary

                                    If the file contains more data than the buffer size of the reader or the card the command has to be repeated until the complete file is read.

                                       File Data

                                       OK

                                    ⇨

                                    Store data to ESM

                                    according to 3.4 Data storage format

                           Note 1: Before selecting the Card_Certificate (or CardSignCertificate) EF, the Tachograph Application must be selected (selection by AID).

                           Note 2: Selecting and reading a file may also be performed in one step using a Read Binary command with a short EF identifier.

                  3.3.3   Sequence for Signed data files

                        DDP_038

                        The following sequence shall be used for each of the following files that has to be downloaded with their signature:

                                    Card

                                    Dir

                                    IDE/IFD

                                    Meaning/Remarks

                                    ⇦

                                       Select File

                                       OK

                                    ⇨

                                    ⇦

                                       Perform Hash of File

                                    Calculates the hash value over the data content of the selected file using the prescribed hash algorithm in accordance with Appendix 11. This command is not an ISO-Command.

                                    Calculate Hash of File and store Hash value temporarily

                                       OK

                                    ⇨

                                    ⇦

                                       Read Binary

                                    If the file contains more data than the buffer of the reader or the card can hold, the command has to be repeated until the complete file is read.

                                       File Data

                                       OK

                                    ⇨

                                    Store received data to ESM

                                    according to 3.4 Data storage format

                                    ⇦

                                       PSO: Compute Digital Signature

                                    Perform Security Operation ‘Compute Digital Signature’ using the temporarily stored Hash value

                                       Signature

                                       OK

                                    ⇨

                                    Append data to the previous stored data on the ESM

                                    according to 3.4 Data storage format

                           Note: Selecting and reading a file may also be performed in one step using a Read Binary command with a short EF identifier. In this case the EF may be selected and read before the command Perform Hash of File is applied.

                  3.3.4   Sequence for resetting the calibration counter.

                        DDP_039

                     The sequence to reset the
                           counter in the EF
                           in a workshop card is the following:
                                    Card

                                    Dir

                                    IDE/IFD

                                    Meaning/Remarks

                                    ⇦

                                       Select File EF Card_Download

                                    Select by File identifiers

                                       OK

                                    ⇨

                                    ⇦

                                       Update Binary

                                    NoOfCalibrationsSinceDownload = ‘00 00’

                                    resets card download number

                                       OK

                                    ⇨

                           Note: Selecting and updating a file may also be performed in one step using an Update Binary command with a short EF identifier.

                  3.4.   Data storage format

            3.4.1   Introduction

                        DDP_040

                        The downloaded data has to be stored according to the following conditions:

                                    —

                                    The data shall be stored transparent. This means that the order of the bytes as well as the order of the bits inside the byte that are transferred from the card has to be preserved during storage.

                                    —

                                    All files of the card downloaded within a download session are stored in one file on the ESM.

                  3.4.2   File format

                        DDP_041

                        The file format is a concatenation of several TLV objects.

                        DDP_042

                        The tag for an EF shall be the FID plus the appendix „00“.

                        DDP_043

                        The tag of an EF's signature shall be the FID of the file plus the appendix „01“.

                        DDP_044

                        The length is a two byte value. The value defines the number of bytes in the value field. The value „FF FF“ in the length field is reserved for future use.

                        DDP_045

                        When a file is not downloaded nothing related to the file shall be stored (no tag and no zero length).

                        DDP_046

                        A signature shall be stored as the next TLV object directly after the TLV object that contains the data of the file.

                                    Definition

                                    Meaning

                                    Length

                                    FID (2 Bytes) || „00“

                                    Tag for EF (FID)

                                    3 Bytes

                                    FID (2 Bytes) || „01“

                                    Tag for Signature of EF(FID)

                                    3 Bytes

                                    xx xx

                                    Length of Value field

                                    2 Bytes

                              Example of data in a download file on an ESM:

                                    Tag

                                    Length

                                    Value

                                    Data of EF ICC

                                    Data of EF Card_Certificate

                                    …

                                 Data of EF

                                 Signature of EF

                  4.   DOWNLOADING A TACHOGRAPH CARD VIA A VEHICLE UNIT.

                        DDP_047

                        The VU must allow for downloading the content of a driver card inserted to a connected IDE.

                        DDP_048

                        The IDE shall send a ‘Transfer Data Request Card Download’ message to the VU to initiate this mode (see 2.2.2.9).

                        DDP_049

                        The VU shall then download the whole card, file by file, in accordance with the card downloading protocol defined in paragraph 3, and forward all data received from the card to the IDE within the appropriate TLV file format (see 3.4.2) and encapsulated within a ‘Positive Response Transfer Data’ message.

                        DDP_050

                        The IDE shall retrieve card data from the ‘Positive Response Transfer Data’ message (stripping all headers, SIDs, TREPs, sub message counters, and checksums) and store them within one single physical file as described in paragraph 2.3.

                        DDP_051

                     The VU shall then, as applicable, update the
                           or the
                           file of the driver card.

               (*)  The card inserted will trigger the appropriate access rights to the downloading function and to the data. It shall, however, be possible to download data from a driver card inserted into one of the VU slots when no other card type is inserted in the other slot.

               (**)  If the VU responds with a Negative Response containing a code meaning ‘request correctly received, response pending’, this value is extended to the same upper limit value of P3.

            Appendix 8

               CALIBRATION PROTOCOL

            TABLE OF CONTENT

                        1.

                     INTRODUCTION
                     283

                        2.

                     TERMS, DEFINITIONS AND REFERENCES
                     283

                        3.

                     OVERVIEW OF SERVICES
                     284

                        3.1.

                     Services available
                     284

                        3.2.

                     Response codes
                     285

                        4.

                     COMMUNICATION SERVICES
                     285

                        4.1.

                     StartCommunication Service
                     285

                        4.2.

                     StopCommunication Service
                     287

                        4.2.1

                     Message description
                     287

                        4.2.2

                     Message format
                     288

                        4.2.3

                     Parameter Definition
                     289

                        4.3.

                     TesterPresent Service
                     289

                        4.3.1

                     Message description
                     289

                        4.3.2

                     Message format
                     289

                        5.

                     MANAGEMENT SERVICES
                     291

                        5.1.

                     StartDiagnosticSession service
                     291

                        5.1.1

                     Message description
                     291

                        5.1.2

                     Message format
                     292

                        5.1.3

                     Parameter definition
                     293

                        5.2.

                     SecurityAccess service
                     294

                        5.2.1

                     Message Description
                     294

                        5.2.2

                     Message format — SecurityAccess — requestSeed
                     295

                        5.2.3

                     Message format — SecurityAccess — sendKey
                     296

                        6.

                     DATA TRANSMISSION SERVICES
                     297

                        6.1.

                     ReadDataByIdentifier service
                     298

                        6.1.1

                     Message description
                     298

                        6.1.2

                     Message format
                     298

                        6.1.3

                     Parameter Definition
                     299

                        6.2.

                     WriteDataByIdentifier service
                     300

                        6.2.1

                     Message description
                     300

                        6.2.2

                     Message format
                     300

                        6.2.3

                     Parameter definition
                     302

                        7.

                     CONTROL OF TEST PULSES — INPUT/OUTPUT CONTROL FUNCTIONAL UNIT
                     302

                        7.1.

                     InputOutputControlByIdentifier service
                     302

                        7.1.1

                     Message description
                     302

                        7.1.2

                     Message format
                     303

                        7.1.3

                     Parameter definition
                     304

                        8.

                     DATARECORDS FORMATS
                     305

                        8.1.

                     Transmitted parameter ranges
                     305

                        8.2.

                     dataRecords formats
                     306
                  1.   INTRODUCTION
            This appendix describes how data is exchanged between a vehicle unit and a tester via the K-line which forms part of the calibration interface described in Appendix 6. It also describes control of the input/output signal line on the calibration connector.
            Establishing K-line communications is described in Section 4 ‘Communication Services’.
            This appendix uses the idea of diagnostic ‘sessions’ to determine the scope of K-line control under different conditions. The default session is the ‘StandardDiagnosticSession’ where all data can be read from a vehicle unit but no data can be written to a vehicle unit.
            Selection of the diagnostic session is described in Section 5 ‘Management Services’.
            This appendix has to be considered as relevant for both generations of VUs and of workshop cards, in compliance with the interoperability requirements laid down in this Regulation.

                        CPR_001

                        The ‘ECUProgrammingSession’ allows data entry into the vehicle unit. In the case of entry of calibration data, the vehicle unit must, in addition be in the CALIBRATION mode of operation.
                        Data transfer via K-line is described in Section 6 ‘Data Transmission Services’. Formats of data transferred are detailed in Section 8 ‘dataRecords formats’.

                        CPR_002

                        The ‘ECUAdjustmentSession’ allows the selection of the I/O mode of the calibration I/O signal line via the K-line interface. Control of the calibration I/O signal line is described in section 7 ‘Control of Test Pulses — Input/Output Control functional unit’.

                        CPR_003

                        Throughout this document the address of the tester is referred to as ‘tt’. Although there may be preferred addresses for testers, the VU shall respond correctly to any tester address. The physical address of the VU is 0xEE.

                  2.   TERMS, DEFINITIONS AND REFERENCES
            The protocols, messages and error codes are principally based on a draft of ISO 14229-1 (Road vehicles — Diagnostic systems — Part 1: Diagnostic services, version 6 of 22 February 2001).
            Byte encoding and hexadecimal values are used for the service identifiers, the service requests and responses, and the standard parameters.
            The term ‘tester’ refers to the equipment used to enter programming/calibration data into the VU.
            The terms ‘client’ and ‘server’ refer to the tester and the VU respectively.
            The term ECU means ‘Electronic Control Unit’ and refers to the VU.

               References:

            ISO 14230-2: Road Vehicles -Diagnostic Systems — Keyword Protocol 2000- Part 2: Data Link Layer.
            First edition: 1999.
            Vehicles — Diagnostic.
            3.   OVERVIEW OF SERVICES
            3.1.   Services available

            The following table provides an overview of the services that will be available in the tachograph and are defined in this document.

                        CPR_004

                        The table indicates the services that are available in an enabled diagnostic session.

                                    —

                                    The 1st column lists the services that are available.

                                    —

                                    The 2nd column includes the section number in this appendix where of service is further defined.

                                    —

                                    The 3rd column assigns the service identifier values for request messages.

                                    —

                                    The 4th column specifies the services of the ‘StandardDiagnosticSession’ (SD) which must be implemented in each VU.

                                    —

                                    The 5th column specifies the services of the ‘ECUAdjustmentSession’ (ECUAS) which must be implemented to allow control of the I/O signal line in the front panel calibration connector of the VU.

                                    —

                                    The 6th column specifies the services of the ‘ECUProgrammingSession’ (ECUPS) which must be implemented to allow for programming of parameters in the VU.

               Table 1

               Service Identifier value summary table

                        Diagnostic Sessions

                        Diagnostic Service Name

                        Section No.

                        SId Req.Value

                        SD

                        ECUAS

                        ECUPS

                        StartCommunication

                        4.1

                        81

                        ■

                        ■

                        ■

                        StopCommunication

                        4.2

                        82

                        ■

                        TesterPresent

                        4.3

                        3E

                        ■

                        ■

                        ■

                        StartDiagnosticSession

                        5.1

                        10

                        ■

                        ■

                        ■

                        SecurityAccess

                        5.2

                        27

                        ■

                        ■

                        ■

                        ReadDataByIdentifier

                        6.1

                        22

                        ■

                        ■

                        ■

                        WriteDataByIdentifier

                        6.2

                        2E

                        ■

                        InputOutputControlByIdentifier

                        7.1

                        2F

                        ■

                                    ■

                                    This symbol indicates that the service is mandatory in this diagnostic session.
                                    No symbol indicates that this service is not allowed in this diagnostic session.

                  3.2.   Response codes

            Response codes are defined for each service.
            4.   COMMUNICATION SERVICES
            Some services are necessary to establish and maintain communication. They do not appear on the application layer. The services available are detailed in the following table:

               Table 2

               Communication Services

                        Service name

                        Description

                        StartCommunication

                        The client requests to start a communication session with a server(s).

                        StopCommunication

                        The client requests to stop the current communication session.

                        TesterPresent

                        The client indicates to the server that it is still present.

                        CPR_005

                        The StartCommunication Service is used for starting a communication. In order to perform any service, communication must be initialised and the communication parameters need to be appropriate for the desired mode.

                  4.1.   StartCommunication Service

                        CPR_006

                        Upon receiving a StartCommunication indication primitive, the VU shall check if the requested communication link can be initialised under the present conditions. Valid conditions for the initialisation of a communication link are described in document ISO 14230-2.

                        CPR_007

                        Then the VU shall perform all actions necessary to initialise the communication link and send a StartCommunication response primitive with the Positive Response parameters selected.

                        CPR_008

                        If a VU that is already initialised (and has entered any diagnostic session) receives a new StartCommunication Request (e.g. due to error recovery in the tester) the request shall be accepted and the VU shall be reinitialised.

                        CPR_009

                        If the communication link cannot be initialised for any reason, the VU shall continue operating as it was immediately prior to the attempt to initialise the communication link..

                        CPR_010

                        The StartCommunication Request message must be physically addressed.

                        CPR_011

                        Initialising the VU for services is performed through a ‘fast initialisation’ method,

                                    —

                                    There is a bus-idle time prior to any activity.

                                    —

                                    The tester then sends an initialisation pattern.

                                    —

                                    All information which is necessary to establish communication is contained in the response of the VU.

                        CPR_012

                        After completion of the initialisation,

                                    —

                                    All communication parameters are set to values defined in Table 4 according to the key bytes.

                                    —

                                    The VU is waiting for the first request of the tester.

                                    —

                                    The VU is in the default diagnostic mode, i.e. StandardDiagnosticSession.

                                    —

                                    The calibration I/O signal line is in the default state, i.e. disabled state.

                        CPR_014

                        The data rate on the K-line shall be 10 400 Baud.

                        CPR_016

                        The fast initialisation is started by the tester transmitting a Wake up pattern (Wup) on the K-line. The pattern begins after the idle time on K-line with a low time of Tinil. The tester transmits the first bit of the StartCommunication Service after a time of Twup following the first falling edge.

                        CPR_017

                        The timing values for the fast initialisation and communications in general are detailed in the tables below. There are different possibilities for the idle time:

                                    —

                                    First transmission after power on, Tidle = 300 ms.

                                    —

                                    After completion of a StopCommunication Service, Tidle = P3 min.

                                    —

                                    After stopping communication by time-out P3 max, Tidle = 0.

                           Table 3

                           Timing values for fast initialisation

                                    Parameter

                                    min value

                                    max value

                                    Tinil

                                    25 ± 1 ms

                                    24 ms

                                    26 ms

                                    Twup

                                    50 ± 1 ms

                                    49 ms

                                    51 ms

                           Table 4

                           Communication timing values

                                    Timing Parameter

                                    Parameter Description

                                    lower limit values [ms]

                                    upper limit values [ms]

                                    min.

                                    max.

                                    P1

                                    Inter byte time for VU response

                                    0

                                    20

                                    P2

                                    Time between tester request and VU response or two VU responses

                                    25

                                    250

                                    P3

                                    Time between end of VU responses and start of new tester request

                                    55

                                    5 000

                                    P4

                                    Inter byte time for tester request

                                    5

                                    20

                        CPR_018

                        The message format for fast initialisation is detailed in the following tables. (NOTE: Hex means hexadecimal)

                           Table 5

                           StartCommunication Request Message

                                    Byte #

                                    Parameter Name

                                    Hex Value

                                    Mnemonic

                                    #1

                                    Format byte — physical addressing

                                    81

                                    FMT

                                    #2

                                    Target address byte

                                    EE

                                    TGT

                                    #3

                                    Source address byte

                                    tt

                                    SRC

                                       #4

                                       StartCommunication Request Service Id

                                       81

                                       SCR

                                    #5

                                    Checksum

                                    00-FF

                                    CS

                           Table 6

                           StartCommunication Positive Response Message

                                    Byte #

                                    Parameter Name

                                    Hex Value

                                    Mnemonic

                                    #1

                                    Format byte — physical addressing

                                    80

                                    FMT

                                    #2

                                    Target address byte

                                    tt

                                    TGT

                                    #3

                                    Source address byte

                                    EE

                                    SRC

                                    #4

                                    Additional length byte

                                    03

                                    LEN

                                       #5

                                       StartCommunication Positive Response Service Id

                                       C1

                                       SCRPR

                                    #6

                                    Key byte 1

                                    EA

                                    KB1

                                    #7

                                    Key byte 2

                                    8F

                                    KB2

                                    #8

                                    Checksum

                                    00-FF

                                    CS

                        CPR_019

                        There is no negative response to the StartCommunication Request message, if there is no positive response message to be transmitted then the VU is not initialised, nothing is transmitted and it remains in its normal operation.

                  4.2.   StopCommunication Service

            4.2.1   Message description

            The purpose of this communication layer service is to terminate a communication session.

                        CPR_020

                        Upon receiving a StopCommunication indication primitive, the VU shall check if the current conditions allow to terminate this communication. In this case the VU shall perform all actions necessary to terminate this communication.

                        CPR_021

                        If it is possible to terminate the communication, the VU shall issue a StopCommunication response primitive with the Positive Response parameters selected, before the communication is terminated.

                        CPR_022

                        If the communication cannot be terminated by any reason, the VU shall issue a StopCommunication response primitive with the Negative Response parameter selected.

                        CPR_023

                        If time-out of P3 max is detected by the VU, the communication shall be terminated without any response primitive being issued.

                  4.2.2   Message format

                        CPR_024

                        The message formats for the StopCommunication primitives are detailed in the following tables.

                           Table 7

                           StopCommunication Request Message

                                    Byte #

                                    Parameter Name

                                    Hex Value

                                    Mnemonic

                                    #1

                                    Format byte — physical addressing

                                    80

                                    FMT

                                    #2

                                    Target address byte

                                    EE

                                    TGT

                                    #3

                                    Source address byte

                                    tt

                                    SRC

                                    #4

                                    Additional length byte

                                    01

                                    LEN

                                       #5

                                       StopCommunication Request Service Id

                                       82

                                       SPR

                                    #6

                                    Checksum

                                    00-FF

                                    CS

                           Table 8

                           StopCommunication Positive Response Message

                                    Byte #

                                    Parameter Name

                                    Hex Value

                                    Mnemonic

                                    #1

                                    Format byte — physical addressing

                                    80

                                    FMT

                                    #2

                                    Target address byte

                                    tt

                                    TGT

                                    #3

                                    Source address byte

                                    EE

                                    SRC

                                    #4

                                    Additional length byte

                                    01

                                    LEN

                                       #5

                                       StopCommunication Positive Response Service Id

                                       C2

                                       SPRPR

                                    #6

                                    Checksum

                                    00-FF

                                    CS

                           Table 9

                           StopCommunication Negative Response Message

                                    Byte #

                                    Parameter Name

                                    Hex Value

                                    Mnemonic

                                    #1

                                    Format byte — physical addressing

                                    80

                                    FMT

                                    #2

                                    Target address byte

                                    tt

                                    TGT

                                    #3

                                    Source address byte

                                    EE

                                    SRC

                                    #4

                                    Additional length byte

                                    03

                                    LEN

                                       #5

                                       negative Response Service Id

                                       7F

                                       NR

                                    #6

                                    StopCommunication Request Service Identification

                                    82

                                    SPR

                                    #7

                                    responseCode = generalReject

                                    10

                                    RC_GR

                                    #8

                                    Checksum

                                    00-FF

                                    CS

                  4.2.3   Parameter Definition

            This service does not require any parameter definition.
            4.3.   TesterPresent Service

            4.3.1   Message description

            The TesterPresent service is used by the tester to indicate to the server that it is still present, in order to prevent the server from automatically returning to normal operation and possibly stopping the communication. This service, sent periodically, keeps the diagnostic session/communication active by resetting the P3 timer each time a request for this service is received.
            4.3.2   Message format

                        CPR_079

                        The message formats for the TesterPresent primitives are detailed in the following tables.

                           Table 10

                           TesterPresent Request Message

                                    Byte #

                                    Parameter Name

                                    Hex Value

                                    Mnemonic

                                    #1

                                    Format byte — physical addressing

                                    80

                                    FMT

                                    #2

                                    Target address byte

                                    EE

                                    TGT

                                    #3

                                    Source address byte

                                    tt

                                    SRC

                                    #4

                                    Additional length byte

                                    02

                                    LEN

                                       #5

                                       TesterPresent Request Service Id

                                       3E

                                       TP

                                    #6

                                    Sub Function = responseRequired =

                                    [ yes

                                    01

                                    RESPREQ_Y

                                    no ]

                                    02

                                    RESPREQ_NO

                                    #7

                                    Checksum

                                    00-FF

                                    CS

                        CPR_080

                        If the responseRequired parameter is set to ‘yes’, then the server shall respond with the following positive response message. If set to ‘no’, then no response is sent by the server.

                           Table 11

                           TesterPresent Positive Response Message

                                    Byte #

                                    Parameter Name

                                    Hex Value

                                    Mnemonic

                                    #1

                                    Format byte — physical addressing

                                    80

                                    FMT

                                    #2

                                    Target address byte

                                    tt

                                    TGT

                                    #3

                                    Source address byte

                                    EE

                                    SRC

                                    #4

                                    Additional length byte

                                    01

                                    LEN

                                       #5

                                       TesterPresent Positive Response Service Id

                                       7E

                                       TPPR

                                    #6

                                    Checksum

                                    00-FF

                                    CS

                        CPR_081

                        The service shall support the following negative responses codes:

                           Table 12

                           TesterPresent Negative Response Message

                                    Byte #

                                    Parameter Name

                                    Hex Value

                                    Mnemonic

                                    #1

                                    Format byte — physical addressing

                                    80

                                    FMT

                                    #2

                                    Target address byte

                                    tt

                                    TGT

                                    #3

                                    Source address byte

                                    EE

                                    SRC

                                    #4

                                    Additional length byte

                                    03

                                    LEN

                                       #5

                                       negative Response Service Id

                                       7F

                                       NR

                                    #6

                                    TesterPresent Request Service Identification

                                    3E

                                    TP

                                    #7

                                    responseCode =

                                    [ SubFunctionNotSupported-InvalidFormat

                                    12

                                    RC_SFNS_IF

                                    incorrectMessageLength ]

                                    13

                                    RC_IML

                                    #8

                                    Checksum

                                    00-FF

                                    CS

                  5.   MANAGEMENT SERVICES
            The services available are detailed in the following table:

               Table 13

               Management Services

                        Service name

                        Description

                        StartDiagnosticSession

                        The client requests to start a diagnostic session with a VU.

                        SecurityAccess

                        The client requests access to functions restricted to authorised users.

                  5.1.   StartDiagnosticSession service

            5.1.1   Message description

                        CPR_025

                        The service StartDiagnosticSession is used to enable different diagnostic sessions in the server. A diagnostic session enables a specific set of services according to Table 17. A session can enable vehicle manufacturer specific services which are not part of this document. Implementation rules shall conform to the following requirements:

                                    —

                                    There shall be always exactly one diagnostic session active in the VU,

                                    —

                                    The VU shall always start the StandardDiagnosticSession when powered up. If no other diagnostic session is started, then the StandardDiagnosticSession shall be running as long as the VU is powered,

                                    —

                                    If a diagnostic session which is already running has been requested by the tester, then the VU shall send a positive response message,

                                    —

                                    Whenever the tester requests a new diagnostic session, the VU shall first send a StartDiagnosticSession positive response message before the new session becomes active in the VU. If the VU is not able to start the requested new diagnostic session, then it shall respond with a StartDiagnosticSession negative response message, and the current session shall continue.

                        CPR_026

                        A diagnostic session shall only be started if communication has been established between the client and the VU.

                        CPR_027

                        The timing parameters defined in Table 4 shall be active after a successful StartDiagnosticSession with the diagnosticSession parameter set to ‘StandardDiagnosticSession’ in the request message if another diagnostic session was previously active.

                  5.1.2   Message format

                        CPR_028

                        The message formats for the StartDiagnosticSession primitives are detailed in the following tables.

                           Table 14

                           StartDiagnosticSession Request Message

                                    Byte #

                                    Parameter Name

                                    Hex Value

                                    Mnemonic

                                    #1

                                    Format byte — physical addressing

                                    80

                                    FMT

                                    #2

                                    Target address byte

                                    EE

                                    TGT

                                    #3

                                    Source address byte

                                    tt

                                    SRC

                                    #4

                                    Additional length byte

                                    02

                                    LEN

                                       #5

                                       StartDiagnosticSession Request Service Id

                                       10

                                       STDS

                                    #6

                                    diagnosticSession = [one value from Table 17]

                                    xx

                                    DS_…

                                    #7

                                    Checksum

                                    00-FF

                                    CS

                           Table 15

                           StartDiagnosticSession Positive Response Message

                                    Byte #

                                    Parameter Name

                                    Hex Value

                                    Mnemonic

                                    #1

                                    Format byte — physical addressing

                                    80

                                    FMT

                                    #2

                                    Target address byte

                                    tt

                                    TGT

                                    #3

                                    Source address byte

                                    EE

                                    SRC

                                    #4

                                    Additional length byte

                                    02

                                    LEN

                                       #5

                                       StartDiagnosticSession Positive Response Service Id

                                       50

                                       STDSPR

                                    #6

                                    diagnosticSession = [same value as in byte #6 Table 14]

                                    xx

                                    DS_…

                                    #7

                                    Checksum

                                    00-FF

                                    CS

                           Table 16

                           StartDiagnosticSession Negative Response Message

                                    Byte #

                                    Parameter Name

                                    Hex Value

                                    Mnemonic

                                    #1

                                    Format byte — physical addressing

                                    80

                                    FMT

                                    #2

                                    Target address byte

                                    tt

                                    TGT

                                    #3

                                    Source address byte

                                    EE

                                    SRC

                                    #4

                                    Additional length byte

                                    03

                                    LEN

                                       #5

                                       Negative Response Service Id

                                       7F

                                       NR

                                    #6

                                    StartDiagnosticSession Request Service Id

                                    10

                                    STDS

                                    #7

                                    ResponseCode =

                                    [subFunctionNotSupported (1)

                                    12

                                    RC_SFNS

                                    incorrectMessageLength (2)

                                    13

                                    RC_IML

                                    conditionsNotCorrect (3)

                                    22

                                    RC_CNC

                                    #8

                                    Checksum

                                    00-FF

                                    CS

                  5.1.3   Parameter definition

                        CPR_029

                        The parameter
                              diagnosticSession (DS_)
                            is used by the StartDiagnosticSession service to select the specific behaviour of the server(s). The following diagnostic sessions are specified in this document:

                           Table 17

                           Definition of diagnosticSession Values

                                    Hex

                                    Description

                                    Mnemonic

                                    81

                                       StandardDiagnosticSession

                                    This diagnostic session enables all services specified in Table 1 column 4 “SD”. These services allow reading of data from a server (VU). This diagnostic Session is active after the initialisation has been successfully completed between client (tester) and server (VU). This diagnostic session may be overwritten by other diagnostic sessions specified in this section.

                                       SD

                                    85

                                       ECUProgrammingSession

                                    This diagnostic session enables all services specified in Table 1 column 6 “ECUPS”. These services support the memory programming of a server (VU) This diagnostic session may be overwritten by other diagnostic sessions specified in this section..

                                       ECUPS

                                    87

                                       ECUAdjustmentSession

                                    This diagnostic session enables all services specified in Table 1 column 5 “ECUAS”. These services support the input/output control of a server (VU). This diagnostic session may be overwritten by other diagnostic sessions specified in this section.

                                       ECUAS

                  5.2.   SecurityAccess service

            Writing of calibration data is not possible unless the VU is in CALIBRATION mode. In addition to insertion of a valid workshop card into the VU, it is necessary to enter the appropriate PIN into the VU before access to the CALIBRATION mode is granted.
            When the VU is in CALIBRATION or CONTROL mode, access to the calibration input/output line is also possible.
            The SecurityAccess service provides a means to enter the PIN and to indicate to the tester whether or not the VU is in CALIBRATION mode.
            It is acceptable that the PIN may be entered through alternative methods.
            5.2.1   Message Description

            The SecurityAccess service consists of a SecurityAccess ‘requestSeed’ message, eventually followed by a SecurityAccess ‘sendKey’ message. The SecurityAccess service must be carried out after the StartDiagnosticSession service.

                        CPR_033

                        The tester shall use the SecurityAccess ‘requestSeed’ message to check if the vehicle unit is ready to accept a PIN.

                        CPR_034

                        If the vehicle unit is already in CALIBRATION mode, it shall answer the request by sending a ‘seed’ of 0x0000 using the service SecurityAccess Positive Response.

                        CPR_035

                        If the vehicle unit is ready to accept a PIN for verification by a workshop card, it shall answer the request by sending a ‘seed’ greater than 0x0000 using the service SecurityAccess Positive Response.

                        CPR_036

                        If the vehicle unit is not ready to accept a PIN from the tester, either because the workshop card inserted is not valid, or because no workshop card has been inserted, or because the vehicle unit expects the PIN from another method, it shall answer the request with a Negative Response with a response code set to conditionsNotCorrectOrRequestSequenceError.

                        CPR_037

                        The tester shall then, eventually, use the SecurityAccess ‘sendKey’ message to forward a PIN to the Vehicle Unit. To allow time for the card authentication process to take place, the VU shall use the negative response code requestCorrectlyReceived-ResponsePending to extend the time to respond. However, the maximum time to respond shall not exceed 5 minutes. As soon as the requested service has been completed, the VU shall send a positive response message or negative response message with a response code different from this one. The negative response code requestCorrectlyReceived-ResponsePending may be repeated by the VU until the requested service is completed and the final response message is sent.

                        CPR_038

                        The vehicle unit shall answer to this request using the service SecurityAccess Positive Response only when in CALIBRATION mode.

                        CPR_039

                        In the following cases, the vehicle unit shall answer to this request with a Negative Response with a response code set to:

                                    —

                                    subFunctionNot supported: Invalid format for the subfunction parameter (accessType),

                                    —

                                    conditionsNotCorrectOrRequestSequenceError: Vehicle unit not ready to accept a PIN entry,

                                    —

                                    invalidKey: PIN not valid and number of PIN checks attempts not exceeded,

                                    —

                                    exceededNumberOfAttempts: PIN not valid and number of PIN checks attempts exceeded,

                                    —

                                    generalReject: Correct PIN but mutual authentication with workshop card failed.

                  5.2.2   Message format — SecurityAccess — requestSeed

                        CPR_040

                        The message formats for the SecurityAccess ‘requestSeed’ primitives are detailed in the following tables.

                           Table 18

                           SecurityAccess Request- requestSeed Message

                                    Byte #

                                    Parameter Name

                                    Hex Value

                                    Mnemonic

                                    #1

                                    Format byte — physical addressing

                                    80

                                    FMT

                                    #2

                                    Target address byte

                                    EE

                                    TGT

                                    #3

                                    Source address byte

                                    tt

                                    SRC

                                    #4

                                    Additional length byte

                                    02

                                    LEN

                                       #5

                                       SecurityAccess Request Service Id

                                       27

                                       SA

                                    #6

                                    accessType — requestSeed

                                    7D

                                    AT_RSD

                                    #7

                                    Checksum

                                    00-FF

                                    CS

                           Table 19

                           SecurityAccess — requestSeed Positive Response Message

                                    Byte #

                                    Parameter Name

                                    Hex Value

                                    Mnemonic

                                    #1

                                    Format byte — physical addressing

                                    80

                                    FMT

                                    #2

                                    Target address byte

                                    tt

                                    TGT

                                    #3

                                    Source address byte

                                    EE

                                    SRC

                                    #4

                                    Additional length byte

                                    04

                                    LEN

                                       #5

                                       SecurityAccess Positive Response Service Id

                                       67

                                       SAPR

                                    #6

                                    accessType — requestSeed

                                    7D

                                    AT_RSD

                                    #7

                                    Seed High

                                    00-FF

                                    SEEDH

                                    #8

                                    Seed Low

                                    00-FF

                                    SEEDL

                                    #9

                                    Checksum

                                    00-FF

                                    CS

                           Table 20

                           SecurityAccess Negative Response Message

                                    Byte #

                                    Parameter Name

                                    Hex Value

                                    Mnemonic

                                    #1

                                    Format byte — physical addressing

                                    80

                                    FMT

                                    #2

                                    Target address byte

                                    tt

                                    TGT

                                    #3

                                    Source address byte

                                    EE

                                    SRC

                                    #4

                                    Additional length byte

                                    03

                                    LEN

                                       #5

                                       negativeResponse Service Id

                                       7F

                                       NR

                                    #6

                                    SecurityAccess Request Service Id

                                    27

                                    SA

                                    #7

                                    responseCode =

                                    [conditionsNotCorrectOrRequestSequenceError

                                    22

                                    RC_CNC

                                    incorrectMessageLength]

                                    13

                                    RC_IML

                                    #8

                                    Checksum

                                    00-FF

                                    CS

                  5.2.3   Message format — SecurityAccess — sendKey

                        CPR_041

                        The message formats for the SecurityAccess ‘sendKey’ primitives are detailed in the following tables.

                           Table 21

                           SecurityAccess Request — sendKey Message

                                    Byte #

                                    Parameter Name

                                    Hex Value

                                    Mnemonic

                                    #1

                                    Format byte — physical addressing

                                    80

                                    FMT

                                    #2

                                    Target address byte

                                    EE

                                    TGT

                                    #3

                                    Source address byte

                                    tt

                                    SRC

                                    #4

                                    Additional length byte

                                    m+2

                                    LEN

                                       #5

                                       SecurityAccess Request Service Id

                                       27

                                       SA

                                    #6

                                    accessType — sendKey

                                    7E

                                    AT_SK

                                    #7 to #m + 6

                                    Key #1 (High)

                                    xx

                                    KEY

                                    …

                                    …

                                    Key #m (low, m must be a minimum of 4, and a maximum of 8)

                                    xx

                                    #m + 7

                                    Checksum

                                    00-FF

                                    CS

                           Table 22

                           SecurityAccess — sendKey Positive Response Message

                                    Byte #

                                    Parameter Name

                                    Hex Value

                                    Mnemonic

                                    #1

                                    Format byte — physical addressing

                                    80

                                    FMT

                                    #2

                                    Target address byte

                                    tt

                                    TGT

                                    #3

                                    Source address byte

                                    EE

                                    SRC

                                    #4

                                    Additional length byte

                                    02

                                    LEN

                                       #5

                                       SecurityAccess Positive Response Service Id

                                       67

                                       SAPR

                                    #6

                                    accessType — sendKey

                                    7E

                                    AT_SK

                                    #7

                                    Checksum

                                    00-FF

                                    CS

                           Table 23

                           SecurityAccess Negative Response Message

                                    Byte #

                                    Parameter Name

                                    Hex Value

                                    Mnemonic

                                    #1

                                    Format byte — physical addressing

                                    80

                                    FMT

                                    #2

                                    Target address byte

                                    tt

                                    TGT

                                    #3

                                    Source address byte

                                    EE

                                    SRC

                                    #4

                                    Additional length byte

                                    03

                                    LEN

                                       #5

                                       NegativeResponse Service Id

                                       7F

                                       NR

                                    #6

                                    SecurityAccess Request Service Id

                                    27

                                    SA

                                    #7

                                    ResponseCode =

                                    [generalReject

                                    10

                                    RC_GR

                                    subFunctionNotSupported

                                    12

                                    RC_SFNS

                                    incorrectMessageLength

                                    13

                                    RC_IML

                                    conditionsNotCorrectOrRequestSequenceError

                                    22

                                    RC_CNC

                                    invalidKey

                                    35

                                    RC_IK

                                    exceededNumberOfAttempts

                                    36

                                    RC_ENA

                                    requestCorrectlyReceived-ResponsePending]

                                    78

                                    RC_RCR_RP

                                    #8

                                    Checksum

                                    00-FF

                                    CS

                  6.   DATA TRANSMISSION SERVICES
            The services available are detailed in the following table:

               Table 24

               Data Transmission Services

                        Service name

                        Description

                        ReadDataByIdentifier

                        The client requests the transmission of the current value of a record with access by recordDataIdentifier.

                        WriteDataByIdentifier

                        The client requests to write a record accessed by recordDataIdentifier.

                  6.1.   ReadDataByIdentifier service

            6.1.1   Message description

                        CPR_050

                        The ReadDataByIdentifier service is used by the client to request data record values from a server. The data are identified by a recordDataIdentifier. It is the VU manufacturer's responsibility that the server conditions are met when performing this service.

                  6.1.2   Message format

                        CPR_051

                        The message formats for the ReadDataByIdentifier primitives are detailed in the following tables.

                           Table 25

                           ReadDataByIdentifier Request Message

                                    Byte #

                                    Parameter Name

                                    Hex Value

                                    Mnemonic

                                    #1

                                    Format byte — physical addressing

                                    80

                                    FMT

                                    #2

                                    Target address byte

                                    EE

                                    TGT

                                    #3

                                    Source address byte

                                    tt

                                    SRC

                                    #4

                                    Additional length byte

                                    03

                                    LEN

                                       #5

                                       ReadDataByIdentifier Request Service Id

                                       22

                                       RDBI

                                    #6 to #7

                                    recordDataIdentifier = [a value fromTable 28]

                                    xxxx

                                    RDI_…

                                    #8

                                    Checksum

                                    00-FF

                                    CS

                           Table 26

                           ReadDataByIdentifier Positive Response Message

                                    Byte #

                                    Parameter Name

                                    Hex Value

                                    Mnemonic

                                    #1

                                    Format byte — physical addressing

                                    80

                                    FMT

                                    #2

                                    Target address byte

                                    tt

                                    TGT

                                    #3

                                    Source address byte

                                    EE

                                    SRC

                                    #4

                                    Additional length byte

                                    m+3

                                    LEN

                                       #5

                                       ReadDataByIdentifier Positive Response Service Id

                                       62

                                       RDBIPR

                                    #6 and #7

                                    recordDataIdentifier = [the same value as bytes #6 and #7 Table 25]

                                    xxxx

                                    RDI_...

                                    #8 to #m + 7

                                    dataRecord[] =

                                    [data#1

                                    xx

                                    DREC_DATA1

                                    :

                                    :

                                    :

                                    data#m]

                                    xx

                                    DREC_DATAm

                                    #m + 8

                                    Checksum

                                    00-FF

                                    CS

                           Table 27

                           ReadDataByIdentifier Negative Response Message

                                    Byte #

                                    Parameter Name

                                    Hex Value

                                    Mnemonic

                                    #1

                                    Format byte — physical addressing

                                    80

                                    FMT

                                    #2

                                    Target address byte

                                    tt

                                    TGT

                                    #3

                                    Source address byte

                                    EE

                                    SRC

                                    #4

                                    Additional length byte

                                    03

                                    LEN

                                       #5

                                       NegativeResponse Service Id

                                       7F

                                       NR

                                    #6

                                    ReadDataByIdentifier Request Service Id

                                    22

                                    RDBI

                                    #7

                                    ResponseCode=

                                    [requestOutOfRange

                                    31

                                    RC_ROOR

                                    incorrectMessageLength

                                    13

                                    RC_IML

                                    conditionsNotCorrect]

                                    22

                                    RC_CNC

                                    #8

                                    Checksum

                                    00-FF

                                    CS

                  6.1.3   Parameter Definition

                        CPR_052

                        The parameter
                              recordDataIdentifier (RDI_)
                            in the ReadDataByIdentifier request message identifies a data record.

                        CPR_053

                        recordDataIdentifier values defined by this document are shown in the table below.
                        The recordDataIdentifier table consists of four columns and multiple lines.

                                    —

                                    The 1st column (Hex) includes the ‘Hex Value’ assigned to the recordDataIdentifier specified in the 3rd column.

                                    —

                                    The 2nd column (Data element) specifies the data element of Appendix 1 on which the recordDataIdentifier is based (transcoding is sometimes necessary).

                                    —

                                    The 3rd column (Description) specifies the corresponding recordDataIdentifier name.

                                    —

                                    The 4th column (Mnemonic) specifies the mnemonic of this recordDataIdentifier.

                           Table 28

                           Definition of recordDataIdentifier values

                                    Hex

                                    Data element

                                    recordDataIdentifier Name
                                    (see format in Section 8.2)

                                    Mnemonic

                                    F90B

                                    TimeDate

                                    RDI_TD

                                    F912

                                    HighResolutionTotalVehicleDistance

                                    RDI_HRTVD

                                    F918

                                    Kfactor

                                    RDI_KF

                                    F91C

                                    LfactorTyreCircumference

                                    RDI_LF

                                    F91D

                                    WvehicleCharacteristicFactor

                                    RDI_WVCF

                                    F921

                                    TyreSize

                                    RDI_TS

                                    F922

                                    NextCalibrationDate

                                    RDI_NCD

                                    F92C

                                    SpeedAuthorised

                                    RDI_SA

                                    F97D

                                    RegisteringMemberState

                                    RDI_RMS

                                    F97E

                                    VehicleRegistrationNumber

                                    RDI_ VRN

                                    F190

                                    VIN

                                    RDI_ VIN

                        CPR_054

                        The parameter
                              dataRecord (DREC_)
                            is used by the ReadDataByIdentifier positive response message to provide the data record value identified by the recordDataIdentifier to the client (tester). Data formats are specified in section 8. Additional user optional dataRecords including VU specific input, internal and output data may be implemented, but are not defined in this document.

                  6.2.   WriteDataByIdentifier service

            6.2.1   Message description

                        CPR_056

                        The WriteDataByIdentifier service is used by the client to write data record values to a server. The data are identified by a recordDataIdentifier. It is the VU manufacturer's responsibility that the server conditions are met when performing this service. To update the parameters listed in Table 28 the VU must be in CALIBRATION mode.

                  6.2.2   Message format

                        CPR_057

                        The message formats for the WriteDataByIdentifier primitives are detailed in the following tables.

                           Table 29

                           WriteDataByIdentifier Request Message

                                    Byte #

                                    Parameter Name

                                    Hex Value

                                    Mnemonic

                                    #1

                                    Format byte — physical addressing

                                    80

                                    FMT

                                    #2

                                    Target address byte

                                    EE

                                    TGT

                                    #3

                                    Source address byte

                                    tt

                                    SRC

                                    #4

                                    Additional length byte

                                    m + 3

                                    LEN

                                       #5

                                       WriteDataByIdentifier Request Service Id

                                       2E

                                       WDBI

                                    #6 to #7

                                    recordDataIdentifier = [a value from Table 28]

                                    xxxx

                                    RDI_…

                                    #8 to m + 7

                                    dataRecord[] =

                                    [data#1

                                    xx

                                    DREC_DATA1

                                    :

                                    :

                                    :

                                    data#m]

                                    xx

                                    DREC_DATAm

                                    #m + 8

                                    Checksum

                                    00-FF

                                    CS

                           Table 30

                           WriteDataByIdentifier Positive Response Message

                                    Byte #

                                    Parameter Name

                                    Hex Value

                                    Mnemonic

                                    #1

                                    Format byte — physical addressing

                                    80

                                    FMT

                                    #2

                                    Target address byte

                                    tt

                                    TGT

                                    #3

                                    Source address byte

                                    EE

                                    SRC

                                    #4

                                    Additional length byte

                                    03

                                    LEN

                                       #5

                                       WriteDataByIdentifier Positive Response Service Id

                                       6E

                                       WDBIPR

                                    #6 to #7

                                    recordDataIdentifier = [the same value as bytes #6 and #7 Table 29]

                                    xxxx

                                    RDI_…

                                    #8

                                    Checksum

                                    00-FF

                                    CS

                           Table 31

                           WriteDataByIdentifier Negative Response Message

                                    Byte #

                                    Parameter Name

                                    Hex Value

                                    Mnemonic

                                    #1

                                    Format byte — physical addressing

                                    80

                                    FMT

                                    #2

                                    Target address byte

                                    tt

                                    TGT

                                    #3

                                    Source address byte

                                    EE

                                    SRC

                                    #4

                                    Additional length byte

                                    03

                                    LEN

                                       #5

                                       NegativeResponse Service Id

                                       7F

                                       NR

                                    #6

                                    WriteDataByIdentifier Request Service Id

                                    2E

                                    WDBI

                                    #7

                                    ResponseCode=

                                    [requestOutOfRange

                                    31

                                    RC_ROOR

                                    incorrectMessageLength

                                    13

                                    RC_IML

                                    conditionsNotCorrect]

                                    22

                                    RC_CNC

                                    #8

                                    Checksum

                                    00-FF

                                    CS

                  6.2.3   Parameter definition

            The parameter
                  recordDataIdentifier (RDI_)
                is defined in Table 28.
            The parameter
                  dataRecord (DREC_)
                is used by the WriteDataByIdentifier request message to provide the data record values identified by the recordDataIdentifier to the server (VU). Data formats are specified in section 8.
            7.   CONTROL OF TEST PULSES — INPUT/OUTPUT CONTROL FUNCTIONAL UNIT
            The services available are detailed in the following table:

               Table 32

               Input/Output Control functional unit

                        Service name

                        Description

                        InputOutputControlByIdentifier

                        The client requests the control of an input/output specific to the server.

                  7.1.   InputOutputControlByIdentifier service

            7.1.1   Message description

            There is a connection via the front connector which allows test pulses to be controlled or monitored using a suitable tester.

                        CPR_058

                        This calibration I/O signal line can be configured by K-line command using the InputOutputControlByIdentifier service to select the required input or output function for the line. The available states of the line are:

                                    —

                                    disabled,

                                    —

                                    speedSignalInput, where the calibration I/O signal line is used to input a speed signal (test signal) replacing the motion sensor speed signal, this function is not available in CONTROL mode,

                                    —

                                    realTimeSpeedSignalOutputSensor, where the calibration I/O signal line is used to output the speed signal of the motion sensor,

                                    —

                                    RTCOutput, where the calibration I/O signal line is used to output the UTC clock signal, this function is not available in CONTROL mode.

                        CPR_059

                        The vehicle unit must have entered an adjustment session and must be in CALIBRATION or CONTROL mode to configure the state of the line. When the VU is in CALIBRATION mode, the four states of the line can be selected (disabled, speedSignalInput, realTimeSpeedSignalOutputSensor, RTCOutput). When the VU is in CONTROL mode, only two states of the lines can be selected (disabled, realTimeSpeedOutputSensor). On exit of the adjustment session or of the CALIBRATION or CONTROL mode the vehicle unit must ensure the calibration I/O signal line is returned to the ‘disabled’ (default) state.

                        CPR_060

                        If speed pulses are received at the real time speed signal input line of the VU while the calibration I/O signal line is set to input then the calibration I/O signal line shall be set to output or returned to the disabled state.

                        CPR_061

                        The sequence shall be:

                                    —

                                    Establish communications by StartCommunication Service

                                    —

                                    Enter an adjustment session by StartDiagnosticSession Service and be in CALIBRATION or CONTROL mode of operation (the order of these two operation is not important).

                                    —

                                    Change the state of the output by InputOutputControlByIdentifier Service.

                  7.1.2   Message format

                        CPR_062

                        The message formats for the InputOutputControlByIdentifier primitives are detailed in the following tables.

                           Table 33

                           InputOutputControlByIdentifier Request Message

                                    Byte #

                                    Parameter Name

                                    Hex Value

                                    Mnemonic

                                    #1

                                    Format byte — physical addressing

                                    80

                                    FMT

                                    #2

                                    Target address byte

                                    EE

                                    TGT

                                    #3

                                    Source address byte

                                    tt

                                    SRC

                                    #4

                                    Additional length byte

                                    xx

                                    LEN

                                       #5

                                       InputOutputControlByIdentifier Request Sid

                                       2F

                                       IOCBI

                                    #6 and #7

                                    InputOutputIdentifier = [CalibrationInputOutput]

                                    F960

                                    IOI_CIO

                                    #8 or
                                    #8 to #9

                                    ControlOptionRecord = [

                                    COR_…

                                    inputOutputControlParameter — one value from Table 36

                                    xx

                                    IOCP_…

                                    controlState — one value from Table 37 (see note below)]

                                    xx

                                    CS_…

                                    #9 or #10

                                    Checksum

                                    00-FF

                                    CS

                           Note: The controlState parameter is present only in some cases (see 7.1.3).

                           Table 34

                           InputOutputControlByIdentifier Positive Response Message

                                    Byte #

                                    Parameter Name

                                    Hex Value

                                    Mnemonic

                                    #1

                                    Format byte — physical addressing

                                    80

                                    FMT

                                    #2

                                    Target address byte

                                    tt

                                    TGT

                                    #3

                                    Source address byte

                                    EE

                                    SRC

                                    #4

                                    Additional length byte

                                    xx

                                    LEN

                                       #5

                                       inputOutputControlByIdentifier Positive Response SId

                                       6F

                                       IOCBIPR

                                    #6 and #7

                                    inputOutputIdentifier = [CalibrationInputOutput]

                                    F960

                                    IOI_CIO

                                    #8 or
                                    #8 to #9

                                    controlStatusRecord = [

                                    CSR_

                                    inputOutputControlParameter (same value as byte #8 Table 33)

                                    xx

                                    IOCP_…

                                    controlState (same value as byte #9 Table 33)] (if applicable)

                                    xx

                                    CS_…

                                    #9 or #10

                                    Checksum

                                    00-FF

                                    CS

                           Table 35

                           InputOutputControlByIdentifier Negative Response Message

                                    Byte #

                                    Parameter Name

                                    Hex Value

                                    Mnemonic

                                    #1

                                    Format byte — physical addressing

                                    80

                                    FMT

                                    #2

                                    Target address byte

                                    tt

                                    TGT

                                    #3

                                    Source address byte

                                    EE

                                    SRC

                                    #4

                                    Additional length byte

                                    03

                                    LEN

                                       #5

                                       negativeResponse Service Id

                                       7F

                                       NR

                                    #6

                                    inputOutputControlByIdentifier Request SId

                                    2F

                                    IOCBI

                                    #7

                                    responseCode=[

                                    incorrectMessageLength

                                    13

                                    RC_IML

                                    conditionsNotCorrect

                                    22

                                    RC_CNC

                                    requestOutOfRange

                                    31

                                    RC_ROOR

                                    deviceControlLimitsExceeded]

                                    7A

                                    RC_DCLE

                                    #8

                                    Checksum

                                    00-FF

                                    CS

                  7.1.3   Parameter definition

                        CPR_064

                        The parameter
                              inputOutputControlParameter (IOCP_)
                            is defined in the following table.

                           Table 36

                           Definition of inputOutputControlParameter values

                                    Hex

                                    Description

                                    Mnemonic

                                    00

                                       ReturnControlToECU

                                    This value shall indicate to the server (VU) that the tester does no longer have control about the calibration I/O signal line.

                                    RCTECU

                                    01

                                       ResetToDefault

                                    This value shall indicate to the server (VU) that it is requested to reset the calibration I/O signal line to its default state.

                                    RTD

                                    03

                                       ShortTermAdjustment

                                    This value shall indicate to the server (VU) that it is requested to adjust the calibration I/O signal line to the value included in the controlState parameter.

                                    STA

                        CPR_065

                        The parameter
                              controlState
                            is present only when the inputOutputControlParameter is set to ShortTermAdjustment and is defined in the following table:

                           Table 37

                           Definition of controlState values

                                    Mode

                                    Hex Value

                                    Description

                                    Disable

                                    00

                                    I/O line is disabled (default state)

                                    Enable

                                    01

                                    Enable calibration I/O line as speedSignalInput

                                    Enable

                                    02

                                    Enable calibration I/O line as realTimeSpeedSignalOutputSensor

                                    Enable

                                    03

                                    Enable calibration I/O line as RTCOutput

                  8.   DATARECORDS FORMATS
            This section details:

                        —

                        general rules that shall be applied to ranges of parameters transmitted by the vehicle unit to the tester,

                        —

                        formats that shall be used for data transferred via the Data Transmission Services described in section 6.

                        CPR_067

                        All parameters identified shall be supported by the VU.

                        CPR_068

                        Data transmitted by the VU to the tester in response to a request message shall be of the measured type (i.e. current value of the requested parameter as measured or observed by the VU).

                  8.1.   Transmitted parameter ranges

                        CPR_069

                        Table 38 defines the ranges used to determine the validity of a transmitted parameter.

                        CPR_070

                        The values in the range ‘error indicator’ provide a means for the vehicle unit to immediately indicate that valid parametric data is not currently available due to some type of error in the tachograph.

                        CPR_071

                        The values in the range ‘not available’ provide a means for the vehicle unit to transmit a message which contains a parameter that is not available or not supported in that module. The values in the range ‘not requested’ provide a means for a device to transmit a command message and identify those parameters where no response is expected from the receiving device.

                        CPR_072

                        If a component failure prevents the transmission of valid data for a parameter, the error indicator as described in Table 38 should be used in place of that parameter's data. However, if the measured or calculated data has yielded a value that is valid yet exceeds the defined parameter range, the error indicator should not be used. The data should be transmitted using the appropriate minimum or maximum parameter value.

                           Table 38

                           dataRecords ranges

                                    Range Name

                                    1 byte
                                    (Hex value)

                                    2 bytes
                                    (Hex value)

                                    4 bytes
                                    (Hex Value)

                                    ASCII

                                    Valid signal

                                    00 to FA

                                    0000 to FAFF

                                    00000000 to FAFFFFFF

                                    1 to 254

                                    Parameter specific indicator

                                    FB

                                    FB00 to FBFF

                                    FB000000 to FBFFFFFF

                                    none

                                    Reserved range for future indicator bits

                                    FC to FD

                                    FC00 to FDFF

                                    FC000000 to FDFFFFFF

                                    none

                                    Error indicator

                                    FE

                                    FE00 to FEFF

                                    FE000000 to FEFFFFFF

                                    0

                                    Not available or not requested

                                    FF

                                    FF00 to FFFF

                                    FF000000 to FFFFFFFF

                                    FF

                        CPR_073

                        For parameters coded in ASCII, the ASCII character ‘*’ is reserved as a delimiter.

                  8.2.   dataRecords formats

            Table 39 to Table 42 below detail the formats that shall be used via the ReadDataByIdentifier and WriteDataByIdentifier Services.

                        CPR_074

                        Table 39 provides the length, resolution and operating range for each parameter identified by its recordDataIdentifier:

                           Table 39

                           Format of dataRecords

                                    Parameter Name

                                    Data length (bytes)

                                    Resolution

                                    Operating range

                                    TimeDate

                                    8

                                    See details in Table 40

                                    HighResolutionTotalVehicleDistance

                                    4

                                    5 m/bit gain, 0 m offset

                                    0 to + 21 055 406  km

                                    Kfactor

                                    2

                                    0,001 pulse/m/bit gain, 0 offset

                                    0 to 64,255 pulse/m

                                    LfactorTyreCircumference

                                    2

                                    0,125 10– 3 m/bit gain, 0 offset

                                    0 to 8,031 m

                                    WvehicleCharacteristicFactor

                                    2

                                    0,001 pulse/m/bit gain, 0 offset

                                    0 to 64,255 pulse/m

                                    TyreSize

                                    15

                                    ASCII

                                    ASCII

                                    NextCalibrationDate

                                    3

                                    See details in Table 41

                                    SpeedAuthorised

                                    2

                                    1/256 km/h/bit gain, 0 offset

                                    0 to 250,996 km/h

                                    RegisteringMemberState

                                    3

                                    ASCII

                                    ASCII

                                    VehicleRegistrationNumber

                                    14

                                    See details in Table 42

                                    VIN

                                    17

                                    ASCII

                                    ASCII

                        CPR_075

                        Table 40 details the formats of the different bytes of the TimeDate parameter:

                           Table 40

                           Detailed format of TimeDate (recordDataIdentifier value # F90B)

                                    Byte

                                    Parameter definition

                                    Resolution

                                    Operating range

                                    1

                                    Seconds

                                    0,25 s/bit gain, 0 s offset

                                    0 to 59,75 s

                                    2

                                    Minutes

                                    1 min/bit gain, 0 min offset

                                    0 to 59 min

                                    3

                                    Hours

                                    1 h/bit gain, 0 h offset

                                    0 to 23 h

                                    4

                                    Month

                                    1 month/bit gain, 0 month offset

                                    1 to 12 month

                                    5

                                    Day

                                    0,25 day/bit gain, 0 day offset
                                    (see NOTE below Table 41)

                                    0,25 to 31,75 day

                                    6

                                    Year

                                    1 year/bit gain, + 1985 year offset
                                    (see NOTE below Table 41)

                                    1985 to 2235 year

                                    7

                                    Local Minute Offset

                                    1 min/bit gain, – 125 min offset

                                    – 59 to + 59 min

                                    8

                                    Local Hour Offset

                                    1 h/bit gain, – 125 h offset

                                    – 23 to + 23 h

                        CPR_076

                        Table 41 details the formats of the different bytes of the NextCalibrationDate parameter.

                           Table 41

                           Detailed format of NextCalibrationDate (recordDataIdentifier value # F922)

                                    Byte

                                    Parameter definition

                                    Resolution

                                    Operating range

                                    1

                                    Month

                                    1 month/bit gain, 0 month offset

                                    1 to 12 month

                                    2

                                    Day

                                    0,25 day/bit gain, 0 day offset
                                    (see NOTE below)

                                    0,25 to 31,75 day

                                    3

                                    Year

                                    1 year/bit gain, + 1985 year offset
                                    (see NOTE below)

                                    1985 to 2235 year

                  NOTE concerning the use of the ‘Day’ parameter:

                        1)

                        A value of 0 for the date is null. The values 1, 2, 3, and 4 are used to identify the first day of the month; 5, 6, 7, and 8 identify the second day of the month; etc.

                        2)

                        This parameter does not influence or change the hours parameter above.

                  NOTE concerning the use of byte ‘Year’ parameter:
            A value of 0 for the year identifies the year 1985; a value of 1 identifies 1986; etc.

                        CPR_078

                        Table 42 details the formats of the different bytes of the VehicleRegistrationNumber parameter:

                           Table 42

                           Detailed format of VehicleRegistrationNumber (recordDataIdentifier value # F97E)

                                    Byte

                                    Parameter definition

                                    Resolution

                                    Operating range

                                    1

                                    Code Page (as defined in Appendix 1)

                                    ASCII

                                    01 to 0A

                                    2 - 14

                                    Vehicle Registration Number (as defined in Appendix 1)

                                    ASCII

                                    ASCII

               (1)  – the value inserted in byte #6 of the request message is not supported, i.e. not in Table 17,

               (2)  – the length of the message is wrong,

               (3)  – the criteria for the request StartDiagnosticSession are not met.

            Appendix 9

               TYPE APPROVAL LIST OF MINIMUM REQUIRED TESTS

            TABLE OF CONTENT

                        1.

                     INTRODUCTION
                     309

                        2.

                     VEHICLE UNIT FUNCTIONAL TESTS
                     311

                        3.

                     MOTION SENSOR FUNCTIONAL TESTS
                     315

                        4.

                     TACHOGRAPH CARDS FUNCTIONAL TESTS
                     318

                        5.

                     EXTERNAL GNSS FACILITY TESTS
                     328

                        6.

                     REMOTE COMMUNICATION FACILITY TESTS
                     331

                        7.

                     PAPER FUNCTIONAL TESTS
                     333

                        8.

                     INTEROPERABILITY TESTS
                     335
                  1.   INTRODUCTION
            1.1.   Type approval

            The EC type approval for a recording equipment (or component) or a tachograph card is based on:

                        —

                        a security certification, based on Common Criteria specifications, against a security target fully compliant with Appendix 10 to this Annex (To be completed/modified),

                        —

                        a functional certification performed by a Member State authority certifying that the item tested fulfils the requirements of this Annex in terms of functions performed, measurement accuracy and environmental characteristics,

                        —

                        an interoperability certification performed by the competent body certifying that the recording equipment (or tachograph card) is fully interoperable with the necessary tachograph card (or recording equipment) models (see Chapter 8 of this Annex).

                  This Appendix specifies which tests, as a minimum, must be performed by a Member State authority during the functional tests, and which tests, as a minimum, must be performed by the competent body during the interoperability tests. Procedures to follow to carry out the tests or the type of tests are not specified further.
            The security certification aspects are not covered by this Appendix. If some tests requested for type approval are performed during the security evaluation and certification process, then these tests do not need to be performed again. In this case, only the results of these security tests may be inspected. For information, the requirements expected to be tested (or closely related to tests expected to be performed) during the security certification, are marked with a ‘*’ in this Appendix.
            The numbered requirements refer to the Annex corpus, while the other requirements refer to the other appendixes (e.g. PIC_001 refers to requirement PIC_001 of Appendix 3 Pictograms).
            This Appendix considers separately the type approval of the motion sensor, of the vehicle unit, and of the external GNSS facility as components of the recording equipment. Each component will get its own type approval certificate in which the other compatible components will be indicated. The functional test of the motion sensor (or external GNSS facility) is done together with the vehicle unit and vice versa.
            Interoperability between every model of motion sensor (resp. external GNSS facility) and every model of vehicle unit is not required. In that case the type approval for a motion sensor (resp. external GNSS facility) can be granted only in combination with the type approval of the relevant vehicle unit and vice versa.
            1.2.   References

            The following references are used in this Appendix:

                  IEC 60068-2-1:
                Environmental testing — Part 2-1: Tests — Test A: Cold

                  IEC 60068-2-2:
                Basic environmental testing procedures; part 2: tests; tests B: dry heat (sinusoidal).

                  IEC 60068-2-6:
                Environmental testing — Part 2: Tests — Test Fc: Vibration

                  IEC 60068-2-14:
                Environmental testing; Part 2-14: Tests; Test N: Change of temperature

                  IEC 60068-2-27:
                Environmental testing. Part 2: Tests. Test Ea and guidance: Shock

                  IEC 60068-2-30:
                Environmental testing — Part 2-30: Tests — Test Db: Damp heat, cyclic (12 h + 12 h cycle)

                  IEC 60068-2-64:
                Environmental testing — Part 2-64: Tests — Test Fh: Vibration, broadband random and guidance

                  IEC 60068-2-78
                Environmental testing — Part 2-78: Tests — Test Cab: Damp heat, steady state

                  ISO 16750-3 —
                Mechanical loads (2012-12)

                  ISO 16750-4 —
                Climatic loads(2010-04).

                  ISO 20653:
                Road vehicles — Degree of protection (IP code) — Protection of electrical equipment against foreign objects, water and access

                  ISO 10605:2008 + Technical Corrigendum:2010 + AMD1:2014
                Road vehicles — Test methods for electrical disturbances from electrostatic discharge

                  ISO 7637-1:2002 + AMD1: 2008
                Road vehicles — Electrical disturbances from conduction and coupling — Part 1: Definitions and general considerations.

                  ISO 7637-2
                Road vehicles — Electrical disturbances from conduction and coupling — Part 2: Electrical transient conduction along supply lines only.

                  ISO 7637-3
                Road vehicles — Electrical disturbances from conduction and coupling — Part 3: Electrical transient transmission by capacitive and inductive coupling via lines other than supply lines.

                  ISO/IEC 7816-1
                Identification cards — Integrated circuit(s) cards with contacts — Part 1: Physical characteristics..

                  ISO/IEC 7816-2
                Information technology — Identification cards — Integrated circuit(s) cards with contacts — Part 2: Dimensions and location of the contacts.

                  ISO/IEC 7816-3
                Information technology — Identification cards — Integrated circuit(s) cards with contacts — Part 3: Electronic signals and transmission protocol.

                  ISO/IEC 10373-1:2006 + AMD1:2012
                Identification cards — Test methods — Part 1: General characteristics

                  ISO/IEC 10373-3:2010 + Technical Corrigendum:2013
                Identification cards — Test methods — Part 3: Integrated circuit cards with contacts and related interface devices

                  ISO 16844-3:2004, Cor 1:2006
                Road vehicles — Tachograph systems — Part 3: Motion sensor interface (with vehicle units).

                  ISO 16844-4
                Road vehicles — Tachograph systems — Part 4: CAN interface

                  ISO 16844-6
                Road vehicles — Tachograph systems — Part 6: Diagnostics

                  ISO 16844-7
                Road vehicles — Tachograph systems — Part 7: Parameters

                  ISO 534
                Paper and board — Determination of thickness, density and specific volume

                  UN ECE R10
                Uniform provisions concerning the approval of vehicles with regard to electromagnetic compatibility (United Nation Economic Commission for Europe)
            2.   VEHICLE UNIT FUNCTIONAL TESTS

                        No

                        Test

                        Description

                        Related requirements

                        1

                           Administrative examination

                        1.1

                        Documentation

                        Correctness of documentation

                        1.2

                        Manufacturer test results

                        Results of manufacturer test performed during integration.
                        Paper demonstrations.

                        88, 89,91

                        2

                           Visual inspection

                        2.1

                        Compliance with documentation

                        2.2

                        Identification/markings

                        224 to 226

                        2.3

                        Materials

                        219 to 223

                        2.4

                        Sealing

                        398, 401 to 405

                        2.5

                        External interfaces

                        3

                           Functional tests

                        3.1

                        Functions provided

                        03, 04, 05, 07, 382,

                        3.2

                        Modes of operation

                        09 to 11*, 132, 133

                        3.3

                        Functions and data access rights

                        12* 13*,, 382, 383, 386 to 389

                        3.4

                        Monitoring cards insertion and withdrawal

                        15, 16, 17, 18, 19*, 20*, 132

                        3.5

                        Speed and distance measurement

                        21 to 31

                        3.6

                        Time measurement (test performed at 20°C)

                        38 to 43

                        3.7

                        Monitoring driver activities

                        44 to 53, 132

                        3.8

                        Monitoring driving status

                        54, 55, 132

                        3.9

                        Manual entries

                        56 to 62

                        3.10

                        Company locks management

                        63 to 68

                        3.11

                        Monitoring control activities

                        69, 70

                        3.12

                        Detection of events and/or faults

                        71 to 88 132

                        3.13

                        Equipment identification data

                        93*, 94*, 97, 100

                        3.14

                        Driver card insertion and withdrawal data

                        102* to 104*

                        3.15

                        Driver activity data

                        105* to 107*

                        3.16

                        Places and positions data

                        108* to 112*

                        3.17

                        Odometer data

                        113* to 115*

                        3.18

                        Detailed speed data

                        116*

                        3.19

                        Events data

                        117*

                        3.20

                        Faults data

                        118*

                        3.21

                        Calibration data

                        119* to 121*

                        3.22

                        Time adjustment data

                        124*, 125*

                        3.23

                        Control activity data

                        126*, 127*

                        3.24

                        Company locks data

                        128*

                        3.25

                        Download activity data

                        129*

                        3.26

                        Specific conditions data

                        130*, 131*

                        3.27

                        Recording and storing on tachographs cards

                        134, 135, 136*, 137*, 139*, 140, 141
                        142, 143, 144*, 145*, 146*, 147, 148

                        3.28

                        Displaying

                        90, 132,
                        149 to 166,
                        PIC_001, DIS_001

                        3.29

                        Printing

                        90, 132, 167 to 179, PIC_001, PRT_001 to PRT_014

                        3.30

                        Warning

                        132, 180 to 189,
                        PIC_001

                        3.31

                        Data downloading to external media

                        90, 132, 190 to 194

                        3.32

                        Remote communication for targeted roadside checks

                        195 to 197

                        3.33

                        Output data to additional external devices

                        198, 199

                        3.34

                        Calibration

                        202 to 206*, 383, 384, 386 to 391

                        3.35

                        Roadside calibration checking

                        207 to 209

                        3.36

                        Time adjustment

                        210 to 212*

                        3.37

                        Non-interference of additional functions

                        06, 425

                        3.38

                        Motion sensor interface

                        02, 122

                        3.39

                        External GNSS facility

                        03, 123

                        3.40

                        Verify that the VU detects, records and stores the event(s) and/or fault(s) defined by the VU manufacturer when a paired motion sensor reacts to magnetic fields disturbing vehicle motion detection.

                        217

                        3.41

                        Cypher suite and standardized domain parameters

                        CSM_48, CSM_50

                        4

                           Environmental tests

                        4.1

                        Temperature

                        Verify functionality through:

                                    Test according to ISO 16750-4, Chapter 5.1.1.2: Low temperature operation test (72 h @ – 20 °C)
                                    This test refers to IEC 60068-2-1: Environmental testing — Part 2-1: Tests — Test A: Cold

                                    Test according to ISO 16750-4: Chapter 5.1.2.2: High temperature operation test (72 h at 70 °C)
                                    This test refers to IEC 60068-2-2: Basic environmental testing procedures; part 2: tests; tests B: dry heat

                                    Test according to ISO 16750-4: Chapter 5.3.2: Rapid change of temperature with specified transition duration (– 20 °C/70 °C, 20 cycles, dwell time 2h at each temperature)
                                    A reduced set of tests (among those defined in section 3 of this table) can be carried out at the lower temperature, the higher temperature and during the temperature cycles

                        213

                        4.2

                        Humidity

                        Verify that the vehicle unit can withstand a cyclic damp (heat test) through IEC IEC 60068-2-30, test Db, six 24 hours cycles, each temperature varying from + 25°C to + 55°C and a relative humidity of 97 % at + 25°C and equal to 93 % at + 55°C

                        214

                        4.3

                        Mechanical

                                    1.

                                    Sinusoidal vibrations.
                                    verify that the vehicle unit can withstand sinusoidal vibrations with the following characteristics:

                                                constant displacement between 5 and 11 Hz: 10 mm peak

                                                constant acceleration between 11 and 300 Hz: 5g

                                          This requirement is verified through IEC 60068-2-6, test Fc, with a minimum test duration of 3 × 12 hours (12 hours per axis)
                                    ISO 16750-3 does not require a sinusoidal vibration test for devices located in the decoupled vehicle cab.

                                    2.

                                    Random vibrations:
                                    Test according to ISO 16750-3: Chapter 4.1.2.8: Test VIII: Commercial vehicle, decoupled vehicle cab
                                    Random vibration test, 10…2 000  Hz, RMS vertical 21,3 m/s2, RMS longitudinal 11,8 m/s2, RMS lateral 13,1 m/s2, 3 axes, 32 h per axis, including temperature cycle – 20…70°C.
                                    This test refers to IEC 60068-2-64: Environmental testing — Part 2-64: Tests — Test Fh: Vibration, broadband random and guidance

                                    3.

                                    Shocks:
                                    mechanical shock with 3g half sinus according ISO 16750.

                              The tests described above are performed on different samples of the equipment type being tested.

                        219

                        4.4

                        Protection against water and foreign bodies

                        Test according to ISO 20653: Road vehicles — Degree of protection (IP code) — Protection of electrical equipment against foreign objects, water and access (No change in parameters); Minimum value IP 40

                        220, 221

                        4.5

                        Over-voltage protection

                        Verify that the vehicle unit can withstand a power supply of:

                        216

                        24 V versions:

                        34 V at + 40°C 1 hour

                        12V versions:

                        17V at +40°C 1 hour

                        (ISO 16750-2)

                        4.6

                        Reverse polarity protection

                        Verify that the vehicle unit can withstand an inversion of its power supply
                        (ISO 16750-2)

                        216

                        4.7

                        Short-circuit protection

                        Verify that input output signals are protected against short circuits to power supply and ground
                        (ISO 16750-2)

                        216

                        5

                           EMC tests

                        5.1

                        Radiated emissions and susceptibility

                        Compliance with Regulation ECE R10

                        218

                        5.2

                        Electrostatic discharge

                        Compliance with ISO 10605:2008 + Technical Corrigendum:2010 + AMD1:2014: +/– 4kV for contact and +/– 8kV for air discharge

                        218

                        5.3

                        Conducted transient susceptibility on power supply

                        For 24V versions: compliance with ISO 7637-2 + ECE Regulation No. 10 Rev. 3:

                                    pulse 1a: Vs = – 450 V Ri = 50 ohms

                                    pulse 2a: Vs = + 37 V Ri = 2 ohms

                                    pulse 2b: Vs = + 20 V Ri = 0,05 ohms

                                    pulse 3a: Vs = – 150 V Ri = 50 ohms

                                    pulse 3b: Vs = + 150 V Ri=50 ohms

                                    pulse 4: Vs = – 16 V Va = – 12 V t6 = 100ms

                                    pulse 5: Vs = + 120 V Ri = 2,2 ohms td = 250ms

                              For 12V versions: compliance with ISO 7637-1 + ECE Regulation No. 10 Rev. 3:

                                    pulse 1: Vs = – 75 V Ri = 10 ohms

                                    pulse 2a: Vs = + 37 V Ri = 2 ohms

                                    pulse 2b: Vs = + 10 V Ri = 0,05 ohms

                                    pulse 3a: Vs = – 112 V Ri = 50 ohms

                                    pulse 3b: Vs = + 75 V Ri = 50 ohms

                                    pulse 4: Vs = – 6 V Va = – 5 V t6 = 15 ms

                                    pulse 5: Vs = + 65 V Ri = 3 ohms td = 100 ms

                                    Pulse 5 shall be tested only for vehicle units designed to be installed in vehicles for which no external common protection against load dump is implemented

                              For load dump proposal, refer to ISO 16750-2, 4th edition, chapter 4.6.4.

                        218

                  3.   MOTION SENSOR FUNCTIONAL TESTS

                        No

                        Test

                        Description

                        Related requirements

                        1.

                           Administrative examination

                        1.1

                        Documentation

                        Correctness of documentation

                        2.

                           Visual inspection

                        2.1.

                        Compliance with documentation

                        2.2.

                        Identification/markings

                        225, 226,

                        2.3

                        Materials

                        219 to 223

                        2.4.

                        Sealing

                        398, 401 to 405

                        3.

                           Functional tests

                        3.1

                        Sensor identification data

                        95 to 97*

                        3.2

                        Motion sensor — vehicle unit pairing

                        122*, 204

                        3.3

                        Motion detection
                        Motion measurement accuracy

                        30 to 35

                        3.4

                        Vehicle unit interface

                        02

                        3.5

                        Check that the motion sensor is immune to constant magnetic field. Alternatively, verify that the motion sensor reacts to constant magnetic fields disturbing vehicle motion detection so that a connected VU can detect, record and store sensor faults

                        217

                        4.

                           Environmental tests

                        4.1

                        Operating temperature

                        Verify functionality (as defined in test No 3.3) in temperature range [– 40°C; + 135°C] through:

                                    IEC 60068-2-1 test Ad, with a test duration of 96 hours at the lowest temperature Tomin,

                                    IEC 60068-2-2 test Bd, with a test duration of 96 hours at the highest temperature Tomax

                                    Test according to ISO 16750-4: Chapter 5.1.1.2: Low temperature operation test (24 h @ – 40 °C)
                                    This test refers to IEC 60068-2-1: Environmental testing — Part 2-1: Tests — Test A: Cold IEC 68-2-2 test Bd, with a test duration of 96 hours at the lowest temperature of – 40°C.

                                    Test according to ISO 16750-4: Chapter 5.1.2.2: High temperature operation test (96 h @ 135 °C)
                                    This test refers to IEC 60068-2-2: Basic environmental testing procedures; part 2: tests; tests B: dry heat

                        213

                        4.2

                        Temperature cycles

                        Test according to ISO 16750-4: Chapter 5.3.2: Rapid change of temperature with specified transition duration (– 40°C/135 °C, 20 cycles, dwell time 30 min at each temperature)
                        IEC 60068-2-14: Environmental testing; Part 2-14: Tests; Test N: Change of temperature

                        213

                        4.3

                        Humidity cycles

                        Verify functionality (as defined in test No. 3.3) through IEC 60068-2-30, test Db, six 24 hours cycles, each temperature varying from + 25°C to + 55°C and a relative humidity of 97 % at + 25°C and equal to 93 % at + 55°C

                        214

                        4.4

                        Vibration

                        ISO 16750-3: Chapter 4.1.2.6: Test VI: Commercial vehicle, engine, gearbox
                        Mixed mode vibration test including

                                    a)

                                    Sinusoidal vibration test, 20…520 Hz, 11,4 … 120 m/s2, <= 0,5 oct/min

                                    b)

                                    Random vibration test, 10…2 000  Hz, RMS 177 m/s2

                              94 h per axis, including temperature cycle – 20…70°C)
                        This test refers to IEC 60068-2-80: Environmental testing — Part 2-80: Tests — Test Fi: Vibration — Mixed mode

                        219

                        4.5

                        Mechanical shock

                        ISO 16750-3: Chapter 4.2.3: Test VI: Test for devices in or on the gearbox
                        half-sinusoidal shock, acceleration to be agreed in the range 3 000 …15 000  m/s2, pulse duration to be agreed, however < 1 ms, number of shocks: to be agreed
                        This test refers to IEC 60068-2-27: Environmental testing. Part 2: Tests. Test Ea and guidance: Shock

                        219

                        4.6

                        Protection against water and foreign bodies

                        Test according to ISO 20653: Road vehicles — Degree of protection (IP code) — Protection of electrical equipment against foreign objects, water and access
                        (Target value IP 64)

                        220, 221

                        4.7

                        Reverse polarity protection

                        Verify that the motion sensor can withstand an inversion of its power supply

                        216

                        4.8

                        Short circuit protection

                        Verify that input output signals are protected against short circuits to power supply and ground

                        216

                        5.

                           EMC

                        5.1

                        radiated emissions and susceptibility

                        Verify compliance with Regulation ECE R10

                        218

                        5.2

                        Electrostatic discharge

                        Compliance with ISO 10605:2008 + Technical Corrigendum:2010 + AMD1:2014: +/– 4kV for contact and +/– 8kV for air discharge

                        218

                        5.3

                        Conducted transient susceptibility on data lines)

                        For 24V versions: compliance with ISO 7637-2 + ECE Regulation No. 10 Rev. 3:

                                    pulse 1a: Vs = – 450 V Ri = 50 ohms

                                    pulse 2a: Vs = + 37 V Ri = 2 ohms

                                    pulse 2b: Vs = + 20 V Ri = 0,05 ohms

                                    pulse 3a: Vs = – 150 V Ri = 50 ohms

                                    pulse 3b: Vs = + 150 V Ri = 50 ohms

                                    pulse 4: Vs= – 16 V Va = – 12 V t6 = 100ms

                                    pulse 5: Vs = + 120 V Ri = 2,2 ohms td = 250ms

                              For 12V versions: compliance with ISO 7637-1 + ECE Regulation No. 10 Rev. 3:

                                    pulse 1: Vs = – 75 V Ri = 10 ohms

                                    pulse 2a: Vs = + 37 V Ri = 2 ohms

                                    pulse 2b: Vs = + 10 V Ri = 0,05 ohms

                                    pulse 3a: Vs = – 112 V Ri = 50 ohms

                                    pulse 3b: Vs = + 75 V Ri = 50 ohms

                                    pulse 4: Vs= – 6 V Va=-5 V t6 = 15 ms

                                    pulse 5: Vs = + 65 V Ri = 3 ohms td = 100 ms

                              Pulse 5 shall be tested only for vehicle units designed to be installed in vehicles for which no external common protection against load dump is implemented
                        For load dump proposal, refer to ISO 16750-2, 4th edition, chapter 4.6.4

                        218

                  4.   TACHOGRAPH CARDS FUNCTIONAL TESTS
            Tests according to this Section 4,

                        no. 5 ‘Protocol tests’,

                        no. 6 ‘Card structure’ and

                        no. 7 ‘Functional tests’

                  can be performed by the evaluator or certifier during the Common Criteria (CC) security certification process for the chip module.
            Tests number 2.3 and 4.2 are the same. These are the mechanical tests of the combination card body and chip module. If one of these components (card body, chip module) is changed, then these tests are necessary.

                        No

                        Test

                        Description

                        Related requirements

                        1.

                           Administrative examination

                        1.1

                        Documentation

                        Correctness of documentation

                        2

                           Card Body

                        2.1

                        Printed Design

                        Make sure that all features for protection and visible data are correctly printed on the card and compliant.
                        [Designator]
                        Annex 1C, chapter 4.1 ‘Visible data’, 227)
                        The front page shall contain:
                        the words ‘Driver card’ or ‘Control card’ or ‘Workshop card’ or ‘Company card’ printed in capital letters in the official language or languages of the Member State issuing the card, according to the type of the card.
                        [Member State name]
                        Annex 1C, chapter 4.1 ‘Visible data’, 228)
                        The front page shall contain:
                        the name of the Member State issuing the card (optional).
                        [Sign]
                        Annex 1C, chapter 4.1 ‘Visible data’, 229)
                        The front page shall contain:
                        the distinguishing sign of the Member State issuing the card, printed in negative in a blue rectangle and encircled by 12 yellow stars.
                        [Enumeration]
                        Annex 1C, chapter 4.1 ‘Visible data’, 232)
                        The reverse page shall contain:
                        an explanation of the numbered items which appear on the front page of the card.
                        [Colour]
                        Annex 1C, chapter 4.1 ‘Visible data’, 234)
                        Tachograph cards shall be printed with the following background predominant colours:

                                    —

                                    driver card: white,

                                    —

                                    workshop card: red,

                                    —

                                    control card: blue,

                                    —

                                    company card: yellow.

                              [Security]
                        Annex 1C, chapter 4.1 ‘Visible data’, 235)
                        Tachograph cards shall bear at least the following features for protection of the card body against counterfeiting and tampering:

                                    —

                                    a security design background with fine guilloche patterns and rainbow printing,

                                    —

                                    at least one two-coloured microprint line.

                              [Markings]
                        Annex 1C, chapter 4.1 ‘Visible data’, 236)
                        Member States may add colours or markings, such as national symbols and security features.
                        [Approval mark]
                        Tachograph cards shall contain an approval mark.
                        The approval mark shall be made up of:

                                    —

                                    a rectangle, within which shall be placed the letter ‘e’ followed by a distinguishing number or letter for the country which has issued the approval,

                                    —

                                    an approval number corresponding to the number of the approval certificate for a tachograph card, placed at any point within the immediate proximity of this rectangle.

                        227 to 229, 232, 234 to 236

                        2.2

                        Mechanical Tests

                        [Card size]
                        Tachograph cards must conform to standard
                        ISO/IEC 7810, Identification cards — Physical characteristics,
                        [5] Dimension of card,
                        [5.1] Card size,
                        [5.1.1] Card dimensions and tolererances,
                        card type ID-1 Unused card
                        [Card edges]
                        Tachograph cards must conform to standard
                        ISO/IEC 7810, Identification cards — Physical characteristics,
                        [5] Dimension of card,
                        [5.1] Card size,
                        [5.1.2] Card edges
                        [Card construction]
                        Tachograph cards must conform to standard
                        ISO/IEC 7810, Identification cards — Physical characteristics,
                        [6] Card construction
                        [Card materials]
                        Tachograph cards must conform to standard
                        ISO/IEC 7810, Identification cards — Physical characteristics,
                        [7] Card materials
                        [Bending stiffness]
                        Tachograph cards must conform to standard
                        ISO/IEC 7810, Identification cards — Physical characteristics,
                        [8] Card characteristics,
                        [8.1] Bending stiffness
                        [Toxicity]
                        Tachograph cards must conform to standard
                        ISO/IEC 7810, Identification cards — Physical characteristics,
                        [8] Card characteristics,
                        [8.3] Toxicity
                        [Resistance to chemicals]
                        Tachograph cards must conform to standard
                        ISO/IEC 7810, Identification cards — Physical characteristics,
                        [8] Card characteristics,
                        [8.4] Resistance to chemicals
                        [Card stability]
                        Tachograph cards must conform to standard
                        ISO/IEC 7810, Identification cards — Physical characteristics,
                        [8] Card characteristics,
                        [8.5] Card dimensional stability and warpage with temperature and humidity
                        [Light]
                        Tachograph cards must conform to standard
                        ISO/IEC 7810, Identification cards — Physical characteristics,
                        [8] Card characteristics,
                        [8.6] Light
                        [Durability]
                        Annex 1C, chapter 4.4 ‘Environmental and electrical specifications’, 241)
                        Tachograph cards shall be capable of operating correctly for a five-year period if used within the environmental and electrical specifications.
                        [Peel strength]
                        Tachograph cards must conform to standard
                        ISO/IEC 7810, Identification cards — Physical characteristics,
                        [8] Card characteristics,
                        [8.8] Peel strength
                        [Adhesion or blocking]
                        Tachograph cards must conform to standard
                        ISO/IEC 7810, Identification cards — Physical characteristics,
                        [8] Card characteristics,
                        [8.9] Adhesion or blocking
                        [Warpage]
                        Tachograph cards must conform to standard
                        ISO/IEC 7810, Identification cards — Physical characteristics,
                        [8] Card characteristics,
                        [8.11] Overall card warpage
                        [Resistance to heat]
                        Tachograph cards must conform to standard
                        ISO/IEC 7810, Identification cards — Physical characteristics,
                        [8] Card characteristics,
                        [8.12] Resistance to heat
                        [Surface distortions]
                        Tachograph cards must conform to standard
                        ISO/IEC 7810, Identification cards — Physical characteristics,
                        [8] Card characteristics,
                        [8.13] Surface distortions
                        [Contamination]
                        Tachograph cards must conform to standard
                        ISO/IEC 7810, Identification cards — Physical characteristics,
                        [8] Card characteristics,
                        [8.14] Contamination and interaction of card components

                        240, 243
                        ISO/IEC 7810

                        2.3

                        Mechanical tests with chip module embedded

                        [Bending]
                        Tachograph cards must conform to standard
                        ISO/IEC 7810:2003/Amd. 1:2009, Identification cards — Physical characteristics, Amendment 1: Criteria for cards containing integrated circuits
                        [9.2] Dynamic bending stress
                        Total number of bending cycles: 4 000 .
                        [Torsion]
                        Tachograph cards must conform to standard
                        ISO/IEC 7810:2003/Amd. 1:2009, Identification cards — Physical characteristics, Amendment 1: Criteria for cards containing integrated circuits
                        [9.3] Dynamic torsional stress
                        Total number of torsion cycles: 4 000 .

                        ISO/IEC 7810

                        3

                           Module

                        3.1

                        Module

                        Module is the chip encapsulation and the contact plate.
                        [Surface profile]
                        Tachograph cards must conform to standard
                        ISO/IEC 7816-1:2011, Identification cards — Integrated circuit cards — Part 1: Cards with contacts — Physical characteristics
                        [4.2] Surface profile of contacts
                        [Mechanical strength]
                        Tachograph cards must conform to standard
                        ISO/IEC 7816-1:2011, Identification cards — Integrated circuit cards — Part 1: Cards with contacts — Physical characteristics
                        [4.3] Mechanical strength (of a card and contacts)
                        [Electrical resistance]
                        Tachograph cards must conform to standard
                        ISO/IEC 7816-1:2011, Identification cards — Integrated circuit cards — Part 1: Cards with contacts — Physical characteristics
                        [4.4] Electrical resistance (of contacts)
                        [Dimension]
                        Tachograph cards must conform to standard
                        ISO/IEC 7816-2:2007, Identification cards — Integrated circuit cards — Part 2: Cards with contacts — Dimension and location of the contacts
                        [3] Dimension of the contacts
                        [Location]
                        Tachograph cards must conform to standard
                        ISO/IEC 7816-2:2007, Identification cards — Integrated circuit cards — Part 2: Cards with contacts — Dimension and location of the contacts
                        [4] Number and location of the contacts
                        In case of modules with six contacts, contact ‘C4’ and ‘C8’ are not part of this test requirement.

                        ISO/IEC 7816

                        4

                           Chip

                        4.1

                        Chip

                        [Operating temperature]
                        The Tachograph card chip shall operate in an ambient temperature range between – 25 °C and + 85 °C.
                        [Temperature and humidity]
                        Annex 1C, chapter 4.4 ‘Environmental and electrical specifications’, 241)
                        Tachograph cards shall be capable of operating correctly in all the climatic conditions normally encountered in Community territory and at least in the temperature range – 25°C to + 70°C with occasional peaks of up to + 85°C, ‘occasional’ meaning not more than 4 hours each time and not over 100 times during the life time of the card.
                        The Tachograph cards are exposed in consecutive steps to the following temperatures and humidities for the given time. After each step the Tachograph cards are tested for electrical functionality.

                                    1.

                                    Temperature of – 20 °C for 2 h.

                                    2.

                                    Temperature of +/– 0 °C for 2 h.

                                    3.

                                    Temperature of + 20 °C, 50 % RH, for 2 h.

                                    4.

                                    Temperature of + 50 °C, 50 % RH, for 2 h.

                                    5.

                                    Temperature of + 70 °C, 50 % RH, for 2 h.
                                    The temperature is increased intermittently to + 85 °C, 50 % RH, for 60 min.

                                    6.

                                    Temperature of + 70 °C, 85 % RH, for 2 h.
                                    The temperature is increased intermittently to + 85 °C, 85 % RH, for 30 min.

                              [Humidity]
                        Annex 1C, chapter 4.4 ‘Environmental and electrical specifications’, 242)
                        Tachograph cards shall be capable of operating correctly in the humidity range 10 % to 90 %.
                        [Electromagnetic compatibility — EMC]
                        Annex 1C, chapter 4.4 ‘Environmental and electrical specifications’ 244)
                        During operation, Tachograph cards shall conform to ECE R10 related to electromagnetic compatibility.
                        [Static electricity]
                        Annex 1C, chapter 4.4 ‘Environmental and electrical specifications’, 244)
                        During operation, Tachograph cards shall be protected against electrostatic discharges.
                        Tachograph cards must conform to standard
                        ISO/IEC 7810:2003/Amd. 1:2009, Identification cards — Physical characteristics, Amendment 1: Criteria for cards containing integrated circuits
                        [9.4] Static electricity
                        [9.4.1] Contact IC cards
                        Test voltage: 4 000  V.
                        [X-rays]
                        Tachograph cards must conform to standard
                        ISO/IEC 7810:2003/Amd. 1:2009, Identification cards — Physical characteristics, Amendment 1: Criteria for cards containing integrated circuits
                        [9.1] X-rays
                        [Ultraviolet light]
                        ISO/IEC 10373-1:2006, Identification cards — Test methods — Part 1: General characteristics
                        [5.11] Ultraviolet light
                        [3-wheel]
                        Tachograph cards must conform to standard
                        ISO/IEC 10373-1:2006/Amd. 1:2012, Identification cards — Test methods — Part 1: General characteristics, Amendment 1
                        [5.22] ICC — Mechanical strength: 3 wheel test for ICCs with contacts
                        [Wrapping]
                        Tachograph cards must conform to standard
                        MasterCard CQM V2.03:2013
                        [11.1.3] R-L3-14-8: Wrapping Test Robustness
                        [13.2.1.32] TM-422: Mechanical Reliability: Wrapping Test

                        241 to 244
                        ECE R10
                        ISO/IEC 7810
                        ISO/IEC 10373

                        4.2

                        Mechanical tests chip module embedded in the card body-> same as 2.3

                        [Bending]
                        Tachograph cards must conform to standard
                        ISO/IEC 7810:2003/Amd. 1:2009, Identification cards — Physical characteristics, Amendment 1: Criteria for cards containing integrated circuits
                        [9.2] Dynamic bending stress
                        Total number of bending cycles: 4 000 .
                        [Torsion]
                        Tachograph cards must conform to standard
                        ISO/IEC 7810:2003/Amd. 1:2009, Identification cards — Physical characteristics, Amendment 1: Criteria for cards containing integrated circuits
                        [9.3] Dynamic torsional stress
                        Total number of torsion cycles: 4 000 .

                        ISO/IEC 7810

                        5

                           Protocol tests

                        5.1

                        ATR

                        Check that the ATR is compliant

                        ISO/IEC 7816-3
                        TCS_14, TCS_17, TCS_18

                        5.2

                        T=0

                        Check that T=0 protocol is compliant

                        ISO/IEC 7816-3
                        TCS_11, TCS_12, TCS_13, TCS_15

                        5.3

                        PTS

                        Check that the PTS command is compliant by setting T=1 from T=0.

                        ISO/IEC 7816-3
                        TCS_12, TCS_19, TCS_20, TCS_21

                        5.4

                        T=1

                        Check that T=1 protocol is compliant

                        ISO/IEC 7816-3
                        TCS_11, TCS_13, TCS_16

                        6

                           Card structure

                        6.1

                        Test that the file structure of the card is compliant by checking the presence of the mandatory files in the card and their access conditions

                        TCS_22 to TCS_28
                        TCS_140 to TCS_179

                        7

                           Functional tests

                        7.1

                        Normal processing

                        Test at least once each allowed usage of each command (ex: test the UPDATE BINARY command with CLA = ‘00’, CLA = ‘0C’ and with different P1,P2 and Lc parameters)
                        Check that the operations have actually been performed in the card (ex: by reading the file the command has been performed on)

                        TCS_29 to TCS_139

                        7.2

                        Error messages

                        Test at least once each error message (as specified in Appendix 2) for each command
                        Test at least once every generic error (except ‘6400’ integrity errors checked during security certification)

                        7.3

                        Cypher suite and standardized domain parameters

                        CSM_48, CSM_50

                        8

                           Personalisation

                        8.1

                        Optical personalisation

                        Annex 1C, chapter 4.1 ‘Visible data’, 230)
                        The front page shall contain:
                        information specific to the card issued.
                        Annex 1C, chapter 4.1 ‘Visible data’, 231)
                        The front page shall contain:
                        dates using a ‘dd/mm/yyyy’ or ‘dd.mm.yyyy’ format (day, month, year).
                        Annex 1C, chapter 4.1 ‘Visible data’, 235)
                        Tachograph cards shall bear at least the following features for protection of the card body against counterfeiting and tampering:

                                    —

                                    in the area of the photograph, the security design background and the photograph shall overlap.

                        230, 231, 235

                  5.   EXTERNAL GNSS FACILITY TESTS

                        No

                        Test

                        Description

                        Related requirements

                        1.

                           Administrative examination

                        1.1

                        Documentation

                        Correctness of documentation

                        2.

                           Visual inspection for external GNSS facility

                        2.1.

                        Compliance with documentation

                        2.2.

                        Identification/markings

                        224 to 226

                        2.3

                        Materials

                        219 to 223

                        3.

                           Functional tests

                        3.1

                        Sensor identification data

                        98,99

                        3.2

                        External GNSS module — vehicle unit coupling

                        123, 205

                        3.3

                        GNSS position

                        36, 37

                        3.4

                        Vehicle unit interface when the GNSS receiver is external to the Vehicle Unit

                        03

                        3.5

                        Cypher suite and standardized domain parameters

                        CSM_48, CSM_50

                        4.

                           Environmental tests

                        4.1

                        Temperature

                        Verify functionality through:

                                    Test according to ISO 16750-4, Chapter 5.1.1.2: Low temperature operation test (72 h @ – 20 °C)
                                    This test refers to IEC 60068-2-1: Environmental testing — Part 2-1: Tests — Test A: Cold

                                    Test according to ISO 16750-4: Chapter 5.1.2.2: High temperature operation test (72 h @ 70 °C)
                                    This test refers to IEC 60068-2-2: Basic environmental testing procedures; part 2: tests; tests B: dry heat

                                    Test according to ISO 16750-4: Chapter 5.3.2: Rapid change of temperature with specified transition duration (– 20 °C/70 °C, 20 cycles, dwell time 1 h at each temperature)
                                    A reduced set of tests (among those defined in section 3 of this table) can be carried out at the lower temperature, the higher temperature and during the temperature cycles

                        213

                        4.2

                        Humidity

                        Verify that the vehicle unit can withstand a cyclic damp (heat test) through IEC 60068-2-30, test Db, six 24 hours cycles, each temperature varying from + 25 °C to + 55 °C and a relative humidity of 97 % at + 25 °C and equal to 93 % at + 55 °C

                        214

                        4.3

                        Mechanical

                                    1.

                                    Sinusoidal vibrations.
                                    verify that the vehicle unit can withstand sinusoidal vibrations with the following characteristics:

                                                constant displacement between 5 and 11 Hz: 10 mm peak

                                                constant acceleration between 11 and 300 Hz: 5g

                                          This requirement is verified through IEC 60068-2-6, test Fc, with a minimum test duration of 3 × 12 hours (12 hours per axis)
                                    ISO 16750-3 does not require a sinusoidal vibration test for devices located in the decoupled vehicle cab.

                                    2.

                                    Random vibrations:
                                    Test according to ISO 16750-3: Chapter 4.1.2.8: Test VIII: Commercial vehicle, decoupled vehicle cab
                                    Random vibration test, 10…2 000  Hz, RMS vertical 21,3 m/s2, RMS longitudinal 11,8 m/s2, RMS lateral 13,1 m/s2, 3 axes, 32 h per axis, including temperature cycle – 20…70°C.
                                    This test refers to IEC 60068-2-64: Environmental testing — Part 2-64: Tests — Test Fh: Vibration, broadband random and guidance

                                    3.

                                    Shocks:
                                    mechanical shock with 3g half sinus according ISO 16750.

                              The tests described above are performed on different samples of the equipment type being tested.

                        219

                        4.4

                        Protection against water and foreign bodies

                        Test according to ISO 20653: Road vehicles — Degree of protection (IP code) — Protection of electrical equipment against foreign objects, water and access (No change in parameters)

                        220, 221

                        4.5

                        Over-voltage protection

                        Verify that the vehicle unit can withstand a power supply of:

                        216

                        24 V versions:

                        34 V at + 40 °C 1 hour

                        12V versions:

                        17 V at + 40 °C 1 hour

                        ( ISO 16750-2, chapter 4.3)

                        4.6

                        Reverse polarity protection

                        Verify that the vehicle unit can withstand an inversion of its power supply
                        (ISO 16750-2, chapter 4.7)

                        216

                        4.7

                        Short-circuit protection

                        Verify that input output signals are protected against short circuits to power supply and ground
                        (ISO 16750-2, chapter 4.10])

                        216

                        5

                           EMC tests

                        5.1

                        Radiated emissions and susceptibility

                        Compliance with Regulation ECE R10

                        218

                        5.2

                        Electrostatic discharge

                        Compliance with ISO 10605:2008 + Technical Corrigendum: 2010 + AMD1:2014: +/– 4kV for contact and +/– 8kV for air discharge

                        218

                        5.3

                        Conducted transient susceptibility on power supply

                        For 24V versions: compliance with ISO 7637-2 + ECE Regulation No. 10 Rev. 3:

                                    pulse 1a: Vs = – 450V Ri = 50 ohms

                                    pulse 2a: Vs= + 37V Ri = 2 ohms

                                    pulse 2b: Vs= + 20V Ri = 0,05 ohms

                                    pulse 3a: Vs= – 150V Ri = 50 ohms

                                    pulse 3b: Vs=+ 150V Ri = 50 ohms

                                    pulse 4: Vs = – 16 V Va = – 12V t6 = 100 ms

                                    pulse 5: Vs= + 120 V Ri = 2,2 ohms td = 250 ms

                              For 12V versions: compliance with ISO 7637-1 + ECE Regulation No. 10 Rev. 3:

                                    pulse 1: Vs= – 75V Ri=10 ohms

                                    pulse 2a: Vs= + 37V Ri=2 ohms

                                    pulse 2b: Vs= + 10V Ri=0,05 ohms

                                    pulse 3a: Vs= – 112V Ri=50 ohms

                                    pulse 3b: Vs= + 75V Ri=50 ohms

                                    pulse 4: Vs= – 6V Va=-5V t6=15ms

                                    pulse 5: Vs= + 65V Ri=3ohms td=100ms

                              Pulse 5 shall be tested only for vehicle units designed to be installed in vehicles for which no external common protection against load dump is implemented
                        For load dump proposal, refer to ISO 16750-2, 4th edition, chapter 4.6.4.

                        218

                  6.   REMOTE COMMUNICATION FACILITY TESTS

                        No

                        Test

                        Description

                        Related requirements

                        1.

                           Administrative examination

                        1.1

                        Documentation

                        Correctness of documentation

                        2.

                           Visual inspection

                        2.1.

                        Compliance with documentation

                        2.2.

                        Identification/markings

                        225, 226

                        2.3

                        Materials

                        219 to 223

                        4.

                           Environmental tests

                        4.1

                        Temperature

                        Verify functionality through:

                                    Test according to ISO 16750-4, Chapter 5.1.1.2: Low temperature operation test (72 h @ – 20 °C)
                                    This test refers to IEC 60068-2-1: Environmental testing — Part 2-1: Tests — Test A: Cold

                                    Test according to ISO 16750-4: Chapter 5.1.2.2: High temperature operation test (72 h @ 70 °C)
                                    This test refers to IEC 60068-2-2: Basic environmental testing procedures; part 2: tests; tests B: dry heat

                                    Test according to ISO 16750-4: Chapter 5.3.2: Rapid change of temperature with specified transition duration (– 20 °C/70 °C, 20 cycles, dwell time 1 h (?) at each temperature)
                                    A reduced set of tests (among those defined in section 3 of this table) can be carried out at the lower temperature, the higher temperature and during the temperature cycles

                        213

                        4.4

                        Protection against water and foreign bodies

                        Test according to ISO 20653: Road vehicles — Degree of protection (IP code) — Protection of electrical equipment against foreign objects, water and access (targeted value IP40)

                        220, 221

                        5

                           EMC tests

                        5.1

                        Radiated emissions and susceptibility

                        Compliance with Regulation ECE R10

                        218

                        5.2

                        Electrostatic discharge

                        Compliance with ISO 10605:2008 + Technical Corrigendum:2010 + AMD1:2014: +/– 4kV for contact and +/– 8kV for air discharge

                        218

                        5.3

                        Conducted transient susceptibility on power supply

                        For 24V versions: compliance with ISO 7637-2 + ECE Regulation No. 10 Rev. 3:

                                    pulse 1a: Vs = – 450 V Ri = 50 ohms

                                    pulse 2a: Vs = + 37 V Ri = 2 ohms

                                    pulse 2b: Vs = + 20 V Ri = 0,05 ohms

                                    pulse 3a: Vs = – 150 V Ri = 50 ohms

                                    pulse 3b: Vs = + 150 V Ri = 50 ohms

                                    pulse 4: Vs = – 16 V Va = – 12 V t6 = 100 ms

                                    pulse 5: Vs = + 120 V Ri = 2,2 ohms td = 250 ms

                              For 12V versions: compliance with ISO 7637-1 + ECE Regulation No. 10 Rev. 3:

                                    pulse 1: Vs = – 75 V Ri = 10 ohms

                                    pulse 2a: Vs = + 37 V Ri = 2 ohms

                                    pulse 2b: Vs = + 10 V Ri = 0,05 ohms

                                    pulse 3a: Vs = – 112 V Ri = 50 ohms

                                    pulse 3b: Vs = + 75 V Ri = 50 ohms

                                    pulse 4: Vs= –6 V Va = – 5 V t6 = 15 ms

                                    pulse 5: Vs = + 65 V Ri=3 ohms td=100 ms

                              Pulse 5 shall be tested only for vehicle units designed to be installed in vehicles for which no external common protection against load dump is implemented
                        For load dump proposal, refer to ISO 16750-2, 4th edition, chapter 4.6.4.

                        218

                  7.   PAPER FUNCTIONAL TESTS

                        No

                        Test

                        Description

                        Related requirements

                        1.

                           Administrative examination

                        1.1

                        Documentation

                        Correctness of documentation

                        2

                           General Tests

                        2.1

                        Number of characters per line

                        Visual inspection of printouts.

                        172

                        2.2

                        Minimum character size

                        Visual inspection of printout and character inspection.

                        173

                        2.3

                        Supported character sets

                        The printer shall support characters specified in Appendix 1 Chapter 4 ‘Character sets’.

                        174

                        2.4

                        Printouts definition

                        Check of tachograph type approval and visual inspection of printouts

                        174

                        2.5

                        Legibility and identification of printouts

                        Inspection of printouts
                        Demonstrated by test reports and test protocols by manufacturer.
                        All homologation number(s) of tachographs with which the printer paper may be used are imprinted on the paper.

                        175, 177, 178

                        2.6

                        Addition of handwritten notes

                        Visual inspection: Field for signature of the driver is available.
                        Fields for additional other handwritten entries are available.

                        180

                        2.7

                        Additional details on paper faces.

                        Paper's face and reverse side may feature additional details and information.
                        These additional details and information may not interfere with the legibility of the printouts.
                        Visual inspection.

                        177, 178

                        3

                           Storage Tests

                        3.1

                        Dry Heat

                        Preconditioning: 16 hours at + 23 °C ± 2 °C/55 % ± 3 % relative humidity
                        Test environment: 72 hours at + 70 °C ± 2 °C
                        Recovery: 16 hours at + 23 °C ± 2 °C/55 % ± 3 % relative humidity

                        176, 178
                        IEC 60068-2-2-Bb

                        2.2

                        Damp Heat

                        Preconditioning: 16 hours at + 23 °C ± 2 °C/55 % ±3 % relative humidity
                        Test environment: 144 hours at + 55 °C ± 2 °C and 93 % ± 3 % r.h.
                        Recovery: 16 hours at + 23 °C ± 2 °C/55 % ± 3 % relative humidity

                        176, 178
                        IEC 60068-2-78-Cab

                        4

                           Paper In-Service Tests

                        4.1

                        Humidity resistance background (unprinted paper)

                        Preconditioning: 16 hours at + 23 °C ± 2 °C/55 % ±3 % relative humidity
                        Test environment: 144 hours at + 55 °C ± 2 °C and 93 % ± 3 % r.h.
                        Recovery: 16 hours at + 23 °C ± 2 °C/55 % ± 3 % relative humidity

                        176, 178
                        IEC 60068-2-78-Cab

                        4.2

                        Printability

                        Preconditioning: 24 hours at + 40 °C ± 2 °C/93 % ± 3 % relative humidity
                        Test environment: printout produced at + 23 °C ± 2 °C
                        Recovery: 16 hours at + 23 °C ± 2 °C/55 % ± 3 % relative humidity

                        176, 178

                        4.3

                        Heat resistance

                        Preconditioning: 16 hours at + 23 °C ± 2 °C/55 % ± 3 % relative humidity
                        Test environment: 2 hours at + 70 °C ± 2 °C, dry heat
                        Recovery: 16 hours at + 23 °C ± 2 °C/55 % ± 3 % relative humidity

                        176, 178
                        IEC 60068-2-2-Bb

                        4.4

                        Low temperature resistance

                        Preconditioning: 16 hours at + 23 °C ± 2 °C/55 % ± 3 % relative humidity
                        Test environment: 24 hours – 20 °C ± 3 °C, dry cold
                        Recovery: 16 hours at + 23 °C ± 2 °C/55 % ± 3 % relative humidity

                        176, 178
                        ISO 60068-2-1-Ab

                        4.5

                        Light resistance

                        Preconditioning: 16 hours at + 23 °C ± 2 °C/55 % ± 3 % relative humidity
                        Test environment: 100 hours under 5 000  Lux illumination at + 23 °C ± 2 °C/55 % ± 3 % relative humidity
                        Recovery: 16 hours at + 23 °C ± 2 °C/55 % ± 3 % relative humidity

                        176, 178

                  Legibility criteria for tests 3.x and 4.x:
            Printout legibility is assured if optical densities comply with the following limits:

                        Printed characters: min. 1,0

                        Background (unprinted paper): max. 0,2

                  Optical densities of the resulting printouts shall be measured according to DIN EN ISO 534.
            Printouts shall show no dimensional changes and remain clearly legible.
            8.   INTEROPERABILITY TESTS

                        No

                        Test

                        Description

                  9.1   Interoperability tests between vehicle units and tachograph cards

                        1

                        Mutual authentication

                        Check that the mutual authentication between the vehicle unit and the tachograph card runs normally

                        2

                        Write/read tests

                        Execute a typical activity scenario on the vehicle unit. The scenario shall be adapted to the type of card being tested and involve writings in as many EFs as possible in the card
                        Verify through a vehicle unit downloading that all corresponding recordings have been properly made
                        Verify through a card downloading that all corresponding recordings have been properly made
                        Verify through daily printouts that all corresponding recordings can be properly read

                  9.2   Interoperability tests between vehicle units and motion sensors

                        1

                        Pairing

                        Check that the pairing between the vehicle units and the motion sensors runs normally

                        2

                        Activity tests

                        Execute a typical activity scenario on the motion sensor. The scenario shall involve a normal activity and creating as many events or faults as possible.
                        Verify through a vehicle unit downloading that all corresponding recordings have been properly made
                        Verify through a card downloading that all corresponding recordings have been properly made
                        Verify through a daily printout that all corresponding recordings can be properly read

                  9.3   Interoperability tests between vehicle units and external GNSS facilities (when applicable)

                        1

                        Mutual Authentication

                        Check that the mutual authentication (coupling) between the vehicle unit and the external GNSS module runs normally.

                        2

                        Activity tests

                        Execute a typical activity scenario on the external GNSS. The scenario shall involve a normal activity and creating as many events or faults as possible.
                        Verify through a vehicle unit downloading that all corresponding recordings have been properly made
                        Verify through a card downloading that all corresponding recordings have been properly made
                        Verify through a daily printout that all corresponding recordings can be properly read

            Appendix 10

               SECURITY REQUIREMENTS

            This appendix specifies the IT security requirements for the smart tachograph system components (second-generation tachograph).

                        SEC_001

                        The following components of the smart tachograph system shall be security certified according to the Common Criteria scheme:

                                    —

                                    vehicle unit

                                    —

                                    tachograph card,

                                    —

                                    motion sensor,

                                    —

                                    external GNSS facility.

                        SEC_002

                        The minimum IT security requirements to be met by each component needing to be security certified shall be defined in a component Protection Profile, according to the Common Criteria scheme.

                        SEC_003

                        The European Commission shall make sure that four Protection Profiles compliant with this Annex are sponsored, developed, approved by the governmental IT security certification bodies organised within the Joint Interpretation Working Group (JIWG) which is supporting the mutual recognition of certificates under the umbrella of the European SOGIS-MRA (Agreement on Mutual Recognition of Information Technology Security Evaluation Certificates) and registered:

                                    —

                                    Protection Profile for vehicle unit,

                                    —

                                    Protection Profile for tachograph card,

                                    —

                                    Protection Profile for motion sensor,

                                    —

                                    Protection Profile for external GNSS facility.

                  The Protection Profile for vehicle unit shall address the cases when the VU is designed to be used or not with an external GNSS facility. In the former case, the security requirements of the external GNSS facility are provided in the dedicated Protection Profile.

                        SEC_004

                        Component manufacturers shall refine and complete the appropriate component Protection Profile as necessary, without amending or deleting existing threats, objectives, procedural means and security enforcing functions specifications, in order to build a Security Target against which they shall seek the security certification of the component.

                        SEC_005

                        Strict conformance of such specific Security Target with the corresponding Protection Profile must be stated during the evaluation process.

                        SEC_006

                        The assurance level for each Protection Profile shall be EAL4 augmented by the assurance components ATE_DPT.2 and AVA_VAN.5.

            Appendix 11

               COMMON SECURITY MECHANISMS

            TABLE OF CONTENTS
            PREAMBLE
                     340

                        PART A

                     FIRST-GENERATION TACHOGRAPH SYSTEM
                     341

                        1.

                     INTRODUCTION
                     341

                        1.1.

                     References
                     341

                        1.2.

                     Notations and abbreviated terms
                     341

                        2.

                     CRYPTOGRAPHIC SYSTEMS AND ALGORITHMS
                     343

                        2.1.

                     Cryptographic systems
                     343

                        2.2.

                     Cryptographic algorithms
                     343

                        2.2.1

                     RSA algorithm
                     343

                        2.2.2

                     Hash algorithm
                     343

                        2.2.3

                     Data Encryption Algorithm
                     343

                        3.

                     KEYS AND CERTIFICATES
                     343

                        3.1.

                     Keys generation and distribution
                     343

                        3.1.1

                     RSA Keys generation and distribution
                     343

                        3.1.2

                     RSA Test keys
                     345

                        3.1.3

                     Motion sensor keys
                     345

                        3.1.4

                     T-DES session keys generation and distribution
                     345

                        3.2.

                     Keys
                     345

                        3.3.

                     Certificates
                     345

                        3.3.1

                     Certificates content
                     346

                        3.3.2

                     Certificates issued
                     348

                        3.3.3

                     Certificate verification and unwrapping
                     349

                        4.

                     MUTUAL AUTHENTICATION MECHANISM
                     349

                        5.

                     VU-CARDS DATA TRANSFER CONFIDENTIALITY, INTEGRITY AND AUTHENTICATION MECHANISMS
                     352

                        5.1.

                     Secure Messaging
                     352

                        5.2.

                     Treatment of Secure Messaging errors
                     354

                        5.3.

                     Algorithm to compute Cryptographic Checksums
                     354

                        5.4.

                     Algorithm to compute cryptograms for confidentiality DOs
                     355

                        6.

                     DATA DOWNLOAD DIGITAL SIGNATURE MECHANISMS
                     355

                        6.1.

                     Signature generation
                     355

                        6.2.

                     Signature verification
                     356

                        PART B

                     SECOND-GENERATION TACHOGRAPH SYSTEM
                     357

                        7.

                     INTRODUCTION
                     357

                        7.1.

                     References
                     357

                        7.2.

                     Notations and Abbreviations
                     357

                        7.3.

                     Definitions
                     359

                        8.

                     CRYPTOGRAPHIC SYSTEMS AND ALGORITHMS
                     359

                        8.1.

                     Cryptographic Systems
                     359

                        8.2.

                     Cryptographic Algorithms
                     360

                        8.2.1

                     Symmetric Algorithms
                     360

                        8.2.2

                     Asymmetric Algorithms and Standardized Domain Parameters
                     360

                        8.2.3

                     Hashing algorithms
                     361

                        8.2.4

                     Cipher Suites
                     361

                        9.

                     KEYS AND CERTIFICATES
                     361

                        9.1.

                     Asymmetric Key Pairs and Public Key Certificates
                     361

                        9.1.1

                     General
                     361

                        9.1.2

                     European Level
                     362

                        9.1.3

                     Member State Level
                     362

                        9.1.4

                     Equipment Level: Vehicle Units
                     363

                        9.1.5

                     Equipment Level: Tachograph Cards
                     365

                        9.1.6

                     Equipment Level: External GNSS Facilities
                     366

                        9.1.7

                     Overview: Certificate Replacement
                     367

                        9.2.

                     Symmetric Keys
                     368

                        9.2.1

                     Keys for Securing VU — Motion Sensor Communication
                     368

                        9.2.2

                     Keys for Securing DSRC Communication
                     372

                        9.3.

                     Certificates
                     375

                        9.3.1

                     General
                     375

                        9.3.2

                     Certificate Content
                     375

                        9.3.3

                     Requesting Certificates
                     377

                        10.

                     VU- CARD MUTUAL AUTHENTICATION AND SECURE MESSAGING
                     378

                        10.1.

                     General
                     378

                        10.2.

                     Mutual Certificate Chain Verification
                     379

                        10.2.1

                     Card Certificate Chain Verification by VU
                     379

                        10.2.2

                     VU Certificate Chain Verification by Card
                     381

                        10.3.

                     VU Authentication
                     384

                        10.4.

                     Chip Authentication and Session Key Agreement
                     385

                        10.5.

                     Secure Messaging
                     387

                        10.5.1

                     General
                     387

                        10.5.2

                     Secure Message Structure
                     388

                        10.5.3

                     Secure Messaging Session Abortion
                     391

                        11.

                     VU — EXTERNAL GNSS FACILITY COUPLING, MUTUAL AUTHENTICATION AND SECURE MESSAGING
                     392

                        11.1.

                     General
                     392

                        11.2.

                     VU and External GNSS Facility Coupling
                     393

                        11.3.

                     Mutual Certificate Chain Verification
                     393

                        11.3.1

                     General
                     393

                        11.3.2

                     During VU — EGF Coupling
                     393

                        11.3.3

                     During Normal Operation
                     394

                        11.4.

                     VU Authentication, Chip Authentication and Session Key Agreement
                     395

                        11.5.

                     Secure Messaging
                     395

                        12.

                     VU — MOTION SENSOR PAIRING AND COMMUNICATION
                     396

                        12.1.

                     General
                     396

                        12.2.

                     VU — Motion Sensor Pairing Using Different Key Generations
                     396

                        12.3.

                     VU — Motion Sensor Pairing and Communication using AES
                     397

                        12.4.

                     VU — Motion Sensor Pairing For Different Equipment Generations
                     399

                        13.

                     SECURITY FOR REMOTE COMMUNICATION OVER DSRC
                     399

                        13.1.

                     General
                     399

                        13.2.

                     Tachograph Payload Encryption and MAC Generation
                     400

                        13.3.

                     Verification and Decryption of Tachograph Payload
                     401

                        14.

                     SIGNING DATA DOWNLOADS AND VERIFYING SIGNATURES
                     401

                        14.1.

                     General
                     401

                        14.2.

                     Signature generation
                     402

                        14.3.

                     Signature verification
                     402
                  PREAMBLE
            This Appendix specifies the security mechanisms ensuring

                        —

                        mutual authentication between different components of the tachograph system.

                        —

                        confidentiality, integrity, authenticity and/or non-repudiation of data transferred between different components of the tachograph system or downloaded to external storage media.

                  This Appendix consists of two parts. Part A defines the security mechanisms for the first-generation tachograph system (digital tachograph). Part B defines the security mechanisms for the second-generation tachograph system (smart tachograph).
            The mechanisms specified in Part A of this Appendix shall apply if at least one of the components of the tachograph system involved in a mutual authentication and/or data transfer process is of the first generation.
            The mechanisms specified in Part B of this Appendix shall apply if both components of the tachograph system involved in the mutual authentication and/or data transfer process are of the second generation.
            Appendix 15 provides more information regarding the use of first generation components in combination with second-generation components.
            PART A

               FIRST-GENERATION TACHOGRAPH SYSTEM

            1.   INTRODUCTION
            1.1.   References

            The following references are used in this Appendix:

                        SHA-1

                        National Institute of Standards and Technology (NIST). FIPS Publication 180-1: Secure Hash Standard. April 1995.

                        PKCS1

                        RSA Laboratories. PKCS # 1: RSA Encryption Standard. Version 2.0. October 1998.

                        TDES

                        National Institute of Standards and Technology (NIST). FIPS Publication 46-3: Data Encryption Standard. Draft 1999.

                        TDES-OP

                        ANSI X9.52, Triple Data Encryption Algorithm Modes of Operation. 1998.

                        ISO/IEC 7816-4

                        Information Technology — Identification cards — Integrated circuit(s) cards with contacts — Part 4: Interindustry commands for interexchange. First edition: 1995 + Amendment 1: 1997.

                        ISO/IEC 7816-6

                        Information Technology — Identification cards — Integrated circuit(s) cards with contacts — Part 6: Interindustry data elements. First edition: 1996 + Cor 1: 1998.

                        ISO/IEC 7816-8

                        Information Technology — Identification cards — Integrated circuit(s) cards with contacts — Part 8: Security related interindustry commands. First edition 1999.

                        ISO/IEC 9796-2

                        Information Technology — Security techniques — Digital signature schemes giving message recovery — Part 2: Mechanisms using a hash function. First edition: 1997.

                        ISO/IEC 9798-3

                        Information Technology — Security techniques — Entity authentication mechanisms — Part 3: Entity authentication using a public key algorithm. Second edition 1998.

                        ISO 16844-3

                        Road vehicles — Tachograph systems — Part 3: Motion sensor interface.

                  1.2.   Notations and abbreviated terms

            The following notations and abbreviated terms are used in this Appendix:

                        (Ka, Kb, Kc)

                        a key bundle for use by the Triple Data Encryption Algorithm,

                        CA

                        Certification Authority,

                        CAR

                        Certification Authority Reference,

                        CC

                        Cryptographic Checksum,

                        CG

                        Cryptogram,

                        CH

                        Command Header,

                        CHA

                        Certificate Holder Authorisation,

                        CHR

                        Certificate Holder Reference,

                        D()

                        Decryption with DES,

                        DE

                        Data Element,

                        DO

                        Data Object,

                           d

                        RSA private key, private exponent,

                           e

                        RSA public key, public exponent,

                        E()

                        Encryption with DES,

                        EQT

                        Equipment,

                           Hash()

                        hash value, an output of Hash,

                           Hash

                        hash function,

                        KID

                        Key Identifier,

                        Km

                        TDES key. Master Key defined in ISO 16844-3.

                        KmVU

                        TDES key inserted in vehicle units.

                        KmWC

                        TDES key inserted in workshop cards.

                           m

                        message representative, an integer between 0 and n-1,

                           n

                        RSA keys, modulus,

                        PB

                        Padding Bytes,

                        PI

                        Padding Indicator byte (for use in Cryptogram for confidentiality DO),

                        PV

                        Plain Value,

                           s

                        signature representative, an integer between 0 and n-1,

                        SSC

                        Send Sequence Counter,

                        SM

                        Secure Messaging,

                        TCBC

                        TDEA Cipher Block Chaining Mode of Operation

                        TDEA

                        Triple Data Encryption Algorithm,

                        TLV

                        Tag Length Value,

                        VU

                        Vehicle Unit,

                        X.C

                        the certificate of user X issued by a certification authority,

                        X.CA

                        a certification authority of user X,

                        X.CA.PK o X.C

                        the operation of unwrapping a certificate to extract a public key. It is an infix operator, whose left operand is the public key of a certification authority, and whose right operand is the certificate issued by that certification authority. The outcome is the public key of the user X whose certificate is the right operand,

                        X.PK

                        RSA public key of a user X,

                        X.PK[I]

                        RSA encipherment of some information I, using the public key of user X,

                        X.SK

                        RSA private key of a user X,

                        X.SK[I]

                        RSA encipherment of some information I, using the private key of user X,

                        ‘xx’

                        an Hexadecimal value,

                        ||

                        concatenation operator.

                  2.   CRYPTOGRAPHIC SYSTEMS AND ALGORITHMS
            2.1.   Cryptographic systems

                        CSM_001

                        Vehicle units and tachograph cards shall use a classical RSA public-key cryptographic system to provide the following security mechanisms:

                                    —

                                    authentication between vehicle units and cards,

                                    —

                                    transport of Triple-DES session keys between vehicle units and tachograph cards,

                                    —

                                    digital signature of data downloaded from vehicle units or tachograph cards to external media.

                        CSM_002

                        Vehicle units and tachograph cards shall use a Triple DES symmetric cryptographic system to provide a mechanism for data integrity during user data exchange between vehicle units and tachograph cards, and to provide, where applicable, confidentiality of data exchange between vehicle units and tachograph cards.

                  2.2.   Cryptographic algorithms

            2.2.1   RSA algorithm

                        CSM_003

                        The RSA algorithm is fully defined by the following relations:

                                    X.SK[m] = s = md
                                        mod n

                                    X.PK[s] = m = se
                                        mod n

                              A more comprehensive description of the RSA function can be found in reference [PKCS1]. Public exponent, e, for RSA calculations is an integer between 3 and n-1 satisfying gcd(e, lcm(p-1, q-1))=1.

                  2.2.2   Hash algorithm

                        CSM_004

                        The digital signature mechanisms shall use the SHA-1 hash algorithm as defined in reference [SHA-1].

                  2.2.3   Data Encryption Algorithm

                        CSM_005

                        DES based algorithms shall be used in Cipher Block Chaining mode of operation.

                  3.   KEYS AND CERTIFICATES
            3.1.   Keys generation and distribution

            3.1.1   RSA Keys generation and distribution

                        CSM_006

                        RSA keys shall be generated through three functional hierarchical levels:

                                    —

                                    European level,

                                    —

                                    Member State level,

                                    —

                                    Equipment level.

                        CSM_007

                        At European level, a single European key pair (EUR.SK and EUR.PK) shall be generated. The European private key shall be used to certify the Member States public keys. Records of all certified keys shall be kept. These tasks shall be handled by a European Certification Authority, under the authority and responsibility of the European Commission.

                        CSM_008

                        At Member State level, a Member State key pair (MS.SK and MS.PK) shall be generated. Member States public keys shall be certified by the European Certification Authority. The Member State private key shall be used to certify public keys to be inserted in equipment (vehicle unit or tachograph card). Records of all certified public keys shall be kept with the identification of the equipment to which it is intended. These tasks shall be handled by a Member State Certification Authority. A Member State may regularly change its key pair.

                        CSM_009

                        At equipment level, one single key pair (EQT.SK and EQT.PK) shall be generated and inserted in each equipment. Equipment public keys shall be certified by a Member State Certification Authority. These tasks may be handled by equipment manufacturers, equipment personalisers or Member State authorities. This key pair is used for authentication, digital signature and encipherement services

                        CSM_010

                        Private keys confidentiality shall be maintained during generation, transport (if any) and storage.
                        The following picture summarises the data flow of this process:

                  3.1.2   RSA Test keys

                        CSM_011

                        For the purpose of equipment testing (including interoperability tests) the European Certification Authority shall generate a different single European test key pair and at least two Member State test key pairs, the public keys of which shall be certified with the European private test key. Manufacturers shall insert, in equipment undergoing type approval tests, test keys certified by one of these Member State test keys.

                  3.1.3   Motion sensor keys

            The confidentiality of the three Triple DES keys described below shall be appropriately maintained during generation, transport (if any) and storage.
            In order to support tachograph components compliant with ISO 16844, the European Certification Authority and the Member State Certification Authorities shall, in addition, ensure the following:

                        CSM_036

                     The European Certification authority shall generate KmVU and KmWC, two independent and unique Triple DES keys, and generate Km as: Km = KmVU XOR KmWC
                        . The European Certification Authority shall forward these keys, under appropriately secured procedures, to Member States Certification Authorities at their request.

                        CSM_037

                        Member States Certification Authorities shall:

                                    —

                                    use Km to encrypt motion sensor data requested by motion sensor manufacturers (data to be encrypted with Km is defined in ISO 16844-3),

                                    —

                                    forward KmVU to vehicle unit manufacturers, under appropriately secured procedures, for insertion in vehicle units,

                                    —

                                    ensure that KmWC will be inserted in all workshop cards ( in elementary file) during card personalisation.

                  3.1.4   T-DES session keys generation and distribution

                        CSM_012

                        Vehicle units and tachograph cards shall, as a part of the mutual authentication process, generate and exchange necessary data to elaborate a common Triple DES session key. This exchange of data shall be protected for confidentiality through an RSA crypt-mechanism.

                        CSM_013

                        This key shall be used for all subsequent cryptographic operations using secure messaging. Its validity shall expire at the end of the session (withdrawal of the card or reset of the card) and/or after 240 use (one use of the key = one command using secure messaging sent to the card and associated response).

                  3.2.   Keys

                        CSM_014

                        RSA keys shall have (whatever the level) the following lengths: modulus n1 024 bits, public exponent e 64 bits maximum, private exponent d1 024 bits.

                        CSM_015

                        Triple DES keys shall have the form (Ka, Kb, Ka) where Ka and Kb are independent 64 bits long keys. No parity error detecting bits shall be set.

                  3.3.   Certificates

                        CSM_016

                        RSA Public key certificates shall be ‘non self-descriptive’‘Card Verifiable’ certificates (Ref.: ISO/IEC 7816-8)

                  3.3.1   Certificates content

                        CSM_017

                        RSA Public key certificates are built with the following data in the following order:

                                    Data

                                    Format

                                    Bytes

                                    Obs

                                    CPI

                                    INTEGER

                                    1

                                    Certificate Profile Identifier (‘01’ for this version)

                                    CAR

                                    OCTET STRING

                                    8

                                    Certification Authority Reference

                                    CHA

                                    OCTET STRING

                                    7

                                    Certificate Holder Authorisation

                                    EOV

                                    TimeReal

                                    4

                                    Certificate end of validity. Optional, ‘FF’ padded if not used.

                                    CHR

                                    OCTET STRING

                                    8

                                    Certificate Holder Reference

                                       n

                                    OCTET STRING

                                    128

                                    Public key (modulus)

                                       e

                                    OCTET STRING

                                    8

                                    Public Key (public exponent)

                                       164

                           Notes:

                                    1.

                                    The ‘Certificate Profile Identifier’ (CPI) delineates the exact structure of an authentication certificate. It can be used as an equipment internal identifier of a relevant headerlist which describes the concatenation of Data Elements within the certificate.
                                    The headerlist associated with this certificate content is as follows:

                                                ‘4D’

                                                ‘16’

                                                ‘5F 29’

                                                ‘01’

                                                ‘42’

                                                ‘08’

                                                ‘5F 4B’

                                                ‘07’

                                                ‘5F 24’

                                                ‘04’

                                                ‘5F 20’

                                                ‘08’

                                                ‘7F 49’

                                                ‘05’

                                                ‘81’

                                                ‘81 80’

                                                ‘82’

                                                ‘08’

                                                Extended Headerlist Tag

                                                Length of header list

                                                CPI Tag

                                                CPI Length

                                                CAR Tag

                                                CAR Length

                                                CHA Tag

                                                CHA Length

                                                EOV Tag

                                                EOV Length

                                                CHR Tag

                                                CHR Length

                                                Public Key Tag (Constructed)

                                                Length of subsequent DOs

                                                modulus Tag

                                                modulus length

                                                public exponent Tag

                                                public exponent length

                                    2.

                                    The ‘Certification Authority Reference’ (CAR) has the purpose of identifying the certificate issuing CA, in such a way that the Data Element can be used at the same time as an Authority Key Identifier to reference the Public Key of the Certification Authority (for coding, see Key Identifier below).

                                    3.

                                 The ‘Certificate Holder Authorisation’ (CHA) is used to identify the rights of the certificate holder. It consists of the Tachograph Application ID and of the type of equipment to which the certificate is intended (according to
                                       data element, ‘00’ for a Member State).

                                    4.

                                    The ‘Certificate Holder Reference’ (CHR) has the purpose of identifying uniquely the certificate holder, in such a way that the Data Element can be used at the same time as a Subject Key Identifier to reference the Public Key of the certificate holder.

                                    5.

                                    Key Identifiers uniquely identify certificate holder or certification authorities. They are coded as follows:

                                                5.1

                                                Equipment (VU or Card):

                                                            Data

                                                            Equipment serial number

                                                            Date

                                                            Type

                                                            Manufacturer

                                                            Length

                                                            4 Bytes

                                                            2 Bytes

                                                            1 Byte

                                                            1 Byte

                                                            Value

                                                            Integer

                                                            mm yy BCD coding

                                                            Manufacturer specific

                                                            Manufacturer code

                                                      In the case of a VU, the manufacturer, when requesting certificates, may or may not know the identification of the equipment in which the keys will be inserted.
                                                In the first case, the manufacturer will send the equipment identification with the public key to its Member State authority for certification. The certificate will then contain the equipment identification, and the manufacturer must ensure that keys and certificate are inserted in the intended equipment. The Key identifier has the form shown above.
                                                In the later case, the manufacturer must uniquely identify each certificate request and send this identification with the public key to its Member State authority for certification. The certificate will contain the request identification. The manufacturer must feed back its Member State authority with the assignment of key to equipment (i.e. certificate request identification, equipment identification) after key installation in the equipment. The key identifier has the following form:

                                                            Data

                                                            Certificate request serial number

                                                            Date

                                                            Type

                                                            Manufacturer

                                                            Length

                                                            4 Bytes

                                                            2 Bytes

                                                            1 Byte

                                                            1 Byte

                                                            Value

                                                            Integer

                                                            mm yy BCD coding

                                                            ‘FF’

                                                            Manufacturer code

                                                5.2

                                                Certification Authority:

                                                            Data

                                                            Authority Identification

                                                            Key serial number

                                                            Additional info

                                                            Identifier

                                                            Length

                                                            4 Bytes

                                                            1 Byte

                                                            2 Bytes

                                                            1 Byte

                                                            Value

                                                            1 Byte nation numerical code
                                                            3 Bytes nation alphanumerical code

                                                            Integer

                                                            additional coding
                                                            (CA specific)
                                                            ‘FF FF’ if not used

                                                            ‘01’

                                                      The key serial number is used to distinguish the different keys of a Member State, in the case the key is changed.

                                    6.

                                    Certificate verifiers shall implicitly know that the public key certified is an RSA key relevant to authentication, digital signature verification and encipherement for confidentiality services (the certificate contains no Object Identifier to specify it).

                  3.3.2   Certificates issued

                        CSM_018

                        The certificate issued is a digital signature with partial recovery of the certificate content in accordance with ISO/IEC 9796-2 (except for its annex A4), with the ‘Certification Authority Reference’ appended.
                        X.C = X.CA.SK[‘6A’ || Cr || Hash(Cc) || ‘BC’] || Cn || X.CAR

                                    With certificate content = Cc =

                                    Cr

                                    ||

                                    Cn

                                    106 bytes

                                    58 bytes

                           Notes:

                                    1.

                                    This certificate is 194 bytes long.

                                    2.

                                    CAR, being hidden by the signature, is also appended to the signature, such that the Public Key of the Certification Authority may be selected for the verification of the certificate.

                                    3.

                                    The certificate verifier shall implicitly know the algorithm used by the Certification Authority to sign the certificate.

                                    4.

                                    The headerlist associated with this issued certificate is as follows:

                                                ‘7F 21’

                                                ‘09’

                                                ‘5F 37’

                                                ‘81 80’

                                                ‘5F 38’

                                                ‘3A’

                                                ‘42’

                                                ‘08’

                                                CV Certificate Tag (Constructed)

                                                Length of subsequent DOs

                                                Signature Tag

                                                Signature Length

                                                Remainder Tag

                                                Remainder Length

                                                CAR Tag

                                                CAR Length

                  3.3.3   Certificate verification and unwrapping

            Certificate verification and unwrapping consists in verifying the signature in accordance with ISO/IEC 9796-2, retrieving the certificate content and the public key contained: X.PK = X.CA.PK o X.C, and verifying the validity of the certificate.

                        CSM_019

                        It involves the following steps:

                                    Verify signature and retrieve content:

                                                            —

                                                            from X.C retrieve Sign, Cn' and CAR':

                                                X.C =

                                                Sign

                                                ||

                                                Cn'

                                                ||

                                                CAR'

                                                128 Bytes

                                                58 Bytes

                                                8 Bytes

                                                —

                                                from CAR' select appropriate Certification Authority Public Key (if not done before through other means)

                                                —

                                                open Sign with CA Public Key: Sr'= X.CA.PK [Sign],

                                                —

                                                check Sr' starts with ‘6A’ and ends with ‘BC’

                                                            —

                                                            compute Cr' and H' from: Sr' =

                                                ‘6A’

                                                ||

                                                Cr'

                                                ||

                                                H'

                                                ||

                                                ‘BC’

                                                106 Bytes

                                                20 Bytes

                                                —

                                                Recover certificate content C' = Cr' || Cn',

                                                —

                                                check Hash(C') = H'

                                    If the checks are OK the certificate is a genuine one, its content is C'.

                                    Verify validity. From C':

                                                —

                                                if applicable, check End of validity date,

                                    Retrieve and store public key, Key Identifier, Certificate Holder Authorisation and Certificate End of Validity from C':

                                                —

                                                X.PK = n || e

                                                —

                                                X.KID = CHR

                                                —

                                                X.CHA = CHA

                                                —

                                                X.EOV = EOV

                  4.   MUTUAL AUTHENTICATION MECHANISM
            Mutual authentication between cards and VUs is based on the following principle:
            Each party shall demonstrate to the other that it owns a valid key pair, the public key of which has been certified by a Member State certification authority, itself being certified by the European certification authority.
            Demonstration is made by signing with the private key a random number sent by the other party, who must recover the random number sent when verifying this signature.
            The mechanism is triggered at card insertion by the VU. It starts with the exchange of certificates and unwrapping of public keys, and ends with the setting of a session key.

                        CSM_020

                        The following protocol shall be used (arrows indicate commands and data exchanged (see Appendix 2)):

                  5.   VU-CARDS DATA TRANSFER CONFIDENTIALITY, INTEGRITY AND AUTHENTICATION MECHANISMS
            5.1.   Secure Messaging

                        CSM_021

                        VU-Cards data transfers integrity shall be protected through Secure Messaging in accordance with references [ISO/IEC 7816-4] and [ISO/IEC 7816-8].

                        CSM_022

                        When data need to be protected during transfer, a Cryptographic Checksum Data Object shall be appended to the Data Objects sent within the command or the response. The Cryptographic Checksum shall be verified by the receiver.

                        CSM_023

                        The cryptographic checksum of data sent within a command shall integrate the command header, and all data objects sent (=>CLA = ‘0C’, and all data objects shall be encapsulated with tags in which b1=1).

                        CSM_024

                        The response status-information bytes shall be protected by a cryptographic checksum when the response contains no data field.

                        CSM_025

                        Cryptographic checksums shall be 4 Bytes long.
                        The structure of commands and responses when using secure messaging is therefore the following:

                                    The DOs used are a partial set of the Secure Messaging DOs described in ISO/IEC 7816-4:

                                                Tag

                                                Mnemonic

                                                Meaning

                                                   ‘81’

                                                TPV

                                                Plain Value not BER-TLV coded data (to be protected by CC)

                                                ‘97’

                                                   TLE

                                                Value of Le in the unsecured command (to be protected by CC)

                                                ‘99’

                                                TSW

                                                Status-Info (to be protected by CC)

                                                ‘8E’

                                                TCC

                                                Cryptographic Checksum

                                                ‘87’

                                                TPI CG

                                                Padding Indicator Byte || Cryptogram (Plain Value not coded in BER-TLV)

                                    Given an unsecured command response pair:

                                                Command header

                                                Command body

                                                CLA

                                                INS

                                                P1

                                                P2

                                                [Lc field]

                                                [Data field]

                                                [Le field]

                                                four bytes

                                                L bytes, denoted as B1 to BL

                                                Response body

                                                Response trailer

                                                [Data field]

                                                SW1

                                                SW2

                                                Lr data bytes

                                                two bytes

                                    The corresponding secured command response pair is:

                                                Secured command:

                                                            Command header (CH)

                                                            Command body

                                                            CLA

                                                            INS

                                                            P1

                                                            P2

                                                            [New Lc field]

                                                            [New Data field]

                                                            [New Le field]

                                                            ‘OC’

                                                            Length of New Data field

                                                            TPV

                                                            LPV

                                                            PV

                                                            TLE

                                                            LLE

                                                            Le

                                                            TCC

                                                            LCC

                                                            CC

                                                            ‘00’

                                                            ‘81’

                                                            Lc

                                                            Data field

                                                            ‘97’

                                                            ‘01’

                                                            Le

                                                            ‘8E’

                                                            ‘04’

                                                            CC

                                                      Data to be integrated in checksum = CH || PB || TPV || LPV || PV || TLE || LLE || Le || PB
                                                PB = Padding Bytes (80 .. 00) in accordance with ISO-IEC 7816-4 and ISO 9797 method 2.
                                                DOs PV and LE are present only when there is some corresponding data in the unsecured command.

                                                Secured response:

                                                            1.

                                                            Case where response data field is not empty and needs not to be protected for confidentiality:

                                                                        Response body

                                                                        Response trailer

                                                                        [New Data field]

                                                                        new SW1 SW2

                                                                        TPV

                                                                        LPV

                                                                        PV

                                                                        TCC

                                                                        LCC

                                                                        CC

                                                                        ‘81’

                                                                        Lr

                                                                        Data field

                                                                        ‘8E’

                                                                        ‘04’

                                                                        CC

                                                                  Data to be integrated in checksum = TPV || LPV || PV || PB

                                                            2.

                                                            Case where response data field is not empty and needs to be protected for confidentiality:

                                                                        Response body

                                                                        Response trailer

                                                                        [New Data field]

                                                                        new SW1 SW2

                                                                        TPI CG

                                                                        LPI CG

                                                                        PI CG

                                                                        TCC

                                                                        LCC

                                                                        CC

                                                                        ‘87’

                                                                        PI || CG

                                                                        ‘8E’

                                                                        ‘04’

                                                                        CC

                                                                  Data to be carried by CG: non BER-TLV coded data and padding bytes.
                                                            Data to be integrated in checksum = TPI CG || LPI CG || PI CG || PB

                                                            3.

                                                            Case where response data field is empty:

                                                                        Response body

                                                                        Response trailer

                                                                        [New Data field]

                                                                        new SW1 SW2

                                                                        TSW

                                                                        LSW

                                                                        SW

                                                                        TCC

                                                                        LCC

                                                                        CC

                                                                        ‘99’

                                                                        ‘02’

                                                                        New SW1 SW2

                                                                        ‘8E’

                                                                        ‘04’

                                                                        CC

                                                                  Data to be integrated in checksum = TSW || LSW || SW || PB

                  5.2.   Treatment of Secure Messaging errors

                        CSM_026

                        When the tachograph card recognises an SM error while interpreting a command, then the status bytes must be returned without SM. In accordance with ISO/IEC 7816-4, the following status bytes are defined to indicate SM errors:

                                    ‘66 88’

                                    :

                                    Verification of Cryptographic Checksum failed,

                                    ‘69 87’

                                    :

                                    Expected SM Data Objects missing,

                                    ‘69 88’

                                    :

                                    SM Data Objects incorrect.

                        CSM_027

                        When the tachograph card returns status bytes without SM DOs or with an erroneous SM DO, the session must be aborted by the VU.

                  5.3.   Algorithm to compute Cryptographic Checksums

                        CSM_028

                        Cryptographic checksums are built using a retail MACs in accordance with ANSI X9.19 with DES:

                                    —

                                    Initial stage: The initial check block y0 is E(Ka, SSC).

                                    —

                                    Sequential stage: The check blocks y1, .., yn are calculated using Ka.

                                    —

                                    Final stage: The cryptographic checksum is calculated from the last check block yn as follows: E(Ka, D(Kb, yn)).

                              where E() means encryption with DES, and D() means decryption with DES.
                        The four most significant bytes of the cryptographic checksum are transferred

                        CSM_029

                        The Send Sequence Counter (SSC) shall be initiated during key agreement procedure to:
                        Initial SSC: Rnd3 (4 least significant bytes) || Rnd1 (4 least significant bytes).

                        CSM_030

                        The Send Sequence Counter shall be increased by 1 each time before a MAC is calculated (i.e. the SSC for the first command is Initial SSC + 1, the SSC for the first response is Initial SSC + 2).
                        The following figure shows the calculation of the retail MAC:

                  5.4.   Algorithm to compute cryptograms for confidentiality DOs

                        CSM_031

                        Cryptograms are computed using TDEA in TCBC mode of operation in accordance with references [TDES] and [TDES-OP] and with the Null vector as Initial Value block.
                        The following figure shows the application of keys in TDES:

                  6.   DATA DOWNLOAD DIGITAL SIGNATURE MECHANISMS

                        CSM_032

                        The Intelligent Dedicated Equipment (IDE) stores data received from an equipment (VU or card) during one download session within one physical data file. This file must contain the certificates MSi.C and EQT.C. The file contains digital signatures of data blocks as specified in Appendix 7 Data Downloading Protocols.

                        CSM_033

                        Digital signatures of downloaded data shall use a digital signature scheme with appendix such, that downloaded data may be read without any decipherment if desired.

                  6.1.   Signature generation

                        CSM_034

                        Data signature generation by the equipment shall follow the signature scheme with appendix defined in reference [PKCS1] with the SHA-1 hash function:

                                    Signature = EQT.SK[‘00’ || ‘01’ || PS || ‘00’ || DER(SHA-1(Data))]

                                       PS = Padding string of octets with value ‘FF’ such that length is 128.

                                    DER(SHA-1(M)) is the encoding of the algorithm ID for the hash function and the hash value into an ASN.1 value of type DigestInfo (distinguished encoding rules):
                                    ‘30’||‘21’||‘30’||‘09’||‘06’||‘05’||‘2B’||‘0E’||‘03’||‘02’||‘1A’||‘05’||‘00’||‘04’||‘14’||Hash Value.

                  6.2.   Signature verification

                        CSM_035

                        Data signature verification on downloaded data shall follow the signature scheme with appendix defined in reference [PKCS1] with the SHA-1 hash function.
                        The European public key EUR.PK needs to be known independently (and trusted) by the verifier.
                        The following table illustrates the protocol an IDE carrying a Control card can follow to verify the integrity of data downloaded and stored on the ESM (External Storage media). The control card is used to perform the decipherement of digital signatures. This function may in this case not be implemented in the IDE.
                        The equipment that has downloaded and signed the data to be analysed is denoted EQT.

                  PART B

               SECOND-GENERATION TACHOGRAPH SYSTEM

            7.   INTRODUCTION
            7.1.   References

            The following references are used in this part of this Appendix.

                        AES

                        National Institute of Standards and Technology (NIST), FIPS PUB 197: Advanced Encryption Standard (AES), November 26, 2001

                        DSS

                        National Institute of Standards and Technology (NIST), FIPS PUB 186-4: Digital Signature Standard (DSS), July 2013

                        ISO 7816-4

                        ISO/IEC 7816-4, Identification cards — Integrated circuit cards — Part 4: Organization, security and commands for interchange. Third edition 2013-04-15

                        ISO 7816-8

                        ISO/IEC 7816-8, Identification cards — Integrated circuit cards — Part 8: Commands for security operations. Second edition 2004-06-01

                        ISO 8825-1

                        ISO/IEC 8825-1, Information technology — ASN.1 encoding rules: Specification of Basic Encoding Rules (BER), Canonical Encoding Rules (CER) and Distinguished Encoding Rules (DER). Fourth edition, 2008-12-15

                        ISO 9797-1

                        ISO/IEC 9797-1, Information technology — Security techniques — Message Authentication Codes (MACs) — Part 1: Mechanisms using a block cipher. Second edition, 2011-03-01

                        ISO 10116

                        ISO/IEC 10116, Information technology — Security techniques — Modes of operation of an n-bit block cipher. Third edition, 2006-02-01

                        ISO 16844-3

                        ISO/IEC 16844-3, Road vehicles — Tachograph systems — Part 3: Motion sensor interface. First edition 2004, including Technical Corrigendum 1 2006

                        RFC 5480

                        Elliptic Curve Cryptography Subject Public Key Information, March 2009

                        RFC 5639

                        Elliptic Curve Cryptography (ECC) — Brainpool Standard Curves and Curve Generation, 2010

                        RFC 5869

                        HMAC-based Extract-and-Expand Key Derivation Function (HKDF), May 2010

                        SHS

                        National Institute of Standards and Technology (NIST), FIPS PUB 180-4: Secure Hash Standard, March 2012

                        SP 800-38B

                        National Institute of Standards and Technology (NIST), Special Publication 800-38B: Recommendation for Block Cipher Modes of Operation: The CMAC Mode for Authentication, 2005

                        TR-03111

                        BSI Technical Guideline TR-03111, Elliptic Curve Cryptography, version 2.00, 2012-06-28

                  7.2.   Notations and Abbreviations

            The following notations and abbreviated terms are used in this Appendix:

                        AES

                        Advanced Encryption Standard

                        CA

                        Certificate Authority

                        CAR

                        Certificate Authority Reference

                        CBC

                        Cipher Block Chaining (mode of operation)

                        CH

                        Command Header

                        CHA

                        Certificate Holder Authorisation

                        CHR

                        Certificate Holder Reference

                        CV

                        Constant Vector

                        DER

                        Distinguished Encoding Rules

                        DO

                        Data Object

                        DSRC

                        Dedicated Short Range Communication

                        ECC

                        Elliptic Curve Cryptography

                        ECDSA

                        Elliptic Curve Digital Signature Algorithm

                        ECDH

                        Elliptic Curve Diffie-Hellman (key agreement algorithm)

                        EGF

                        External GNSS Facility

                        EQT

                        Equipment

                        IDE

                        Intelligent Dedicated Equipment

                        KM

                        Motion Sensor Master Key, allowing the pairing of a Vehicle Unit to a Motion Sensor

                        KM-VU

                        Key inserted in vehicle units, allowing a VU to derive the Motion Sensor Master Key if a workshop card is inserted into the VU

                        KM-WC

                        Key inserted in workshop cards, allowing a VU to derive the Motion Sensor Master Key if a workshop card is inserted into the VU

                        MAC

                        Message Authentication Code

                        MoS

                        Motion Sensor

                        MSB

                        Most Significant Bit

                        PKI

                        Public Key Infrastructure

                        RCF

                        Remote Communication Facility

                        SSC

                        Send Sequence Counter

                        SM

                        Secure Messaging

                        TDES

                        Triple Data Encryption Standard

                        TLV

                        Tag Length Value

                        VU

                        Vehicle Unit

                        X.C

                        the public key certificate of user X

                        X.CA

                        the certificate authority that issued the certificate of user X

                        X.CAR

                        the certificate authority reference mentioned in the certificate of user X

                        X.CHR

                        the certificate holder reference mentioned in the certificate of user X

                        X.PK

                        public key of user X

                        X.SK

                        private key of user X

                        X.PKeph

                        ephemeral public key of user X

                        X.SKeph

                        ephemeral private key of user X

                        ‘xx’

                        a hexadecimal value

                        ||

                        concatenation operator

                  7.3.   Definitions

            The definitions of terms used in this Appendix are included in section I of Annex 1C.
            8.   CRYPTOGRAPHIC SYSTEMS AND ALGORITHMS
            8.1.   Cryptographic Systems

                        CSM_38

                        Vehicle units and tachograph cards shall use an elliptic curve-based public-key cryptographic system to provide the following security services:

                                    —

                                    mutual authentication between a vehicle unit and a card,

                                    —

                                    agreement of AES session keys between a vehicle unit and a card,

                                    —

                                    ensuring the authenticity, integrity and non-repudiation of data downloaded from vehicle units or tachograph cards to external media.

                        CSM_39

                        Vehicle units and external GNSS facilities shall use an elliptic curve-based public-key cryptographic system to provide the following security services:

                                    —

                                    coupling of a vehicle unit and an external GNSS facility,

                                    —

                                    mutual authentication between a vehicle unit and an external GNSS facility,

                                    —

                                    agreement of an AES session key between a vehicle unit and an external GNSS facility.

                        CSM_40

                        Vehicle units and tachograph cards shall use an AES-based symmetric cryptographic system to provide the following security services:

                                    —

                                    ensuring authenticity and integrity of data exchanged between a vehicle unit and a tachograph card,

                                    —

                                    where applicable, ensuring confidentiality of data exchanged between a vehicle unit and a tachograph card.

                        CSM_41

                        Vehicle units and external GNSS facilities shall use an AES-based symmetric cryptographic system to provide the following security services:

                                    —

                                    ensuring authenticity and integrity of data exchanged between a vehicle unit and an external GNSS facility.

                        CSM_42

                        Vehicle units and motion sensors shall use an AES-based symmetric cryptographic system to provide the following security services:

                                    —

                                    pairing of a vehicle unit and a motion sensor,

                                    —

                                    mutual authentication between a vehicle unit and a motion sensor,

                                    —

                                    ensuring confidentiality of data exchanged between a vehicle unit and a motion sensor.

                        CSM_43

                        Vehicle units and control cards shall use an AES-based symmetric cryptographic system to provide the following security services on the remote communication interface:

                                    —

                                    ensuring confidentiality, authenticity and integrity of data transmitted from a vehicle unit to a control card.

                           Notes:

                                    —

                                    Properly speaking, data is transmitted from a vehicle unit to a remote interrogator under the control of a control officer, using a remote communication facility that may be internal or external to the VU, see Appendix 14. However, the remote interrogator sends the received data to a control card for decryption and validation of authenticity. From a security point of view, the remote communication facility and the remote interrogator are fully transparent.

                                    —

                                    A workshop card offers the same security services for the DSRC interface as a control card does. This allows a workshop to validate the proper functioning of the remote communication interface of a VU, including security. Please refer to section 9.2.2 for more information.

                  8.2.   Cryptographic Algorithms

            8.2.1   Symmetric Algorithms

                        CSM_44

                        Vehicle units, tachograph cards, motion sensors and external GNSS facilities shall support the AES algorithm as defined in [AES], with key lengths of 128, 192 and 256 bits.

                  8.2.2   Asymmetric Algorithms and Standardized Domain Parameters

                        CSM_45

                        Vehicle units, tachograph cards and external GNSS facilities shall support elliptic curve cryptography with a key size of 256, 384 and 512/521 bits.

                        CSM_46

                        Vehicle units, tachograph cards and external GNSS facilities shall support the ECDSA signing algorithm, as specified in [DSS].

                        CSM_47

                        Vehicle units, tachograph cards and external GNSS facilities shall support the ECKA-EG key agreement algorithm, as specified in [TR 03111].

                        CSM_48

                        Vehicle units, tachograph cards and external GNSS facilities shall support all standardized domain parameters specified in Table 1 below for elliptic curve cryptography.

                           Table 1

                           Standardized domain parameters

                                    Name

                                    Size (bits)

                                    Reference

                                    Object identifier

                                    NIST P-256

                                    256

                                    [DSS], [RFC 5480]

                                    BrainpoolP256r1

                                    256

                                    [RFC 5639]

                                    NIST P-384

                                    384

                                    [DSS], [RFC 5480]

                                    BrainpoolP384r1

                                    384

                                    [RFC 5639]

                                    BrainpoolP512r1

                                    512

                                    [RFC 5639]

                                    NIST P-521

                                    521

                                    [DSS], [RFC 5480]

                           Note: the object identifiers mentioned in the last column of Table 1 are specified in [RFC 5639] for the Brainpool curves and in [RFC 5480] for the NIST curves.
                        Text of image

                           Example 1: the object identifier of the BrainpoolP256r1 curve is {iso(1) identified-organization(3) teletrust(36) algorithm(3) signaturealgorithm(3) ecSign(2) ecStdCurvesAndGeneration (8) ellipticCurve(1) versionOne(1) 7}.
                           Or in dot notation: 1.3.36.3.3.2.8.1.1.7.
                           Example 2: the object identifier of the NIST P-384 curve is
                           {iso(1) identified-organization(3) certicom(132) curve(0) 34}.
                           Or in dot notation: 1.3.132.0.34.

                  8.2.3   Hashing algorithms

                        CSM_49

                        Vehicle units and tachograph cards shall support the SHA-256, SHA-384 and SHA-512 algorithms specified in [SHS].

                  8.2.4   Cipher Suites

                        CSM_50

                        In case a symmetric algorithm, an asymmetric algorithm and/or a hashing algorithm are used together to form a security protocol, their respective key lengths and hash sizes shall be of (roughly) equal strength. Table 2 shows the allowed cipher suites:

                           Table 2

                           Allowed cipher suites

                                    Cipher suite Id

                                    ECC key size (bits)

                                    AES key length (bits)

                                    Hashing algorithm

                                    MAC length (bytes)

                                    CS#1

                                    256

                                    128

                                    SHA-256

                                    8

                                    CS#2

                                    384

                                    192

                                    SHA-384

                                    12

                                    CS#3

                                    512/521

                                    256

                                    SHA-512

                                    16

                           Note: ECC keys sizes of 512 bits and 521 bits are considered to be equal in strength for all purposes within this Appendix.

                  9.   KEYS AND CERTIFICATES
            9.1.   Asymmetric Key Pairs and Public Key Certificates

            9.1.1   General

               Note: the keys described in this section are used for mutual authentication and secure messaging between vehicle units and tachograph cards and between vehicle units and external GNSS facilities. These processes are described in detail in chapters 10 and 11 of this Appendix.

                        CSM_51

                        Within the European Smart Tachograph system, ECC key pairs and corresponding certificates shall be generated and managed through three functional hierarchical levels:

                                    —

                                    European level,

                                    —

                                    Member State level,

                                    —

                                    Equipment level.

                        CSM_52

                        Within the entire European Smart Tachograph system, public and private keys and certificates shall be generated, managed and communicated using standardized and secure methods.

                  9.1.2   European Level

                        CSM_53

                        At European level, a single unique ECC key pair designated as EUR shall be generated. It shall consist of a private key (EUR.SK) and a public key (EUR.PK). This key pair shall form the root key pair of the entire European Smart Tachograph PKI. This task shall be handled by a European Root Certificate Authority (ERCA), under the authority and responsibility of the European Commission.

                        CSM_54

                        The ERCA shall use the European private key to sign a (self-signed) root certificate of the European public key, and shall communicate this European root certificate to all Member States.

                        CSM_55

                        The ERCA shall use the European private key to sign the certificates of the Member States public keys upon request. The ERCA shall keep records of all signed Member State public key certificates
[cell cut: 2728155 characters, first 2000000 kept]