Automotive Ethernet. Who uses Automotive Ethernet? Why use Automotive Ethernet? And some technologies
to know. Who am I? Xavier D. Johnson, otherwise known as Infinite on Twitter. Born and raised
in the Motown. Hacking around since about 12. First mentor for Team 94. Techno J's.
Organizer of DC313. Director for MySecDetroit. And I host a show on YouTube called How the
Guy Hacked. Enough about me. Let's dig into what exactly is Automotive Ethernet. So electronics
in a car. They're split up into these things called domains. Powertrain domain. Body and
comfort domain. The human machine interface. Driver assistance. Chassis. These things do
anything from control steering and braking all the way to controlling your radios and
your windows and your seating. As well as allowing humans to be able to interface with
controls via interfaces. Things that actually control the machine. Automotive Ethernet is
a physical network that is used to connect components within a car using wires. So why
was Ethernet not used in vehicles before now? Well, Ethernet didn't meet the OEM requirements
for the automotive market. Basically 100 megabits per second and above Ethernet has too much radio
frequency noise. Too much alien noise on the wire from other devices inside of the car. So
Ethernet cannot guarantee low latency due to the low microsecond range that is required by
vehicles. And this was a hard requirement to replace any communication that needs fast reaction
times. 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. So what are some of the use cases for
automotive Ethernet? Well, the different drivers of automotive Ethernet come from, of course,
those domains that we spoke about earlier. The complexity of the components and the wiring
harness to a vehicle. The wiring harness is actually the third costliest and third heaviest
component in a vehicle. 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%. 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. So
these are some of the drivers behind the main motivators behind using automotive Ethernet.
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. 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. 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. If there's danger, you know, arrows could appear and let you know exactly how to avoid
the danger. And these technologies are considered for passengers as well, right? 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. So vehicle-to-vehicle communications allow cars to be able to speak to one another.
The NHTSA estimates that by using VtoV, 79% of target vehicle crashes would be avoided.
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. Digging deeper into these technologies, right? 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, which is extremely
exciting, and Time Triggered Ethernet. So digging into AutoSAR, it's an open,
standardized automotive architecture jointly developed by manufacturers and tool developers.
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. Broadcom made a physical chip, a PHY,
a standard called Broad R-Reach. This is allowing us to be able to enable longer distance
copper Ethernet connectivity at a sustained 100 megabits per second. It's using technology
from 1GE copper, including multi-level PAM3 signaling, better encoding, echo cancellers.
These allow for bi-directional data flows on a single pair. Due to lower bandwidth,
standard met the automotive EMI requirements and Broadcom started marketing this to the automotive
world. Power over Ethernet. 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. 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. Energy efficient Ethernet. So when you're dealing with cars, not all of
the electrical components turn off when the engine is turned off. 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. So the components that don't need to be powered on stay off until
the engine turns on. This is to help with minimizing power consumption.
And so time synchronization. We talked about this. Time is a must. It needs to be synchronized
between all the nodes in the car. So the IEEE 802.1AS, timing and synchronization for time
sensitive applications and bridge local area networks is the standard to actually synchronize
timing. This uses a profile and introduces simpler, faster methods for choosing a master clock.
Time triggered Ethernet. Many controls in the car require communication latency in a single
microsecond range. Literally. So controllers can get sensor readings to control functions
of vehicles. And if we're talking about self-driving cars, we want to make sure that
the sensors have communication latency that is extremely low. So time triggered Ethernet
simplifies the design of this, creates fault tolerance and high availability. The safety and
redundancy are maintained upstream at the network level without any need for the application to be
involved. 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. 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.
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. So this covers our diagnostics over IP
portion. 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.
Thank you very much. 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.
All right, Infinite, thank you very much for such a great overview of the automotive Ethernet.
Infinite will be available on the Discord channel. 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.
So if you do have questions about automotive Ethernet later,
please get in touch with him directly. 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. 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. So the next talk, we're going to be talking about this MQTT standard
and how to use it to hack your own car. So looking forward to that with Jamie.
All right, so we'll see you back here in about 47 minutes with the next talk.