Search Legislation

Advanced Search

Commission Implementing Regulation (EU) 2016/799Show full 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)

Help about what version

What Version

Help about UK-EU Regulation

Legislation originating from the EU

When the UK left the EU, legislation.gov.uk published EU legislation that had been published by the EU up to IP completion day (31 December 2020 11.00 p.m.). On legislation.gov.uk, these items of legislation are kept up-to-date with any amendments made by the UK since then.

Close

This item of legislation originated from the EU

Legislation.gov.uk publishes the UK version. EUR-Lex publishes the EU version. The EU Exit Web Archive holds a snapshot of EUR-Lex’s version from IP completion day (31 December 2020 11.00 p.m.).

Status:

This is the original version as it was originally adopted in the EU.
This legislation may since have been updated - see the latest available (revised) version

  1. Introductory Text

  2. Article 1.Subject matter and scope

  3. Article 2.Definitions

  4. Article 3.Location-based services

  5. Article 4.Procedure for type-approval of a tachograph and tachograph components

  6. Article 5.Modifications to type-approvals

  7. Article 6.Entry into force

  8. Signature

    1. ANNEX I C

      Requirements for construction, testing, installation, and inspection

      1. INTRODUCTION

      2. 1. DEFINITIONS

      3. 2. GENERAL CHARACTERISTICS AND FUNCTIONS OF THE RECORDING EQUIPMENT

        1. 2.1 General characteristics

          1. (1) The recording equipment includes cables, a motion sensor, and a...

          2. (2) The interface between motion sensors and vehicle units shall comply...

          3. (3) The vehicle unit shall be connected to global navigation satellite...

          4. (4) The vehicle unit shall communicate with remote early detection communication...

          5. (5) The vehicle unit may include an ITS interface, which is...

          6. (6) Any inclusion in or connection to the recording equipment of...

          7. (7) The recording equipment provides selective access rights to data and...

        2. 2.2 Functions

          1. (8) The recording equipment shall ensure the following functions:

        3. 2.3 Modes of operation

          1. (9) The recording equipment shall possess four modes of operation:

          2. (10) The recording equipment shall switch to the following mode of...

          3. (11) The recording equipment shall ignore non-valid cards inserted, except displaying,...

          4. (12) All functions listed in 2.2. shall work in any mode...

          5. (13) The recording equipment can output any data to display, printer...

        4. 2.4 Security

          1. (14) In order to achieve the system security, the following components...

      4. 3. CONSTRUCTION AND FUNCTIONAL REQUIREMENTS FOR RECORDING EQUIPMENT

        1. 3.1 Monitoring cards insertion and withdrawal

          1. (15) The recording equipment shall monitor the card interface devices to...

          2. (16) Upon card insertion the recording equipment shall detect whether the...

          3. (17) First generation tachograph cards shall be considered as non-valid by...

          4. (18) First generation workshop cards which are inserted in the second...

          5. (19) The recording equipment shall be so designed that the tachograph...

          6. (20) The release of tachograph cards may function only when the...

        2. 3.2 Speed, position and distance measurement

          1. (21) The motion sensor (possibly embedded in the adaptor) is the...

          2. (22) This function shall continuously measure and be able to provide...

          3. (23) This function shall continuously measure and be able to provide...

          4. (24) The speed measurement function shall also provide the information whether...

          5. (25) Devices displaying speed (speedometer) and total distance travelled (odometer) installed...

          6. (26) To detect manipulation of motion data, information from the motion...

          7. (27) This function shall measure the position of the vehicle in...

          8. 3.2.1 Measurement of distance travelled

            1. (28) The distance travelled may be measured either:

            2. (29) The recording equipment shall measure distance from 0 to 9...

            3. (30) Distance measured shall be within the following tolerances (distances of...

            4. (31) Distance measured shall have a resolution better than or equal...

          9. 3.2.2 Measurement of speed

            1. (32) The recording equipment shall measure speed from 0 to 220...

            2. (33) To ensure a maximum tolerance on speed displayed of ±...

            3. (34) The speed shall be measured correctly within the normal tolerances...

            4. (35) Speed measurement shall have a resolution better than or equal...

          10. 3.2.3 Measurement of position

            1. (36) The recording equipment shall measure the absolute position of the...

            2. (37) The absolute position is measured in geographical coordinates of latitude...

        3. 3.3 Time measurement

          1. (38) The time measurement function shall measure permanently and digitally provide...

          2. (39) UTC date and time shall be used for dating data...

          3. (40) In order to visualise the local time, it shall be...

          4. (41) Time drift shall be within ± 2 seconds per day...

          5. (42) Time measured shall have a resolution better than or equal...

          6. (43) Time measurement shall not be affected by an external power...

        4. 3.4 Monitoring driver activities

          1. (44) This function shall permanently and separately monitor the activities of...

          2. (45) Driver activity shall be DRIVING, WORK, AVAILABILITY or BREAK/REST.

          3. (46) It shall be possible for the driver and/or the co-driver...

          4. (47) When the vehicle is moving, DRIVING shall be selected automatically...

          5. (48) When the vehicle stops, WORK shall be selected automatically for...

          6. (49) The first change of activity to REST or AVAILABILITY arising...

          7. (50) This function shall output activity changes to the recording functions...

          8. (51) Given a calendar minute, if DRIVING is registered as the...

          9. (52) Given a calendar minute that is not regarded as DRIVING...

          10. (53) This function shall also permanently monitor the continuous driving time...

        5. 3.5 Monitoring driving status

          1. (54) This function shall permanently and automatically monitor the driving status....

          2. (55) The driving status CREW shall be selected when two valid...

        6. 3.6 Driver's entries

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

            1. (56) This function shall allow for the entry of places where,...

            2. (57) Places are defined as the country and, in addition where...

            3. (58) At the time of a driver card withdrawal, the recording...

            4. (59) The driver shall then enter the current place of the...

            5. (60) It shall be possible to input places where daily work...

          2. 3.6.2 Manual entry of driver activities and driver consent for ITS...

            1. (61) Upon driver (or workshop) card insertion, and only at this...

          3. 3.6.3 Entry of specific conditions

            1. (62) The recording equipment shall allow the driver to enter, in...

        7. 3.7 Company locks management

          1. (63) This function shall allow the management of the locks placed...

          2. (64) Company locks consist in a start date/time (lock-in) and an...

          3. (65) Locks may be turned ‘in’ or ‘out’ in real time...

          4. (66) Locking-out shall only be possible for the company whose lock...

          5. (67) Locking-out shall be automatic if another company locks in.

          6. (68) In the case where a company locks in and where...

        8. 3.8 Monitoring control activities

          1. (69) This function shall monitor DISPLAYING, PRINTING, VU and card DOWNLOADING,...

          2. (70) This function shall also monitor OVER SPEEDING CONTROL activities while...

        9. 3.9 Detection of events and/or faults

          1. (71) This function shall detect the following events and/or faults:

          2. 3.9.1 ‘Insertion of a non-valid card’ event

            1. (72) This event shall be triggered at the insertion of any...

          3. 3.9.2 ‘Card conflict’ event

            1. (73) This event shall be triggered when any of the valid...

          4. 3.9.3 ‘Time overlap’ event

            1. (74) This event shall be triggered when the date / time...

          5. 3.9.4 ‘Driving without an appropriate card’ event

            1. (75) This event shall be triggered for any valid tachograph cards...

          6. 3.9.5 ‘Card insertion while driving’ event

            1. (76) This event shall be triggered when a tachograph card is...

          7. 3.9.6 ‘Last card session not correctly closed’ event

            1. (77) This event shall be triggered when at card insertion the...

          8. 3.9.7 ‘Over speeding’ event

            1. (78) This event shall be triggered for each over speeding.

          9. 3.9.8 ‘Power supply interruption’ event

            1. (79) This event shall be triggered, while not in calibration or...

          10. 3.9.9 ‘Communication error with the remote communication facility’ event

            1. (80) This event shall be triggered, while not in calibration mode,...

          11. 3.9.10 ‘Absence of position information from GNSS receiver’ event

            1. (81) This event shall be triggered, while not in calibration mode,...

          12. 3.9.11 ‘Communication error with the external GNSS facility’ event

            1. (82) This event shall be triggered, while not in calibration mode,...

          13. 3.9.12 ‘Motion data error’ event

            1. (83) This event shall be triggered, while not in calibration mode,...

          14. 3.9.13 ‘Vehicle motion conflict’ event

            1. (84) This event shall be triggered, while not in calibration mode,...

          15. 3.9.14 ‘Security breach attempt’ event

            1. (85) This event shall be triggered for any other event affecting...

          16. 3.9.15 ‘Time conflict’ event

            1. (86) This event shall be triggered, while not in calibration mode,...

          17. 3.9.16 ‘Card’ fault

            1. (87) This fault shall be triggered when a tachograph card failure...

          18. 3.9.17 ‘Recording equipment’ fault

            1. (88) This fault shall be triggered for any of these failures,...

        10. 3.10 Built-in and self-tests

          1. (89) The recording equipment shall self-detect faults through self-tests and built-in-tests,...

        11. 3.11 Reading from data memory

          1. (90) The recording equipment shall be able to read any data...

        12. 3.12 Recording and storing in the data memory

          1. (91) Data stored into the data memory shall not be affected...

          2. (92) The recording equipment shall be able to record and store...

          3. 3.12.1 Equipment identification data

            1. 3.12.1.1 Vehicle unit identification data

              1. (93) The recording equipment shall be able to store in its...

              2. (94) Vehicle unit identification data are recorded and stored once and...

            2. 3.12.1.2 Motion sensor identification data

              1. (95) The motion sensor shall be able to store in its...

              2. (96) Motion sensor identification data are recorded and stored once and...

              3. (97) The vehicle unit shall be able to record and store...

            3. 3.12.1.3 Global Navigation Satellite Systems identification data

              1. (98) The external GNSS facility shall be able to store in...

              2. (99) The identification data are recorded and stored once and for...

              3. (100) The vehicle unit shall be able to record and store...

          4. 3.12.2 Keys and certificates

            1. (101) The recording equipment shall be able to store a number...

          5. 3.12.3 Driver or workshop card insertion and withdrawal data

            1. (102) For each insertion and withdrawal cycle of a driver or...

            2. (103) The data memory shall be able to hold these data...

            3. (104) When storage capacity is exhausted, new data shall replace oldest...

          6. 3.12.4 Driver activity data

            1. (105) The recording equipment shall record and store in its data...

            2. (106) The data memory shall be able to hold driver activity...

            3. (107) When storage capacity is exhausted, new data shall replace oldest...

          7. 3.12.5 Places and positions where daily work periods begin, end, and/or...

            1. (108) The recording equipment shall record and store in its data...

            2. (109) When the position of the vehicle is not available from...

            3. (110) Together with each place or position, the recording equipment shall...

            4. (111) The data memory shall be able to hold places and...

            5. (112) When storage capacity is exhausted, new data shall replace oldest...

          8. 3.12.6 Odometer data

            1. (113) The recording equipment shall record in its data memory the...

            2. (114) The data memory shall be able to store midnight odometer...

            3. (115) When storage capacity is exhausted, new data shall replace oldest...

          9. 3.12.7 Detailed speed data

            1. (116) The recording equipment shall record and store in its data...

          10. 3.12.8 Events data

            1. (117) The recording equipment shall record and store in its data...

          11. 3.12.9 Faults data

            1. (118) The recording equipment shall attempt to record and store in...

          12. 3.12.10 Calibration data

            1. (119) The recording equipment shall record and store in its data...

            2. (120) The following data shall be recorded for each of these...

            3. (121) In addition, the recording equipment shall record and store in...

            4. (122) The motion sensor shall record and store in its memory...

            5. (123) The external GNSS facility shall record and store in its...

          13. 3.12.11 Time adjustment data

            1. (124) The recording equipment shall record and store in its data...

            2. (125) The following data shall be recorded for each of these...

          14. 3.12.12 Control activity data

            1. (126) The recording equipment shall record and store in its data...

            2. (127) In case of downloading, the dates of the oldest and...

          15. 3.12.13 Company locks data

            1. (128) The recording equipment shall record and store in its data...

          16. 3.12.14 Download activity data

            1. (129) The recording equipment shall record and store in its data...

          17. 3.12.15 Specific conditions data

            1. (130) The recording equipment shall record in its data memory the...

            2. (131) The data memory shall be able to hold specific conditions...

          18. 3.12.16 Tachograph card data

            1. (132) The recording equipment shall be able to store the following...

            2. (133) The recording equipment shall be able to store at least...

        13. 3.13 Reading from tachograph cards

          1. (134) The recording equipment shall be able to read from first...

          2. (135) In case of a reading error, the recording equipment shall...

        14. 3.14 Recording and storing on tachograph cards

          1. 3.14.1 Recording and storing in first generation tachograph cards

            1. (136) Provided first generation tachograph cards use has not been suppressed...

            2. (137) The recording equipment shall set the ‘card session data’ in...

            3. (138) The recording equipment shall update data stored on valid driver,...

            4. (139) The recording equipment shall update driver activity and places data...

            5. (140) All events not defined for the first generation recording equipment,...

            6. (141) Tachograph cards data update shall be such that, when needed...

            7. (142) In the case of a writing error, the recording equipment...

            8. (143) Before releasing a driver card and after all relevant data...

          2. 3.14.2 Recording and storing in second generation tachograph cards

            1. (144) Second generation tachograph cards shall contain 2 different card applications,...

            2. (145) The recording equipment shall set the ‘card session data’ in...

            3. (146) The recording equipment shall update data stored on the 2...

            4. (147) The recording equipment shall update driver activity places and positions...

            5. (148) Tachograph cards data update shall be such that, when needed...

            6. (149) In the case of a writing error, the recording equipment...

            7. (150) Before releasing a driver card and after all relevant data...

        15. 3.15 Displaying

          1. (151) The display shall include at least 20 characters.

          2. (152) The minimum character size shall be 5 mm high and...

          3. (153) The display shall support the characters specified in Appendix 1...

          4. (154) The display shall be provided with adequate non-dazzling lighting.

          5. (155) Indications shall be visible from outside the recording equipment.

          6. (156) The recording equipment shall be able to display:

          7. (157) The display of the recording equipment shall use the pictograms...

          8. (158) The display shall always be ON when the vehicle is...

          9. (159) The recording equipment may include a manual or automatic feature...

          10. 3.15.1 Default display

            1. (160) When no other information needs to be displayed, the recording...

            2. (161) Display of data related to each driver shall be clear,...

            3. (162) In the case where the display width does not allow...

            4. (163) The recording equipment shall briefly display the card holder name...

            5. (164) When an ‘OUT OF SCOPE’ or FERRY/TRAIN condition is opened,...

          11. 3.15.2 Warning display

            1. (165) The recording equipment shall display warning information using primarily the...

          12. 3.15.3 Menu access

            1. (166) The recording equipment shall provide necessary commands through an appropriate...

          13. 3.15.4 Other displays

            1. (167) It shall be possible to display selectively on request:

            2. (168) Printout content display shall be sequential, line by line. If...

        16. 3.16 Printing

          1. (169) The recording equipment shall be able to print information from...

          2. (170) The ‘driver activities from card daily printout’ and ‘Events and...

          3. (171) In order to produce the ‘driver activities from card daily...

          4. (172) The printer shall be able to print 24 characters per...

          5. (173) The minimum character size shall be 2.1 mm high and...

          6. (174) The printer shall support the characters specified in Appendix 1...

          7. (175) Printers shall be so designed as to produce these printouts...

          8. (176) Printouts shall retain their dimensions and recordings under normal conditions...

          9. (177) The type approved paper used by the recording equipment shall...

          10. (178) Printouts shall remain clearly legible and identifiable under normal conditions...

          11. (179) Printouts shall conform at least to the test specifications defined...

          12. (180) It shall also be possible to add hand-written notes, such...

          13. (181) The recording equipment shall manage ‘paper out’ events while printing...

        17. 3.17 Warnings

          1. (182) The recording equipment shall warn the driver when detecting any...

          2. (183) Warning of a power supply interruption event may be delayed...

          3. (184) The recording equipment shall warn the driver 15 minutes before...

          4. (185) Warnings shall be visual. Audible warnings may also be provided...

          5. (186) Visual warnings shall be clearly recognisable by the user, shall...

          6. (187) Visual warnings may be built into the recording equipment and/or...

          7. (188) In the latter case it shall bear a ‘T’ symbol....

          8. (189) Warnings shall have a duration of at least 30 seconds,...

          9. (190) Warning cause shall be displayed on the recording equipment and...

          10. (191) Additional warnings may be provided, as long as they do...

        18. 3.18 Data downloading to external media

          1. (192) The recording equipment shall be able to download on request...

          2. (193) In addition and as an optional feature, the recording equipment...

          3. (194) Downloading shall not alter or delete any stored data.

          4. (195) The calibration/downloading connector electrical interface is specified in Appendix 6....

          5. (196) Downloading protocols are specified in Appendix 7.

        19. 3.19 Remote communication for targeted roadside checks

          1. (197) When the ignition is on, the Vehicle Unit shall store...

          2. (198) Data to be checked remotely shall be available to remote...

          3. (199) Data necessary for the purpose of targeted roadside checks shall...

        20. 3.20 Output data to additional external devices

          1. (200) The recording equipment may also be equipped with standardised interfaces...

          2. (201) The serial link interface as specified in Annex 1B to...

        21. 3.21 Calibration

          1. (202) The calibration function shall allow:

          2. (203) In addition, the calibration function shall allow to supress the...

          3. (204) Pairing the motion sensor to the VU shall consist, at...

          4. (205) Coupling the external GNSS facility to the VU shall consist,...

          5. (206) The calibration function shall be able to input necessary data...

        22. 3.22 Roadside calibration checking

          1. (207) The roadside calibration checking function shall allow reading the motion...

          2. (208) This reading shall at least be possible on the vehicle...

          3. (209) The roadside calibration checking function shall also allow controlling the...

        23. 3.23 Time adjustment

          1. (210) The time adjustment function shall allow for automatically adjusting the...

          2. (211) The time setting of the VU internal clock shall be...

          3. (212) The time adjustment function shall also allow for triggered adjustment...

        24. 3.24 Performance characteristics

          1. (213) The Vehicle Unit shall be fully operational in the temperature...

          2. (214) The tachograph shall be fully operational in the humidity range...

          3. (215) The seals used in the smart tachograph shall withstand the...

          4. (216) The recording equipment shall be protected against over-voltage, inversion of...

          5. (217) Motion sensors shall either:

          6. (218) The recording equipment and the external GNSS facility shall conform...

        25. 3.25 Materials

          1. (219) All the constituent parts of the recording equipment shall be...

          2. (220) For normal conditions of use, all the internal parts of...

          3. (221) The Vehicle Unit and the external GNSS facility shall meet...

          4. (222) The recording equipment shall conform to applicable technical specifications related...

          5. (223) The recording equipment shall be protected against accidental damage.

        26. 3.26 Markings

          1. (224) If the recording equipment displays the vehicle odometer value and...

          2. (225) A descriptive plaque shall be affixed to each separate component...

          3. (226) When physical space is not sufficient to show all above...

      5. 4. CONSTRUCTION AND FUNCTIONAL REQUIREMENTS FOR TACHOGRAPH CARDS

        1. 4.1 Visible data

          1. (227) the words ‘Driver card’ or ‘Control card’ or ‘Workshop card’...

          2. (228) the name of the Member State issuing the card (optional);...

          3. (229) the distinguishing sign of the Member State issuing the card,...

          4. (230) information specific to the card issued, numbered as follows:

          5. (231) dates shall be written using a ‘dd/mm/yyyy’ or ‘dd.mm.yyyy’ format...

          6. (232) an explanation of the numbered items which appear on the...

          7. (233) with the specific written agreement of the holder, information which...

          8. (234) Tachograph cards shall be printed with the following background predominant...

          9. (235) Tachograph cards shall bear at least the following features for...

          10. (236) After consulting the Commission, Member States may add colours or...

          11. (237) Temporary cards referred to in Article 26.4 of Regulation (EU)...

        2. 4.2 Security

          1. (238) In order to achieve the system security, the tachograph cards...

          2. (239) Tachograph cards shall be readable by other equipment such as...

        3. 4.3 Standards

          1. (240) Tachograph cards shall comply with the following standards:

        4. 4.4 Environmental and electrical specifications

          1. (241) Tachograph cards shall be capable of operating correctly in all...

          2. (242) Tachograph cards shall be capable of operating correctly in the...

          3. (243) Tachograph cards shall be capable of operating correctly for a...

          4. (244) During operation, tachograph cards shall conform to ECE R10, related...

        5. 4.5 Data storage

          1. (245) This paragraph specifies minimum storage capacity for the various application...

          2. (246) Any additional data that may be stored on tachograph cards,...

          3. (247) Each Master File (MF) of any tachograph card shall contain...

          4. 4.5.1 Elementary files for identification and card management

          5. 4.5.2 IC card identification

            1. (248) Tachograph cards shall be able to store the following smart...

            2. 4.5.2.1 Chip identification

              1. (249) Tachograph cards shall be able to store the following Integrated...

            3. 4.5.2.2 DIR (only present in second generation tachograph cards)

              1. (250) Tachograph cards shall be able to store the application identification...

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

              1. (251) Tachograph cards shall be able to store the following extended...

            5. 4.5.2.4 Extended length information (conditional, only present in second generation tachograph...

              1. (252) Tachograph cards shall be able to store the following extended...

          6. 4.5.3 Driver card

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

              1. 4.5.3.1.1 Application identification

                1. (253) The driver card shall be able to store the following...

              2. 4.5.3.1.2 Key and certificates

                1. (254) The driver card shall be able to store a number...

              3. 4.5.3.1.3 Card identification

                1. (255) The driver card shall be able to store the following...

              4. 4.5.3.1.4 Card holder identification

                1. (256) The driver card shall be able to store the following...

              5. 4.5.3.1.5 Card download

                1. (257) The driver card shall be able to store the following...

                2. (258) The driver card shall be able to hold one such...

              6. 4.5.3.1.6 Driving licence information

                1. (259) The driver card shall be able to store the following...

              7. 4.5.3.1.7 Events data

                1. (260) The driver card shall be able to store data related...

                2. (261) The driver card shall be able to store the following...

                3. (262) The driver card shall be able to store data for...

              8. 4.5.3.1.8 Faults data

                1. (263) The driver card shall be able to store data related...

                2. (264) The driver card shall be able to store the following...

                3. (265) The driver card shall be able to store data for...

              9. 4.5.3.1.9 Driver activity data

                1. (266) The driver card shall be able to store, for each...

                2. (267) The driver card memory shall be able to hold driver...

                3. (268) The data listed under requirements 261, 264 and 266 shall...

              10. 4.5.3.1.10 Vehicles used data

                1. (269) The driver card shall be able to store, for each...

                2. (270) The driver card shall be able to store at least...

              11. 4.5.3.1.11 Places where daily work periods start and/or end

                1. (271) The driver card shall be able to store the following...

                2. (272) The driver card memory shall be able to hold at...

              12. 4.5.3.1.12 Card session data

                1. (273) The driver card shall be able to store data related...

              13. 4.5.3.1.13 Control activity data

                1. (274) The driver card shall be able to store the following...

                2. (275) The driver card shall be able to hold one such...

              14. 4.5.3.1.14 Specific conditions data

                1. (276) The driver card shall be able to store the following...

                2. (277) The driver card shall be able to store at least...

            2. 4.5.3.2 Tachograph generation 2 application (not accessible to first generation vehicle...

              1. 4.5.3.2.1 Application identification

                1. (278) The driver card shall be able to store the following...

              2. 4.5.3.2.2 Keys and certificates

                1. (279) The driver card shall be able to store a number...

              3. 4.5.3.2.3 Card identification

                1. (280) The driver card shall be able to store the following...

              4. 4.5.3.2.4 Card holder identification

                1. (281) The driver card shall be able to store the following...

              5. 4.5.3.2.5 Card download

                1. (282) The driver card shall be able to store the following...

                2. (283) The driver card shall be able to hold one such...

              6. 4.5.3.2.6 Driving licence information

                1. (284) The driver card shall be able to store the following...

              7. 4.5.3.2.7 Events data

                1. (285) The driver card shall be able to store data related...

                2. (286) The driver card shall be able to store the following...

                3. (287) The driver card shall be able to store data for...

              8. 4.5.3.2.8 Faults data

                1. (288) The driver card shall be able to store data related...

                2. (289) The driver card shall be able to store the following...

                3. (290) The driver card shall be able to store data for...

              9. 4.5.3.2.9 Driver activity data

                1. (291) The driver card shall be able to store, for each...

                2. (292) The driver card memory shall be able to hold driver...

                3. (293) The data listed under requirements 286, 289 and 291 shall...

              10. 4.5.3.2.10 Vehicles used data

                1. (294) The driver card shall be able to store, for each...

                2. (295) The driver card shall be able to store at least...

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

                1. (296) The driver card shall be able to store the following...

                2. (297) The driver card memory shall be able to hold at...

              12. 4.5.3.2.12 Card session data

                1. (298) The driver card shall be able to store data related...

              13. 4.5.3.2.13 Control activity data

                1. (299) The driver card shall be able to store the following...

                2. (300) The driver card shall be able to hold one such...

              14. 4.5.3.2.14 Specific conditions data

                1. (301) The driver card shall be able to store the following...

                2. (302) The driver card shall be able to store at least...

              15. 4.5.3.2.15 Vehicle units used data

                1. (303) The driver card shall be able to store the following...

                2. (304) The driver card shall be able to store at least...

              16. 4.5.3.2.16 Three hours' continuous driving places data

                1. (305) The driver card shall be able to store the following...

                2. (306) The driver card shall be able to store at least...

          7. 4.5.4 Workshop card

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

              1. 4.5.4.1.1 Application identification

                1. (307) The workshop card shall be able to store the following...

              2. 4.5.4.1.2 Keys and certificates

                1. (308) The workshop card shall be able to store a number...

                2. (309) The workshop card shall be able to store a Personal...

              3. 4.5.4.1.3 Card identification

                1. (310) The workshop card shall be able to store the following...

              4. 4.5.4.1.4 Card holder identification

                1. (311) The workshop card shall be able to store the following...

              5. 4.5.4.1.5 Card download

                1. (312) The workshop card shall be able to store a card...

              6. 4.5.4.1.6 Calibration and time adjustment data

                1. (313) The workshop card shall be able to hold records of...

                2. (314) Each calibration record shall be able to hold the following...

                3. (315) The workshop card shall be able to store at least...

                4. (316) The workshop card shall hold a counter indicating the total...

                5. (317) The workshop card shall hold a counter indicating the number...

              7. 4.5.4.1.7 Events and faults data

                1. (318) The workshop card shall be able to store events and...

                2. (319) The workshop card shall be able to store data for...

              8. 4.5.4.1.8 Driver activity data

                1. (320) The workshop card shall be able to store driver activity...

                2. (321) The workshop card shall be able to hold driver activity...

              9. 4.5.4.1.9 Vehicles used data

                1. (322) The workshop card shall be able to store vehicles used...

                2. (323) The workshop card shall be able to store at least...

              10. 4.5.4.1.10 Daily work periods start and/or end data

                1. (324) The workshop card shall be able to store daily works...

                2. (325) The workshop card shall be able to hold at least...

              11. 4.5.4.1.11 Card session data

                1. (326) The workshop card shall be able to store a card...

              12. 4.5.4.1.12 Control activity data

                1. (327) The workshop card shall be able to store a control...

              13. 4.5.4.1.13 Specific conditions data

                1. (328) The workshop card shall be able to store data relevant...

                2. (329) The workshop card shall be able to store at least...

            2. 4.5.4.2 Tachograph generation 2 application (not accessible to first generation vehicle...

              1. 4.5.4.2.1 Application identification

                1. (330) The workshop card shall be able to store the following...

              2. 4.5.4.2.2 Keys and certificates

                1. (331) The workshop card shall be able to store a number...

                2. (332) The workshop card shall be able to store a Personal...

              3. 4.5.4.2.3 Card identification

                1. (333) The workshop card shall be able to store the following...

              4. 4.5.4.2.4 Card holder identification

                1. (334) The workshop card shall be able to store the following...

              5. 4.5.4.2.5 Card download

                1. (335) The workshop card shall be able to store a card...

              6. 4.5.4.2.6 Calibration and time adjustment data

                1. (336) The workshop card shall be able to hold records of...

                2. (337) Each calibration record shall be able to hold the following...

                3. (338) The workshop card shall be able to store at least...

                4. (339) The workshop card shall hold a counter indicating the total...

                5. (340) The workshop card shall hold a counter indicating the number...

              7. 4.5.4.2.7 Events and faults data

                1. (341) The workshop card shall be able to store events and...

                2. (342) The workshop card shall be able to store data for...

              8. 4.5.4.2.8 Driver activity data

                1. (343) The workshop card shall be able to store driver activity...

                2. (344) The workshop card shall be able to hold driver activity...

              9. 4.5.4.2.9 Vehicles used data

                1. (345) The workshop card shall be able to store vehicles used...

                2. (346) The workshop card shall be able to store at least...

              10. 4.5.4.2.10 Daily work periods start and/or end data

                1. (347) The workshop card shall be able to store daily works...

                2. (348) The workshop card shall be able to hold at least...

              11. 4.5.4.2.11 Card session data

                1. (349) The workshop card shall be able to store a card...

              12. 4.5.4.2.12 Control activity data

                1. (350) The workshop card shall be able to store a control...

              13. 4.5.4.2.13 Vehicle units used data

                1. (351) The workshop card shall be able to store the following...

                2. (352) The workshop card shall be able to store at least...

              14. 4.5.4.2.14 Three hours' continuous driving places data

                1. (353) The workshop card shall be able to store the following...

                2. (354) The workshop card shall be able to store at least...

              15. 4.5.4.2.15 Specific conditions data

                1. (355) The workshop card shall be able to store data relevant...

                2. (356) The workshop card shall be able to store at least...

          8. 4.5.5 Control card

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

              1. 4.5.5.1.1 Application identification

                1. (357) The control card shall be able to store the following...

              2. 4.5.5.1.2 Keys and certificates

                1. (358) The control card shall be able to store a number...

              3. 4.5.5.1.3 Card identification

                1. (359) The control card shall be able to store the following...

              4. 4.5.5.1.4 Card holder identification

                1. (360) The control card shall be able to store the following...

              5. 4.5.5.1.5 Control activity data

                1. (361) The control card shall be able to store the following...

                2. (362) The control card shall be able to hold at least...

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

              1. 4.5.5.2.1 Application identification

                1. (363) The control card shall be able to store the following...

              2. 4.5.5.2.2 Keys and certificates

                1. (364) The control card shall be able to store a number...

              3. 4.5.5.2.3 Card identification

                1. (365) The control card shall be able to store the following...

              4. 4.5.5.2.4 Card holder identification

                1. (366) The control card shall be able to store the following...

              5. 4.5.5.2.5 Control activity data

                1. (367) The control card shall be able to store the following...

                2. (368) The control card shall be able to hold at least...

          9. 4.5.6 Company card

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

              1. 4.5.6.1.1 Application identification

                1. (369) The company card shall be able to store the following...

              2. 4.5.6.1.2 Keys and Certificates

                1. (370) The company card shall be able to store a number...

              3. 4.5.6.1.3 Card identification

                1. (371) The company card shall be able to store the following...

              4. 4.5.6.1.4 Card holder identification

                1. (372) The company card shall be able to store the following...

              5. 4.5.6.1.5 Company activity data

                1. (373) The company card shall be able to store the following...

                2. (374) The company card shall be able to hold at least...

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

              1. 4.5.6.2.1 Application identification

                1. (375) The company card shall be able to store the following...

              2. 4.5.6.2.2 Keys and certificates

                1. (376) The company card shall be able to store a number...

              3. 4.5.6.2.3 Card identification

                1. (377) The company card shall be able to store the following...

              4. 4.5.6.2.4 Card holder identification

                1. (378) The company card shall be able to store the following...

              5. 4.5.6.2.5 Company activity data

                1. (379) The company card shall be able to store the following...

                2. (380) The company card shall be able to hold at least...

      6. 5. INSTALLATION OF RECORDING EQUIPMENT

        1. 5.1 Installation

          1. (381) New recording equipment shall be delivered non-activated to fitters or...

          2. (382) Before its activation, the recording equipment shall give access to...

          3. (383) Before its activation, the recording equipment shall neither record nor...

          4. (384) During installation, vehicle manufacturers shall pre-set all known parameters.

          5. (385) Vehicle manufacturers or fitters shall activate the installed recording equipment...

          6. (386) The activation of the recording equipment shall be triggered automatically...

          7. (387) Specific pairing operations required between the motion sensor and the...

          8. (388) In a similar way, specific coupling operations between the external...

          9. (389) After its activation, the recording equipment shall fully enforce functions...

          10. (390) After its activation, the recording equipment shall communicate to the...

          11. (391) The recording and storing functions of the recording equipment shall...

          12. (392) Installation shall be followed by a calibration. The first calibration...

          13. (393) The installation of an external GNSS facility requires the coupling...

          14. (394) The recording equipment must be positioned in the vehicle in...

        2. 5.2 Installation plaque

          1. (395) After the recording equipment has been checked on installation, an...

          2. (396) The plaque shall bear at least the following details:

          3. (397) For M1 and N1 vehicles only, and which are fitted...

        3. 5.3 Sealing

          1. (398) The following parts shall be sealed:

          2. (399) The seals mentioned above may be removed:

          3. (400) On each occasion that these seals are broken a written...

          4. (401) Seals shall hold an identification number, allocated by its manufacturer....

          5. (402) The seals shall have a free space where approved fitters,...

          6. (403) Seals manufacturers shall be registered in a dedicated database and...

          7. (404) Approved workshops and vehicle manufacturers shall, in the frame of...

          8. (405) Seal manufacturers and their distributors shall maintain full traceability records...

          9. (406) Seals unique identification numbers shall be visible on the installation...

      7. 6. CHECKS, INSPECTIONS AND REPAIRS

        1. 6.1 Approval of fitters, workshops and vehicle manufacturers

        2. 6.2 Check of new or repaired instruments

          1. (407) Every individual device, whether new or repaired, shall be checked...

        3. 6.3 Installation inspection

          1. (408) When being fitted to a vehicle, the whole installation (including...

        4. 6.4 Periodic inspections

          1. (409) Periodic inspections of the equipment fitted to the vehicles shall...

          2. (410) These inspections shall include the following checks:

          3. (411) If one of the events listed in Chapter 3.9 (Detection...

          4. (412) Workshops shall keep traces in their inspection reports of any...

          5. (413) These inspections shall include a calibration and a preventive replacement...

        5. 6.5 Measurement of errors

          1. (414) The measurement of errors on installation and during use shall...

        6. 6.6 Repairs

          1. (415) Workshops shall be able to download data from the recording...

          2. (416) Approved workshops shall issue to transport companies a certificate of...

      8. 7. CARD ISSUING

        1. (417) The card number of the first issue of a tachograph...

        2. (418) The card numbers of all non-personal tachograph cards issued to...

        3. (419) A tachograph card issued in replacement of an existing tachograph...

        4. (420) A tachograph card issued in replacement of an existing tachograph...

        5. (421) A tachograph card issued in renewal of an existing tachograph...

        6. (422) The exchange of an existing tachograph card, in order to...

        7. (423) The ‘card holder surname’ for non-personal workshop or control cards...

        8. (424) Member States shall exchange data electronically in order to ensure...

      9. 8. TYPE-APPROVAL OF RECORDING EQUIPMENT AND TACHOGRAPH CARDS

        1. 8.1 General points

          1. (425) Recording equipment shall be submitted for approval complete with any...

          2. (426) Type approval of recording equipment and of tachograph cards shall...

          3. (427) Member States type approval authorities will not grant a type...

          4. (428) Any modification in software or hardware of the equipment or...

          5. (429) Procedures to upgrade in-situ recording equipment software shall be approved...

          6. (430) Type approval of software modifications aimed to upgrade a previously...

        2. 8.2 Security certificate

          1. (431) The security certificate is delivered in accordance with the provisions...

          2. (432) In the exceptional circumstance that the security certification authorities refuse...

          3. (433) In this circumstance the Member State concerned shall, without delay,...

        3. 8.3 Functional certificate

          1. (434) Each candidate for type approval shall provide the Member State's...

          2. (435) Manufacturers shall provide the relevant samples of type approval candidate...

          3. (436) A functional certificate shall be delivered to the manufacturer only...

          4. (437) The type approval authority delivers the functional certificate. This certificate...

          5. (438) The functional certificate of any recording equipment component shall also...

          6. (439) The functional certificate of any recording equipment component shall also...

        4. 8.4 Interoperability certificate

          1. (440) Interoperability tests are carried out by a single laboratory under...

          2. (441) The laboratory shall register interoperability test requests introduced by manufacturers...

          3. (442) Requests will be officially registered only when the laboratory is...

          4. (443) No interoperability tests shall be carried out by the laboratory,...

          5. (444) Any manufacturer requesting interoperability tests shall commit to leave to...

          6. (445) The interoperability tests shall be carried out, in accordance with...

          7. (446) The interoperability tests shall cover all generations of recording equipment...

          8. (447) The interoperability certificate shall be delivered by the laboratory to...

          9. (448) If the interoperability tests are not successful with one or...

          10. (449) The interoperability certificate is valid for six months. It is...

          11. (450) Any element that could be at the origin of an...

        5. 8.5 Type-approval certificate

          1. (451) The type approval authority of the Member State may deliver...

          2. (452) The type approval certificate of any recording equipment component shall...

          3. (453) The type approval certificate shall be copied by the type...

          4. (454) The laboratory competent for interoperability tests shall run a public...

        6. 8.6 Exceptional procedure: first interoperability certificates for 2nd generation recording equipment...

          1. (455) Until four months after a first couple of 2nd generation...

          2. (456) If at the end of this period, all products concerned...

          3. (457) If during this period, interoperability faults are found, the laboratory...

          4. (458) If at the end of this period, interoperability problems still...

          5. (459) Any request for interoperability tests, registered by the laboratory between...

      10. Appendix 1

        DATA DICTIONARY

        1. 1. INTRODUCTION

          1. 1.1. Approach for definitions of data types

          2. 1.2. References

        2. 2. DATA TYPE DEFINITIONS

          1. 2.1. ActivityChangeInfo

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

            2. Note for the case ‘card withdrawal’:

          2. 2.2. Address

          3. 2.3. AESKey

          4. 2.4. AES128Key

          5. 2.5. AES192Key

          6. 2.6. AES256Key

          7. 2.7. BCDString

          8. 2.8. CalibrationPurpose

          9. 2.9. CardActivityDailyRecord

          10. 2.10. CardActivityLengthRange

          11. 2.11. CardApprovalNumber

          12. 2.12. CardCertificate

          13. 2.13. CardChipIdentification

          14. 2.14. CardConsecutiveIndex

          15. 2.15. CardControlActivityDataRecord

          16. 2.16. CardCurrentUse

          17. 2.17. CardDriverActivity

          18. 2.18. CardDrivingLicenceInformation

          19. 2.19. CardEventData

          20. 2.20. CardEventRecord

          21. 2.21. CardFaultData

          22. 2.22. CardFaultRecord

          23. 2.23. CardIccIdentification

          24. 2.24. CardIdentification

          25. 2.25. CardMACertificate

          26. 2.26. CardNumber

          27. 2.27. CardPlaceDailyWorkPeriod

          28. 2.28. CardPrivateKey

          29. 2.29. CardPublicKey

          30. 2.30. CardRenewalIndex

          31. 2.31. CardReplacementIndex

          32. 2.32. CardSignCertificate

          33. 2.33. CardSlotNumber

          34. 2.34. CardSlotsStatus

          35. 2.35. CardSlotsStatusRecordArray

          36. 2.36. CardStructureVersion

          37. 2.37. CardVehicleRecord

          38. 2.38. CardVehiclesUsed

          39. 2.39. CardVehicleUnitRecord

          40. 2.40. CardVehicleUnitsUsed

          41. 2.41. Certificate

          42. 2.42. CertificateContent

          43. 2.43. CertificateHolderAuthorisation

          44. 2.44. CertificateRequestID

          45. 2.45. CertificationAuthorityKID

          46. 2.46. CompanyActivityData

          47. 2.47. CompanyActivityType

          48. 2.48. CompanyCardApplicationIdentification

          49. 2.49. CompanyCardHolderIdentification

          50. 2.50. ControlCardApplicationIdentification

          51. 2.51. ControlCardControlActivityData

          52. 2.52. ControlCardHolderIdentification

          53. 2.53. ControlType

          54. 2.54. CurrentDateTime

          55. 2.55. CurrentDateTimeRecordArray

          56. 2.56. DailyPresenceCounter

          57. 2.57. Datef

          58. 2.58. DateOfDayDownloaded

          59. 2.59. DateOfDayDownloadedRecordArray

          60. 2.60. Distance

          61. 2.61. DriverCardApplicationIdentification

          62. 2.62. DriverCardHolderIdentification

          63. 2.63. DSRCSecurityData

          64. 2.64. EGFCertificate

          65. 2.65. EmbedderIcAssemblerId

          66. 2.66. EntryTypeDailyWorkPeriod

          67. 2.67. EquipmentType

          68. 2.68. EuropeanPublicKey

          69. 2.69. EventFaultRecordPurpose

          70. 2.70. EventFaultType

          71. 2.71. ExtendedSealIdentifier

          72. 2.72. ExtendedSerialNumber

          73. 2.73. FullCardNumber

          74. 2.74. FullCardNumberAndGeneration

          75. 2.75. Generation

          76. 2.76. GeoCoordinates

          77. 2.77. GNSSAccuracy

          78. 2.78. GNSSContinuousDriving

          79. 2.79. GNSSContinuousDrivingRecord

          80. 2.80. GNSSPlaceRecord

          81. 2.81. HighResOdometer

          82. 2.82. HighResTripDistance

          83. 2.83. HolderName

          84. 2.84. InternalGNSSReceiver

          85. 2.85. K-ConstantOfRecordingEquipment

          86. 2.86. KeyIdentifier

          87. 2.87. KMWCKey

          88. 2.88. Language

          89. 2.89. LastCardDownload

          90. 2.90. LinkCertificate

          91. 2.91. L-TyreCircumference

          92. 2.92. MAC

          93. 2.93. ManualInputFlag

          94. 2.94. ManufacturerCode

          95. 2.95. ManufacturerSpecificEventFaultData

          96. 2.96. MemberStateCertificate

          97. 2.97. MemberStateCertificateRecordArray

          98. 2.98. MemberStatePublicKey

          99. 2.99. Name

          100. 2.100. NationAlpha

          101. 2.101. NationNumeric

          102. 2.102. NoOfCalibrationRecords

          103. 2.103. NoOfCalibrationsSinceDownload

          104. 2.104. NoOfCardPlaceRecords

          105. 2.105. NoOfCardVehicleRecords

          106. 2.106. NoOfCardVehicleUnitRecords

          107. 2.107. NoOfCompanyActivityRecords

          108. 2.108. NoOfControlActivityRecords

          109. 2.109. NoOfEventsPerType

          110. 2.110. NoOfFaultsPerType

          111. 2.111. NoOfGNSSCDRecords

          112. 2.112. NoOfSpecificConditionRecords

          113. 2.113. OdometerShort

          114. 2.114. OdometerValueMidnight

          115. 2.115. OdometerValueMidnightRecordArray

          116. 2.116. OverspeedNumber

          117. 2.117. PlaceRecord

          118. 2.118. PreviousVehicleInfo

          119. 2.119. PublicKey

          120. 2.120. RecordType

          121. 2.121. RegionAlpha

          122. 2.122. RegionNumeric

          123. 2.123. RemoteCommunicationModuleSerialNumber

          124. 2.124. RSAKeyModulus

          125. 2.125. RSAKeyPrivateExponent

          126. 2.126. RSAKeyPublicExponent

          127. 2.127. RtmData

          128. 2.128. SealDataCard

          129. 2.129. SealDataVu

          130. 2.130. SealRecord

          131. 2.131. SensorApprovalNumber

          132. 2.132. SensorExternalGNSSApprovalNumber

          133. 2.133. SensorExternalGNSSCoupledRecord

          134. 2.134. SensorExternalGNSSIdentification

          135. 2.135. SensorExternalGNSSInstallation

          136. 2.136. SensorExternalGNSSOSIdentifier

          137. 2.137. SensorExternalGNSSSCIdentifier

          138. 2.138. SensorGNSSCouplingDate

          139. 2.139. SensorGNSSSerialNumber

          140. 2.140. SensorIdentification

          141. 2.141. SensorInstallation

          142. 2.142. SensorInstallationSecData

          143. 2.143. SensorOSIdentifier

          144. 2.144. SensorPaired

          145. 2.145. SensorPairedRecord

          146. 2.146. SensorPairingDate

          147. 2.147. SensorSCIdentifier

          148. 2.148. SensorSerialNumber

          149. 2.149. Signature

          150. 2.150. SignatureRecordArray

          151. 2.151. SimilarEventsNumber

          152. 2.152. SpecificConditionRecord

          153. 2.153. SpecificConditions

          154. 2.154. SpecificConditionType

          155. 2.155. Speed

          156. 2.156. SpeedAuthorised

          157. 2.157. SpeedAverage

          158. 2.158. SpeedMax

          159. 2.159. TachographPayload

          160. 2.160. TachographPayloadEncrypted

          161. 2.161. TDesSessionKey

          162. 2.162. TimeReal

          163. 2.163. TyreSize

          164. 2.164. VehicleIdentificationNumber

          165. 2.165. VehicleIdentificationNumberRecordArray

          166. 2.166. VehicleRegistrationIdentification

          167. 2.167. VehicleRegistrationNumber

          168. 2.168. VehicleRegistrationNumberRecordArray

          169. 2.169. VuAbility

          170. 2.170. VuActivityDailyData

          171. 2.171. VuActivityDailyRecordArray

          172. 2.172. VuApprovalNumber

          173. 2.173. VuCalibrationData

          174. 2.174. VuCalibrationRecord

          175. 2.175. VuCalibrationRecordArray

          176. 2.176. VuCardIWData

          177. 2.177. VuCardIWRecord

          178. 2.178. VuCardIWRecordArray

          179. 2.179. VuCardRecord

          180. 2.180. VuCardRecordArray

          181. 2.181. VuCertificate

          182. 2.182. VuCertificateRecordArray

          183. 2.183. VuCompanyLocksData

          184. 2.184. VuCompanyLocksRecord

          185. 2.185. VuCompanyLocksRecordArray

          186. 2.186. VuControlActivityData

          187. 2.187. VuControlActivityRecord

          188. 2.188. VuControlActivityRecordArray

          189. 2.189. VuDataBlockCounter

          190. 2.190. VuDetailedSpeedBlock

          191. 2.191. VuDetailedSpeedBlockRecordArray

          192. 2.192. VuDetailedSpeedData

          193. 2.193. VuDownloadablePeriod

          194. 2.194. VuDownloadablePeriodRecordArray

          195. 2.195. VuDownloadActivityData

          196. 2.196. VuDownloadActivityDataRecordArray

          197. 2.197. VuEventData

          198. 2.198. VuEventRecord

          199. 2.199. VuEventRecordArray

          200. 2.200. VuFaultData

          201. 2.201. VuFaultRecord

          202. 2.202. VuFaultRecordArray

          203. 2.203. VuGNSSCDRecord

          204. 2.204. VuGNSSCDRecordArray

          205. 2.205. VuIdentification

          206. 2.206. VuIdentificationRecordArray

          207. 2.207. VuITSConsentRecord

          208. 2.208. VuITSConsentRecordArray

          209. 2.209. VuManufacturerAddress

          210. 2.210. VuManufacturerName

          211. 2.211. VuManufacturingDate

          212. 2.212. VuOverSpeedingControlData

          213. 2.213. VuOverSpeedingControlDataRecordArray

          214. 2.214. VuOverSpeedingEventData

          215. 2.215. VuOverSpeedingEventRecord

          216. 2.216. VuOverSpeedingEventRecordArray

          217. 2.217. VuPartNumber

          218. 2.218. VuPlaceDailyWorkPeriodData

          219. 2.219. VuPlaceDailyWorkPeriodRecord

          220. 2.220. VuPlaceDailyWorkPeriodRecordArray

          221. 2.221. VuPrivateKey

          222. 2.222. VuPublicKey

          223. 2.223. VuSerialNumber

          224. 2.224. VuSoftInstallationDate

          225. 2.225. VuSoftwareIdentification

          226. 2.226. VuSoftwareVersion

          227. 2.227. VuSpecificConditionData

          228. 2.228. VuSpecificConditionRecordArray

          229. 2.229. VuTimeAdjustmentData

          230. 2.230. VuTimeAdjustmentGNSSRecord

          231. 2.231. VuTimeAdjustmentGNSSRecordArray

          232. 2.232. VuTimeAdjustmentRecord

          233. 2.233. VuTimeAdjustmentRecordArray

          234. 2.234. WorkshopCardApplicationIdentification

          235. 2.235. WorkshopCardCalibrationData

          236. 2.236. WorkshopCardCalibrationRecord

          237. 2.237. WorkshopCardHolderIdentification

          238. 2.238. WorkshopCardPIN

          239. 2.239. W-VehicleCharacteristicConstant

          240. 2.240. VuPowerSupplyInterruptionRecord

          241. 2.241. VuPowerSupplyInterruptionRecordArray

          242. 2.242. VuSensorExternalGNSSCoupledRecordArray

          243. 2.243. VuSensorPairedRecordArray

        3. 3. VALUE AND SIZE RANGE DEFINITIONS

        4. 4. CHARACTER SETS

        5. 5. ENCODING

        6. 6. OBJECT IDENTIFIERS UND APPLICATION IDENTIFIERS

          1. 6.1. Object Identifiers

            1. VU Authentication protocol identifiers

            2. Chip Authentication protocol identifiers

          2. 6.2. Application Identifiers

      11. Appendix 2

        TACHOGRAPH CARDS SPECIFICATION

        1. 1. INTRODUCTION

          1. 1.1. Abbreviations

          2. 1.2. References

        2. 2. ELECTRICAL AND PHYSICAL CHARACTERISTICS

          1. TCS_01 All electronic signals shall be in accordance with ISO/IEC 7816-3...

          2. TCS_02 The location and dimensions of the card contacts shall comply...

          3. 2.1. Supply Voltage and Current Consumption

            1. TCS_03 The card shall work according to specifications within the consumption...

            2. TCS_04 The card shall work with Vcc = 3V (± 0,3V)...

          4. 2.2. Programming Voltage Vpp

            1. TCS_05 The card shall not require a programming voltage at pin...

          5. 2.3. Clock generation and Frequency

            1. TCS_06 The card shall operate within a frequency range of 1...

            2. TCS_07 Under conditions contained into the card file EF ICC, the...

          6. 2.4. I/O Contact

            1. TCS_08 The I/O contact C7 is used to receive data from...

          7. 2.5. States of the Card

            1. TCS_09 The card works in two states while the supply voltage...

        3. 3. HARDWARE AND COMMUNICATION

          1. 3.1. Introduction

          2. 3.2. Transmission Protocol

            1. TCS_10 The Transmission protocol shall be compliant with ISO/IEC 7816-3 for...

            2. 3.2.1 Protocols

              1. TCS_11 The card shall provide both protocol T=0 and protocol T=1....

              2. TCS_12 T=0 is the default protocol, a PTS command is therefore...

              3. TCS_13 Devices shall support direct convention in both protocols: the direct...

              4. TCS_14 The Information Field Size Card byte shall be presented at...

              5. TCS_15 T=0

              6. TCS_16 T=1

            3. 3.2.2 ATR

              1. TCS_17 The device checks ATR bytes, according to ISO/IEC 7816-3. No...

              2. TCS_18 After the Answer To Reset (ATR), the Master File (MF)...

            4. 3.2.3 PTS

              1. TCS_19 The default Protocol is T=0. To set the T=1 protocol,...

              2. TCS_20 As both T=0 and T=1 protocols are mandatory for the...

              3. TCS_21 If no other baud rate than the default one are...

          3. 3.3. Access Rules

            1. TCS_22 An access rule specifies for an access mode, i.e. command,...

            2. TCS_23 The following security conditions are used for the tachograph card:...

            3. TCS_24 These security conditions can be linked in the following ways:...

            4. TCS_25 In the DF Tachograph G1 application the following access rules...

            5. TCS_26 In the DF Tachograph_G2 application the following access rules are...

            6. TCS_27 In the MF the following access rules are used:

            7. TCS_28 A tachograph card may or may not accept a command...

          4. 3.4. Commands and error codes overview

            1. TCS_29 The status words SW1 SW2 are returned in any response...

            2. TCS_30 If more than one error condition is fulfilled in one...

          5. 3.5. Command descriptions

            1. TCS_31 If both length bytes (Lc and Le) are requested, the...

            2. TCS_32 If both length bytes are requested, and Le=0 (secure messaging):...

            3. TCS_33 A tachograph card may support extended length fields according to...

              1. Notes:

            4. TCS_34 The VU shall perform the complete generation 2 VU —...

            5. 3.5.1 SELECT

              1. 3.5.1.1 Selection by name (AID)

                1. TCS_35 This command can be performed from anywhere in the file...

                2. TCS_36 The selection of an application resets the current security environment....

                3. TCS_37 Command Message

                4. TCS_38 Response Message (no response asked)

              2. 3.5.1.2 Selection of an Elementary File using its File Identifier

                1. TCS_39 Command Message

                2. TCS_40 A tachograph card shall support the generation 2 secure messaging...

                3. TCS_41 Response Message (no response asked)

            6. 3.5.2 READ BINARY

              1. 3.5.2.1 Command with offset in P1-P2

                2. TCS_42 Command Message

                3. TCS_43 Response Message

                4. 3.5.2.1.1 Command with secure messaging (examples)

                  1. TCS_44 Command Message

                  2. TCS_45 Response Message if SM-R-ENC-MAC-G1 (generation 1) / SM-R-ENC-MAC-G2 (generation 2)...

                  3. TCS_46 Response Message if SM-R-ENC-MAC-G1 (generation 1) / SM-R-ENC-MAC-G2 (generation 2)...

                  4. TCS_47 Response Message if incorrect Secure Messaging input format

              2. 3.5.2.2 Command with short EF (Elementary File) identifier

                1. TCS_48 A tachograph card shall support this command variant for all...

                2. TCS_49 Command Message

                3. TCS_50 Response Message

              3. 3.5.2.3 Command with odd instruction byte

                1. TCS_51 A tachograph card which supports EFs with 32 768 bytes...

                2. TCS_52 Command Message

                3. TCS_53 Response Message

                4. 3.5.2.3.1 Command with secure messaging (example)

                  1. TCS_54 Command message

                  2. TCS_55 Response message if the command is successful

            7. 3.5.3 UPDATE BINARY

              1. 3.5.3.1 Command with offset in P1-P2

                2. TCS_56 Command Message

                3. TCS_57 Response Message

                4. 3.5.3.1.1 Command with secure messaging (examples)

                  1. TCS_58 Command Message

                  2. TCS_59 Response message if correct Secure Messaging input format

                  3. TCS_60 Response Message if error in secure messaging

              2. 3.5.3.2 Command with short EF identifier

                1. TCS_61 A tachograph card shall support this command variant for all...

                2. TCS_62 Command Message

                3. TCS_63 Response Message

              3. 3.5.3.3 Command with odd instruction byte

                1. TCS_64 A tachograph card which supports EFs with 32 768 bytes...

                2. TCS_65 Command Message

                3. TCS_66 Response Message

                4. 3.5.3.3.1 Command with secure messaging (example)

                  1. TCS_67 Command message

                  2. TCS_68 Response message if the command is successful

            8. 3.5.4 GET CHALLENGE

              1. TCS_69 The Challenge issued by the card is only valid for...

              2. TCS_70 Command Message

              3. TCS_71 Response Message

            9. 3.5.5 VERIFY

              1. TCS_72 The PIN entered by the user must be ASCI encoded...

              2. TCS_73 The tachograph applications generation 1 and 2 shall use the...

              3. TCS_74 The tachograph card shall check whether the command is encoded...

              4. TCS_75 If the command is successful, the remaining CHV attempt counter...

              5. TCS_76 An unsuccessful comparison is recorded in the card, i.e. the...

              6. TCS_77 Command Message

              7. TCS_78 Response Message

            10. 3.5.6 GET RESPONSE

              1. TCS_79 Command Message

              2. TCS_80 Response Message

            11. 3.5.7 PSO: VERIFY CERTIFICATE

              1. 3.5.7.1 Generation 1 Command — Response pair

                1. TCS_81 This command variant is only supported by a generation 1...

                2. TCS_82 When a VERIFY CERTIFICATE command is successful, the Public Key...

                3. TCS_83 In any case, the VERIFY CERTIFICATE command uses the public...

                4. TCS_84 Command Message

                5. TCS_85 Response Message

              2. 3.5.7.2 Generation 2 Command — Response pair

                1. TCS_86 The command can be performed in the MF, DF Tachograph...

                2. TCS_87 Command Message

                3. TCS_88 For short length APDUs the following provisions apply: The IFD...

                4. TCS_89 For extended length APDUs the following provisions apply: If the...

                5. TCS_90 In addition to the error codes listed in TCS_85, the...

            12. 3.5.8 INTERNAL AUTHENTICATE

              1. TCS_91 All tachograph cards shall support this command in the DF...

              2. TCS_92 The INTERNAL AUTHENTICATE command uses the card Private Key (implicitly...

              3. TCS_93 Command Message

              4. TCS_94 Response Message

              5. TCS_95 If the INTERNAL AUTHENTICATE command is successful, the current session...

            13. 3.5.9 EXTERNAL AUTHENTICATE

              1. TCS_96 The command variant for the generation 1 mutual authentication mechanism...

              2. TCS_97 The command variant for the second generation VU-card mutual authentication...

              3. TCS_98 Command Message

              4. TCS_99 Response Message

            14. 3.5.10 GENERAL AUTHENTICATE

              1. TCS_100 The command can be performed in the MF, DF Tachograph...

              2. TCS_101 Command Message

              3. TCS_102 Response Message

            15. 3.5.11 MANAGE SECURITY ENVIRONMENT

              1. 3.5.11.1 Generation 1 Command — Response pair

                1. TCS_103 This command is only supported by a generation 1 tachograph...

                2. TCS_104 The key referenced in the MSE data field remains the...

                3. TCS_105 If the key referenced is not (already) present into the...

                4. TCS_106 Command Message

                5. TCS_107 Response Message

              2. 3.5.11.2 Generation 2 Command — Response pairs

                1. 3.5.11.2.1 MSE:SET AT for Chip Authentication

                  1. TCS_108 The command can be performed in the MF, DF Tachograph...

                  2. TCS_109 MSE:SET AT Command Message for Chip Authentication

                2. 3.5.11.2.2 MSE:SET AT for VU Authentication

                  1. TCS_110 The command can be performed in the MF, DF Tachograph...

                  2. TCS_111 MSE:SET AT Command Message for VU Authentication

                3. 3.5.11.2.3 MSE:SET DST

                  1. TCS_112 The command can be performed in the MF, DF Tachograph...

                  2. TCS_113 MSE:SET DST Command Message

                  3. TCS_114 Response Message

            16. 3.5.12 PSO: HASH

              1. TCS_115 The temporarily stored hash value shall be deleted if a...

              2. TCS_116 Command Message

              3. TCS_117 Response Message

            17. 3.5.13 PERFORM HASH of FILE

              1. TCS_118 The PERFORM HASH of FILE command is used to hash...

              2. TCS_119 A tachograph card shall support this command only for the...

              3. TCS_120 The result of the hash operation is stored temporarily in...

              4. TCS_121 The temporarily stored hash of file value shall be deleted...

              5. TCS_122 The Tachograph Generation 1 application shall support SHA-1.

              6. TCS_123 The Tachograph Generation 2 application shall support SHA-1 and SHA-2...

              7. TCS_124 Command Message

              8. TCS_125 Response Message

            18. 3.5.14 PSO: COMPUTE DIGITAL SIGNATURE

              1. TCS_126 This command shall not compute a digital signature of previously...

              2. TCS_127 The card private key is used to compute the digital...

              3. TCS_128 The Generation 1 tachograph application performs a digital signature using...

              4. TCS_129 The Generation 2 tachograph application computes an elliptic curve based...

              5. TCS_130 Command Message

              6. TCS_131 Response Message

            19. 3.5.15 PSO: VERIFY DIGITAL SIGNATURE

              1. TCS_132 The VERIFY DIGITAL SIGNATURE command always uses the public key...

              2. TCS_133 Command Message

              3. TCS_134 Response Message

            20. 3.5.16 PROCESS DSRC MESSAGE

              1. TCS_135 The DSRC master key is accessible only in the DF...

              2. TCS_136 The command shall only decrypt the DSRC data and verify...

              3. TCS_137 The order of the data objects in the command data...

              4. TCS_138 Command Message

              5. TCS_139 Response Message

        4. 4. TACHOGRAPH CARDS STRUCTURE

          1. TCS_140 A generation 2 tachograph card shall host the Master File...

          2. TCS_141 A tachograph card shall support at least the minimum number...

          3. 4.1. Master File MF

            1. TCS_142 After its personalisation, the master file MF shall have the...

            2. TCS_143 All EF structures shall be transparent.

            3. TCS_144 The Master File MF shall have the following data structure:...

            4. TCS_145 The elementary file EF DIR shall contain the following application...

            5. TCS_146 The elementary file EF ATR/INFO shall be present if the...

            6. TCS_147 The elementary file EF Extended_Length shall be present if the...

          4. 4.2. Driver card applications

            1. 4.2.1 Driver card application generation 1

              1. TCS_148 After its personalisation, the driver card application generation 1 shall...

              2. TCS_149 All EF structures shall be transparent.

              3. TCS_150 The driver card application generation 1 shall have the following...

              4. TCS_151 The following values, used to provide sizes in the table...

            2. 4.2.2 Driver card application generation 2

              1. TCS_152 After its personalisation, the driver card application generation 2 shall...

              2. TCS_153 All EF structures shall be transparent.

              3. TCS_154 The driver card application generation 2 shall have the following...

              4. TCS_155 The following values, used to provide sizes in the table...

          5. 4.3. Workshop card applications

            1. 4.3.1 Workshop card application generation 1

              1. TCS_156 After its personalisation, the workshop card application generation 1 shall...

              2. TCS_157 All EF structures shall be transparent.

              3. TCS_158 The workshop card application generation 1 shall have the following...

              4. TCS_159 The following values, used to provide sizes in the table...

            2. 4.3.2 Workshop card application generation 2

              1. TCS_160 After its personalisation, the workshop card application generation 2 shall...

              2. TCS_161 All EFs structures shall be transparent.

              3. TCS_162 The workshop card application generation 2 shall have the following...

              4. TCS_163 The following values, used to provide sizes in the table...

          6. 4.4. Control card applications

            1. 4.4.1 Control Card application generation 1

              1. TCS_164 After its personalisation, the control card application generation 1 shall...

              2. TCS_165 All EF structures shall be transparent.

              3. TCS_166 The control card application generation 1 shall have the following...

              4. TCS_167 The following values, used to provide sizes in the table...

            2. 4.4.2 Control card application generation 2

              1. TCS_168 After its personalisation, the control card application generation 2 shall...

              2. TCS_169 All EF structures shall be transparent.

              3. TCS_170 The control card application generation2 shall have the following data...

              4. TCS_171 The following values, used to provide sizes in the table...

          7. 4.5. Company card applications

            1. 4.5.1 Company card application generation 1

              1. TCS_172 After its personalisation, the company card application generation 1 shall...

              2. TCS_173 All EF structures shall be transparent.

              3. TCS_174 The company card application generation 1 shall have the following...

              4. TCS_175 The following values, used to provide sizes in the table...

            2. 4.5.2 Company card application generation 2

              1. TCS_176 After its personalisation, the company card application generation 2 shall...

              2. TCS_177 All EF structures shall be transparent.

              3. TCS_178 The company card application generation 2 shall have the following...

              4. TCS_179 The following values, used to provide sizes in the table...

      12. Appendix 3

        PICTOGRAMS

        1. PIC_001 The tachograph may optionally use the following pictograms and pictogram...

      13. Appendix 4

        PRINTOUTS

        1. 1. GENERALITIES

        2. 2. DATA BLOCKS SPECIFICATION

          1. PRT_007 Printouts shall use the following data blocks and/or data records,...

        3. 3. PRINTOUT SPECIFICATIONS

          1. 3.1. Driver Activities from Card Daily Printout

            1. PRT_008 The driver activities from card daily printout shall be in...

          2. 3.2. Driver Activities from VU Daily Printout

            1. PRT_009 The driver activities from VU daily printout shall be in...

          3. 3.3. Events and Faults from Card Printout

            1. PRT_010 The events and faults from card printout shall be in...

          4. 3.4. Events and Faults from VU Printout

            1. PRT_011 The events and faults from VU printout shall be in...

          5. 3.5. Technical data Printout

            1. PRT_012 The technical data printout shall be in accordance with the...

          6. 3.6. Over speeding Printout

            1. PRT_013 The over speeding printout shall be in accordance with the...

          7. 3.7. Historic of inserted cards

            1. PRT_014 The historic of inserted cards printout shall be in accordance...

      14. Appendix 5

        DISPLAY

        1. In this appendix the following format notation conventions have been...

        2. characters printed in bold denote plain text to be displayed...

        3. DIS_001 The tachograph shall display data using the following formats:

      15. Appendix 6

        FRONT CONNECTOR FOR CALIBRATION AND DOWNLOAD

        1. 1. HARDWARE

          1. 1.1. Connector

            1. INT_001 The downloading/calibration connector shall be a 6 pin connector, accessible...

          2. 1.2. Contact allocation

            1. INT_002 Contacts shall be allocated in accordance with the following table:...

          3. 1.3. Block diagram

            1. INT_003 The block diagram shall comply with the following:

        2. 2. DOWNLOADING INTERFACE

          1. INT_004 The downloading interface shall comply to RS232 specifications.

          2. INT_005 The downloading interface shall use one start bit, 8 data...

          3. Data byte organisation

          4. INT_006 Transmission baud rates shall be adjustable from 9 600 bps...

        3. 3. CALIBRATION INTERFACE

          1. INT_007 The data communication shall comply to ISO 14230-1 Road vehicles...

          2. INT_008 The input/output signal shall comply with the following electrical specification:...

          3. INT_009 The input/output signal shall comply with the following timing diagrams:...

      16. Appendix 7

        DATA DOWNLOADING PROTOCOLS

        1. 1. INTRODUCTION

          1. 1.1. Scope

            1. DDP_001 Data downloaded during one download session must be stored in...

          2. 1.2. Acronyms and notations

        2. 2. V.U. DATA DOWNLOADING

          1. 2.1. Download procedure

          2. 2.2. Data download protocol

            1. 2.2.1 Message structure

              1. DDP_002 All the messages exchanged between the IDE and the VU...

              2. DDP_003 In the case where the data to be carried by...

              3. DDP_004 If the last sub message contains exactly 255 bytes in...

            2. 2.2.2 Message types

              1. Notes:

              2. 2.2.2.1 Start Communication Request (SID 81)

                1. DDP_005 This message is issued by the IDE to establish the...

              3. 2.2.2.2 Positive Response Start Communication (SID C1)

                1. DDP_006 This message is issued by the VU to answer positively...

              4. 2.2.2.3 Start Diagnostic Session Request (SID 10)

                1. DDP_007 The Start Diagnostic Session request message is issued by the...

              5. 2.2.2.4 Positive Response Start Diagnostic (SID 50)

                1. DDP_008 The Positive Response Start Diagnostic message is sent by the...

              6. 2.2.2.5 Link Control Service (SID 87)

                1. DDP_052 The Link Control Service is used by the IDE to...

              7. 2.2.2.6 Link Control Positive Response (SID C7)

                1. DDP_053 The Link Control Positive Response is issued by the VU...

              8. 2.2.2.7 Request Upload (SID 35)

                1. DDP_009 The Request Upload message is issued by the IDE to...

              9. 2.2.2.8 Positive Response Request Upload (SID 75)

                1. DDP_010 The Positive Response Request Upload message is sent by the...

              10. 2.2.2.9 Transfer Data Request (SID 36)

                1. DDP_011 The Transfer Data Request is sent by the IDE to...

                2. DDP_054 It is mandatory for the IDE to request the overview...

              11. 2.2.2.10 Positive Response Transfer Data (SID 76)

                1. DDP_012 The Positive Response Transfer Data is sent by the VU...

                2. DDP055 In the first case (TREP 01), the VU will send...

              12. 2.2.2.11 Request Transfer Exit (SID 37)

                1. DDP_013 The Request Transfer Exit message is sent by the IDE...

              13. 2.2.2.12 Positive Response Request Transfer Exit (SID 77)

                1. DDP_014 The Positive Response Request Transfer Exit message is sent by...

              14. 2.2.2.13 Stop Communication Request (SID 82)

                1. DDP_015 The Stop Communication Request message is sent by the IDE...

              15. 2.2.2.14 Positive Response Stop Communication (SID C2)

                1. DDP_016 The Positive Response Stop Communication message is sent by the...

              16. 2.2.2.15 Acknowledge Sub Message (SID 83)

                1. DDP_017 The Acknowledge Sub Message is sent by the IDE to...

              17. 2.2.2.16 Negative Response (SID 7F)

                1. DDP_018 The Negative Response message is sent by the VU in...

            3. 2.2.3 Message flow

            4. 2.2.4 Timing

              1. DDP_019 During normal operation the timing parameters shown in the following...

            5. 2.2.5 Error handling

              1. 2.2.5.1 Start Communication phase

                1. DDP_020 If the IDE detects an error during the Start Communication...

                2. DDP_021 If the VU detects an error in the sequence coming...

              2. 2.2.5.2 Communication phase

            6. 2.2.6 Response Message content

              2. 2.2.6.1 Positive Response Transfer Data Overview

                1. DDP_029 The data field of the ‘Positive Response Transfer Data Overview’...

              3. 2.2.6.2 Positive Response Transfer Data Activities

                1. DDP_030 The data field of the ‘Positive Response Transfer Data Activities’...

              4. 2.2.6.3 Positive Response Transfer Data Events and Faults

                1. DDP_031 The data field of the ‘Positive Response Transfer Data Events...

              5. 2.2.6.4 Positive Response Transfer Data Detailed Speed

                1. DDP_032 The data field of the ‘Positive Response Transfer Data Detailed...

              6. 2.2.6.5 Positive Response Transfer Data Technical Data

                1. DDP_033 The data field of the ‘Positive Response Transfer Data Technical...

          3. 2.3. ESM File storage

            1. DDP_034 When a download session has included a VU data transfer,...

        3. 3. TACHOGRAPH CARDS DOWNLOADING PROTOCOL

          1. 3.1. Scope

          2. 3.2. Definitions

          3. 3.3. Card Downloading

            1. DDP_035 The download of a tachograph card includes the following steps:...

            2. 3.3.1 Initialisation sequence

              1. DDP_036 The IDE shall initiate the sequence as follows:

            3. 3.3.2 Sequence for un-signed data files

              1. DDP_037 The sequence to download the EFs ICC, IC, Card_Certificate (or...

            4. 3.3.3 Sequence for Signed data files

              1. DDP_038 The following sequence shall be used for each of the...

            5. 3.3.4 Sequence for resetting the calibration counter.

              1. DDP_039 The sequence to reset the counter in the EF in...

          4. 3.4. Data storage format

            1. 3.4.1 Introduction

              1. DDP_040 The downloaded data has to be stored according to the...

            2. 3.4.2 File format

              1. DDP_041 The file format is a concatenation of several TLV objects....

              2. DDP_042 The tag for an EF shall be the FID plus...

              3. DDP_043 The tag of an EF's signature shall be the FID...

              4. DDP_044 The length is a two byte value. The value defines...

              5. DDP_045 When a file is not downloaded nothing related to the...

              6. DDP_046 A signature shall be stored as the next TLV object...

        4. 4. DOWNLOADING A TACHOGRAPH CARD VIA A VEHICLE UNIT.

          1. DDP_047 The VU must allow for downloading the content of a...

          2. DDP_048 The IDE shall send a ‘Transfer Data Request Card Download’...

          3. DDP_049 The VU shall then download the whole card, file by...

          4. DDP_050 The IDE shall retrieve card data from the ‘Positive Response...

          5. DDP_051 The VU shall then, as applicable, update the or the...

      17. Appendix 8

        CALIBRATION PROTOCOL

        1. 1. INTRODUCTION

          1. CPR_001 The ‘ECUProgrammingSession’ allows data entry into the vehicle unit. In...

          2. CPR_002 The ‘ECUAdjustmentSession’ allows the selection of the I/O mode of...

          3. CPR_003 Throughout this document the address of the tester is referred...

        2. 2. TERMS, DEFINITIONS AND REFERENCES

          1. References:

        3. 3. OVERVIEW OF SERVICES

          1. 3.1. Services available

            1. CPR_004 The table indicates the services that are available in an...

          2. 3.2. Response codes

        4. 4. COMMUNICATION SERVICES

          1. CPR_005 The StartCommunication Service is used for starting a communication. In...

          2. 4.1. StartCommunication Service

            1. CPR_006 Upon receiving a StartCommunication indication primitive, the VU shall check...

            2. CPR_007 Then the VU shall perform all actions necessary to initialise...

            3. CPR_008 If a VU that is already initialised (and has entered...

            4. CPR_009 If the communication link cannot be initialised for any reason,...

            5. CPR_010 The StartCommunication Request message must be physically addressed.

            6. CPR_011 Initialising the VU for services is performed through a ‘fast...

            7. CPR_012 After completion of the initialisation,

            8. CPR_014 The data rate on the K-line shall be 10 400...

            9. CPR_016 The fast initialisation is started by the tester transmitting a...

            10. CPR_017 The timing values for the fast initialisation and communications in...

            11. CPR_018 The message format for fast initialisation is detailed in the...

            12. CPR_019 There is no negative response to the StartCommunication Request message,...

          3. 4.2. StopCommunication Service

            1. 4.2.1 Message description

              1. CPR_020 Upon receiving a StopCommunication indication primitive, the VU shall check...

              2. CPR_021 If it is possible to terminate the communication, the VU...

              3. CPR_022 If the communication cannot be terminated by any reason, the...

              4. CPR_023 If time-out of P3 max is detected by the VU,...

            2. 4.2.2 Message format

              1. CPR_024 The message formats for the StopCommunication primitives are detailed in...

            3. 4.2.3 Parameter Definition

          4. 4.3. TesterPresent Service

            1. 4.3.1 Message description

            2. 4.3.2 Message format

              1. CPR_079 The message formats for the TesterPresent primitives are detailed in...

              2. CPR_080 If the responseRequired parameter is set to ‘yes’, then the...

              3. CPR_081 The service shall support the following negative responses codes:

        5. 5. MANAGEMENT SERVICES

          1. 5.1. StartDiagnosticSession service

            1. 5.1.1 Message description

              1. CPR_025 The service StartDiagnosticSession is used to enable different diagnostic sessions...

              2. CPR_026 A diagnostic session shall only be started if communication has...

              3. CPR_027 The timing parameters defined in Table 4 shall be active...

            2. 5.1.2 Message format

              1. CPR_028 The message formats for the StartDiagnosticSession primitives are detailed in...

            3. 5.1.3 Parameter definition

              1. CPR_029 The parameter diagnosticSession (DS_) is used by the StartDiagnosticSession service...

          2. 5.2. SecurityAccess service

            1. 5.2.1 Message Description

              1. CPR_033 The tester shall use the SecurityAccess ‘requestSeed’ message to check...

              2. CPR_034 If the vehicle unit is already in CALIBRATION mode, it...

              3. CPR_035 If the vehicle unit is ready to accept a PIN...

              4. CPR_036 If the vehicle unit is not ready to accept a...

              5. CPR_037 The tester shall then, eventually, use the SecurityAccess ‘sendKey’ message...

              6. CPR_038 The vehicle unit shall answer to this request using the...

              7. CPR_039 In the following cases, the vehicle unit shall answer to...

            2. 5.2.2 Message format — SecurityAccess — requestSeed

              1. CPR_040 The message formats for the SecurityAccess ‘requestSeed’ primitives are detailed...

            3. 5.2.3 Message format — SecurityAccess — sendKey

              1. CPR_041 The message formats for the SecurityAccess ‘sendKey’ primitives are detailed...

        6. 6. DATA TRANSMISSION SERVICES

          1. 6.1. ReadDataByIdentifier service

            1. 6.1.1 Message description

              1. CPR_050 The ReadDataByIdentifier service is used by the client to request...

            2. 6.1.2 Message format

              1. CPR_051 The message formats for the ReadDataByIdentifier primitives are detailed in...

            3. 6.1.3 Parameter Definition

              1. CPR_052 The parameter recordDataIdentifier (RDI_) in the ReadDataByIdentifier request message identifies...

              2. CPR_053 recordDataIdentifier values defined by this document are shown in the...

              3. CPR_054 The parameter dataRecord (DREC_) is used by the ReadDataByIdentifier positive...

          2. 6.2. WriteDataByIdentifier service

            1. 6.2.1 Message description

              1. CPR_056 The WriteDataByIdentifier service is used by the client to write...

            2. 6.2.2 Message format

              1. CPR_057 The message formats for the WriteDataByIdentifier primitives are detailed in...

            3. 6.2.3 Parameter definition

        7. 7. CONTROL OF TEST PULSES — INPUT/OUTPUT CONTROL FUNCTIONAL UNIT

          1. 7.1. InputOutputControlByIdentifier service

            1. 7.1.1 Message description

              1. CPR_058 This calibration I/O signal line can be configured by K-line...

              2. CPR_059 The vehicle unit must have entered an adjustment session and...

              3. CPR_060 If speed pulses are received at the real time speed...

              4. CPR_061 The sequence shall be:

            2. 7.1.2 Message format

              1. CPR_062 The message formats for the InputOutputControlByIdentifier primitives are detailed in...

            3. 7.1.3 Parameter definition

              1. CPR_064 The parameter inputOutputControlParameter (IOCP_) is defined in the following table....

              2. CPR_065 The parameter controlState is present only when the inputOutputControlParameter is...

        8. 8. DATARECORDS FORMATS

          1. CPR_067 All parameters identified shall be supported by the VU.

          2. CPR_068 Data transmitted by the VU to the tester in response...

          3. 8.1. Transmitted parameter ranges

            1. CPR_069 Table 38 defines the ranges used to determine the validity...

            2. CPR_070 The values in the range ‘error indicator’ provide a means...

            3. CPR_071 The values in the range ‘not available’ provide a means...

            4. CPR_072 If a component failure prevents the transmission of valid data...

            5. CPR_073 For parameters coded in ASCII, the ASCII character ‘*’ is...

          4. 8.2. dataRecords formats

            1. CPR_074 Table 39 provides the length, resolution and operating range for...

            2. CPR_075 Table 40 details the formats of the different bytes of...

            3. CPR_076 Table 41 details the formats of the different bytes of...

            6. CPR_078 Table 42 details the formats of the different bytes of...

      18. Appendix 9

        TYPE APPROVAL LIST OF MINIMUM REQUIRED TESTS

        1. 1. INTRODUCTION

          1. 1.1. Type approval

          2. 1.2. References

        2. 2. VEHICLE UNIT FUNCTIONAL TESTS

        3. 3. MOTION SENSOR FUNCTIONAL TESTS

        4. 4. TACHOGRAPH CARDS FUNCTIONAL TESTS

        5. 5. EXTERNAL GNSS FACILITY TESTS

        6. 6. REMOTE COMMUNICATION FACILITY TESTS

        7. 7. PAPER FUNCTIONAL TESTS

        8. 8. INTEROPERABILITY TESTS

      19. Appendix 10

        SECURITY REQUIREMENTS

        1. This appendix specifies the IT security requirements for the smart...

        2. SEC_001 The following components of the smart tachograph system shall be...

        3. SEC_002 The minimum IT security requirements to be met by each...

        4. SEC_003 The European Commission shall make sure that four Protection Profiles...

        5. The Protection Profile for vehicle unit shall address the cases...

        6. SEC_004 Component manufacturers shall refine and complete the appropriate component Protection...

        7. SEC_005 Strict conformance of such specific Security Target with the corresponding...

        8. SEC_006 The assurance level for each Protection Profile shall be EAL4...

      20. Appendix 11

        COMMON SECURITY MECHANISMS

        1. PREAMBLE

        2. PART A FIRST-GENERATION TACHOGRAPH SYSTEM

          1. 1. INTRODUCTION

            1. 1.1. References

            2. 1.2. Notations and abbreviated terms

          2. 2. CRYPTOGRAPHIC SYSTEMS AND ALGORITHMS

            1. 2.1. Cryptographic systems

              1. CSM_001 Vehicle units and tachograph cards shall use a classical RSA...

              2. CSM_002 Vehicle units and tachograph cards shall use a Triple DES...

            2. 2.2. Cryptographic algorithms

              1. 2.2.1 RSA algorithm

                1. CSM_003 The RSA algorithm is fully defined by the following relations:...

              2. 2.2.2 Hash algorithm

                1. CSM_004 The digital signature mechanisms shall use the SHA-1 hash algorithm...

              3. 2.2.3 Data Encryption Algorithm

                1. CSM_005 DES based algorithms shall be used in Cipher Block Chaining...

          3. 3. KEYS AND CERTIFICATES

            1. 3.1. Keys generation and distribution

              1. 3.1.1 RSA Keys generation and distribution

                1. CSM_006 RSA keys shall be generated through three functional hierarchical levels:...

                2. CSM_007 At European level, a single European key pair (EUR.SK and...

                3. CSM_008 At Member State level, a Member State key pair (MS.SK...

                4. CSM_009 At equipment level, one single key pair (EQT.SK and EQT.PK)...

                5. CSM_010 Private keys confidentiality shall be maintained during generation, transport (if...

              2. 3.1.2 RSA Test keys

                1. CSM_011 For the purpose of equipment testing (including interoperability tests) the...

              3. 3.1.3 Motion sensor keys

                1. CSM_036 The European Certification authority shall generate KmVU and KmWC, two...

                2. CSM_037 Member States Certification Authorities shall:

              4. 3.1.4 T-DES session keys generation and distribution

                1. CSM_012 Vehicle units and tachograph cards shall, as a part of...

                2. CSM_013 This key shall be used for all subsequent cryptographic operations...

            2. 3.2. Keys

              1. CSM_014 RSA keys shall have (whatever the level) the following lengths:...

              2. CSM_015 Triple DES keys shall have the form (Ka, Kb, Ka)...

            3. 3.3. Certificates

              1. CSM_016 RSA Public key certificates shall be ‘non self-descriptive’‘Card Verifiable’ certificates...

              2. 3.3.1 Certificates content

                1. CSM_017 RSA Public key certificates are built with the following data...

                  1. Notes:

                    1. 1. The ‘Certificate Profile Identifier’ (CPI) delineates the exact structure of...

                    2. 2. The ‘Certification Authority Reference’ (CAR) has the purpose of identifying...

                    3. 3. The ‘Certificate Holder Authorisation’ (CHA) is used to identify the...

                    4. 4. The ‘Certificate Holder Reference’ (CHR) has the purpose of identifying...

                    5. 5. Key Identifiers uniquely identify certificate holder or certification authorities. They...

                    6. 6. Certificate verifiers shall implicitly know that the public key certified...

              3. 3.3.2 Certificates issued

                1. CSM_018 The certificate issued is a digital signature with partial recovery...

                  1. Notes:

                    1. 1. This certificate is 194 bytes long.

                    2. 2. CAR, being hidden by the signature, is also appended to...

                    3. 3. The certificate verifier shall implicitly know the algorithm used by...

                    4. 4. The headerlist associated with this issued certificate is as follows:...

              4. 3.3.3 Certificate verification and unwrapping

                1. CSM_019 It involves the following steps:

          4. 4. MUTUAL AUTHENTICATION MECHANISM

            1. CSM_020 The following protocol shall be used (arrows indicate commands and...

          5. 5. VU-CARDS DATA TRANSFER CONFIDENTIALITY, INTEGRITY AND AUTHENTICATION MECHANISMS

            1. 5.1. Secure Messaging

              1. CSM_021 VU-Cards data transfers integrity shall be protected through Secure Messaging...

              2. CSM_022 When data need to be protected during transfer, a Cryptographic...

              3. CSM_023 The cryptographic checksum of data sent within a command shall...

              4. CSM_024 The response status-information bytes shall be protected by a cryptographic...

              5. CSM_025 Cryptographic checksums shall be 4 Bytes long.

            2. 5.2. Treatment of Secure Messaging errors

              1. CSM_026 When the tachograph card recognises an SM error while interpreting...

              2. CSM_027 When the tachograph card returns status bytes without SM DOs...

            3. 5.3. Algorithm to compute Cryptographic Checksums

              1. CSM_028 Cryptographic checksums are built using a retail MACs in accordance...

              2. CSM_029 The Send Sequence Counter (SSC) shall be initiated during key...

              3. CSM_030 The Send Sequence Counter shall be increased by 1 each...

            4. 5.4. Algorithm to compute cryptograms for confidentiality DOs

              1. CSM_031 Cryptograms are computed using TDEA in TCBC mode of operation...

          6. 6. DATA DOWNLOAD DIGITAL SIGNATURE MECHANISMS

            1. CSM_032 The Intelligent Dedicated Equipment (IDE) stores data received from an...

            2. CSM_033 Digital signatures of downloaded data shall use a digital signature...

            3. 6.1. Signature generation

              1. CSM_034 Data signature generation by the equipment shall follow the signature...

            4. 6.2. Signature verification

              1. CSM_035 Data signature verification on downloaded data shall follow the signature...

        3. PART B SECOND-GENERATION TACHOGRAPH SYSTEM

          1. 7. INTRODUCTION

            1. 7.1. References

            2. 7.2. Notations and Abbreviations

            3. 7.3. Definitions

          2. 8. CRYPTOGRAPHIC SYSTEMS AND ALGORITHMS

            1. 8.1. Cryptographic Systems

              1. CSM_38 Vehicle units and tachograph cards shall use an elliptic curve-based...

              2. CSM_39 Vehicle units and external GNSS facilities shall use an elliptic...

              3. CSM_40 Vehicle units and tachograph cards shall use an AES-based symmetric...

              4. CSM_41 Vehicle units and external GNSS facilities shall use an AES-based...

              5. CSM_42 Vehicle units and motion sensors shall use an AES-based symmetric...

              6. CSM_43 Vehicle units and control cards shall use an AES-based symmetric...

                1. Notes:

                  1. — Properly speaking, data is transmitted from a vehicle unit to...

                  2. — A workshop card offers the same security services for the...

            2. 8.2. Cryptographic Algorithms

              1. 8.2.1 Symmetric Algorithms

                1. CSM_44 Vehicle units, tachograph cards, motion sensors and external GNSS facilities...

              2. 8.2.2 Asymmetric Algorithms and Standardized Domain Parameters

                1. CSM_45 Vehicle units, tachograph cards and external GNSS facilities shall support...

                2. CSM_46 Vehicle units, tachograph cards and external GNSS facilities shall support...

                3. CSM_47 Vehicle units, tachograph cards and external GNSS facilities shall support...

                4. CSM_48 Vehicle units, tachograph cards and external GNSS facilities shall support...

              3. 8.2.3 Hashing algorithms

                1. CSM_49 Vehicle units and tachograph cards shall support the SHA-256, SHA-384...

              4. 8.2.4 Cipher Suites

                1. CSM_50 In case a symmetric algorithm, an asymmetric algorithm and/or a...

          3. 9. KEYS AND CERTIFICATES

            1. 9.1. Asymmetric Key Pairs and Public Key Certificates

              1. 9.1.1 General

                2. CSM_51 Within the European Smart Tachograph system, ECC key pairs and...

                3. CSM_52 Within the entire European Smart Tachograph system, public and private...

              2. 9.1.2 European Level

                1. CSM_53 At European level, a single unique ECC key pair designated...

                2. CSM_54 The ERCA shall use the European private key to sign...

                3. CSM_55 The ERCA shall use the European private key to sign...

                4. CSM_56 As shown in Figure 1 in section 9.1.7, the ERCA...

                5. CSM_57 Before generating a new European root key pair, the ERCA...

                6. CSM_58 Whenever it generates a new European root key pair, the...

                7. CSM_59 The ERCA shall not use the private key of a...

                8. CSM_60 At any moment in time, the ERCA shall dispose of...

              3. 9.1.3 Member State Level

                1. CSM_61 At Member State level, all Member States required to sign...

                2. CSM_62 The task of generating Member State key pairs shall be...

                3. CSM_63 An MSCA shall choose the strength of a Member State...

                4. CSM_64 An MSCA_VU-EGF key pair, if present, shall consist of private...

                5. CSM_65 An MSCA_Card key pair shall consist of private key MSCA_Card.SK...

                6. CSM_66 An MSCA shall keep records of all signed VU certificates,...

                7. CSM_67 The validity period of an MSCA_VU-EGF certificate shall be 17...

                8. CSM_68 As shown in Figure 1 in section 9.1.7, the private...

                9. CSM_69 An MSCA shall not use the private key of an...

                10. CSM_70 At any moment in time, an MSCA shall dispose of...

                11. CSM_71 If an MSCA is required to sign certificates for vehicle...

              4. 9.1.4 Equipment Level: Vehicle Units

                1. CSM_72 Two unique ECC key pairs shall be generated for each...

                2. CSM_73 The VU_MA and VU_Sign certificates of a given vehicle unit...

                3. CSM_74 A VU manufacturer shall choose the strength of a VU...

                4. CSM_75 A vehicle unit shall use its VU_MA key pair, consisting...

                5. CSM_76 A vehicle unit shall be capable of generating ephemeral ECC...

                6. CSM_77 A vehicle unit shall use the private key VU_Sign.SK of...

                7. CSM_78 As shown in Figure 1 in section 9.1.7, the validity...

                  1. Notes:

                    1. — The extended validity period of a VU_Sign certificate allows a...

                    2. — The extended validity period of a VU_MA certificate is needed...

                8. CSM_79 A vehicle unit shall not use the private key of...

                9. CSM_80 The VU key pairs (except ephemeral keys pairs) and corresponding...

                  1. Notes:

                    1. — Ephemeral key pairs are not included in this requirement, as...

                    2. — This requirement does not forbid the possibility of replacing static...

                10. CSM_81 When put in operation, vehicle units shall contain the following...

                11. CSM_82 In addition to the cryptographic keys and certificates listed in...

              5. 9.1.5 Equipment Level: Tachograph Cards

                1. CSM_83 One unique ECC key pair, designated as Card_MA, shall be...

                2. CSM_84 The Card_MA and Card_Sign certificates of a given driver card...

                3. CSM_85 A card manufacturer or card personaliser shall choose the strength...

                4. CSM_86 A tachograph card shall use its Card_MA key pair, consisting...

                5. CSM_87 A driver card or workshop card shall use the private...

                6. CSM_88 The validity period of a Card_MA certificate shall be as...

                7. CSM_89 The validity period of a Card_Sign certificate shall be as...

                8. CSM_90 The key pairs and corresponding certificates of a given tachograph...

                9. CSM_91 When issued, tachograph cards shall contain the following cryptographic keys...

                10. CSM_92 In addition to the cryptographic keys and certificates listed in...

              6. 9.1.6 Equipment Level: External GNSS Facilities

                1. CSM_93 One unique ECC key pair shall be generated for each...

                2. CSM_94 An EGF manufacturer shall choose the strength of an EGF_MA...

                3. CSM_95 An external GNSS facility shall use its EGF_MA key pair,...

                4. CSM_96 The validity period of an EGF_MA certificate shall be 15...

                5. CSM_97 An external GNSS facility shall not use the private key...

                6. CSM_98 The EGF_MA key pair and corresponding certificate of a given...

                7. CSM_99 When put in operation, an external GNSS facility shall contain...

              7. 9.1.7 Overview: Certificate Replacement

                1. Notes to Figure 1:

                  1. 1. Different generations of the root certificate are indicated by a...

                  2. 2. Other certificates are indicated by two numbers in brackets, the...

                  3. 3. The MSCA_Card (2-1) and MSCA_Card (1-last) certificates are issued at...

                  4. 4. As shown in the figure, the first VU and Card...

                  5. 5. The validity period shown for cards is the one for...

                  6. 6. To save space, the difference in validity period between the...

            2. 9.2. Symmetric Keys

              1. 9.2.1 Keys for Securing VU — Motion Sensor Communication

                1. 9.2.1.1 General

                  2. CSM_100 A number of symmetric keys is needed for pairing vehicle...

                  3. CSM_101 The European Root Certificate Authority shall generate KM-VU and KM-WC,...

                  4. CSM_102 The ERCA shall assign to each motion sensor master key...

                  5. CSM_103 A Member State Certificate Authority shall forward KM-VU, together with...

                  6. CSM_104 A Member State Certificate Authority shall ensure that KM-WC, together...

                    1. Notes:

                      1. — See the description of data type in Appendix 2.

                      2. — as explained in section 9.2.1.2, in fact multiple generations of...

                  7. CSM_105 In addition to the AES key specified in CSM_104, a...

                    1. Notes:

                      1. — This allows a second-generation workshop card to be used for...

                      2. — A second-generation workshop card will contain two different applications, one...

                  8. CSM_106 An MSCA involved in issuing motion sensors shall derive the...

                  9. CSM_107 Motion sensor manufacturers shall generate a random and unique pairing...

                  10. CSM_108 Motion sensor manufacturers shall generate a unique serial number for...

                  11. CSM_109 For requirements CSM_107 and CSM_108, the MSCA shall use the...

                  12. CSM_110 The motion sensor manufacturer shall store the encrypted pairing key...

                  13. CSM_111 In addition to the AES-based cryptographic material specified in CSM_110,...

                  14. CSM_112 The length of the session key KS generated by a...

                2. 9.2.1.2 Motion Sensor Master Key Replacement in Second-Generation Equipment

                  1. CSM_113 Each motion sensor master key and all related keys (see...

                  2. CSM_114 At least one year before generating a new European root...

                  3. CSM_115 An MSCA shall ensure that all valid generations of KM-WC...

                  4. CSM_116 In relation to the process described in CSM_107 and CSM_108...

                  5. CSM_117 In relation to the process described in CSM_107 above: Since...

                  6. CSM_118 Vehicle unit manufacturers shall insert only one generation of KM-VU...

                    1. Notes:

                      1. — A vehicle unit based on the generation X ERCA certificate...

                      2. — A VU of generation X cannot be paired to a...

                      3. — Since workshop cards have a validity period of one year,...

              2. 9.2.2 Keys for Securing DSRC Communication

                1. 9.2.2.1 General

                  1. CSM_119 The authenticity and confidentiality of data communicated from a vehicle...

                  2. CSM_120 The DSRC master key KMDSRC shall be an AES key...

                  3. CSM_121 The ERCA shall communicate the DSRC master key to Member...

                  4. CSM_122 The ERCA shall assign to each DSRC master key a...

                  5. CSM_123 For every vehicle unit, the vehicle unit manufacturer shall create...

                  6. CSM_124 Upon receiving a request for VU-specific DSRC keys, the MSCA...

                  7. CSM_125 The MSCA shall distribute K_VUDSRC_ENC and K_VUDSRC_MAC to the VU...

                  8. CSM_126 When issued, a vehicle unit shall have stored K_VUDSRC_ENC and...

                  9. CSM_127 When issued, control cards and workshop cards shall have stored...

                  10. CSM_128 The MSCA shall keep records of all VU-specific DSRC keys...

                2. 9.2.2.2 DSRC Master Key Replacement

                  1. CSM_129 Each DSRC master key is associated to a particular generation...

                  2. CSM_130 At least two years before generating a new European root...

                  3. CSM_131 An MSCA shall ensure that all valid generations of KMDSRC...

                  4. CSM_132 An MSCA shall ensure that all generations of KMDSRC that...

                  5. CSM_133 Vehicle unit manufacturers shall insert only one set of VU-specific...

                    1. Notes:

                      1. — This implies that a vehicle unit based on the generation...

                      2. — Since workshop cards have a validity period of one year...

            3. 9.3. Certificates

              1. 9.3.1 General

                1. CSM_134 All certificates in the European Smart Tachograph system shall be...

                2. CSM_135 The Distinguished Encoding Rules (DER) according to [ISO 8825-1] shall...

              2. 9.3.2 Certificate Content

                1. CSM_136 All certificates shall have the structure shown in the certificate...

                2. 9.3.2.1 Certificate Profile Identifier

                  1. CSM_137 Certificates shall use a Certificate Profile Identifier to indicate the...

                3. 9.3.2.2 Certificate Authority Reference

                  1. CSM_138 The Certificate Authority Reference shall be used to identify the...

                  2. CSM_139 An ERCA root certificate shall be self-signed, i.e., the Certificate...

                  3. CSM_140 For an ERCA link certificate, the Certificate Holder Reference shall...

                4. 9.3.2.3 Certificate Holder Authorisation

                  1. CSM_141 The Certificate Holder Authorisation shall be used to identify the...

                5. 9.3.2.4 Public Key

                  1. CSM_142 The data element Domain Parameters shall contain one of the...

                  2. CSM_143 The data element Public Point shall contain the public point....

                6. 9.3.2.5 Certificate Holder Reference

                  1. CSM_144 The Certificate Holder Reference is an identifier for the public...

                  2. CSM_145 For card certificates and external GNSS facility certificates, the Certificate...

                  3. CSM_146 For vehicle units, the manufacturer, when requesting a certificate, may...

                  4. CSM_147 For ERCA and MSCA certificates, the Certificate Holder Reference shall...

                7. 9.3.2.6 Certificate Effective Date

                  1. CSM_148 The Certificate Effective Date shall indicate the starting date and...

                8. 9.3.2.7 Certificate Expiration Date

                  1. CSM_149 The Certificate Expiration Date shall indicate the end date and...

                9. 9.3.2.8 Certificate Signature

                  1. CSM_150 The signature on the certificate shall be created over the...

              3. 9.3.3 Requesting Certificates

                1. CSM_151 When requesting a certificate, a requester shall send the following...

                2. CSM_152 In addition to the data in CSM_151, an MSCA shall...

                3. CSM_153 In addition to the data in CSM_151, an equipment manufacturer...

                4. CSM_154 In the case of a VU, the manufacturer, when requesting...

          4. 10. VU- CARD MUTUAL AUTHENTICATION AND SECURE MESSAGING

            1. 10.1. General

              1. CSM_155 On a high level, secure communication between a vehicle unit...

              2. CSM_156 The mechanism described in CSM_155 shall be triggered by the...

            2. 10.2. Mutual Certificate Chain Verification

              1. 10.2.1 Card Certificate Chain Verification by VU

                1. CSM_157 Vehicle units shall use the protocol depicted in Figure 4...

                  1. Notes to Figure 4:

                    1. — The Card certificates and public keys mentioned in the figure...

                    2. — The Card.CA certificates and public keys mentioned in the figure...

                    3. — The Card.CA.EUR certificate mentioned in the figure is the European...

                    4. — The Card.Link certificate mentioned in the figure is the card's...

                    5. — The Card.Link.EUR certificate is the European root certificate that is...

                2. CSM_158 As depicted in Figure 4, verification of the card's certificate...

                3. CSM_159 As indicated in Figure 4, once the VU has verified...

                4. CSM_160 The VU shall verify the temporal validity of any certificate...

              2. 10.2.2 VU Certificate Chain Verification by Card

                1. CSM_161 Tachograph cards shall use the protocol depicted in Figure 5...

                2. Notes to Figure 5:

                  1. — The VU certificates and public keys mentioned in the figure...

                  2. — The VU.CA certificates and public keys mentioned in the figure...

                  3. — The VU.CA.EUR certificate mentioned in the figure is the European...

                  4. — The VU.Link certificate mentioned in the figure is the VU's...

                  5. — The VU.Link.EUR certificate is the European root certificate that is...

                3. CSM_162 As depicted in Figure 5, verification of the certificate chain...

                  1. Note: There are three ways in which the card may...

                    1. — the VU.CA.EUR certificate is the same certificate as the card's...

                    2. — the VU.CA.EUR certificate precedes the card's own EUR certificate and...

                    3. — the VU.CA.EUR certificate succeeds the card's own EUR certificate and...

                4. CSM_163 The VU shall use the MSE: Set AT command to...

                5. CSM_164 The MSE: Set AT command also contains an indication of...

                6. CSM_165 If the MSE: Set AT command is successful, the card...

                7. CSM_166 The card shall verify the temporal validity of any certificate...

                8. CSM_167 For verifying the temporal validity of a certificate presented by...

                9. CSM_168 As indicated in Figure 5, once the card has verified...

            3. 10.3. VU Authentication

              1. CSM_169 Vehicle units and cards shall use the VU Authentication protocol...

              2. CSM_170 Next to the card challenge, the VU shall include in...

              3. CSM_171 The VU shall also include in the signature the identifier...

              4. CSM_172 If multiple GET CHALLENGE commands are sent by the VU...

              5. CSM_173 The signing algorithm used by the VU for VU Authentication...

              6. CSM_174 Upon receiving the VU's signature in an EXTERNAL AUTHENTICATE command,...

            4. 10.4. Chip Authentication and Session Key Agreement

              1. CSM_175 Vehicle units and cards shall use the Chip Authentication protocol...

              2. CSM_176 The VU and the card shall take the following steps:...

              3. CSM_177 In step 3 above, the card shall compute Comp(VU.PKeph) as...

              4. CSM_178 In steps 4 and 7 above, the card and the...

              5. CSM_179 In steps 5 and 8 above, the card and the...

              6. CSM_180 In steps 6 and 9 above, the card and the...

            5. 10.5. Secure Messaging

              1. 10.5.1 General

                1. CSM_181 All commands and responses exchanged between a vehicle unit and...

                2. CSM_182 Except when reading from a file with access condition SM-R-ENC-MAC-G2...

                3. CSM_183 When reading data from a file with access condition SM-R-ENC-MAC-G2,...

                4. CSM_184 Secure Messaging shall use AES as defined in [AES] with...

                5. CSM_185 An unsigned integer shall be used as the Send Sequence...

                6. CSM_186 For message encryption, KENC shall be used with AES in...

                7. CSM_187 For message authentication, KMAC shall be used with AES in...

              2. 10.5.2 Secure Message Structure

                1. CSM_188 Secure Messaging shall make use only of the Secure Messaging...

                2. CSM_189 All SM data objects shall be encoded in DER TLV...

                3. CSM_190 APDUs protected by Secure Messaging shall be created as follows:...

                4. CSM_191 Any data object to be encrypted shall be padded according...

                5. Summary and Examples

              3. 10.5.3 Secure Messaging Session Abortion

                1. CSM_192 A vehicle unit shall abort an ongoing Secure Messaging session...

                2. CSM_193 A tachograph card shall abort an ongoing Secure Messaging session...

                3. CSM_194 Regarding SM error handling by a tachograph card:

                4. CSM_195 If a Secure Messaging session between a VU and a...

                5. CSM_196 If for any reason the VU decides to restart mutual...

          5. 11. VU — EXTERNAL GNSS FACILITY COUPLING, MUTUAL AUTHENTICATION AND SECURE...

            1. 11.1. General

              1. CSM_197 The GNSS facility used by a VU to determine its...

              2. CSM_198 Secure communication between a vehicle unit and an external GNSS...

              3. CSM_199 Communication between a vehicle unit and an EGF differs from...

              4. CSM_200 For communication between a vehicle unit and an EGF, APDU...

            2. 11.2. VU and External GNSS Facility Coupling

              1. CSM_201 A vehicle unit and an EGF in a vehicle shall...

              2. CSM_202 Coupling of a vehicle unit and an EGF shall only...

              3. CSM_203 A workshop may re-couple a vehicle unit to another EGF...

              4. CSM_204 A workshop may re-couple an external GNSS facility to another...

            3. 11.3. Mutual Certificate Chain Verification

              1. 11.3.1 General

                1. CSM_205 Mutual certificate chain verification between a VU and an EGF...

              2. 11.3.2 During VU — EGF Coupling

                1. CSM_206 During the coupling to an EGF, a vehicle unit shall...

                  1. Notes to Figure 4 within this context:

                    1. — Communication control is out of the scope of this Appendix....

                    2. — The Card certificates and public keys mentioned in the figure...

                    3. — The Card.CA certificates and public keys mentioned in the figure...

                    4. — The Card.CA.EUR certificate mentioned in the figure shall be interpreted...

                    5. — The Card.Link certificate mentioned in the figure shall be interpreted...

                    6. — The Card.Link.EUR certificate is the European root certificate that is...

                    7. — Instead of the , the VU shall read the from...

                    8. — Instead of selecting the Tachograph AID, the VU shall select...

                    9. — ‘Ignore Card’ shall be interpreted as ‘Ignore EGF’.

                2. CSM_207 Once it has verified the EGF_MA certificate, the vehicle unit...

                3. CSM_208 During the coupling to a VU, an external GNSS unit...

                  1. Notes to Figure 5 within this context:

                    1. — The VU shall generate a fresh ephemeral key pair using...

                    2. — The VU certificates and public keys mentioned in the figure...

                    3. — The VU.CA certificates and public keys mentioned in the figure...

                    4. — The VU.CA.EUR certificate mentioned in the figure is the European...

                    5. — The VU.Link certificate mentioned in the figure is the VU's...

                    6. — The VU.Link.EUR certificate is the European root certificate that is...

                4. CSM_209 In deviation from requirement CSM_167, an EGF shall use the...

                5. CSM_210 Once it has verified the VU_MA certificate, the external GNSS...

              3. 11.3.3 During Normal Operation

                1. CSM_211 During normal operation, a vehicle unit and an EGF shall...

                2. CSM_212 As shown in Figure 11, the vehicle unit shall log...

            4. 11.4. VU Authentication, Chip Authentication and Session Key Agreement

              1. CSM_213 VU Authentication, Chip Authentication and session key agreement between a...

            5. 11.5. Secure Messaging

              1. CSM_214 All commands and responses exchanged between a vehicle unit and...

              2. CSM_215 If a Secure Messaging session between a VU and an...

          6. 12. VU — MOTION SENSOR PAIRING AND COMMUNICATION

            1. 12.1. General

              1. CSM_216 A vehicle unit and a motion sensor shall communicate using...

            2. 12.2. VU — Motion Sensor Pairing Using Different Key Generations

              1. CSM_217 A second-generation VU and a second-generation motion sensor shall be...

            3. 12.3. VU — Motion Sensor Pairing and Communication using AES

              1. CSM_218 As specified in Table 3 in section 9.2.1, all keys...

              2. CSM_219 The pairing information that is sent in instructions 43 (VU...

              3. CSM_220 In case the plaintext data length (using AES keys) is...

              4. CSM_221 For instruction 11 and in case more than one block...

            4. 12.4. VU — Motion Sensor Pairing For Different Equipment Generations

              1. CSM_222 As explained in section 9.2.1, a second-generation motion sensor may...

                1. Notes:

                  1. — It is not possible to pair a second-generation VU to...

                  2. — It is not possible to use a first-generation workshop card...

          7. 13. SECURITY FOR REMOTE COMMUNICATION OVER DSRC

            1. 13.1. General

              1. CSM_223 The plaintext data communicated by a VU to a Remote...

              2. CSM_224 The DSRC security data shall consist of the concatenation of...

              3. CSM_225 The 3-byte counter in the DSRC security data shall be...

            2. 13.2. Tachograph Payload Encryption and MAC Generation

              1. CSM_226 Given a plaintext data element with data type as described...

              2. CSM_227 A VU shall calculate the MAC in the DSRC security...

            3. 13.3. Verification and Decryption of Tachograph Payload

              1. CSM_228 When a remote interrogator receives RTM data from a VU,...

              2. CSM_229 In order to prevent replay attacks, the remote interrogator shall...

                1. Notes:

                  1. — This requires the remote interrogator to have an accurate and...

                  2. — Since Appendix 14 requires a VU to calculate a new...

              3. CSM_230 When a workshop verifies the correct functioning of the DSRC...

          8. 14. SIGNING DATA DOWNLOADS AND VERIFYING SIGNATURES

            1. 14.1. General

              1. CSM_231 The Intelligent Dedicated Equipment (IDE) shall store data received from...

              2. CSM_232 The IDE shall also dispose of.

            2. 14.2. Signature generation

              1. CSM_233 The signing algorithm to create digital signatures over downloaded data...

            3. 14.3. Signature verification

              1. CSM_234 An IDE may perform verification of a signature over downloaded...

                1. Notes to Figure 13:

                  1. — The equipment that signed the data to be analysed is...

                  2. — The EQT certificates and public keys mentioned in the figure...

                  3. — The EQT.CA certificates and public keys mentioned in the figure...

                  4. — The EQT.CA.EUR certificate mentioned in the figure is the European...

                  5. — The EQT.Link certificate mentioned in the figure is the EQT's...

                  6. — The EQT.Link.EUR certificate is the European root certificate that is...

              2. CSM_235 For calculating the hash M sent to the control card...

              3. CSM_236 For verifying the EQT's signature, the control card shall follow...

      21. Appendix 12

        POSITIONING BASED ON GLOBAL NAVIGATION SATELLITE SYSTEM (GNSS)

        1. 1. INTRODUCTION

          1. 1.1. Scope

            1. GNS_1 The Vehicle Unit shall collect location data from at least...

          2. 1.2. Acronyms and notations

        2. 2. SPECIFICATION OF THE GNSS RECEIVER

          1. GNS_2 Manufacturers shall ensure that the GNSS receivers in the Smart...

          2. GNS_3 The GNSS receiver shall have the capability to support Authentication...

        3. 3. NMEA SENTENCES

          1. GNS_4 The location data is based on the NMEA sentence Recommended...

          2. GNS_5 The Vehicle Unit shall store in the VU database the...

          3. GNS_6 The GSA sentence shall be stored with record number ‘06’....

          4. GNS_7 The maximum size of the NMEA sentences (e.g., RMC, GSA...

        4. 4. VEHICLE UNIT WITH AN EXTERNAL GNSS FACILITY

          1. 4.1. Configuration

            1. 4.1.1 Main components and interfaces

              1. GNS_8 The external GNSS facility must be powered with a specific...

              2. GNS_9 The external GNSS facility shall consist of the following components...

              3. GNS_10 The external GNSS facility has at least the following external...

              4. GNS_11 In the VU, the VU Secure Transceiver is the other...

              5. GNS_12 For the physical layer of the communication with the external...

            2. 4.1.2 External GNSS facility state at the end of production

              1. GNS_13 The external GNSS facility shall store the following values in...

          2. 4.2. Communication between the external GNSS facility and the vehicle unit...

            1. 4.2.1 Communication Protocol

              1. GNS_14 The communication protocol between the external GNSS facility and the...

              2. GNS_15 The communication protocol shall be based on standard ISO/IEC 7816-4:2013 with...

              3. GNS_16 In the communication protocol, extended length fields shall not supported....

              4. GNS_17 The communication protocol of ISO 7816 (both *-4:2013 and *-12:2005)...

              5. GNS_18 Regarding the functions 1) the collection and distribution of GNSS...

              6. GNS_19 The GNSS Secure Transceiver shall store the data coming from...

              7. GNS_20 The GNSS Secure Transceiver shall use a memory to store...

              8. GNS_21 The file structure is provided in Table 1. For the...

            2. 4.2.2 Secure transfer of GNSS data

              1. GNS_22 The secure transfer of GNSS position data shall be allowed...

              2. GNS_23 Every T seconds, where T is a value lower or...

            3. 4.2.3 Structure of the Read Record command

              1. GNS_24 The command shall support the Secure Messaging authentication-only-mode, see Appendix...

              2. GNS_25 Command Message

              3. GNS_26 The record referenced in P1 becomes the current record.

              4. GNS_27 The GNSS Secure Transceiver shall support the following tachograph generation...

          3. 4.3. Coupling, mutual authentication and session key agreement of the external...

          4. 4.4. Error Handling

            1. 4.4.1 Communication error with the external GNSS facility

              1. GNS_28 If the VU does not manage to communicate to the...

            2. 4.4.2 Breach of the physical integrity of the external GNSS facility...

              1. GNS_29 If the external GNSS facility has been breached, the GNSS...

            3. 4.4.3 Absence of position information from GNSS receiver

              1. GNS_30 If the GNSS Secure Transceiver does not receive data from...

            4. 4.4.4 External GNSS facility certificate expired

              1. GNS_31 If the VU detects that the EGF certificate used for...

        5. 5. VEHICLE UNIT WITHOUT AN EXTERNAL GNSS FACILITY

          1. 5.1. Configuration

            1. GNS_32 The GNSS receiver shall act as a talker and transmit...

            2. GNS_33 An external GNSS antenna installed on the vehicle or an...

          2. 5.2. Error Handling

            1. 5.2.1 Absence of position information from GNSS receiver

              1. GNS_34 If the VU does not receive data from the GNSS...

        6. 6. GNSS TIME CONFLICT

        7. 7. VEHICLE MOTION CONFLICT

          1. GNS_35 The VU shall trigger and record an Vehicle Motion Conflict...

      22. Appendix 13

        ITS INTERFACE

        1. 1. INTRODUCTION

        2. 2. SCOPE

          1. 2.1. Acronyms, definitions and notations

        3. 3. REFERENCED REGULATIONS AND STANDARDS

        4. 4. INTERFACE WORKING PRINCIPLES

          1. 4.1. Preconditions to data transfer via the ITS interface

            1. 4.1.1 Data provided through the ITS interface

            2. 4.1.2 Content of the Data

            3. 4.1.3 ITS Applications

          2. 4.2. Communication technology

          3. 4.3. PIN authorization

          4. 4.4. Message Format

            1. Header

            2. Data Field

            3. RequestPIN (SID 01)

            4. SendITSID (SID 02)

            5. SendPIN (SID 03)

            6. PairingResult (SID 04)

            7. SendPUC (SID 05)

            8. BanLiftingResult (SID 06)

            9. RequestRejected (SID 07)

            10. RequestData (SID 08)

            11. ResquestAccepted (SID 09)

            12. DataUnavailable (SID 0A)

            13. NegativeAnswer (SID 0B)

          5. 4.5. Driver consent

          6. 4.6. Standard data retrieval

          7. 4.7. Personal data retrieval

          8. 4.8. Event and fault data retrieval

        5. ANNEX 1

          LIST OF AVAILABLE DATA THROUGH THE ITS INTERFACE

          1. (2) CONTINUOUS GNSS DATA AVAILABLE AFTER DRIVER CONSENT

          2. (3) EVENT CODES AVAILABLE WITHOUT DRIVER CONSENT

          3. (4) EVENT CODES AVAILABLE WITH DRIVER CONSENT

          4. (5) FAULT DATA CODES AVAILABLE WITHOUT DRIVER CONSENT

          5. (6) MANUFACTURER SPECIFIC EVENTS AND FAULTS WITHOUT DRIVER CONSENT

        6. ANNEX 2

          SEQUENCE DIAGRAMS OF MESSAGES EXCHANGES WITH THE ITS UNIT.

        7. ANNEX 3

          ASN.1 SPECIFICATIONS

      23. Appendix 14

        REMOTE COMMUNICATION FUNCTION

        1. 1. INTRODUCTION

          1. DSC_1 Regulation (EU) No 165/2014 determines that the tachograph shall be...

          2. DSC_2 The Data shall be exchanged using the Communication which shall...

          3. DSC_3 The Communication shall be established with the communications equipment only...

          4. DSC_4 The Data shall be secured to ensure integrity.

          5. DSC_5 Access to the Data communicated shall be restricted to competent...

          6. DSC_6 The Data exchanged during the Communication shall be limited to...

          7. DSC_7 Data integrity and security shall be obtained by securing the...

          8. DSC_8 The Data shall contain a timestamp for the time of...

          9. DSC_9 The content of the security data shall be known only...

          10. DSC_10 The same architecture and equipment shall be capable be used...

          11. DSC_11 For clarification, in accordance with the provisions of Regulation (EU)...

        2. 2. SCOPE

        3. 3. ACRONYMS, DEFINITIONS AND NOTATIONS

        4. 4. OPERATIONAL SCENARIOS

          1. 4.1 Overview

            1. 4.1.1 Preconditions to data transfer via 5,8 GHz DSRC interface

              2. 4.1.1.1 Data held in VU

                1. DSC_12 The VU shall be responsible to keep updated every 60...

              3. 4.1.1.2 Data provided to DSRC-VU Facility

                1. DSC_13 The VU shall be responsible to update the DSRC tachograph...

                2. DSC_14 The VU data shall be used as a basis to...

              4. 4.1.1.3 Content of the Data

                1. DSC_15 The content and format of the Data shall be such...

              5. 4.1.1.4 Data presentation

                1. DSC_16 The Data, having been kept frequently updated in accordance with...

              6. 4.1.1.5 Security data

                1. DSC_17 Security data (securityData), comprising the data required by the REDCR...

              7. 4.1.1.6 VUPM data available for transfer across the DSRC interface

                1. DSC_18 The data concept which shall always be available in the...

              8. General overview of communication Profile 1

            2. 4.1.2 Profile 1a: via a hand aimed or temporary roadside mounted...

            3. 4.1.3 Profile 1b: via a vehicle mounted and directed Remote Early...

          2. 4.2 Security/Integrity

        5. 5. REMOTE COMMUNICATION DESIGN AND PROTOCOLS

          1. 5.1 Design

            1. DSC_19 The following functions are located in the VU:

            2. DSC_20 The Antenna and The Communication shall operate within ERC 70-03,...

            3. DSC_21 The DSRC antenna shall be connected to the DSRC-VU facility...

            4. DSC_22 The form factor of the antenna is not defined and...

            5. DSC_23 The design and form factor of the REDCR shall be...

            6. DSC_24 The design and form factor of the DSRC-VU and its...

            7. DSC_25 However, the DSRC-VU shall be reasonably capable to accept data...

          2. 5.2 Workflow

            1. 5.2.1 Operations

            2. 5.2.2 Interpretation of the Data received via the DSRC communication

              1. DSC_26 Data received across the 5.8 GHz interface shall carry the...

          3. 5.3 DSRC Physical interface parameters for remote communication

            1. 5.3.1 Location constraints

              1. DSC_27 The remote interrogation of vehicles using a 5.8GHz DSRC interface...

            2. 5.3.2 Downlink and uplink parameters

              1. DSC_28 The equipment used for remote tachograph monitoring shall conform to...

              2. DSC_29 Further, to ensure compatibility with the operational parameters of other...

            3. 5.3.3 Antenna design

              1. 5.3.3.1 REDCR antenna

                1. DSC_30 The design of the REDCR antenna shall be a function...

              2. 5.3.3.2 VU antenna

                1. DSC_31 The design of the DSRC-VU antenna shall be a function...

                2. DSC_32 The VU antenna shall be fixed to, or close to,...

                3. DSC_33 In the test environment in a workshop (see section 6.3),...

          4. 5.4 DSRC Protocol requirements for RTM

            1. 5.4.1 Overview

              1. DSC_34 The transaction protocol to download the Data across the 5.8...

            2. 5.4.2 Commands

              1. DSC_35 The following commands are the only functions used in an...

            3. 5.4.3 Interrogation command sequence

              1. DSC_36 From the perspective of the command and response sequence, the...

            4. 5.4.4 Data structures

              1. DSC_37 The semantic structure of the Data when passed across the...

              2. DSC_38 The payload (RTM data) consists of the concatenation of

              3. DSC_39 The RTM Data is being addressed as RTM Attribute=1 and...

              4. DSC_40 The RTM Context Mark shall identify the supported standard part...

            5. 5.4.5 Elements of RtmData, actions performed and definitions

              1. DSC_41 The data values to be calculated by the VU and...

            6. 5.4.6 Data transfer mechanism

              1. DSC_42 Payload data defined previously are requested by the REDCR after...

              2. DSC_43 For all DSRC exchanges, data shall be encoded using PER...

            7. 5.4.7 Detailed DSRC transaction description

              1. DSC_44 Initialisation is performed according to DSC_44 — DSC_48 and Tables...

              2. DSC_45 A DSRC-VU, when receiving a BST, requires the allocation of...

              3. DSC_46 The REDCR then answers by allocating a private window, as...

              4. DSC_47 The DSRC-VU, when receiving the private window allocation, sends its...

              5. DSC_48 The DSRC-VU shall support the ‘Freight and Fleet’ application, identified...

              6. DCS_49 The REDCR then reads the data by issuing a GET...

              7. DSC_50 The DSRC-VU, when receiving the GET request, sends a GET...

              8. DSC_51 The REDCR then closes the connection by issuing a EVENT_REPORT,...

              9. DSC_52 The DSRC-VU is not expected to answer to the Release...

            8. 5.4.8 DSRC Test transaction description

              1. DSC_53 Full tests that include securing the data, need to be...

              2. DSC_54 Commissioning and periodic inspection tests that require decrypting and comprehension...

              3. DSC_55 In order to effect this basic communication test, the ECHO...

              4. DSC_56 Initialisation is performed according to 5.4.7 (DSC_44 — DSC_48) and...

              5. DSC_57 The REDCR then issues an ACTION, ECHO command conforming to...

              6. DSC_58 The DSRC-VU, when receiving the ECHO request, sends an ECHO...

          5. 5.5 Support for Directive 2015/71/EC

            1. 5.5.1 Overview

              1. DSC_59 To support the Directive 2015/719/EC on the maximal weights and...

            2. 5.5.2 Commands

              1. DSC_60 The commands used for an OWS transaction will be the...

            3. 5.5.3 Interrogation command sequence

              1. DSC_61 The interrogation command sequence for OWS data will be the...

            4. 5.5.4 Data structures

              1. DSC_62 The payload (OWS data) consists of the concatenation of

            5. 5.5.5 ASN.1 module for the OWS DSRC transaction

              1. DSC_63. The ASN.1 module definition for the DSRC data within the...

            6. 5.5.6 Elements of OwsData, actions performed and definitions

            7. 5.5.7 Data transfer mechanisms

              1. DSC_64 The Data transfer mechanism for OWS data between the Interrogator...

              2. DSC_65 The Data transfer between the platform collecting the maximal weights...

          6. 5.6 Data transfer between the DSRC-VU and VU

            1. 5.6.1 Physical Connection and interfaces

              1. DSC_66 The connection between the VU and the DSRC-VU can be...

              2. DSC_67 Regardless of the choice of the physical connection and interface,...

              3. DSC_68 a) In order that different suppliers may be contracted to...

                1. a) In order that different suppliers may be contracted to supply...

              4. DSC_69 b) the definition of the interfaces and connection between the...

                1. b) the definition of the interfaces and connection between the VU...

              5. DSC_70 c) the VU and DSRC-VU must support the operation of...

                1. c) the VU and DSRC-VU must support the operation of the...

            2. 5.6.2 Application Protocol

              1. DSC_71 The application protocol between the VU Remote Communication facility and...

              2. DSC_72 The following main commands are identified:

              3. DSC_73 In ASN1.0, the previous commands may be defined as:

              4. DSC_74 The description of the commands and parameters is following:

              5. DSC_75 The initialization of the communication link shall be done only...

              6. DSC_76 At the restart of the DSRC-VU or a VU, all...

          7. 5.7 Error handling

            1. 5.7.1 Recording and communication of the Data in the DSRC-VU

              1. DSC_77 The Data shall be provided, already secured, by the VUSM...

              2. DSC_78 The VU shall maintain a file identified by a unique...

              3. DSC_79 If the VUPM attempts to obtain VU data from the...

            2. 5.7.2 Wireless Communication errors

              1. DSC_80 Communication error handling shall be consistent with the related DSRC...

              2. 5.7.2.1 Encryption and signature errors

                1. DSC_81 Encryption and signature errors shall be handled as defined in...

              3. 5.7.2.2 Recording of errors

                1. DSC_82 The REDCR shall therefore record, time-stamped, the number of occasions...

                2. DSC_83 The REDCR shall therefore record, time-stamped, the number of occasions...

        6. 6. COMMISSIONING AND PERIODIC INSPECTION TESTS FOR THE REMOTE COMMUNICATION FUNCTION...

          1. 6.1 General

            1. DSC_84 Two type of tests are foreseen for the remote communication...

          2. 6.2 ECHO

          3. 6.3 Tests to validate the secure data content

            1. DSC_85 This test is execute to validate the end-to-end security flow...

            2. DSC_86 The workshop personnel must position the DSRC test reader at...

            3. DSC_87 Then the workshop personnel will insert a workshop card in...

      24. Appendix 15

        MIGRATION: MANAGING THE CO-EXISTENCE OF EQUIPMENT GENERATIONS

        1. 1. DEFINITIONS

        2. 2. GENERAL PROVISIONS

          1. 2.1. Overview of the transition

          2. 2.2. Interoperability between VU and cards

            1. MIG_001 Except as provided for in requirement MIG_004 and MIG_005, first...

            2. MIG_002 Second generation vehicle units shall be able to use any...

            3. MIG_003 This capability may be suppressed once and forever in such...

            4. MIG_004 Second generation vehicle units shall only be able to use...

            5. MIG_005 For determining the mode of operation, second generation vehicle units...

            6. MIG_006 Any valid second generation tachograph card shall be able to...

          3. 2.3. Interoperability between VU and MS

            1. MIG_007 Second generation vehicle units will not be able to be...

            2. MIG_008 Second generation motion sensors may be paired and used with...

          4. 2.4. Interoperability between vehicle units, tachograph cards and equipment for data...

            1. MIG_009 Equipment for data download may be used with one generation...

            2. 2.4.1 Direct card download by IDE

              1. MIG_010 Data shall be downloaded by IDE from tachograph cards of...

              2. MIG_011 To allow drivers' control by non EU control authorities, it...

            3. 2.4.2 Card download through a vehicle unit

              1. MIG_012 Data shall be downloaded from a second generation card inserted...

              2. MIG_013 Data shall be downloaded from a first generation card inserted...

            4. 2.4.3 Vehicle unit download

              1. MIG_014 Data shall be downloaded from second generation vehicle units using...

              2. MIG_015 To allow drivers' control by non EU control authorities and...

          5. 2.5. Interoperability between VU and calibration equipment

            1. MIG_016 Calibration equipment shall be able to perform calibration of each...

        3. 3. MAIN STEPS DURING THE PERIOD BEFORE THE INTRODUCTION DATE

          1. MIG_017 Test keys and certificates shall be available to manufacturers at...

          2. MIG_018 Interoperability tests shall be ready to start if requested by...

          3. MIG_019 Official keys and certificates shall be available to manufacturers at...

          4. MIG_020 Member states shall be able to issue second generation workshop...

          5. MIG_021 Member States shall be able to issue all types of...

        4. 4. PROVISIONS FOR THE PERIOD AFTER THE INTRODUCTION DATE

          1. MIG_022 After the introduction date, Member States shall only issue second...

          2. MIG_023 Vehicle units/motion sensors manufacturers shall be allowed to produce first...

          3. MIG_024 Vehicle units/motion sensors manufacturers shall be allowed to request and...

      25. Appendix 16

        ADAPTOR FOR M1 AND N1 CATEGORY VEHICLES

        1. 1. ABBREVIATIONS AND REFERENCE DOCUMENTS

          1. 1.1. Abbreviations

          2. 1.2. Reference standards

        2. 2. GENERAL CHARACTERISTICS AND FUNCTIONS OF THE ADAPTOR

          1. 2.1. Adaptor general description

            1. ADA_001 The adaptor shall provide a connected VU with secured motion...

            2. ADA_002 A type approved motion sensor (according to the provisions of...

          2. 2.2. Functions

            1. ADA_003 The adaptor shall include the following functions:

          3. 2.3. Security

            1. ADA_004 The adaptor shall not be security certified according to the...

        3. 3. REQUIREMENTS FOR THE RECORDING EQUIPMENT WHEN AN ADAPTOR IS INSTALLED...

          1. ADA_005 The recording equipment of any vehicle fitted with an adaptor...

          2. ADA_006 When an adaptor is installed, the recording equipment includes cables,...

          3. ADA_007 The detection of events and/or faults function of the recording...

          4. ADA_008 The adaptor faults detectable by the recording equipment shall be...

          5. ADA_009 The VU calibration function shall allow to automatically pair the...

        4. 4. CONSTRUCTION AND FUNCTIONAL REQUIREMENTS FOR THE ADAPTOR

          1. 4.1. Interfacing and adapting incoming speed pulses

            1. ADA_011 The adaptor input interface shall accept frequency pulses representative of...

            2. ADA_012 The adaptor input interface shall be able, if applicable, to...

          2. 4.2. Inducing the incoming pulses to the embedded motion sensor

            1. ADA_013 The incoming pulses, possibly adapted as specified above, shall be...

          3. 4.3. Embedded motion sensor

            1. ADA_014 The embedded motion sensor shall be stimulated by the induced...

            2. ADA_015 The identification data of the embedded motion sensor shall be...

            3. ADA_016 The installation data stored in the embedded motion sensor shall...

          4. 4.4. Security requirements

            1. ADA_017 The adaptor housing shall be designed so that it cannot...

            2. ADA_018 It shall not be possible to remove the embedded motion...

            3. ADA_019 The adaptor shall ensure that motion data may only been...

          5. 4.5. Performance characteristics

            1. ADA_020 The adaptor shall be fully operational in the temperature range...

            2. ADA_021 The adaptor shall be fully operational in the humidity range...

            3. ADA_022 The adaptor shall be protected against over-voltage, inversion of its...

            4. ADA_023 The adaptor shall either:

            5. ADA_024 The adaptor shall conform to international regulation UN ECE R10,...

          6. 4.6. Materials

            1. ADA_025 The adaptor shall meet the protection grade (TBD by the...

            2. ADA_026 The colour of the adaptor housing shall be yellow.

          7. 4.7. Markings

            1. ADA_027 A descriptive plaque shall be affixed to the adaptor and...

            2. ADA_028 The descriptive plaque shall also show the following details (if...

        5. 5. INSTALLATION OF THE RECORDING EQUIPMENT WHEN AN ADAPTOR IS USED...

          1. 5.1. Installation

            1. ADA_029 Adaptors to be installed in vehicles shall only be installed...

            2. ADA_030 Such approved workshop installing the adaptor shall adjust the input...

            3. ADA_031 Such approved workshop installing the adaptor shall seal the adaptor...

            4. ADA_032 The adaptor shall be fitted as close as possible to...

            5. ADA_033 The cables for providing the adaptor power supply shall be...

          2. 5.2. Sealing

            1. ADA_034 The following sealing requirements shall apply:

        6. 6. CHECKS, INSPECTIONS AND REPAIRS

          1. 6.1. Periodic inspections

            1. ADA_035 When an adaptor is used, each periodic inspection (periodic inspections...

            2. ADA_036 These inspections shall include a calibration and a replacement of...

        7. 7. TYPE APPROVAL OF RECORDING EQUIPMENT WHEN AN ADAPTOR IS USED...

          1. 7.1. General points

            1. ADA_037 Recording equipment shall be submitted for type approval complete, with...

            2. ADA_038 Any adaptor may be submitted for its own type approval,...

            3. ADA_039 Such type approval shall include functional tests involving the adaptor....

          2. 7.2. Functional certificate

            1. ADA_040 A functional certificate of an adaptor or of recording equipment...

Back to top

Options/Help

Print Options

You have chosen to open the Whole Regulation

The Whole Regulation you have selected contains over 200 provisions and might take some time to download. You may also experience some issues with your browser, such as an alert box that a script is taking a long time to run.

Would you like to continue?

You have chosen to open Schedules only

The Schedules you have selected contains over 200 provisions and might take some time to download. You may also experience some issues with your browser, such as an alert box that a script is taking a long time to run.

Would you like to continue?

Close

Legislation is available in different versions:

Latest Available (revised):The latest available updated version of the legislation incorporating changes made by subsequent legislation and applied by our editorial team. Changes we have not yet applied to the text, can be found in the ‘Changes to Legislation’ area.

Original (As adopted by EU): The original version of the legislation as it stood when it was first adopted in the EU. No changes have been applied to the text.

Close

Opening Options

Different options to open legislation in order to view more content on screen at once

Close

More Resources

Access essential accompanying documents and information for this legislation item from this tab. Dependent on the legislation item being viewed this may include:

  • the original print PDF of the as adopted version that was used for the EU Official Journal
  • lists of changes made by and/or affecting this legislation item
  • all formats of all associated documents
  • correction slips
  • links to related legislation and further information resources
Close

More Resources

Use this menu to access essential accompanying documents and information for this legislation item. Dependent on the legislation item being viewed this may include:

  • the original print PDF of the as adopted version that was used for the print copy
  • correction slips

Click 'View More' or select 'More Resources' tab for additional information including:

  • lists of changes made by and/or affecting this legislation item
  • confers power and blanket amendment details
  • all formats of all associated documents
  • links to related legislation and further information resources

The data on this page is available in the alternative data formats listed: