CN104901828A - Equipment end fault removing method - Google Patents
Equipment end fault removing method Download PDFInfo
- Publication number
- CN104901828A CN104901828A CN201510136767.1A CN201510136767A CN104901828A CN 104901828 A CN104901828 A CN 104901828A CN 201510136767 A CN201510136767 A CN 201510136767A CN 104901828 A CN104901828 A CN 104901828A
- Authority
- CN
- China
- Prior art keywords
- equipment end
- weighted value
- recovery scenario
- recovery
- file
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 48
- 230000008439 repair process Effects 0.000 claims abstract description 46
- 238000011084 recovery Methods 0.000 claims description 109
- 238000013024 troubleshooting Methods 0.000 claims description 28
- 230000000052 comparative effect Effects 0.000 claims description 9
- 230000004044 response Effects 0.000 claims description 2
- 230000008030 elimination Effects 0.000 abstract 1
- 238000003379 elimination reaction Methods 0.000 abstract 1
- 230000000875 corresponding effect Effects 0.000 description 15
- 230000008569 process Effects 0.000 description 5
- 230000000694 effects Effects 0.000 description 3
- 230000008901 benefit Effects 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 2
- 230000015556 catabolic process Effects 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 230000009467 reduction Effects 0.000 description 2
- 241001269238 Data Species 0.000 description 1
- 230000004888 barrier function Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 230000002596 correlated effect Effects 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 230000004069 differentiation Effects 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- NHDHVHZZCFYRSB-UHFFFAOYSA-N pyriproxyfen Chemical compound C=1C=CC=NC=1OC(C)COC(C=C1)=CC=C1OC1=CC=CC=C1 NHDHVHZZCFYRSB-UHFFFAOYSA-N 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
Abstract
A method for eliminating equipment end faults is suitable for a server. The equipment side fault elimination method comprises the following steps. Receiving a record file, wherein the record file is transmitted from the equipment terminal. One of a plurality of repair schemes is generated according to the record file, wherein each repair scheme corresponds to a weight value. One of the repair solutions is provided to the device side. And receiving a result file responded by the equipment terminal, wherein the result file corresponds to the repair scheme. And adjusting the weight value of the repair scheme according to the result file, and returning to the step of receiving the record file. Therefore, the self-learning function of the equipment-side fault removal method is achieved, and the success rate and convenience of equipment-side fault removal are improved.
Description
Technical field
The present invention has about a kind of equipment end troubleshooting methodology, particularly a kind of equipment end troubleshooting methodology being suitable for server.
Background technology
In general, all can carry out online between server and equipment end, and equipment end is often distributed in different entities place, and in system, present different records, when equipment end breaks down, traditional troubleshooting methodology all relies on the fault of artificial discovering device end, then is noted down by the system of artificial Pinging device end one by one and judged reason, finally according to failure cause by removing barriers manually.When the physical distance that equipment end One's name is legion or equipment end scatter place is longer, traditional equipment end management method manual time that also relative expenses is too much and efficiency is low.
Traditional equipment end troubleshooting methodology, needs to judge to adopt which kind of method to fix a breakdown by artificial experience, except being highly dependent on except artificial experience, also failing effectively to note down the solution effect of various recovery scenario, therefore cannot propose effective recovery scenario fast.Therefore, server space that the troubleshooting methodology with equipment end is still improved.
Summary of the invention
In view of this, the invention provides a kind of equipment end troubleshooting methodology, use the efficiency and convenience that increase equipment end failture evacuation.
The invention provides a kind of equipment end troubleshooting methodology, be suitable for server.This equipment end troubleshooting methodology comprises the following steps.Receive record file, wherein note down document backup from equipment end.One of them of multiple recovery scenario is produced, wherein each recovery scenario corresponding weighted value respectively according to record file.One of them providing recovery scenario is to equipment end.The destination file of receiving equipment end response, the wherein corresponding recovery scenario of destination file.
In one embodiment, aforementioned device end troubleshooting methodology more comprises the weighted value according to destination file adjustment recovery scenario, and gets back to the step of receiving record file.
In one embodiment, the weighted value of aforementioned adjustment recovery scenario can comprise the following steps.According to destination file, obtain reparation message.According to the state of repairing message, calculate the success rate of recovery scenario.According to success rate, the weighted value of adjustment recovery scenario.
In one embodiment, the weighted value of aforementioned adjustment recovery scenario also can comprise the following steps.According to destination file, obtained for one first repair time.The second repair time that first repair time of comparison and all the other recovery scenarios record, to produce comparative result.According to comparative result, the weighted value of adjustment recovery scenario.
Equipment end troubleshooting methodology provided by the present invention, after receiving the record file that equipment end sends, corresponding recovery scenario is just produced according to this by server, and server end is after receiving the destination file that equipment end responds, and adjusts the weighted value of recovery scenario according to this.Thus, can according to success rate or the repair time of repairing result, adjustment server provides the order of recovery scenario, reaches the function of equipment end troubleshooting methodology self-teaching, to increase success rate and the convenience of equipment end failture evacuation, and the time of effective reduction personnel Cha Xiu.
The above explanation about content of the present invention and the explanation of following execution mode in order to demonstration and explanation spirit of the present invention and principle, and provide patent claim of the present invention further to explain.
Accompanying drawing explanation
The schematic diagram that between the equipment end of Fig. 1 disclosed by one embodiment of the invention and server, data transmit.
The flow chart of the equipment end troubleshooting methodology of Fig. 2 disclosed by one embodiment of the invention.
Fig. 3 is the detail flowchart of first embodiment of the step S210 of Fig. 2.
Fig. 4 is the detail flowchart of second embodiment of the step S210 of Fig. 2.
[symbol description]
100 servers
101,102,103 equipment end
Embodiment
Below detailed features of the present invention and advantage is described in embodiments in detail, its content is enough to make any relevant art of haveing the knack of understand technology contents of the present invention and implement according to this, and content, claims and the accompanying drawing disclosed by this specification, any those skilled in the art can understand the object and advantage that the present invention is correlated with easily.Following embodiment further describes viewpoint of the present invention, but non-to limit category of the present invention anyways.
As employed some vocabulary to censure specific components in the middle of specification and claims.Those skilled in the art should understand, and hardware manufacturer may call same assembly with different noun.This specification and claims book is not used as with the difference of title the mode distinguishing assembly, but is used as the criterion of differentiation with assembly difference functionally." comprising " as mentioned in the middle of specification and claims is in the whole text an open language, therefore should be construed to " including but not limited to "." roughly " refer to that in receivable error range, those skilled in the art can solve the technical problem within the scope of certain error, reach described technique effect substantially.Specification subsequent descriptions is implement every execution mode of the application, and right described description is for the purpose of the rule that the application is described, and is not used to the scope limiting the application.The protection range of the application is when being as the criterion depending on the appended claims person of defining.
Also it should be noted that, term " comprises ", " comprising " or its any other variant are intended to contain comprising of nonexcludability, thus make to comprise the process of a series of key element, method, commodity or system and not only comprise those key elements, but also comprise other key elements clearly do not listed, or also comprise by the intrinsic key element of this process, method, commodity or system.When not more restrictions, the key element limited by statement " comprising ... ", and be not precluded within process, method, commodity or the system comprising described key element and also there is other identical element.
The schematic diagram that between the equipment end of Fig. 1 disclosed by one of the present invention embodiment and server, data transmit.The flow chart of the equipment end troubleshooting methodology of Fig. 2 disclosed by one of the present invention embodiment.The equipment end troubleshooting methodology of the present embodiment is suitable for server 100, namely for the method for server 100 remover apparatus end 101,102,103 fault.Wherein, equipment end 101,102,103 is such as network camera, networked environment transducer or the communication apparatus with network on-line, but the kind of equipment end is not as limit.For convenience of description, in following every embodiment, equipment end 101,102,103 all only with equipment end 101 for representative.
In step S202, receive record file (log file), wherein note down document backup from equipment end 101.That is, server 100 can receiving equipment end 101 sends record file, and this record file to be such as equipment end 101 run or equipment end 101 performs the result of a certain program.The transmission of aforementioned record file can be adopt timed sending pattern according to setting, or adopts not timing sending mode according to the running status of equipment end 101.Further, device address information and fault message that file such as comprises equipment end 101 is noted down.
Furthermore, the master data of device address information such as in order to provide server 100 to understand equipment end 101, the master datas such as such as device name, device category, IP address, online type, available machine time and running time, but master data is not as limit.Fault message such as in order to the state that provides server 100 to understand equipment end 101 fault and type, fault messages such as such as failure mode, failure cause, fault time and trouble duration, but fault message is not as limit.
In step S204, select one of them of multiple recovery scenario (solution) according to record file, wherein each recovery scenario corresponding weighted value respectively.That is, when server 100 receives the record file that equipment end 101 sends, server 100, according to the information of current record file, such as, from the multiple different recovery scenario stored by its database, picks out the recovery scenario that can carry out failture evacuation to equipment end 101.Furthermore, aforesaid multiple recovery scenario goes back correspondence one weighted value respectively, so that server 100 can pick out applicable recovery scenario according to aforementioned weighted value.
In step S206, one of them providing multiple recovery scenario is to equipment end 101.That is, after selecting suitable recovery scenario, selected recovery scenario is supplied to equipment end 101 by server 100, to carry out the operation of failture evacuation.Aforementioned recovery scenario such as comprises repairs instruction and/or repair procedure.
In the present embodiment, server 100 is provided to the weighted value of one of them of the recovery scenario of equipment end 101 such as weighted value in each recovery scenario is maximum.In other words, server 100 such as can sort to aforementioned weighted value, according to weighted value size, to select the recovery scenario that weighted value is maximum, carry out failture evacuation for equipment end 101 from multiple recovery scenario.
In step S208, the destination file (result file) that receiving equipment end is responded, the wherein corresponding recovery scenario of destination file.That is, the recovery scenario (such as weighted value is maximum) that equipment end 101 can provide according to server 100, carry out failture evacuation, with the destination file of the corresponding aforementioned recovery scenario of output, in destination file, record performs the relevant information of recovery scenario, such as repair result success or not, repair time, aforementioned result file is sent to server 100 by equipment end 101 again.
In step S210, according to the weighted value of destination file adjustment recovery scenario.That is, when server 100 receives the destination file that equipment end 101 sends, server 100 previously can be supplied to the weighted value of the maximum recovery scenario of the weighted value of equipment end 101 according to the adjustment of the message of destination file, that is aforesaid weighted value is upgraded, in order to when server 100 needs to provide recovery scenario to equipment end 101 next time, can sort according to the weighted value after adjustment, to pick out the recovery scenario that applicable equipment end 101 carries out failture evacuation.
Then, after step S210 is complete, again can get back to step S202, and repeat step S202 to S210, to continue to monitor equipment end 101 and the operation of failture evacuation, and the related procedure such as the weighted value of the result adjustment recovery scenario of corresponding failture evacuation.
The explanation of above is known, server 100 is for carrying out the troubleshooting methodology of equipment end 101, all need first to receive the record file that each equipment end 101,102,103 provides, with obtain record file in device address information and fault message, and from multiple recovery scenario, select applicable recovery scenario (recovery scenario that such as weighted value is maximum) according to the information of record file, reoffer this be applicable to recovery scenario to equipment end 101,102,103, carry out the reparation of failture evacuation for equipment end 101,102,103.In addition, server 100 also can receive and the destination file responded according to equipment end 101,102,103 further, the weighted value of the recovery scenario of adjustment corresponding to destination file, using as the foundation selecting applicable recovery scenario next time.
Above embodiment illustrates, be the weighted value being provided to one of them of the recovery scenario of equipment end 101 for server 100 is that in each recovery scenario, weighted value is maximum, but the present invention is not as limit.
In an alternative embodiment of the invention, server 100 is provided to the weighted value of one of them of the recovery scenario of equipment end 101 also can be that in each recovery scenario, weighted value is minimum.In other words, server 100 such as can sort to aforementioned weighted value, according to weighted value size, to select the recovery scenario that weighted value is minimum, carry out failture evacuation for equipment end 101 from multiple recovery scenario.In addition, aforementioned recovery scenario such as comprises reparation instruction and/or repair procedure.
Fig. 3 is the detail flowchart of first embodiment of the step S210 of Fig. 2.In step S312, according to destination file, obtain reparation message.That is, the destination file that server 100 sends according to equipment end 101, equipment end 101 carries out the reparation message of failture evacuation.In the present embodiment, repairing message is such as repair success or repairing failure, but repairs message not as limit, and repairing message also can be such as that the reparation number of times that equipment state, repair time and recovery scenario are corresponding etc. repairs message.
In step S314, according to the state of repairing message, calculate the success rate of recovery scenario.Wherein, the state of message is repaired for repairing success or repairing failure.For example, when reparation message is that when repairing successfully (such as the fault of successful remover apparatus end 101), then server 100 such as increases the number of success of this kind of recovery scenario.When repairing message and being repairing failure the fault of remover apparatus end 101 (such as cannot), then server 100 increases the frequency of failure of this kind of recovery scenario.Then, server 100 according to the number of success of aforesaid statistical and the frequency of failure, can calculate the success rate that this recovery scenario corresponding device end 101 carries out failture evacuation.
In step S316, according to success rate, the weighted value of adjustment recovery scenario.That is, equipment end 101 has various faults type, such as B1-B10, and every type all may correspond to multiple recovery scenario such as F1-F5.In often kind of fault type, server 100 can according to the success rate of each recovery scenario, the weighted value of adjustment recovery scenario.In the present embodiment, weighted value size is directly proportional to success rate height.
For example, when the success rate of carrying out fault type B1 with recovery scenario F1 is higher, represent recovery scenario F1 and be easier to repair fault type B1, server 100 will improve the weighted value of recovery scenario F1 in fault type B1.So, when equipment end 101 to break down type B 1 next time equally, server 100 will preferentially select the recovery scenario F1 of high success rate, carry out failture evacuation for equipment end 101, make equipment end 101 recovery mode of operation as early as possible.
In other words, when the success rate of carrying out fault type B2 with recovery scenario F2 is lower, represents recovery scenario F2 and not easily repair fault type B2, server 100 will reduce the weighted value of recovery scenario F2 at fault type B2.So, when breaking down type B 2 equally next time, server 100, by selecting other recovery scenarios (such as recovery scenario F3) in advance, carries out failture evacuation for equipment end 101.
Fig. 4 is the detail flowchart of second embodiment of the step S210 of Fig. 2.
In step S412, according to destination file, obtained for the first repair time.That is, the destination file that server 100 sends according to equipment end 101, equipment end 101 repair successfully spent by first repair time T1.In the present embodiment, first repair time T1 be such as that equipment end 101 carries out failture evacuation via recovery scenario, recovery scenario by equipment end 101 from fault mode reparation to mode of operation spent by activity duration, but first repair time T1 not as limit.
In step S414, compare first repair time T1 and remaining recovery scenario record second repair time T2, to produce comparative result.For example, equipment end 101 can have various faults type, such as B1-B10, and every type all may correspond to multiple recovery scenario such as F1-F5.Suppose that server 100 provides the recovery scenario F1 of fault type B1, and equipment end 101 carries out corresponding failture evacuation process according to this, then its time spent by failture evacuation process be such as first repair time T1.Then, server 100 can by the first repair time in destination file, T1 and the recovery scenario F2-F5 of other type B 1 of fixing a breakdown expended second repair time T2 compare, and produce comparative result.Wherein, aforementioned comparative result be such as first repair time T1 be greater than second repair time T2, or first repair time T1 be less than second repair time T2.
In step S416, server 100, according to comparative result, adjusts the weighted value of recovery scenario.That is, at corresponding fault type B1, server 100 can according to aforesaid comparative result (that is length repair time of each recovery scenario), the weighted value of adjustment recovery scenario.In the present embodiment, the weighted value size corresponding to aforementioned recovery scenario is such as inversely proportional to length repair time.
For example, when carrying out the repair time of fault type B1 more in short-term with recovery scenario F1, the efficiency representing recovery scenario F1 reparation fault type B1 is higher, then server 100 will improve the weighted value of recovery scenario F1 in fault type B1.So, when equipment end 101 to break down type B 1 next time equally, server 100, by preferentially selecting short recovery scenario F1 repair time, carries out failture evacuation for equipment end 101, makes equipment end 101 recovery mode of operation as early as possible.
In other words, when the repair time of carrying out fault type B2 with recovery scenario F2 is longer, the efficiency representing recovery scenario F2 reparation fault type B2 is lower, and server 100 will reduce the weighted value of recovery scenario F2 at fault type B2.So, when equipment end 101 to break down type B 2 next time equally, server 100, by selecting other recovery scenarios (such as recovery scenario F3) in advance, carries out failture evacuation for equipment end 101.
The equipment end troubleshooting methodology that the present embodiment provides, corresponding recovery scenario is just produced according to this after receiving by server the record file that equipment end sends, and equipment end just produces corresponding destination file according to this after the recovery scenario receiving server and provide carries out failture evacuation, server is again according to the weighted value of destination file adjustment recovery scenario.Thus, according to success rate or the repair time of repairing result, adjustment server provides the order of recovery scenario, reaches the function of equipment end troubleshooting methodology self-teaching, to increase success rate and the convenience of equipment end failture evacuation, and the time of effective reduction personnel Cha Xiu.
Method of the present invention, or specific kenel or its part, can exist with the kenel of program code.Program code can be stored in tangible media, as floppy disk, disc, hard disk or any other machine-readable (as embodied on computer readable) Storage Media, also or be not limited to the computer program of external form, wherein, when program code is by machine, as computer load and perform time, this machine becomes to participate in device of the present invention.Program code also can pass through some transfer mediums, as electric wire or cable, optical fiber or any transmission kenel transmit, wherein, when program code is by machine, as computer receive, load and perform time, this machine becomes to participate in device of the present invention.When general service processing unit implementation, program code provides a class of operation to be similar to the unique apparatus of application particular logic circuit in conjunction with processing unit.
Although the present invention discloses as above with aforesaid embodiment, so itself and be not used to limit the present invention.Without departing from the spirit and scope of the present invention, the change of doing and retouching, all belong to scope of patent protection of the present invention.The protection range defined about the present invention please refer to appending claims.
Claims (9)
1. an equipment end troubleshooting methodology, is suitable for a server, it is characterized in that, this equipment end troubleshooting methodology comprises:
Receive a record file, wherein this record document backup is from an equipment end;
One of them of multiple recovery scenario is selected, wherein those recovery scenarios corresponding weighted value respectively according to this record file;
One of them providing those recovery scenarios is to this equipment end; And
Receive a destination file of this equipment end response, wherein this destination file is to should recovery scenario.
2. equipment end troubleshooting methodology according to claim 1, is characterized in that, wherein this record file comprises a device address information and a fault message.
3. equipment end troubleshooting methodology according to claim 1, is characterized in that, this weighted value being wherein provided to one of them of those recovery scenarios of this equipment end is maximum in those weighted values; Or this weighted value being wherein provided to one of them of those recovery scenarios of this equipment end is minimum in those weighted values.
4. equipment end troubleshooting methodology according to claim 1, is characterized in that, more comprises this weighted value adjusting this recovery scenario according to this destination file, and gets back to the step of this this log file of reception.
5. equipment end troubleshooting methodology according to claim 4, is characterized in that, this weighted value wherein adjusting this recovery scenario comprises:
According to this destination file, obtain a reparation message;
According to the state of this reparation message, calculate a success rate of this recovery scenario; And
According to this success rate, adjust this weighted value of this recovery scenario.
6. equipment end troubleshooting methodology according to claim 5, is characterized in that, wherein this weighted value size is directly proportional to this success rate height; Or wherein this weighted value size and this success rate height are inversely proportional to.
7. equipment end troubleshooting methodology according to claim 3, is characterized in that, this weighted value wherein adjusting this recovery scenario comprises:
According to this destination file, obtained for one first repair time;
The second repair time that this first repair time of comparison and remaining those recovery scenario record, to produce a comparative result; And
According to this comparative result, adjust this weighted value of this recovery scenario.
8. equipment end troubleshooting methodology according to claim 7, is characterized in that, wherein this weighted value size and those repair time length be inversely proportional to; Or wherein this weighted value size is directly proportional to those of length repair time.
9. equipment end troubleshooting methodology according to claim 1, is characterized in that, wherein this recovery scenario more comprises a reparation instruction and/or a repair procedure.
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| TW104102121 | 2015-01-22 | ||
| TW104102121A TW201627883A (en) | 2015-01-22 | 2015-01-22 | Equipment troubleshooting method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN104901828A true CN104901828A (en) | 2015-09-09 |
Family
ID=54034232
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510136767.1A Pending CN104901828A (en) | 2015-01-22 | 2015-03-26 | Equipment end fault removing method |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN104901828A (en) |
| TW (1) | TW201627883A (en) |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106201757A (en) * | 2016-07-12 | 2016-12-07 | 网易（杭州）网络有限公司 | A kind of abnormality eliminating method and device |
| CN107332722A (en) * | 2017-08-31 | 2017-11-07 | 郑州云海信息技术有限公司 | The method for removing and system of a kind of fault message |
| CN109901544A (en) * | 2017-12-07 | 2019-06-18 | 开利公司 | Refrigeration system, the fault diagnosis system for it, method for diagnosing faults and controller and storage medium |
| CN110687897A (en) * | 2019-10-28 | 2020-01-14 | 北京小米智能科技有限公司 | Troubleshooting method, troubleshooting device, and troubleshooting system |
| CN110825923A (en) * | 2019-10-25 | 2020-02-21 | 袁茂银 | Underground cable fault repairing method and device based on single model |
| CN110837898A (en) * | 2019-10-25 | 2020-02-25 | 袁茂银 | Underground cable fault repairing method and device based on model selection |
| CN110851670A (en) * | 2019-10-25 | 2020-02-28 | 袁茂银 | Underground cable fault repairing method and device |
| CN110866839A (en) * | 2019-10-25 | 2020-03-06 | 袁茂银 | Underground cable fault repairing method and device based on multiple models |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| TW200614019A (en) * | 2004-06-22 | 2006-05-01 | Taiwan Semiconductor Mfg Co Ltd | System and method to build, retrieve and track information in a knowledge database for trouble shooting purposes |
| CN102663537A (en) * | 2012-03-13 | 2012-09-12 | 凯里供电局 | Maintenance system of power equipment based on risk assessment |
| US20130035883A1 (en) * | 2011-08-01 | 2013-02-07 | Ramon Juan San Andres | Systems and methods to monitor the operation of a power generation system |
-
2015
- 2015-01-22 TW TW104102121A patent/TW201627883A/en unknown
- 2015-03-26 CN CN201510136767.1A patent/CN104901828A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| TW200614019A (en) * | 2004-06-22 | 2006-05-01 | Taiwan Semiconductor Mfg Co Ltd | System and method to build, retrieve and track information in a knowledge database for trouble shooting purposes |
| US20130035883A1 (en) * | 2011-08-01 | 2013-02-07 | Ramon Juan San Andres | Systems and methods to monitor the operation of a power generation system |
| CN102663537A (en) * | 2012-03-13 | 2012-09-12 | 凯里供电局 | Maintenance system of power equipment based on risk assessment |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106201757A (en) * | 2016-07-12 | 2016-12-07 | 网易（杭州）网络有限公司 | A kind of abnormality eliminating method and device |
| CN107332722A (en) * | 2017-08-31 | 2017-11-07 | 郑州云海信息技术有限公司 | The method for removing and system of a kind of fault message |
| CN109901544A (en) * | 2017-12-07 | 2019-06-18 | 开利公司 | Refrigeration system, the fault diagnosis system for it, method for diagnosing faults and controller and storage medium |
| CN110825923A (en) * | 2019-10-25 | 2020-02-21 | 袁茂银 | Underground cable fault repairing method and device based on single model |
| CN110837898A (en) * | 2019-10-25 | 2020-02-25 | 袁茂银 | Underground cable fault repairing method and device based on model selection |
| CN110851670A (en) * | 2019-10-25 | 2020-02-28 | 袁茂银 | Underground cable fault repairing method and device |
| CN110866839A (en) * | 2019-10-25 | 2020-03-06 | 袁茂银 | Underground cable fault repairing method and device based on multiple models |
| CN110687897A (en) * | 2019-10-28 | 2020-01-14 | 北京小米智能科技有限公司 | Troubleshooting method, troubleshooting device, and troubleshooting system |
Also Published As
| Publication number | Publication date |
|---|---|
| TW201627883A (en) | 2016-08-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN104901828A (en) | Equipment end fault removing method | |
| CN110401662B (en) | Industrial control equipment fingerprint identification method and storage medium | |
| EP2455897B1 (en) | Methods and systems involving power system grid management | |
| CN106301823B (en) | Fault warning method and device for key component and big data management system | |
| CN104468201B (en) | A kind of offline auto-deleted method of network equipment and equipment | |
| CN102904977B (en) | Network address allocation method, server and node | |
| CN103227662A (en) | Safety detection method and system of electric power communication equipment based on state control | |
| CN112367345A (en) | Data processing method, server device and computer readable storage medium | |
| JP5949785B2 (en) | Information processing method, apparatus and program | |
| CN111130917B (en) | Line testing method, device and system | |
| CN105094860A (en) | Terminal software online upgrade method and device | |
| CN105978939A (en) | Data downloading method and data downloading device | |
| CN113411209A (en) | Distributed password service full-link detection system and method | |
| CN110445658B (en) | Message processing method and system | |
| CN110609761B (en) | Method and device for determining fault source, storage medium and electronic equipment | |
| CN107315592A (en) | A kind of method for upgrading software and device | |
| CN112134734B (en) | Configuration method and device of network equipment | |
| CN108933824A (en) | A kind of method, system and relevant apparatus keeping RabbitMQ service | |
| JPH07298498A (en) | Power system stabilizing method and apparatus | |
| CN109936609A (en) | Terminal chain type upgrade method, device and updating and management server | |
| CN113569947A (en) | Arc detection method and system | |
| CN107707590A (en) | System, the method and device of data transfer | |
| CN103023697B (en) | A kind of management method, Apparatus and system of array multipath | |
| US20220129337A1 (en) | Training a Model for Use with a Software Installation Process | |
| CN110311833B (en) | Method and device for detecting provider service, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20150909 |
|
| RJ01 | Rejection of invention patent application after publication |