Transportation Information Center --> Other Transportation Information Centers:
trip plan
This triple is bi-directional. See also
Other Transportation Information Centers --> Transportation Information Center: trip plan Definitions
trip plan (Information Flow): A travel itinerary covering single or multimodal travel. The itinerary identifies a route and associated traveler information and instructions identifying recommended trip modes (including indoor and outdoor wayfinding) and transfer information, ride sharing options, and transit and parking reservation information. This flow also includes intermediate information that is provided as the trip plan is interactively created, including identification of alternatives, requests for additional information as well as amenities along the trip.
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:
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
-
US: ATIS - Secure Internet (ITS) (24)
-
(None-Data) - Secure Internet (ITS) (43)
Selected Solution
(None-Data) - Secure Internet (ITS)Solution Description
|
ITS Application Entity
![]() ![]()
Development needed ![]() |
Click gap icons for more info.
|
||
|
Mgmt
|
Facilities
Development needed ![]() |
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 | False |
| Cardinality | Unicast |
| Initiator | Destination |
| Authenticable | True |
| Encrypt | True |
| Interoperability | Description |
|---|---|
| National | This triple should be implemented consistently within the geopolitical region through which movement is essentially free (e.g., the United States, the European Union). |
Security
| Information Flow Security | ||||
|---|---|---|---|---|
| Confidentiality | Integrity | Availability | ||
| Rating | Moderate | Moderate | Moderate | |
| Basis | Contains information dedicated to a particular user, so should be obfuscated to prevent determination of PII. May also incude payment information. | The trip plan will affect the user's interaction with the transit system, and notably can include payment information. If any of this is incorrect, the traveler will be adversely affected. If this is hacked, a traveler may be able to use the system for free. | This flow is part of a car-pooling service. If it doesn't work, the car-pooling service doesn't work. | |
| Security Characteristics | Value |
|---|---|
| Authenticable | True |
| Encrypt | True |


