A transaction monitoring method, device, electronic device, and storage medium

Abstract

The present application discloses a transaction monitoring method, apparatus, electronic device, and storage medium. The method includes: obtaining transaction detail data of a target transaction type within a unit time length; calculating the current occurrence proportion and current occurrence frequency of each target return code based on the transaction detail data of the target transaction type; calculating the current proportion deviation of each target return code based on the current occurrence proportion of each target return code and its baseline proportion, and calculating the current frequency deviation of each target return code based on the current occurrence frequency of each target return code and its baseline frequency; respectively for each target return code, determining whether each current deviation of the target return code is not greater than the deviation threshold of the target return code corresponding to the target transaction type; where the current deviation includes the current proportion deviation and the current frequency deviation; if not all are not greater than the deviation threshold of the target return code corresponding to the target transaction type, feedback the warning information of the target return code.

Description

Technical Field

[0001] The present application relates to the technical field of system monitoring, and particularly relates to a transaction monitoring method, device, electronic device, and storage medium. Background Art

[0002] With the continuous development of business, the amount of transactions that enterprise application systems need to process data and provide external services is increasing, so the maintenance of application systems is becoming increasingly important.

[0003] In an enterprise, usually the personnel responsible for system operation and maintenance are different from those responsible for system R & D. Therefore, the operation and maintenance team cannot obtain the source program of the application, or cannot obtain all the source programs. Therefore, currently for system maintenance, mainly after a problem occurs in the system, data related to the problem is collected and provided to R & D personnel for analysis. The problems that occur are solved through the analyzed information, and these information can be used for operation and maintenance to facilitate faster identification of the problem next time.

[0004] However, due to the large number of potential unknown problems in the system, problems that have not occurred cannot be predicted in advance. Analyzing and fixing problems after they occur will greatly affect the normal processing of business. Summary of the Invention

[0005] Based on the above deficiencies of the prior art, the present application provides a transaction monitoring method, device, electronic device, and storage medium to solve the problem that the prior art affects the normal processing of business.

[0006] To achieve the above object, the present application provides the following technical solutions:

[0007] The first aspect of the present application provides a transaction monitoring method, including:

[0008] Obtaining transaction detail data of a target transaction type within a unit time length; wherein, the transaction detail data at least includes a return code of the transaction;

[0009] Based on the transaction detail data of the target transaction type within the unit time length, calculating the current occurrence ratio and the current occurrence frequency of each target return code;

[0010] Based on the current occurrence ratio of each target return code and the baseline ratio of each target return code, calculating the current ratio deviation of each target return code, and based on the current occurrence frequency of each target return code and the baseline frequency of each target return code, calculating the current frequency deviation of each target return code;

[0011] For each of the target return codes, determine whether each current deviation of the target return code is not greater than the deviation threshold of the target return code corresponding to the target transaction type; wherein, each current deviation of the target return code includes the current proportional deviation of the target return code and the current frequency deviation of the target return code;

[0012] If it is determined that each current deviation of the target return code is not not greater than the deviation threshold of the target return code corresponding to the target transaction type, then feedback the warning information of the target return code.

[0013] Optionally, in the above transaction monitoring method, calculating the current occurrence proportion and the current occurrence frequency of each target return code based on the transaction detail data of the target transaction type within the unit time length includes:

[0014] Based on the transaction detail data of the target transaction type within the unit time length, determine the number of occurrences of each target return code within the unit time length;

[0015] Respectively determine the number of occurrences of each target return code as the current occurrence frequency of the target return code;

[0016] Respectively calculate the number of occurrences of each target return code and the total transaction volume of the target transaction type with responses within the unit time length to obtain the current occurrence frequency of each target return code.

[0017] Optionally, in the above transaction monitoring method, calculating the current proportional deviation of each target return code based on the current occurrence proportion of each target return code and the baseline proportion of each target return code includes:

[0018] For each target return code, calculate the absolute value of the difference between the current occurrence proportion of the target return code and the baseline proportion of the target return code corresponding to the target transaction type to obtain the proportional difference of the target return code;

[0019] Divide the proportional difference of the target return code by the baseline proportion of the target return code corresponding to the target transaction type to obtain the current proportional deviation of the target return code.

[0020] Optionally, in the above transaction monitoring method, calculating the current frequency deviation of each target return code based on the current occurrence frequency of each target return code and the baseline frequency of each target return code includes:

[0021] For each of the target return codes, calculate the absolute value of the difference between the current occurrence frequency of the target return code and the baseline frequency of the target return code corresponding to the target transaction type, to obtain the frequency difference of the target return code;

[0022] Divide the frequency difference of the target return code by the baseline frequency of the target return code corresponding to the target transaction type, to obtain the current frequency deviation of the target return code.

[0023] Optionally, in the above transaction monitoring method, after determining whether each current deviation of the target return code is not greater than the deviation threshold of the target return code corresponding to the target transaction type for each of the target return codes, it further includes:

[0024] If it is determined that the current proportional deviation of the target return code is greater than the proportional deviation threshold of the target return code corresponding to the target transaction type, then weight the current proportional deviation of the target return code and the baseline proportion of the target return code, to obtain an updated value of the baseline proportion of the target return code;

[0025] Update the baseline proportion of the target return code by using the updated value of the baseline proportion of the target return code;

[0026] If it is determined that the current frequency deviation of the target return code is greater than the frequency deviation threshold of the target return code corresponding to the target transaction type, then weight the current frequency deviation of the target return code and the baseline frequency of the target return code, to obtain an updated value of the baseline frequency of the target return code;

[0027] Update the baseline frequency of the target return code by using the updated value of the baseline frequency of the target return code.

[0028] A second aspect of the present application provides a transaction monitoring device, including:

[0029] A data acquisition unit, configured to acquire transaction detail data of a target transaction type within a unit time length; wherein, the transaction detail data at least includes the return code of the transaction;

[0030] An index calculation unit, configured to calculate the current occurrence proportion and the current occurrence frequency of each target return code based on the transaction detail data of the target transaction type within the unit time length;

[0031] A proportional deviation calculation unit, configured to calculate the current proportional deviation of each target return code based on the current occurrence proportion of each target return code and the baseline proportion of each target return code;

[0032] A frequency deviation calculation unit, configured to calculate the current frequency deviation of each of the target return codes based on the current occurrence frequency of each of the target return codes and the baseline frequency of each of the target return codes;

[0033] A judgment unit, configured to respectively judge, for each of the target return codes, whether each of the current deviations of the target return code is not greater than the deviation threshold of the target return code corresponding to the target transaction type; wherein, each of the current deviations of the target return code includes the current ratio deviation of the target return code and the current frequency deviation of the target return code;

[0034] An alarm unit, configured to, when it is judged that each of the current deviations of the target return code is not not greater than the deviation threshold of the target return code corresponding to the target transaction type, feedback the alarm information of the target return code.

[0035] Optionally, in the above transaction monitoring device, the index calculation unit includes:

[0036] A statistics unit, configured to determine the occurrence times of each of the target return codes within the unit time length based on the transaction detail data of the target transaction type within the unit time length;

[0037] A frequency determination unit, configured to respectively determine the occurrence times of each of the target return codes as the current occurrence frequency of the target return code;

[0038] A ratio calculation unit, configured to respectively calculate the ratio of the occurrence times of each of the target return codes to the total transaction volume of the target transaction type with responses within the unit time length, to obtain the current occurrence frequency of each of the target return codes.

[0039] Optionally, in the above transaction monitoring device, the ratio deviation calculation unit includes:

[0040] A first calculation unit, configured to respectively calculate, for each of the target return codes, the absolute value of the difference between the current occurrence ratio of the target return code and the baseline ratio of the target return code corresponding to the target transaction type, to obtain the ratio difference of the target return code;

[0041] A second calculation unit, configured to divide the ratio difference of the target return code by the baseline ratio of the target return code corresponding to the target transaction type, to obtain the current ratio deviation of the target return code.

[0042] Optionally, in the above transaction monitoring device, the frequency deviation calculation unit includes:

[0043] A third calculation unit, configured to calculate, for each of the target return codes, an absolute value of a difference between the current occurrence frequency of the target return code and a baseline frequency of the target return code corresponding to the target transaction type, to obtain a frequency difference of the target return code;

[0044] A fourth calculation unit, configured to divide the frequency difference of the target return code by the baseline frequency of the target return code corresponding to the target transaction type, to obtain a current frequency deviation of the target return code.

[0045] Optionally, in the above transaction monitoring device, further included are:

[0046] A fifth calculation unit, configured to, when it is determined that a current ratio deviation of the target return code is greater than a ratio deviation threshold of the target return code corresponding to the target transaction type, perform weighting on the current ratio deviation of the target return code and a baseline ratio of the target return code, to obtain an updated value of the baseline ratio of the target return code;

[0047] A first update unit, configured to update the baseline ratio of the target return code by using the updated value of the baseline ratio of the target return code;

[0048] A sixth calculation unit, configured to, when it is determined that a current frequency deviation of the target return code is greater than a frequency deviation threshold of the target return code corresponding to the target transaction type, perform weighting on the current frequency deviation of the target return code and a baseline frequency of the target return code, to obtain an updated value of the baseline frequency of the target return code;

[0049] A second update unit, configured to update the baseline frequency of the target return code by using the updated value of the baseline frequency of the target return code.

[0050] A third aspect of the present application provides an electronic device, including:

[0051] A memory and a processor;

[0052] wherein, the memory is configured to store a program;

[0053] The processor is configured to execute the program, and when the program is executed, it is specifically configured to implement the transaction monitoring method as described in any one of the above.

[0054] A fourth aspect of the present application provides a computer storage medium, configured to store a computer program, and when the computer program is executed, it is configured to implement the transaction monitoring method as described in any one of the above.

[0055] The present application provides a transaction monitoring method, which obtains transaction detail data of a target transaction type within a unit time length. Among them, the transaction detail data at least includes the return code of the transaction. Then, based on the transaction detail data of the target transaction type within the unit time length, calculate the current occurrence ratio and the current occurrence frequency of each target return code, and based on the current occurrence ratio of each target return code and the baseline ratio of each target return code, calculate the current ratio deviation of each target return code, and based on the current occurrence frequency of each target return code and the baseline frequency of each target return code, calculate the current frequency deviation of each target return code. Then, for each target return code, determine whether each current deviation of the target return code is not greater than the deviation threshold of the target return code corresponding to the target transaction type. Among them, each current deviation of the target return code includes the current ratio deviation of the target return code and the current frequency deviation of the target return code; if it is determined that each current deviation of the target return code is not all not greater than the deviation threshold of the target return code corresponding to the target transaction type, it indicates that the return situation of the target return code is different from usual, indicating that the system may be abnormal. Therefore, feedback the alarm information of the target return code, so that an anomaly can be detected in advance before the problem occurs, and the anomaly can be processed in a timely manner, thereby avoiding problems from affecting the normal transaction processing of the system. Description of the Drawings

[0056] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings required for use in the description of the embodiments or the prior art. Obviously, the drawings in the following description are only the embodiments of the present application. For those of ordinary skill in the art, without creative efforts, other drawings can also be obtained according to the provided drawings.

[0057] Figure 1 It is a flowchart of a transaction monitoring method provided by an embodiment of the present application;

[0058] Figure 2 It is a flowchart of a method for calculating the current occurrence ratio and the current occurrence frequency provided by an embodiment of the present application;

[0059] Figure 3 It is a flowchart of a method for calculating the current ratio deviation provided by an embodiment of the present application;

[0060] Figure 4 It is a flowchart of a method for calculating the current frequency deviation provided by an embodiment of the present application;

[0061] Figure 5 It is a schematic diagram of the architecture of a transaction monitoring device provided by an embodiment of the present application;

[0062] Figure 6Schematic diagram of the architecture of an electronic device provided by an embodiment of the present application. Detailed implementation manners

[0063] Next, the technical solutions in the embodiments of the present application will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application.

[0064] In the present application, relational terms such as first and second are only used 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 "include", "comprise" or any other variant thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements not only includes those elements, but also includes other elements not expressly listed, or further includes elements inherent to such process, method, article or device. Without further limitation, an element defined by the statement "including one..." does not exclude the existence of additional identical elements in the process, method, article or device including the said element.

[0065] An embodiment of the present application provides a transaction monitoring method, as Figure 1 shown, which specifically includes the following steps:

[0066] S101. Obtain transaction detail data of a target transaction type within a unit time length.

[0067] Among them, the transaction detail data at least includes the return code of the transaction. Of course, the transaction detail data may also include transaction type, whether to respond, response time, whether to succeed, and other transaction and service fields that are meaningful for monitoring. However, the return code is mainly concerned in the embodiments of the present application. Therefore, the return code is obtained by obtaining the transaction detail data.

[0068] Since the characteristics of different transaction types are different, in the present application, the methods provided by the embodiments of the present application are respectively executed for each transaction type, so as to realize the monitoring of transactions of each transaction type. Therefore, the target transaction type refers to one of the monitored transaction types.

[0069] It should be noted that the transactions mentioned in the embodiments of the present application refer to data processing and operations of providing services externally by the application system. The client sends a request to the server to obtain a response, so as to complete specific data processing with business significance.

[0070] It should also be noted that the unit time length can be set according to specific requirements.

[0071] S102. Calculate the current occurrence ratio and current occurrence frequency of each target return code based on the transaction detail data of the target transaction type within the unit time length.

[0072] It should be noted that during the transaction processing, there are many types of return codes returned. However, the types of common return codes are relatively fixed. Therefore, when an exception occurs in the application system, some return codes that rarely appear in daily life usually appear, or the ratio of the return codes that often appear in daily life to the business volume changes significantly.

[0073] Therefore, in the embodiments of the present application, based on the transaction detail data of the target transaction type within the unit time length, calculate the current occurrence ratio and current occurrence frequency of each specific return code that appears within the unit time, so as to determine whether the system has an exception based on the current occurrence ratio and current occurrence frequency.

[0074] Among them, the target return code refers to a specific return code.

[0075] Optionally, in another embodiment of the present application, a specific implementation manner of step S102 is as Figure 2 shown, including:

[0076] S201. Determine the occurrence times of each target return code within the unit time length based on the transaction detail data of the target transaction type within the unit time length.

[0077] Specifically, since each transaction detail data includes a return code, the occurrence times of each target return code within the unit time can be counted based on the transaction detail data of the target transaction type within the unit time length.

[0078] S202. Respectively determine the occurrence times of each target return code as the current occurrence frequency of the target return code.

[0079] Since the occurrence times of the target return code within the unit time are counted, this occurrence here is the occurrence frequency of the target return code within the unit time length.

[0080] S203. Respectively calculate the ratio of the occurrence times of each target return code to the total transaction volume of the target transaction type with responses within the unit time length to obtain the current occurrence frequency of each target return code.

[0081] S103. Calculate the current ratio deviation of each target return code based on the current occurrence ratio of each target return code and the baseline ratio of each target return code, and calculate the current frequency deviation of each target return code based on the current occurrence frequency of each target return code and the baseline frequency of each target return code.

[0082] It should be noted that when the system has an exception, the current occurrence frequency and the current occurrence ratio of the target return code will be different from the usual values. Therefore, in order to determine that the current occurrence frequency and the current occurrence ratio of the target return code are different from the usual values. Therefore, in the embodiments of the present application, the baseline ratio and the baseline frequency are set in advance for the target transaction type, which are used for the ratio level and the frequency level under normal conditions.

[0083] Optionally, the baseline ratio and the baseline frequency can be set based on the average value of the occurrence ratios and the average value of the occurrence frequencies of each target transaction code in the transaction detail data of the target transaction type under historical normal conditions in advance, so as to set the ratio baseline and the frequency baseline corresponding to each target transaction code of the target transaction type. And the ratio baseline and the frequency baseline can be continuously updated.

[0084] Considering that the business is constantly changing, in the embodiments of the present application, a certain fluctuation in the occurrence ratio and the occurrence frequency is allowed. Therefore, in the embodiments of the present application, the current ratio deviation of each target return code is calculated based on the current occurrence ratio of each target return code and the baseline ratio of each target return code, and the current frequency deviation of each target return code is calculated based on the current occurrence frequency of each target return code and the baseline frequency of each target return code. Then, step S104 is executed based on the current ratio deviation and the current frequency deviation.

[0085] Specifically, as Figure 3 shown, a specific implementation manner of calculating the current ratio deviation of each target return code based on the current occurrence ratio of each target return code and the baseline ratio of each target return code includes:

[0086] S301. For each target return code, calculate the absolute value of the difference between the current occurrence ratio of the target return code and the baseline ratio of the target return code corresponding to the target transaction type, to obtain the ratio difference of the target return code.

[0087] S302. Divide the ratio difference of the target return code by the baseline ratio of the target return code corresponding to the target transaction type, to obtain the current ratio deviation of the target return code.

[0088] Similarly, as Figure 4As shown, a specific implementation for calculating the current frequency deviation of each target return code based on the current occurrence frequency of each target return code and the baseline frequency of each target return code includes:

[0089] S401. For each target return code, calculate the absolute value of the difference between the current occurrence frequency of the target return code and the baseline frequency of the target return code corresponding to the target transaction type, to obtain the frequency difference of the target return code.

[0090] S402. Divide the frequency difference of the target return code by the baseline frequency of the target return code corresponding to the target transaction type, to obtain the current frequency deviation of the target return code.

[0091] S104. For each target return code, determine whether each current deviation of the target return code is not greater than the deviation threshold of the target return code corresponding to the target transaction type.

[0092] If it is determined that not all current deviations of the target return code are not greater than the deviation threshold of the target return code corresponding to the target transaction type, that is, when it is determined that any one of the two current deviations of the target return code is greater than the deviation threshold of the target return code corresponding to the target transaction type, execute step S105 for the target return code.

[0093] It should be noted that since the characteristics of transactions of different transaction types are different, and the occurrence frequencies and occurrence ratios of different target return codes are also different, the deviation threshold of each target return code can be set for each transaction type respectively, so as to obtain the deviation threshold of each target return code corresponding to each target transaction type.

[0094] Among them, each current deviation of the target return code includes the current ratio deviation of the target return code and the current frequency deviation of the target return code.

[0095] It should be noted that for the current ratio deviation, its corresponding deviation threshold is the ratio deviation threshold. For the current frequency deviation, its corresponding deviation threshold is the frequency deviation threshold.

[0096] Therefore, step S401 is specifically: for each target return code, determine whether the current ratio deviation of the target return code is not greater than the ratio deviation threshold of the target return code corresponding to the target transaction type, and determine whether the current frequency deviation of the target return code is not greater than the frequency deviation threshold of the target return code corresponding to the target transaction type.

[0097] Optionally, in order to make the baseline more accurate and better reflect the current transaction execution environment, in another embodiment of the present application, the baseline will be updated after each execution of step S104. Specifically:

[0098] If it is determined that the current proportional deviation of the target return code is greater than the proportional deviation threshold of the target return code corresponding to the target transaction type, then the current proportional deviation of the target return code and the baseline proportion of the target return code are weighted to obtain an updated value of the baseline proportion of the target return code, and the baseline proportion of the target return code is updated using the updated value of the baseline proportion of the target return code.

[0099] If it is determined that the current frequency deviation of the target return code is greater than the frequency deviation threshold of the target return code corresponding to the target transaction type, then the current frequency deviation of the target return code and the baseline frequency of the target return code are weighted to obtain an updated value of the baseline frequency of the target return code, and the baseline frequency of the target return code is updated using the updated value of the baseline frequency of the target return code.

[0100] Optionally, the specific weighted calculation may be the product of the original baseline value multiplied by 90% plus the product of the current deviation value multiplied by 10% to obtain an updated value of the baseline. Then, the updated value is used to replace the original baseline value.

[0101] S105. Feed back the warning information of the target return code.

[0102] Optionally, the warning information may include the target return code, the current occurrence proportion and the current occurrence frequency of the target return code, and the transaction volume of the target return code, etc.

[0103] The embodiment of the present application provides a transaction monitoring method, which obtains transaction detail data of a target transaction type within a unit time length. Among them, the transaction detail data at least includes the return code of the transaction. Then, based on the transaction detail data of the target transaction type within the unit time length, the current occurrence proportion and the current occurrence frequency of each target return code are calculated, and based on the current occurrence proportion of each target return code and the baseline proportion of each target return code, the current proportional deviation of each target return code is calculated, and based on the current occurrence frequency of each target return code and the baseline frequency of each target return code, the current frequency deviation of each target return code is calculated. Then, for each target return code, it is determined whether each current deviation of the target return code is not greater than the deviation threshold of the target return code corresponding to the target transaction type. Among them, each current deviation of the target return code includes the current proportional deviation of the target return code and the current frequency deviation of the target return code. If it is determined that each current deviation of the target return code is not all not greater than the deviation threshold of the target return code corresponding to the target transaction type, it indicates that the return situation of the target return code is different from usual, indicating that the system may be abnormal. Therefore, the warning information of the target return code is fed back, so that the operation and maintenance personnel can be informed in advance before the problem occurs and can be processed in time, thereby avoiding problems from affecting the normal transaction processing of the system.

[0104] Another embodiment of the present application provides a transaction monitoring device, as Figure 5 shown, including:

[0105] A data acquisition unit 501, configured to acquire transaction detail data of a target transaction type within a unit time length.

[0106] Among them, the transaction detail data at least includes a return code of the transaction.

[0107] An index calculation unit 502, configured to calculate the current occurrence ratio and the current occurrence frequency of each target return code based on the transaction detail data of the target transaction type within a unit time length.

[0108] A ratio deviation calculation unit 503, configured to calculate the current ratio deviation of each target return code based on the current occurrence ratio of each target return code and the baseline ratio of each target return code.

[0109] A frequency deviation calculation unit 504, configured to calculate the current frequency deviation of each target return code based on the current occurrence frequency of each target return code and the baseline frequency of each target return code.

[0110] A judgment unit 505, configured to respectively determine, for each target return code, whether each current deviation of the target return code is not greater than the deviation threshold of the target return code corresponding to the target transaction type.

[0111] Among them, each current deviation of the target return code includes the current ratio deviation of the target return code and the current frequency deviation of the target return code.

[0112] An alarm unit 506, configured to feedback the alarm information of the target return code when it is determined that each current deviation of the target return code is not all not greater than the deviation threshold of the target return code corresponding to the target transaction type.

[0113] Optionally, in the transaction monitoring device provided by another embodiment of the present application, the index calculation unit includes:

[0114] A statistics unit, configured to determine the occurrence times of each target return code within a unit time length based on the transaction detail data of the target transaction type within a unit time length.

[0115] A frequency determination unit, configured to respectively determine the occurrence times of each target return code as the current occurrence frequency of the target return code.

[0116] A ratio calculation unit, configured to respectively calculate the occurrence times of each target return code and the total transaction volume of the target transaction type with responses within a unit time length to obtain the current occurrence frequency of each target return code.

[0117] Optionally, in the transaction monitoring device provided in another embodiment of the present application, the ratio deviation calculation unit includes:

[0118] A first calculation unit, configured to calculate, for each target return code, the absolute value of the difference between the current occurrence ratio of the target return code and the baseline ratio of the target return code corresponding to the target transaction type, to obtain the ratio difference of the target return code.

[0119] A second calculation unit, configured to divide the ratio difference of the target return code by the baseline ratio of the target return code corresponding to the target transaction type, to obtain the current ratio deviation of the target return code.

[0120] Optionally, in the above transaction monitoring device, the frequency deviation calculation unit includes:

[0121] A third calculation unit, configured to calculate, for each target return code, the absolute value of the difference between the current occurrence frequency of the target return code and the baseline frequency of the target return code corresponding to the target transaction type, to obtain the frequency difference of the target return code.

[0122] A fourth calculation unit, configured to divide the frequency difference of the target return code by the baseline frequency of the target return code corresponding to the target transaction type, to obtain the current frequency deviation of the target return code.

[0123] Optionally, the transaction monitoring device provided in another embodiment of the present application further includes:

[0124] A fifth calculation unit, configured to, when it is determined that the current ratio deviation of the target return code is greater than the ratio deviation threshold of the target return code corresponding to the target transaction type, perform weighting on the current ratio deviation of the target return code and the baseline ratio of the target return code, to obtain an updated value of the baseline ratio of the target return code.

[0125] A first update unit, configured to update the baseline ratio of the target return code by using the updated value of the baseline ratio of the target return code.

[0126] A sixth calculation unit, configured to, when it is determined that the current frequency deviation of the target return code is greater than the frequency deviation threshold of the target return code corresponding to the target transaction type, perform weighting on the current frequency deviation of the target return code and the baseline frequency of the target return code, to obtain an updated value of the baseline frequency of the target return code.

[0127] A second update unit, configured to update the baseline frequency of the target return code by using the updated value of the baseline frequency of the target return code.

[0128] It should be noted that for the specific working processes of the respective units provided in the above embodiments of the present application, reference may be made correspondingly to the corresponding steps in the above method embodiments, which will not be elaborated herein.

[0129] Another embodiment of the present application provides an electronic device, such as Figure 6 shown, including:

[0130] a memory 601 and a processor 602.

[0131] Among them, the memory 601 is used to store programs.

[0132] The processor 602 is used to execute the programs stored in the memory 601. When the programs are executed, they are specifically used to implement the transaction monitoring method provided in any of the above embodiments.

[0133] Another embodiment of the present application provides a computer storage medium for storing a computer program, which is used to implement the transaction monitoring method as described above when the computer program is executed.

[0134] The computer storage medium includes permanent and non-permanent, removable and non-removable media, and information storage can be implemented by any method or technology. The information can be computer-readable instructions, data structures, program modules, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory, or other memory technologies, compact disc read-only memory (CD-ROM), digital versatile disc (DVD), or other optical storage, magnetic cassette tapes, magnetic disk storage, or other magnetic storage devices, or any other non-transmission medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media do not include transitory media, such as modulated data signals and carrier waves.

[0135] Those skilled in the art can further realize that the units and algorithm steps of each example described in combination with the embodiments disclosed herein can be implemented by electronic hardware, computer software, or a combination of the two. To clearly illustrate the interchangeability of hardware and software, the components and steps of each example have been generally described according to functions in the above description. Whether these functions are executed in a hardware or software manner depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present application.

[0136] The foregoing description of the disclosed embodiments enables those skilled in the art to implement or use the present application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein can be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application will not be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A transaction monitoring method, characterized in that, Including: Obtain transaction detail data of the target transaction type within a unit time length; wherein, the transaction detail data at least includes a return code of the transaction; Based on the transaction detail data of the target transaction type within the unit time length, calculate the current occurrence proportion and the current occurrence frequency of each target return code; Based on the current occurrence proportion of each target return code and the baseline proportion of each target return code, calculate the current proportion deviation of each target return code, and based on the current occurrence frequency of each target return code and the baseline frequency of each target return code, calculate the current frequency deviation of each target return code; For each target return code, determine whether each current deviation of the target return code is not greater than the deviation threshold of the target return code corresponding to the target transaction type; wherein, each current deviation of the target return code includes the current proportion deviation of the target return code and the current frequency deviation of the target return code; If it is determined that each current deviation of the target return code is not all not greater than the deviation threshold of the target return code corresponding to the target transaction type, then feedback the alarm information of the target return code; If it is determined that the current proportion deviation of the target return code is greater than the proportion deviation threshold of the target return code corresponding to the target transaction type, then weight the current proportion deviation of the target return code and the baseline proportion of the target return code to obtain an updated value of the baseline proportion of the target return code; Use the updated value of the baseline proportion of the target return code to update the baseline proportion of the target return code; If it is determined that the current frequency deviation of the target return code is greater than the frequency deviation threshold of the target return code corresponding to the target transaction type, then weight the current frequency deviation of the target return code and the baseline frequency of the target return code to obtain an updated value of the baseline frequency of the target return code; Use the updated value of the baseline frequency of the target return code to update the baseline frequency of the target return code.

2. The method according to claim 1, wherein The calculating the current occurrence proportion and the current occurrence frequency of each target return code based on the transaction detail data of the target transaction type within the unit time length includes: Based on the transaction detail data of the target transaction type within the unit time length, determine the occurrence times of each target return code within the unit time length; Respectively determine the occurrence times of each target return code as the current occurrence frequency of the target return code; Respectively calculate the ratio of the occurrence times of each target return code to the total transaction volume of the target transaction type with responses within the unit time length to obtain the current occurrence frequency of each target return code.

3. The method according to claim 1, characterized in that The calculating the current proportion deviation of each target return code based on the current occurrence proportion of each target return code and the baseline proportion of each target return code includes: For each of the target return codes, calculate the absolute value of the difference between the current occurrence ratio of the target return code and the baseline ratio of the target return code corresponding to the target transaction type, to obtain the ratio difference of the target return code; Divide the ratio difference of the target return code by the baseline ratio of the target return code corresponding to the target transaction type, to obtain the current ratio deviation of the target return code.

4. The method according to claim 1, wherein The calculating the current frequency deviation of each target return code based on the current occurrence frequency of each target return code and the baseline frequency of each target return code includes: For each of the target return codes, calculate the absolute value of the difference between the current occurrence frequency of the target return code and the baseline frequency of the target return code corresponding to the target transaction type, to obtain the frequency difference of the target return code; Divide the frequency difference of the target return code by the baseline frequency of the target return code corresponding to the target transaction type, to obtain the current frequency deviation of the target return code.

5. A transaction monitoring device, characterized in that, including: A data acquisition unit, configured to acquire transaction detail data of a target transaction type within a unit time length; wherein, the transaction detail data at least includes the return code of the transaction; An index calculation unit, configured to calculate the current occurrence ratio and the current occurrence frequency of each target return code based on the transaction detail data of the target transaction type within the unit time length; A ratio deviation calculation unit, configured to calculate the current ratio deviation of each target return code based on the current occurrence ratio of each target return code and the baseline ratio of each target return code; A frequency deviation calculation unit, configured to calculate the current frequency deviation of each target return code based on the current occurrence frequency of each target return code and the baseline frequency of each target return code; A judgment unit, configured to respectively for each target return code, judge whether each current deviation of the target return code is not greater than the deviation threshold of the target return code corresponding to the target transaction type; wherein, each current deviation of the target return code includes the current ratio deviation of the target return code and the current frequency deviation of the target return code; An alarm unit, configured to, when it is judged that each current deviation of the target return code is not all not greater than the deviation threshold of the target return code corresponding to the target transaction type, feedback the alarm information of the target return code; A fifth calculation unit, configured to, when it is judged that the current ratio deviation of the target return code is greater than the ratio deviation threshold of the target return code corresponding to the target transaction type, perform weighting on the current ratio deviation of the target return code and the baseline ratio of the target return code, to obtain an updated value of the baseline ratio of the target return code; A first update unit, configured to update the baseline ratio of the target return code by using the updated value of the baseline ratio of the target return code; A sixth computing unit, configured to, when it is determined that the current frequency deviation of the target return code is greater than the frequency deviation threshold of the target return code corresponding to the target transaction type, weight the current frequency deviation of the target return code and the baseline frequency of the target return code to obtain an updated value of the baseline frequency of the target return code; A second updating unit, configured to update the baseline frequency of the target return code by using the updated value of the baseline frequency of the target return code.

6. The device according to claim 5, characterized in that, The metric calculation unit includes: A statistics unit, configured to determine the occurrence times of each target return code within the unit time length based on the transaction detail data of the target transaction type within the unit time length; A frequency determination unit, configured to respectively determine the occurrence times of each target return code as the current occurrence frequency of the target return code; A ratio calculation unit, configured to respectively calculate the ratio of the occurrence times of each target return code to the total transaction volume of the target transaction type with responses within the unit time length to obtain the current occurrence frequency of each target return code.

7. The device according to claim 5, characterized in that, The ratio deviation calculation unit includes: A first calculation unit, configured to respectively calculate, for each target return code, the absolute value of the difference between the current occurrence ratio of the target return code and the baseline ratio of the target return code corresponding to the target transaction type to obtain the ratio difference of the target return code; A second calculation unit, configured to divide the ratio difference of the target return code by the baseline ratio of the target return code corresponding to the target transaction type to obtain the current ratio deviation of the target return code.

8. An electronic device, characterized in that, It includes: A memory and a processor; Wherein, the memory is used to store a program; The processor is used to execute the program, and when the program is executed, it is specifically used to implement the transaction monitoring method according to any one of claims 1 to 4.

9. A computer storage medium, characterized in that, For storing a computer program, which is used to implement the transaction monitoring method according to any one of claims 1 to 4 when the computer program is executed.

Images