CN114625400A - Finished automobile OTA upgrading method and system, storage medium and automobile end upgrading device - Google Patents
Finished automobile OTA upgrading method and system, storage medium and automobile end upgrading device Download PDFInfo
- Publication number
- CN114625400A CN114625400A CN202011475816.1A CN202011475816A CN114625400A CN 114625400 A CN114625400 A CN 114625400A CN 202011475816 A CN202011475816 A CN 202011475816A CN 114625400 A CN114625400 A CN 114625400A
- Authority
- CN
- China
- Prior art keywords
- upgrading
- vehicle
- version number
- software
- independent software
- 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
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
- G06F8/656—Updates while running
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
- H04W8/24—Transfer of terminal data
- H04W8/245—Transfer of terminal data from a network towards a terminal
Abstract
The invention discloses a whole vehicle OTA upgrading method and system, a storage medium and a vehicle end upgrading device, wherein the whole vehicle OTA upgrading method comprises the following steps: acquiring version information of each independent software under the current finished automobile version number; sending the current finished automobile version number and the version information of each independent software to a cloud server so that the cloud server can compare the version information of each independent software under the current finished automobile version number with the version information of each independent software under the target finished automobile version number to generate a software upgrading file; receiving a software upgrading file issued by a cloud server; and upgrading the independent software under the current finished automobile version number in sequence according to the software upgrading file, and updating the current finished automobile version number to the target finished automobile version number after upgrading is completed. Therefore, the whole-vehicle OTA upgrading method can simplify the upgrading mode, reduce the occurrence rate of upgrading faults and improve the upgrading speed and user experience.
Description
Technical Field
The invention relates to the technical field of automobile communication, in particular to a finished automobile OTA upgrading method, a computer-readable storage medium, automobile-end upgrading equipment, a cloud server and a finished automobile OTA upgrading system.
Background
With the progress of society, automobiles become almost necessary transportation means for each family, so that the life of people is more and more convenient. And, as various advanced technologies in the automobile field are developed, more and more intelligent various devices and functions are integrated in the automobile, and these devices and functions are generally controlled by a corresponding ECU (Electronic Control Unit). However, as the automobile intelligence is continuously improved, the requirements of people on the functions and the performance of each system of the automobile are also continuously improved, the software of the vehicle-mounted electronic equipment is increasingly complex, the probability of software problems is correspondingly increased, the potential of the vehicle-mounted electronic equipment can be further developed through upgrading the software, the requirements of people are met to repair the software problems, the running safety of the automobile and the normal use of each function are ensured, and therefore, automobile developers often need to upgrade the software of the generated delivered automobile.
In the related art, software upgrading of an automobile is faced with a complex dependency relationship, and is also faced with a complex rollback processing logic after an upgrading error. The common method in the current OTA (Over the Air) upgrade is that single software is upgraded one by one, and when upgrading dependency is processed, an iterative method is often adopted, that is, when the dependency is found, the dependency is upgraded first, and so on until all dependency relations are upgraded, but the method is difficult to roll back when upgrading faults occur, because different software upgrades are in relatively independent processes, the upgrade of automobile software cannot be completed well, and the user experience is reduced.
Disclosure of Invention
The present invention is directed to solving, at least to some extent, one of the technical problems in the related art. Therefore, an object of the present invention is to provide an Over The Air (OTA) upgrade method for an entire vehicle, which can simplify an upgrade manner, reduce an occurrence rate of upgrade failures, and improve an upgrade speed and user experience.
The second purpose of the invention is to provide another whole vehicle OTA upgrading method.
A third object of the invention is to propose a computer-readable storage medium.
The fourth purpose of the invention is to provide vehicle-end upgrading equipment.
The fifth objective of the present invention is to provide a cloud server.
The sixth purpose of the invention is to provide a whole vehicle OTA upgrading system.
In order to achieve the above object, an embodiment of a first aspect of the present invention provides a finished vehicle OTA upgrading method, including the following steps: acquiring version information of each independent software under the current finished automobile version number; sending the current finished automobile version number and the version information of each independent software to a cloud server so that the cloud server can compare the version information of each independent software under the current finished automobile version number with the version information of each independent software under the target finished automobile version number to generate a software upgrading file; receiving a software upgrading file issued by the cloud server; and upgrading the independent software under the current finished automobile version number in sequence according to the software upgrading file, and updating the current finished automobile version number to the target finished automobile version number after upgrading is completed.
The OTA upgrading method for the whole vehicle comprises the steps of firstly obtaining version information of each independent software under a current whole vehicle version number, then sending the current whole vehicle version number and the version information of each independent software to a cloud server, enabling the cloud server to compare the version information of each independent software under the current whole vehicle version number with the version information of each independent software under a target whole vehicle version number to generate a software upgrading file, then receiving the software upgrading file sent by the cloud server, finally sequentially upgrading each independent software under the current whole vehicle version number according to the software upgrading file, and updating the current whole vehicle version number to serve as the target whole vehicle version number after upgrading is completed. Therefore, the whole-vehicle OTA upgrading method can simplify the upgrading mode, reduce the occurrence rate of upgrading faults and improve the upgrading speed and user experience.
In some examples of the present invention, sequentially upgrading each piece of independent software under the current vehicle version number according to the software upgrade file includes: judging whether each independent software under the current vehicle version number needs to be upgraded or not according to the version number of each independent software in the software upgrading file; if yes, upgrading the current independent software according to the corresponding upgrading text in the software upgrading file; if not, the current stand-alone software is skipped.
In some examples of the invention, the individual pieces of software cooperate with each other in the same overall vehicle version number.
In order to achieve the purpose, the invention provides another OTA (on-board technology over the air) upgrading method for a whole vehicle, which comprises the following steps: receiving a current finished automobile version number uploaded by automobile end upgrading equipment and version information of each independent software under the current finished automobile version number; comparing the version information of each independent software under the current finished automobile version number with the version information of each independent software under the target finished automobile version number, and generating a software upgrading file according to the comparison result and the target finished automobile version number; and issuing the software upgrading file to the vehicle-end upgrading device so that the vehicle-end upgrading device can upgrade the independent software under the current finished vehicle version number in sequence according to the software upgrading file, and updating the current finished vehicle version number to the target finished vehicle version number after upgrading is completed.
The OTA upgrading method for the whole vehicle firstly receives a current whole vehicle version number uploaded by a vehicle-end upgrading device and version information of each independent software under the current whole vehicle version number, then carries out version difference comparison on the version information of each independent software under the current version number and the version information of each independent software under a target whole vehicle version number, generates a software upgrading file according to a comparison result and the target whole vehicle version number, and then sends the software upgrading file to the vehicle-end upgrading device, so that the vehicle-end upgrading device can upgrade each independent software under the current whole vehicle version number in sequence according to the software upgrading file, and updates the current whole vehicle version number as the target whole vehicle version number after upgrading is finished. Therefore, the whole-vehicle OTA upgrading method can simplify the upgrading mode, reduce the occurrence rate of upgrading faults and improve the upgrading speed and user experience.
In some examples of the present invention, generating a software upgrade file according to the comparison result and the target vehicle version number includes: when determining that the version information of any one independent software under the current finished automobile version number is lower than the version information of the corresponding independent software under the target finished automobile version number according to the comparison result, acquiring an upgrade text of the independent software; and generating the software upgrading file according to the obtained upgrading text and the target finished automobile version number.
In some examples of the invention, the individual pieces of software cooperate with each other in the same vehicle version number.
To achieve the above object, a third embodiment of the present invention provides a computer-readable storage medium, on which a whole vehicle OTA upgrade program is stored, where the whole vehicle OTA upgrade program, when executed by a processor, implements the whole vehicle OTA upgrade method according to the first embodiment or the whole vehicle OTA upgrade method according to the second embodiment.
According to the computer-readable storage medium provided by the embodiment of the invention, the processor executes the whole-vehicle OTA upgrading program stored on the storage medium, so that the upgrading mode can be simplified, the occurrence rate of upgrading faults is reduced, and the upgrading speed and the user experience are improved.
In order to achieve the above object, a fourth aspect of the present invention provides a vehicle-end upgrading device, where the vehicle-end upgrading device includes a memory, a processor, and a whole vehicle OTA upgrading program stored in the memory and operable on the processor, and when the processor executes the whole vehicle OTA upgrading program, the whole vehicle OTA upgrading method according to the first aspect of the present invention is implemented.
The vehicle-end upgrading device comprises the memory and the processor, and the processor executes the whole vehicle OTA upgrading program stored on the memory, so that the upgrading mode can be simplified, the occurrence rate of upgrading faults is reduced, and the upgrading speed and the user experience are improved.
In order to achieve the above object, a fifth embodiment of the present invention provides a cloud server, where the cloud server includes a memory, a processor, and a whole-vehicle OTA upgrade program stored in the memory and executable on the processor, and when the processor executes the whole-vehicle OTA upgrade program, the whole-vehicle OTA upgrade method according to the second embodiment of the present invention is implemented.
The cloud server comprises the memory and the processor, and the processor executes the whole OTA upgrading program stored in the memory, so that the upgrading mode can be simplified, the occurrence rate of upgrading faults is reduced, and the upgrading speed and the user experience are improved.
In order to achieve the above object, a sixth aspect of the present invention provides an OTA upgrading system for a whole vehicle, where the OTA upgrading system for a whole vehicle includes a vehicle-end upgrading device and a cloud server, where the vehicle-end upgrading device is configured to obtain version information of each piece of independent software under a current whole vehicle version number, and send the current whole vehicle version number and the version information of each piece of independent software to the cloud server; the cloud server is used for comparing the version information of each independent software under the current finished automobile version number with the version information of each independent software under the target finished automobile version number to generate a software upgrading file, and sending the software upgrading file to the automobile end upgrading device; and the vehicle-end upgrading equipment is also used for sequentially upgrading each independent software under the current finished vehicle version number according to the software upgrading file and updating the current finished vehicle version number to the target finished vehicle version number after upgrading is completed.
The OTA upgrading system of the whole vehicle comprises vehicle-end upgrading equipment and a cloud server, wherein, the vehicle-end upgrading device is used for acquiring the version information of each independent software under the current vehicle version, and sends the current vehicle version number and the version information of each independent software to the cloud server, after the cloud server receives the version information, comparing the version information of each independent software under the current finished automobile version number with the version information of each independent software under the target finished automobile version number, and generates a corresponding software upgrade file, and transmits the software upgrade file to the vehicle-end upgrade device, after the vehicle-end upgrade device receives the software upgrade file, and upgrading the independent software under the current finished automobile version number in sequence, and updating the current finished automobile version number to be the target finished automobile version number after upgrading is completed. Therefore, the whole OTA upgrading system can simplify the upgrading mode, reduce the occurrence rate of upgrading faults and improve the upgrading speed and the user experience.
Additional aspects and advantages of the invention will be set forth in part in the description which follows and, in part, will be obvious from the description, or may be learned by practice of the invention.
Drawings
FIG. 1 is a flowchart of a first OTA vehicle upgrade method according to an embodiment of the present invention;
FIG. 2 is a flowchart of a first OTA full vehicle upgrade method according to another embodiment of the present invention;
FIG. 3 is a flowchart of a second OTA vehicle upgrade method according to an embodiment of the present invention;
FIG. 4 is a flowchart of a second OTA full car upgrade method according to another embodiment of the present invention;
FIG. 5 is a block diagram of a vehicle-end upgrading device according to an embodiment of the present invention;
fig. 6 is a block diagram of a cloud server according to an embodiment of the present invention;
fig. 7 is a block diagram of the whole-vehicle OTA upgrading system according to the embodiment of the present invention.
Detailed Description
Reference will now be made in detail to embodiments of the present invention, 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 function throughout. The embodiments described below with reference to the drawings are illustrative and intended to be illustrative of the invention and are not to be construed as limiting the invention.
The following describes a whole-vehicle OTA upgrading method and system, a storage medium and a vehicle-side upgrading device according to the embodiment of the invention with reference to the attached drawings.
Fig. 1 is a flowchart of a first vehicle OTA upgrading method according to an embodiment of the present invention.
As shown in fig. 1, the whole-vehicle OTA upgrading method includes the following steps:
and S10, obtaining the version information of each independent software under the current vehicle version number.
Specifically, the software version of the ECU or other devices provided on the entire vehicle needs to be compatible with the version of the entire vehicle, thereby ensuring that the vehicle can be accurately and safely controlled. In this embodiment, version information of each independent software under the current finished vehicle version number is first acquired, for example, the finished vehicle includes three independent software, which are A, B and C respectively, assuming that the current finished vehicle version number is 1.2, the version information of the independent software a is 1.1, the version information of the independent software B is 1.0, and the version information of the independent software C is 1.2.
And S20, sending the current finished automobile version number and the version information of each independent software to the cloud server so that the cloud server can compare the version information of each independent software under the current finished automobile version number with the version information of each independent software under the target finished automobile version number to generate a software upgrading file.
Specifically, after the current finished automobile version number and the version information of each independent software are obtained, the obtained current finished automobile version number and the obtained version information of each independent software are sent to the cloud server, and after the cloud server receives the current finished automobile version number and the version information of each independent software, the version information of each independent software and the version information of each independent software under the target finished automobile version number are subjected to version difference comparison, and a software upgrading file is generated. For example, the target vehicle version number in this embodiment is 1.3, and under the target vehicle version number, the version information corresponding to the independent software a is 1.3, and the version information corresponding to the independent software B and the independent software C is 1.2. In this example, after comparing the difference between the version information of each independent software under the target vehicle version number and the current vehicle version number, the independent software a and the independent software B need to be upgraded, while the independent software C does not need to be upgraded, so that the software upgrade files of the independent software a and the independent software B can be generated.
And S30, receiving the software upgrading file sent by the cloud server.
Specifically, in this embodiment, after the cloud server generates the software upgrade files of the independent software a and the independent software B, the software upgrade files may be sent to the vehicle-side upgrade device. Optionally, after receiving the software upgrading file sent by the cloud server, the vehicle-side upgrading device can also verify the received software upgrading file to reduce the probability of the software upgrading file failing in the using process.
And S40, sequentially upgrading each independent software under the current finished automobile version number according to the software upgrading file, and updating the current finished automobile version number to be the target finished automobile version number after upgrading is completed.
Specifically, after receiving the software upgrade file issued by the cloud server, the vehicle-end upgrade device may sequentially upgrade each independent software under the current vehicle version number according to the software upgrade file, and may update the current vehicle version number to the target vehicle version number after the upgrade is completed.
In some embodiments of the present invention, as shown in fig. 2, upgrading each independent software in the current entire vehicle version number in sequence according to the software upgrade file includes: s201, judging whether each independent software under the current vehicle version number needs to be upgraded or not according to the version number of each independent software in the software upgrading file. S202, if yes, upgrading the current independent software according to the corresponding upgrading text in the software upgrading file. S203, if not, skipping the current independent software.
More specifically, after the vehicle-end upgrading device receives the software upgrading file, whether each piece of independent software under the current vehicle version number needs to be upgraded is judged according to the version number of each piece of independent software in the software upgrading file. In a specific embodiment, only the independent software a and the independent software B need to be upgraded in the independent software a, the independent software B and the independent software C under the current vehicle version number, and the independent software a and the independent software B are upgraded in sequence, and the independent software C is skipped. After the upgrade is completed, the current finished automobile version number can be updated to be the target finished automobile version number, that is, the target finished automobile version number 1.3 replaces the current finished automobile version number 1.2, at this moment, the current finished automobile version number is 1.3, and then the version information of the independent software under the current finished automobile version number is respectively: independent software a was 1.3, independent software B was 1.2, and independent software C was 1.2.
In some embodiments, each independent software works cooperatively under the same overall vehicle version number.
It should be noted that after the software upgrade file is generated, an internal test may be performed in the entire vehicle version, and when the test is passed, the entire vehicle version of a small batch may be upgraded, and if the failure feedback has not been received after the entire vehicle version of the small batch is upgraded for a preset time, the entire vehicle version may be upgraded.
In conclusion, the OTA updating method for the whole vehicle can simplify the updating mode, reduce the occurrence rate of updating faults and improve the updating speed and user experience.
Fig. 3 is a flowchart of a second vehicle OTA upgrading method according to an embodiment of the present invention.
Further, as shown in fig. 3, the present invention provides a second vehicle OTA upgrading method, which includes the following steps:
and S100, receiving the current finished automobile version number uploaded by the automobile end upgrading equipment and the version information of each independent software under the current finished automobile version number.
Specifically, the software version of the ECU or other devices provided on the entire vehicle needs to be compatible with the version of the entire vehicle, thereby ensuring that the vehicle can be accurately and safely controlled. In this embodiment, version information of each independent software under the current finished vehicle version number is first acquired, for example, the finished vehicle includes three independent software, which are A, B and C respectively, assuming that the current finished vehicle version number is 1.2, the version information of the independent software a is 1.1, the version information of the independent software B is 1.0, and the version information of the independent software C is 1.2.
S200, comparing the version information of each independent software under the current finished automobile version number with the version information of each independent software under the target finished automobile version number, and generating a software upgrading file according to the comparison result and the target finished automobile version number.
Specifically, after the current finished automobile version number and the version information of each independent software are obtained, the obtained current finished automobile version number and the obtained version information of each independent software are sent to the cloud server, and after the cloud server receives the current finished automobile version number and the version information of each independent software, the version information of each independent software and the version information of each independent software under the target finished automobile version number are compared in a version difference mode, and a software upgrading file is generated. For example, the target vehicle version number in this embodiment is 1.3, and under the target vehicle version number, the version information corresponding to the independent software a is 1.3, and the version information corresponding to the independent software B and the independent software C is 1.2. In this example, after comparing the difference between the version information of each independent software under the target vehicle version number and the current vehicle version number, the independent software a and the independent software B need to be upgraded, while the independent software C does not need to be upgraded, so that the software upgrade files of the independent software a and the independent software B can be generated.
And S300, the software upgrading file is sent to the vehicle-end upgrading device, so that the vehicle-end upgrading device can upgrade the independent software under the current finished vehicle version number according to the software upgrading file in sequence, and the current finished vehicle version number is updated to be the target finished vehicle version number after upgrading is completed.
Specifically, in this embodiment, after the cloud server generates the software upgrade files of the independent software a and the independent software B, the software upgrade files may be sent to the vehicle-side upgrade device. Optionally, after receiving the software upgrading file sent by the cloud server, the vehicle-side upgrading device can also verify the received software upgrading file to reduce the probability of the software upgrading file failing in the using process. After receiving the software upgrading file sent by the cloud server, the vehicle-end upgrading device can sequentially upgrade each independent software under the current finished vehicle version number according to the software upgrading file, and can update the current finished vehicle version number to be the target finished vehicle version number after upgrading is completed.
In some embodiments of the present invention, as shown in fig. 4, generating a software upgrade file according to the comparison result and the target vehicle version number includes:
s401, when the version information of any one independent software under the current finished automobile version number is lower than the version information of the corresponding independent software under the target finished automobile version number according to the comparison result, the upgrade text of the independent software is obtained. And S402, generating a software upgrading file according to the obtained upgrading text and the target complete vehicle version number.
Specifically, after the vehicle-end upgrading device receives the software upgrading file, whether each piece of independent software under the current vehicle version number needs to be upgraded is judged according to the version number of each piece of independent software in the software upgrading file. In a specific embodiment, only if the version information of the independent software a and the independent software B in the independent software a, the independent software B and the independent software C under the current vehicle version number is lower than the version information of the corresponding software under the target vehicle version number, and the software needs to be upgraded, the upgrade texts of the independent software a and the independent software B are obtained, the independent software a and the independent software B are sequentially upgraded, and the independent software C is skipped over. After the upgrade is completed, the current finished automobile version number can be updated to be the target finished automobile version number, that is, the target finished automobile version number 1.3 replaces the current finished automobile version number 1.2, at this moment, the current finished automobile version number is 1.3, and then the version information of the independent software under the current finished automobile version number is respectively: independent software a was 1.3, independent software B was 1.2, and independent software C was 1.2.
In some embodiments of the invention, each independent software performs cooperative work under the same vehicle version number.
It should be noted that after the software upgrade file is generated, an internal test may be performed in the entire vehicle version, and when the test is passed, the entire vehicle version of a small batch may be upgraded, and if the failure feedback has not been received after the entire vehicle version of the small batch is upgraded for a preset time, the entire vehicle version may be upgraded.
In conclusion, the second vehicle OTA upgrading method of the embodiment can simplify the upgrading mode, reduce the occurrence rate of upgrading faults and improve the upgrading speed and user experience.
Further, the present invention provides a computer-readable storage medium, on which a whole vehicle OTA upgrade program is stored, where the whole vehicle OTA upgrade program, when executed by a processor, implements the first whole vehicle OTA upgrade method in the above-mentioned embodiment or the second whole vehicle OTA upgrade method in the above-mentioned embodiment.
The computer-readable storage medium of the embodiment of the invention executes the whole OTA upgrading program stored on the storage medium through the processor, so that the upgrading mode can be simplified, the occurrence rate of upgrading faults can be reduced, and the upgrading speed and the user experience can be improved.
Fig. 5 is a block diagram of a vehicle-end upgrading device according to an embodiment of the present invention.
Further, as shown in fig. 5, the present invention provides a vehicle-end upgrading device 10, where the vehicle-end upgrading device 10 includes a memory 11, a processor 12, and a whole vehicle OTA upgrading program stored on the memory 11 and operable on the processor 12, and when the processor 12 executes the whole vehicle OTA upgrading program, the first whole vehicle OTA upgrading method in the foregoing embodiment is implemented.
The vehicle-end upgrading device comprises the memory and the processor, and the processor executes the whole vehicle OTA upgrading program stored on the memory, so that the upgrading mode can be simplified, the occurrence rate of upgrading faults is reduced, and the upgrading speed and the user experience are improved.
Fig. 6 is a block diagram of a cloud server according to an embodiment of the present invention.
Further, as shown in fig. 6, the present invention provides a cloud server 20, where the cloud server 20 includes a memory 21, a processor 22, and a whole vehicle OTA upgrade program stored in the memory 21 and capable of running on the processor 22, and when the processor 22 executes the whole vehicle OTA upgrade program, the second whole vehicle OTA upgrade method in the above embodiment is implemented.
The cloud server comprises the memory and the processor, and the processor executes the whole OTA upgrading program stored in the memory, so that the upgrading mode can be simplified, the occurrence rate of upgrading faults is reduced, and the upgrading speed and the user experience are improved.
Fig. 7 is a block diagram of the whole-vehicle OTA upgrading system according to the embodiment of the present invention.
Further, as shown in fig. 7, the present invention provides a whole vehicle OTA upgrading system 100, where the whole vehicle OTA upgrading system 100 includes a vehicle-end upgrading device 101 and a cloud server 102, where,
the vehicle-end upgrading device 101 is used for acquiring version information of each independent software under the current finished vehicle version number, and sending the current finished vehicle version number and the version information of each independent software to the cloud server 102; the cloud server 102 is configured to compare version information of each independent software under the current finished automobile version number with version information of each independent software under the target finished automobile version number to generate a software upgrade file, and issue the software upgrade file to the automobile-end upgrade device 101; the vehicle-end upgrading device 101 is further configured to sequentially upgrade each piece of independent software under the current finished vehicle version number according to the software upgrading file, and update the current finished vehicle version number to the target finished vehicle version number after upgrading is completed.
Specifically, the software version of the ECU or other devices provided on the entire vehicle needs to be compatible with the version of the entire vehicle, thereby ensuring that the vehicle can be accurately and safely controlled. In this embodiment, the vehicle-end upgrading device 101 first obtains version information of each independent software under the current vehicle version number, for example, the vehicle includes three independent software, which are A, B and C respectively, and it is assumed that the current vehicle version number is 1.2, the version information of the independent software a is 1.1, the version information of the independent software B is 1.0, and the version information of the independent software C is 1.2. After the vehicle-end upgrading device 101 acquires the current finished vehicle version number and the version information of each independent software, the acquired current finished vehicle version number and the version information of each independent software are sent to the cloud server 102, after the cloud server 102 receives the current finished vehicle version number and the version information of each independent software, the version information of each independent software and the version information of each independent software under the target finished vehicle version number are subjected to version difference comparison, a software upgrading file is generated, and the software upgrading file is issued to the vehicle-end upgrading device 101. For example, the target vehicle version number in this embodiment is 1.3, and under the target vehicle version number, the version information corresponding to the independent software a is 1.3, and the version information corresponding to the independent software B and the independent software C is 1.2. In this example, after comparing the difference between the version information of each independent software under the target vehicle version number and the current vehicle version number, it can be found that the independent software a and the independent software B need to be upgraded, and the independent software C does not need to be upgraded, so that software upgrade files of the independent software a and the independent software B can be generated and sent to the vehicle-end upgrade device 101.
In this embodiment, after the cloud server 102 generates the software upgrade files of the independent software a and the independent software B, the software upgrade files may be sent to the vehicle-side upgrade device 101. Optionally, after receiving the software upgrade file sent by the cloud server 102, the vehicle-side upgrade device 101 may also verify the received software upgrade file, so as to reduce the probability of the software upgrade file failing in the use process. After receiving the software upgrade file sent by the cloud server 102, the vehicle-end upgrade device 101 may sequentially upgrade each piece of independent software under the current vehicle version number according to the software upgrade file, and may update the current vehicle version number to the target vehicle version number after the upgrade is completed.
In some embodiments of the present invention, the upgrading device at the vehicle end sequentially upgrades each independent software under the current vehicle version number according to the software upgrade file, and specifically includes: judging whether each independent software under the current vehicle version number needs to be upgraded or not according to the version number of each independent software in the software upgrading file; if yes, upgrading the current independent software according to the corresponding upgrading text in the software upgrading file; if not, the current stand-alone software is skipped.
In some embodiments of the invention, each independent software performs cooperative work under the same vehicle version number.
It should be noted that after the software upgrade file is generated, an internal test may be performed in the entire vehicle version, and when the test is passed, the entire vehicle version of a small batch may be upgraded, and if the failure feedback has not been received after the entire vehicle version of the small batch is upgraded for a preset time, the entire vehicle version may be upgraded.
In conclusion, the whole-vehicle OTA upgrading system of the embodiment can simplify the upgrading mode, reduce the occurrence rate of upgrading faults and improve the upgrading speed and user experience.
It should be noted that the logic and/or steps represented in the flowcharts or otherwise described herein, such as an ordered listing of executable instructions that can be considered to implement logical functions, can be embodied in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions. For the purposes of this description, a "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of the computer-readable medium would include the following: an electrical connection (electronic device) having one or more wires, a portable computer diskette (magnetic device), a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber device, and a portable compact disc read-only memory (CDROM). Additionally, the computer-readable medium could even be paper or another suitable medium upon which the program is printed, as the program can be electronically captured, via for instance optical scanning of the paper or other medium, then compiled, interpreted or otherwise processed in a suitable manner if necessary, and then stored in a computer memory.
It should be understood that portions of the present invention may be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, the various steps or methods may be implemented in software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, any one or combination of the following technologies, which are well known in the art, may be used: a discrete logic circuit having a logic gate circuit for implementing a logic function on a data signal, an application specific integrated circuit having an appropriate combinational logic gate circuit, a Programmable Gate Array (PGA), a Field Programmable Gate Array (FPGA), or the like.
In the description herein, references to the description of the term "one embodiment," "some embodiments," "an example," "a specific example," or "some examples," etc., mean that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the invention. In this specification, the schematic representations of the terms used above do not necessarily refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.
In the description of the present invention, it is to be understood that the terms "central," "longitudinal," "lateral," "length," "width," "thickness," "upper," "lower," "front," "rear," "left," "right," "vertical," "horizontal," "top," "bottom," "inner," "outer," "clockwise," "counterclockwise," "axial," "radial," "circumferential," and the like are used in the orientations and positional relationships indicated in the drawings for convenience in describing the invention and to simplify the description, and are not intended to indicate or imply that the referenced devices or elements must have a particular orientation, be constructed and operated in a particular orientation, and are therefore not to be considered limiting of the invention.
Furthermore, the terms "first", "second" and "first" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one such feature. In the description of the present invention, "a plurality" means at least two, e.g., two, three, etc., unless specifically limited otherwise.
In the present invention, unless otherwise expressly stated or limited, the terms "mounted," "connected," "secured," and the like are to be construed broadly and can, for example, be fixedly connected, detachably connected, or integrally formed; can be mechanically or electrically connected; they may be directly connected or indirectly connected through intervening media, or they may be connected internally or in any other suitable relationship, unless expressly stated otherwise. The specific meanings of the above terms in the present invention can be understood by those skilled in the art according to specific situations.
In the present invention, unless otherwise expressly stated or limited, the first feature "on" or "under" the second feature may be directly contacting the first and second features or indirectly contacting the first and second features through an intermediate. Also, a first feature "on," "above," and "over" a second feature may be directly on or obliquely above the second feature, or simply mean that the first feature is at a higher level than the second feature. A first feature being "under," "below," and "beneath" a second feature may be directly under or obliquely under the first feature, or may simply mean that the first feature is at a lesser elevation than the second feature.
Although embodiments of the present invention have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting the present invention, and that variations, modifications, substitutions and alterations can be made to the above embodiments by those of ordinary skill in the art within the scope of the present invention.
Claims (10)
1. A whole vehicle OTA upgrading method is characterized by comprising the following steps:
acquiring version information of each independent software under the current finished automobile version number;
sending the current finished automobile version number and the version information of each independent software to a cloud server so that the cloud server can compare the version information of each independent software under the current finished automobile version number with the version information of each independent software under the target finished automobile version number to generate a software upgrading file;
receiving a software upgrading file issued by the cloud server;
and upgrading the independent software under the current finished automobile version number in sequence according to the software upgrading file, and updating the current finished automobile version number to the target finished automobile version number after upgrading is completed.
2. The OTA upgrading method for the whole vehicle according to claim 1, wherein upgrading the independent software under the current whole vehicle version number in sequence according to the software upgrading file comprises:
judging whether each independent software under the current finished automobile version number needs to be upgraded or not according to the version number of each independent software in the software upgrading file;
if yes, upgrading the current independent software according to the corresponding upgrading text in the software upgrading file;
if not, the current stand-alone software is skipped.
3. The finished vehicle OTA upgrade method according to claim 1 or 2, wherein the individual software collaborates under the same finished vehicle version number.
4. A whole vehicle OTA upgrading method is characterized by comprising the following steps:
receiving a current finished automobile version number uploaded by automobile end upgrading equipment and version information of each independent software under the current finished automobile version number;
comparing the version information of each independent software under the current finished automobile version number with the version information of each independent software under the target finished automobile version number, and generating a software upgrading file according to the comparison result and the target finished automobile version number;
and issuing the software upgrading file to the vehicle-end upgrading device so that the vehicle-end upgrading device can upgrade the independent software under the current finished vehicle version number in sequence according to the software upgrading file, and updating the current finished vehicle version number to the target finished vehicle version number after upgrading is completed.
5. The OTA upgrade method for a complete vehicle according to claim 4, wherein generating a software upgrade file according to the comparison result and the target complete vehicle version number comprises:
when determining that the version information of any one independent software under the current finished automobile version number is lower than the version information of the corresponding independent software under the target finished automobile version number according to the comparison result, acquiring an upgrade text of the independent software;
and generating the software upgrading file according to the obtained upgrading text and the target finished automobile version number.
6. The finished vehicle OTA upgrade method according to claim 4 or 5, wherein the individual software collaborates under the same finished vehicle version number.
7. A computer-readable storage medium, on which a full vehicle OTA upgrade program is stored, which when executed by a processor implements the full vehicle OTA upgrade method of any one of claims 1 to 3 or the full vehicle OTA upgrade method of any one of claims 4 to 6.
8. A vehicle-end upgrading device, which is characterized by comprising a memory, a processor and a whole vehicle OTA upgrading program stored on the memory and capable of running on the processor, wherein when the processor executes the whole vehicle OTA upgrading program, the whole vehicle OTA upgrading method according to any one of claims 1-3 is realized.
9. A cloud server, characterized by comprising a memory, a processor and a whole vehicle OTA upgrading program which is stored on the memory and can run on the processor, wherein when the processor executes the whole vehicle OTA upgrading program, the whole vehicle OTA upgrading method according to any one of claims 4-6 is realized.
10. The whole-vehicle OTA upgrading system is characterized by comprising a vehicle-end upgrading device and a cloud server, wherein,
the vehicle-end upgrading device is used for acquiring version information of each independent software under the current vehicle version number and sending the current vehicle version number and the version information of each independent software to the cloud server;
the cloud server is used for comparing the version information of each independent software under the current finished automobile version number with the version information of each independent software under the target finished automobile version number to generate a software upgrading file, and issuing the software upgrading file to the automobile end upgrading device;
and the vehicle-end upgrading equipment is also used for sequentially upgrading each independent software under the current finished vehicle version number according to the software upgrading file and updating the current finished vehicle version number to the target finished vehicle version number after upgrading is finished.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011475816.1A CN114625400A (en) | 2020-12-14 | 2020-12-14 | Finished automobile OTA upgrading method and system, storage medium and automobile end upgrading device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011475816.1A CN114625400A (en) | 2020-12-14 | 2020-12-14 | Finished automobile OTA upgrading method and system, storage medium and automobile end upgrading device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114625400A true CN114625400A (en) | 2022-06-14 |
Family
ID=81896609
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011475816.1A Pending CN114625400A (en) | 2020-12-14 | 2020-12-14 | Finished automobile OTA upgrading method and system, storage medium and automobile end upgrading device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114625400A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115396309A (en) * | 2022-08-23 | 2022-11-25 | 浙江吉智新能源汽车科技有限公司 | Software upgrading method, OTA function purchasing method and information interaction system |
| CN116088913A (en) * | 2023-04-11 | 2023-05-09 | 北京集度科技有限公司 | Integrated device, method and computer program product for whole vehicle upgrade software |
| CN117667178A (en) * | 2024-02-02 | 2024-03-08 | 北京云驰未来科技有限公司 | Whole vehicle software updating method and system based on differential upgrading |
-
2020
- 2020-12-14 CN CN202011475816.1A patent/CN114625400A/en active Pending
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115396309A (en) * | 2022-08-23 | 2022-11-25 | 浙江吉智新能源汽车科技有限公司 | Software upgrading method, OTA function purchasing method and information interaction system |
| CN116088913A (en) * | 2023-04-11 | 2023-05-09 | 北京集度科技有限公司 | Integrated device, method and computer program product for whole vehicle upgrade software |
| CN117667178A (en) * | 2024-02-02 | 2024-03-08 | 北京云驰未来科技有限公司 | Whole vehicle software updating method and system based on differential upgrading |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN114625400A (en) | Finished automobile OTA upgrading method and system, storage medium and automobile end upgrading device | |
| US20170242678A1 (en) | Method and apparatus for vehicle software update installation | |
| US10782955B2 (en) | Pre-shutdown swap verification | |
| US8655541B2 (en) | Vehicle upgrade system and method thereof | |
| US10936306B2 (en) | Vehicle control system and software compatibility checking method | |
| CN110659038B (en) | Vehicle-mounted millimeter wave radar upgrading method and device, computer equipment and storage medium | |
| CN112328294A (en) | OTA (over the air) upgrading method and system for vehicle ECU (electronic control Unit) | |
| CN110244958B (en) | Method and device for updating calibration data of a vehicle | |
| JPWO2012056773A1 (en) | Program rewriting system for vehicles | |
| CN110311960A (en) | A kind of method for upgrading software, device, equipment and storage medium | |
| CN103136134A (en) | Data rewrite system for vehicle, in-vehicle apparatus and rewrite apparatus | |
| CN110275726A (en) | A kind of onboard electronic control unit control program backup upgrade method | |
| US20230066683A1 (en) | Apparatus for operating ota update for vehicle, and method thereof | |
| US20220391192A1 (en) | Ota master, center, system, method, non-transitory storage medium, and vehicle | |
| US20220283799A1 (en) | Center, update management method, and non-transitory storage medium | |
| US11544051B2 (en) | Vehicle update system and method | |
| CN111344641A (en) | Control device for a motor vehicle and method for operating the control device | |
| CN115291907A (en) | Vehicle upgrading method, device and system | |
| KR102275142B1 (en) | Update system and method of controller for vehicle | |
| CN112256285A (en) | OTA (over the air) upgrading method of vehicle, computer-readable storage medium and electronic equipment | |
| CN115129335A (en) | Remote upgrading method and device for electric automobile, T-Box and electric automobile | |
| CN116909609B (en) | Software upgrading method and device of vehicle-mounted intelligent equipment and vehicle-mounted intelligent equipment | |
| US20230051369A1 (en) | Apparatus for operating over-the-air ota update for vehicle, and method thereof | |
| US20220326933A1 (en) | Update management apparatus of vehicle, operating method of the same, and vehicle | |
| US20230052548A1 (en) | Update management apparatus for vehicle and method thereof |
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 |