Vehicle Controller Network Management for Dynamic Partial Wake-Up
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional methods for configuring vehicle networks require prior configurations and fixed data sizes, limiting the management of various use-cases and necessitating recalls for software updates in mass-produced vehicles.
Innovation Solution
A method and system for dynamically configuring a partial network of vehicle controllers using network management messages that allow controllers to maintain a wake-up state regardless of sleep conditions, enabling flexible subscription and cancellation of partial network clusters without changing the PN specification.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If prior configuration methods are used for partial network, then controllers can be selectively woken up through one-to-one static match, but the system requires prior configurations and cannot dynamically adapt to various use-cases
Solution Approach 1:
The patent implements dynamic configuration by allowing controllers to subscribe to and unsubscribe from partial network clusters without prior static matching. The CCU can dynamically determine which controllers should be woken up based on current needs, replacing the fixed one-to-one static match with a flexible many-to-many dynamic relationship that adapts to various use-cases.
Solution Approach 2:
The patent segments the vehicle network into multiple partial network clusters (PNCs) that can be independently configured and managed. Each PNC can be subscribed to by multiple controllers, allowing fine-grained control over which controllers are woken up for specific tasks, thereby reducing overall system complexity while increasing adaptability.
2Adaptability or versatility
If fixed data size is used for network configuration, then the system structure is simplified, but various combinations of use-cases cannot be managed
Solution Approach 1:
The patent changes the parameter representation from fixed data sizes to variable-length identifiers. Instead of using fixed 4-byte PNI that limits to 32 use-cases, the system uses variable-length PNC identifiers that can represent any number of use-cases, thereby increasing adaptability without proportionally increasing data structure complexity.
Solution Approach 2:
The patent transitions from a flat fixed-size configuration space to a multi-dimensional configuration space where controllers can be dynamically assigned to different PNCs based on multiple criteria (functional groups, priority levels, communication requirements). This dimensional expansion allows management of various use-case combinations that were impossible in fixed-size systems.
3Adaptability or versatility
If static one-to-one matching is used between CCU and controllers, then the communication protocol is simple, but vehicle recalls are required when new use-cases are discovered in mass-produced vehicles
Solution Approach 1:
The patent implements dynamic subscription and unsubscription mechanisms that allow the CCU to modify which controllers are woken up without changing the fundamental network architecture. This dynamic capability enables software updates and use-case additions in mass-produced vehicles without requiring physical recalls, while maintaining system stability through structured message protocols.
Solution Approach 2:
The patent incorporates feedback mechanisms where controllers acknowledge receipt of wake-up messages and where the CCU receives status information about controller states. This feedback loop ensures reliable communication and allows the system to adapt to new use-cases while maintaining stability through verified message delivery and controller responsiveness.
Data Source
AI summary
Systems and methods for controlling vehicle controllers are provided. According to an exemplary embodiment, a method of transceiving performed in a network is provided. The methods comprises transmitting, by a first controller, a first network management (NM) message, wherein the first NM message comprises a request for a subscription to a specific partial network cluster (PNC) to one or more second controllers, performing, by each of the one or more second controllers, an operation setting for the specific PNC in response to the first NM message, broadcasting, by the first controller, a second NM message, wherein the second NM message comprises a request that an identifier of the specific PNC be set to the network, and, maintaining, by the one or more second controllers, a wake-up state, regardless of a preset sleep condition, upon receiving the second NM message.