Vehicle --> Connected Vehicle Roadside Equipment:
automated vehicle control status

Definitions

automated vehicle control status (Information Flow): Data provided by a connected vehicle identifying it's current mode and operational status and information provided to support check-in/checkout of the lane and coordinated maneuvers while on the automated facility.

Vehicle (Source 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.

Connected Vehicle Roadside Equipment (Destination Physical Object): 'Connected Vehicle Roadside Equipment' (CV RSE) represents the Connected Vehicle roadside devices (i.e., Roadside Units (RSUs)) equipped with short range wireless (SRW) communications technology, as well as any other supporting equipment that leverage the RSU and are not described by other objects (e.g., a local roadside processor). CVRSE are used to send messages to, and receive messages from, nearby vehicles and personal devices equipped with compatible communications technology. Communications with adjacent field equipment and back office centers that monitor and control the RSE are also supported. This device operates from a fixed position and may be permanently deployed or a portable device that is located temporarily in the vicinity of a traffic incident, road construction, or a special event. It includes a processor, data storage, and communications capabilities that support secure communications with passing vehicles, other field equipment, and centers.

Included In

This Triple is in the following Service Packages:

• VS17: Automated Vehicle Operations

This triple is associated with the following Functional Objects:

• RSE Automated Vehicle Operations
• Vehicle Platoon Operations

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

• avo_route_data
• avo_vehicle_condition

This Triple has the following triple relationships:

Communication Solutions

• (None-Data) - LTE-V2X WSMP (49)
• (None-Data) - BTP/GeoNetworking/G5 (58)
• (None-Data) - WAVE WSMP (62)

Selected Solution

(None-Data) - WAVE WSMP

Solution Description

ITS Application Entity Development needed			Click gap icons for more info.
Mgmt Addressed Elsewhere	Facilities Development needed	Security Bundle: IEEE 1609.2
	TransNet IEEE 1609.3
	Access Bundle: WAVE - Subnet

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