Battery Management Architecture Using Raw Sensor Data Offloading
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional battery management systems (BMS) for Li-ion batteries are costly and inefficient due to manufacturer-specific programming, leading to increased weight and decreased efficiency, and lack broad compatibility across different platforms.
Innovation Solution
Implementing a secondary BMS architecture that collects raw data from sensors in a non-proprietary format and transmits it to a primary ECU for processing, reducing BMS complexity and enabling broader compatibility across various platforms.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the BMS includes manufacturer-specific programming and processing algorithms, then the battery control functionality is improved, but the device complexity and cost increase
Solution Approach 1:
The system divides functionality into two segments: the BMS hardware collects and transmits raw sensor data, while the vehicle ECU performs all processing algorithms and control decisions. This segmentation removes complex processing requirements from the BMS, reducing its complexity while maintaining full battery control functionality through the ECU's computational capabilities.
Solution Approach 2:
The patent extracts the processing algorithms and control logic from the BMS and relocates them to the vehicle ECU. The BMS is left with only data acquisition and transmission functions, effectively taking out the computational burden and reducing BMS complexity while preserving all necessary battery management capabilities in the ECU.
2Reliability
If the BMS includes all battery control functions with manufacturer-specific programming, then the battery management capability is improved, but the weight and cost of BMS hardware increase
Solution Approach 1:
The patent extracts computational functions from the BMS hardware and relocates them to the vehicle ECU. This extraction eliminates the need for heavy processing components in the BMS, reducing its weight while maintaining full battery management capability through the ECU's computational resources.
Solution Approach 2:
The vehicle ECU serves multiple functions: it manages battery processing algorithms, controls battery operations, and performs other vehicle control tasks. By making the ECU universal and multi-functional, the patent eliminates the need for dedicated heavy processing hardware in the BMS, reducing weight while maintaining comprehensive battery management capability.
3Manufacturing precision
If the BMS is configured with manufacturer-specific programming, then the battery control precision is improved, but the adaptability across different platforms decreases
Solution Approach 1:
The system segments the battery management functionality into platform-independent data collection (BMS) and platform-specific processing (ECU). The BMS collects raw data in a standardized format that can be used across different platforms, while the ECU implements manufacturer-specific algorithms, achieving both precision and adaptability.
Solution Approach 2:
The patent changes the parameter of data representation from processed manufacturer-specific formats to raw standardized sensor data. This parameter change allows the same BMS hardware to interface with different vehicle platforms by simply changing the processing algorithms in the ECU, maintaining precision while improving adaptability across platforms.
Data Source
AI summary
Various systems and methods are provided for a battery management system. In one example, the battery management system includes a battery data receiving unit communicatively coupled to sensors of a battery pack. Further the battery data receiving unit includes instructions stored on non-transitory memory that when executed cause the battery data receiving unit to collect raw data from the sensors of the battery pack in a first format and transmit the collected raw data to an electronic control unit for downstream processing into a second format.