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.
Rationale
Cooperative driving automation technologies enable mobility applications that are not achievable by individual automated driving system (ADS)-operated vehicles operating independently of each other. These technologies do so by sharing information that can be used to increase safety, efficiency, and reliability of the transportation system, and that may serve to accelerate the deployment of driving automation in on-road motor vehicles. Driving automation and connectivity present opportunities to deploy multiple cooperative automation strategies, but successful deployment of multiple cooperative automation strategies depends on coordination among diverse stakeholders. These include road operators, intelligent transportation system (ITS) technology providers, ADS and ADS-equipped vehicle manufacturers and suppliers, as well as ADS-dedicated vehicle (ADS-DV) fleet operators. These public and private sector stakeholders are preparing for and deploying different use cases at different temporal and spatial scales. These use cases may implement vehicle strategies, such as speed harmonization and/or transportation systems management and operations (TSMO) strategies, e.g., basic travel, traffic incident management, weather management, and workzone management data sharing. The United States Department of Transportation (U.S. DOT) highlighed the importance of cooperative situational awareness standards in its guideline document “Automated Vehicles 3.0: Preparing for the Future of Transportation.”
To develop these strategies, stakeholders are engaging each other and would benefit from a common language and organization of complex technology concepts. Standardizing terms and definitions for cooperative automation and its components serves several purposes, including:
1
Clarifying the types of information to be exchanged during cooperative automation operations.
2
Clarifying cooperation capabilities (status sharing, intent sharing, agreement seeking, prescriptive) that may be required to enable cooperative automation.
3
Answering questions of scope when it comes to developing laws, policies, regulations, and standards.
4
Providing a useful framework for cooperative automation standards, specifications, technical requirements, and open-source platform development.
5
Providing clarity and stability in communications on the topic of cooperative automation, as well as a useful short-hand that saves considerable time and effort.
6
Providing a foundation and reference for future standards.
7
Reflecting current industry practice and preserving prior art to the extent practicable.
Cooperative Driving Automation (CDA) technologies enable safety and mobility applications and outcomes that are not achievable by individual automated driving system (ADS)-operated vehicles operating independently of each other. CDA is enabled using machine-to-machine (M2M) communication technologies to foster cooperation between two or more traffic participants. Information shared between traffic participants is used to coordinate their respective movements, or change their state (e.g., a traffic signal), thereby reducing the risk of conflicts developing, and facilitating each participant’s mobility goals. This Committee includes subject matter experts from the On-Road Automated Driving (ORAD) Committee, the technical committees under the V2X Steering Committee, the Driving Automation Systems Committee (under the Safety and Human Factors Steering Committee) and other stakeholders (e.g., IOOs, OEMs, suppliers, government agencies, et al.).Building on J3216:2020 - Taxonomy and Definitions for Terms Related to Cooperative Driving Automation for On-Road Motor Vehicles, this Committee will oversee the development of additional supportive documents. The initial scope of work will be organized around the following focus areas: • Architecture and Interfaces for Interoperable CDA Use Case Testing • Cooperative Intersection Management • Cooperative Perception • Cooperative Traffic Management • Security Analysis for CDA Standards
* Redlines comparisons are available for those standards
listed in the Revision History that contain a radio button. A
redline comparison of the current version against a revision is
accomplished by selecting the radio button next to the standard and
then selecting 'compare'. At this time, Redline versions only exist
for some AMS standards. SAE will continue to add redline versioning
with ongoing updates to SAE MOBILUS.
View/Annotate
Content Loading, Please Wait
Document Preview
Content Loading, Please Wait
Document Comparison
Content Loading, Please Wait
Download
A list of downloadable items.
Product Code
Document Title
File Type
Download
J3216_202005
Taxonomy and Definitions for Terms Related to Cooperative Driving Automation for On-Road Motor Vehicles
Export Metadata
This modal will allow the user to download citation information or export specific fields of data into one of three file formats: Excel, comma-separated values, or text.
You are currently not logged into your Dashboard account, which is required for annotating.
Please select Login to login or register for the Dashboard. Select Continue to view the content without the ability to annotate.
Redline Warning
You are currently not logged into your Dashboard account, which is required for annotating.
Please select Login to login or register for the Dashboard. Select Continue to view the content without the ability to annotate.
Data Set Warning
Taxonomy and Definitions for Terms Related to Cooperative Driving Automation for On-Road Motor Vehicles
SAE Journal Subscriptions are available in a variety of options, which include electronic, electronic with back file, and archive. For detailed information and options, please complete the following:
Content Request
Check My Access!
You may already have access to the Ground Vehicle Standard, Taxonomy and Definitions for Terms Related to Cooperative Driving Automation for On-Road Motor Vehicles
Subscription Access
If you have Subscription Access with a username and password, please login below.
Institutional Login
If you have Institutional Access to SAE MOBILUS, using a predetermined organizational login utilizing single-sign-on (Shibboleth), please login below. To request institutional access to SAE MOBILUS, please complete the institutional subscription information form.
Purchase
If you do not have access to SAE MOBILUS via username/password or institutional access, you can still purchase the Ground Vehicle Standard, Taxonomy and Definitions for Terms Related to Cooperative Driving Automation for On-Road Motor Vehicles.
Search Tips: Search Operators:AND, OR, NOT; Wild Cards; Using Quotes
SAE MOBILUS® Search Tips
Please note: All terms not contained within quotes, will be evaluated using the OR operator. This means that your search results will contain all results that contain ANY of the entered terms.
AND, OR, NOT
SAE MOBILUS supports the use of the AND, OR and NOT BOOLEAN operators ONLY function with the Advanced Search.
Wild Cards
Using the asterisk, ( * ) allows you to search for a partial word. For example, entering a keyword search of aero* will search for any word beginning with aero.
Using the question mark, ( ? ) allows you to search for a word with a single character wildcard. For example, searching for t?re would match both tire and tyre
Using Quotes
Words in double quotes " " are treated as a phrase. Conducting a search for "heat model" will return all results in which the exact phrase "heat model" is found, while "heat modeling" would NOT be included.
A term combined with a phrase will be joined with an OR operator.
Searching for Standards
When searching for a standard please use the entire Document Number assigned, which includes the abbreviation. A space can be used, or omitted between the abbreviation and number.