Batch accounting transaction checking method and device, storage medium and program product
By collecting and processing the original transaction number of batch transactions, summarizing and comparing the transaction number statistics, and triggering full-link data verification, the detection problem of transaction duplication and missed handling of abnormalities during batch accounting transaction processing is solved, and the abnormal detection timeliness and system stability is improved.
Patent Information
- Application Number
- CN202411560126.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-11-04
- Publication Date
- 2025-03-21
AI Technical Summary
In monitoring batch accounting transaction processing, it is difficult to verify whether there are transaction duplicate processing and missed processing exceptions by simply comparing transaction entrance and export data.
The original transaction number of each batch of transactions is collected, processed through predefined statistical formulas, summarized and compared the statistics of transactions, and triggered full-link data verification to detect abnormalities.
Improve the abnormal detection timeliness of the batch processing process, reduce the risk of abnormality, and enhance the stability and availability of the system.
Smart Images
Figure CN119671725A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of information processing technology, and in particular to a batch account transaction verification method, device, storage medium and program product. Background Art
[0002] The credit card clearing system is responsible for receiving credit card payment transaction clearing documents from various channels, performing transaction pre-inspection, transaction control, transaction interception, pre-entry processing, transaction splitting, conversion, holding account and other processing on transactions, and pushing them to the core system.
[0003] At present, the transaction processing flow of the entire system is based on the financial transaction cloud platform. In the process of batch transaction data processing, due to the long processing link, large transaction volume, complex processing logic, and many processing links in the transaction process, involving multiple business scenarios, there have been major changes from data entry to exit. The transaction data of each channel has certain changes after clearing batch processing, such as transaction splitting, transaction merging and conversion, etc. Often, a clearing transaction will generate multiple transactions or be converted into a new transaction after clearing batch processing.
[0004] Therefore, when monitoring the entire batch processing process, it is difficult to verify whether there are duplicate or missed transaction exceptions in the batch account transactions during the entire clearing system processing process by simply comparing the transaction entry and exit data.
[0005] The above contents are only used to assist in understanding the technical solution of the present application and do not constitute an admission that the above contents are prior art. Summary of the invention
[0006] The main purpose of this application is to provide a batch account transaction verification method, equipment, storage medium and program product, aiming to solve the technical problem that it is difficult to verify whether there are duplicate transaction processing and missed transaction processing exceptions in the entire clearing system processing process by simply comparing the transaction entry and exit data during the monitoring of the entire batch processing process.
[0007] To achieve the above purpose, the present application proposes a batch account transaction verification method, the method comprising:
[0008] Collect the original number of transactions submitted in each batch of transactions;
[0009] Processing the original transaction number by a predefined batch transaction number statistical formula to obtain a transaction number statistical result for each batch transaction;
[0010] The total transaction count of all batches of transactions in a processing node is obtained according to the pre-defined processing node formula;
[0011] Compare the total transaction number statistics result with the total transaction number system statistics result in the database, if the comparison results are consistent, execute the task of the next processing node, otherwise suspend or roll back the task of the current processing node;
[0012] When all processing nodes complete their tasks, full-link data verification is triggered according to the pre-defined verification formula.
[0013] In one embodiment, the step of collecting the original number of transactions submitted by each batch of transactions includes:
[0014] Define the triggering conditions for batch transaction submission and record the original transaction data submitted for each batch transaction;
[0015] When the batch transaction submission meets the triggering condition, the recorded original transaction data is submitted in batches to the database;
[0016] The number of original transactions submitted in the batch transaction is counted and stored in the specified data table or log file.
[0017] In one embodiment, the step of processing the original transaction count by using a predefined batch transaction count statistical formula to obtain a transaction count statistical result for each batch transaction includes:
[0018] Get the original transaction number data submitted for each batch of transactions;
[0019] Input the acquired raw transaction count data into a predefined batch transaction count statistical formula, and perform data processing according to the logic of the batch transaction count statistical formula;
[0020] According to the processing result of the batch transaction number statistical formula, the transaction number statistical result of each batch transaction is generated.
[0021] In one embodiment, the step of obtaining a total result of the number of transactions of all batches of transactions in a processing node according to a predefined processing node formula includes:
[0022] Get the transaction count statistics for each batch of transactions;
[0023] Input the transaction count statistics of each batch of transactions into the pre-defined processing node formula, calculate the total transaction count statistics of all batches for data aggregation;
[0024] According to the processing result of the processing node formula, a total statistical result of the number of transactions of all batches of transactions in the processing node is generated and stored in a specified data table or log file.
[0025] In one embodiment, the generating of the total transaction number statistics of all batch transactions in the processing node according to the processing result of the processing node formula and storing the statistics in a designated data table or log file includes:
[0026] The number of transactions in each batch of input transactions is tracked and counted independently, and the processing nodes are checked level by level, including internal and inter-node checks.
[0027] In one embodiment, the step of comparing the total transaction number statistics result with the total transaction number system statistics result in the database, and if the comparison results are consistent, executing the task of the next processing node, otherwise pausing or rolling back the task of the current processing node includes:
[0028] Obtain the total statistical results of the number of transactions of the current processing node and the total statistical results of the number of transactions stored in advance by the system;
[0029] Compare the total transaction number statistics generated by the current processing node with the pre-stored total transaction number system statistics to determine the comparison result;
[0030] If the comparison results are consistent, the task of the next processing node is started, otherwise the task of the current processing node is paused or rolled back.
[0031] In one embodiment, the step of triggering full-link data verification according to a predefined verification formula after all processing nodes complete their tasks includes:
[0032] Get predefined nuclear inspection formulas;
[0033] Collect full-link data from each processing node;
[0034] Input the full-link data into a predefined verification formula to perform data verification;
[0035] Generate a verification result of the full-link data based on the verification result of the verification formula.
[0036] In addition, to achieve the above-mentioned purpose, the present application also proposes a batch account transaction verification device, which includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, and the computer program is configured to implement the steps of the batch account transaction verification method described above.
[0037] In addition, to achieve the above-mentioned purpose, the present application also proposes a storage medium, which is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by the processor, the steps of the batch account transaction verification method described above are implemented.
[0038] In addition, to achieve the above-mentioned purpose, the present application also provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, the steps of the batch account transaction verification method described above are implemented.
[0039] One or more technical solutions proposed in this application have at least the following technical effects:
[0040] By collecting the original number of transactions submitted by each batch transaction; processing the original number of transactions through a pre-defined batch transaction transaction number statistical formula to obtain the transaction number statistical result of each batch transaction; summarizing the transaction number statistical result of all batch transactions in a processing node according to the pre-defined processing node formula; comparing the transaction number statistical total result with the transaction number system statistical total result in the database, if the comparison result is consistent, the task of the next processing node is executed, otherwise the task of the current processing node is paused or rolled back; when all processing nodes complete the task, the full-link data verification is triggered according to the pre-defined verification formula; simulating the batch data change process through the pre-defined formula solves the problem of repeated processing of transaction data and missed processing exception discovery in the batch processing of big data, greatly improves the timeliness of batch process anomaly detection, reduces the anomaly risk of batch transaction data processing, and enhances the stability and availability of the system. BRIEF DESCRIPTION OF THE DRAWINGS
[0041] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.
[0042] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.
[0043] Figure 1 A flowchart of the first embodiment of the batch account transaction verification method of this application;
[0044] Figure 2 A flow chart of the second embodiment of the batch account transaction verification method of this application;
[0045] Figure 3 A flowchart of the third embodiment of the batch account transaction verification method of this application;
[0046] Figure 4 A flowchart diagram of the fourth embodiment of the batch account transaction verification method of this application;
[0047] Figure 5 A flowchart diagram of the fifth embodiment of the batch account transaction verification method of this application;
[0048] Figure 6 A schematic diagram of a simplified process of a batch account transaction verification method provided in Example 6 of the present application;
[0049] Figure 7 A flowchart diagram of the seventh embodiment of the batch account transaction verification method of this application;
[0050] Figure 8 This is a schematic diagram of the module structure of the batch account transaction verification device of the embodiment of the present application;
[0051] Fig. 9 Schematic diagram of the device structure of the hardware operating environment involved in the batch account transaction verification method in the embodiment of the present application.
[0052] The purpose, features and advantages of this application will be further described in conjunction with the embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION
[0053] It should be understood that the specific embodiments described herein are only used to explain the technical solutions of the present application and are not used to limit the present application.
[0054] In order to better understand the technical solution of the present application, a detailed description will be given below in conjunction with the accompanying drawings and specific implementation methods.
[0055] In the process of batch transaction data processing, the existing technology has a long processing link, a large transaction volume, and complex processing logic. In addition, there are many processing links in the transaction processing process, involving multiple business scenarios, and there have been major changes from data entry to exit. The transaction data of various channels have certain changes after clearing batch processing, such as transaction splitting, transaction merging and conversion, etc. Often, a clearing transaction will generate multiple transactions or be converted into a new transaction after clearing batch processing. In the monitoring of the entire batch processing process, it is difficult to verify whether there are duplicate transactions and missed transactions in the batch account transactions during the entire clearing system processing process by simply comparing the transaction entry and exit data.
[0056] This application provides a solution by collecting the original number of transactions submitted by each batch of transactions;
[0057] The original number of transactions is processed by a predefined batch transaction transaction number statistical formula to obtain the transaction number statistical result of each batch transaction; the total transaction number statistical result of all batch transactions in a processing node is obtained according to the predefined processing node formula; the total transaction number statistical result is compared with the total transaction number system statistical result in the database. If the comparison result is consistent, the task of the next processing node is executed, otherwise the task of the current processing node is paused or rolled back; when all processing nodes have completed the task, the full-link data verification is triggered according to the predefined verification formula. Based on the present application scheme, the batch data change process is simulated by a predefined formula, which solves the problem of duplicate processing and missed processing of transaction data in the batch processing of big data, greatly improves the timeliness of batch process anomaly detection, reduces the anomaly risk of batch transaction data processing, and enhances the stability and availability of the system.
[0058] Based on this, the present application embodiment provides a batch account transaction verification method, referring to Figure 1 , Figure 1 This is a flow chart of the first embodiment of the batch account transaction verification method of the present application.
[0059] In this embodiment, the batch account transaction verification method includes steps S10 to S50:
[0060] Step S10: Collect the original number of transactions submitted in each batch of transactions.
[0061] It should be noted that the minimum verification unit is defined as a batch transaction, that is, the basic unit for processing the data submitted for each transaction.
[0062] Step S20: Processing the original transaction number by using a predefined batch transaction number statistical formula to obtain a transaction number statistical result for each batch transaction.
[0063] It should be noted that the predefined batch transaction number statistical formula is N c0 =∑±xn c0 , where x is the split-merge coefficient, n is the transaction count of a single batch of transactions, and c0 is the task number, which is used to identify unused clearing tasks. According to the statistical direction of the number of transactions, positive ones are counted in and negative ones are eliminated; data processing operations include splitting, merging, eliminating, supplementing, and converting transactions of a fixed number.
[0064] Step S30: The total transaction number statistics of all batches of transactions in a processing node are obtained according to a predefined processing node formula.
[0065] It should be noted that the predefined processing node formula is M p =f(Nc0 ...N cn ), where M p N is the total number of transactions in all batches of transactions in the pth processing node. cn The statistical result of the number of transactions in the nth batch of transactions; the processing node formula may include data processing logic such as summarizing, weighted averaging, maximum value, minimum value, etc. of the number of transactions in multiple batches of transactions.
[0066] Step S40: Compare the total statistical result of the number of transactions with the total statistical result of the number of transactions in the database. If the comparison result is consistent, execute the task of the next processing node, otherwise pause or roll back the task of the current processing node.
[0067] It should be noted that the total statistical results of the number of transactions can be cross-checked or compared to ensure consistency with the original batch data, wherein the cross-check can be carried out in the following ways: using different statistical methods or tools to calculate the number of transactions in the same batch and comparing whether the results are consistent; using different statistical methods or tools to calculate the number of transactions in the same batch and comparing whether the results are consistent; comparing the statistical results of different time periods to check whether the trend is reasonable and whether there are abnormal fluctuations. When the comparison results are inconsistent, exception handling should be triggered, such as recording error information and difference details, and deciding to correct or recalculate the data based on the analysis results; suspending the task of the current processing node to prevent data errors from further affecting subsequent processing, or deciding whether to roll back based on business needs to restore to the previous stable state.
[0068] Step S50: When all processing nodes complete their tasks, full-link data verification is triggered according to a predefined verification formula.
[0069] It should be noted that the predefined nuclear inspection formula is R PP ? =(N PP =f(M 00 ...M PP )), wherein said R PP is the pre-stored full-link statistical result, the N PP is the computing processing node M 00 To M PP The total statistical result of the number of transactions is obtained by the whole link statistical result, and the symbol "?=" is used to judge R PP With N PP The data are the same; the task status of each processing node is confirmed through the task status monitoring system or log records to ensure that the tasks of all processing nodes have been completed; each processing node collects full-link data, including the input data, processing results, output data, etc. of each node.
[0070] The present embodiment provides a batch account transaction verification method, which collects the original transaction number submitted by each batch transaction; processes the original transaction number through a pre-defined batch transaction transaction number statistical formula to obtain a transaction number statistical result for each batch transaction; summarizes the transaction number statistical total result of all batch transactions in a processing node according to a pre-defined processing node formula; compares the transaction number statistical total result with the transaction number system statistical total result in a database, and if the comparison result is consistent, executes the task of the next processing node, otherwise pauses or rolls back the task of the current processing node; when all processing nodes complete the task, triggers the full-link data verification according to the pre-defined verification formula; simulates the batch data change process through the pre-defined formula, solves the problem of repeated processing and missed processing of transaction data in the batch processing of big data, greatly improves the timeliness of batch process anomaly detection, reduces the anomaly risk of batch transaction data processing, and enhances the stability and availability of the system.
[0071] Further, refer to Figure 2 The second embodiment of the batch account transaction verification method of the present application provides a flow chart based on the above Figure 2 The embodiment shown further refines the "collecting the original number of transactions submitted by each batch of transactions" in step S10, including steps A201 to A203:
[0072] Step A201: define the triggering conditions for batch transaction submission and record the original transaction data submitted for each batch transaction.
[0073] It should be noted that the triggering condition for submitting the batch transaction can be based on a time period, such as every hour or every day, or by the number of transactions, such as every 100 or 300 transactions; the original transaction data includes transaction ID, transaction time, transaction amount, transaction type, etc.
[0074] Step A202: When the batch transaction submission meets the triggering condition, the recorded original transaction data is submitted in batches to the database.
[0075] Specifically, every time a new transaction occurs, it is checked whether the number of transactions currently recorded can reach the set threshold or whether the time period has been reached. When the trigger condition is met, the database submission interface is called to insert the original transaction data into the database in batches.
[0076] Step A203: Count the number of original transactions submitted in the batch transaction and store it in a specified data table or log file.
[0077] Specifically, assuming that the system is set to submit transaction data once an hour, such as "{transaction ID: 001, transaction time: 2024-01-01 09:00:00, transaction amount: 50.00, transaction type: recharge}", assuming that 123 transactions are recorded between 09:00 and 10:00, when it reaches 10:00, the timer or detects that the transaction record reaches or exceeds the predetermined threshold, it will trigger the batch submission process, and the system will batch insert the 123 transaction records in this time period into the database. After successful submission, the system will record the number of transactions submitted in this batch and write this information to the log file, including the submission time 09:00:00 to 10:00 and the number of 123 transactions. After the batch submission is completed, the system will clear the transaction record list for the next round of transaction records.
[0078] This embodiment defines the triggering conditions for batch transaction submission and records the original transaction data submitted by each batch transaction; when the batch transaction submission meets the triggering conditions, the recorded original transaction data is submitted in batches to the database; the number of original transactions submitted in the batch transaction is counted and stored in a specified data table or log file, thereby reducing the resource consumption of a single submission, improving data processing efficiency, ensuring data persistence and traceability, and enhancing system stability.
[0079] Further, refer to Figure 3 The third embodiment of the batch account transaction verification method of the present application provides a flow chart based on the above Figure 3 The embodiment shown further refines the step S20 of "processing the original transaction number by a predefined batch transaction number statistical formula to obtain a transaction number statistical result for each batch transaction", including steps A301 to A303:
[0080] Step A301: Obtain the original transaction number data submitted for each batch of transactions.
[0081] Step A302: input the acquired original transaction number data into a predefined batch transaction number statistical formula, and perform data processing according to the logic of the batch transaction number statistical formula.
[0082] It should be noted that the predefined batch transaction number statistical formula is N c0 =∑±xn c0 , where x is the split-merge coefficient, n is the transaction count of a single batch of transactions, and c0 is the task number, which is used to identify unused clearing tasks. According to the statistical direction of the number of transactions, positive ones are counted in and negative ones are eliminated; data processing operations include splitting, merging, eliminating, supplementing, and converting transactions of a fixed number.
[0083] Step A303: Generate a statistical result of the number of transactions for each batch of transactions based on the processing result of the statistical formula for the number of transactions in the batch.
[0084] It should be noted that a daily report on the number of transactions in each batch of transactions can be generated based on the processing results of the statistical formula, and stored in a specified data table or log file for subsequent query and analysis.
[0085] Specifically, the transaction data on January 1, 2024 is obtained from the database, including transaction ID, transaction time, transaction amount, transaction type, etc.; data example: {transaction ID: 123456; transaction time: 2024-01-01 10:00:00; transaction amount: 1,000 yuan; transaction type: transfer}; the pre-defined batch transaction transaction number statistical formula N is used c0 =∑±xn c0 The number of transactions is processed, wherein the transfer transaction weight may be recorded as 1.5, and the transfer transaction may be recorded as positive inclusion +. According to the processing result of the statistical formula, the statistical result of the number of transactions on January 1, 2024 is generated, and the statistical result of the number of transactions is stored in a specified data table or log file.
[0086] In this embodiment, the original number of transactions is accurately calculated and processed through a predefined batch transaction number statistical formula to ensure the accuracy of the statistical results. A unified statistical formula is used to process the number of transactions for all batch transactions to ensure consistency in the statistical results between different batches and avoid errors caused by different processing methods.
[0087] Further, refer to Figure 4 The fourth embodiment of the batch account transaction verification method of the present application provides a flow chart based on the above Figure 4 The embodiment shown further refines the "obtaining a total result of the number of transactions of all batches of transactions in a processing node according to a predefined processing node formula" in step S30, including steps A401 to A403:
[0088] Step A401: Obtain the transaction count statistics for each batch of transactions.
[0089] Step A402: Input the transaction count statistics of each batch of transactions into a predefined processing node formula, and calculate the total transaction count statistics of all batches for data aggregation.
[0090] It should be noted that the predefined processing node formula is M p =f(N c0 ...N cn ), where M pN is the total number of transactions in all batches of transactions in the pth processing node. cn This is the statistical result of the number of transactions in the nth batch of transactions.
[0091] Step A403: According to the processing result of the processing node formula, a total statistical result of the number of transactions of all batch transactions in the processing node is generated and stored in a specified data table or log file.
[0092] Specifically, assume that the statistical results of the number of transactions in each batch of transactions in the first processing node on January 1, 2024 are obtained from the database, such as batch 1: 100 transactions, batch 2: 160 transactions, batch 3: 120 transactions; the obtained statistical results of the number of transactions in each batch of transactions are input into the pre-defined processing node formula, that is, N1=100, N2=160, N3=120, and the total statistical result of the number of transactions of all batch transactions in the first processing node is obtained as M1=N1+N2+N3=380, and the calculated total statistical result of the number of transactions of all batch transactions in the first processing node is stored in the specified data table or log file. The storage content example is {processing node: 1; date: January 1, 2024; total statistical result of the number of transactions: 380 transactions}.
[0093] Further, the generating of the total statistical result of the number of transactions of all batches of transactions in the processing node according to the processing result of the processing node formula and storing it in a designated data table or log file includes:
[0094] The number of transactions in each batch of input transactions is tracked and counted independently, and the processing nodes are checked level by level, including internal and inter-node checks.
[0095] It should be noted that the independent tracking statistics is to record the detailed information of each transaction in each processing node, including timestamp, transaction type, amount, etc., and regularly summarize the number of transactions at each node to form independent statistical data; the internal node verification is to compare the independent statistical results of each node with the number of transactions calculated by the node to ensure that the data processing and statistical results within the node are correct; the inter-node verification is to summarize the statistical results of each node to the upper-level node after all nodes are completed. The upper-level node will compare the received results with its own statistical results to ensure data consistency.
[0096] Further, refer to Figure 5 The fifth embodiment of the batch account transaction verification method of the present application provides a flow chart based on the above Figure 5In the embodiment shown, the step S40 of "comparing the total statistical result of the number of transactions with the total statistical result of the number of transactions in the database, if the comparison results are consistent, executing the task of the next processing node, otherwise pausing or rolling back the task of the current processing node" is further refined, including steps A501 to A503:
[0097] Step A501: Obtain the total statistical result of the number of transactions of the current processing node and the total statistical result of the number of transactions stored in advance by the system.
[0098] Step A502: Compare the total statistical result of the number of transactions generated by the current processing node with the total statistical result of the number of transactions stored in advance by the system, and determine the comparison result.
[0099] Step A503: If the comparison results are consistent, the task of the next processing node is started; otherwise, the task of the current processing node is paused or rolled back.
[0100] Specifically, assuming that the total number of transactions pre-stored in the system statistics obtained from the database is 500, the total number of transactions generated by the current processing node is compared with the total number of transactions in the database, and the consistency is determined based on the comparison result. If the total number of transactions generated by the current processing node is also 500, that is, the comparison result is consistent, then the task of the next processing node is started, and the comparison time, comparison result and corresponding operation content can be recorded.
[0101] This embodiment can detect data inconsistencies in a timely manner by comparing the total statistical results of the number of transactions of the current processing node with the total statistical results of the number of transactions stored in advance, avoid system problems caused by data errors, and suspend or roll back the tasks of the current processing node when the comparison results are inconsistent, thereby reducing repeated processing and correction work caused by data errors and enhancing system stability.
[0102] In one embodiment, if Figure 6 As shown, it can be seen that the complete transaction processing flow consists of multiple processing nodes. After the transactions at processing nodes M1, M2 and M3 are completed, the system obtains node snapshots M1, M2 and M3 of each node according to the preset node formula, among which the node M1 obtained based on the transaction snapshot is compared and verified with the node snapshot M1 stored in Oracle.
[0103] Further, refer to Figure 7 The seventh embodiment of the batch account transaction verification method of the present application provides a flow chart based on the above Figure 7The embodiment shown further refines the step S50 of "when all processing nodes complete their tasks, triggering full-link data verification according to a predefined verification formula", including steps A601 to A604:
[0104] Step A601: Obtain a predefined verification formula.
[0105] It should be noted that the predefined nuclear inspection formula is R PP ? =(N PP =f(M 00 ...M PP )), wherein said R PP is the pre-stored full-link statistical result, the N PP The computing processing node M 00 To M PP The total statistical result of the number of transactions is obtained by the whole link statistical result, and the symbol "?=" is used to judge R PP With N PP are the data the same.
[0106] Step A602: Collect full-link data of each processing node.
[0107] It should be noted that the task status of each processing node is confirmed through the task status monitoring system or log records to ensure that the tasks of all processing nodes have been completed; each processing node collects full-link data, including the input data, processing results, output data, etc. of each node.
[0108] Step A603: Input the full-link data into a predefined verification formula to perform data verification.
[0109] Specifically, according to the requirements of the verification formula, the collected total statistical results of the number of transactions of each processing node are formatted and sorted, and the sorted data are input into the verification formula for calculation.
[0110] Step A604: Generate a verification result of the full-link data according to the verification result of the verification formula.
[0111] It should be noted that the inspection results should be checked to see whether they meet the expected standards and thresholds, and a detailed full-link data inspection report should be generated based on the inspection results, including inspection indicators, result analysis, abnormal situations and handling suggestions.
[0112] In the above embodiments, data anomalies can be discovered in a timely manner through the implementation of a monitoring and early warning mechanism, and the full-link data can be automatically processed through a pre-defined verification formula, thereby improving the timeliness of batch process anomaly detection and reducing the anomaly risk of batch transaction data processing.
[0113] In addition, this application also provides a batch account transaction verification device, please refer to Figure 8 , the batch account transaction verification device comprises:
[0114] The data collection module is used to collect the original transaction number submitted by each batch of transactions;
[0115] The data processing module processes the original transaction number through a predefined batch transaction number statistical formula to obtain a transaction number statistical result for each batch transaction;
[0116] The data aggregation module aggregates the transaction count of all batches of transactions in a processing node according to the processing node formula defined by the pre-defined verification formula;
[0117] The data comparison module is responsible for comparing the generated transaction count statistics with the system statistics in the database, and deciding whether to execute the task of the next processing node based on the comparison results;
[0118] The data verification module triggers full-link data verification according to the pre-defined verification formula when all processing nodes complete their tasks.
[0119] The batch account transaction verification device provided by the present application adopts the batch account transaction verification method in the above embodiment, which can solve the technical problems of batch account transaction verification. Compared with the prior art, the beneficial effects of the batch account transaction verification device provided by the present application are the same as the beneficial effects of the batch account transaction verification method provided by the above embodiment, and the other technical features in the batch account transaction verification device are the same as the features disclosed in the above embodiment method, which will not be repeated here.
[0120] In addition, the present application also provides a batch account transaction verification device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the batch account transaction verification method in the above-mentioned embodiment one.
[0121] Reference below Fig. 9, which shows a schematic diagram of the structure of a batch account transaction verification device suitable for implementing the embodiment of the present application. The batch account transaction verification device in the embodiment of the present application may include but is not limited to mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Descriptions), PMPs (Portable Media Players), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Figure 8 The batch account transaction verification device shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.
[0122] like Fig. 9 As shown, the batch account transaction verification device may include a processing device 1001 (such as a central processing unit, a graphics processing unit, etc.), which can perform various appropriate actions and processes according to the program stored in the read-only memory (ROM: Read Only Memory) 1002 or the program loaded from the storage device 1003 to the random access memory (RAM: Random Access Memory) 1004. In RAM1004, various programs and data required for the operation of the xxx device are also stored. The processing device 1001, ROM1002 and RAM1004 are connected to each other through a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Generally, the following systems can be connected to the I / O interface 1006: an input device 1007 including, for example, a touch screen, a touch pad, a keyboard, a mouse, an image sensor, a microphone, an accelerometer, a gyroscope, etc.; an output device 1008 including, for example, a liquid crystal display (LCD: Liquid Crystal Display), a speaker, a vibrator, etc.; a storage device 1003 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 1009. The communication device 1009 can allow the batch account transaction verification device to communicate wirelessly or wired with other devices to exchange data. Although the figure shows a batch account transaction verification device with various systems, it should be understood that it is not required to implement or have all the systems shown. More or fewer systems can be implemented or have alternatively.
[0123] In particular, according to the embodiments disclosed in the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present application include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication device, or installed from a storage device 1003, or installed from a ROM 1002. When the computer program is executed by the processing device 1001, the above-mentioned functions defined in the method of the embodiment disclosed in the present application are executed.
[0124] The batch account transaction verification device provided by the present application adopts the batch account transaction verification method in the above embodiment, which can solve the technical problems of batch account transaction verification. Compared with the prior art, the beneficial effects of the batch account transaction verification device provided by the present application are the same as the beneficial effects of the batch account transaction verification method provided by the above embodiment, and the other technical features in the batch account transaction verification device are the same as the features disclosed in the method of the previous embodiment, which will not be repeated here.
[0125] It should be understood that the various parts disclosed in this application can be implemented by hardware, software, firmware or a combination thereof. In the description of the above embodiments, specific features, structures, materials or characteristics can be combined in any one or more embodiments or examples in a suitable manner.
[0126] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.
[0127] In addition, the present application provides a computer-readable storage medium having computer-readable program instructions (ie, computer programs) stored thereon, the computer-readable program instructions being used to execute the batch account transaction verification method in the above-mentioned embodiment.
[0128] The computer-readable storage medium provided in the present application may be, for example, a USB flash drive, but is not limited to electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, systems or devices, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, system or device. The program code contained on the computer-readable storage medium may be transmitted using any appropriate medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination of the above.
[0129] The computer-readable storage medium may be included in the batch account transaction verification device; or may exist independently without being assembled into the batch account transaction verification device.
[0130] The computer-readable storage medium carries one or more programs. When the one or more programs are executed by the batch account transaction verification device, the batch account transaction verification device: collects the original number of transactions submitted by each batch transaction; processes the original number of transactions through a pre-defined batch transaction transaction number statistical formula to obtain a transaction number statistical result for each batch transaction; obtains a total transaction number statistical result for all batch transactions in a processing node according to a pre-defined processing node formula; compares the total transaction number statistical result with the total transaction number system statistical result in the database. If the comparison results are consistent, the task of the next processing node is executed, otherwise the task of the current processing node is suspended or rolled back; when all processing nodes complete their tasks, full-link data verification is triggered according to a pre-defined verification formula.
[0131] Computer program code for performing the operations of the present application may be written in one or more programming languages or a combination thereof, including object-oriented programming languages such as Java, Smalltalk, C++, and conventional procedural programming languages such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).
[0132] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present application. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.
[0133] The modules involved in the embodiments described in this application may be implemented by software or hardware, wherein the name of the module does not constitute a limitation on the unit itself in some cases.
[0134] The readable storage medium provided in this application is a computer-readable storage medium, which stores computer-readable program instructions (i.e., computer programs) for executing the above-mentioned batch account transaction verification method, and can solve the technical problems of batch account transaction verification. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided in this application are the same as the beneficial effects of the batch account transaction verification method provided in the above-mentioned embodiment, and will not be repeated here.
[0135] In addition, the present application also provides a computer program product, including a computer program, which implements the steps of the batch account transaction verification method as described above when executed by a processor.
[0136] The computer program product provided by this application can solve the technical problem of batch account transaction verification. Compared with the prior art, the beneficial effects of the computer program product provided by this application are the same as the beneficial effects of the batch account transaction verification method provided by the above embodiment, which will not be repeated here.
[0137] The above descriptions are only some embodiments of the present application, and are not intended to limit the patent scope of the present application. All equivalent structural changes made using the contents of the present application specification and drawings under the technical concept of the present application, or direct / indirect applications in other related technical fields are included in the patent protection scope of the present application.
Claims
1. A batch account transaction verification method, characterized in that: The method comprises: Collect the original number of transactions submitted in each batch of transactions; Processing the original transaction number by a predefined batch transaction number statistical formula to obtain a transaction number statistical result for each batch transaction; The total transaction count of all batches of transactions in a processing node is obtained according to the pre-defined processing node formula; Compare the total transaction number statistics result with the total transaction number system statistics result in the database, if the comparison results are consistent, execute the task of the next processing node, otherwise suspend or roll back the task of the current processing node; When all processing nodes complete their tasks, full-link data verification is triggered according to the pre-defined verification formula.
2. The method according to claim 1, characterized in that The step of collecting the original number of transactions submitted by each batch of transactions includes: Define the triggering conditions for batch transaction submission and record the original transaction data submitted for each batch transaction; When the batch transaction submission meets the triggering condition, the recorded original transaction data is submitted in batches to the database; The number of original transactions submitted in the batch transaction is counted and stored in the specified data table or log file.
3. The method according to claim 2, characterized in that The step of processing the original transaction number by using a predefined batch transaction number statistical formula to obtain a transaction number statistical result for each batch transaction includes: Get the original transaction number data submitted for each batch of transactions; Input the acquired raw transaction count data into a predefined batch transaction count statistical formula, and perform data processing according to the logic of the batch transaction count statistical formula; According to the processing result of the batch transaction number statistical formula, the transaction number statistical result of each batch transaction is generated.
4. The method according to claim 3, characterized in that The step of obtaining the total transaction number statistics of all batches of transactions in a processing node according to a predefined processing node formula includes: Get the transaction count statistics for each batch of transactions; Input the transaction count statistics of each batch of transactions into the pre-defined processing node formula, calculate the total transaction count statistics of all batches for data aggregation; According to the processing result of the processing node formula, a total statistical result of the number of transactions of all batches of transactions in the processing node is generated and stored in a specified data table or log file.
5. The method according to claim 4, characterized in that The step of generating a total statistical result of the number of transactions of all batches of transactions in the processing node according to the processing result of the processing node formula and storing the result in a designated data table or log file includes: The number of transactions in each batch of input transactions is tracked and counted independently, and the processing nodes are checked level by level, including internal and inter-node checks.
6. The method according to claim 5, characterized in that The step of comparing the total transaction number statistics result with the total transaction number system statistics result in the database, and if the comparison results are consistent, executing the task of the next processing node, otherwise pausing or rolling back the task of the current processing node includes: Obtain the total statistical results of the number of transactions of the current processing node and the total statistical results of the number of transactions stored in advance by the system; Compare the total transaction number statistics generated by the current processing node with the pre-stored total transaction number system statistics to determine the comparison result; If the comparison results are consistent, the task of the next processing node is started, otherwise the task of the current processing node is paused or rolled back.
7. The method according to claim 6, characterized in that The step of triggering full-link data verification according to a predefined verification formula after all processing nodes complete their tasks includes: Get predefined nuclear inspection formulas; Collect full-link data from each processing node; Input the full-link data into a predefined verification formula to perform data verification; Generate a verification result of the full-link data based on the verification result of the verification formula.
8. A batch account transaction verification device, characterized in that: The device comprises: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program is configured to implement the steps of the batch account transaction verification method according to any one of claims 1 to 7.
9. A storage medium, characterized in that: The storage medium is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, the steps of the batch account transaction verification method according to any one of claims 1 to 7 are implemented.
10. A computer program product, characterized in that The computer program product comprises a computer program, and when the computer program is executed by a processor, the steps of the batch account transaction verification method according to any one of claims 1 to 7 are implemented.