CN111309388B - Automatic rollback system and method for system software version of equipment - Google Patents
Automatic rollback system and method for system software version of equipment Download PDFInfo
- Publication number
- CN111309388B CN111309388B CN202010079218.6A CN202010079218A CN111309388B CN 111309388 B CN111309388 B CN 111309388B CN 202010079218 A CN202010079218 A CN 202010079218A CN 111309388 B CN111309388 B CN 111309388B
- Authority
- CN
- China
- Prior art keywords
- system software
- version
- network
- state
- component
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/4401—Bootstrapping
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1415—Saving, restoring, recovering or retrying at system level
- G06F11/142—Reconfiguring to eliminate the error
- G06F11/143—Reconfiguring to eliminate the error with loss of software functionality
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Quality & Reliability (AREA)
- Stored Programmes (AREA)
Abstract
The present disclosure provides a method of automatic rollback of a system software version of a device, the device including a bootstrap component, a system software component containing a current version of system software and one or more alternate versions of system software, and a network status flag storage medium, the method comprising: the bootstrap component resets the network state flag after acquiring the network state flag of the network state flag storage medium when the device is currently started; and the bootstrap component directly boots and enables the standby version of the system software in the system software component when the first field portion of the acquired network state flag is a first state indicating that the device was not able to complete network initialization when the device was last booted. The disclosure also provides a system adopting the method.
Description
Technical Field
The present disclosure relates to the field of internet device management/maintenance technology, and in particular, to a system and method for automatically rolling back a software version when a remote device fails.
Background
With the continuous development of network technology, embedded technology has been applied to various corners and fields of the world, and various embedded network devices are applied to areas such as villages, mines, power stations, deserts, and mountainous areas where traffic is inconvenient. Because the equipment distribution range is wide, once installation and debugging are finished, later maintenance work (such as firmware upgrading, version upgrading, feature library upgrading, new instruction issuing for equipment and the like) is mostly carried out remotely through a network, and the equipment is more dependent on the network condition, so that great challenges are brought to the stability and reliability of the equipment in long-term operation.
For example, if the device's own network communication function fails, it will be in an out-of-connection state and maintenance personnel will not be able to perform remote maintenance. In this case, maintenance personnel can only go to the site to troubleshoot the problem, thereby incurring significant maintenance costs.
One common equipment maintenance scheme is a dual-standby scheme (dual hot standby), wherein when one piece of equipment fails, service functions are automatically switched to the other standby, so that the service is not affected. However, this solution has the following drawbacks: 1. if the standby machine also fails, namely, when two devices cannot work normally, maintenance personnel must go to the site to perform maintenance; 2. by using the dual-machine backup scheme, the dual-machine backup scheme can be realized by purchasing more additional equipment with the same function, and a corresponding support system is also needed, so that the equipment cost is at least doubled; 3. the long-term double-machine hot standby is also a huge energy consumption.
Disclosure of Invention
The present disclosure has been made in view of the above-described circumstances in the prior art. It is an aim of exemplary embodiments of the present disclosure to overcome the above and/or other problems in the prior art.
The occurrence of on-site maintenance conditions of maintenance personnel is reduced, the smoothness of a network, particularly the network function of the maintained equipment is guaranteed, the network function of the equipment is required to be monitored, the network function of the equipment is monitored from two stages of equipment operation, and therefore the remote maintainability of the equipment is guaranteed.
The present disclosure thus proposes a method of automatic rollback of a system software version of a device comprising a bootstrap component, a system software component comprising a current version of system software and one or more alternate versions of system software, and a network status flag storage medium, the method comprising: the bootstrap component resets the network state flag after acquiring the network state flag of the network state flag storage medium when the device is currently started; and the bootstrap component directly boots and enables the standby version of the system software in the system software component when the first field portion of the acquired network state flag is a first state indicating that the device was not able to complete network initialization when the device was last booted.
The automatic rollback method of the system software version of the device according to the present disclosure further comprises: the bootstrap component directs the direct enablement of the last boot-time enabled current version of the system software components when the first field portion is in a second state indicating that network initialization has been completed at a last boot-time of the device, and places the first field portion in the second state by the enabled current version of the system software.
The automatic rollback method of the system software version of the device according to the present disclosure further comprises: the enabled current version of system software ends the automatic rollback operation of the device upon initiating and completing a remote service connection with the remote server.
The automatic rollback method of the system software version of the device according to the present disclosure further comprises: the enabled current version system software sets a second field portion to a first state when the enabled current version system software has completed a state of a remote service connection if the acquired network state flags further include the second field portion.
The automatic rollback method of the system software version of the device according to the present disclosure further comprises: the enabled current version system software resets the network status flag upon a predetermined number of initiation of a remote service connection with a remote server and failure, so that the bootstrap component boots up directly to enable the alternate version system software in the system software component after restarting the device.
The automatic rollback method of the system software version of the device according to the present disclosure further comprises: and under the condition that the acquired network state mark also comprises a second field part, the enabled current version system software sets the second field part into a second state when the message request message is not sent to the server when the remote service connection with the remote server is initiated, and sets the second field part into a third state when the message request message is sent to the server when the remote service connection with the remote server is initiated but the server response message is not acquired.
According to another aspect of the present disclosure, there is also provided an automatic rollback system for a system software version of a device, the device including a bootstrap component, a system software component including a current version of system software and one or more alternate versions of system software, and a network state flag storage medium, wherein the bootstrap component resets the network state flag after acquiring a network state flag of the network state flag storage medium when the device is currently started; and the bootstrap component directly boots and enables the standby version of the system software in the system software component when the first field portion of the acquired network state flag is a first state indicating that the device was not able to complete network initialization when the device was last booted.
An automatic rollback system for system software versions of devices according to the present disclosure, wherein the bootstrap component directs direct enablement of a current version of system software enabled at a previous boot in the system software component when the first field portion is a second state indicating that network initialization has been completed at a previous boot of a device, and places the first field portion in the second state by the enabled current version of system software.
An automatic rollback system for a system software version of a device according to the present disclosure, wherein the enabled current version of system software ends an automatic rollback operation of the device upon initiating a remote service connection with a remote server and completing the remote service connection.
An automatic rollback system for a system software version of a device according to the present disclosure, wherein the enabled current version system software, if the acquired network state flag further comprises a second field portion, places the second field portion in a first state when the enabled current version system software has completed a state of a remote service connection.
An automatic rollback system for a system software version of a device according to the present disclosure, wherein the enabled current version of system software resets the network status flag upon a predetermined number of times of initiating a remote service connection with a remote server and failure, so that the bootstrap component boots up directly enabling a standby version of system software in the system software component after restarting the device.
An automatic rollback system for a system software version of a device according to the present disclosure, wherein the enabled current version system software, in the case where the acquired network state flag further includes a second field portion, places the second field portion in a second state when a message request message to a server is not issued upon initiation of a remote service connection with a remote server, and places the second field portion in a third state when a message request message to a server is completed upon initiation of a remote service connection with a remote server but a server response message is not acquired.
Through the automatic rollback system and the method for the system software version of the equipment, when the equipment is abnormal in maintenance or operation and cannot be controlled through a remote function (in a disconnection state), the equipment automatically analyzes and diagnoses the current operation state, makes simple repair, tries to solve the problem that remote management cannot be carried out in the aspect of the equipment, or provides necessary data information for subsequent field maintenance personnel, and is convenient for positioning and solving the problem. The automatic rollback system and the method for the system software version of the equipment can automatically select the guided system software version under the boot program of the operating system, automatically analyze the state of the current network environment under the system software version and automatically repair the current network environment, thereby reducing manual intervention and saving maintenance cost.
The beneficial effects of the embodiment of the disclosure include: the number of times that maintenance personnel go to on-site maintenance equipment is reduced, the stability of the equipment is improved, the networking environment of the equipment is simplified, and the maintenance cost is reduced.
Drawings
The disclosure may be better understood by describing exemplary embodiments thereof in conjunction with the accompanying drawings, in which:
FIG. 1 is a block schematic diagram of an automatic rollback system of a system software version of a device according to an embodiment of the present disclosure;
FIG. 2 is a process flow diagram illustrating the bootstrap components of an automatic rollback method of a system software version of a device according to an embodiment of the present disclosure; and
fig. 3 is a process flow diagram illustrating the system software components of an automatic rollback method for a system software version of a device according to an embodiment of the present disclosure.
Detailed Description
Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples are not representative of all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present disclosure as detailed in the accompanying claims. It should be appreciated that in the actual implementation of any of the implementations, as in any engineering or design project, numerous implementation-specific decisions must be made to achieve the developers' specific goals, such as compliance with system-related and business-related constraints, which may vary from one implementation to another. Moreover, it should be appreciated that while such a development effort might be complex and lengthy, it would nevertheless be a routine undertaking of design, fabrication, or manufacture for those of ordinary skill having the benefit of this disclosure, and thus should not be construed as having the benefit of this disclosure.
The terminology used in the present disclosure is for the purpose of describing particular embodiments only and is not intended to be limiting of the present disclosure. As used in this disclosure and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any or all possible combinations of one or more of the associated listed items.
It should be understood that although the terms first, second, third, etc. may be used in this disclosure to describe various information, these information should not be limited to these terms. These terms are only used to distinguish one type of information from another, but not to identify any order, quantity, or importance, but rather to distinguish between different components. When referring to "first", it is not intended that there be necessarily "second" or "third" like elements or portions. For example, a first field portion may also be referred to as a second field portion, and vice versa, without departing from the scope of the present disclosure. The terms "a" or "an" and the like do not denote a limitation of quantity, but rather denote the presence of at least one. The word "comprising" or "comprises", and the like, is intended to mean that elements or items that are immediately preceding the word "comprising" or "comprising", are included in the word "comprising" or "comprising", and equivalents thereof, without excluding other elements or items. The terms "connected" or "connected," and the like, are not limited to physical or mechanical connections, nor to direct or indirect connections. The word "if" as used herein may be interpreted as "at …" or "at …" or "responsive to a determination", depending on the context.
In general, embodiments according to the present disclosure implement remote malfunction problem analysis by the system software and boot program of the device cooperating together, and then by the version rollback operation of the system software and recording data of the current device state. Specifically, embodiments according to the present disclosure primarily utilize a network status flag of a device to determine which version of system software the device is using at the current or current boot-up. This network status flag is stored in a non-volatile storage medium (e.g., EEPROM, flash chip) of the device itself, which first obtains the network status flag before a boot program (Bootloader) enables the selected read system software, and then selects a version of the system software based on the network status flag. The system software may be an operating system, an application program.
FIG. 1 is a block schematic diagram of an automatic rollback system 100 of a system software version of a device according to an embodiment of the present disclosure; as shown in fig. 1, the automatic rollback system 100 includes a bootstrap component 101, a system software component 102 that includes a current version of system software and one or more alternate versions of system software, and a network status flag storage medium 103. The bootstrap component 101 starts a bootstrap program (Bootloader) at device start-up. The boot program will then enable the system software in the corresponding system software component. The system software may be either operating software or an application software. To enable remote self-repair of a device, the system software component 102 includes a current version of system software and one or more alternate versions of system software. The current version of system software is the system software that the system is running or the system software that the device has just been enabled before the device is started. While the alternate version of system software is a set of system software that can replace the current version of system software, typically the same family of old versions of system software of the current version of system software or the current version of system software of another company. Alternatively, a plurality of different alternate versions of system software may be provided, if necessary.
When a device is started up due to a network connection failure, the bootstrap component 101 will initially acquire the network status flag stored in the storage medium 103. The network status flag describes the status of the network connection of the device during the previous run. The network connection state mainly records the network connection initialization state when the device is started. In general, if the device has not completed network initialization at the previous boot-up, then the network status flag is set to the first state; if the device has completed network initialization at the previous start-up, the network status flag is set to the second state. Typically, the network status markers use a 32-bit unsigned integer to record network status. The method is mainly used for recording the initialization completion state of the network function. The lower 16-bit first field portion, typically using a 32-bit unsigned integer flag, indicates whether the network is complete with initialization, and the upper 16-bit second field portion of the flag may be left empty instead of used. The first state of the first field portion thus represents a state in which the network initialization was not completed at the previous start-up of the device, and the second state of the first field portion represents a state in which the network initialization was completed at the previous start-up of the device. In this disclosure, the first state of the first field portion is denoted as "0", i.e. "0" indicates that the last boot of the device did not complete the network function initialization (and is then restarted), and thus the last boot of the system software version has a network function initialization failure. And the second state of the first field part is denoted as "1", where "1" indicates that the last started system software version completes the initialization of the network function and can be started normally. Specifically, "0" and "1" are used to distinguish different states or other modes, and the user can configure itself according to the needs or the actual situation of the device.
Optionally, in order to facilitate technicians to know more fault clues during subsequent manual detection and analysis of faults, faults can be more conveniently troubleshooted, and the status code of the occurrence of the faults can be recorded in the upper 16 bits of the network status flag. Thus, in another alternative embodiment, the high 16 bits of the network status flag may be used to record the status of whether the network remote management function is normal, i.e., the first field indicates whether the network is initialized and the second field indicates whether the network remote management function is normal. Typically, when a device communicates with a remote server 104 remotely, a message request and a server response message receipt are required. For this reason, the present disclosure adopts to put the second field part of the network status flag into the first state to indicate that the device has completed the remote service connection with the enabled current version system software, that is, has completed the sending of the message request and has received the response message fed back by the server; the present disclosure employs placing a second field portion of the network status flag in a second state to indicate that the enabled current version of system software did not complete sending a message request message to the server 104 when initiating a remote service connection with the remote server 104; and the present disclosure employs placing the second field portion of the network status flag in a third state to indicate that the enabled current version of system software completes issuing a message request message to server 101 but does not obtain a response message for server 104 when initiating a remote service connection with remote server 104. The first state of the second field portion may be denoted as "0", the second state may be denoted as "1" and the third state may be denoted as "2", in which way the configuration may be performed by itself according to the user's needs. In this case, the upper 16-bit region with the 32-bit unsigned integer network status flag indicates whether the network remote management function is normal and the lower 16-bit region indicates whether the network is complete in initialization.
Fig. 2 is a process flow diagram of an automatic rollback method of a system software version of a device at a bootstrap component 101 according to an embodiment of the present disclosure. As shown in fig. 2, upon a device failing in a network connection, the bootstrap component of the automatic rollback system 100 begins to obtain the network state flag stored therein from the storage medium 103 at step S110, e.g., to obtain the value of the first field portion of the network state flag located in the lower 16 bits, or the value of the first field portion located in the lower 16 bits and the value of the second field portion located in the upper 16 bits. While the first field portion of the network status flag in the storage medium 103 is set to 0 (default state). The network status flag is reset after the network status flag stored therein is acquired. The purpose of resetting the network status flag is to re-record the network connection procedure of the enabled system software during subsequent execution so that a later technician can understand the cause of the device network connection procedure.
It is then determined at step S120 whether the acquired network state flag is in a first state, e.g. whether the value of the first field portion of the network state flag located at the lower 16 bits is 0. If the value of the first field portion is 0, it is determined that the acquired network state flag is in the first state, and the process goes to step S130. If the value of the first field portion is not 0 (e.g., 1), it is determined that the acquired network state flag is not in the first state but in the second state, and the process goes to step S140. If it is determined that the acquired network status flag is in the first state, meaning that the last started current system software version has not completed network function initialization, a failure occurs, so at step S130, the bootstrap component 101 directly boots the enabling of the alternate version of the system software in the system software component, thereby immediately effecting an automatic rollback of the version of the system software. If it is determined that the acquired network status flag is in the second state, meaning that the last started current system software version has completed network function initialization, there is no failure, so at step S140, the bootstrap component 101 directly enables the last started current version of system software in the system software components to enable a subsequent network connection management attempt.
After the bootstrap component 101 of the device selects the system software after the device is restarted based on the state of the first field portion, the backup version system software or the current version system software in the selected system software component performs the remote service connection operation. Fig. 3 is a process flow diagram illustrating the system software components of an automatic rollback method for a system software version of a device according to an embodiment of the present disclosure. As shown in fig. 3, after the current version of the system software in the system software component 102 is selected at S140, the current version of the system software sets the first field portion of the network status flag to a second state, e.g., to a non-zero state, documenting information displayed on the prior version of the system software device that is capable of completing network initialization, so that a technician may thereafter override the existence of network initialization failure of the device or system software when field technology maintenance is enabled.
Subsequently, at step S220, the current version of system software in the system software component 102 begins attempting to communicate with the remote server 104 over the network, i.e., attempting to send a message request message for a remote service connection to the remote server 104. The current version of system software in the system software component 102 then determines that the sending of the message request message is complete at step S230. If the determination is that the transmission of the message request message is not completed (of course, the response of the server 104 is not obtained), the current version system software in the system software component 102 sets the second field part of the network status flag to the second state, for example, to the "1" state, and records the information that the device can complete the network initialization but cannot transmit the network connection request message under the current version system software, so that the technician does not need to consider that the device or the system software has a problem of receiving in the network connection and directly considers the situation of transmitting failure in the network connection when the technician can perform field technology maintenance. On the other hand, if it is determined at step S230 that the transmission of the message request message has been completed, it is determined at step S250 whether the device receives a response message of the server 104 to the message request message.
If the result of the determination at step S250 is that the device 100 receives a response message of the server 104 to the message request message, the current version of the system software in the system software component 102 sets the second field part of the network status flag to the first state, for example, to the "0" state, and records information that the device can complete network initialization, can send a network connection request message, and can receive a response message of the server 104 to the message request message under the previous version of the system software, so that a technician can remotely learn that the current system is running well, and field technical maintenance is not required. Subsequently, at step S270, the current version of system software in the system software component 102 ends the device auto-rollback operation and enters the normal operating scenario.
If the result of the determination at step S250 is that the device 100 does not receive the response message of the server 104 to the message request message, the current version system software in the system software component 102 sets the second field part of the network status flag to a third state, for example, to a "2" state, and records information indicating that the device can complete network initialization under the previous version system software, can transmit the network connection request message, but cannot receive the response message of the server 104 to the message request message, so that the technician does not need to consider that the device or the system software has a problem of transmitting in network connection when field technology maintenance is enabled, but directly considers the situation of receiving failure in network connection.
Subsequently, at step S290, the current version of system software in the system software component 102 counts the number of times the message request message for the remote service connection is sent to the remote server 104, and determines whether the number of times the message request message is continuously sent exceeds a predetermined number of times, for example, exceeds 2 times, 3 times, 4 times, 5 times or 6 times, and typically the predetermined number of times is 5 times. If it is judged at step S290 that the number of attempts to transmit the message request message does not exceed the predetermined number, the process returns to step S220, and the next round of attempts in network connection management are repeated.
When it is determined in step S290 that the number of attempts to transmit the message request message exceeds the predetermined number, this means that the current version of system software cannot solve the present problem in terms of network connection management. Thus, the current version of the system software resets the network status flag entirely, e.g., resets the status of the first field portion to "0", at step S300, thereby triggering the prior version of the system software to perform a reboot of the device. Thus, after the device is restarted, the bootstrap component 101 of the device marks the network initialization state of the first field portion in the direct acquisition network state flag in the process shown in fig. 2 as the first state, i.e. "0", so that the bootstrap component 101 of the device directly enables the standby version software to implement the version rollback of the system software.
Alternatively, the information of the system software version at each start (including the last system software version started) and the standby system software version may also be recorded in the storage medium for the bootstrap program and the system software to read and write.
While the basic principles of the present disclosure have been described above in connection with specific embodiments, it should be noted that all or any steps or components of the methods and apparatus of the present disclosure can be implemented in hardware, firmware, software, or combinations thereof in any computing device (including processors, storage media, etc.) or network of computing devices, as would be apparent to one of ordinary skill in the art upon reading the present disclosure.
Thus, the objects of the present disclosure may also be achieved by running a program or set of programs on any computing device. The computing device may be a well-known general purpose device. Thus, the objects of the present disclosure may also be achieved by simply providing a program product containing program code for implementing the method or apparatus. That is, such a program product also constitutes the present disclosure, and a storage medium storing such a program product also constitutes the present disclosure. It is apparent that the storage medium may be any known storage medium or any storage medium developed in the future.
It should also be noted that in the apparatus and methods of the present disclosure, it is apparent that the components or steps may be disassembled and/or assembled. Such decomposition and/or recombination should be considered equivalent to the present disclosure. The steps of executing the series of processes may naturally be executed in chronological order in the order described, but are not necessarily executed in chronological order. Some steps may be performed in parallel or independently of each other.
The above detailed description should not be taken as limiting the scope of the present disclosure. It will be apparent to those skilled in the art that various modifications, combinations, sub-combinations and alternatives can occur depending upon design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present disclosure are intended to be included within the scope of the present disclosure.
Claims (8)
1. A method of automatic rollback of a system software version of a device, the device including a bootstrap component, a system software component containing a current version of system software and one or more alternate versions of system software, and a network status flag storage medium, the method comprising:
the bootstrap component resets the network state flag after acquiring the network state flag of the network state flag storage medium when the device is currently started;
the bootstrap component directly boots and enables the standby version system software in the system software component when the first field part of the acquired network state mark is a first state indicating that the device is in the network initialization failure when the device is started up last time;
when the first field part of the bootstrap component is a second state indicating that network initialization is completed when the device is started up last time, the bootstrap component directly starts up the current version system software started up last time in the system software component, and the first field part is set into the second state through the started current version system software; and
the enabled current version system software resets the network status flag upon a predetermined number of initiation of a remote service connection with a remote server and failure, so that the bootstrap component boots up directly to enable the alternate version system software in the system software component after restarting the device.
2. The method of automatic rollback of a system software version of a device of claim 1, further comprising:
the enabled current version of system software ends the automatic rollback operation of the device upon initiating and completing a remote service connection with the remote server.
3. The method of automatic rollback of a system software version of a device of claim 2, further comprising:
the enabled current version system software sets a second field portion to a first state when the enabled current version system software has completed a state of a remote service connection if the acquired network state flags further include the second field portion.
4. The method of automatic rollback of a system software version of a device of claim 1, further comprising:
and under the condition that the acquired network state mark also comprises a second field part, the enabled current version system software sets the second field part into a second state when the message request message is not sent to the server when the remote service connection with the remote server is initiated, and sets the second field part into a third state when the message request message is sent to the server when the remote service connection with the remote server is initiated but the server response message is not acquired.
5. An automatic rollback system for a system software version of a device, the device comprising a bootstrap component, a system software component comprising a current version of system software and one or more alternate versions of system software, and a network status flag storage medium, wherein
The bootstrap component resets the network state flag after acquiring the network state flag of the network state flag storage medium when the device is currently started; and
the bootstrap component directs the enablement of the alternate version of the system software component when the first field portion of the acquired network state flag indicates that the device was in a first state that failed to complete network initialization when the device was previously booted, directs the direct enablement of the current version of the system software component that was previously booted when the device was in a second state that was completed network initialization when the device was previously booted, and places the first field portion in the second state with the current version of the system software that was enabled, and resets the network state flag when the current version of the system software that was enabled initiates a remote service connection with a remote server a predetermined number of times and fails, such that the bootstrap component directs the direct enablement of the alternate version of the system software component after rebooting the device.
6. The system for automatic rollback of a system software version of a device of claim 5, wherein the enabled current version system software ends an automatic rollback operation of the device upon initiating a remote service connection with a remote server and completing the remote service connection.
7. The automatic rollback system of a system software version of a device of claim 6, wherein the enabled current version system software, if the acquired network state flag further comprises a second field portion, places the second field portion in a first state when the enabled current version system software has completed a state of a remote service connection.
8. The system software version automatic rollback system of a device of claim 5, wherein the enabled current version system software, if the acquired network state flag further includes a second field portion, places the second field portion in a second state when a message request message to a server is not complete upon initiating a remote service connection with a remote server, and places the second field portion in a third state when a message request message to a server is complete upon initiating a remote service connection with a remote server but a server response message is not obtained.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010079218.6A CN111309388B (en) | 2020-02-03 | 2020-02-03 | Automatic rollback system and method for system software version of equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010079218.6A CN111309388B (en) | 2020-02-03 | 2020-02-03 | Automatic rollback system and method for system software version of equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111309388A CN111309388A (en) | 2020-06-19 |
| CN111309388B true CN111309388B (en) | 2023-07-21 |
Family
ID=71145750
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010079218.6A Active CN111309388B (en) | 2020-02-03 | 2020-02-03 | Automatic rollback system and method for system software version of equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111309388B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112968744B (en) * | 2021-01-22 | 2023-07-07 | 福建新大陆通信科技股份有限公司 | Log debugging method for emergency broadcasting equipment |
| CN113590213B (en) * | 2021-06-24 | 2023-04-25 | 深圳开源互联网安全技术有限公司 | Component maintenance method, electronic device and storage medium |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5958062A (en) * | 1997-03-19 | 1999-09-28 | Fujitsu Limited | Client/server system and computer system |
| CN1801746A (en) * | 2004-12-31 | 2006-07-12 | 技嘉科技股份有限公司 | Dynamic monitoring and operating method for entity network layer state |
| CN1809816A (en) * | 2003-06-30 | 2006-07-26 | 汤姆森许可贸易公司 | Network equipment and a method for monitoring the start up of such equipment |
| CN101741534A (en) * | 2008-11-14 | 2010-06-16 | 英业达股份有限公司 | Backup system and backup method of multi-sever system |
| CN102388361A (en) * | 2009-04-03 | 2012-03-21 | 微软公司 | Differential file and system restores from peers and the cloud |
| CN102571462A (en) * | 2012-04-06 | 2012-07-11 | 烽火通信科技股份有限公司 | Self-protecting method for long-distance upgrading of optical network unit |
| WO2012163093A1 (en) * | 2011-06-01 | 2012-12-06 | 南京中兴新软件有限责任公司 | Software updating system and method |
| US9189345B1 (en) * | 2013-09-25 | 2015-11-17 | Emc Corporation | Method to perform instant restore of physical machines |
| CN105955846A (en) * | 2016-04-29 | 2016-09-21 | 乐视控股（北京）有限公司 | Method and system for carrying out recovery after upgrade failure of mobile terminal on basis of network |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050132351A1 (en) * | 2003-12-12 | 2005-06-16 | Randall Roderick K. | Updating electronic device software employing rollback |
| US9378011B2 (en) * | 2009-03-19 | 2016-06-28 | Microsoft Technology Licensing, Llc | Network application versioning |
| US20120166665A1 (en) * | 2010-12-22 | 2012-06-28 | Research In Motion Limited | Method and system for selectively performing proxy services |
| JP6740543B2 (en) * | 2016-07-21 | 2020-08-19 | 日本電気株式会社 | Communication device, system, rollback method, and program |
-
2020
- 2020-02-03 CN CN202010079218.6A patent/CN111309388B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5958062A (en) * | 1997-03-19 | 1999-09-28 | Fujitsu Limited | Client/server system and computer system |
| CN1809816A (en) * | 2003-06-30 | 2006-07-26 | 汤姆森许可贸易公司 | Network equipment and a method for monitoring the start up of such equipment |
| CN1801746A (en) * | 2004-12-31 | 2006-07-12 | 技嘉科技股份有限公司 | Dynamic monitoring and operating method for entity network layer state |
| CN101741534A (en) * | 2008-11-14 | 2010-06-16 | 英业达股份有限公司 | Backup system and backup method of multi-sever system |
| CN102388361A (en) * | 2009-04-03 | 2012-03-21 | 微软公司 | Differential file and system restores from peers and the cloud |
| WO2012163093A1 (en) * | 2011-06-01 | 2012-12-06 | 南京中兴新软件有限责任公司 | Software updating system and method |
| CN102571462A (en) * | 2012-04-06 | 2012-07-11 | 烽火通信科技股份有限公司 | Self-protecting method for long-distance upgrading of optical network unit |
| US9189345B1 (en) * | 2013-09-25 | 2015-11-17 | Emc Corporation | Method to perform instant restore of physical machines |
| CN105955846A (en) * | 2016-04-29 | 2016-09-21 | 乐视控股（北京）有限公司 | Method and system for carrying out recovery after upgrade failure of mobile terminal on basis of network |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111309388A (en) | 2020-06-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN113064747B (en) | Fault positioning method, system and device in server starting process | |
| US7991988B2 (en) | Communication device and firmware update method thereof | |
| US9081964B2 (en) | Firmware upgrade error detection and automatic rollback | |
| CN105677398A (en) | Universal embedded computer software on-line upgrading method | |
| CN109587005B (en) | Connection detection method and device, computer equipment and readable storage medium | |
| CN111309388B (en) | Automatic rollback system and method for system software version of equipment | |
| CN102508734B (en) | Operating system recovery method and intelligent equipment | |
| CN100492305C (en) | Fast restoration method of computer system and apparatus | |
| CN110908847A (en) | Abnormity recovery method, system, electronic equipment and storage medium | |
| CN104021014B (en) | A kind of firmware upgrade method based on dual-CPU system | |
| US20210294593A1 (en) | Method, apparatus, device, and storage medium for upgrading vehicle-mounted tbox | |
| CN107315656A (en) | The Embedded PLC software rejuvenation method and PLC of many kernels | |
| CN114116280B (en) | Interactive BMC self-recovery method, system, terminal and storage medium | |
| CN115658113A (en) | Server self-starting method and device, readable storage medium and electronic equipment | |
| CN107070747B (en) | Device, system and method for automatically testing network card network connection stability in network card binding mode | |
| CN111338698A (en) | Method and system for accurately booting server by BIOS (basic input output System) | |
| CN108510287A (en) | Judgment method, electronic device and the computer readable storage medium that client pays a return visit | |
| CN117251333A (en) | Method, device, equipment and storage medium for acquiring hard disk information | |
| CN113918200A (en) | High-efficiency and reliable wireless upgrading method for application program of embedded equipment | |
| CN110442493B (en) | Automatic service management system and method | |
| CN104158843A (en) | Storage unit invalidation detecting method and device for distributed file storage system | |
| CN113553243A (en) | Remote error detection method | |
| CN115951949A (en) | Recovery method and device for configuration parameters of BIOS (basic input output System) and computing equipment | |
| CN115904773A (en) | Memory fault information collection method and device and storage medium | |
| CN114741119A (en) | System starting method and device, computer equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |