METR Distribution Center --> METR System:
system-generated discrepancy report
Definitions
system-generated discrepancy report (Information Flow): METR Regulation Centers can learn of discrepancies from METR Distribution Centers or other regulation centers that identify conflicts during their rule verification processes. The system-generated discrepancy report identifies the specific elements of METR information that caused the verification error, including the METR information identifier and the specific issue that caused the problem.
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).
METR System (Destination 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.
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:
- None
This Triple has the following triple relationships:
None |
Communication Solutions
- METR: Regulation Requirements - Secure Internet (ITS) (14)
- (None-Data) - Secure Internet (ITS) (32)
- (None-Data) - OASIS MQTT (42)
- (None-Data) - OASIS AMQP (45)
Selected Solution
Solution Description
ITS Application Entity
ISO 24315-4 ISO 24315-8 |
Click gap icons for more info.
|
||
Mgmt
|
Facilities
(None) |
Security
|
|
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 | Source |
Authenticable | True |
Encrypt | True |
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 | Moderate | Moderate | Moderate | |
Basis | Discrepancy-handling flows may contain a significant amount of discrepancy reporting information, which could imply behavior in the field, actions of rules-agents and other activities that could be leveraged by bad actors. | Information contained in this flow will be used to assess the accuracy of existing rules; this will require some process that strips out incorrect reports, but the number of incorrect reports should be minimized to reduce undue processing.` | Backoffice discrepancy handling flows should be basically reliable, else the discrepancy handling system will have difficulty functioning, which in turn could lead to negative safety or other impacts in the field. |
Security Characteristics | Value |
---|---|
Authenticable | True |
Encrypt | True |