ISO/TS 23792-1:2023
Intelligent transport systems — Motorway chauffeur systems (MCS) — Part 1: Framework and general requirements
Motorway chauffeur systems (MCS) perform Level 3 automated driving on limited access motorways with the presence of a fallback-ready user (FRU). MCS can be implemented in various forms capable of responding to different driving scenarios. This document describes a framework of MCS including system characteristics, system states/transition conditions and system functions.
MCS are equipped with a basic set of functionalities to perform in-lane operation and can also be equipped with additional functionalities such as lane changing.
This document specifies requirements of the basic set of functionalities and test procedures to verify these requirements. The requirements include vehicle operation to perform the entire dynamic driving task (DDT) within the current lane of travel, to issue a request to intervene (RTI) before disengaging, and to extend operation and temporarily continue to perform the DDT after issuing an RTI.
This document describes one specific form of system engagement. Other forms are possible. These other system engagement forms, especially those provided in combination with other driving automation system features, are not within the scope of this document.
Requirements and test procedures for the additional functionalities are provided in other parts of the ISO 23792 series.
Means related to setting a destination and selecting a route to reach the destination are not within the scope of this document. This document applies to MCS installed in light vehicles.
| Get this standard | Prices exclude GST | |
|---|---|---|
| PDF ( Single user document) |
$301.00 NZD
|
|
| HardCopy |
$346.00 NZD
|
|
| Networkable PDF |
Price varies
|
Foreword
Introduction
1 Scope
2 Normative references
3 Terms and definitions
4 Abbreviated terms
5 Characteristics of MCS
5.1 General
5.2 Operational design domain
5.2.1 General
5.2.2 Roadway physical characteristics
5.2.3 Traffic in the surrounding environment
5.2.4 Abnormalities in roadway operational condition
5.2.5 Ambient environmental conditions
5.3 System functionalities
5.3.1 General
5.3.2 Basic functionalities to realize in-lane operation
5.3.3 Lane changing functionalities
5.4 System limitations
5.5 Providing information to the user
6 Operational requirements
6.1 Operating conditions
6.1.1 General
6.1.2 Engagement conditions
6.1.3 Disengagement triggering conditions
6.1.4 Direct disengagement conditions
6.2 State transition
6.2.1 General
6.2.2 Off state
6.2.3 Standby state
6.2.4 Normal state
6.2.5 Requesting fallback state
6.3 System functions
6.3.1 General
6.3.2 Object and event detection and response (OEDR)
6.3.3 Vehicle motion control (VMC)
6.3.4 Generation of request to intervene (RTI)
6.3.5 Status indication
6.3.6 User control interface
6.3.7 FRU input detection
6.3.8 MCS monitoring the FRU
6.3.9 Subject vehicle condition monitor
6.3.10 MCS condition monitor
6.3.11 Localization
6.3.12 External warning generation
6.3.13 Function required for route following functionalities
6.3.14 Related functions
6.4 Requirements for continuing operation after detecting disengagement-triggering conditions
6.4.1 General
6.4.2 Classification of adverse situations
6.4.3 Responses to adverse situations
7 Minimum performance requirements of the DDT
7.1 General
7.2 Operating speed range
7.3 Normal operation
7.3.1 Sustained longitudinal vehicle motion control
7.3.2 Sustained lateral vehicle motion control
7.3.3 Crash avoidance
7.4 Performance-impaired operation
7.5 MCS reaction to unresponsive FRU
8 Test procedures
8.1 General
8.1.1 Purpose
8.1.2 Driving environment
8.1.3 System settings and test driver roles
8.1.4 Common test pass criteria
8.1.5 Confirmation of the HMI design
8.1.6 Success rate and number of trials
8.1.7 List of test scenarios
8.1.8 Test sites
8.2 Scenario 1: MCS reaction to unresponsive FRU
8.2.1 Test scenario
8.2.2 Pass criteria
8.3 Scenario 2: Direct disengagement by steering input
8.3.1 Test scenario
8.3.2 Pass criteria
8.4 Scenario 3: Continued operation after brake intervention
8.4.1 Test scenario
8.4.2 Pass criteria
8.5 Scenario 4: Forward vehicle braking hard
8.5.1 Test scenario
8.5.2 Pass criteria
8.6 Scenario 5: Aggressive cut-in from the adjacent lane
8.6.1 Test scenario
8.6.2 Pass criteria
8.7 Scenario 6: Obstacle in lane
8.7.1 Test scenario
8.7.2 Pass criteria
8.8 Scenario 8: Approaching geographical ODD boundary
8.8.1 Test scenario
8.8.2 Pass criteria
8.9 Scenario 9: Engagement restricted outside ODD
8.9.1 Test scenario
8.9.2 Pass criteria
Bibliography
Keep me up-to-date
Sign up to receive updates when there are changes to this standard
Related Information
Similar Standards
-
23/30382233DC
BS EN 9300-00. Aerospace series. LOTAR -LOng Term Archiving and Retrieval of digital technical product documentation such as 3D, CAD and PDM data, Part 007. Terms and references
-
AS/NZS 2890.1:2004
Parking facilities - Off-street car parking
-
AS/NZS 2890.1:2004 A1
Parking facilities - Off-street car parking: Amendment 1
-
AS/NZS 2890.6:2009
Parking facilities - Off-street parking for people with disabilities
Foreword
Introduction
1 Scope
2 Normative references
3 Terms and definitions
4 Abbreviated terms
5 Characteristics of MCS
5.1 General
5.2 Operational design domain
5.2.1 General
5.2.2 Roadway physical characteristics
5.2.3 Traffic in the surrounding environment
5.2.4 Abnormalities in roadway operational condition
5.2.5 Ambient environmental conditions
5.3 System functionalities
5.3.1 General
5.3.2 Basic functionalities to realize in-lane operation
5.3.3 Lane changing functionalities
5.4 System limitations
5.5 Providing information to the user
6 Operational requirements
6.1 Operating conditions
6.1.1 General
6.1.2 Engagement conditions
6.1.3 Disengagement triggering conditions
6.1.4 Direct disengagement conditions
6.2 State transition
6.2.1 General
6.2.2 Off state
6.2.3 Standby state
6.2.4 Normal state
6.2.5 Requesting fallback state
6.3 System functions
6.3.1 General
6.3.2 Object and event detection and response (OEDR)
6.3.3 Vehicle motion control (VMC)
6.3.4 Generation of request to intervene (RTI)
6.3.5 Status indication
6.3.6 User control interface
6.3.7 FRU input detection
6.3.8 MCS monitoring the FRU
6.3.9 Subject vehicle condition monitor
6.3.10 MCS condition monitor
6.3.11 Localization
6.3.12 External warning generation
6.3.13 Function required for route following functionalities
6.3.14 Related functions
6.4 Requirements for continuing operation after detecting disengagement-triggering conditions
6.4.1 General
6.4.2 Classification of adverse situations
6.4.3 Responses to adverse situations
7 Minimum performance requirements of the DDT
7.1 General
7.2 Operating speed range
7.3 Normal operation
7.3.1 Sustained longitudinal vehicle motion control
7.3.2 Sustained lateral vehicle motion control
7.3.3 Crash avoidance
7.4 Performance-impaired operation
7.5 MCS reaction to unresponsive FRU
8 Test procedures
8.1 General
8.1.1 Purpose
8.1.2 Driving environment
8.1.3 System settings and test driver roles
8.1.4 Common test pass criteria
8.1.5 Confirmation of the HMI design
8.1.6 Success rate and number of trials
8.1.7 List of test scenarios
8.1.8 Test sites
8.2 Scenario 1: MCS reaction to unresponsive FRU
8.2.1 Test scenario
8.2.2 Pass criteria
8.3 Scenario 2: Direct disengagement by steering input
8.3.1 Test scenario
8.3.2 Pass criteria
8.4 Scenario 3: Continued operation after brake intervention
8.4.1 Test scenario
8.4.2 Pass criteria
8.5 Scenario 4: Forward vehicle braking hard
8.5.1 Test scenario
8.5.2 Pass criteria
8.6 Scenario 5: Aggressive cut-in from the adjacent lane
8.6.1 Test scenario
8.6.2 Pass criteria
8.7 Scenario 6: Obstacle in lane
8.7.1 Test scenario
8.7.2 Pass criteria
8.8 Scenario 8: Approaching geographical ODD boundary
8.8.1 Test scenario
8.8.2 Pass criteria
8.9 Scenario 9: Engagement restricted outside ODD
8.9.1 Test scenario
8.9.2 Pass criteria
Bibliography