210 likes | 408 Views
Future Communication between Outstations and Centres – A Concept for the German Motorways. Eike Pögel Heusch/Boesefeldt GmbH Dr. Lutz Rittershaus Federal Highway Research Institute - BASt. Implementation of an ITS-system in Germany since about 30 years. 1975: VRZ Aichelberg.
E N D
Future Communication between Outstations and Centres – A Concept for the German Motorways Eike PögelHeusch/Boesefeldt GmbH Dr. Lutz RittershausFederal Highway Research Institute - BASt
Implementation of an ITS-system in Germany since about 30 years. 1975: VRZ Aichelberg 2005: VZ Hessen
Programme on traffic management for the federal motorways in Germany. Current and planned (till 2007) systems:1.200 km Section Management 1.700 km Network Management
Regional Traffic Information Centre Communication interface to external Systems (e.g. Datex) Directives Traffic Control Centre TCC Instructions for the Equipment of Traffic Control and Sub Centres (MARZ), "AK VRZ" Sub-Centre SC SC SC Technical Specifications for Outstations (TLS) Outstation OS OS OS Detectors, Variable Message Signs, ... Traffic Control System Germany. ForeignTraffic Centre
Basic idea of the TLS: to define functional groups for roadside equipment, to standardise the interfaces and communication protocols, to create a common data modelling, to make the equipment of different suppliers compatible, to define and test performances and to allow open and clear tendering and system operation. Interface between Outstations and TCCs. TLS Roadside Outstation Traffic Control Centre / Sub-Centre TLS: Technische Lieferbedingungen für Streckenstationen / Technical Specifications for Outstations
Structure of TLS. • FG 0: Reserved for testing purposes • FG 1: Traffic data acquisition • FG 2: Weight in motion • FG 3: Environmental data acquisition • FG 4: Variable message sign and variable direction sign control • FG 6: Operational messages and control • FG 7: Control of external systems • FG 8: Speed control systems • FG 9: Ramp metering • FG 10 to 127: Reserved for subsequent universal definitions • FG 128 to 253: Res. for manufacturer defined function groups • FG 254: System control (internal) • FG 255: Reserved for special applications
History of TLS. • Preliminary Issue in 1988, content: Traffic data acquisition • Issue in 1990 with additional features on communication • Issue 1993: first complete edition, compulsory for roadside traffic control equipment • Main Draft in 1997 • Issue 2002: optimised, revised edition • Issue 2007 in preparation: new communication technique and additional features
Communication restricted by infrastructure of the 80´s Partyline 1200 Baud datagram size <256 bytes Research projects: Recommendations for a new TLS Communication technology Technical Organizational Constraints of todays TLS
Recommendation: „TLS goes TCP/IP“ Todays standard communication protocol Austrian ASFiNAG: Adoption of TLS, but with TCP/IP extensions NTCIP (USA) based on TCP/IP (UDP) In-field communication: PROFIBUS -> PROFINET TT: DATEX(2) TCP/IP
With introduction of TCP/IP broad range of technologies available Fiber optics Twisted pair WLAN GSM/GPRS Hard- and software vendors Conclusion: Motorway communication infrastructure as network Hardware Infrastructure
TLS-ISO/OSI Layer 7 Actual TLS-datagramm description Bits&bytes Paperwork, not toolbased Ambigous Error-prone interpretation Weak modelling Data Modelling (1/3)
Tool: UML as platform independent modelling language TLS-datagrams as UML packages and class diagrams TLS procedures as UML sequence diagrams UML profiling for various aspects possible XML profiles SOA profiles (e.g CORBA, SOAP) „old TLS“ profile (->backward compatibility) Data Modelling (2/2)
TCC/SC networks firewalled IP communication between outstation and TCC/SC Outstations become part of TCC/SC network Potential breach of security Recommendation: Tunneling (ssh/ssl) Point-to-point communication: Portforwarding Strong encryption: Verifies data integrity Public-private-key authentication Security aspects
Migration Strategy TCC/SC Applications application level gateway TLS-OSI 1-7 SOAP/ TCP/IP network infastructure field bus / party line TLS-OSI 1-7 SOAP/ TCP/IP outstation functional groups outstation applications
Concept based on TCP/IP OTS communication hard- and software Exact data modelling Backward compatibility: Migration concept allowing for integration of old and new TLS infrastructure Recommendation: Concept study of a TCP/IP/SOA(P)-based TLS system Consistent TLS-communication concept
This working group consists of representatives from: Road operators (German road administrations) Sensor and VMS manufacturer Traffic control centre manufacturer Engineering and consulting companies Creation of TLS. The further development of the TLS is be done by the AK TLS (Working Group TLS).
A modular loose-leaf document system allow the actualisation and release of single chapters without releasing a complete new edition. Updates and corrections should in the future be initiated by any member of the TLS community using a RFP/RFC procedure, moderated by BASt. Updating of TLS.
! Thank you for your attention Eike Pögel Heusch/Boesefeldt GmbH Transport Telematics Tempelhofer Straße 4-6 52068 Aachen Germany eike.poegel@heuboe.de Dr.-Ing. Lutz Rittershaus Federal Highway Research Institute Telematics, Traffic Management Brüderstraße 53 51427 Bergisch Gladbach Germany rittershaus@bast.de