Scalable EE Architecture for Automotive ECU Load Balancing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The increasing complexity of electrical vehicle (EV) systems with numerous electronic controller units (ECUs) across multiple domains poses challenges in scalable, integrated, and flexible automotive configurations, particularly in handling advanced driver-assistance systems (ADAS) operations, due to fragmented subsystems with over-designed and under-utilized resources.

Innovation Solution

A scalable electrical engineering (EE) architecture network that enables intelligent load balancing and distribution across heterogeneous subsystems by directing sensor data to specialized and non-specialized ECUs for processing, using a multi-core computing platform, sensor connectivity switches, and domain connectivity distribution modules, supporting various communication protocols and fault-tolerant configurations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If sensor data is processed by dedicated ADAS ECUs only, then ADAS operation reliability is improved, but device complexity and resource under-utilization increase

Engineering Contradiction:
ImproveADAS operation reliabilityVSAvoidECU subsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent enables non-ADAS ECUs to process ADAS sensor data in addition to their primary functions, creating multi-functional ECUs. This allows the same ECU to handle both infotainment tasks and ADAS processing tasks, reducing the need for dedicated ADAS ECUs and lowering overall system complexity while maintaining reliability through flexible task distribution

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Productivity

If sensor data is routed through multiple domains, then resource utilization is improved, but latency and jitter increase

Engineering Contradiction:
ImproveResource utilization efficiencyVSAvoidData transmission latency
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent introduces a gateway ECU as an intermediary that receives sensor data and intelligently routes it to appropriate ECUs across different domains. The gateway acts as a central coordination point that can direct data to both ADAS and non-ADAS ECUs, enabling load distribution while managing transmission paths to optimize latency through intelligent routing decisions

Inventive Principle:
Principle #24Intermediary (Mediator)

3Speed

If dedicated ADAS ECUs are used, then ADAS processing speed is improved, but resource under-utilization and cost increase

Engineering Contradiction:
ImproveADAS processing speedVSAvoidOverall system resource utilization
Core Design Contradiction:
SpeedVSProductivity

Solution Approach 1:

The patent implements dynamic task allocation where ADAS processing tasks can be dynamically assigned to either dedicated ADAS ECUs or non-ADAS ECUs based on real-time system conditions, workload demands, and resource availability. This dynamic flexibility allows the system to optimize processing speed when needed while utilizing available resources efficiently during normal operations, reducing the need for over-provisioning dedicated hardware

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS10678243B2Systems and methods for scalable electrical engineering (EE) architecture in vehicular environments
Publication Date: 2020.06.09 SERES AUTOMOBILE CO LTD
  • US10678243B2 patent drawing
  • US10678243B2 patent drawing
  • US10678243B2 patent drawing

AI summary

Provided herein are systems and methods of operating electronic controller units (ECUs) across multiple ECU domains in an automotive configuration. A first advanced driver-assistance system (ADAS) environmental sensor can generate a first output. A sensor connectivity switch can direct the first output to a first ECU in one of the non-ADAS domains to generate a second output. Each of the non-ADAS domains can include at least one ECU. A second ECU in a domain for ADAS can use the second output to perform an ADAS operation or autonomous driving in vehicular environments.