Refine Your Search

Topic

Search Results

Technical Paper

Research on Vehicle Cybersecurity Based on Dedicated Security Hardware and ECDH Algorithm

2017-09-23
2017-01-2005
Vehicle cybersecurity consists of internal security and external security. Dedicated security hardware will play an important role in car’s internal and external security communication. ...For certain AURIX MCU consisting of HSM, the experiment result shows that cheaper 32-bit HSM’s AES calculating speed is 25 times of 32-bit main controller, so HSM is an effective choice to realize cybersecurity. After comparing two existing methods that realize secure CAN communication, A Modified SECURE CAN scheme is proposed, and differences of the three schemes are analyzed.
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.
Training / Education

Validating Requirements and Improving Specifications with Telematics Data

Field failures cause high warranty expenses, perhaps the highest quality cost. Failures occur when new designs are introduced, existing products are sold in new markets, and product specifications don’t reflect actual product usage. Any mistake in product specifications affects the entire product development process and cascades through the supply chain. New product requirements are developed using prior requirements, rely on customer surveys, use “expert” opinion, or are the result of compromises to meet timing or management direction. The resulting requirements may be excessive or insufficient.
Standard

Implementation Guide for Data Management

2014-07-01
WIP
GEIAHB859A
The federal government and industry have moved to concurrent acquisition and development processes using integrated process teams (IPTs). These processes are supported by timely, accurate, cross functional access to data within an integrated data environment (IDE) enabled by advances in information technology (IT). Since the advent of acquisition reform in 1994, Data Management (DM) practices have evolved from being directed by a prescriptive set of standards and procedures to use of the guidance in a principles-based standard -- ANSI/EIA 859.

GEIA Handbook 859 provides implementation guidance for ANSI/EIA 859, with discussions of applications of the standard's principles, tools, examples, and case studies. Handbook 859 is organized according to the lifecycle of data management and covers activities from the pre-RFP stage through records disposition.

Technical Paper

Communication between Plug-in Vehicles and the Utility Grid

2010-04-12
2010-01-0837
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.
Magazine

Automotive Engineering: October 6, 2015

2015-10-06
2016 Malibu sheds 300 lb, adds new hybrid system More wheelbase, style, fuel economy, and comfort aim to move GM's volume midsize sedan from the sidelines to the fast lane. Lighter, more powerful 2016 Honda Pilot The third-generation SUV gets a sleek new look and plenty of slick technology for enhanced performance and safety. 2016 Mazda MX-5 stays true to its roots Mazda engineers give the industry a lesson in getting more from less. 2016 Land Rover Discovery Sport spearheads more efficient Land Rovers JLR's space-efficient, flexible SUV moves to JLR's new Ingenium modular engines. Audi chooses high technology, cautious design evolution for new A4 In addition to lighter weight and significant improvements in efficiency, the new car employs plenty of technology and driver support.
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.
Magazine

SAE Off-Highway Engineering: October 7, 2015

2015-10-07
HMIs extend beyond the cab Telematics functions are being integrated into multi-function user interfaces. Standards step forward in design of off-highway electronics Functional safety standards are starting to impact many development projects, while the auto industry's AUTOSAR standard is being deployed to help enable software reuse and simplify designs. Leveraging automotive lightweighting techniques to improve off-highway emissions Where systems engineers can gain efficiencies in off-highway equipment is agnostic, they'll take it anywhere, and so they should, but one of the ways, often underestimated, is through the use of strong and lightweight advanced materials. Waste heat recovery for the long haul A WHR system based on an organic Rankine cycle has been developed for a long-haul Iveco Stralis truck.
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.
Standard

Digital Communications for Plug-in Electric Vehicles

2014-12-11
CURRENT
J2931/1_201412
This SAE Information Report SAE J2931 establishes the requirements for digital communication between Plug-In Electric Vehicles (PEV), the Electric Vehicle Supply Equipment (EVSE) and the utility or service provider, Energy Services Interface (ESI), Advanced Metering Infrastructure (AMI) and Home Area Network (HAN). This is the third version of this document and completes the effort that specifies the digital communication protocol stack between Plug-in Electric Vehicles (PEV) and the Electric Vehicle Supply Equipment (EVSE). The purpose of the stack outlined in Figure 1 and defined by Layers 3 to 6 of the OSI Reference Model (Figure 1) is to use the functions of Layers 1 and 2 specified in SAE J2931/4 and export the functionalities to Layer 7 as specified in SAE J2847/2 (as of August 1, 2012, revision) and SAE J2847/1 (targeting revision at the end of 2012).
X