METR System --> Other METR Systems:
consolidated discrepancy report
This triple is bi-directional. See also
Other METR Systems --> METR System: consolidated discrepancy report
Definitions
consolidated discrepancy report (Information Flow): This flow allows the METR Discrepancy Handling Center to send consolidated discrepancy reports to the intended destination. The consolidated reports are sent when conditions, as defined by local policies, are met (e.g., a sufficient number of reports have been received). The destination might be another METR Discrepancy Handing Center (e.g., an OEM sending data to a governmental handling system) but eventually, the consolidated reports are sent to the relevant METR Regulation Center.
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.
Other METR Systems (Destination Physical Object): The 'Other METR System' represents...
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: Discrepancy Reporting Requirements - Secure Internet (ITS) (19)
- METR: Discrepancy Reporting Requirements - Apache Kafka (23)
- METR: Discrepancy Reporting Requirements - OMG DDS (23)
- METR: Discrepancy Reporting Requirements - OASIS MQTT (29)
- (None-Data) - Secure Internet (ITS) (32)
- METR: Discrepancy Reporting Requirements - OASIS AMQP (32)
- (None-Data) - OASIS MQTT (42)
- (None-Data) - OASIS AMQP (45)
Selected Solution
Solution Description
ITS Application Entity
ISO 24315-7 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 |