Third-party system fault emergency processing method, device, equipment and medium

Abstract

The invention discloses a third-party system fault emergency processing method and device, equipment and a medium, and relates to the technical field of information, and the method comprises the steps: judging whether obtained third-party system fault data is fault data in a preset fault library or not; if the fault data of the third-party system is the fault data in the preset fault library, starting a protection mechanism of a local system to shut down an outbound transaction service; if the third-party system fault data is not the fault data in the preset fault library, judging whether the number of continuous transaction failures of the third-party system fault data or the duration required by the transaction meets a preset fusing condition or not; and if the number of failure times of the continuous transaction or the duration required by the transaction meets a preset fusing condition, starting a fusing mechanism to shut down the outbound transaction service, detecting the recovery state of the third-party system by using a preset timed task based on the fusing mechanism, and reactivating the outbound transaction service through a detection result. The emergency situation of the third-party system can be responded in time without relying on manpower.

Description

Technical Field

[0001] The present invention relates to the field of information technology, and in particular to a method, device, equipment and medium for emergency handling of third-party system failures. Background Art

[0002] In modern financial services, in order to improve customer experience and business efficiency, financial institutions have established close and secure collaboration relationships with external partners to achieve one-stop services such as fund settlement and account management. However, with the integration of multiple systems, new challenges have also emerged: the instability of third-party systems and frequent emergencies, such as downtime during system upgrades and network connection failures, which directly affect the service quality of financial institutions.

[0003] Current countermeasures usually rely on the monitoring function of the external platform, which notifies relevant personnel to conduct manual intervention when abnormal transactions are detected, including locating the source of the fault, coordinating third-party technical support, and dealing with the resulting public opinion impact. Although this approach can solve the problem to a certain extent, the process is cumbersome, time-consuming, and highly dependent on manpower input.

[0004] From the above, it can be seen that how to respond to emergencies in third-party systems in a timely manner without relying on manpower is an urgent problem that needs to be solved. Summary of the invention

[0005] In view of this, the purpose of the present invention is to provide a third-party system failure emergency processing method, device, equipment and medium, which can respond to the emergency of the third-party system in a timely manner without relying on manpower. The specific scheme is as follows:

[0006] In a first aspect, the present application provides a method for emergency handling of a third-party system failure, comprising:

[0007] Obtaining third-party system fault data, and determining whether the third-party system fault data is fault data in a preset fault library;

[0008] If the third-party system fault data is fault data in a preset fault library, the protection mechanism of the local system is activated to shut down the outbound transaction service of the local system;

[0009] If the third-party system fault data is not the fault data in the preset fault library, determining whether the number of consecutive transaction failures or the transaction duration corresponding to the third-party system fault data meets the preset fuse condition;

[0010] If the number of consecutive transaction failures or the duration required for the transaction meets the preset circuit breaker condition, the circuit breaker mechanism of the local system is activated to shut down the outbound transaction service of the local system, and the recovery status of the third-party system is detected based on the circuit breaker mechanism and using the preset timed task to reactivate the outbound transaction service of the local system through the detection result.

[0011] Optionally, before obtaining the third-party system fault data and determining whether the third-party system fault data is fault data in a preset fault library, the method further includes:

[0012] Obtain maintenance information for third-party systems and the corresponding maintenance time period;

[0013] Obtaining corresponding fault data based on the maintenance information and the maintenance time period, and saving the fault data to a preset fault library;

[0014] The maintenance information includes system update information and network adjustment information of the third-party system.

[0015] Optionally, if the third-party system fault data is fault data in a preset fault library, a protection mechanism of the local system is started to shut down the outbound transaction service of the local system, including:

[0016] If the third-party system fault data is fault data in a preset fault library, the protection mechanism of the local system is activated to shut down the outbound transaction service of the local system, and the maintenance time period corresponding to the fault data is displayed on the preset display interface of the local system based on the preset fault library.

[0017] Optionally, if the third-party system fault data is not fault data in the preset fault library, determining whether the number of consecutive transaction failures or the transaction duration corresponding to the third-party system fault data meets a preset fuse condition includes:

[0018] If the third-party system fault data is not the fault data in the preset fault library, determining whether the number of consecutive transaction failures corresponding to the third-party system fault data exceeds a preset transaction failure number threshold;

[0019] Or, if the third-party system fault data is not the fault data in the preset fault library, it is determined whether the transaction time corresponding to the third-party system fault data exceeds a preset transaction delay threshold.

[0020] Optionally, if the number of consecutive transaction failures or the duration required for the transaction meets the preset fuse condition, the fuse mechanism of the local system is activated to shut down the outbound transaction service of the local system, including:

[0021] If the number of consecutive transaction failures corresponding to the third-party system failure data exceeds the preset transaction failure threshold, the fuse mechanism of the local system is activated to shut down the outbound transaction service of the local system;

[0022] Alternatively, if the transaction time corresponding to the third-party system fault data exceeds a preset transaction time threshold, the fuse mechanism of the local system is activated to shut down the outbound transaction service of the local system.

[0023] Optionally, the detecting the recovery status of the third-party system based on the fuse mechanism and using a preset timed task to reactivate the outbound transaction service of the local system according to the detection result includes:

[0024] Sending the transaction request of the local system to the third-party system based on the circuit breaker mechanism and the preset interval time;

[0025] The recovery state of the third-party system is determined based on a response result obtained after the third-party system responds to the transaction request, so as to use the recovery state to restore the outbound transaction service of the local system.

[0026] Optionally, the detecting the recovery status of the third-party system based on the fuse mechanism and using a preset timed task to reactivate the outbound transaction service of the local system according to the detection result includes:

[0027] Based on the fuse mechanism and using a preset timed task, the recovery status of the third-party system is detected;

[0028] If the detection result indicates that the third-party system is in a normal operating state, a stability detection is performed on the operating state of the third-party system, and the outbound transaction service of the local system is reactivated based on the stability detection result.

[0029] In a second aspect, the present application provides a third-party system failure emergency processing device, including:

[0030] A fault data judgment module is used to obtain third-party system fault data and judge whether the third-party system fault data is fault data in a preset fault library;

[0031] A protection mechanism startup module, used to start the protection mechanism of the local system if the third-party system fault data is fault data in a preset fault library, so as to shut down the outbound transaction service of the local system;

[0032] A fuse condition judgment module, used for judging whether the number of consecutive transaction failures or the transaction time required corresponding to the third-party system fault data satisfies a preset fuse condition if the third-party system fault data is not the fault data in the preset fault library;

[0033] The transaction service activation module is used to activate the circuit breaker mechanism of the local system to shut down the outbound transaction service of the local system if the number of consecutive transaction failures or the duration required for the transaction meets the preset circuit breaker condition, and to detect the recovery status of the third-party system based on the circuit breaker mechanism and using the preset timed task, so as to reactivate the outbound transaction service of the local system through the detection result.

[0034] In a third aspect, the present application provides an electronic device, including:

[0035] Memory, used to store computer programs;

[0036] The processor is used to execute the computer program to implement the aforementioned third-party system failure emergency processing method.

[0037] In a fourth aspect, the present application provides a computer-readable storage medium for storing a computer program, wherein the computer program, when executed by a processor, implements the aforementioned third-party system failure emergency handling method.

[0038] The present application first obtains the third-party system fault data, and determines whether the third-party system fault data is the fault data in the preset fault library; if the third-party system fault data is the fault data in the preset fault library, the protection mechanism of the local system is started; if the third-party system fault data is not the fault data in the preset fault library, it is determined whether the number of consecutive transaction failures or the transaction time required corresponding to the third-party system fault data meets the preset fuse condition; if the number of consecutive transaction failures or the transaction time required meets the preset fuse condition, the fuse mechanism of the local system is started, and the recovery status of the third-party system is detected based on the fuse mechanism and using the preset timed task, so as to reactivate the outbound transaction service of the local system through the detection result.

[0039] As can be seen from the above, the acquired third-party system fault data is judged by the pre-established preset fault library. If the preset fault library contains fault data corresponding to the third-party system fault data, the protection mechanism of the local system is activated, which can directly process the fault data in the preset fault library, effectively prevent foreseeable service interruptions, and reduce the workload of temporary troubleshooting; if the preset fault library does not contain fault data corresponding to the third-party system fault data, it is determined whether the number of consecutive transaction failures or the transaction duration corresponding to the third-party system fault data meets the preset fuse conditions. If so, the fuse mechanism of the local system is activated, and the preset timed task is used to reactivate the outbound transaction service of the local system. Through the protection mechanism and fuse mechanism configured by the local system, the start and shutdown of outbound transactions can be automatically triggered, with a high degree of automation. It not only replaces manual monitoring and repair, but also greatly reduces labor costs and operating costs. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying creative work.

[0041] Figure 1 A flowchart of a method for emergency handling of a third-party system failure disclosed in this application;

[0042] Figure 2 A flowchart of a specific third-party system failure emergency handling method disclosed in this application;

[0043] Figure 3 This is a schematic diagram of the structure of a third-party system failure emergency processing device disclosed in this application;

[0044] Figure 4 This is a structural diagram of an electronic device disclosed in this application. DETAILED DESCRIPTION

[0045] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0046] At present, the response measures for failures in third-party systems usually rely on the monitoring function of the external liaison platform. When a transaction anomaly is detected, relevant personnel are promptly notified for manual intervention, including locating the source of the fault, coordinating third-party technical support, and dealing with the resulting public opinion impact. Although this approach can solve the problem to a certain extent, the process is cumbersome, time-consuming, and highly dependent on manpower input. To this end, the present application provides a third-party system failure emergency handling method. Through the protection mechanism and fuse mechanism configured by the local system, the start and shutdown of outbound transactions can be automatically triggered. It has a high degree of automation and not only replaces manual monitoring and repair, but also greatly reduces labor costs and operating costs.

[0047] See also Figure 1 As shown, an embodiment of the present invention discloses a method for emergency handling of a third-party system failure, including:

[0048] Step S11: Acquire third-party system fault data, and determine whether the third-party system fault data is fault data in a preset fault library.

[0049] In this embodiment, a connection relationship between the local system and the third-party system is established, and maintenance information and a corresponding maintenance time period for maintaining the third-party system are obtained based on the connection relationship, and corresponding fault data are constructed through the maintenance information and the maintenance time period, and the fault data is saved in a preset fault library. Specifically, before obtaining the third-party system fault data and determining whether the third-party system fault data is fault data in the preset fault library, it also includes: obtaining maintenance information and a corresponding maintenance time period for maintaining the third-party system; obtaining corresponding fault data based on the maintenance information and the maintenance time period, and saving the fault data in the preset fault library; wherein the maintenance information includes system update information and network adjustment information of the third-party system.

[0050] It is understandable that the API interface or other information acquisition tools provided by the third-party system can be used to obtain the third-party system fault data, and then the third-party system fault data can be cleaned to remove invalid or redundant data, and the cleaned third-party system fault data can be converted into a data format corresponding to the preset fault to determine whether the converted third-party system fault data is the fault data in the preset fault library.

[0051] Step S12: If the third-party system fault data is fault data in a preset fault library, the protection mechanism of the local system is activated to shut down the outbound transaction service of the local system.

[0052] In this embodiment, if the third-party system fault data is consistent with the fault data in the preset fault library, the protection mechanism of the local system is activated to shut down the outbound call transaction service of the local system, and the maintenance time period corresponding to the third-party system fault data is obtained based on the preset fault library, and the maintenance time period is displayed on the preset display interface of the local system. Specifically, if the third-party system fault data is fault data in the preset fault library, the protection mechanism of the local system is activated to shut down the outbound call transaction service of the local system, including: if the third-party system fault data is fault data in the preset fault library, the protection mechanism of the local system is activated to shut down the outbound call transaction service of the local system, and the maintenance time period corresponding to the fault data is displayed on the preset display interface of the local system based on the preset fault library.

[0053] It is understandable that the third-party system fault data can be compared with the fault data in the preset fault library based on a preset matching algorithm. If the third-party system fault data is consistent with the fault data in the preset fault library, the protection mechanism of the local system is activated based on the preset system monitoring tool to shut down the outbound transaction service of the local system. By shutting down the outbound transaction service of the local system, it can be ensured that the service is stopped quickly and safely to avoid the loss of transaction data. In a specific embodiment, if an ongoing transaction service appears during the process of shutting down the outbound transaction service of the local system, a prompt indicating the failure of the current transaction is displayed on the preset display interface, and relevant personnel are notified through system logs, emails, text messages or instant messaging tools.

[0054] Step S13: If the third-party system fault data is not the fault data in the preset fault library, it is determined whether the number of consecutive transaction failures or the transaction duration corresponding to the third-party system fault data meets the preset fuse condition.

[0055] In this embodiment, if the third-party system fault data is not the fault data in the preset fault library, it is determined whether the number of consecutive transaction failures corresponding to the third-party system fault data exceeds the preset transaction failure number threshold or whether the transaction time required for the third-party system fault data exceeds the preset transaction delay threshold. Specifically, if the third-party system fault data is not the fault data in the preset fault library, it is determined whether the number of consecutive transaction failures or the transaction time required for the third-party system fault data meets the preset fuse condition, including: if the third-party system fault data is not the fault data in the preset fault library, it is determined whether the number of consecutive transaction failures corresponding to the third-party system fault data exceeds the preset transaction failure number threshold; or, if the third-party system fault data is not the fault data in the preset fault library, it is determined whether the transaction time required for the third-party system fault data exceeds the preset transaction delay threshold.

[0056] In a specific implementation, if the third-party system fault data is not fault data in the preset fault library, the number of consecutive transaction failures corresponding to the third-party system fault data within a preset time period is obtained, and the number of consecutive transaction failures is the number of transaction failures corresponding to each consecutive transaction failure, that is, there is no obvious successful transaction interval between each transaction failure. A preset transaction failure number threshold is set based on factors such as transaction importance and business tolerance, and it is determined whether the number of consecutive transaction failures corresponding to the third-party system fault data exceeds the preset transaction failure number threshold.

[0057] In another specific implementation, the total time required from the start to the end of each transaction calculated based on the third-party system failure data is the transaction time required corresponding to the third-party system failure data. The transaction time required may include all necessary transaction processing time and waiting time during the transaction. Then, a preset transaction delay threshold is set based on factors such as the nature of the transaction and the processing capacity of the third-party system to determine whether the transaction time required corresponding to the third-party system failure data exceeds the preset transaction delay threshold.

[0058] Step S14: If the number of consecutive transaction failures or the duration required for the transaction meets the preset fuse condition, the fuse mechanism of the local system is activated to shut down the outbound transaction service of the local system, and the recovery status of the third-party system is detected based on the fuse mechanism and using the preset timed task to reactivate the outbound transaction service of the local system through the detection result.

[0059] In this embodiment, if the number of consecutive transaction failures corresponding to the third-party system fault data exceeds the preset transaction failure number threshold or if the transaction time required corresponding to the third-party system fault data exceeds the preset transaction time threshold within the preset time period, it indicates that the fuse trigger condition of the local system is met, and the fuse mechanism of the local system is activated to shut down the outbound transaction service of the local system. Specifically, if the number of consecutive transaction failures or the transaction time required meets the preset fuse condition, the fuse mechanism of the local system is activated to shut down the outbound transaction service of the local system, including: if the number of consecutive transaction failures corresponding to the third-party system fault data exceeds the preset transaction failure number threshold, the fuse mechanism of the local system is activated to shut down the outbound transaction service of the local system; or, if the transaction time required corresponding to the third-party system fault data exceeds the preset transaction time threshold, the fuse mechanism of the local system is activated to shut down the outbound transaction service of the local system.

[0060] It is understandable that after the fuse mechanism is activated, the activation time and activation reason of the fuse mechanism are recorded, and relevant personnel are notified to perform troubleshooting and repair work. The fuse mechanism is set based on multiple aspects such as the stability of the local system and the third-party system to avoid setting an overly strict or overly loose fuse mechanism to ensure system availability and business continuity.

[0061] In this embodiment, after the fuse mechanism is started, a preset interval is determined based on business needs and the historical recovery time required for the corresponding third-party system, and the transaction request of the local system is sent to the third-party system based on the preset interval, so as to determine the recovery status of the third-party system through the response result obtained by the third-party system in response to the transaction request, and the outbound transaction service is restored based on the recovery status. Specifically, the recovery status of the third-party system is detected based on the fuse mechanism and using a preset timed task to reactivate the outbound transaction service of the local system through the detection result, including: sending the transaction request of the local system to the third-party system based on the fuse mechanism and the preset interval; determining the recovery status of the third-party system based on the response result obtained after the third-party system responds to the transaction request, so as to restore the outbound transaction service of the local system using the recovery status.

[0062] It can be understood that after sending the transaction request of the local system to the third-party system based on the preset interval time, if the response result obtained by the third-party system in response to the transaction request indicates that the transaction corresponding to the transaction request is successful, it means that the state of the third-party system is normal and the outbound transaction service of the local system can be restored; if the response result obtained by the third-party system in response to the transaction request indicates that the transaction corresponding to the transaction request fails, it means that the state of the third-party system is abnormal, and then jump to the step of sending the transaction request of the local system to the third-party system based on the fuse mechanism and the preset interval time. It is worth mentioning that the transaction request can be a low-priority transaction or a simulated transaction, which is intended to detect the state of the third-party system without interfering with the actual business.

[0063] Furthermore, based on the fuse mechanism and using a preset timed task, the recovery state of the third-party system is detected. If the detection result indicates that the third-party system is in a normal operating state, the third-party system is further subjected to a stability detection. If the stability detection result indicates that the third-party system is stable, the outbound transaction service of the local system is reactivated. Specifically, based on the fuse mechanism and using a preset timed task, the recovery state of the third-party system is detected, so as to reactivate the outbound transaction service of the local system through the detection result, including: based on the fuse mechanism and using a preset timed task, the recovery state of the third-party system is detected; if the detection result indicates that the third-party system is in a normal operating state, the operating state of the third-party system is subjected to a stability detection, and the outbound transaction service of the local system is reactivated based on the stability detection result.

[0064] It is understandable that the stability detection may include a series of test transaction requests, and monitor transaction indicators such as the response time and success rate of each transaction request. If the transaction indicator meets the preset stability condition, it indicates that the third-party system is in a stable state, and the outbound transaction service of the local system can be reactivated. In a specific implementation, the preset stability condition may be that when the transaction indicators such as the response time and success rate of each transaction request remain stable for ten consecutive detection cycles, it indicates that the transaction indicator meets the preset stability condition.

[0065] As can be seen from the above, the acquired third-party system fault data is judged by the pre-established preset fault library. If the preset fault library contains fault data corresponding to the third-party system fault data, the protection mechanism of the local system is activated, which can directly process the fault data in the preset fault library, effectively prevent foreseeable service interruptions, and reduce the workload of temporary troubleshooting; if the preset fault library does not contain fault data corresponding to the third-party system fault data, it is determined whether the number of consecutive transaction failures or the transaction duration corresponding to the third-party system fault data meets the preset fuse conditions. If so, the fuse mechanism of the local system is activated, and the preset timed task is used to reactivate the outbound transaction service of the local system. Through the protection mechanism and fuse mechanism configured by the local system, the start and shutdown of outbound transactions can be automatically triggered, with a high degree of automation. It not only replaces manual monitoring and repair, but also greatly reduces labor costs and operating costs.

[0066] It can be seen from the above embodiments that the present application reduces manual monitoring and repair costs based on fault data in a preset fault library. Therefore, the process of reducing manual monitoring and repair costs based on fault data in a preset fault library is described.

[0067] See also Figure 2 As shown, the embodiment of the present invention discloses a specific third-party system failure emergency processing method, including:

[0068] First, maintenance information for maintaining a third-party system and a corresponding maintenance time period are obtained, and fault data is constructed based on the maintenance information and the maintenance time period, and the fault data is saved in a preset fault library; after obtaining the preset fault library, the third-party system fault data is obtained to determine whether the third-party system fault data is consistent with the fault data in the preset fault library. If the third-party system fault data is consistent with the fault data in the preset fault library, it is characterized that the third-party system fault data is a predictive fault, and the protection mechanism of the local system is activated to shut down the outbound transaction service of the local system.

[0069] If the third-party system fault data is inconsistent with the fault data in the preset fault library, then determine whether the number of consecutive transaction failures corresponding to the third-party system fault data exceeds the preset transaction failure number threshold or determine whether the transaction time corresponding to the third-party system fault data exceeds the preset transaction delay threshold; if the number of consecutive transaction failures corresponding to the third-party system fault data does not exceed the preset transaction failure number threshold or determine that the transaction time corresponding to the third-party system fault data does not exceed the preset transaction delay threshold, then perform the outbound transaction service of the local system normally; if the number of consecutive transaction failures corresponding to the third-party system fault data exceeds the preset transaction failure number threshold or determine that the transaction time corresponding to the third-party system fault data exceeds the preset transaction delay threshold, then activate the fuse mechanism of the local system to shut down the outbound transaction service of the local system.

[0070] Then, based on a preset interval, the transaction request of the local system is sent to the third-party system, so as to determine the recovery status of the third-party system by utilizing the response result obtained after the third-party system responds to the transaction request; if the recovery status indicates that the third-party system is in a normal operating state, the outbound transaction service and related services of the local system are restored based on the recovery status without manual operation.

[0071] It can be seen from the above that the preset fault library built in advance can directly process the fault data of the third-party system that is consistent with the fault data of the preset fault library, effectively prevent foreseeable service interruptions, reduce the workload of temporary troubleshooting, and automatically trigger the start and shutdown of outbound transactions through system configuration, thereby improving the degree of system automation. Using automated tools instead of manual monitoring and repair not only greatly reduces labor costs and operating costs, but also improves the efficiency of fault handling.

[0072] Accordingly, see Figure 3 As shown, the present application also provides a third-party system failure emergency processing device, including:

[0073] A fault data judgment module 11 is used to obtain third-party system fault data and judge whether the third-party system fault data is fault data in a preset fault library;

[0074] A protection mechanism starting module 12 is used to start the protection mechanism of the local system to shut down the outbound transaction service of the local system if the third-party system fault data is the fault data in the preset fault library;

[0075] The fuse condition judgment module 13 is used to judge whether the number of consecutive transaction failures or the transaction time required corresponding to the third-party system fault data meets the preset fuse condition if the third-party system fault data is not the fault data in the preset fault library;

[0076] The transaction service activation module 14 is used to activate the circuit breaker mechanism of the local system to shut down the outbound transaction service of the local system if the number of consecutive transaction failures or the duration required for the transaction meets the preset circuit breaker condition, and detect the recovery status of the third-party system based on the circuit breaker mechanism and using the preset timed task, so as to reactivate the outbound transaction service of the local system through the detection result.

[0077] As can be seen from the above, the acquired third-party system fault data is judged by the pre-established preset fault library. If the preset fault library contains fault data corresponding to the third-party system fault data, the protection mechanism of the local system is activated, which can directly process the fault data in the preset fault library, effectively prevent foreseeable service interruptions, and reduce the workload of temporary troubleshooting; if the preset fault library does not contain fault data corresponding to the third-party system fault data, it is determined whether the number of consecutive transaction failures or the transaction duration corresponding to the third-party system fault data meets the preset fuse conditions. If so, the fuse mechanism of the local system is activated, and the preset timed task is used to reactivate the outbound transaction service of the local system. Through the protection mechanism and fuse mechanism configured by the local system, the start and shutdown of outbound transactions can be automatically triggered, with a high degree of automation. It not only replaces manual monitoring and repair, but also greatly reduces labor costs and operating costs.

[0078] In some specific implementations, the third-party system failure emergency processing device may further include:

[0079] A maintenance information acquisition unit, used to acquire maintenance information for maintaining a third-party system and a corresponding maintenance time period;

[0080] A fault data storage unit is used to obtain corresponding fault data based on the maintenance information and the maintenance time period, and save the fault data to a preset fault library.

[0081] In some specific implementations, the protection mechanism starting module 12 may specifically include:

[0082] A maintenance time period display unit is used to activate the protection mechanism of the local system if the third-party system fault data is fault data in a preset fault library, so as to shut down the outbound transaction service of the local system, and display the maintenance time period corresponding to the fault data on the preset display interface of the local system based on the preset fault library.

[0083] In some specific implementations, the fuse condition judgment module 13 may specifically include:

[0084] a transaction failure number judgment unit, configured to judge whether the number of consecutive transaction failures corresponding to the third-party system fault data exceeds a preset transaction failure number threshold if the third-party system fault data is not the fault data in the preset fault library;

[0085] The transaction time determination unit is used to determine whether the transaction time corresponding to the third-party system fault data exceeds a preset transaction delay threshold if the third-party system fault data is not the fault data in the preset fault library.

[0086] In some specific implementations, the transaction service activation module 14 may specifically include:

[0087] A first fuse mechanism initiation unit, configured to initiate a fuse mechanism of the local system to shut down the outbound transaction service of the local system if the number of consecutive transaction failures corresponding to the third-party system fault data exceeds a preset transaction failure number threshold;

[0088] The second fuse mechanism activation unit is used to activate the fuse mechanism of the local system to shut down the outbound transaction service of the local system if the transaction time corresponding to the third-party system fault data exceeds a preset transaction time threshold.

[0089] In some specific implementations, the transaction service activation module 14 may specifically include:

[0090] A transaction request sending unit, configured to send the transaction request of the local system to the third-party system based on the fuse mechanism and a preset interval time;

[0091] The recovery status determination unit is used to determine the recovery status of the third-party system based on the response result obtained after the third-party system responds to the transaction request, so as to use the recovery status to restore the outbound transaction service of the local system.

[0092] In some specific implementations, the transaction service activation module 14 may specifically include:

[0093] A recovery status detection unit, used to detect the recovery status of the third-party system based on the fuse mechanism and using a preset timed task;

[0094] The stability detection unit is used to perform a stability detection on the operating state of the third-party system if the detection result indicates that the third-party system is in a normal operating state, and reactivate the outbound transaction service of the local system based on the stability detection result.

[0095] Furthermore, the present application also discloses an electronic device. Figure 4 It is a structural diagram of an electronic device 20 shown according to an exemplary embodiment, and the content in the figure cannot be regarded as any limitation on the scope of use of this application. The electronic device 20 may specifically include: at least one processor 21, at least one memory 22, a power supply 23, a communication interface 24, an input / output interface 25, and a communication bus 26. Among them, the memory 22 is used to store a computer program, and the computer program is loaded and executed by the processor 21 to implement the relevant steps in the third-party system failure emergency handling method disclosed in any of the aforementioned embodiments. In addition, the electronic device 20 in this embodiment may specifically be an electronic computer.

[0096] In this embodiment, the power supply 23 is used to provide working voltage for each hardware device on the electronic device 20; the communication interface 24 can create a data transmission channel between the electronic device 20 and the external device, and the communication protocol it follows is any communication protocol that can be applied to the technical solution of the present application, and is not specifically limited here; the input and output interface 25 is used to obtain external input data or output data to the outside world, and its specific interface type can be selected according to specific application needs and is not specifically limited here.

[0097] In addition, the memory 22, as a carrier for storing resources, can be a read-only memory, a random access memory, a disk or an optical disk, etc. The resources stored thereon can include an operating system 221, a computer program 222, etc., and the storage method can be temporary storage or permanent storage.

[0098] The operating system 221 is used to manage and control the hardware devices and computer programs 222 on the electronic device 20, which can be Windows Server, Netware, Unix, Linux, etc. In addition to including a computer program that can be used to complete the third-party system failure emergency processing method performed by the electronic device 20 disclosed in any of the aforementioned embodiments, the computer program 222 can further include a computer program that can be used to complete other specific tasks.

[0099] Furthermore, the present application also discloses a computer-readable storage medium for storing a computer program; wherein, when the computer program is executed by a processor, the third-party system failure emergency handling method disclosed above is implemented. For the specific steps of the method, reference may be made to the corresponding contents disclosed in the above embodiments, and no further description will be given here.

[0100] In this specification, each embodiment is described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the embodiments can be referred to each other. For the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant parts can be referred to the method part.

[0101] Professionals may further appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the composition and steps of each example have been generally described in the above description according to function. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0102] The steps of the method or algorithm described in conjunction with the embodiments disclosed herein may be implemented directly using hardware, a software module executed by a processor, or a combination of the two. The software module may be placed in a random access memory (RAM), a memory, a read-only memory (ROM), an electrically programmable ROM, an electrically erasable programmable ROM, a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.

[0103] Finally, it should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the presence of other identical elements in the process, method, article or device including the elements.

[0104] The technical solution provided by the present application is introduced in detail above. Specific examples are used in this article to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method of the present application and its core idea. At the same time, for general technicians in this field, according to the idea of ​​the present application, there will be changes in the specific implementation methods and application scope. In summary, the content of this specification should not be understood as a limitation on the present application.

Claims

1. A method for emergency handling of third-party system failure, characterized in that: include: Obtaining third-party system fault data, and determining whether the third-party system fault data is fault data in a preset fault library; If the third-party system fault data is fault data in a preset fault library, the protection mechanism of the local system is activated to shut down the outbound transaction service of the local system; If the third-party system fault data is not the fault data in the preset fault library, determining whether the number of consecutive transaction failures or the transaction duration corresponding to the third-party system fault data meets the preset fuse condition; If the number of consecutive transaction failures or the duration required for the transaction meets the preset circuit breaker condition, the circuit breaker mechanism of the local system is activated to shut down the outbound transaction service of the local system, and the recovery status of the third-party system is detected based on the circuit breaker mechanism and using the preset timed task to reactivate the outbound transaction service of the local system through the detection result.

2. The method for emergency handling of third-party system failure according to claim 1, characterized in that: Before obtaining the third-party system fault data and determining whether the third-party system fault data is fault data in a preset fault library, the method further includes: Obtain maintenance information for third-party systems and the corresponding maintenance time period; Obtaining corresponding fault data based on the maintenance information and the maintenance time period, and saving the fault data to a preset fault library; The maintenance information includes system update information and network adjustment information of the third-party system.

3. The method for emergency handling of third-party system failure according to claim 2, characterized in that: If the third-party system fault data is fault data in a preset fault library, a protection mechanism of the local system is activated to shut down the outbound transaction service of the local system, including: If the third-party system fault data is fault data in a preset fault library, the protection mechanism of the local system is activated to shut down the outbound transaction service of the local system, and the maintenance time period corresponding to the fault data is displayed on the preset display interface of the local system based on the preset fault library.

4. The method for emergency handling of third-party system failure according to claim 1, characterized in that: If the third-party system fault data is not the fault data in the preset fault library, determining whether the number of consecutive transaction failures or the transaction duration corresponding to the third-party system fault data meets the preset fuse condition includes: If the third-party system fault data is not the fault data in the preset fault library, determining whether the number of consecutive transaction failures corresponding to the third-party system fault data exceeds a preset transaction failure number threshold; Or, if the third-party system fault data is not the fault data in the preset fault library, it is determined whether the transaction time corresponding to the third-party system fault data exceeds a preset transaction delay threshold.

5. The method for emergency handling of third-party system failure according to claim 4, characterized in that: If the number of consecutive transaction failures or the duration of the transaction meets the preset fuse condition, the fuse mechanism of the local system is activated to shut down the outbound transaction service of the local system, including: If the number of consecutive transaction failures corresponding to the third-party system failure data exceeds the preset transaction failure threshold, the fuse mechanism of the local system is activated to shut down the outbound transaction service of the local system; Alternatively, if the transaction time corresponding to the third-party system fault data exceeds a preset transaction time threshold, the fuse mechanism of the local system is activated to shut down the outbound transaction service of the local system.

6. The method for emergency handling of third-party system failure according to claim 1, characterized in that: The detecting of the recovery status of the third-party system based on the fuse mechanism and using a preset timed task, so as to reactivate the outbound transaction service of the local system according to the detection result, includes: Sending the transaction request of the local system to the third-party system based on the circuit breaker mechanism and the preset interval time; The recovery state of the third-party system is determined based on a response result obtained after the third-party system responds to the transaction request, so as to use the recovery state to restore the outbound transaction service of the local system.

7. The method for emergency handling of third-party system failure according to any one of claims 1 to 6, characterized in that: The detecting of the recovery status of the third-party system based on the fuse mechanism and using a preset timed task, so as to reactivate the outbound transaction service of the local system according to the detection result, includes: Based on the fuse mechanism and using a preset timed task, the recovery status of the third-party system is detected; If the detection result indicates that the third-party system is in a normal operating state, a stability detection is performed on the operating state of the third-party system, and the outbound transaction service of the local system is reactivated based on the stability detection result.

8. A third-party system failure emergency processing device, characterized in that: include: A fault data judgment module is used to obtain third-party system fault data and judge whether the third-party system fault data is fault data in a preset fault library; A protection mechanism startup module, used to start the protection mechanism of the local system if the third-party system fault data is fault data in a preset fault library, so as to shut down the outbound transaction service of the local system; A fuse condition judgment module, used for judging whether the number of consecutive transaction failures or the transaction time required corresponding to the third-party system fault data satisfies a preset fuse condition if the third-party system fault data is not the fault data in the preset fault library; The transaction service activation module is used to activate the circuit breaker mechanism of the local system to shut down the outbound transaction service of the local system if the number of consecutive transaction failures or the duration required for the transaction meets the preset circuit breaker condition, and to detect the recovery status of the third-party system based on the circuit breaker mechanism and using the preset timed task, so as to reactivate the outbound transaction service of the local system through the detection result.

9. An electronic device, characterized in that: include: Memory, used to store computer programs; A processor is used to execute the computer program to implement the third-party system failure emergency processing method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: Used to store a computer program, wherein when the computer program is executed by a processor, the third-party system failure emergency processing method according to any one of claims 1 to 7 is implemented.

Images