IP Library Granted Patent US 12,511,119
Granted Patent B2
US 12,511,119 · App. 18/359,403 · Granted Dec 30, 2025

Data processing method and related device

Inventors: Lei Han (Hangzhou, CN); Xingwang Wu (Hangzhou, CN)
Assignee: Shenzhen Yinwang Intelligent Technologies Co., Ltd.
G06F8/658
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,511,119
App. No.
18/359,403
Granted
Dec 30, 2025
Kind
B2
Abstract

Embodiments of this application disclose a data processing method and a related device. One example method includes: A control device receives a first data transmission request sent by a diagnostic device, where the first data transmission request is used to request the control device to receive an upgrade file, the first data transmission request carries a first memory address corresponding to the upgrade file, and the upgrade file is used to upgrade the control device. The control device obtains a first file path corresponding to the first memory address, receives the upgrade file sent by the diagnostic device, and stores the upgrade file into a file to which the first file path points.

Claims (67)

1 . An upgrade method of an intelligent electronic control unit (ECU) of a vehicle, wherein the method comprises:

receiving, by the intelligent ECU, a first data transmission request sent by a diagnostic device based on a constraint of unified diagnostic services (UDS) protocol, wherein the first data transmission request comprises a request to the intelligent ECU to receive an upgrade file, the first data transmission request carries a first memory address corresponding to the upgrade file, and the upgrade file is used to upgrade the intelligent ECU;

obtaining, by the intelligent ECU, a first file path corresponding to the first memory address;

receiving, by the intelligent ECU, the upgrade file sent by the diagnostic device;

storing the upgrade file into a first file to which the first file path points;

receiving, by the intelligent ECU, a reset request sent by the diagnostic device; and

determining, by the intelligent ECU in response to the received reset request, whether a programming dependency check operation is performed by the intelligent ECU; and

based the determination of whether the programming dependency check operation is performed by the intelligent ECU, performing at least one of the following:

performing an upgrade operation based on the upgrade file, and performing a reset operation; or

triggering a reset operation without performing the upgrade operation.

2 . The method according to claim 1 , wherein the obtaining, by the intelligent ECU, the first file path corresponding to the first memory address comprises:

obtaining, by the intelligent ECU based on a correspondence between a memory address and a file path, the first file path corresponding to the first memory address.

3 . The method according to claim 1 , wherein before the receiving, by the intelligent ECU, the first data transmission request sent by the diagnostic device based on the constraint of UDS protocol, the method further comprises:

receiving, by the intelligent ECU, a second data transmission request sent by the diagnostic device, wherein the second data transmission request comprises a request to the intelligent ECU to receive a flash drive program, and the second data transmission request carries a second memory address corresponding to the flash drive program;

obtaining, by the intelligent ECU, a second file path corresponding to the second memory address;

receiving, by the intelligent ECU, the flash drive program sent by the diagnostic device; and

storing the flash drive program into a second file to which the second file path points;

wherein the second data transmission request is based on the constraint of UDS protocol.

4 . The method according to claim 1 , wherein

the reset request is received when the intelligent ECU is in a programming session, and the upgrade operation based on the upgrade file is performed in response to determining, by the intelligent ECU in response to the received reset request, that the programming dependency check operation is performed by the intelligent ECU.

5 . The method according to claim 4 , wherein after the performing, by the intelligent ECU, the upgrade operation based on the upgrade file, the method further comprises:

when it is determined that the upgrade operation fails, setting a system version number of the intelligent ECU to an invalid value, wherein the invalid value indicates that the upgrade operation fails.

6 . The method according to claim 1 , wherein the upgrade operation is not performed in response to determining that the intelligent ECU does not perform the programming dependency check operation.

7 . An upgrade method of an intelligent electronic control unit (ECU) of a vehicle, wherein the method comprises:

sending, by a diagnostic device based on a constraint of unified diagnostic services (UDS) protocol, a first data transmission request to the intelligent ECU, wherein the first data transmission request comprises a request to the intelligent ECU to receive an upgrade file, the first data transmission request carries a first memory address corresponding to the upgrade file, the first memory address corresponds to a first file path, and the upgrade file is used to upgrade the intelligent ECU; and

receiving, by the diagnostic device, a first positive response sent by the intelligent ECU;

sending the upgrade file to the intelligent ECU based on the first positive response, wherein the upgrade file is stored into a first file to which the first file path points; and

sending, by the diagnostic device, a reset request to the intelligent ECU, wherein the reset request indicates the intelligent ECU to trigger, when a programming dependency check operation is performed, an upgrade operation based on the upgrade file, and a reset operation.

8 . The method according to claim 7 , wherein the method further comprises:

sending, by the diagnostic device, a version number query request to the intelligent ECU; and

receiving a system version number sent by the intelligent ECU, wherein when the system version number is an invalid value, the invalid value indicates that upgrade of the intelligent ECU fails.

9 . The method according to claim 8 , wherein the method further comprises: obtaining a target instruction, and wherein the version number query request is sent in response to the target instruction.

10 . The method according to claim 9 , wherein the target instruction is received through a user interface of the diagnostic device.

11 . The method according to claim 9 , wherein the target instruction indicates whether the upgrade operation is successfully completed.

12 . An intelligent ECU, wherein the intelligent ECU comprises:

at least one processor; and

one or more memories coupled to the at least one processor and storing programming instructions for execution by the at least one processor to cause the intelligent ECU to:

receive a first data transmission request sent by a diagnostic device based on a constraint of unified diagnostic services (UDS) protocol, wherein the first data transmission request comprises a request to the intelligent ECU to receive an upgrade file, the first data transmission request carries a first memory address corresponding to the upgrade file, and the upgrade file is used to upgrade the intelligent ECU;

obtain a first file path corresponding to the first memory address;

receive the upgrade file sent by the diagnostic device;

store the upgrade file into a first file to which the first file path points;

receive a reset request sent by the diagnostic device; and

determine, in response to the received reset request, whether a programming dependency check operation is performed by the intelligent ECU; and

based the determination of whether the programming dependency check operation is performed by the intelligent ECU, perform at least one of the following:

perform an upgrade operation based on the upgrade file, and performing a reset operation; or

trigger a reset operation without performing the upgrade operation.

13 . The intelligent ECU according to claim 12 , wherein the programming instructions, when executed by the at least one processor, cause the intelligent ECU to execute the program to obtain, based on a correspondence between a memory address and a file path, the first file path corresponding to the first memory address.

14 . The intelligent ECU according to claim 12 , wherein the programming instructions, when executed by the at least one processor, cause the intelligent ECU to:

receive a second data transmission request sent by the diagnostic device, wherein the second data transmission request comprises a request to the intelligent ECU to receive a flash drive program, and the second data transmission request carries a second memory address corresponding to the flash drive program;

obtain a second file path corresponding to the second memory address;

receive the flash drive program sent by the diagnostic device; and

store the flash drive program into a second file to which the second file path points;

wherein the second data transmission request is based on the constraint of UDS protocol.

15 . The intelligent ECU according to claim 12 , wherein the reset request is received when the intelligent ECU is in a programming session, and the upgrade operation based on the upgrade file is performed in response to determining that the programming dependency check operation is performed by the intelligent ECU.

16 . The intelligent ECU according to claim 15 , wherein the programming instructions, when executed by the at least one processor, cause the intelligent ECU to: when it is determined that the upgrade operation fails, set a system version number of the intelligent ECU to an invalid value, wherein the invalid value indicates that the upgrade operation fails.

17 . The intelligent ECU according to claim 12 , wherein the upgrade operation is not performed in response to determining that the intelligent ECU does not perform the programming dependency check operation.

18 . A diagnostic device, wherein the diagnostic device comprises:

at least one processor; and

one or more memories coupled to the at least one processor and storing programming instructions for execution by the at least one processor to cause the diagnostic device to:

send a first data transmission request to an intelligent electronic control unit (ECU) based on a constraint of unified diagnostic services (UDS) protocol, wherein the first data transmission request comprises a request to the intelligent ECU to receive an upgrade file, the first data transmission request carries a first memory address corresponding to the upgrade file, the first memory address corresponds to a first file path, and the upgrade file is used to upgrade the intelligent ECU;

receive a first positive response sent by the intelligent ECU;

send the upgrade file to the intelligent ECU based on the first positive response, wherein the upgrade file is stored into a first file to which the first file path points; and

send a reset request to the intelligent ECU, wherein the reset request indicates the intelligent ECU to trigger, when a programming dependency check operation is performed, an upgrade operation based on the upgrade file, and a reset operation.

19 . The diagnostic device according to claim 18 , wherein the programming instructions, when executed by the at least one processor, cause the diagnostic device to:

send a version number query request to the intelligent ECU; and

receive a system version number sent by the intelligent ECU, wherein when the system version number is an invalid value, the invalid value indicates that upgrade of the intelligent ECU fails.

20 . The diagnostic device according to claim 19 , wherein the programming instructions, when executed by the at least one processor, cause the diagnostic device to obtain a target instruction, and wherein the version number query request is sent in response to the target instruction.

Assignments (3)
CHANGE OF NAME Recorded Apr 28, 2026
From: SHENZHEN YINWANG INTELLIGENT TECHNOLOGIES CO., LTD.
To: YINWANG INTELLIGENT TECHNOLOGIES CO., LTD.
Reel/Frame 075492/0796 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 12, 2024
From: HUAWEI TECHNOLOGIES CO., LTD.
To: SHENZHEN YINWANG INTELLIGENT TECHNOLOGIES CO., LTD.
Reel/Frame 069336/0125 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 4, 2024
From: HAN, LEI; WU, XINGWANG
To: HUAWEI TECHNOLOGIES CO., LTD.
Reel/Frame 069127/0917 →