Fault processing method, device, equipment, medium and program product

Abstract

The invention provides a fault processing method and device, equipment, a medium and a program product, which can be applied to the field of information technology or financial science and technology. The method comprises the following steps: acquiring fault data of a target subsystem, a target user corresponding to the target subsystem and a terminal of the target user; obtaining candidate fault processing schemes for the fault data from a plurality of subsystems by using a preset clustering model; under the condition that the login token of the target user is not expired, sending a candidate fault processing scheme to the terminal; and in response to receiving a target fault processing scheme sent by the terminal, executing the target fault processing scheme, the target fault processing scheme being selected from the candidate fault processing scheme by the target user.

Description

Technical Field

[0001] The present disclosure relates to the field of information technology or financial technology, and more specifically to a fault handling method, device, equipment, medium and program product. Background Art

[0002] With the popularization of online banking services, more and more system operation and maintenance work is involved, and the banking system will interact with third-party systems and upstream and downstream systems, which is highly complex. When problems occur in the system, only the corresponding developers know the solutions, while the personnel responsible for operation and maintenance are less familiar with the system and it takes a long time to solve the problems in the system, which reduces system stability. Summary of the invention

[0003] In view of the above problems, the present disclosure provides methods, devices, equipment, media and program products for improving fault handling.

[0004] According to the first aspect of the present disclosure, a fault handling method is provided, comprising: obtaining fault data of a target subsystem, a target user corresponding to the target subsystem, and a terminal of the target user; obtaining candidate fault handling solutions for the fault data from the multiple subsystems using a preset clustering model; sending the candidate fault handling solutions to the terminal when a login token of the target user has not expired; and executing the target fault handling solution in response to receiving the target fault handling solution sent by the terminal, wherein the target fault handling solution is obtained by the target user modifying parameters of the candidate fault handling solution based on the target subsystem.

[0005] According to an embodiment of the present disclosure, fault labels corresponding to fault handling solutions are also stored in the above-mentioned multiple subsystems, and the above-mentioned fault labels represent the fault data corresponding to the above-mentioned fault handling solutions. The above-mentioned use of a preset clustering model to obtain candidate fault handling solutions for the fault data from the above-mentioned multiple subsystems includes: performing feature extraction on the above-mentioned fault data to obtain a fault feature vector; inputting the above-mentioned fault feature vector into the preset clustering model to obtain candidate fault labels related to the above-mentioned fault data, wherein the above-mentioned preset clustering model is obtained by clustering the above-mentioned fault labels; and determining the fault handling solution corresponding to the above-mentioned candidate fault label as the candidate fault handling solution.

[0006] According to an embodiment of the present disclosure, the above method also includes: in response to receiving a login instruction from the above terminal, obtaining the identity identifier and biometric information in the above login instruction; sending the identity identifier and biometric information of the above target user to the above target subsystem; in response to the matching result returned by the above target subsystem indicating a successful match, generating a login token based on the above identity identifier; and sending the above token to the above terminal.

[0007] According to an embodiment of the present disclosure, in the case where the candidate fault handling solutions include a fault handling solution for the first subsystem, the fault handling solution for the first subsystem is desensitized.

[0008] According to an embodiment of the present disclosure, the above-mentioned desensitizing processing is performed on the fault handling solution of the above-mentioned first subsystem, including: determining the data to be desensitized in the above-mentioned preset fault handling solution and the desensitizing operation corresponding to the above-mentioned data to be desensitized according to preset desensitizing rules; performing the above-mentioned desensitizing operation on the above-mentioned data to be desensitized to obtain the desensitized fault handling solution.

[0009] According to an embodiment of the present disclosure, the method further includes: when the target fault handling solution is a fault handling solution of the first subsystem, storing the target handling solution in the target subsystem.

[0010] According to an embodiment of the present disclosure, the clustering algorithm adopted by the above clustering model includes any one of a K-means algorithm, a spectral clustering algorithm, a deep clustering algorithm, and an agglomerative clustering algorithm.

[0011] A second aspect of the present disclosure provides a fault handling device, which is installed on an operation and maintenance platform, and the operation and maintenance platform communicates data with multiple subsystems, including: a fault data acquisition module, used to acquire the fault data of a target subsystem, a target user corresponding to the target subsystem, and a terminal of the target user; a fault handling solution acquisition module, used to use a preset clustering model to acquire candidate fault handling solutions for the fault data from the multiple subsystems; a sending module, used to send the candidate fault handling solutions to the terminal if the login token of the target user has not expired; and an execution module, used to execute the target fault handling solution in response to receiving the target fault handling solution sent by the terminal, the target fault handling solution being obtained by the target user modifying the parameters of the candidate fault handling solution based on the target subsystem.

[0012] According to an embodiment of the present disclosure, fault labels corresponding to fault handling solutions are also stored in the above-mentioned multiple subsystems, and the above-mentioned fault labels represent fault data corresponding to the above-mentioned fault handling solutions. The above-mentioned fault handling solution acquisition module includes: a feature extraction submodule, which is used to extract features from the above-mentioned fault data to obtain a fault feature vector; an input submodule, which is used to input the above-mentioned fault feature vector into a preset clustering model to obtain candidate fault labels related to the above-mentioned fault data, wherein the above-mentioned preset clustering model is obtained by clustering the above-mentioned fault labels; a determination submodule, which is used to determine the fault handling solution corresponding to the above-mentioned candidate fault label as a candidate fault handling solution.

[0013] According to an embodiment of the present disclosure, the above-mentioned device also includes: a feature acquisition module, which is used to obtain the identity identification and biometric information in the above-mentioned login instruction in response to receiving the login instruction of the above-mentioned terminal; a feature sending module, which is used to send the identity identification and biometric information of the above-mentioned target user to the above-mentioned target subsystem; a generation module, which is used to generate a login token based on the above-mentioned identity identification in response to the matching result returned by the above-mentioned target subsystem indicating a successful match; and a terminal sending module, which is used to send the above-mentioned token to the above-mentioned terminal.

[0014] According to an embodiment of the present disclosure, the above-mentioned device also includes: a desensitizing module, which is used to desensitize the fault handling solution of the above-mentioned first subsystem when the above-mentioned candidate fault handling solutions include the fault handling solution of the first subsystem.

[0015] According to an embodiment of the present disclosure, the above-mentioned desensitizing module includes: a desensitizing operation determination submodule, which is used to determine the data to be desensitized in the above-mentioned preset fault handling solution and the desensitizing operation corresponding to the above-mentioned data to be desensitized according to preset desensitization rules; a desensitizing submodule, which is used to perform the above-mentioned desensitizing operation on the above-mentioned data to be desensitized to obtain the fault handling solution after desensitization.

[0016] According to an embodiment of the present disclosure, the device further includes: a storage module, configured to store the target fault handling solution in the target subsystem when the target fault handling solution is a fault handling solution of the first subsystem.

[0017] A third aspect of the present disclosure provides an electronic device, comprising: one or more processors; and a memory for storing one or more computer programs, wherein the one or more processors execute the one or more computer programs to implement the steps of the above method.

[0018] The fourth aspect of the present disclosure further provides a computer-readable storage medium on which a computer program or instruction is stored, and the steps of the above method are implemented when the above computer program or instruction is executed by a processor.

[0019] The fifth aspect of the present disclosure further provides a computer program product, including a computer program or instructions, which implement the steps of the above method when the above computer program or instructions are executed by a processor.

[0020] According to an embodiment of the present disclosure, by acquiring the fault data of a target subsystem, a target user corresponding to the target subsystem and a terminal of the target user, and acquiring candidate fault handling solutions for the fault data according to a preset clustering model, and when the login token of the target user has not expired, the candidate fault handling solutions are sent to the terminal, thereby handling the fault of the target subsystem in response to the target fault handling solution selected by the target user. The operation and maintenance personnel only need to select the corresponding fault handling solution from the candidate solutions to execute to handle the system fault, and there is no need for the corresponding developers to perform specific debugging. This speeds up the fault handling process while improving the system stability, further decoupling the developers and the system, and reducing the difficulty of system operation and maintenance. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] The above contents and other objects, features and advantages of the present disclosure will become more apparent through the following description of the embodiments of the present disclosure with reference to the accompanying drawings, in which:

[0022] Figure 1 The following schematically shows an application scenario diagram of the fault handling method and device according to an embodiment of the present disclosure;

[0023] Figure 2 A flowchart of a fault handling method according to an embodiment of the present disclosure is schematically shown;

[0024] Figure 3 A schematic diagram schematically shows a maintenance personnel inputting instructions according to an embodiment of the present disclosure;

[0025] Figure 4 A schematic diagram of a fault handling solution after desensitization processing according to an embodiment of the present disclosure is schematically shown;

[0026] Figure 5 The structure block diagram of the fault handling device according to the embodiment of the present disclosure is schematically shown;

[0027] Figure 6 A block diagram of an electronic device suitable for implementing a fault handling method according to an embodiment of the present disclosure is schematically shown. DETAILED DESCRIPTION

[0028] Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of the present disclosure. In the following detailed description, for ease of explanation, many specific details are set forth to provide a comprehensive understanding of the embodiments of the present disclosure. However, it is apparent that one or more embodiments may also be implemented without these specific details. In addition, in the following description, descriptions of known structures and technologies are omitted to avoid unnecessary confusion of the concepts of the present disclosure.

[0029] The terms used herein are only for describing specific embodiments and are not intended to limit the present disclosure. The terms "comprise", "include", etc. used herein indicate the existence of the features, steps, operations and / or components, but do not exclude the existence or addition of one or more other features, steps, operations or components.

[0030] All terms (including technical and scientific terms) used herein have the meanings commonly understood by those skilled in the art unless otherwise defined. It should be noted that the terms used herein should be interpreted as having a meaning consistent with the context of this specification and should not be interpreted in an idealized or overly rigid manner.

[0031] When using expressions such as "at least one of A, B, and C, etc.", they should generally be interpreted according to the meaning of the expression commonly understood by those skilled in the art (for example, "a system having at least one of A, B, and C" should include but is not limited to a system having A alone, B alone, C alone, A and B, A and C, B and C, and / or A, B, C, etc.).

[0032] It should be noted that the fault handling method, apparatus, equipment, medium and program product disclosed in the present invention can be used in the field of financial technology, and can also be used in any field other than the field of financial technology. The present disclosure does not limit the application field of the fault handling method, apparatus, equipment, medium and program product.

[0033] In the technical solution of the present disclosure, the user information (including but not limited to user personal information, user image information, user device information, such as location information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved are all information and data authorized by the user or fully authorized by all parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of the relevant data comply with relevant laws, regulations and standards, take necessary confidentiality measures, do not violate public order and good morals, and provide corresponding operation entrances for users to choose to authorize or refuse.

[0034] In the scenario of using personal information for automated decision-making, the methods, devices, and systems provided by the embodiments of the present disclosure provide users with corresponding operation portals for users to choose to agree or reject the automated decision-making results; if the user chooses to reject, the expert decision-making process will be entered. The expression "automated decision-making" here refers to the activity of automatically analyzing and evaluating a person's behavioral habits, interests and hobbies, or economic, health, credit status, etc. through computer programs, and making decisions. The expression "expert decision-making" here refers to the activity of making decisions by people who specialize in a certain field, have specialized experience, knowledge and skills, and have reached a certain level of professionalism.

[0035] In the technical solution of the present disclosure, the user information (including but not limited to user personal information, user image information, user device information, such as location information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved are all information and data authorized by the user or fully authorized by all parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of the relevant data comply with relevant laws, regulations and standards, take necessary confidentiality measures, do not violate public order and good morals, and provide corresponding operation entrances for users to choose to authorize or refuse.

[0036] In the scenario of using personal information for automated decision-making, the methods, devices, and systems provided by the embodiments of the present disclosure provide users with corresponding operation portals for users to choose to agree or reject the automated decision-making results; if the user chooses to reject, the expert decision-making process will be entered. The expression "automated decision-making" here refers to the activity of automatically analyzing and evaluating a person's behavioral habits, interests and hobbies, or economic, health, credit status, etc. through computer programs, and making decisions. The expression "expert decision-making" here refers to the activity of making decisions by people who specialize in a certain field, have specialized experience, knowledge and skills, and have reached a certain level of professionalism.

[0037] With the popularization of online banking services, system operation and maintenance work faces more and more challenges. Bank systems not only need to handle internal business processes, but also need to interact with third-party systems and upstream and downstream systems, which increases the complexity of the system. Due to the increase in system complexity, relevant operation and maintenance personnel may have low familiarity with the system, which leads to a longer time to locate and solve the problem when the system has problems, reducing system stability and business continuity.

[0038] An embodiment of the present disclosure provides a fault handling method, which is applied to an operation and maintenance platform, and the operation and maintenance platform communicates data with multiple subsystems. The method includes: obtaining fault data of a target subsystem, a target user corresponding to the target subsystem, and a terminal of the target user; using a preset clustering model, obtaining candidate fault handling solutions for the fault data from multiple subsystems; sending the candidate fault handling solutions to the terminal when the login token of the target user has not expired; and executing the target fault handling solution in response to receiving the target fault handling solution sent by the terminal, where the target fault handling solution is selected by the target user from the candidate fault handling solutions.

[0039] Figure 1 The application scenario diagram of the fault handling method and device according to the embodiments of the present disclosure is schematically shown.

[0040] like Figure 1As shown, the application scenario 100 according to this embodiment may include a first terminal device 101, a second terminal device 102, a third terminal device 103, a network 104, a first server 105, and a second server 106. The network 104 is used to provide a medium for a communication link between the first terminal device 101, the second terminal device 102, the third terminal device 103, the first server 105, and the second server 106. The network 104 may include various connection types, such as wired, wireless communication links, or optical fiber cables, etc.

[0041] The user may use the first terminal device 101, the second terminal device 102, and the third terminal device 103 to interact with the first server 105 through the network 104 to receive or send messages, etc. Various communication client applications may be installed on the first terminal device 101, the second terminal device 102, and the third terminal device 103, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social platform software, etc. (only for example).

[0042] The first terminal device 101, the second terminal device 102, and the third terminal device 103 may be various electronic devices having display screens and supporting web browsing, including but not limited to smart phones, tablet computers, laptop computers, desktop computers, and the like.

[0043] The first server 105 may be a server that provides operation and maintenance services, and the second server 106 may be a server that provides services for the subsystem. The first server 105 and the second server 106 may communicate data via the network 104 .

[0044] It should be noted that the fault handling method provided in the embodiment of the present disclosure can generally be executed by the first server 105. Accordingly, the fault handling device provided in the embodiment of the present disclosure can generally be set in the first server 105. The fault handling method provided in the embodiment of the present disclosure can also be executed by a server or server cluster that is different from the first server 105 and can communicate with the first terminal device 101, the second terminal device 102, the third terminal device 103 and / or the first server 105. Accordingly, the fault handling device provided in the embodiment of the present disclosure can also be set in a server or server cluster that is different from the first server 105 and can communicate with the first terminal device 101, the second terminal device 102, the third terminal device 103 and / or the first server 105.

[0045] It should be understood that Figure 1 The number of terminal devices, networks and servers in the embodiment is only for illustration. Any number of terminal devices, networks and servers may be provided according to implementation requirements.

[0046] The following will be based on Figure 1 The scene described by Figure 2~Figure 4 The fault handling method of the disclosed embodiment is described in detail.

[0047] Figure 2 The flowchart of the fault handling method according to the embodiment of the present disclosure is schematically shown.

[0048] like Figure 2 As shown, the fault handling method of this embodiment includes operations S210 to S240.

[0049] In operation S210, fault data of a target subsystem, a target user corresponding to the target subsystem, and a terminal of the target user are acquired.

[0050] According to an embodiment of the present disclosure, the above-mentioned fault data may be, for example, fault data such as memory usage exceeding a preset threshold or an abnormal calling interface; the above-mentioned target user may be, for example, an operation and maintenance personnel corresponding to the target subsystem.

[0051] In operation S220 , candidate fault processing solutions for the fault data are obtained from a plurality of subsystems using a preset clustering model.

[0052] According to the embodiments of the present disclosure, the above-mentioned candidate fault handling solutions can be the fault handling solutions in the target subsystem or the fault handling solutions in other subsystems. When multiple fault handling solutions are obtained through clustering, a preset number of fault handling solutions can be selected as candidate fault handling solutions according to the clustering matching degree. Alternatively, only the fault handling solutions in the target subsystem can be used as candidate fault handling solutions, and the fault handling solutions in other subsystems can be used as reference fault handling solutions and pushed to the target user together.

[0053] In operation S230 , if the login token of the target user has not expired, a candidate fault handling solution is sent to the terminal.

[0054] In operation S240 , in response to receiving the target fault processing solution sent by the terminal, the target fault processing solution is executed.

[0055] The target fault handling solution is obtained by the target user modifying the parameters of the candidate fault handling solutions based on the target subsystem.

[0056] According to an embodiment of the present disclosure, the above-mentioned target fault handling solution can be obtained by the user selecting the fault handling solution that is most suitable for the target subsystem after receiving multiple candidate fault handling solutions and modifying some parameters therein, or it can be obtained by directly selecting the target fault handling solution from the candidate fault handling solutions. The present disclosure does not impose any restrictions on this.

[0057] According to an embodiment of the present disclosure, by acquiring the fault data of a target subsystem, a target user corresponding to the target subsystem and a terminal of the target user, and acquiring candidate fault handling solutions for the fault data according to a preset clustering model, and when the login token of the target user has not expired, the candidate fault handling solutions are sent to the terminal, thereby handling the fault of the target subsystem in response to the target fault handling solution selected by the target user. The operation and maintenance personnel only need to select the corresponding fault handling solution from the candidate solutions to execute to handle the system fault, and there is no need for the corresponding developers to perform specific debugging. This speeds up the fault handling process while improving the system stability, further decoupling the developers and the system, and reducing the difficulty of system operation and maintenance.

[0058] According to an embodiment of the present disclosure, fault labels corresponding to fault handling solutions are also stored in multiple subsystems, and the fault labels represent fault data corresponding to the fault handling solutions. A preset clustering model is used to obtain candidate fault handling solutions for the fault data from multiple subsystems, including: extracting features from the fault data to obtain a fault feature vector; inputting the fault feature vector into the preset clustering model to obtain candidate fault labels related to the fault data, wherein the preset clustering model is obtained by clustering the fault labels; and determining the fault handling solution corresponding to the candidate fault label as the candidate fault handling solution.

[0059] According to the embodiment of the present disclosure, the above fault label can be, for example, T=<A,B,C,D,E,F,…> An n-tuple of fault labels, where the fault label may include the category to which it belongs. For example, A can have two values. When the value of A is 1, it represents accounting business, and when the value of A is 0, it represents non-accounting business. B can represent the memory usage rate. When the value of B is 1, it represents the memory usage rate is less than 50%, 2 represents the memory usage rate is between 50% and 90%, and 3 represents the memory usage rate is greater than 90%. C can represent the system abnormality indicator. When the interface call times out, it can be set to 2, and if it does not time out, it can be set to 1. If a fault label has no set value, it can be set to 0.

[0060] According to the embodiment of the present disclosure, the label can be used as a feature value to train a preset clustering model, and the clustering results are characterized under similar categories or similar fault labels. These candidate fault handling solutions can be used as reference processing or directly implemented.

[0061] According to an embodiment of the present disclosure, the clustering algorithm adopted by the above clustering model includes any one of a K-means algorithm, a spectral clustering algorithm, a deep clustering algorithm, and an agglomerative clustering algorithm.

[0062] According to the embodiments of the present disclosure, after a problem occurs in the target subsystem, feature extraction is performed on the fault data to obtain a feature vector, and the feature vector is input into a pre-trained clustering model to obtain a candidate fault handling solution. This can reduce the time required to determine the candidate fault handling solution, and the candidate fault handling solution determined to be more compatible with the fault of the target subsystem. Furthermore, clustering through feature vectors can speed up the clustering process and ensure system stability.

[0063] According to an embodiment of the present disclosure, the above method also includes: in response to receiving a login instruction from a terminal, obtaining an identity identifier and biometric information in the login instruction; sending the identity identifier and biometric information of the target user to a target subsystem; in response to a matching result returned by the target subsystem indicating a successful match, generating a login token based on the identity identifier; and sending the token to the terminal.

[0064] According to an embodiment of the present disclosure, the above-mentioned identity identification may be, for example, an employee number, an identity number, etc., and the above-mentioned biometric information may be, for example, facial information, fingerprint information, iris information, etc. The relevant personnel may send information to the operation and maintenance platform through a mobile phone or other device, and the operation and maintenance platform inquires whether the corresponding mobile phone number is in the blacklist and the whitelist. If it is in the whitelist, the operation and maintenance platform sends a message to the relevant personnel asking them to enter the employee number. After receiving the input employee number, the system determines whether the employee number exists. If it exists, a hyperlink is sent to the terminal device of the relevant personnel. After the relevant personnel clicks on the node, the client camera is awakened to identify the relevant personnel. The biometric information obtained by the identity identification is encrypted and sent to the operation and maintenance platform. After decryption, the system compares the identity identification to determine whether the biometric information is consistent with that retained by the system. If it is inconsistent, the relevant personnel are informed to re-verify. If the number of inconsistencies exceeds the verification error threshold, it will be added to the blacklist. If it needs to be removed from the blacklist, the administrator of the operation and maintenance platform must be contacted. If it is consistent, it is considered that the login is successful and a login token is generated. Within the valid time of the login token, the operation and maintenance platform can be operated without re-verifying the identity identification and biometric information. After that, the operation and maintenance platform sends the system name of the target subsystem and all candidate fault handling solutions to the relevant personnel. The relevant personnel control the operation and maintenance platform to implement the target fault handling solution by editing instructions.

[0065] Figure 3 A schematic diagram schematically shows an operation and maintenance personnel inputting instructions according to an embodiment of the present disclosure.

[0066] like Figure 3As shown, the relevant staff enters the name of the target subsystem within the validity period of the login token and sends it to the operation and maintenance platform, where "11XXX" can represent the mobile phone number used by the operation and maintenance platform to receive instructions from relevant personnel. The operation and maintenance platform finds all candidate fault handling solutions corresponding to the current target subsystem fault data and sends them to the relevant staff. The relevant staff enters "01". The operation and maintenance platform sends the quick solution of "01" to the relevant staff for review, and then sends the target subsystem number, target fault handling solution number and implementation time to the operation and maintenance platform, for example, "Apply for A system|01|20XX-01-15 20:00". When the operation and maintenance platform receives the instruction, it forwards it to the corresponding terminal of the auditor for review. The auditor can agree or reject it, and forward the corresponding result to the relevant personnel through the operation and maintenance platform. When the review is passed, the relevant target fault handling solution is automatically implemented through the automated operation and maintenance platform at the scheduled time, and the corresponding result is returned to the terminal of the target user.

[0067] According to the embodiment of the present disclosure, the effect of a login token can also be achieved through a whitelist, that is, after a successful login, the corresponding data of the target user is added to the whitelist and a countdown is set. After the countdown ends, the corresponding data is removed from the whitelist so that the relevant personnel can authenticate their identity again.

[0068] According to the embodiments of the present disclosure, the security of the operation and maintenance platform is improved by sending the identity identification and biometric information to the target subsystem for verification, and generating a login token when the match is successful and returning it to the target user terminal. Through the dual verification of the identity identification and biometric information, unauthorized access can be effectively prevented and the operation and maintenance efficiency can be improved.

[0069] According to an embodiment of the present disclosure, the method further includes desensitizing the fault handling solution of the first subsystem when the candidate fault handling solutions include the fault handling solution of the first subsystem.

[0070] According to the embodiment of the present disclosure, the above-mentioned desensitizing processing of the fault handling solution of the first subsystem includes: determining the data to be desensitized in the preset fault handling solution and the desensitizing operation corresponding to the data to be desensitized according to the preset desensitizing rules; performing the desensitizing operation on the data to be desensitized to obtain the desensitized fault handling solution.

[0071] According to the embodiments of the present disclosure, key information in the fault handling solution may be desensitized, for example, server IP or user name and password information may be desensitized.

[0072] Figure 4 A schematic diagram of a fault handling solution after desensitization processing according to an embodiment of the present disclosure is schematically shown.

[0073] like Figure 4As shown, different preset desensitization rules can be set for different key information. For example, for user names, you can choose to invalidate some of the values. For a user named "user2", it can be invalidated as "u***2". For password information, the corresponding password value can be calculated through an encryption algorithm and filled in the corresponding position, or some of the data can be invalidated and displayed to relevant users.

[0074] According to an embodiment of the present disclosure, when the candidate fault handling solutions include a fault handling solution for the first subsystem, different desensitizing operations are performed on different data to be desensitized in the fault handling solution based on preset desensitizing rules, which can effectively protect data security.

[0075] According to an embodiment of the present disclosure, when the target fault processing solution is a fault processing solution of the first subsystem, the target processing solution is stored in the target subsystem.

[0076] According to an embodiment of the present disclosure, if the target fault handling solution that ultimately solves the system problem is not the fault handling solution in the target subsystem, the target fault handling solution can be stored in the target subsystem. If the candidate fault handling solutions obtained through multiple matches are not the fault handling solutions in the target subsystem, the number of unmatched times can be recorded. When the number is greater than a threshold, it is necessary to adjust the parameters of the preset clustering model or check the fault labels.

[0077] According to the embodiment of the present disclosure, after the problem in the subsystem is solved, if it is not solved by the target fault handling solution, the corresponding data can be recorded in the target subsystem.

[0078] Based on the above fault handling method, the present disclosure also provides a fault handling device. Figure 5 The device is described in detail.

[0079] Figure 5 The structural block diagram of the fault handling device according to the embodiment of the present disclosure is schematically shown.

[0080] like Figure 5 As shown, the fault handling device 500 of this embodiment includes a fault data acquisition module 510 , a fault handling solution acquisition module 520 , a sending module 530 and an execution module 540 .

[0081] The fault data acquisition module 510 is used to acquire the fault data of the target subsystem, the target user corresponding to the target subsystem, and the terminal of the target user. In one embodiment, the fault data acquisition module 510 can be used to perform the operation S210 described above, which will not be described in detail here.

[0082] The fault handling solution acquisition module 520 is used to obtain candidate fault handling solutions for fault data from multiple subsystems using a preset clustering model. In one embodiment, the fault handling solution acquisition module 520 can be used to perform the operation S220 described above, which will not be described in detail here.

[0083] The sending module 530 is used to send a candidate fault handling solution to the terminal when the login token of the target user has not expired. In one embodiment, the sending module 530 can be used to perform the operation S230 described above, which will not be repeated here.

[0084] The execution module 540 is used to execute the target fault handling solution in response to receiving the target fault handling solution sent by the terminal, where the target fault handling solution is obtained by the target user modifying the parameters of the candidate fault handling solution based on the target subsystem. In one embodiment, the execution module 540 can be used to execute the operation S240 described above, which will not be repeated here.

[0085] According to an embodiment of the present disclosure, fault labels corresponding to fault handling solutions are also stored in the above-mentioned multiple subsystems, and the above-mentioned fault labels represent fault data corresponding to the above-mentioned fault handling solutions. The above-mentioned fault handling solution acquisition module includes: a feature extraction submodule, which is used to extract features from the above-mentioned fault data to obtain a fault feature vector; an input submodule, which is used to input the above-mentioned fault feature vector into a preset clustering model to obtain candidate fault labels related to the above-mentioned fault data, wherein the above-mentioned preset clustering model is obtained by clustering the above-mentioned fault labels; a determination submodule, which is used to determine the fault handling solution corresponding to the above-mentioned candidate fault label as a candidate fault handling solution.

[0086] According to an embodiment of the present disclosure, the above-mentioned device also includes: a feature acquisition module, which is used to obtain the identity identification and biometric information in the above-mentioned login instruction in response to receiving the login instruction of the above-mentioned terminal; a feature sending module, which is used to send the identity identification and biometric information of the above-mentioned target user to the above-mentioned target subsystem; a generation module, which is used to generate a login token based on the above-mentioned identity identification in response to the matching result returned by the above-mentioned target subsystem indicating a successful match; and a terminal sending module, which is used to send the above-mentioned token to the above-mentioned terminal.

[0087] According to an embodiment of the present disclosure, the above-mentioned device also includes: a desensitizing module, which is used to desensitize the fault handling solution of the above-mentioned first subsystem when the above-mentioned candidate fault handling solutions include the fault handling solution of the first subsystem.

[0088] According to an embodiment of the present disclosure, the above-mentioned desensitizing module includes: a desensitizing operation determination submodule, which is used to determine the data to be desensitized in the above-mentioned preset fault handling solution and the desensitizing operation corresponding to the above-mentioned data to be desensitized according to preset desensitization rules; a desensitizing submodule, which is used to perform the above-mentioned desensitizing operation on the above-mentioned data to be desensitized to obtain the fault handling solution after desensitization.

[0089] According to an embodiment of the present disclosure, the device further includes: a storage module, configured to store the target fault handling solution in the target subsystem when the target fault handling solution is a fault handling solution of the first subsystem.

[0090] According to an embodiment of the present disclosure, any multiple modules among the fault data acquisition module 510, the fault handling solution acquisition module 520, the sending module 530 and the execution module 540 can be combined into one module for implementation, or any one of the modules can be split into multiple modules. Alternatively, at least part of the functions of one or more of these modules can be combined with at least part of the functions of other modules and implemented in one module. According to an embodiment of the present disclosure, at least one of the fault data acquisition module 510, the fault handling solution acquisition module 520, the sending module 530 and the execution module 540 can be at least partially implemented as a hardware circuit, such as a field programmable gate array (FPGA), a programmable logic array (PLA), a system on a chip, a system on a substrate, a system on a package, an application specific integrated circuit (ASIC), or can be implemented by hardware or firmware such as any other reasonable way of integrating or packaging the circuit, or implemented in any one of the three implementation methods of software, hardware and firmware or in a proper combination of any of them. Alternatively, at least one of the fault data acquisition module 510, the fault handling solution acquisition module 520, the sending module 530 and the execution module 540 may be at least partially implemented as a computer program module, and when the computer program module is executed, the corresponding function may be executed.

[0091] Figure 6 A block diagram of an electronic device suitable for implementing a fault handling method according to an embodiment of the present disclosure is schematically shown.

[0092] like Figure 6As shown, the electronic device 600 according to an embodiment of the present disclosure includes a processor 601, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 602 or a program loaded from a storage part 608 to a random access memory (RAM) 603. The processor 601 may include, for example, a general-purpose microprocessor (e.g., a CPU), an instruction set processor and / or a related chipset and / or a dedicated microprocessor (e.g., an application-specific integrated circuit (ASIC)), etc. The processor 601 may also include an onboard memory for caching purposes. The processor 601 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present disclosure.

[0093] In RAM 603, various programs and data required for the operation of electronic device 600 are stored. Processor 601, ROM 602 and RAM 603 are connected to each other via bus 604. Processor 601 performs various operations of the method flow according to the embodiment of the present disclosure by executing the program in ROM 602 and / or RAM 603. It should be noted that the program can also be stored in one or more memories other than ROM 602 and RAM 603. Processor 601 can also perform various operations of the method flow according to the embodiment of the present disclosure by executing the program stored in the one or more memories.

[0094] According to an embodiment of the present disclosure, the electronic device 600 may further include an input / output (I / O) interface 605, which is also connected to the bus 604. The electronic device 600 may further include one or more of the following components connected to the input / output (I / O) interface 605: an input portion 606 including a keyboard, a mouse, etc.; an output portion 607 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage portion 608 including a hard disk, etc.; and a communication portion 609 including a network interface card such as a LAN card, a modem, etc. The communication portion 609 performs communication processing via a network such as the Internet. A drive 610 is also connected to the input / output (I / O) interface 605 as needed. A removable medium 611, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 610 as needed, so that a computer program read therefrom is installed into the storage portion 608 as needed.

[0095] The present disclosure also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments; or may exist independently without being assembled into the device / apparatus / system. The above computer-readable storage medium carries one or more programs, and when the above one or more programs are executed, the method according to the embodiment of the present disclosure is implemented.

[0096] According to an embodiment of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, for example, it may include but is not limited to: a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program, which may be used by or in combination with an instruction execution system, an apparatus or a device. For example, according to an embodiment of the present disclosure, the computer-readable storage medium may include the ROM 602 and / or RAM 603 described above and / or one or more memories other than ROM 602 and RAM 603.

[0097] The embodiment of the present disclosure also includes a computer program product, which includes a computer program, and the computer program contains program code for executing the method shown in the flowchart. When the computer program product is run in a computer system, the program code is used to enable the computer system to implement the fault handling method provided by the embodiment of the present disclosure.

[0098] The above functions defined in the system / device of the embodiment of the present disclosure are performed when the computer program is executed by the processor 601. According to the embodiment of the present disclosure, the system, device, module, unit, etc. described above can be implemented by a computer program module.

[0099] In one embodiment, the computer program may rely on tangible storage media such as optical storage devices, magnetic storage devices, etc. In another embodiment, the computer program may also be transmitted and distributed in the form of signals on a network medium, and downloaded and installed through the communication part 609, and / or installed from a removable medium 611. The program code contained in the computer program may be transmitted using any appropriate network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

[0100] In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 609, and / or installed from the removable medium 611. When the computer program is executed by the processor 601, the above functions defined in the system of the embodiment of the present disclosure are performed. According to the embodiment of the present disclosure, the system, device, apparatus, module, unit, etc. described above can be implemented by a computer program module.

[0101] According to an embodiment of the present disclosure, the program code for executing the computer program provided by the embodiment of the present disclosure can be written in any combination of one or more programming languages. Specifically, these computing programs can be implemented using high-level process and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages ​​include, but are not limited to, Java, C++, python, "C" language or similar programming languages. The program code can be executed entirely on the user computing device, partially on the user device, partially on the remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device can be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computing device (for example, using an Internet service provider to connect through the Internet).

[0102] The flow charts and block diagrams in the accompanying drawings illustrate the possible architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each box in the flow chart or block diagram can represent a module, a program segment, or a part of a code, and the above-mentioned module, program segment, or a part of a code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flow chart, and the combination of the boxes in the block diagram or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0103] It will be appreciated by those skilled in the art that the features described in the various embodiments of the present disclosure may be combined and / or combined in a variety of ways, even if such combinations or combinations are not explicitly described in the present disclosure. In particular, without departing from the spirit and teachings of the present disclosure, the features described in the various embodiments of the present disclosure may be combined and / or combined in a variety of ways. All of these combinations and / or combinations fall within the scope of the present disclosure.

[0104] The embodiments of the present disclosure are described above. However, these embodiments are only for illustrative purposes and are not intended to limit the scope of the present disclosure. Although the embodiments are described above, this does not mean that the measures in the various embodiments cannot be used in combination to advantage. Without departing from the scope of the present disclosure, those skilled in the art may make a variety of substitutions and modifications, which should all fall within the scope of the present disclosure.

Claims

1. A fault handling method, characterized in that: The method is applied to an operation and maintenance platform, the operation and maintenance platform communicates data with multiple subsystems, and the method includes: Acquire fault data of a target subsystem, a target user corresponding to the target subsystem, and a terminal of the target user; Using a preset clustering model, obtaining candidate fault processing solutions for the fault data from the multiple subsystems; If the login token of the target user has not expired, sending the candidate fault handling solution to the terminal; In response to receiving a target fault handling solution sent by the terminal, the target fault handling solution is executed, where the target fault handling solution is obtained by the target user modifying parameters of the candidate fault handling solution based on the target subsystem.

2. The method according to claim 1, characterized in that The multiple subsystems also store fault labels corresponding to the fault processing solutions, the fault labels represent fault data corresponding to the fault processing solutions, and the method of using a preset clustering model to obtain candidate fault processing solutions for the fault data from the multiple subsystems includes: Extracting features from the fault data to obtain a fault feature vector; Inputting the fault feature vector into a preset clustering model to obtain a candidate fault label associated with the fault data, wherein the preset clustering model is obtained by clustering the fault labels; The fault processing solution corresponding to the candidate fault label is determined as a candidate fault processing solution.

3. The method according to claim 1, characterized in that The method further comprises: In response to receiving a login instruction from the terminal, acquiring the identity identifier and biometric information in the login instruction; Sending the target user's identity and biometric information to the target subsystem; In response to the matching result returned by the target subsystem indicating a successful match, generating a login token based on the identity identifier; The token is sent to the terminal.

4. The method according to claim 1, characterized in that The method further comprises: In a case where the candidate fault handling solutions include the fault handling solution of the first subsystem, desensitization processing is performed on the fault handling solution of the first subsystem.

5. The method according to claim 4, characterized in that The desensitizing the fault handling solution of the first subsystem includes: Determine the data to be desensitized in the preset fault handling solution and the desensitization operation corresponding to the data to be desensitized according to the preset desensitization rule; The desensitizing operation is performed on the data to be desensitized to obtain a fault handling solution after desensitization.

6. The method according to claim 1, characterized in that The method further comprises: In a case where the target fault processing solution is a fault processing solution of the first subsystem, the target processing solution is stored in the target subsystem.

7. The method according to claim 2, characterized in that: The clustering algorithm used by the clustering model includes any one of a K-means algorithm, a spectral clustering algorithm, a deep clustering algorithm, and an agglomerative clustering algorithm.

8. A fault handling device, characterized in that: The device is installed on an operation and maintenance platform, and the operation and maintenance platform communicates data with multiple subsystems. The device includes: A fault data acquisition module, used to acquire fault data of a target subsystem, a target user corresponding to the target subsystem, and a terminal of the target user; A fault handling solution acquisition module, used to acquire candidate fault handling solutions for the fault data from the multiple subsystems using a preset clustering model; A sending module, configured to send the candidate fault handling solution to the terminal if the login token of the target user has not expired; The execution module is used to execute the target fault processing solution in response to receiving the target fault processing solution sent by the terminal, wherein the target fault processing solution is obtained by the target user modifying the parameters of the candidate fault processing solution based on the target subsystem.

9. An electronic device, comprising: one or more processors; a memory for storing one or more computer programs, It is characterized in that the one or more processors execute the one or more computer programs to implement the steps of the method according to any one of claims 1 to 7.

10. A computer-readable storage medium having a computer program or instruction stored thereon, characterized in that: When the computer program or instruction is executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.

11. A computer program product comprising a computer program or instructions, characterized in that When the computer program or instruction is executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.

Images