In-Vehicle Network Architecture for the Next-Generation Vehicles

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.

Towards designing secure in-vehicle network architectures using community detection algorithms

“…Three architectures were considered during their evaluation: (1) a backbone architecture where suitable sub-networks are defined (domains) and connected together via gateways over a backbone network, (2) a multi-gateway architecture where no backbone network is used, instead each sub-network has a gateway and all gateways are chained together, and (3) a central gateway architecture where all sub-networks are connected to one single gateway that connects them together. Other variants have also been discussed by Mahmud and Alles [2], where different faulttolerant architectures are presented. The fault-tolerance is achieved by duplicating parts of the network.…”

“…A simulation model to evaluate the performance of different topologies were also introduced. Yet, the main goal in [1,2] has been to present different possible architectures in future vehicles where safety has been the main aspect. Methods for how to partition the in-vehicle network into domains were not presented nor was security considered.…”

“…Currently, these domains are defined based on functions or bus technologies using a "best engineering practice" approach [1,2]. When using a domainbased approach and concentrating functions that are united by some criteria to specific domains, e.g., body control, powertrain, and telematics, it is expected that communication inside the domains should increase and communication between domains decrease.…”