Search Results

The scope of this document is the concept of operations including reference system architecture, the user needs, the system functional and performance requirements, the messages, the corresponding data frames and elements, and other related functionality to enable V2X-based fee collection and other financial transactions.

This SAE Standard describes the concept of operation, use cases, and message flows to create a Sensor Sharing Service (SSS). This service enable RSUs and V2X1 vehicles to share information about their localized driving environment. This work defines message structure, V2X entity requirements, and information elements to describe detected objects to facilitate sensor sharing.

This SAE Standard is a truth-in-labeling standard for map databases.

This series of SAE Recommended Practices was developed to provide an open architecture system for on-board electronic systems. It is the intention of these documents to allow electronic devices to communicate with each other by providing a standard architecture. This particular document describes the Network Interface and Cabling which defines the requirements needed for communicating between devices that are on different segments of the SAE J2496 Transport Area Network. While these recommended practices may be used in retrofitting older vehicles, the primary intent is for implementation in new bus procurements.

This SAE Recommended Practice provides a taxonomy of terms related to local and regional on-demand and shared mobility services (including ground, aviation, and maritime) and their enabling technologies. Functional definitions for shared modes (both fleet sharing and ride services), services, business models, and mobility applications are defined in this SAE Recommended Practice. This SAE Recommended Practice also provides a taxonomy of related terms and definitions. Though public transport is part of shared mobility, it is not included in this SAE Recommended Practice because its definition is well-established and documented. This document does not provide specifications or otherwise impose requirements on on-demand and shared mobility.

This Recommended Practice provides a taxonomy and definitions for terms related to shared mobility and enabling technologies. Included are functional definitions for shared modes (e.g., carsharing, bikesharing, ridesourcing, etc.). Public transit services and other incumbent services—such as car rentals, shuttles, taxis, paratransit, ridesharing (carpooling/vanpooling), and pedicabs—are also included in the ecosystem of shared mobility services. This Recommended Practice also provides a taxonomy of related terms and definitions (e.g., station-based roundtrip, free-floating one-way, etc.). This Recommended Practice does not provide specifications or otherwise impose requirements on shared mobility.

This Recommended Practice provides a taxonomy and definitions for terms related to shared mobility and enabling technologies. Included are functional definitions for shared modes (e.g., carsharing, bikesharing, ridesourcing, etc.). Public transit services and other incumbent services—such as car rentals, shuttles, taxis, paratransit, ridesharing (carpooling/vanpooling), and pedicabs—are also included in the ecosystem of shared mobility services. This Recommended Practice also provides a taxonomy of related terms and definitions (e.g., station-based roundtrip, free-floating one-way, etc.). This Recommended Practice does not provide specifications or otherwise impose requirements on shared mobility.

This Recommended Practice provides a taxonomy and definitions for terms related to shared mobility and enabling technologies. Included are functional definitions for shared modes (e.g., carsharing, bikesharing, ridesourcing, etc.). Public transit services and other incumbent services—such as car rentals, shuttles, taxis, paratransit, ridesharing (carpooling/vanpooling), and pedicabs—are also included in the ecosystem of shared mobility services. This Recommended Practice also provides a taxonomy of related terms and definitions (e.g., station-based roundtrip, free-floating one-way, etc.). This Recommended Practice does not provide specifications or otherwise impose requirements on shared mobility.

This document describes [motor] vehicle driving automation systems that perform part or all of the dynamic driving task (DDT) on a sustained basis. It provides a taxonomy with detailed definitions for six levels of driving automation, ranging from no driving automation (Level 0) to full driving automation (Level 5), in the context of [motor] vehicles (hereafter also referred to as “vehicle” or “vehicles”) and their operation on roadways: Level 0: No Driving Automation Level 1: Driver Assistance Level 2: Partial Driving Automation Level 3: Conditional Driving Automation Level 4: High Driving Automation Level 5: Full Driving Automation These level definitions, along with additional supporting terms and definitions provided herein, can be used to describe the full range of driving automation features equipped on [motor] vehicles in a functionally consistent and coherent manner.

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.

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.

This SAE Information Report classifies and defines a harmonized set of safety principles intended to be considered by ADS and ADS-equipped vehicle development stakeholders. The set of safety principles herein is based on the collection and analysis of existing information from multiple entities, reflecting the content and spirit of their efforts, including: SAE ITC AVSC Best Practices CAMP Automated Vehicle Research for Enhanced Safety - Final Report RAND Report - Measuring Automated Vehicle Safety: Forging a Framework U.S. DOT: Automated Driving Systems 2.0 - A Vision for Safety Safety First for Automated Driving (SaFAD) UNECE WP29 amendment proposal UNECE/TRANS/WP.29/GRVA/2019/13 On a Formal Model of Safe and Scalable Self-Driving Cars (Intel RSS model) SAE J3018 This SAE Information Report provides guidance for the consideration and application of the safety principles for the development and deployment of ADS and ADS-equipped vehicles.

This SAE Standard is a truth-in-labeling standard for map databases.

This SAE Recommended Practice provides a test procedure for determining passenger car tire revolutions per mile. It is intended to supplement SAE J678.

This SAE Standard outlines the US standard for sending Advanced Traveler Information Services (ATIS) messages over various Bandwidth Reduced Media (BRM). It specifies the “over the air” format and method for such data messages at a bit level. The methodology allows a cooperative sharing of the media’s total bandwidth with other non-ATIS data services. It allows for further expansion to other ATIS messages such as transit schedules and weather use. It uses a common directory of messages to divide out those messages which are the subject of this specification from others. It is built upon the concept of “waveform neutrality” in that it can be hosted by a wide variety of media often found in the delivery of wireless data services (although it is also useful for wire line applications). This message set is incorporated into each medium (“host medium”) by a formatting process specific to each media. A graphical overview ofthis process is shown in Figure 1.

This SAE Recommended Practice provides an orderly series for designating the thickness of unocated and coated hot-rolled and cold-rolled sheet and strip. This document also provides methods for specifying thickness tolerances.

This SAE Information Report describes requirements gathering workshops for Public Sector use of ITS Referencing Datums.

This SAE Standard applies to spark plug installation sockets of the long length type which are to be used for installing spark plugs of the most commonly used sizes for the North American market.

This SAE Information Report provides test procedures, requirements, and guidelines for clearance, side marker, and identification lamps.

SAE is developing a number of standards, including the SAE J2945/x and SAE J3161/x series, that specify a set of applications using message sets from the SAE J2735 data dictionary. (“Application” is used here to mean “a collection of activities including interactions between different entities in the service of a collection of related goals and associated with a given IEEE Provider Service Identifier (PSID)”). Authenticity and integrity of the communications for these applications are ensured using digital signatures and IEEE 1609.2 digital certificates, which also indicate the permissions of the senders using Provider Service Identifiers (PSIDs) and Service Specific Permissions (SSPs). The PSID is a globally unique identifier associated with an application specification that unambiguously describes how to build interoperable instances of that application.