This application provides validation for SEMI and SAE DSRC J2735 3/2016 messages encoded as ASN.1 Unaligned PER (UPER) bytes. It supports one or more versions of the CVCS SEMI messages as specified in the SEMI ASN.1 Specification Version list.

A message for validation can be provided as a binary file via file browse or file drag and drop, or by pasting the message bytes encoded as HEX or Base64 string.

Please note that decoding UPER encoded messages per specification requires the decoder to know the ASN.1 definition of the message. Since messages that arrive at the SDC/SDW warehouses do not explicitly provide that information, the warehouses attempt to derive the information from a message itself. If a message is formatted correctly, this results in proper and unambiguous detection of the message type and the subsequent successful decoding of the message. However, for messages that contain errors, it’s impossible for the warehouses and this validator to produce an accurate error report. The recommended validation procedure below is designed to mitigate the problem.

Recommended message validation steps:

1. Select desired SEMI ASN.1 Specification Version.
2. Specify Data Encoding if message bytes are provided as an encoded string.
3. Make sure that Message Type is set to Auto-detect message type.
4. Provide the message by browsing for a file, file drag and drop, or encoded string paste.
5. Click Validate.
6. If the message is validated correctly (message type and validation results are green)
   1. Verify that the message type matches the intended type of the provided message. If those match, no other actions are necessary and the message is ready for deposit to the warehouses.
   2. If the message type does not match, please open a ticket at the CVCS management site https://cvcs.samanage.com/ providing the message file or string, expected message type, and detected message type from the validator. This message can’t be deposited until the problem is resolved.
7. If the message failed validation, specify intended message type in the Message Type combo-box. If desired type is not listed, the messages of that type can’t be validated with this application and can’t be deposited to the CVCS warehouses.
8. Click Validate. Now that the validator has a hint regarding the intended message type, it will be able to provide more accurate error reporting. Use the information provided to correct errors.
9. Continue correcting errors and re-validating the updated message with the intended type selected in the Message Type combo-box until the message validates and the message type reported matches the intended message type.
10. When the message correctly validates with the intended message type provided, it needs to be re-validated without the message type hint to make sure that the warehouses that will not have the hint will be able to correctly decode it as well. For this, perform the validation again starting with no. 3 above.

Please do not attempt depositing any messages that did not completely pass the validation without the message type hint to the warehouses as they are guarantee to be dropped.

The application is compatible with most modern browsers including Internet Explorer 11, Firefox, and Chrome. If you experience any problems using the application, please report those by opening a ticket at CVCS management site https://cvcs.samanage.com/.