Division 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:

1. 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.

2. 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:

   1. a))

      The type HashAlgorithm shall be set at sha256.

   2. b))

      The type SignerIdentifier shall be set at ‘digest’.

   3. c))

      The type SignedDataPayload shall be the OWS data as laid down in point 7.

   4. d))

      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.

3. 8.2.3.

   The ASN.1 module definition for the type Signature shall be as follows:

   

4. 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.

5. 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.