Receive VSD via UDP and deposit to SDC

Goal

This tests the full end-to-end functionality of the VSD SDC depositor feature. An UPER encoded VSD message will be sent over UDP from a test instance (emulating an OBE or RSE) to an instance running the ODE over IPv6. The ODE will then automatically forward and deposit this message to the SDC.

This expands on the functionality in .

VSD Dialog

1. RSE -----ServiceRequest-----> ODE -----ServiceRequest----> SDC

2. RSE <----ServiceResponse----- ODE <----ServiceResponse---- SDC

3. RSE --------VsdMessage------> ODE --------VsdMessage-----> SDC

4. RSE sends ServiceRequest to ODE, which forwards it to the SDC.

5. ODE receives ServiceResponse from SDC, and forwards it back to the RSE.

6. RSE sends VSD to ODE, which forwards it to the SDC.

Procedure

This test deposits VSD from ODE to SDC by following the VSD Dialog. In order to demonstrate this functionality, the sample VSD message which originates in Wyoming is sent as a unit test. Once ODE-308 is complete, this process will be automated as a service.

1. Deploy ODE in an IPv6 environment and create a separate IPv6 test instance to emulate an RSE/OBE.
2. On the RSE emulator instance, obtain a VSDM uper file. curl https://raw.githubusercontent.com/usdot-jpo-ode/jpo-ode/ode-308/data/vsdm.uper > vsdm.uper
3. Send the VSDM UPER file to the ODE over IPv6. cat vsdm.uper | nc -6u <ode_ip> 46753
4. Verify the ODE received the message by checking ode.log. In the log there should be confirmation of UDP reception as well as a list of JSON BSMs extracted/converted from the VSDM: (Screenshot)[screenshot.jpg]
5. Verify the ODE attempted to send the VSD message to the SDC by checking the logs.
6. Open up the SDC interface and verify the message was deposited. (Instructions)[link.html]