Why


The ADAS/AD challenge
Learn about the challenges of developing safe ADAS/AD vehicle functions


The AD Cycle - How it works
Learn about the AD Cycle works for efficient ADAS/AD development


Benefits of ETAS Deterministic Middleware Solution
See why the worlds top automotive OEMs choose us

Solution concepts


System representation concepts
Fundamental concepts to construct ADAS / AD systems


YAAA Modeling Concepts and Workflow
YAML-based concepts and workflows to model ADAS / AD systems


Deterministic Recompute and Virtual Drives
The 🔑 to development efficiency


Scheduling Mechanisms in ETAS DMS
Achieving optimal compromises between latency and predictability

Basics


Determinism
Gain deeper understanding on determinism in embedded real-time systems


Differences of μC and μP-based embedded systems
Why achieving deterministic behavior μP-based embedded systems is a challenge


Glossary
Understand the terms and abbreviations used in ETAS Deterministic Middleware Solution

Products


ETAS DMS Software Development Kit
Design, develop, build, debug and test ADAS/AD applications

ETAS DMS Middleware & Runtime Libraries
Safety-certified middleware and runtime libraries for series production

For whom


Software Architects
Architecture-as-code. Git-based collaboration. Auto-generated graphics.


Feature Developers
Reduced development complexity. Fast debugging with real vehicle data.

Services


Trainings
Get up to speed on developing with ETAS Deterministic Middleware Solution through our expert trainings


Consultancy
Want to know how to best make use of ETAS Deterministic Middleware Solution for your ADAS/AD platform or project?


Proof of Concept (PoC)
See one of your ADAS/AD vehicle functions developed with ETAS Deterministic Middleware Solution


Custom Project
Have a special need or require an extension to ETAS Deterministic Middleware Solution?

Support


FAQs
Get answers to frequently asked questions about ETAS Deterministic Middleware Solution


Contact
Get in touch with an expert to obtain support

Infos and news about ETAS Deterministic Middleware Solution


Blog
Get the latest news about ETAS Deterministic Middleware Solution


Newsletter
Get the latest news about ETAS Deterministic Middleware Solution delivered to your email inbox


Whitepapers
Read in-depth information, analysis, and insights from our experts

High-speed communication

Communication demands

Traditional automotive software, for example engine control software, has modest communication demands that typically consumes much less than 1MB/s.

In AD/ADAS such as Drive Assistance or Automated Driving software, efficient communication is essential and typically requires high bandwidths in the range from 100MB/s-1GB/s or more.

...

Standard communication approach

The standard communication approach, for example found in the AUTOSAR Classic Runtime Environment (RTE), involves the creation of multiple copies of data for communication purposes.

While functional, this methodology exhibits a fundamental limitation in scalability. As data communication requirements increase, so too does the need for additional data copies, resulting in significant communication overhead. This inherent overhead hinders the efficiency and performance of the system, making it less suitable for applications demanding high bandwidths and real-time responsiveness.

...

The standard communication approach's reliance on data duplication can lead to reduced performance and increased resource consumption as data volumes grow.

Zero-copy communication approach

ETAS DMS communication a true zero-copy, shared memory approach that allows to transfer data from publishers to subscribers without any copies in the middleware. This ensures data transmissions with constant latency, regardless of the size of the payload.

The use of true zero-copy communication with constant overheads in ETAS DMS has a number of interesting and important properties. In particular, communication scales very well and as the message size increases the bandwidth increases as well - this is because the only cost is the fixed overhead and therefore the same whatever the message size!

The ETAS DMS middleware includes a communication management server. This handles two critical tasks for the middleware: firstly as a broker connecting publishers/subscribers, and, secondly, as a shared memory manager controller segment allocation for zero-copy support.

...