Multimodal Crossing Equipment --> Traffic Management Center:
multimodal crossing status

Definitions

multimodal crossing status (Information Flow): Indication of operational status and pending requests for right-of-way from equipment supporting the non-highway mode at multimodal crossings.

Multimodal Crossing Equipment (Source Physical Object): 'Multimodal Crossing Equipment' represents the control equipment that interfaces to a non-road based transportation system at an interference crossing with the roadway. The majority of these crossings are railroad grade crossings that are more specifically addressed by the "Wayside Equipment" terminator. This multimodal crossing terminator addresses similar interface requirements, but for other specialized intersections like draw bridges at rivers and canals. These crossings carry traffic that may take priority over the road traffic at the intersection. The data provided will in its basic form be a simple "stop road traffic" indication. However more complex data flows may be provided that give the time at which right-of-way will be required and the duration of that right-of-way requirement.

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:

This Triple has the following triple relationships:

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) - OMG DDS

Solution Description

This solution is used within the U.S.. It combines standards associated with (None-Data) with those for OMG DDS. The (None-Data) standards include an unspecified set of standards at the upper layers. The OMG DDS standards include lower-layer standards that support secure data sharing and command operations between remote devices.

ITS Application Entity
Mind the gap

Development needed
Click gap icons for more info.

Mgmt

OMG DDS
Facilities
Mind the gapMind the gap

Development needed
OMG DDS
OMG DDS-RPC
OMG DDSI-RTPS
Security

OMG DDS-Security
TransNet

IETF RFC 768
IP Alternatives
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 Local
Acknowledgement True
Cardinality Unicast
Initiator Source
Authenticable True
Encrypt False


Interoperability Description
Local In cases where an interface is normally encapsulated by a single stakeholder, interoperability is still desirable, but the motive is vendor independence and the efficiencies and choices that an open standards-based interface provides.

Security

Information Flow Security
  Confidentiality Integrity Availability
Rating Low Moderate Low
Basis There should be no sensitive information in this flow. Raise to MODERATE if reverse engineering of a proprietary interface is a concern. This information can indicate when a road is closed to due a drawbridge being raised, which has a significant effect on traffic. If this information were falsified, it could have a significant negative effect on mobility over a large area. Should not require rapid response or frequent update. Raise to MODERATE if frequent real-time updates are part of the system scope.


Security Characteristics Value
Authenticable True
Encrypt False