Ten gigabits per second seemed like a lot when IEEE 802.3ch was approved in 2020. For the central computers and zonal backbones of autonomous and software-defined vehicles, it is no longer enough. IEEE 802.3cy, approved in 2023, defines 25GBASE-T1, 50GBASE-T1 and 100GBASE-T1 — electrical automotive PHYs that push a single shielded pair further than ever. The specification work of the NAV Alliance’s TWG1/TWG2 working group focused on exactly these speeds.
Key takeaways
- Aggregated sensor traffic, compute-to-compute links and storage are driving backbone requirements beyond 10 Gb/s.
- IEEE 802.3cy specifies 25, 50 and 100 Gb/s full-duplex PHYs for automotive use over a single shielded differential pair.
- At these speeds the channel — cables, connectors and PCB — and EMC behaviour determine success as much as the PHY silicon.
- NAV Alliance TWG1/TWG2 defined use cases, channel specifications and RF-ingress limit lines for 25G/50G links, including asymmetric cases.
Why the vehicle needs more than 10 Gb/s
Consider a zonal controller at the front of a vehicle connected to four high-resolution cameras, two imaging radars and a lidar. Even with light compression, those sensors can together produce well over 10 Gb/s. The link from that zone to the central computer must carry all of it plus control, diagnostics and headroom. Central computers themselves are increasingly split across multiple systems-on-chip or boards that exchange raw and fused sensor data; high-speed storage for logging and over-the-air updates adds more. A 25 Gb/s or 50 Gb/s backbone link replaces several parallel 10 Gb/s links, saving cable weight and connector count.
| Use case | Typical requirement | Suitable PHY |
|---|---|---|
| Zone → central compute (sensor aggregation) | 15 – 40 Gb/s | 25GBASE-T1 / 50GBASE-T1 |
| Compute ↔ compute (redundant AI computers) | 25 – 100 Gb/s | 50GBASE-T1 / 100GBASE-T1 |
| Compute → data logger (development fleets) | 25 – 50 Gb/s | 25GBASE-T1 / 50GBASE-T1 |
| High-resolution sensor (asymmetric) | 10 – 25 Gb/s uplink | Asymmetric variants |
What IEEE 802.3cy specifies
IEEE 802.3cy is an amendment to IEEE 802.3 titled “Physical Layer Specifications and Management Parameters for Greater than 10 Gb/s Electrical Automotive Ethernet”. It defines three PHY types — 25GBASE-T1, 50GBASE-T1 and 100GBASE-T1 — that operate full-duplex over a single balanced pair, together with the link segment (channel) characteristics, management registers, and optional features aligned with the earlier 802.3ch PHYs. Reusing concepts from 802.3ch, such as single-pair operation, PAM4 signalling, Reed-Solomon forward error correction and fast link start-up, made it easier for silicon vendors and car makers to scale their designs.
The target channels are shorter than in 802.3ch at the highest speed, reflecting the physics: at 50 or 100 Gb/s the signal occupies a much wider frequency band, and cable insertion loss rises with frequency. Car makers therefore place the highest-speed links between devices that are physically close — for example between computers in the same compute box or between a central computer and a nearby zone.
Signal processing at 25G and beyond
Modulation
Four-level pulse amplitude modulation (PAM4) carries two bits per symbol, halving the symbol rate compared with two-level signalling for the same data rate. The trade-off is a smaller vertical eye opening — each level is only one third of the total swing — which makes the signal more sensitive to noise. The PHY compensates with stronger equalization and error correction.
Forward error correction
Reed-Solomon FEC adds parity symbols that let the receiver correct bursts of errors. Automotive PHYs size the FEC to correct the burst noise produced by RF ingress and transient disturbances, so that the frame-loss rate stays extremely low — a necessity when the link carries safety-relevant sensor data.
Echo cancellation and equalization
Full-duplex on one pair means each PHY receives a faint far-end signal on top of its own strong transmitted signal and its reflections from every connector. Echo cancellers model and subtract these components; decision-feedback and feed-forward equalizers remove inter-symbol interference caused by the cable. All of this must be implemented at automotive temperatures and within a tight power budget.
The channel is the hard part
Above 10 Gb/s, the link segment becomes the dominant design challenge. NAV Alliance TWG1/TWG2 set out to define 25 Gb/s (and possibly 50 Gb/s) channel specifications based on target network topologies, covering both the link segment and the MDI-to-PHY chip channel on the PCB, with limit lines for insertion loss, return loss and crosstalk, and refinements for cable return loss and micro-reflections. Key parameters include:
- Insertion loss — attenuation along the channel at the Nyquist frequency and below.
- Return loss and micro-reflections — reflections from impedance discontinuities in connectors and cable manufacturing; at high speed even small periodic variations create notches in the channel response.
- Mode conversion — conversion between differential and common-mode signals, which governs both emissions and susceptibility.
- Alien crosstalk and coupling — interference from neighbouring cables in the harness.
Our guide to cables and connectors for Multi-Gig covers these in detail.
EMC: designing for the real vehicle
The TWG1/TWG2 charter also included defining the EMC requirements of 25G (and possibly 50G) Ethernet links — characterizing and measuring RF ingress over target channels (cables, connectors and modules) and defining limit lines for RF ingress levels at PHY inputs. These limits let PHY designers know what disturbance their receivers must tolerate, and let harness and connector suppliers know how much shielding and balance they must deliver. Read our article on EMC for Multi-Gig automotive Ethernet.
Symmetric and asymmetric use cases
The working group explicitly considered both symmetric links (backbones, compute interconnect) and asymmetric links (high-resolution sensors). It weighed requirements such as cable quality and reach, the number of inline connectors, Power over Data Lines (PoDL) and error tolerance against cost, the number of cables, connector complexity and PHY complexity. That holistic trade-off — rather than chasing the highest possible data rate — is characteristic of automotive engineering.
Integration into ECUs and computers
A 25G or 50G PHY is only as good as its integration. NAV Alliance TWG3 addresses power supply dimensioning, PCB design rules for signal integrity, additional components on the board, link diagnosis, power dissipation and host CPU interconnection for Multi-Gig PHYs. At these speeds, PCB losses and via stubs can consume a significant share of the channel budget, so board design must follow high-speed practices familiar from data-center hardware while meeting automotive reliability requirements.
Optical alternative: IEEE 802.3cz
For links where EMC is especially critical or weight must be minimized, IEEE 802.3cz defines multi-gigabit optical automotive Ethernet over multimode glass fibre at rates from 2.5 to 50 Gb/s. Optical links are immune to electromagnetic interference but bring their own challenges in connector cleanliness, bend radius and harness assembly. Many architectures are expected to mix electrical and optical links.
Frequently asked questions
When will 25G automotive Ethernet be in production vehicles?
Silicon supporting 802.3cy rates has been announced by several suppliers, and car makers are designing it into next-generation central-compute platforms. Exact timing depends on each OEM’s program.
Can a 25GBASE-T1 PHY talk to a 10GBASE-T1 PHY?
They are different PHY types. Some silicon supports multiple speeds, but a link operates at one defined PHY type at both ends.
Does higher speed mean shorter cables?
Generally yes, for a given cable quality. Link reach is a trade-off between data rate, cable and connector performance, and cost.
How can I contribute to future specifications?
Engineers from Promoter and Contributor companies can join NAV Alliance working groups. Become a member.
Updated November 2026. Summaries of IEEE 802.3cy are informative; the IEEE standard is normative.