Traffic Management Center --> Surface Transportation Weather Service:
road network environmental situation data

Definitions

road network environmental situation data (Information Flow): Aggregated environmental situation data collected from vehicles and other sources for the road network. Aggregated information would include measured air temperature, exterior light status, wiper status, sun sensor status, rain sensor status, traction control status, ALB status, and other collected vehicle system status and sensor information for the region.

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.

Surface Transportation Weather Service (Destination Physical Object): The 'Surface Transportation Weather Service' represents the providers of value-added sector-specific meteorological services. These providers utilize National Weather Service data and predictions, road condition information and local environmental data provided by traffic management or maintenance organizations, and their own models to provide surface transportation related weather observations and forecasts including pavement temperature and conditions.

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

Solutions are sorted in ascending Gap Severity order. The Gap Severity is the parenthetical number at the end of the solution.

Selected Solution

(None-Data) - OASIS MQTT

Solution Description

This solution is used within Australia, Canada and the U.S.. It combines standards associated with (None-Data) with those for OASIS MQTT. The (None-Data) standards include an unspecified set of standards at the upper layers. The OASIS MQTT standards include lower-layer standards that support data distribution of specific types of data.

ITS Application Entity
Mind the gapMind the gapMind the gap

Development needed
Click gap icons for more info.
Mgmt

OASIS MQTT DMP
Facilities
Mind the gapMind the gapMind the gap

Development needed
OASIS MQTT
Security
Mind the gapMind the gap
TransNet
Access

Internet Subnet Alternatives
TransNet TransNet

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

Access Access

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

ITS Application ITS Application

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

Mgmt Mgmt

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

Facility Facility

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

Security Security

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

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 Aggregated data, but indicates the types of systems and status of those systems on vehicles. Should be LOW, but if identifiers are preserved could be MODERATE. Weather Service providers will have many sources of data, and depend on consistent, quality data inputs, so this data needs to meet similar standards at least in terms of transmission quality. MODERATE or HIGH depending on the context; if critical to some operation then HIGH, if not critical then MODERATE. Weather Service providers will have many sources of data, and depend on consistent, quality data inputs, so this data needs to meet similar standards at least in terms of transmission quality.


Security Characteristics Value
Authenticable True
Encrypt False