Battery Management Software Architecture for Multi-Project Version Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing embedded software model architectures require multiple model versions for different projects, leading to a heavy workload in maintenance and difficulty in tracing version disorders, as each project has unique strategies and unit divisions.

Innovation Solution

A system controller with a control chip architecture that includes a project determination unit, project units, and a model-level output signal summary unit, allowing different projects to use a single version of the embedded software model architecture by switching between project units and logic execution units based on calibration parameters, thereby reducing maintenance workload.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If different projects use different model versions to accommodate unique strategies and unit divisions, then project-specific requirements are met, but maintenance workload increases and version tracing becomes difficult

Engineering Contradiction:
Improveproject-specific requirementsVSAvoidmaintenance workload
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent creates a universal embedded software model architecture that can serve multiple different projects through configuration rather than requiring separate model versions. The architecture includes a project configuration file that defines project-specific parameters, unit divisions, and logic strategies, allowing a single model version to adapt to different project requirements. This multi-functional design enables the same model architecture to be reused across numerous projects while maintaining project-specific customization through configurable parameters and selectable logic execution units.

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

2Device complexity

If a single version of embedded software model architecture is used across different projects, then maintenance workload is reduced, but project-specific customization capabilities are limited

Engineering Contradiction:
Improvemaintenance workloadVSAvoidproject-specific customization
Core Design Contradiction:
Device complexityVSAdaptability or versatility

Solution Approach 1:

The patent segments the model architecture into independent, configurable components including multiple project units, multiple logic execution units, and a project configuration file. Each segment can be independently configured or selected based on project requirements. The segmentation allows the system to maintain a single version of the overall architecture while enabling project-specific customization through selective activation and configuration of individual segments, thus reducing maintenance workload while preserving adaptability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements dynamic configurability through project configuration files and selectable logic execution units that can be changed without modifying the core model architecture. The system dynamically selects which project unit and logic execution unit to activate based on the specific project, allowing a single model version to adapt to different projects. This dynamic approach maintains low maintenance complexity while providing full project-specific customization capability.

Inventive Principle:
Principle #15Dynamics

3Adaptability or versatility

If multiple model versions are maintained for different projects, then each project can have optimized logic and unit division, but model version disorder leads to difficulty in tracing

Engineering Contradiction:
Improveproject-optimized logicVSAvoidversion tracing
Core Design Contradiction:
Adaptability or versatilityVSLoss of information

Solution Approach 1:

Instead of creating multiple model versions, the patent creates a single model version that is copied and configured for different projects through project configuration files. Each project has its own configuration copy that references the same underlying model architecture, allowing project-optimized logic and unit division without creating separate model versions. This approach maintains version tracing simplicity while preserving project-specific optimizations.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS20250021311A1Embedded software model architecture, battery management system controller, and vehicle
Publication Date: 2025.01.16 BYD CO LTD
  • US20250021311A1 patent drawing
  • US20250021311A1 patent drawing
  • US20250021311A1 patent drawing

AI summary

A system controller for a battery management includes a control chip including a processor and an architecture embedded in the control chip. The architecture includes a target unit, a project determination unit, a project unit, and a model-level output signal summary unit. The processor is configured to run on the architecture to perform the battery management. The project determination unit is configured to output a project enable signal corresponding to the target unit. The project unit includes the target unit, and the project enable signal is configured to trigger startup of the target unit to execute a corresponding logic control strategy. The target unit is configured to receive the project enable signal, and output a unit-level output summary signal based on the project enable signal, and the model-level output signal summary unit is configured to receive the unit-level output summary signal, and to output a model-level output summary signal.