# NAV Alliance > The NAV (Networking for Autonomous Vehicles) Alliance is a nonprofit industry consortium that provides a platform for the automotive industry to develop the next generation of in-vehicle network infrastructure for autonomous vehicles — Multi-Gig Automotive Ethernet — and to facilitate wide deployment of networking technologies and products. Key facts: - Official name: NAV Alliance, Inc. (Networking for Autonomous Vehicles Alliance) - Website: https://nav-alliance.org/ - Legal form: Delaware nonprofit corporation; EIN 82-3869081 - Launched: June 2018, San Jose, California, USA - Founding members: Bosch, Continental, Marvell (formerly Aquantia), NVIDIA, Volkswagen Group of America - Contributors include: Amphenol, HARMAN International, Huawei, LEONI Bordnetz-Systeme, Molex, Rosenberger, Sony, Sumitomo Electric, Tektronix - Membership levels: Promoter (USD 20k/yr), Contributor (USD 10k/yr), Adopter (USD 5k/yr) - Technical working groups: TWG1/TWG2 25G/50G Automotive Ethernet PHY & EMC; TWG3 Physical Layer System & Component Integration; TWG4 Protocol Encapsulation for Ethernet; TWG5 System Controls & Management - Topics: Multi-Gig Automotive Ethernet, Asymmetrical Ethernet for cameras and sensors, IEEE 802.3ch, IEEE 802.3cy, zonal architecture, TSN, automotive EMC, MACsec, PoDL - Contact: admin@nav-alliance.org · Media: pr@nav-alliance.org This file contains the full text of the main NAV Alliance pages and technical articles, provided for AI assistants and search systems. Please cite https://nav-alliance.org/ as the source. --- # Home URL: https://nav-alliance.org/ ## Next Generation In-Vehicle Networking Technologies for Autonomous Vehicles The purpose of the NAV Alliance is to provide a platform for the automotive industry to develop the next generation of in-vehicle network infrastructure for autonomous vehicles and facilitate wide deployment of networking technologies and products. The NAV Alliance was founded by leading auto manufacturers and technology providers sharing the goal of developing the ecosystem that is required for next generation Multi-Gig Automotive Ethernet network in the vehicle. The NAV Alliance is promoting Asymmetrical Ethernet for sensor interface. For additional details, please contact our member companies. ## Join the Revolution for the Future of Autonomous Vehicles Team up with industry leaders to define the future of automotive networking. Join the NAV Alliance. --- # Services & Membership URL: https://nav-alliance.org/services/ --- # About Us URL: https://nav-alliance.org/about/ Our story ## The Dawn of a New Era in Automotive The goal to make autonomous driving a reality is creating a paradigm shift in the automotive industry. Revolutionary new ideas and technologies are being developed that will forever change how we conceive and use this mode of transportation, bringing benefits to society in terms of safety, convenience and mobility. But to relinquish control to a machine, trusting it with our lives and those of others, will require a concerted effort to develop new technologies in the area of sensors, computing, algorithms and networking. It will also rely on a new concept for in-vehicle networking, one that is able to deliver rich data at blazing speeds to powerful computing elements inside the vehicle. Why NAV ## The Need for an Advanced Nervous System in the Car This new breed of in-vehicle networking architecture is practically a data-center on wheels. Akin to a very advanced nervous system, it is based on an array of ECUs, CPUs/GPUs, high-definition cameras, sensors, gateways, and storage devices, all connected through a high-speed, Multi-Gigabit/s Ethernet network that seamlessly moves data throughout the vehicle with a focus on redundancy, security and reliability. We call it Networking for Autonomous Vehicles — NAV. ## About the NAV Alliance The charter of the NAV Alliance is to provide a platform for the automotive industry to develop the next generation of in-vehicle network infrastructure for autonomous vehicles, and facilitate wide deployment of networking technologies and products. It was founded by Bosch, Continental, Marvell, NVIDIA, and Volkswagen Group of America, each a leader in their respective segment as an auto manufacturer or technology provider. These founding members share the goal of developing the ecosystem that is required for next generation Multi-Gig automotive Ethernet network in the vehicle. The alliance was publicly launched in June 2018 in San Jose, California. Aquantia — whose multi-gig Ethernet chips were at the core of the alliance's early work — was among the founders; following its acquisition by Marvell in 2019, Marvell became a founding promoter. Since then the membership has grown to include connector and cable makers, wiring-harness suppliers, image-sensor and electronics companies, and test-and-measurement vendors — so that every component of the future in-vehicle network is represented. - - - - - ## The Alliance Objectives ## 01 · Ecosystem Develop the ecosystem for next generation Multi-Gig Ethernet automotive networking. ## 02 · Specifications Create procedures and specifications to ensure interoperability, security and reliability of the network. ## 03 · Best practices Promote best practices and solutions that adhere to the new specifications. ## 04 · Liaisons Establish standards body liaisons, working closely with organizations such as the IEEE. ## 05 · Education Build marketing activities to build awareness and educate the marketplace and users. ## 06 · Interoperability Support third-party testing, certification procedures, plugfests and interoperability demonstrations. ## How the Alliance Works GovernanceMembershipStandardsIntellectual property The Alliance is incorporated in Delaware as a nonprofit corporation, with tax-exempt status (EIN 82-3869081). It is managed by a board of directors comprised of representatives from Promoter member companies — car manufacturers, system suppliers, silicon suppliers, networking and AI computing companies. Representatives from Promoter and Contributor companies join technical and marketing working groups that shape the alliance's specifications and outreach. Any company can apply. There are three levels of participation: Promoter, Contributor and Adopter. Promoters vote on specifications, sit on the board and chair working groups; Contributors participate in and chair working groups; Adopters receive early access to specifications and collateral and take part in alliance events. Compare membership levels → The NAV Alliance builds consensus around new ideas, architectures and technologies that propel Ethernet into Multi-Gigabit speeds inside the car. Technologies emerging from this industry-wide effort are specified by the appropriate bodies; many individuals from member companies participate in IEEE 802.3 work such as the P802.3ch Multi-Gig Automotive Ethernet PHY Task Force, on behalf of their organizations. The NAV Alliance has adopted an IP Rights (IPR) Policy consistent with industry-standard practice used by organizations such as the IEEE. Members agree to license their Necessary Claims to other members on Reasonable And Non-Discriminatory (RAND) terms. Specifications are distributed to member companies according to the bylaws. ## Milestones ## Download the NAV Alliance overview presentation A concise briefing on the alliance's mission, members, working groups and roadmap — ideal for sharing with your engineering and product teams. Download overview (PDF)   Ask a question ## Join the Revolution for the Future of Autonomous Vehicles Team up with industry leaders to define the future of automotive networking. Join the NAV Alliance --- # Membership URL: https://nav-alliance.org/membership/ ## Become a Member The NAV Alliance is currently receiving applications from candidate companies. Members should be willing and able to help drive and support new interoperability requirements, third party testing, certification procedures and higher data rate specification requirements. There are three levels of participation: Promoter, Contributor and Adopter. Please contact us if you are interested in joining the alliance as a member. ## Adopter Early access and a seat at alliance events. $5,000 / year - Access to alliance specifications and collateral before they become public - Participation in internal alliance discussions - Interoperability demonstrations, plugfests and exhibits - Member listing and logo use per guidelines - Working-group participation - Voting on specifications - Board seat Join as Adopter Most popular ## Contributor Shape the specifications from the inside. $10,000 / year - Everything in Adopter - Participate in, and chair, technical and marketing working groups - Participate in task forces - Future right to elect a Contributor representative to the board (subject to board resolution) - Early influence on new Multi-Gig requirements - Voting on specifications - Board seat Join as Contributor ## Promoter Lead the alliance and its direction. $20,000 / year - Everything in Contributor - Vote on proposed specifications - Eligible to sit on the board of directors - Chair task forces and working groups - Participate in all aspects of the alliance - Highest visibility in alliance communications - Strategic input on liaisons with standards bodies Join as Promoter Fees are annual, in US dollars, as published in the alliance FAQ. Membership becomes effective once the member agreement is signed and the invoice is paid. ## Compare benefits BenefitAdopterContributorPromoter Early access to specifications & collateral✓✓✓ Internal discussions & member communications✓✓✓ Plugfests, interoperability demos & exhibits✓✓✓ License to members' Necessary Claims on RAND terms (IPR Policy)✓✓✓ Join Technical (TWG) & Marketing (MWG) working groups–✓✓ Chair working groups and task forces–✓✓ Vote on proposed specifications––✓ Board of directors seat–Elected representative (future)✓ Annual feeUSD 5kUSD 10kUSD 20k ## How to join ## 1. Apply Submit the application below or order a membership level online. ## 2. Review We send the member agreement form, the IPR Policy and the Bylaws. ## 3. Sign & pay Sign the agreement and settle the annual invoice by bank transfer. ## 4. Onboard Get portal accounts for your domain and join working groups. ## Promoters & Contributors Join the companies already shaping the in-vehicle network. ## Interested in joining the NAV Alliance? Please provide the following information. We reply within two business days. --- # Our Members URL: https://nav-alliance.org/members/ NAV Alliance members represent the pinnacle of technology leadership available for autonomous vehicles within their own respective market segments — together they cover every component necessary to support the in-vehicle network in future autonomous vehicles. The alliance was founded by Bosch, Continental, Marvell (formerly Aquantia), NVIDIA and Volkswagen Group of America. Contributor members include connector, cable and wiring-harness specialists, connected-car and image-sensor companies, and test-and-measurement vendors. Use the filters to browse by membership level; each card links to the member's own website. ## Become one of them Any company can apply to join at the Promoter, Contributor or Adopter level. Compare levels and apply, or contact us to request the member agreement, IPR Policy and Bylaws. --- # Working Groups URL: https://nav-alliance.org/working-groups/ ## Technical Working Groups NAV Alliance welcomes the participation of individuals from Promoter and Contributor companies in both technical and marketing activities. Below is an overview of the NAV Alliance working groups. If you are a member and would like to sign up to participate in a working group, please contact the alliance administration. All groups Physical layer System & protocol TWG1 / TWG2 ## 25G/50G Automotive Ethernet PHY Specifications and EMC Requirements Chairman: Ramin Farjad, Marvell Scope: This project is to create Physical Layer specifications and Management Parameters for 25 Gb/s and 50 Gb/s electrical interfaces for automotive Ethernet networks. Objectives: - Define automotive use cases and topologies for 25 Gb/s / 50 Gb/s Ethernet — considerations for both symmetric and asymmetric use cases; defining requirements for cable quality and reach, number of connectors, PoDL requirements and error tolerance, with trade-off considerations for cost, number of cables, connector complexity and PHY complexity. - Define 25 Gb/s (and possibly 50 Gb/s) channel specifications based on target network topologies — specifications for link segments and MDI-to-PHY chip channels (insertion loss, return loss, crosstalk and other limit lines); refinements to cable return loss and micro-reflection specifications. - Define the EMC requirements of 25G (and possibly 50G) Ethernet links — characterizing and measuring RF ingress over target channels (cables, connectors, module) and defining limit lines for RF ingress levels at PHY inputs. Background: 25G and 50G automotive PHYs explained → TWG3 ## Physical Layer System and Component Integration Chairman: Olaf Grau, Bosch Scope: This project is to specify the integration of an Automotive Multi-Gig PHY in an Automotive Electronic Control Unit (ECU) or an Electronic Vehicle Computer (EVC). Objectives: - Specify and dimension automotive power supply applications for Automotive Multi-Gig PHYs - Specify PCB design rules that cover the needed signal integrity for Automotive Multi-Gig PHYs - Propose additional PCB-placed components needed for Automotive Multi-Gig operation - Specify diagnosis for an Automotive Multi-Gig link segment - Define power dissipation handling for automotive Multi-Gig components - Define host CPU interconnection for Automotive Multi-Gig PHYs TWG4 ## Protocol Encapsulation for Ethernet Chairman: Hari Parmar, Marvell · Start date: May 2019 Scope: This working group defines standard encapsulation of various protocols within Ethernet frames in a backwards-compatible manner. The initial target protocols for encapsulation are I2C, SPI, various camera interfaces and, for example, radar and lidar applications. Objectives: - Backwards compatibility with the existing Ethernet frame formats - Extensibility and adaptability with new or developing protocols - Will not define encapsulation where other relevant standards exist Background: protocol encapsulation over Ethernet → TWG5 ## System Controls and Management Chairman: Helge Zinner, Continental Scope: This working group defines how to interface the IVN (In-Vehicle Network) components and their features with respect to manageability. It identifies recommendations associated with hardware- and software-based interfaces that support systems used for autonomous vehicles, and elaborates an automotive network management protocol with additional considerations including enhanced diagnosis, predictive maintenance, redundancy, Quality of Service, wake-up and sleep, and device management. Objectives: - Identification of IVN key features for autonomous vehicle systems - IVN interface (software, protocol) definition - Definition of an automotive management protocol MWG ## Marketing Working Group Scope: Builds awareness and educates the market about Multi-Gig in-vehicle networking through trade shows, conferences, interoperability demonstrations, plugfests, exhibits, white papers and blogs. Contact the Marketing Working Group Chair at mktg-chair@nav-alliance.org. ## How to participate ## Eligibility Individuals from Promoter and Contributor member companies can join any technical or marketing working group. ## Sign up Log in to your member account and complete the short online process, or email admin@nav-alliance.org. ## Contribute Bring proposals, measurement data and use cases; chairs drive consensus toward specifications. ## Join the Revolution for the Future of Autonomous Vehicles Team up with industry leaders to define the future of automotive networking. Join the NAV Alliance --- # Multi-Gig Automotive Ethernet URL: https://nav-alliance.org/technology/ Technology ## Why the car needs Multi-Gig Ethernet A vehicle capable of automated driving combines many high-resolution cameras with radar, lidar and ultrasonic sensors, central AI computers, storage, displays and over-the-air connectivity. Each high-resolution camera alone can produce several gigabits per second of raw data, and redundancy requirements double critical paths. Classic in-vehicle buses — CAN at up to a few Mb/s, FlexRay at 10 Mb/s — and even 100 Mb/s or 1 Gb/s Ethernet cannot carry this load. Multi-Gig Automotive Ethernet brings data-center bandwidth into the car while meeting automotive constraints: single-pair or coaxial cabling to save weight, strict electromagnetic emission and immunity limits, an operating range from −40 °C to over 105 °C, low power, functional safety and fifteen-plus-year lifetimes. - 2.5, 5 and 10 Gb/s over a single pair — IEEE 802.3ch - 25, 50 and 100 Gb/s electrical PHYs — IEEE 802.3cy - Asymmetrical links for cameras and sensors ## The Automotive Ethernet speed ladder Each generation was standardized in IEEE 802.3 with automotive-specific requirements. Multi-Gig — everything above 1 Gb/s — is the NAV Alliance focus. PHYData rateIEEE standardMediumTypical use 10BASE-T1S10 Mb/s (shared)802.3cg (2019)Single unshielded pair, multidropSensors/actuators at the edge, CAN/LIN replacement 100BASE-T1100 Mb/s802.3bw (2015)Single unshielded pairBody, infotainment, diagnostics 1000BASE-T11 Gb/s802.3bp (2016)Single pairDomain/zonal links, compressed cameras 2.5/5/10GBASE-T12.5–10 Gb/s802.3ch (2020)Single shielded pair, up to 15 m with 4 inline connectorsBackbones, compute interconnect, cameras, storage 25/50/100GBASE-T125–100 Gb/s802.3cy (2023)Single shielded pairZonal backbone, central compute, high-res sensors 2.5–50GBASE-AU2.5–50 Gb/s802.3cz (2023)Multimode glass optical fibreEMC-critical or long links Asymmetrical EthernetMulti-Gig one way, low rate backP802.3dm (in development)Single pair / coaxCameras, radar, lidar, displays ## Building blocks of the NAV network ## Asymmetrical sensor links Gigabits upstream from cameras and sensors, a low-rate control channel downstream, plus Energy-Efficient Ethernet. Learn more ## Zonal backbone Zone controllers aggregate local devices and connect to central compute over 10–50 Gb/s links. Read the article ## Deterministic delivery TSN time synchronization, scheduling and redundancy make Ethernet safe for control loops. Read the article ## EMC robustness Channel, connector and PHY design that meets emission limits and tolerates RF ingress. Read the article ## Security by design MACsec, secure boot, firewalls and intrusion detection in line with ISO/SAE 21434. Read the article ## Power & diagnostics Power over Data Lines, sleep/wake and built-in cable diagnostics for predictive maintenance. Read the article Try it ## Size your camera links Our interactive calculator turns resolution, frame rate, bit depth and compression into a required data rate and suggests the matching Automotive Ethernet speed grade. Open the calculator   Glossary --- # Asymmetrical Ethernet for Sensors URL: https://nav-alliance.org/automotive-asymmetrical-ethernet-camera-with-eee/ The NAV Alliance is promoting Asymmetrical Ethernet for the sensor interface. Smart Car and Data Center-on-wheels are just some of the terms being used to define the exciting new waves of technology transforming the automotive industry and promising safer, greener self-driving cars and enhanced user experiences. Cameras, radar and lidar are the eyes of the autonomous vehicle. Their traffic is fundamentally one-directional: a camera sends several gigabits per second of image data towards the central computer, while the computer sends back only a few megabits per second of configuration, control and synchronization messages. A conventional symmetric Ethernet link spends the same effort — and power — in both directions. Asymmetrical Ethernet matches the physical layer to the real traffic pattern. ## What makes an Ethernet link asymmetrical? - High-speed uplink: Multi-Gig data rate from the sensor to the ECU or zonal controller, sized for uncompressed or lightly compressed high-resolution video. - Low-speed downlink: a much lower data rate back to the sensor for register access, triggers, time synchronization and firmware updates — enough for control, with far less transmitter power and complexity at the camera end. - Ethernet end-to-end: camera data enters the same switched, secured and managed Ethernet network as the rest of the vehicle, instead of a separate proprietary point-to-point SerDes link. - Energy-Efficient Ethernet (EEE): low-power idle modes let the link save energy between frames and when a sensor is inactive, reducing heat in compact camera housings. ## Why it matters for vehicle architectures Using Ethernet for sensors removes the need for dedicated serializer/deserializer chipsets and their protocol bridges in every ECU. Camera streams can be switched to multiple consumers, replicated for redundancy, time-stamped with gPTP, protected with MACsec and diagnosed with the same tools as the rest of the network. That is exactly the "Ethernet camera bridge" approach for software-defined vehicles that NAV Alliance members have presented, and it is the subject of the IEEE P802.3dm Asymmetrical Electrical Automotive Ethernet project. ## Further reading - Asymmetrical Ethernet for cameras and sensors — in-depth article - What is Multi-Gig Automotive Ethernet? - Power over Data Lines and Energy-Efficient Ethernet - Camera bandwidth calculator Blog: Ethernet Camera Bridge for Software-Defined VehiclesBy Amir Bar-Niv, VP of Marketing, Automotive Business Unit, Marvell. For additional information, please contact our member companies. --- # Camera Bandwidth Calculator URL: https://nav-alliance.org/camera-bandwidth-calculator/ How fast does the link from a camera to the central computer need to be? Move the sliders to estimate the data rate of a single camera and of several cameras sharing a zonal backbone, and see which Automotive Ethernet speed grade fits. ## How the calculation works The raw data rate of an image sensor is width × height × frames per second × bits per pixel. A 2.9-megapixel ADAS camera at 30 frames per second with 12-bit RAW output therefore produces about 1.06 Gb/s before any protocol overhead. Compression divides that figure; protocol overhead (Ethernet, IP/UDP or IEEE 1722 headers, inter-frame gaps, metadata) adds a few percent back. Suggested speed grades come from the Automotive Ethernet ladder: 1000BASE-T1 (IEEE 802.3bp), 2.5/5/10GBASE-T1 (IEEE 802.3ch) and 25/50/100GBASE-T1 (IEEE 802.3cy). For the backbone we keep 30 % headroom for other traffic, redundancy and future growth. ## Typical results CameraFormatApprox. raw rateFits on Surround-view, 1.3 MP, 30 fpsYUV422 (16 bit)~0.6 Gb/s1000BASE-T1 ADAS front, 2.9 MP, 30 fpsRAW12~1.1 Gb/s2.5GBASE-T1 8.3 MP, 30 fpsRAW12~3.0 Gb/s5GBASE-T1 8.3 MP, 60 fpsRAW12~6.0 Gb/s10GBASE-T1 12.6 MP, 60 fpsRAW20 HDR~15 Gb/s25GBASE-T1 Because camera traffic flows overwhelmingly in one direction, these links are ideal candidates for Asymmetrical Ethernet. The calculator gives a first-order estimate for architecture studies; final link budgets depend on the sensor interface, metadata, coding and the specific PHY. See our Disclaimer. --- # Automotive Networking Glossary URL: https://nav-alliance.org/glossary/ From 10BASE-T1S to zonal architecture — a quick reference for the vocabulary of in-vehicle networking. Type to search, or pick a letter. Missing a term? Tell us and we will add it. For deeper explanations, read our technical articles. --- # Insights URL: https://nav-alliance.org/insights/ Technical articles from the NAV Alliance. --- # News and Events URL: https://nav-alliance.org/news-and-events/ The NAV Alliance newsroom features our latest news from around the world. Find recent and past press releases and articles related to the NAV Alliance, our members, technical experts, and events. ## MEDIA CONTACT For general media inquiries, please contact pr@nav-alliance.org ## Automotive Ethernet Congress 2019 February 13-14, 2019Munich, Germany ## IEEE-SA Ethernet & IP @ Automotive Technology Day 2018 October 9-10, 2018London, England All events & milestones   RSS feed --- # Events URL: https://nav-alliance.org/events/ The NAV Alliance participates at trade shows and conferences, including interoperability demonstrations, plugfests and exhibits. Here is where the alliance has been — and how to meet us next. ## Meet the alliance Alliance representatives regularly attend the IEEE SA Ethernet & IP @ Automotive Technology Day and the Automotive Ethernet Congress, the two main gatherings of the automotive Ethernet community. Members can register for interoperability plugfests and technical workshops. ## Press and speaking requests Members of the press interested in speaking to a NAV Alliance representative at an event, and organizers who would like an alliance speaker, should contact pr@nav-alliance.org. --- # FAQ URL: https://nav-alliance.org/faqs/ General What does “NAV” stand for? It stands for Networking for Autonomous Vehicles. What is the NAV Alliance? NAV Alliance is an industry-wide cooperative effort focused on enabling the development and deployment of products that support Multi-Gigabit Ethernet connectivity for autonomous vehicles. The alliance was formed to build consensus around, and help streamline the development of, new Multi-Gig specifications in collaboration with standards organizations, such as the IEEE. NAV Alliance objectives also include creating specifications for interoperability, security and reliability of the in-vehicle network as well as educating the market about the multiple applications of the technology. Which companies have joined the NAV Alliance? NAV Alliance was founded by Bosch, Continental, Marvell, NVIDIA, and Volkswagen Group of America — leading car manufacturers, system suppliers, networking and Artificial Intelligence (AI) computing companies in the automotive market, sharing the goal of developing the ecosystem that is required for next generation Multi-Gig automotive Ethernet network in the vehicle. Following its public launch in June 2018, NAV Alliance is accepting submissions for membership by all interested players. A complete list of our members can be found here. Why does autonomous vehicle networking technology need its own alliance? NAV Alliance provides a forum for consensus and collaboration around technology, specification, interoperability, testing and product development with a focus on innovative Multi-Gig in-vehicle networking technologies. This process is important to solve real-world challenges and develop solutions that can be broadly adopted by the industry. What is the advantage of becoming a member of NAV Alliance, and why is this beneficial to the automotive industry? By joining NAV Alliance, your organization benefits from the following: - Access to the most up-to-date information on Multi-Gig development for autonomous vehicles - Ability to influence the direction of new technologies and specification development - Opportunity to generate business advantage through early adoption of the latest specifications - Opportunity to work and network with the Multi-Gig industry leaders What is the NAV Alliance working on next? The alliance is constantly evaluating proposals from member companies to address challenges and discuss new ideas in the area of Multi-Gig Ethernet connectivity inside the car. Among other things, the alliance evaluates technology solutions for speeds exceeding 10 Gbit/s — including 25G and 50G PHYs and Asymmetrical Ethernet for sensors — as bandwidth requirements for high-resolution cameras and sensors, backbone, storage connectivity and others continue to increase. Where can I find additional information about the NAV Alliance? Please visit us at nav-alliance.org, read our technical articles or download the overview presentation. We look forward to helping you with any questions you might have. To become a member, please contact the alliance and request the member agreement form, as well as the IPR Policy and the Bylaws. Legal What is the corporate structure of the NAV Alliance? The Alliance is incorporated in Delaware as a nonprofit corporation, with tax exempt status. Its Employer Identification Number (EIN) is 82-3869081. What is the leadership structure of the NAV Alliance? The NAV Alliance is managed by a board of directors. Companies represented on the board include car manufacturers, system suppliers and silicon suppliers, networking and AI computing companies. What levels of membership are offered and how can I become a member? Any company can submit an application to join the NAV Alliance, which offers three levels of membership: Promoter, Contributor and Adopter. Promoters have the ability to participate in all aspects of the alliance, including voting on proposed specifications, sitting on the board and participating in, as well as chairing, task forces and working groups. Contributors have the ability to participate in, as well as chair, working groups and task forces. In addition, contributor companies will have the right in the future to vote on one individual to represent the Contributor community on the board. Such decision will require being formalized by the board of directors of the Alliance. Adopters gain access to alliance specifications and collateral before they become publicly available, participate in internal discussions about the alliance and have the opportunity to participate in alliance events such as interoperability demonstrations, plugfests and exhibits. For more information on how to join the alliance, please visit the Become a Member section of our website. What are the yearly fees to join the NAV Alliance? - Promoter: USD 20k - Contributor: USD 10k - Adopter: USD 5k How is the NAV Alliance organized and managed? NAV Alliance is managed by a board of directors, comprised of representatives from promoter-member companies. Representatives from promoter and contributor companies can also join various working groups to have input into either the promotional activities planned by NAV Alliance or the technical aspects of its specifications. What is the NAV Alliance IP policy? NAV Alliance has adopted an IP Rights (IPR) Policy that is consistent with the industry standard practice used by organizations such as IEEE. Under NAV Alliance’s IPR Policy, a member agrees to grant to other members a license to its Necessary Claims (as defined in the IPR Policy), under Reasonable And Non-Discriminatory (RAND) terms. Are NAV specifications confidential, can I forward the specifications to my suppliers or other 3rd parties? The alliance publishes its specifications according to its bylaws, which limit distribution to member companies only. Please check the member section for the list of members. In which applications am I allowed to use the NAV specifications? The NAV Alliance does not place any restriction on the use of the specifications, according to its IPR. Technology, Working Groups and Standards What are the possible Multi-Gigabit applications in an automotive environment? The scope of the NAV Alliance includes all vehicle domains based on an array of ECUs (Electronic Control Units), CPUs/GPUs, high-definition cameras, sensors, gateways, and storage devices, all connected through a high-speed, Multi-Gigabit Ethernet network. Where can I access the specifications? Technical documents and specifications are available to member companies in the respective working group sections of the member portal. If you need access, please contact admin@nav-alliance.org. How do I join the NAV Alliance Marketing Working Group or Technical Working Group? Member companies that are promoter or contributor level are encouraged to join the Marketing Working Group (MWG) and Technical Working Group (TWG) by logging in to their NAV Alliance user account and completing the short online process. See the Working Groups page for the current groups. What marketing activities are organized by the NAV Alliance and how can my company get involved? The NAV Alliance intends to participate at trade shows and conferences, including interoperability demonstrations, plugfests and exhibits. The alliance also publishes white papers, blogs and other collaterals with the goal of educating the industry about the benefits of these new Multi-Gig technologies. For more information on how you can get involved, please contact the NAV Alliance Marketing Working Group Chair at mktg-chair@nav-alliance.org or NAV Alliance Administration at admin@nav-alliance.org. What are the NAV Alliance plans with regard to standardization of Multi-Gig technologies? NAV Alliance is committed to building consensus around new ideas, architectures and technologies propelling Ethernet networking into the realm of Multi-Gigabit/s speeds inside the autonomous car, which in itself resembles a data center on wheels. The car environment is unique: engineers face tremendous challenges related to noise emission and immunity, power consumption, reliability, safety standards, security, and cables that are of different construct than those commonly found in data centers and enterprise infrastructure. To continue the evolution of the Ethernet technology into this new, fascinating environment takes an industry-broad approach to solving problems and a drive towards standardization, based on the fundamental principle of consensus building. Technologies emerging from this industry-wide effort will be specified by the appropriate bodies, with help from NAV Alliance and its members working closely with industry standard organizations like the IEEE. How does the NAV Alliance work with standards organizations like IEEE? Since IEEE meetings are comprised of individuals, as opposed to organizations and companies, the Alliance doesn’t directly participate in these meetings. However, many individuals from our member companies are actively involved, on behalf of their respective organizations, in the standardization process via their participation in activities such as the IEEE P802.3ch Multigigabit Automotive Ethernet PHY Task Force. What is Asymmetrical Ethernet and why does the alliance promote it? Asymmetrical Ethernet provides a Multi-Gig data rate in one direction (from a camera or sensor to the ECU) and a much lower rate in the other (control and configuration). It matches the real traffic of sensors, saving power and cost at the sensor end while keeping the data inside the vehicle’s Ethernet network. Read more. Can my organization have more than one user account? Yes, as long as your email account is from the same domain that your company used to register as a member of the alliance. For any additional question regarding access to the portal, please contact admin@nav-alliance.org. Website, Orders & Privacy Can I order a membership or service online? Yes. Membership levels and alliance programs are listed under Services & Membership. Checkout creates an order and we email an official invoice with bank transfer details; memberships are activated once the member agreement is signed and payment received. See our Refund & Cancellation Policy. How do you handle the personal data I submit? We use the information you provide only to respond to your request or process your membership, as described in our Privacy Policy. You may opt out of communications at any time. Does the website use cookies? Only essential cookies are set by default. Optional cookies require your consent through the cookie banner, which you can change at any time. Details are in our Cookie Policy. NAV ALLIANCE and NAV are trademarks and certification marks of NAV Alliance, Inc. (or its licensor) in the United States and other countries. All rights reserved. Unauthorized use is strictly prohibited. ## Still have a question? Our administration team replies within two business days. Contact us --- # Contact Us URL: https://nav-alliance.org/contact/ Get in touch ## Contact the NAV Alliance Whether you are evaluating membership, want to join a working group, need information for an article or have a question about an order, we are happy to help. - ## Administration & membership admin@nav-alliance.org - ## Media inquiries pr@nav-alliance.org - ## Marketing Working Group mktg-chair@nav-alliance.org - ## Location NAV Alliance, Inc.San Jose, California, United States - ## Legal entity Delaware nonprofit corporationEIN 82-3869081 - ## Response time Within two business days (Mon–Fri, Pacific Time) ## Contact the NAV Alliance Please provide the following information. ## Before you write ## Membership Compare levels, fees and benefits on the Membership page. ## Answers Many questions are covered in our FAQ — searchable and categorized. ## Privacy requests To access, correct or delete your data, choose “Website / privacy request” as the topic. See the Privacy Policy. --- # Privacy Policy URL: https://nav-alliance.org/privacy-policy/ NAV Alliance, Inc. (“NAV Alliance”, “we”, “our”, or “us”) respects your privacy choices. This Privacy Policy explains what personal information we collect through our website located at nav-alliance.org (the “Site”), including through the resources, forms, member accounts and online services offered on the Site, how we use and share it, and the rights and choices available to you. Original policy effective June 26, 2018. This version is effective November 16, 2026. ## Summary - We collect only what we need: mainly the details you type into our forms, order data if you buy a membership or service, and basic technical data. - We do not sell or rent personal information, and we do not use it for cross-context behavioral advertising. - Optional cookies are used only with your consent, which you can change at any time. - You can ask us to access, correct, delete or export your data by writing to admin@nav-alliance.org. ## 1. Who we are (data controller) The controller responsible for personal information processed through the Site is NAV Alliance, Inc., a Delaware nonprofit corporation (EIN 82-3869081), San Jose, California, United States. You can reach us at admin@nav-alliance.org or through our contact form. This Privacy Policy applies only to our Site and the services and resources provided on it. It does not apply to any other websites, services or resources, including those linked to or from our Site, or to websites of our member companies. We encourage you to read this Privacy Policy and those of all websites you visit. ## 2. Information we collect ## 2.1 Information you provide In general, when you visit our Site, you do not have to disclose any personal information. Personal information means any information that identifies an individual, including but not limited to a first and last name, a business or other physical address, an email address or other work contact information. We collect personal information when you choose to provide it: - Contact form: name, company, email address, phone (optional), topic and message, so that we can follow up on your request. - Membership application: name, job title, company, business email, phone, country, desired membership level and any message you add. - Newsletter: your email address. - Orders and accounts (WooCommerce): billing name, company, address, email, phone, order details and account credentials. Payments are made by bank transfer against an invoice; we do not collect or store payment card numbers on the Site. - Member portal registration: name, title, business email and phone, which typically is all that is requested to create or edit a member profile. - Communications: the content of emails and other correspondence you send us. There may be occasions where we ask for additional information to better understand your needs and provide services that we believe may be valuable to you. If you choose not to provide personal information that we request, we may not be able to provide certain services or information to you. ## 2.2 Information collected automatically When you use the Site, our servers and security tools automatically record certain technical information, such as IP address, browser and operating system type, referring page, pages visited, date and time of access, and Internet domain and host names. We use this information to operate, secure and improve the Site. ## 2.3 Cookies and similar technologies The Site uses cookies and similar technologies as described in our Cookie Policy. Essential cookies (for example for security, the shopping cart and remembering your consent choice) are always active; optional analytics cookies are only set if you consent through the cookie banner. ## 3. How we use information and our legal bases PurposeExamplesLegal basis (EEA/UK) Respond to inquiriesAnswer contact-form messages and questionsLegitimate interests; steps prior to a contract Process membership applicationsSend member agreement, IPR Policy and Bylaws; onboard membersContract; legitimate interests Fulfil ordersIssue invoices, register plugfest/workshop participants, provide servicesContract; legal obligation (accounting) Send newsNewsletter, event invitationsConsent (withdraw at any time) Security and fraud preventionFirewall, spam filtering, login protectionLegitimate interests Improve the SiteAggregated usage statisticsConsent (analytics cookies) or legitimate interests for server logs Legal complianceTax records, responding to lawful requestsLegal obligation We will not use your personal information for purposes that are incompatible with those described above without telling you first. We do not make decisions based solely on automated processing that produce legal or similarly significant effects on you. ## 4. How we share information We protect the personal information you share with us. Access is limited to people who need it to do their job. We do not sell personal information. NAV Alliance shares personal information with companies or individuals outside of NAV Alliance only in the following limited circumstances: - With your consent. We require opt-in consent for the sharing of any sensitive personal information. - Service providers. We provide information to affiliated companies or other trusted businesses or persons that process it on our behalf — for example our web hosting provider, email delivery, security (Wordfence), consent management (CookieYes) and accounting services. We require them to process it only on our instructions, in compliance with this policy and with appropriate confidentiality and security measures. - Web hosting. Our Site is developed, hosted and maintained by third parties who may have technical access to information on the Site. They retain no rights to the information and may not distribute, sell or exchange it. - Legal reasons. When we have a good-faith belief that access, use, preservation or disclosure is reasonably necessary to: (a) satisfy any applicable law, regulation, legal process or enforceable governmental request; (b) enforce applicable terms, including investigation of potential violations; (c) detect, prevent or otherwise address fraud, security or technical issues; or (d) protect against imminent harm to the rights, property or safety of NAV Alliance, its members or the public as required or permitted by law. - Organizational changes. If NAV Alliance becomes involved in an assignment, merger, acquisition or any form of sale of some or all of its assets, we will provide notice before personal information is transferred and becomes subject to a different privacy policy. We may share aggregated, non-personal information with third parties — for example, the number of users who visited a certain part of our Site, or how many users clicked on a particular link. Such information does not identify you individually. ## 5. International transfers NAV Alliance processes personal information on servers in the United States of America and in other countries. In some cases, we may process personal information on a server outside your own country. Where we transfer personal information from the European Economic Area, the United Kingdom or Switzerland, we rely on appropriate safeguards such as the European Commission’s Standard Contractual Clauses or an adequacy mechanism, and you may request a copy of the relevant safeguards. ## 6. Data retention - Contact and membership inquiries: up to 24 months after our last interaction, unless you become a member. - Member records: for the duration of membership and up to 7 years afterwards for governance and legal purposes. - Orders and invoices: as required by tax and accounting law (generally 7 years). - Newsletter subscriptions: until you unsubscribe. - Security logs: typically up to 90 days. ## 7. Security measures We use administrative, technical and physical safeguards to protect personal information, including encrypted connections (HTTPS), a web application firewall and malware scanning, login protection, least-privilege access and regular updates. No method of transmission over the Internet or electronic storage is completely secure, so we cannot guarantee absolute security. NAV Alliance will not display or make available personal information that is not otherwise publicly available. ## 8. Your rights and choices Depending on where you live, you may have the right to: - access the personal information we hold about you and receive a copy (portability); - correct inaccurate or incomplete information; - delete your information; - object to or restrict certain processing, including processing based on legitimate interests; - withdraw consent at any time (for example for the newsletter or analytics cookies), without affecting earlier processing; - lodge a complaint with your local data protection authority. We give you the opportunity to elect not to receive information from us regarding upcoming events and other news: every newsletter contains an unsubscribe link, and you can also email us. To exercise any right, contact admin@nav-alliance.org or use the contact form with the topic “Website / privacy request”. We will verify your request and respond within the period required by law (generally 30 days under the GDPR and 45 days under California law). ## 9. Additional information for California residents This section supplements the policy for California residents under the California Consumer Privacy Act as amended by the California Privacy Rights Act (CCPA/CPRA). In the last 12 months we collected the following categories of personal information: identifiers (name, email, IP address); professional information (company, job title); commercial information (orders); and internet activity (pages visited). We collect them from you and your device for the purposes described in section 3, and disclose them to service providers for business purposes. - We do not sell personal information or share it for cross-context behavioral advertising, and we have no actual knowledge of selling or sharing information of consumers under 16. - We do not use or disclose sensitive personal information for purposes that would give rise to a right to limit. - You have the rights to know, delete, correct and opt out, and the right not to receive discriminatory treatment for exercising them. You may use an authorized agent; we may ask for proof of authorization. - We honor Global Privacy Control (GPC) signals as a request to opt out of optional cookies. ## 10. Linked websites We provide links to third-party sites, including member companies and standards organizations. Since we do not control these websites, we encourage you to review their privacy policies. NAV Alliance is not responsible for the privacy practices of third-party sites and cannot be held liable for any use of personal data they collect. ## 11. Children’s privacy The Site is intended for professionals and is not directed to children. We do not knowingly collect personal information from children under the age of 13 (or under 16 in the EEA). If we learn that we have personal information about a child, we will delete it from our systems. ## 12. Accessing and updating information We need your help to make sure your personal information is correct. Please notify us of changes to your name, address, title, phone number or email address; members can also update their details in their account. ## 13. Policy updates We may change this Privacy Policy from time to time. All updates will be posted on this page and are effective on the date posted, shown at the top of this policy. If changes are material, we will provide additional notice, for example by email to members. ## 14. Contacting us If you have any questions about this Privacy Policy, the practices of this Site, or your dealings with this Site, please contact the Site Administrator at admin@nav-alliance.org. NAV Alliance, Inc. · San Jose, California, USA · EIN 82-3869081 --- # Terms and Conditions URL: https://nav-alliance.org/terms/ These Terms and Conditions of Use (“Agreement”) govern the use of NAV Alliance, Inc.’s (“NAV Alliance”) website nav-alliance.org (“Site”) by you (“You” or “User”), including any purchase of memberships or services through the Site. YOUR USE OF THIS SITE INDICATES THAT YOU ACCEPT THIS AGREEMENT AND AGREE TO ALL OF ITS TERMS. YOU AGREE THAT YOUR USE OF THE SITE IS CONDITIONED ON YOUR ACCEPTANCE, WITHOUT MODIFICATION, OF THIS AGREEMENT. IF YOU DO NOT ACCEPT THE TERMS IN THIS AGREEMENT THEN YOU DO NOT HAVE ANY RIGHT TO USE THIS SITE AND YOU SHOULD EXIT THIS SITE AND NOT USE THE SITE. You should download and print this Agreement for your records. NAV Alliance retains the right to change this Agreement at any time as set forth in Section 14 below. Original terms effective June 26, 2018. This version is effective November 16, 2026. ## 1. Access and conditions of use 1.1 User’s right to use this Site is subject to compliance with all terms in this Agreement. Within this Site, NAV Alliance provides User with access to a variety of resources including, but not limited to, membership information, technical articles, interactive tools, press releases, online ordering of memberships and services, and other general information about NAV Alliance (“Resources”). Your use of these Resources is subject to the terms of this Agreement. 1.2 As conditions to User’s use of this Site, You agree that You will not: - modify, copy, distribute, transmit, display, perform, reproduce, publish, broadcast, license, create derivative works from, transfer or sell any information, software, products or services obtained from the Site, except as expressly permitted in Section 4; - use the Site or any of the Resources for any unlawful or abusive purpose, including without limitation to harass, threaten, or defame any person or entity; - use the Site or any of the Resources in a manner that could damage, disable, overburden or impair any Alliance Server or the networks connected to any Alliance Server. “Alliance Server” means the computer software and/or hardware that serves the Site to users across the Internet, and which hosts the pages, scripts, programs, and multimedia files and serves them using a protocol designed to send files to users; - attempt to gain unauthorized access to any of the Resources or Alliance Server through hacking, password mining or other unauthorized means, or probe, scan or test the vulnerability of the Site without our written permission; - obtain or attempt to obtain any materials or information not intentionally made available on the Site or through the Resources; - use any robot, spider or other automatic device to monitor or copy the Site’s pages or content in a way that circumvents technical limits, imposes an unreasonable load, or ignores our robots.txt instructions — indexing by search engines and AI assistants in accordance with our robots.txt and llms.txt files is welcome; - upload files, other than as provided by the Resources, that contain viruses, Trojan horses, worms, time bombs, cancelbots, corrupted files or any other similar software or programs that may damage the operation of the Site or another computer; or - submit false information, impersonate any person or entity, or misrepresent your affiliation with a company. 1.3 User is responsible for obtaining and maintaining any equipment or ancillary services needed to connect to or access the Site, including, without limitation, Internet connections, hardware and software. ## 2. User registration, user IDs and passwords If any of the Resources require You to register on this Site, You must complete the registration by providing current, complete and accurate information as prompted by the registration form. You may also receive a user ID and password. You are entirely responsible for protecting and maintaining the confidentiality of Your user ID and password as well as all activities that occur under Your account. You agree to immediately notify NAV Alliance of any unauthorized use of Your account. NAV Alliance will not be liable for any loss that You may incur as a result of an unauthorized use of Your user ID or password. However, You could be held liable for losses incurred by NAV Alliance due to an improper use of Your user ID or password, and NAV Alliance reserves the right to take any remedial action it sees fit in the event of any violation of this Agreement. You may not use any other person or entity’s user ID or password at any time. Member-portal accounts are available to individuals with an email address on the domain of a member company. ## 3. Membership, orders and services 3.1 Membership. Membership in the NAV Alliance is governed by the member agreement, the Bylaws and the IPR Policy of the alliance. An online order for a membership level is a request to join; membership becomes effective only when NAV Alliance has accepted the application, the member agreement has been executed and the annual fee has been paid. If these Terms conflict with the member agreement, Bylaws or IPR Policy, those documents prevail. 3.2 Services. Plugfest registrations, workshops and pre-compliance reviews are described on their service pages. Dates, locations, scope and deliverables are confirmed in writing after the order. Services are provided for engineering guidance only and do not constitute certification unless expressly stated. 3.3 Prices and payment. Prices are shown in US dollars and exclude any applicable taxes, bank charges and travel costs. Orders are paid by bank transfer against an invoice issued by NAV Alliance, Inc.; invoices are payable within 30 days unless stated otherwise. We may correct obvious pricing errors and may decline or cancel orders, in which case any payment received is refunded. 3.4 Cancellations and refunds are handled under our Refund & Cancellation Policy, which forms part of this Agreement. ## 4. Copyrights, trademarks and other IP rights; reservation of rights 4.1 The Site and its content — including text, graphics, logos, the calculator and other tools, and the selection and arrangement thereof — are owned by NAV Alliance or its licensors and are protected by copyright, trademark and other laws. NAV ALLIANCE and NAV are trademarks and certification marks of NAV Alliance, Inc. (or its licensor) in the United States and other countries. Unauthorized use is strictly prohibited. Names and logos of member companies are trademarks of their respective owners. 4.2 You may view, download and print pages of the Site for your personal or internal business reference, and quote short excerpts of our articles with attribution and a link to the source page. Any other use requires our prior written permission. 4.3 NAV Alliance’s policy is to respect the copyrights and intellectual property rights of others. NAV Alliance has the right to (i) terminate a User’s use of this Site if User’s use in any manner infringes upon the copyright or intellectual property rights of others, and (ii) remove any content from the Site that, in NAV Alliance’s opinion, may infringe the copyright or other intellectual property rights of any third party. See our DMCA Policy. 4.4 This Agreement shall not be interpreted to transfer any rights in any intellectual property from NAV Alliance to User other than the limited right to use the Site or any of the Resources as set forth herein. Alliance specifications are licensed only to members under the IPR Policy. ## 5. Submissions You agree that any information, feedback, questions, comments and related materials that you provide to NAV Alliance in connection with your use of this Site (“Submissions”) are provided on a non-confidential and non-proprietary basis. NAV Alliance shall have no obligations to You of any kind with respect to any Submissions and shall be free to reproduce, use, disclose and/or distribute any Submissions for any purpose whatsoever, without limitation. Personal information in Submissions is handled according to our Privacy Policy. Do not send confidential or proprietary technical information through the Site; contributions to specifications are made only through working groups under the IPR Policy. ## 6. Privacy Policy and other policies governing this Site NAV Alliance’s Privacy Policy, Cookie Policy, Disclaimer, Refund & Cancellation Policy and any other terms that govern this Site are hereby incorporated into this Agreement by this reference, and User agrees to comply with the same at all times. ## 7. Links to third-party sites As a convenience, the Site may provide links to other websites that are not owned or controlled by NAV Alliance (“Third Party Websites”). NAV Alliance does not control Third Party Websites and is not responsible for their content, for any links contained in them, or for any changes or updates to them. Any link from this Site to a Third Party Website does not constitute or imply any endorsement or recommendation by NAV Alliance. Your visit to any Third Party Website is subject to the terms and conditions of that website. ## 8. No warranty THE SITE, THE RESOURCES AND THE MATERIALS IN THE SITE ARE PROVIDED ON AN “AS IS” AND “AS AVAILABLE” BASIS WITHOUT REPRESENTATIONS OR WARRANTIES OF ANY KIND, EITHER EXPRESS OR IMPLIED. NAV ALLIANCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT. NAV ALLIANCE DOES NOT REPRESENT OR WARRANT THAT THE RESOURCES OR MATERIALS IN THIS SITE, INCLUDING WITHOUT LIMITATION ANY INFORMATION ABOUT NAV ALLIANCE PROVIDED BY THIRD PARTIES, ARE ACCURATE, COMPLETE, RELIABLE, CURRENT OR ERROR-FREE, OR THAT THIS SITE OR ITS SERVERS ARE FREE OF VIRUSES OR OTHER HARMFUL COMPONENTS. NAV Alliance does not guarantee continuous, uninterrupted or secure access to its Resources, and operation of the Site may be interfered with by numerous factors outside of the control of NAV Alliance, including, but not limited to, telecommunications network disruptions. ## 9. Limit of liability TO THE MAXIMUM EXTENT PERMITTED BY LAW, IN NO EVENT SHALL NAV ALLIANCE, ITS DIRECTORS, OFFICERS, MEMBERS OR VOLUNTEERS BE LIABLE FOR ANY SPECIAL, INDIRECT, INCIDENTAL OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER FROM THE LOSS OF USE, DATA OR PROFITS, WHETHER IN CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE SITE. NAV ALLIANCE’S TOTAL LIABILITY FOR ANY CLAIM RELATING TO A PAID ORDER SHALL NOT EXCEED THE AMOUNT YOU PAID FOR THAT ORDER. This Site may contain information targeted to a wide range of audiences that could be not accessible or valid in your country; NAV Alliance does not take responsibility for accessing such information which may not comply with legal requirements in your country. Nothing in this Agreement excludes liability that cannot be excluded under applicable law. ## 10. Indemnification You agree to indemnify and hold harmless NAV Alliance and its directors, officers, members and agents from any claims, damages, losses and expenses (including reasonable attorneys’ fees) arising from your breach of this Agreement or your misuse of the Site. ## 11. Termination In addition to any other rights, NAV Alliance reserves the right, without notice and in its sole discretion, to terminate your use of this Site and to block or prevent further access to and use of this Site by You. Sections 4, 5, 8, 9, 10, 12 and 13 survive termination. ## 12. Governing law and disputes This Agreement will be construed and controlled by, and any dispute arising from the terms of this Agreement shall be governed by, the laws of the State of Delaware, without regard to its conflict-of-laws rules. The parties will first attempt in good faith to resolve any dispute informally by contacting admin@nav-alliance.org. Consumers resident in the European Union or United Kingdom retain the protection of mandatory provisions of the law of their country of residence. ## 13. Entire agreement, severability; non-waiver This Agreement, along with the Privacy Policy and the other policies referenced in Section 6, constitutes the entire agreement between the parties with respect to the subject matter hereof. If any provision of this Agreement is deemed unlawful, void or for any reason unenforceable, that provision shall be deemed severable and shall not affect the validity and enforceability of the remaining provisions. The failure of NAV Alliance to insist upon or enforce strict performance of any provision or to exercise any right or remedy will not be construed as a waiver or relinquishment of NAV Alliance’s right to assert or rely upon any such provision, right or remedy in that or any other instance. ## 14. Changes to this Agreement NAV Alliance may modify this Agreement at any time, and User will be bound by the version in effect at the time User visits this Site. Any use of this Site by User after changes are posted shall be deemed to constitute acceptance of the amendments. Changes do not affect orders already accepted. ## 15. Copyright notice Copyright © 2018–2026 NAV Alliance, Inc. All rights reserved. ## 16. Questions and contact information If You have questions about the terms of this Agreement, please send an email to the Site Administrator at admin@nav-alliance.org. NAV Alliance, Inc. · Delaware nonprofit corporation · EIN 82-3869081 · San Jose, California, USA --- # Disclaimer URL: https://nav-alliance.org/disclaimer/ The information on nav-alliance.org is published by NAV Alliance, Inc. for general information about the alliance and about in-vehicle networking technology. Please read this Disclaimer carefully before relying on any content of the Site. ## 1. General information only Content on this Site — including technical articles, glossary entries, tables, diagrams, press releases and the Camera Bandwidth Calculator — is provided for general informational and educational purposes. While we take care to keep it accurate and current, NAV Alliance makes no representations or warranties of any kind, express or implied, about the completeness, accuracy, reliability or suitability of the information. Any reliance you place on such information is strictly at your own risk. ## 2. Not engineering, legal or professional advice Nothing on the Site constitutes engineering, safety, regulatory, legal, financial or other professional advice. Vehicle networks are safety-relevant systems. Design decisions must be validated against the applicable standards (for example IEEE 802.3, ISO 26262, ISO/SAE 21434, CISPR 25 and OEM-specific requirements), qualified test results and the advice of qualified professionals. ## 3. Standards and specifications References to IEEE, ISO, OPEN Alliance and other standards are summaries prepared for readability. The official standards documents published by their respective organizations are authoritative; standards and projects evolve, and project numbers, scopes and status may change after publication of an article. NAV Alliance specifications are distributed to members under the alliance Bylaws and IPR Policy; descriptions on the public Site do not grant any license. ## 4. Calculators and tools Interactive tools such as the Camera Bandwidth Calculator produce first-order estimates based on simplified formulas and assumptions shown on the page. Results do not account for every protocol, coding, metadata, error-correction or implementation detail and must not be used as the sole basis for product decisions. ## 5. Statements by members and third parties Press releases may contain quotations and forward-looking statements by member companies. Such statements reflect the views of those companies at the time of publication and are subject to risks and uncertainties. Mention of any company, product or service does not constitute an endorsement or recommendation by NAV Alliance, and listing as a member does not imply that a member endorses any particular article on the Site. ## 6. Trademarks NAV ALLIANCE and NAV are trademarks and certification marks of NAV Alliance, Inc. All other company names, product names and logos are trademarks or registered trademarks of their respective owners and are used for identification purposes only. ## 7. External links The Site contains links to external websites that are not provided or maintained by NAV Alliance. We do not guarantee the accuracy, relevance, timeliness or completeness of any information on these external websites. ## 8. Images Photographs used to illustrate articles are openly licensed works credited on our Image Credits page. Vehicles and products shown are illustrative and do not imply that their manufacturers are alliance members or endorse alliance content. ## 9. Availability We do not warrant that the Site will be available without interruption or free of errors, and we may change or withdraw content at any time without notice. ## 10. Limitation of liability To the fullest extent permitted by law, NAV Alliance shall not be liable for any loss or damage, including indirect or consequential loss, arising from the use of, or reliance on, this Site. See section 9 of our Terms and Conditions. ## 11. Contact If you notice an error or have questions about this Disclaimer, please contact admin@nav-alliance.org. Corrections are handled under our Editorial Policy. --- # DMCA Policy URL: https://nav-alliance.org/dmca-policy/ NAV Alliance, Inc. respects the intellectual property rights of others and expects users of nav-alliance.org to do the same. In accordance with the Digital Millennium Copyright Act of 1998, 17 U.S.C. § 512 (“DMCA”), we will respond expeditiously to valid notices of claimed copyright infringement. ## 1. Reporting claimed infringement If you believe that material on the Site infringes a copyright you own or are authorized to enforce, please send a written notification to our designated agent containing all of the following: - A physical or electronic signature of a person authorized to act on behalf of the owner of the exclusive right that is allegedly infringed. - Identification of the copyrighted work claimed to have been infringed or, if multiple works are covered by a single notification, a representative list of such works. - Identification of the material that is claimed to be infringing, and information reasonably sufficient to permit us to locate it — ideally the exact URL(s). - Information reasonably sufficient to permit us to contact you, such as your name, address, telephone number and email address. - A statement that you have a good-faith belief that use of the material in the manner complained of is not authorized by the copyright owner, its agent or the law. - A statement that the information in the notification is accurate, and, under penalty of perjury, that you are authorized to act on behalf of the owner of the exclusive right that is allegedly infringed. ## 2. Designated agent DMCA Agent, NAV Alliance, Inc.San Jose, California, United StatesEmail: admin@nav-alliance.org (subject line: “DMCA Notice”) Notices that do not substantially comply with the requirements above may not be acted upon. Please note that under 17 U.S.C. § 512(f), any person who knowingly materially misrepresents that material or activity is infringing may be subject to liability for damages. ## 3. What happens next On receipt of a valid notice we will remove or disable access to the material identified, notify the person who supplied it where applicable, and keep a record of the notice. We aim to acknowledge notices within three business days. ## 4. Counter-notification If you believe material you supplied was removed by mistake or misidentification, you may send a counter-notification to our designated agent including: - Your physical or electronic signature. - Identification of the material that has been removed and the location at which it appeared before removal. - A statement under penalty of perjury that you have a good-faith belief that the material was removed or disabled as a result of mistake or misidentification. - Your name, address and telephone number, and a statement that you consent to the jurisdiction of the Federal District Court for the judicial district in which your address is located (or, if outside the United States, any judicial district in which NAV Alliance may be found), and that you will accept service of process from the person who provided the original notification or an agent of such person. If we receive a valid counter-notification, we may restore the material in 10 to 14 business days unless the original complainant notifies us that it has filed an action seeking a court order. ## 5. Repeat infringers It is our policy, in appropriate circumstances, to disable and/or terminate the accounts of users who are repeat infringers. ## 6. Images and licensed content Photographs on this Site are used under open licenses and credited on our Image Credits page. If you are the author of an image and believe the attribution or license terms are not being followed, please contact us — we will correct the credit or remove the image promptly. ## 7. Other intellectual property For trademark or other intellectual property concerns that are not copyright claims, please contact admin@nav-alliance.org with details of your claim. --- # Cookie Policy URL: https://nav-alliance.org/cookie-policy/ This Cookie Policy explains how NAV Alliance, Inc. uses cookies and similar technologies on nav-alliance.org, and how you can control them. It supplements our Privacy Policy. ## 1. What are cookies? A cookie is a small text file stored on your device when you visit a website. Cookies may be used, for example, to keep you signed in, remember items in a cart, record your consent choice or collect information about site activity. Similar technologies include local storage and pixels; we refer to all of them as “cookies”. ## 2. How we use cookies We keep cookies to a minimum. The Site loads its fonts, scripts and styles from our own server, so visiting a page does not send data to font or script CDNs. CategoryPurposeExamplesDurationConsent Strictly necessarySecurity, load balancing, remembering your consent choicecookieyes-consent, Wordfence security cookies (wfwaf-authcookie-* for logged-in users)Session – 1 yearNot required Functional (shop & accounts)Shopping cart, checkout and member loginwoocommerce_cart_hash, woocommerce_items_in_cart, wp_woocommerce_session_*, wordpress_logged_in_*Session – 2 days (14 days with “remember me”)Not required (needed for the service you request) AnalyticsUnderstand how pages are used so we can improve themOnly if an analytics tool is enabled — listed in the cookie bannerUp to 13 monthsRequired MarketingWe do not use advertising cookies——— The current, detailed list of cookies — automatically scanned — is always available in the cookie banner’s “Customize” view. ## 3. Your choices - Cookie banner: on your first visit you can accept all, reject non-essential, or customize categories. You can change your choice at any time with the “Cookie settings” / revisit consent button shown on the Site. - Browser settings: most browsers let you block or delete cookies. If you block necessary cookies, parts of the Site such as the cart, checkout or member login will not work, and you will need to re-enter your user ID and password to access certain areas. - Global Privacy Control: we treat a GPC signal as a request to reject non-essential cookies. ## 4. Third-party content Links to social networks (LinkedIn, X, Facebook) are simple links; we do not embed their tracking widgets. If you follow such a link, the third party’s own cookie policy applies. ## 5. Updates We may update this Cookie Policy when we change the technologies we use. The “Last updated” date at the top shows the latest revision. ## 6. Contact Questions about cookies: admin@nav-alliance.org. --- # Refund & Cancellation Policy URL: https://nav-alliance.org/refund-policy/ This policy explains how cancellations and refunds work for memberships and services ordered through nav-alliance.org. It forms part of our Terms and Conditions. ## 1. How orders work All products on the Site are services or memberships; nothing is shipped. When you place an order we email an invoice with bank transfer details. Your membership or service is confirmed once (a) we have accepted the order, (b) for memberships, the member agreement has been signed, and (c) payment has been received. ## 2. Memberships (Promoter, Contributor, Adopter) - Before activation: you may cancel an order at any time before the member agreement is signed — any amount paid is refunded in full. - Cooling-off period: within 14 days after activation you may cancel for a full refund, provided you have not yet received confidential specifications or participated in working-group meetings. - After 14 days or after access to specifications: annual fees are non-refundable. Membership continues until the end of the paid term and can be terminated for the following year according to the Bylaws. - Changing level: upgrades are charged pro rata for the remainder of the membership year; downgrades take effect at renewal. - If NAV Alliance declines an application, any payment is refunded in full. ## 3. Plugfest registrations - More than 30 days before the event: full refund, or free transfer to another event. - 15–30 days before the event: 50 % refund, or free transfer. - Less than 15 days before the event or no-show: no refund; you may name a substitute engineer from your company at no charge. ## 4. Workshops and training - More than 14 days before the session: full refund. - 7–14 days before: 50 % refund or a free seat at a later session. - Less than 7 days before: no refund; substitutions are welcome. ## 5. Pre-compliance design reviews - Before the kick-off meeting: full refund. - After kick-off: fees are refunded pro rata for work not yet performed, less any third-party costs already incurred. - Once the written review report has been delivered: non-refundable. ## 6. Cancellation by NAV Alliance If we cancel or postpone an event or service, you may choose a full refund or transfer to the rescheduled date. We are not responsible for travel or accommodation costs you incurred. ## 7. How refunds are paid Refunds are issued by bank transfer to the paying account within 14 days of approval, in US dollars. Bank charges and currency conversion differences are not refunded unless the cancellation was caused by NAV Alliance. ## 8. How to request a cancellation Email admin@nav-alliance.org with your order number, or use the contact form with the topic “Services & orders”. We confirm every request in writing. ## 9. Statutory rights Nothing in this policy limits any mandatory consumer rights you may have under applicable law. --- # Accessibility Statement URL: https://nav-alliance.org/accessibility/ NAV Alliance is committed to making nav-alliance.org accessible to everyone, including people with disabilities. We aim to conform to the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. ## 1. Measures we take - Semantic HTML with a logical heading structure, landmarks and a “Skip to content” link. - Full keyboard navigation for menus, accordions, tabs, filters, modals and the search overlay; the Escape key closes overlays. - Visible focus indicators and sufficient color contrast for body text and controls. - Descriptive alternative text for informative images; decorative images are hidden from assistive technology. - Form fields with visible labels, required-field indicators and clear error messages announced next to each field. - Animations respect the operating-system “reduce motion” setting and are disabled when it is on. - Text can be resized up to 200 % and the layout adapts to small screens. - Fonts are served locally for fast, reliable rendering. ## 2. Known limitations - Some historical PDF documents, such as older presentations, may not be fully tagged for screen readers. We will provide an accessible version on request. - Third-party components (for example the cookie-consent banner or the checkout provided by WooCommerce) are maintained by their vendors; we report issues we find to them. - Member logos are images of text; company names are provided as alternative text and as visible labels in the member directory. ## 3. Feedback and assistance If you encounter an accessibility barrier, need information in a different format, or have suggestions, please contact us at admin@nav-alliance.org or through the contact form. Please describe the page and the problem. We aim to respond within five business days and to provide the content you need in an accessible alternative. ## 4. Assessment This statement is based on a self-assessment of the Site combined with automated testing tools. It is reviewed whenever the Site changes significantly. --- # Editorial Policy URL: https://nav-alliance.org/editorial-policy/ NAV Alliance publishes technical articles to educate the automotive industry about Multi-Gig in-vehicle networking — one of the alliance’s founding objectives. This page describes how that content is created, reviewed and maintained. ## 1. Purpose and independence Our Insights articles explain technologies, standards and architectures. They are educational, vendor-neutral and are not advertising for any member company. Where a product or company is mentioned, it is because it illustrates a technical point. ## 2. Authorship and review - Articles are written by the NAV Alliance editorial team with input from engineers working in alliance working groups. - Each article is technically reviewed before publication, checking standard numbers, data rates and terminology against primary sources such as IEEE 802.3 and 802.1 project documentation, ISO standards and OPEN Alliance publications. - Articles never disclose confidential working-group material or unpublished specifications. ## 3. Accuracy, corrections and updates Standards evolve. We review articles periodically and update them when projects are approved, renamed or superseded. Material corrections are made promptly; if a correction changes the meaning of an article, we note it at the end of the article. To report an error, contact admin@nav-alliance.org. ## 4. Sources and quotations We prefer primary sources (standards bodies, official announcements). Quotations in press releases are provided by the companies quoted and approved by them before release. ## 5. Images We use original alliance graphics and openly licensed photographs, credited on the Image Credits page. We do not use images in a way that suggests endorsement by the people or companies shown. ## 6. Use of AI tools Editors may use software tools, including AI-based tools, to help with research, drafting or language editing. Every published article is reviewed, fact-checked and approved by a human editor who is accountable for its content. ## 7. Reuse of our content You may quote short excerpts with attribution and a link to the original article. Search engines and AI assistants may index our content in line with our llms.txt and robots.txt; please cite nav-alliance.org as the source. --- # Image Credits URL: https://nav-alliance.org/image-credits/ The NAV Alliance logo, member logos and banner graphics are from the original nav-alliance.org website. The photographs below are used under the open licenses indicated, via Wikimedia Commons. We thank the photographers for making their work available. Company names and logos are trademarks of their respective owners. If you believe an image is credited incorrectly, please contact us or see our DMCA Policy. --- # Power over Data Lines, Sleep/Wake and Energy-Efficient Ethernet in Vehicles URL: https://nav-alliance.org/power-over-data-lines-energy-efficient-ethernet-automotive/ Published: 2026-08-25 In a vehicle, power is never free. Every watt drawn by electronics costs fuel or driving range, every wire adds weight, and every ECU that stays awake while the car is parked drains the battery. Multi-Gig networks must therefore be not only fast, but frugal. This article covers four technologies that make that possible: Power over Data Lines, Energy-Efficient Ethernet, network sleep/wake, and PHY-level diagnostics. ## Key takeaways - PoDL (IEEE 802.3bu) delivers DC power over the same single pair that carries data, eliminating separate power wires for sensors. - Energy-Efficient Ethernet lets PHYs enter low-power idle when there is no traffic. - Sleep/wake over the data line (OPEN Alliance TC10) powers down whole links and ECUs while parked and wakes them in milliseconds. - Built-in diagnostics — signal quality indicators and cable tests — enable predictive maintenance. ## Power over Data Lines (PoDL) Power over Ethernet (PoE) is familiar from office networks, where it powers phones and access points over four-pair cabling. Automotive single-pair links use a different scheme: IEEE 802.3bu, Power over Data Lines, superimposes DC power on the single data pair. Coupling inductors at each end separate DC from the high-frequency data signal, and capacitors block DC from the PHY. PoDL defines power classes for nominal 12 V and 24 V systems (and others), plus a detection and classification procedure so power is applied only to compatible devices. For cameras and remote sensors, powering over the data cable removes a power wire and a connector pin, saving weight and cost and simplifying the harness. The challenge at Multi-Gig speeds is the coupling network: inductors must present a high impedance across a very wide frequency range so they do not degrade the data channel. Integrated solutions and careful component selection are essential. NAV Alliance TWG1/TWG2 explicitly included PoDL requirements in its 25G/50G use-case analysis. ## Energy-Efficient Ethernet (EEE) An Ethernet PHY that keeps transmitting idle symbols at full rate wastes energy. Energy-Efficient Ethernet allows link partners to agree to enter a low-power idle state when there is no data, periodically refreshing the link to keep receivers trained, and to return to full operation within microseconds when frames arrive. For bursty traffic — sensor frames separated by gaps, periodic control messages — EEE can significantly reduce average PHY power. IEEE 802.3ch includes optional EEE for 2.5/5/10GBASE-T1, and the NAV Alliance promotes EEE for asymmetrical camera links where heat in the camera module matters. Heat is the hidden costImage sensors produce more noise at higher temperature. Lower PHY power inside a sealed camera housing directly improves image quality and reliability. ## Sleep and wake-up over the data line When a car is parked, most of its electronics must sleep, drawing microamps — yet some functions (keyless entry, alarm, telematics, charging management) must be able to wake the network. CAN has long supported selective wake-up. For automotive Ethernet, the OPEN Alliance TC10 specification defines how a PHY can sleep with the link down and be woken by its link partner over the same data line, and how ECUs coordinate a network-wide sleep. Wake-up must be fast — link up within tens of milliseconds — so that a door opening or a remote command feels instantaneous. NAV Alliance TWG5, System Controls and Management, lists wake-up and sleep among the considerations for its automotive network management protocol, alongside enhanced diagnosis, predictive maintenance, redundancy, Quality of Service and device management. ## Partial networking in a zonal architecture In a zonal architecture, power management becomes more flexible: zone controllers can keep only the links and devices needed for an active function awake. For example, during AC charging an electric vehicle may need its battery management, charging interface and telematics active, but none of the perception sensors or the central AI computer. Coordinated sleep/wake of Ethernet links and PoDL-powered devices enables these partial-network states. ## Diagnostics for predictive maintenance A network that will run for fifteen years needs to report its own health. Automotive PHYs provide diagnostics such as: - Signal Quality Indicator (SQI) — an estimate of link margin derived from the receiver's internal signal-to-noise measurements. A slowly decreasing SQI warns of a degrading cable or connector before errors occur. - Cable tests / time-domain reflectometry (TDR) — detecting opens, shorts and their approximate distance from the PHY. - Error counters — FEC-corrected and uncorrectable errors, link-down events. - Temperature and power monitoring — for thermal management and fault analysis. Collected through the network management protocol and reported via telematics, these diagnostics let OEMs schedule repairs proactively, reduce no-fault-found replacements in workshops and improve future designs. NAV Alliance TWG3 includes diagnosis of a Multi-Gig link segment in its integration work. TechnologyStandard / specMain benefit Power over Data LinesIEEE 802.3buFewer wires, lighter harness Energy-Efficient EthernetIEEE 802.3 (optional in 802.3ch and others)Lower average PHY power and heat Sleep/wake over data lineOPEN Alliance TC10Low quiescent current, fast wake-up Link diagnosticsPHY features (SQI, TDR), management protocolsPredictive maintenance, faster repairs ## Design recommendations - Budget power per link, including PHY, PoDL losses and MACsec, for each operating mode (driving, parked, charging). - Enable EEE where traffic is bursty and latency requirements allow. - Define partial-network states early and map them to link sleep/wake capabilities. - Validate wake-up time over temperature and with worst-case harnesses. - Expose PHY diagnostics to the vehicle's health monitoring from day one. ## Frequently asked questions ## Is PoDL the same as Power over Ethernet? Both deliver power over data cabling, but PoE targets multi-pair enterprise cabling, while PoDL is defined for single-pair Ethernet and automotive/industrial voltages. ## Does EEE add latency? Waking from low-power idle takes microseconds. For most automotive traffic this is negligible; latency-critical streams can keep EEE disabled. ## Where can I learn the basics first? Start with What is Multi-Gig Automotive Ethernet? and our glossary. Updated November 2026. --- # Cables and Connectors for Multi-Gig: Designing the Automotive Ethernet Channel URL: https://nav-alliance.org/multi-gig-cables-connectors-channel-design/ Published: 2026-05-05 At 100 Mb/s almost any twisted pair works. At 10 Gb/s and beyond, the channel — cable, connectors, PCB traces and everything in between — decides whether a link has margin for fifteen years on the road or fails on a cold morning. This guide explains the key channel parameters, the cable and connector types used for Multi-Gig automotive Ethernet, and practical harness design tips. ## Key takeaways - A channel is specified by insertion loss, return loss, crosstalk, mode conversion and shielding/coupling attenuation over frequency. - Multi-Gig automotive links use shielded parallel or twisted pairs and, in some designs, coaxial cable. - Inline connectors are the biggest source of reflections; their number and quality limit reach. - Ageing, temperature and humidity change cable behaviour — design with margin. ## What "the channel" means In IEEE terms, the link segment is the cabling between the two MDI connectors of the communicating devices, including inline connectors. The full channel seen by a PHY also includes the PCB traces, common-mode chokes, ESD protection and connector footprint between the PHY pins and the MDI — sometimes called the MDI-to-PHY channel. NAV Alliance TWG1/TWG2 defined specifications for both portions for 25G and 50G links, because at these speeds the PCB can consume a significant part of the loss budget. ## Key parameters ParameterWhat it describesWhy it matters at Multi-Gig Insertion loss (IL)Signal attenuation versus frequencyRises with frequency and length; sets maximum reach Return loss (RL)Energy reflected by impedance mismatchesReflections appear as echo the PHY must cancel Micro-reflectionsSmall periodic impedance variations along the cableCan create narrow notches in the channel response Crosstalk / alien crosstalkCoupling between neighbouring pairs or cablesAdds noise that cannot be cancelled Mode conversion (LCL/LCTL)Differential ↔ common-mode conversionDrives emissions and susceptibility Coupling attenuation / screeningShield effectivenessProtects against RF ingress and limits emissions ## Cable types ## Shielded parallel pair (SPP) and shielded twisted pair (STP) Two insulated conductors under a common foil and/or braid shield. Parallel pairs (not twisted) can offer very consistent impedance and low skew at high frequency; twisted versions add some intrinsic balance. These cables are the natural medium for single-pair Ethernet PHYs such as 10GBASE-T1 and 25GBASE-T1. ## Coaxial cable A single centre conductor surrounded by dielectric and a braided shield, as shown in our article image. Coax is widely used for camera SerDes links and supports power over coax. It is a single-ended medium, so PHYs designed for differential pairs require adaptation; some automotive Ethernet and asymmetric solutions support coax operation. ## Optical fibre For the highest immunity, IEEE 802.3cz specifies multimode glass optical fibre at 2.5 to 50 Gb/s — no electrical coupling at all, at the cost of optical connector handling. ## Connectors Automotive high-speed connector families — for example Rosenberger's H-MTD® (differential) and HFM® (coaxial) systems, along with comparable families from other suppliers — are designed for controlled impedance, 360° shielding, mechanical robustness and automated harness assembly. Every inline connector, however, introduces a small impedance discontinuity and therefore a reflection. Standards define channels with a maximum number of inline connectors (IEEE 802.3ch specifies up to four in a 15 m link segment). At 25 and 50 Gb/s, connector quality, the number of inline connections and their spacing become critical design choices. Spacing mattersReflections from two connectors combine; at certain spacings they add up constructively at frequencies inside the signal band. Channel simulation with real connector models helps avoid unlucky combinations. ## Environmental effects and ageing - Temperature: insertion loss increases with temperature; a channel that passes at 23 °C may lack margin at 105 °C. - Humidity: moisture ingress into the dielectric can raise loss over time; jacket materials and sealing matter. - Mechanical stress: tight bends, crushing and vibration change geometry and impedance; respect minimum bend radii. - Connector wear: mating cycles and fretting corrosion affect contact resistance and shielding. Specifications therefore define requirements over temperature and after ageing, and designers keep margin for the vehicle's lifetime. ## PCB and MDI design From the PHY pins to the connector, keep differential pairs symmetric and short, minimize vias and remove via stubs, maintain a continuous reference plane, and follow the PHY vendor's reference design for common-mode chokes, termination and ESD protection. NAV Alliance TWG3 addresses PCB design rules, additional components and diagnosis for Multi-Gig PHY integration in ECUs and vehicle computers. ## Power over the same cable Cameras and some sensors receive power over the data cable — Power over Data Lines (IEEE 802.3bu) on pairs or power over coax. The coupling network (inductors and capacitors) must pass DC while being invisible at signal frequencies; its parasitics enter the channel budget. See PoDL and Energy-Efficient Ethernet. ## Harness design tips - Choose the cable and connector system for the highest data rate you expect over the platform life, not just today's. - Minimize the number of inline connectors on Multi-Gig links; place necessary ones thoughtfully. - Keep high-speed bundles away from high-voltage and high-current cables. - Specify and verify channel parameters with vector network analyzer measurements on production-representative harnesses. - Use the PHY's built-in diagnostics (signal quality indicators, cable tests) in validation and in the field. ## Frequently asked questions ## Can I reuse 1 Gb/s cabling for 10 Gb/s? Usually not without verification. Multi-Gig PHYs require channels specified up to much higher frequencies, generally shielded. ## Coax or shielded pair? Both are used. The choice depends on the PHY, power delivery, harness standardization and the OEM's connector strategy. ## How long can the link be? IEEE 802.3ch targets up to 15 m with four inline connectors; higher-rate links may target shorter reaches. Use our glossary for terms and contact us for design reviews. Updated November 2026. Connector trade names are trademarks of their respective owners. --- # Securing the In-Vehicle Network: MACsec, Firewalls and ISO/SAE 21434 URL: https://nav-alliance.org/automotive-ethernet-security-macsec/ Published: 2026-03-10 The more a vehicle is connected — to the cloud, to chargers, to phones, to other vehicles — the more its internal network becomes a target. Multi-Gig Ethernet brings enormous capacity into the car, and with it a responsibility: every link, switch and endpoint must be designed to resist attack. This article outlines a defense-in-depth approach for in-vehicle Ethernet and how it maps to regulation. ## Key takeaways - Regulation now requires cybersecurity management for new vehicles in many markets (UN Regulation No. 155) and engineering per ISO/SAE 21434. - MACsec (IEEE 802.1AE) authenticates — and can encrypt — every Ethernet frame between neighbouring nodes at line rate. - Segmentation (VLANs), switch firewalls, per-stream policing and intrusion detection limit what an attacker can reach. - Security starts at boot: secure boot, hardware security modules and protected keys anchor trust. ## The regulatory backdrop UN Regulation No. 155 (UN R155) requires vehicle manufacturers in participating markets to operate a certified Cyber Security Management System and to demonstrate that vehicle types are protected against identified threats; UN R156 covers software update management. ISO/SAE 21434, "Road vehicles — Cybersecurity engineering", defines the engineering process: threat analysis and risk assessment (TARA), cybersecurity goals and requirements, verification and validation, and post-production monitoring. The in-vehicle network is central to many identified threats — spoofing of messages, tampering with sensor data, denial of service and lateral movement from a compromised ECU. ## Threats to in-vehicle Ethernet ThreatExampleMitigations SpoofingA compromised ECU sends fake brake or camera dataMACsec, message authentication, switch ingress filtering TamperingDevice inserted into a harness alters trafficMACsec integrity protection, link monitoring EavesdroppingInterception of personal or proprietary dataMACsec encryption, TLS at higher layers Denial of serviceFlooding the backbonePer-stream policing (802.1Qci), rate limits, segmentation Lateral movementFrom infotainment to safety domainVLAN segmentation, firewalls in switches and gateways PersistenceMalicious firmware on an ECUSecure boot, signed updates (UN R156), attestation ## MACsec: security at the link layer MACsec, standardized in IEEE 802.1AE, protects Ethernet frames hop by hop. Each protected frame carries a security tag and an integrity check value computed with AES-GCM; optionally the payload is encrypted. Because MACsec operates at Layer 2, it protects all traffic on a link — IP, AVTP video, SOME/IP, diagnostics — without changes to applications. Modern automotive PHYs and switches implement MACsec in hardware at full Multi-Gig line rate with minimal added latency. ## Key management MACsec needs keys. IEEE 802.1X defines the MACsec Key Agreement protocol (MKA), which uses pre-shared or derived connectivity association keys to distribute and rotate session keys. In vehicles, long-term keys are typically provisioned at the end of line and stored in a hardware security module; MKA then establishes sessions automatically at every start-up. The design must balance security with fast network start-up. ## Authentication-only or encryption? Many automotive use cases need integrity and authenticity more than confidentiality: it matters that a camera frame is genuine, less that it is secret. Authentication-only (integrity) mode keeps payloads in clear text for diagnostics while preventing tampering. Encryption is applied where privacy or intellectual property is at stake. Why not only TLS or IPsec?Higher-layer protocols protect specific applications end to end and remain useful. MACsec complements them by protecting every frame on every link, including non-IP traffic such as IEEE 1722 sensor streams. ## Segmentation and firewalls Not every ECU needs to talk to every other ECU. VLANs divide the physical network into logical segments — for example safety, body, infotainment and diagnostics — and switches forward frames only within allowed segments. Automotive switches increasingly include Layer 2–4 firewall functions: access-control lists that check addresses, protocols and ports at line rate. Central gateways or zone controllers enforce policies between domains and towards external interfaces such as the telematics unit or the diagnostic connector. ## Policing, monitoring and intrusion detection TSN per-stream filtering and policing (IEEE 802.1Qci) limits each stream to its expected rate and timing, containing faulty or compromised nodes — see TSN in the vehicle. On top of that, intrusion detection systems (IDS) monitor traffic patterns, unexpected addresses, protocol violations and timing anomalies. Switches can mirror or summarize traffic for a host-based IDS, and security events are reported to the vehicle security operations centre as required for post-production monitoring under ISO/SAE 21434. ## Secure boot and trusted firmware Network protection is only as strong as the devices it connects. Every switch, PHY with integrated processor, zone controller and computer should verify the signature of its firmware at start-up (secure boot), store keys in a hardware security module or secure element, and accept only signed and authorized updates. Debug interfaces must be locked in production. ## Security by design in the architecture - Minimize the attack surface: disable unused ports and services. - Apply least privilege to communication: allow-list flows, deny everything else. - Separate safety-critical and non-critical traffic physically or logically. - Protect sensor links — spoofed camera images are a credible threat for automated driving. Asymmetrical Ethernet sensors can use MACsec like any other node. - Plan for crypto agility and key rotation over a fifteen-year vehicle life. - Log securely and support forensic analysis. ## Performance considerations Hardware MACsec adds a few bytes per frame (security tag and integrity check value) and a small fixed latency. At Multi-Gig speeds the overhead is negligible for large frames but noticeable for very small control frames; designers include it in bandwidth budgets. Key exchange time affects network start-up and must be considered for fast-wake requirements. ## Frequently asked questions ## Is MACsec mandatory? No standard mandates MACsec specifically, but UN R155 and ISO/SAE 21434 require appropriate mitigations for identified risks, and MACsec is a widely adopted solution for link-level protection. ## Does MACsec work across switches? MACsec is hop-by-hop: each link has its own security association, and switches decrypt and re-protect frames. Switches therefore must be trusted and secured themselves. ## Does the NAV Alliance address security? Creating procedures and specifications to ensure interoperability, security and reliability of the network is one of the alliance's founding objectives. Learn more about the alliance. Updated November 2026. This article is informational and not legal or compliance advice. --- # EMC for Multi-Gig Automotive Ethernet: Emissions, RF Ingress and How to Pass URL: https://nav-alliance.org/automotive-ethernet-emc-rf-ingress-emissions/ Published: 2026-01-14 Few environments are as electromagnetically hostile as a modern car. Electric drive inverters switch hundreds of amperes in nanoseconds; DC-DC converters, ignition systems and wireless chargers radiate; and the car itself carries sensitive radio receivers for AM/FM, DAB, GNSS, cellular and Wi-Fi. A Multi-Gig Ethernet link must neither disturb those receivers nor be disturbed by everything around it. That is the discipline of electromagnetic compatibility (EMC) — and it is one of the main reasons NAV Alliance working groups specify EMC requirements alongside PHY speeds. ## Key takeaways - EMC has two halves: emissions (what the link radiates) and immunity (how it tolerates disturbance, including RF ingress). - Higher data rates spread energy to higher frequencies, raising both emission risk and sensitivity. - Balance and mode conversion of the channel are as important as shielding. - Tests include CISPR 25 emissions, bulk current injection, stripline and direct power injection — plus vehicle-level validation. - NAV Alliance TWG1/TWG2 defined RF-ingress characterization and limit lines at PHY inputs for 25G/50G links. ## Emissions: staying quiet A differential signal on a perfectly balanced pair produces fields that largely cancel. In practice, small imbalances in the cable, connectors, PCB traces or PHY output convert part of the differential signal into common-mode current, which radiates efficiently from the cable acting as an antenna. Automotive emission limits are strict because the receivers they protect operate at very low signal levels. CISPR 25, the international standard for vehicle component emissions, defines measurement methods and limit classes for conducted and radiated emissions across the bands used by vehicle receivers. Design measures to reduce emissions include: - shielded cables and connectors with low-impedance 360° shield termination; - tightly controlled balance in cable manufacturing and connector design (low mode conversion); - common-mode chokes and careful filtering in the MDI circuit; - PHY transmit spectra shaped to minimize energy in sensitive bands; - PCB layout with continuous reference planes and symmetric differential routing. ## Immunity and RF ingress: staying robust Immunity is the ability to operate correctly in the presence of disturbances. For Ethernet links the critical mechanism is RF ingress: external fields induce common-mode currents on the cable shield or conductors; any imbalance converts part of this into differential noise at the receiver. At Multi-Gig speeds the receiver's eye opening is small — with PAM4, each level is a third of the swing — so the tolerable noise is limited. Robust links rely on: - good shielding effectiveness and coupling attenuation of the cable and connectors; - high common-mode rejection in the PHY receiver; - forward error correction sized for burst errors; - fast adaptation and retraining strategies that maintain the link during transients. The NAV Alliance TWG1/TWG2 charter included characterizing and measuring the RF ingress over target channels (cables, connectors, module) and defining limit lines for RF ingress levels at PHY inputs for 25G and 50G links. Such limit lines bridge two worlds: they tell PHY designers what disturbance the receiver must survive and tell harness suppliers how much the channel may let through. ## Why EMC gets harder at higher speed FactorEffect of higher data rate Signal bandwidthExtends into hundreds of MHz to several GHz, overlapping more radio services Cable and connector behaviourImbalances and shield transfer impedance matter at higher frequencies Receiver noise marginSmaller eye openings, more sensitive to residual differential noise PCB effectsVia stubs, reference-plane gaps and connector footprints become significant ## Common test methods - CISPR 25 — conducted and radiated emission measurements of components and modules in a shielded (anechoic) chamber. - Bulk current injection (BCI, ISO 11452-4) — RF current is injected onto the harness with a clamp to simulate coupling from nearby fields. - Radiated immunity (ISO 11452-2) — the device under test is exposed to strong RF fields from an antenna. - Stripline and TEM cell tests — controlled field coupling into cables for repeatable channel characterization. - Direct power injection (IEC 62132-4) — RF injected at IC pins to characterize PHY immunity at chip level. - Transient tests (ISO 7637) — fast electrical transients on supply and signal lines. Component-level tests are complemented by vehicle-level validation, because harness routing and grounding in the real car determine the final coupling. ## Design checklist for Multi-Gig EMC - Choose cable and connector systems specified for the target data rate with documented coupling attenuation and mode-conversion performance. - Follow the PHY vendor's MDI reference design, including common-mode termination and ESD protection placement. - Route differential pairs symmetrically with matched lengths and minimal via transitions; keep a solid reference plane. - Terminate shields 360° at the connector and the housing; avoid pigtails. - Separate high-speed harness bundles from high-power cables, especially in electric vehicles. - Verify early with near-field scans and pre-compliance tests before formal CISPR 25 measurements. - Monitor link-quality indicators (such as SQI) during immunity tests to measure remaining margin, not just pass/fail. Need a second pair of eyes?NAV Alliance offers a pre-compliance design review for Multi-Gig PHY integration — schematic, layout and channel checks before you book the chamber. ## Electric vehicles raise the bar High-voltage inverters, on-board chargers and DC-DC converters generate strong broadband disturbances, and their cables run close to data harnesses. EV platforms often impose tighter internal limits than the baseline standards. Optical links (IEEE 802.3cz) are one option where electrical immunity margins are hard to achieve; careful harness separation and shielding are the other. ## Frequently asked questions ## Is shielding always required for Multi-Gig links? For 2.5 Gb/s and above, shielded pairs or coax are typical in automotive designs. Unshielded operation is common at 100 Mb/s and 1 Gb/s. ## What is mode conversion? The conversion between differential and common-mode signals caused by imbalance. Low mode conversion means lower emissions and better immunity. ## Who defines the EMC limits for my product? Standards such as CISPR 25 define methods and classes; each OEM specifies the limits and test levels in its component requirements. Updated November 2026. --- # Time-Sensitive Networking (TSN) in the Vehicle: Deterministic Ethernet Explained URL: https://nav-alliance.org/time-sensitive-networking-tsn-in-vehicle/ Published: 2025-10-21 Classic Ethernet delivers frames "as soon as possible" — usually fast, but with no guarantee. A braking command or a camera frame used for emergency steering cannot rely on "usually". Time-Sensitive Networking (TSN), a set of IEEE 802.1 standards, adds synchronized time, bounded latency and seamless redundancy to Ethernet. In 2025 the IEEE published 802.1DG, a TSN profile specifically for automotive in-vehicle networks. ## Key takeaways - TSN is a toolbox, not a single protocol: time synchronization, traffic shaping and scheduling, redundancy, policing and configuration. - gPTP (IEEE 802.1AS) gives every node a common sense of time — the basis for sensor fusion and scheduled traffic. - Shapers such as credit-based shaping (802.1Qav) and time-aware shaping (802.1Qbv) bound latency for critical streams. - Frame replication and elimination (802.1CB) delivers seamless redundancy; per-stream filtering and policing (802.1Qci) contains faults. - IEEE 802.1DG-2025 selects and parameterizes these features for in-vehicle use, improving interoperability. ## From AVB to TSN TSN grew out of Audio Video Bridging (AVB), developed for professional and consumer audio/video. AVB introduced precise time synchronization and reserved bandwidth for media streams, and it found early use in automotive infotainment. As Ethernet moved into safety-relevant domains, the IEEE 802.1 working group broadened the scope to Time-Sensitive Networking for industrial, automotive and other applications. Today TSN refers to dozens of amendments to IEEE 802.1Q and related standards. ## The TSN toolbox FunctionStandardWhat it doesTypical automotive use Time synchronizationIEEE 802.1AS (gPTP)Synchronizes clocks across bridges and endpoints to sub-microsecond precisionSensor fusion timestamps, scheduled traffic, AVTP presentation time Credit-based shaperIEEE 802.1QavSmooths stream traffic to reserved bandwidthAudio/video streams, cameras Time-aware shaperIEEE 802.1QbvOpens and closes queue gates on a cyclic scheduleHard real-time control loops Frame preemptionIEEE 802.1Qbu / 802.3brInterrupts long low-priority frames for urgent onesLower latency on slower links Per-stream filtering & policingIEEE 802.1QciEnforces per-stream rate and timing limits at ingressFault containment ("babbling idiot" protection), security Frame replication & eliminationIEEE 802.1CBSends duplicates over disjoint paths, removes duplicates at the receiverFail-operational backbones Asynchronous traffic shapingIEEE 802.1QcrBounded latency without network-wide scheduleMixed-criticality backbones ## Time synchronization with gPTP gPTP elects a grandmaster clock and propagates its time through every bridge, measuring and compensating link delays and the residence time of frames in each switch. The result is a common timebase across the vehicle. Why it matters: - Sensor fusion aligns camera, radar and lidar measurements by capture time. A misalignment of a millisecond at highway speed corresponds to around three centimetres of motion — significant for precise perception. - Scheduled traffic (802.1Qbv) requires every switch to open its gates at the same instants. - Media playback across multiple speakers and displays stays in sync. For safety, automotive networks often run redundant time domains and monitor clock quality, so a faulty grandmaster cannot silently corrupt timestamps. ## Bounding latency: shapers and schedules Ethernet switches use priority queues, but strict priority alone cannot guarantee latency when bursts collide. Credit-based shaping limits how much bandwidth each stream class may consume, protecting lower classes and bounding delay for the shaped class. Time-aware shaping goes further: it divides time into cycles and reserves windows in which only critical traffic may transmit, giving deterministic latency and near-zero jitter — at the price of network-wide schedule configuration. Many automotive designs combine strict priority, credit-based shaping for streams and a limited use of time-aware windows for the most critical control traffic. Practical noteAt Multi-Gig speeds, a maximum-size frame occupies a 10 Gb/s link for only about 1.2 µs. Higher link speeds therefore reduce the latency penalty of contention by themselves — one reason Multi-Gig and TSN complement each other. ## Redundancy and fault containment Higher automation levels require fail-operational behaviour: a single failure must not stop a critical function. IEEE 802.1CB replicates frames of critical streams at the source or an intermediate bridge, sends them over disjoint paths (for example both directions of a ring backbone) and eliminates duplicates at the destination using sequence numbers. A cable break or switch failure causes no frame loss and no recovery delay. Per-stream filtering and policing (802.1Qci) protects the network from misbehaving nodes: if a faulty ECU starts flooding traffic, the switch drops its excess frames at ingress so other streams keep their guarantees. The same mechanism limits the impact of certain cyber-attacks — see automotive Ethernet security. ## IEEE 802.1DG: the automotive TSN profile The TSN toolbox is large, and different suppliers implementing different subsets would harm interoperability. IEEE 802.1DG, Time-Sensitive Networking Profile for Automotive In-Vehicle Ethernet Communications, was approved in May 2025 and published in June 2025. It provides guidance to automotive vendors and suppliers on designing vehicular systems with bounded latency, and on using IEEE 802.1 features to meet the bandwidth, latency and synchronization needs of in-vehicle communications — addressing the industry's move toward autonomous and software-defined vehicles. A profile like this lets OEMs specify "802.1DG-conformant" switches and endpoints instead of long feature lists. ## Configuration: static by design Enterprise and industrial TSN networks often use dynamic configuration. Vehicles are different: the network is known at design time and does not change in the field except through controlled software updates. Most automotive TSN networks are therefore configured statically — stream reservations, schedules and policers are computed by tools during development and flashed into the switches. This makes behaviour verifiable, which is important for functional safety (ISO 26262). ## TSN and Multi-Gig together In a zonal architecture, the backbone mixes camera streams, control messages, diagnostics and bulk transfers like software updates. Multi-Gig links provide the capacity; TSN guarantees that capacity is shared predictably. NAV Alliance TWG5 (System Controls and Management) covers related topics including Quality of Service, redundancy and diagnosis for the in-vehicle network. ## Frequently asked questions ## Do all automotive Ethernet networks need TSN? No. Infotainment or diagnostic networks may work fine with priorities alone. Safety-relevant and high-load backbones benefit most. ## Is TSN a replacement for FlexRay? For many applications, yes: TSN over Ethernet provides deterministic communication with far more bandwidth, while FlexRay remains in legacy designs. ## How precise is gPTP in a car? Well-implemented gPTP networks achieve synchronization on the order of tens to hundreds of nanoseconds between nodes, more than sufficient for sensor fusion. Updated November 2026. Standards references are informative summaries. --- # Protocol Encapsulation over Ethernet: Carrying I2C, SPI, Camera and Radar Data URL: https://nav-alliance.org/protocol-encapsulation-over-ethernet-i2c-spi-camera/ Published: 2025-09-18 The sensors and peripherals in a vehicle speak many languages: I2C and SPI for configuration, MIPI CSI-2 for cameras, proprietary interfaces for radar and lidar, CAN for control. To unify them on one Ethernet network, their data has to be carried inside Ethernet frames — encapsulated — without breaking the devices that rely on it. This is the scope of the NAV Alliance working group TWG4, Protocol Encapsulation for Ethernet. ## Key takeaways - Encapsulation wraps a native protocol's data in Ethernet frames so it can cross a switched network and be unwrapped at the destination. - TWG4 targets I2C, SPI, camera interfaces and radar/lidar data, with three principles: backwards compatibility with Ethernet frame formats, extensibility, and no duplication where other relevant standards exist. - IEEE 1722 (AVTP) already defines formats for video, audio and control-bus tunnelling and is a key building block. - Timing, latency and error handling must be preserved — especially for control buses that expect immediate acknowledgements. ## Why encapsulate at all? The industry is moving sensors from dedicated point-to-point links to the vehicle Ethernet network, as described in our article on Asymmetrical Ethernet. But the image sensor inside a camera still outputs MIPI CSI-2, and its registers are still configured over I2C. A radar front end may deliver raw ADC samples over a high-speed serial interface. Rather than redesigning every sensor, encapsulation lets these native interfaces ride over Ethernet transparently: - Video and sensor data are packetized at the sensor and reassembled at the computer. - Control transactions (I2C reads/writes, SPI transfers, GPIO events) are carried as messages in the opposite direction. - Timing information (frame start, trigger signals, timestamps) is conveyed so the receiver can reconstruct the original timing relationships. ## Design principles defined by TWG4 PrincipleWhat it means in practice Backwards compatibility with existing Ethernet frame formatsEncapsulated traffic must be ordinary Ethernet frames — standard switches, MACsec, VLANs and diagnostics continue to work without modification. Extensibility and adaptabilityThe scheme must accommodate new or evolving protocols and sensor types without a redesign. No duplication of existing standardsWhere a relevant standard already exists (for example IEEE 1722 formats), it is reused rather than re-invented. ## The building block: IEEE 1722 (AVTP) IEEE 1722, the Audio Video Transport Protocol, was developed for time-sensitive audio and video over Ethernet and has grown into a general transport for automotive streams. It defines stream formats for compressed and uncompressed video, audio, and — through its Alternative Control Format (ACF) — messages for CAN, LIN, FlexRay, GPIO, serial ports and sensor data. AVTP streams carry a presentation time derived from the gPTP-synchronized network clock (IEEE 802.1AS), so a receiver knows exactly when each sample or frame was captured. For cameras, encapsulating CSI-2 packets into AVTP or a similar format lets the computer's receiver reconstruct the CSI-2 stream and feed it into an existing image signal processor. For control, ACF messages carry bus transactions with timestamps. ## Encapsulating control buses: I2C and SPI I2C and SPI are synchronous, master-driven buses. An I2C master expects a slave to acknowledge each byte within microseconds; it may also stretch the clock while waiting. Directly extending that handshake across a network would be impractical. Encapsulation schemes therefore typically use one of two approaches: - Transaction-level tunnelling: the host sends a complete transaction ("write these bytes to register X of device Y" or "read N bytes") in one Ethernet message; a bridge at the sensor executes it locally on the I2C/SPI bus and returns the result and status. - Remote device abstraction: software on the host sees a virtual I2C/SPI controller whose driver translates calls into network messages, keeping existing sensor drivers unchanged. Either way, the system must handle lost or delayed messages with timeouts and retries, and must protect control traffic — reconfiguring a camera is a security-relevant action, so integrity protection (for example MACsec) is essential. ## Radar and lidar data Radar and lidar sensors increasingly move from sending object lists (small, processed data) to sending raw or lightly processed data for central fusion. Imaging radar may stream radar cubes; lidar sends point clouds. These streams are bursty and synchronized to the sensor's measurement cycle. Encapsulation must preserve measurement timestamps and support efficient packetization of large blocks, while letting the network prioritize them alongside cameras with TSN mechanisms. ## Latency, jitter and synchronization Encapsulation adds a small amount of latency for packetization and buffering, plus switch transit time. For perception pipelines, what matters is that latency is bounded and timestamps are accurate: sensor fusion aligns data by capture time, not arrival time. With gPTP synchronization and TSN shaping, end-to-end latency in a well-designed network is predictable at the microsecond level. See TSN in the vehicle. Engineering tipTimestamp at the source. Capturing the gPTP time when the image sensor's frame starts — not when the Ethernet frame leaves the camera — gives fusion software the information it really needs. ## Bandwidth efficiency Headers cost bandwidth. A 1500-byte payload in an Ethernet frame with IP/UDP or AVTP headers plus preamble and inter-frame gap has an overhead in the range of a few percent; small frames have much higher relative overhead. Video encapsulation therefore packs full lines or multiple lines per frame, and some links use larger frames where all devices support them. Our bandwidth calculator lets you include a protocol-overhead percentage when sizing links. ## Error handling and diagnostics - Sequence numbers detect lost frames; video receivers can conceal or flag missing lines. - Frame counters and checksums let safety software detect frozen or repeated images. - Control transactions return explicit status codes and are retried on timeout. - Bridges report statistics through the network management interface defined by the vehicle's management protocol. ## Frequently asked questions ## Is protocol encapsulation the same as a gateway? No. A gateway translates between protocols and often terminates them. Encapsulation carries the native protocol transparently so the endpoints can behave as if directly connected. ## Does encapsulation require special switches? No — that is the point of backwards compatibility. Standard Ethernet switches forward encapsulated frames like any other traffic; TSN features help guarantee timing. ## How can I participate in TWG4? Engineers from Promoter and Contributor companies can join. See Working Groups and Membership. Updated November 2026. --- # Zonal Architecture and the Software-Defined Vehicle: Why the Ethernet Backbone Matters URL: https://nav-alliance.org/zonal-architecture-software-defined-vehicle-ethernet-backbone/ Published: 2025-07-29 For thirty years, cars gained features by gaining boxes: one electronic control unit per function, each with its own wiring. Premium vehicles reached more than a hundred ECUs and several kilometres of copper. The software-defined vehicle reverses that trend — and the zonal architecture with a Multi-Gig Ethernet backbone is how it is built. ## Key takeaways - Zonal architecture groups devices by physical location instead of by function, cutting wiring length, weight and complexity. - Zone controllers connect to a few central computers over a high-speed Ethernet backbone, typically 10 Gb/s today and 25 Gb/s or more next. - Software features become independent of where hardware is installed — the foundation of the software-defined vehicle (SDV). - The backbone must be deterministic, redundant, secure and manageable — not just fast. ## From domains to zones Early electrical/electronic (E/E) architectures were distributed: every function had its own ECU. The next generation introduced domain architectures, where powerful domain controllers handled groups of related functions — powertrain, chassis, body, infotainment, driver assistance — still wired by function across the whole car. A door-mirror motor and the rear lights might connect to different domain controllers on opposite sides of the vehicle. In a zonal architecture, the vehicle is divided into physical regions — typically front-left, front-right, rear-left, rear-right and sometimes a centre or cockpit zone. A zone controller in each region connects every sensor and actuator nearby, whatever its function, and handles local power distribution. The zone controllers in turn connect to one or a few central vehicle computers that run the application software. AspectDistributedDomainZonal OrganizationOne ECU per functionController per function groupController per physical zone + central compute WiringVery long, function-specificLongShort local runs + backbone NetworkCAN, LIN, FlexRayCAN + EthernetEthernet backbone + CAN/10BASE-T1S edge Software updatesMany ECUs, many suppliersFewer controllersCentralized, OTA-friendly ## What the backbone carries The backbone is the set of links between zone controllers and central computers, and between the computers themselves. It carries: - raw or lightly processed sensor data from cameras, radar and lidar connected to the zones; - actuator commands for steering, braking, lighting, doors and climate; - tunnelled legacy traffic from CAN and LIN devices that remain at the edge; - diagnostics, logging and over-the-air update data; - time-synchronization and network-management messages. Because one link aggregates many sources, backbone bandwidth grows quickly. A typical first-generation zonal design uses 1 to 10 Gb/s links; architectures for high levels of automation plan for 25 and 50 Gb/s using IEEE 802.3cy PHYs. Use our camera bandwidth calculator to estimate how many sensors fit on a given backbone link. ## Topologies and redundancy A safety-relevant vehicle function must keep working if a single link or switch fails. Common backbone topologies include: - Star: each zone connects directly to the central computer. Simple and low-latency, but the computer is a single point of failure unless duplicated. - Dual star: each zone connects to two redundant computers, providing fail-operational behaviour. - Ring: zones connect in a ring so traffic can reach the computer in either direction; combined with frame replication (IEEE 802.1CB) a single break causes no data loss. - Mesh / hybrid: combinations tuned to the vehicle's safety concept and harness routing. Deterministic behaviour is provided by Time-Sensitive Networking: synchronized clocks, traffic shaping and seamless redundancy. See TSN in the vehicle. ## The edge: CAN, LIN and 10BASE-T1S Not every device needs gigabits. Window motors, seat controls and many sensors need only a few kilobits per second. Zonal architectures keep low-cost buses at the edge: CAN and CAN FD (and increasingly CAN XL), LIN, and 10BASE-T1S — a 10 Mb/s multidrop Ethernet standardized in IEEE 802.3cg that lets several nodes share one unshielded pair. 10BASE-T1S is attractive because it extends Ethernet addressing and security all the way to simple devices without the cost of a switch port per node. ## Why this enables the software-defined vehicle In a software-defined vehicle, features are implemented mainly in software on central computers and can be updated or added over the air throughout the vehicle's life. The zonal architecture decouples software from wiring: an application that controls the rear lights does not care which zone controller drives them, because the backbone delivers its commands as service-oriented messages (for example SOME/IP) or data streams. This separation lets OEMs: - update and add features without changing hardware; - reuse the same software across vehicle models with different physical layouts; - consolidate compute, reducing the number of ECUs and suppliers to coordinate; - collect fleet data for continuous improvement of driver-assistance functions. ## Harness and weight benefits Because devices connect to the nearest zone controller, wire runs become shorter and the harness can be split into simpler, more automatable sections. Industry studies and OEM announcements have reported substantial reductions in harness length and weight when moving to zonal designs — relevant for every vehicle and especially for electric vehicles, where weight affects range. Zone controllers also take over power distribution with electronic fuses, replacing traditional fuse boxes. ## Requirements for a zonal Ethernet backbone ChecklistBandwidth with headroom for growth · deterministic latency (TSN) · redundancy without single points of failure · security on every link (MACsec, firewalls) · fast wake-up and low sleep current · rich diagnostics · long-term availability of silicon and connectors. NAV Alliance TWG5 — System Controls and Management — addresses several of these: the identification of key in-vehicle network features for autonomous systems, interface definitions and an automotive network management protocol covering enhanced diagnosis, predictive maintenance, redundancy, Quality of Service, wake-up and sleep and device management. See the working groups. ## Migration path - Introduce a gigabit Ethernet backbone between existing domain controllers. - Add zone controllers that aggregate body and comfort functions and tunnel CAN/LIN traffic. - Consolidate application software onto central computers with service-oriented communication. - Move sensors to zone controllers with Multi-Gig and Asymmetrical Ethernet links. - Scale the backbone to 25/50 Gb/s and add redundancy for higher automation levels. ## Frequently asked questions ## How many zones does a vehicle have? Typically four to six, depending on vehicle size and the OEM's architecture. ## Is Ethernet the only option for the backbone? For high bandwidth, Ethernet is the de facto choice because of its switching, security and software ecosystem. Edge networks continue to use CAN, LIN and 10BASE-T1S. ## Does zonal architecture increase latency? An extra switch hop adds microseconds, not milliseconds. With TSN scheduling, end-to-end latency is bounded and predictable. Updated November 2026. --- # 25G and 50G Automotive Ethernet PHYs: Inside IEEE 802.3cy URL: https://nav-alliance.org/25g-50g-automotive-ethernet-phy-ieee-802-3cy/ Published: 2025-06-12 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 caseTypical requirementSuitable PHY Zone → central compute (sensor aggregation)15 – 40 Gb/s25GBASE-T1 / 50GBASE-T1 Compute ↔ compute (redundant AI computers)25 – 100 Gb/s50GBASE-T1 / 100GBASE-T1 Compute → data logger (development fleets)25 – 50 Gb/s25GBASE-T1 / 50GBASE-T1 High-resolution sensor (asymmetric)10 – 25 Gb/s uplinkAsymmetric 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. --- # Asymmetrical Ethernet for Cameras and Sensors: Why Uplink and Downlink Should Differ URL: https://nav-alliance.org/asymmetrical-ethernet-cameras-sensors/ Published: 2025-04-22 A camera in a modern vehicle sends gigabits of image data per second towards the central computer — and receives only a trickle of configuration and control messages in return. Asymmetrical Ethernet is built around that imbalance. It is the sensor interface the NAV Alliance promotes, and it is now being standardized in IEEE P802.3dm. ## Key takeaways - Sensor traffic is extremely asymmetric: multi-gigabit upstream, megabits downstream. - Asymmetrical Ethernet uses a high-speed uplink and a low-speed back channel on the same single pair or coax, saving power, cost and heat at the sensor. - Video enters the vehicle Ethernet network directly — switchable, time-synchronized, secured and diagnosed like any other traffic. - Energy-Efficient Ethernet (EEE) further reduces power when the sensor idles. - IEEE P802.3dm (Asymmetrical Electrical Automotive Ethernet) passed IEEE 802.3 working-group ballot in 2026 and is heading to IEEE SA ballot. ## The problem: symmetric links for asymmetric traffic Standard Ethernet PHYs are symmetric: a 10GBASE-T1 link offers 10 Gb/s in each direction at the same time. That is ideal between switches and computers, where traffic flows both ways. A camera, however, mostly talks and rarely listens. Its downstream traffic — register writes, exposure settings, frame triggers, time-synchronization messages, occasional firmware updates — needs perhaps tens of megabits per second at most. A symmetric PHY at the camera still has to build a full-rate transmitter and receiver for both directions, with the associated silicon area, power and heat inside a small, sealed housing that is often mounted behind a hot windshield. That is why the industry has relied on point-to-point serializer/deserializer (SerDes) links for cameras: they are inherently asymmetric and efficient. But SerDes creates separate islands outside the Ethernet network, requiring bridge chips at the ECU, proprietary configuration channels and separate diagnostics. ## How Asymmetrical Ethernet works An asymmetrical link pairs a high-speed transmitter at the sensor with a low-speed transmitter at the ECU or zonal controller. Both share the same physical medium — a single shielded pair or a coaxial cable — and the PHYs separate the two directions with echo cancellation and frequency planning. Conceptually: Uplink (sensor → ECU)Downlink (ECU → sensor) PurposeVideo, point clouds, radar cubesControl, configuration, triggers, time sync, updates Data rate classMulti-gigabit (target speeds up to ~10 Gb/s in P802.3dm)Tens to hundreds of Mb/s Transmitter complexityHigh (at the sensor)Low (at the ECU) Power focusMinimize at the sensor endNot critical Because the frames are Ethernet frames, the sensor can be a normal network endpoint with a MAC address. Its stream can be switched to several consumers — the perception computer, a redundant safety computer and a data logger — without special splitter hardware. ## Why Ethernet end-to-end matters - Switching and replication. Streams can be routed or duplicated by standard Ethernet switches, enabling redundancy and flexible software-defined architectures. - Time synchronization. gPTP (IEEE 802.1AS) timestamps let the computer align frames from many sensors precisely for sensor fusion. See TSN in the vehicle. - Security. MACsec can authenticate and encrypt sensor data on the link, defending against spoofed camera feeds. See our security article. - One diagnostic model. Link quality, cable faults and errors are reported the same way as everywhere else in the network. - Fewer bridge chips. Removing SerDes-to-Ethernet bridges in the ECU saves cost and board space. ## Energy-Efficient Ethernet at the sensor Even a busy camera does not transmit continuously: there are gaps between lines and frames, and many sensors are only needed in certain driving modes (for example parking cameras). Energy-Efficient Ethernet allows the PHY to enter low-power idle states when there is nothing to send and to wake within microseconds when traffic resumes. At the system level, OPEN Alliance TC10-style sleep/wake lets entire links power down when a function is not in use. Less power means less heat in the camera module, which in turn improves image-sensor noise and reliability. Read more in PoDL, EEE and sleep/wake. ## Powering the sensor over the same cable Cameras usually receive power over the same cable that carries their data, avoiding a separate power wire. On coaxial links this is commonly called power over coax; on twisted or parallel pairs, IEEE 802.3bu Power over Data Lines (PoDL) defines the approach. The PHY and the power-coupling network must be designed together so the power filter does not degrade the high-frequency data signal. ## Standardization: IEEE P802.3dm The IEEE 802.3 working group launched the P802.3dm project, titled Asymmetrical Electrical Automotive Ethernet, to add physical layer specifications and management parameters optimized for automotive end-node links such as cameras. The task force adopted a timeline that took its draft through IEEE 802.3 working-group ballot in 2026 — the first recirculation closed successfully in August 2026 — with IEEE SA ballot planned to follow and final approval targeted for 2027. NAV Alliance members are active contributors, consistent with the alliance's long-standing promotion of Asymmetrical Ethernet for the sensor interface. Status noteStandards projects evolve. Check the IEEE 802.3 P802.3dm task force pages for the latest draft and timeline before making product commitments. ## Sizing a camera link The data rate of a camera depends on resolution, frame rate, bits per pixel and compression. A 2.9 MP front camera at 30 fps with 12-bit raw output needs about 1.1 Gb/s; an 8.3 MP camera at 60 fps with 12-bit raw needs roughly 6 Gb/s. Our interactive camera bandwidth calculator lets you explore these trade-offs and see which link speed fits. ## Asymmetrical Ethernet vs. SerDes vs. symmetric Ethernet CriterionProprietary / standard SerDesSymmetric Multi-Gig EthernetAsymmetrical Ethernet Power at sensorLowHigherLow Network integrationBridge requiredNativeNative Switching / replicationNoYesYes Standard security (MACsec)Vendor-specificYesYes EcosystemPer-vendor or per-standardBroad EthernetBroad Ethernet ## Design considerations for camera modules Moving from SerDes to Asymmetrical Ethernet changes how camera modules and ECUs are designed. A few practical points engineers should consider early in a program: - Image-sensor interface. Most image sensors output MIPI CSI-2. The camera therefore needs a bridge function that packetizes CSI-2 data into Ethernet frames — for example using IEEE 1722 video formats — ideally integrated into the PHY or a small companion device. Our article on protocol encapsulation explains the options. - Control path. Sensor registers are traditionally accessed over I2C. With Ethernet, those transactions travel in the low-rate back channel, either encapsulated or translated into a higher-level protocol. Latency for control is rarely critical, but frame triggers and synchronization are. - Thermal budget. Every hundred milliwatts saved at the camera reduces sensor temperature and image noise. Asymmetric PHYs with EEE put the power where it matters. - Diagnostics and functional safety. Link-quality monitoring, frame counters and timestamps let the perception software detect a frozen or corrupted image stream — a key safety mechanism. - Harness reuse. Choosing a medium (shielded pair or coax) and connector system that the vehicle already uses for other high-speed links simplifies the harness. See cables and connectors for Multi-Gig. ## What it means for the vehicle architecture When cameras are Ethernet endpoints, architects gain freedom. A camera can be connected to the nearest zonal controller rather than routed all the way to the central computer, cutting cable length. Its stream can be forwarded to the compute cluster over the backbone, mirrored to a data logger during development and removed again in production by configuration rather than hardware changes. That flexibility is a cornerstone of the software-defined vehicle. ## Frequently asked questions ## Is Asymmetrical Ethernet only for cameras? Cameras are the main use case, but radar, lidar and displays (where the traffic flows the other way) have similar asymmetric patterns. ## Can asymmetrical and symmetric links coexist in one vehicle? Yes. Sensors connect asymmetrically at the edge; zonal controllers and computers connect symmetrically on the backbone. All carry standard Ethernet frames. ## Where can I learn more? Visit our Asymmetrical Ethernet page or contact our member companies through the member directory. Updated November 2026 to reflect the IEEE P802.3dm ballot status. --- # What Is Multi-Gig Automotive Ethernet? A Complete Guide for 2026 URL: https://nav-alliance.org/what-is-multi-gig-automotive-ethernet/ Published: 2025-03-18 Multi-Gig Automotive Ethernet is the family of Ethernet physical layers that carry more than one gigabit per second — today from 2.5 Gb/s up to 100 Gb/s — over the lightweight cabling and in the harsh electrical environment of a car. It is the data backbone that makes advanced driver assistance, automated driving and software-defined vehicles possible, and it is the technology the NAV Alliance was founded to advance. ## Key takeaways - Multi-Gig means Ethernet faster than 1 Gb/s: 2.5, 5 and 10 Gb/s (IEEE 802.3ch) and 25, 50 and 100 Gb/s (IEEE 802.3cy) over a single shielded pair, plus optical variants (IEEE 802.3cz). - It replaces a patchwork of proprietary links with one switched, secure and manageable network. - Cameras, sensor fusion, central compute, storage and zonal backbones are the main drivers. - The hard problems are physical: EMC, temperature, cable weight, power and lifetime — which is why automotive PHYs differ from data-center Ethernet. ## From CAN to the data-center on wheels For decades, vehicle electronics communicated over low-speed buses. CAN, introduced in the 1980s, carries up to 1 Mb/s (and a few Mb/s with CAN FD); LIN serves simple actuators at 20 kb/s; FlexRay reaches 10 Mb/s for chassis control; MOST was used for infotainment. These buses were designed for short control messages between dozens of electronic control units (ECUs), each owning one function. Driver assistance and automated driving changed the scale of the problem. A modern sensor suite can include eight to twelve cameras, five or more radars, one or more lidars and ultrasonic sensors, all feeding powerful AI computers that must fuse their data within milliseconds. Add high-definition maps, in-cabin displays, logging for validation and over-the-air updates, and the vehicle becomes what the NAV Alliance calls a data-center on wheels. A single 8-megapixel camera running at 30 frames per second with 12-bit raw output already generates about 3 Gb/s — more than the total capacity of every CAN bus in the car combined, by three orders of magnitude. Ethernet entered the car first at 100 Mb/s (100BASE-T1, standardized in IEEE 802.3bw in 2015) for infotainment and diagnostics, then at 1 Gb/s (1000BASE-T1, IEEE 802.3bp, 2016). Multi-Gig is the next step: bringing Ethernet to the bandwidth class of the sensors and computers themselves. ## The Multi-Gig standards at a glance StandardPHY namesApprovedMediumNotes IEEE 802.3ch2.5GBASE-T1, 5GBASE-T1, 10GBASE-T12020Single shielded differential pair, up to 15 m, up to 4 inline connectorsFirst Multi-Gig automotive standard; optional EEE and PoDL support IEEE 802.3cy25GBASE-T1, 50GBASE-T1, 100GBASE-T12023Single shielded pair (shorter reach at highest rates)Backbones and central compute; see our 802.3cy deep-dive IEEE 802.3cz2.5GBASE-AU … 50GBASE-AU2023Multimode glass optical fibreImmune to electromagnetic interference IEEE P802.3dmAsymmetrical electrical PHYsIn developmentSingle pair / coaxHigh-speed uplink from cameras and sensors, low-rate back channel All of these are amendments to IEEE 802.3, the Ethernet standard. The automotive physical layers share the same MAC, frame format and higher-layer protocols as office and data-center Ethernet, which is precisely why Ethernet is attractive: the car can reuse a vast ecosystem of switches, software stacks, security protocols and tools. ## Why "single pair" matters Office Ethernet at 10 Gb/s (10GBASE-T) uses four twisted pairs and a bulky RJ45 connector. In a car, every wire adds weight, cost and assembly effort — the wiring harness is already among the three heaviest and most expensive subsystems of a vehicle. Automotive PHYs therefore transmit full-duplex over a single pair of conductors: one shielded twisted or parallel pair, or for some designs a coaxial cable. Achieving 10 Gb/s or more over one pair requires sophisticated signal processing — multi-level modulation, echo cancellation, adaptive equalization and strong forward error correction (FEC) — all implemented in a PHY that must also meet automotive power, temperature and reliability targets. ## What makes automotive Ethernet different from data-center Ethernet? - Electromagnetic compatibility. The link must not disturb the radio receivers in the car (emissions) and must keep working next to electric motors, ignition systems, inverters and phone transmitters (immunity and RF ingress). Read more in our article on Multi-Gig EMC. - Temperature and vibration. Components typically qualify to AEC-Q100 Grade 2 (−40 °C to +105 °C) or better, and connectors must survive years of vibration and humidity. - Lifetime. Vehicles stay on the road for fifteen years or more; the link must keep margin as cables and connectors age. - Fast link-up and low power. Links must come up within milliseconds after wake-up and sleep when not needed — see PoDL, EEE and sleep/wake. - Functional safety and security. Network elements contribute to ISO 26262 safety goals and must be protected against cyber-attacks — see automotive Ethernet security. ## Where Multi-Gig links are used ## Sensor links Cameras, imaging radars and lidars produce the largest data streams in the vehicle. Their traffic is mostly one-way, which is why the NAV Alliance promotes Asymmetrical Ethernet for the sensor interface. Use our camera bandwidth calculator to see which speed a given sensor needs. ## Backbone and zonal links In a zonal architecture, zone controllers collect data from the devices in one region of the car and forward it to central computers. The links between them carry aggregated traffic from many sources and typically need 10 Gb/s today and 25 Gb/s or more for upcoming platforms. ## Compute interconnect and storage Redundant AI computers exchange fused object lists and raw sensor data; data loggers record petabytes of drive data during development; event data recorders and over-the-air update storage all benefit from Multi-Gig connections. ## Displays and infotainment Large cockpit displays and rear-seat entertainment add further video streams, often in parallel with the safety-relevant sensor network. ## Inside a Multi-Gig PHY A Multi-Gig automotive PHY converts frames from the Ethernet MAC into a waveform suitable for the channel. The key building blocks are: - Line coding and modulation — for example PAM4 (four amplitude levels, two bits per symbol) to keep the signal bandwidth manageable. - Forward error correction — Reed-Solomon codes correct bursts of errors caused by noise and RF ingress, so the link can run at very low frame-loss rates. - Echo cancellation — because both directions share one pair, the PHY must subtract its own transmitted signal from what it receives. - Adaptive equalization — digital filters compensate for frequency-dependent cable loss and reflections from connectors. - Diagnostics — signal quality indicators and cable tests that let the vehicle detect a degrading link before it fails. ## Design challenges the industry is solving The NAV Alliance working groups focus precisely on the hard problems: defining channels and EMC limits for 25G and 50G PHYs (TWG1/TWG2), integrating Multi-Gig PHYs into ECUs with the right power supply and PCB design rules (TWG3), encapsulating legacy protocols such as I2C, SPI and camera interfaces into Ethernet (TWG4), and defining management, diagnosis and wake-up for the in-vehicle network (TWG5). See the working groups page for details. Rule of thumbEach doubling of data rate roughly doubles the frequency content of the signal, which increases cable loss, reflections and susceptibility to interference. Higher speed is never "just a faster chip" — the whole channel has to be designed for it. ## Multi-Gig versus SerDes Many cameras and displays today use proprietary point-to-point serializer/deserializer (SerDes) links, and standardized SerDes such as MIPI A-PHY and ASA Motion Link also exist. SerDes links are efficient for one job — moving video from A to B — but they create islands that require bridging chips and cannot be switched, replicated or secured like the rest of the network. Ethernet brings switching, standard security (MACsec), time synchronization (gPTP) and a single diagnostic and management model to every link. Asymmetrical Ethernet aims to combine the efficiency of SerDes with these network advantages. ## What comes next - Broad production deployment of 10GBASE-T1 in zonal backbones and compute interconnects. - First 25G and 50G links for central compute and high-resolution sensor aggregation. - Asymmetrical Ethernet for cameras and sensors as IEEE P802.3dm moves through ballot. - Deterministic, TSN-based networks using the IEEE 802.1DG automotive profile. - More integrated switches with security, routing and diagnostics in a single chip. ## Frequently asked questions ## Is Multi-Gig Automotive Ethernet the same as 10GBASE-T? No. 10GBASE-T uses four pairs and is designed for buildings. 10GBASE-T1 transmits 10 Gb/s over a single automotive pair with very different EMC and temperature requirements. ## How long can a Multi-Gig automotive link be? IEEE 802.3ch targets link segments up to 15 metres with up to four inline connectors — enough to span any passenger car. Higher-rate PHYs may support shorter reaches depending on the cable. ## Does Multi-Gig Ethernet replace CAN? Not entirely. CAN, CAN XL and 10BASE-T1S remain efficient for low-speed control at the network edge. Multi-Gig links form the high-bandwidth backbone and sensor connections above them. ## How can my company get involved? Join the NAV Alliance as a Promoter, Contributor or Adopter — compare membership levels. Updated November 2026. Standard numbers and approval years refer to IEEE 802.3 amendments; consult the official IEEE documents for normative requirements. --- # Marvell Now a Founding Promoter of NAV Alliance URL: https://nav-alliance.org/press-release-4/ Published: 2019-10-09 ## Marvell Now a Founding Promoter of NAV Alliance San Jose, CA – October 9, 2019 – The Networking for Autonomous Vehicles (NAV) Alliance announced that Marvell (NASDAQ: MRVL) is joining the NAV Alliance as a promoter following the completion of its recent acquisition of Aquantia Corp. The NAV Alliance brings together leading automotive manufacturers and technology providers to create an ecosystem for developing the next generation of in-vehicle network infrastructure. Marvell’s advancements in automotive Ethernet add valued expertise to the NAV Alliance working groups. The company joins 14 other industry leaders in delivering the future of autonomous vehicles including founding members Bosch, Continental, NVIDIA, and Volkswagen. “The NAV Alliance is developing the platforms that will create the future of transportation and we believe that Multi-Gig Ethernet is at its core,” said Will Chu, vice president and general manager of the Automotive Business Unit at Marvell Semiconductor, Inc. “We are excited to work alongside other industry leaders to accelerate the development of the innovations that will drive the automotive industry.” “Marvell’s broad automotive Ethernet product portfolio, including its recently announced family of high-port count, ultra-low latency secure automotive switches with multi-gigabit routing throughput capabilities complements the depth and breadth of the technologies offered by other alliance members. I am pleased that our membership represents all the components necessary to support the in-vehicle network in future autonomous vehicles,” said Amir Bar-Niv, President of the NAV Alliance. Marvell is an industry leader in the automotive Ethernet connectivity space and offers several networking components for autonomous driving functions including PHYs, controllers, and switches. The company’s inclusion in the NAV Alliance will enhance the efforts of the NAV Alliance technical working groups. The five NAV Alliance technical working groups are: - Protocol Encapsulation for Ethernet - System Controls and Management - 25G and 50G Automotive Ethernet PHY Specifications - Physical Layer System & Component Integration - EMC Requirements and Limits ## About Marvell Marvell first revolutionized the digital storage industry by moving information at speeds never thought possible. Today, that same breakthrough innovation remains at the heart of the company’s storage, processing, networking, security and connectivity solutions. With leading intellectual property and deep system-level knowledge, Marvell’s semiconductor solutions continue to transform the enterprise, cloud, automotive, industrial, and consumer markets. To learn more, visit www.marvell.com. Marvell and the M logo are registered trademarks of Marvell and/or its affiliates in the US and/or elsewhere. Other names and brands may be claimed as the property of others. ## About NAV Alliance NAV Alliance was created to provide a platform for the automotive industry to develop the next generation of in-vehicle network infrastructure for autonomous vehicles and facilitate wide deployment of networking technologies and products. The Alliance was founded by leading vehicle manufacturers, technology suppliers and networking players in the automotive market, sharing the goal of developing the ecosystem that is required for next-generation Multi-Gig Automotive Ethernet networks in the vehicle. To become a member of the NAV Alliance visit nav-alliance.org. NAV ALLIANCE and NAV are trademarks and certification marks of NAV Alliance, Inc. (or its licensor) in the United States and other countries. Unauthorized use is strictly prohibited. ## Media Contacts MarvellHanna Kang, Senior Manager, Public Relations · 408-222-3780 · hhkang@marvell.comKristin Hehir, Senior Manager, Public Relations · 408-222-8744 · kristinh@marvell.com NAV AllianceErica HooperLee, StrategicLee Inc. · 415-359-7322 · PR@NAV-Alliance.org --- # NAV Alliance Picks Up Speed with New Members Amphenol, HARMAN International, LEONI Bordnetz-Systeme, Rosenberger Hochfrequenztechnik, and Sony URL: https://nav-alliance.org/press-release-3/ Published: 2019-09-23 ## NAV Alliance Picks Up Speed with New Members Amphenol, HARMAN International, LEONI Bordnetz-Systeme, Rosenberger Hochfrequenztechnik, and Sony Growing the Technology Ecosystem to Develop High-Speed Networks for Autonomous Vehicles, NAV Alliance Sponsors IEEE SA Ethernet & IP @Automotive Technology Day San Jose, CA – September 23, 2019 – The Networking for Autonomous Vehicles (NAV) Alliance today announced the expansion of its membership with leading companies Amphenol, HARMAN International, LEONI Bordnetz-Systeme, Rosenberger Hochfrequenztechnik, and Sony. NAV Alliance members represent the pinnacle of technology leadership available for autonomous vehicles within their own respective market segments. These new members join Aquantia, Bosch, Continental, Molex, NVIDIA, Sumitomo Electric, Tektronix and Volkswagen in shaping the future of transportation. “We look forward to working with the NAV Alliance,” said Tim VanGoethem, Vice President, Advanced Mobility Solutions, HARMAN International. “Working collaboratively with industry stakeholders, we are able to leverage our expertise in developing other vehicle networking standards to establish multi-Gb Ethernet best practices and standards that will enable the future of mobility.” “As a global provider of products, solutions and services for intelligent energy and data solutions in the automotive sector, we highly appreciate the platform provided by the NAV Alliance to develop the next-generation of in-vehicle networking infrastructure. We see the pursued work as an essential piece of the puzzle to complete our system approach in terms of connectivity for highly automated driving. We look forward to contributing to the joint development to accelerate the progress of bringing next-generation Multi-Gig Ethernet in OEMs’ vehicles,” said Udo Hornfeck, Chief Technology Officer and Member of the Executive Board, LEONI Bordnetz-Systeme GmbH. “Autonomous driving is an essential challenge of today’s and future automotive industry and its suppliers. Our connector series HFM® and H-MTD® support coaxial and differential connectivity solutions at unprecedented electrical and mechanical properties, offering highest bandwidth, best possible quality and reliability. Rosenberger appreciates the platform provided by the NAV Alliance to develop a standardized in-vehicle networking infrastructure. As a global manufacturer of high-frequency and high-voltage connectivity solutions, we will contribute to the NAV Alliance as a reliable partner with well-experienced know-how and systems knowledge,” said Martin Zebhauser, Executive Vice President Business Area Automotive, Rosenberger. The NAV Alliance membership participates in five technical working groups focused on developing a comprehensive ecosystem for Multi-Gig Ethernet networking in autonomous vehicles. These technical working groups include: - Protocol Encapsulation for Ethernet - System Controls and Management - 25G and 50G Automotive Ethernet PHY Specifications - Physical Layer System & Component Integration - EMC Requirements and Limits “We are very excited about the addition of such a broad range of industry leaders to the Alliance and the exemplary efforts of all our members toward achieving our mission,” said Amir Bar-Niv, President of the NAV Alliance. “Our working groups are making good progress and moving forward the standards and specifications for In-Vehicle Networks and in particular have made excellent progress in development of specifications for 25G Ethernet automotive PHYs. It’s encouraging to see the collaboration between companies, that are each expert in their respective fields, working together to shape the future of automotive in-vehicle-networks.” ## IEEE SA Ethernet & IP @Automotive Technology Day NAV Alliance is also sponsoring the IEEE-SA Ethernet & IP @Automotive Technology Day, September 24th & 25th in Detroit, Michigan, US. Representatives from NAV Alliance member companies will be available to discuss the organization’s momentum, mission, and technical working groups, at Booth A14. Members of the press interested in speaking to a NAV Alliance representative should contact Erica HooperLee. ## About NAV Alliance NAV Alliance was created to provide a platform for the automotive industry to develop the next generation of in-vehicle network infrastructure for autonomous vehicles and facilitate wide deployment of networking technologies and products. The Alliance was founded by leading vehicle manufacturers, technology suppliers and networking players in the automotive market, sharing the goal of developing the ecosystem that is required for next-generation Multi-Gig Automotive Ethernet networks in the vehicle. To become a member of the NAV Alliance visit nav-alliance.org. NAV ALLIANCE and NAV are trademarks and certification marks of NAV Alliance, Inc. (or its licensor) in the United States and other countries. Unauthorized use is strictly prohibited. ## Media Contact Erica HooperLeeStrategicLee Inc.+1 415 359-7322pr@nav-alliance.org --- # Multi-Gig PHY Integration Pre-Compliance Design Review URL: https://nav-alliance.org/product/pre-compliance-design-review/ ## Catch integration issues before the chamber Integrating a 2.5G–10G (or 25G) automotive Ethernet PHY into an ECU or vehicle computer touches power supply design, high-speed PCB layout, MDI circuitry, connectors, EMC and diagnostics. A pre-compliance design review checks your design against established best practices — the same topics addressed by NAV Alliance TWG3, Physical Layer System and Component Integration — before you spend time and money on formal EMC and compliance testing. ## Scope of the review - PHY power supply dimensioning, decoupling and sequencing - PCB stack-up, differential routing, vias and reference planes for signal integrity - MDI circuit: common-mode choke, termination, ESD protection, PoDL coupling network - Connector footprint and channel budget (MDI-to-PHY and link segment) - EMC design measures for emissions and RF ingress - Thermal and power-dissipation considerations - Diagnostics and host-CPU interconnect ## Deliverables - Kick-off call to agree scope and receive design files under NDA - Written report with findings ranked by risk and concrete recommendations - Review call with your engineering team Typical turnaround is two to three weeks after receiving complete design data. The review is engineering guidance and does not constitute certification. See our EMC article and Refund & Cancellation Policy. --- # Multi-Gig Automotive Ethernet Technical Workshop (1 seat) URL: https://nav-alliance.org/product/multi-gig-automotive-ethernet-workshop/ ## One day from fundamentals to design decisions This engineer-to-engineer workshop gives hardware, system and network engineers a practical understanding of Multi-Gig automotive Ethernet — from the physics of single-pair links to architecture-level choices. Sessions are taught by practitioners and combine lectures, worked examples and hands-on lab exercises. ## Agenda - Why Multi-Gig: sensor data rates, zonal architectures and the software-defined vehicle - PHYs: IEEE 802.3ch and 802.3cy — modulation, FEC, echo cancellation, link start-up - Channels: cables, connectors, insertion and return loss, PCB/MDI design - EMC: emissions, RF ingress, test methods and design rules - Asymmetrical Ethernet: camera and sensor links, encapsulation, EEE and PoDL - TSN and security: gPTP, shaping, 802.1CB redundancy, MACsec - Lab: link bring-up, diagnostics (SQI, TDR) and channel measurements ## Included - One seat (in person or live virtual, as scheduled) - Workshop slides and lab notes - Certificate of attendance Prepare with our free articles: What is Multi-Gig Automotive Ethernet? and the glossary. --- # Interoperability Plugfest Registration URL: https://nav-alliance.org/product/interoperability-plugfest-registration/ ## Prove interoperability before the vehicle does A plugfest brings engineers from PHY, switch, ECU, harness and test-equipment vendors together to connect their products to each other under a common, confidential test plan. It is the fastest way to find interoperability issues — link-up behaviour, EEE, sleep/wake, diagnostics, MACsec, timing — before they appear in an OEM integration lab. ## What is included - Registration for one engineering team (up to three engineers) at one NAV Alliance plugfest - Access to the common test plan and test matrix in advance - Shared lab infrastructure: power, reference harnesses and channels, analyzers provided by test-equipment members - Pairing sessions with other participants' devices - Confidential results for your devices; aggregated, anonymized findings shared with participants ## Typical test topics - Link-up time and stability across 2.5G/5G/10GBASE-T1 and emerging 25G devices - Energy-Efficient Ethernet and sleep/wake behaviour - PHY diagnostics (SQI, cable tests) consistency - MACsec and key agreement between vendors - Channel margin with reference harnesses and inline connectors Plugfests are open to NAV Alliance members; Adopter membership or higher is required. Date and venue are confirmed after registration. Cancellation terms are in our Refund & Cancellation Policy. See upcoming and past events. --- # Adopter Membership (Annual) URL: https://nav-alliance.org/product/adopter-membership/ ## Stay ahead with early access Adopters gain access to alliance specifications and collateral before they become publicly available, participate in internal discussions about the alliance and have the opportunity to participate in alliance events such as interoperability demonstrations, plugfests and exhibits. Adopter membership is ideal for companies that implement Multi-Gig automotive Ethernet in their products and want early visibility without committing engineering time to working groups. ## Included benefits - Early access to NAV Alliance specifications and collateral - Participation in internal alliance discussions and member communications - Eligibility to join plugfests, interoperability demonstrations and exhibits - License to other members' Necessary Claims on RAND terms under the IPR Policy - Member listing per alliance guidelines ## How ordering works Place the order to receive an invoice and the member agreement. Membership starts upon signature and payment of USD 5,000 per year. You can upgrade to Contributor or Promoter at any time — see the policy on level changes. --- # Contributor Membership (Annual) URL: https://nav-alliance.org/product/contributor-membership/ ## Shape the specifications from the inside Contributor members have the ability to participate in, as well as chair, working groups and task forces. In addition, contributor companies will have the right in the future to vote on one individual to represent the Contributor community on the board — a decision to be formalized by the board of directors. Contributor members include connector, cable, harness, electronics and test-and-measurement leaders such as Amphenol, HARMAN, LEONI, Molex, Rosenberger, Sony, Sumitomo Electric and Tektronix. ## Included benefits - Participation in technical working groups — 25G/50G PHY & EMC, Physical Layer Integration, Protocol Encapsulation, System Controls & Management - Participation in the Marketing Working Group - Eligibility to chair working groups and task forces - Early access to specifications and collateral - License to other members' Necessary Claims on RAND terms under the IPR Policy - Plugfests, interoperability demonstrations and exhibits - Member listing and logo use per alliance guidelines ## How ordering works - Place the order — you receive an invoice by email. - Sign the member agreement, IPR Policy acknowledgement and Bylaws. - Membership starts upon signature and payment of USD 10,000 per year. Compare all levels on the Membership page. --- # Promoter Membership (Annual) URL: https://nav-alliance.org/product/promoter-membership/ ## Lead the future of in-vehicle networking Promoter members have the ability to participate in all aspects of the NAV Alliance. They vote on proposed specifications, are eligible to sit on the board of directors, and participate in — as well as chair — task forces and working groups. The alliance was founded by Promoter companies Bosch, Continental, Marvell, NVIDIA and Volkswagen Group of America. ## Included benefits - Voting rights on proposed NAV Alliance specifications - Eligibility for a seat on the board of directors - Participation in and chairing of all technical (TWG) and marketing (MWG) working groups and task forces - Early access to specifications and collateral before public availability - License to other members' Necessary Claims on RAND terms under the IPR Policy - Participation in plugfests, interoperability demonstrations and exhibits - Prominent listing among alliance members and in alliance communications - Member-portal accounts for all employees on your company domain ## How ordering works - Place the order — no online payment is taken; you receive an invoice by email. - We send the member agreement form, the IPR Policy and the Bylaws for signature. - Membership starts when the agreement is signed and the invoice (USD 20,000 per year) is paid by bank transfer. Questions? Contact the alliance administration or read the FAQ. See also the Refund & Cancellation Policy.