CN103902399A - Software system repair processing method and software system repair processing device - Google Patents
Software system repair processing method and software system repair processing device Download PDFInfo
- Publication number
- CN103902399A CN103902399A CN201210584395.5A CN201210584395A CN103902399A CN 103902399 A CN103902399 A CN 103902399A CN 201210584395 A CN201210584395 A CN 201210584395A CN 103902399 A CN103902399 A CN 103902399A
- Authority
- CN
- China
- Prior art keywords
- statistical indicant
- software systems
- startup value
- processing mode
- value
- 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.)
- Granted
Links
Images
Abstract
An embodiment of the invention provides a software system repair processing method and a software system repair processing device. The software system repair processing method includes: acquiring historical running status information of a software system when the software is restarted from breakdown; adopting a processing mode corresponding to the historical running status information to repair the software system. According to the technical scheme, the historical running status information of the software system is acquired when the software system is restarted from breakdown and the processing mode corresponding to the historical running status information is adopted to repair the software system, breakdown reasons of the software system can be avoided from being misjudged, and reliability and stability of repair processing during breakdown of the software system can be improved.
Description
Technical field
The embodiment of the present invention relates to the communication technology, relates in particular to software systems repair process method and device on a kind of communication facilities.
Background technology
For real-time and the higher communication facilities of reliability requirement, the software systems of moving if current collapse, cannot recover to start operation at short notice as early as possible, and the loss that user is caused is very large.
Currently collapse for software systems the technology of taking and comprise by the manual update software system of technical attendant, enable stand-by equipment and software systems are automatically retracted back into the modes such as the software version successfully starting last time.By the manual update software system of technical attendant, the mode of enabling stand-by equipment, technician individual professional skill is had relatively high expectations, if software systems collapse can not be found to increase the cost of loss in time, therefore, prior art generally adopts software systems to be automatically retracted back into the mode of the software version successfully starting last time.
For example, but under some scene,, software itself is no problem, and just due to system exception power down in software upgrade process, software also can rollback to legacy version, thereby cause software systems remediation efficiency lower.
Summary of the invention
The embodiment of the present invention provides a kind of software systems repair process method and device, in order to improve the reliability and stability of repairing when software systems are collapsed.
First aspect present invention, provides a kind of software systems repair process method, comprising:
Carry out system while restarting in software systems collapses, obtain the history run status information of described software systems;
Adopt the processing mode corresponding with described history run status information, described software systems are repaired.
In the possible implementation of the first of first aspect, described in obtain the history run status information of described software systems, comprising:
The startup value of statistical indicant that starts the frequency of failure for recording the history of described software systems of storing in read memory, adds a new startup value of statistical indicant obtaining by described startup value of statistical indicant, and described new startup value of statistical indicant is described history run status information;
The processing mode that described employing is corresponding with described history run status information, repairs described software systems, comprising:
According to the magnitude relationship between described new startup value of statistical indicant and predetermined threshold value, determine corresponding processing mode, and adopt described processing mode to carry out repair process to software systems.
The implementation possible according to the first of first aspect, in the possible implementation of the second of first aspect, described described startup value of statistical indicant is added to a new startup value of statistical indicant obtaining after, also comprise:
Described new startup value of statistical indicant is write to described storer;
Described software systems are carried out to repair process after, also comprise:
If described repair process success, by the startup value of statistical indicant zero clearing of storing in described storer.
In conjunction with the first or the possible implementation of the second of first aspect, in the third possible implementation of first aspect, described described startup value of statistical indicant is added to a new startup value of statistical indicant obtaining before, also comprise:
If be defined as the software systems fault that powered-off fault causes;
Described described startup value of statistical indicant is added to a new startup value of statistical indicant obtaining, comprising:
First will after the zero clearing of described startup value of statistical indicant, add again one, obtain described new startup value of statistical indicant.
In conjunction with the first, the second or the third possible implementation of first aspect or first aspect, in the 4th kind of possible implementation of first aspect, describedly determine corresponding processing mode according to the magnitude relationship between described new startup value of statistical indicant and predetermined threshold value, comprising:
If described new startup value of statistical indicant is less than or equal to first threshold, determine the first processing mode, described the first processing mode is to call this CONFIG.SYS that will start being stored in first memory to start described software systems;
If described new startup value of statistical indicant is greater than first threshold and is less than or equal to Second Threshold, determine the second processing mode, described the second processing mode is to call the CONFIG.SYS successfully starting last time of being stored in first memory to start described software systems;
If described new startup value of statistical indicant is greater than Second Threshold and is less than or equal to the 3rd threshold value, determine the 3rd processing mode, described the 3rd processing mode is to call the CONFIG.SYS that successfully starts last time of being stored in second memory or the default CONFIG.SYS that can make this equipment successfully start starts described software systems;
If described new startup value of statistical indicant is greater than the 3rd threshold value, determine the 4th processing mode, described the 4th processing mode is for confirming software systems repairing failure, by described new startup value of statistical indicant zero clearing.
In conjunction with the first of first aspect or first aspect, the second, the third or the 4th kind of possible implementation, in the 5th kind of possible implementation of first aspect, described method, also comprises:
After the guidance code of update software system, the startup value of statistical indicant of storing in described storer is subtracted to one.
According to the 4th of first aspect the kind of possible implementation, in the 6th kind of possible implementation of first aspect, described storer, described first memory and described second memory are power down nonvolatile memory.
Second aspect present invention, provides a kind of software systems repair process device, comprising:
Acquisition module, for carrying out system in software systems collapses while restarting, obtains the history run status information of described software systems;
Repair module, for adopting the processing mode corresponding with described history run status information, described software systems are repaired.
In the possible implementation of the first of second aspect, described acquisition module, specifically for the startup value of statistical indicant that starts the frequency of failure for recording the history of described software systems of storing in read memory, described startup value of statistical indicant is added to a new startup value of statistical indicant obtaining, and described new startup value of statistical indicant is described history run status information;
Described reparation module, specifically for according to the magnitude relationship between described new startup value of statistical indicant and predetermined threshold value, is determined corresponding processing mode, and is adopted described processing mode to carry out repair process to software systems.
The implementation possible according to the first of second aspect, in the possible implementation of the second of second aspect, also comprises:
Writing module, after described startup value of statistical indicant being added to a new startup value of statistical indicant obtaining at described acquisition module, writes described storer by described new startup value of statistical indicant;
Update module, for after described reparation module is carried out repair process to software systems, if described repair process success, by the startup value of statistical indicant zero clearing of storing in described storer.
In conjunction with the first or the possible implementation of the second of second aspect, in the third possible implementation of second aspect, described acquisition module, also for described described startup value of statistical indicant is added to a new startup value of statistical indicant obtaining before, if be defined as the software systems fault that powered-off fault causes, first will after the zero clearing of described startup value of statistical indicant, add again one, obtain described new startup value of statistical indicant.
In conjunction with the first, the second or the third possible implementation of second aspect or second aspect, in the 4th kind of possible implementation of second aspect, described reparation module, also for:
If described new startup value of statistical indicant is less than or equal to first threshold, determine the first processing mode, described the first processing mode is to call this CONFIG.SYS that will start being stored in first memory to start described software systems;
If described new startup value of statistical indicant is greater than first threshold and is less than or equal to Second Threshold, determine the second processing mode, described the second processing mode is to call the CONFIG.SYS successfully starting last time of being stored in first memory to start described software systems;
If described new startup value of statistical indicant is greater than Second Threshold and is less than or equal to the 3rd threshold value, determine the 3rd processing mode, described the 3rd processing mode is to call the CONFIG.SYS that successfully starts last time of being stored in second memory or the default CONFIG.SYS that can make this equipment successfully start starts described software systems;
If described new startup value of statistical indicant is greater than the 3rd threshold value, determine the 4th processing mode, described the 4th processing mode is for confirming software systems repairing failure, by described new startup value of statistical indicant zero clearing.
In conjunction with the first of second aspect or second aspect, the second, the third or the 4th kind of possible implementation, in the 5th kind of possible implementation of second aspect, also comprise:
Correcting module, after the guidance code in update software system, subtracts one by the startup value of statistical indicant of storing in described storer.
According to the 4th of second aspect the kind of possible implementation, in the 6th kind of possible implementation of second aspect, described storer, described first memory and described second memory are power down nonvolatile memory.
Software systems repair process method and device that the embodiment of the present invention provides, by carrying out system in software systems collapses while restarting, obtain the history run status information of software systems, adopt again the processing mode corresponding with history run status information, software systems are repaired, can avoid the erroneous judgement to software systems crash reason, thus the reliability and stability of repair process while improving software systems collapse.
Brief description of the drawings
In order to be illustrated more clearly in the embodiment of the present invention or technical scheme of the prior art, to the accompanying drawing of required use in embodiment or description of the Prior Art be briefly described below, apparently, accompanying drawing in the following describes is some embodiments of the present invention, for those of ordinary skill in the art, do not paying under the prerequisite of creative work, can also obtain according to these accompanying drawings other accompanying drawing.
Fig. 1 is the process flow diagram of software systems repair process embodiment of the method one provided by the invention;
Fig. 2 is the process flow diagram of software systems repair process embodiment of the method two provided by the invention;
Fig. 3 is the process flow diagram of software systems repair process embodiment of the method three provided by the invention;
Fig. 4 is the process flow diagram of software systems repair process embodiment of the method six provided by the invention;
Fig. 5 is the structural representation of software systems repair process device embodiment mono-provided by the invention;
Fig. 6 is the structural representation of software systems repair process device embodiment bis-provided by the invention;
Fig. 7 is the structural representation of software systems repair process device embodiment tetra-provided by the invention;
Fig. 8 is the structural representation of software systems repair process device embodiment five provided by the invention.
Embodiment
For making object, technical scheme and the advantage of the embodiment of the present invention clearer, below in conjunction with the accompanying drawing in the embodiment of the present invention, technical scheme in the embodiment of the present invention is clearly and completely described, obviously, described embodiment is the present invention's part embodiment, instead of whole embodiment.Based on the embodiment in the present invention, those of ordinary skill in the art, not making the every other embodiment obtaining under creative work prerequisite, belong to the scope of protection of the invention.
Fig. 1 is the process flow diagram of software systems repair process embodiment of the method one provided by the invention, and as shown in Figure 1, the software systems repair process method of the present embodiment, comprising:
S101, carry out system while restarting in software systems collapses, obtain the history run status information of software systems.
Specifically, can to be that logging software system is normal start or attempt repairing correlation parameter when starting failed number of times, software systems and starting or the fortune correlation parameter of software systems the history run status information of software systems, the history run status information of software systems can be used for characterizing the performance that Start-up and operating performance is repaired in the trial of current software systems, when collapsing, break down in software systems, can be used as the foundation of selecting repair mode.
For instance, it can be in the time that software systems are collapsed that software systems collapses carries out that system restarts, reset by diagnostic analysis technology, autoboot system, can avoid manually restarting problem, the problem includes: can not find the very first time fault, loss seriously and to technician's professional skill require the problems such as high.
S102, the employing processing mode corresponding with history run status information, repair software systems.
For instance, software systems history run status information is that current software systems attempt repairing the number of times that startup is failed, can be in the time that the failed number of times of trial reparation startup be less, again start software systems, in the time that the failed number of times of startup is more, the configuration file that calls the software version that can normally start starts, can realize and adopt the processing mode corresponding with history run status information, software systems are repaired, there is corresponding relation with the reason that causes software systems collapse in history run status information, cause the repair process mode corresponding to reason of software systems collapse, but in prior art mostly in software release upgrade when failure, will carry out version rollback, for not being the upgrading failure causing due to the problem of software systems own, can cause unnecessary version rollback.
The software systems repair process method of the present embodiment, can be applied to communication facilities but be not limited to the embedded system on communication facilities, the executive agent of the present embodiment can be software systems repair process device, in practical application, can be operation embedded system communication facilities in central processing unit (Central Processing Unit, be called for short CPU), this CPU can be for calling the repair function code adding in the software systems guidance code bootloader storing in storer, carry out the software systems repair process method of the present embodiment, further can also add protection to this bootloader that is added with repair function code, make it can not be modified destruction.
The software systems repair process method that the present embodiment provides, by carrying out system in software systems collapses while restarting, obtain the history run status information of software systems, adopt again the processing mode corresponding with history run status information, software systems are repaired, can avoid the erroneous judgement to software systems crash reason, thus the reliability and stability of repair process while improving software systems collapse.
Fig. 2 is the process flow diagram of software systems repair process embodiment of the method two provided by the invention, and as shown in Figure 2, the software systems repair process method of the present embodiment, on basis embodiment illustrated in fig. 1, can comprise:
The history for logging software system of storing in S201, read memory starts the startup value of statistical indicant of the frequency of failure, adds a new startup value of statistical indicant obtaining by starting value of statistical indicant, and new startup value of statistical indicant is history run status information.
Specifically, the present embodiment is provided for logging software system and attempts repairing the startup value of statistical indicant that starts the frequency of failure, and startup value of statistical indicant is stored in storer, when starting to restart after software systems collapse, can be in the time of bootloader completion system hardware initialization, startup value of statistical indicant in read memory, adds a new startup value of statistical indicant obtaining by starting value of statistical indicant, and new startup value of statistical indicant is the history run status information in the present embodiment.
S202, by new startup value of statistical indicant write store.
Specifically, by new startup value of statistical indicant write store, can ensure to start the renewal of value of statistical indicant.
S203, according to the magnitude relationship between new startup value of statistical indicant and predetermined threshold value, determine corresponding processing mode, and adopt processing mode to carry out repair process to software systems.
If S204 repair process success, by the startup value of statistical indicant zero clearing of storing in storer.
Specifically, if the repair process success to software systems can think that current software systems can normally be used, the reason that causes its collapse may be powered-off fault, so need to be by the startup value of statistical indicant zero clearing of storing in storer.
The software systems repair process method that the present embodiment provides, start the startup value of statistical indicant of the frequency of failure by the history for logging software system of storing in read memory, add a new startup value of statistical indicant obtaining by starting value of statistical indicant, new startup value of statistical indicant is history run status information, again according to the magnitude relationship between new startup value of statistical indicant and predetermined threshold value, determine corresponding processing mode, and adopt processing mode to carry out repair process to software systems, can avoid the erroneous judgement to software systems crash reason, thereby the reliability and stability of repair process while improving software systems collapse.
Fig. 3 is the process flow diagram of software systems repair process embodiment of the method three provided by the invention, and as shown in Figure 3, the software systems repair process method of the present embodiment, on Fig. 1 or basis embodiment illustrated in fig. 2, can comprise:
The history for logging software system of storing in S301, read memory starts the startup value of statistical indicant of the frequency of failure.
If S302 is defined as the software systems fault that powered-off fault causes.
S303, first will after the zero clearing of startup value of statistical indicant, add again one, obtain new startup value of statistical indicant.
Specifically, if be defined as the software systems fault that powered-off fault causes, think that software systems fault is not to be caused by the problem of software systems itself, so need to value of statistical indicant zero clearing will be started.
S304, according to the magnitude relationship between new startup value of statistical indicant and predetermined threshold value, determine corresponding processing mode, and adopt processing mode to carry out repair process to software systems.
Specifically, if be defined as the software systems fault that powered-off fault causes, first will after the zero clearing of startup value of statistical indicant, add again one, obtain new startup value of statistical indicant, new startup value of statistical indicant is 1, can be according to new startup value of statistical indicant, call this CONFIG.SYS that will start and start software systems, and prior art can be called the system configuration software of old software version and carries out version rollback in this kind of situation, the present embodiment, by the software systems fault that determines whether to cause for powered-off fault, can be avoided the defect of prior art.
If S305 repair process success, by the startup value of statistical indicant zero clearing of storing in storer.
The software systems repair process method that the present embodiment provides, start the startup value of statistical indicant of the frequency of failure by the history for logging software system of storing in read memory, if be defined as the software systems fault that powered-off fault causes, first will after the zero clearing of startup value of statistical indicant, add again one, obtain new startup value of statistical indicant, again according to the magnitude relationship between new startup value of statistical indicant and predetermined threshold value, determine corresponding processing mode, and adopt processing mode to carry out repair process to software systems, can avoid the erroneous judgement to software systems crash reason, thereby the reliability and stability of repair process while improving software systems collapse.
On Fig. 2 or basis embodiment illustrated in fig. 3, in software systems repair process embodiment of the method four provided by the invention, S203 or S304 specifically can comprise:
If new startup value of statistical indicant is less than or equal to first threshold, determine the first processing mode, the first processing mode is to call this CONFIG.SYS that will start being stored in first memory to start software systems;
The scene of the software systems fault that the first processing mode can cause for powered-off fault, calls this CONFIG.SYS that will start being stored in first memory and starts software systems.
If new startup value of statistical indicant is greater than first threshold and is less than or equal to Second Threshold, determine the second processing mode, the second processing mode is to call the CONFIG.SYS startup software systems that successfully start last time of being stored in first memory;
The second processing mode can be more for starting the frequency of failure, shows software systems existing problems that this will start, so call the CONFIG.SYS startup software systems that successfully start last time of being stored in first memory.
If new startup value of statistical indicant is greater than Second Threshold and is less than or equal to the 3rd threshold value, determine the 3rd processing mode, the 3rd processing mode is to call the CONFIG.SYS that successfully starts last time of being stored in second memory or the default CONFIG.SYS startup software systems that can make this equipment successfully start;
The 3rd processing mode can start the scene that software systems still can not successfully start for calling the CONFIG.SYS successfully starting last time of being stored in first memory, call the CONFIG.SYS successfully starting last time of being stored in second memory and start software systems, second memory can refer to store the CONFIG.SYS that successfully started other last time or the default storer that can make the CONFIG.SYS that this equipment successfully starts.
If new startup value of statistical indicant is greater than the 3rd threshold value, determine the 4th processing mode, the 4th processing mode is for confirming software systems repairing failure, by new startup value of statistical indicant zero clearing.
The 4th processing mode can for start the frequency of failure too much, call the CONFIG.SYS successfully starting last time of being stored in second memory and can not successfully start the scene of software systems, for this kind of scene, think software systems repairing failure, by new startup value of statistical indicant zero clearing, by new startup value of statistical indicant write store, extremely exit.
Specifically, above-mentioned first threshold, Second Threshold and the 3rd threshold value are the threshold value of switching different Starting mode, and its concrete numerical value can be determined according to distinct device.
In the time that system starts successfully, by this or the software version that successfully started last time and start configuration information and backup in first memory and second memory, starting configuration information mainly can comprise: the deposit position of startup file, specifically can comprise the address of first memory and the address of second memory; The title of startup file, specifically can comprise filename and this filename that will start of successfully starting last time; Processing mode, specifically can comprise the first processing mode, the second processing mode and the 3rd processing mode.
Further, on the basis of software systems repair process embodiment of the method four provided by the invention, software systems repair process embodiment of the method five provided by the invention, can also comprise:
After the guidance code of update software system, the startup value of statistical indicant of storing in storer is subtracted to one.
Specifically, because software systems are in the time starting, if when the bootloader that the bootloader of current system and the CONFIG.SYS calling are corresponding is not identical, both need to be upgraded unanimously, in the time of the bootloader of update software system, software systems need to be restarted once, can cause starting value of statistical indicant and add one, what but renewal bootloader caused restarts, be not because the problem of software itself causes, so need to be after the bootloader of update software system, the startup value of statistical indicant of storing in storer is subtracted to one, ensureing to start value of statistical indicant only records due to restarting that the problem of software systems itself causes.
Further, in above-mentioned arbitrary embodiment, storer, first memory and second memory can be power down nonvolatile memory, are specifically as follows pocket flash memory (Compact Flash is called for short CF) card, flash memory flash etc.
The software systems repair process method that the present embodiment provides, start the startup value of statistical indicant of the frequency of failure by the history for logging software system of storing in read memory, add a new startup value of statistical indicant obtaining by starting value of statistical indicant, new startup value of statistical indicant is history run status information, again according to the magnitude relationship between new startup value of statistical indicant and predetermined threshold value, determine corresponding processing mode, and adopt the first processing mode, the second processing mode, one in the 3rd processing mode or the 4th processing mode is carried out repair process to software systems, can avoid the erroneous judgement to software systems crash reason, thereby the reliability and stability of repair process while improving software systems collapse.
Below to start value of statistical indicant as n, first threshold is N1, Second Threshold is N2, the 3rd threshold value is that N3 is example, technical scheme of the present invention is elaborated, and Fig. 4 is the process flow diagram of software systems repair process embodiment of the method six provided by the invention, as shown in Figure 4, the software systems repair process method of the present embodiment, comprising:
System is restarted in S401, software systems collapse.
The history for logging software system of storing in S402, read memory starts the startup value of statistical indicant of the frequency of failure.
S403, determine whether the software systems fault that powered-off fault causes, if so, carry out S404, if not, carry out S405.
S404, will start value of statistical indicant zero clearing.
S405, by start value of statistical indicant add a new startup value of statistical indicant obtaining.
S406, judge the magnitude relationship between new startup value of statistical indicant n and first threshold N1, Second Threshold N2, the 3rd threshold value N3, if n≤N1 carries out S407; If N1 < is n≤N2, carry out S408; If N2 < is n≤N3, carry out S409; If n > is N3, carry out S410.
S407, call this CONFIG.SYS that will start being stored in first memory and start software systems.
S408, call the CONFIG.SYS successfully starting last time of being stored in first memory and start software systems.
S409, call the CONFIG.SYS that successfully starts last time of being stored in second memory or the default CONFIG.SYS that this equipment successfully starts that can make starts software systems.
S410, confirmation software systems repairing failure, by new startup value of statistical indicant zero clearing, exit extremely.
S411, after the guidance code of update software system, the startup value of statistical indicant of storing in storer is subtracted to one.
S412, judge that whether software systems successfully start, if so, carry out S413, if not, return to S401.
S413, by the startup value of statistical indicant zero clearing of storing in storer.
The software systems repair process method that the present embodiment provides, start the startup value of statistical indicant of the frequency of failure by the history for logging software system of storing in read memory, add a new startup value of statistical indicant obtaining by starting value of statistical indicant, new startup value of statistical indicant is history run status information, again according to the magnitude relationship between new startup value of statistical indicant and predetermined threshold value, determine corresponding processing mode, and adopt processing mode to carry out repair process to software systems, can avoid the erroneous judgement to software systems crash reason, thereby the reliability and stability of repair process while improving software systems collapse.
Fig. 5 is the structural representation of software systems repair process device embodiment mono-provided by the invention, as shown in Figure 5, the system repair process device of the present embodiment, comprise acquisition module 51 and repair module 52, wherein, when acquisition module 51 is restarted for carry out system in software systems collapse, obtain the history run status information of software systems; Repair module 52 for adopting the processing mode corresponding with history run status information, software systems are repaired.
The device of the present embodiment, can be for the technical scheme of embodiment of the method shown in execution graph 1, and it realizes principle and technique effect is similar, repeats no more herein.
Fig. 6 is the structural representation of software systems repair process device embodiment bis-provided by the invention, the system repair process device of the present embodiment, on the basis of software systems repair process device embodiment bis-provided by the invention, can also comprise writing module 53 and update module 54, wherein, acquisition module 51 starts the startup value of statistical indicant of the frequency of failure specifically for the history for logging software system of storing in read memory, add a new startup value of statistical indicant obtaining by starting value of statistical indicant, new startup value of statistical indicant is history run status information; Writing module 53 is for after startup value of statistical indicant is added a new startup value of statistical indicant obtaining by acquisition module, by new startup value of statistical indicant write store; Update module 54 is for after reparation module is carried out repair process to software systems, if repair process success, by the startup value of statistical indicant zero clearing of storing in storer; Repair module 52 specifically for according to the magnitude relationship between new startup value of statistical indicant and predetermined threshold value, determine corresponding processing mode, and adopt processing mode to carry out repair process to software systems.
The device of the present embodiment, can be for the technical scheme of embodiment of the method shown in execution graph 2, and it realizes principle and technique effect is similar, repeats no more herein.
On basis embodiment illustrated in fig. 6, in software systems repair process device embodiment tri-provided by the invention, acquisition module 51 is also for before adding a new startup value of statistical indicant obtaining by startup value of statistical indicant, if be defined as the software systems fault that powered-off fault causes, first will after the zero clearing of startup value of statistical indicant, add again one, obtain new startup value of statistical indicant.
The device of the present embodiment, can be for the technical scheme of embodiment of the method shown in execution graph 3, and it realizes principle and technique effect is similar, repeats no more herein.
Fig. 7 is the structural representation of software systems repair process device embodiment tetra-provided by the invention, as shown in Figure 7, and the system repair process device of the present embodiment, on the basis of said apparatus embodiment, also comprise correcting module 55, wherein, repair module 52 also for:
If new startup value of statistical indicant is less than or equal to first threshold, determine the first processing mode, the first processing mode is to call this CONFIG.SYS that will start being stored in first memory to start software systems;
If new startup value of statistical indicant is greater than first threshold and is less than or equal to Second Threshold, determine the second processing mode, the second processing mode is to call the CONFIG.SYS startup software systems that successfully start last time of being stored in first memory;
If new startup value of statistical indicant is greater than Second Threshold and is less than or equal to the 3rd threshold value, determine the 3rd processing mode, the 3rd processing mode is to call the CONFIG.SYS that successfully starts last time of being stored in second memory or the default CONFIG.SYS startup software systems that can make this equipment successfully start;
If new startup value of statistical indicant is greater than the 3rd threshold value, determine the 4th processing mode, the 4th processing mode is for confirming software systems repairing failure, by new startup value of statistical indicant zero clearing.
Correcting module 55 for the guidance code in update software system after, the startup value of statistical indicant of storing in storer is subtracted to one.
The device of the present embodiment, can be for the technical scheme of embodiment of the method shown in execution graph 4, and it realizes principle and technique effect is similar, repeats no more herein.
Further, storer, first memory and the second memory in above-mentioned software systems prosthetic device is power down nonvolatile memory.
Fig. 8 is the structural representation of software systems repair process device embodiment five provided by the invention, as shown in Figure 8, the software systems repair process device of the present embodiment comprises at least one bus 801, at least one processor 802 being connected with bus 801 and at least one storer 803 being connected with bus 801, wherein, processor 802 is by bus 801, call the code of storage in storer 803, for:
Carry out system while restarting in software systems collapses, obtain the history run status information of software systems.
Adopt the processing mode corresponding with history run status information, software systems are repaired.
The software systems repair process device that the present embodiment provides, can be arbitrary for execution graph 1-Fig. 4 shown in the corresponding part of carrying out of software systems repair process device in the technical scheme of embodiment of the method, it realizes principle and technique effect is similar, repeats no more herein.Fig. 8 is only a kind of schematic diagram of the structure of software systems repair process device provided by the invention, and concrete structure can be adjusted according to actual.
One of ordinary skill in the art will appreciate that: all or part of step that realizes above-mentioned each embodiment of the method can complete by the relevant hardware of programmed instruction.Aforesaid program can be stored in a computer read/write memory medium.This program, in the time carrying out, is carried out the step that comprises above-mentioned each embodiment of the method; And aforesaid storage medium comprises: various media that can be program code stored such as ROM, RAM, magnetic disc or CDs.
Finally it should be noted that: above each embodiment, only in order to technical scheme of the present invention to be described, is not intended to limit; Although the present invention is had been described in detail with reference to aforementioned each embodiment, those of ordinary skill in the art is to be understood that: its technical scheme that still can record aforementioned each embodiment is modified, or some or all of technical characterictic is wherein equal to replacement; And these amendments or replacement do not make the essence of appropriate technical solution depart from the scope of various embodiments of the present invention technical scheme.
Claims (14)
1. a software systems repair process method, is characterized in that, comprising:
Carry out system while restarting in software systems collapses, obtain the history run status information of described software systems;
Adopt the processing mode corresponding with described history run status information, described software systems are repaired.
2. method according to claim 1, is characterized in that, described in obtain the history run status information of described software systems, comprising:
The startup value of statistical indicant that starts the frequency of failure for recording the history of described software systems of storing in read memory, adds a new startup value of statistical indicant obtaining by described startup value of statistical indicant, and described new startup value of statistical indicant is described history run status information;
The processing mode that described employing is corresponding with described history run status information, repairs described software systems, comprising:
According to the magnitude relationship between described new startup value of statistical indicant and predetermined threshold value, determine corresponding processing mode, and adopt described processing mode to carry out repair process to software systems.
3. method according to claim 2, is characterized in that, described described startup value of statistical indicant is added to a new startup value of statistical indicant obtaining after, also comprise:
Described new startup value of statistical indicant is write to described storer;
Described software systems are carried out to repair process after, also comprise:
If described repair process success, by the startup value of statistical indicant zero clearing of storing in described storer.
4. according to the method in claim 2 or 3, it is characterized in that, described described startup value of statistical indicant is added to a new startup value of statistical indicant obtaining before, also comprise:
If be defined as the software systems fault that powered-off fault causes;
Described described startup value of statistical indicant is added to a new startup value of statistical indicant obtaining, comprising:
First will after the zero clearing of described startup value of statistical indicant, add again one, obtain described new startup value of statistical indicant.
5. according to the method described in any one in claim 1～4, it is characterized in that, describedly determine corresponding processing mode according to the magnitude relationship between described new startup value of statistical indicant and predetermined threshold value, comprising:
If described new startup value of statistical indicant is less than or equal to first threshold, determine the first processing mode, described the first processing mode is to call this CONFIG.SYS that will start being stored in first memory to start described software systems;
If described new startup value of statistical indicant is greater than first threshold and is less than or equal to Second Threshold, determine the second processing mode, described the second processing mode is to call the CONFIG.SYS successfully starting last time of being stored in first memory to start described software systems;
If described new startup value of statistical indicant is greater than Second Threshold and is less than or equal to the 3rd threshold value, determine the 3rd processing mode, described the 3rd processing mode is to call the CONFIG.SYS that successfully starts last time of being stored in second memory or the default CONFIG.SYS that can make this equipment successfully start starts described software systems;
If described new startup value of statistical indicant is greater than the 3rd threshold value, determine the 4th processing mode, described the 4th processing mode is for confirming software systems repairing failure, by described new startup value of statistical indicant zero clearing.
6. according to the method described in any one in claim 1～5, it is characterized in that, described method, also comprises:
After the guidance code of update software system, the startup value of statistical indicant of storing in described storer is subtracted to one.
7. method according to claim 5, is characterized in that, described storer, described first memory and described second memory are power down nonvolatile memory.
8. a software systems repair process device, is characterized in that, comprising:
Acquisition module, for carrying out system in software systems collapses while restarting, obtains the history run status information of described software systems;
Repair module, for adopting the processing mode corresponding with described history run status information, described software systems are repaired.
9. device according to claim 8, it is characterized in that, described acquisition module, specifically for the startup value of statistical indicant that starts the frequency of failure for recording the history of described software systems of storing in read memory, described startup value of statistical indicant is added to a new startup value of statistical indicant obtaining, and described new startup value of statistical indicant is described history run status information;
Described reparation module, specifically for according to the magnitude relationship between described new startup value of statistical indicant and predetermined threshold value, is determined corresponding processing mode, and is adopted described processing mode to carry out repair process to software systems.
10. device according to claim 9, is characterized in that, also comprises:
Writing module, after described startup value of statistical indicant being added to a new startup value of statistical indicant obtaining at described acquisition module, writes described storer by described new startup value of statistical indicant;
Update module, for after described reparation module is carried out repair process to software systems, if described repair process success, by the startup value of statistical indicant zero clearing of storing in described storer.
11. according to the device described in claim 9 or 10, it is characterized in that, described acquisition module, also for described described startup value of statistical indicant is added to a new startup value of statistical indicant obtaining before, if be defined as the software systems fault that powered-off fault causes, first will after the zero clearing of described startup value of statistical indicant, add again one, obtain described new startup value of statistical indicant.
Device in 12. according to Claim 8～11 described in any one, is characterized in that, described reparation module, also for:
If described new startup value of statistical indicant is less than or equal to first threshold, determine the first processing mode, described the first processing mode is to call this CONFIG.SYS that will start being stored in first memory to start described software systems;
If described new startup value of statistical indicant is greater than first threshold and is less than or equal to Second Threshold, determine the second processing mode, described the second processing mode is to call the CONFIG.SYS successfully starting last time of being stored in first memory to start described software systems;
If described new startup value of statistical indicant is greater than Second Threshold and is less than or equal to the 3rd threshold value, determine the 3rd processing mode, described the 3rd processing mode is to call the CONFIG.SYS that successfully starts last time of being stored in second memory or the default CONFIG.SYS that can make this equipment successfully start starts described software systems;
If described new startup value of statistical indicant is greater than the 3rd threshold value, determine the 4th processing mode, described the 4th processing mode is for confirming software systems repairing failure, by described new startup value of statistical indicant zero clearing.
Device in 13. according to Claim 8～12 described in any one, is characterized in that, also comprises:
Correcting module, after the guidance code in update software system, subtracts one by the startup value of statistical indicant of storing in described storer.
14. devices according to claim 12, is characterized in that, described storer, described first memory and described second memory are power down nonvolatile memory.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210584395.5A CN103902399B (en) | 2012-12-28 | 2012-12-28 | Software system repair processing method and software system repair processing device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210584395.5A CN103902399B (en) | 2012-12-28 | 2012-12-28 | Software system repair processing method and software system repair processing device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN103902399A true CN103902399A (en) | 2014-07-02 |
| CN103902399B CN103902399B (en) | 2017-05-10 |
Family
ID=50993737
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201210584395.5A Active CN103902399B (en) | 2012-12-28 | 2012-12-28 | Software system repair processing method and software system repair processing device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN103902399B (en) |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105224413A (en) * | 2015-10-09 | 2016-01-06 | 广东欧珀移动通信有限公司 | A kind of method and disposal system promoting application program steady state (SS) |
| CN105808411A (en) * | 2016-03-08 | 2016-07-27 | 李小荣 | Method and device for alarming system fault through social application |
| CN106020866A (en) * | 2016-05-10 | 2016-10-12 | 北京金山安全软件有限公司 | Blue screen processing method and device and terminal |
| CN106155736A (en) * | 2016-06-22 | 2016-11-23 | 广州优视网络科技有限公司 | Software is installed and is started type detection method, device and user terminal |
| CN106547635A (en) * | 2015-09-18 | 2017-03-29 | 阿里巴巴集团控股有限公司 | A kind of operation of operation retries method and apparatus |
| CN107479997A (en) * | 2017-07-26 | 2017-12-15 | 太仓华淏信息科技有限公司 | Self- healing software system |
| CN108055583A (en) * | 2017-12-28 | 2018-05-18 | 深圳市九洲电器有限公司 | set-top box automatic recovery method and system |
| CN110175034A (en) * | 2019-05-30 | 2019-08-27 | 烽火通信科技股份有限公司 | A kind of restoration methods and system of application program |
| CN110908722A (en) * | 2019-11-29 | 2020-03-24 | 北京嘀嘀无限科技发展有限公司 | Method and device applied to starting of operating system, electronic equipment and storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6272626B1 (en) * | 1997-12-20 | 2001-08-07 | International Business Machines Corporation | System for setting a flag indicating a boot failure of loading a procedure and aborting additional loading attempt thereof when the flag is detected |
| CN101441576A (en) * | 2009-01-08 | 2009-05-27 | 杭州华三通信技术有限公司 | Software restarting method and equipment of embedded type equipment |
| CN102681874A (en) * | 2012-05-14 | 2012-09-19 | 腾讯科技（深圳）有限公司 | Method and device for ensuring normal running of software |
| CN102681917A (en) * | 2012-04-24 | 2012-09-19 | 中标软件有限公司 | Operating system (OS) and recovery method thereof |
-
2012
- 2012-12-28 CN CN201210584395.5A patent/CN103902399B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6272626B1 (en) * | 1997-12-20 | 2001-08-07 | International Business Machines Corporation | System for setting a flag indicating a boot failure of loading a procedure and aborting additional loading attempt thereof when the flag is detected |
| CN101441576A (en) * | 2009-01-08 | 2009-05-27 | 杭州华三通信技术有限公司 | Software restarting method and equipment of embedded type equipment |
| CN102681917A (en) * | 2012-04-24 | 2012-09-19 | 中标软件有限公司 | Operating system (OS) and recovery method thereof |
| CN102681874A (en) * | 2012-05-14 | 2012-09-19 | 腾讯科技（深圳）有限公司 | Method and device for ensuring normal running of software |
Cited By (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106547635A (en) * | 2015-09-18 | 2017-03-29 | 阿里巴巴集团控股有限公司 | A kind of operation of operation retries method and apparatus |
| US10866862B2 (en) | 2015-09-18 | 2020-12-15 | Alibaba Group Holding Limited | Method and apparatus for job operation retry |
| CN105224413B (en) * | 2015-10-09 | 2018-05-15 | 广东欧珀移动通信有限公司 | A kind of method and processing system for lifting application program stable state |
| CN105224413A (en) * | 2015-10-09 | 2016-01-06 | 广东欧珀移动通信有限公司 | A kind of method and disposal system promoting application program steady state (SS) |
| CN105808411A (en) * | 2016-03-08 | 2016-07-27 | 李小荣 | Method and device for alarming system fault through social application |
| CN106020866A (en) * | 2016-05-10 | 2016-10-12 | 北京金山安全软件有限公司 | Blue screen processing method and device and terminal |
| CN106155736A (en) * | 2016-06-22 | 2016-11-23 | 广州优视网络科技有限公司 | Software is installed and is started type detection method, device and user terminal |
| CN106155736B (en) * | 2016-06-22 | 2019-04-12 | 广州优视网络科技有限公司 | Software installation starts type detection method, apparatus and user terminal |
| CN107479997A (en) * | 2017-07-26 | 2017-12-15 | 太仓华淏信息科技有限公司 | Self- healing software system |
| CN108055583A (en) * | 2017-12-28 | 2018-05-18 | 深圳市九洲电器有限公司 | set-top box automatic recovery method and system |
| CN108055583B (en) * | 2017-12-28 | 2020-08-07 | 深圳市九洲电器有限公司 | Automatic recovery method and system for set top box |
| CN110175034A (en) * | 2019-05-30 | 2019-08-27 | 烽火通信科技股份有限公司 | A kind of restoration methods and system of application program |
| CN110908722A (en) * | 2019-11-29 | 2020-03-24 | 北京嘀嘀无限科技发展有限公司 | Method and device applied to starting of operating system, electronic equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN103902399B (en) | 2017-05-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103902399A (en) | Software system repair processing method and software system repair processing device | |
| CN102023908B (en) | Method and device for backing up boot program | |
| US8341386B2 (en) | Method for updating basic input/output system and method for repairing thereof | |
| CN103842968B (en) | A kind of moving method of internal storage data, computing machine and device | |
| CN102455950A (en) | Firmware recovery system and method of base board management controller | |
| CN104915226A (en) | Network device software starting method, device and network device | |
| CN102855146A (en) | Firmware updating system and method | |
| CN103513993A (en) | Firmware updating system and method | |
| CN102681874B (en) | A kind ofly guarantee the method that software normally runs and device | |
| CN105183517A (en) | Method and device for mounting external storage equipment in recovery mode and electronic device | |
| CN108345464A (en) | A kind of the startup method and Android vehicle device of Android system | |
| CN100583782C (en) | Software upgrade method and device | |
| CN109324918A (en) | Processing method and processing device, terminal and the storage medium of application exception | |
| KR20080023841A (en) | The method of firmware upgrade and automatic firmware recovery system | |
| CN111767172A (en) | Self-repairing method for set top box based on watchdog and bootloader | |
| CN102063317A (en) | Method and system for renewedly burning application program by embedded equipment | |
| CN102880530B (en) | Terminal and terminal backup and restoration methods | |
| CN113190256B (en) | Upgrading method, device and equipment | |
| CN105868047A (en) | Repairing method and device of data partition, and terminal | |
| KR100832269B1 (en) | Program update method and system for wireless communication terminal | |
| CN103019773A (en) | System update power failure protection method and system, and mobile terminal | |
| CN107436783B (en) | Differential upgrading method for mobile terminal, storage medium and mobile terminal | |
| CN115951949A (en) | Recovery method and device for configuration parameters of BIOS (basic input output System) and computing equipment | |
| CN114995852A (en) | Equipment upgrading method, equipment and computer readable storage medium | |
| CN101546281A (en) | Method and device for improving reliability of embedded system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20191210 Address after: 056000 north of Yao village, Yongnian, Handan, Hebei Patentee after: Handan Yongnian yongsha glass products Co.,Ltd. Address before: 510000 unit 2414-2416, building, No. five, No. 371, Tianhe District, Guangdong, China Patentee before: GUANGDONG GAOHANG INTELLECTUAL PROPERTY OPERATION Co.,Ltd. Effective date of registration: 20191210 Address after: 510000 unit 2414-2416, building, No. five, No. 371, Tianhe District, Guangdong, China Patentee after: GUANGDONG GAOHANG INTELLECTUAL PROPERTY OPERATION Co.,Ltd. Address before: 518129 Bantian HUAWEI headquarters office building, Longgang District, Guangdong, Shenzhen Patentee before: HUAWEI TECHNOLOGIES Co.,Ltd. |
|
| TR01 | Transfer of patent right |