METR Distribution Center --> Personal Information Device:
METR information for users
Definitions
METR information for users (Information Flow): The provision of METR information to METR User Devices based on requested criteria. This includes 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. The flow includes the regulations and the associated locations, effective date and time periods, and applicable vehicle classes. This flow supports targeted transfer of regulations to end user systems and may be initiated based on a query or pushed so that vehicles have access to relevant regulations for their vehicle classification at the current location, date, and timeframe.
METR Distribution Center (Source Physical Object): The 'METR Distribution Center' manages the collection and dissemination of rules received from one or more METR Regulation Centers and will verify that, holistically, the collective information is trustworthy for subsequent distribution to METR Users. It will accept and respond to requests for METR information from METR Consumer Systems using the provided request criteria.
The METR Distribution Center can be distinct from the METR Regulation Center because it will frequently need to collect rules from multiple METR Regulation Centers representing various rule-makers with different jurisdictional authority (e.g., traffic agency vs. environmental agency), in different areas (e.g., neighboring jurisdictional areas), and different levels of government (e.g., federal, state, and local). Likewise, there might be different METR Distribution Centers for different purposes (e.g., one that focuses on mainstream vehicles and another for commercial vehicles). The METR Distribution Center may register its availability as a service, and its associated cyber location information, with the Object Registration and Discovery System (ORDS).
Personal Information Device (Destination 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.
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:
Relationship | Source | Destination | Flow |
---|---|---|---|
Depends On | METR System | METR Distribution Center | METR information |
Communication Solutions
- METR: Distribution Requirements - Secure Wireless Internet (ITS) (19)
- METR: Distribution Requirements - Apache Kafka over Wireless (23)
- METR: Distribution Requirements - OMG DDS over Wireless (23)
- METR: Distribution Requirements - OASIS MQTT over Wireless (29)
- (None-Data) - Secure Wireless Internet (EU) (32)
- METR: Distribution Requirements - OASIS AMQP over Wireless (32)
- (None-Data) - OASIS MQTT over Wireless (42)
- (None-Data) - OASIS AMQP over Wireless (45)
Selected Solution
Solution Description
ITS Application Entity
ISO 24315-5 ISO 24315-8 |
Click gap icons for more info.
|
||
Mgmt
OASIS MQTT DMP |
Facilities
(None) OASIS MQTT |
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 | False |
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 | Low | High | Moderate | |
Basis | Since all rules are intended for public/machine consumption, there is little reason to obfuscate the information. Only in the case of an instance of the flow that is targeted to a specific vehicle or class of vehicles might encryption be warranted, as that distribution may imply the behavior or desired action of the target vehicles. | Rules could be used to guide vehicle behavior, and if incorrect could lead to vehicles breaking actual rules with potentially highly damaging consequences. | Updates are probably infrequent so often this flow can be a less than HIGH availability. In cases of high update (e.g., work zones, incidents), it could be HIGH. |
Security Characteristics | Value |
---|---|
Authenticable | True |
Encrypt | False |