Please note that the date you requested in the address for this web page is not an actual date upon which a change occurred to this item of legislation. You are being shown the legislation from , which is the first date before then upon which a change was made.
ANNEX I CU.K. Requirements for construction, testing, installation, and inspection
Appendix 7
DATA DOWNLOADING PROTOCOLS U.K.
3.TACHOGRAPH CARDS DOWNLOADING PROTOCOLU.K.
3.1. Scope U.K.
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 U.K.
:
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).
:
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 U.K.
[F1DDP_035 The download of a tachograph card includes the following steps: U.K.
Download the common information of the card in the EFs
and
This information is optional and is not secured with a digital signature.
(for first and second generation tachograph cards) Download EFs within
:
Download the EFs
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
) except EF
. This information is secured with a digital signature, using Appendix 11 Common Security Mechanisms Part A.
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:
(for second generation tacograph cards only) Except when a download of a driver card inserted in a VU is performed during drivers' control by a non EU control authority, using a first generation control card, download EFs within
:
Download the EFs CardSignCertificate, CA_Certificate and Link_Certificate (if present). 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
) except EF
. This information is secured with a digital signature, using Appendix 11 Common Security Mechanisms Part B.
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
, in the
and, if applicable,
DFs.
When downloading a workshop card, reset the calibration counter in EF
in the
and, if applicable,
DFs.
When downloading a workshop card the EF
in the
and, if applicable,
DFs shall not be downloaded.]
Textual Amendments
3.3.1 Initialisation sequence U.K.
DDP_036The IDE shall initiate the sequence as follows:U.K.
| 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 U.K.
DDP_037 [F1The sequence to download EFs ICC, IC, Card_Certificate (or CardSignCertificate for DF Tachograph_G2), CA_Certificate and Link_Certificate (for DF Tachograph_G2 only) is as follows:] U.K.
| 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).U.K.
Note 2: Selecting and reading a file may also be performed in one step using a Read Binary command with a short EF identifier.U.K.
3.3.3 Sequence for Signed data files U.K.
DDP_038The following sequence shall be used for each of the following files that has to be downloaded with their signature:U.K.
| [F1Card | 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, part A or B. 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.U.K.
3.3.4 Sequence for resetting the calibration counter. U.K.
DDP_039The sequence to reset the 
counter in the EF 
in a workshop card is the following:U.K.
| 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.U.K.
3.4. Data storage format U.K.
3.4.1 Introduction U.K.
DDP_040The downloaded data has to be stored according to the following conditions:U.K.
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 U.K.
DDP_041The file format is a concatenation of several TLV objects.U.K.
DDP_042The tag for an EF shall be the FID plus the appendix „00“.U.K.
DDP_043The tag of an EF's signature shall be the FID of the file plus the appendix „01“.U.K.
DDP_044The 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.U.K.
DDP_045When a file is not downloaded nothing related to the file shall be stored (no tag and no zero length).U.K.
[F1DDP_046 A signature shall be stored as the next TLV object directly after the TLV object that contains the data of the file. U.K.
| Definition | Meaning | Length |
|---|---|---|
| FID (2 Bytes) || ‘ 00 ’ | Tag for EF (FID) in the  or for common information of the card | 3 Bytes |
| FID (2 Bytes) || ‘ 01 ’ | Tag for Signature of EF (FID) in the  DF | 3 Bytes |
| FID (2 Bytes) || ‘ 02 ’ | Tag for EF (FID) in the  DF | 3 Bytes |
| FID (2 Bytes) || ‘ 03 ’ | Tag for Signature of EF (FID) in the  DF | 3 Bytes |
| xx xx | Length of Value field | 2 Bytes |
Example of data in a download file on an ESM:
