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)

- DSC_31The design of the DSRC-VU antenna shall be a function of commercial design, operating within the limits defined in 5.3.2 which is adapted to optimise the reading performance of the DSRC-REDCR for the specific purpose and read circumstances in which the REDCR has been designed to operate.

• DSC_32The VU antenna shall be fixed to, or close to, the front windshield of the vehicle as specified in 5.1 above.

• DSC_33In the test environment in a workshop (see section 6.3), a DSRC-VU antenna, affixed according to 5.1 above, shall successfully connect with a standard test communication and successfully provide an RTM transaction as defined within this Appendix, at a distance between 2 and 10 meters, better than 99 % of the time, averaged over 1 000 read interrogations.

5.4   DSRC Protocol requirements for RTM

5.4.1   Overview

• DSC_34The transaction protocol to download the Data across the 5.8 GHz DSRC interface link shall be according to the following steps. This section describes a transaction flow under ideal conditions without retransmissions or communication interrupts.

NOTE The purpose of the initialisation phase (Step 1) is to set up the communication between the REDCR and DSRC-VUs that have entered the 5.8 GHz DSRC (master-slave) transaction zone but have not yet established communication with the REDCR, and to notify the application processes.

• — Step 1Initialisation. The REDCR sends a frame containing a ‘beacon service table’ (BST) that includes the application identifiers (AIDs) in the service list that it supports. In the RTM application this will simply be the service with the AID value = 2 (Freight&Fleet). The DSRC-VU evaluates the received BST, and shall respond (see below) with the list of the supported applications within the Freight&Fleet domain, or shall not respond if none are supported. If the REDCR does not offer AID=2, the DSRC-VU shall not answer to the REDCR.

• — Step 2The DSRC-VU sends a frame containing a request for a private window allocation.

- — Step 3The REDCR sends a frame containing a private window allocation.

• — Step 4The DSRC-VU uses the allocated private window to send a frame containing its vehicle service table (VST). This VST includes a list of all the different application instantiations that this DSRC-VU supports in the framework of AID=2. The different instantiations shall be identified by means of uniquely generated EIDs, each associated with an Application Context Mark parameter value indicating the application and standard supported.

- — Step 5Next the REDCR analyses the offered VST, and either terminates the connection (RELEASE) since it is not interested in anything the VST has to offer (i.e. it is receiving a VST from a DSRC-VU that is not supporting the RTM transaction), or, if it receives an appropriate VST it starts an app instantiation.

- — Step 6To bring this about, the REDCR shall send a frame containing a command to retrieve the RTM data, identifying the RTM application instantiation by specifying the identifier corresponding to the RTM application instantiation (as specified by the DSRC-VU in the VST), and shall allocate a private window.

• — Step 7The DSRC-VU uses the newly allocated private window to send a frame that contains the addressed identifier corresponding to the RTM application instantiation as provided in the VST, followed by the attribute RtmData (payload element + security element).

• — Step 8If there are multiple services requested, the value ‘n’ is changed to the next service reference number and the process repeated.

- — Step 9The REDCR confirms receipt of the data by sending a frame containing a RELEASE command to the DSRC-VU to terminate the session OR if it has failed to validate a successful receipt of the LDPU goes back to step 6.

• See Figure 14.6 for a pictorial description of the transaction protocol.

Figure 14.6

RTM over 5,8 GHz DSRC process flow

Image omitted; see official source

5.4.2   Commands

- DSC_35The following commands are the only functions used in an RTM transaction phase

• — INITIALISATION.request : A command, issued from the REDCR in the form of a broadcast with definition of applications that the REDCR supports.

• — INITIALISATION.response : An answer from the DSRC-VU confirming the connection and containing a list of supported application instances with characteristics and information how to address them (EID).

- — GET.request : A command, issued from the REDCR to the DSRC-VU, that specifies the application instantiation to be addressed by means of a defined EID, as received in the VST, instructing the DSRC-VU to send the selected attribute(s) with the Data. The objective of the GET command is for the REDCR to obtain the Data from the DSRC-VU.

- — GET.response : An answer from the DSRC-VU that contains the Data requested.

• — ACTION.request ECHO : A command, instructing the DSRC-VU to send back data from the DSRC-VU to the REDCR. The objective of the ECHO command is to enable workshops or type approval test facilities to test that the DSRC link is working without needing access to security credentials.

• — ACTION.response ECHO : An answer from the DSRC VU on the ECHO command.

- — EVENT_REPORT.request RELEASE : A command, instructing the DSRC-VU that the transaction is ended. The objective of the RELEASE command is to end the session with the DSRC-VU. On receipt of the RELEASE the DSRC-VU shall not respond to any further interrogations under the current connection. Note that according to EN 12834 a DSRC-VU will not connect twice to the same interrogator unless it has been out of the communication zone for 255 seconds or if the Beacon ID of the interrogator is changed.

5.4.3   Interrogation command sequence

• DSC_36From the perspective of the command and response sequence, the transaction is described as follows:

Sequence	Sender		Receiver	Description	Action
1	REDCR	>	DSRC-VU	Initialisation of the communication link — Request	REDCR broadcasts BST
2	DSRC-VU	>	REDCR	Initialisation of the communication link — Response	If BST supports AID=2 then DSRC-VU Requests a private window
3	REDCR	>	DSRC-VU	Grants a private window	Sends Frame containing private window allocation
4	DSRC-VU	>	REDCR	Sends VST	Sends Frame comprising VST
5	REDCR	>	DSRC-VU	Sends GET.request for data in Attribute for specific EID
6	DSRC-VU	>	REDCR	Sends GET.response with requested Attribute for specific EID	Sends Attribute (RTMData, OWSData….) with data for specific EID
7	REDCR	>	DSRC-VU	Sends GET.request for data of other Attribute (if appropriate)
8	DSRC-VU	>	REDCR	Sends GET.response with requested Attribute	Sends Attribute with data for specific EID
9	REDCR	>	DSRC-VU	Acknowledges successful receipt of data	Sends RELEASE command which closes transaction
10	DSRC-VU			Closes transaction

• An example of the transaction sequence and contents of the exchanged frames is defined in clauses 5.4.7 and 5.4.8

5.4.4   Data structures

- DSC_37The semantic structure of the Data when passed across the 5.8 GHz DSRC interface shall be consistent with what described in this Appendix. The way these data are structured is specified in this clause.

• DSC_38The payload (RTM data) consists of the concatenation of

• 1. EncryptedTachographPayload data, which is the encryption of the TachographPayload defined in ASN.1 in section 5.4.5. The method of encryption is described in Appendix 11

- 2. DSRCSecurityData, specified in Appendix 11.

- DSC_39The RTM Data is being addressed as RTM Attribute=1 and is transferred in the RTM container = 10.

• DSC_40The RTM Context Mark shall identify the supported standard part in the TARV series of standards (RTM corresponds to Part 9)

• The ASN.1 module definition for the DSRC data within the RTM application is defined as follows:

• Image omitted; see official source

Image omitted; see official source

5.4.5   Elements of RtmData, actions performed and definitions

- DSC_41The data values to be calculated by the VU and used to update the secured data in the DSRC-VU shall be calculated according to the rules defined in Table 14.3:

Table 14.3

Elements of RtmData, actions performed and definitions

| (1) RTM Data Element | (2) Action performed by the VU | | (3) ASN.1 definition of data |

| --- | --- | --- | --- | | RTM1 Vehicle Registration Plate | The VU shall set the value of the tp15638VehicleRegistrationPlate data element RTM1 from the recorded value of the data type VehicleRegistrationIdentification as defined in Appendix 1 VehicleRegistrationIdentification | Vehicle Registration Plate expressed as a string of characters | tp15638VehicleRegistrationPlate LPN, --Vehicle RegistrationPlate using the data structure from ISO 14906, but with the following limitation for the RTM application: the SEQUENCE starts with the Country Code, followed by an alphabet indicator, followed by the plate number itself, which is always 14 octets (padded with zero's) so the LPN type length is always 17 octets (no length determinant needed), of which 14 are the ‘real’ plate number. | | RTM2 Speeding Event | The VU shall generate a Boolean value for data element RTM2 tp15638SpeedingEvent. The tp15638SpeedingEvent value shall be calculated by the VU from the over speeding events recorded in the VU within the last 10 days, as defined in Annex IC. | 1 (TRUE): if the most recent over speeding event ended within the last 10 days or is still ongoing; 0 (FALSE): in any other case. | tp15638SpeedingEvent BOOLEAN, | | RTM3 Driving Without Valid Card | The VU shall generate a Boolean value for data element RTM3 tp15638DrivingWithoutValidCard. The VU shall assign a value of TRUE to the tp15638DrivingWithoutValidCard variable if at least one driving without an appropriate card event has been recorded in the VU within the last 10 days as defined in Annex IC. | 1 (TRUE): if the most recent driving without an appropriate card event ended within the last 10 days or is still ongoing; 0 (FALSE): in any other case. | tp15638DrivingWithoutValidCard BOOLEAN, | | RTM4 Valid Driver Card | The VU shall generate a Boolean value for data element RTM4 tp15638DriverCard on the basis of the inserted valid driver card in the driver slot. | 1 (TRUE): if no valid driver card is present in the driver slot of the VU; 0 (FALSE): if a valid driver card is present in the driver slot of the VU. | tp15638DriverCard BOOLEAN, | | RTM5 Card Insertion while Driving | The VU shall generate a Boolean value for data element RTM5 tp15638CardInsertion. The VU shall assign a value of TRUE to the tp15638CardInsertion variable if at least one card insertion while driving event has been recorded in the VU within the last 10 days as defined in Annex IC. | 1 (TRUE): if the most recent card insertion while driving event has occurred within the last 10 days; 0 (FALSE): in any other case. | tp15638CardInsertion BOOLEAN, | | RTM6 Motion Data Error | The VU shall generate a Boolean value for data element RTM6. The VU shall assign a value of TRUE to the tp15638MotionDataError variable if at least one motion data error event has been recorded in the VU within the last 10 days as defined in Annex IC. | 1 (TRUE): if the most recent motion data error event ended within the last 10 days or is still ongoing; 0 (FALSE): in any other case. | tp15638MotionDataError BOOLEAN, | | RTM7 Vehicle Motion Conflict | The VU shall generate a Boolean value for data element RTM7. The VU shall assign a value of TRUE to the tp15638VehicleMotionConflict variable if at least one vehicle motion conflict event has been recorded in the VU within the last 10 days. | 1 (TRUE): if the most recent vehicle motion conflict event ended within the last 10 days or is still ongoing; 0 (FALSE): in any other case. | tp15638VehicleMotionConflict BOOLEAN, | | RTM8 2nd Driver Card | The VU shall generate a Boolean value for data element RTM8 on the basis of Annex IC (Driver Activity Data CREW and CO-DRIVER). If a valid co-driver card is present the VU shall set the value of RTM8 to TRUE. | 1 (TRUE): if a valid co-driver card is present in the VU; 2 (FALSE): if no valid co-driver card is present in the VU. | tp156382ndDriverCard BOOLEAN, | | RTM9 Current Activity | The VU shall generate a Boolean value for data element RTM9. If the current activity is recorded in the VU as any activity other than DRIVING as defined in Annex IC the VU shall set the value of RTM9 to TRUE. | 1 (TRUE): other activity selected; 0 (FALSE): driving selected | tp15638CurrentActivityDriving BOOLEAN | | RTM10 Last Session Closed | The VU shall generate a Boolean value for data element RTM10. If the last card session was not properly closed as defined in Annex IC the VU shall set the value of RTM10 to TRUE. | 1 (TRUE): at least one of the inserted cards has triggered a last card session not correctly closed event; 0 (FALSE): None of the inserted cards has triggered a last card session not correctly closed event. | tp15638LastSessionClosed BOOLEAN | | RTM11 Power Supply Interruption | The VU shall generate an integer value for data element RTM11. The VU shall assign a value for the tp15638PowerSupplyInterruption variable equal to the number of the recorded power supply interruption events stored in the VU within last 10 days as defined in Annex IC. If no power supply interruption event has been recorded in the VU within the last 10 days, it shall set the value of RTM11 to 0. | Number of the recorded power supply interruption events within the last 10 days. | tp15638PowerSupplyInterruption INTEGER (0..127), | | RTM12 Sensor Fault | The VU shall generate an integer value for data element RTM12. The VU shall assign to the variable sensorFault a value of: — 1 if an event of type ‘35’H Sensor — fault ended during the last 10 days or is still ongoing. — 2 if an event of type GNSS receiver fault (either internal or external with enum values ‘36’H or — ‘37’H) ended during the last 10 days or is still ongoing. — 3 if an event of type ‘0E’H Communication error with the external GNSS facility event ended during the last 10 days or is still ongoing. — 4 If both Sensor Fault and GNSS receiver faults ended during the last 10 days or are still ongoing. — 5 If both Sensor Fault and Communication error with the external GNSS facility event ended during the last 10 days or are still ongoing. — 6 If both GNSS receiver fault and Communication error with the external GNSS facility event ended during the last 10 days or are still ongoing. — 7 If all three sensor faults ended during the last 10 days or are still ongoing. If no event have ended during the last 10 days or is still ongoing, the VU shall set the value of RTM12 to 0. | --sensor fault one octet as per data dictionary | tp15638SensorFault INTEGER (0..255), | | RTM13 Time Adjustment | The VU shall generate an integer value (timeReal from Appendix 1) for data element RTM13 on the basis of the presence of Time Adjustment data as defined in Annex IC. The VU shall set the value of RTM13 to the time at which the last time adjustment data event has occurred. If no time adjustment event as defined in Annex IC is present in the VU data, it shall set the value of RTM13 to 0. | oldTimeValue of the most recent time adjustment. | tp15638TimeAdjustment INTEGER(0..4294967295), | | RTM14 Security Breach Attempt | The VU shall generate an integer value (timeReal from Appendix 1) for data element RTM14 on the basis of the presence of a security breach attempt event as defined in Annex IC. The VU shall set the value of the time of the latest security breach attempt event recorded by the VU. If no security breach attempt event as defined in Annex IC is present in the VU data, it shall set the value of RTM14 to 0. | Beginning time of the latest stored security breach attempt event. | tp15638LatestBreachAttempt INTEGER(0..4294967295), | | RTM15 Last Calibration | The VU shall generate an integer value (timeReal from Appendix 1) for data element RTM15 on the basis of the presence of Last Calibration data as defined in Annex IC and Appendix 1. The VU shall set the value of RTM15 to the oldTimeValue of the latest calibration record. If there has been no calibration, the VU shall set the value of RTM15 to 0. | oldTimeValue of the most recent calibration record. | tp15638LastCalibrationData INTEGER(0..4294967295), | | RTM16 Previous Calibration | The VU shall generate an integer value (timeReal from Appendix 1) for data element RTM16 on the basis of the calibration record preceding the last calibration. The VU shall set the value of RTM16 to the oldTimeValue of the calibration record preceding the last calibration. If there has been no previous calibration, the VU shall set the value of RTM16 to 0. | oldTimeValue of the calibration record preceding the most recent calibration record. | tp15638PrevCalibrationData INTEGER(0..4294967295), | | RTM17 Date Tachograph Connected | The VU shall generate an integer value (timeReal from Appendix 1) for data element RTM17. The VU shall set the value of RTM17 to the date of first calibration of the VU in the current vehicle. The VU shall extract this data from the VuCalibrationData (Appendix 1) from the vuCalibrationRecords with CalibrationPurpose equal to: ‘03’H If there has been no previous calibration, the VU shall set the value of RTM17 to 0. | Date of first calibration of the VU in the current vehicle. | tp15638DateTachoConnected INTEGER(0..4294967295), | | RTM18 Current Speed | The VU shall generate an integer value for data element RTM18. The VU shall set the value of RTM18 to the last current recorded speed at the time of the latest update of the RtmData. | Last current recorded speed | tp15638CurrentSpeed INTEGER (0..255), | | RTM19 Timestamp | The VU shall generate an integer value for data element RTM19 (timeReal from Appendix 1). The VU shall set the value of RTM19 to the time of the latest update of the RtmData. | Timestamp of current TachographPayload record | tp15638Timestamp INTEGER(0..4294967295), | | RTM20 Time at which the latest authenticated vehicle position was available | The VU shall generate an integer value (timeReal from Appendix 1) for data element RTM20. The VU shall set the value of RTM20 to the time at which the latest authenticated vehicle position was available from the GNSS receiver. If no authenticated vehicle position was available ever from the GNSS receiver the VU shall set the value of RTM20 to 0. | Timestamp of the latest authenticated vehicle position | tp15638LatestAuthenticatedPosition INTEGER(0..4294967295), | | RTM21 Continuous driving time | The VU shall generate an integer value for data element RTM21. The VU shall set the value of RTM21 to the ongoing continuous driving time of the driver. | Continuous driving time of the driver, encoded as an integer value. Length: 1 byte Resolution: 2 minutes/bit No offset Data range: 0 to 250 A value of 250 shall indicate that the continuous driving time of the driver is equal or greater than 500 minutes. Values 251 to 254 are not used. Value 255 indicates that the information is not available. | tp15638ContinuousDrivingTime INTEGER(0..255), | | RTM22 Longest daily driving time for the ongoing and previous RTM-shift, calculated in accordance with the Addendum to Appendix 14 | The VU shall generate an integer value for data element RTM22. The VU shall set the value of RTM22 to the longer of the two daily driving times of the driver, being either the ongoing or the previous RTM-shift. | Daily driving time of the driver, encoded as an integer value. Length: 1 byte Resolution: 4 minutes/bit No offset Data range: 0 to 250 A value of 250 shall indicate that the daily driving time of the driver is equal or greater than 1 000 minutes. Values 251 to 254 are not used. Value 255 indicates that the information is not available. | tp15638DailyDrivingTimeShift INTEGER(0..255), | | RTM23 Longest daily driving time within the ongoing week, calculated in accordance with the Addendum to Appendix 14 | The VU shall generate an integer value for data element RTM23. The VU shall set the value of RTM23 to the longest daily driving time of the driver, being either the ongoing RTM-shift or any completed RTM-shift having started or finished in the ongoing week. | Daily driving time of the driver, encoded as an integer value. Length: 1 byte Resolution: 4 minutes/bit No offset Data range: 0 to 250 A value of 250 shall indicate that the daily driving time of the driver is equal or greater than 1 000 minutes. Values 251 to 254 are not used. Value 255 indicates that the information is not available. | tp15638DailyDrivingTimeWeek INTEGER(0..255), | | RTM24 Weekly driving time, calculated in accordance with the Addendum to Appendix 14 | The VU shall generate an integer value for data element RTM24. The VU shall set the value of RTM24 to the weekly driving time of the driver. | Weekly driving time of the driver, encoded as an integer value. Length: 1 byte Resolution: 20 minutes/bit No offset Data range: 0 to 250 A value of 250 shall indicate that the weekly driving time of the driver is equal or greater than 5 000 minutes. Values 251 to 254 are not used. Value 255 indicates that the information is not available. | tp15638WeeklyDrivingTime INTEGER(0..255), | | RTM25 Fortnightly driving time, calculated in accordance with the Addendum to Appendix 14 | The VU shall generate an integer value for data element RTM25. The VU shall set the value of RTM25 to the fortnightly driving time of the driver. | Fortnightly driving time of the driver, encoded as an integer value. Length: 1 byte Resolution: 30 minutes/bit No offset Data range: 0 to 250 A value of 250 shall indicate that the fortnightly driving time of the driver is equal or greater than 7 500 minutes. Values 251 to 254 are not used. Value 255 indicates that the information is not available. | tp15638FortnightlyDrivingTime INTEGER(0..255), |

Note: RTM22, RTM23, RTM24 and RTM25 shall be computed according to the Addendum to this Appendix

5.4.6   Data transfer mechanism

• DSC_42Payload data defined previously are requested by the REDCR after initialisation phase, and consequently transmitted by the DSRC-VU in the allocated window. The command GET is used by the REDCR to retrieve data.

- DSC_43For all DSRC exchanges, data shall be encoded using PER (Packed Encoding Rules) UNALIGNED, apart from Image omitted; see official source and Image omitted; see official source , which shall be encoded using OER (Octet Encoding Rules) defined in ISO/IEC 8825-7, Rec. ITU-T X.696.

5.4.7   Detailed DSRC transaction description

• DSC_44Initialisation is performed according to DSC_44 — DSC_48 and Tables 14.4 — 14.9. In the initialisation phase, the REDCR starts sending a frame containing a BST (Beacon Service Table) according to EN 12834 and EN 13372, 6.2, 6.3, 6.4 and 7.1 with settings as specified in the following Table 14.4.

Table 14.4

Initialisation — BST frame settings

| Field | Settings |

| --- | --- | | Link Identifier | Broadcast address | | BeaconId | As per EN 12834 | | Time | As per EN 12834 | | Profile | No extension, 0 or 1 to be used | | MandApplications | No extension, EID not present, Parameter not present, AID= 2 Freight&Fleet | | NonMandApplications | Not present | | ProfileList | No extension, number of profiles in list = 0 | | Fragmentation header | No fragmentation | | Layer 2 settings | Command PDU, UI command |

• A practical example of the settings specified in Table 14.4, with an indication of bit encodings, is given in the following Table 14.5.

Table 14.5

Initialisation — BST frame contents example

| Octet # | Attribute/Field | Bits in octet | Description |

| --- | --- | --- | --- | | 1 | FLAG | Image omitted; see official source | Start flag | | 2 | Broadcast ID | Image omitted; see official source | Broadcast address | | 3 | MAC Control Field | Image omitted; see official source | Command PDU | | 4 | LLC Control field | Image omitted; see official source | UI command | | 5 | Fragmentation header | Image omitted; see official source | No fragmentation | | 6 | BST | Image omitted; see official source | Initialisation request | | 6 | SEQUENCE { | | | | 6 | OPTION indicator BeaconID SEQUENCE { ManufacturerId INTEGER (0..65535) | Image omitted; see official source | NonMand applications not present | | 6 | | | | | 6 | | Image omitted; see official source | Manufacturer Identifier | | 7 | | Image omitted; see official source | | | 8 | | Image omitted; see official source | | | 8 | IndividualID INTEGER (0..134217727) } | Image omitted; see official source | 27 bit ID available for manufacturer | | 9 | IndividualID INTEGER (0..134217727) } | Image omitted; see official source | 27 bit ID available for manufacturer | | 10 | IndividualID INTEGER (0..134217727) } | Image omitted; see official source | 27 bit ID available for manufacturer | | 11 | IndividualID INTEGER (0..134217727) } | Image omitted; see official source | 27 bit ID available for manufacturer | | 12 | Time INTEGER (0..4294967295) | Image omitted; see official source | 32 bit UNIX real time | | 13 | Time INTEGER (0..4294967295) | Image omitted; see official source | 32 bit UNIX real time | | 14 | Time INTEGER (0..4294967295) | Image omitted; see official source | 32 bit UNIX real time | | 15 | Time INTEGER (0..4294967295) | Image omitted; see official source | 32 bit UNIX real time | | 16 | Profile INTEGER (0..127,...) | Image omitted; see official source | No extension. Example profile 0 | | 17 | MandApplications SEQUENCE (SIZE(0..127,...)) OF { | Image omitted; see official source | No extension, Number of mandApplications = 1 | | 18 | SEQUENCE { | | | | 18 | OPTION indicator | Image omitted; see official source | EID not present | | 18 | OPTION indicator | Image omitted; see official source | Parameter not present | | 18 | AID DSRCApplicationEntityID } } | Image omitted; see official source | No extension. AID= 2 Freight&Fleet | | 19 | ProfileList SEQUENCE (0..127,...) OF Profile } | Image omitted; see official source | No extension, number of profiles in list = 0 | | 20 | FCS | Image omitted; see official source | Frame check sequence | | 21 | FCS | Image omitted; see official source | Frame check sequence | | 22 | Flag | Image omitted; see official source | End Flag |

• DSC_45A DSRC-VU, when receiving a BST, requires the allocation of a private window, as specified by EN 12795 and EN 13372, 7.1.1, with no specific RTM settings. Table 14.6 provides an example of bit encoding.

Table 14.6

Initialisation — Private window allocation request frame contents

| Octet # | Attribute/Field | Bits in octet | Description |

| --- | --- | --- | --- | | 1 | FLAG | Image omitted; see official source | Start flag | | 2 | Private LID | Image omitted; see official source | Link address of specific DSRC-VU | | 3 | Private LID | Image omitted; see official source | Link address of specific DSRC-VU | | 4 | Private LID | Image omitted; see official source | Link address of specific DSRC-VU | | 5 | Private LID | Image omitted; see official source | Link address of specific DSRC-VU | | 6 | MAC Control field | Image omitted; see official source | Private window request | | 7 | FCS | Image omitted; see official source | Frame check sequence | | 8 | FCS | Image omitted; see official source | Frame check sequence | | 9 | Flag | Image omitted; see official source | End Flag |

• DSC_46The REDCR then answers by allocating a private window, as specified by EN 12795 and EN 13372, 7.1.1 with no specific RTM settings.

• Table 14.7 provides an example of bit encoding.

Table 14.7

Initialisation — Private window allocation frame contents

Octet #	Attribute/Field	Bits in octet	Description
1	FLAG	Image omitted; see official source	Start flag
2	Private LID	Image omitted; see official source	Link address of the specific DSRC-VU
3	Private LID	Image omitted; see official source	Link address of the specific DSRC-VU
4	Private LID	Image omitted; see official source	Link address of the specific DSRC-VU
5	Private LID	Image omitted; see official source	Link address of the specific DSRC-VU
6	MAC Control field	Image omitted; see official source	Private window allocation
7	FCS	Image omitted; see official source	Frame check sequence
8	FCS	Image omitted; see official source	Frame check sequence
9	Flag	Image omitted; see official source	End Flag

• DSC_47The DSRC-VU, when receiving the private window allocation, sends its VST (Vehicle Service Table) as defined in EN 12834 and EN 13372, 6.2, 6.3, 6.4 and 7.1 with settings as specified Table 14.8, using the allocated transmission window.

Table 14.8

Initialisation — VST frame settings

Field	Settings
Private LID	As per EN 12834
VST parameters	Fill=0, then for each supported application: EID present, parameter present, AID=2, EID as generated by the OBU
Parameter	No extension, Contains the RTM Context Mark
ObeConfiguration	The optional ObeStatus field may be present, but shall not be used by the REDCR
Fragmentation header	No fragmentation
Layer 2 settings	Command PDU, UI command

• DSC_48The DSRC-VU shall support the ‘Freight and Fleet’ application, identified by the Application Identifier ‘2’. Other Application Identifiers may be supported, but shall not be present in this VST, as the BST only requires AID=2. The ‘Applications’ field contains a list of the supported application instances in the DSRC-VU. For each supported application instantiation, a reference to the appropriate standard is given, made of an Rtm Context mark, which is composed of an OBJECT IDENTIFIER representing the related standard, its part (9 for RTM) and possibly its version, plus an EID that is generated by the DSRC-VU, and associated to that application instance.

• A practical example of the settings specified in Table 14.8, with an indication of bit encodings, is given in Table 14.9.

Table 14.9

Initialisation – VST frame contents example

Octet #	Attribute/Field	Bits in octet	Description
1	FLAG	0111 1110	Start flag
2	Private LID	xxxx xxxx	Link address of the specific DSRC-VU
3		xxxx xxxx	Link address of the specific DSRC-VU
4		xxxx xxxx	Link address of the specific DSRC-VU
5		xxxx xxxx	Link address of the specific DSRC-VU
6	MAC Control field	1100 0000	Command PDU
7	LLC Control field	0000 0011	UI command
8	Fragmentation header	1xxx x001	No fragmentation
9	VST SEQUENCE { Fill BIT STRING (SIZE(4))	1001	Initialisation response
9	VST SEQUENCE { Fill BIT STRING (SIZE(4))	0000	Unused and set to 0
10	Profile INTEGER (0..127,...) Applications SEQUENCE OF {	0000 0000	No extension. Example profile 0 No extension, 1 application
11		0000 0001	No extension. Example profile 0 No extension, 1 application
12	SEQUENCE { OPTION indicator OPTION indicator AID DSRCApplicationEntityID	1	EID present
12	SEQUENCE { OPTION indicator OPTION indicator AID DSRCApplicationEntityID	1	Parameter present
12	SEQUENCE { OPTION indicator OPTION indicator AID DSRCApplicationEntityID	00 0010	No extension. AID= 2 Freight&Fleet
13	EID Dsrc-EID	xxxx xxxx	Defined within the OBU and identifying the application instance.
14	Parameter Container {	0000 0010	No extension, Container Choice = 02, Octet string
15		0000 0110	No extension, Rtm Context Mark length = 6
16	Rtm-ContextMark ::= SEQUENCE { StandardIdentifier	0000 0101	First octet is 05H, which is its length. Subsequent 5 octets encode the Object Identifier of the supported standard, part and version. {ISO (1) Standard (0) TARV (15638) part9(9) Version2 (2)}
17	standardIdentifier	0010 1000	First octet is 05H, which is its length. Subsequent 5 octets encode the Object Identifier of the supported standard, part and version. {ISO (1) Standard (0) TARV (15638) part9(9) Version2 (2)}
18		1111 1010	First octet is 05H, which is its length. Subsequent 5 octets encode the Object Identifier of the supported standard, part and version. {ISO (1) Standard (0) TARV (15638) part9(9) Version2 (2)}
19		0001 0110	First octet is 05H, which is its length. Subsequent 5 octets encode the Object Identifier of the supported standard, part and version. {ISO (1) Standard (0) TARV (15638) part9(9) Version2 (2)}
20		0000 1001	First octet is 05H, which is its length. Subsequent 5 octets encode the Object Identifier of the supported standard, part and version. {ISO (1) Standard (0) TARV (15638) part9(9) Version2 (2)}
21		0000 0010	First octet is 05H, which is its length. Subsequent 5 octets encode the Object Identifier of the supported standard, part and version. {ISO (1) Standard (0) TARV (15638) part9(9) Version2 (2)}
22	ObeConfiguration Sequence { OPTION indicator	0	ObeStatus not present
22	EquipmentClass INTEGER (0..32767)	xxx xxxx	This field shall be used to carry
23	EquipmentClass INTEGER (0..32767)	xxxx xxxx	manufacturer’s indications about the software/hardware version of the DSRC interface
24	ManufacturerId INTEGER (0..65535)	xxxx xxxx	Manufacturer identifier for the DSRC-VU as described in ISO 14816 Register
25	ManufacturerId INTEGER (0..65535)	xxxx xxxx	Manufacturer identifier for the DSRC-VU as described in ISO 14816 Register
26	FCS	xxxx xxxx	Frame check sequence
27	FCS	xxxx xxxx	Frame check sequence
28	Flag	0111 1110	End Flag

• DCS_49The REDCR then reads the data by issuing a GET command, conforming to the GET command defined in EN 13372, 6.2, 6.3, 6.4 and EN 12834, with settings as specified in Table 14.10.

Table 14.10

Presentation — GET request frame settings

Field	Settings
Invoker Identifier (IID)	Not present
Link Identifier (LID)	Link address of the specific DSRC-VU
Chaining	No
Element Identifier (EID)	As specified in the VST. No extension
Access Credentials	No
AttributeIdList	No extension, 1 attribute, AttributeID = 1 (RtmData)
Fragmentation	No
Layer2 settings	Command PDU, Polled ACn command

• Table 14.11 shows an example of reading the RTM data.

Table 14.11

Presentation — Get Request frame example

Octet #	Attribute/Field	Bits in octet	Description
1	FLAG	Image omitted; see official source	Start flag
2	Private LID	Image omitted; see official source	Link address of the specific DSRC-VU
3	Private LID	Image omitted; see official source	Link address of the specific DSRC-VU
4	Private LID	Image omitted; see official source	Link address of the specific DSRC-VU
5	Private LID	Image omitted; see official source	Link address of the specific DSRC-VU
6	MAC Control field	Image omitted; see official source	Command PDU
7	LLC Control field	Image omitted; see official source	Polled ACn command, n bit
8	Fragmentation header	Image omitted; see official source	No fragmentation
9	Get.request SEQUENCE {	Image omitted; see official source	Get request
9	OPTION indicator	Image omitted; see official source	Access Credentials not present
9	OPTION indicator	Image omitted; see official source	IID not present
9	OPTION indicator	Image omitted; see official source	AttributeIdList present
9	Fill BIT STRING(SIZE(1))	Image omitted; see official source	Set to 0.
10	EID INTEGER(0..127,…)	Image omitted; see official source	The EID of the RTM application instance, as specified in the VST. No extension
11	AttributeIdList SEQUENCE OF { AttributeId }}	Image omitted; see official source	No extension, number of attributes = 1
12	AttributeIdList SEQUENCE OF { AttributeId }}	Image omitted; see official source	AttributeId=1, RtmData. No extension
13	FCS	Image omitted; see official source	Frame check sequence
14	FCS	Image omitted; see official source	Frame check sequence
15	Flag	Image omitted; see official source	End Flag

• DSC_50The DSRC-VU, when receiving the GET request, sends a GET response with the requested data conforming to the GET response defined in EN 13372, 6.2, 6.3, 6.4 and EN 12834, with settings as specified in Table 14.12.

Table 14.12

Presentation — GET response frame settings

Field	Settings
Invoker Identifier (IID)	Not present
Link Identifier (LID)	As per EN 12834
Chaining	No
Element Identifier (EID)	As specified in the VST.
Access Credentials	No
Fragmentation	No
Layer2 settings	Response PDU, Response available and command accepted, ACn command

- Table 14.13 shows an example of reading the RTM data.

Table 14.13

Presentation — Response frame contents example

Octet #	Attribute/Field	Bits in octet	Description
1	FLAG	Image omitted; see official source	Start flag
2	Private LID	Image omitted; see official source	Link address of the specific DSRC-VU
3	Private LID	Image omitted; see official source	Link address of the specific DSRC-VU
4	Private LID	Image omitted; see official source	Link address of the specific DSRC-VU
5	Private LID	Image omitted; see official source	Link address of the specific DSRC-VU
6	MAC Control field	Image omitted; see official source	Response PDU
7	LLC Control field	Image omitted; see official source	Response available, ACn command n bit
8	LLC Status field	Image omitted; see official source	Response available and command accepted
9	Fragmentation header	Image omitted; see official source	No fragmentation
10	Get.response SEQUENCE {	Image omitted; see official source	Get response
10	OPTION indicator	Image omitted; see official source	IID not present
10	OPTION indicator	Image omitted; see official source	Attribute List present
10	OPTION indicator	Image omitted; see official source	Return status not present
10	Fill BIT STRING(SIZE(1))	Image omitted; see official source	Not used
11	EID INTEGER(0..127,…)	Image omitted; see official source	Responding from the RTM application Instance. No extension,
12	AttributeList SEQUENCE OF {	Image omitted; see official source	No extension, number of attributes = 1
13	Attributes SEQUENCE { AttributeId	Image omitted; see official source	No extension, AttributeId=1 (RtmData)
14	AttributeValue CONTAINER {	Image omitted; see official source	No extension, Container Choice = 1010.
15	AttributeValue CONTAINER {	Image omitted; see official source	RtmData
16	AttributeValue CONTAINER {	Image omitted; see official source	RtmData
17	AttributeValue CONTAINER {	Image omitted; see official source	RtmData
…	AttributeValue CONTAINER {	…	RtmData
n	}}}}	Image omitted; see official source	RtmData
n+1	FCS	Image omitted; see official source	Frame check sequence
n+2	FCS	Image omitted; see official source	Frame check sequence
n+3	Flag	Image omitted; see official source	End Flag

• DSC_51The REDCR then closes the connection by issuing a EVENT_REPORT, RELEASE command conforming to EN 13372, 6.2, 6.3, 6.4 and EN 12834,7.3.8, with no specific RTM settings. Table 14.14 shows a bit encoding example of the RELEASE command.

Table 14.14

Termination. EVENT_REPORT Release frame contents

Octet #	Attribute/Field	Bits in octet	Description
1	FLAG	Image omitted; see official source	Start flag
2	Private LID	Image omitted; see official source	Link address of the specific DSRC-VU
3	Private LID	Image omitted; see official source	Link address of the specific DSRC-VU
4	Private LID	Image omitted; see official source	Link address of the specific DSRC-VU
5	Private LID	Image omitted; see official source	Link address of the specific DSRC-VU
6	MAC Control field	Image omitted; see official source	The frame contains a command LPDU
7	LLC Control field	Image omitted; see official source	UI command
8	Fragmentation header	Image omitted; see official source	No fragmentation
9	EVENT_REPORT.request SEQUENCE {	Image omitted; see official source	EVENT_REPORT (Release)
9	OPTION indicator	Image omitted; see official source	Access Credentials not present
9	OPTION indicator	Image omitted; see official source	Event parameter not present
9	OPTION indicator	Image omitted; see official source	IID not present
9	Mode BOOLEAN	Image omitted; see official source	No response expected
10	EID INTEGER (0..127,…)	Image omitted; see official source	No extension, EID = 0 (System)
11	EventType INTEGER (0..127,…) }	Image omitted; see official source	Event type 0 = Release
12	FCS	Image omitted; see official source	Frame check sequence
13	FCS	Image omitted; see official source	Frame check sequence
14	Flag	Image omitted; see official source	End Flag

- DSC_52The DSRC-VU is not expected to answer to the Release command. The communication is then closed.

5.4.8   DSRC Test transaction description

• DSC_53Full tests that include securing the data, need to be carried out as defined in Appendix 11 Common Security Mechanisms, by authorised persons with access to security procedures, using the normal GET command as defined above.

• DSC_54Commissioning and periodic inspection tests that require decrypting and comprehension of the decrypted data content shall be undertaken as specified in Appendix 11 Common Security Mechanisms and Appendix 9, Type Approval List of Minimum required tests.

• However, the basic DSRC communication can be tested by the command ECHO. Such tests may be required on commissioning, at periodic inspection, or otherwise to the requirement of the competent control authority or Regulation (EU) No 165/2014 (See 6 below)

• DSC_55In order to effect this basic communication test, the ECHO command is issued by the REDCR during a session, i.e., after an initialisation phase has been completed successfully. The sequence of interactions is thus similar to that of an interrogation:

• — Step 1

The REDCR sends a ‘beacon service table’ (BST) that includes the application identifiers (AIDs) in the service list that it supports. In the RTM applications this will simply be the service with the AID value = 2.

The DSRC-VU evaluates the received BST, and where it identifies that the BST is requesting Freight&Fleet (AID = 2), the DSRC-VU shall respond. If the REDCR does not offer AID=2, the DSRC-VU shall shut down its transaction with the REDCR.

• — Step 2The DSRC-VU sends a request for a private window allocation.

• — Step 3The REDCR sends a private window allocation.

• — Step 4The DSRC-VU uses the allocated private window to send its vehicle service table (VST). This VST includes a list of all the different application instantiations that this DSRC-VU supports in the framework of AID=2. The different instantiations shall be identified by means of uniquely EIDs, each associated with a parameter value indicating the instance of the application that is supported.

• — Step 5Next the REDCR analyses the offered VST, and either terminates the connection (RELEASE) since it is not interested in anything the VST has to offer (i.e., it is receiving a VST from a DSRC-VU that is not an RTM VU, or, if it receives an appropriate VST it starts an app instantiation.

• — Step 6The REDCR shall issue a command (ECHO) to the specific DSRC-VU, and allocates a private window.

• — Step 7The DSRC-VU uses the newly allocated private window to send an ECHO response frame.

The following tables give a practical example of an ECHO exchange session.

• DSC_56Initialisation is performed according to 5.4.7 (DSC_44 — DSC_48) and Tables 14.4 — 14.9

• DSC_57The REDCR then issues an ACTION, ECHO command conforming to ISO 14906, containing 100 octets of data and with no specific settings for RTM. Table 14.15 shows the contents of the frame sent by the REDCR.

Table 14.15

ACTION, ECHO request frame example

| Octet # | Attribute/Field | Bits in octet | Description |

| --- | --- | --- | --- | | 1 | FLAG | Image omitted; see official source | Start flag | | 2 | Private LID | Image omitted; see official source | Link address of the specific DSRC-VU | | 3 | Private LID | Image omitted; see official source | Link address of the specific DSRC-VU | | 4 | Private LID | Image omitted; see official source | Link address of the specific DSRC-VU | | 5 | Private LID | Image omitted; see official source | Link address of the specific DSRC-VU | | 6 | MAC Control field | Image omitted; see official source | Command PDU | | 7 | LLC Control field | Image omitted; see official source | Polled ACn command, n bit | | 8 | Fragmentation header | Image omitted; see official source | No fragmentation | | 9 | ACTION.request SEQUENCE { | Image omitted; see official source | Action request (ECHO) | | 9 | OPTION indicator | Image omitted; see official source | Access Credentials not present | | 9 | OPTION indicator | Image omitted; see official source | Action parameter present | | 9 | OPTION indicator | Image omitted; see official source | IID not present | | 9 | Mode BOOLEAN | Image omitted; see official source | Response expected | | 10 | EID INTEGER (0..127,…) | Image omitted; see official source | No extension, EID = 0 (System) | | 11 | ActionType INTEGER (0..127,…) | Image omitted; see official source | No extension, Action type ECHO request | | 12 | ActionParameter CONTAINER { | Image omitted; see official source | No extension, Container Choice = 2 | | 13 | ActionParameter CONTAINER { | Image omitted; see official source | No extension. String length = 100 octets | | 14 | | Image omitted; see official source | Data to be echoed | | … | | … | Data to be echoed | | 113 | }} | Image omitted; see official source | Data to be echoed | | 114 | FCS | Image omitted; see official source | Frame check sequence | | 115 | FCS | Image omitted; see official source | Frame check sequence | | 116 | Flag | Image omitted; see official source | End Flag |

- DSC_58The DSRC-VU, when receiving the ECHO request, sends an ECHO response of 100 octets of data by reflecting the received command, according to ISO 14906, with no specific settings for RTM. Table 14.16 shows a bit level encoding example.

Table 14.16

ACTION, ECHO response frame example

Octet #	Attribute/Field	Bits in octet	Description
1	FLAG	Image omitted; see official source	Start flag
2	Private LID	Image omitted; see official source	Link address of the specific VU
3	Private LID	Image omitted; see official source	Link address of the specific VU
4	Private LID	Image omitted; see official source	Link address of the specific VU
5	Private LID	Image omitted; see official source	Link address of the specific VU
6	MAC Control field	Image omitted; see official source	Response PDU
7	LLC Control field	Image omitted; see official source	ACn command n bit
8	LLC status field	Image omitted; see official source	Response available
9	Fragmentation header	Image omitted; see official source	No fragmentation
10	ACTION.response SEQUENCE {	Image omitted; see official source	ACTION response (ECHO)
10	OPTION indicator	Image omitted; see official source	IID not present
10	OPTION indicator	Image omitted; see official source	Response parameter present
10	OPTION indicator	Image omitted; see official source	Return status not present
10	Fill BIT STRING (SIZE (1))	Image omitted; see official source	Not used
11	EID INTEGER (0..127,…)	Image omitted; see official source	No extension, EID = 0 (System)
12	ResponseParameter CONTAINER {	Image omitted; see official source	No extension, Container Choice = 2
13	ResponseParameter CONTAINER {	Image omitted; see official source	No extension. String length = 100 octets
14		Image omitted; see official source	Echoed data
…		…	Echoed data
113	}}	Image omitted; see official source	Echoed data
114	FCS	Image omitted; see official source	Frame check sequence
115	FCS	Image omitted; see official source	Frame check sequence
116	Flag	Image omitted; see official source	End Flag

5.5   Reserved for future use

5.6   Data transfer between the DSRC-VU and VU

5.6.1   Physical Connection and interfaces

• DSC_66The connection between the VU and the DSRC-VU can be either by physical cable or short range wireless communication based on Bluetooth v4.0 BLE.

• DSC_67Regardless of the choice of the physical connection and interface, the following requirements shall be satisfied:

• DSC_68

a)In order that different suppliers may be contracted to supply the VU and the DSRC-VU, and indeed different batches of DSRC-VU, the connection between the VU and the DSRC-VU not internal to the VU shall be an open standard connection. The VU shall connect with the DSRC-VU either

ii) using Bluetooth Low Energy (BLE) iii) using a standard ISO 11898 or SAE J1939 connection

• DSC_69

b)the definition of the interfaces and connection between the VU and DSRC-VU must support the application protocol commands defined in 5.6.2. and

• DSC_70

c)the VU and DSRC-VU must support the operation of the data transfer via the connection in regard to performance and power supply.

5.6.2   Application Protocol

• DSC_71The application protocol between the VU Remote Communication facility and DSRC-VU is responsible for periodically transferring the remote communication data from the VU to the DSRC.

• DSC_72The following main commands are identified:

• 1. Initialisation of the communication link — Request

• 1. Initialisation of the communication link — Response

• 1. Send Data with Identifier of the RTM application and Payload defined by RTM Data

• 1. Acknowledgment of the data

• 1. Termination of the communication link — Request

- 6. Termination of the communication link — Response

- DSC_73In ASN1.0, the previous commands may be defined as:

• Image omitted; see official source

• DSC_74The description of the commands and parameters is following:

• — Image omitted; see official sourceis used to initialize the communication link. The command is sent by the VU to the DSRC-VU. The LinkIdentifier is set by the VU and communicated to the DSRC-VU to track a specific communication link. (Note: this is to support future links and other application/modules like Weighing on board).

- — Image omitted; see official sourceis used by the DSRC-VU to provide the response of the request to initialize the communication link. The command is sent by the DSRC-VU to the VU. The command provides the result of the initialisation as answer = 1 (Success) or =0 (Failure).

• DSC_75The initialization of the communication link shall be done only after installation, calibration, and start of the engine/VU is switched on.

• — Image omitted; see official sourceis used to by the VU to send the signed RCDTData (i.e., the remote communication Data) to the DSRC-VU. The data will be sent every 60 seconds. The DataTransactionId parameter identifies the specific transmission of data. The LinkIdentifier is also used to ensure that the appropriate link is correct.

- — Image omitted; see official sourceis sent by the DSRC-VU to provide the feedback to the VU on the reception of the data from a Image omitted; see official source command identified by the DataTransactionId parameter. The Answer parameter is 1 (Success) or =0 (Failure). If a VU receives more than three answers equal to 0 or if the VU does not receive a RCDT Data Acknowledgment for a specific previously sent RCDT- Send Data with a specific DataTransactionId, the VU will generate and record an event.

• — Image omitted; see official sourceis sent by the VU to DSRC-VU to terminate a link for a specific LinkIdentifier.

• DSC_76At the restart of the DSRC-VU or a VU, all the existing Communication Links should be removed as there could be ‘dangling’ Links due to the sudden shutdown of a VU.

• — Image omitted; see official sourceis sent by the DSRC-VU to the VU to confirm the request of termination of the link by the VU for the specific LinkIdentifier.

5.7   Error handling

5.7.1   Recording and communication of the Data in the DSRC-VU

• DSC_77 The Data shall be provided, already secured, by the VUSM function to the DSRC-VU. The VUSM shall verify that data recorded in the DSRC-VU has been transmitted successfully to the DSRC-VU. The recording and reporting of any errors in the transfer of data from the VU to the memory of the DSRC-VU shall be recorded with type EventFaultType and enum value set to ‘0C’H Communication error with the remote communication facility event together with the timestamp. The VUSM shall verify that the data has been transmitted successfully to the DSRC-VU.

• DSC_78Reserved for future use.

• DSC_79If the VUPM attempts to obtain VU data from the security module (to pass to the VU-DSRC), but fails to do so, it shall record that failure with type EventFaultType and enum value set to ‘62’H Remote Communication Facility' communication fault together with the timestamp. The failure of the communication is detected when a Image omitted; see official source message is not received for the related (i.e., with the same DataTransactionId Image omitted; see official source messages) Image omitted; see official source for more than three consecutive times.

5.7.2   Wireless Communication errors

• DSC_80Communication error handling shall be consistent with the related DSRC standards, namely EN 300 674-1, EN 12253, EN 12795, EN 12834 and the appropriate parameters of EN 13372.

5.7.2.1   Encryption and signature errors

• DSC_81Encryption and signature errors shall be handled as defined in Appendix 11 Common Security Mechanisms and are not present in any error messages associated with the DSRC transfer of data.

5.7.2.2   Recording of errors

The DSRC medium is a dynamic wireless communication in an environment of uncertain atmospheric and interference conditions, particularly in the ‘portable REDCR’ and ‘moving vehicle’ combinations involved in this application. It is therefore necessary to ascertain the difference between a ‘read failure’ and an ‘error’ condition. In a transaction across a wireless interface, read failure is common and the consequence is usually to retry, i.e. rebroadcast the BST and reattempt the sequence, which will in most circumstances lead to a successful communication connection and transfer of data, unless the target vehicle moves out of range during the time required to retransmit. (A ‘successful’ instance of a ‘read’ may have involved several attempts and retries).