Controller Network Activation Profiles for Selective Function Execution

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current network architectures for controllers require substantial updating and planning when new controllers are added, leading to increased power consumption due to unnecessary actuation of non-essential controllers.

Innovation Solution

A network architecture with programmable chips equipped with software managers and power managers that dynamically discover and activate only the necessary controllers for a specific function, reducing the need for address sharing and minimizing power consumption by utilizing only dependent functions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If each controller is programmed with the address of other controllers required to perform its function, then the system ensures reliable function execution, but the network requires substantial updating and planning when new controllers are added

Engineering Contradiction:

Improvefunction execution reliabilityVSAvoidnetwork updating complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The software manager on each controller automatically discovers and identifies other controllers in the network without requiring manual address configuration. When a new controller is added, it automatically registers itself with the network, and existing controllers automatically discover the new controller through the software manager's identification process, eliminating the need for manual updating and planning

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The software manager pre-establishes the identification and discovery mechanisms before any controllers need to communicate. By having the software manager ready to identify and register controllers in advance, the system eliminates the need for reactive updating when new controllers are added, as the discovery process is already in place and operational

Inventive Principle:

Principle #10Preliminary action

2Reliability

If controllers are programmed to carry out predetermined routines requiring actuation of predetermined controllers, then the system ensures consistent function performance, but power consumption increases due to actuation of unnecessary controllers

Engineering Contradiction:

Improvefunction performance consistencyVSAvoidcontroller power consumption

Core Design Contradiction:

ReliabilityVSUse of energy by moving object

Solution Approach 1:

The system dynamically determines which controllers need to be activated based on the specific function being executed. The software manager processes the function request and identifies only the necessary controllers required for that particular function, allowing the system to adapt its controller activation pattern rather than following a fixed predetermined routine, thus reducing power consumption while maintaining functional consistency

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The software manager applies different activation patterns to different controllers based on their specific roles and the function being executed. Instead of uniformly activating all controllers in a predetermined routine, the system selectively activates only those controllers that have the specific capabilities needed for the current function, optimizing power consumption while ensuring consistent function performance

Inventive Principle:

Principle #3Local quality

3Reliability

If all controllers are activated to ensure function execution, then the system maintains operational reliability, but power consumption increases due to unnecessary controller actuation

Engineering Contradiction:

Improveoperational reliabilityVSAvoidunnecessary power consumption

Core Design Contradiction:

ReliabilityVSLoss of energy

Solution Approach 1:

The software manager applies partial action by activating only the specific subset of controllers needed for each function rather than all controllers. By processing the function request and identifying the minimum necessary controllers, the system avoids excessive activation of unnecessary controllers, reducing power consumption while maintaining sufficient operational reliability through selective controller engagement

Inventive Principle:

Principle #16Partial or excessive action

Data Source

PatentUS20250206321A1Network having software entities for actuating controllers

Publication Date: 2025.06.26 GM GLOBAL TECHNOLOGY OPERATIONS LLC

AI summary

A network for actuating a plurality of controllers to perform a selected functions includes a plurality of programmable chips communicatively coupled to a corresponding controller. Each programmable chip includes a software manager having a first data processing hardware and a first memory hardware. The first memory hardware stores instructions that causes the first data processing hardware to perform a primary function. An activation profile is stored in the first memory hardware and includes a list of software entities having an identifier identifying a primary function and/or a dependent function. The software manager of at least one of the plurality of controllers is further configured to process the activation profile and perform activation of the software entities by determining each of the plurality of controllers that hosts the software entities having the primary function and/or dependent function needed to perform the desired function.