SAE Liaison Report ITU CITS e-meeting (28 October 2019) · 10/28/2019 · SAE Liaison Report . ITU...

Keith Wilson, Program Manager, SAE International

SAE Liaison Report ITU CITS e-meeting (28 October 2019)

2Copyright © SAE International. Further use or distribution is not permitted without permission from SAE International.

SAE Standards in Advanced Technology Focus Areas

Wireless Charging

Vehicle Electronics Cyber Security

Driving Automation Systems

Driver-Vehicle Interface

Shared MobilityActive Safety Functional Safety

Mobility for Elderly and Persons with Disabilities

EV/Hybrid/FC Vehicle& Battery

V2X CommunicationsIntelligent Transport

Systems

Electronics System Reliability

Cooperative Driving Automation



SAE ADAS Standards Activities


SAE ADAS Standards ActivitiesActive Safety

Systems Standards

Committee

Active Safety Test

Target Validation

Correlation Task Force

Active Safety

Bicycle Test Targets Task

Force

Vehicle Lane Deviation Warning

Task Force

Harware-in-the-Loop

Task Force

ActiveSafety Terms

and Definitions Task Force


ADAS Standards Focus

Standards focus has shifted from Passive Safety to collision mitigation:

Electronic Stability Control Traction Control Adaptive Cruise Control Forward Collision Warning Rear Collision Warning Lane Departure Warning Crash Imminent Braking Blind Spot Detection Adaptive Headlamps


ADAS StandardsJ3063™ Active Safety System Terms & Definitions

J3087™ Automatic Emergency Braking (AEB) System Performance Testing

J3088™ Active Safety System Sensors

J2399™ Adaptive Cruise Control (ACC) Operating Characteristics and User Interface

J2802™ Blind Spot Monitoring System Operating Characteristics & User Interface

J3116™ Active Safety Pedestrian Test Mannequin Recommendation

J3157™ Active Safety Bicyclist Test Targets

J3029™ Forward Collision Warning & Mitigation Vehicle Test Procedure – T&B

J3045™: Truck & Bus Lane Departure Warning Systems Test Procedure

VEHICLE SYSTEM & PERFORMANCE REQUIREMENTS


ADAS Standards

Safety and Human Factors Standards Related to ADASJ3048™: Driver-Vehicle Interface Considerations for Lane Keeping Assistance Systems J2988™: Guidelines for Speech Input & Audible Output in Driver Vehicle InterfaceJ2400™: Human Factors in Forward Collision Warning Systems Operating Characteristics & User Interface J2831™: Development of Design & Engineering Recommendations for In-Vehicle Alphanumeric MessagesJ2972™: Definition of Hands-Free Operation of a Person to Person Wireless Communication System or Device J2399™: Adaptive Cruise Control Operating Characteristics & User InterfaceJ2808™: Road/Lane Departure Warning Systems: Information for the Human InterfaceJ3077™: Definitions and Data Sources for the Driver Vehicle Interface (DVI)

ADAS Related Documents – Work In-Process J3122 WIP: Active Safety Test Target CorrelationJ3063 WIP: Update to Active Safety Systems Terms & Definitions



SAE On-Road Automated Driving Standards Activities


SAE On-Road Automated Driving Standards ActivitiesOn-Road

Automated Driving (ORAD)

Committee

Definitions Task Force

Planning Task Force

Verification and

ValidationTask Force

Reference Architecture

InterfacesTask Force

ADS-DV User Issues for

Persons with DisabilitiesTask Force

On Road Automated

Driving ManeuverTask Force

ADS TestingTask Force

J3018Task Force

Infrastructure Needs Related to Automated Driving ORAD

Task Force

Scope:Taxonomy for motor vehicle driving automation systems that perform part or all of the dynamic driving task on a sustained basis

Scope:Coordinates with other SAE committees and with external organizations doing complementary work, including ISO, UNECE, NHTSA, IEEE, ULC

Scope:Information and guidelines for verification and validation (V&V) of Automated Driving Systems (ADS).

Scope:automated driving reference architecture that contains functional modules supporting future application interfaces for Levels 3 through 5

Scope:gather and develop information on user issues specific to this population of ADS-DV users

Scope:Define information, best practices, and standards for maneuvers of on road automated driving systems (ADSs) for automation levels 3, 4, 5

Scope:Gathering point for the ADS Testing project

Scope:general safety-relevant guidelines for performing tests of prototype automated driving systems (ADSs) equipped on test vehicles operated in mixed-traffic environments on public roads

Scope:Uniformity of design Maintenance levelsConsistency of application Optimization Environmental conditions•Markings •Signs/ signals •Work/school zones, etc

Definitions Task Force

ISO/SAE Joint

Driving Skills Committee

J3300 ADS Fallback Ready Test

Driver


J3016 Levels of Driving Automation – Consumer VersionRecommended Practice: Taxonomy and Definitions for Terms Related to Driving Automation Systems for On-Road Motor VehiclesSeminal standard for automated driving systems (ADS) that defines key terms and a hierarchy of automation (levels 0-5). Allows industry to speak with a common language about ADS.


ORAD Standards Overview


Additional Committee Activity for Developing Automation Standards

Committee OverviewSafety and Human Factors

CommitteeDriving Automation Systems

J3196 Task Force

Responsible for all safety & human factors issues concerning driving automation systems and how these new technologies will impact the driving experience. J3114 - Human Factors Definitions for Automated Driving and Related ResearchJ3196 - Describing human roles and capabilities as part of driving automation systems

Event Data Recorder Committee ADS Logger Task Force

Task Force to identify ADS data elements and develop definitions that can be gathered in crash or near-crash events in ADS. These additional data elements may be those useful for accident reconstruction and assessing ADS performance

Signaling and Marking Devices Standards Committee ADS Lamps Task Force

Task Force to develop test procedures, performance requirements, and design guidelines for ADS vehicle lighting (J3134).

Driving Skills Committee Drafting J3300 AV Safety Operator endorsement (Driving Skills Certification Criteria) for test drivers (safety operators) on proving grounds as a complement to the four skill levels defined in the foundational license.

Stakeholder communication of US DOT FHWA funded project to advance the development of SAE Cooperative

Driving Automation standards


Cooperative Driving Automation Standards Support Project


What is Cooperative Driving Automation?

Cooperative Driving Automation (CDA)Driving automation that includes machine-to-machine (M2M) communication to enable cooperation between entities with capable communications technology and is intended to support or enable performance of the Dynamic Driving Task (DDT) for a subject vehicle with driving automation feature(s) engaged, for the purposes of facilitating the safer, more efficient movement of road users.

Why is it useful?• Enables larger field of view that sensors like cameras and LIDAR may not provide• Provides an interface to infrastructure, e.g. traffic signals and road condition information• Supports self-organizing groups of vehicles for purposes such as platooning• Allows participation of other types of transportation system users, e.g. pedestrians,

cyclists, etc.


SAE Cooperative Driving Automation Project Deliverables #1

Develop a taxonomy for the role of communications and relationship to automation

SAE J3216 Taxonomy and Definitions for Terms Related to Cooperative Driving Automation for On-Road Motor Vehicles in development

• ORAD Definitions Task Force activity• Provides a common set of terms for use in future development activities• Builds on the J3016 taxonomy to include levels of cooperative

automation


CDA: Automation + Cooperation

Automation Cooperation

SAE J3216 (in development)

CDA can involve interactions between vehicles and infrastructure, or between vehicles and pedestrians or cyclists, to support the dynamic driving task.


Types of CDA-enabled communication

Example: Vehicles coordinate merging due to a lane drop.Example types of communication that support this application:A. Informational: CDA-enabled Roadside Device shares that lane is closed at a specified locationB. Intent Sharing: Car 2 shares intent to merge in front of Car 3; Car 3 may or may not consider requestC. Agreement Seeking: Car 2 shares intent to merge in front of Car 3; Car 3 agrees to permit this

maneuver

RoadsideDevice

1

2

3Example of a zipper merge where vehicles can inform each other about status of the road ahead, vehicle intent, or even negotiate a coordinated merge

CDA can also involve interactions between vehicles and infrastructure, or vehicles and pedestrians or cyclists



Stakeholder identification, outreach and engagement activities• Ten Categories of Stakeholders Identified• Engagement Plan Developed • Stakeholder Registry Developed• Engagement Activities Planning Log Developed• Outreach Timeline Developed• Stakeholder Outreach In-Process


Who cares about Cooperative Driving Automation?

Appropriate SAE Technical Committees (ORAD, V2X Communications, Active Safety, S&HF, etc.)

Domestic / International Standard Development Organizations NTCIP, AASHTO, ITE, IEEE, ISO, ETSI, Others

Public-sector stakeholders State DOTs, Trade Associations, emergency responders

Ground Vehicle OEM Community GM, Ford Motor, FCA, Honda, Toyota, Mitsubishi, BMW, Daimler, Volkswagen, etc.

Supplier Community Bosch, Waymo, Uber, Visteon, APTIV, Delphi, Apple, Qualcomm, Panasonic, Mahindra, etc.

Testing Community Intertek, TUV SUD, TRC, ACM, SwRI, Intertek, etc.

Universities and Research Coalitions Carnegie Mellon Univ., Univ. Mich. Transport. Research Inst., Univ. CA-Berkeley, etc.

Government Transport Agencies and Entities DOT, FHWA, NHTSA, DOE, FMCSA, NIST, Volpe, NTSB, etc.

Technical Consultant Community Exponent, BAH, P3 Group, Leidos, Mixon Hill Inc, JMC Rota, OnBoard Security,

Software, Simulation and Modeling Services Altair, Vector, rFpro, Ansis, AVL, IPG, dSPACE, Cognata, Spirent

Stakeholders



Identify cooperation and automation factors suitable for standardization to support integration of ADS with infrastructure

• Standards gap analysis• Standardization road map

– Potential standards and other technical reports may include but are not limited to the following:• Monitoring the driving environment via object and event detection, recognition,

classification, and response preparation (operational and tactical);• Mapping and localization• Maneuver planning (tactical)• Object and event response execution (operational and tactical)• Longitudinal vehicle motion control via acceleration and deceleration (operational)• Lateral vehicle motion control via steering (operational)• Enhancing conspicuity via lighting, signaling and gesturing, etc. (tactical)


SAE Cooperative Driving Automation Project Deliverables #4 & #5

4. Develop new and augment existing standards to support ADS integration using the Systems Engineering Process (SEP)

5. Foster the development of ITS standards including: V2V, V2I, V2P, V2 other using the SEP

Timeline 12-18 months

Mutual Agreement

onSubject Topic

Input:Agency, industry needs (top-down or bottom-up)

Open SAE Technical

Committee

Document Development & Balloting

Process

Document Sponsor –

SAE Project Team SME

SAEProject Team

Open, Transparent and Consensus Based Process


V2X Communications Standards that Support Safety, Mobility and Support of Cooperative

Automation


V2X Communications Standards Activities


SAE V2X Communications Technical Committees

DSRC Technical

Committee

C-V2X Technical

Committee

Advanced Applications

Technical Committee

Security Technical

Committee

Cross-Cutting Technical

Committee

Infrastructure Applications

Technical Committee

Traffic Signal Applications

Technical Committee

Vehicular Applications

Technical Committee

Tolling Applications

Technical Committee

Scope:DSRC Radio access-specific items

Scope:C-V2X Radio access-specific items

Scope:Lower layer-unknown applications that may require new communication technologies

Scope:Over the air security

Scope:Common to multiple applications or communication technologies

Scope:Infrastructure applications that do not require traffic signal data

Scope:Infrastructure applications that require traffic signal data or interface

Scope:Vehicle communication needs

Scope:Applications for tolling and financial transactions

V2X Communications Steering Committee

Mapping Task Force

Maneuver Sharing &

Coordinating Task Force

Deployment Profiles Task

Force

Antenna Task Force

J2945/1 Task Force


SAE V2X Communication Standards

J2735: Message Set Dictionary• Over the air messages used in DSRC and other systems• E.g. Basic Safety Message (BSM) and Signal Phase and Timing (SPaT) message

Note: Messages are no longer directly added to J2735 without first being vetted through an application standard (e.g. J2945/3 creates the Road Weather Message, which may be incorporated in a later revision of J2735 if 2945/3 is not likely to be further revised)

J2945: Systems engineering guidance and common design concepts• Includes recommended EDCA priority settings• Includes recommended channel usage and recommended max TX power per channel

J2945/1: On Board System Requirements for V2V Safety Communications• Light vehicles only (FHWA classes 2 & 3)• Specifies functional and performance requirements for sending and receiving BSMs

• Revision currently underway (in balloting) • Reference applications: EEBL, FCW, BSW/LCW, IMA, LTA, CLW• Uses 802.11p for the physical interface; J3161/1 is in development and uses PC5


SAE V2X Communication Standards and Other Technical Reports Other Published Documents

J2945/2: V2V safety awareness recommended practice (builds on 2945/1)J2945/9: Vulnerable road user recommended practice

J3067: Systems engineering enhancements to J2735 (information report)In Development

J2945/3: Road weather applications (draft standard in balloting)J2945/4: Road safety applicationsJ2945/5: Security guidelines for connected vehicle applicationsJ2945/6: Adaptive cruise control and platooningJ2945/7: Positioning enhancementsJ2945/8: Cooperative perception systemJ2945/A: Next generation mapping (revised from original SPaT / MAP scope)J2945/B: Signal preemption recommended practice J2945/C: Probe dataJ2945/D: Road user to road user courteous communicationJ2945/1A: Vehicle level test proceduresJ3161: C-V2X deployment profilesJ3161/1: On-Board System Requirements for LTE V2X V2V Safety CommunicationsJ3186: Maneuver Sharing


Shared Mobility Standards Activities


SAE Shared Mobility Activities

Rapidly advancing technology

Environment concerns

Increasing traveler

expectationsCongestion &

travel time

Demographic changes

Limited Resources

https://www.sae.org/shared-mobility

BackgroundShared mobility is the shareduse of a vehicle, motorcycle, scooter, bicycle, or other travel mode. Shared mobility provides users with short-term access to one of these modes of travel as they are needed.

What is Shared Mobility?

https://www.sae.org/shared-mobility


SAE Shared And Digital Mobility Standards Committee

MILESTONES• Committee established in September 2017• First technical report:J3163 – Taxonomy and Definitions for Terms Related

to Shared Mobility and Enabling Technologies.It covers six categories of terms related to shared mobility:

• Next steps include– Symbols and signage for shared mobility– Data format for data sharing– Household travel surveys – Exploring intersect with core GV

technologies– Revision in second half of 2019

SAE Shared and Digital Mobility Committee embarked on the task of standardizing terms and definitions related to shared mobility.


SAE Micro-Mobility Devices Committee New!

This committee will initially focus on low-speed personal mobility devices and the technology and systems that support them that are not normally subject to the United States Federal Motor Vehicle Safety Standards or similar regulations. These may be device-propelled or have propulsion assistance.

Initial standards:1. Taxonomy of Micromobility Devices2. J3171 ADS-DV User Issues for Persons with

Disabilities

Emerging and innovative mobility vehicles and devices, sometimes referred to as micro-mobility, are proliferating in cities around the world.

These technologies have the potential to expand mobility options for a variety of people. Some of these technologies fall outside traditional definitions, standards, and regulations.

Electric Kick Scooter

Electric Skateboard

(Half) Segways Electric Self-Balancing Unicycles


Cybersecurity Standards Activities


SAE Cybersecurity Standards Activities

SAE Vehicle Electrical System Security Committee

• Vehicle Electrical Hardware Security Task Force

• RFC Cybersecurity Task Force

SAE Vehicle Cybersecurity Systems Engineering Committee

• Cybersecurity Assurance Testing Task Force

• Automotive Cybersecurity Integrity Level (ACsIL) Task Force

http://www.sae.org/servlets/works/committeeHome.do?comtID=TEVEES18A1

J3061 Cyber Security Guidebook

http://www.sae.org/servlets/works/committeeHome.do?comtID=TEVEES18A1


ISO/SAE 21434 Automotive Cybersecurity Engineering

First joint standard developed under the ISO / SAE PSDO Agreement

ISO/SAE 21434 development began Oct 2016 - anticipate Draft International Standard Ballot in Jan 2020.

SAE J3061: 2016 Cyber Security Guidebook was used as a baseline document in the development of ISO/SAE 21434

Defines a structured process to ensure cybersecurity is designed in upfront• Applicable to Road-vehicles• Goal of reasonably secure vehicles and systems.• Automakers and Suppliers can use to show “due diligence”• Focus on automotive cybersecurity engineering• Based on current state-of-the-art for Cybersecurity Engineering

SAE INTERNATIONAL

Keith [email protected]

Thank You

mailto:[email protected]

SAE Liaison Report ITU CITS e-meeting (28 October 2019) · 10/28/2019 · SAE Liaison Report . ITU...

Documents

Transcript of SAE Liaison Report ITU CITS e-meeting (28 October 2019) · 10/28/2019 · SAE Liaison Report . ITU...