WO2020015064A1 - 系统故障处理方法、装置、设备及存储介质 - Google Patents

系统故障处理方法、装置、设备及存储介质 Download PDF

Info

Publication number
WO2020015064A1
WO2020015064A1 PCT/CN2018/103769 CN2018103769W WO2020015064A1 WO 2020015064 A1 WO2020015064 A1 WO 2020015064A1 CN 2018103769 W CN2018103769 W CN 2018103769W WO 2020015064 A1 WO2020015064 A1 WO 2020015064A1
Authority
WO
WIPO (PCT)
Prior art keywords
fault
current
preset
solution
similar
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.)
Ceased
Application number
PCT/CN2018/103769
Other languages
English (en)
French (fr)
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.)
Ping An Technology Shenzhen Co Ltd
Original Assignee
Ping An Technology Shenzhen 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 Ping An Technology Shenzhen Co Ltd filed Critical Ping An Technology Shenzhen Co Ltd
Publication of WO2020015064A1 publication Critical patent/WO2020015064A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • GPHYSICS
    • G06COMPUTING OR CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/30Monitoring
    • GPHYSICS
    • G06COMPUTING OR CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/30Monitoring
    • G06F11/34Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment

Definitions

  • the present application relates to the field of system maintenance, and in particular, to a method, a device, a device, and a computer-readable storage medium for processing a system fault.
  • the main purpose of the present application is to provide a system failure processing method, device, device, and computer-readable storage medium, which are aimed at solving the technical problems of low efficiency in solving system failure in the prior art.
  • the system fault processing method includes the following steps:
  • system fault processing method further includes:
  • the method further includes:
  • the steps to the current terminal to guide the user to solve the current fault include:
  • a fault solution corresponding to the similar fault problem is obtained in the preset diagnosis library, and the fault solution is pushed to the current terminal, so as to guide the user to solve the current fault problem.
  • the method further includes:
  • the method before the step of acquiring the fault interface information of the current terminal when receiving the fault diagnosis instruction, and acquiring the current fault parameters of the system being diagnosed in the fault interface information, the method further includes:
  • the preset diagnostic library includes: software fault number, software fault name, configuration parameters, alarm parameters, performance index parameters, fault cause parameters, solution parameters, and whether a software defect is identified;
  • the configuration parameters include configuration A parameter number and a configuration parameter weight, the alarm parameter includes an alarm parameter number and an alarm parameter weight, and the performance index parameter includes a performance index number and a performance index weight.
  • system fault processing apparatus includes:
  • a parameter acquiring module configured to acquire the fault interface information of the current terminal when receiving the fault diagnosis instruction, and acquire the current fault parameters of the system being diagnosed in the fault interface information;
  • a fault diagnosis module configured to match the current fault parameters with a preset diagnostic library, and determine whether a similar fault problem exists in the preset diagnostic library
  • a fault resolution module configured to obtain a fault solution corresponding to the similar fault problem in the preset diagnostic library if the similar fault problem exists in the preset diagnostic library, and push the fault solution To the current terminal, so as to guide the user to solve the current fault problem.
  • the present application further provides a system fault processing device, where the system fault processing device includes a processor, a memory, and computer-readable instructions stored on the memory and executable by the processor.
  • the computer-readable instructions are executed by the processor, the steps of the system fault processing method as described above are implemented.
  • the present application further provides a computer-readable storage medium, characterized in that the computer-readable storage medium stores computer-readable instructions, wherein when the computer-readable instructions are executed by a processor, To implement the steps of the system fault processing method as described above.
  • the present application provides a system fault processing method, that is, when receiving a fault diagnosis instruction, acquiring the fault interface information of the current terminal, and acquiring the current fault parameters of the system being diagnosed in the fault interface information; Matching with the preset diagnostic library to determine whether there is a similar fault problem in the preset diagnostic library; if the similar fault problem exists in the preset diagnostic library, obtaining the similar fault in the preset diagnostic library The fault solution corresponding to the fault problem, and the fault solution is pushed to the current terminal, so as to guide the user to solve the current fault problem.
  • the present application realizes intelligent diagnosis of system faults and real-time monitoring of system faults, improves the efficiency of fault diagnosis, and thereby solves the technical problem of low efficiency of existing system faults.
  • FIG. 1 is a schematic diagram of a hardware structure of a system fault processing device involved in a solution according to an embodiment of the present application
  • FIG. 2 is a schematic flowchart of a first embodiment of a system fault processing method of the present application
  • FIG. 3 is a schematic flowchart of a second embodiment of a system fault processing method of the present application.
  • FIG. 4 is a schematic flowchart of a third embodiment of a system fault processing method of the present application.
  • FIG. 5 is a schematic diagram of the functional modules of the first embodiment of the system fault processing device of the present application.
  • the system fault processing method according to the embodiment of the present application is mainly applied to a system fault processing device, and the system fault processing device may be a device with a display and processing function, such as a PC, a portable computer, or a mobile terminal.
  • FIG. 1 is a schematic diagram of a hardware structure of a system fault processing device involved in a solution according to an embodiment of the present application.
  • the system fault processing device may include a processor 1001 (for example, a CPU), a communication bus 1002, a user interface 1003, a network interface 1004, and a memory 1005.
  • the communication bus 1002 is used to implement connection and communication between these components.
  • the user interface 1003 may include a display and an input unit such as a keyboard.
  • the network interface 1004 may optionally include a standard wired interface and a wireless interface.
  • the memory 1005 can be a high-speed RAM memory or a stable memory (non-volatile memory), such as a disk memory, the memory 1005 may optionally be a storage device independent of the foregoing processor 1001.
  • FIG. 1 does not constitute a limitation on the system fault processing equipment, and may include more or fewer components than shown in the figure, or combine certain components, or arrange different components. .
  • the memory 1005 as a computer-readable storage medium in FIG. 1 may include an operating system, a network communication module, and computer-readable instructions.
  • the network communication module is mainly used to connect to a server and perform data communication with the server; and the processor 1001 can call the computer-readable instructions stored in the memory 1005 and execute the system fault processing method provided in the embodiment of the present application.
  • the embodiment of the present application provides a system fault processing method.
  • FIG. 2 is a schematic flowchart of a first embodiment of a system fault processing method of the present application.
  • system fault processing method includes the following steps:
  • Step S10 When receiving the fault diagnosis instruction, acquiring the fault interface information of the current terminal, and acquiring the current fault parameters of the system being diagnosed in the fault interface information;
  • a system fault processing method is provided. Specifically, a server program is installed and run on a system fault diagnosis server, and a client agent program is installed and run on a system client.
  • the client agent program edits the diagnosis task and diagnosis plan through human-machine commands, and sends messages containing the diagnosis task and diagnosis plan to the server program through the TCP protocol to monitor the system status in real time; the server program is on the server of the software system to be diagnosed During running, obtain the diagnosis task and diagnosis plan sent by the client program, execute the diagnosis task, and output the diagnosis result to the client program.
  • the user can send a fault diagnosis instruction through the one-click diagnosis of the client.
  • the server When the server receives the fault diagnosis instruction sent by the client, the server obtains the fault interface information of the current terminal, such as by taking a screenshot or directly capturing related information in the fault page of the current terminal, and then from the fault interface information To obtain the current fault parameters corresponding to the system being diagnosed, such as the current page address, system error log information, and fault prompt information.
  • step S10 the method further includes:
  • the preset diagnosis library includes software fault number, software fault name, configuration parameters, alarm parameters, performance index parameters, fault cause parameters, solution parameters, and whether a software defect is identified
  • the configuration parameters include configuration parameter numbers.
  • configuration parameter weights, the alarm parameters include alarm parameter numbers and alarm parameter weights, and the performance index parameters include performance index numbers and performance index weights.
  • all verified fault parameters are stored in a data recording manner, and the verified fault parameters are stored correspondingly, that is, entered in a fault attribute database
  • the fault attribute database includes a configuration attribute database including a configuration attribute number , Software fault number queue and configuration table; alarm attribute database, including alarm attribute number, software fault number queue, and alarm characteristics; performance index attribute database, including performance index attribute number, software fault number queue, and performance indicator characteristics; fault cause attribute library , Including fault cause attribute number, software fault number queue and fault cause description; solution attribute library, including solution attribute number, software fault number queue and solution description.
  • the fault rule database is composed of a software fault number, a software fault name, a corresponding configuration attribute group, an alarm attribute group, a performance index attribute group, a fault cause attribute group, a solution attribute group, and a software defect identifier.
  • the attribute queue is composed of attribute numbers and attribute weights; the software fault attribution relationship database and elements in each attribute database have a many-to-many relationship, and an index table is established with each other. Then, a preset diagnosis database is established according to the fault data database and the fault rule database.
  • Step S20 Match the current fault parameters with a preset diagnostic library to determine whether there is a similar fault problem in the preset diagnostic library;
  • the keyword information is extracted from the current fault parameters, and the keyword information is compared with a preset diagnosis database to match similar fault problems that are suitable for the keyword information, and the predictive information is found. Let's set up a fault solution corresponding to a similar fault problem described in the diagnostic library.
  • fault parameters of the software system to be diagnosed are obtained through the system, and the fault parameters include configuration parameters, alarm parameters, performance index parameters, fault cause parameters, and solution parameters, and then the verified configuration of the software system to be diagnosed
  • the combination of the parameter, the alarm parameter, and the performance index parameter and the corresponding fault cause and solution combination are used to establish a mapping relationship, and the mapping relationship is modeled and stored in a database, that is, added to the preset diagnosis database.
  • Step S30 if the similar fault problem exists in the preset diagnostic library, obtain a fault solution corresponding to the similar fault problem in the preset diagnostic library, and push the fault solution to the Current terminal in order to guide users to resolve current faults.
  • a fault solution corresponding to the similar fault problem or a diagnosis problem list corresponding to the similar fault problem is obtained in the preset diagnosis library, and the fault solution is either pushed to all
  • the current terminal is described to guide users or technicians to try to recover from the fault, thereby achieving intelligent diagnosis of system faults and real-time monitoring of system faults, improving the efficiency of fault diagnosis, and thereby solving the inefficient technology of existing system faults. problem.
  • step S30 the method further includes:
  • a secondary diagnosis instruction may be triggered by a fault diagnosis function button.
  • a fault diagnosis function button When receiving the secondary diagnosis instruction, firstly take a screenshot or directly capture the relevant information in the secondary fault page of the current terminal, and then obtain the secondary fault corresponding to the system being diagnosed from the secondary interface information. Parameters, such as the current page address, system error log information, and fault information. Keyword information is extracted from the secondary fault parameters, and the keyword information is compared with a preset diagnosis database to determine whether there is problem information matching the secondary fault parameters in the preset diagnosis database. . If it exists, a solution corresponding to the matched problem information is acquired and displayed through the current terminal.
  • This embodiment provides a system fault processing method, that is, when a fault diagnosis instruction is received, the fault interface information of the current terminal is obtained, and the current fault parameters of the system being diagnosed are obtained in the fault interface information; The parameters are matched with the preset diagnostic library to determine whether there is a similar fault problem in the preset diagnostic library; if the similar fault problem exists in the preset diagnostic library, the preset diagnostic library is used to obtain the A fault solution corresponding to a similar fault problem, and the fault solution is pushed to the current terminal, so as to guide the user to solve the current fault problem.
  • the present application realizes intelligent diagnosis of system faults and real-time monitoring of system faults, improves the efficiency of fault diagnosis, and thereby solves the technical problem of low efficiency of existing system faults.
  • FIG. 3 is a schematic flowchart of a second embodiment of a system fault processing method of the present application.
  • the method for processing a system fault after step S30 further includes:
  • Step S41 if the similar fault problem does not exist in the preset diagnosis library, report the fault interface information and current fault parameters to a preset processing end;
  • Step S42 When receiving the current fault solution feedback from the preset processing end, push the current fault solution to the terminal, and add the current fault parameter and the current fault solution to the preset Diagnostic library.
  • the fault interface information and the current fault parameters are reported to the corresponding technician.
  • the default processing end that is, the artificial exception processing node.
  • the technician can perform fault diagnosis according to the system error log information or fault prompt information therein, and correspondingly sort out the current fault solution and feed it back to the current terminal.
  • a preset processing terminal may be reported to call a corresponding technician for on-site diagnosis, and then the corresponding current fault solution is sorted out, and the current fault parameter and the current fault solution are added to the preset.
  • the diagnostic library updates the preset diagnostic library.
  • FIG. 4 is a schematic flowchart of a third embodiment of a system fault processing method of the present application.
  • the step S30 includes:
  • Step S31 if the similar fault problem exists in the preset diagnosis library, obtain the number of problems of the similar fault problem, and determine whether the number of the problems is unique;
  • Step S32 if the number of the problems is not unique, according to the matching degree between the similar failure problem and the current failure parameter, sort multiple related problems in the similar failure problem, and generate and display the corresponding related problems List
  • Step S33 Receive a selection instruction triggered by a user selection operation based on the associated problem list, and determine a target fault problem corresponding to the current fault parameter in the associated problem list according to the selection instruction;
  • Step S34 Obtain a fault solution corresponding to the target fault problem in the preset diagnosis database, and push the fault solution to the current terminal, so as to guide the user to solve the current fault problem.
  • Step S35 if the number of the problems is unique, obtain a fault solution corresponding to the similar fault problem in the preset diagnosis library, and push the fault solution to the current terminal, so as to guide the user to solve the current problem Problems.
  • the number of similar fault problems is unique. If the number of similar fault problems is unique, the fault solution corresponding to the similar fault problem may be directly obtained in the preset diagnosis library, and the fault solution may be pushed to the current terminal to guide the user Solve the current problem. If the number of similar failure problems is not unique, then calculate the matching degree information of the related problem information in the similar failure problem and the current failure parameter, and sequentially calculate all the matching problems according to the order of the matching degree from large to small.
  • the related problem information in similar failure problems is arranged to generate a corresponding related problem list.
  • the related problem list is pushed to the current terminal, so that the user can select the closest target fault problem among the related problems according to his own situation. Then, a fault solution corresponding to the target fault problem is selected in the preset diagnosis library, and the fault solution is pushed to the current terminal.
  • an embodiment of the present application further provides a system fault processing device.
  • FIG. 5 is a schematic diagram of functional modules of a first embodiment of a system fault processing apparatus of the present application.
  • system fault processing device includes:
  • a parameter acquiring module 10 configured to acquire the fault interface information of the current terminal when receiving the fault diagnosis instruction, and acquire the current fault parameters of the system being diagnosed in the fault interface information;
  • a fault diagnosis module 20 configured to match the current fault parameters with a preset diagnosis library, and determine whether a similar fault problem exists in the preset diagnosis library;
  • a fault resolution module 30 is configured to obtain a fault solution corresponding to the similar fault problem from the preset diagnostic library if the similar fault problem exists in the preset diagnostic library, and apply the fault solution Push to the current terminal to guide the user to resolve the current fault.
  • system fault processing device further includes:
  • a parameter storage module is configured to form a fault parameter data record according to the verified fault parameter, and store the fault parameter data record in the preset diagnosis database, wherein the verified fault parameter includes: a configuration attribute, Alarm attributes, performance index attributes, fault cause attributes, and solution parameters;
  • the solution association module is configured to establish a mapping relationship between the fault parameter and the solution parameter, and store the corresponding mapping relationship in the preset diagnosis database.
  • the fault resolution module 30 includes:
  • a secondary diagnosis unit is configured to obtain secondary interface information of the current terminal, obtain terminal information of the current terminal, and obtain all information in the secondary interface information if a secondary diagnostic instruction triggered by a user is received. Describe the secondary fault parameters of the system being diagnosed;
  • a fault reporting unit configured to report the current fault parameters, fault solutions, terminal information, secondary interface information, and secondary fault parameters to a preset processing end;
  • a secondary push unit configured to push the secondary solution to the terminal when receiving the secondary solution feedback from the preset processing end, and send the secondary fault parameter and the secondary solution A solution is added to the preset diagnostic library.
  • system fault processing device further includes:
  • a reporting module configured to report the fault interface information and current fault parameters to a preset processing end if the similar fault problem does not exist in the preset diagnostic library
  • a push module configured to push the current fault solution to the terminal when receiving the current fault solution feedback from the preset processing end, and add the current fault parameter and the current fault solution to the terminal Preset diagnostic library.
  • the fault resolution module 30 includes:
  • a quantity judging unit configured to obtain the number of similar failure problems if the similar failure problem exists in the preset diagnosis library, and determine whether the number of the problems is unique;
  • a list generating unit is configured to, if the number of the problems is not unique, sort a plurality of related problems among the similar failure problems according to the matching degree between the similar failure problems and the current failure parameters, and generate and display corresponding responses. List of related issues;
  • a problem confirmation unit configured to receive a selection instruction triggered by a user selection operation based on the related problem list, and determine a target failure problem corresponding to the current failure parameter in the related problem list according to the selection instruction;
  • a first pushing unit is configured to obtain a fault solution corresponding to the target fault problem in the preset diagnosis database, and push the fault solution to the current terminal, so as to guide a user to solve the current fault problem.
  • a second push unit if the number of problems is unique, obtain a fault solution corresponding to the similar fault problem in the preset diagnosis library, and push the fault solution to the current terminal to guide the user Solve the current problem.
  • Each module in the above-mentioned system fault processing device corresponds to each step in the embodiment of the above-mentioned system fault processing method, and its functions and implementation processes are not repeated here one by one.
  • an embodiment of the present application further provides a computer-readable storage medium.
  • the computer-readable storage medium of the present application stores computer-readable instructions, wherein the computer-readable storage medium may be a non-volatile readable storage medium, and when the computer-readable instructions are executed by a processor, the implementation is as described above. Steps of the system failure handling method.
  • the methods in the above embodiments can be implemented by means of software plus a necessary universal hardware platform, and of course, also by hardware, but in many cases the former is better.
  • Implementation Based on such an understanding, the technical solution of this application that is essentially or contributes to the existing technology can be embodied in the form of a software product.
  • the computer software product is stored in a storage medium (such as ROM / RAM) as described above. , Magnetic disk, optical disc), including a number of instructions to enable a terminal device (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the methods described in the embodiments of this application.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Hardware Design (AREA)
  • Debugging And Monitoring (AREA)

Abstract

一种系统故障处理方法、装置、设备及计算机可读存储介质,该方法通过在接收到故障诊断指令时,获取当前终端的故障界面信息,并在所述故障界面信息中获取被诊断系统的当前故障参数(S10);将所述当前故障参数与预设诊断库进行匹配,判断所述预设诊断库中是否存在类似故障问题(S20);若所述预设诊断库中存在所述类似故障问题,则在所述预设诊断库中获取所述类似故障问题对应的故障解决方案,并将所述故障解决方案推送至所述当前终端,以便指导用户解决当前故障问题(S30)。通过上述方式,实现了系统故障的智能诊断以及系统故障的实时监测,提高了故障诊断的效率,从而解决了现有系统故障的效率低下的技术问题。

Description

系统故障处理方法、装置、设备及存储介质
本申请要求于2018年7月18日提交中国专利局、申请号为201810791075.4、发明名称为“系统故障处理方法、装置、设备及存储介质”的中国专利申请的优先权,其全部内容通过引用结合在申请中。
技术领域
本申请涉及系统维护领域,尤其涉及一种系统故障处理方法、装置、设备及计算机可读存储介质。
背景技术
随着科技的发展,人们的生活方式及工作方式都发生了变化,计算机已经成为人们日常生活中必不可少的一部分。用户可以利用计算机进行办公或者网购等操作。而上述操作是在系统支持下才能进行,系统是用户和计算机的接口。用户在使用系统过程中,若遇到故障问题,需要手动填写相关问题描述等信息,然后上报该信息,以便IT技术人员确定发生故障的原因,从而解决该故障问题。但是,用户的描述信息差异较大,且提供的描述信息不一定完整,而产生故障的原因有很多。也就是说,依靠用户上报的描述信息无法准确定位故障原因,容易导致解决系统故障的效率低下。因此,如何解决现有技术中解决系统故障的效率低下,成为了目前亟待解决的技术问题。
发明内容
本申请的主要目的在于提供一种系统故障处理方法、装置、设备及计算机可读存储介质,旨在解决现有技术中解决系统故障的效率低下的技术问题。
为实现上述目的,本申请提一种系统故障处理方法,所述系统故障处理方法包括以下步骤:
在接收到故障诊断指令时,获取当前终端的故障界面信息,并在所述故障界面信息中获取被诊断系统的当前故障参数;
将所述当前故障参数与预设诊断库进行匹配,判断所述预设诊断库中是否存在类似故障问题;
若所述预设诊断库中存在所述类似故障问题,则在所述预设诊断库中获取所述类似故障问题对应的故障解决方案,并将所述故障解决方案推送至所述当前终端,以便指导用户解决当前故障问题。
可选地,所述系统故障处理方法还包括:
若所述预设诊断库中不存在所述类似故障问题,则将所述故障界面信息以及当前故障参数上报至预设处理端;
在接收所述预设处理端反馈的当前故障解决方案时,将所述当前故障解决方案推送至所述终端,并将所述当前故障参数与当前故障解决方案添加至所述预设诊断库。
可选地,所述若所述预设诊断库中存在所述类似故障问题,则在所述预设诊断库中获取所述类似故障问题对应的故障解决方案,并将所述故障解决方案推送至所述当前终端,以便指导用户解决当前故障问题的步骤之后,还包括:
若接收到用户触发的二次诊断指令时,获取所述当前终端的二次界面信息,获取所述当前终端的终端信息,并在所述二次界面信息中获取所述被诊断系统的二次故障参数;
将所述当前故障参数、故障解决方案、终端信息、二次界面信息以及二次故障参数上报至预设处理端;
在接收到所述预设处理端反馈的二次解决方案时,将所述二次解决方案推送至所述终端,并将所述二次故障参数以及所述二次解决方案添加至所述预设诊断库。
可选地,所述若所述预设诊断库中存在所述类似故障问题,则在所述预设诊断库中获取所述类似故障问题对应的故障解决方案,并将所述故障解决方案推送至所述当前终端,以便指导用户解决当前故障问题的步骤包括:
若所述预设诊断库中存在所述类似故障问题,获取所述类似故障问题的问题数量,并判断所述问题数量是否唯一;
若所述问题数量唯一,则在所述预设诊断库中获取所述类似故障问题对应的故障解决方案,并将所述故障解决方案推送至所述当前终端,以便指导用户解决当前故障问题。
可选地,所述若所述预设诊断库中存在所述类似故障问题,获取所述类似故障问题的问题数量,并判断所述问题数量是否唯一的步骤之后,还包括:
若所述问题数量不唯一,则根据所述类似故障问题与所述当前故障参数的匹配度,将所述类似故障问题中的多个关联问题进行排序,生成并显示对应的关联问题列表;
基于所述关联问题列表,接收用户选择操作触发的选择指令,并根据所述选择指令,在所述关联问题列表中确定所述当前故障参数对应的目标故障问题;
在所述预设诊断库中获取所述目标故障问题对应的故障解决方案,并将所述故障解决方案推送至所述当前终端,以便指导用户解决当前故障问题。
可选地,所述在接收到故障诊断指令时,获取当前终端的故障界面信息,并在所述故障界面信息中获取被诊断系统的当前故障参数的步骤之前,还包括:
根据已验证的故障参数形成故障参数数据记录,并将所述故障参数数据记录存储至所述预设诊断库中,其中,所述已验证的故障参数包括:配置属性、告警属性、性能指标属性、故障原因属性和解决方案参数;
建立所述故障参数和解决方案参数的映射关系,并将所述映射关系对应关联存储至所述预设诊断库中。
可选地,所述预设诊断库包括:软件故障编号、软件故障名称、配置参数、告警参数、性能指标参数、故障原因参数、解决办法参数和是否软件缺陷标识等;所述配置参数包括配置参数编号和配置参数权值,所述告警参数包括告警参数编号和告警参数权值,所述性能指标参数包括性能指标编号和性能指标权值。
此外,为实现上述目的,本申请还提供一种系统故障处理装置,所述系统故障处理装置包括:
参数获取模块,用于在接收到故障诊断指令时,获取当前终端的故障界面信息,并在所述故障界面信息中获取被诊断系统的当前故障参数;
故障诊断模块,用于将所述当前故障参数与预设诊断库进行匹配,判断所述预设诊断库中是否存在类似故障问题;
故障解决模块,用于若所述预设诊断库中存在所述类似故障问题,则在所述预设诊断库中获取所述类似故障问题对应的故障解决方案,并将所述故障解决方案推送至所述当前终端,以便指导用户解决当前故障问题。
此外,为实现上述目的,本申请还提供一种系统故障处理设备,所述系统故障处理设备包括处理器、存储器、以及存储在所述存储器上并可被所述处理器执行的计算机可读指令,其中所述计算机可读指令被所述处理器执行时,实现如上述的系统故障处理方法的步骤。
此外,为实现上述目的,本申请还提供一种计算机可读存储介质,其特征在于,所述计算机可读存储介质上存储有计算机可读指令,其中所述计算机可读指令被处理器执行时,实现如上述的系统故障处理方法的步骤。
本申请提供一种系统故障处理方法,即在接收到故障诊断指令时,获取当前终端的故障界面信息,并在所述故障界面信息中获取被诊断系统的当前故障参数;将所述当前故障参数与预设诊断库进行匹配,判断所述预设诊断库中是否存在类似故障问题;若所述预设诊断库中存在所述类似故障问题,则在所述预设诊断库中获取所述类似故障问题对应的故障解决方案,并将所述故障解决方案推送至所述当前终端,以便指导用户解决当前故障问题。通过上述方式,本申请实现了系统故障的智能诊断以及系统故障的实时监测,提高了故障诊断的效率,从而解决了现有系统故障的效率低下的技术问题。
附图说明
图1为本申请实施例方案中涉及的系统故障处理设备的硬件结构示意图;
图2为本申请系统故障处理方法第一实施例的流程示意图;
图3为本申请系统故障处理方法第二实施例的流程示意图;
图4为本申请系统故障处理方法第三实施例的流程示意图;
图5为本申请系统故障处理装置第一实施例的功能模块示意图。
本申请目的的实现、功能特点及优点将结合实施例,参照附图做进一步说明。
具体实施方式
应当理解,此处所描述的具体实施例仅仅用以解释本申请,并不用于限定本申请。
本申请实施例涉及的系统故障处理方法主要应用于系统故障处理设备,该系统故障处理设备可以是PC、便携计算机、移动终端等具有显示和处理功能的设备。
参照图1,图1为本申请实施例方案中涉及的系统故障处理设备的硬件结构示意图。本申请实施例中,系统故障处理设备可以包括处理器1001(例如CPU),通信总线1002,用户接口1003,网络接口1004,存储器1005。其中,通信总线1002用于实现这些组件之间的连接通信;用户接口1003可以包括显示屏(Display)、输入单元比如键盘(Keyboard);网络接口1004可选的可以包括标准的有线接口、无线接口(如WI-FI接口);存储器1005可以是高速RAM存储器,也可以是稳定的存储器(non-volatile memory),例如磁盘存储器,存储器1005可选的还可以是独立于前述处理器1001的存储装置。
本领域技术人员可以理解,图1中示出的硬件结构并不构成对系统故障处理设备的限定,可以包括比图示更多或更少的部件,或者组合某些部件,或者不同的部件布置。
继续参照图1,图1中作为一种计算机可读存储介质的存储器1005可以包括操作系统、网络通信模块以及计算机可读指令。
在图1中,网络通信模块主要用于连接服务器,与服务器进行数据通信;而处理器1001可以调用存储器1005中存储的计算机可读指令,并执行本申请实施例提供的系统故障处理方法。
本申请实施例提供了一种系统故障处理方法。
参照图2,图2为本申请系统故障处理方法第一实施例的流程示意图。
本实施例中,所述系统故障处理方法包括以下步骤:
步骤S10, 在接收到故障诊断指令时,获取当前终端的故障界面信息,并在所述故障界面信息中获取被诊断系统的当前故障参数;
目前,用户可以利用计算机进行办公或者网购等操作。而上述操作是在各个系统的支持下才能进行,系统是用户和计算机的接口。用户在使用系统过程中,若遇到故障问题,需要手动填写相关问题描述等信息,然后上报该信息,以便IT技术人员确定发生故障的原因,从而解决该故障问题。但是,用户的描述信息差异较大,且提供的描述信息不一定完整,而产生故障的原因有很多。也就是说,依靠用户上报的描述信息无法准确定位故障原因,容易导致解决系统故障的效率低下。因此,如何解决现有技术中解决系统故障的效率低下,成为了目前亟待解决的技术问题。
本实施例中,为了解决现有的技术问题,提供一种系统故障处理方法。具体地,在系统故障诊断服务器安装并运行服务端程序,在系统客户端安装并运行客户端代理程序。客户端代理程序通过人机命令,编辑诊断任务和诊断计划,并通过TCP协议将包含诊断任务和诊断计划的消息发送至服务端程序以实时监控系统状态;服务端程序在待诊断软件系统的服务器中运行,获取客户端程序发来的诊断任务和诊断计划,并执行诊断任务,输出诊断结果反馈给客户端程序。用户在遇到系统故障问题时,可通过客户端的一键诊断发送故障诊断指令。所述服务器在接收到所述客户端发送的故障诊断指令时,获取当前终端的故障界面信息,如通过截图或者直接抓取当前终端的故障页面中的相关信息等,然后从所述故障界面信息中获取被诊断系统对应的当前故障参数,如当前页面地址、系统报错日志信息、故障提示信息等。
进一步地,步骤S10之前,还包括:
根据已验证的故障参数形成故障参数数据记录,并将所述故障参数数据记录存储至所述预设诊断库中,其中,所述已验证的故障参数包括:配置属性、告警属性、性能指标属性、故障原因属性和解决方案参数;
建立所述故障参数和解决方案参数的映射关系,并将所述映射关系对应关联存储至所述预设诊断库中。
其中,所述预设诊断库包括:软件故障编号、软件故障名称、配置参数、告警参数、性能指标参数、故障原因参数、解决办法参数和是否软件缺陷标识等;所述配置参数包括配置参数编号和配置参数权值,所述告警参数包括告警参数编号和告警参数权值,所述性能指标参数包括性能指标编号和性能指标权值。
本实施例中,采用数据记录方式存储所有已验证的故障参数,并将该已验证的故障参数分别对应存储,即录入故障属性数据库,所述故障属性数据库包括:配置属性库,包括配置属性编号、软件故障编号队列和配置表;告警属性库,包括告警属性编号、软件故障编号队列和告警特征;性能指标属性库,包括性能指标属性编号、软件故障编号队列和性能指标特征;故障原因属性库,包括故障原因属性编号、软件故障编号队列和故障原因描述;解决办法属性库,包括解决办法属性编号、软件故障编号队列和解决办法描述。建立故障现象与故障原因属性和解决办法属性组合的映射关系,并将该映射关系录入所述故障规则数据库中,其中,故障现象包括配置属性、告警属性和性能指标属性,故障原因与解决办法属性一一对应。将软件故障的属性和软件故障建立对应关系,形成故障规则数据库。即所述故障规则数据库由软件故障编号、软件故障名称、对应配置属性组、告警属性组、性能指标属性组、故障原因属性组、解决办法属性组和是否软件缺陷标识组成;归属软件故障的各属性队列,由属性编号和属性权重组成;软件故障归属关系库和各个属性库中的元素具有多对多的关系,互相建立索引表。然后根据所述故障数据数据库和所述故障规则数据库建立预设诊断库。
步骤S20,将所述当前故障参数与预设诊断库进行匹配,判断所述预设诊断库中是否存在类似故障问题;
本实施例中,在所述当前故障参数提取关键字信息,并将所述关键字信息与预设诊断库进行比对,匹配出于该关键字信息相适的类似故障问题,并查找出预设诊断库中所述类似故障问题对应的故障解决方案。在本实施例中,通过系统获取被诊断软件系统的故障参数,该故障参数包括配置参数、告警参数、性能指标参数、故障原因参数和解决办法参数,然后将被诊断软件系统的已验证的配置参数、告警参数和性能指标参数的组合与对应的故障原因和解决办法组合建立映射关系,并将该映射关系建模和入库,即添加至所述预设诊断库中。最后根据被诊断软件系统的故障参数在预设诊断库中进行匹配,根据故障参数与预设诊断库中问题的匹配度确定对应的类似故障问题,还可生成对应的故障诊断问题列表。
步骤S30,若所述预设诊断库中存在所述类似故障问题,则在所述预设诊断库中获取所述类似故障问题对应的故障解决方案,并将所述故障解决方案推送至所述当前终端,以便指导用户解决当前故障问题。
本实施例中,在所述预设诊断库中获取所述类似故障问题对应的故障解决方案,或者是所述类似故障问题对应的诊断问题列表,并将所述故障解决方案或者是推送至所述当前终端,以指导用户或者是技术人员尝试恢复故障,由此实现了系统故障的智能诊断以及系统故障的实时监测,提高了故障诊断的效率,从而解决了现有系统故障的效率低下的技术问题。
进一步地,步骤S30之后,还包括:
若接收到用户触发的二次诊断指令时,获取所述当前终端的二次界面信息,获取所述当前终端的终端信息,并在所述二次界面信息中获取所述被诊断系统的二次故障参数;
将所述当前故障参数、故障解决方案、终端信息、二次界面信息以及二次故障参数上报至预设处理端;
在接收到所述预设处理端反馈的二次解决方案时,将所述二次解决方案推送至所述终端,并将所述二次故障参数以及所述二次解决方案添加至所述预设诊断库。
本实施例中,在用户或者技术人员通过所述故障解决方案未能解决故障问题,或者产生了新的故障问题时,可通过故障诊断功能按钮触发二次诊断指令。在接收到所述二次诊断指令时,可首先通过截图或者直接抓取当前终端的二次故障页面中的相关信息等,然后从所述二次界面信息中获取被诊断系统对应的二次故障参数,如当前页面地址、系统报错日志信息、故障提示信息等。在所述二次故障参数中提取关键字信息,并将所述关键字信息与预设诊断库进行比对,判断所述预设诊断库中是否存在与所述二次故障参数匹配的问题信息。若存在,则获取并通过当前终端显示所述匹配的问题信息对应的解决方案。若不存在,则获取所述当前终端的终端信息,并将所述当前故障参数、故障解决方案、终端信息、二次界面信息以及二次故障参数上报至预设处理端,以便对应的技术人员,根据上述信息进行异常处理,并在接收到所述预设处理端反馈的二次解决方案时,将所述二次故障参数以及所述二次解决方案添加至所述预设诊断库,并在所述预设诊断库中将所述当前故障参数、故障解决方案、终端信息、二次故障参数以及对应的二次故障解决方案进行关联。
本实施例提供一种系统故障处理方法,即在接收到故障诊断指令时,获取当前终端的故障界面信息,并在所述故障界面信息中获取被诊断系统的当前故障参数;将所述当前故障参数与预设诊断库进行匹配,判断所述预设诊断库中是否存在类似故障问题;若所述预设诊断库中存在所述类似故障问题,则在所述预设诊断库中获取所述类似故障问题对应的故障解决方案,并将所述故障解决方案推送至所述当前终端,以便指导用户解决当前故障问题。通过上述方式,本申请实现了系统故障的智能诊断以及系统故障的实时监测,提高了故障诊断的效率,从而解决了现有系统故障的效率低下的技术问题。
参照图3,图3为本申请系统故障处理方法第二实施例的流程示意图。
基于上述图2所示实施例,本实施例中,所述系统故障处理方法在步骤S30之后,还包括:
步骤S41,若所述预设诊断库中不存在所述类似故障问题,则将所述故障界面信息以及当前故障参数上报至预设处理端;
步骤S42,在接收所述预设处理端反馈的当前故障解决方案时,将所述当前故障解决方案推送至所述终端,并将所述当前故障参数与当前故障解决方案添加至所述预设诊断库。
本实施例中,在根据所述当前故障参数中的关键字在所述预设诊断库中农匹配不到对应的类似故障问题时,则将所述故障界面信息以及当前故障参数上报至技术人员对应的预设处理端,即人工异常处理节点。技术人员接收到所述故障界面信息和所述当前故障参数时,可根据其中的系统报错日志信息或者故障提示信息进行故障诊断,并对应整理出当前故障解决方案,并反馈至所述当前终端。具体实施例中,也可通过上报预设处理端,以呼叫对应的技术人员进行现场诊断,然后整理出对应的当前故障解决方案,并将所述当前故障参数与当前故障解决方案添加至预设诊断库,进行预设诊断库的更新。
参照图4,图4为本申请系统故障处理方法第三实施例的流程示意图。
基于上述图3所示实施例,本实施例中,所述步骤S30包括:
步骤S31,若所述预设诊断库中存在所述类似故障问题,获取所述类似故障问题的问题数量,并判断所述问题数量是否唯一;
步骤S32,若所述问题数量不唯一,则根据所述类似故障问题与所述当前故障参数的匹配度,将所述类似故障问题中的多个关联问题进行排序,生成并显示对应的关联问题列表;
步骤S33,基于所述关联问题列表,接收用户选择操作触发的选择指令,并根据所述选择指令,在所述关联问题列表中确定所述当前故障参数对应的目标故障问题;
步骤S34,在所述预设诊断库中获取所述目标故障问题对应的故障解决方案,并将所述故障解决方案推送至所述当前终端,以便指导用户解决当前故障问题。
步骤S35,若所述问题数量唯一,则在所述预设诊断库中获取所述类似故障问题对应的故障解决方案,并将所述故障解决方案推送至所述当前终端,以便指导用户解决当前故障问题。
本实施例中,在判定所述预设诊断库中存在与所述当前故障参数匹配的类似故障问题时,进一步判断所述类似故障问题的数量是否唯一。若所述类似故障问题的数量唯一,则可直接在所述预设诊断库中获取所述类似故障问题对应的故障解决方案,并将所述故障解决方案推送至所述当前终端,以便指导用户解决当前故障问题。若所述类似故障问题的数量不唯一,则将所述类似故障问题中的关联问题信息与所述当前故障参数进行匹配度计算,并根据所述匹配度由大到小的顺序,依次将所述类似故障问题中的关联问题信息进行排列,生成对应的关联问题列表。并将所述关联问题列表推送至所述当前终端,以便用户根据自身情况在所述关联问题中选择最接近的目标故障问题。然后在所述预设诊断库中选择所述目标故障问题对应的故障解决方案,并将所述故障解决方案推送至所述当前终端。
此外,本申请实施例还提供一种系统故障处理装置。
参照图5,图5为本申请系统故障处理装置第一实施例的功能模块示意图。
本实施例中,所述系统故障处理装置包括:
参数获取模块10,用于在接收到故障诊断指令时,获取当前终端的故障界面信息,并在所述故障界面信息中获取被诊断系统的当前故障参数;
故障诊断模块20,用于将所述当前故障参数与预设诊断库进行匹配,判断所述预设诊断库中是否存在类似故障问题;
故障解决模块30,用于若所述预设诊断库中存在所述类似故障问题,则在所述预设诊断库中获取所述类似故障问题对应的故障解决方案,并将所述故障解决方案推送至所述当前终端,以便指导用户解决当前故障问题。
进一步地,所述系统故障处理装置还包括:
参数存储模块,用于根据已验证的故障参数形成故障参数数据记录,并将所述故障参数数据记录存储至所述预设诊断库中,其中,所述已验证的故障参数包括:配置属性、告警属性、性能指标属性、故障原因属性和解决方案参数;
方案关联模块,用于建立所述故障参数和解决方案参数的映射关系,并将所述映射关系对应关联存储至所述预设诊断库中。
进一步地,所述故障解决模块30包括:
二次诊断单元,用于若接收到用户触发的二次诊断指令时,获取所述当前终端的二次界面信息,获取所述当前终端的终端信息,并在所述二次界面信息中获取所述被诊断系统的二次故障参数;
故障上报单元,用于将所述当前故障参数、故障解决方案、终端信息、二次界面信息以及二次故障参数上报至预设处理端;
二次推送单元,用于在接收到所述预设处理端反馈的二次解决方案时,将所述二次解决方案推送至所述终端,并将所述二次故障参数以及所述二次解决方案添加至所述预设诊断库。
进一步地,所述系统故障处理装置还包括:
上报模块,用于若所述预设诊断库中不存在所述类似故障问题,则将所述故障界面信息以及当前故障参数上报至预设处理端;
推送模块,用于在接收所述预设处理端反馈的当前故障解决方案时,将所述当前故障解决方案推送至所述终端,并将所述当前故障参数与当前故障解决方案添加至所述预设诊断库。
进一步地,所述故障解决模块30包括:
数量判断单元,用于若所述预设诊断库中存在所述类似故障问题,获取所述类似故障问题的问题数量,并判断所述问题数量是否唯一;
列表生成单元,用于若所述问题数量不唯一,则根据所述类似故障问题与所述当前故障参数的匹配度,将所述类似故障问题中的多个关联问题进行排序,生成并显示对应的关联问题列表;
问题确认单元,用于基于所述关联问题列表,接收用户选择操作触发的选择指令,并根据所述选择指令,在所述关联问题列表中确定所述当前故障参数对应的目标故障问题;
第一推送单元,用于在所述预设诊断库中获取所述目标故障问题对应的故障解决方案,并将所述故障解决方案推送至所述当前终端,以便指导用户解决当前故障问题。
第二推送单元,若所述问题数量唯一,则在所述预设诊断库中获取所述类似故障问题对应的故障解决方案,并将所述故障解决方案推送至所述当前终端,以便指导用户解决当前故障问题。
其中,上述系统故障处理装置中各个模块与上述系统故障处理方法实施例中各步骤相对应,其功能和实现过程在此处不再一一赘述。
此外,本申请实施例还提供一种计算机可读存储介质。
本申请计算机可读存储介质上存储有计算机可读指令,其中,所述计算机可读存储介质可以为非易失性可读存储介质,所述计算机可读指令被处理器执行时,实现如上述的系统故障处理方法的步骤。
其中,计算机可读指令被执行时所实现的方法可参照本申请系统故障处理方法的各个实施例,此处不再赘述。
需要说明的是,在本文中,术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含,从而使得包括一系列要素的过程、方法、物品或者系统不仅包括那些要素,而且还包括没有明确列出的其他要素,或者是还包括为这种过程、方法、物品或者系统所固有的要素。在没有更多限制的情况下,由语句“包括一个……”限定的要素,并不排除在包括该要素的过程、方法、物品或者系统中还存在另外的相同要素。
上述本申请实施例序号仅仅为了描述,不代表实施例的优劣。
通过以上的实施方式的描述,本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现,当然也可以通过硬件,但很多情况下前者是更佳的实施方式。基于这样的理解,本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来,该计算机软件产品存储在如上所述的一个存储介质(如ROM/RAM、磁碟、光盘)中,包括若干指令用以使得一台终端设备(可以是手机,计算机,服务器,空调器,或者网络设备等)执行本申请各个实施例所述的方法。
以上仅为本申请的优选实施例,并非因此限制本申请的专利范围,凡是利用本申请说明书及附图内容所作的等效结构或等效流程变换,或直接或间接运用在其他相关的技术领域,均同理包括在本申请的专利保护范围内。

Claims (20)

  1. 一种系统故障处理方法,其特征在于,所述系统故障处理方法包括以下步骤:
    在接收到故障诊断指令时,获取当前终端的故障界面信息,并在所述故障界面信息中获取被诊断系统的当前故障参数;
    将所述当前故障参数与预设诊断库进行匹配,判断所述预设诊断库中是否存在类似故障问题;
    若所述预设诊断库中存在所述类似故障问题,则在所述预设诊断库中获取所述类似故障问题对应的故障解决方案,并将所述故障解决方案推送至所述当前终端,以便指导用户解决当前故障问题。
  2. 如权利要求1所述的系统故障处理方法,其特征在于,所述系统故障处理方法还包括:
    若所述预设诊断库中不存在所述类似故障问题,则将所述故障界面信息以及当前故障参数上报至预设处理端;
    在接收所述预设处理端反馈的当前故障解决方案时,将所述当前故障解决方案推送至所述终端,并将所述当前故障参数与当前故障解决方案添加至所述预设诊断库。
  3. 如权利要求1所述的系统故障处理方法,其特征在于,所述若所述预设诊断库中存在所述类似故障问题,则在所述预设诊断库中获取所述类似故障问题对应的故障解决方案,并将所述故障解决方案推送至所述当前终端,以便指导用户解决当前故障问题的步骤之后,还包括:
    若接收到用户触发的二次诊断指令时,获取所述当前终端的二次界面信息,获取所述当前终端的终端信息,并在所述二次界面信息中获取所述被诊断系统的二次故障参数;
    将所述当前故障参数、故障解决方案、终端信息、二次界面信息以及二次故障参数上报至预设处理端;
    在接收到所述预设处理端反馈的二次解决方案时,将所述二次解决方案推送至所述终端,并将所述二次故障参数以及所述二次解决方案添加至所述预设诊断库。
  4. 如权利要求1所述的系统故障处理方法,其特征在于,所述若所述预设诊断库中存在所述类似故障问题,则在所述预设诊断库中获取所述类似故障问题对应的故障解决方案,并将所述故障解决方案推送至所述当前终端,以便指导用户解决当前故障问题的步骤包括:
    若所述预设诊断库中存在所述类似故障问题,获取所述类似故障问题的问题数量,并判断所述问题数量是否唯一;
    若所述问题数量唯一,则在所述预设诊断库中获取所述类似故障问题对应的故障解决方案,并将所述故障解决方案推送至所述当前终端,以便指导用户解决当前故障问题。
  5. 如权利要求4所述的系统故障处理方法,其特征在于,所述若所述预设诊断库中存在所述类似故障问题,获取所述类似故障问题的问题数量,并判断所述问题数量是否唯一的步骤之后,还包括:
    若所述问题数量不唯一,则根据所述类似故障问题与所述当前故障参数的匹配度,将所述类似故障问题中的多个关联问题进行排序,生成并显示对应的关联问题列表;
    基于所述关联问题列表,接收用户选择操作触发的选择指令,并根据所述选择指令,在所述关联问题列表中确定所述当前故障参数对应的目标故障问题;
    在所述预设诊断库中获取所述目标故障问题对应的故障解决方案,并将所述故障解决方案推送至所述当前终端,以便指导用户解决当前故障问题。
  6. 如权利要求1所述的系统故障处理方法,其特征在于,所述在接收到故障诊断指令时,获取当前终端的故障界面信息,并在所述故障界面信息中获取被诊断系统的当前故障参数的步骤之前,还包括:
    根据已验证的故障参数形成故障参数数据记录,并将所述故障参数数据记录存储至所述预设诊断库中,其中,所述已验证的故障参数包括:配置属性、告警属性、性能指标属性、故障原因属性和解决方案参数;
    建立所述故障参数和解决方案参数的映射关系,并将所述映射关系对应关联存储至所述预设诊断库中。
  7. 如权利要求1所述的系统故障处理方法,其特征在于,所述预设诊断库包括:软件故障编号、软件故障名称、配置参数、告警参数、性能指标参数、故障原因参数、解决办法参数和是否软件缺陷标识等;所述配置参数包括配置参数编号和配置参数权值,所述告警参数包括告警参数编号和告警参数权值,所述性能指标参数包括性能指标编号和性能指标权值。
  8. 一种系统故障处理装置,其特征在于,所述系统故障处理装置包括:
    参数获取模块,用于在接收到故障诊断指令时,获取当前终端的故障界面信息,并在所述故障界面信息中获取被诊断系统的当前故障参数;
    故障诊断模块,用于将所述当前故障参数与预设诊断库进行匹配,判断所述预设诊断库中是否存在类似故障问题;
    故障解决模块,用于若所述预设诊断库中存在所述类似故障问题,则在所述预设诊断库中获取所述类似故障问题对应的故障解决方案,并将所述故障解决方案推送至所述当前终端,以便指导用户解决当前故障问题。
  9. 如权利要求8所述的系统故障处理装置,其特征在于,所述系统故障处理装置包括:
    上报模块,用于若所述预设诊断库中不存在所述类似故障问题,则将所述故障界面信息以及当前故障参数上报至预设处理端;
    推送模块,用于在接收所述预设处理端反馈的当前故障解决方案时,将所述当前故障解决方案推送至所述终端,并将所述当前故障参数与当前故障解决方案添加至所述预设诊断库。
  10. 如权利要求8所述的系统故障处理装置,其特征在于,所述故障解决模块包括:
    二次诊断单元,用于若接收到用户触发的二次诊断指令时,获取所述当前终端的二次界面信息,获取所述当前终端的终端信息,并在所述二次界面信息中获取所述被诊断系统的二次故障参数;
    故障上报单元,用于将所述当前故障参数、故障解决方案、终端信息、二次界面信息以及二次故障参数上报至预设处理端;
    二次推送单元,用于在接收到所述预设处理端反馈的二次解决方案时,将所述二次解决方案推送至所述终端,并将所述二次故障参数以及所述二次解决方案添加至所述预设诊断库。
  11. 如权利要求8所述的系统故障处理装置,其特征在于,所述故障解决模块包括:
    数量判断单元,用于若所述预设诊断库中存在所述类似故障问题,获取所述类似故障问题的问题数量,并判断所述问题数量是否唯一;
    列表生成单元,用于若所述问题数量不唯一,则根据所述类似故障问题与所述当前故障参数的匹配度,将所述类似故障问题中的多个关联问题进行排序,生成并显示对应的关联问题列表;
    问题确认单元,用于基于所述关联问题列表,接收用户选择操作触发的选择指令,并根据所述选择指令,在所述关联问题列表中确定所述当前故障参数对应的目标故障问题。
  12. 如权利要求8所述的系统故障处理装置,其特征在于,所述故障解决模块包括:
    第一推送单元,用于在所述预设诊断库中获取所述目标故障问题对应的故障解决方案,并将所述故障解决方案推送至所述当前终端,以便指导用户解决当前故障问题。
    第二推送单元,若所述问题数量唯一,则在所述预设诊断库中获取所述类似故障问题对应的故障解决方案,并将所述故障解决方案推送至所述当前终端,以便指导用户解决当前故障问题。
  13. 一种系统故障处理设备,其特征在于,所述系统故障处理设备包括处理器、存储器、以及存储在所述存储器上并可被所述处理器执行的计算机可读指令,其中所述计算机可读指令被所述处理器执行时,实现如权利要求1所述的系统故障处理方法的步骤。
  14. 一种系统故障处理设备,其特征在于,所述系统故障处理设备包括处理器、存储器、以及存储在所述存储器上并可被所述处理器执行的计算机可读指令,其中所述计算机可读指令被所述处理器执行时,实现如权利要求2所述的系统故障处理方法的步骤。
  15. 一种系统故障处理设备,其特征在于,所述系统故障处理设备包括处理器、存储器、以及存储在所述存储器上并可被所述处理器执行的计算机可读指令,其中所述计算机可读指令被所述处理器执行时,实现如权利要求3所述的系统故障处理方法的步骤。
  16. 一种系统故障处理设备,其特征在于,所述系统故障处理设备包括处理器、存储器、以及存储在所述存储器上并可被所述处理器执行的计算机可读指令,其中所述计算机可读指令被所述处理器执行时,实现如权利要求4所述的系统故障处理方法的步骤。
  17. 一种计算机可读存储介质,其特征在于,所述计算机可读存储介质上存储有计算机可读指令,其中所述计算机可读指令被处理器执行时,实现如权利要求1所述的系统故障处理方法的步骤。
  18. 一种计算机可读存储介质,其特征在于,所述计算机可读存储介质上存储有计算机可读指令,其中所述计算机可读指令被处理器执行时,实现如权利要求2所述的系统故障处理方法的步骤。
  19. 一种计算机可读存储介质,其特征在于,所述计算机可读存储介质上存储有计算机可读指令,其中所述计算机可读指令被处理器执行时,实现如权利要求3所述的系统故障处理方法的步骤。
  20. 一种计算机可读存储介质,其特征在于,所述计算机可读存储介质上存储有计算机可读指令,其中所述计算机可读指令被处理器执行时,实现如权利要求4所述的系统故障处理方法的步骤。
PCT/CN2018/103769 2018-07-18 2018-09-03 系统故障处理方法、装置、设备及存储介质 Ceased WO2020015064A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810791075.4A CN109726071A (zh) 2018-07-18 2018-07-18 系统故障处理方法、装置、设备及存储介质
CN201810791075.4 2018-07-18

Publications (1)

Publication Number Publication Date
WO2020015064A1 true WO2020015064A1 (zh) 2020-01-23

Family

ID=66294676

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/103769 Ceased WO2020015064A1 (zh) 2018-07-18 2018-09-03 系统故障处理方法、装置、设备及存储介质

Country Status (2)

Country Link
CN (1) CN109726071A (zh)
WO (1) WO2020015064A1 (zh)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115185735A (zh) * 2022-08-04 2022-10-14 中国平安财产保险股份有限公司 软件故障识别自愈方法及相关设备
CN115203390A (zh) * 2022-06-23 2022-10-18 拉扎斯网络科技(上海)有限公司 故障处理方法、装置、设备、程序产品及存储介质
CN115310503A (zh) * 2021-05-06 2022-11-08 芜湖美智空调设备有限公司 故障诊断方法、装置及计算机可读存储介质
CN116257433A (zh) * 2022-12-22 2023-06-13 南方电网数字电网研究院有限公司 一种基于国产芯片底层框架的应用软件测试故障分析方法

Families Citing this family (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110307990B (zh) * 2019-06-05 2020-12-25 中国中车股份有限公司 一种柴油机机油系统故障的智能诊断方法及系统
CN111967614B (zh) * 2020-09-03 2024-02-06 中国联合网络通信集团有限公司 一种人工智能学习方法及装置
CN112235638B (zh) * 2020-10-10 2023-04-25 深圳创维-Rgb电子有限公司 异常信息定位方法、系统、服务器及存储介质
CN112383589B (zh) * 2020-10-26 2022-09-13 珠海格力电器股份有限公司 移动试验车中管理系统的数据处理方法及装置
CN112348211B (zh) * 2020-11-05 2023-09-26 通用电气(武汉)自动化有限公司 一种过程诊断方法、装置、设备和介质
CN112612258B (zh) * 2020-12-04 2025-05-23 武汉第二船舶设计研究所(中国船舶重工集团公司第七一九研究所) 载人运载器的故障检测方法及检测系统
CN112866839B (zh) * 2021-01-05 2022-12-02 深圳市双翼科技股份有限公司 万兆无源光网络终端设备掉电告警装置以及方法
CN113810457A (zh) * 2021-04-06 2021-12-17 北京京东拓先科技有限公司 业务访问异常上报方法、装置及可读存储介质和电子设备
CN113254248B (zh) * 2021-05-26 2024-07-09 统信软件技术有限公司 一种故障诊断方法、系统及计算设备
CN113655770B (zh) * 2021-07-02 2024-10-29 上海乐意修科技有限公司 一种汽车故障诊断教学系统及方法
CN113704578A (zh) * 2021-09-09 2021-11-26 广东粤港澳大湾区硬科技创新研究院 一种故障告警诊断方法及系统
CN114371675A (zh) * 2021-12-31 2022-04-19 四川德胜集团钒钛有限公司 一种运行设备的异常预测运维系统和方法
CN115629919A (zh) * 2022-08-26 2023-01-20 湖南三湘银行股份有限公司 一种快速故障系统切换的方法及装置
CN115512823A (zh) * 2022-09-27 2022-12-23 深圳市联影高端医疗装备创新研究院 设备异常处理方法、装置、异常处理系统和设备
CN120476360A (zh) * 2023-01-16 2025-08-12 西门子股份公司 系统故障诊断的方法、装置、计算机设备
CN116298869A (zh) * 2023-03-03 2023-06-23 苏州汇川联合动力系统有限公司 过流故障识别方法、电机驱动单元及计算机可读存储介质
CN117035747B (zh) * 2023-10-09 2024-02-02 国网山东省电力公司博兴县供电公司 一种机房多系统故障诊断处理方法、系统、设备及介质
CN118839864A (zh) * 2024-08-22 2024-10-25 深圳友讯达科技股份有限公司 基于电力设备检修的ftu信息调取方法及系统

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103678566A (zh) * 2013-12-09 2014-03-26 北京奇虎科技有限公司 提供移动终端故障问题解决方案的方法、服务器和系统
CN104281526A (zh) * 2014-10-28 2015-01-14 用友软件股份有限公司 故障反馈方法、故障反馈系统和终端
CN105277224A (zh) * 2014-07-01 2016-01-27 珠海格力电器股份有限公司 一种空调的故障内容显示方法及系统
CN106896804A (zh) * 2017-04-24 2017-06-27 南京越博动力系统股份有限公司 一种纯电动汽车远程监控故障诊断报警系统及方法
CN106909973A (zh) * 2015-12-17 2017-06-30 北京奇虎科技有限公司 一种车辆故障的处理方法和系统

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103473143A (zh) * 2012-06-07 2013-12-25 中兴通讯股份有限公司 故障修复的处理、故障的修复方法及装置
CN102843612A (zh) * 2012-08-31 2012-12-26 深圳市龙视传媒有限公司 一种语音智能处理数字电视终端故障的方法和装置
CN103793313B (zh) * 2014-02-20 2017-12-19 Tcl通讯(宁波)有限公司 一种移动终端故障记录方法及其系统
CN103838637A (zh) * 2014-03-03 2014-06-04 江苏智联天地科技有限公司 基于数据挖掘的终端自主故障诊断与恢复方法
CN105740140A (zh) * 2014-12-10 2016-07-06 中兴通讯股份有限公司 软件系统故障诊断方法、服务器及系统
CN106091244A (zh) * 2016-06-07 2016-11-09 珠海格力电器股份有限公司 空调故障处理的方法及装置
CN107490494A (zh) * 2016-06-13 2017-12-19 许斌 一种设备故障监测系统
KR101699034B1 (ko) * 2016-06-16 2017-01-23 (주)그린정보시스템 분산전원 대상의 지능형 자율 제어 장치 및 자율 제어 방법
CN107566170B (zh) * 2017-08-24 2020-07-14 广东电网有限责任公司珠海供电局 一种基于规则库的配网自动化远动通道自动检测方法
CN107862393A (zh) * 2017-10-31 2018-03-30 广西宜州市联森网络科技有限公司 一种it运维管理系统
CN108256654B (zh) * 2018-01-02 2022-06-21 中电长城(长沙)信息技术有限公司 一种设备报障和故障诊断方法及系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103678566A (zh) * 2013-12-09 2014-03-26 北京奇虎科技有限公司 提供移动终端故障问题解决方案的方法、服务器和系统
CN105277224A (zh) * 2014-07-01 2016-01-27 珠海格力电器股份有限公司 一种空调的故障内容显示方法及系统
CN104281526A (zh) * 2014-10-28 2015-01-14 用友软件股份有限公司 故障反馈方法、故障反馈系统和终端
CN106909973A (zh) * 2015-12-17 2017-06-30 北京奇虎科技有限公司 一种车辆故障的处理方法和系统
CN106896804A (zh) * 2017-04-24 2017-06-27 南京越博动力系统股份有限公司 一种纯电动汽车远程监控故障诊断报警系统及方法

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115310503A (zh) * 2021-05-06 2022-11-08 芜湖美智空调设备有限公司 故障诊断方法、装置及计算机可读存储介质
CN115203390A (zh) * 2022-06-23 2022-10-18 拉扎斯网络科技(上海)有限公司 故障处理方法、装置、设备、程序产品及存储介质
CN115185735A (zh) * 2022-08-04 2022-10-14 中国平安财产保险股份有限公司 软件故障识别自愈方法及相关设备
CN116257433A (zh) * 2022-12-22 2023-06-13 南方电网数字电网研究院有限公司 一种基于国产芯片底层框架的应用软件测试故障分析方法

Also Published As

Publication number Publication date
CN109726071A (zh) 2019-05-07

Similar Documents

Publication Publication Date Title
WO2020015064A1 (zh) 系统故障处理方法、装置、设备及存储介质
WO2020015067A1 (zh) 数据采集方法、装置、设备及存储介质
WO2020253034A1 (zh) 客户端埋点测试方法、装置、设备及存储介质
WO2020119369A1 (zh) 智能it运维故障定位方法、装置、设备及可读存储介质
WO2020119115A1 (zh) 数据审核方法、装置、设备及存储介质
WO2021027143A1 (zh) 信息推送方法、装置、设备及计算机可读存储介质
WO2020147264A1 (zh) 多系统日志数据的监控方法、装置、设备及可读存储介质
WO2020048047A1 (zh) 系统故障的预警方法、装置、设备及存储介质
WO2020087978A1 (zh) 风控审核模型的生成方法、装置、设备及存储介质
WO2020258657A1 (zh) 异常检测方法、装置、计算机设备及存储介质
WO2020062658A1 (zh) 合同生成方法、装置、设备及存储介质
WO2020147385A1 (zh) 数据录入方法、装置、终端及计算机可读存储介质
WO2020253135A1 (zh) 自动化分析方法、用户设备、存储介质及装置
WO2020073688A1 (zh) 预测网络设备异常的方法、装置、设备及存储介质
WO2020073494A1 (zh) 网页后门检测方法、设备、存储介质及装置
WO2021003923A1 (zh) FreeSWITCH监控方法、设备、存储介质及装置
WO2020233089A1 (zh) 测试用例生成方法、装置、终端及计算机可读存储介质
WO2021003956A1 (zh) 产品信息的管理方法、装置、设备及存储介质
WO2020233073A1 (zh) 区块链环境检测方法、设备、装置及存储介质
WO2020019405A1 (zh) 数据库监控方法、装置、设备及可读存储介质
WO2020015060A1 (zh) 用电量异常评估方法、装置、设备和计算机存储介质
WO2021017332A1 (zh) 语音控制报错方法、电器及计算机可读存储介质
WO2012015164A1 (ko) 변전자동화시스템의 클라이언트 적합성 시험 장치 및 그 방법
WO2020077832A1 (zh) 云桌面的访问方法、装置、设备及存储介质
WO2020062641A1 (zh) 识别用户角色的方法、用户设备、存储介质及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18926900

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18926900

Country of ref document: EP

Kind code of ref document: A1