Modern Network

Modern Network


Let’s go back to after 2011. Imagine the following picture as a representation of a vehicle (You already did that before! 😄).



Article content

currently in this period we have more applications need to be fulfilled like:

  • ADAS
  • Infotainment


Network C/S:

  • Topology: Star topology
  • Protocols: Ethernet
  • Data Rates: 10 Mbps: 10 BASE-T 100 Mbps: 100 BASE-TX (Fast Ethernet) 1 Gbps: 1000 BASE-T (Gigabit Ethernet)
  • Data Path: Dynamic
  • Data Length: Dynamic
  • Real-time Constraints: No with High Latency.


1. Topology: Star Topology

In a star topology, all Electronic Control Units (ECUs) connect to a central hub or switch. This design allows each ECU to communicate through the central point, making it easy to manage and troubleshoot. If one connection fails, it does not disrupt the entire network.


2. Protocol and Real-Time Constraints

The main protocol used is Ethernet, which supports fast data transfer. It's suitable for applications like:

  • ADAS: Enhancing vehicle safety.
  • Infotainment: Providing entertainment and connectivity.


However, this network has high latency and does not meet real-time requirements, which can affect critical applications.



3. Data Rate

Ethernet supports several data rates:

  • 10 Mbps (10BASE-T): Basic speed for simple applications.
  • 100 Mbps (100BASE-TX): Fast Ethernet for moderate needs.
  • 1 Gbps (1000BASE-T): Gigabit Ethernet for demanding applications like ADAS and infotainment.


4. Dynamic Data Paths

The data paths in this network are dynamic. But what does that mean?

It means that new paths can be created at runtime, allowing for high flexibility. This flexibility enables us to add new features on the fly!

You might be wondering, how is this possible? We will explore this further in the upcoming sections, where we will discuss Service-Oriented Architecture (SOA) and the SOME/IP protocol.



5. Dynamic Data Length

The data itself can also change at runtime, which means we cannot determine the exact length of the data during the design phase.

For example, consider a camera that detects the number of objects in its field of view and sends a frame containing this count. This calculation occurs in real time, meaning the length of the data is not fixed.



Prev: Legacy Network Next: Looks inside ECU

To view or add a comment, sign in

More articles by Hazem Khaled

  • Embedded Android & Linux Training — Course Schedule

    For more information about our system, Please check the following link: https://www.linkedin.

  • Embedded Linux and Embedded Android Programs

    Hello 👋 In this article I am going to provide the following: New Learning experience provided by Bullet Guru. How can…

    2 Comments
  • Practicing on VSOMEIP

    To practise on VSOMEIP you need the following setup: Host Machine: Linux Machine use "Ubuntu" OS. Virtual Machine on…

  • Next: How SOMEIP and SOMEIP-SD Work

    SOMEIP and SOMEIP-SD developed by BMW Group at 2011, to over come the issue of "static data path" and "static data…

  • Look Inside ECU

    Before going to Service-Oriented Architecture (SOA) and the SOME/IP protocol, that enabled the "Dynamic Path and…

  • Legacy Network Architecture

    Let’s go back before 2011. Imagine the following picture as a representation of a vehicle (yes, consider it a vehicle!…

  • Automotive Network Architecture from Legacy SOA to Modern SOA.

    1. Introduction One of the most exciting changes in the automotive industry is the shift in network design, moving from…

  • Embedded Linux Road Map Part #1

    Hello 👋, In this article and the following ones I would like to share a road map for Embedded Linux Software…

    7 Comments
  • Embedded Linux Diploma Batch 4 🚀🚀🚀🚀🚀🚀

    Batch 4 is coming Next Friday (10/11/2023) god-willing 🚀🚀🚀 Our diploma taken by +70 Engineers with overall 4.3/5 🌟…

    8 Comments

Insights from the community

Others also viewed

Explore topics