This section lists all major events that are in some way related to Automotive Ethernet. The idea is to give the readers a perspective on the development predecessing and in parallel to the introduction of Automotive Ethernet.

This chapter gives a personal outlook on how the authors see the changes, chances, and challenges in the automotive industry in relation to the introduction of Automotive Ethernet.

This chapter enlightens the framework that allowed Ethernet to be introduced as a new in-vehicle networking technology. It explains the early use cases as well as the infrastructure that was set up in order to support the proliferation of Automotive Ethernet in the automotive industry.

Before adopting Automotive Ethernet, the automotive industry had developed and used a number of in-vehicle networking technologies. This chapter explains why and how in-vehicle networking was done before the advent of Automotive Ethernet. Furthermore, it explains the eco-system the automotive industry is used to working in when adopting new technologies.

Limited power consumption is ever more important. This chapter, therefore, explains the relationship between Ethernet and the power supply and introduces the methods available for power saving when deploying Automotive Ethernet.

This chapter addresses many other aspects that are affected in addition to the direct communication links, when introducing Automotive Ethernet into the vehicle architecture. It describes how the system development process is affected, the software design, the networking architecture, test and qualification, as well as functional safety. Last but not least it shares some important lessons learned.

One of the key advantages to use Automotive Ethernet is the large number of protocols that can be used with it. This chapter explains the options that exist for Quality of Service with the Time Sensitive Networking standards. It furthermore addresses the topic of switches and virtual LANs, of IP-related decisions, and of a communication middleware that enables service-oriented communication also in the in-vehicle network. Furthermore, the basics of Automotive Ethernet related security are described.

In cars, Ethernet has to function under very specific conditions with stringent electromagnetic compatibility and quality requirements. These are true for all electronics, but especially challenging for the communication technologies and the communication links they use. This chapter thus gives an overview on the EMC, channel, and quality requirements Automotive Ethernet (and any other communication technology) has to fulfill.

This chapter gives an overview on the background and main properties of all Automotive Ethernet physical layer technologies currently available, starting from the channel, over PCS, PMA, and multidrop channel access in the case of 10BASE-T1S.

Ethernet was invented more than 40 years ago. Originally intended for the IT industry/data centers, it was adopted in a variety of industries. This chapter explains the main developments in these industries to show the starting point for the automotive industry, when adopting Automotive Ethernet.

Learning Outcomes

After reading this chapter, the reader will be able to:

• List common data types in IoT applications

• Understand the importance of processing

• Explain the various processing topologies in IoT

• Understand the importance of processing off-loading toward achieving scalability and cost-effectiveness of IoT solutions

• Determine the importance of choosing the right processing topologies and associated considerations while designing IoT applications

• Determine the requirements that are associated with IoT-based processing of sensed and communicated data.

Data Format

The Internet is a vast space where huge quantities and varieties of data are generated regularly and flow freely. As of January 2018, there are a reported 4:021 billion Internet users worldwide. The massive volume of data generated by this huge number of users is further enhanced by the multiple devices utilized by most users. In addition to these data-generating sources, non-human data generation sources such as sensor nodes and automated monitoring systems further add to the data load on the Internet. This huge data volume is composed of a variety of data such as e-mails, text documents (Word docs, PDFs, and others), social media posts, videos, audio files, and images, as shown in Figure 6.1. However, these data can be broadly grouped into two types based on how they can be accessed and stored: 1) Structured data and 2) unstructured data.

Structured data

These are typically text data that have a pre-defined structure [1]. Structured data are associated with relational database management systems (RDBMS). These are primarily created by using length-limited data fields such as phone numbers, social security numbers, and other such information. Even if the data is human or machinegenerated, these data are easily searchable by querying algorithms as well as humangenerated queries. Common usage of this type of data is associated with flight or train reservation systems, banking systems, inventory controls, and other similar systems. Established languages such as Structured Query Language (SQL) are used for accessing these data in RDBMS. However, in the context of IoT, structured data holds a minor share of the total generated data over the Internet.

Unstructured data

In simple words, all the data on the Internet, which is not structured, is categorized as unstructured. These data types have no pre-defined structure and can vary according to applications and data-generating sources.