Commission Implementing Regulation (EU) 2016/799Show full title

4.2.1 Communication Protocol U.K.

GNS_14 The communication protocol between the external GNSS facility and the vehicle unit shall support three functions: U.K.

1.

The collection and distribution of GNSS data (e.g., position, timing, speed),

2.

The collection of the configuration data of the external GNSS facility,

3.

The management protocol to support the coupling, mutual authentication and session key agreement between the external GNSS facility and the VU.

GNS_15 The communication protocol shall be based on standard ISO/IEC 7816-4:2013 with the VU Secure Transceiver playing the master role and the GNSS Secure Transceiver playing the slave role. The physical connection between the external GNSS facility and the vehicule unit is based on ISO/IEC 7816-12:2005 or another standard able to support ISO/IEC 7816-4:2013 U.K.

[F1 GNS_16 In the communication protocol, extended length fields shall not be supported.] U.K.

Textual Amendments

F1 Substituted by Commission Implementing Regulation (EU) 2018/502 of 28 February 2018 amending Implementing Regulation (EU) 2016/799 laying down the requirements for the construction, testing, installation, operation and repair of tachographs and their components (Text with EEA relevance).

GNS_17 The communication protocol of ISO 7816 (both *-4:2013 and *-12:2005) between the external GNSS facility and the VU shall be set to T = 1. U.K.

[F1 GNS_18 Regarding the functions 1) the collection and distribution of GNSS data and 2) the collection of the configuration data of the external GNSS facility and 3) management protocol, the GNSS Secure Transceiver shall simulate a smart card with a file system architecture composed by a Master File (MF), a Dedicated File (DF) with Application Identifier specified in Appendix 1 chapter 6.2 ( ‘ FF 44 54 45 47 4D ’ ) and with 3 EFs containing certificates and one single Elementary File (EF.EGF) with file identifier equal to ‘ 2F2F ’ as described in Table 1.] U.K.

GNS_19 The GNSS Secure Transceiver shall store the data coming from the GNSS receiver and the configuration in the EF.EGF. This is a linear, variable-length record file with an identifier equal to ‘2F2F’ in hexadecimal format. U.K.

[F1 GNS_20 The GNSS Secure Transceiver shall use a memory to store the data and be able to perform at least 20 millions write/read cycles. Apart from this aspect, the internal design and implementation of the GNSS Secure Transceiver is left to the manufacturers. U.K.

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

GNS_21 The file structure is provided in Table 1. For the access conditions (ALW, NEV, SM-MAC) see Appendix 2 chapter 3.5. U.K.

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’