METR Discrepancy Handling System --> Other METR Discrepancy Handling Systems:
discrepancy suppression information

Definitions

discrepancy suppression information (Information Flow): Once a METR Regulation Center has been alerted to a discrepancy, it may wish to suppress further notices in one of two ways. If it still wants vehicles to gather data but for that data not to be submitted except on request, it can use discrepancy suppression info flow to prevent METR Discrepancy Handling Centers from issuing consolidated discrepancy reports (but the newly gathered information is still available through the detailed flow). Alternatively, the METR Regulation Center can revise the associated rule meta-data to inform vehicles that a discrepancy with the rule is already known and that discrepancy reports should not be provided for the rule. This mechanism uses the centralized and localized rule distribution services. Furthermore, the METR Regulation Center may wish to inform other METR Discrepancy Handling Centers to correspondingly suppress further notices of those suppressed discrepancies.

METR Discrepancy Handling System (Source Physical Object): The 'METR Discrepancy Handling System' receives reports of discrepancies in rules from METR User Systems. It will perform a numerical analysis of discrepancy count vs. time for any given rule, and when warranted, report to the METR Regulation Center those rules with sufficient discrepancy reports to justify further investigation. It is identified as a separate center to provide a level of anonymity for the user that reports the issue. The METR Discrepancy Handling Center may register its availability as a service, and its associated cyber location information, with the Object Registration and Discovery System (ORDS).

Other METR Discrepancy Handling Systems (Destination Physical Object): Depending on deployments scenarios, a discrepancy report might be passed among multiple levels of Discrepancy Handling Systems. For example, a vehicle might be configured to report all its detected discrepancies to an OEM-operated Discrepancy Handling Center. This allows the OEM to become aware of potential problems with its discrepancy detection logic.
Once established thresholds are met, the OEM-operated Discrepancy Handling System might notify a Discrepancy Handling Center operated by a jurisdictional entity. The jurisdictional Discrepancy Handling System can then determine when the METR Regulation System is notified of the reported discrepancies.

Included In

This Triple is in the following Service Packages:

• None

This triple is associated with the following Functional Objects:

• None

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

• None

This Triple has the following triple relationships:

Communication Solutions

• METR: Discrepancy Reporting Requirements - Secure Internet (ITS) (27)
• METR: Discrepancy Reporting Requirements - Apache Kafka (28)
• METR: Discrepancy Reporting Requirements - OMG DDS (28)
• METR: Discrepancy Reporting Requirements - OASIS MQTT (34)
• (None-Data) - Secure Internet (ITS) (43)
• METR: Discrepancy Reporting Requirements - OASIS AMQP (45)

Selected Solution

METR: Discrepancy Reporting Requirements - Apache Kafka

Solution Description

ITS Application Entity ISO 24315-7 ISO 24315-8			Click gap icons for more info.
Mgmt Apache Zookeeper	Facilities (None) Apache Kafka Apache Zookeeper	Security IETF RFC 8446
	TransNet IP Alternatives IETF RFC 9293
	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

Security