Alternate Mode Transportation Center --> Traffic Management 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.
Alternate Mode Transportation Center (Source Physical Object): The 'Alternate Mode Transportation Center' provides the interface through which non-ITS transportation systems (e.g., airlines, ferry services, passenger-carrying heavy rail) can exchange data with ITS. This two-way interface enables coordination for efficient movement of people across multiple transportation modes. It also enables the traveler to efficiently plan itineraries which include segments using other modes.
Traffic Management Center (Destination Physical Object): The 'Traffic Management Center' monitors and controls traffic and the road network. It represents centers that manage a broad range of transportation facilities including freeway systems, rural and suburban highway systems, and urban and suburban traffic control systems. It communicates with ITS Roadway Equipment and Connected Vehicle Roadside Equipment (RSE) to monitor and manage traffic flow and monitor the condition of the roadway, surrounding environmental conditions, and field equipment status. It manages traffic and transportation resources to support allied agencies in responding to, and recovering from, incidents ranging from minor traffic incidents through major disasters.
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:
- famtc-air_services
- famtc-alternate_mode_incident_information
- famtc-ferry_services
- famtc-non_motorized_services
- famtc-rail_services
This Triple has the following triple relationships:
None |
Communication Solutions
- EU: DATEX - DATEX Messaging (3)
- EU: SIRI - Secure Internet (ITS) (11)
- US: ATIS - Secure Internet (ITS) (18)
- (None-Data) - Secure Internet (ITS) (32)
- Data for Distribution (TBD) - Apache Kafka (36)
- Data for Distribution (TBD) - OMG DDS (36)
- (None-Data) - OASIS MQTT (42)
- Data for Distribution (TBD) - OASIS MQTT (42)
- Data for Distribution (TBD) - OASIS AMQP (45)
Selected Solution
Solution Description
ITS Application Entity
Development needed |
Click gap icons for more info.
|
||
Mgmt
OASIS MQTT DMP |
Facilities
OASIS MQTT |
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 | Now |
Spatial Context | Regional |
Acknowledgement | True |
Cardinality | Unicast |
Initiator | Source |
Authenticable | True |
Encrypt | False |
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 | Low | Moderate | Low | |
Basis | Should not contain any personal or confidential information. | 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 |