Contents
StandardIEEE

IEEE 802.3cg (10BASE-T1S)

Physical layer specifications and management parameters for 10 Mb/s operation and associated power delivery over a single balanced pair of conductors

IEEE 802.3cg defines Ethernet communication at 10 Mb/s over one wire pair, including 10BASE-T1S for connecting small devices on a shared automotive network.

What it is

IEEE 802.3cg is an amendment to the Ethernet standard that introduced communication at 10 Mb/s over a single balanced pair of conductors. It includes two physical-layer families: 10BASE-T1S for short-reach connections, including shared multidrop segments, and 10BASE-T1L for longer-reach point-to-point connections. In automotive zonal architectures, 10BASE-T1S is the main focus. IEEE technical overview

A physical layer, or PHY, turns Ethernet data into electrical signals and back again. This lets relatively small sensors, actuators and controllers participate in an Ethernet network. Several devices can share a 10BASE-T1S wire pair instead of each needing a separate switched connection.

Who it applies to

The document is relevant to PHY suppliers, ECU hardware developers, harness designers and engineers integrating automotive Ethernet networks. A vehicle manufacturer or supplier uses it when specifying and verifying a compatible physical connection.

For a zone controller, it informs how an Ethernet segment reaches nearby edge nodes. For an edge ECU, it informs the transceiver and communication interface. Application developers mainly need to understand the resulting bandwidth, latency and failure behavior.

It is a technical interoperability standard. Compliance with it alone does not establish vehicle functional safety, cybersecurity or suitability for a particular control function.

What it covers

The amendment specifies physical-layer behavior, associated management parameters and changes related to power delivery over a single pair. Its scope includes the following elements. IEEE technical overview

Element Engineering meaning
10BASE-T1S Short-reach Ethernet with support for a shared medium
10BASE-T1L Longer-reach, point-to-point single-pair Ethernet
PHY management Controls and status used to configure and monitor the link
Physical Layer Collision Avoidance (PLCA) Optional coordination of transmission opportunities on a shared T1S segment

PLCA coordinates when participating nodes may transmit, reducing contention and making medium access more predictable. It operates with the Ethernet MAC, which handles frame transmission. It does not assign application priorities or guarantee an entire application’s deadline. Traffic volume, frame sizes, configuration and processing delays still matter. IEEE PLCA overview

The power-delivery scope needs careful interpretation: selecting a 10BASE-T1S PHY does not automatically provide power to every node on a multidrop harness. The intended power topology and applicable specifications need separate verification.

How it fits with other documents

IEEE 802.3cg belongs to the broader IEEE 802.3 Ethernet family. Engineers should consult the applicable consolidated standard and check the current edition when preparing requirements or compliance evidence.

IEEE 802.1 documents address complementary bridging and network functions. IP, transport protocols, diagnostics and application middleware sit above the physical connection. Consequently, 10BASE-T1S can provide connectivity for a smart node without defining its middleware contract or service behavior.

Automotive integration also needs applicable channel, EMC, environmental and supplier requirements. IEEE provides no-cost access to published Ethernet standards through its standards access program; commercial copies are also offered. IEEE access guidance

In practice

Begin with the edge devices and their communication needs. Estimate aggregate traffic and acceptable delays, then decide which devices can share a segment. The 10 Mb/s rate is shared capacity, and useful application throughput is lower after communication overhead.

Agree on the PHY capabilities, harness topology, PLCA settings and initialization responsibilities across suppliers. Validate startup, peak traffic, node resets and the effects of a disconnected or malfunctioning device.

Finally, test communication through the complete ECU software path. A working electrical link is only one part of delivering timely, dependable application data.

What it means for your discipline

  • Networks & communicationCore

    Defines segment topology, shared bandwidth and PLCA configuration. Network engineers must assess access delays and validate communication under realistic traffic and fault conditions.

  • Hardware & siliconCore

    Guides PHY selection and the electrical design of the wire pair, coupling and board interface. Hardware engineers must validate the complete channel, including harness effects and electromagnetic compatibility.

  • E/E architecturePartial

    Helps determine which edge devices can share an Ethernet segment behind a zone controller. Architects must account for shared capacity and the effect of segment faults on multiple functions.

  • Base softwarePartial

    Affects Ethernet driver integration, PHY management and PLCA initialization. Basic software must configure the selected hardware consistently and expose useful communication fault information.

  • Functional safetyPartial

    Provides link behavior that informs communication failure analysis. Safety engineers must assess shared-segment failures and any additional end-to-end protection required by the function.

  • CybersecurityPartial

    A shared segment affects exposure to traffic observation and disruption. Security engineers must define protection and isolation above the physical link; PLCA does not authenticate devices.

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