Search Results

The new generation vehicles these days are managed by networked controllers. A large portion of the networks is planned with more security which has recently roused researchers to exhibit various attacks against the system. This paper talks about the liabilities of the Controller Area Network (CAN) inside In-vehicle communication protocol and a few potentials that could take due advantage of it. Moreover, this paper presents a few security measures proposed in the present examination status to defeat the attacks. In any case, the fundamental objective of this paper is to feature a comprehensive methodology known as Intrusion Detection System (IDS), which has been a significant device in getting network data in systems over many years. To the best of our insight, there is no recorded writing on a through outline of IDS execution explicitly in the CAN transport network system.

There continues to be massive advancements in modern connected vehicles and with these advancements, connectivity continues to rapidly become more integral to the way these vehicles are designed and operated. Vehicle connectivity was originally introduced for the purpose of providing software updates to the vehicle’s main system software, and we have seen the adoption of Over The Air updates (OTA) become mainstream with most OEMs. The exploitation of this connectivity is far more reaching than just basic software updates. In the latest vehicles it is possible to update software not just on the main vehicle systems, but to potentially update embedded software in all smart ECUs within the vehicle. Only using the connectivity to push data to the vehicle is not making full use of the potential of this increased connectivity. Being able to collect vehicle data for offline analysis and processing also brings huge benefits to the use of this technology.

Modern automobiles collect around 25 gigabytes of data per hour and autonomous vehicles are expected to generate more than 100 times that number. In comparison, the Apollo Guidance Computer assisting in the moon launches had only a 32-kilobtye hard disk. Without question, the breadth of in-vehicle data has opened new possibilities and challenges. The potential for accessing this data has led many entrepreneurs to claim that data is more valuable than even the vehicle itself. These intrepid data-miners seek to explore business opportunities in predictive maintenance, pay-as-you-drive features, and infrastructure services. Yet, the use of data comes with inherent challenges: accessibility, ownership, security, and privacy. Unsettled Legal Issues Facing Data in Autonomous, Connected, Electric, and Shared Vehicles examines some of the pressing questions on the minds of both industry and consumers. Who owns the data and how can it be used?

By looking into the vehicle-infrastructure cooperation (VIC) which is oriented towards intelligent, networked and integrated development, this paper analyzes and proposes the essence and development direction of Intelligent Vehicle Infrastructure Cooperation Systems (I-VICS). With an in-depth analysis of technologies of core importance to VIC and influence factors that constrain VIC development as a whole, the paper comes up with a technological route for VIC, and identifies a direction for vehicle-infrastructure cooperative development that progresses from primary to intermediate cooperation, then to advanced cooperation, and finally to full-fledged cooperation. Policy recommendations aiming at strengthening top-level design, building an integrated vehicle-infrastructure-cloud platform, expediting independence of key techs, building robust standards and regulations for VIC, enhancing workforce development as well as greater efforts at market promotion are put forward.

It is deemed that currently the intelligent connected vehicle (ICV) is in its early stage of development, and it will go through multiple development stages in the future to realize its final goal—autonomous driving. Based on the existing ICV researches, this paper believes that ICV can be used to improve the efficiency and safety of freeway. The current research of ICV has two main directions: one focuses on the traffic flow characteristics of vehicles with different attributes, the other is concerned with using ICV to reduce congestion. From the policies issued by countries around the world and the development plans promoted by major vehicle manufacturers, the future development trends and challenges of ICV are analyzed. ICV must overcome all the shortcomings to achieve its final goal, including insufficient hardware capabilities or excessive cost, and the degree of intelligence that needs to be improved.

Automotive system functionalities spread over a wide range of sub-domains ranging from non-driving related components to complex autonomous driving related components. The requirements to design and develop these components span across software, hardware, firmware, etc. elements. The successful development of these components to achieve the needs from the stockholders requires accurate understanding and traceability of the requirements of these component systems. The high-level customer requirements transformation into low level granularity requires an efficient requirement engineer. The manual understanding of the customer requirements from the requirement documents are influenced by the context and the knowledge gap of the requirement engineer in understanding and transforming the requirements.

Vehicles equipped with Level 4 and 5 autonomy will need to be tested according to regulatory standards (or future revisions thereof) that vehicles with lower levels of autonomy are currently subject to. Today, dynamic Federal Motor Vehicle Safety Standards (FMVSS) tests are performed with human drivers and driving robots controlling the test vehicle’s steering wheel, throttle pedal, and brake pedal. However, many Level 4 and 5 vehicles will lack these traditional driver controls, so it will be impossible to control these vehicles using human drivers or traditional driving robots. Therefore, there is a need for an electronic interface that will allow engineers to send dynamic steering, speed, and brake commands to a vehicle. This paper describes the design and implementation of a market-ready Automated Driving Systems (ADS) Test Data Interface (TDI), a secure electronic control interface which aims to solve the challenges outlined above.

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

Recent advances in automotive technologies have paved way to a new era of connectivity. Advanced Driver Assistance Systems are getting deployed in automobiles; many companies are developing driverless cars; connected cars are no more a work of mere research. [1] Vehicle manufacturers are developing ways to interface mobile devices with vehicles. However, all these advances in technology has introduced security risks. Unlike traditional computing systems, the security risk of an automobile can be fatal and can result in loss of lives [2]. The in-vehicle network of an automobile was originally designed to operate in a closed environment and hence network security was not considered during its design [3]. Several studies have already shown that an in-vehicle network can be easily compromised and an intruder can take full control of the vehicle. Researchers are working on various ways to solve this problem. Securing the in-vehicle communication by encrypting the messages is one such way.

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.

Transportation departments are under-going a dramatic transformation, shifting from organizations focused primarily on building roads to a focus on mobility for all users. The transformation is the result of rapidly advancing autonomous vehicle technology and personal telecommunication technology. These technologies provide the opportunity to dramatically improve safety, mobility, and economic opportunity for society and industry. Future generations of engineers and other transportation professionals have the opportunity to be part of that societal change. This paper will focus on the technologies state DOT’s and the private sector are researching, developing, and deploying to promote the future of mobility and improved efficiency for commercial trucking through advancements in truck platooning, self-driving long-haul trucking, and automated last mile distribution networks.

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.

Autonomous driving systems and connected mobility are the next big developments for the car manufacturers and their suppliers during the next decade. To achieve the high computing power needs and fulfill new upcoming requirements due to functional safety and security, heterogeneous processor architectures with a mixture of different core architectures and hardware accelerators are necessary. To tackle this new type of hardware complexity and nevertheless stay within monetary constraints, high performance computers, inspired by state of the art data center hardware, could be adapted in order to fulfill automotive quality requirements. The European Processor Initiative (EPI) research project tries to come along with that challenge for next generation semiconductors. To be as close as possible to series development needs for the next upcoming car generations, we present a hybrid semiconductor system-on-chip architecture for automotive.

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.

Technological advances in both hardware (Nano-electronics) and software (artificial intelligence) are increasingly influencing our lives on equipment and devices that surrounds us and more recently our means of locomotion. The autonomous vehicles, which previously appeared only in movie scenes, can already be found in our environment, such as ships, cars, trucks, tractors and aero engines. Considering the autonomous vehicles, its launching is much closer than we could imagine, since many companies signalize having the conditions to launch them in a large scale within 2018 year. The insertion of this type of technology opens a range of advances related to vehicles and the environment in which it is inserted. The communication between the vehicles, roads and people can be highlighted. These advances reveal a series of benefits to the customer such as free time during the route, higher safety, etc.

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.