CN113504921A - Vehicle software updating method and system - Google Patents
Vehicle software updating method and system Download PDFInfo
- Publication number
- CN113504921A CN113504921A CN202110620815.XA CN202110620815A CN113504921A CN 113504921 A CN113504921 A CN 113504921A CN 202110620815 A CN202110620815 A CN 202110620815A CN 113504921 A CN113504921 A CN 113504921A
- Authority
- CN
- China
- Prior art keywords
- vehicle
- ecu
- upgraded
- software
- information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 34
- 238000004519 manufacturing process Methods 0.000 description 6
- 230000008569 process Effects 0.000 description 3
- 238000010586 diagram Methods 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 230000002159 abnormal effect Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 230000003247 decreasing effect Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000009467 reduction Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The invention provides a whole vehicle software updating method and a system, wherein the whole vehicle software updating method comprises the following steps: acquiring ECU dynamic information tables and entire vehicle software version tables of all vehicles; comparing the whole vehicle software version table with the ECU dynamic information table to obtain the information of the vehicle to be upgraded and the information of the ECU to be upgraded in the vehicle to be upgraded; and generating at least one upgrading task according to the ECU information in the vehicle to be upgraded so as to update the vehicle to be upgraded. The invention establishes the information table of each ECU for each vehicle, thereby facilitating the acquisition of vehicle information, and the vehicle software upgrading station is considered from the perspective of the whole vehicle, thereby solving the compatibility problem between the ECU software of the whole vehicle after upgrading.
Description
Technical Field
The invention relates to the technical field of computers, in particular to a method and a system for updating vehicle software.
Background
At present, more and more ECUs are arranged on a vehicle, and software versions are released more and more frequently. The method aims to better and quickly solve the existing software BUG, add new function experience to a user, purchase differentiated functions and increase communication to a customer circle. OTA is a very good function. However, OTA upgrades can cause compatibility issues with each ECU software version.
Because the functions of the vehicle are more and more complex at present, some functions can be realized only by the cooperation of specific software of a plurality of ECUs, and the patent application numbers are as follows: CN 111221549a solves the problem of differential comparison of ECU, and then generates OTA. However, the patent does not stand on the software version of the whole vehicle for management and control, and after one or more ECUs are possibly upgraded, the problem of software compatibility between the ECU and the ECUs without upgrading occurs, so that the vehicle is abnormal.
Therefore, a method and a system for updating vehicle software are needed to solve the above problems.
Disclosure of Invention
The invention solves the technical problem of providing a whole vehicle software updating method and a whole vehicle software updating system, which can avoid the problem of software compatibility between ECUs after upgrading.
The technical problem to be solved by the invention is realized by adopting the following technical scheme:
a whole vehicle software updating method comprises the following steps: acquiring ECU dynamic information tables and entire vehicle software version tables of all vehicles; comparing the whole vehicle software version table with the ECU dynamic information table to obtain the information of the vehicle to be upgraded and the information of the ECU to be upgraded in the vehicle to be upgraded; and generating at least one upgrading task according to the ECU information in the vehicle to be upgraded so as to update the vehicle to be upgraded.
In a preferred embodiment of the present invention, the step of acquiring the ECU dynamic information table and the entire vehicle software version table of each vehicle includes: establishing an ECU dynamic information table, wherein the ECU dynamic information table is used for storing the VIN number of the vehicle, the number of the ECUs and the software and hardware version number of the ECU; and establishing a complete vehicle software version table, wherein the complete vehicle software version table comprises the number of the ECUs of the complete vehicle software version and the software and hardware versions of each ECU.
In a preferred embodiment of the present invention, the step of acquiring the ECU dynamic information table and the entire vehicle software version table of each vehicle includes: when the whole vehicle software version has an upgrading requirement, editing a whole vehicle software version table to modify the whole vehicle ECU software and hardware version; and checking the edited whole vehicle software version table to ensure that the whole vehicle ECU software and hardware version exists in the software library.
In a preferred embodiment of the present invention, the step of acquiring the ECU dynamic information table and the entire vehicle software version table of each vehicle further includes: and the vehicle-mounted terminal uploads each software and hardware version of the ECU through the OTA server.
In a preferred embodiment of the present invention, the step of comparing the entire vehicle software version table with the ECU dynamic information table to obtain the information of the vehicle to be upgraded and the information of the ECU to be upgraded in the vehicle to be upgraded includes: comparing the ECU information of each vehicle in the ECU dynamic information table with a whole vehicle software version table; and acquiring vehicles with the same number and hardware as those of the ECUs in the whole vehicle software version table, and recording the vehicles as the vehicles to be upgraded.
In a preferred embodiment of the present invention, the step of acquiring vehicles with the same number and hardware as those of ECUs in the entire vehicle software version table, and recording the vehicles as the vehicles to be upgraded includes: and recording and storing the vehicle to be upgraded in the modified whole vehicle software version table.
In a preferred embodiment of the present invention, the step of comparing the entire vehicle software version table with the ECU dynamic information table to obtain the vehicle information required to be updated and the ECU information required to be updated in the vehicle includes: and acquiring the ECU in the vehicle to be upgraded, which is different from the ECU software version in the whole vehicle software version table, and recording the ECU as the ECU to be upgraded.
In a preferred embodiment of the present invention, the step of generating at least one upgrade task according to the ECU information in the vehicle to be upgraded to update the vehicle to be upgraded includes: comparing ECU information among vehicles to be upgraded; if the ECUs to be upgraded among different vehicles are the same, merging the ECUs into the same upgrading task; and if the ECUs to be upgraded are different among different vehicles, generating different upgrading tasks.
In a preferred embodiment of the present invention, the step of generating at least one upgrade task according to the ECU information in the vehicle to be upgraded to update the vehicle to be upgraded further includes: and pushing the upgrading task to the OTA server so that the OTA server acquires a corresponding upgrading file from the software library according to the upgrading task to update the vehicle to be upgraded.
A whole vehicle software updating system comprises: the system comprises an information acquisition module, a whole vehicle software version comparison module and a task generation module; the information acquisition module is used for acquiring ECU dynamic information tables and finished vehicle software version tables of all vehicles; the whole vehicle software version comparison module is used for comparing the whole vehicle software version table with the ECU dynamic information table to obtain the information of the vehicle to be upgraded and the information of the ECU to be upgraded in the vehicle to be upgraded; and the task generation module is used for generating at least one upgrading task according to the ECU information in the vehicle to be upgraded so as to update the vehicle to be upgraded.
The technical effect achieved by adopting the technical scheme is as follows: the vehicle software upgrading is not the matter of one or more ECUs but is considered from the perspective of the whole vehicle, the compatibility problem among the ECU software of the whole vehicle is solved, and the information table of each ECU is established for each vehicle, so that the vehicle information is conveniently acquired.
The foregoing description is only an overview of the technical solutions of the present invention, and in order to make the technical means of the present invention more clearly understood, the present invention may be implemented in accordance with the content of the description, and in order to make the above and other objects, features, and advantages of the present invention more clearly understood, the following preferred embodiments are specifically described in detail with reference to the accompanying drawings.
Drawings
Fig. 1 is a flowchart of a vehicle software updating method according to an embodiment of the present invention;
FIG. 2 is a flowchart of a vehicle to be upgraded and a method for ECU acquisition according to an embodiment of the present invention;
FIG. 3 is a table of ECU dynamic information in one embodiment of the present invention;
FIG. 4 is a vehicle software version table according to an embodiment of the present invention;
fig. 5 is a schematic structural diagram of a complete vehicle software update system according to an embodiment of the present invention.
Detailed Description
To further illustrate the technical measures and effects taken by the present invention to achieve the intended objects, embodiments of the present invention will be described in detail below, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to the same or similar elements or elements having the same or similar functions throughout. The embodiments described below are only a part of the embodiments of the present invention, and not all of them. All other embodiments that can be obtained by a person skilled in the art based on the embodiments of the present invention without any inventive step belong to the scope of the embodiments of the present invention. While the present invention has been described in connection with the preferred embodiments, it is to be understood that the invention is not limited to the disclosed embodiments, but is intended to cover various modifications, equivalent arrangements, and specific embodiments thereof.
Referring to fig. 1, fig. 3 and fig. 4, fig. 1 is a flowchart illustrating a vehicle software updating method according to an embodiment of the present invention, fig. 3 is an ECU dynamic information table according to an embodiment of the present invention, and fig. 4 is a vehicle software version table according to an embodiment of the present invention.
As shown in fig. 1, the entire vehicle software updating method of the present invention includes the following steps:
step S11: and acquiring ECU dynamic information tables and whole vehicle software version tables of all vehicles.
In one embodiment, step S11: acquiring ECU dynamic information tables and entire vehicle software version tables of each vehicle, which comprises the following steps: establishing an ECU dynamic information table, wherein the ECU dynamic information table is used for storing the VIN number of the vehicle, the number of the ECUs and the software and hardware version number of the ECU; and establishing a complete vehicle software version table, wherein the complete vehicle software version table comprises the number of the ECUs of the complete vehicle software version and the software and hardware versions of each ECU.
In one embodiment, step S11: the method for acquiring the ECU dynamic information table and the whole vehicle software version table of each vehicle further comprises the following steps: and the vehicle-mounted terminal uploads each software and hardware version of the ECU of the vehicle through the OTA server.
Specifically, the production system: the OTA pays attention to how many ECUs capable of being operated by the OTA are contained in the delivery vehicle and software and hardware version information of each ECU. This information is stored in the production system.
The whole vehicle software updating system takes the project number, VIN number, ECU number and the version number of each ECU software and hardware from the production system. And then putting the acquired information into an ECU dynamic information table established by the electronic control unit. After the ECU of the vehicle is awakened and updated in the later period, the vehicle can upload the latest software and hardware versions of the ECU to a whole vehicle software updating system through the OTA server so as to update an ECU dynamic information table, so that the software and hardware versions of the ECU below each VIN (vehicle) in the ECU dynamic information table are the latest. And the number of ECUs in the ECU dynamic information table is not allowed to be increased or decreased.
Specifically, when the entire vehicle software version table is created, it is necessary to inform the entire vehicle software update system of how many ECUs are needed. If the whole vehicle software version required for upgrading comprises 6 ECUs, 6 ECUs are required in a whole vehicle soft reduction version table; the whole vehicle software version comprises 2 ECUs, and 2 ECUs are needed in the whole vehicle software version table. The number of the ECUs in the finished automobile software version table is consistent with the number of the ECUs in the finished automobile software version with the upgrading requirement.
In one embodiment, step S11: the method for acquiring the ECU dynamic information table and the whole vehicle software version table of each vehicle comprises the following steps: when the whole vehicle software version has an upgrading requirement, editing a whole vehicle software version table to modify the whole vehicle ECU software and hardware version; and checking the edited whole vehicle software version table to ensure that the whole vehicle ECU software and hardware version exists in the software library.
Specifically, when the finished automobile software version has an upgrading requirement, the finished automobile software version table is edited. And filling the name of the whole vehicle version in the whole vehicle software version and modifying the ECU software version needing to be upgraded. And then, storing the modified content, and checking when the modified finished automobile software version table is stored: 1. judging whether the name of the version of the whole vehicle meets the specification requirements, if so, judging whether the name of the version of the whole vehicle contains special characters, and if not, judging whether the information of each ECU contains the special characters; 2. and if the filled software version is correct, and if the corresponding software version is not searched in the software library, carrying out error reporting prompt.
In one embodiment, the complete vehicle software version table further includes a complete vehicle version ID. Specifically, the vehicle version ID is automatically generated after being stored, does not need to be manually changed, and is a unique version ID number after being generated.
Step S12: and comparing the whole vehicle software version table with the ECU dynamic information table to obtain the information of the vehicle to be upgraded and the information of the ECU to be upgraded in the vehicle to be upgraded.
Specifically, the entire vehicle software version table further includes an associated vehicle VIN. The associated vehicle VIN is obtained by comparing each VIN in an ECU dynamic information table according to the generated information of each ECU (the comparison rule is as follows: firstly, the requirements of the number of the ECUs are the same and different, and then the ECUs are directly skipped over, secondly, under the condition that the ECUs are the same, the requirements of each ECU are the same except for different software version numbers, and other requirements are the same.
Step S13: and generating at least one upgrading task according to the ECU information in the vehicle to be upgraded so as to update the vehicle to be upgraded.
In one embodiment, step S13: generating at least one upgrading task according to ECU information in a vehicle to be upgraded so as to update the vehicle to be upgraded, wherein the upgrading task comprises the following steps: comparing ECU information among vehicles to be upgraded; if the ECUs to be upgraded among different vehicles are the same, merging the ECUs into the same upgrading task; and if the ECUs to be upgraded are different among different vehicles, generating different upgrading tasks.
Specifically, after the vehicle to be upgraded is confirmed, an "automatic task issuing" process is started. The automatic release process is carried out according to the whole vehicle software version table, and task calculation is carried out through vehicles in the 'associated vehicle VIN' in the whole vehicle software version table. The specific rule is as follows: 1. and comparing the software information of each ECU in the vehicle to be upgraded, and if the software information is different, recording the software information. If the software versions of the ECU1 and the ECU3 in the vehicle A are different from the software versions of the whole vehicle software version table, the ECU1 and the ECU3 in the vehicle A are recorded as the ECUs to be upgraded. And if the ECU1 in the vehicle B is different from the whole vehicle software version table, recording that the ECU1 in the vehicle B is the ECU to be upgraded. Then, vehicles to be upgraded are compared with each other, if the number of the ECUs to be upgraded is the same and the software versions in the dynamic information tables of the ECUs are the same, the vehicles to be upgraded can be combined into the same upgrade task (namely, the ECUs of 5 ECUs in the vehicle C which need to be upgraded are the ECUs 1, the software versions are the a versions, the ECUs of 5 ECUs in the vehicle D which need to be upgraded are also the ECUs 1, and when the software versions are also the a versions, the vehicles C, D can be upgraded more easily through one upgrade task), and the other tasks are different tasks.
In one embodiment, step S13: generating at least one upgrading task according to ECU information in the vehicle to be upgraded so as to update the vehicle to be upgraded, and the method further comprises the following steps: and pushing the upgrading task to the OTA server so that the OTA server acquires a corresponding upgrading file from the software library according to the upgrading task to update the vehicle to be upgraded.
Specifically, the updating of ECU software of the vehicle to be upgraded is realized through the OAT server, so that the updating efficiency of the whole vehicle software can be improved, and for a non-test sample vehicle, the improvement of the updating efficiency of the whole vehicle software is beneficial to reducing the occurrence of the condition that the vehicle cannot be used due to slow updating of the whole vehicle software.
According to the vehicle software updating method, the ECU dynamic information table and the vehicle software version table are established for each vehicle. And then comparing the whole vehicle software version table with the dynamic information table of the ECU. And obtaining the vehicle to be upgraded and the ECU information to be upgraded in the vehicle to be upgraded. And comparing the vehicles needing to be upgraded, and if the number of the ECUs needing to be upgraded is the same and the software versions in the ECU dynamic information table are the same, merging the ECUs into the same upgrading task, otherwise, merging the ECUs into different upgrading tasks. And finally, enabling the OTA server to update the vehicle according to the upgrading task. The vehicle software upgrading of the method is not the matter of one or more ECUs but is considered from the perspective of the whole vehicle, the compatibility problem among the ECU software of the whole vehicle is solved, and the information table of each ECU is established for each vehicle, so that the vehicle information is conveniently acquired.
Referring to fig. 2 to 4, fig. 2 is a flowchart illustrating a vehicle to be upgraded and an ECU obtaining method according to an embodiment of the present invention, fig. 3 is an ECU dynamic information table according to an embodiment of the present invention, and fig. 4 is a complete vehicle software version table according to an embodiment of the present invention.
As shown in fig. 2, the vehicle to be upgraded and the ECU acquisition method of the present invention include the steps of:
step S21: and comparing the ECU information of each vehicle in the ECU dynamic information table with the whole vehicle software version table.
Step S22: and acquiring vehicles with the same number and hardware as those of the ECUs in the whole vehicle software version table, and recording the vehicles as the vehicles to be upgraded.
Specifically, the whole vehicle software version table is compared with the ECU dynamic information table. Firstly, comparing the number of the ECUs of each vehicle in an ECU dynamic information table with the number in a complete vehicle software version table to obtain vehicle information with the same number, then comparing the information of ECU hardware, models and the like of the vehicles in the vehicle information with the information of the ECU hardware, models and the like in a complete vehicle software version, then obtaining the vehicles with different ECU software versions from the vehicles again, and recording and storing the information of the vehicles.
In one embodiment, step S22: obtaining vehicles with the same number and hardware as those of ECUs in a whole vehicle software version table, and recording the vehicles as vehicles to be upgraded, wherein the method comprises the following steps: and recording and storing the vehicle to be upgraded in the modified whole vehicle software version table.
Step S23: and acquiring the ECU in the vehicle to be upgraded, which is different from the ECU software version in the whole vehicle software version table, and recording the ECU as the ECU to be upgraded.
Specifically, the software information of each ECU in the vehicle to be upgraded is compared, and if not, recorded. If the software versions of the ECU1 and the ECU3 in the vehicle A are different from the software versions of the whole vehicle software version table, the ECU1 and the ECU3 in the vehicle A are recorded as the ECUs to be upgraded. And if the ECU1 in the vehicle B is different from the whole vehicle software version table, recording that the ECU1 in the vehicle B is the ECU to be upgraded. Then, vehicles to be upgraded are compared with each other, if the number of the ECUs to be upgraded is the same and the software versions in the dynamic information tables of the ECUs are the same, the vehicles to be upgraded can be combined into the same upgrade task (namely, the ECUs of 5 ECUs in the vehicle C which need to be upgraded are the ECUs 1, the software versions are the a versions, the ECUs of 5 ECUs in the vehicle D which need to be upgraded are also the ECUs 1, and when the software versions are also the a versions, the vehicles C, D can be upgraded more easily through one upgrade task), and the other tasks are different tasks.
According to the embodiment, the whole vehicle software version table is compared with the dynamic information table of the ECU, the vehicle to be upgraded and the EC to be upgraded in the vehicle to be upgraded are obtained, the upgrade task is automatically generated, and the problem of software compatibility between the ECUs after upgrading is solved.
Referring to fig. 5, fig. 5 is a schematic structural diagram of a complete vehicle software updating system according to an embodiment of the present invention.
As shown in fig. 5, the entire vehicle software updating system of the present invention includes: the system comprises an information acquisition module, a whole vehicle software version comparison module and a task generation module; the information acquisition module is used for acquiring ECU dynamic information tables and finished vehicle software version tables of all vehicles; the whole vehicle software version comparison module is used for comparing the whole vehicle software version table with the ECU dynamic information table to obtain the information of the vehicle to be upgraded and the information of the ECU to be upgraded in the vehicle to be upgraded; and the task generation module is used for generating at least one upgrading task according to the ECU information in the vehicle to be upgraded so as to update the vehicle to be upgraded.
The production system comprises: the OTA pays attention to how many ECUs capable of being operated by the OTA are contained in the delivery vehicle and software and hardware version information of each ECU. This information is stored in the production system.
The whole vehicle software updating system comprises: the project number, VIN number, ECU number and ECU software and hardware version number of each vehicle are taken from the production system and are put into an ECU dynamic information table, and later vehicles upload the latest ECU software and hardware versions to the whole vehicle software updating system through an OTA server to update the dynamic table. Therefore, the ECU software and hardware versions below each VIN (one VIN corresponds to one vehicle) on the surface and the back of the ECU dynamic information are all the latest. The increase or decrease in the number of ECUs is not allowed. And the whole vehicle software updating system creates a whole vehicle software version table according to the number of the ECUs of the whole vehicle software version needing to be upgraded.
The software library stores the latest software version of each ECU in the vehicle. And the OTA service acquires a corresponding upgrading file from the software library according to the upgrading task generated by the whole vehicle software updating system to upgrade and update the vehicle to be upgraded.
Through the above description of the embodiments, it is clear to those skilled in the art that the embodiments of the present invention may be implemented by hardware, or by software plus a necessary general hardware platform. Based on such understanding, the technical solutions of the embodiments of the present invention may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (which may be a CD-ROM, a usb disk, a removable hard disk, etc.), and includes several instructions for enabling a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the methods described in the various implementation scenarios of the embodiments of the present invention.
It should be understood that, although the steps in the flowchart of fig. 1 are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and may be performed in other orders unless explicitly stated herein. Moreover, at least a portion of the steps in fig. 1 may include multiple sub-steps or multiple stages that are not necessarily performed at the same time, but may be performed at different times, in different orders, and may be performed alternately or at least partially with respect to other steps or other steps.
The present invention is not limited to the details of the above embodiments, which are exemplary, and the modules or processes in the drawings are not necessarily essential to the implementation of the embodiments of the present invention, and should not be construed as limiting the present invention.
Claims (10)
1. A whole vehicle software updating method is characterized by comprising the following steps:
acquiring ECU dynamic information tables and entire vehicle software version tables of all vehicles;
comparing the whole vehicle software version table with the ECU dynamic information table to obtain the information of the vehicle to be upgraded and the information of the ECU to be upgraded in the vehicle to be upgraded;
and generating at least one upgrading task according to the ECU information in the vehicle to be upgraded so as to update the vehicle to be upgraded.
2. The vehicle software updating method according to claim 1, wherein the step of obtaining the ECU dynamic information table and the vehicle software version table of each vehicle comprises:
establishing an ECU dynamic information table, wherein the ECU dynamic information table is used for storing the VIN number of the vehicle, the number of ECUs and the ECU software and hardware version number;
and establishing a finished automobile software version table, wherein the finished automobile software version table comprises the number of ECUs of the finished automobile software version and the software and hardware versions of each ECU.
3. The vehicle software updating method according to claim 1, wherein the step of obtaining the ECU dynamic information table and the vehicle software version table of each vehicle comprises:
when the whole vehicle software version has an upgrading requirement, editing the whole vehicle software version table to modify the whole vehicle ECU software and hardware version;
and checking the edited whole vehicle software version table to ensure that the whole vehicle ECU software and hardware version exists in a software library.
4. The vehicle software updating method according to claim 1, wherein the step of obtaining the ECU dynamic information table and the vehicle software version table of each vehicle further comprises:
and the vehicle-mounted terminal uploads each software and hardware version of the ECU through the OTA server.
5. The vehicle software updating method according to claim 1, wherein the step of comparing the vehicle software version table with the ECU dynamic information table to obtain the vehicle information to be upgraded and the ECU information to be upgraded in the vehicle to be upgraded comprises:
comparing the ECU information of each vehicle in the ECU dynamic information table with the whole vehicle software version table;
and acquiring vehicles with the same number and hardware as those of the ECUs in the whole vehicle software version table, and recording the vehicles as vehicles to be upgraded.
6. The vehicle software updating method according to claim 5, wherein the step of obtaining vehicles with the same number and hardware as those of ECUs in the vehicle software version table and recording the vehicles as the vehicles to be upgraded comprises:
and recording and storing the vehicle to be upgraded in the modified whole vehicle software version table.
7. The vehicle software updating method according to claim 1, wherein the step of comparing the vehicle software version table with the ECU dynamic information table to obtain the vehicle information required to be updated and the ECU information required to be updated in the vehicle comprises:
and acquiring the ECU in the vehicle to be upgraded, which is different from the ECU software version in the whole vehicle software version table, and recording the ECU as the ECU to be upgraded.
8. The vehicle software updating method according to claim 1, wherein the step of generating at least one upgrade task according to the ECU information in the vehicle to be upgraded to update the vehicle to be upgraded comprises:
comparing ECU information among the vehicles to be upgraded with each other;
if the ECUs to be upgraded among different vehicles are the same, merging the ECUs into the same upgrading task;
and if the ECUs to be upgraded are different among different vehicles, generating different upgrading tasks.
9. The vehicle software updating method according to claim 1, wherein the step of generating at least one upgrade task according to the ECU information in the vehicle to be upgraded to update the vehicle to be upgraded further comprises:
and pushing the upgrading task to an OTA server so that the OTA server acquires a corresponding upgrading file from a software library according to the upgrading task to update the vehicle to be upgraded.
10. The utility model provides a whole car software update system which characterized in that includes: the system comprises an information acquisition module, a whole vehicle software version comparison module and a task generation module;
the information acquisition module is used for acquiring ECU dynamic information tables and finished vehicle software version tables of all vehicles;
the whole vehicle software version comparison module is used for comparing the whole vehicle software version table with the ECU dynamic information table to obtain the information of the vehicle to be upgraded and the information of the ECU to be upgraded in the vehicle to be upgraded;
and the task generation module is used for generating at least one upgrading task according to the ECU information in the vehicle to be upgraded so as to update the vehicle to be upgraded.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110620815.XA CN113504921A (en) | 2021-06-03 | 2021-06-03 | Vehicle software updating method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110620815.XA CN113504921A (en) | 2021-06-03 | 2021-06-03 | Vehicle software updating method and system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113504921A true CN113504921A (en) | 2021-10-15 |
Family
ID=78008970
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110620815.XA Pending CN113504921A (en) | 2021-06-03 | 2021-06-03 | Vehicle software updating method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113504921A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114428634A (en) * | 2022-01-29 | 2022-05-03 | 重庆长安汽车股份有限公司 | Vehicle-mounted software version control method and system based on software large version |
| US20220308856A1 (en) * | 2021-03-24 | 2022-09-29 | Hyundai Motor Company | Vehicle and method of controlling the same |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2015154636A1 (en) * | 2014-04-11 | 2015-10-15 | 比亚迪股份有限公司 | Method, device and system for updating vehicle body control module of vehicle, and computer readable storage medium |
| CN107291457A (en) * | 2017-06-08 | 2017-10-24 | 重庆长安汽车股份有限公司 | The long-range renewal computing system and method for entire car controller software |
| CN110955444A (en) * | 2019-12-04 | 2020-04-03 | 福尔达车联网（深圳）有限公司 | Vehicle ECU upgrading method, system, terminal and storage medium |
| CN111708555A (en) * | 2020-05-25 | 2020-09-25 | 上海迪璞电子科技股份有限公司 | Data processing device, method and system |
| CN112328294A (en) * | 2020-11-12 | 2021-02-05 | 杭州创想智联科技有限公司 | OTA (over the air) upgrading method and system for vehicle ECU (electronic control Unit) |
| CN112666927A (en) * | 2020-12-28 | 2021-04-16 | 深圳市元征科技股份有限公司 | Upgrading method and upgrading system for vehicle Electronic Control Unit (ECU) |
-
2021
- 2021-06-03 CN CN202110620815.XA patent/CN113504921A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2015154636A1 (en) * | 2014-04-11 | 2015-10-15 | 比亚迪股份有限公司 | Method, device and system for updating vehicle body control module of vehicle, and computer readable storage medium |
| CN107291457A (en) * | 2017-06-08 | 2017-10-24 | 重庆长安汽车股份有限公司 | The long-range renewal computing system and method for entire car controller software |
| CN110955444A (en) * | 2019-12-04 | 2020-04-03 | 福尔达车联网（深圳）有限公司 | Vehicle ECU upgrading method, system, terminal and storage medium |
| CN111708555A (en) * | 2020-05-25 | 2020-09-25 | 上海迪璞电子科技股份有限公司 | Data processing device, method and system |
| CN112328294A (en) * | 2020-11-12 | 2021-02-05 | 杭州创想智联科技有限公司 | OTA (over the air) upgrading method and system for vehicle ECU (electronic control Unit) |
| CN112666927A (en) * | 2020-12-28 | 2021-04-16 | 深圳市元征科技股份有限公司 | Upgrading method and upgrading system for vehicle Electronic Control Unit (ECU) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20220308856A1 (en) * | 2021-03-24 | 2022-09-29 | Hyundai Motor Company | Vehicle and method of controlling the same |
| US11900095B2 (en) * | 2021-03-24 | 2024-02-13 | Hyundai Motor Company | Vehicle and method of controlling the same |
| CN114428634A (en) * | 2022-01-29 | 2022-05-03 | 重庆长安汽车股份有限公司 | Vehicle-mounted software version control method and system based on software large version |
| CN114428634B (en) * | 2022-01-29 | 2024-09-17 | 重庆长安汽车股份有限公司 | Vehicle-mounted software version management and control method and system based on large software version |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3301565B1 (en) | Computer system, method of updating software with computer system, and program therefor | |
| CN113504921A (en) | Vehicle software updating method and system | |
| CN111488165B (en) | Method and system for upgrading vehicle ECU through script | |
| CN101977121A (en) | Configuration file processing method, device and system | |
| CN105468422A (en) | Method and system for optimizing operation system | |
| CN111163340A (en) | IVI system remote LOG reporting method and device based on Internet of vehicles | |
| CN111708555A (en) | Data processing device, method and system | |
| CN112363984A (en) | In-vehicle safety rule file generation method and device | |
| CN118170431A (en) | Cross-operating system service migration method and device and electronic equipment | |
| CN117785237A (en) | Remote upgrading method and device for vehicle-end software, computer equipment and storage medium | |
| US7281165B2 (en) | System and method for performing product tests utilizing a single storage device | |
| CN116257270A (en) | Vehicle, upgrading method and device of vehicle | |
| US8615751B2 (en) | Seeding product information | |
| CN112256978B (en) | Data processing method, device and medium based on data model | |
| CN115982043A (en) | Vehicle interface testing method, device, equipment and storage medium | |
| CN113568842B (en) | Automatic testing method and system for batch tasks | |
| CN111813880B (en) | Homeland space planning project management method, system and storage medium | |
| CN109828752B (en) | Project code automatic generation method, device, computer equipment and storage medium | |
| CN109753296B (en) | Intelligent management method and system for model component library and related equipment | |
| CN112947951A (en) | Software installation method and related equipment | |
| CN114721691A (en) | Method for updating vehicle end preinstalled application | |
| CN115756554B (en) | Version upgrading method and device | |
| CN118820359A (en) | Vehicle data synchronization method, device, equipment and storage medium | |
| CN114979116B (en) | Vehicle-mounted software upgrading method, system, terminal equipment and storage medium | |
| CN102624864A (en) | Device and method for automatically updating services of portable device with serial port |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |