WEBVTT 00:00.000 --> 00:01.200 Automotive Ethernet. 00:01.200 --> 00:03.940 Who uses Automotive Ethernet? 00:03.940 --> 00:06.140 Why use Automotive Ethernet? 00:06.140 --> 00:08.060 And some technologies to know. 00:08.180 --> 00:09.380 Who am I? 00:09.380 --> 00:10.240 Xavier D. 00:10.240 --> 00:13.120 Johnson, otherwise known as Infinite on Twitter. 00:13.120 --> 00:14.880 Born and raised in the Motown. 00:14.880 --> 00:16.720 Hacking around since about 12. 00:16.720 --> 00:18.920 First mentor for Team 94. 00:19.140 --> 00:20.820 Techno J's. 00:20.820 --> 00:23.020 Organizer of DC313. 00:23.020 --> 00:25.140 Director for MySecDetroit. 00:25.140 --> 00:28.220 And I host a show on YouTube called How the Guy Hacked. 00:28.800 --> 00:30.160 Enough about me. 00:30.160 --> 00:34.060 Let's dig into what exactly is Automotive Ethernet. 00:34.200 --> 00:36.460 So electronics in a car. 00:36.540 --> 00:39.260 They're split up into these things called domains. 00:39.260 --> 00:40.560 Powertrain domain. 00:40.560 --> 00:42.440 Body and comfort domain. 00:42.440 --> 00:44.340 The human machine interface. 00:44.340 --> 00:45.640 Driver assistance. 00:45.640 --> 00:46.400 Chassis. 00:46.400 --> 00:54.420 These things do anything from control steering and braking all the way to controlling your radios and your windows and your seating. 00:54.420 --> 01:03.000 As well as allowing humans to be able to interface with controls via interfaces. 01:03.000 --> 01:06.200 Things that actually control the machine. 01:07.140 --> 01:13.880 Automotive Ethernet is a physical network that is used to connect components within a car using wires. 01:13.880 --> 01:19.840 So why was Ethernet not used in vehicles before now? 01:19.840 --> 01:26.280 Well, Ethernet didn't meet the OEM requirements for the automotive market. 01:26.280 --> 01:33.560 Basically 100 megabits per second and above Ethernet has too much radio frequency noise. 01:33.560 --> 01:40.900 Too much alien noise on the wire from other devices inside of the car. 01:40.980 --> 01:50.360 So Ethernet cannot guarantee low latency due to the low microsecond range that is required by vehicles. 01:50.360 --> 01:58.740 And this was a hard requirement to replace any communication that needs fast reaction times. 01:59.060 --> 02:08.640 Also, there was no way for Ethernet to be able to do time syncing between devices and having multiple devices sample data at the same rate. 02:08.640 --> 02:13.360 So what are some of the use cases for automotive Ethernet? 02:13.360 --> 02:23.880 Well, the different drivers of automotive Ethernet come from, of course, those domains that we spoke about earlier. 02:24.360 --> 02:31.700 The complexity of the components and the wiring harness to a vehicle. 02:31.700 --> 02:37.320 The wiring harness is actually the third costliest and third heaviest component in a vehicle. 02:37.320 --> 03:01.940 So talking about costs, there's been a joint study between Broadcom and Bosch that estimated using UTP cable to deliver data at a rate of 100 megabits per second along with the smaller and more compact connectors can reduce connectivity costs up to 80% and cabling weight down by 30%. 03:01.940 --> 03:19.960 So, you know, when we talk about the data rates via unshielded twisted pair, you know, the electronics in cars are becoming much more complicated, more controllers, more sensors, more interfaces, and all of this stuff requires higher bandwidth. 03:19.960 --> 03:26.860 So these are some of the drivers behind the main motivators behind using automotive Ethernet. 03:26.860 --> 03:48.740 So technologies that are entering the automotive space include self-driving connected cars, augmented reality, vehicle-to-vehicle communications, and things like self-driving require lasers and radars that can process anything, things much more faster than humans can and more reliably than humans. 03:48.740 --> 04:09.620 And we can use these tools and these advancements to be able to do things more efficiently and more effectively on the road doing things like platooning where cars get close to one another so that they can occupy less space on the road and parking very closely in parking spaces. 04:09.720 --> 04:25.080 Augmented reality, things like dashboards for the driver to be able to look through the windshield and see things at a distance and be able to understand exactly, you know, what those things are and categorize them and how far exactly they are away, how fast the driver's moving towards it. 04:25.080 --> 04:30.120 If there's danger, you know, arrows could appear and let you know exactly how to avoid the danger. 04:30.200 --> 04:35.080 And these technologies are considered for passengers as well, right? 04:36.220 --> 04:55.920 Connected cars, which we're living through right now with the advancements in cellular and Wi-Fi connectivity, this allows us to be able to communicate and do video streaming as well as remote diagnostics and updating firmware, which usually require access to the internal networks and computers in cars. 04:55.920 --> 05:03.730 So vehicle-to-vehicle communications allow cars to be able to speak to one another. 05:03.960 --> 05:12.630 The NHTSA estimates that by using VtoV, 79% of target vehicle crashes would be avoided. 05:12.630 --> 05:27.150 So we're talking about huge benefits and safety just by allowing us to be able to increase the amount of technology censoring in the vehicles, but we're going to have to have networks that can actually handle that bandwidth and capability. 05:28.310 --> 05:30.690 Digging deeper into these technologies, right? 05:30.690 --> 05:51.270 So AutoSAR, the Automotive Open System Architecture, One Pair Ethernet, otherwise known as OPEN, Power Over Ethernet or PoE, Energy Efficient Ethernet, EEE, Time Synchronization, as we talked about that being a problem before, AV Bridging, Diagnostics over IP, 05:51.270 --> 05:55.410 which is extremely exciting, and Time Triggered Ethernet. 05:55.730 --> 06:03.930 So digging into AutoSAR, it's an open, standardized automotive architecture jointly developed by manufacturers and tool developers. 06:04.490 --> 06:22.290 TCP, UDP, IP stack that is used in automotive components and is basically the standard that all of the automotive industry came together and decided to agree on versus just fragmenting out and working in silos. 06:22.810 --> 06:30.870 Broadcom made a physical chip, a PHY, a standard called Broad R-Reach. 06:30.870 --> 06:39.430 This is allowing us to be able to enable longer distance copper Ethernet connectivity at a sustained 100 megabits per second. 06:39.430 --> 06:49.350 It's using technology from 1GE copper, including multi-level PAM3 signaling, better encoding, echo cancellers. 06:49.350 --> 06:54.630 These allow for bi-directional data flows on a single pair. 06:54.850 --> 07:03.990 Due to lower bandwidth, standard met the automotive EMI requirements and Broadcom started marketing this to the automotive world. 07:03.990 --> 07:05.670 Power over Ethernet. 07:05.910 --> 07:16.510 It's used to further reduce the wiring needed since you can actually power the end devices as well as sending data over that wire at the same time. 07:16.570 --> 07:25.670 So you're able to power the device as well as get data over it without the need for having extra wiring to power the device. 07:26.230 --> 07:28.250 Energy efficient Ethernet. 07:28.330 --> 07:36.310 So when you're dealing with cars, not all of the electrical components turn off when the engine is turned off. 07:36.310 --> 07:46.710 So with that being said, you have a drain on the battery and to minimize that, energy efficient Ethernet turns off the network when it's not in use. 07:46.710 --> 07:51.530 So the components that don't need to be powered on stay off until the engine turns on. 07:51.570 --> 07:58.150 This is to help with minimizing power consumption. 07:59.370 --> 08:00.950 And so time synchronization. 08:00.950 --> 08:01.850 We talked about this. 08:01.850 --> 08:03.070 Time is a must. 08:03.070 --> 08:06.470 It needs to be synchronized between all the nodes in the car. 08:06.770 --> 08:23.390 So the IEEE 802.1AS, timing and synchronization for time sensitive applications and bridge local area networks is the standard to actually synchronize timing. 08:23.390 --> 08:29.590 This uses a profile and introduces simpler, faster methods for choosing a master clock. 08:30.690 --> 08:32.970 Time triggered Ethernet. 08:32.970 --> 08:38.270 Many controls in the car require communication latency in a single microsecond range. 08:38.270 --> 08:38.790 Literally. 08:38.790 --> 08:44.650 So controllers can get sensor readings to control functions of vehicles. 08:44.650 --> 08:52.510 And if we're talking about self-driving cars, we want to make sure that the sensors have communication latency that is extremely low. 08:52.510 --> 08:58.630 So time triggered Ethernet simplifies the design of this, creates fault tolerance and high availability. 08:58.630 --> 09:07.850 The safety and redundancy are maintained upstream at the network level without any need for the application to be involved. 09:08.190 --> 09:23.710 So for AV bridging, 802.1QAT, also known as stream reservation, is a simple protocol to notify the various network elements in a path to reserve the resources needed to supply a particular stream. 09:23.710 --> 09:37.930 And 801.1QAV, the queuing and forwarding for AV bridges, defines rules to ensure that an AV stream will pass through the networks within the delayed specified time in the reservation. 09:41.010 --> 09:53.450 ISO 13400 is a standard that is adopted by the automotive industry to both read out diagnostics from the computers in the car and update firmware in a car. 09:53.450 --> 09:57.510 So this covers our diagnostics over IP portion. 09:57.650 --> 10:06.730 The protocols run over TCP IP and are used both on dedicated diagnostics Ethernet connections as well as over the air system such as GM OnStar. 10:08.490 --> 10:09.790 Thank you very much. 10:09.790 --> 10:17.430 I hope that you learned a few new things about automotive Ethernet and if you have any questions, please don't hesitate to hit me up on Twitter. 10:20.270 --> 10:28.870 All right, Infinite, thank you very much for such a great overview of the automotive Ethernet. 10:30.350 --> 10:35.370 Infinite will be available on the Discord channel. 10:35.730 --> 10:44.330 There's no real questions for him right now, but if you need to get in touch with him, he will be on the Discord channel, Infinite. 10:46.050 --> 10:52.870 So if you do have questions about automotive Ethernet later, please get in touch with him directly. 10:53.570 --> 11:08.230 All right, guys, we're getting down to the last talks here and the next talk is going to be about cloud to car communication. 11:08.330 --> 11:21.770 And if you guys have ever heard anything about MQTT before, well, don't worry if you haven't because we will talk about it here in about 47 minutes. 11:21.770 --> 11:30.670 So the next talk, we're going to be talking about this MQTT standard and how to use it to hack your own car. 11:30.670 --> 11:33.980 So looking forward to that with Jamie. 11:34.760 --> 11:40.960 All right, so we'll see you back here in about 47 minutes with the next talk.