Transaction event processing method and device, equipment and storage medium

Abstract

The embodiment of the invention provides a transaction event processing method and device, equipment and a storage medium, which can be applied to the technical field of computers, in the method, a processing flow link for a transaction event is split into a plurality of sub-processing links; for each sub-processing link, executing the following operations: receiving a processing request for the transaction event sent by the previous sub-processing link; performing admission detection on the processing request of the transaction event to obtain an admission detection result; in this way, the abnormity of the processing request of the transaction event can be positioned to a specific sub-processing link, and if the admission detection result is flow interruption, abnormal factors causing the flow interruption are repaired; and after the abnormal factors are repaired, the steps of executing admission detection on the processing request of the transaction event and obtaining the admission detection result are returned, so that the timely repair of the process interruption is realized, the business processing efficiency of the transaction system is improved, and the availability and stability of the transaction system are ensured.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of computer technology, and in particular, to a transaction event processing method, apparatus, device, and storage medium. Background Art

[0002] With the development of Internet technology, the interaction of trading systems is increasing. Accordingly, when trading systems process trading events, there are more and more processing links. In related technologies, when access anomalies occur when trading events flow between different links, special technical means are usually used to modify the erroneous results in the database and then reprocess the trading events from the beginning.

[0003] However, when an abnormality occurs in a transaction event, the above method is difficult to locate the specific link where the abnormality occurs, and each time an abnormality occurs, the transaction event needs to be reprocessed from the beginning, which seriously affects the business processing efficiency of the transaction system and cannot guarantee the availability and stability of the transaction system. Summary of the invention

[0004] The embodiments of the present invention provide a transaction event processing method, device, equipment and storage medium for locating the specific link where the abnormality occurs, improving the business processing efficiency of the transaction system, and ensuring the availability and stability of the transaction system.

[0005] On the one hand, an embodiment of the present application provides a transaction event processing method, the method comprising:

[0006] Split the transaction event processing process into multiple sub-processing steps;

[0007] For each sub-processing step, perform the following operations:

[0008] Receiving a processing request for the transaction event sent by a previous sub-processing link;

[0009] Performing an access detection on the processing request of the transaction event to obtain an access detection result;

[0010] If the admission detection result is a process interruption, the abnormal factors causing the process interruption are repaired; and after the abnormal factors are repaired, the process returns to the step of performing an admission detection on the processing request of the transaction event to obtain the admission detection result.

[0011] Optionally, performing an admission test on the processing request of the transaction event to obtain an admission test result includes:

[0012] For the preset multiple checkpoints, the following operations are respectively performed: using a check program corresponding to a checkpoint, detecting the information of the processing request of the transaction event at the checkpoint, and obtaining a corresponding checkpoint result;

[0013] The admission detection result is determined based on the obtained multiple checkpoint results.

[0014] Optionally, determining the admission detection result based on the obtained multiple checkpoint results includes:

[0015] If at least one of the multiple checkpoint results is an abnormal result, the admission detection result is a process interruption.

[0016] Optionally, the one checkpoint is a data checkpoint; the using a check program corresponding to the one checkpoint to detect the information of the one checkpoint on the processing request of the transaction event to obtain a corresponding checkpoint result includes:

[0017] Using the check program corresponding to the data checkpoint, respectively perform anomaly detection on multiple data items in the processing request of the transaction event;

[0018] When there is at least one data item abnormality, the checkpoint result of the data checkpoint is a data configuration abnormality;

[0019] When the multiple data items are all normal, the checkpoint result of the data checkpoint is that the data configuration is normal.

[0020] Optionally, the abnormal factor is a data configuration abnormality; and repairing the abnormal factor causing the process interruption includes:

[0021] Return to the previous sub-processing link and modify the abnormal data item in the processing request of the transaction event.

[0022] Optionally, the parameter checkpoint of the one checkpoint; the use of a check program corresponding to the one checkpoint to detect the information of the processing request of the transaction event at the one checkpoint to obtain a corresponding checkpoint result, comprises:

[0023] If the processing identifier configured in the check program corresponding to the parameter checkpoint is different from the processing identifier carried by the processing request, the checkpoint result of the parameter checkpoint is a parameter configuration exception, wherein the processing identifier carried by the processing request is used to characterize the type of the processing request;

[0024] If the processing identifier of the check program configuration corresponding to the parameter checkpoint is the same as the processing identifier carried by the processing request, the checkpoint result of the parameter checkpoint is a parameter configuration exception.

[0025] Optionally, the abnormal factor is a parameter configuration abnormality; and repairing the abnormal factor causing the process interruption includes:

[0026] Return to the parameter configuration link and modify the processing identifier configured in the inspection program corresponding to the parameter checkpoint.

[0027] Optionally, the multiple sub-processing links are executed asynchronously.

[0028] On the one hand, an embodiment of the present application provides a transaction information processing device, the device comprising:

[0029] The decomposition module is used to split the processing flow of transaction events into multiple sub-processing links.

[0030] The processing module is used to perform the following operations for each sub-processing link: receiving a processing request for the transaction event sent by the previous sub-processing link; performing an admission detection on the processing request for the transaction event to obtain an admission detection result;

[0031] If the admission detection result is a process interruption, the abnormal factors causing the process interruption are repaired; and after the abnormal factors are repaired, the process returns to the step of performing an admission detection on the processing request of the transaction event to obtain the admission detection result.

[0032] Optionally, the processing module is specifically used for:

[0033] For the preset multiple checkpoints, the following operations are respectively performed: using a check program corresponding to a checkpoint, detecting the information of the processing request of the transaction event at the checkpoint, and obtaining a corresponding checkpoint result;

[0034] The admission detection result is determined based on the obtained multiple checkpoint results.

[0035] Optionally, the processing module is specifically used for:

[0036] If at least one of the multiple checkpoint results is an abnormal result, the admission detection result is a process interruption.

[0037] Optionally, the processing module is specifically used for:

[0038] Using the check program corresponding to the data checkpoint, respectively perform anomaly detection on multiple data items in the processing request of the transaction event;

[0039] When there is at least one data item abnormality, the checkpoint result of the data checkpoint is a data configuration abnormality;

[0040] When the multiple data items are all normal, the checkpoint result of the data checkpoint is that the data configuration is normal.

[0041] Optionally, the processing module is specifically used for:

[0042] If the processing identifier configured in the check program corresponding to the parameter checkpoint is different from the processing identifier carried by the processing request, the checkpoint result of the parameter checkpoint is a parameter configuration exception, wherein the processing identifier carried by the processing request is used to characterize the type of the processing request;

[0043] If the processing identifier of the check program configuration corresponding to the parameter checkpoint is the same as the processing identifier carried by the processing request, the checkpoint result of the parameter checkpoint is a parameter configuration exception.

[0044] Optionally, the processing module is specifically used for:

[0045] Return to the parameter configuration link and modify the processing identifier configured in the inspection program corresponding to the parameter checkpoint.

[0046] Optionally, the multiple sub-processing links are processed asynchronously.

[0047] In one aspect, an embodiment of the present application provides a computer device, including:

[0048] A memory for storing program instructions;

[0049] The processor is used to call the program instructions stored in the memory and execute the steps of the above-mentioned transaction event processing method according to the obtained program.

[0050] On the one hand, an embodiment of the present application provides a computer-readable storage medium storing a computer program executable by a computer device, and when the program is run on the computer device, the computer executes the steps of the above-mentioned transaction event processing method.

[0051] On the one hand, an embodiment of the present application provides a computer program product, including a computer program stored on a computer-readable storage medium, wherein the computer program includes program instructions, and when the program instructions are executed by a computer device, the computer device executes the steps of the above-mentioned transaction event processing method.

[0052] In an embodiment of the present application, the processing flow of a transaction event is divided into a plurality of sub-processing links for processing, and in each sub-processing link, an access check is first performed on the received processing request, so that the anomaly of the processing request of the transaction event can be located in a specific sub-processing link, and, when the access check result is a process interruption, the abnormal factors that cause the process interruption can be repaired, and after the abnormal factors are repaired, the process returns to execute the access check on the processing request of the transaction event to obtain the access check result, thereby achieving timely repair of process interruptions and improving the fault tolerance, maintainability and robustness of the transaction system; at the same time, the increasingly complex transaction system is modeled, standardized and formatted, thereby improving the processing efficiency of the transaction system and making the transaction system suitable for promotion and reuse. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0054] Figure 1 A schematic diagram of a system architecture provided in an embodiment of the present application;

[0055] Figure 2 A flowchart of a transaction event processing method provided in an embodiment of the present application;

[0056] Figure 3 A flowchart of a transaction event processing method provided in an embodiment of the present application;

[0057] Figure 4 A flowchart of a transaction event processing method provided in an embodiment of the present application;

[0058] Figure 5 A schematic diagram of a process processing link provided in an embodiment of the present application;

[0059] Figure 6 A schematic diagram of the structure of a transaction event processing device provided in an embodiment of the present application;

[0060] Figure 7 A schematic diagram of the structure of a computer device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0061] In order to make the purpose, technical scheme and beneficial effects of the present invention more clear, the present invention is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not intended to limit the present invention. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present invention.

[0062] The following is a brief introduction to the system architecture diagram applicable to the technical solution of the embodiment of the present application. It should be noted that the process introduced below is only used to illustrate the embodiment of the present application and is not a limitation.

[0063] refer to Figure 1 , which is a system architecture diagram applicable to an embodiment of the present application. The system architecture includes at least a terminal device 101 and a server 102. The number of terminal devices 101 can be one or more, and the number of servers 102 can also be one or more. The present application does not specifically limit the number of terminal devices 101 and servers 102.

[0064] The terminal device 101 is pre-installed with an application with transaction functions, which is a client application, a web application, a small program application, etc. The terminal device 101 can be a smart phone, a tablet computer, a laptop computer, a desktop computer, a smart home appliance, a smart voice interaction device, a smart car device, etc., but is not limited thereto.

[0065] Server 102 is the background server of the application. Server 102 can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers. It can also be a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content delivery networks (CDN), as well as big data and artificial intelligence platforms, but is not limited to these.

[0066] It should be noted that the method in the embodiment of the present application can be executed by the terminal device 101 or the server 102 alone, or can be executed by the terminal device 101 and the server 102 together.

[0067] In the embodiment of the present application, the terminal device 101 and the server 102 may be directly or indirectly connected to each other through one or more networks. The network may be a wired network or a wireless network, for example, a mobile cellular network, or a wireless fidelity (Wireless-Fidelity, WIFI) network, or other possible networks, which are not limited in the embodiment of the present application.

[0068] The following is a description of exemplary embodiments of the present application in conjunction with the accompanying drawings, including various details of the embodiments of the present application to facilitate understanding, which should be considered as merely exemplary. Therefore, those of ordinary skill in the art should recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope of the present application. Similarly, for the sake of clarity and conciseness, the description of well-known functions and structures is omitted in the following description. It should be noted that in the embodiments of the present application, certain software, components, models and other existing solutions in the industry may be mentioned, which should be considered as exemplary, and their purpose is only to illustrate the feasibility of the implementation of the technical solution of the present application, but it does not mean that the applicant has or will necessarily use the solution.

[0069] It should be noted that the acquisition, transmission, storage, and use of data in the technical solution of this application are in compliance with the relevant provisions of national laws and regulations.

[0070] The following is based on Figure 1 The system architecture diagram shown in FIG. 1 shows a flow chart of a transaction event processing method provided in an embodiment of the present application. The flow chart of the transaction event processing method can be as follows: Figure 1 The terminal device 101 shown in the figure may also be executed by the server 102, or the terminal device 101 and the server 102 may interact to execute the Figure 2 As shown, the following steps are included:

[0071] Step 201, split the processing flow link for the transaction event into multiple sub-processing links.

[0072] Specifically, a transaction event needs to be processed differently according to its functions. Since a long processing flow link has complex functions, a processing flow link is split into multiple sub-processing links, and the multiple sub-processing links are managed independently.

[0073] Before the processing flow of a transaction event is split into multiple sub-processing links, the processing flow generates a processing identifier for each transaction event. All subsequent processing requests for transaction events issued by all sub-processing links carry the processing identifier. The processing identifier carried by the processing request is used to characterize the type of the processing request.

[0074] Step 202: for each sub-processing step, perform the following steps 2021 to 2023 respectively:

[0075] Step 2021, receiving a processing request for a transaction event sent by the previous sub-processing link.

[0076] Specifically, if the current sub-processing link is the first sub-processing link in the processing flow link, then in the first sub-processing link, an initial processing request of the transaction event corresponding to the processing flow link is received. In the first sub-processing link, the initial processing request of the transaction event is processed to obtain a processing result. Then, the operation to be performed in the next sub-processing link is analyzed, and a corresponding processing request is generated, and then the processing request is sent to the next sub-processing link.

[0077] If the current sub-processing link is not the first sub-processing link in the processing flow link, then in the current sub-processing link, a processing request for the transaction event sent after the previous sub-processing link is completed is received.

[0078] When a processing request for a transaction event enters the current sub-processing link from the previous sub-processing link, the current sub-processing link needs to record the processing request for the transaction event so that the current sub-processing link knows the processing operation that needs to be performed on the processing request for the transaction event.

[0079] Step 2022: perform an access check on the request for processing the transaction event and obtain an access check result.

[0080] Specifically, in a traditional trading system, when processing a request to process a trading event, if data errors or parameter configuration errors are found, the trading system cannot restore the normal event processing flow, and it is often necessary to start an emergency version of the trading system or adopt technical repair methods. Therefore, the present application first performs access detection on the processing request of the trading event in multiple sub-processing links, and then performs the execution method of the processing.

[0081] In an embodiment of the present application, in multiple sub-processing links, the processing request of a transaction event is first subjected to access detection and then processed. Compared with the prior art in which the processing request of a transaction event is directly processed, an error is found during the processing process, resulting in abnormal transaction event access. Even if the data is repaired, the normal transaction event processing flow cannot be restored. The operation of first conducting access detection and then processing in the present application can ensure the accuracy of the processing request of a transaction event during the processing process, thereby improving the processing efficiency of the transaction system.

[0082] Specifically, traditional inspection procedures are hard-coded and fixed, resulting in random error causes. Once an abnormality is found in the processing request of a transaction event, it cannot be processed normally through preset means.

[0083] In view of this, the present application performs the following operations for the preset multiple checkpoints of the processing request for the transaction event: adopt the inspection program corresponding to a checkpoint to detect the information of the processing request for the transaction event at a checkpoint, and obtain the corresponding checkpoint result; based on the obtained multiple checkpoint results, determine the access detection result.

[0084] Specifically, after the current sub-processing link records the processing request of the transaction event, it is necessary to perform accuracy and validity checks on multiple preset checkpoints of the processing request in the current sub-processing link. Each checkpoint corresponds to a check program, and a processing identifier is configured in the check program. The processing identifiers configured in the check program corresponding to multiple checkpoints are different. The processing identifier configured in the check program determines the check rule of the corresponding checkpoint.

[0085] In an embodiment of the present application, the processing identifier in the current inspection program is flexibly configured, and the processing identifiers configured in the inspection programs corresponding to multiple checkpoints are different. Therefore, it is possible to quickly locate the error of the processing identifier in the inspection program corresponding to a specific checkpoint, so that it can be repaired in time and the transaction system can resume the normal processing flow of transaction events.

[0086] Step 2023, if the result of the access detection is that the process is interrupted, the abnormal factors that cause the process interruption are repaired; and after the abnormal factors are repaired, return to the step of performing access detection on the processing request of the transaction event to obtain the access detection result.

[0087] In some embodiments, if at least one of the multiple checkpoint results is an abnormal result, the admission detection result is a process interruption.

[0088] Specifically, when there is at least one checkpoint result that is an abnormal result, the processing request for the transaction event issued by the previous sub-processing link is considered abnormal. It can be inferred that the previous sub-processing link is an abnormal processing link. Therefore, the current sub-processing link will not process the processing request for the received transaction event, thereby causing the process to be interrupted.

[0089] In some embodiments, a check program corresponding to the data checkpoint is used to perform anomaly detection on multiple data items in the processing request of the transaction event; when there is at least one data item abnormality, the checkpoint result of the data checkpoint is that the data configuration is abnormal; when multiple data items are normal, the checkpoint result of the data checkpoint is that the data configuration is normal.

[0090] Specifically, when data items are missing or blank, the data items are considered abnormal, that is, the checkpoint result of the data checkpoint is abnormal data configuration. If the data items are complete and accurate, the checkpoint result of the data checkpoint is considered normal data configuration.

[0091] In some embodiments, if the abnormal factor is a data configuration abnormality, the process returns to the previous sub-processing link to modify the abnormal data item in the processing request of the transaction event.

[0092] Specifically, the previous sub-processing link sends a processing request for a transaction event to the current sub-processing link, and the check program of the current sub-processing link checks the processing request for the transaction event and generates a checkpoint result. When the current sub-processing link determines that the abnormal factor of the processing request for the transaction event is a data configuration abnormality based on the checkpoint result, the processing request for the transaction event is returned to the previous sub-processing link, so that the previous sub-processing link can modify the data configuration abnormality in the processing request; if the previous sub-processing link cannot modify the data configuration abnormality of the processing request, it is manually forced to modify it.

[0093] In some embodiments, if the processing identifier configured in the check program corresponding to the parameter checkpoint is different from the processing identifier carried by the processing request, the checkpoint result of the parameter checkpoint is that the parameter configuration is abnormal, wherein the processing identifier carried by the processing request is used to characterize the type of the processing request; if the processing identifier configured in the check program corresponding to the parameter checkpoint is the same as the processing identifier carried by the processing request, then the checkpoint result of the parameter checkpoint is that the parameter configuration is normal.

[0094] Specifically, before the processing flow is split into multiple sub-processing links, a processing identifier is generated for each transaction event. All subsequent processing requests for transaction events issued by the sub-processing links carry the processing identifier, and the processing identifier carried by the processing request is used to characterize the type of processing request. The processing identifier configured in the check program is used to indicate the type of processing request that the check program can check.

[0095] When the processing identifier carried in the processing request is different from the processing identifier configured in the checking program, it means that the type of processing request that the checking program can check does not match the type of processing request of the transaction event actually checked. Therefore, the checkpoint result of the parameter checkpoint is determined to be a parameter configuration abnormality. If the processing identifier carried in the processing request is the same as the processing identifier configured in the checking program, the checkpoint result of the parameter checkpoint is considered to be a normal parameter configuration.

[0096] In some embodiments, if the abnormal factor is a parameter configuration abnormality, the process returns to the parameter configuration link and the processing identifier configured in the inspection program corresponding to the parameter checkpoint is modified.

[0097] Specifically, if the inspection result of the parameter checkpoint in the sub-processing link is that the parameter configuration is abnormal, the processing request of the transaction event is placed in the queue to be repaired for the parameter configuration abnormality, and the parameter configuration link is returned to modify the processing identifier configured in the inspection program.

[0098] The processing identifier configured in the inspection program is modified in the parameter configuration stage. The parameter configuration stage can modify it automatically according to the preset parameter configuration rules, or it can be manually forced to modify it.

[0099] In an embodiment of the present application, by classifying the abnormal factors of the checkpoint results, the abnormal checkpoint results of the processing request can be located as two specific situations: data configuration abnormality and parameter configuration abnormality. Corresponding repair methods can be preset for these two situations, thereby achieving automatic repair of process interruptions, reducing manual losses, and improving the processing efficiency of the transaction system.

[0100] If the checkpoint result of the transaction event processing request is a data configuration anomaly, the data configuration anomaly of the transaction event processing request is repaired, and the previous sub-processing link automatically initiates reprocessing and re-outputs the transaction event processing request. After the current sub-processing link receives the transaction event processing request, it re-performs an admission detection on the transaction event processing request to obtain the admission detection result.

[0101] If the checkpoint result of the transaction event processing request is a parameter configuration exception, the processing identifier configured in the parameter check program in the parameter configuration link is modified. After the modification is completed, the current sub-processing link re-performs an access check on the transaction event processing request to obtain the test result.

[0102] In an embodiment of the present application, the processing flow of a transaction event is divided into a plurality of sub-processing links for processing, and in each sub-processing link, an access check is first performed on the received processing request, so that the anomaly of the processing request of the transaction event can be located in a specific sub-processing link, and, when the access check result is a process interruption, the abnormal factors that cause the process interruption can be repaired, and after the abnormal factors are repaired, the process returns to execute the access check on the processing request of the transaction event to obtain the access check result, thereby achieving timely repair of process interruptions and improving the fault tolerance, maintainability and robustness of the transaction system; at the same time, the increasingly complex transaction system is modeled, standardized and formatted, thereby improving the processing efficiency of the transaction system and making the transaction system suitable for promotion and reuse.

[0103] In some embodiments, multiple sub-processing steps are executed asynchronously.

[0104] Specifically, when processing multiple transaction events, among multiple sub-processing links, after the previous sub-processing link completes processing of a received processing request for a transaction event, a new processing request is discovered to the next sub-processing link based on the processing result. At this time, the previous sub-processing link cannot wait for the next sub-processing link to process the new processing request, but immediately starts processing the next received processing request for a transaction event. Therefore, multiple sub-processing links are processed asynchronously to improve the processing efficiency of the transaction system.

[0105] In addition, each step in a sub-processing link is also executed asynchronously.

[0106] In order to better explain the embodiment of the present application, the following describes a transaction event processing method provided by the embodiment of the present application in combination with an abnormality check scenario of a processing request. The process of the method is as follows: Figure 1 The server execution shown includes the following steps: Figure 3 As shown:

[0107] Step 301, split the processing flow link for the transaction event into multiple sub-processing links.

[0108] Step 302, for each sub-processing link, execute the following steps 3021-3028 respectively.

[0109] Step 3021, receiving a processing request for a transaction event sent by the previous sub-processing link.

[0110] Step 3022, for the preset multiple checkpoints, perform the following operations respectively: use the check program corresponding to a checkpoint to detect the information of the processing request of the transaction event at the checkpoint, and obtain the corresponding checkpoint result.

[0111] Step 3023: If at least one checkpoint result is an abnormal result, the process is interrupted.

[0112] Step 3024, determine whether the abnormal factor causing the process interruption is a data configuration abnormality, if so, execute step 3025, otherwise execute step 3026.

[0113] Step 3025, return to the previous sub-processing link, modify the abnormal data items in the processing request of the transaction event, and return to execute step 3022.

[0114] Step 3026, determine whether the abnormal factor that causes the process interruption is a parameter configuration abnormality. If so, execute step 3027, otherwise execute step 3028.

[0115] Step 3027, return to the parameter configuration link, modify the processing identifier configured in the inspection program corresponding to the parameter checkpoint, and return to execute step 3022.

[0116] Step 3028, return to manual processing, return to execute step 3022.

[0117] In some embodiments, for each sub-processing step, refer to Figure 4 The current sub-processing link interacts with the previous sub-processing link and the next sub-processing link. Taking the current sub-processing link as an example, the sub-processing link includes an access module, an inspection module, an abnormality judgment module, a repair module, and an admission processing module. The modules contained in the sub-processing link are executed asynchronously.

[0118] The access module receives the processing request of the transaction event sent by the previous sub-processing link and records the information of the processing request; the inspection module contains an inspection program, and one inspection module can have multiple inspection programs, each inspection program corresponds to a checkpoint; when the inspection program detects each checkpoint of the processing request of the transaction event and generates a checkpoint result, the abnormal judgment module judges the abnormal factors according to the checkpoint result. If the checkpoint result is normal, there is no abnormal factor, so that the admission processing module performs admission processing on the processing request of the transaction event.

[0119] Specifically, for the data checkpoint, the check program corresponding to the data checkpoint is used to perform anomaly detection on multiple data items in the processing request of the transaction event; when there is at least one data item abnormality, the checkpoint result of the data checkpoint is that the data configuration is abnormal; when multiple data items are normal, the checkpoint result of the data checkpoint is that the data configuration is normal.

[0120] Specifically, for a parameter checkpoint, if the processing identifier configured in the check program corresponding to the parameter checkpoint is different from the processing identifier carried by the processing request, then the checkpoint result of the parameter checkpoint is a parameter configuration exception, where the processing identifier carried by the processing request is used to characterize the type of the processing request; if the processing identifier configured in the check program corresponding to the parameter checkpoint is the same as the processing identifier carried by the processing request, then the checkpoint result of the parameter checkpoint is a normal parameter configuration.

[0121] If the checkpoint result is abnormal, the abnormal factor is determined. If the abnormal factor is data configuration abnormality, the processing request of the current transaction event is sent to the repair module. The repair module returns the processing request of the transaction event to the previous sub-processing link, allowing the previous sub-processing link to modify the data configuration abnormality in the processing request and automatically re-initiate processing;

[0122] If the abnormal factor is a parameter configuration abnormality, the repair module returns the processing request of the transaction event to the parameter configuration module, modifies the processing identifier configured in the inspection program corresponding to the parameter checkpoint, and after the modification, the inspection program restarts the inspection of the processing request for the transaction event.

[0123] In the embodiment of the present application, each sub-processing link performs access detection before processing, which effectively improves the accuracy of the processing requests of transaction events; in each sub-processing link, an access detection is performed on the processing request of the previous link, and the abnormal factors are located as data configuration abnormalities and parameter configuration abnormalities according to the checkpoint results, and differentiated repairs are performed, and the processing requests are re-entered for access detection to ensure the accuracy of the processing requests of transaction events, while effectively improving the processing efficiency and continuity of the transaction system.

[0124] For example, refer to Figure 5The transaction event enters a large process processing link, which generates a processing identifier A for the transaction event. The processing identifier A indicates the type of the processing request for the transaction event, and makes any subsequent processing request for the transaction event issued by any sub-processing link carry the processing identifier A. The process processing link includes multiple sub-processing links.

[0125] Assuming that there is an error in the processing request for the transaction event sent by the first sub-processing link to the second sub-processing link, that is, there is an error in the processing result of the transaction event in the first sub-processing link, then in the second sub-processing link, the inspection program detects that there is a data configuration anomaly in the processing request, and returns the processing request for the transaction event to the first sub-processing link, allowing the first sub-processing link to modify the data configuration anomaly of the processing request and re-initiate the processing request for the transaction event to the second sub-processing link.

[0126] Assuming that in the third sub-processing link, the processing identifier in the check program is mismatched to B, then when the second sub-processing link sends a processing request for a transaction event to the third sub-processing link, the processing identifier B of the abnormally configured check program does not match the processing identifier A carried by the processing request for the transaction event, indicating that the type of processing request that the check program in the third sub-processing link can check does not match the type of processing request for the transaction event actually checked, causing a process interruption. Therefore, the abnormal factor of this process interruption can be located as a parameter configuration abnormality based on the checkpoint result. In the parameter configuration link, according to the parameter configuration rules, the parameters configured in the parameter check program of the third link are modified, and after the modification is completed, the processing request for the transaction event is re-performed with an access test to obtain the test results.

[0127] In the embodiment of the present application, the abnormal factors are located as data configuration anomalies and parameter configuration anomalies based on the checkpoint results, and differentiated repairs are performed, and the processing requests are re-entered into access detection to ensure the accuracy of the processing requests for transaction events. At the same time, the processing efficiency and continuity of the transaction system are effectively improved, and the breakpoint continuation of transaction events is achieved.

[0128] Based on the same technical concept, the embodiment of the present application provides a structural diagram of transaction event processing, such as Figure 6 As shown, the transaction event processing device 600 includes:

[0129] A decomposition module 601 is used to split the processing flow link for the transaction event into multiple sub-processing links;

[0130] The processing module 602 is used to perform the following operations for each sub-processing link: receiving a processing request for the transaction event sent by the previous sub-processing link; performing an admission detection on the processing request for the transaction event to obtain an admission detection result;

[0131] If the admission detection result is a process interruption, the abnormal factors causing the process interruption are repaired; and after the abnormal factors are repaired, the process returns to the step of performing an admission detection on the processing request of the transaction event to obtain the admission detection result.

[0132] Optionally, the processing module 602 is specifically configured to:

[0133] For the preset multiple checkpoints, the following operations are respectively performed: using a check program corresponding to a checkpoint, detecting the information of the processing request of the transaction event at the checkpoint, and obtaining a corresponding checkpoint result;

[0134] The admission detection result is determined based on the obtained multiple checkpoint results.

[0135] Optionally, the processing module 602 is specifically configured to:

[0136] If at least one of the multiple checkpoint results is an abnormal result, the admission detection result is a process interruption.

[0137] Optionally, the processing module 602 is specifically configured to:

[0138] Using the check program corresponding to the data checkpoint, respectively perform anomaly detection on multiple data items in the processing request of the transaction event;

[0139] When there is at least one data item abnormality, the checkpoint result of the data checkpoint is a data configuration abnormality;

[0140] When the multiple data items are all normal, the checkpoint result of the data checkpoint is that the data configuration is normal.

[0141] Optionally, the processing module 602 is specifically configured to:

[0142] If the processing identifier configured in the check program corresponding to the parameter checkpoint is different from the processing identifier carried by the processing request, the checkpoint result of the parameter checkpoint is a parameter configuration exception, wherein the processing identifier carried by the processing request is used to characterize the type of the processing request;

[0143] If the processing identifier of the check program configuration corresponding to the parameter checkpoint is the same as the processing identifier carried by the processing request, the checkpoint result of the parameter checkpoint is a parameter configuration exception.

[0144] Optionally, the processing module 602 is specifically configured to:

[0145] Return to the parameter configuration link and modify the processing identifier configured in the inspection program corresponding to the parameter checkpoint.

[0146] Optionally, the multiple sub-processing links are processed asynchronously.

[0147] In the embodiment of the present application, access detection is performed on the processing request of the previous link in each sub-processing link, which effectively improves the accuracy of the processing request of the transaction event; the anomalies are located as data configuration and parameter configuration anomalies, and differentiated repairs are performed, which effectively improves the processing efficiency and consistency of the transaction system.

[0148] In addition, the transaction event processing flow is divided into multiple sub-links, and processing requests for transaction events are handled separately, which improves the fault tolerance of the transaction system and enables the transaction system to quickly locate errors and repair them, thereby improving the maintainability and robustness of the transaction system; at the same time, the increasingly complex transaction system is modeled, standardized, and formatted, making the transaction system suitable for promotion and reuse.

[0149] Based on the same technical concept, the embodiment of the present application provides a computer device, which can be Figure 1 The server shown, such as Figure 7 As shown, it includes at least one processor 701 and a memory 702 connected to the at least one processor. The specific link medium between the processor 701 and the memory 702 is not limited in the embodiment of the present application. Figure 7 For example, the processor 701 and the memory 702 are connected via a bus. The bus can be divided into an address bus, a data bus, a control bus, etc.

[0150] In the embodiment of the present application, the memory 702 stores instructions executed by at least one processor 701, and the at least one processor 701 can execute the steps of the above-mentioned transaction event processing method by executing the instructions stored in the memory 702.

[0151] The processor 701 is the control center of the computer device, and can use various interfaces and lines to connect various parts of the computer device, and realize transaction event processing by running or executing instructions stored in the memory 702 and calling data stored in the memory 702. Optionally, the processor 701 may include one or more processing modules, and the processor 701 may integrate an application processor and a modem processor, wherein the application processor mainly processes the operating system, user interface, and application programs, and the modem processor mainly processes wireless communications. It is understandable that the above-mentioned modem processor may not be integrated into the processor 701. In some embodiments, the processor 701 and the memory 702 may be implemented on the same chip, and in some embodiments, they may also be implemented separately on independent chips.

[0152] Processor 701 can be a general-purpose processor, such as a central processing unit (CPU), a digital signal processor, an application-specific integrated circuit (ASIC), a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, and can implement or execute the various methods, steps and logic block diagrams disclosed in the embodiments of the present application. A general-purpose processor can be a microprocessor or any conventional processor, etc. The steps of the method disclosed in the embodiments of the present application can be directly embodied as a hardware processor for execution, or can be executed by a combination of hardware and software modules in the processor.

[0153] The memory 702 is a non-volatile computer-readable storage medium that can be used to store non-volatile software programs, non-volatile computer executable programs and modules. The memory 702 may include at least one type of storage medium, such as a flash memory, a hard disk, a multimedia card, a card-type memory, a random access memory (Random Access Memory, RAM), a static random access memory (Static Random Access Memory, SRAM), a programmable read-only memory (Programmable Read Only Memory, PROM), a read-only memory (Read Only Memory, ROM), an electrically erasable programmable read-only memory (Electrically Erasable Programmable Read-Only Memory, EEPROM), a magnetic memory, a disk, an optical disk, etc. The memory 702 is any other medium that can be used to carry or store a desired program code in the form of an instruction or data structure and can be accessed by a computer device, but is not limited thereto. The memory 702 in the embodiment of the present application can also be a circuit or any other device that can realize a storage function, for storing program instructions and / or data.

[0154] Based on the same inventive concept, an embodiment of the present application provides a computer-readable storage medium, which stores a computer program executable by a computer device. When the program runs on the computer device, the computer device executes the steps of the above-mentioned transaction event processing method.

[0155] Based on the same inventive concept, an embodiment of the present application provides a computer program product, including a computer program stored on a computer-readable storage medium, wherein the computer program includes program instructions, and when the program instructions are executed by a computer device, the computer device executes the steps of the above-mentioned transaction event processing method.

[0156] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that include computer-usable program code.

[0157] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0158] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0159] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process in the computer or other programmable device. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0160] Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.

Claims

1. A transaction event processing method, characterized in that: include: Split the transaction event processing process into multiple sub-processing steps; For each sub-processing step, perform the following operations: Receiving a processing request for the transaction event sent by a previous sub-processing link; Performing an access detection on the processing request of the transaction event to obtain an access detection result; If the admission detection result is a process interruption, repair the abnormal factors that caused the process interruption; After the abnormal factors are repaired, the process returns to the step of performing an access check on the processing request of the transaction event to obtain an access check result.

2. The method according to claim 1, characterized in that The performing an admission detection on the processing request of the transaction event and obtaining the admission detection result comprises: For the preset multiple checkpoints, the following operations are respectively performed: using a check program corresponding to a checkpoint, detecting the information of the processing request of the transaction event at the checkpoint, and obtaining a corresponding checkpoint result; The admission detection result is determined based on the obtained multiple checkpoint results.

3. The method according to claim 2, characterized in that The step of determining the admission detection result based on the obtained multiple checkpoint results includes: If at least one of the multiple checkpoint results is an abnormal result, the admission detection result is a process interruption.

4. The method according to claim 2, characterized in that If a checkpoint is a data checkpoint; using a check program corresponding to a checkpoint to detect the information of the processing request of the transaction event at the checkpoint to obtain a corresponding checkpoint result, including: Using the check program corresponding to the data checkpoint, respectively perform anomaly detection on multiple data items in the processing request of the transaction event; When there is at least one data item abnormality, the checkpoint result of the data checkpoint is a data configuration abnormality; When the multiple data items are all normal, the checkpoint result of the data checkpoint is that the data configuration is normal.

5. The method according to claim 4, characterized in that The abnormal factor is a data configuration abnormality; and repairing the abnormal factor that causes the process to be interrupted includes: Return to the previous sub-processing link and modify the abnormal data item in the processing request of the transaction event.

6. The method according to claim 2, characterized in that The parameter checkpoint of the one checkpoint; the use of a check program corresponding to the one checkpoint to detect the information of the processing request of the transaction event at the one checkpoint to obtain a corresponding checkpoint result, including: If the processing identifier configured in the check program corresponding to the parameter checkpoint is different from the processing identifier carried by the processing request, the checkpoint result of the parameter checkpoint is a parameter configuration exception, wherein the processing identifier carried by the processing request is used to characterize the type of the processing request; If the processing identifier of the check program configuration corresponding to the parameter checkpoint is the same as the processing identifier carried in the processing request, the checkpoint result of the parameter checkpoint is that the parameter configuration is normal.

7. The method according to claim 6, characterized in that The abnormal factor is a parameter configuration abnormality; and the repairing of the abnormal factor causing the process interruption includes: Return to the parameter configuration link and modify the processing identifier configured in the inspection program corresponding to the parameter checkpoint.

8. The method according to any one of claims 1 to 7, characterized in that: The multiple sub-processing links are executed asynchronously.

9. A device for processing transaction events, characterized in that: include: A decomposition module is used to split the processing flow of transaction events into multiple sub-processing links; The processing module is used to perform the following operations for each sub-processing link: receiving a processing request for the transaction event sent by the previous sub-processing link; performing an admission detection on the processing request for the transaction event to obtain an admission detection result; If the admission detection result is a process interruption, repair the abnormal factors that caused the process interruption; After the abnormal factors are repaired, the process returns to the step of performing an access check on the processing request of the transaction event to obtain an access check result.

10. A computer device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the program, the steps of any one of the methods of claims 1 to 8 are implemented.

11. A computer-readable storage medium, characterized in that: It stores a computer program executable by a computer device. When the program is run on the computer device, the computer device executes the steps of any method described in claims 1 to 8.

12. A computer program product, characterized in that The computer program product comprises a computer program stored on a computer-readable storage medium, wherein the computer program comprises program instructions, and when the program instructions are executed by a computer device, the computer device is caused to execute the steps of the method according to any one of claims 1 to 8.

Images