Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
SAE J3164: An Ontology and Lexicon for ADS Behaviors and Maneuvers in Routine Operations
As automated driving systems (ADS) continue to evolve, the need for a common language to describe their behaviors and maneuvers becomes critical. SAE J3164-2023 addresses this need by providing a high-level ontology and lexicon for ADS-operated vehicle behaviors and maneuvers during routine/normal operation, as defined in SAE J3016. This information report aims to standardize terminology, support validation and verification methods, and facilitate clear communication across engineering, legal, and public domains.
Why Standardized Terminology Matters for ADS Development
Inconsistent use of terms like ‘behavior’, ‘maneuver’, and ‘scenario’ can lead to confusion in specifications, regulatory discussions, and public discourse. SAE J3164 provides a consistent framework that clarifies expected driving behaviors and the context in which they are appropriate. Its guiding principles emphasize descriptive and informative content, functional definitions, consistency with industry practice, and cross-disciplinary utility. The document does not impose requirements but offers a foundation for building technical requirements and policies.
🛠️ Engineering Design Insight: The ontology introduces a three-level hierarchy of behaviors (strategic, tactical, operational) based on Michon’s driver behavior model. This decomposition helps engineers align ADS development with human driving models and structure validation scenarios at appropriate levels of abstraction.
Understanding the Framework: Behavior Hierarchy, Maneuver Lexicon, and Scenario Abstraction
J3164 defines a taxonomy where behaviors are high-level competencies, maneuvers are specific driving actions, and scenarios provide the operational context. The document adopts a scenario abstraction ontology (functional, logical, and concrete) and a maneuver lexicon based on lane structure, including elemental and composite maneuvers.
| Abstraction Level | Description | Example |
|---|---|---|
| Functional | Brusque, qualitative description | Vehicle changes lane |
| Logical | Parametric description with ranges | Lane change with speed 50-70 km/h, distance 10-20 m |
| Concrete | Specific, numeric values | Lane change at 60 km/h on a 3.5m lane with 15m gap |
Maneuvers are categorized based on lane structure, providing an unambiguous description of vehicle motion. Elemental maneuvers include lane keeping, lane changing, and turning; composite maneuvers combine multiple actions, such as a passing maneuver. This hierarchy supports systematic scenario generation and verification.
⚠️ Common Mistake: Conflating routine/normal maneuvers with emergency safety-critical actions. J3164 explicitly focuses on routine performance of the complete Dynamic Driving Task (DDT) and does not cover emergency maneuvers, which require separate analysis.
Practical Applications: Validation, Specifications, and Cross-Disciplinary Communication
The ontology and lexicon in J3164 are designed to reduce inconsistency and support answering questions of scope for laws, policies, and regulations. By providing a common language, engineers can develop technical requirements, validation scenarios, and test cases more systematically. The framework also aids in clarifying the relationship between Operational Design Domain (ODD) elements and Object and Event Detection and Response (OEDR) requirements.
For instance, when specifying an ADS’s behavioral competencies, developers can refer to the ontology to ensure coverage of all necessary maneuvers under relevant ODD conditions. This promotes consistency across design, testing, and deployment phases.
FAQs:
- How does SAE J3164 relate to SAE J3016? J3164 builds on J3016 by providing a detailed ontology for behaviors and maneuvers specifically for ADS levels 3-5 during routine/normal operation.
- What maneuvers are covered? The standard focuses on routine on-road maneuvers such as lane keeping, lane changing, turning, and passing, but excludes emergency or safety-critical maneuvers.
- Can this ontology be used for Level 2 systems? While many concepts are relevant, J3164 is primarily aimed at ADS features that perform the complete DDT without driver supervision (levels 3-5).
- How does the ontology support validation? By providing a consistent lexicon and hierarchy, it enables systematic scenario generation from functional to concrete levels, helping engineers design comprehensive test suites.
