Traffic Management Center --> Other Traffic Management Centers:
road network conditions
This triple is bi-directional. See also
Other Traffic Management Centers --> Traffic Management Center: road network conditions
Definitions
road network conditions (Information Flow): Current and forecasted traffic information, road and weather conditions, and other road network status. Either raw data, processed data, or some combination of both may be provided by this flow. Information on diversions and alternate routes, closures, and special traffic restrictions (lane/shoulder use, weight restrictions, width restrictions, HOV requirements) in effect is included.
Traffic Management Center (Source 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.
Other Traffic Management Centers (Destination Physical Object): Representing another Traffic Management Center, 'Other Traffic Management Centers' is intended to provide a source and destination for information exchange between peer (e.g. inter-regional) traffic management functions. It enables traffic management activities to be coordinated across different jurisdictional areas.
Included In
This Triple is in the following Service Packages:
- ST07: Eco-Lanes Management
- TM07: Regional Traffic Management
- TM08: Traffic Incident Management System
- TM09: Integrated Decision Support and Demand Management
- TM24: Tunnel Management
- VS08: Queue Warning
This triple is associated with the following Functional Objects:
- TMC Advanced Rail Crossing Management
- TMC Basic Surveillance
- TMC Environmental Monitoring
- TMC Incident Dispatch Coordination
- TMC Multimodal Crossing Management
- TMC Regional Traffic Management
- TMC Situation Data Management
- TMC Traffic Information Dissemination
- TMC Variable Speed Limits
This Triple is described by the following Functional View Data Flows:
- totm-road_network_inventory_and_status
- totm-road_weather_data
- totm-roadway_detours_and_closures
- totm-traffic_data
This Triple has the following triple relationships:
None |
Communication Solutions
- EU: DATEX - DATEX Messaging (3)
- US: TMDD - NTCIP Messaging (11)
- (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
|
Click gap icons for more info.
|
||
Mgmt
|
Facilities
No Standard Needed |
Security
IETF RFC 8446 |
|
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 | encrypted; but no harm should come from seeing this data | info needs to be accurate and should not be tampered but should be able to cope with some bad data; should be able to confirm conditions by other mechanisms | condition info should be timely and readily available so that TMCs are aware of current traffic info, conditions, restrictions, etc. but should not have severe/catastrophic consequences if not |
Security Characteristics | Value |
---|---|
Authenticable | True |
Encrypt | False |