xmlns:atom="http://www.w3.org/2005/Atom" xmlns:atom="http://www.w3.org/2005/Atom"
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.
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.
Data downloaded from a VU are signed using Appendix 11 Common Security Mechanisms Part B (Second-generation tachograph system), except when drivers' control is performed by a non EU control authority, using a first generation control card, in which case data are signed using Appendix 11 Common Security Mechanisms Part A (First-generation tachograph system), as requested by Appendix 15 Migration, requirement MIG_015.
This Appendix specifies therefore two types of data downloads from the VU:
Generation 2 type of VU data download, providing the generation 2 data structure, signed using Appendix 11 Common Security Mechanisms Part B,
Generation 1 type of VU data download, providing the generation 1 data structure, signed using Appendix 11 Common Security Mechanisms Part A.
Similarly, there are two types of data downloads from second generation driver cards inserted in a VU, as specified in paragraphs 3 and 4 of this Appendix.]
Textual Amendments
The following acronyms are used in this appendix:
Application Identifier
Answer To Reset
Checksum byte
Dedicated File
Diagnostic Session
Elementary File
External Storage Medium
File Identifier (File ID)
Format Byte (first byte of message header)
Integrated Circuit Card
Intelligent Dedicated Equipment: The equipment used to perform data downloading to the ESM (e.g. Personal Computer)
Interface Device
Keyword Protocol 2000
Length Byte (last byte of message header)
Protocol Parameter Selection
Perform Security Operation
Service Identifier
Source byte
Target Byte
Tag Length Value
Transfer Response Parameter
Transfer Request Parameter
Vehicle Unit