METR Distribution Center --> Vehicle:
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).

Vehicle (Destination Physical Object): This 'Vehicle' physical object is used to model core capabilities that are common to more than one type of Vehicle. It provides the vehicle-based general sensory, processing, storage, and communications functions that support efficient, safe, and convenient travel. Many of these capabilities (e.g., see the Vehicle Safety service packages) apply to all vehicle types including personal vehicles, commercial vehicles, emergency vehicles, transit vehicles, and maintenance vehicles. From this perspective, the Vehicle includes the common interfaces and functions that apply to all motorized vehicles. The radio(s) supporting V2V and V2I communications are a key component of the Vehicle. Both one-way and two-way communications options support a spectrum of information services from basic broadcast to advanced personalized information services. Advanced sensors, processors, enhanced driver interfaces, and actuators complement the driver information services so that, in addition to making informed mode and route selections, the driver travels these routes in a safer and more consistent manner. This physical object supports all six levels of driving automation as defined in SAE J3016. Initial collision avoidance functions provide 'vigilant co-pilot' driver warning capabilities. More advanced functions assume limited control of the vehicle to maintain lane position and safe headways. In the most advanced implementations, this Physical Object supports full automation of all aspects of the driving task, aided by communications with other vehicles in the vicinity and in coordination with supporting infrastructure subsystems.

Included In

This Triple is in the following Service Packages:

• VS17: Management of Electronic Traffic Regulations (METR)

This triple is associated with the following Functional Objects:

• MDC METR Dissemination
• Vehicle METR Management
• Vehicle METR Reception

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

• None

This Triple has the following triple relationships:

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

(None-Data) - OASIS MQTT over Wireless

Solution Description

ITS Application Entity Development needed			Click gap icons for more info.
Mgmt OASIS MQTT DMP	Facilities Development needed OASIS MQTT	Security IP Security Alternatives OASIS MQTT
	TransNet IP Alternatives Internet Transport Alternatives
	Access Wireless Internet Alternatives (NA)

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