Cooperative ITS Corridor and C-ITS Architecture Discussion

Delve into the Cooperative ITS Corridor initiative that began in 2013, focusing on enhancing road safety and traffic flow through cooperative communication technology. Explore the goals, challenges, data vs. protocol differences, and the intricate structure of interfaces in the C-ITS Corridor. Gain insights into connecting trailers, roadworks information centers, traffic control centers, and more, as discussed at the DATEX II User Forum in Dublin.

• Cooperative ITS Corridor
• C-ITS
• Road Safety
• Traffic Flow
• Communication Technology

jea_n Follow

Uploaded on Feb 28, 2025 | 0 Views

Download Presentation

Please find below an Image/Link to download the presentation.

The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.

You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.

The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.

Presentation Transcript

1. Datex II in the cooperative ITS Corridor DATEX II User Forum, Dublin, 14 September 2016 Dipl.-Math. Werner Scholtes Werner Scholtes IT-Beratung DATEX II User Forum Dublin 13&14 September 2016

2. DATEX II User Forum Dublin 13&14 September 2016

3. Cooperative ITS Corridor Started in 2013 Cooperation between Austria, Netherlands and Germany Improve road safety and traffic flow Enable roadworks safety trailers for cooperative communication Technology shall be used for introduction of further C-ITS functions DATEX II User Forum Dublin 13&14 September 2016

4. Architecture of the C-ITS-Corridor DATEX II User Forum Dublin 13&14 September 2016

5. Architecture of a cooperative centre Traffic lights DATEX II TCC OCIT-O DATEX II Trailer Cooperative Centre ? Cooperative Centre of Babel Urban TMC ITS G5 OCIT-C Outstation RIS Serviceprovider DATEX II TLS TPEG DATEX II User Forum Dublin 13&14 September 2016

6. Goals and Challenges Connect Trailers Connect Roadworks information centre Connect Traffic Control Centre Connect MDM Different communication interfaces are in use Different data models are in use Different protocols are in use How can this variety be supported without loosing control? DATEX II User Forum Dublin 13&14 September 2016

7. Difference between data and protocol Data models correlate to languages German English Chinese Protocols correlate to communication types Telephone call Letter Email Talk Data is essential, not protocol DATEX II User Forum Dublin 13&14 September 2016

8. Structure of interfaces Data Example UML, Conceptual data description Platform Independent Model (PIM) Logical data model Platform Specific Model (PSM) Physical data coding XSD, ASN.1, XML, ASN.1-PER, JSON, Protocol Application protocol Transfer protocol SOAP, REST, SNMP, ITS G5, HTTP, Websockets, ITS-transport, DATEX II User Forum Dublin 13&14 September 2016

9. Interface stacks in C-ITS Corridor General structure DATEX II ICS ITS-G5 ? ITS TS PDF Conceptual DATEX II UML ICS UML Data Logical ITS ASN.1 DATEX II XSD ICS XSD Physical DATEX II XML ICS XML ASN.1 UPER Protocol Application protocol SOAP STOMP ITS G5 Transfer protocol HTTP Websockets ITS Transport DATEX II User Forum Dublin 13&14 September 2016

10. What happens? Roadworks trailer Code with failure Chinese whispers! DATEX II User Forum Dublin 13&14 September 2016

11. Project specific solution Platform independent data model: ICS UML Work in progress DATEX II UML ICS UML ITS ASN.1 DATEX II XSD ICS XSD DATEX II XML ICS XML ASN.1 UPER SOAP STOMP ITS G5 HTTP Websockets ITS Transport DATEX II User Forum Dublin 13&14 September 2016

12. General project specific solution 1. Collect platform specific models (PSMs) 2. Develop canonical data model (PIM) 3. Map PIM to every PSM PSM 2 PSM 3 PSM 1 PIM PSM 4 PSM 6 PSM 5 DATEX II User Forum Dublin 13&14 September 2016

13. General cross-project solution Many PIMs ITS-Metadata Registry ITS-Metadata Registry ITS-Frame architecture PIM 1 PIM 2 PIM n ITS-Reference architecture PSM 1 PSM 2 PSM n Coding 1 Coding 2 Coding n Application 1 Application 2 Application n Community solution Future dreams Transfer 1 Transfer 2 Transfer n DATEX II User Forum Dublin 13&14 September 2016

14. Thank you for your attention Any questions? DATEX II User Forum Dublin 13&14 September 2016