Other Vehicles --> Vehicle:
vehicle platoon coordination

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

Definition
Included In
Communication Solutions
Characteristics
Security

Definitions

vehicle platoon coordination (Information Flow): Coordination of control commands between leader and follower vehicles allowing vehicles to join, coordinate with, and separate from platoons of cooperative vehicles. This flow shares platoon size, location, and performance parameters (e.g., platoon speed and spacing) between platooned vehicles.

Other Vehicles (Source 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.

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: Automated Vehicle Operations

This triple is associated with the following Functional Objects:

Vehicle Platoon Operations

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

fov-vehicle_platoon_information

This Triple has the following triple relationships:

None

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

(None-Data) - LTE-V2X WSMP

Solution Description

This solution is used within Canada and the U.S.. It combines standards associated with (None-Data) with those for V-X: LTE-V2X WSMP. The (None-Data) standards include an unspecified set of standards at the upper layers. The V-X: LTE-V2X WSMP standards include lower-layer standards that support connectionless, near constant, ultra-low latency vehicle-to-any communications using the WAVE Short Messaging Protocol (WSMP) over 3GPP C-V2X in the 5.9GHz spectrum.

ITS Application Entity Development needed			Click gap icons for more info.
Mgmt SAE J3161 3GPP 24.301 3GPP 36.331	Facilities Development needed	Security Bundle: IEEE 1609.2
	TransNet IEEE 1609.3
	Access Bundle: 3GPP LTE-V2X

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	Now
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	Includes the identity of the lead vehicle but no PII. Intended for vehicles to coordinate tightly, and with no previous relationship so likely open to other vehicles monitoring.	Platooning coordination data must be correct or potentially severe consequences can result, particularly if data relevant to high speed operations is corrupted.	Platooning will not fully function without this flow; the worst case is that vehicles drop from the platoon however; lack of this flow is unlikely to generate a severe incident on its own.

Security Characteristics	Value
Authenticable	True
Encrypt	False

Other Vehicles --> Vehicle:vehicle platoon coordination