Connected Vehicle Roadside Equipment --> Vehicle:
vehicle cluster coordination
This triple is bi-directional. See also
Vehicle --> Connected Vehicle Roadside Equipment: vehicle cluster coordination
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.
Connected Vehicle Roadside Equipment (Source Physical Object): 'Connected Vehicle Roadside Equipment' (CV RSE) represents the Connected Vehicle roadside devices that are used to send messages to, and receive messages from, nearby vehicles using Dedicated Short Range Communications (DSRC) or other alternative wireless communications technologies. 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.
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:
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
- US: SAE Platooning - LTE-V2X WSMP (21)
- US: SAE Platooning - WAVE WSMP (23)
- (None-Data) - BTP/GeoNetworking/G5 (42)
Selected Solution
Solution Description
ITS Application Entity
Development needed |
Click gap icons for more info.
|
||
Mgmt
ETSI 302 890-1 Addressed Elsewhere |
Facilities
Development needed |
Security
|
|
TransNet
|
|||
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 | 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 may function without this flow, but will probably not be as efficient without benefit of roadside inputs. |
Security Characteristics | Value |
---|---|
Authenticable | True |
Encrypt | False |