CN100525206C - Realizing method and system for automatic restoring equipment fault - Google Patents

Realizing method and system for automatic restoring equipment fault Download PDF

Info

Publication number
CN100525206C
CN100525206C CNB200510080688XA CN200510080688A CN100525206C CN 100525206 C CN100525206 C CN 100525206C CN B200510080688X A CNB200510080688X A CN B200510080688XA CN 200510080688 A CN200510080688 A CN 200510080688A CN 100525206 C CN100525206 C CN 100525206C
Authority
CN
China
Prior art keywords
equipment
program file
server
fault
management
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
Application number
CNB200510080688XA
Other languages
Chinese (zh)
Other versions
CN1859162A (en
Inventor
刁猛
李磊
杨波
张志勇
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to CNB200510080688XA priority Critical patent/CN100525206C/en
Publication of CN1859162A publication Critical patent/CN1859162A/en
Application granted granted Critical
Publication of CN100525206C publication Critical patent/CN100525206C/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Abstract

The present invention relates to an automatic recovery equipment trouble implementation method and system. Said method includes when equipment gone wrong, transmitting recovering request information to management equipment or server; management equipment or server according to received recovering request information transmitting relevant program file information used in fault recovery to equipment; equipment according to received program file recovering fault. The present invention can completely automatically realize equipment trouble recovering.

Description

The implementation method of automatic restoring equipment fault and system
Technical field
The present invention relates to network communications technology field, relate in particular to a kind of implementation method and system of automatic restoring equipment fault.
Background technology
The equipment of operator's local side, the communication equipments such as terminal equipment in the user family all can be managed by opposite equip. in normal course of operation accordingly.Described opposite equip. is called management equipment.Communicate by a kind of management agreement between management equipment and the communication equipment,, comprise equipment is carried out software upgrading, failure diagnosis, configuration management to realize that equipment is carried out normal maintenance management, or the like.
Usually, normal operational outfit also can initiatively be set up with the opposite end server and get in touch, and asks download software to be upgraded or the request msg configuration, and the server of this opposite end can simply be a document storage server, and does not need management function.
Syndeton between communication equipment and management equipment or server as shown in Figure 1, communication equipment and management equipment or server directly couple together by wide area network or local area network (LAN), and adopt a kind of communication protocol to communicate.
Needed all the firmware/programs of device power operation all are stored in the memory that power down do not lose, and as FLASH (flash memory) etc., and are divided into one section and start boot (BOOTP) and application firmware/program.Device power starts or resets when restarting, and carries out the startup boot that is solidificated among the FLASH earlier, jumps to the application program operation by boot at last.
In order to guarantee the fail safe of equipment, the startup boot of equipment can not be revised by on-line software updating, but and application firmware/program generally all is the online updating upgrading in order to satisfy the demand.So except that equipment generation hardware fault, the equipment that can guarantee can start from boot.
Yet, in actual application, when management equipment is carried out firmware/program upgrade to equipment, or the equipment active request is when server download firmware/program upgrade, if in document transmission process, or file verification is insufficient, or in a series of escalation processs such as write device FLASH preservation, mistake has taken place, the fault that can't normally move in the time of then will causing equipment to adopt the firmware of new upgrading/program start.
Except firmware/program error that escalation process takes place, if in equipment running process, there is write operation to FLASH, also may be the required firmware/program crash of equipment operation, and cause equipment normally not start.
Therefore, for guaranteeing the reliable startup of equipment, the firmware/software program of the renewable upgrading in the equipment adopts double copies usually.On equipment, will move required firmware or program software and all carry out the double backup, when a copy of it is damaged, can be from the program software operation of backup.
Because program need be carried out double copies, need take a lot of FLASH space, requires the FLASH space of equipment enough big, has increased the hardware cost of equipment.
For this reason, also adopted another kind of solution at present, be specially: when equipment can not normally start, recovered by the emergent restoring means of this locality; As in the startup boot of equipment, eject the urgent page request user of WEB (World Wide Web) ROMPaq again.
Be not difficult to find out that the realization of this scheme requires equipment to have local maintenance management interface and means, and can't finish the emergent restoring of equipment automatically, but require the user to assist to finish.Therefore, make user's technical capability is had relatively high expectations that promptly the user need understand certain network knowledge, just can realize handling at the fault recovery of equipment.If the user unconditionally operates accordingly, then need operator's on-site maintenance, cause maintenance cost to improve greatly.
Summary of the invention
In view of above-mentioned existing in prior technology problem, the implementation method and the system that the purpose of this invention is to provide a kind of automatic restoring equipment fault, thereby when equipment breaks down can't start the time, can control the recovery of carrying out fault automatically and handle, realize the automatic recovery of equipment fault.
The objective of the invention is to be achieved through the following technical solutions:
The invention provides a kind of implementation method of automatic restoring equipment fault, comprising:
When A, device fails, send recovery request information to management equipment or server;
B, management equipment or server send the program file information that is used for fault recovery accordingly according to the recovery request information that receives to equipment;
C, equipment restart the execution boot, determine to re-execute steps A according to the startup sign in the boot, perhaps, the program file that execution is obtained, and when the startup that the program file that obtains when equipment operation carries out equipment moves successfully, equipment normally moves, otherwise the startup sign of boot is set to re-execute steps A.
Described management equipment or server are arranged at local network and by local network and devices communicating, perhaps are arranged in the Wide Area Network and by Wide Area Network and devices communicating.
Described steps A specifically comprises:
A1, when equipment since the program file fault can't start the time, connect between equipment and management equipment or server;
A2, equipment send recovery request information by the connection of setting up to management equipment or server.
Described steps A comprises:
Equipment is carrying the version information of the program file of the last normal operation of equipment in the recovery request information of management equipment or server transmission;
Perhaps,
Equipment obtains the version information of operable program file to management equipment or server, and selects the version information of definite program file that need obtain;
Described version information is carried on sends to management equipment or server in the recovery request information.
Described step B comprises:
The version information that B1, management equipment or server send according to described equipment sends to equipment with the program file of its corresponding version, and execution in step C;
Perhaps,
B2, management equipment or server at first send to equipment with the program file of current latest edition, and execution in step C, and after the program file failure of carrying out described current latest edition among the step C, the version information that is sent according to described equipment by management equipment or server sends to equipment with the program file of its corresponding version again, and execution in step C again.
Described steps A comprises:
Equipment does not carry the version information of program file in the recovery request information of management equipment or server transmission.
Described step B comprises:
The recovery request information that management equipment or server basis receive sends to equipment with the program file of current latest edition, and execution in step C.
Described step B comprises:
After carrying out the program file failure of obtaining among the step C, the last normally program file of the program file version information correspondence of operation of equipment is sent to equipment by management equipment or server.
Described step B also comprises:
Equipment receive described be used to recover the program file of fault after, the startup that boot is set is masked as from the program file that obtains and starts.
As seen from the above technical solution provided by the invention, realization of the present invention makes the recovery can realize equipment fault fully automatically, and whole failover procedure need not local user's intervention, thereby makes the realization of upgrading restoring more convenient, flexible.
Simultaneously, fully automatic realization makes that also the processing procedure of fault recovery is more safe and reliable to the fault emergent restoring of equipment in the present invention, and can effectively reduce the maintenance cost of this locality maintenance of equipment.
Description of drawings
Fig. 1 be equipment with management equipment or server between be connected the networking structure schematic diagram;
Fig. 2 is the device structure schematic diagram that can recover fault automatically provided by the invention;
Fig. 3 is the automatically restoring fault process schematic diagram on equipment among the present invention;
Fig. 4 is automatically restoring fault process schematic diagram between equipment among the present invention and management equipment or server;
Fig. 5 is the automatic Configuration Framework structural representation of CPE;
Fig. 6 is the BOOT bootstrap program module structural representation of CPE;
Fig. 7 realizes the handling process schematic diagram of fault recovery for CPE;
Fig. 8 is connected the networking structure schematic diagram based between the equipment of File Transfer Protocol and file server;
Fig. 9 is that the equipment fault among Fig. 8 recovers the handling process schematic diagram.
Embodiment
One aspect of the present invention need realize being undertaken by management equipment or server the recovery processing of equipment fault; Need on the one hand in addition to realize finishing automatically of equipment fault recovery, and do not need user's intervention, simultaneously, can not increase the realization cost of device hardware.
Core of the present invention is to realize when causing equipment to start owing to the program file fault in the equipment, then by communicating between equipment and management equipment or server, thereby obtain the program file that can be used for fault recovery on management equipment or the server, the equipment that makes can utilize described program file to carry out the recovery of equipment fault.Be that the present invention has guaranteed when equipment breaks down, can carry out the recovery of fault automatically and handle, guarantee the reliable startup of equipment.
The present invention needs the hypervisor software module structure that is arranged in the equipment of being managed is made amendment in the specific implementation process, amended structure as shown in Figure 2, wherein:
BA_BOOT: be basic boot, promptly present boot.
Fault recovery processing module RE_BOOT: for recovering boot, be the part that the present invention increases setting, be used for the boot of fault recovery; This RE_BOOT also can not online upgrading, RE_BOOT be used to finish and the management equipment of opposite end or server between connect, and use corresponding communication agreement and management equipment or server interaction to finish the program upgrade recovery of equipment automatically.
APP: program file, promptly application firmware/program software is existing program software.
The structure of the system of automatic restoring equipment fault provided by the invention as shown in Figure 2, the concrete structure of described system comprises:
Fault recovery processing module: be arranged at equipment side, equipment is used for when can't start owing to program file breaks down, send recovery request message to management equipment or server, and obtain the program file that is used to carry out fault recovery from management equipment or server, simultaneously, also the program file that obtains is carried out in control, thereby the recovery of carrying out fault in equipment is handled;
Equipment fault processing module: be arranged at management equipment or server side, be used for the recovery request message that the receiving equipment end is sent, and send the program file that is used to carry out fault recovery of its needs according to described recovery request message to equipment.
To be described in detail implementation method of the present invention below.In the method for the present invention, when equipment breaks down, the fault recovery processing module will start corresponding processing procedure on equipment, and and management equipment or server between communicate, thereby obtain to can be used for the damage assessment routine (DAR) file on management equipment or the server, the recovery that utilizes the program file that obtains to carry out fault is afterwards handled.
For clearly demonstrating method of the present invention, below will be respectively in conjunction with Fig. 3 and Fig. 4 to method of the present invention in the specific implementation process, fault recovery processing procedure on equipment, and the fault recovery processing procedure that communicates between equipment and management equipment or server.
When device fails can not be normally when APP starts operation, the inter-process flow process of equipment specifically comprises following processing procedure as shown in Figure 3:
Step 31: device reset starts from BOOTP, carries out BA_BOOT earlier, promptly carries out the startup that basic boot begins to carry out equipment;
Step 32: judging to start sign in BA_BOOT, is normally to start from APP, still breaks down and need start from RE_BOOT;
If start sign is to start from RE_BOOT, and then execution in step 33, otherwise, execution in step 36;
Step 33: restoring running boot RE_BOOT;
Step 34:RE_BOOT and management equipment or server connect and obtain recovery routine RE_APP from management equipment or server;
Step 35: after getting access to described RE_APP program, then the startup sign of BA_BOOT is set to: start from APP; Then, resetting restarts, and promptly execution in step 31, thereby makes and can be again to realize the normal startup of equipment promptly realizing fault recovery by the operation of the APP that newly obtains;
Step 36: judging after the device reset to start sign in BA_BOOT, is to start from APP, and then operation starts APP;
After starting APP, judge whether and can normally start from APP that promptly starting APP successfully still is failure, if success, then execution in step 37, otherwise, execution in step 38;
Step 37:APP normally moves, and the fault recovery processing procedure finishes.
Step 38: if APP starts the operation failure, then the startup sign of BA_BOOT is set to: starts from RE_BOOT, and execution in step 31 again.
When device fails can not be from APP behind normal the startup, the automatic recovery interaction process flow process between equipment and management equipment or server as shown in Figure 4, the equipment that A is managed for quilt among the figure, B is management equipment or server, specifically comprises following processing procedure:
Step 41: device A connects earlier and between management equipment or server B, and promptly equipment moves and set up corresponding the connection in RE_BOOT.
Step 42: equipment reports recovery request message by the connection of setting up to management equipment or server, i.e. fault recovery request, and with the version information of going up subnormal operation, the APP program of the version of going up subnormal operation is downloaded in request to this locality;
Fault has taken place in this step indication equipment, recovers to management equipment or server requests, and the preferential APP program of downloading the version of going up subnormal operation;
If equipment is not noted the version information of subnormal operation then the default request latest edition.
Step 43: device A is downloaded restored version program RE_APP from management equipment or server B appointed positions, promptly is used for the program file of fault recovery.
Step 44: equipment restarts according to the APP that obtains, and promptly starts from the program file that recovers.
Step 45: if starts successfully, equipment connects with management equipment or server after (APP moves being connected of rebuliding), and equipment reports and recovers successfully, comprises the version information of current operation.Simultaneously current version information is recorded in the FLASH memory that power down is not lost in the equipment.
Step 46: if start failure, equipment and management equipment or server connect after (after being device reset, operation RE_BOOT sets up corresponding the connection in RE_BOOT), equipment continues to report the fault recovery request, and with the version information of going up subnormal operation.
Step 47: management equipment or discovering server device upgrade recover not success, and then the designated equipment upgrading is than the older version of last subnormal operation.Being provided with of this step can be avoided occurring downloading same version always, and situation about can not normally recover occurs.
Step 48: equipment is downloaded the legacy version recovery routine from management equipment or server, afterwards, repeats above-mentioned steps 44.
For the present invention there being further understanding, the back will the present invention will be described in detail in conjunction with concrete application example.
To on CPE (subscriber terminal equipment), be applied as example with the present invention program below specific implementation of the present invention will be described explanation; Can communicate by letter by CWMP (CPE wide area network management agreement) between CPE and the ACS (Automatic Configuration Server), also can communicate by letter with the PC that is moving hypervisor by LAN (local area network (LAN)) in this locality.
Wherein, CWMP is the terminal wide area network management agreement TR-069 that DSL family of DSL (Digital Subscriber Line) forum technical work group is worked out.This agreement is intended to the communication between standard CPE and the ACS, and the major function of its support comprises: CPE is configuration and dynamic Service granting, software/firmware upgrade management, state performance supervision and failure diagnosis automatically.
The target of CPE WAN management agreement is a management broadband access terminal (B-NT), but this agreement also can be used for managing the CPE of other types.
The automatic Configuration Framework of CPE of CPE WAN management agreement definition as shown in Figure 5.
When CPE communicates by letter with the management equipment PC by LAN, then the configuration file can be automatically service provider and user set of the hypervisor in the PC is handed down to CPE, and CPE obtains and just can set up WAN according to configuration behind the configuration file and connect.
According to implementation of the present invention, the BOOT boot structure by WAN or LAN and management equipment or server communication CPE specifically comprises following part as shown in Figure 6:
BA_BOOT: be original basic boot;
Fault recovery processing module RE_BOOT: the modular assembly for increasing newly specifically comprises: the driver of CWMP management protocol stack, PPP (point-to-point protocol) or DHCP (DHCP) protocol stack and up WAN device.
When CPE breaks down can't be normally from application program launching the time, the startup flow process of BOOT boot specifically comprises following processing procedure as shown in Figure 7:
Step 71:CPE breaks down and can't normally start, and then starts the minimum system recovery routine from BOOT, and concrete processing procedure is as follows:
(1) when the basic boot BA_BOOT of operation CPE, starts and recover boot RE_BOOT;
(2) recover boot and start the WAN_DRV assembly earlier, finish the initialization of upstream hardware equipment, be specially the initialization of finishing the hardware of communicating by letter between cpe device and network side so that cpe device can be set up and ACS between communicate to connect;
(3) recover boot and from FLASH, read configuration file, be the configuration file of cpe device when normally moving, if configuration file mistake or read failure and then adopt the default configuration of dispatching from the factory, the purpose of obtaining configuration file is the information that needs in the fault recovery processing procedures such as address of obtaining CPE and ACS;
(4) recover boot according to configuration data, start PPP or DHCP protocol stack and obtain the IP address of CPE and the address of ACS; If the address of ACS obtains failure and then obtains from configuration file;
(5) recover boot at last and start the CWMP protocol stack.
Step 72:CPE sets up with ACS and initially is connected, and informs ACS by notice (Inform) message.In the Inform message call, carry " BOOTLOAD " event code;
Device software version in the Inform parameter list is the version number of the normal operation of CPE last time, if version number reads the version of failing then for empty.
Step 73: when ACS received " BOOTLOAD " event code of CPE, identifying was the CPE request of loading upgrading restoring in BOOT that breaks down, and ACS enters that the CPE fault recovery is handled and the daily record of record CPE event of failure.
Step 74:ACS is according to the software version number that CPE reports in BOOTLOAD, and download (Download) the method indication CPE that the calls CPE upgrading restoring that downloads is carrying corresponding fault recovery program file version information in the message;
Default situation is specified and is downloaded the version that CPE reports, because can normally start operation before this version CPE;
If the software version number that CPE reports is for empty, the default appointment latest edition of ACS is upgraded;
In addition, ACS also can customize the program version that CPE recovers loading by the keeper.
Step 75:CPE is by communicating the program file of mutual download ACS appointment to carry out the fault recovery processing with ACS.
After step 76:CPE obtained corresponding program file, CPE restarted, and utilized the program file of downloading acquisition to carry out program start and handle.
Step 77: after CPE recovers successfully, report notice ACS by normal flow, comprise current version information (i.e. the version of Hui Fuing), simultaneously, also the software version number with current normal operation is recorded among the FLASH of equipment, in order to recovery process use next time.
If CPE recovers failure, then repeat above-mentioned corresponding step; ACS need write down the part old version information of CPE correspondence; do not receive the normal recovery notice of CPE as ACS; when receiving the BOOTLOAD request of CPE again, ACS need specify the program file of the older old version of CPE upgrading to issue equipment end to carry out fault recovery.
On conventional equipment, adopt the embodiment of FTP (file transfer protocol (FTP)) below again with the present invention program, as shown in Figure 8, communicate by letter with a common file server by WAN or lan device and to obtain corresponding program file, on server, deposit the version information of equipment and concrete version program file, comprise the program file of old version.
Comprise the File Transfer Protocol stack in the recovery boot of equipment, after device fails started the recovery boot, corresponding processing procedure specifically may further comprise the steps as shown in Figure 9:
Step 91: equipment is set up FTP with the file server of opposite end earlier and is connected.
Step 92: equipment gets access to the version information file of the corresponding program file of the equipment that exists the file server earlier from the opposite end file server.
Step 93: after equipment obtained corresponding version information, the version information of the normal operation of preserving according to corresponding version information and self was determined the version information of the program file that needs obtain;
Relatively whether there is the version of subnormal operation in the version information,, then do not prepare from the program file of the older version of file server download if having then prepare the program file of the version of subnormal operation from the file server download equipment.
Step 94: after equipment is determined the version information of the program file that it need obtain, just can download the program file of the respective version that needs the recovery process from file server.
Step 95: equipment restarts, and the recovery routine file of operation download and upgrade, be specially and utilize the program file that obtains to carry out restarting of equipment, thereby the recovery that realizes fault is handled.
In above-mentioned processing procedure, if equipment can not normally start, i.e. fault recovery failure then repeats above-mentioned steps, asks older old version to carry out fault recovery and handles, and proves an abortion until fault recovery success or recovery process.
In sum, it is more safe and reliable to the fault emergent restoring of equipment that realization of the present invention makes, and do not need local user's intervention and realize fault recovery fully automatically, thereby effectively reduced the maintenance cost of this locality maintenance of equipment.
The above; only for the preferable embodiment of the present invention, but protection scope of the present invention is not limited thereto, and anyly is familiar with those skilled in the art in the technical scope that the present invention discloses; the variation that can expect easily or replacement all should be encompassed within protection scope of the present invention.Therefore, protection scope of the present invention should be as the criterion with the protection range of claim.

Claims (9)

1, a kind of implementation method of automatic restoring equipment fault is characterized in that, comprising:
When A, device fails, send recovery request information to management equipment or server;
B, management equipment or server send the program file information that is used for fault recovery accordingly according to the recovery request information that receives to equipment;
C, equipment restart the execution boot, determine to re-execute steps A according to the startup sign in the boot, perhaps, the program file that execution is obtained, and when the startup that the program file that obtains when equipment operation carries out equipment moves successfully, equipment normally moves, otherwise the startup sign of boot is set to re-execute steps A.
2, the implementation method of automatic restoring equipment fault according to claim 1, it is characterized in that, described management equipment or server are arranged at local network and by local network and devices communicating, perhaps are arranged in the Wide Area Network and by Wide Area Network and devices communicating.
3, the implementation method of automatic restoring equipment fault according to claim 1 is characterized in that, described steps A specifically comprises:
A1, when equipment since the program file fault can't start the time, connect between equipment and management equipment or server;
A2, equipment send recovery request information by the connection of setting up to management equipment or server.
4, the implementation method of automatic restoring equipment fault according to claim 1 is characterized in that, described steps A comprises:
Equipment is carrying the version information of the program file of the last normal operation of equipment in the recovery request information of management equipment or server transmission;
Perhaps,
Equipment obtains the version information of the program file that can use to management equipment or server, and selects the version information of definite program file that need obtain;
Described version information is carried on sends to management equipment or server in the recovery request information.
5, the implementation method of automatic restoring equipment fault according to claim 4 is characterized in that, described step B comprises:
The version information that B1, management equipment or server send according to described equipment sends to equipment with the program file of its corresponding version, and execution in step C;
Perhaps,
B2, management equipment or server at first send to equipment with the program file of current latest edition, and execution in step C, and after the program file failure of carrying out described current latest edition among the step C, the version information that is sent according to described equipment by management equipment or server sends to equipment with the program file of its corresponding version again, and execution in step C again.
According to the implementation method of claim 1 or 4 described automatic restoring equipment faults, it is characterized in that 6, described steps A comprises: equipment does not carry the version information of program file in the recovery request information of management equipment or server transmission.
7, the implementation method of automatic restoring equipment fault according to claim 6 is characterized in that, described step B comprises:
The recovery request information that management equipment or server basis receive sends to equipment with the program file of current latest edition, and execution in step C.
According to the implementation method of claim 1,4 or 7 described automatic restoring equipment faults, it is characterized in that 8, described step B comprises:
After carrying out the program file failure of obtaining among the step C, the last normally program file of the program file version information correspondence of operation of equipment is sent to equipment by management equipment or server.
According to the implementation method of claim 1,4 or 7 described automatic restoring equipment faults, it is characterized in that 9, described step B also comprises:
Equipment receive described be used to recover the program file of fault after, the startup that boot is set is masked as from the program file that obtains and starts.
CNB200510080688XA 2005-06-15 2005-07-06 Realizing method and system for automatic restoring equipment fault Active CN100525206C (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CNB200510080688XA CN100525206C (en) 2005-06-15 2005-07-06 Realizing method and system for automatic restoring equipment fault

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN200510078421.7 2005-06-15
CN200510078421 2005-06-15
CN200510080177.8 2005-06-30
CNB200510080688XA CN100525206C (en) 2005-06-15 2005-07-06 Realizing method and system for automatic restoring equipment fault

Publications (2)

Publication Number Publication Date
CN1859162A CN1859162A (en) 2006-11-08
CN100525206C true CN100525206C (en) 2009-08-05

Family

ID=37298029

Family Applications (1)

Application Number Title Priority Date Filing Date
CNB200510080688XA Active CN100525206C (en) 2005-06-15 2005-07-06 Realizing method and system for automatic restoring equipment fault

Country Status (1)

Country Link
CN (1) CN100525206C (en)

Families Citing this family (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101431428B (en) * 2007-11-09 2011-07-27 中国电信股份有限公司 Security monitoring service recovery method and system
WO2009082836A1 (en) * 2007-12-26 2009-07-09 Zte Corporation Fault handling method and device
CN102316503B (en) * 2011-09-30 2014-09-10 大唐移动通信设备有限公司 Fault processing method for remote radio unit (RRU) and device
CN102693166B (en) * 2012-05-10 2015-04-22 华为技术有限公司 Method, device and system for processing information
US9798608B2 (en) * 2013-02-28 2017-10-24 Hewlett Packard Enterprise Development Lp Recovery program using diagnostic results
CN103731301A (en) * 2013-12-06 2014-04-16 南京智达康无线通信科技股份有限公司 Dual backup achieving method of remote network system
CN106209406A (en) * 2015-05-06 2016-12-07 中兴通讯股份有限公司 Process the method and device of TR-069 message
CN106248415A (en) * 2016-08-16 2016-12-21 珠海格力电器股份有限公司 Equipment fault monitoring method, Apparatus and system
CN106648973A (en) * 2016-11-18 2017-05-10 济南中维世纪科技有限公司 NVR software partner repair method and system
JP2018170618A (en) * 2017-03-29 2018-11-01 Kddi株式会社 Automatic failure recovery system, control apparatus, procedure creation apparatus, and program
CN110083493A (en) * 2018-01-25 2019-08-02 厦门雅迅网络股份有限公司 A kind of embedded system failure self-recovery method, terminal device and storage medium
CN109213629B (en) * 2018-07-02 2022-04-22 广东睿江云计算股份有限公司 Method and device for self-recovering joint file system fault
CN109542660B (en) * 2018-11-15 2022-06-10 北京小米移动软件有限公司 Fault processing method and device
CN109542486A (en) * 2018-11-23 2019-03-29 珠海格力电器股份有限公司 A kind of terminal device firmware upgrade system and its method and air-conditioning
CN111813427A (en) * 2019-04-12 2020-10-23 杭州海康威视数字技术股份有限公司 Equipment repairing method and device, electronic equipment and storage medium
CN110300103A (en) * 2019-06-20 2019-10-01 厦门市美亚柏科信息股份有限公司 Wireless data detecting devices, restorative procedure and backup method
CN110879765B (en) * 2019-11-15 2022-01-14 飞天诚信科技股份有限公司 Method and device for avoiding terminal abnormity
CN113050959A (en) * 2019-12-26 2021-06-29 深圳Tcl新技术有限公司 System upgrading method, terminal and storage medium
CN113542318B (en) * 2020-04-15 2023-04-14 杭州海康威视数字技术股份有限公司 Equipment fault repairing method

Also Published As

Publication number Publication date
CN1859162A (en) 2006-11-08

Similar Documents

Publication Publication Date Title
CN100525206C (en) Realizing method and system for automatic restoring equipment fault
EP1887759B1 (en) Method and system for realizing automatic restoration after a device failure
US7809836B2 (en) System and method for automating bios firmware image recovery using a non-host processor and platform policy to select a donor system
CN102238093B (en) Service interruption prevention method and device
RU2417415C2 (en) Method and system for deploying software, software deployment server and user server
CN100545809C (en) A kind of method for upgrading software and system thereof
EP2456257B1 (en) Method and system for upgrading wireless data card
EP2582089A1 (en) System and method for implementing automatic configuration for equipments
US20070266120A1 (en) System and method for handling instructions in a pre-boot execution environment
CN102375764A (en) Managing operating system deployment failure
KR100952585B1 (en) Method and system for automatic recovery of an embedded operating system
CN104915226A (en) Network device software starting method, device and network device
CN101453374A (en) On-line updating method and system for network appliance
CN112948008B (en) Method for managing physical bare machine based on Ironic
CN112732412B (en) Service configuration file processing method and device, storage medium and electronic equipment
JP5387767B2 (en) Update technology for running programs
JP2006113754A (en) Software update device and method
CN114006901B (en) Embedded network equipment cover-dismounting-free firmware upgrading method and system
JPH117382A (en) Version-up method for firmware
JP2011053780A (en) Restoration system, restoration method and backup control system
CN111769966B (en) Clone upgrading method, system and application
CN111338667B (en) Application program APP upgrading method and device
CN110780943B (en) Method and system for unifying firmware of slave equipment
JP2006172098A (en) Packet communication device, rebooting method in packet communication device, and program
CN111083001B (en) Firmware abnormity detection method and device

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
C10 Entry into substantive examination
SE01 Entry into force of request for substantive examination
C14 Grant of patent or utility model
GR01 Patent grant