Differentiate Infrastructure Communication from Vehicle Communication (Port Drayage)

[paulbourelly999]

Types of Issue

• [ x ] Anomaly report (something appears to not work correctly)
• Enhancement request (describe the enhancement being requested)
• Other (please ensure the description clarifies why the issue doesn’t fall into either of the above categories)

Descriptive summary

The mobility operation messages we currently use for Vehicle and Infrastructure communication does not indicate the origin of the message so if there is overlapping communication between multiple infrastructure elements or potentially for vehicles there is a possibility for unintended behavior. If we add indication of the origin or target in the mobility operation header or message payload we can filter out unnecessary messages.

V2XHUB version where this issue was discovered

6.2

Expected behavior

Infrastructure ignore other infrastructure communication

Actual behavior

Infrastructure may attempt to respond to other infrastructure communication

Steps to reproduce the actual behavior

1. Overlapping RSU communication with two V2X-Hubs and Port Drayage Web Services will cause one V2X-Hub to receive communication from the other V2X-Hub and attempt to respond to it as if it were vehicle communication

Related work