What is the background and motivation of Ethernet 10BASE-T1S?

The primary motivation behind 10BASE-T1S was to bring Ethernet capabilities to edge devices in automotive and industrial settings while addressing the specific needs of these environments such as space constraints, electromagnetic interference, and the need for simplified, cost-effective networking solutions.Summary of the background and motivation for Ethernet 10BASE-T1S:

“The CAN bus got us here, but it won’t take us there.”
That’s the sentiment quietly building up in automotive engineering halls.

With the shift toward Software-Defined Vehicles (SDVs) and zonal architectures, OEMs are rethinking how to wire their cars not just physically, but also logically. In this rethink, 10BASE-T1S is beginning to stand out not because it’s fast or flashy, but because it’s the right fit for the right job.

Why Move On from CAN, LIN & FlexRay?

Legacy vehicle networks are like patchwork quilts: CAN for control, LIN for peripherals, FlexRay where needed. These protocols were designed for specific use cases, and they’ve served well but they don’t scale well into tomorrow’s IP-driven world.

Here’s the catch with them:

  • Each has its own wiring, its own protocol stack, and its own bandwidth cap

  • You need gateways to translate data between them that introduces latency, cost, and software complexity

Image: Left---> Device with both Switch & Gateway Right---> Device with only switch feature

In contrast, Automotive Ethernet offers:

  •  IP compatibility (key for cloud & OTA updates)

  •  Higher and more predictable bandwidth

  •  Scalability and simplicity across the entire vehicle

And that’s where 10BASE-T1S earns its place.

 So Why 10BASE-T1S Specifically?

When people hear “Ethernet,” they often think of high-speed, high-cost, or point-to-point links like 100BASE-T1 or 1000BASE-T1.

But 10BASE-T1S plays a very different role:

  • It’s designed for low-speed ECUs (think doors, lights, seat sensors)

  • It allows multiple devices to share a single cable (multidrop)

  • And it eliminates the need for a switch at every corner

That makes it ideal for SDVs, where dozens or hundreds of edge nodes need simple, secure, time-aware connectivity.

What Makes 10BASE-T1S So Useful?

Let’s break it down into the core reasons it matters:

1. All-Ethernet Architecture

Instead of mixing CAN, LIN, and Ethernet, engineers can now use Ethernet for everything. 10BASE-T1S allows edge devices to plug directly into the IP network. No gateways. No translation layers.

2. Wiring Simplicity = Lower Cost

10BASE-T1S uses a single twisted-pair cable that multiple ECUs can share.

No need for:

  • Complex star topologies

  • Excessive connectors

  • Ethernet switches everywhere

You can run 8 or more nodes on the same cable perfect for doors, roofs, seats, HVAC zones, and more.

3. PLCA Enables Collision-Free Access

Here’s the magic: 10BASE-T1S uses PLCA (Physical Layer Collision Avoidance) not CSMA/CD like traditional Ethernet.

Every node is given a turn to transmit (called a Transmit Opportunity).

There’s:

  • No guesswork

  • No collisions

  • No retransmissions

This deterministic access is crucial in automotive use cases especially for real-time signals that can’t afford jitter.

Image showing PLCA

4. Ideal for SDVs and Zonal Design

Zonal architectures need to be:

  • Modular

  • Easily reconfigurable

  • OTA-friendly

10BASE-T1S fits that perfectly. Once all edge ECUs are IP-addressable over Ethernet, updating them is just software deployment, no separate buses, firmware bridges, or interface headaches.

5. Security with MACsec + IKA

A common critique of shared media: “What about security?” 10BASE-T1S supports MACsec (IEEE 802.1AE) for encryption and authentication.But standard MACsec has a delay issue in shared networks.


The workaround? IKA (Infineon’s Intrusion-resistant Key Agreement), which embeds keys inline 10× faster than MKA in many tests. That means you can encrypt the bus even in multidrop setups without losing time.

Technical Nuggets Worth Knowing

From IEEE research and industry papers:

  • 90% of in-vehicle ECUs need ≤10 Mbps → perfect for 10BASE-T1S

  • PLCA guarantees fair access even over half-duplex media

  • IKA reduces key negotiation time drastically, especially with small packets

  • All devices must support PLCA to comply with 10BASE-T1S specs

A Quick Look Inside PLCA (How It Works)

Here’s PLCA simplified:

  1. A coordinator node sends out a BEACON

  2. Each node listens for its turn (TO)

  3. If a node has data → it transmits

  4. If not → the cycle continues to the next node

Benefits:

  •  Fast cycle times

  •  No collisions

  •  Efficient bus usage

All of this happens at the PHY layer, making it robust against noise and electrical interference perfect for harsh automotive environments.

Summary Table

Final Thoughts: Not Just Another Ethernet Spec

10BASE-T1S isn’t about speed, it's about efficiency, simplicity, and unity. It’s a backbone for the edges.

As the automotive world transitions to software-first design, every ECU will need to be network-aware, time-synced, and secure. 10BASE-T1S lets you achieve that cost-effectively and scalably.

It’s not here to replace high-speed Ethernet. It’s here to replace CAN, LIN, and complexity.

And that’s a big deal.