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:

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.

For card data types used for Generation 1 and Generation 2 applications, the size specified in this Appendix is the one for Generation 2 application. The size for Generation 1 application is supposed to be already known by the reader. The Annex IC requirement numbers related to such data types cover both Generation 1 and Generation 2 applications.

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.

Value assignment — Octet Aligned: ‘scpaattttttttttt’B (16 bits)

For Data Memory recordings (or slot status):

For Driver (or Workshop) card recordings (and driver status):

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.

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.

Value assignment: not further specified.

2.4. AES128Key

Generation 2:

An AES128 key.

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.

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.

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’.

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.

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.

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.

Value assignment: see Appendix 2.

2.11. CardApprovalNumber

Type approval number of the card.

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.

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.

icSerialNumber is the IC serial number.

icManufacturingReferences is the IC manufacturer specific identifier.

2.14. CardConsecutiveIndex

A card consecutive index (definition h)).

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).

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).

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).

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).

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

Generation 1:

Information, stored in a driver or workshop card, related to the events associated with the card holder (Annex IC requirements 260 and 318).

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).

Generation 2:

Information, stored in a driver or workshop card, related to the events associated with the card holder (Annex IC requirements 285 and 341).

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).

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).

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).

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).

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).

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.

2.26. CardNumber

A card number as defined by definition g).

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).

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.

2.29. CardPublicKey

The public key of a card.

2.30. CardRenewalIndex

A card renewal index (definition i)).

Value assignment : (see this Annex chapter 7).

Order for increase: ‘ 0, …, 9, A, …, Z ’

2.31. CardReplacementIndex

A card replacement index (definition j)).

Value assignment: (see this Annex chapter VII).

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.

2.33. CardSlotNumber

Code to distinguish between the two slots of a Vehicle Unit.

Value assignment: not further specified.

2.34. CardSlotsStatus

Code indicating the type of cards inserted in the two slots of the vehicle unit.

Value assignment — Octet Aligned: ‘ccccdddd’B

with the following identification codes:

2.35. CardSlotsStatusRecordArray

Generation 2:

The CardSlotsStatus plus metadata as used in the download protocol.

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.

Value assignment: ‘aabb’H:

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:

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:

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).

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).

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).

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:

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:

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.

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.

• 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.

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).

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).

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.

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).

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).

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).

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).

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).

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.

• 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.

Value assignment: not further specified.

2.55. CurrentDateTimeRecordArray

Generation 2:

The current date and time plus metadata as used in the download protocol.

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.

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.

Value assignment:

2.58. DateOfDayDownloaded

Generation 2:

The date and time of the download.

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.

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).

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:

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:

In addition to generation 1 the following data elements are used:

noOfGNSSADRecords is the number of GNSS accumulated driving records the card can store.

noOfSpecificConditionRecords is the number of specific condition records the card can store.

noOfCardVehicleUnitRecords is the number of vehicle units used 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).

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. Reserved for future use

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.

2.65. EmbedderIcAssemblerId

Provides information about the IC embedder.

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

Value assignment: according to ISO/IEC8824-1.

Generation 2

Value assignment: according to ISO/IEC8824-1.

2.67. EquipmentType

Code to distinguish different types of equipment for the tachograph application.

Generation 1:

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:

Note 1: 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.

Note 2: In the CardHolderAuthorisation (CHA) field of a generation 2 certificate, the values (1), (2), and (6) are to be interpreted as indicating a certificate for Mutual Authentication for the respective equipment type. For indicating the respective certificate for creating a digital signature, the values (17), (18) or (19) must be used.

2.68. EuropeanPublicKey

Generation 1:

The European public key.

2.69. EventFaultRecordPurpose

Code explaining why an event or a fault has been recorded.

Value assignment:

2.70. EventFaultType

Code qualifying an event or a fault.

Value assignment:

Generation 1:

Generation 2:

2.71. ExtendedSealIdentifier

Generation 2:

The extended seal identifier uniquely identifies a seal (Annex IC requirement 401).

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:

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:

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.

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.

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.

Value assignment:

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.

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.

2.78. GNSSAccumulatedDriving

Generation 2:

Information, stored in a driver or workshop card, related to the GNSS position of the vehicle if the accumulated driving time reaches a multiple of three hours (Annex IC requirement 306 and 354).

gnssADPointerNewestRecord is the index of the last updated GNSS accumulated driving record.

Value assignment is the number corresponding to the numerator of the GNSS accumulated driving record, beginning with '0' for the first occurrence of the GNSS accumulated driving record in the structure.

gnssAccumulatedDrivingRecords is the set of records containing the date and time the accumulated driving reaches a multiple of three hours and information on the position of the vehicle.

2.79. GNSSAccumulatedDrivingRecord

Generation 2:

Information, stored in a driver or workshop card, related to the GNSS position of the vehicle if the accumulated driving time reaches a multiple of three hours (Annex IC requirement 305 and 353)

timeStamp is the date and time when the accumulated driving time reaches a multiple of three hours.

gnssPlaceRecord contains information related to the position of the vehicle.

vehicleOdometerValue is the odometer value when the accumulated driving time reaches a multiple of three hours.

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).

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.

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.

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.

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.

2.85. K-ConstantOfRecordingEquipment

Constant of the recording equipment (definition m)).

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.

The first choice is suitable to reference the public key of a Vehicle Unit, of a tachograph card or of an external GNSS facility.

The second choice is suitable to reference the public key of a Vehicle Unit (in cases where 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.

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.

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.

Value assignment: not further specified.

2.90. LinkCertificate

Generation 2:

The link certificate between European Root CA key pairs.

2.91. L-TyreCircumference

Effective circumference of the wheel tyres (definition u)).

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 check sum of 8, 12 or 16 bytes length corresponding to the cipher suites specified in Appendix 11.

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).

Value assignment: not further specified.

2.94. ManufacturerCode

Code identifying a manufacturer of type approved equipment.

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.

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.

2.97. MemberStateCertificateRecordArray

Generation 2:

The member state certificate plus metadata as used in the download protocol.

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.

2.99. Name

A name.

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).

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.

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:

Value assignment: see Appendix 2.

Generation 2:

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).

Value assignment: Not specified further.

2.104. NoOfCardPlaceRecords

Number of place records a driver or workshop card can store.

Generation 1:

Value assignment: see Appendix 2.

Generation 2:

Value assignment: see Appendix 2.

2.105. NoOfCardVehicleRecords

Number of vehicles used records a driver or workshop card can store.

Value assignment: see Appendix 2.

2.106. NoOfCardVehicleUnitRecords

Generation 2:

Number of vehicle units used records a driver or workshop card can store.

Value assignment: see Appendix 2.

2.107. NoOfCompanyActivityRecords

Number of company activity records, a company card can store.

Value assignment: see Appendix 2.

2.108. NoOfControlActivityRecords

Number of control activity records, a control card can store.

Value assignment: see Appendix 2.

2.109. NoOfEventsPerType

Number of events per type of event a card can store.

Value assignment: see Appendix 2.

2.110. NoOfFaultsPerType

Number of faults per type of fault a card can store.

Value assignment: see Appendix 2.

2.111. NoOfGNSSADRecords

Generation 2:

Number of GNSS accumulated driving records a card can store.

Value assignment: see Appendix 2.

2.112. NoOfSpecificConditionRecords

Generation 2:

Number of specific condition records a card can store.

Value assignment: see Appendix 2.

2.113. OdometerShort

Odometer value of the vehicle in a short form.

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).

Value assignment: not further specified.

2.115. OdometerValueMidnightRecordArray

Generation 2:

The OdometerValueMidnight plus metadata used in the download protocol.

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.

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:

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:

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:

vehicleRegistrationIdentification is the VRN and the registering Member State of the vehicle.

cardWithdrawalTime is the card withdrawal date and time.

Generation 2:

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.

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.

Value assignment:

2.121. RegionAlpha

Alphabetic reference to a region within a specified country.

Generation 1:

Value assignment:

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.

Generation 1:

Value assignment:

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.

2.124. RSAKeyModulus

Generation 1:

The modulus of a RSA key pair.

Value assignment: Unspecified.

2.125. RSAKeyPrivateExponent

Generation 1:

The private exponent of a RSA key pair.

Value assignment: Unspecified.

2.126. RSAKeyPublicExponent

Generation1:

The public exponent of a RSA key pair.

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.

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.

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.

equipmentType identifies the type of equipment the seal is attached to.

extendedSealIdentifier is the identifier of the seal attached to the equipment.