data

Building Test Data Files

• You can construct test data files by working with the BSM MessageFrame and working up.

j2735.MessageFrame.Bsm.xml : apply converter-example -ixer -oper -p MessageFrame j2735.MessageFrame.Bsm.per : apply xxd -p j2735.MessageFrame.Bsm.hex : cut and paste into Ieee1609Dot2Data xml structure.

Ieee1609Dot2Data.unsecuredData.xml : apply converter-example -ixer -oper -p Ieee1609Dot2Data Ieee1609Dot2Data.unsecuredData.per : apply xxd -p Ieee1609Dot2Data.unsecuredData.hex : cut and paste into the BAH packet that goes into the input Kafka stream.

BAH.Input.xml : the data that is received on the Kafka input stream.

Notes on using "xxd" for conversion from bytes to hex strings and hex strings to bytes.

• Be careful to follow these directions or you will produce errors. The hex dump is normally annotated and that is not needed in the hex strings input into the payload sections of these XML files.

• xxd -p .bin > .hex // converts a binary file into a straight hex string.

• xxd -r -p .hex > .bin // converts the binary string above into a binary file.

Schemas and searching for payload data

• For both unsigned (unsecuredData) and signed data (signedData -> tbsData -> payload -> data -> unsecuredData) we can just search for the unsecuredData tag; that contains the bytes.

• Encrypted data is different. (encryptedData -> ciphertext -> aes128ccm -> ccmCiphertext) but this data must be processed by a decryption algorithm and a key -- not a current concern.

• signedCertificateRequest. This is the data directly (similar to unsecuredData) but it is for a different purpose.

  unsecuredData Opaque, signedData SignedData, encryptedData EncryptedData, signedCertificateRequest Opaque,