摘要: |
The GCM Corridor was one of the four priority corridors established under the ISTEA legislation. The Gateway TIS is the core system that facilitates the integration and interoperation of many other ITS systems within this corridor. The Gateway TIS collects transportation related information from geographically widely distributed TIS data source systems, validates and fuses the information collected, and disseminates it to interested public and private entities and the general public via internet and intranet. The implementation of the Gateway TIS involves integrating a growing number of ITS related center systems of assorted natures and various technical configurations. Apart from a myriad of institutional issues that needed to be solved, a range of Center-to-Center (C2C) technical standards were needed to define communication protocols, data formats, and application programming interfaces (API). It was realized at the beginning of the project that the adoption of and compliance with national ITS standards would considerably increase the chance of success in effectively achieving C2C interconnectivity and interoperability. However, it was soon discovered that, not only the C2C API standard was absolutely absent, but also the available national ITS C2C data standards were specified as data dictionaries, message sets, which were not in a form to support object-oriented or CORBA-based software engineering practices. The Gateway TIS system architecture called for the use of CORBA as its C2C and Inter-Process Communication (IPC) protocols. CORBA was one of the two NTCIP C2C protocols, it was chosen because it provides the most efficient way for the Gateway to interface a large number of different ITS center systems, and offers a pure object-oriented software engineering environment. To fill in the vacuum created by the lack of national CORBA standards for C2C applications, the Gateway development team conducted a close evaluation of available non-CORBA standards, and developed a basic set of CORBA-based standards to support the integration of ITS center systems within the GCM corridor. This standard set includes two components: Gateway Data Object Model (GDOM) and Gateway Message Oriented Middleware (GMOM). While GDOM specifies the data format in terms of CORBA data constructs, GMOM provides a CORBA specification of APIs that facilitates the exchange of TIS data in the format defined by GDOM. Recently, the Object Management Group (OMG), an international standard development organization, formed a Transportation Domain Task Force (DTF). This OMG Transportation DTF issued a RFI in an effort to start a process of full scale specification development of CORBA-based ITS C2C standards. The Illinois Department of Transportation (IDOT) and Parsons Transportation Group (PTG) have jointly responded to this RFI by providing information on GDOM, GMOM, and our Gateway implementation experiences. We hope our pioneering efforts in CORBA-based C2C standardization in the GCM corridor could provide a proven starting ground for national CORBA-based standardization process. |