A third-party system failure emergency processing method, device, equipment and medium

Abstract

The present application discloses a third-party system fault emergency response method, apparatus, device, and medium, which relate to the field of information technology, including: determining whether acquired third-party system fault data is fault data in a preset fault library; if the third-party system fault data is fault data in the preset fault library, activating a local system protection mechanism to shut down an outbound call transaction service; 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 of the third-party system fault data meets a preset circuit breaker condition; if the number of consecutive transaction failures or the transaction duration meets the preset circuit breaker condition, activating a circuit breaker mechanism to shut down the outbound call transaction service, detecting the recovery status of the third-party system based on the circuit breaker mechanism and using a preset timed task, and reactivating the outbound call transaction service based on the detection result. This allows for timely response to emergencies in the third-party system 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, to enhance customer experience and business efficiency, financial institutions have established close, secure collaborations with a wide range of external partners, enabling one-stop services such as fund settlement and account management. However, the integration of multiple systems also presents new challenges: the instability of third-party systems and the frequent occurrence of unexpected incidents, such as downtime during system upgrades and network connection failures, which directly impact the quality of financial institutions' services.

[0003] Current countermeasures typically rely on external platforms' monitoring capabilities. When anomalies are detected, they notify relevant personnel for manual intervention, including locating the source of the problem, coordinating third-party technical support, and addressing the resulting public outcry. While this approach can address the problem to a certain extent, it is cumbersome, time-consuming, and highly labor-intensive.

[0004] As can be seen from the above, 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 handling method, device, equipment and medium, which can respond to the sudden situation of the third-party system in a timely manner without relying on manpower. The specific solution is as follows:

[0006] In a first aspect, the present application provides a method for emergency handling of third-party system failures, 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 the preset fault database, 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 fault data in the preset fault database, determining whether the number of consecutive transaction failures or the transaction duration corresponding to the third-party system fault data meets the preset circuit breaker conditions;

[0010] If the number of consecutive transaction failures or the duration of the transaction meets the preset circuit breaker conditions, 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 results.

[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 and corresponding maintenance time periods for third-party systems;

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

[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 database, activating a protection mechanism of the local system to shut down the outbound transaction service of the local system includes:

[0016] 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 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 database, determining whether the number of consecutive transaction failures or the transaction duration corresponding to the third-party system fault data meets a preset circuit breaker condition includes:

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

[0019] Alternatively, if the third-party system fault data is not fault data in the preset fault database, 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 transaction duration meets the preset circuit breaker condition, activating a circuit breaker mechanism of the local system to shut down the outbound transaction service of the local system includes:

[0021] If the number of consecutive transaction failures corresponding to the third-party system fault data exceeds a preset transaction failure threshold, the circuit breaker 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 circuit breaker mechanism of the local system is activated to shut down the outbound transaction service of the local system.

[0023] Optionally, the detecting of the recovery status of the third-party system based on the circuit breaker mechanism and using a preset timed task to reactivate the outbound transaction service of the local system based on 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 a preset interval;

[0025] The recovery status 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 status to restore the outbound transaction service of the local system.

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

[0027] Based on the fuse mechanism and using preset timed tasks, 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 test 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 test result.

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

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

[0031] a protection mechanism activation module, configured to activate 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 fault data in a preset fault database;

[0032] a circuit breaker condition judgment module, configured to judge whether the number of consecutive transaction failures or the transaction duration corresponding to the third-party system fault data satisfies a preset circuit breaker condition if the third-party system fault data is not fault data in the preset fault database;

[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, comprising:

[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] This 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 activated; 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 circuit breaker conditions; if the number of consecutive transaction failures or the transaction time required meets the preset circuit breaker conditions, the circuit breaker mechanism of the local system is activated, and the recovery status of the third-party system is detected 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 results.

[0039] As can be seen from the above, the acquired third-party system fault data is judged by using a pre-established preset fault library. If there is fault data corresponding to the third-party system fault data in the preset fault library, 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 there is no fault data corresponding to the third-party system 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 circuit breaker conditions. If so, the circuit breaker 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 circuit breaker 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 following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are merely embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying any creative work.

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

[0042] Figure 2 This is 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 fault 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 clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the accompanying drawings. 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 making creative efforts 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 failure, 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, this application provides a third-party system failure emergency response method. Through the protection mechanism and fuse mechanism configured in the local system, the start and stop of outbound transactions can be automatically triggered. The high degree of automation 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 is established between the local system and the third-party system. Based on the connection relationship, maintenance information and a corresponding maintenance time period for maintaining the third-party system are obtained. Corresponding fault data is constructed using 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, the process 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 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 database, 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, avoiding the loss of transaction data. In a specific embodiment, if an ongoing transaction service occurs during the process of shutting down the outbound transaction service of the local system, a prompt indicating that the current transaction has failed 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 fault data in the preset fault database, determine whether the number of consecutive transaction failures or the transaction duration corresponding to the third-party system fault data meets the preset circuit breaker condition.

[0055] In this embodiment, if the third-party system fault data is not fault data in the preset fault library, then it is determined whether the number of consecutive transaction failures corresponding to the third-party system fault data exceeds the preset transaction failure threshold or whether the transaction duration corresponding to the third-party system fault data exceeds the preset transaction delay threshold. Specifically, if the third-party system fault data is not fault data in the preset fault library, then 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 circuit breaker condition, including: if the third-party system fault data is not fault data in the preset fault library, then it is determined whether the number of consecutive transaction failures corresponding to the third-party system fault data exceeds the preset transaction failure threshold; or if the third-party system fault data is not fault data in the preset fault library, then it is determined whether the transaction duration corresponding to the third-party system fault data exceeds the preset transaction delay threshold.

[0056] In one specific embodiment, if the third-party system fault data is not in the preset fault database, the number of consecutive transaction failures corresponding to the third-party system fault data within a preset time period is obtained. The consecutive transaction failure number is the number of consecutive transaction failures, i.e., the number of transaction failures corresponding to each transaction failure is continuous, i.e., there is no obvious interval between successful transactions. A preset transaction failure threshold is set based on factors such as transaction importance and business tolerance, and a determination is made as to whether the number of consecutive transaction failures corresponding to the third-party system fault data exceeds the preset transaction failure threshold.

[0057] In another specific embodiment, the total duration required from the start to the end of each transaction is calculated based on the third-party system failure data, which is the transaction duration corresponding to the third-party system failure data. The transaction duration 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 duration 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 of 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.

[0059] In this embodiment, if the number of consecutive transaction failures corresponding to the third-party system fault data exceeds a preset transaction failure threshold within a preset time period, or if the transaction duration corresponding to the third-party system fault data exceeds a preset transaction duration threshold, it indicates that the circuit breaker trigger condition of the local system is met, and the circuit breaker 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 duration 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, including: if the number of consecutive transaction failures corresponding to the third-party system fault data exceeds the preset transaction failure threshold, the circuit breaker mechanism of the local system is activated to shut down the outbound transaction service of the local system; or if the transaction duration corresponding to the third-party system fault data exceeds the preset transaction duration threshold, the circuit breaker 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 circuit breaker mechanism is activated, the activation time and activation reason of the circuit breaker mechanism are recorded, and relevant personnel are notified to perform troubleshooting and repair work. The circuit breaker 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 circuit breaker mechanism to ensure system availability and business continuity.

[0061] In this embodiment, after the fuse mechanism is activated, 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 is understandable that after the transaction request of the local system is sent 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 status 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 status of the third-party system is abnormal, and the process jumps to the step of sending the transaction request of the local system to the third-party system based on the circuit breaker 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 status of the third-party system without interfering with actual business.

[0063] Furthermore, 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, the third-party system is further subjected to a stability test. If the stability test 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 status of the third-party system is detected, so as to reactivate the outbound transaction service of the local system through the test result, including: 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, the operating status of the third-party system is subjected to a stability test, and the outbound transaction service of the local system is reactivated based on the stability test result.

[0064] It is understood that the stability test 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 indicators meet the preset stability conditions, the third-party system is in a stable state, and the outbound transaction service of the local system can be reactivated. In a specific embodiment, 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, the transaction indicators meet the preset stability condition.

[0065] As can be seen from the above, the acquired third-party system fault data is judged by using a pre-established preset fault library. If there is fault data corresponding to the third-party system fault data in the preset fault library, 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 there is no fault data corresponding to the third-party system 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 circuit breaker conditions. If so, the circuit breaker 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 circuit breaker 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 method for emergency handling of third-party system failures, 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, and it is determined 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 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 threshold or it is determined that the transaction time corresponding to the third-party system fault data does not exceed the preset transaction delay threshold, then the outbound transaction service of the local system is carried out normally; if the number of consecutive transaction failures corresponding to the third-party system fault data exceeds the preset transaction failure threshold or it is determined that the transaction time corresponding to the third-party system fault data exceeds the preset transaction delay threshold, then the fuse mechanism of the local system is activated 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 using 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] As can be seen from the above, the preset fault library built in advance can directly process third-party system fault data that is consistent with the fault data in the preset fault library, effectively preventing foreseeable service interruptions and reducing the workload of temporary troubleshooting. The system configuration automatically triggers the start and shutdown of outbound call transactions, thereby improving the system's automation level. By using automated tools instead of manual monitoring and repair, it 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 fault emergency processing device, including:

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

[0074] A protection mechanism activation module 12 is configured to activate a 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 fault data in a preset fault database;

[0075] a circuit breaker condition determination module 13 for determining, if the third-party system fault data is not fault data in the preset fault database, whether the number of consecutive transaction failures or the transaction duration corresponding to the third-party system fault data satisfies a preset circuit breaker condition;

[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 time 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.

[0077] As can be seen from the above, the acquired third-party system fault data is judged by using a pre-established preset fault library. If there is fault data corresponding to the third-party system fault data in the preset fault library, 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 there is no fault data corresponding to the third-party system 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 circuit breaker conditions. If so, the circuit breaker 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 circuit breaker 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 fault emergency processing device may further include:

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

[0080] The fault data storage unit is configured to obtain corresponding fault data based on the maintenance information and the maintenance time period, and to store the fault data in a preset fault database.

[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 determination unit, configured to determine, if the third-party system fault data is not fault data in the preset fault database, whether the number of consecutive transaction failures corresponding to the third-party system fault data exceeds a preset transaction failure number threshold;

[0085] The transaction time determination unit is configured 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 circuit breaker mechanism activation unit, configured 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 corresponding to the third-party system fault data exceeds a preset transaction failure number threshold;

[0088] The second circuit breaker mechanism activation unit 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 transaction time corresponding to the third-party system fault data exceeds the 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 circuit breaker mechanism and a preset interval;

[0091] The recovery status determining 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, configured to detect the recovery status of a 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 status 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 embodiment of the present application also discloses an electronic device, Figure 4 This is a structural diagram of an electronic device 20 according to an exemplary embodiment. The content in the diagram cannot be considered 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. The memory 22 is used to store a computer program, which 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 operating 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. The communication protocol it follows is any communication protocol that can be applied to the technical solution of this 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. 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 resource storage, can be a read-only memory, random access memory, disk or CD, 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 on the electronic device 20 and the computer program 222, and can be Windows Server, NetWare, Unix, Linux, etc. In addition to including a computer program capable of implementing the third-party system failure emergency handling method executed by the electronic device 20 disclosed in any of the aforementioned embodiments, the computer program 222 can further include computer programs capable of completing other specific tasks.

[0099] Furthermore, this application also discloses a computer-readable storage medium for storing a computer program; wherein, when executed by a processor, the computer program implements the aforementioned disclosed method for emergency handling of third-party system failures. The specific steps of this method can be found in the corresponding contents disclosed in the aforementioned embodiments and will not be further described here.

[0100] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on its differences from the other embodiments. Reference can be made to the descriptions of the identical or similar parts between the various embodiments. For the devices disclosed in the embodiments, since they correspond to the methods disclosed in the embodiments, the descriptions are relatively simple, and the relevant parts can be referred to the descriptions of the methods.

[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 above description has generally described the components and steps of each example according to their functions. 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 beyond the scope of this application.

[0102] The steps of the methods or algorithms 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 random access memory (RAM), internal memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, 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 document, relational terms such as first and second, etc., are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the terms "comprises," "comprising," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or elements inherent to such process, method, article, or device. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of additional identical elements in the process, method, article, or device comprising the element.

[0104] The above is a detailed introduction to the technical solution provided by the present application. Specific examples are used herein 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 those skilled in the art, according to the ideas of the present application, there may 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 failures, 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 the preset fault database, 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 fault data in the preset fault database, determining whether the number of consecutive transaction failures or the transaction duration corresponding to the third-party system fault data meets the preset circuit breaker conditions; If the number of consecutive transaction failures or the transaction duration 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 a preset timer task, so as to reactivate the outbound transaction service of the local system based on the detection result; 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: obtaining maintenance information for maintaining the third-party system and a corresponding maintenance time period; obtaining corresponding fault data based on the maintenance information and the maintenance time period, and saving the fault data to the preset fault library; wherein the maintenance information includes system update information and network adjustment information of the third-party system; Among them, 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, 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.

2. 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 fault data in the preset fault database, determining whether the number of consecutive transaction failures or the transaction duration corresponding to the third-party system fault data meets a preset circuit breaker condition includes: If the third-party system fault data is not fault data in the preset fault database, determining whether the number of consecutive transaction failures corresponding to the third-party system fault data exceeds a preset transaction failure threshold; Alternatively, if the third-party system fault data is not fault data in the preset fault database, it is determined whether the transaction time corresponding to the third-party system fault data exceeds a preset transaction delay threshold.

3. The method for emergency handling of third-party system failure according to claim 2, characterized in that: If the number of consecutive transaction failures or the transaction duration 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, including: If the number of consecutive transaction failures corresponding to the third-party system fault data exceeds a preset transaction failure threshold, the circuit breaker 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 circuit breaker mechanism of the local system is activated to shut down the outbound transaction service of the local system.

4. 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 circuit breaker 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 a preset interval; The recovery status 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 status to restore the outbound transaction service of the local system.

5. The method for emergency handling of third-party system failure according to any one of claims 1 to 4, characterized in that: The detecting of the recovery status of the third-party system based on the circuit breaker 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 preset timed tasks, 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 test 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 test result.

6. A third-party system fault emergency processing device, characterized in that: include: A fault data judgment module is used to obtain third-party system fault data and determine whether the third-party system fault data is fault data in a preset fault library; a protection mechanism activation module, configured to activate 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 fault data in a preset fault database; a circuit breaker condition judgment module, configured to judge whether the number of consecutive transaction failures or the transaction duration corresponding to the third-party system fault data satisfies a preset circuit breaker condition if the third-party system fault data is not fault data in the preset fault database; a transaction service activation module configured to activate a local system circuit breaker mechanism to shut down the outbound transaction service of the local system if the number of consecutive transaction failures or the transaction duration 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 a preset timed task, so as to reactivate the outbound transaction service of the local system based on the detection result; The third-party system fault emergency processing device is further configured to obtain maintenance information and a corresponding maintenance time period for the third-party system; obtain corresponding fault data based on the maintenance information and the maintenance time period, and save the fault data to a preset fault database; wherein the maintenance information includes system update information and network adjustment information of the third-party system; Among them, the protection mechanism startup module is specifically used to start the protection mechanism of the local system if the third-party system fault data is fault data in the 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.

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

8. 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 5 is implemented.

Images