METR System --> Maint and Constr Vehicle OBE:
METR management information

Definitions

METR management information (Information Flow): If the rule is to be distributed through a specialized vehicle OBE, the METR input device configures and monitors the OBE using the METR management info. While the content of this flow is similar to a combination of the "METR application information" flow and the "METR application status" flow, the mobile nature of the OBE results in different communication characteristics, which results in a different flow.

METR System (Source Physical Object): The 'METR System' creates and maintains electronic versions of traffic rules, regulations, ordinances and statutes that have official status and must be understood by all motor vehicle operators and intelligent vehicles that operate at higher automation levels. This system represents multiple authorities that operate at local, regional, state, and national levels and represents organizations that establish, manage, and enact the traffic code. Each electronic rule is approved, signed, and traceable to a specific rule-maker. Rules are independently verified. Any identified or reported rule discrepancies are analyzed, investigated, and addressed.

Maint and Constr Vehicle OBE (Destination Physical Object): The 'Maint and Constr Vehicle OBE' resides in a maintenance, construction, or other specialized service vehicle or equipment and provides the processing, storage, and communications functions necessary to support highway maintenance and construction. All types of maintenance and construction vehicles are covered, including heavy equipment, supervisory vehicles, unmanned remote controlled field maintenance robots, and sensory platforms that may be wheeled or low altitude aerial vehicles (e.g. drones, balloons). The MCV OBE provides two-way communications between drivers/operators and dispatchers and maintains and communicates current location and status information. A wide range of operational status is monitored, measured, and made available, depending on the specific type of vehicle or equipment. A snow plow for example, would monitor whether the plow is up or down and material usage information. The Maint and Constr Vehicle OBE may also contain capabilities to monitor vehicle systems to support maintenance of the vehicle itself. A separate 'Vehicle OBE' physical object supports the general vehicle safety and driver information capabilities that apply to all vehicles, including maintenance and construction vehicles. The Maint and Constr Vehicle OBE supplements these general capabilities with capabilities that are specific to maintenance and construction vehicles.

Included In

This Triple is in the following Service Packages:

• VS17: Management of Electronic Traffic Regulations (METR)

This Triple is described by the following Functional View Functional Objects:

• MCV METR Emergent Information Dissemination
• METR Localized Distribution

This Triple is described by the following Functional View Data Flows:

• None

This Triple has the following triple relationships:

Communication Solutions

• US: NTCIP Roadside Unit - Wireless SNMPv3/TLS (7)
• (None-Data) - Secure Wireless Internet (EU) (32)
• (None-Data) - OASIS MQTT over Wireless (42)
• (None-Data) - OASIS AMQP over Wireless (45)

Selected Solution

US: NTCIP Roadside Unit - Wireless SNMPv3/TLS

Solution Description

ITS Application Entity NTCIP 1218			Click gap icons for more info.
Mgmt NTCIP 1201 Bundle: SNMPv3 MIB	Facilities NTCIP 1218 ISO 15784-2	Security IETF RFC 6353
	TransNet IP Alternatives Internet Transport Alternatives
	Access Wireless Internet Alternatives (NA)

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

Security