Vehicle ECU Power State Configuration via Command Interface

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing power management systems for electronic control units (ECUs) in vehicles are inflexible and inefficient, requiring costly software updates to adapt power states and transitions, which are not optimally configured for different vehicle makes, models, and usage patterns, leading to excessive energy consumption.

Innovation Solution

A command-based framework for configuring power management state machines in ECUs, allowing for the addition, removal, and modification of power states, trigger conditions, and actions, enabling dynamic updates based on vehicle-specific properties and usage models without the need for software flashing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a software-update framework is used to modify power states and transitions, then power management can be updated, but the process requires costly software flashing and is not adaptable to different vehicle configurations

Engineering Contradiction:
Improveadaptability to different vehicle configurationsVSAvoidcost and complexity of software updates
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The patent implements dynamic power management by allowing power states and transitions to be configured and modified at runtime through a command interface, rather than being fixed in pre-flashed software. This enables the system to adapt to different vehicle configurations, usage patterns, and operational requirements without requiring costly software updates or flashing operations.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The system enables modification of power management parameters (power states, transitions, trigger conditions, guard conditions, and actions) through received commands that update configuration data structures in memory. This allows flexible adjustment of power management behavior to match different vehicle makes, models, and usage scenarios without changing the underlying software binary.

Inventive Principle:
Principle #35Parameter changes

2Adaptability or versatility

If pre-defined power management software is used, then system design requirements are met, but the system cannot be optimized for different usage patterns such as taxi fleets versus city use

Engineering Contradiction:
Improveoptimization for different usage patternsVSAvoidproliferation of distinct software profiles
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent creates a universal power management configuration system that can serve multiple vehicle types and usage patterns through a single platform. By using a command interface that updates configuration parameters in memory, the same hardware and software binary can be adapted to optimize power management for taxi fleets, city vehicles, or any other usage pattern without requiring separate software profiles or flashing operations.

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

Solution Approach 2:

The system transitions from static pre-defined power management software to dynamic configurable power management, where the same software instance can be reconfigured at runtime to match different usage patterns. This eliminates the need to maintain multiple distinct software profiles while still providing optimization for various vehicle types and operational requirements.

Inventive Principle:
Principle #15Dynamics

3Productivity

If software flashing is used to update power management, then transitions can be modified, but the process is time-consuming and requires vehicle downtime

Engineering Contradiction:
Improvespeed of power management updatesVSAvoidvehicle downtime for updates
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The system prepares power management configuration updates by receiving and validating commands in advance, storing them in memory without requiring vehicle downtime. The configuration changes are applied immediately upon receipt of valid commands, eliminating the need for time-consuming software flashing operations and vehicle downtime while ensuring proper validation and error handling.

Inventive Principle:
Principle #10Preliminary action

4Use of energy by moving object

If a unified software profile is used across all vehicles, then maintenance is simplified, but energy consumption is not minimized for specific vehicle configurations

Engineering Contradiction:
Improveenergy consumption optimizationVSAvoidconfiguration management complexity
Core Design Contradiction:
Use of energy by moving objectVSDevice complexity

Solution Approach 1:

The patent enables local optimization of power management configuration for each vehicle based on its specific make, model, and usage pattern. By receiving and applying targeted commands that update configuration parameters specific to each vehicle type and operational requirement, the system achieves energy consumption optimization tailored to local conditions while maintaining a unified underlying software platform.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The system optimizes energy consumption by dynamically changing power management parameters (power states, transitions, trigger conditions, guard conditions, and actions) based on specific vehicle configurations and usage patterns. This allows each vehicle to operate with optimized power management settings without requiring separate software profiles, balancing energy efficiency with configuration management simplicity.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS20250021351A1Method for power states in vehicles
Publication Date: 2025.01.16 HARMAN INT IND INC
  • US20250021351A1 patent drawing
  • US20250021351A1 patent drawing
  • US20250021351A1 patent drawing

AI summary

Systems and methods are provided for managing power states of electronic control units (ECUs) of a vehicle. A method may include receiving a command at the vehicle in a language for establishing parts of state machines, and identifying the command as being for the configuration of state machine transitions for power states of one or more ECUs of the vehicle, based on a value of a command-type field of the command. For commands identified as being for the configuration of state machine transitions, the method may further include configuring a transition of a state machine based on a value in a start-state field of the command, a value in an end-state field of the command, and: one or more values in a trigger-condition field of the command, zero or more values in a guard-condition field of the command, and/or zero or more values in an action field of the command.