Personal Information Device --> METR System:
METR discrepancy report
Definitions
METR discrepancy report (Information Flow): The "METR discrepancy report" information flow enables a METR User Device to alert the METR Discrepancy Handing Center of detected discrepancies (e.g., a conflict among METR rules, a conflict between an METR rule and a physical TCD) by issuing a report (e.g., images, OCR data) that identifies the apparent discrepancy in transport-related rules. The discrepancy will indicate the rule identifier(s), type of discrepancy, and supporting evidence to assist in a further, independent investigation. The discrepancy might be between electronic rules or between electronic and physical rules.
Personal Information Device (Source Physical Object): The 'Personal Information Device' provides the capability for travelers to receive formatted traveler information wherever they are. Capabilities include traveler information, trip planning, and route guidance. Frequently a smart phone, the Personal Information Device provides travelers with the capability to receive route planning and other personally focused transportation services from the infrastructure in the field, at home, at work, or while en-route. Personal Information Devices may operate independently or may be linked with vehicle on-board equipment. This subsystem also supports safety related services with the capability to broadcast safety messages and initiate a distress signal or request for help.
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: Consumer Requirements - Secure Wireless Internet (ITS) (19)
- (None-Data) - Secure Wireless Internet (EU) (32)
Selected Solution
Solution Description
ITS Application Entity
Development needed |
Click gap icons for more info.
|
||
Mgmt
|
Facilities
Development needed |
Security
|
|
TransNet
|
|||
Access
|
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 |
---|---|
National | This triple should be implemented consistently within the geopolitical region through which movement is essentially free (e.g., the United States, the European Union). |
Security
Information Flow Security | ||||
---|---|---|---|---|
Confidentiality | Integrity | Availability | ||
Rating | Moderate | Moderate | Low | |
Basis | Will include some artifact indicating the identity of the reporter; while this could be a pseudonym, it could eventually be associated with the reporter. There is no good reason for discrepancy reporters to be observed by anyone outside the METR system. | 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. | There should be many opportunities to provide discrepancy reports, so there is no pressing need for a requirement above LOW. |
Security Characteristics | Value |
---|---|
Authenticable | True |
Encrypt | True |