- Latest available (Revised)
- Original (As adopted by EU)
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)
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.
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.).
There are outstanding changes not yet made to Commission Implementing Regulation (EU) 2016/799. Any changes that have already been made to the legislation appear in the content and are referenced with annotations.
Revised legislation carried on this site may not be fully up to date. Changes and effects are recorded by our editorial team in lists which can be found in the ‘Changes to Legislation’ area. Where those effects have yet to be applied to the text of the legislation by the editorial team they are also listed alongside the legislation in the affected provisions. Use the ‘more’ link to open the changes and effects relevant to the provision you are viewing.
The collection and distribution of GNSS data (e.g., position, timing, speed),
The collection of the configuration data of the external GNSS facility,
The management protocol to support the coupling, mutual authentication and session key agreement between the external GNSS facility and the VU.
Textual Amendments
The mapping of record numbers and data is provided in Table 1. Note that there are five GSA sentences for the GNSS constellations and Satellite-Based Augmentation System (SBAS).]
Table 1 | ||||
File Structure | ||||
Access conditions | ||||
---|---|---|---|---|
File | File ID | Read | Update | Encrypted |
MF | 3F00 | |||
EF.ICC | 0002 | ALW | NEV (by VU) | No |
DF GNSS Facility | 0501 | ALW | NEV | No |
EF EGF_MACertificate | C100 | ALW | NEV | No |
EF CA_Certificate | C108 | ALW | NEV | No |
EF Link_Certificate | C109 | ALW | NEV | No |
EF.EGF | 2F2F | SM-MAC | NEV (by VU) | No |
File / Data element | Record no | Size (bytes) | Default values | |
---|---|---|---|---|
Min | Max | |||
MF | 552 | 1 031 | ||
EF.ICC | ||||
sensorGNSSSerialNumber | 8 | 8 | ||
DF GNSS Facility | 612 | 1 023 | ||
EF EGF_MACertificate | 204 | 341 | ||
EGFCertificate | 204 | 341 | {00..00} | |
EF CA_Certificate | 204 | 341 | ||
MemberStateCertificate | 204 | 341 | {00..00} | |
EF Link_Certificate | 204 | 341 | ||
LinkCertificate | 204 | 341 | {00..00} | |
EF.EGF | ||||
RMC NMEA Sentence | ‘01’ | 85 | 85 | |
1st GSA NMEA Sentence | ‘02’ | 85 | 85 | |
2nd GSA NMEA Sentence | ‘03’ | 85 | 85 | |
3rd GSA NMEA Sentence | ‘04’ | 85 | 85 | |
4th GSA NMEA Sentence | ‘05’ | 85 | 85 | |
5th GSA NMEA Sentence | ‘06’ | 85 | 85 | |
Extended serial-number of the external GNSS facility defined in Appendix 1 as SensorGNSSSerialNumber. | ‘07’ | 8 | 8 | |
Operating system identifier of the GNSS Secure Transceiver defined in Appendix 1 as SensorOSIdentifier. | ‘08’ | 2 | 2 | |
Type approval number of the external GNSS facility defined in Appendix 1 as SensorExternalGNSSApprovalNumber. | ‘09’ | 16 | 16 | |
Identifier of the security component of the external GNSS facility defined in Appendix 1 as SensorExternalGNSSSCIdentifier | ‘10’ | 8 | 8 | |
RFU — Reserved for Future Use | From ‘11’ to ‘FD’ |
The coupling process has been completed as described in Appendix 11. Common security mechanisms.
The periodic mutual authentication and session key agreement between the VU and the external GNSS facility also described in Appendix 11. Common security mechanisms has been executed with the indicated frequency.
The VU requests location data from the External GNSS facility together with Dilution of Precision data (from the GSA NMEA sentence). The VU Secure Transceiver shall use the ISO/IEC 7816-4:2013 SELECT and READ RECORD(S) command in secure messaging authentication-only mode as described in Appendix 11 section 11.5 with the file identifier ‘2F2F’ and RECORD number equal to ‘01’ for RMC NMEA sentence and ‘02’,‘03’,‘04’,‘05’,‘06’ for GSA NMEA sentence.
The last location data received is stored in the EF with identifier ‘2F2F’ and the records described in Table 1 in the GNSS secure transceiver as the GNSS secure transceiver receives NMEA data with a frequency of at least 1 Hz from the GNSS receiver through the GNSS data interface.
The GNSS Secure Transceiver sends the response to the VU Secure Transceiver by using the APDU response message in secure messaging authentication-only mode as described in Appendix 11 section 11.5.
The VU Secure Transceiver checks the authenticity and integrity of the received response. In case of positive outcome, the location data is transferred to the VU processor through the GNSS data interface.
[F1The VU processor checks the received data extracting the information (e.g., latitude, longitude, time) from the RMC NMEA sentence. The RMC NMEA sentence includes the information if the position is valid. If the position is not valid, the location data is not available yet and it cannot be used to record the position of the vehicle. If the position is valid, the VU processor also extracts the values of HDOP from GSA NMEA sentences and calculate the minimum value on the available satellite systems (i.e., when the fix is available).]
The VU processor stores the received and processed information such as latitude, longitude, time and speed in the VU in the format defined in Appendix 1 Data Dictionary as GeoCoordinates together with the value of HDOP calculated as the minimum of the HDOP values collected on the available GNSS systems.
This section describes in detail the structure of the Read Record command. Secure messaging (authentication-only mode) is added as described in Appendix 11 Common security mechanisms.
Byte | Length | Value | Description |
---|---|---|---|
CLA | 1 | ‘0Ch’ | Secure messaging asked. |
INS | 1 | ‘B2h’ | Read Record |
P1 | 1 | ‘XXh’ | Record number (‘00’ references the current record) |
P2 | 1 | ‘04h’ | Read the record with the record number indicated in P1 |
Le | 1 | ‘XXh’ | Length of data expected. Number of Bytes to be read. |
Byte | Length | Value | Description |
---|---|---|---|
#1-#X | X | ‘XX..XXh’ | Data read |
SW | 2 | ‘XXXXh’ | Status Words (SW1,SW2) |
If the command is successful, the GNSS secure transceiver returns ‘9000’.
If the current file is not record oriented, the GNSS secure transceiver returns ‘6981’.
If the command is used with P1 = ‘00’ but there is no current EF the GNSS secure transceiver returns ‘6986’ (command not allowed).
If the record is not found, the GNSS secure transceiver returns ‘6A 83’.
If the external GNSS facility has detected tampering, it shall return status words ‘66 90’.
Command | Reference |
---|---|
Select | Appendix 2 chapter 3.5.1 |
Read Binary | Appendix 2 chapter 3.5.2 |
Get Challenge | Appendix 2 chapter 3.5.4 |
PSO: Verify Certificate | Appendix 2 chapter 3.5.7 |
External Authenticate | Appendix 2 chapter 3.5.9 |
General Authenticate | Appendix 2 chapter 3.5.10 |
MSE:SET | Appendix 2 chapter 3.5.11 |
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?
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?
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.
Geographical Extent: Indicates the geographical area that this provision applies to. For further information see ‘Frequently Asked Questions’.
Show Timeline of Changes: See how this legislation has or could change over time. Turning this feature on will show extra navigation options to go to these specific points in time. Return to the latest available version by using the controls above in the What Version box.
Access essential accompanying documents and information for this legislation item from this tab. Dependent on the legislation item being viewed this may include:
This timeline shows the different versions taken from EUR-Lex before exit day and during the implementation period as well as any subsequent versions created after the implementation period as a result of changes made by UK legislation.
The dates for the EU versions are taken from the document dates on EUR-Lex and may not always coincide with when the changes came into force for the document.
For any versions created after the implementation period as a result of changes made by UK legislation the date will coincide with the earliest date on which the change (e.g an insertion, a repeal or a substitution) that was applied came into force. For further information see our guide to revised legislation on Understanding Legislation.
Use this menu to access essential accompanying documents and information for this legislation item. Dependent on the legislation item being viewed this may include:
Click 'View More' or select 'More Resources' tab for additional information including: