IEEE 802.3cz vs V-PON: Architecture, Latency, Wiring, and Automotive Use Cases

As vehicle architectures move toward centralized computing and zonal control, in-vehicle networks must carry increasing volumes of camera, LiDAR, sensor, display, diagnostic, and control traffic. This raises requirements for bandwidth, predictable latency, fault containment, cable weight, electromagnetic compatibility, and network scalability.

Two optical approaches are receiving attention: IEEE 802.3cz automotive optical Ethernet and vehicular passive optical networking, or V-PON.

IEEE 802.3cz defines high-speed Ethernet physical layers for dedicated optical links. V-PON proposes a shared point-to-multipoint optical-distribution architecture. The engineering question is not which technology is universally better, but which architecture fits a specific traffic pattern, timing requirement, endpoint count, failure model, and vehicle platform.

Centralized and zonal architectures consolidate computing into fewer high-performance controllers while connecting cameras, sensors, displays, actuators, and other devices through regional nodes.

This concentrates several traffic classes within the vehicle:

• High-bandwidth sensor streams

• Deterministic control communication

• Low-rate body-control messages

• Diagnostics and maintenance traffic

• Infotainment and display data

• Software-update traffic

Copper remains suitable for many automotive interfaces, especially at lower data rates. However, as link rates and endpoint counts increase, copper networks face greater pressure in bandwidth, electromagnetic compatibility, cable mass, shielding, and routing complexity.

Optical fiber is immune to electromagnetic interference along the transmission medium and can support high data rates with lower cable mass. However, automotive deployment still requires qualified connectors, transceivers, cable retention, bend control, contamination management, temperature performance, vibration resistance, and practical repair procedures.

IEEE 802.3cz defines point-to-point automotive optical Ethernet PHYs, while V-PON proposes a point-to-multipoint network in which a central optical terminal communicates with multiple endpoints through passive optical distribution.

IEEE 802.3cz-2023 defines automotive glass-fiber Ethernet PHY specifications for 2.5, 5, 10, 25, and 50 Gb/s BASE-AU operation.

An individual BASE-AU connection is a dedicated optical link between two Ethernet interfaces. These links may connect sensors, controllers, switches, zonal nodes, or central computing platforms.

A point-to-point link does not mean the complete vehicle network must contain only two-node connections. IEEE 802.3cz links can be combined with switches and bridges to create star, zonal, or hierarchical Ethernet architectures.

Its main advantage is continuity with Ethernet. Each link has dedicated bandwidth, while existing Ethernet-oriented software, switching, diagnostics, and network-management experience may be reused.

V-PON applies passive optical-network principles to the vehicle environment. A proposed architecture normally includes:

• An optical line terminal, or OLT

• Passive optical splitters

• Multiple optical network units, or ONUs

Several ONUs share the same optical-distribution structure. Downstream data is distributed from the OLT, while upstream traffic must be scheduled and aggregated.

This structure can reduce duplicated home-run data cables in endpoint-dense areas. It also introduces shared bandwidth, scheduling, optical-budget, endpoint-management, and central-node dependencies.

In the 2025 paper “Trends in Vehicular Optical Communication and Suggestions for Developing Vehicular Passive Optical Networks”, Chen Shanzhi and Luo Wenyong present V-PON as a proposed architecture and recommend developing dedicated specifications. It is therefore more accurate to describe V-PON as an emerging standardization route rather than an already completed national standard.

                                 Point-to-Point IEEE 802.3cz vs Point-to-Multipoint V-PON Topology

A dedicated optical link gives each endpoint an independent physical path and line rate. Traffic on another connection does not directly consume its capacity.

This simplifies bandwidth planning and can limit a link failure to a small part of the network. The trade-off is that additional endpoints usually require more PHY ports, connectors, fibers, and switch capacity.

V-PON allows multiple endpoints to share part of the same optical path. A passive splitter does not require powered packet-processing electronics at the branch point.

However, upstream access, endpoint management, timing, and bandwidth assignment must be coordinated by the OLT and the V-PON protocol.

The supported endpoint count is not universal. It depends on optical budget, aggregate traffic, scheduling, connector loss, redundancy, and the final implementation specification.

A small number of high-bandwidth cameras, LiDAR units, or computing modules often favors dedicated optical links.

A large group of lower-bandwidth body sensors, door controllers, or lighting nodes may benefit from shared distribution. The result depends on actual traffic demand and total system cost rather than endpoint count alone.

Network latency includes:

1. PHY and transceiver delay

2. Fiber-propagation delay

3. Switching, queuing, or scheduling

4. Endpoint processing

Optical media alone does not determine end-to-end performance.

Dedicated full-duplex links do not require multiple endpoints to compete for one upstream transmission window. This removes one source of variable access delay.

However, no single sub-microsecond figure describes every IEEE 802.3cz network. PHY delay varies by rate and implementation, while switching, queuing, scheduling, propagation, and endpoint processing also contribute to total latency.

IEEE 802.3cz defines the optical PHY. It does not itself provide a complete TSN system.

IEEE 802.1DG-2025 defines an automotive in-vehicle TSN profile for bridged IEEE 802.3 Ethernet networks. Deterministic operation therefore depends on the combined PHY, switch, TSN, synchronization, and traffic-scheduling design.

In V-PON, several ONUs share upstream capacity. A scheduling mechanism determines when each endpoint may transmit.

Actual delay and jitter depend on:

• Frame structure

• Scheduling-cycle length

• Reserved bandwidth

• Dynamic bandwidth allocation

• Network load

• Synchronization

• OLT processing

TDM does not automatically make V-PON unsuitable for a vehicle function. Performance depends on how the shared network is designed and validated.

The 2025 V-PON proposal targets transmission delay below 100 microseconds and tighter synchronization for selected future designs. These remain proposal-level targets rather than standardized or independently validated production limits.

Names such as TS-PON or TSN-PON do not by themselves prove that an implementation satisfies a deterministic-latency or safety requirement.

                                       Dedicated-Link Transmission vs Shared-Timeslot Scheduling

More point-to-point endpoints generally require additional:

• PHY ports

• Transceivers

• Connectors

• Fiber paths

• Switch capacity

The resulting optical harness may still be lighter than a comparable high-speed copper design, but point-to-point networking does not automatically minimize cable count.

A shared V-PON trunk can reduce repeated data paths where several devices communicate mainly with one central or zonal controller.

A passive splitter can also simplify the branch point. However, each ONU still requires power, an optical interface, diagnostics, mechanical protection, and integration with the endpoint electronics.

No fixed wiring-reduction percentage applies to every vehicle.

The result depends on:

• Endpoint number and location

• Baseline network topology

• Cable and jacket construction

• Connector and transceiver mass

• Redundant paths

• Remaining power wiring

• Routing requirements

V-PON can reduce duplicated data cables in a suitable layout, but the actual saving must be calculated at vehicle level.

                                Optical Link and Port Scaling as Vehicle Node Count Increases

A failure in one point-to-point optical link may affect only the devices connected through that path. This supports relatively direct diagnosis.

The trade-off is a greater number of active interfaces and physical connections, each of which may become a failure point.

A passive splitter contains no powered packet-processing electronics, but this does not make the complete V-PON system inherently more reliable.

Availability still depends on:

• OLT and ONU electronics

• Optical transceivers

• Connectors and fibers

• Power supplies

• Timing and scheduling

• Fault detection and recovery

If one OLT serves several critical devices, an OLT or shared-trunk failure may affect all of them. Redundant paths or central nodes may therefore be required.

                                            Fault Domains in IEEE 802.3cz and V-PON Networks

The optical harness must be qualified separately from the PHY.

ISO 24581:2024 defines performance requirements and test methods for in-vehicle optical harnesses supporting up to 100 Gbit/s per fiber channel.

The OPEN Alliance automotive Ethernet specifications include complementary optical-harness and nGBASE-AU system-testing requirements.

PHY compliance alone is not sufficient to qualify a complete automotive optical link.

IEEE 802.3cz preserves the Ethernet physical-layer and frame environment. This may allow reuse of Ethernet switches, network management, diagnostics, and engineering tools.

However, TSN, diagnostics, and OTA are not functions contained inside the IEEE 802.3cz PHY.

The AUTOSAR Diagnostic over IP specification treats DoIP as a separate software module aligned with ISO 13400. DoIP is therefore an upper-layer diagnostic function transported over an IP network.

A V-PON system requires a defined method for transporting Ethernet, legacy vehicle-bus traffic, camera streams, display data, and control messages.

Possible methods include gateways, encapsulation, traffic adaptation, and centralized scheduling. These functions affect software, diagnostics, test equipment, and system validation.

Cable and connector prices alone are not sufficient for comparison. Total cost can include:

• PHYs or OLT/ONU devices

• Switches, splitters, and gateways

• Software integration

• Timing and scheduling design

• Verification and safety analysis

• Harness qualification

• Production testing

• Service and repair procedures

V-PON may reduce repeated links but increase protocol and central-controller complexity. IEEE 802.3cz may simplify Ethernet migration but require more independent optical interfaces.

IEEE 802.3cz is a strong candidate for high-bandwidth sensors and central-compute links because it provides dedicated capacity and integrates with Ethernet switching and TSN systems.

It is not the only technically possible architecture for every automated-driving platform. Suitability depends on the complete safety case, including timing, redundancy, error detection, fault containment, and endpoint behavior.

V-PON proposals also consider intelligent-driving traffic, but safety-critical use still requires standardized protocols and independently validated latency, reliability, and recovery performance.

Cockpit and body systems often contain many endpoints with very different bandwidth requirements.

Shared optical distribution may be attractive when these endpoints communicate mainly with one zonal or central controller. However, low-rate devices may remain more economical on established electrical vehicle buses.

V-PON should therefore be selected only where cable-sharing and aggregation benefits justify the cost of ONUs, protocol adaptation, and central management.

                            IEEE 802.3cz and V-PON Engineering Application Selection Matrix

IEEE developed and published IEEE 802.3cz within the global Ethernet standards system. The OPEN Alliance supports implementation through harness, interoperability, compliance, and testing specifications.

This ecosystem includes PHYs, switches, connectors, harnesses, laboratories, tools, and engineering experience. Existing investment in technologies such as 100BASE-T1 and 1000BASE-T1 may reduce migration barriers to optical Ethernet.

V-PON aims to adapt telecom PON principles to automotive requirements. This involves more than shortening transmission distance.

Vehicle-specific work is required for:

• Temperature and vibration

• Compact packaging

• Deterministic traffic

• Fault diagnosis

• Redundancy

• Long service life

A dedicated automotive protocol and specification framework is therefore necessary. V-PON cannot be treated as a conventional FTTH network installed inside a vehicle.

Technology adoption is also influenced by chip availability, connector qualification, tooling, supplier experience, production scale, and existing software investment.

An established Ethernet ecosystem may reduce development risk. A developing V-PON ecosystem may create alternative component and architecture options.

Technical selection should not rely on unsupported claims about complete localization, monopoly positions, or inevitable regional alignment.

IEEE 802.3cz is generally favored for dedicated high-bandwidth links, Ethernet continuity, and controllable fault domains.

V-PON becomes attractive when many endpoints communicate with one central node and shared distribution can reduce repeated cabling.

Both approaches require validation of optical loss, connectors, temperature, vibration, redundancy, diagnostics, safety behavior, production testing, and repair procedures.

A vehicle could use dedicated IEEE 802.3cz links for high-bandwidth or timing-critical devices and shared optical distribution for suitable endpoint groups.

Such a hybrid system would still require gateway design, synchronization, endpoint management, diagnostics, fault control, and redundancy.

It remains one possible architecture rather than a confirmed industry-wide solution.

IEEE 802.3cz and V-PON address different architectural needs.

IEEE 802.3cz provides standardized automotive optical Ethernet PHYs from 2.5 to 50 Gb/s. Its strengths are dedicated bandwidth, Ethernet compatibility, and relatively narrow link-level fault domains.

V-PON proposes shared optical distribution through an OLT, passive splitters, and multiple ONUs. Its main potential advantage is reducing duplicated data links in endpoint-dense networks.

The key trade-offs are:

• Dedicated versus shared bandwidth

• Independent links versus common infrastructure

• Ethernet reuse versus protocol adaptation

• Narrow fault domains versus OLT dependency

• Published standardization versus an emerging route

Real-time behavior must be evaluated end to end. IEEE 802.3cz is not deterministic merely because its PHY is fast, and V-PON is not unsuitable merely because it uses shared scheduling.

IEEE 802.3cz uses dedicated point-to-point Ethernet links. V-PON allows multiple endpoints to share an optical-distribution network.

Potentially, but bandwidth, latency, jitter, redundancy, and safety behavior must be validated for the specific implementation.

Yes, shared trunks can reduce duplicated data cables. The actual saving depends on the vehicle layout and network design.

No. IEEE 802.3cz defines the optical PHY. TSN and DoIP are separate higher-layer technologies.

It usually provides narrower fault domains, but complete reliability depends on switches, OLTs, connectors, power, redundancy, and diagnostics.

Yes. Dedicated links and shared distribution can be used for different traffic groups if the complete system is properly integrated and validated.