Standards List

The main function of a lane keeping assistance system (LKAS) is to support the driver in keeping the vehicle within the current lane. LKAS acquires information on the position of the vehicle within the lane and, when required, sends commands to actuators to influence the lateral movement of the vehicle, and in turn provides status information to the driver.
This document is intended to assess the complete performance of an LKAS fitted in a road vehicle:
— the capacity to keep the vehicle within the current lane during other situations not described in this test method (more complex scenarios, other weather conditions);
— the capacity to avoid undesired lane change.

This document specifies requirements, procedures and message formats for controlling and monitoring of test targets, used for testing of active safety functions and autonomous vehicles.
The document specifies functionality and messaging for monitoring and controlling of test objects by a control centre facilitating an interoperable test object environment. This document defines a communication protocol which allows for the control centre to safely execute tests using test objects from multiple vendors.
This document does not specify the internal architecture of the test object nor control centre.
This document does not specify how testing of the vehicles shall be performed.

This standard defines an approach for the categorization of the scenarios by providing tags that carry information about the scenarios.
This standard is applicable to SAE level 3 to SAE level 5 Automated Driving System (ADS).

This document provides guidance for a scenario-based safety evaluation framework for automated driving systems (ADSs). The framework elaborates a scenario-based safety evaluation process that is applied during product development. The guidance for the framework is intended to be applied to ADS defined in ISO/SAE PAS 22736 and to vehicle categories 1 and 2 according to Reference [10]. This scenario-based safety evaluation framework for ADS is applicable for limited access highways.
This document does not address safety-related issues involving misuse, human machine interface and cybersecurity.
This document does not address non-safety related issues involving comfort, energy efficiency or traffic flow efficiency.

This standard defines a methodology to evaluate the test scenarios and provides a procedure extending test scenarios to test cases for a given function in a traceable way based on the testability. This standard also defines necessary characteristics of a test case that include but not limited to test initialization, test stimulation, test steps, pass/fail-criteria and expected results etc. This standard describes evaluation methods and criteria that include but not limited to the relation between the test case, real world as well as databases/information-sources, e.g. frequency, criticality, complexity, and the relation between the test scenario and the tested function, e.g. coverage of ODD. The contents are intended to be applied to Level 3 and higher ADS defined in ISO/SAE 22736.

This document specifies the requirements for the hierarchical taxonomy for specifying operating conditions which enable the definition of an operational design domain (ODD) of an automated driving system (ADS). This document also specifies requirements for the definition format of an ODD using the taxonomy. The ODD comprises specific conditions (which include the static and dynamic attributes) within which an ADS is designed to function.
This document is mainly applicable to level 3 and level 4 ADS. An ODD for level 5 ADS is unlimited (i.e. operation is possible everywhere).
This document can be used by organizations taking part in developing safety cases for automated vehicles, in particular, for organizations conducting trials, testing and commercial deployment. This document can also be used by manufacturers of level 3/4 ADS to define the ADS’ operating capability. It may also be of interest to insurers, regulators, service providers, national, local and regional governments to enable them to understand possible ADS deployments and capabilities.
This document does not cover the basic test procedures for attributes of the ODD. It does not cover the monitoring requirements of the ODD attributes.

The document defines terms in the context of test scenarios for automated driving systems (ADS).
The document is applicable to ADS of Level 3 and above defined in ISO/SAE PAS 22736.

This Technical Report documents the findings of the 5GAA STiCAD cross-work item. The purpose of the STiCAD work item has been to determine, propose and evaluate possibilities for telecommunication operators, vendors, and any further identified stakeholders to provide what is necessary in order to enable the car OEM to better treat safety for systems that exist beyond a single vehicle. To achieve this, it was decided to find representative safety requirements for two selected use cases that cover the V2X scenarios of direct communication and network-based information delivery.

This document provides preliminary1 safety-relevant guidance for in-vehicle fallback test driver training and for on-road testing of vehicles being operated by prototype conditional, high, and full (Levels 3 to 5) ADS, as defined by SAE J3016. It does not include guidance for evaluating the performance of post-production ADS-equipped vehicles. Moreover, this guidance only addresses testing of ADS-operated vehicles as overseen by in-vehicle fallback test drivers (IFTD).
These guidelines do not address:
Remote driving, including remote fallback test driving of prototype ADS-operated test vehicles in driverless operation. (Note: The term “remote fallback test driver” is included as a defined term herein and is intended to be addressed in a future iteration of this document. However, at this time, too little is published or known about this type of testing to provide even preliminary guidance.)
Testing of driver support features (i.e., Levels 1 and 2), which rely on a human driver to perform part of the dynamic driving task (DDT) and to supervise the driving automation feature’s performance in real time. (Refer to SAE J3016.)
Closed-course testing.
Simulation testing (except for training purposes).
Component-level testing.
These guidelines also do not address prototype vehicle and IFTD performance data collection and retention. The collection of data invokes various legal and risk management considerations that users of this document should nevertheless bear in mind, such as:
Maintaining auditable procedures and documentation.
Adhering to applicable privacy laws and principles.
Ensuring adequate data collection and recording integrity to support post-crash forensic analysis.

The present document defines the functional requirements applicable to location systems, based on a summary of types of applications relying on location-related data provided by location systems.
The present document can be considered as the Stage 1 characterization of location systems according to the ITU/3GPP approach [i.2].
ETSI TS 103 246 parts 2 [i.14], 3 [i.15], 4 [i.16] and 5 [i.17] addresse integrated GNSS based location systems (GBLS) that combine Global Navigation Satellite Systems (GNSS), with other navigation technologies, as well as with telecommunication networks in order to deliver location-based services to users. As a consequence the present document is not applicable to GNSS only receivers.
ETSI TS 103 246 parts 2 [i.14], 3 [i.15], 4 [i.16] and 5 [i.17] propose a list of functional and performance requirements and related test procedures. For each performance requirement, different classes are defined allowing the benchmark of different GNSS Based Location Systems (GBLS) addressing the same applications. The requirements are intended to address the growing use of complex location systems required for the provision of location-based applications particularly for the mass-market (refer to ETSI TR 103 183 [i.1]).