Other METR Regulation Systems --> METR Regulation System:
system-generated discrepancy report

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

Other METR Regulation Systems (Source Physical Object): 'Other METR Regulation Systems' supports information exchange between METR Regulation Systems. A METR Regulation System may exchange METR information with other METR regulation systems to enhance the trustworthiness, both in terms of accuracy and completeness.

METR Regulation System (Destination Physical Object): The 'METR Regulation System' creates and maintains electronic versions of traffic regulations for eventual consumption by traveler systems and other interested parties. Once approved, each rule is signed and traceable to a specific Rule-Maker. Depending on local policies and division of labor, the METR Regulation Center might need to coordinate with a METR Verification Center, a Maintenance and Construction Management System, and METR Discrepancy Handling Centers.

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:

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: Regulation Requirements - Secure Internet (ITS)

Solution Description

This solution is used within Canada, the E.U. and the U.S.. It combines standards associated with METR: Regulation Requirements with those for I-I: Secure Internet (ITS). The METR: Regulation Requirements standards include upper-layer standards required to exchange traffic regulations with a regulatory center. The I-I: Secure Internet (ITS) standards include lower-layer standards that support secure communications between ITS equipment using X.509 or IEEE 1609.2 security certificates.

ITS Application Entity
Mind the gapMind the gap

ISO 24315-4
ISO 24315-8
Click gap icons for more info.
Mgmt
Facilities
Mind the gap

(None)
Security
Mind the gapMind the gap
TransNet
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