Vehicle Battery Data Binding for Accurate Health Evaluation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing battery management systems for new energy vehicles have limited accuracy in evaluating the health status of power batteries, which is crucial for ensuring driving safety.

Innovation Solution

A battery data management method that involves a vehicle communication apparatus and a cloud server, where a unique identifier is generated based on vehicle identification number and target vehicle type information, or vehicle communication apparatus identification and user identification, to accurately bind and manage battery data.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a battery management system monitors battery health status in real time, then driving safety is improved, but the accuracy of health status evaluation is insufficient

Engineering Contradiction:
Improvedriving safetyVSAvoidbattery health status evaluation accuracy
Core Design Contradiction:
ReliabilityVSMeasurement precision

Solution Approach 1:

The patent introduces a cloud server as an intermediary between the battery management system and the evaluation process. The cloud server receives battery data from the vehicle, performs comprehensive analysis using multiple parameters (temperature, voltage, current, historical data), and generates accurate health status evaluations. This intermediary enables complex processing that enhances measurement precision without burdening the real-time vehicle system.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent transitions from single-dimension real-time monitoring to multi-dimensional evaluation by incorporating historical battery data, environmental conditions, charging patterns, and multiple electrical parameters. This dimensional expansion allows for much more accurate health status assessment through comprehensive data analysis.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Measurement precision

If multiple parameters are collected for battery evaluation, then evaluation accuracy is improved, but data management complexity increases

Engineering Contradiction:
Improvebattery health status evaluation accuracyVSAvoiddata management complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent extracts the complex data management and analysis functions from the vehicle's battery management system and relocates them to a cloud server. The vehicle system only needs to collect and transmit raw data, while the cloud server handles the complex processing, storage, and analysis of multiple parameters, significantly reducing on-vehicle data management complexity.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The cloud server is designed as a universal platform that can handle multiple battery types, different vehicle models, and various evaluation scenarios. This multi-functional approach simplifies data management by providing a standardized processing framework that accommodates diverse battery data without requiring complex vehicle-specific management systems.

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

Data Source

PatentUS20250193281A1Battery data management method for vehicle, system, server and vehicle communication apparatus
Publication Date: 2025.06.12 AUTEL DIGITAL POWER CO LTD
  • US20250193281A1 patent drawing
  • US20250193281A1 patent drawing
  • US20250193281A1 patent drawing

AI summary

A battery data management method for a vehicle is provided by embodiments of the present disclosure. The method includes: transmitting, by a vehicle communication apparatus, a unique identifier acquisition request to a cloud server; determining, by the cloud server, whether the vehicle supports reading the vehicle identification number according to the target vehicle type information; when the vehicle supports, acquiring, by the cloud server, the vehicle identification number via the vehicle communication apparatus, and generating a first unique identifier according to the vehicle identification number and the target vehicle type information; and when the vehicle does not support, generating, by the cloud server, a second unique identifier according to a vehicle communication apparatus identification, a user identification and the target vehicle type information acquired from the vehicle communication apparatus.