Abstract
The article summarizes key recommendations for creating a traffic and travel information distribution architecture, which will function properly and without changes for longer time. Recommendations are based on a work proposing an architecture over a distributing traffic and travel information over digital radio broadcasting and Internet using TPEG formats and protocols. The whole process of architecturing is briefly described starting with the planning scope, expected results and steps to achieve them; and the process of requirement engineering. For the requirements a list of user needs, created for intelligent transportation systems (ITS) by project KAREN, was found to be very useful. Lessons learned from existing traffic information distribution systems are also discussed as they were another source of requirements. Before describing the architecture, unique design concepts of TPEG itself are mentioned, namely the possibility to seamlessly convert a TPEG message from binary format to XML and back; promising location referencing methods incl. AGORA C; and the ability to be backward compatible even after enhancing the TPEG message to the server for new or updated TPEG applications. All those TPEG design concepts allowed the development of very modular and flexible architecture for distribution. The architecture itself is then briefly outlined by means of selected set of use cases, describing core functionality of reception and distribution; and by a sample deployment model, depicting the possible physical structure of a future working system. Finally, based on the created architecture, recommendations are stated. The system must be designed as a pure distribution channel, changes expected in the future are identified, suitable requirement engineering methods are proposed and the need for monitoring and auditing tooling is highlighted. Open issue is practical availability of the dynamic location referencing method which shall be evaluated in the near future.
Highlights
The architecture of an information distribution system affects many parties: the information provider, distributor and many information consumers
Key architectural concepts for TPEG itself are very close to the definition of a universal soldier: they change the form appropriate to the situation while not loosing anything of their identity; are expert on knowing where you are; and are able to evolve and grow without harming cooperation with older systems and colleagues.We found these TPEG concepts very handy for architecting our TPEG distribution system
« d e vi ce » DAB receiv er TPEG design concepts allow designing the architecture of a system for traffic information distribution, which is very likely to last unchanged as new TPEG applications and even distribution channels will appear
Summary
The architecture of an information distribution system affects many parties: the information provider, distributor and many information consumers. It is highly desirable to create such an architecture, which provides the needed functionality and works in a long term view. This article aims to summarize key recommendations for creating a traffic information distribution architecture, which will function properly and without changes for a longer time. Recommendations are based on a detailed architecture design for distributing traffic information using the TPEG protocol as described in (Vlčinský 2008a). Before describing the resulting architecture, unique features of TPEG are discussed, as they strongly affected and simplified the task. The resulting architecture is described and key findings are summarized
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
