CN113050960A - OTA (over the air) upgrading method and device, vehicle-mounted terminal and storage medium - Google Patents
OTA (over the air) upgrading method and device, vehicle-mounted terminal and storage medium Download PDFInfo
- Publication number
- CN113050960A CN113050960A CN201911376772.4A CN201911376772A CN113050960A CN 113050960 A CN113050960 A CN 113050960A CN 201911376772 A CN201911376772 A CN 201911376772A CN 113050960 A CN113050960 A CN 113050960A
- Authority
- CN
- China
- Prior art keywords
- module
- repaired
- ota
- upgraded
- upgrade
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 58
- 230000008439 repair process Effects 0.000 claims description 19
- 238000004590 computer program Methods 0.000 claims description 12
- 238000012545 processing Methods 0.000 claims description 12
- 230000003068 static effect Effects 0.000 claims description 3
- 230000008569 process Effects 0.000 abstract description 13
- 238000004891 communication Methods 0.000 description 12
- 238000010586 diagram Methods 0.000 description 9
- 230000006870 function Effects 0.000 description 9
- 238000005516 engineering process Methods 0.000 description 3
- 230000009471 action Effects 0.000 description 2
- 230000007547 defect Effects 0.000 description 2
- 238000001514 detection method Methods 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 239000004973 liquid crystal related substance Substances 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 1
- 230000008859 change 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
- 238000005096 rolling process Methods 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- 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
Abstract
The application discloses an OTA upgrading method, an OTA upgrading device, a vehicle-mounted terminal and a storage medium, wherein the method comprises the following steps: determining a module to be repaired after the previous OTA fails to be upgraded, wherein the module to be repaired is the module to be upgraded after the previous OTA fails to be upgraded; initializing the OTA environment again; and when the OTA environment is initialized successfully, repairing the module to be repaired. The method can determine the module to be repaired and initialize the environment after the previous OTA upgrade of the vehicle fails, so that the module to be repaired is repaired under the condition of reducing the influence of the previous upgrade on the vehicle, the process does not need excessive manpower participation, the module to be repaired can be directly repaired on the vehicle-mounted terminal, the operation is convenient and rapid, the upgrade time can be saved, the OTA upgrade success rate is further improved, and the danger of the vehicle in the use process is avoided.
Description
Technical Field
The invention relates to the technical field of networks, 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 need to be upgraded continuously during use, such as vehicle control systems, by using Over-the-Air Technology (OTA for short). The OTA upgrading is mainly to upgrade the system firmware by automatically downloading an OTA upgrading packet through a network, or to upgrade the OTA by downloading the OTA upgrading packet to the SD card, and system bugs can be repaired by upgrading to optimize system functions.
Currently, an 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 completes an OTA upgrade operation by configuring a task list and an upgrade software package and sending the upgrade software package to the OTA front end upon receiving a request from the OTA front end.
However, in the upgrading scheme, after the OTA upgrading fails, the version of the control system program is too low or no program exists, the system needs to be updated manually by using a specific mobile device on site, and the operation process wastes manpower and time, so that the vehicle cannot be used normally and run safely.
Disclosure of Invention
In view of the above-mentioned defects 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 the OTA upgrading of a vehicle fails, and the method is convenient and fast, does not require excessive human involvement, can improve the success rate of OTA upgrading, and reduces the possibility of danger during the use of the vehicle.
In a first aspect, the present application provides an OTA upgrading method, including:
determining a module to be repaired after the previous OTA fails to be upgraded, wherein the module to be repaired is the module to be upgraded after the previous OTA fails to be upgraded;
initializing the OTA environment again;
and when the OTA environment is initialized successfully, repairing the module to be repaired.
In one embodiment, determining a 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;
and if the current version number of the module to be upgraded is lower than the target version number, determining the module to be upgraded as a module to be repaired.
In one embodiment, the previous OTA upgrade comprises:
detecting vehicle state information;
initializing an OTA environment when the vehicle state information satisfies OTA conditions, the OTA conditions including: the vehicle is in a static state and the electric quantity is sufficient;
and upgrading the module to be upgraded, and recording the information of the module to be repaired and the information of the upgraded version.
In one embodiment, the performing the repair process on the module to be repaired includes:
when the number of the modules to be repaired is multiple, acquiring the information of the modules to be repaired and the corresponding upgrade version information of each module to be repaired;
and restoring each module to be restored to a target version according to the information of each module to be restored and the corresponding upgrade version information.
In one embodiment, the module information to be repaired includes: 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 upgrade version information includes: 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; restoring each module to be restored to a target version according to each module to be restored information and the corresponding upgrade version information, including:
replacing the current version software package corresponding to the module identifier to be repaired with the target version upgrading package corresponding to the module identifier to be repaired;
and updating the current version number corresponding to the identifier to be repaired to be the target version number corresponding to the identifier of the module to be repaired.
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 modules to be repaired are repaired to the target version, quitting the OTA environment;
and if the modules to be repaired which fail to be repaired exist in all the modules to be repaired, continuously initializing the OTA environment, and repairing the modules to be repaired which fail to be repaired until all the modules to be repaired which fail to be repaired are repaired to the target version.
In a second aspect, the present application provides an OTA upgrading apparatus, comprising:
the determining module is used for determining a module to be repaired after the previous OTA fails to be upgraded, and the module to be repaired is the module to be upgraded after the OTA fails to be upgraded;
the first initialization module is used for initializing the OTA environment again;
and the repairing module is used for repairing the module to be repaired after the OTA environment is successfully initialized.
In a third aspect, an embodiment of the present application provides a vehicle-mounted terminal, which includes a memory and a processor, where the memory stores a computer program, and the processor implements the OTA upgrading method when executing the computer program.
In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored, and the computer program, when executed by a processor, implements the OTA upgrading method described above.
In summary, the application provides an OTA upgrading method, an OTA upgrading device, a vehicle-mounted terminal and a storage medium, in the method, 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 OTA upgrading fails, the OTA environment is initialized again, and after the OTA environment is successfully initialized, the module to be repaired is repaired. The method can reduce the influence of the previous upgrading on the vehicle by determining the module to be repaired and initializing the environment again after the previous OTA upgrading of the vehicle fails, so that the module to be repaired is repaired under the condition of reducing the influence of the previous upgrading on the vehicle.
Drawings
Other features, objects and advantages of the present application will become more apparent upon reading of the following detailed description of non-limiting embodiments thereof, made with reference to the accompanying drawings in which:
fig. 1 is a schematic flowchart of an OTA upgrading method provided in an embodiment of the present application;
fig. 2 is a schematic flowchart of an OTA upgrading method provided in an embodiment of the present application;
fig. 3 is a schematic structural diagram of an OTA upgrading apparatus provided in 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 present application will be described in further detail with reference to the following drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the relevant invention and not restrictive of the invention. It should be noted that, for convenience of description, only the portions related to the present invention are shown in the drawings.
It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict. The present application will be described in detail below with reference to the embodiments with reference to the attached drawings.
It can be understood that with the intelligent development of the vehicle-mounted equipment, OTA upgrade is generally required to be performed on various vehicle-mounted control systems such as vehicle-mounted applications at an indefinite time, and currently common OTA upgrade mainly aims at upgrading multimedia functions such as navigation, parking assistance, infotainment, comfort configuration and the like, so that system bugs are repaired, system functions are optimized, and user experience is greatly optimized.
As mentioned in the background, currently, existing vehicle control systems include an OTA management system and an OTA front end of a vehicle to be upgraded, the OTA management system enabling the OTA front end to complete an OTA upgrade according to a software upgrade package by sending the OTA front end a software upgrade package. However, the scheme only relates to an upgrading operation process, and does not consider a processing process after upgrading failure, if upgrading failure occurs, the version of a control system program is too low or no program exists, after-sales personnel are required to package downloaded software onto a vehicle field, and a specific device is used for updating the system, so that the operation process wastes manpower and time.
Based on the defects, the OTA upgrading method is characterized in that after the previous OTA upgrading fails, the module to be repaired is determined, the OTA environment is initialized, and after the OTA environment is successfully initialized, the module to be repaired is repaired. Compared with the prior art, the method does not need excessive manpower participation, can directly carry out repair processing on the module to be repaired on the vehicle-mounted terminal, is simple, convenient and quick in repair operation, can save the upgrade time, further improves the OTA upgrade success rate, and avoids the danger of the vehicle in the use process.
Fig. 1 is a schematic flowchart 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 comprises the following steps:
step S101, after the OTA fails to be upgraded in the previous time, determining a module to be repaired, wherein the module to be repaired is the module to be upgraded after the OTA fails to be upgraded.
It can be understood that the vehicle-mounted terminal is a front-end device of the vehicle monitoring management system, and may include a wireless communication module, a navigation module, a vehicle-mounted Liquid Crystal Display (LCD), an external camera, a vehicle burglar alarm, and the like. For the vehicle OTA, the upgrade must be performed at an appropriate time, at an appropriate location, and in an appropriate state of the vehicle.
Specifically, before upgrading the vehicle, the vehicle state information needs to be read through the vehicle network, and may include information of a gear, a vehicle speed, a rotating speed, an electric quantity, and the like of the vehicle. The vehicle Network may include a Controller Area Network (CAN) bus Network, a Local Interconnect Network (LIN) and a vehicle ethernet Network.
The OTA upgrading condition may include that the vehicle is in a stationary state, and the electric quantity of the vehicle is sufficient, for example, when the gear of the vehicle is P gear, the speed and the rotating 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 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 where safety is ensured and interference to other vehicles is not caused.
After the OTA environment is initialized, the module to be upgraded in the vehicle can be upgraded. 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 (MCU) or each Electronic Control Unit (ECU) related to the vehicle, may include a vehicle-mounted 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 a navigation module, an entertainment module, and other key function modules.
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 for a corresponding target version upgrade package according to the module identifier and the target version number in response to the upgrade request, and sends the target version upgrade package to the vehicle-mounted terminal, and after receiving the target version upgrade package, the vehicle-mounted terminal updates and upgrades the current version software package according to the target version upgrade package.
Further, the vehicle-mounted terminal can monitor the upgrading process in real time to determine that the module failed in upgrading is the module to be repaired, after upgrading is completed, the module failed in upgrading needs to be determined to be the module to be repaired, the module to be repaired is repaired, whether the current version number 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 in upgrading, the module to be upgraded is determined to be the module to be repaired, and the information of the module to be repaired and the information of the upgrading version 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 the module to be upgraded is not required to be repaired.
Wherein, the module information to be repaired includes: the module to be repaired comprises 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 upgrade version information comprises: the target version number corresponding to the module identifier to be repaired and the target version upgrading packet corresponding to the module identifier to be repaired.
Exemplarily, when the modules to be repaired are the module 1, the module 2, and the module 3, respectively, the current version numbers of the module 1, the module 2, and the module 3 are all 1.0, it is necessary to upgrade the current versions 1.0 of the module 1, the module 2, and the module 3 to the target version 2.0, and it may be caused by a change in network environment, that one or more modules are failed to be upgraded, for example, if there is no upgrade package in the module 1 or the current version is still 1.0, it indicates that the module 1 is failed to be upgraded, the vehicle-mounted terminal records the upgrade package corresponding to the current version 1.0 and the upgrade package corresponding to the target version 2.0, respectively, and determines that the module 1 is the module to be repaired.
And step S102, initializing the OTA environment again.
In this application embodiment, after the current OTA upgrading fails, after determining the module to be repaired that fails upgrading, when needing to treat the module to be repaired and repair, the OTA environment CAN be initialized again, when initializing the OTA environment, CAN judge whether each module in the vehicle is in the open state and whether is the module that influences the upgrading, when this module is for influencing the upgrading and is in the module of open state, CAN close this module that influences the upgrading, for example, close CAN bus communication module, wherein, this CAN bus communication module is used for realizing the data communication between vehicle internal control system and each detection and the actuating mechanism. Because the vehicle is when normal power-on work, have different modules and communicate through CAN bus communication module, through closing this module that influences the upgrading to avoid waiting to restore the module and in the in-process of carrying out repair treatment, other modules send the message to this vehicle terminal, influence the repair operation of module.
And step S103, when the OTA environment is initialized successfully, repairing the module to be repaired.
Specifically, after the module to be repaired is determined, when the module to be repaired is repaired, the OTA environment is initialized first, after the OTA environment is initialized successfully, whether the vehicle safety is affected by the repair can be judged, when the vehicle safety is not affected, the module information to be repaired and the upgrade version information are acquired, and the module to be repaired is repaired to the target version according to the module information to be repaired and the upgrade version information.
Optionally, the process of determining whether to affect the vehicle safety 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, it is determined that the repair does not affect the vehicle safety, and when the parameter of the module to be repaired is not in the normal range, it is determined that the repair affects the vehicle safety, where the parameter of the module to be repaired may be gear information. Whether influence vehicle safety through judging can prevent that the vehicle from rolling away at the restoration in-process, avoids the vehicle to take place danger at restoration processing in-process.
And when the repair is determined not to affect the vehicle safety, performing repair processing on the module to be repaired. Optionally, one or more modules to be repaired may be used, and when one module to be repaired is used, the vehicle-mounted terminal may obtain information of the module to be repaired and corresponding upgrade version information, and repair the module to be repaired to the target version according to the information of the module to be repaired and the corresponding upgrade version information; when the number of the modules to be repaired is multiple, the information of the modules to be repaired and the corresponding upgrade version information of each module to be repaired are obtained, and each module to be repaired is 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, the module to be repaired is determined after the previous OTA upgrading fails, the module to be repaired is the module to be upgraded after the upgrading fails, the OTA environment is initialized again, and the module to be repaired is repaired after the OTA environment is initialized successfully. The method can reduce the influence of the previous upgrading on the vehicle by determining the module to be repaired and initializing the environment again after the previous OTA upgrading of the vehicle fails, so that the module to be repaired is repaired under the condition of reducing the influence of the previous upgrading on the vehicle.
As an implementation manner, on the basis of the foregoing embodiment, fig. 2 is a schematic flow chart of an OTA upgrading method provided in this embodiment. 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 identifier to be repaired to be the target version number corresponding to the identifier of the module to be repaired.
Specifically, after the module to be repaired is determined, the environment is initialized first, after the OTA environment is initialized successfully, whether the vehicle safety is affected by repairing can be judged, and when the vehicle safety is not affected, the module to be repaired is repaired.
In this embodiment, when a plurality of modules to be repaired are repaired, the module information to be repaired and the corresponding upgrade version information of each module to be repaired may be obtained, and each module to be repaired is repaired to the target version according to each module information to be repaired and the corresponding upgrade version information.
When each module to be repaired is repaired, the current version number, the current version software package, the target version number and the target version upgrade package corresponding to the identifier of the module to be repaired can be acquired, when necessary, the target version upgrade package corresponding to the identifier of the module to be repaired replaces the current version software package corresponding to the identifier of the module to be repaired, and the current version number corresponding to the identifier of the module to be repaired is updated to be the target version number corresponding to the identifier of the module to be repaired.
It should be noted that, when repairing a plurality of modules to be repaired, the plurality of modules to be repaired may be repaired simultaneously, or the modules to be repaired one by one may be repaired.
For example, all modules to be repaired may be sorted according to the update package sizes of the target upgrade package and the current software package, and may be sorted into a first module to be repaired and a second module to be repaired one by one from small to large according to the update package size, where the update package size of the first module to be repaired is the smallest. When modules to be repaired are 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 identifier to be repaired are obtained, the current version number corresponding to the first module identifier to be repaired is updated to be the target version number, and the current version software package corresponding to the first module identifier to be repaired 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, 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 the corresponding target version, and repeating the steps to execute the repairing operation on all the modules to be repaired.
Further, after all the modules to be repaired are repaired, whether the modules to be repaired are repaired to the target version or not can be judged, and the modules to be repaired are not repaired to the target version and need to be continuously repaired until the modules to be repaired are repaired to the target version by acquiring the current version number and the 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; and if the current version number is the target version number, the module to be repaired is repaired to be the target version number, and the repairing treatment is not required to be continuously carried out. And when all the modules to be repaired are repaired to the target version, exiting the OTA environment, wherein the exiting OTA environment is used for starting the modules which are closed when the OTA environment is initialized, for example, the CAN bus communication module is started.
And if the modules to be repaired which fail to be repaired exist in all the modules to be repaired, continuously initializing the OTA environment, and repairing the modules to be repaired which fail to be repaired until all the modules to be repaired which fail to be repaired are repaired to the target version.
In the embodiment of the application, the current version number, the current version software package, the target version number and the target version upgrade package corresponding to the identifier to be repaired are obtained, the target version upgrade package corresponding to the identifier of the module to be repaired is used for replacing the current version software package corresponding to the identifier of the module to be repaired, and the current version number corresponding to the identifier to be repaired is updated to be the target version number corresponding to the identifier of the module to be repaired. According to the method, the module to be repaired can be repaired at the vehicle-mounted terminal according to the information of the module to be upgraded and the information of the upgraded version recorded after the upgrade fails 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 apparatus according to an embodiment of the present application. As shown in fig. 3, the apparatus includes:
the determining module 10 is configured to determine a module to be repaired after a previous OTA upgrade fails, where the module to be repaired is the module to be upgraded after the upgrade fails;
a first initialization module 20 for initializing the OTA environment again;
and the repairing module 30 is configured to perform repairing processing on the module to be repaired after the OTA environment is initialized successfully.
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 determining unit 102, configured to determine whether the current version number is lower than the target version number;
a determining unit 103, configured to determine that the module to be upgraded is the 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 OTA conditions, the OTA conditions including: the vehicle is in a static state and the electric quantity is sufficient;
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:
a second obtaining unit 301, configured to obtain, when there are multiple modules to be repaired, module information to be repaired and corresponding upgrade version information of each module to be repaired;
a repairing unit 302, 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 information of the module to be repaired includes: 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 upgrade version information includes: 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 repair unit 302 is specifically configured to:
replacing the current version software package corresponding to the module identifier to be repaired with the target version upgrading package corresponding to the module identifier to be repaired;
and updating the current version number corresponding to the identifier to be repaired to be the target version number corresponding to the identifier of the module to be repaired.
Optionally, the apparatus further comprises:
a judging module 70, configured to judge whether the module to be repaired is repaired to the target version;
the second processing module 80 is configured to quit the OTA environment if all the modules to be repaired are repaired to the target version; and if the modules to be repaired which fail to be repaired exist in all the modules to be repaired, continuously initializing the OTA environment, and repairing the modules to be repaired which fail to be repaired until all the modules to be repaired which fail to be repaired are repaired to the target version.
The OTA upgrading device provided by this embodiment may implement the embodiments of the method described above, and the implementation principle and the technical effect are similar, which are not described herein again.
Fig. 4 is a schematic structural diagram of a computer device according to an embodiment of the present invention. As shown in fig. 4, a schematic structural diagram of a computer system 400 suitable for implementing the vehicle-mounted device 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 that can perform various appropriate actions and processes in accordance with 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 the RAM403, various programs and data necessary for the operation of the system 400 are also stored. The CPU401, ROM402, and RAM403 are connected to each other via 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 section 407 including a display device such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage section 408 including a hard disk and 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. A driver 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 mounted on the drive 410 as necessary, so that a computer program read out therefrom is mounted into the storage section 408 as necessary.
In particular, the process described above with reference to fig. 2 may be implemented as a computer software program, according to an embodiment of the present disclosure. 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 through the communication section 409, and/or installed from the removable medium 411.
The flowchart 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 described in the embodiments of the present application may be implemented by software or hardware. The described units or modules may also be provided in a processor, and may be described as: a processor includes a determination module, a first initialization module, and a repair module. The names of these units or modules do not form a limitation on the units or modules themselves in some cases, for example, the determining module may also be described as "determining a module to be repaired after a previous OTA upgrade fails, where the module to be repaired is the module to be upgraded after the upgrade fails".
As another aspect, the present application also provides a computer-readable medium, which may be contained in the electronic device described in the above embodiments; or may exist separately without being assembled into the electronic device. The computer readable medium carries one or more programs which, when executed by an electronic device, cause the electronic device to implement the OTA upgrade method as described in the embodiments above.
For example, the electronic device may implement the following as shown in fig. 1: step S101, after the previous OTA fails to be upgraded, determining a module to be repaired, wherein the module to be repaired is the module to be upgraded after the previous OTA fails to be upgraded; step S102, initializing OTA environment again; and step S103, when the OTA environment is initialized successfully, the module to be repaired is 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 the 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, according to embodiments of the present disclosure. Conversely, the features and functions of one module or unit described above may be further divided into embodiments by a plurality of modules or units.
Moreover, although the steps of the methods of the present disclosure are depicted in the drawings in a particular order, this does not require or imply that the steps must be performed in this particular order, or that all of the depicted steps must be performed, to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step execution, and/or one step broken down into multiple step executions, etc. Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein may be implemented by software, or by software in combination with necessary hardware.
To sum up, according to the OTA upgrading method, the OTA upgrading device, the vehicle-mounted terminal and the storage medium provided by the embodiment of the application, after the previous OTA upgrading fails, the module to be repaired is determined, the module to be repaired is the module to be upgraded after the OTA upgrading fails, the OTA environment is initialized again, and after the OTA environment is successfully initialized, the module to be repaired is repaired. This technical scheme can be after the vehicle OTA upgrading fails last time, through confirming the module of waiting to restore to the initialization OTA environment, thereby the influence of upgrading to the vehicle state last time has been avoided when making the module of waiting to restore the processing, compare with prior art, this method need not too much manpower and participates in, can directly carry out restoration processing to the module of waiting to restore at on-vehicle terminal, convenient operation is swift, can save the upgrade time, further improve OTA upgrade success rate, avoid the vehicle to take place dangerously in the use.
The foregoing is considered as illustrative only of the preferred embodiments of the invention and illustrative only of the principles of the technology employed. It will be understood by those skilled in the art that the scope of the present application is not limited to the specific combination of the above-mentioned features, but also encompasses the combination of the above-mentioned features and the features disclosed in the present application (but not limited to) having similar functions, without departing from the spirit of the present application.
Claims (10)
1. An OTA upgrade method, comprising:
determining a module to be repaired after the previous OTA fails to be upgraded, wherein the module to be repaired is the module to be upgraded which fails to be upgraded;
initializing the OTA environment again;
and when the OTA environment is initialized successfully, repairing the module to be repaired.
2. The OTA upgrading method of claim 1, wherein determining the module to be repaired comprises:
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 the module to be upgraded as a module to be repaired.
3. The OTA upgrade method of claim 1, wherein the previous OTA upgrade comprises:
detecting vehicle state information;
initializing an OTA environment when the vehicle state information satisfies OTA conditions, the OTA conditions including: the vehicle is in a static state and the electric quantity is sufficient;
and upgrading the module to be upgraded, and recording the information of the module to be repaired and the information of the upgraded version.
4. The OTA upgrading method according to claim 2, wherein the repairing the module to be repaired includes:
when the number of the modules to be repaired is multiple, acquiring the information of the modules to be repaired and the corresponding upgrade version information of each module to be repaired;
and restoring each module to be restored to a target version according to the information of each module to be restored and the corresponding upgrade version information.
5. The OTA upgrade method of claim 4, wherein the to-be-repaired module information comprises: 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 upgrade version information includes: 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;
restoring each module to be restored to a target version according to each module to be restored information and the corresponding upgrade version information, including:
replacing the current version software package corresponding to the module identifier to be repaired with the target version upgrading package corresponding to the module identifier to be repaired;
and updating the current version number corresponding to the identifier to be repaired to be the target version number corresponding to the identifier of the module to be repaired.
6. The OTA upgrade method according to any one of claims 1-5, wherein after repair processing of 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 modules to be repaired are repaired to the target version, quitting the OTA environment;
and if the modules to be repaired which fail to be repaired exist in all the modules to be repaired, continuously initializing the OTA environment, and repairing the modules to be repaired which fail to be repaired until all the modules to be repaired which fail to be repaired are repaired to the target version.
7. An OTA upgrade apparatus, characterized in that the apparatus comprises:
the determining module is used for determining a module to be repaired after the previous OTA fails to be upgraded, and the module to be repaired is the module to be upgraded after the OTA fails to be upgraded;
the first initialization module is used for initializing the OTA environment again;
and the repairing module is used for repairing the module to be repaired after the OTA environment is successfully initialized.
8. The OTA upgrading device according to claim 1, wherein the determining module comprises:
the first obtaining unit is used for obtaining the current version number and the target version number of the module to be upgraded;
the judging unit is used for judging 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.
9. An in-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-6 when executing the program.
10. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the method according to any one of claims 1-6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911376772.4A CN113050960A (en) | 2019-12-27 | 2019-12-27 | OTA (over the air) upgrading method and device, vehicle-mounted terminal and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911376772.4A CN113050960A (en) | 2019-12-27 | 2019-12-27 | OTA (over the air) upgrading method and device, vehicle-mounted terminal and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113050960A true CN113050960A (en) | 2021-06-29 |
Family
ID=76506326
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911376772.4A Pending CN113050960A (en) | 2019-12-27 | 2019-12-27 | OTA (over the air) upgrading method and device, vehicle-mounted terminal and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113050960A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114827106A (en) * | 2022-03-18 | 2022-07-29 | 中科晶上（苏州）信息技术有限公司 | Electric vehicle remote upgrading method |
| CN115118577A (en) * | 2022-06-24 | 2022-09-27 | 重庆长安汽车股份有限公司 | Method and device for determining remote upgrade abnormal reason, electronic equipment and storage medium |
Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104375844A (en) * | 2013-08-12 | 2015-02-25 | 中兴通讯股份有限公司 | Firmware upgrading method and device |
| CN105357231A (en) * | 2014-07-24 | 2016-02-24 | 中兴通讯股份有限公司 | Difference upgrade method, server and terminal |
| CN105589719A (en) * | 2015-12-17 | 2016-05-18 | 广州汽车集团股份有限公司 | System for remotely upgrading full vehicle-mounted controller softwares and upgrading method thereof |
| CN106339248A (en) * | 2016-10-09 | 2017-01-18 | 大道网络（上海）股份有限公司 | Remote software upgrading method and remote software upgrading system |
| WO2017067448A1 (en) * | 2015-10-22 | 2017-04-27 | 深圳市中兴微电子技术有限公司 | Firmware-over-the-air upgrade method, system and computer storage medium |
| CN107748667A (en) * | 2017-10-23 | 2018-03-02 | 郑州云海信息技术有限公司 | A kind of method for lifting server power supply online updating firmware reliability |
| 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 |
| CN109491681A (en) * | 2018-10-19 | 2019-03-19 | 北京经纬恒润科技有限公司 | The upgrade method and device of MCU in a kind of automobile |
| CN110162323A (en) * | 2019-05-28 | 2019-08-23 | 广州小鹏汽车科技有限公司 | Onboard system upgrade method, device, storage medium and vehicle |
| CN110347412A (en) * | 2019-06-27 | 2019-10-18 | 中国第一汽车股份有限公司 | Electronic control unit firmware upgrade management method, device, equipment and storage medium |
-
2019
- 2019-12-27 CN CN201911376772.4A patent/CN113050960A/en active Pending
Patent Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104375844A (en) * | 2013-08-12 | 2015-02-25 | 中兴通讯股份有限公司 | Firmware upgrading method and device |
| CN105357231A (en) * | 2014-07-24 | 2016-02-24 | 中兴通讯股份有限公司 | Difference upgrade method, server and terminal |
| WO2017067448A1 (en) * | 2015-10-22 | 2017-04-27 | 深圳市中兴微电子技术有限公司 | Firmware-over-the-air upgrade method, system and computer storage medium |
| CN105589719A (en) * | 2015-12-17 | 2016-05-18 | 广州汽车集团股份有限公司 | System for remotely upgrading full vehicle-mounted controller softwares and upgrading method thereof |
| 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 |
| CN107748667A (en) * | 2017-10-23 | 2018-03-02 | 郑州云海信息技术有限公司 | A kind of method for lifting server power supply online updating firmware reliability |
| CN108958774A (en) * | 2018-07-13 | 2018-12-07 | 深圳市道通智能航空技术有限公司 | Module updating method and module to be upgraded in UAV system |
| CN109491681A (en) * | 2018-10-19 | 2019-03-19 | 北京经纬恒润科技有限公司 | The upgrade method and device of MCU in a kind of automobile |
| CN110162323A (en) * | 2019-05-28 | 2019-08-23 | 广州小鹏汽车科技有限公司 | Onboard system upgrade method, device, storage medium and vehicle |
| CN110347412A (en) * | 2019-06-27 | 2019-10-18 | 中国第一汽车股份有限公司 | Electronic control unit firmware upgrade management method, device, equipment and storage medium |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114827106A (en) * | 2022-03-18 | 2022-07-29 | 中科晶上（苏州）信息技术有限公司 | Electric vehicle remote upgrading method |
| CN115118577A (en) * | 2022-06-24 | 2022-09-27 | 重庆长安汽车股份有限公司 | Method and device for determining remote upgrade abnormal reason, electronic equipment and storage medium |
| CN115118577B (en) * | 2022-06-24 | 2023-08-18 | 重庆长安汽车股份有限公司 | Remote upgrade abnormality cause determination method, device, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10782955B2 (en) | Pre-shutdown swap verification | |
| US20170242678A1 (en) | Method and apparatus for vehicle software update installation | |
| CN111399884A (en) | Vehicle component upgrading method and device and electronic equipment | |
| US11204757B2 (en) | Server, software update system, and software update apparatus | |
| CN112104736B (en) | OTA-based multi-ECU upgrading method | |
| CN109491671B (en) | Diagnostic software downloading method and device, terminal equipment and storage medium | |
| US9569404B2 (en) | In-vehicle controller and non-transitory tangible computer readable medium | |
| CN112134940A (en) | OTA upgrade task life cycle strategy management method | |
| CN112134961B (en) | Client use control method, client and computer storage medium | |
| CN113050960A (en) | OTA (over the air) upgrading method and device, vehicle-mounted terminal and storage medium | |
| KR102239904B1 (en) | Ota master device, system and method for managing update of vehicle ecus | |
| 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 | |
| CN112015489A (en) | Management method, device, storage medium and system for vehicle-mounted software | |
| CN115437915A (en) | Vehicle-based version testing method and device and electronic equipment | |
| CN103067499A (en) | Data processing method and processing device | |
| CN113268257A (en) | Vehicle-mounted application upgrading system, method and computer storage medium | |
| CN116257270A (en) | Vehicle, upgrading method and device of vehicle | |
| CN116048587A (en) | Remote automatic upgrading method, device, server, equipment and medium for vehicle | |
| CN115934130A (en) | ECU (electronic control Unit) upgrading method, device, equipment and medium | |
| CN106445601A (en) | Device and method for plugin upgrading | |
| CN116339784A (en) | Emergency method and device for failure in upgrading vehicle application, vehicle, equipment and medium | |
| CN116126368A (en) | Whole-vehicle OTA upgrading method and device, electronic equipment and vehicle | |
| CN114579161A (en) | Application program updating method and ECU | |
| CN114647424A (en) | ECU application program updating method, device, system, storage medium and electronic equipment |
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 |