WO2022267812A1

WO2022267812A1 - Software recovery method, electronic device, and storage medium

Info

Publication number: WO2022267812A1
Application number: PCT/CN2022/095332
Authority: WO
Inventors: 苏勇刚; 雒主纲
Original assignee: 中兴通讯股份有限公司
Priority date: 2021-06-23
Filing date: 2022-05-26
Publication date: 2022-12-29
Also published as: CN115509803A

Abstract

The embodiments of the present application relate to the field of embedded systems. Disclosed is a software recovery method, comprising: when software runs to a preset self-healing position point, acquiring and storing a target running variable of the software, wherein there is at least one self-healing position point; and if it is detected that the software runs abnormally, recovering the software according to the target running variable. Further disclosed in the embodiments of the present application are an electronic device and a storage medium.

Description

Software recovery method, electronic device and storage medium

cross reference

This application is based on the Chinese patent application with the application number "202110700003.6" and the filing date is June 23, 2021, and claims the priority of the Chinese patent application. The entire content of the Chinese patent application is hereby incorporated by reference. Application.

technical field

The embodiments of the present application relate to the field of embedded systems, and in particular to a software restoration method, electronic equipment and storage media.

Background technique

Embedded system (Embedded System) is a computer system embedded in a mechanical or electrical system with specific functions and real-time computing performance. At present, there are more and more embedded systems used in various industries. In the process of embedded applications, due to the different requirements for the adaptation of various embedded devices in embedded systems, for example, some are suitable for high temperature, and some are suitable for low temperature. , so that the embedded system has high requirements for comprehensive adaptation of hardware and software, and it is prone to software and hardware abnormalities. For example, the software has abnormal memory stampede due to irregular codes, and the hardware has abnormalities due to external temperature and voltage problems. Wait.

At present, when the above problems occur in the embedded system, there are mainly two ways to solve them: one is to restart the system after shutting down the system, and the other is to recover by initializing the configuration. However, the recovery cycle through shutdown and restart is long, and the real-time performance of recovery is poor, especially for embedded systems with strong real-time recovery requirements; and the recovery method through initialization configuration requires software. The re-running of the corresponding business has a great impact on the execution progress of the business.

Contents of the invention

The embodiment of the present application provides a software recovery method, including: when the software runs to a preset self-healing position point, acquire and save the target operating variable of the software, the self-healing position point is at least one; if detected If the software runs abnormally, restore the software according to the target running variable.

The embodiment of the present application also provides a software recovery method, including: when the software is running, detecting whether the software is running abnormally; if it is detected that the software is running abnormally, calling the self-healing module to restore the software, so The self-healing module obtains and saves the target operating variable of the software when the software runs to the preset self-healing position, and when called, restores the software according to the target operating variable, so There is at least one self-healing location point.

The embodiment of the present application also provides an electronic device, including: at least one processor; and a memory connected in communication with the at least one processor; wherein, the memory stores information that can be executed by the at least one processor. instructions, the instructions are executed by the at least one processor to enable the at least one processor to perform the above-mentioned software recovery method.

The embodiment of the present application also provides a computer-readable storage medium storing a computer program, and implementing the above-mentioned software recovery method when the computer program is executed by a processor.

Description of drawings

One or more embodiments are exemplified by pictures in the accompanying drawings, and these exemplifications are not intended to limit the embodiments.

FIG. 1 is a schematic diagram of the principle of a software recovery method provided in an embodiment of the present application;

Fig. 2 is a schematic flow chart of the software restoration method provided by the embodiment of the present application;

FIG. 3 is a schematic flow chart of the refinement steps of S102 in the software restoration method provided in the embodiment of the present application;

FIG. 4 is an example flow diagram of a software recovery method provided in an embodiment of the present application;

FIG. 5 is an example diagram of a recovery process in a software recovery method provided in an embodiment of the present application;

FIG. 6 is another schematic diagram of the principle of the software recovery method provided by the embodiment of the present application;

Fig. 7 is another schematic flowchart of the software restoration method provided by the embodiment of the present application;

FIG. 8 is a schematic structural diagram of an electronic device provided by an embodiment of the present application.

detailed description

In order to make the purpose, technical solutions and advantages of the embodiments of the present application clearer, the embodiments of the present application will be described in detail below with reference to the accompanying drawings. However, those of ordinary skill in the art can understand that in each embodiment of the application, many technical details are provided for readers to better understand the application. However, even without these technical details and various changes and modifications based on the following embodiments, the technical solutions claimed in this application can also be realized. The division of the following embodiments is for the convenience of description, and should not constitute any limitation to the specific implementation of the present application, and the embodiments can be combined and referred to each other on the premise of no contradiction.

In one embodiment, it relates to a software recovery method, by presetting the self-healing position point in the software, when the software runs to the self-healing position point, the target operating variable of the software is acquired and saved; when the abnormality of the software is detected The software is restored according to the target operating variables. Since the self-healing position point can be preset according to the different running progress of the software, the software can be recovered according to the target operating variable of the self-healing position point, so that the software can be recovered from the position nearer before the abnormal operation, thereby shortening the time for software recovery The required time is improved, the real-time performance of recovery is improved, and the impact on the business progress of the software is reduced at the same time.

The software recovery method of the embodiment of the present application can be applied to an embedded system, and the specific execution subject can be a certain module of the embedded system, such as a self-healing module as shown in Figure 1, wherein Figure 1 is provided by the embodiment of the present application Schematic diagram of the software recovery method. As shown in Figure 1, the self-healing module presets the self-healing position point in the software, and when it detects that the software is running abnormally (after the abnormality is triggered by the hardware device in Figure 1, the self-healing module obtains the abnormal information for detection), Perform business recovery on the software based on the self-healing location point. For the convenience of description, in the following specific examples, the self-healing module is used as the execution subject for illustration.

The specific flow of the software recovery method provided in the embodiment of the present application is shown in Figure 2, including the following steps:

S101: When the software runs to a preset self-healing position point, acquire and save the target running variable of the software, and there is at least one self-healing position point.

When presetting the self-healing position points of the software, the granularity can be set larger, for example, a self-healing position point is preset for a function of the software, so that the number of preset self-healing position points can be reduced and the storage The storage space required by the target operating variables of the software, but it will reduce the accuracy of software recovery, and the deviation from the execution progress of the software before business recovery is large; the granularity can also be set smaller, such as a function preset for the software A self-healing position point, which can improve the accuracy of software recovery and reduce the deviation from the execution progress of the software before business recovery, but it will increase the preset number of self-healing position points and increase the target operating variables of the saved software required storage space. The preset of the self-healing position point can be set according to factors such as the storage space of the embedded system itself, the complexity of the software itself, the recovery time requirement, and the recovery accuracy requirement, which are not limited in this embodiment of the present application.

If there are multiple self-healing position points, when obtaining and saving the target operating variable of the self-healing position point, obtain and save the increase of the target operating variable of the current self-healing position point relative to the target operating variable of the previous self-healing position point quantity. In particular, when the current self-healing position is the first self-healing position, the target operating variable of the current self-healing position is acquired and saved. Since the memory of an embedded system is generally limited, saving in incremental form can reduce the occupation of the storage space of the embedded system by the target running variable. Since saving in incremental form can reduce the storage space occupied by the embedded system, compared with the form of full saving, the granularity of self-healing position points can be set smaller, which improves the accuracy of software recovery and reduces the Deviations in the execution progress of the software before business recovery.

The target operating variable refers to the corresponding operating variable when the software is at the current self-healing position. The specific target operating variable can be set according to actual needs, as long as the software can resume operation according to the target operating variable. When the storage space of the embedded system is relatively sufficient, all the running variables of the software can be used as the target running variables. In a specific example, the target operating variable is a key variable that affects the secondary operation of the software, such as key information such as memory, PC pointer and register information, which can reduce the storage space of the embedded system for the saved target operating variable. It can also shorten the time required for software recovery and improve the efficiency of software recovery.

S102: If it is detected that the software is running abnormally, restore the software according to the target running variable.

Since the hardware device will have abnormal state information when the software is running abnormally, when detecting whether the software is running abnormally, it can be triggered by the hardware device in the embedded system, and then detected by the self-healing module. For example, when a hardware device interrupts an instruction, it triggers an exception, and the self-healing module captures the corresponding exception information. When an exception is triggered by a hardware device, the hardware device is required to support reporting the status information of the hardware exception to the self-healing module. The specific detection method for abnormal software operation can be set according to the actual situation. For example, it can also be implemented by other monitoring software or scripts. There is no limitation here, as long as information about abnormal software operation can be detected.

In a specific example, S102 may include: if the abnormality of the software is detected, analyzing the type of the abnormality; if the type of the abnormality is self-healing, restoring the software according to the target operating variable, otherwise restarting the software. When the type of abnormal operation is self-healing, it indicates that self-healing can be achieved by restoring the target operating variable at the self-healing position point, then restore the software according to the target operating variable; if the type of abnormal operation is non-self-healing , it indicates that the self-healing cannot be achieved by restoring the target operating variable of the self-healing position point, and the software is restarted directly to recover, avoiding an invalid recovery process. As for whether the type of abnormal operation is self-healing or non-self-healing, it can be pre-configured in the self-healing module.

In a specific example, after recovering the software according to the target operating variables, it also includes: obtaining and saving the abnormal information and self-healing time of the software recovery this time, so that statistics and evaluation of the effect of the software recovery can be conveniently performed, and Further analyze and improve the setting of self-healing position points, so as to further improve the effect of software recovery.

When there are multiple self-healing position points and the target operating variable is saved in incremental form, as shown in Figure 3, restoring the software according to the target operating variable may include the following steps:

S1021: Restore the target operating variables of the self-healing position points one by one according to the order in which the self-healing position points are saved.

Since the self-healing position points are saved in increments, if the restoration of the previous self-healing position point fails, the restoration of the following self-healing position points will fail, and the self-healing position points will be restored one by one according to the order in which the self-healing position points are saved , the software can be restored to the last self-healing point where the restoration was successful, and the self-healing of the software can be realized.

Before restoring the target operating variable at the self-healing point, optionally, an integrity check of the target operating variable may be performed. Specifically, after S101, that is, after acquiring and saving the target operating variables of the software, calculate and save the first integrity characteristic value of the target operating variables; then, before restoring the target operating variables of each self-healing position point, Calculate the second integrity eigenvalue of the target operating variable corresponding to the self-healing position point that needs to be restored currently. If the second integrity eigenvalue is equal to the first integrity eigenvalue, it indicates that the backup of the target operating variable is complete, then restore The target operating variable of the current self-healing position point, otherwise it is judged that the restoration of the current self-healing position point fails. Wherein, the first integrity characteristic value and the second integrity characteristic value are used to verify the integrity of the backup of the target operating variable, and the specific selected value can be selected according to actual needs, for example, it can be CRC (Cyclic Redundancy Check, Cyclic redundancy check) value or MD5 (MD5Message-Digest Algorithm, MD5 message digest algorithm) value, etc., there is no limitation here. Since the backup of the target operating variable may be incomplete due to memory stampede, etc., before restoring the target operating variable of the self-healing point, the integrity check of the target operating variable can be performed to ensure that the restoration of the self-healing point is successful; When the backup of the target operating variable is incomplete, it is determined that the restoration of the current self-healing position fails, and the incomplete self-healing position point can be automatically identified as an invalid self-healing position point.

S1022: If the current self-healing position point is successfully restored, continue to restore the next self-healing position point.

S1023: If the restoration of the current self-healing position point fails, determine whether the current self-healing position point is the first self-healing position point.

S1024: If the current self-healing position point is the first self-healing position point, restart the software; otherwise, point the PC pointer to the previous self-healing position point that was restored successfully, and complete the recovery of the software.

When the self-healing position points store target operating variables in incremental form, if the current self-healing position point is the first self-healing position point, it means that all self-healing position points are invalid self-healing position points, and cannot To achieve the effect of restoring the software, restart the software directly. If the current self-healing position is not the first self-healing position point, it indicates that at least one self-healing position point is a valid self-healing position point, and the PC pointer points to the previous self-healing position point (also the last restored position point) successful self-healing point) from which to resume software operation.

In particular, if all the self-healing points are restored successfully, the PC pointer is pointed to the last self-healing point restored successfully, and the restoration of the software is completed.

In the above example shown in Figure 3, the self-healing position points save the target operating variables in the form of increments. If the target operating variables are saved in the form of full quantities, the software can be restored from the last self-healing position point. If the last If one self-healing point is successfully restored, it is not necessary to restore other self-healing points, and the software can be restored directly; One self-healing location point restored successfully; if all self-healing location points fail to restore, restart the software.

It is understandable that the software may also be composed of several modules with little correlation. Therefore, when presetting the self-healing position points, it is necessary to set different self-healing position points for these modules separately. At this time, the The self-healing points are independent of each other; when the software is restored according to the target operating variables, the self-healing points of all modules must be successfully restored to realize the self-healing of the software. Of course, for the same module in the software, multiple self-healing points can still be set, such as the same function or function at different time points, when the target running variable of the self-healing point in the module is saved, it can still be set as Save in incremental form to reduce storage space usage.

In order to better illustrate the software recovery method in the embodiment of the present application, a specific example is used below for illustration. Please refer to FIG. 4 , which is an example diagram of a software restoration method according to an embodiment of the present application. The specific process is as follows:

1. Start the software;

2. The software searches for the self-healing location according to the logic of the business. When the first self-healing location is reached, the self-healing module obtains key information that affects the secondary operation of the business, such as the memory of the software, PC pointers, and register information, as the target operation variable and save, and calculate the CRC value of the saved target running variable to verify the integrity of the target running variable backup;

3. After saving the first self-healing position point, the software continues to run;

4. According to the operating mechanism of the software, continue to set the next self-healing position point of the software, and store the target operating variable of the next self-healing position point, here can be repeated according to actual needs, and store the target operating variables of multiple self-healing position points ;

5. The software continues to run;

6. The software runs abnormally;

7. Determine whether recovery can be performed. If recovery can be performed, enter the recovery process, and then return to 5 after recovery; if recovery cannot be performed, enter 8;

8. Restart the software;

9. End the process.

Wherein, the process example specifically included in the recovery process may be shown in Figure 5, specifically including the following steps:

1. The recovery process starts;

2. The self-healing module first judges whether the current number of self-healing exceeds the threshold (this value can be built-in or issued by the network management); if it exceeds the threshold, it indicates that the number of self-healing is too large, and there may be a large software failure, which needs to be restarted software, enter 8; if the threshold is not exceeded, enter 3;

3. The self-healing module obtains the abnormal information of software operation (here is the abnormal information reported by the hardware device), analyzes the abnormal type, and saves the abnormal information;

4. The self-healing module judges whether self-healing is currently possible according to the abnormal type, and if so, enter 5, otherwise enter 9;

5. The self-healing module clears the abnormal state bit, abnormal interrupt, abnormal register and other information of the hardware device according to the analyzed abnormal type, so that the hardware device can normally trigger the abnormal state when it recognizes the abnormal state next time;

6. The first self-healing point is restored;

7. Restoring other self-healing points; among them, 6 and 7 take three self-healing points A, B and C as an example, A is the first self-healing point, restore A self-healing point first, and set A Recalculate the CRC value from the backup data of the target operating variable at the self-healing position point. If the current CRC value is consistent with the previously saved CRC value, restore the target operating variable saved at the self-healing position point and record this time as valid Self-healing, and continue to restore the self-healing point of B; if the restoration of the self-healing point of A fails, go to 9; when the restoration of the self-healing point of A is successful, continue to restore the self-healing point of B, and recalculate the self-healing position of B first The CRC value of the backup data of the target operating variable of the point, if the currently calculated CRC value is consistent with the previously saved CRC value, restore the target operating variable saved at the B self-healing position point, and record this time as an effective self-healing, Continue to restore the self-healing point C; if the restoration of the self-healing point B fails, go to 8; when the restoration of the self-healing point B succeeds, continue to restore the self-healing point C, first recalculate the target operation of the self-healing point C The CRC value of the backup data of the variable, if the currently calculated CRC value is consistent with the previously saved CRC value, restore the target running variable saved at the C self-healing position point, and record that this time is effective self-healing, and enter 7; if C self-healing point restore fails, then enter 8;

8. Save the cause of the abnormality triggered by this software recovery (running dead position, abnormal cause), and the self-healing position point of this recovery, and record the self-healing times and self-healing time of this self-healing position point, so as to pass The statistical data is used for granular analysis of the self-healing location point; finally, the PC is pointed to the self-healing location point of the last effective recovery record, and the business operation of the software is continued;

9. Save the abnormal information and abnormal location, and record the number of times of self-healing and the reason for self-healing;

10. Trigger restart operation;

11. The software starts running.

In the software recovery method provided in the embodiment of the present application, by presetting the self-healing position point in the software, when the software runs to the self-healing position point, the target operating variable of the software is obtained and saved; Variables are restored by the software. Since the self-healing position point can be preset according to the different running progress of the software, the software can be recovered according to the target operating variable of the self-healing position point, so that the software can be recovered from the position nearer before the abnormal operation, thereby shortening the time for software recovery It improves the real-time performance of embedded system software recovery, and at the same time reduces the impact on the execution progress of embedded system software business.

In one embodiment, it relates to a software recovery method. When the software is running, it is detected whether the software is running abnormally; When the preset self-healing position point is reached, the target operating variable of the software is obtained and saved, and when called, the software is restored according to the target operating variable, and there is at least one self-healing position point. By calling the self-healing module actively by the software itself, the software can achieve the effect of active self-healing.

It should be noted that the execution subject of the software restoration method provided by the embodiment of the present application is the software of the embedded system itself, such as the software shown in Figure 6, where Figure 6 is a principle example of the software restoration method provided by the embodiment of the present application picture. As shown in Figure 6, the software detects whether an abnormality occurs at its own software level during operation, and actively calls the self-healing module to restore the software when an abnormality occurs. Since it is the software itself that detects whether the software level is abnormal, it is necessary for the software to support the abnormality detection function at the software level.

The specific flow of the software recovery method provided in the embodiment of the present application is shown in Figure 7, including the following steps:

S201: When the software is running, detect whether the software runs abnormally.

S202: If the abnormal operation of the software is detected, the self-healing module is called to recover the software. When the software runs to the preset self-healing position, the self-healing module acquires and saves the target running variable of the software, and when called, The software is restored according to the target operating variables, and there is at least one self-healing position point.

The software recovery method provided by the embodiment of the present application detects whether the operation is abnormal through the software itself, and actively invokes the self-healing module to realize the self-healing of the software when the operation is abnormal, which can achieve the effect of active self-healing of the software and improve the recovery time of the embedded system recovery software. Diversity in concrete implementations.

It is not difficult to find that this embodiment is an embodiment applied to the software side corresponding to the foregoing method embodiments, and this embodiment can be implemented in cooperation with the foregoing method embodiments. The relevant technical details mentioned in the foregoing method embodiments are still valid in this embodiment, and will not be repeated here in order to reduce repetition. Correspondingly, the relevant technical details mentioned in this embodiment may also be applied to the foregoing method embodiments.

In addition, those skilled in the art can understand that the division of the steps of the various methods above is only for the sake of clarity of description, and can be combined into one step or split into multiple steps during implementation, as long as the same logical relationship is included , are all within the protection scope of this patent; adding insignificant modifications or introducing insignificant designs to the algorithm or process, but not changing the core design of its algorithm and process are all within the protection scope of this patent.

In one embodiment, it relates to an electronic device, as shown in FIG. 8 , including: at least one processor 301; and a memory 302 communicatively connected to at least one processor 301; Instructions executed by the processor 301, the instructions are executed by at least one processor 301, so that the at least one processor 301 can execute the above software restoration method.

Wherein, the memory and the processor are connected by a bus, and the bus may include any number of interconnected buses and bridges, and the bus connects one or more processors and various circuits of the memory together. The bus may also connect together various other circuits such as peripherals, voltage regulators, and power management circuits, all of which are well known in the art and therefore will not be further described herein. The bus interface provides an interface between the bus and the transceivers. A transceiver may be a single element or multiple elements, such as multiple receivers and transmitters, providing means for communicating with various other devices over a transmission medium. The data processed by the processor is transmitted on the wireless medium through the antenna, further, the antenna also receives the data and transmits the data to the processor.

The processor is responsible for managing the bus and general processing, and can also provide various functions, including timing, peripheral interface, voltage regulation, power management, and other control functions. Instead, memory may be used to store data that the processor uses when performing operations.

In one embodiment, it relates to a computer readable storage medium storing a computer program. The above method embodiments are implemented when the computer program is executed by the processor.

That is, those skilled in the art can understand that all or part of the steps in the method of the above-mentioned embodiments can be completed by instructing related hardware through a program, the program is stored in a storage medium, and includes several instructions to make a device ( It may be a single-chip microcomputer, a chip, etc.) or a processor (processor) to execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), magnetic disk or optical disc, etc., which can store program codes. .

Those of ordinary skill in the art can understand that the above-mentioned embodiments are specific embodiments for realizing the present application, and in practical applications, various changes can be made to it in form and details without departing from the spirit and spirit of the present application. scope.

Claims

A software recovery method comprising:

When the software runs to a preset self-healing position point, acquire and save the target operating variable of the software, and the self-healing position point is at least one;

If it is detected that the software is running abnormally, the software is restored according to the target running variable.
The software recovery method according to claim 1, wherein the target running variable is a key variable that affects the secondary running of the software, and the key variable includes the following information: memory, PC pointer and register information.
The software recovery method according to claim 1 or 2, wherein there are multiple self-healing locations, and the acquiring and saving the target operating variables of the software includes:

When acquiring and saving the target operating variable of the self-healing position point, the increment of the target operating variable of the current self-healing position point relative to the target operating variable of the previous self-healing position point is acquired and saved.
The software restoration method according to claim 3, wherein said restoration of said software according to said target operating variable comprises:

Restore the target operating variables of the self-healing position points one by one according to the order in which the self-healing position points are saved;

If the current self-healing position is successfully restored, continue to restore the next self-healing position;

If the restoration of the current self-healing position point fails, it is judged whether the current self-healing position point is the first self-healing position point;

If the current self-healing position point is the first self-healing position point, then restart the software, otherwise point the PC pointer to the previous self-healing position point that was successfully restored, and complete the recovery of the software.
The software recovery method according to claim 4, wherein, after said acquiring and saving the target operating variables of said software, further comprising:

calculating and saving the first integrity characteristic value of the target operating variable;

The step of restoring the target operating variables of the self-healing position points one by one according to the order in which the self-healing position points are saved includes:

According to the order of saving the self-healing position points, calculate the second integrity characteristic value of each self-healing position point corresponding to the target operating variable one by one;

If the second integrity characteristic value is equal to the first integrity characteristic value, the target operating variable of the current self-healing position is restored, otherwise it is determined that the restoration of the current self-healing position fails.
The software restoration method according to any one of claims 1 to 5, wherein, if it is detected that the software is running abnormally, restoring the software according to the target operation variable includes:

If the abnormal operation of the software is detected, the type of abnormal operation is analyzed;

If the type is a self-healing type, restore the software according to the target operating variable, otherwise restart the software.
The software restoration method according to any one of claims 1 to 6, wherein, after restoring the software according to the target operating variable, further comprising:

Obtain and save the abnormal information and self-healing time of the software recovery this time.
A software recovery method comprising:

When the software is running, detect whether the software is running abnormally;

If it is detected that the software is running abnormally, the self-healing module is called to restore the software, and the self-healing module obtains and saves the target running of the software when the software runs to the preset self-healing position variable, and when called, restore the software according to the target running variable, and the self-healing position is at least one.
An electronic device comprising:

at least one processor; and,

a memory communicatively coupled to the at least one processor; wherein,

The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor, so that the at least one processor can perform the operation described in any one of claims 1 to 7. The software recovery method or the software recovery method as claimed in claim 8.
A computer-readable storage medium storing a computer program, which implements the software recovery method according to any one of claims 1 to 7 or the software recovery method according to claim 8 when the computer program is executed by a processor.