1.
This Annex, complementary to Appendix 14 to Annex IC to Regulation (EU) 2016/799 (henceforth Appendix 14), specifies the requirements for the preparation and transfer of OWS data from the motor vehicle to the Remote Early Detection Communication Reader (‘REDCR’).
2.1.
OWS data shall be provided to the dedicated short range communication vehicle unit (‘DSRC-VU’) by the motor vehicle unit (‘MVU’).
2.2.
The MVU shall:
2.2.1. Build up the OWS data with the information received from the MVU and the trailer unit (‘TU’), according to the structure set out in point 6;
2.2.2. forward the OWS data to the DSRC-VU for further transmission to the REDCR.
3.1.
OWS data shall be provided to the DSRC-VU by the C-ITS station in the motor vehicle.
3.2.
The C-ITS station in the motor vehicle shall:
3.2.1. Build up the OWS data with the information received from the MVU and the C-ITS stations of the trailers or semi-trailers being towed, according to the structure set out in point 6;
3.2.2. secure the OWS data as laid down in point 8, and
3.2.3. forward the OWS data to the DSRC-VU for further transmission to the REDCR.
4.
Data transfer between the DSRC-VU and either the MVU (stage 1) or the C-ITS station in the motor vehicle (stage 2) shall be implemented as set out in point 5.6 of Appendix 14, where VU shall be understood as being either the MVU or the C-ITS station, depending on the stage.
5.1.
The communication between the DSRC-VU and the REDCR shall be carried out through the interface defined by the CEN DSRC standards EN 12253, EN 12795, EN 12834, EN 13372 and ISO 14906, as referred to in Council Directive 96/53/EC.
5.2.
The transaction protocol to download OWS data across the 5.8 GHz DSRC interface link shall be the same as the one used for the RTM data in point 5.4.1 of Appendix 14, the only difference being that the Object Identifier that relates to the TARV standard shall be addressing the ISO 15638 standard (TARV) Part 20 related to WOB/OWS.
5.3.
The commands used for an OWS transaction shall be the same as those set out in point 5.4.2 of Appendix 14 for a RTM transaction.
5.4.
The interrogation command sequence for OWS data shall be the same as the one set out in point 5.4.3 of Appendix 14 for RTM data.
5.5.
Data transfer mechanism and DSRC transaction description shall be the same as set out in points 5.4.6 and 5.4.7 of Appendix 14. The Vehicle Service Table shall be however adapted for the transmission of OWS data. Consequently, the Rtm-ContextMark shall be replaced by an Ows-ContextMark, which object identifier shall refer to the ISO 15638 standard (TARV) Part 20 related to WOB/OWS.
5.6.
The DSRC physical interface parameters shall be the same as those set out in point 5.3 of Appendix 14.
The ASN.1 module definition for the DSRC data within the OWS application is defined as follows:
7.
Elements of OWS data, actions performed and definitions:
The OWS data shall be calculated by either the MVU (stage 1) or the C-ITS station in the motor vehicle (stage 2) according to table 1
OWSData element | Action performed by the C-ITS station in the motor vehicle | Comment | ASN.1 definition of data
OWS1
Total weight
An integer value shall be generated. | Last measured total weight |
recordedWeight
INTEGER (0..65535),
OWS2
technically permissible maximum laden mass
An integer value shall be generated | Technically permissible maximum laden mass declared by the manufacturer |
maximumTechnicalWeight
INTEGER (0..65535)
OWS3
Axles configuration of the vehicle
An octet string size 4 shall be generated. | Axles configuration |
axlesConfiguration
OCTET STRING SIZE (4),
OWS4
Axle weight
An octet string size 26 shall be generated. | Weight per axle |
axlesRecordedWeight
OCTET STRING SIZE (26),
OWS5
Time recorded total weight
An integer value shall be generated.
The value for OWS2 shall be set to the time of the current record of total weight.
Timestamp of the current recorded weight |
tp15638Timestamp
INTEGER (0..4294967295),
OWS6
DSRC Communication error
A Boolean value shall be generated.
A TRUE value to the tp15638DSRCcommunicationError variable shall be assigned if the OBW has encountered at least one event of type Communication Error with the DSRC-VU in the last 30 days.
ELSE if there are no events in the last 30 days, a FALSE value shall be assigned.
1 (TRUE), indicates communication error between the OBW and the DSRC-VU in the last 30 days |
tp15638DSRCcommunicationError,
BOOLEAN,
OWS7
OBW Communication error
A Boolean value shall be generated.
A TRUE value to the tp15638CommunicationError variable shall be assigned if the OBW has encountered at least one OBW communication error event inside the OBW in the last 30 days.
ELSE if there are no events in the last 30 days, a FALSE value shall be assigned.
1 (TRUE), indicates communication error in the OBW in the last 30 days |
tp15638OBWCommunicationError,
BOOLEAN,
OWS8
Security Breach Attempt
A Boolean value shall be generated.
A TRUE value to the tp15638SecurityBreachAttempt variable shall be assigned if the OBW has in the last 2 years recorded at least one event of type security breach attempt.
ELSE if there have not been security breach attempt events in the last 2 years, a FALSE value shall be assigned.
1 (TRUE), indicates a security breach attempt to the OBW within last 2 years |
tp15638SecurityBreachAttempt
BOOLEAN,
where
recordedWeight represents the total measured weight of the vehicle or vehicle combination with a resolution of 10 kg as defined in EN ISO 14906. For example, a value of 2500 represents a weight of 25 ton.
axlesConfiguration represents the configuration of the vehicle or vehicle combination as number of axles.
The configuration is defined with the bit mask of 20 bits (extended from EN ISO 14906).
A bit mask of 2 bits represents the configuration of an axle with the following format:
Value 00B means that value is ‘non available’ because the vehicle does not have equipment to collect the weight on the axle.
Value 01B means that the axle is not present.
Value 10B means that the axle is present and the weight has been calculated and collected and it is provided in the axlesRecordedWeight field.
Value 11B is reserved for future uses.
The last 6 bits are reserved for future uses.
Number of Axles |
Number of axles on tractor unit | Number of axles on trailer
00/01/10/11 | 00/01/10/11 | 00/01/10/11 | 00/01/10/11 | 00/01/10/11 | 00/01/10/11 | 00/01/10/11 | 00/01/10/11 | 00/01/10/11 | 00/01/10/11 | 00/01/10/11 | 00/01/10/11 | 00/01/10/11 |
RFU
(6 bits)
axlesRecordedWeight represent the specific weight recorded for each axle with a resolution of 10 Kg. Two octets are used for each axle. For example, a value of 150, represent a weight of 1500 Kgs.
maximumTechnicalWeight represent the technically permissible maximum laden mass of the vehicle or vehicle combination as declared by the manufacturer. This value shall only be provided for stage 2. For stage 1, a 0 value shall be assigned.
8.1.
For stage 1, the OWS data shall not be signed; the plaintext of the OWS data shall be transferred from the MVU to the DSRC-VU.
8.2.
For stage 2, the OWS data shall be signed in the C-ITS station of the motor vehicle and transferred from the latter to the DSRC-VU, in accordance with the following provisions:
8.2.1. The secured data structure shall be constructed as set out in points 5.1 and 5.2 of ETSI TS 103 097-V1.3.1.
8.2.2. The type SignedData referred to in point 5.2 of ETSI TS 103 097-V1.3.1 shall have the following constraints:
The type HashAlgorithm shall be set at sha256.
The type SignerIdentifier shall be set at ‘digest’.
The type SignedDataPayload shall be the OWS data as laid down in point 7.
The type HeaderInfo shall be constrained to have the following security headers:
The component psid shall be set equal to 0.
The component generationTime as defined in IEEE Std 1609.2.
The component expiryTime shall be absent.
The component generationLocation shall be absent.
The component p2pcdLearningRequest shall be absent.
The component missingCrlIdentifier shall be absent.
The component encryptionKey shall be absent.
The component inlineP2pcdRequest shall be absent.
The component requestedCertificate shall be absent.
8.2.3. The ASN.1 module definition for the type Signature shall be as follows:
8.2.4. The signing certificate shall be the certificate in the authorisation ticket that the C-ITS station is using for the transaction between the C-ITS station and the REDCR, in accordance with point 6 of ETSI TS 103 097-V1.3.1.
8.2.5. When receiving the message, the REDCR shall verify the certificate and shall use the public key included in that certificate to read the OWS data signature.
9.
The application protocol and error handling for OWS data shall be the same as set out in points 5.6.2 and 5.7 of Appendix 14.
10.
For stage 2, OWS data may also be served directly to the REDCR of the enforcer via the C-ITS station in the motor vehicle instead of via the DSRC-VU. In that case, the REDCR will also be a C-ITS station.