Contents
StandardIEEE

IEEE 802.3 automotive PHYs

Automotive Ethernet physical layers: 100BASE-T1, 1000BASE-T1, 2.5–10GBASE-T1 and optical

IEEE 802.3 automotive PHY specifications define how Ethernet data travels over single-pair copper cables or optical fibre inside a vehicle.

What it is

An Ethernet physical layer, usually called a PHY, converts digital data into signals that can cross a cable or optical fibre and converts received signals back into data. IEEE 802.3 defines Ethernet, including several PHY families suited to vehicles.

“Automotive Ethernet PHYs” is a collection of specifications within that larger standard. Names such as 100BASE-T1 identify a particular physical-layer technology. Amendment identifiers such as 802.3bw identify the documents that originally introduced it; their requirements can later become part of a consolidated IEEE 802.3 edition.

Who it applies to

These specifications matter to PHY suppliers, ECU and switch designers, vehicle network engineers, and teams responsible for cables, connectors and validation. They provide a common technical basis for components from different suppliers to communicate.

They are technical standards rather than vehicle type-approval regulations. A vehicle programme typically makes selected requirements binding through its network specifications, purchasing requirements and supplier agreements. Compliance must refer to a particular PHY and its applicable requirements, rather than a general claim of being “automotive Ethernet compatible.”

What it covers

The main families relevant to this page are:

PHY family Original amendment Main distinction
100BASE-T1 802.3bw 100 Mbit/s over one copper pair
1000BASE-T1 802.3bp 1 Gbit/s over one copper pair
2.5GBASE-T1, 5GBASE-T1, 10GBASE-T1 802.3ch Multi-gigabit operation over one copper pair
10BASE-T1S 802.3cg Short-reach 10 Mbit/s Ethernet, including shared-medium operation
Gigabit plastic optical fibre 802.3bv Optical transmission using plastic fibre
Multi-gigabit automotive glass optical fibre 802.3cz Optical transmission using glass fibre

Depending on the PHY, requirements address signalling, encoding, transmitter and receiver behaviour, link establishment, management and channel characteristics. Copper and optical implementations have different channel constraints and test methods.

Matching speed alone is insufficient: both ends must support compatible PHY types and configurations. Likewise, one copper pair does not mean that all T1 technologies support the same topology. Shared-medium 10BASE-T1S needs different planning from a point-to-point link.

How it fits with other documents

IEEE 802.3 supplies the Ethernet physical-layer and MAC foundation. IEEE 802.1 documents address functions such as bridging, VLANs and time-sensitive networking. IP, transport protocols and middleware operate above these layers.

OPEN Alliance specifications complement IEEE requirements with automotive implementation and test guidance, depending on the technology. Vehicle manufacturers add programme-specific requirements for channel construction, electromagnetic compatibility, environmental durability and system behaviour.

PHY selection also needs coordination with power and sleep arrangements. Do not assume that choosing an IEEE PHY automatically selects a wake-up mechanism, power-delivery method or complete ECU power-state strategy.

In practice

Start with traffic demand, topology, cable routing, environmental conditions and power constraints. Select the PHY family, then record the applicable IEEE edition, amendments and vehicle-specific requirements in the interface specification.

Validate the complete channel, including boards, connectors and harnesses. Plan separate checks for physical-layer conformance, supplier interoperability and vehicle operation under electrical and environmental stress.

During integration, check configuration and link status before investigating higher-layer protocols. A working physical link is the starting point for communication; it does not by itself demonstrate adequate bandwidth, timing, safety or security.

What it means for your discipline

  • Networks & communicationCore

    Select the PHY, link speed and supported topology for each connection. Define interoperability requirements and investigate link establishment or communication failures.

  • Hardware & siliconCore

    Design and validate PHY circuits, board routing, connectors and cable or optical channels against the selected physical-layer requirements.

  • E/E architecturePartial

    Use link capabilities and constraints when allocating functions across ECUs, switches and zones. Balance bandwidth, wiring, power and redundancy needs.

  • Base softwarePartial

    Implement PHY configuration, management and link-state handling. Coordinate driver behaviour with startup, sleep and fault recovery requirements.

  • Diagnostics & lifecyclePartial

    Turn available PHY status and fault indications into useful service diagnostics. Distinguish physical connection faults from higher-layer communication failures.

  • Functional safetyPartial

    Assess how link loss, corruption and recovery affect safety-related communication. PHY conformance alone does not establish functional safety.

  • CybersecurityPartial

    Account for physical access and link disruption in threat analysis. These PHY specifications do not provide application authentication or confidentiality.

No direct stake: HPC & application software · Software update & OTA