METR Distribution Center --> Other METR Distribution Centers:
METR information

This triple is bi-directional. See also Other METR Distribution Centers --> METR Distribution Center: METR information

Definitions

METR information (Information Flow): Transport-related regulations, ordinances, statutes, warnings, and advisories that have official status and are legally-binding upon traveling entities (whether human or automated). Each rule is associated with its meaning, associated location(s), and conditional characteristics (e.g., effective times, applicable vehicle classes). This flow supports targeted transfer of rules to end user systems and may be initiated based on a query or pushed in a manner that provides user systems with access to rules that are relevant to their current conditions (e.g., vehicle classification, user classification, location, timeframe). Each rule is associated with an expiration time, after which it is no longer considered fully trustworthy. This flow supports bulk transfer of rules between back-office systems.

METR Distribution Center (Source Physical Object): The 'METR Distribution Center' manages the collection and dissemination of rules received from one or more METR Regulation Centers and will verify that, holistically, the collective information is trustworthy for subsequent distribution to METR Users. It will accept and respond to requests for METR information from METR Consumer Systems using the provided request criteria.
The METR Distribution Center can be distinct from the METR Regulation Center because it will frequently need to collect rules from multiple METR Regulation Centers representing various rule-makers with different jurisdictional authority (e.g., traffic agency vs. environmental agency), in different areas (e.g., neighboring jurisdictional areas), and different levels of government (e.g., federal, state, and local). Likewise, there might be different METR Distribution Centers for different purposes (e.g., one that focuses on mainstream vehicles and another for commercial vehicles). The METR Distribution Center may register its availability as a service, and its associated cyber location information, with the Object Registration and Discovery System (ORDS).

Other METR Distribution Centers (Destination Physical Object):

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

METR: Regulation Requirements - Apache Kafka

Solution Description

This solution is used within Canada and the U.S.. It combines standards associated with METR: Regulation Requirements with those for Apache Kafka. The METR: Regulation Requirements standards include upper-layer standards required to exchange traffic regulations with a regulatory center. The Apache Kafka standards include lower-layer open source code that supports data distribution of specific types of data.

ITS Application Entity
Mind the gap

ISO 24315-4
ISO 24315-8
Click gap icons for more info.

Mgmt

Apache Zookeeper
Facilities
Mind the gapMind the gapMind the gap

(None)
Apache Kafka
Apache Zookeeper
Security

IETF RFC 8446
TransNet

IP Alternatives
IETF RFC 9293
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 Source
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 High Moderate
Basis Since all rules are intended for public/machine consumption, there is little reason to obfuscate the information. Only in the case of an instance of the flow that is targeted to a specific vehicle or class of vehicles might encryption be warranted, as that distribution may imply the behavior or desired action of the target vehicles. Rules could be used to guide vehicle behavior, and if incorrect could lead to vehicles breaking actual rules with potentially highly damaging consequences. Updates are probably infrequent so often this flow can be a less than HIGH availability. In cases of high update (e.g., work zones, incidents), it could be HIGH.


Security Characteristics Value
Authenticable True
Encrypt False