Refine Your Search

Topic

Search Results

Research Report

Unsettled Issues Regarding Autonomous Vehicles and Open-source Software

2021-04-21
EPR2021009
Unsettled Issues Regarding Autonomous Vehicles and Open-source Software introduces the impact of software in advanced automotive applications, the role of open-source communities in accelerating innovation, and the important topic of safety and cybersecurity. As electronic functionality is captured in software and a bigger percentage of that software is open-source code, some critical challenges arise concerning security and validation.
Technical Paper

Implementation Methodologies for Simulation as a Service (SaaS) to Develop ADAS Applications

2021-04-06
2021-01-0116
Over the years, the complexity of autonomous vehicle development (and concurrently the verification and validation) has grown tremendously in terms of component-, subsystem- and system-level interactions between autonomy and the human users. Simulation-based testing holds significant promise in helping to identify both problematic interactions between component-, subsystem-, and system-levels as well as overcoming delays typically introduced by the default full-scale on-road testing. Software in Loop (SiL) simulation is utilized as an intermediate step towards software deployment for autonomous vehicles (AV) to make them reliable. SiL efforts can help reduce the resources required for successful deployment by helping to validate the software for millions of road miles. A key enabler for accelerating SiL processes is the ability to use Simulation as a Service (SaaS) rather than just isolated instances of software.
Technical Paper

Deep Learning Based Real Time Vulnerability Fixes Verification Mechanism for Automotive Firmware/Software

2021-04-06
2021-01-0183
Software vulnerability management is one of the most critical and crucial security techniques, which analyzes the automotive software/firmware across the digital cockpit, ADAS, V2X, etc. domains for vulnerabilities, and provides security patches for the concerned Common Vulnerabilities and Exposures (CVE). The process of automotive SW/FW vulnerability management system between the OEMs and vendors happen through a channel of fixing a certain number of vulnerabilities by 1st tier supplier which needs to be verified in front of OEMs for the fixed number and type of patches in there deliverable SW/FW. The gap of verification between for the fixed patches between the OEMs and 1st tier supplier requires a reliable human independent intelligent technique to have a trustworthiness of verification.
Technical Paper

Leveraging Systems Theoretic Process Analysis (STPA) for Efficient ISO 26262 Compliance

2021-04-06
2021-01-0067
There has been a significant increase - both in the content of electronics and software in vehicles as well as in recalls attributed to these components and systems. The advanced features, including the onset of autonomous vehicles accompanied by millions of lines of code in software have exponentially increased the complexity of vehicle systems and decreased effectiveness of many of the safety analysis techniques being used to identify hazards and safety requirements - for example, FMEA, FTA, ETA, etc.- which were invented decades before the existence of complexities of such magnitude. This paper examines a new hazard identification technique formalized by Nancy G Leveson of Massachusetts Institute of Technology (MIT), USA in her book “Engineering a Safer World” and further elaborated in the STPA Handbook co-authored with John P Thomas in March 2018.
Research Report

Unsettled Issues Facing Automated Vehicles and Insurance

2020-08-05
EPR2020015
This SAE EDGE™ Research Report explores how the deployment of automated vehicles (AVs) will affect the insurance industry and the principles of liability that underly the structure of insurance in the US. As we trade human drivers for suites of sensors and computers, who (or what) is responsible when there is a crash? The owner of the vehicle? The automaker that built it? The programmer that wrote the code? Insurers have over 100 years of experience and data covering human drivers, but with only a few years’ worth of information on AVs – how can they properly predict the true risks associated with their deployment? Without an understanding of the nature and risks of AVs, how can the government agencies that regulate the insurance industry provide proper oversight? Do the challenges AVs present require a total reworking of our insurance and liability systems, or can our current structures be adapted to fit them with minor modifications?
Research Report

Unsettled Topics Concerning User Experience and Acceptance of Automated Vehicles

2020-06-29
EPR2020012
This SAE EDGE Research Report addresses the unsettled topic of user acceptance of automated driving, analyzing the user experience for a more intuitive and safe driving experience. Unsettled Topics Concerning User Experience and Acceptance of Automated Vehicles examines the requirements for safer driver/user engagement with driving for the various SAE automation levels. It analyzes consumer sentiment toward automated driving - both consumer excitement about the perceived benefits and dislikes or concerns about the technology. The findings from surveys about drivers' experience with advanced driving assistance technologies and its application to automated driving is also brought to the surface of the discussion, together with driver profiles observed during a user-centric experience in an immersive automated driving cockpit.
Technical Paper

Selftrust - A Practical Approach for Trust Establishment

2020-04-14
2020-01-0720
In recent years, with increase in external connectivity (V2X, telematics, mobile projection, BYOD) the automobile is becoming a target of cyberattacks and intrusions. Any such intrusion reduces customer trust in connected cars and negatively impacts brand image (like the recent Jeep Cherokee hack). To protect against intrusion, several mechanisms are available. These range from a simple secure CAN to a specialized symbiote defense software. A few systems (e.g. V2X) implement detection of an intrusion (defined as a misbehaving entity). However, most of the mechanisms require a system-wide change which adds to the cost and negatively impacts the performance. In this paper, we are proposing a practical and scalable approach to intrusion detection. Some benefits of our approach include use of existing security mechanisms such as TrustZone® and watermarking with little or no impact on cost and performance. In addition, our approach is scalable and does not require any system-wide changes.
Technical Paper

Safety Development Trend of the Intelligent and Connected Vehicle

2020-04-14
2020-01-0085
Automotive safety is always the focus of consumers, the selling point of products, the focus of technology. In order to achieve automatic driving, interconnection with the outside world, human-automatic system interaction, the security connotation of intelligent and connected vehicles (ICV) changes: information security is the basis of its security. Functional safety ensures that the system is operating properly. Behavioral safety guarantees a secure interaction between people and vehicles. Passive security should not be weakened, but should be strengthened based on new constraints. In terms of information safety, the threshold for attacking cloud, pipe, and vehicle information should be raised to ensure that ICV system does not fail due to malicious attacks. The cloud is divided into three cloud platforms according to functions: ICVs private cloud, TSP cloud, public cloud.
Technical Paper

Test Method for the SAE J3138 Automotive Cyber Security Standard

2020-04-14
2020-01-0142
This paper will provide an Overview of Automotive Cyber Security Standards related to the Vehicle OBD-II Data Link. The OBD-II Connector Attack Tree is described with respect to the SAE J3138 requirements for Intrusive vs. non-Intrusive Services. A proposed test method for SAE J3138 is described including hardware and software scripting. Finally, example test results are reviewed and compared with a potential threat boundary.
Research Report

Unsettled Issues in Determining Appropriate Modeling Fidelity for Automated Driving Systems Simulation

2019-12-06
EPR2019007
This SAE EDGE™ Research Report identifies key unsettled issues of interest to the automotive industry regarding the challenges of achieving optimal model fidelity for developing, validating, and verifying vehicles capable of automated driving. Three main issues are outlined that merit immediate interest: First, assuring that simulation models represent their real-world counterparts, how to quantify simulation model fidelity, and how to assess system risk. Second, developing a universal simulation model interface and language for verifying, simulating, and calibrating automated driving sensors. Third, characterizing and determining the different requirements for sensor, vehicle, environment, and human driver models. SAE EDGE™ Research Reports are preliminary investigations of new technologies.
Technical Paper

Enabling Efficient Functional Safety Audits - The Missing Link between ISO 26262 and Automotive SPICE

2019-04-02
2019-01-0144
In the field of electric and electronic (E/E) design for the automotive industry, there are separate traditions related to functional safety and software quality assurance. Both relying on the evaluation of the processes used; Automotive SPICE provides detailed guidance on how to perform this evaluation whilst ISO 26262 does not and simply mention Automotive SPICE as one possible solution. ISO 26262 additionally requires for an evaluation of the functional safety achieved by the product and uses the process evaluation (or functional safety audit in ISO 26262 terms) to support the final functional safety assessment. The purpose is to evaluate the implementation of the necessary safety processes according to the claimed scope defined in the safety plan. Automotive SPICE does not make a distinction on whether the application of the software under evaluation is safety related or not.
Technical Paper

Analyze This! Sound Static Analysis for Integration Verification of Large-Scale Automotive Software

2019-04-02
2019-01-1246
Safety-critical embedded software has to satisfy stringent quality requirements. One such requirement, imposed by all contemporary safety standards, is that no critical run-time errors must occur. Runtime errors can be caused by undefined or unspecified behavior of the programming language; examples are buffer overflows or data races. They may cause erroneous or erratic behavior, induce system failures, and constitute security vulnerabilities. A sound static analyzer reports all such defects in the code, or proves their absence. Sound static program analysis is a verification technique recommended by ISO/FDIS 26262 for software unit verification and for the verification of software integration. In this article we propose an analysis methodology that has been implemented with the static analyzer Astrée. It supports quick turn-around times and gives highly precise whole-program results.
Technical Paper

Experimental Setup Enabling Self-Confrontation Interviews for Modelling Naturalistic Driving Behavior

2019-04-02
2019-01-1082
Behavioral models of traffic actors have a potential of unlocking sophisticated safety features and mitigating several challenges of urban automated driving. Intuitively, volunteers driving on routes of daily commuting in their private vehicles are the preferred source of information to be captured by data collection system. Such dataset can then serve as a basis for identifying efficient methods of context representation and parameterization of behavioral models. This paper describes the experimental setup supporting the development of driver behavioral models within the SIMUSAFE project. In particular, the paper presents an IoT data acquisition and analysis infrastructure supporting self-confrontation interviews with drivers. The proposed retrofit system was installed in private vehicles of volunteers in two European cities. Wherever possible, the setup used open source software and electronic components available on consumer market.
Technical Paper

Application of Suspend Mode to Automotive ECUs

2018-04-03
2018-01-0021
To achieve high robustness and quality, automotive ECUs must initialize from low-power states as quickly as possible. However, microprocessor and memory advances have failed to keep pace with software image size growth in complex ECUs such as in Infotainment and Telematics. Loading the boot image from non-volatile storage to RAM and initializing the software can take a very long time to show the first screen and result in sluggish performance for a significant time thereafter which both degrade customer perceived quality. Designers of mobile devices such as portable phones, laptops, and tablets address this problem using Suspend mode whereby the main processor and peripheral devices are powered down during periods of inactivity, but memory contents are preserved by a small “self-refresh” current. When the device is turned back “on”, fully initialized memory content allows the system to initialize nearly instantaneously.
Technical Paper

Proposal of HILS-Based In-Vehicle Network Security Verification Environment

2018-04-03
2018-01-0013
We propose a security-testing framework to analyze attack feasibilities for automotive control software by integrating model-based development with model checking techniques. Many studies have pointed out the vulnerabilities in the Controller Area Network (CAN) protocol, which is widely used in in-vehicle network systems. However, many security attacks on automobiles did not explicitly consider the transmission timing of CAN packets to realize vulnerabilities. Additionally, in terms of security testing for automobiles, most existing studies have only focused on the generation of the testing packets to realize vulnerabilities, but they did not consider the timing of invoking a security testing. Therefore, we focus on the transmit timing of CAN packets to realize vulnerabilities. In our experiments, we have demonstrated the classification of feasible attacks at the early development phase by integrating the model checking techniques into a virtualized environment.
Technical Paper

Total Vehicle Integration and Design - Journey to Electrification, Digitization and Connectivity Leading to Autonomy

2018-04-03
2018-01-0003
Total vehicle integration and design is a complex process and deals with interactions of many subsystems. The subsystems in a vehicle not only have to perform their role but interfaces between the subsystems must be well understood to design for all the interactions. The global automotive market is following electrification, digitization and connectivity trends that eventually lead to Autonomy. Therefore, the vehicle integration design process needs to include these new use cases of these trends. The process starts with establishing the top-level vehicle metrics relative to key deliverables of the vehicle ranging from providing comfortable environment to the driver to good performance. The process of establishing vehicle level metrics is not trivial and quite often must be derived from the customer verbatim. Frequently, there are conflicting requirements and priority must be given to one over another.
Technical Paper

Case Study for Defining Security Goals and Requirements for Automotive Security Parts Using Threat Modeling

2018-04-03
2018-01-0014
Several external networks like telematics, and SOTA and many in-vehicle networks by gateways and domain controllers have been increasingly introduced. However, these trends may potentially make many critical data opened, attacked and modified by hackers. These days, vehicle security has been significantly required as these vehicle security threats are related to the human life like drivers and pedestrians. Threat modeling is process of secure software development lifecycle which is developed by Microsoft. It is a systematic approach for analyzing the potential threat in software and identifying the security risk associated with software. Through threat modeling, security risk is be mitigated and eliminated. In vehicle software System, one of vulnerability can affect critical problem about safety. An approach from experience and hacking cases is not enough for analyzing the potential threat and preparing new hacking attack.
X