CN113050960B - OTA upgrading method and device, vehicle-mounted terminal and storage medium - Google Patents
OTA upgrading method and device, vehicle-mounted terminal and storage medium Download PDFInfo
- Publication number
- CN113050960B CN113050960B CN201911376772.4A CN201911376772A CN113050960B CN 113050960 B CN113050960 B CN 113050960B CN 201911376772 A CN201911376772 A CN 201911376772A CN 113050960 B CN113050960 B CN 113050960B
- Authority
- CN
- China
- Prior art keywords
- module
- repaired
- ota
- vehicle
- upgrading
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 62
- 230000008439 repair process Effects 0.000 claims description 49
- 238000004891 communication Methods 0.000 claims description 14
- 238000004590 computer program Methods 0.000 claims description 12
- 238000012545 processing Methods 0.000 claims description 11
- 230000008569 process Effects 0.000 abstract description 18
- 238000010586 diagram Methods 0.000 description 9
- 230000006870 function Effects 0.000 description 9
- 238000005516 engineering process Methods 0.000 description 3
- 239000004973 liquid crystal related substance Substances 0.000 description 3
- 230000009471 action Effects 0.000 description 2
- 238000001514 detection method Methods 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 239000002699 waste material Substances 0.000 description 1
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
-
- 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
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 application discloses an OTA upgrading method, an OTA upgrading device, a vehicle-mounted terminal and a storage medium, wherein the OTA upgrading method comprises the following steps: after the previous OTA upgrade fails, determining a module to be repaired, wherein the module to be repaired is the module to be upgraded after the upgrade fails; initializing the OTA environment again; and after the OTA environment is successfully initialized, repairing the module to be repaired. According to the method, after the previous OTA upgrading of the vehicle fails, the module to be repaired is determined, and the initialization environment is carried out, so that the module to be repaired is repaired under the condition that the influence of the previous upgrading on the vehicle is reduced, excessive manpower is not needed in the process, the module to be repaired can be directly repaired at the vehicle-mounted terminal, the operation is convenient and quick, the upgrading time can be saved, the OTA upgrading success rate is further improved, and the danger of the vehicle in the using process is avoided.
Description
Technical Field
The present invention relates generally to the field of network technologies, and in particular, to an OTA upgrading method, an OTA upgrading device, a vehicle-mounted terminal, and a storage medium.
Background
With the rapid development of communication Technology, more and more devices are in use, and are continuously updated by using the space downloading Technology (OTA for short), such as a vehicle control system. The OTA upgrade is to upgrade the system firmware by automatically downloading an OTA upgrade package through a network, or upgrade the OTA by downloading the OTA upgrade package to the SD card, and repair the system bug and optimize the system function through upgrade.
At present, the existing vehicle control system comprises an OTA management system and an OTA front end of a vehicle to be upgraded, and the OTA management system completes OTA upgrading operation by configuring a task list and an upgrading software package and sending the upgrading software package to the OTA front end when receiving a request of the OTA front end.
However, in the upgrade scheme, when the OTA upgrade fails, the program version of the control system is too low or no program is needed, and a specific mobile device is required to be used for updating the system on site manually, which is a waste of manpower and time, so that the vehicle cannot be used normally and is safe to run.
Disclosure of Invention
In view of the above-mentioned drawbacks or shortcomings in the prior art, it is desirable to provide an OTA upgrading method, which can determine a module to be repaired and repair the module to be repaired after an OTA upgrade failure of a vehicle, and the method is convenient and fast, does not need excessive human intervention, can improve the success rate of the OTA upgrade, and reduces the possibility of danger of the vehicle in the use process.
In a first aspect, the present application provides an OTA upgrade method, which includes:
After the previous OTA upgrade fails, determining a module to be repaired, wherein the module to be repaired is the module to be upgraded after the upgrade fails;
initializing the OTA environment again;
And after the OTA environment is successfully initialized, repairing the module to be repaired.
In one embodiment, determining a module to repair includes:
acquiring a current version number and a target version number of the module to be upgraded;
judging whether the current version number is lower than the target version number;
And if the current version number of the module to be upgraded is lower than the target version number, determining that the module to be upgraded is a module to be repaired.
In one embodiment, the previous OTA upgrade includes:
Detecting vehicle state information;
When the vehicle state information meets an OTA condition, initializing an OTA environment, wherein the OTA condition comprises: the vehicle is in a stationary state and has sufficient electric quantity;
and upgrading the module to be upgraded, and recording the information of the module to be repaired and the upgrade version information.
In one embodiment, the repairing the module to be repaired includes:
When a plurality of modules to be repaired are provided, obtaining information of the modules to be repaired and corresponding upgrade version information of each module to be repaired;
and repairing each module to be repaired to a target version according to the information of each module to be repaired and the corresponding upgrading version information.
In one embodiment, the module to be repaired information includes: the method comprises the steps of identifying a module to be repaired, a current version number corresponding to the module to be repaired and a current version software package corresponding to the module to be repaired, wherein the upgrading version information comprises: a target version number corresponding to the module identifier to be repaired and a target version upgrade package corresponding to the module identifier to be repaired; according to the information of each module to be repaired and the corresponding upgrade version information, repairing each module to be repaired to a target version comprises the following steps:
replacing the current version software package corresponding to the module identifier to be repaired with the target version upgrade package corresponding to the module identifier to be repaired;
And updating the current version number corresponding to the to-be-repaired identification as the target version number corresponding to the to-be-repaired module identification.
In one embodiment, after performing the repair process on the module to be repaired, the method further includes:
judging whether the module to be repaired is repaired to a target version or not;
If all the modules to be repaired are repaired to the target version, exiting the OTA environment;
If the to-be-repaired modules with the repair failure exist in all the to-be-repaired modules, the OTA environment is continuously initialized, and the to-be-repaired modules with the repair failure are subjected to repair processing until all the to-be-repaired modules with the repair failure are repaired to the target version.
In a second aspect, the present application provides an OTA upgrading device, including:
the determining module is used for determining a module to be repaired after the previous OTA upgrading fails, wherein the module to be repaired is the module to be upgraded after the upgrading fails;
the first initialization module is used for initializing the OTA environment again;
And the repair module is used for repairing the module to be repaired after the OTA environment is initialized successfully.
In a third aspect, an embodiment of the present application provides a vehicle-mounted terminal, including a memory and a processor, where the memory stores a computer program, and the processor implements the above OTA upgrading method when executing the computer program.
In a fourth aspect, an embodiment of the present application provides a computer readable storage medium having a computer program stored thereon, where the computer program when executed by a processor implements the above-mentioned OTA upgrading method.
In summary, the application provides an OTA upgrading method, an OTA upgrading device, a vehicle-mounted terminal and a storage medium, wherein after the previous OTA upgrading fails, a module to be repaired is determined, the module to be repaired is the module to be upgraded after the upgrading fails, an OTA environment is initialized again, and when the OTA environment is initialized successfully, repairing treatment is carried out on the module to be repaired. According to the method, after the previous OTA upgrade of the vehicle fails, the module to be repaired is determined, and the initialization environment is carried out again, so that the influence of the previous upgrade on the vehicle is reduced, the module to be repaired is repaired under the condition that the influence of the previous upgrade on the vehicle is reduced, excessive manpower is not needed, the module to be repaired can be repaired directly at the vehicle-mounted terminal, the operation is convenient and quick, the upgrading time can be saved, the OTA upgrading success rate is further improved, and the danger of the vehicle in the use process is avoided.
Drawings
Other features, objects and advantages of the present application will become more apparent upon reading of the detailed description of non-limiting embodiments, made with reference to the accompanying drawings in which:
Fig. 1 is a schematic flow chart of an OTA upgrading method according to an embodiment of the present application;
fig. 2 is a schematic flow chart of an OTA upgrading method according to an embodiment of the present application;
Fig. 3 is a schematic structural diagram of an OTA upgrading device according to an embodiment of the present application;
fig. 4 is a schematic structural diagram of a computer system according to an embodiment of the present application.
Detailed Description
The application is described in further detail below with reference to the drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the application and are not limiting of the application. It should be noted that, for convenience of description, only the portions related to the application are shown in the drawings.
It should be noted that, without conflict, the embodiments of the present application and features of the embodiments may be combined with each other. The application will be described in detail below with reference to the drawings in connection with embodiments.
It can be appreciated that with the development of the intelligence of the vehicle-mounted device, for various vehicle-mounted control systems such as vehicle-mounted applications, OTA upgrades are generally required to be performed at random, and currently, common OTA upgrades are mainly aimed at upgrading multimedia functions such as navigation, parking assistance, information entertainment, comfort configuration and the like, so that system holes are repaired, system functions are optimized, and user experience is greatly optimized.
As mentioned in the background art, currently, the existing vehicle control system includes an OTA management system and an OTA front end of a vehicle to be upgraded, and the OTA management system sends a software upgrade packet to the OTA front end, so that the OTA front end completes OTA upgrade according to the software upgrade packet. However, the scheme only involves an upgrade operation process, and does not consider a processing process after the upgrade failure, if the upgrade failure occurs, the control system program version is too low or no program is caused, after-sales personnel are required to bring the downloaded software package to the vehicle site, and the system is updated by using specific equipment, so that the operation process is labor-consuming and time-consuming.
Based on the defects, the application provides an OTA upgrading method, which comprises the steps of determining a module to be repaired after the previous OTA upgrading fails, initializing an OTA environment, and repairing the module to be repaired after the OTA environment is successfully initialized. Compared with the prior art, the method does not need excessive manpower, can directly repair the module to be repaired at the vehicle-mounted terminal, is simple in repair operation, convenient and quick, can save upgrading time, further improves the OTA upgrading success rate, and avoids danger of the vehicle in the use process.
Fig. 1 is a flow chart of an OTA upgrading method according to an embodiment of the present invention. As shown in fig. 1, the method is applied to a vehicle-mounted terminal, and includes:
step S101, after the previous OTA upgrade fails, determining a module to be repaired, wherein the module to be repaired is the module to be upgraded after the upgrade fails.
It can be understood that the vehicle-mounted terminal is front-end equipment of the vehicle monitoring and management system, and may include a wireless communication module, a navigation module, a vehicle-mounted Liquid crystal display touch screen (Liquid CRYSTAL DISPLAY, abbreviated as LCD), an external camera, a vehicle burglar alarm, and the like. For a vehicle OTA, upgrades must be made at an appropriate time, at an appropriate location, and in an appropriate state of the vehicle.
Specifically, before the upgrading operation is performed on the vehicle, the vehicle state information needs to be read through a vehicle network, the vehicle state information can include information such as a gear, a vehicle speed, a rotating speed and electric quantity of the vehicle, after the vehicle state information is detected, whether the vehicle state information meets an OTA condition is judged, and when the vehicle state information meets the OTA condition, a module to be upgraded in the vehicle is upgraded. The vehicle network may include a controller area (Controller Area Network, abbreviated as CAN) bus network, a local area connection network (Local Interconnect Network, abbreviated as LIN), and a vehicle ethernet.
The OTA upgrading condition may include that the vehicle is in a stationary state, and the vehicle has sufficient electric quantity, for example, when the vehicle gear is in P gear, the vehicle speed and the rotational speed of the vehicle are both 0, and the vehicle is in a parking state and the electric quantity is greater than a preset value, the OTA environment is initialized, and the preset value is a minimum electric quantity value capable of completing the vehicle upgrading. In addition, before upgrading, it is necessary to determine that the vehicle cannot move, and ensure that the vehicle is in an environment that is safe and does not interfere with other vehicles.
After initializing the OTA environment, upgrade operations can be performed on the modules to be upgraded in the vehicle. Optionally, the module to be upgraded may be a software system using electronic intelligent control in the vehicle, for example, the module to be upgraded may be a driving micro control unit (Microcontroller Unit, abbreviated as MCU) or each electronic control unit (Electronic Control Unit, abbreviated as ECU) related to the vehicle, may include a vehicle information and communication control system ECU, a power transmission system ECU, a chassis control system ECU, a back control system ECU, and may further include key function modules such as a navigation module, an entertainment module, and the like.
Optionally, the process of upgrading the module to be upgraded may be that the vehicle-mounted terminal sends an upgrade request to the OTA server, where the upgrade request may include a module identifier, a current version number and a target version number of the module to be upgraded, the OTA server searches a corresponding target version upgrade package according to the module identifier and the target version number and sends the corresponding target version upgrade package to the vehicle-mounted terminal in response to the upgrade request, and the vehicle-mounted terminal updates and upgrades the current version software package according to the target version upgrade package after receiving the target version upgrade package.
Further, the vehicle-mounted terminal can monitor the upgrading process in real time to determine that the module with upgrading failure is a module to be repaired, when the upgrading is completed, the module with upgrading failure is required to be determined to be the module to be repaired, the module to be repaired is repaired, whether the current version number of the module to be upgraded is lower than the target version number is judged by acquiring the current version number and the target version number of the module to be upgraded, if the current version number of the module to be upgraded is lower than the target version number, the module to be upgraded is indicated to be failed to upgrade, the module to be upgraded is determined to be the module to be repaired, and the information and the upgrading version information of the module to be repaired are recorded; if the current version number of the module to be upgraded is the target version number, the module to be upgraded is successfully upgraded, and repair processing of the module to be upgraded is not needed.
The module information to be repaired comprises: the method comprises the steps of a module identifier to be repaired, a current version number corresponding to the module identifier to be repaired and a current version software package corresponding to the module identifier to be repaired, wherein the upgrading version information comprises: a target version number corresponding to the module identifier to be repaired and a target version upgrade package corresponding to the module identifier to be repaired.
For example, when the modules to be repaired are the module 1, the module 2 and the module 3, the current version numbers of the module 1, the module 2 and the module 3 are 1.0, the current version 1.0 of the module 1, the module 2 and the module 3 need to be upgraded to the target version 2.0, possibly due to the network environment change and other reasons, so that one or more modules fail to upgrade, for example, no upgrade package is in the module 1 or the current version is still 1.0, the module 1 fails to upgrade, the vehicle-mounted terminal records the upgrade package corresponding to the current version 1.0 corresponding to the module 1 and the upgrade package corresponding to the target version 2.0, and determines that the module 1 is the module to be repaired.
Step S102, initializing the OTA environment again.
In the embodiment of the application, after the to-be-repaired module with the upgrading failure is determined, when the to-be-repaired module is required to be repaired after the OTA upgrading failure is confirmed, the OTA environment CAN be initialized again, when the OTA environment is initialized, whether each module in the vehicle is in an open state or not and whether the module is a module affecting the upgrading CAN be judged, and when the module is the module affecting the upgrading and in the open state, the module affecting the upgrading CAN be closed, for example, a CAN bus communication module is closed, wherein the CAN bus communication module is used for realizing data communication between a vehicle internal control system and each detection and execution mechanism. Because the vehicle is normally powered on, different modules communicate through the CAN bus communication module, and the module which affects the upgrade is closed, the problem that other modules send messages to the vehicle-mounted terminal to affect the repair operation of the module in the repair processing process of the module to be repaired is avoided.
And step S103, after the initialization of the OTA environment is successful, repairing the module to be repaired.
Specifically, after determining the module to be repaired, when repairing the module to be repaired, initializing an OTA environment, after the OTA environment is successfully initialized, judging whether the repair affects the safety of the vehicle, and when the safety of the vehicle is not affected, acquiring information of the module to be repaired and upgrade version information, and repairing the module to be repaired to a target version according to the information of the module to be repaired and the upgrade version information.
Optionally, the process of determining whether to affect the safety of the vehicle may be determining whether the parameter of the module to be repaired is in a normal range, when the parameter of the module to be repaired is in the normal range, determining that the repair does not affect the safety of the vehicle, and when the parameter of the module to be repaired is not in the normal range, determining that the repair affects the safety of the vehicle, wherein the parameter of the module to be repaired may be gear information. By judging whether the safety of the vehicle is affected or not, the vehicle can be prevented from sliding in the repairing process, and the danger of the vehicle in the repairing process is avoided.
And when the repair is determined not to influence the safety of the vehicle, performing repair treatment on the module to be repaired. Optionally, the number of the to-be-repaired module may be one or more, and when the number of the to-be-repaired module is one, the vehicle-mounted terminal may acquire information of the to-be-repaired module and corresponding upgrade version information of the to-be-repaired module, and repair the to-be-repaired module to the target version according to the information of the to-be-repaired module and the corresponding upgrade version information; when a plurality of modules to be repaired are provided, obtaining the information of the modules to be repaired and the corresponding upgrade version information of each module to be repaired, and repairing each module to be repaired to the target version according to the information of each module to be repaired and the corresponding upgrade version information.
According to the OTA upgrading method provided by the embodiment of the application, after the previous OTA upgrading fails, the module to be repaired is determined, the module to be upgraded after the upgrading fails, the OTA environment is initialized again, and after the OTA environment is initialized successfully, the module to be repaired is repaired. According to the method, after the previous OTA upgrade of the vehicle fails, the module to be repaired is determined, and the initialization environment is carried out again, so that the influence of the previous upgrade on the vehicle is reduced, the module to be repaired is repaired under the condition that the influence of the previous upgrade on the vehicle is reduced, excessive manpower is not needed, the module to be repaired can be repaired directly at the vehicle-mounted terminal, the operation is convenient and quick, the upgrading time can be saved, the OTA upgrading success rate is further improved, and the danger of the vehicle in the use process is avoided.
As an implementation manner, based on the foregoing embodiment, fig. 2 is a schematic flow chart of an OTA upgrading method provided by an embodiment of the present application. As shown in fig. 2, the method includes:
Step S201, replacing the current version software package corresponding to the module identifier to be repaired with the target version upgrade package corresponding to the module identifier to be repaired.
Step S202, updating the current version number corresponding to the to-be-repaired identification as the target version number corresponding to the to-be-repaired module identification.
Specifically, after the module to be repaired is determined, the environment is initialized, after the OTA environment is initialized successfully, whether the repair affects the safety of the vehicle can be judged, and when the safety of the vehicle is not affected, the module to be repaired is repaired.
In this embodiment, when repairing a plurality of modules to be repaired, information of the modules to be repaired and corresponding upgrade version information of each module to be repaired may be obtained, and each module to be repaired is repaired to a target version according to the information of each module to be repaired and the corresponding upgrade version information.
When each module to be repaired is repaired, a current version number, a current version software package, a target version number and a target version upgrade package corresponding to the module to be repaired can be obtained, and when needed, the current version software package corresponding to the module to be repaired is replaced by the target version upgrade package corresponding to the module to be repaired, and the current version number corresponding to the module to be repaired is updated to be the target version number corresponding to the module to be repaired.
It should be noted that, when repairing a plurality of modules to be repaired, the modules to be repaired may be repaired synchronously, or the modules to be repaired one by one may be repaired.
For example, all modules to be repaired may be ordered according to the update package sizes of the target upgrade package and the current software package, and the modules to be repaired may be ordered into a first module to be repaired and a second module to be repaired one by one according to the update package sizes from small to large, where the update package size of the first module to be repaired is the smallest. When repairing modules to be repaired one by one, a current version number, a current version software package, a target version number and a target version upgrade package corresponding to a first module to be repaired identification are obtained, the current version number corresponding to the first module to be repaired identification is updated to be the target version number, and the current version software package corresponding to the first module to be repaired identification is updated to be the target version upgrade package; and after the first module to be repaired is repaired, determining a second module to be repaired, similarly, executing the same operation as the first module to be repaired on the second module to be repaired, repairing the second module to be repaired to a corresponding target version, and repeating the steps to execute the repairing operation on all the modules to be repaired.
Further, after repairing all the modules to be repaired, judging whether the modules to be repaired are repaired to a target version, acquiring a current version number and a target version number of the modules to be repaired, and according to the current version number and the target version number, if the current version number is smaller than the target version number, indicating that the modules to be repaired are not repaired to the target version, and continuing the repairing until the modules to be repaired are repaired to the target version; if the current version number is the target version number, the module to be repaired is repaired to be the target version, and the repair process is not required to be continued. And when all the modules to be repaired are repaired to the target version, exiting the OTA environment, wherein the exiting OTA environment is that the module closed during initializing the OTA environment is started, for example, a CAN bus communication module is started.
If the to-be-repaired modules with the repair failure exist in all the to-be-repaired modules, the OTA environment is continuously initialized, and the to-be-repaired modules with the repair failure are repaired until all the to-be-repaired modules with the repair failure are repaired to the target version.
In the embodiment of the application, the current version number corresponding to the to-be-repaired identification, the current version software package, the target version number and the target version upgrading package are obtained, the target version upgrading package corresponding to the to-be-repaired module identification is replaced with the current version software package corresponding to the to-be-repaired module identification, and the current version number corresponding to the to-be-repaired identification is updated to be the target version number corresponding to the to-be-repaired module identification. According to the method, the vehicle-mounted terminal can repair the module to be repaired according to the information of the module to be upgraded and the upgrading version information recorded after the upgrading failure until the module to be repaired is repaired to the target version, so that the OTA upgrading success rate is improved, and the danger of the vehicle in the using process is avoided.
Fig. 3 is a schematic structural diagram of an OTA upgrading device according to an embodiment of the present application. As shown in fig. 3, the apparatus includes:
The determining module 10 is configured to determine, after a previous OTA upgrade fails, a module to be repaired, where the module to be repaired is a module to be upgraded after the upgrade fails;
A first initializing module 20, configured to initialize the OTA environment again;
and the repair module 30 is configured to repair the module to be repaired after the initialization of the OTA environment is successful.
Optionally, the determining module 10 includes:
a first obtaining unit 101, configured to obtain a current version number and a target version number of the module to be upgraded;
a judging unit 102, configured to judge whether the current version number is lower than the target version number;
And the determining unit 103 is configured to determine that the module to be upgraded is a module to be repaired if the current version number of the module to be upgraded is lower than the target version number.
Optionally, the apparatus further comprises:
A detection module 40 for detecting vehicle state information;
A second initialization module 50, configured to initialize an OTA environment when the vehicle state information satisfies an OTA condition, where the OTA condition includes: the vehicle is in a stationary state and has sufficient electric quantity;
the first processing module 60 is configured to upgrade the module to be upgraded, and record information of the module to be repaired and upgrade version information.
Optionally, the repair module 30 includes:
the second obtaining unit 301 is configured to obtain, when the number of to-be-repaired modules is multiple, to-be-repaired module information and corresponding upgrade version information of each to-be-repaired module;
And the repairing unit 302 is configured to repair each module to be repaired to a target version according to each module to be repaired information and the corresponding upgrade version information.
Optionally, the module information to be repaired includes: the method comprises the steps of identifying a module to be repaired, a current version number corresponding to the module to be repaired and a current version software package corresponding to the module to be repaired, wherein the upgrading version information comprises: a target version number corresponding to the module identifier to be repaired and a target version upgrade package corresponding to the module identifier to be repaired;
the repairing unit 302 is specifically configured to:
replacing the current version software package corresponding to the module identifier to be repaired with the target version upgrade package corresponding to the module identifier to be repaired;
And updating the current version number corresponding to the to-be-repaired identification as the target version number corresponding to the to-be-repaired module identification.
Optionally, the apparatus further includes:
A judging module 70, configured to judge whether the module to be repaired is repaired to a target version;
The second processing module 80 is configured to exit the OTA environment if all the modules to be repaired are repaired to the target version; if the to-be-repaired modules with the repair failure exist in all the to-be-repaired modules, the OTA environment is continuously initialized, and the to-be-repaired modules with the repair failure are subjected to repair processing until all the to-be-repaired modules with the repair failure are repaired to the target version.
The OTA upgrading device provided in this embodiment can execute the embodiment of the method, and its implementation principle and technical effects are similar, and will not be described in detail herein.
Fig. 4 is a schematic structural diagram of a computer device according to an embodiment of the present application. As shown in fig. 4, a schematic diagram of a computer system 400 suitable for use in implementing the in-vehicle apparatus of the embodiment of the present application is shown.
As shown in fig. 4, the computer system 400 includes a Central Processing Unit (CPU) 401, which can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 402 or a program loaded from a storage section 408 into a Random Access Memory (RAM) 403. In RAM403, various programs and data required for the operation of system 400 are also stored. The CPU401, ROM402, and RAM403 are connected to each other by a bus 404. An input/output (I/O) interface 406 is also connected to bus 404.
The following components are connected to the I/O interface 405: an input section 406 including a keyboard, a mouse, and the like; an output portion 407 including a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker, and the like; a storage section 408 including a hard disk or the like; and a communication section 409 including a network interface card such as a LAN card, a modem, or the like. The communication section 409 performs communication processing via a network such as the internet. The drive 410 is also connected to the I/O interface 406 as needed. A removable medium 411 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is installed on the drive 410 as needed, so that a computer program read therefrom is installed into the storage section 408 as needed.
In particular, according to embodiments of the present disclosure, the process described above with reference to fig. 2 may be implemented as a computer software program. For example, embodiments of the present disclosure include a computer program product comprising a computer program tangibly embodied on a machine-readable medium, the computer program comprising program code for performing the method of fig. 2. In such an embodiment, the computer program may be downloaded and installed from a network via the communication portion 409 and/or installed from the removable medium 411.
The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The units or modules involved in the embodiments of the present application may be implemented in software or in hardware. The described units or modules may also be provided in a processor, for example, as: a processor includes a determination module, a first initialization module, and a repair module. The names of these units or modules do not in some cases limit the unit or module itself, for example, the determining module may also be described as "determining a module to be repaired after the previous OTA upgrade fails," where the module to be repaired is a module to be upgraded after the upgrade fails ".
As another aspect, the present application also provides a computer-readable medium that may be contained in the electronic device described in the above embodiment; or may exist alone without being incorporated into the electronic device. The computer readable medium carries one or more programs which, when executed by the electronic device, cause the electronic device to implement the OTA upgrade method as described in the above embodiments.
For example, the electronic device may implement the method as shown in fig. 1: step S101, after the previous OTA upgrade fails, determining a module to be repaired, wherein the module to be repaired is the module to be upgraded after the upgrade fails; step S102, initializing the OTA environment again; step S103, after the OTA environment is initialized successfully, repairing the module to be repaired. As another example, the electronic device may implement the various steps as shown in fig. 2.
It should be noted that although in the above detailed description several modules or units of a device for action execution are mentioned, such a division is not mandatory. Indeed, the features and functionality of two or more modules or units described above may be embodied in one module or unit in accordance with embodiments of the present disclosure. Conversely, the features and functions of one module or unit described above may be further divided into a plurality of modules or units to be embodied.
Furthermore, although the steps of the methods in the present disclosure are depicted in a particular order in the drawings, this does not require or imply that the steps must be performed in that particular order, or that all illustrated steps be performed, to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step to perform, and/or one step decomposed into multiple steps to perform, etc. From the above description of embodiments, those skilled in the art will readily appreciate that the example embodiments described herein may be implemented in software, or may be implemented in software in combination with the necessary hardware.
In summary, according to the method, the device, the vehicle-mounted terminal and the storage medium for upgrading the OTA provided by the embodiment of the application, after the previous OTA upgrading fails, the module to be repaired is determined, the module to be upgraded after the upgrading fails, the OTA environment is initialized again, and when the OTA environment is initialized successfully, the module to be repaired is repaired. According to the technical scheme, after the vehicle fails to upgrade the OTA at the previous time, the module to be repaired is determined, and the OTA environment is initialized, so that the influence of the last upgrade on the vehicle state is avoided when the module to be repaired is repaired.
The foregoing description is only illustrative of the principles of the application as it may be embodied in this disclosure. It will be appreciated by those skilled in the art that the scope of the application is not limited to the specific combination of the above technical features, but also covers technical solutions formed by mutually replacing the above technical features with the technical features disclosed in the application (but not limited to the technical features with similar functions) without departing from the concept of the application.
Claims (7)
1. An OTA upgrade method, comprising:
detecting vehicle state information and judging whether the vehicle state information meets OTA upgrading conditions or not; the OTA upgrade condition comprises: the vehicle is in a stationary state and has sufficient electric quantity;
when the vehicle state information meets OTA upgrading conditions, initializing an OTA environment, upgrading a module to be upgraded in a vehicle, and recording information of the module to be repaired and upgrading version information;
After the previous OTA upgrade fails, determining a module to be repaired, wherein the module to be repaired is a module to be upgraded which fails to upgrade;
Judging whether each module in the vehicle is in an open state or not and whether the module is a module affecting upgrading, and closing the module in the open state and affecting upgrading when the module is in the open state and is a module affecting upgrading so as to initialize the OTA environment again; the module for influencing upgrading comprises a CAN bus communication module;
Judging whether the repair affects the safety of the vehicle after the OTA environment is successfully initialized, and repairing the module to be repaired according to the information of the module to be repaired and the upgrade version information when the safety of the vehicle is not affected; judging whether the repair affects the safety of the vehicle or not includes judging whether the parameters of the module to be repaired are in a normal range or not, and determining that the repair affects the safety of the vehicle when the parameters of the module to be repaired are not in the normal range; the module parameters to be repaired comprise gear information;
Wherein the determining the module to be repaired includes:
acquiring a current version number and a target version number of the module to be upgraded;
judging whether the current version number is lower than the target version number;
if the current version number of the module to be upgraded is lower than the target version number, determining that the module to be upgraded is a module to be repaired;
The module information to be repaired comprises: the method comprises the steps of identifying a module to be repaired, a current version number corresponding to the module to be repaired and a current version software package corresponding to the module to be repaired, wherein the upgrading version information comprises: a target version number corresponding to the module identifier to be repaired and a target version upgrade package corresponding to the module identifier to be repaired;
the repairing the module to be repaired according to the module to be repaired information and the upgrade version information comprises the following steps:
replacing the current version software package corresponding to the module identifier to be repaired with the target version upgrade package corresponding to the module identifier to be repaired;
and updating the current version number corresponding to the module identifier to be repaired to be the target version number corresponding to the module identifier to be repaired.
2. The OTA upgrading method of claim 1 wherein performing repair processing on the module to be repaired comprises:
When a plurality of modules to be repaired are provided, obtaining information of the modules to be repaired and corresponding upgrade version information of each module to be repaired;
and repairing each module to be repaired to a target version according to the information of each module to be repaired and the corresponding upgrading version information.
3. The OTA upgrading method according to any one of claims 1-2 wherein after performing a repair process on the module to be repaired, the method further comprises:
judging whether the module to be repaired is repaired to a target version or not;
If all the modules to be repaired are repaired to the target version, exiting the OTA environment;
If the to-be-repaired modules with the repair failure exist in all the to-be-repaired modules, the OTA environment is continuously initialized, and the to-be-repaired modules with the repair failure are subjected to repair processing until all the to-be-repaired modules with the repair failure are repaired to the target version.
4. An OTA upgrading device, said device comprising:
The method comprises the steps of determining a module to be repaired after a previous OTA upgrading fails, wherein the module to be repaired is the module to be upgraded after the upgrading fails;
The first initialization module is used for judging whether each module in the vehicle is in an open state and is a module affecting upgrading, and when the module is in the open state and is a module affecting upgrading, the module in the open state and is a module affecting upgrading is closed so as to initialize the OTA environment again; the module for influencing upgrading comprises a CAN bus communication module;
the repair module is used for judging whether the repair affects the safety of the vehicle after the initialization of the OTA environment is successful, and performing repair treatment on the module to be repaired when the safety of the vehicle is not affected; judging whether the repair affects the safety of the vehicle or not includes judging whether the parameters of the module to be repaired are in a normal range or not, and determining that the repair affects the safety of the vehicle when the parameters of the module to be repaired are not in the normal range; the module parameters to be repaired comprise gear information;
The device is further configured to: detecting vehicle state information and judging whether the vehicle state information meets OTA upgrading conditions or not; when the vehicle state information meets OTA upgrading conditions, initializing an OTA environment, upgrading a module to be upgraded in a vehicle, and recording information of the module to be repaired and upgrading version information; the OTA upgrade condition comprises: the vehicle is in a stationary state and has sufficient electric quantity;
The determining module is specifically configured to obtain a current version number and a target version number of the module to be upgraded;
judging whether the current version number is lower than the target version number;
if the current version number of the module to be upgraded is lower than the target version number, determining that the module to be upgraded is a module to be repaired;
The module information to be repaired comprises: the method comprises the steps of identifying a module to be repaired, a current version number corresponding to the module to be repaired and a current version software package corresponding to the module to be repaired, wherein the upgrading version information comprises: a target version number corresponding to the module identifier to be repaired and a target version upgrade package corresponding to the module identifier to be repaired;
the device is further configured to: replacing the current version software package corresponding to the module identifier to be repaired with the target version upgrade package corresponding to the module identifier to be repaired;
and updating the current version number corresponding to the module identifier to be repaired to be the target version number corresponding to the module identifier to be repaired.
5. The OTA upgrading device of claim 4, wherein the determining module comprises:
The first acquisition unit is used for acquiring the current version number and the target version number of the module to be upgraded;
A judging unit, configured to judge whether the current version number is lower than the target version number;
and the determining unit is used for determining the module to be upgraded as the module to be repaired if the current version number of the module to be upgraded is lower than the target version number.
6. A vehicle terminal comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the method according to any of claims 1-3 when executing the program.
7. A computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements the method of any of claims 1-3.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911376772.4A CN113050960B (en) | 2019-12-27 | 2019-12-27 | OTA upgrading method and device, vehicle-mounted terminal and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911376772.4A CN113050960B (en) | 2019-12-27 | 2019-12-27 | OTA upgrading method and device, vehicle-mounted terminal and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113050960A CN113050960A (en) | 2021-06-29 |
| CN113050960B true CN113050960B (en) | 2024-07-16 |
Family
ID=76506326
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911376772.4A Active CN113050960B (en) | 2019-12-27 | 2019-12-27 | OTA upgrading method and device, vehicle-mounted terminal and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113050960B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114827106A (en) * | 2022-03-18 | 2022-07-29 | 中科晶上（苏州）信息技术有限公司 | Electric vehicle remote upgrading method |
| CN115118577B (en) * | 2022-06-24 | 2023-08-18 | 重庆长安汽车股份有限公司 | Remote upgrade abnormality cause determination method, device, electronic equipment and storage medium |
| WO2024197832A1 (en) * | 2023-03-31 | 2024-10-03 | 华为技术有限公司 | Upgrade method and apparatus, and vehicle |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105357231A (en) * | 2014-07-24 | 2016-02-24 | 中兴通讯股份有限公司 | Difference upgrade method, server and terminal |
| CN107748667A (en) * | 2017-10-23 | 2018-03-02 | 郑州云海信息技术有限公司 | A kind of method for lifting server power supply online updating firmware reliability |
| CN110162323A (en) * | 2019-05-28 | 2019-08-23 | 广州小鹏汽车科技有限公司 | Onboard system upgrade method, device, storage medium and vehicle |
Family Cites Families (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP6056424B2 (en) * | 2012-11-29 | 2017-01-11 | 株式会社デンソー | In-vehicle program update device |
| CN104375844A (en) * | 2013-08-12 | 2015-02-25 | 中兴通讯股份有限公司 | Firmware upgrading method and device |
| CN106610840A (en) * | 2015-10-22 | 2017-05-03 | 深圳市中兴微电子技术有限公司 | FOTA (Firmware Over-The-Air) upgrade method and system |
| CN105589719B (en) * | 2015-12-17 | 2019-12-13 | 广州汽车集团股份有限公司 | system for remotely upgrading whole vehicle-mounted controller software and upgrading method |
| CN106339248A (en) * | 2016-10-09 | 2017-01-18 | 大道网络（上海）股份有限公司 | Remote software upgrading method and remote software upgrading system |
| CN108334356A (en) * | 2017-09-21 | 2018-07-27 | 安徽江淮汽车集团股份有限公司 | A kind of remotely updating program method and system |
| CN108958774A (en) * | 2018-07-13 | 2018-12-07 | 深圳市道通智能航空技术有限公司 | Module updating method and module to be upgraded in UAV system |
| CN109491681B (en) * | 2018-10-19 | 2022-03-01 | 北京经纬恒润科技股份有限公司 | Method and device for upgrading MCU in automobile |
| CN110347412B (en) * | 2019-06-27 | 2023-05-30 | 中国第一汽车股份有限公司 | Electronic control unit firmware upgrade management method, device, equipment and storage medium |
-
2019
- 2019-12-27 CN CN201911376772.4A patent/CN113050960B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105357231A (en) * | 2014-07-24 | 2016-02-24 | 中兴通讯股份有限公司 | Difference upgrade method, server and terminal |
| CN107748667A (en) * | 2017-10-23 | 2018-03-02 | 郑州云海信息技术有限公司 | A kind of method for lifting server power supply online updating firmware reliability |
| CN110162323A (en) * | 2019-05-28 | 2019-08-23 | 广州小鹏汽车科技有限公司 | Onboard system upgrade method, device, storage medium and vehicle |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113050960A (en) | 2021-06-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN113050960B (en) | OTA upgrading method and device, vehicle-mounted terminal and storage medium | |
| CN111399884A (en) | Vehicle component upgrading method and device and electronic equipment | |
| CN110659038B (en) | Vehicle-mounted millimeter wave radar upgrading method and device, computer equipment and storage medium | |
| CN110673576A (en) | Automatic test method and device, vehicle and storage medium | |
| CN110687888B (en) | Automatic upgrading test device and system applied to locomotive | |
| CN108241498B (en) | Vehicle-mounted equipment upgrading method and device and vehicle | |
| US9569404B2 (en) | In-vehicle controller and non-transitory tangible computer readable medium | |
| CN113238774A (en) | Vehicle-mounted greeting animation updating method and device, vehicle-mounted terminal and storage medium | |
| CN113608763A (en) | Vehicle-mounted OTA upgrading method, device, equipment and operation machine | |
| CN116028092A (en) | Method, device, equipment and storage medium for fusing automobile OTA upgrading task | |
| KR102239904B1 (en) | Ota master device, system and method for managing update of vehicle ecus | |
| CN112134961A (en) | Client use control method, client and computer storage medium | |
| CN116048587A (en) | Remote automatic upgrading method, device, server, equipment and medium for vehicle | |
| CN111158729A (en) | System upgrading method, device, equipment and storage medium | |
| CN113037850A (en) | Application program upgrading method and device, electronic equipment and storage medium | |
| CN112181467A (en) | Method and device for upgrading memory firmware of terminal, terminal and storage medium | |
| WO2020001249A1 (en) | Method and device for updating tire pressure monitoring system (tpms) diagnostic tool | |
| CN110618826A (en) | Method and device for updating application program and terminal equipment | |
| CN116257270A (en) | Vehicle, upgrading method and device of vehicle | |
| CN115583206A (en) | Vehicle abnormity eliminating method and device, electronic equipment and storage medium | |
| CN113791800A (en) | Automatic parking control module remote upgrading method and system and automobile | |
| CN115934130A (en) | ECU (electronic control Unit) upgrading method, device, equipment and medium | |
| CN114647424A (en) | ECU application program updating method, device, system, storage medium and electronic equipment | |
| CN118259939B (en) | Electronic control unit upgrading method and device, vehicle terminal and storage medium | |
| CN113110861A (en) | Automobile data recorder terminal upgrading method, device, equipment and storage medium |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |