Transportation Information Center --> Other Transportation Information Centers:
alternate mode information
This triple is bi-directional. See also
Other Transportation Information Centers --> Transportation Information Center: alternate mode information
Definitions
alternate mode information (Information Flow): Schedule information for alternate mode transportation providers such as air, ferry, and passenger-carrying heavy rail. This also includes details of incidents and other service disruptions that have occurred in the alternative mode. This also includes measures of service demand that supports assessment of their impact on the road network.
Transportation Information Center (Source Physical Object): The 'Transportation Information Center' collects, processes, stores, and disseminates transportation information to system operators and the traveling public. The physical object can play several different roles in an integrated ITS. In one role, the TIC provides a data collection, fusing, and repackaging function, collecting information from transportation system operators and redistributing this information to other system operators in the region and other TICs. In this information redistribution role, the TIC provides a bridge between the various transportation systems that produce the information and the other TICs and their subscribers that use the information. The second role of a TIC is focused on delivery of traveler information to subscribers and the public at large. Information provided includes basic advisories, traffic and road conditions, transit schedule information, yellow pages information, ride matching information, and parking information. The TIC is commonly implemented as a website or a web-based application service, but it represents any traveler information distribution service.
Other Transportation Information Centers (Destination Physical Object): Representing another Transportation Information Center, this object is intended to provide a source and destination for ITS information flows between peer information and service provider functions. It enables cooperative information sharing between providers as conditions warrant.
Included In
This Triple is in the following Service Packages:
- TI01: Broadcast Traveler Information
- TI02: Personalized Traveler Information
- TI03: En-Route Guidance
- TI04: Trip Planning and Payment
- TI08: Personal Wayfinding
This triple is associated with the following Functional Objects:
This Triple is described by the following Functional View Data Flows:
This Triple has the following triple relationships:
None |
Communication Solutions
- EU: DATEX - DATEX Messaging (3)
- EU: SIRI - Secure Internet (ITS) (6)
- US: ATIS - Secure Internet (ITS) (24)
- (None-Data) - Secure Internet (ITS) (43)
- Data for Distribution (TBD) - Apache Kafka (44)
- Data for Distribution (TBD) - OMG DDS (44)
- (None-Data) - OASIS MQTT (50)
- Data for Distribution (TBD) - OASIS MQTT (50)
- Data for Distribution (TBD) - OASIS AMQP (61)
Selected Solution
Solution Description
ITS Application Entity
CEN 15531-5 CEN 15213-4 CEN 15531-3 CEN 12896-4 CEN 12896-6 |
Click gap icons for more info.
|
||
Mgmt
|
Facilities
CEN 15531-2 |
Security
|
|
TransNet
|
|||
Access
Internet Subnet Alternatives |
Note that some layers might have alternatives, in which case all of the gap icons associated with every alternative may be shown on the diagram, but the solution severity calculations (and resulting ordering of solutions) includes only the issues associated with the default (i.e., best, least severe) alternative.
Characteristics
Characteristic | Value |
---|---|
Time Context | Recent |
Spatial Context | Regional |
Acknowledgement | True |
Cardinality | Unicast |
Initiator | Destination |
Authenticable | True |
Encrypt | False |
Interoperability | Description |
---|---|
Regional | Interoperability throughout the geopolitical region is highly desirable, but if implemented differently in different transportation management jurisdictions, significant benefits will still accrue in each jurisdiction. Regardless, this Information Flow Triple should be implemented consistently within a transportation jurisdiction (i.e., the scope of a regional architecture). |
Security
Information Flow Security | ||||
---|---|---|---|---|
Confidentiality | Integrity | Availability | ||
Rating | Low | Moderate | Low | |
Basis | Generally, center-originating flows destined for a TIC don't contain any personal or confidential information, and are eventually intended for some kind of public consumption. | Generally transportation coordination information should be correct between source and destination, or inappropriate actions may be taken. | While useful, there is little impact if this flow is not available. |
Security Characteristics | Value |
---|---|
Authenticable | True |
Encrypt | False |