In-Vehicle Network Architecture for the Next-Generation Vehicles

In-Vehicle Network Architecture for the Next-Generation Vehicles

Syed Masud Mahmud (Wayne State University, USA)
DOI: 10.4018/978-1-60566-338-8.ch015

Abstract

New types of communication networks will be necessary to meet various consumer and regulatory demands as well as satisfy requirements of safety and fuel efficiency. Various functionalities of vehicles will require various types of communication networks and networking protocols. For example, driveby- wire and active safety features will require fault tolerant networks with time-triggered protocols to guarantee deterministic latencies. Multimedia systems will require high-bandwidth networks for video transfer, and body electronics need low-bandwidth networks to keep the cost down. As the size and complexity of the network grows, the ease of integration, maintenance and troubleshooting has become a major challenge. To facilitate integration and troubleshooting of various nodes and networks, it would be desirable that networks of future vehicles should be partitioned, and the partitions should be interconnected by a hierarchical or multi-layer physical network. This book chapter describes a number of ways using which the networks of future vehicles could be designed and implemented in a cost-effective manner. The book chapter also shows how simulation models can be developed to evaluate the performance of various types of in-vehicle network topologies and select the most appropriate topology for given requirements and specifications.
Chapter Preview
Top

Introduction

Early vehicles used dedicated point-to-point connections for inter-module communications. As the number of modules and features increased in vehicles, the wiring system became bulky, complex, expensive and difficult to install and maintain. As a result, over the years, evolution of in-vehicle communications via a serial bus took place. A serial bus can replace all the dedicated point-to-point wiring between modules. Thus, it significantly reduces wiring complexity as well as weight of the vehicle making the vehicle more fuel efficient. A serial bus system is also scalable, meaning that more modules can be connected to the bus at any time without requiring any changes at other modules. Since different functions of a vehicle need different data rates, such as power-train needs higher data rate than body electronics, the use of a single serial bus for the entire vehicle may not be the best choice to design the in-vehicle communication network. As high-speed electronic components are more expensive than low-speed electronic components, it would be desirable and cost effective to partition the serial bus into two buses: a high-speed serial bus and a low-speed serial bus. The high-speed bus can be used for power-train and the low-speed bus can be used for body electronics. This is the reason why currently most vehicles have at least two serial buses: one for power-train and the other for body electronics, as shown in Figure 1. Since there are some mutually required data between the two partitions of the in-vehicle network, the partitions are interconnected by a gateway device as shown in Figure 1. The two partitions need not use the same type of bus though they can. Since the LIN (Local Interconnection Network) bus is less expensive and LIN protocol (Uplap, 2004) is less complex than the corresponding CAN (Controller Area Network) bus and CAN protocol (Motorola,1998), nowadays many vehicles are considering using a low-speed LIN bus for body electronics and a high-speed CAN bus for power-train. The gateway device which interconnects a CAN bus and a LIN bus converts messages from one protocol to another protocol when the messages need to go from one partition to another partition.

Figure 1.

An in-vehicle networking system with two partitions

978-1-60566-338-8.ch015.f01

As the government and consumer demands are increasing for many features such as safety, fuel efficiency, comfort, navigation, entertainment, telematics, multimedia and many more, future vehicles will have many more partitions. Each partition will take care of a particular type of application. All the partitions will need to be interconnected for exchanging mutually required information as well as for diagnostic purposes. Like early vehicles, dedicated point-to-point connections among various partitions will increase the complexity of connectivity, as shown in Figure 2. Figure 2 shows an in-vehicle networking system with four partitions. Each has its own bus system. Each pair of partitions is interconnected by a gateway device. For example, Partition-1 and Partition-2 are connected by the gateway device G12. Similarly, Partition-1 and Partition-4 are connected by the gateway device G14. The number of gateway devices increases exponentially with the increase in the number of partitions. For N partitions, the number of gateway devices required for dedicated connections among the various partitions is 978-1-60566-338-8.ch015.m01. Thus, dedicated connections among the partitions will be very complex and cost prohibitive.

Figure 2.

Dedicated connections among four partitions of an in-vehicle networking system.

978-1-60566-338-8.ch015.f02

As the number of partitions in a vehicle is going to increase, the automakers must come up with less complex and less expensive techniques for interconnecting the partitions.

The main objective of this book chapter is to show various cost-effective interconnection mechanisms among the partitions of an in-vehicle networking system. The advantages, disadvantages and the feasibility of various interconnection mechanisms using the current technology are also explained in this book chapter.

Complete Chapter List

Search this Book:
Reset