Method and device for determining fault emergency scheme, equipment, medium and program product

Abstract

The invention provides a method for determining a fault emergency scheme. The method can be applied to the field of financial science and technology and the field of big data technology. The method for determining the fault emergency scheme comprises the steps of obtaining comment information in response to monitoring of the comment information associated with a production fault of a financial system under the condition of obtaining authorization; based on the fault type of the production fault, analyzing the comment information to obtain a target fault type associated with the comment information; and matching the target fault type with the fault emergency scheme for the fault type to obtain a target fault emergency scheme for the target fault type. The invention further provides a device and equipment for determining the fault emergency scheme, a storage medium and a program product.

Description

Technical Field

[0001] The present disclosure relates to the fields of financial technology and big data technology, and specifically to a method, device, equipment, medium and program product for determining a fault emergency plan. Background Art

[0002] With the continuous development of financial technology, the financial system architecture and business scale are becoming increasingly large. However, due to the security and real-time requirements of the financial industry, higher requirements are also placed on technology.

[0003] In the process of implementing the embodiments of the present disclosure, it was found that for emergency response to failures in the financial system, it is necessary to wait until the failure occurs, trigger an alarm, analyze and locate the cause, and then start the corresponding emergency procedures, which leads to low emergency efficiency. Summary of the invention

[0004] In view of the above problems, the present disclosure provides a method, apparatus, device, medium and program product for determining a fault emergency plan.

[0005] According to a first aspect of the present disclosure, a method for determining a fault emergency plan is provided, comprising: with authorization, in response to monitoring comment information associated with a production failure in a financial system, obtaining comment information; based on the failure type for the production failure, analyzing the comment information to obtain a target failure type associated with the comment information; and matching the target failure type with a fault emergency plan for the failure type to obtain a target failure emergency plan for the target failure type.

[0006] According to an embodiment of the present disclosure, the method for determining a fault emergency plan also includes: determining trigger words associated with production failures in the financial system based on historical comment information published on social media; and determining that comment information has been monitored when comments associated with the trigger words are generated.

[0007] According to an embodiment of the present disclosure, based on the fault type for production failures, comment information is analyzed to obtain a target fault type associated with the comment information, including: inputting the comment information into a fault type matching model, and outputting the target fault type associated with the comment information; wherein the fault type matching model is pre-trained by executing the following steps: based on sample trigger words associated with production failures in the financial system in the sample comment information, determining the fault type that matches the sample trigger words; configuring the fault type as a fault label of the sample comment information; and based on the sample comment information with the configured fault label, fine-tuning the pre-trained language model to obtain a fault type matching model.

[0008] According to an embodiment of the present disclosure, the method for determining a fault emergency plan also includes: classifying historical fault emergency plans based on emergency measures that have been taken for production failures in the financial system to obtain classified historical fault emergency plans; and based on fault labels, mapping sample comment information configured with fault labels with the classified historical fault emergency plans to obtain fault emergency plans for the fault type.

[0009] According to an embodiment of the present disclosure, a target fault type is matched with a fault contingency plan for the fault type to obtain a target fault contingency plan for the target fault type, including: when it is determined that the target fault type matches the fault label successfully, sample comment information configured with the fault label is determined as target comment information that matches the target fault type; and historical fault contingency plans that have a mapping relationship with the target comment information are determined as the target fault contingency plan.

[0010] According to an embodiment of the present disclosure, fault types include transaction-type fault types and business-type fault types; the method for determining a fault emergency plan also includes: classifying production faults of the financial system based on transaction types to obtain transaction-type fault types; and classifying production faults based on financial service business types to obtain business-type fault types.

[0011] According to an embodiment of the present disclosure, a target fault emergency plan includes a target fault emergency means and an emergency interface of an emergency system that matches the target fault emergency means; the method for determining a fault emergency plan also includes: based on the target fault emergency plan, calling the emergency interface to execute the target fault emergency means; and generating an emergency warning notification according to the target fault emergency plan, and sending the emergency warning notification to a third-party device.

[0012] A second aspect of the present disclosure provides a device for determining a fault emergency plan, including: an acquisition module for acquiring comment information in response to monitoring comment information associated with a production failure of a financial system, with authorization; an analysis module for analyzing the comment information based on the failure type for the production failure to obtain a target failure type associated with the comment information; and a matching module for matching the target failure type with a fault emergency plan for the failure type to obtain a target failure emergency plan for the target failure type.

[0013] 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.

[0014] The fourth aspect of the present disclosure further provides a computer-readable storage medium having a computer program or instructions stored thereon, which implements the steps of the above method when the above computer program or instructions are executed by a processor.

[0015] 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.

[0016] According to the embodiments of the present disclosure, by real-time monitoring of comment information, it is possible to utilize the characteristics of comment information that responds quickly to sudden production failures, reduce the failure notification time, and achieve real-time monitoring of financial system failures. When a failure occurs, there is no need to wait for alarm analysis to locate the cause, but to determine the target failure type by analyzing the comment information, and then match the target failure emergency plan, shorten the time to determine the emergency plan, and thus improve the emergency efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] 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:

[0018] Figure 1 The application scenario diagram schematically shows the method, apparatus, device, medium and program product for determining a fault emergency plan according to an embodiment of the present disclosure;

[0019] Figure 2 A flowchart schematically illustrates a method for determining a fault emergency plan according to an embodiment of the present disclosure;

[0020] Figure 3 A flowchart of a fault type matching model pre-training method according to an embodiment of the present disclosure is schematically shown;

[0021] Figure 4 A flowchart for determining a target fault emergency plan according to an embodiment of the present disclosure is schematically shown;

[0022] Figure 5 A flowchart schematically illustrates a method for determining a fault emergency plan according to another embodiment of the present disclosure;

[0023] Figure 6 A structural block diagram schematically shows a device for determining a fault emergency plan according to an embodiment of the present disclosure; and

[0024] Figure 7 A block diagram of an electronic device suitable for implementing a method for determining a fault emergency plan according to an embodiment of the present disclosure is schematically shown. DETAILED DESCRIPTION

[0025] 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.

[0026] 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 features, steps, operations and / or components, but do not exclude the existence or addition of one or more other features, steps, operations or components.

[0027] 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.

[0028] 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.).

[0029] 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.

[0030] 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.

[0031] In the process of implementing the embodiments of the present disclosure, it was found that due to the security and real-time requirements of the financial industry, higher requirements are also placed on the technology. However, for emergency response after a failure in the financial system, it is necessary to wait until the failure occurs, trigger an alarm, analyze and locate the cause, and then start the corresponding emergency procedure, which has low emergency efficiency. For example, for a financial system, such as a bank system, if a user encounters a transfer failure when using the bank system, the user will actively contact the customer service of the bank system to feedback the problem. After the customer service receives the feedback, it will analyze and locate the cause, and then start the corresponding emergency procedure. The emergency efficiency is low. In addition, in a high-concurrency scenario, due to the limited number of customer service staff, feedback problems cannot be obtained at the same time, resulting in the user's inability to quickly feedback, resulting in a poor user experience. Therefore, how to maximize the ability to respond to various emergencies has become a technical problem that needs to be solved urgently.

[0032] An embodiment of the present disclosure provides a method for determining a fault emergency plan, including: with authorization, in response to monitoring comment information associated with a production failure in a financial system, obtaining comment information; based on the failure type for the production failure, analyzing the comment information to obtain a target failure type associated with the comment information; and matching the target failure type with a fault emergency plan for the failure type to obtain a target failure emergency plan for the target failure type.

[0033] Figure 1 The application scenario diagram of the method, apparatus, device, medium and program product for determining a fault emergency plan according to an embodiment of the present disclosure is schematically shown.

[0034] like Figure 1 As 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, and a server 105. 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, and the server 105. The network 104 may include various connection types, such as wired, wireless communication links, or optical fiber cables, etc.

[0035] The user can use the first terminal device 101, the second terminal device 102, and the third terminal device 103 to interact with the server 105 through the network 104 to receive or send messages, etc. Various communication client applications can 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).

[0036] 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.

[0037] The server 105 may be a server that provides various services, such as a background management server (only as an example) that provides support for websites browsed by users using the first terminal device 101, the second terminal device 102, and the third terminal device 103. The background management server may analyze and process the received data such as user requests, and feed back the processing results (such as web pages, information, or data obtained or generated according to user requests) to the terminal device.

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

[0039] 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.

[0040] The following will be based on Figure 1 The scene described by Figure 2~Figure 5 The method for determining the fault emergency plan of the disclosed embodiment is described in detail.

[0041] Figure 2The flowchart of the method for determining a fault emergency plan according to an embodiment of the present disclosure is schematically shown.

[0042] like Figure 2 As shown, the method for determining a fault emergency plan in this embodiment includes operations S210 to S230.

[0043] In operation S210, in response to monitoring comment information associated with a production failure of a financial system, comment information is acquired if authorization is obtained.

[0044] In operation S220 , based on the failure type for the production failure, the comment information is analyzed to obtain a target failure type associated with the comment information.

[0045] In operation S230 , the target fault type is matched with a fault contingency plan for the fault type to obtain a target fault contingency plan for the target fault type.

[0046] In an embodiment of the present disclosure, before monitoring and acquiring the comment information, the consent or authorization of the website or application to which the comment information belongs and the user may be obtained. For example, before operation S210, a request to monitor and acquire the comment information may be sent to the website or application to which the comment information belongs and the user. When the website or application to which the comment information belongs and the user agree or authorize that the comment information may be monitored and acquired, operation S210 is performed.

[0047] According to the embodiments of the present disclosure, the production failure of the financial system can be understood as a state in which the financial system cannot perform a specified function. The comment information can be information uploaded by the user through the network to comment on the inability to normally perform the operation required by the user when the financial system cannot normally perform the operation required by the user when the user is using the financial system.

[0048] For example, when a user needs to use mobile banking to conduct transactions, he finds that the login to mobile banking fails, and the user uploads a comment about "Why can't I log in to mobile banking?" on the Internet. Since the comment information represents the state that the mobile banking cannot perform the login function, the comment information is associated with the production failure of the financial system, and the comment information can be obtained in a timely manner.

[0049] According to an embodiment of the present disclosure, the fault type of production fault may include a transaction fault type and a business fault type. The transaction fault type may include, but is not limited to, account faults, user information faults, financial system software faults, etc. The business fault type may include, but is not limited to, business process design faults, system configuration faults, data faults, etc.

[0050] In the embodiments of the present disclosure, a corresponding operation entry may be provided for the user to choose to agree or reject the automated processing / decision result. That is, before the comment information is analyzed and processed / decision-made, the user's instruction to agree or reject the analysis may be obtained through the corresponding operation entry. If the user agrees to process / decide, the comment information is analyzed and processed / decision-made, that is, step S220 is executed. If the user refuses to process / decide, the expert decision-making process is entered.

[0051] According to an embodiment of the present disclosure, the analysis result can be obtained by semantically analyzing the comment information. The analysis result is divided based on the fault type of the production fault to obtain the fault type to which the analysis result belongs, and the fault type to which the analysis result belongs is determined as the target fault type associated with the comment information.

[0052] According to the embodiments of the present disclosure, the fault contingency plan for each fault type may be pre-configured based on expert experience, or the fault contingency plan for each fault type may be pre-determined based on historical contingency measures for handling faults.

[0053] According to the embodiments of the present disclosure, by real-time monitoring of comment information, it is possible to utilize the characteristics of comment information that responds quickly to sudden production failures, reduce the failure notification time, and achieve real-time monitoring of financial system failures. When a failure occurs, there is no need to wait for alarm analysis to locate the cause, but to determine the target failure type by analyzing the comment information, and then match the target failure emergency plan, shorten the time to determine the emergency plan, and thus improve the emergency efficiency.

[0054] In the process of implementing the embodiments of the present disclosure, it was found that for scenarios where users use financial systems, when a production failure occurs in the financial system, if the third-party equipment used to maintain the financial system does not promptly push the production failure information to the operation and maintenance personnel, the operation and maintenance personnel cannot perform maintenance in a timely manner, resulting in the production failure not being resolved in a timely manner and a poor user experience.

[0055] According to an embodiment of the present disclosure, the method for determining a fault emergency plan may include the above Figure 2 In addition to the operations S210 to S230 shown, the operation may also include: determining trigger words associated with production failures in the financial system based on historical comment information published on social media; and determining that comment information is monitored when comments associated with the trigger words are generated.

[0056] According to an embodiment of the present disclosure, social media may include a website or platform for providing a function for publishing comment information. Users may publish comments on the website or platform providing the function for publishing comment information through the network. Comment information may include images, texts, videos, etc. containing texts. Trigger words may be used to monitor production failures in financial systems.

[0057] According to an embodiment of the present disclosure, a web crawler can be used to continuously collect historical review information, and multiple trigger words associated with production failures in the financial system can be obtained by identifying keywords in the historical review information. The keyword identification method is not specifically limited in the present disclosure.

[0058] According to the embodiments of the present disclosure, social media is monitored by trigger words associated with production failures in the financial system. Since the trigger words are associated with production failures in the financial system, it is possible to determine whether a production failure has occurred in the financial system. In the event of a production failure, the comment information on social media can be accurately and timely monitored, without waiting for third-party equipment that maintains the financial system to push production failure information to operation and maintenance personnel in a timely manner, thus shortening the time for reporting failures, thereby improving the efficiency of fault handling and enhancing user experience.

[0059] According to an embodiment of the present disclosure, the fault type may include a transaction type fault type and a business type fault type.

[0060] The method for determining the emergency plan for failure may include the above Figure 2 In addition to the operations S210 to S230 shown, the operations may also include: classifying the production failures of the financial system based on the transaction type to obtain the transaction failure type; and classifying the production failures based on the financial service business type to obtain the business failure type.

[0061] According to an embodiment of the present disclosure, the transaction type may be a type of transaction for mobile banking, electronic payment system, corporate online banking, quick payment, etc. Transaction fault types may include, but are not limited to, account faults, user information faults, financial system software faults, etc. Business fault types may include, but are not limited to, business process design faults, system configuration faults, data faults, etc.

[0062] According to the embodiments of the present disclosure, production failures are classified based on transaction types and business types, and emergency response measures can be accurately matched through the classified categories, which is conducive to improving emergency response efficiency.

[0063] According to the embodiments of the present disclosure, for the above Figure 2The operation S220 shown, based on the fault type for the production fault, analyzes the comment information to obtain the target fault type associated with the comment information, and may include the operation of inputting the comment information into a fault type matching model and outputting the target fault type associated with the comment information.

[0064] Figure 3 The flowchart of the fault type matching model pre-training method according to an embodiment of the present disclosure is schematically shown.

[0065] like Figure 3 As shown, the fault type matching model pre-training method of this embodiment includes operations S310 to S330.

[0066] In operation S310 , based on sample trigger words associated with production failures of a financial system in sample comment information, a failure type matching the sample trigger words is determined.

[0067] In operation S320 , the fault type is configured as a fault label of the sample comment information.

[0068] In operation S330 , the pre-trained language model is fine-tuned based on sample comment information configured with fault labels to obtain a fault type matching model.

[0069] According to an embodiment of the present disclosure, the historical comment information published on social media can be preprocessed, such as image-to-text preprocessing, to remove symbols and words that are not related to production failures in the text. The preprocessed historical comment information is used as sample comment information. Sample trigger words used to describe production failures in financial systems are extracted from the sample comment information.

[0070] According to an embodiment of the present disclosure, production failures used to describe a financial system may be determined based on sample trigger words, and the production failures used to describe the financial system may be classified to obtain failure types that match the sample trigger words.

[0071] According to an embodiment of the present disclosure, sample comment information with fault labels configured can be input into a pre-trained language model to allow the pre-trained language model to learn fault features of different fault labels. The pre-trained language model can include a model for natural language understanding tasks and a model for natural language production tasks.

[0072] For example, sample comment information with fault labels configured can be input into the pre-trained language model to output the predicted fault type. Based on the predicted fault type and fault label, the parameters of the pre-trained language model are adjusted. When the maximum number of iterations is reached, the training is stopped, and the fine-tuning of the pre-trained language model is completed to obtain a fault type matching model.

[0073] According to an embodiment of the present disclosure, by configuring the fault type as the fault label of the sample comment information and pre-training the fault type matching model, it is possible to accurately analyze the fault type of the comment information when the comment information is monitored, thereby achieving fast and accurate matching of the comment information with the fault type.

[0074] According to another embodiment of the present disclosure, the pre-trained language model can be updated in real time based on the real-time tracking results of the operation of the financial system by the operation and maintenance personnel after taking emergency measures for the fault, so as to more accurately identify the fault. It should be noted that emergency can be understood as taking remedial measures for sudden events that require urgent handling.

[0075] According to an embodiment of the present disclosure, the method for determining a fault emergency plan may include the above Figure 2 In addition to the operations S210 to S230 shown, the following operations may also be included: based on the emergency measures that have been taken for production failures in the financial system, classifying historical failure emergency plans to obtain classified historical failure emergency plans; and based on the fault labels, mapping the sample comment information configured with the fault labels with the classified historical failure emergency plans to obtain a fault emergency plan for the fault type.

[0076] According to the embodiments of the present disclosure, emergency measures may include but are not limited to isolation, restart, flow switching, degradation, fuse, etc. Historical fault emergency plans may include but are not limited to emergency measures and emergency objects, etc. For example, historical fault emergency plans may be divided into isolation type, restart type, flow switching type, degradation type, fuse type historical fault emergency plans.

[0077] According to an embodiment of the present disclosure, a mapping relationship is formed between sample comment information configured with fault labels and classified historical fault emergency plans so as to subsequently match the target fault emergency plan. The beneficial effect is that the target fault emergency plan can be matched in a timely manner according to the mapping relationship.

[0078] In the process of implementing the embodiments of the present disclosure, it was found that if the operation and maintenance personnel select appropriate emergency plans based on experience and implement them manually, the emergency handling time is long and the subjective factors of the operation and maintenance personnel have a great influence, resulting in low emergency efficiency and high emergency costs.

[0079] Figure 4 A flowchart for determining a target fault emergency plan according to an embodiment of the present disclosure is schematically shown.

[0080] According to the embodiments of the present disclosure, for the above Figure 2 Operation S230 shown in FIG. 1 matches the target fault type with the fault emergency plan for the fault type to obtain the target fault emergency plan for the target fault type, which may include: Figure 4 Operations S431 to S434 are shown.

[0081] In operation S431 , it is determined whether the target fault type matches the fault label.

[0082] According to an embodiment of the present disclosure, the target fault type may be matched with the fault label. The matching method may be, for example, by determining the similarity between the target fault type and the fault label. When it is determined that the similarity is greater than or equal to a preset similarity, it is determined that the target fault type and the fault label are successfully matched, and operation S432 is performed. When it is determined that the similarity is less than a preset similarity, it is determined that the target fault type and the fault label are unmatched, and operation S434 is performed.

[0083] In operation S432 , when it is determined that the target fault type matches the fault label successfully, the sample comment information configured with the fault label is determined as the target comment information matching the target fault type.

[0084] In operation S433, the historical fault contingency plan having a mapping relationship with the target comment information is determined as the target fault contingency plan.

[0085] In operation S434 , when it is determined that the target fault type fails to match the fault label, a fault warning notification is generated based on the target fault type and the comment information, and the fault warning notification is sent to the third-party device.

[0086] According to an embodiment of the present disclosure, the target fault type and the comment information can be combined to obtain early warning prompt information. A fault warning notification is generated according to the early warning prompt information and the fault warning identifier. When a third-party device receives a fault warning notification, the fault warning notification can be visualized for operation and maintenance personnel to handle the emergency.

[0087] According to the embodiments of the present disclosure, the target fault emergency plan is matched based on the pre-configured mapping relationship, without waiting for the alarm to be received and then analyzing and locating the cause, which shortens the time for determining the emergency plan, thereby improving the emergency efficiency and reducing the emergency cost.

[0088] Figure 5 The flowchart schematically shows a method for determining a fault emergency plan according to another embodiment of the present disclosure.

[0089] According to an embodiment of the present disclosure, a target failure contingency plan may include a target failure contingency means and an contingency interface of an contingency system matching the target failure contingency means.

[0090] The method for determining the emergency plan for failure may include the above Figure 2 In addition to the operations S210 to S230 shown in FIG. Figure 5 Operations S510~S520 are shown.

[0091] In operation S510, based on the target fault emergency plan, an emergency interface is called to execute the target fault emergency measure.

[0092] In operation S520, an emergency warning notification is generated according to the target fault emergency plan, and the emergency warning notification is sent to a third-party device.

[0093] According to the embodiment of the present disclosure, the emergency interface can be opened through the emergency system. The emergency interface matching the target fault emergency plan can be called from the emergency system to execute the target fault emergency means and complete the automatic emergency.

[0094] According to the embodiments of the present disclosure, the third-party device can be used by the operation and maintenance personnel to perform control operations on the financial system. The emergency warning notification can be used to remind the operation and maintenance personnel that a production failure has occurred in the financial system and that the failure has been automatically handled in an emergency.

[0095] According to the embodiment of the present disclosure, after matching the fault emergency plan, the relevant interface is automatically called for emergency response, thereby improving the emergency response efficiency. In addition, according to the target fault emergency plan, an emergency warning notification is generated, which enables relevant personnel to continue to pay attention to the follow-up of the fault and plays a certain role in fault warning.

[0096] Based on the above-mentioned method for determining a fault emergency plan, the present disclosure also provides a device for determining a fault emergency plan. Figure 6 The device is described in detail.

[0097] Figure 6 The structural block diagram of the device for determining a fault emergency plan according to an embodiment of the present disclosure is schematically shown.

[0098] like Figure 6 As shown, the apparatus 600 for determining a fault emergency plan in this embodiment includes an acquisition module 610 , an analysis module 620 and a matching module 630 .

[0099] The acquisition module 610 is used to acquire the comment information in response to monitoring the comment information associated with the production failure of the financial system under the condition of obtaining authorization. In one embodiment, the acquisition module 610 can be used to perform the operation S210 described above, which will not be repeated here.

[0100] The analysis module 620 is used to analyze the comment information based on the fault type of the production fault to obtain the target fault type associated with the comment information. In one embodiment, the analysis module 620 can be used to perform the operation S220 described above, which will not be described in detail here.

[0101] The matching module 630 is used to match the target fault type with the fault contingency plan for the fault type to obtain the target fault contingency plan for the target fault type. In one embodiment, the matching module 630 can be used to perform the operation S230 described above, which will not be described in detail here.

[0102] According to an embodiment of the present disclosure, the apparatus 600 for determining a fault emergency plan may further include: a first determining module and a second determining module.

[0103] The first determination module is used to determine the trigger words associated with the production failure of the financial system based on the historical comment information published on the social media. The second determination module is used to determine that the comment information is monitored when the generation of the comment associated with the trigger word is monitored.

[0104] According to an embodiment of the present disclosure, based on the fault type for production failures, comment information is analyzed to obtain a target fault type associated with the comment information, including: inputting the comment information into a fault type matching model, and outputting a target fault type associated with the real-time comment information; wherein the fault type matching model is pre-trained by executing the following steps: based on sample trigger words associated with production failures in the financial system in the sample comment information, determining the fault type that matches the sample trigger words; configuring the fault type as a fault label of the sample comment information; and based on the sample comment information with the configured fault label, fine-tuning the pre-trained language model to obtain a fault type matching model.

[0105] According to an embodiment of the present disclosure, the apparatus 600 for determining a fault emergency plan may further include: a first classification module and a mapping module.

[0106] The first classification module is used to classify historical fault emergency plans based on the emergency measures that have been taken for production failures in the financial system, and obtain classified historical fault emergency plans. The mapping module is used to form a mapping relationship between sample comment information configured with fault labels and classified historical fault emergency plans based on fault labels, and obtain fault emergency plans for fault types.

[0107] According to an embodiment of the present disclosure, a target fault type is matched with a fault contingency plan for the fault type to obtain a target fault contingency plan for the target fault type, including: when it is determined that the target fault type matches the fault label successfully, sample comment information configured with the fault label is determined as target comment information that matches the target fault type; and historical fault contingency plans that have a mapping relationship with the target comment information are determined as the target fault contingency plan.

[0108] According to an embodiment of the present disclosure, the fault types include transaction fault types and business fault types. The fault emergency plan determination device 600 may further include: a second classification module and a third classification module.

[0109] The second classification module is used to classify the production failures of the financial system based on the transaction type to obtain the transaction failure type. The third classification module is used to classify the production failures based on the financial service business type to obtain the business failure type.

[0110] According to an embodiment of the present disclosure, the target fault emergency plan includes a target fault emergency means and an emergency interface of an emergency system matching the target fault emergency means. The fault emergency plan determination device 600 may further include: a calling module and a processing module.

[0111] The calling module is used to call the emergency interface based on the target fault emergency plan so as to execute the target fault emergency measures. The processing module is used to generate an emergency warning notification according to the target fault emergency plan and send the emergency warning notification to the third-party device.

[0112] According to an embodiment of the present disclosure, any multiple modules of the acquisition module 610, the analysis module 620 and the matching module 630 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 acquisition module 610, the analysis module 620 and the matching module 630 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 modes of software, hardware and firmware or in any appropriate combination of any of them. Alternatively, at least one of the acquisition module 610, the analysis module 620 and the matching module 630 can be at least partially implemented as a computer program module, and when the computer program module is run, the corresponding function can be executed.

[0113] Figure 7 A block diagram of an electronic device suitable for implementing a method for determining a fault emergency plan according to an embodiment of the present disclosure is schematically shown.

[0114] like Figure 7As shown, the electronic device 700 according to an embodiment of the present disclosure includes a processor 701, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 702 or a program loaded from a storage part 708 to a random access memory (RAM) 703. The processor 701 may include, for example, a general-purpose microprocessor (such as a CPU), an instruction set processor and / or a related chipset and / or a special-purpose microprocessor (for example, an application-specific integrated circuit (ASIC)), etc. The processor 701 may also include an onboard memory for caching purposes. The processor 701 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.

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

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

[0117] 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.

[0118] 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 702 and / or RAM 703 described above and / or one or more memories other than ROM 702 and RAM 703.

[0119] 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 method provided by the embodiment of the present disclosure.

[0120] 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 701. According to the embodiment of the present disclosure, the system, device, module, unit, etc. described above can be implemented by a computer program module.

[0121] 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 709, and / or installed from the removable medium 711. 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.

[0122] In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 709, and / or installed from the removable medium 711. When the computer program is executed by the processor 701, 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, means, module, unit, etc. described above can be implemented by a computer program module.

[0123] 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).

[0124] 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.

[0125] 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.

[0126] 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 method for determining a fault emergency plan, characterized in that: The method comprises: In response to monitoring the comment information associated with the production failure of the financial system, obtaining the comment information if authorized; Analyzing the comment information based on the fault type of the production fault to obtain a target fault type associated with the comment information; and The target fault type is matched with a fault emergency plan for the fault type to obtain a target fault emergency plan for the target fault type.

2. The method according to claim 1, characterized in that The method further comprises: Determining trigger words associated with the production failure of the financial system based on historical comment information published on social media; and In the case where the generation of a comment associated with the trigger word is monitored, it is determined that the comment information is monitored.

3. The method according to claim 1 or 2, characterized in that: The analyzing the comment information based on the fault type of the production fault to obtain a target fault type associated with the comment information includes: Inputting the comment information into a fault type matching model, and outputting the target fault type associated with the comment information; The fault type matching model is pre-trained by performing the following steps: Determining, based on sample trigger words associated with the production failure of the financial system in the sample comment information, a failure type matching the sample trigger words; configuring the fault type as a fault label of the sample comment information; and Based on the sample comment information configured with the fault label, a pre-trained language model is fine-tuned to obtain the fault type matching model.

4. The method according to claim 3, characterized in that The method further comprises: Based on the emergency measures that have been taken for the production failures of the financial system, classify the historical failure emergency plans to obtain classified historical failure emergency plans; and Based on the fault label, a mapping relationship is formed between the sample comment information configured with the fault label and the classified historical fault emergency plan to obtain a fault emergency plan for the fault type.

5. The method according to claim 4, characterized in that The matching of the target fault type with the fault emergency plan for the fault type to obtain the target fault emergency plan for the target fault type includes: In the case where it is determined that the target fault type successfully matches the fault label, determining the sample comment information configured with the fault label as the target comment information matching the target fault type; and The historical fault emergency plan having a mapping relationship with the target comment information is determined as the target fault emergency plan.

6. The method according to claim 3, characterized in that The fault types include transaction fault types and business fault types; The method further comprises: Based on the transaction type, the production failure of the financial system is classified to obtain the transaction failure type; and The production failure is classified based on the financial service business type to obtain the business failure type.

7. The method according to claim 1 or 2, characterized in that: The target fault emergency plan includes a target fault emergency means and an emergency interface of an emergency system matching the target fault emergency means; The method further comprises: Based on the target fault emergency plan, calling the emergency interface to execute the target fault emergency measure; and An emergency warning notification is generated according to the target fault emergency plan, and the emergency warning notification is sent to a third-party device.

8. A device for determining a fault emergency plan, characterized in that: The device comprises: an acquisition module, configured to acquire the comment information in response to monitoring the comment information associated with the production failure of the financial system, if authorized; an analysis module, configured to analyze the comment information based on the fault type of the production fault to obtain a target fault type associated with the comment information; and The matching module is used to match the target fault type with a fault emergency plan for the fault type to obtain a target fault emergency plan for the target fault type.

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