View Categories

V2X – Backward Compatibility in V2X System Evolution

As introduced by relevant V2X industrial definitions (C2C-CC, 2017), C-ITS systems will be deployed in different phases with the aim of providing increased support for new applications, especially in the field of AD. As it cannot be always ensured that older C-ITS systems in the field can be upgraded with new communication capabilities, it is essential that improved C-ITS systems deployed at later stages are still capable to communicate with and hence support older systems. As an example, if a new C-ITS system is deployed with the capability of transmitting new V2X messages with a new communication technology, these improvements shall not prevent the capability of older C-ITS systems to receive the older messages with the older supported communication technologies . At the same time, this shall not prevent the new C-ITS system to receive and use older messages from older C-ITS stations.

For this reason, it is very important for developers to consider backwards compatibility when integrating V2X solutions in their ADF implementations: in the design phase, V2X solutions shall be selected based on their capability to be extended at newer generations without compromising interoperability with older generations. Not following this principle can compromize the continuity in the functionality of ADFs implementations based on older V2X solutions. For the same reason is also advisable to introduce backwards compatibility requirements and their assessment via suitable testing procedures. Lastly, as V2X gets more relevance for ADF support, ADF developers are invited to get involved in standardization activities and industry alliances composed by all relevant C-ITS stakeholders to collaboratively specify evolutions of V2X solutions ensuring backwards compatibility

Main Question

Is backward compatibility maintained across different generations of V2X systems when implementing new features or upgrading own existing ADF functionalities?

Sub-Questions

  1. Are newer versions of radio access technologies and communication protocols used by V2X applications able to communicate with implementation of older versions without disruption? 
  2. When updates or changes are introduced, is backward compatibility maintained, ensuring that older data formats, encoding schemes, message exchange, data interpretation, and feature compatibility continue to function as expected?
  3. Are there comprehensive transition strategies such as phased adoption, gradual migration from older systems to newer ones while maintaining compatibility to minimize disruption? 
  4. Are clear documentation and support resources, such as guidance on migration steps, necessary configuration changes, provided to assist users in transitioning to newer versions of V2X applications? Are user support channels available to address queries and issues related to backward compatibility? 
  5. Is there active participation in standardization efforts and industry alliances that allows for alignment and coordination in maintaining compatibility as the V2X ecosystem evolves?

References