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

This triple is bi-directional. See also Other METR Systems --> METR System: 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 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

Solutions are sorted in ascending Gap Severity order. The Gap Severity is the parenthetical number at the end of the solution.

Selected Solution

METR: Discrepancy Reporting Requirements - OMG DDS

Solution Description

This solution is used within the U.S.. It combines standards associated with METR: Discrepancy Reporting Requirements with those for OMG DDS. The METR: Discrepancy Reporting Requirements standards include upper-layer standards required to exchange traffic regulation discrepancies with a discrepancy handling center. The OMG DDS standards include lower-layer standards that support secure data sharing and command operations between remote devices.

ITS Application Entity
Mind the gapMind the gap

ISO 24315-7
ISO 24315-8
Click gap icons for more info.
Mgmt

OMG DDS
Facilities
Mind the gapMind the gapMind the gap

(None)
OMG DDS
OMG DDS-RPC
OMG DDSI-RTPS
Security

OMG DDS-Security
TransNet

IETF RFC 768
IP Alternatives
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 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