A V2X enabler provides added values to the ADF it supports, only if it is able to correctly interoperate with corresponding V2X enablers deployed and made available in the field by other implementers. As a non restrictive example, an ADF based on reception of hazardous location notifications via V2X should be able to interoperate with corresponding notification dissemination services offered nowadays by road operators and made available via direct short range communication or cellular technologies.
As a consequence, the ADF developer should adopt compatible V2X radio access technologies and dedicated communication stack protocol standards, proprietary customized solutions would prevent interoperability with independent third parties. Particular attention has to be devoted to the data formats, encoding rules and profiling of the exchanged information. An unambiguous setting of transmitted V2X messages shall be preliminarily agreed between any interested communication party to restrict the countless setting possibilities to those really needed by the use cases implemented by the receiving party.
In this regard, it is very beneficial to follow and refer to the profiling activities of industrial organizations active in the field of Cooperative ITS development and deployment like C2C-CC (2017) and C-Roads (2019) as well as 5GAA (2020). The mentioned organizations provide also specifications on the currently available V2X services and the details on how to make use of them. Finally, it is essential that the ADF developer adopts assessment schemes to ensure compliance to the aforementioned standards and profiling specifications. A proof of successful assessment might be in the future a pre-requisite to be admitted in a trusted network of C-ITS systems (e.g.European C-ITS Credential Management System).
Main Question
Can V2X systems adopted by the developed ADF interoperate with V2X systems deployed by other implementers?
Sub-Questions
- Is the communication by V2X implemented based on standardized radio access protocols, e.g., IEEE 802.11p or Cellular Vehicle-to-Everything (C-V2X) protocols based on 3GPP specifications?
- Is compliance with all relevant definitions from standards organizations, e.g. 3GPP, the Institute of Electrical and Electronics Engineers (IEEE), the Society of Automotive Engineers (SAE), and the European Telecommunications Standards Institute (ETSI) taken in account as part of the system requirements for V2X?
- Do data formats and encoding schemes implemented comply with standard formats for V2X messages?
- Are the adopted V2X standards profiled following the definitions of industrial organizations dictating the rules for ensuring interoperability of deployed systems?
- Are standardized service discovery and advertisement protocols, or standardized addressing schemes used for V2X systems to identify and interact with compatible services in the environment?
References
- C-Roads (2019) C-Roads Platform. Available at: https://www.c-roads.eu/platform/documents.html (Accessed: 31 October 2023).
- C2C-CC (2017) Guidance for day 2 and beyond roadmap. Available at https://www.car-2-car.org/fileadmin/documents/General_Documents/C2CCC_WP_2072_RoadmapDay2AndBeyond_V1.2.pdf (Accessed: 31 October 2023).
- 5GAA (2020) C-ITS Communication System Profile. Available at: https://5gaa.org/5gaa-publishes-c-its-communication-system-profiles/ (Accessed: 31 October 2023).