Refine Your Search




Search Results

Journal Article

(R)evolution of E/E Architectures

Functionalities such as automated driving, connectivity and cyber-security have gained increasing importance over the past few years. The importance of these functionalities will continue to grow as these cutting-edge technologies mature and market acceptance increases.
Technical Paper

A Controller Area Network Bus Identity Authentication Method Based on Hash Algorithm

With the development of vehicle intelligence and the Internet of Vehicles, how to protect the safety of the vehicle network system has become a focus issue that needs to be solved urgently. The Controller Area Network (CAN) bus is currently a very widely used vehicle-mounted bus, and its security largely determines the degree of vehicle-mounted information security. The CAN bus lacks adequate protection mechanisms and is vulnerable to external attacks such as replay attacks, modifying attacks, and so on. On the basis of the existing work, this paper proposes an authentication method that combines Hash-based Message Authentication Code (HMAC)-SHA256 and Tiny Encryption Algorithm (TEA) algorithms. This method is based on dynamic identity authentication in challenge/response made and combined with the characteristics of the CAN bus itself as it achieves the identity authentication between the gateway and multiple electronic control units (ECUs).
Technical Paper

A Domain-Centralized Automotive Powertrain E/E Architecture

This paper proposes a domain-centralized powertrain E/E (electrical and/or electronic) architecture for all-electric vehicles that features: a powerful master controller (domain controller) that implements most of the functionality of the domain; a set of smart actuators for electric motor(s), HV (High Voltage) battery pack, and thermal management; and a gateway that routes all hardware signals, including digital and analog I/O, and field bus signals between the domain controller and the rest of the vehicle that is outside of the domain. Major functional safety aspects of the architecture are presented and a safety architecture is proposed. The work represents an early E/E architecture proposal. In particular, detailed partitioning of software components over the domain’s Electronic Control Units (ECUs) has not been determined yet; instead, potential partitioning schemes are discussed.
Journal Article

A Novel Assessment and Administration Method of Autonomous Vehicle

As a promising strategic industry group that is rapidly evolving around the world, autonomous vehicle is entering a critical phase of commercialization from demonstration to end markets. The global automotive industry and governments are facing new common topics and challenges brought by autonomous vehicle, such as how to test, assess, and administrate the autonomous vehicle to ensure their safe running in real traffic situations and proper interactions with other road users. Starting from the facts that the way to autonomous driving is the process of a robot or a machine taking over driving tasks from a human. This paper summarizes the main characteristics of autonomous vehicle which are different from traditional one, then demonstrates the limitations of the existing certification mechanism and related testing methods when applied to autonomous vehicle.
Technical Paper

Adopting Aviation Safety Knowledge into the Discussions of Safe Implementation of Connected and Autonomous Road Vehicles

The development of connected and autonomous vehicles (CAVs) is progressing fast. Yet, safety and standardization-related discussions are limited due to the recent nature of the sector. Despite the effort that is initiated to kick-start the study, awareness among practitioners is still low. Hence, further effort is required to stimulate this discussion. Among the available works on CAV safety, some of them take inspiration from the aviation sector that has strict safety regulations. The underlying reason is the experience that has been gained over the decades. However, the literature still lacks a thorough association between automation in aviation and the CAV from the safety perspective. As such, this paper motivates the adoption of safe-automation knowledge from aviation to facilitate safer CAV systems.
Technical Paper

An Analysis of Secure Software Development Lifecycle from an Automotive Development Perspective

The modern vehicle development is highly dependent on software. The software development plays an extremely important role in vehicle safety and security. In order to ensure software high quality and safety standards, we have investigated the secure software development process and analyzed the works in this area. Based on our analysis, we have identified the similarities and differences between the secure software development process and the existing vehicle development process. We then made suggestions on how to adopt the secure software development process in the overall vehicle development process.
Technical Paper

An Integrated View on Automotive SPICE, Functional Safety and Cyber-Security

This increases the attractiveness of an attack on vehicles and thus introduces new risks for vehicle cybersecurity. Thus, just as safety became a critical part of the development in the late 20th century, the automotive domain must now consider cybersecurity as an integral part of the development of modern vehicles. ...Thus, just as safety became a critical part of the development in the late 20th century, the automotive domain must now consider cybersecurity as an integral part of the development of modern vehicles. Aware of this fact, the automotive industry has, therefore, recently taken multiple efforts in designing and producing safe and secure connected and automated vehicles. ...As the domain geared up for the cybersecurity challenges, they leveraged experiences from many other domains, but must face several unique challenges.
Technical Paper

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

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

Android Defense in Depth Strategy in an Automobile Ecosystem

Android is becoming an environment of choice in the automotive sector because of near production grade open source stack availability and large developer community. With growing interest from Automotive OEMs for Android IVI (In-Vehicle Infotainment) solutions, we predict a similar growth trend in an automobile like in Mobile space. At another end, the need for more interconnected devices within the Automobile ecosystem is increasing, which leads to an increased threat to security. In sophisticated device interconnections, identifying the gateways and implementing the right security strategy is key to improve overall system security & stability. While Android is maturing for automotive and with growing interest from automotive OEMs, we spent time in analyzing current Android defense-in-depth concepts with the automotive perspective.
Technical Paper

Application of Suspend Mode to Automotive ECUs

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

Building Responsibility in AI: Transparent AI for Highly Automated Vehicle Systems

Replacing a human driver is an extraordinarily complex task. While machine learning (ML) and its’ subset, deep learning (DL) are fueling breakthroughs in everything from consumer mobile applications to image and gesture recognition, significant challenges remain. The majority of artificial intelligence (AI) learning applications, particularly with respect to Highly Automated Vehicles (HAVs) and their ecosystem have remained opaque - genuine “black boxes.” Data is loaded into one side of the ML system and results come out the other, however, there is little to no understanding at how the decision was arrived at. To make these systems accurate, these AI systems require lots of data to crunch and the sheer computational complexity of building these DL based AI models also slows down the progress in accuracy and the practicality of deploying DL at scale.
Technical Paper

CAN Crypto FPGA Chip to Secure Data Transmitted Through CAN FD Bus Using AES-128 and SHA-1 Algorithms with A Symmetric Key

Robert Bosch GmBH proposed in 2012 a new version of communication protocol named as Controller area network with Flexible Data-Rate (CANFD), that supports data frames up to 64 bytes compared to 8 bytes of CAN. With limited data frame size of CAN message, and it is impossible to be encrypted and secured. With this new feature of CAN FD, we propose a hardware design - CAN crypto FPGA chip to secure data transmitted through CAN FD bus by using AES-128 and SHA-1 algorithms with a symmetric key. AES-128 algorithm will provide confidentiality of CAN message and SHA-1 algorithm with a symmetric key (HMAC) will provide integrity and authentication of CAN message. The design has been modeled and verified by using Verilog HDL – a hardware description language, and implemented successfully into Xilinx FPGA chip by using simulation tool ISE (Xilinx).
Technical Paper

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

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.
Technical Paper

Challenges in Integrating Cybersecurity into Existing Development Processes

Strategies designed to deal with these challenges differ in the way in which added duties are assigned and cybersecurity topics are integrated into the already existing process steps. Cybersecurity requirements often clash with existing system requirements or established development methods, leading to low acceptance among developers, and introducing the need to have clear policies on how friction between cybersecurity and other fields is handled. ...Cybersecurity requirements often clash with existing system requirements or established development methods, leading to low acceptance among developers, and introducing the need to have clear policies on how friction between cybersecurity and other fields is handled. A cybersecurity development approach is frequently perceived as introducing impediments, that bear the risk of cybersecurity measures receiving a lower priority to reduce inconvenience. ...For an established development process and a team accustomed to this process, adding cybersecurity features to the product initially means inconvenience and reduced productivity without perceivable benefits.
Technical Paper

Challenges in the Regulatory Framework of Automated Driving

Automated Driving (AD) is foreseen to be one of the major social and technological challenges in the coming years. Many manufacturers are developing new models with cutting-edge functionalities, which are not included in the scope of the current regulatory framework. Apart from demonstrating their know-how and expertise about AD, their willingness to sell their AD models in the European market is accelerating the rule-making system. However, which is the roadmap for the European regulatory framework? Policy makers and regulatory bodies are pushing their boundaries at all levels (national and international) in order to introduce modifications in existing regulations. These regulations will enable the introduction of these new functionalities into the market. Without decreasing the standards of safety and security, the implementation of a clear and harmonized regulatory framework and approval process is extremely needed.
Technical Paper

Communication Requirements for Plug-In Electric Vehicles

This paper is the second in the series of documents designed to record the progress of a series of SAE documents - SAE J2836™, J2847, J2931, & J2953 - within the Plug-In Electric Vehicle (PEV) Communication Task Force. This follows the initial paper number 2010-01-0837, and continues with the test and modeling of the various PLC types for utility programs described in J2836/1™ & J2847/1. This also extends the communication to an off-board charger, described in J2836/2™ & J2847/2 and includes reverse energy flow described in J2836/3™ and J2847/3. The initial versions of J2836/1™ and J2847/1 were published early 2010. J2847/1 has now been re-opened to include updates from comments from the National Institute of Standards Technology (NIST) Smart Grid Interoperability Panel (SGIP), Smart Grid Architectural Committee (SGAC) and Cyber Security Working Group committee (SCWG).
Technical Paper

Communication between Plug-in Vehicles and the Utility Grid

This paper is the first in a series of documents designed to record the progress of the SAE J2293 Task Force as it continues to develop and refine the communication requirements between Plug-In Electric Vehicles (PEV) and the Electric Utility Grid. In February, 2008 the SAE Task Force was formed and it started by reviewing the existing SAE J2293 standard, which was originally developed by the Electric Vehicle (EV) Charging Controls Task Force in the 1990s. This legacy standard identified the communication requirements between the Electric Vehicle (EV) and the EV Supply Equipment (EVSE), including off-board charging systems necessary to transfer DC energy to the vehicle. It was apparent at the first Task Force meeting that the communications requirements between the PEV and utility grid being proposed by industry stakeholders were vastly different in the type of communications and messaging documented in the original standard.
Technical Paper

Connected Vehicles - A Testing Approach and Methodology

With the introduction of Connected Vehicles, it is possible to extend the limited horizon of vehicles on the road by collective perceptions, where vehicles periodically share their information with other vehicles and servers using cloud. Nevertheless, by the time the connected vehicle spread expands, it is critical to understand the validation techniques which can be used to ensure a flawless transfer of data and connectivity. Connected vehicles are mainly characterized by the smartphone application which is provided to the end customers to access the connectivity features in the vehicle. The end result which is delivered to the customer is through the integrated telematics unit in the vehicle which communicates through a communication layer with the cloud platform. The cloud server in turn interacts with the final application layer of the mobile application given to the customer.
Technical Paper

Connectivity in 2 Wheelers: Opportunities and Challenges

Mobility is undergoing a “horses to cars”-sized shift that will reverberate across business and society for generations. Future of Mobility is mainly driven by 4 main pillars viz. Connected, Electrified, Automated and Shared Driving. With advancement in Communication Technology supplemented by huge customer base, Connectivity has proven to deliver better Services to the End-user. Connected Mobility is going to be the next Big Thing in the Mobility Arena. In this paper, we will try to qualitatively explore what Connected Mobility is all about and what it has to offer in terms of - Opportunities on one side as well as new challenges that were never witnessed in the realm of Mobility in the Past, with focus on the 2 wheeler segment. This paper focuses on Opportunities in terms of Location Based services, Vehicle Management, Data Analytics, Infotainment and possible Business scenarios and Models as well as challenges in Terms of Security and Data Ownership