CN113419903A - Fault repairing method and system in OTA (over the air) upgrading process - Google Patents
Fault repairing method and system in OTA (over the air) upgrading process Download PDFInfo
- Publication number
- CN113419903A CN113419903A CN202110734845.3A CN202110734845A CN113419903A CN 113419903 A CN113419903 A CN 113419903A CN 202110734845 A CN202110734845 A CN 202110734845A CN 113419903 A CN113419903 A CN 113419903A
- Authority
- CN
- China
- Prior art keywords
- vehicle
- fault
- upgrading
- cloud server
- ota
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1415—Saving, restoring, recovering or retrying at system level
- G06F11/1433—Saving, restoring, recovering or retrying at system level during software upgrading
-
- 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
Abstract
The invention discloses a fault repairing method and a fault repairing system in an OTA (over the air) upgrading process, which belong to the technical field of automobile electronics, and comprise a cloud server, a vehicle-end processor, a vehicle-end cache, a software package in the cache, an extensible markup language file and a user; the cloud server sends OTA upgrading tasks and files to the vehicle-end processor, and the vehicle-end processor returns the task running state to the cloud server; the vehicle-end processor is responsible for analyzing the extensible markup language file and the software package; and the vehicle-end processor operates and informs the user whether the upgrading is successful. The method utilizes the cache space in the vehicle to store the upgrade file successfully upgraded last time, and when the OTA upgrade process encounters a fault and cannot be continuously carried out, the upgrade package in the cache process can be analyzed, so that the purpose of processing the fault is achieved.
Description
Technical Field
The invention belongs to the technical field of automotive electronics, and particularly relates to a fault repairing method and system in an OTA (over the air) upgrading process.
Background
The advent of OTA remote upgrade technology has had a profound impact on the automotive industry, making point-of-sale (pos) a host factory from the original 4S shop. However, because the OTA technology is not developed for a long time, the technology is not developed yet, some faults may exist in each upgrading process, and if upgrading fails due to the faults, user experience may be reduced, vehicle using risks may be increased for users, and troubles may be brought to a host factory. Therefore, if faults possibly occur in the upgrading process are processed, the problems to be solved at present are solved.
Disclosure of Invention
The invention provides a fault repairing method and a fault repairing system in an OTA (over the air) upgrading process to solve the problems. The method utilizes the cache space in the vehicle to store the upgrade file successfully upgraded last time, and when the OTA upgrade process encounters a fault and cannot be continuously carried out, the upgrade package in the cache process can be analyzed, so that the purpose of processing the fault is achieved.
The invention is realized by the following technical scheme:
a fault repairing system in an OTA (over the air) upgrading process comprises a cloud server, a vehicle-end processor, a vehicle-end cache, a software package in the cache, an extensible markup language file and a user; the cloud server sends OTA upgrading tasks and files to the vehicle-end processor, and the vehicle-end processor returns the task running state to the cloud server; the vehicle-end processor is responsible for analyzing the extensible markup language file and the software package; and the vehicle-end processor operates and informs the user whether the upgrading is successful.
Preferably, the vehicle-side cache specifically refers to a storage space reserved by the vehicle side to store the upgrade package successfully upgraded last time; the software package in the cache specifically refers to an upgrade package which is successfully upgraded last time; the xml file is specifically an index file of the flash file, and the index file includes a flash start position and a flash field length.
A fault repairing method in an OTA upgrading process specifically comprises the following steps:
the method comprises the following steps: when a fault is encountered in the upgrading process, the process is started, and information for executing the repairing operation is sent to the cloud server;
step two: after the fault repairing information is sent to the cloud server, the fault repairing information is stored in a cache in the vehicle;
step three: after searching the software package which is successfully upgraded at the last time, the processor analyzes the extensible markup language file;
step four: after the extensible markup language file is analyzed, continuously analyzing the upgrade file in the software package;
step five: if the upgrade file in the software package is successfully analyzed, the upgrade file is used for writing the controller upgraded at the vehicle end;
step six: and after the flash is successful, sending information of successful fault repair to the cloud end and informing a user of successful upgrade, and finally finishing the process.
Preferably, in the step one, if the information for performing the repair operation fails to be sent, the information is repeatedly sent three times, and if the number of times reaches the upper limit, the user is notified that the upgrade fails and the information of the failure repair failure is returned to the cloud server, and the process ends.
Preferably, if the search fails in the second step, the failure repair failure information is returned to the cloud server and the user is notified that the upgrade fails, and the process ends.
Preferably, if the processing fails in the third step, the user is notified that the upgrade fails and a failure repair message is returned to the cloud server, and the process ends.
Preferably, if the resolution fails in the fourth step, the failure repair failure information is returned to the cloud server and the user is notified of the upgrade failure.
Preferably, if the flash fails in the step five, the information of failure repair failure is returned to the cloud server and the user is notified of upgrade failure.
Compared with the prior art, the invention has the following advantages:
1) a fault repairing mechanism is added in the OTA upgrading process, so that the fault tolerance and reliability of the upgrading process are improved;
2) by feeding back the information of the server and the user, the host factory can master the specific process of upgrading in time and optimize the user experience;
3) the universality is stronger, the risk of upgrading failure exists in the OTA upgrading failure process, and more vehicle types carrying OTA functions can be used in the method.
Drawings
In order to more clearly illustrate the detailed description of the invention or the technical solutions in the prior art, the drawings that are needed in the detailed description of the invention or the prior art will be briefly described below. Throughout the drawings, like elements or portions are generally identified by like reference numerals. In the drawings, elements or portions are not necessarily drawn to scale.
FIG. 1 is a system block diagram of a fault remediation system during an OTA upgrade process of the present invention;
fig. 2 is a flow diagram of a fault recovery method in an OTA upgrade process according to the present invention.
Detailed Description
For clearly and completely describing the technical scheme and the specific working process thereof, the specific implementation mode of the invention is as follows by combining the attached drawings of the specification:
in the present invention, unless otherwise expressly stated or limited, the terms "mounted," "connected," "secured," and the like are to be construed broadly and can, for example, be fixedly connected, detachably connected, or integrally formed; can be mechanically or electrically connected; they may be directly connected or indirectly connected through intervening media, or they may be connected internally or in any other suitable relationship, unless expressly stated otherwise. The specific meanings of the above terms in the present invention can be understood by those skilled in the art according to specific situations.
In the present invention, unless otherwise expressly stated or limited, the first feature "on" or "under" the second feature may be directly contacting the first and second features or indirectly contacting the first and second features through an intermediate. Also, a first feature "on," "over," and "above" a second feature may be directly or diagonally above the second feature, or may simply indicate that the first feature is at a higher level than the second feature. A first feature being "under," "below," and "beneath" a second feature may be directly under or obliquely under the first feature, or may simply mean that the first feature is at a lesser elevation than the second feature.
In the description herein, references to the description of the term "one embodiment," "some embodiments," "an example," "a specific example," or "some examples," etc., mean that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the invention. In this specification, the schematic representations of the terms used above are not necessarily intended to refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, various embodiments or examples and features of different embodiments or examples described in this specification can be combined and combined by one skilled in the art without contradiction.
Example 1
A fault repairing system in an OTA (over the air) upgrading process comprises a cloud server, a vehicle-end processor, a vehicle-end cache, a software package in the cache, an extensible markup language file and a user; the cloud server sends OTA upgrading tasks and files to the vehicle-end processor, and the vehicle-end processor returns the task running state to the cloud server; the vehicle-end processor is responsible for analyzing the extensible markup language file and the software package; and the vehicle-end processor operates and informs the user whether the upgrading is successful.
The vehicle end cache specifically refers to a storage space reserved by the vehicle end to store an upgrade patch successfully upgraded last time; the software package in the cache specifically refers to an upgrade package which is successfully upgraded last time; the xml file is specifically an index file of the flash file, and the index file includes a flash start position and a flash field length.
As shown in fig. 2, a method for repairing a fault in an OTA upgrade process specifically includes the following steps:
the method comprises the following steps: when a fault is encountered in the upgrading process, the process is started, and information for executing the repairing operation is sent to the cloud server;
step two: after the fault repairing information is sent to the cloud server, the fault repairing information is stored in a cache in the vehicle;
step three: after searching the software package which is successfully upgraded at the last time, the processor analyzes the extensible markup language file;
step four: after the extensible markup language file is analyzed, continuously analyzing the upgrade file in the software package;
step five: if the upgrade file in the software package is successfully analyzed, the upgrade file is used for writing the controller upgraded at the vehicle end;
step six: and after the flash is successful, sending information of successful fault repair to the cloud end and informing a user of successful upgrade, and finally finishing the process.
In the first step, if the information for executing the repair operation fails to be sent, the information is repeatedly sent for three times, if the times reach the upper limit, the user is informed of the upgrade failure, the information of the failure repair failure is returned to the cloud server, and the process is ended.
And if the search fails, returning failure repair information to the cloud server and informing the user of the upgrade failure, and ending the process.
And if the processing fails in the third step, notifying the user of the failure of upgrading and returning a failure repairing message to the cloud server, and ending the process.
And in the fourth step, if the analysis fails, returning failure repair information to the cloud server and informing the user of the failure of upgrading.
And fifthly, if the flash fails, returning failure repair failure information to the cloud server and informing the user of upgrade failure.
The working principle of the fault repairing system in the OTA upgrading process is as follows:
if an error occurs in the upgrading of the door module, the failover mechanism is enabled at this time. Firstly, a message is sent to a cloud server to inform that OTA upgrading is wrong, and fault repairing is needed. And then, the user goes to a corresponding folder in the vehicle to find the backup file successfully upgraded last time, reads the stored flash file and the configuration file in the format of the extensible language file, reads the position of the flash field and the size of the flash field in the configuration file, and writes the backup file successfully flashed last time into the door module so as to ensure the normal use of the function, inform the user of successful upgrade and prevent the user from having anxiety. The fault repairing steps in the OTA upgrading process are illustrated and completed.
The preferred embodiments of the present invention have been described in detail with reference to the accompanying drawings, however, the present invention is not limited to the specific details of the above embodiments, and various simple modifications can be made to the technical solution of the present invention within the technical idea of the present invention, and these simple modifications are within the protective scope of the present invention.
It should be noted that the various technical features described in the above embodiments can be combined in any suitable manner without contradiction, and the invention is not described in any way for the possible combinations in order to avoid unnecessary repetition.
In addition, any combination of the various embodiments of the present invention is also possible, and the same should be considered as the disclosure of the present invention as long as it does not depart from the spirit of the present invention.
Claims (8)
1. A fault repairing system in an OTA (over the air) upgrading process is characterized by comprising a cloud server, a vehicle-end processor, a vehicle-end cache, a software package in the cache, an extensible markup language file and a user; the cloud server sends OTA upgrading tasks and files to the vehicle-end processor, and the vehicle-end processor returns the task running state to the cloud server; the vehicle-end processor is responsible for analyzing the extensible markup language file and the software package; and the vehicle-end processor operates and informs the user whether the upgrading is successful.
2. The system for repairing the fault during the OTA upgrade process according to claim 1, wherein the vehicle-side cache specifically refers to a storage space reserved by the vehicle side to store the upgrade package successfully upgraded last time; the software package in the cache specifically refers to an upgrade package which is successfully upgraded last time; the xml file is specifically an index file of the flash file, and the index file includes a flash start position and a flash field length.
3. The method for repairing the fault in the OTA upgrading process according to claim 1, comprising the following steps:
the method comprises the following steps: when a fault is encountered in the upgrading process, the process is started, and information for executing the repairing operation is sent to the cloud server;
step two: after the fault repairing information is sent to the cloud server, the fault repairing information is stored in a cache in the vehicle;
step three: after searching the software package which is successfully upgraded at the last time, the processor analyzes the extensible markup language file;
step four: after the extensible markup language file is analyzed, continuously analyzing the upgrade file in the software package;
step five: if the upgrade file in the software package is successfully analyzed, the upgrade file is used for writing the controller upgraded at the vehicle end;
step six: and after the flash is successful, sending information of successful fault repair to the cloud end and informing a user of successful upgrade, and finally finishing the process.
4. The OTA upgrading method according to claim 1, wherein in the step one, if the sending of the information for performing the repair operation fails, the sending is repeated three times, and if the number of times has reached the upper limit, the user is notified that the upgrading failed and the information of the failure of the fault repair is returned to the cloud server, and the process is ended.
5. The OTA upgrading process fault recovery method of claim 1, wherein in the second step, if the search fails, the fault recovery failure information is returned to the cloud server and the user is notified of the upgrading failure, and the process is ended.
6. The OTA upgrading process fault recovery method of claim 1, wherein in step three, if the processing fails, the user is notified that the upgrading fails and a fault recovery failure message is returned to the cloud server, and the process ends.
7. The OTA upgrading process fault repair method of claim 1, wherein in step four, if the parsing fails, the fault repair failure information is returned to the cloud server and the user is notified of the upgrading failure.
8. The OTA upgrading process fault repair method of claim 1, wherein in step five, if the flash fails, the fault repair failure information is returned to the cloud server and the user is notified of the upgrading failure.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110734845.3A CN113419903A (en) | 2021-06-30 | 2021-06-30 | Fault repairing method and system in OTA (over the air) upgrading process |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110734845.3A CN113419903A (en) | 2021-06-30 | 2021-06-30 | Fault repairing method and system in OTA (over the air) upgrading process |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113419903A true CN113419903A (en) | 2021-09-21 |
Family
ID=77717929
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110734845.3A Pending CN113419903A (en) | 2021-06-30 | 2021-06-30 | Fault repairing method and system in OTA (over the air) upgrading process |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113419903A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114785688A (en) * | 2022-06-21 | 2022-07-22 | 深圳市华曦达科技股份有限公司 | Terminal equipment upgrading method and system |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8555273B1 (en) * | 2003-09-17 | 2013-10-08 | Palm. Inc. | Network for updating electronic devices |
| US20170090901A1 (en) * | 2015-09-30 | 2017-03-30 | Apple Inc. | Software Updating |
| CN109343885A (en) * | 2018-11-01 | 2019-02-15 | 百度在线网络技术（北京）有限公司 | Method for upgrading system and multi-system equipment |
| CN110597542A (en) * | 2019-09-17 | 2019-12-20 | Oppo（重庆）智能科技有限公司 | Automatic OTA (over the air) software upgrading method and device and electronic equipment |
| CN110716727A (en) * | 2019-09-02 | 2020-01-21 | 领翌技术(横琴)有限公司 | Software upgrading method and system |
| CN110825422A (en) * | 2019-11-05 | 2020-02-21 | 四川爱联科技有限公司 | System for managing MCU version of intelligent household equipment |
-
2021
- 2021-06-30 CN CN202110734845.3A patent/CN113419903A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8555273B1 (en) * | 2003-09-17 | 2013-10-08 | Palm. Inc. | Network for updating electronic devices |
| US20170090901A1 (en) * | 2015-09-30 | 2017-03-30 | Apple Inc. | Software Updating |
| CN109343885A (en) * | 2018-11-01 | 2019-02-15 | 百度在线网络技术（北京）有限公司 | Method for upgrading system and multi-system equipment |
| CN110716727A (en) * | 2019-09-02 | 2020-01-21 | 领翌技术(横琴)有限公司 | Software upgrading method and system |
| CN110597542A (en) * | 2019-09-17 | 2019-12-20 | Oppo（重庆）智能科技有限公司 | Automatic OTA (over the air) software upgrading method and device and electronic equipment |
| CN110825422A (en) * | 2019-11-05 | 2020-02-21 | 四川爱联科技有限公司 | System for managing MCU version of intelligent household equipment |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114785688A (en) * | 2022-06-21 | 2022-07-22 | 深圳市华曦达科技股份有限公司 | Terminal equipment upgrading method and system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US6658603B1 (en) | Method and apparatus for efficiently generating and implementing engine error codes and verifying the correctness of the implementation of the engine error codes | |
| CN110758483A (en) | Method, apparatus, device and medium for remote restart | |
| CN112328294A (en) | OTA (over the air) upgrading method and system for vehicle ECU (electronic control Unit) | |
| CN103019759A (en) | Vehicle upgrade system and method thereof | |
| CN105760200A (en) | Terminal device and system updating method thereof | |
| CN113419903A (en) | Fault repairing method and system in OTA (over the air) upgrading process | |
| CN112202920B (en) | Vehicle-mounted system upgrading method and device | |
| CN109343885B (en) | System upgrading method and multi-system equipment | |
| CN109032632A (en) | A kind of FOTA upgrade method, wireless communication terminal and storage medium | |
| CN102203779A (en) | Method for updating data and control apparatus thereof | |
| CN112650624B (en) | Cluster upgrading method, device, equipment and computer readable storage medium | |
| JP5223995B1 (en) | Print control apparatus, data management method and program | |
| CN108973542B (en) | Upgrading method and equipment for tire pressure detection system TPMS (tire pressure monitoring System) diagnosis tool | |
| CN113535095B (en) | Data storage method, device and equipment for double storage pools and storage medium | |
| CN102158462A (en) | Method for repairing remote diagnosis by using 2nd Generation (2G) or 3rd Generation (3G) module | |
| CN106708541A (en) | Version upgrading processing method and apparatus | |
| CN114866701A (en) | Offline configuration system and method for 540-degree panoramic image | |
| CN114880381A (en) | Vehicle abnormity processing method and device, electronic equipment and storage medium | |
| CN112051826B (en) | Automobile fault detection method and system | |
| CN116909609B (en) | Software upgrading method and device of vehicle-mounted intelligent equipment and vehicle-mounted intelligent equipment | |
| CN114979116B (en) | Vehicle-mounted software upgrading method, system, terminal equipment and storage medium | |
| CN102265666A (en) | Method and device for obtaining equipment replacement information of base station transceiver | |
| CN115658339B (en) | Method, system, device and storage medium for realizing idempotent of interface message | |
| CN116108110B (en) | Kafka message consumption compensation method, system and medium | |
| JP5223996B1 (en) | Print control apparatus, data management method and program |
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 |