Vehicle --> Other Vehicles:
vehicle cluster coordination

This triple is bi-directional. See also Other Vehicles --> Vehicle: vehicle cluster coordination

Definition
Included In
Communication Solutions
Characteristics
Security

Definitions

vehicle cluster coordination (Information Flow): Coordination between CACC-equipped vehicles that enable formation and management of strings of adjacent equipped vehicles that coordinate speed management across the string. This flow includes coordination between CACC-equipped vehicles that enable adjacent vehicles in the same lane to identify each other and couple. Depending on the CACC implementation, this flow also supports identification of the lead vehicle in the string, operating performance parameters for the string, destination information so that drivers can join strings that share their destination, and coordination so that strings of vehicles are ordered based on the individual weight and performance profile of each participating vehicle. This flow also supports dissolution of CACC vehicle strings as vehicles depart from the string.

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.

Other Vehicles (Destination Physical Object): 'Other Vehicle OBEs' represents other connected vehicles that are communicating with the host vehicle. This includes all connected motorized vehicles including passenger cars, trucks, and motorcycles and specialty vehicles (e.g., maintenance vehicles, transit vehicles) that also include the basic 'Vehicle OBE' functionality that supports V2V communications. This object provides a source and destination for information transfers between connected vehicles. The host vehicle on-board equipment, represented by the Vehicle OBE physical object, sends information to, and receives information from the Other Vehicle OBEs to model all connected vehicle V2V communications in ARC-IT.

Included In

This Triple is in the following Service Packages:

This triple is associated with the following Functional Objects:

Vehicle Cooperative Cruise Control

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

tov-platoon_data_to_other_vehicle

This Triple has the following triple relationships:

Relationship	Source	Destination	Flow
Request-Response	Other Vehicles	Vehicle	vehicle cluster coordination

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

US: SAE Platooning - WAVE WSMP

Solution Description

This solution is used within Canada and the U.S.. It combines standards associated with US: SAE Platooning with those for V-X: WAVE WSMP. The US: SAE Platooning standards include upper-layer standards required to manage platooning and cooperative adaptive cruise control. The V-X: WAVE WSMP standards include lower-layer standards that support connectionless, near constant, ultra-low latency vehicle-to-any communications within ~300m using the WAVE Short Messaging Protocol (WSMP) over IEEE WAVE in the 5.9GHz spectrum. The broadcast mode is interoperable with M5 FNTP.

ITS Application Entity SAE J2735 SAE J2945/6			Click gap icons for more info.
Mgmt Addressed Elsewhere	Facilities SAE J2735 SAE J2945	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

Characteristic	Value
Time Context	Recent
Spatial Context	Adjacent
Acknowledgement	False
Cardinality	Broadcast
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	This data is intentionally transmitted to nearby roadside equipment and vehicles operating in a vehicle cluster.	Vehicle cluster coordination is critical to the performance of a group of vehicles in a vehicle cluster scenario. Incorrect data here is unlikely to trigger a severe accident scenario, but could have negative consequences on the performance of the cluster. Considered HIGH to be safe.	Vehicle clustering scenarios cannot function without this flow. Worst case is non-initiation of the cluster however, which while significant to mobility does not have a direct severe consequence.

Security Characteristics	Value
Authenticable	True
Encrypt	False

Vehicle --> Other Vehicles:vehicle cluster coordination