SAE J3216_202107

This document describes machine-to-machine (M2M) communication to enable cooperation between two or more participating entities or communication devices possessed or controlled by those entities.

This document describes machine-to-machine (M2M) communication to enable cooperation between two or more participating entities or communication devices possessed or controlled by those entities. The cooperation supports or enables performance of the dynamic driving task (DDT) for a subject vehicle with driving automation feature(s) engaged. Other participants may include other vehicles with driving automation feature(s) engaged, shared road users (e.g., drivers of manually operated vehicles or pedestrians or cyclists carrying personal devices), or road operators (e.g., those who maintain or operate traffic signals or workzones).Cooperative driving automation (CDA) aims to improve the safety and flow of traffic and/or facilitate road operations by supporting the movement of multiple vehicles in proximity to one another. This is accomplished, for example, by sharing information that can be used to influence (directly or indirectly) DDT performance by one or more nearby road users. Vehicles and infrastructure elements engaged in cooperative automation may share information, such as state (e.g., vehicle position, signal phase), intent (e.g., planned vehicle trajectory, signal timing), or seek agreement on a plan (e.g., coordinated merge). Cooperation among multiple participants and perspectives in traffic can improve safety, mobility, situational awareness, and operations. However, nothing in this document is intended to suggest that driving automation requires such cooperation in order to be performed safely.Cooperative strategies may be enabled by the sharing of information in a way that meets the needs of a given application. The needs may be expressed in terms of performance characteristics, such as latency, transmission mode (e.g., one-way, two-way), range, privacy and security, and information content and quality. There are several potential technologies for communicating information between the subject vehicle and other participants.This document focuses on application-oriented functionality and does not imply the need for or require any specific functionality associated with communications protocols or the open systems interconnection model layers in a protocol stack. This document addresses the operational and tactical timescales of dynamic driving on ADS-operated vehicles, and excludes strategic functions such as trip scheduling and selection of destinations and waypoints. This information report is intended to facilitate communication and awareness for the design and anticipated development and validation of cooperative driving automation.