Vehicle --> Other Vehicles:
vehicle control event
This triple is bi-directional. See also
Other Vehicles --> Vehicle: vehicle control event
Definitions
vehicle control event (Information Flow): Notification that the vehicle has performed an emergency maneuver or action that could impact the safety of surrounding vehicles. This includes hard braking and activation of traction/stability control systems or other actions that warrant immediate notification of surrounding vehicles. The information flow conveys the current vehicle location, path, and current control actions. This may also include the list of maneuvers includes lane changes/departures and overtaking/passing maneuvers.
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:
None |
Communication Solutions
- EU: CA Service - BTP/GeoNetworking/G5 (16)
- EU: DEN Service - BTP/GeoNetworking/G5 (16)
- US: SAE LTE-V2X BSM - LTE-V2X WSMP (16)
- US: SAE Basic Safety Messages - WAVE WSMP (18)
Selected Solution
Solution Description
ITS Application Entity
SAE J2735 SAE J3161/1 |
Click gap icons for more info.
|
||
Mgmt
SAE J3161 3GPP 24.301 3GPP 36.331 |
Facilities
SAE J2735 |
Security
|
|
TransNet
IEEE 1609.3 |
|||
Access
|
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 | Moderate | Moderate | |
Basis | This data is intentionally transmitted to everyone via a broadcast. It can also be determined via other visual indicators. | BSM info needs to be accurate and should not be tampered with, suggesting HIGH. From NYC: Integrity would need to be high if there were no mitigations against bad data in incoming BSMs. In fact, there are two mitigations: plausibility checking, and misbehavior reporting plus revocation. Taking these into account we believe, with [18], that the security requirements are met by requiring an integrity level of MODERATE on these information flows. RES: Sided with NYC due to mitigation documentation. | BSM must be broadcast regularly to make data available for other vehicle OBEs, but cannot guarantee wireless communication |
Security Characteristics | Value |
---|---|
Authenticable | True |
Encrypt | False |