Battery Control Device Standardizing BMS via Event-Driven Arbitration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current battery management systems lack standardization, leading to dependencies among application modules that cannot operate independently in time or mode, resulting in impaired functionality and data compatibility issues across different automotive software architectures.
Innovation Solution
A battery control device with an application layer unit for independent operation, a module relay layer unit for data relaying, and a basic program layer unit for hardware interaction, which determines execution times and sequences, and manages mode changes without direct connection to application modules.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If application modules are integrated in a traditional BMS architecture, then data sharing and coordination are simplified, but the modules cannot operate independently in time or mode, causing functional impairment when mode changes occur
Solution Approach 1:
The system is divided into distinct layers: application modules layer, event-driven arbitration layer, and execution layer. Application modules are segmented to operate independently by publishing events without direct inter-module dependencies, allowing each module to function autonomously while maintaining system coordination through the event-driven architecture.
Solution Approach 2:
An event-driven arbitration layer acts as an intermediary between application modules and the execution layer. This mediator receives events from modules, manages mode changes centrally, and coordinates execution without creating direct dependencies between modules, enabling independent operation while maintaining reliability during transitions.
2Productivity
If application modules share data directly, then data access is efficient, but data becomes subordinate to each other causing changes in one module to affect others
Solution Approach 1:
Direct data sharing between modules is extracted and replaced with an event-driven communication mechanism. Modules publish events to a central arbitration layer rather than sharing data directly, which maintains efficient data access through standardized event interfaces while preventing data subordination and ensuring data independence among modules.
3Adaptability or versatility
If a standardized software architecture is implemented, then portability across different automotive platforms is improved, but compatibility with both opened and non-opened AUTOSAR architectures simultaneously cannot be achieved
Solution Approach 1:
The event-driven arbitration layer implements a universal interface that can operate with both opened and non-opened AUTOSAR architectures. By defining standardized event publishing and subscription mechanisms that work across different automotive software platforms, the system achieves multi-functionality and portability without requiring separate implementations for different architecture types.
Data Source
AI summary
Provided is a battery control device for the standardization of a battery, and more particularly, to a battery control device for the standardization of a battery, which allows one or more application modules performing functions of a battery management system (BMS) to independently operate with respect to a time, prevents data shared by one or more respective application modules from being subordinate to each other, and further, allows one or more application modules to perform functions thereof regardless of a change of the mode.