Travel Services Provider System --> Transportation Information Center:
travel service information
Definitions
travel service information (Information Flow): Information supplied by a service provider (e.g., a hotel or restaurant) that identifies the service provider and provides details of the service offering. This flow covers initial registration of a service provider and subsequent submittal of new information and status updates so that data currency is maintained.
Travel Services Provider System (Source Physical Object): The 'Travel Services Provider System' represents the individual information systems operated by providers of traveler-oriented services. Example services that could be included are gas, food, lodging, electric vehicle charging, vehicle repair, points of interest, and recreation areas. Also included are services specifically directed toward bicyclists and pedestrians such as bicycle shops and parking locations and bicycle and pedestrian rest areas. The interface with the Service Provider is necessary so that accurate, up-to-date service information can be provided to the traveler and to support electronic reservation capabilities.
Transportation Information Center (Destination 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.
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:
- ftsp-emergency_travel_service_update
- ftsp-provider_profile_update
- ftsp-request_provider_registration
- ftsp-travel_services_data
This Triple has the following triple relationships:
None |
Communication Solutions
- (None-Data) - Secure Internet (ITS) (44)
- (None-Data) - Apache Kafka (45)
- (None-Data) - OMG DDS (45)
- (None-Data) - OASIS MQTT (51)
- (None-Data) - OASIS AMQP (62)
Selected Solution
Solution Description
ITS Application Entity
Development needed |
Click gap icons for more info.
|
||
Mgmt
OMG DDS |
Facilities
Development needed OMG DDS OMG DDS-RPC OMG DDSI-RTPS |
Security
OMG DDS-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 | Moderate | |
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. | While accuracy of this data is important for decision making purposes, applications should be able to cfunction without it. Thus MODERATE generally. | While accuracy of this data is important for decision making purposes, applications should be able to cfunction without it. Thus MODERATE generally. |
Security Characteristics | Value |
---|---|
Authenticable | True |
Encrypt | False |