Vehicle --> Other Vehicles:
vehicle maneuver coordination

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

Definitions

vehicle maneuver coordination (Information Flow): Statements of intent, permission and status of a lane change or merge operation by a connected vehicle

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:

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

This Triple has the following triple relationships:

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 Maneuver Coordination - LTE-V2X WSMP

Solution Description

This solution is used within Canada and the U.S.. It combines standards associated with US: SAE Maneuver Coordination with those for V-X: LTE-V2X WSMP. The US: SAE Maneuver Coordination standards include upper-layer standards required to enable maneuver coordination between equipped vehicles. 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
Mind the gap

SAE J2735
SAE J3186
Click gap icons for more info.

Mgmt

SAE J3161
3GPP 24.301
3GPP 36.331
Facilities
Mind the gap

SAE J2735
SAE J2945
Security
Mind the gap
TransNet

IEEE 1609.3
Access
Mind the gapMind the gap
TransNet TransNet

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

Access Access

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

ITS Application ITS Application

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

Mgmt Mgmt

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

Facility Facility

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

Security Security

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

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 Low
Basis Data contained within this flow is intended to alert other nearby vehicles to a desired or impending movement by the source vehicle. The data does include identifiers indicating the sending vehicle, which needs to be recognized and protected as appropriate. It may be impractical to encrypt this data to meet performance requirements, and in any event no more than one vehicle would be identified and only in the field environment, so mass collection of this information would be difficult. This flow is core to automated vehicle merge and lane change operations; flaws in the data could result in a crash, and so integrity should be ensured to the highest practical level. L4/5 ADS will operate more smoothly if this flow works, but as the vehicle fleet will include L0 vehicles for the foreseeable future, any ADS must use other methods to ensure safe operation anyway. May be MODERATE in ADS-dedicated facilities.


Security Characteristics Value
Authenticable True
Encrypt False