Distributed Battery Data Management with Broker Caching and Failover
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing battery data management systems face challenges in efficiently processing and managing high-capacity battery data due to the need for high-performance systems that incur high installation costs and maintenance resources, while also being vulnerable to failures.
Innovation Solution
A battery data management apparatus with distributed functional modules, brokers, and controllers that enable efficient data processing and management by relaying and caching battery data, and dynamically responding to module failures through vertical and horizontal scaling.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If a high-performance single system is used to process battery data, then data processing capability is improved, but installation cost and maintenance resources increase
Solution Approach 1:
The patent divides the battery management system into multiple functional modules (data collection module, data processing module, control module) that can independently process battery data. Each module has specific responsibilities and can operate autonomously, eliminating the need for a single high-performance system while maintaining overall processing capability.
Solution Approach 2:
The patent transitions from a single-system architecture to a distributed multi-module architecture, adding the dimension of spatial distribution. Multiple modules are deployed across different physical or logical locations, transforming the system from centralized to distributed processing.
2Speed
If a single high-performance system is used, then data processing speed is improved, but vulnerability to failures increases
Solution Approach 1:
By segmenting the system into multiple functional modules, the patent ensures that if one module fails, others can continue operating. The data collection module, processing module, and control module are independent, so a failure in one does not necessarily bring down the entire system.
Solution Approach 2:
The patent implements redundant communication paths and alternative processing routes before failures occur. The broker maintains cached data and can relay information through alternative modules if a failure is detected, providing a cushion against system failures.
3Ease of manufacture
If functional modules are distributed, then maintenance cost is reduced, but data communication complexity increases
Solution Approach 1:
The patent introduces a broker as an intermediary component that manages communication between functional modules. The broker receives data from collection modules, processes it through processing modules, and relays commands to control modules, simplifying the communication architecture despite the distributed nature of the system.
Solution Approach 2:
The broker performs multiple functions including data reception, data caching, data relaying, and failure detection. This multi-functional component reduces the need for separate specialized communication channels between each module pair, simplifying the overall communication structure.
4Productivity
If a broker caches and relays battery data, then data processing efficiency is improved, but system complexity increases
Solution Approach 1:
The broker caches battery data before it is needed for processing or control decisions. By pre-storing data in the broker's cache, the system avoids repeated data collection and transmission operations, improving processing efficiency while the caching mechanism is managed through standardized protocols.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A battery data management apparatus according to an embodiment disclosed herein includes a plurality of functional modules configured to perform a defined function based on a preset algorithm, a first broker configured to relay linked operations among the plurality of functional modules based on battery data of at least any one functional module among the plurality of functional modules, and a first controller configured to control operations of the plurality of functional modules and the first broker.