Data consistency verification method, device and system

Abstract

The present application discloses a data consistency verification method, device and system. The method includes: receiving information flows of multiple business systems through a business interface system; verifying the consistency of the amount and status of the capital chain based on the information flow; triggering a rule system to generate an alarm notification of a corresponding level according to the verification result; and pushing the alarm notification to the corresponding business owner through an early warning system. The present application solves the technical problem that data consistency cannot be detected in related technologies.

Description

Technical Field

[0001] The present application relates to the field of Internet finance, and more specifically, to a method, device and system for verifying data consistency. Background Art

[0002] In the era of financial technology, the payment business scenarios and architecture of payment companies are basically based on distributed large-scale clustering to solve high-concurrency access and transaction responsiveness. In the payment link of the core payment system, there are four core systems: gateway system, cash register, bank channel, and fund account system. In order to support high concurrency, each system is independent and each system handles its own fund-based information flow.

[0003] When this technical solution is used, it is very easy for inconsistent funds, inconsistent data, and inconsistent status to occur when the system funds are calculated according to a time period (such as every month). Therefore, there is an urgent need for a method to effectively verify the funds and status of each business system to solve the problem of poor consistency in the system's funds and status.

[0004] To address the above-mentioned problems, no effective solution has been proposed yet. Summary of the invention

[0005] The embodiments of the present application provide a method, device and system for verifying data consistency, so as to at least solve the technical problem that data consistency cannot be detected in the related art.

[0006] According to one aspect of an embodiment of the present application, a system consistency verification system is provided, including: a funds security system, which is used to verify the data consistency between multiple business systems; a business interface system, which is communicated with the funds security system and multiple business systems, and is used to provide docking solutions and interface packaging services to multiple business systems; a rule system, which is communicated with the funds security system, and is used to trigger corresponding alarm notifications according to the verification results of the funds security system; an early warning system, which is communicated with the rule system and the funds security system, and is used to push alarm notifications to the business owner.

[0007] According to another aspect of an embodiment of the present application, a method for verifying data consistency is also provided, including: receiving information flows of multiple business systems through a business interface system; performing consistency verification of the amount and status of the capital chain based on the information flow; triggering a rule system to generate an alarm notification of a corresponding level based on the verification result; and pushing the alarm notification to the corresponding business attribution party through an early warning system.

[0008] According to another aspect of an embodiment of the present application, a data consistency verification device is also provided, including: a receiving unit, used to receive information flows of multiple business systems through a business interface system; a verification unit, used to perform consistency verification of the amount and status of the capital chain based on the information flow; an alarm unit, used to trigger a rule system to generate an alarm notification of a corresponding level according to the verification result; and a push unit, used to push the alarm notification to the corresponding business attribution party through an early warning system.

[0009] According to another aspect of an embodiment of the present application, a storage medium is further provided, which includes a stored program, and the above method is executed when the program is run.

[0010] According to another aspect of an embodiment of the present application, an electronic device is further provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the above method through the computer program.

[0011] In the system consistency verification solution of the present application, the data is pushed to the fund security system by connecting the business system to the fund security system message queue. The fund security system makes timely warnings and responses based on the information flow and quickly locates problems. Compared with each business system performing its own fund accounting, production efficiency has been effectively improved, making it an effective fund security prevention strategy that can solve the technical problem that related technologies cannot detect data consistency. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0013] Figure 1 is a schematic diagram of a data consistency verification system according to an embodiment of the present application;

[0014] Figure 2 is a flow chart of an optional data consistency verification method according to an embodiment of the present application;

[0015] Figure 3 is a schematic diagram of an optional data consistency verification solution according to an embodiment of the present application;

[0016] Figure 4 is a schematic diagram of an optional data link content according to an embodiment of the present application;

[0017] Figure 5 is a schematic diagram of an optional data consistency verification device according to an embodiment of the present application; and,

[0018] Figure 6It is a structural block diagram of a terminal according to an embodiment of the present application. DETAILED DESCRIPTION

[0019] In order to enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of this application.

[0020] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0021] First, some nouns or terms that appear in the description of the embodiments of the present application are subject to the following interpretation:

[0022] JMS, the Java Message Service (JMS) application program interface, is an API for message-oriented middleware (MOM) in the Java platform. It is used to send messages between two applications or in a distributed system for asynchronous communication.

[0023] Wrapper class, Java provides two type systems, basic types and reference types. The use of basic types is efficiency. However, when you want to use APIs or new features designed only for objects (such as generics), the data of basic data types needs to be wrapped in wrapper classes.

[0024] The business process in the related technology is a serial mode, which is initiated by the business system and then passes through the gateway, cashier counter, bank channel and other systems in sequence. In this mode, each system is independent of each other, there is no verification based on information flow between systems, and the consistency of the system cannot be verified at all, which easily leads to inconsistent status, inconsistent amount and inconsistent data between systems.

[0025] For example, the financial risks that may occur when acquiring transactions include: duplicate entries, where an order is successfully paid but entered into the account multiple times; over-entry, where the amount entered into the account for the customer is greater than the amount successfully paid; wrong entry: customer A's funds are entered into the account for customer B; duplicate refunds: when a transaction is refunded, the merchant account balance is deducted once but the cardholder is refunded multiple times; refund without deduction: the merchant account balance is not deducted once when a transaction is refunded but the cardholder is refunded multiple times; missed entry: the order payment is successful but the account is not entered into the account for the customer; under-entry: the amount entered into the account for the customer is less than the amount successfully paid; wrong refund: the refund for cardholder A is returned to cardholder B; failed refund but funds are not refunded: the amount entered into the account for the customer is less than the amount successfully paid.

[0026] The financial risks that may occur when making withdrawals include: repeated withdrawals: the merchant account balance is deducted once but the customer is paid multiple times; over-withdrawals: the amount paid to the customer is greater than the amount deducted from the account; erroneous withdrawals: the amount that should be paid to customer A is paid to customer B; repeated returns of failed payments: the funds of a failed transaction are returned to the merchant account multiple times; withdrawals without deductions: the customer account balance is not deducted but the cardholder is refunded multiple times; successful deductions but no payments: the merchant account balance is deducted but no payments are made to the customer; under-withdrawals: the amount paid to the customer is less than the amount deducted from the account.

[0027] In view of the above problems, according to one aspect of the embodiment of the present application, an embodiment of a data consistency verification system (or fund security engine) is provided. In this solution, it mainly includes four parts: fund security system, business interface system, rule system and early warning system.

[0028] Fund security system: The fund security system is a security system for processing fund transactions. It is used to ensure the correctness of bilateral transactions in the system and verify whether there are unilateral errors.

[0029] The main business scenarios include: 1. Business warning on whether the business status of business system orders and the business status of capital accounts are consistent; 2. Business warning on whether the order amount of the business system and the amount of account changes in the capital account are consistent; 3. Statistical verification on whether the transaction quantity of the business system and the data of the capital security system are consistent (T+1 verification, that is, the data of the day will be verified on the next day).

[0030] Its technical features include: 1. It is loosely coupled with the business system, and the business system does not need to report data through the facade interface; 2. The business interface is highly adaptable and can be connected by relying on the basic core and message queue; 3. The system provides a T+1 data verification method, which can verify the correctness of the data with the business system again; 4. The system processing engine adopts the data tagging mode, and the business data table has high data processing performance; the data adopts the T+2 mode to regularly transfer the information collection table data to the historical table to ensure the working efficiency of the pre-processing engine.

[0031] Business interface system: provides docking strategies (i.e. docking solutions) and packaging services for various business systems, making docking of various business systems simple. There is no need to pay attention to the implementation of the code, only simple configuration is required.

[0032] Rule system: defines the system rules and alarm response levels, and triggers corresponding response strategies based on the response levels.

[0033] Early warning system: The early warning system provides alarm recipient configuration, which can set the response alarm group and recipient. The alarm is sent to the relevant business person according to the business platform. The business personnel receive the alarm information and perform the corresponding business processing.

[0034] The link between the business system and the fund security system is: the business system includes the gateway, cash register, bank channel, and fund account system. The four business systems push messages through the JMS messages of the business interface system and the fund security system. When the order based on the information flow flows through the above four business systems, the corresponding message is triggered to the fund security system. After receiving the message from the above four business systems, the fund security system verifies the amount and status based on the fund chain. If the verification passes, the information is delivered. If the verification fails, the rule system rules are triggered. The rule system pushes the corresponding level of alarm to the early warning system and sends it to the business owner.

[0035] The link between the business system and the business interface system is: the business interface system provides a simple packaging service interface to facilitate the business system to connect to the gateway, cash register, bank channel, and capital account.

[0036] The link between the fund security system and the rule system is: when processing the account balance of the fund information data chain, the fund security system compares the funds and status signs of the four business systems. When the status is inconsistent or the fund amount is inconsistent, a response alarm is triggered according to the rule level of the rule system.

[0037] The link between the fund security system and the early warning system is: the rule system triggers the relevant alarm email, and the early warning system finds the corresponding alarm group according to the business configuration relationship of the business system and sends the alarm email to the alarm group users.

[0038] Figure 2 is a flow chart of an optional data consistency verification method according to an embodiment of the present application, such as Figure 2 As shown, the method may include the following steps:

[0039] Step S202: The fund security system receives information flows from multiple business systems through the business interface system.

[0040] For example: receiving the information flow of the gateway through the business interface system; receiving the information flow of the cash register through the business interface system; receiving the information flow of the bank channel through the business interface system; receiving the information flow of the fund account through the business interface system.

[0041] Step S204: the funds security system verifies the consistency of the amount and status of the funds chain based on the information flow.

[0042] Based on the information flow, the abnormalities in the capital chain during the acquisition process can be verified, such as: based on the information flow, verify whether there are repeated entries, which means that an order is successfully paid to the customer but is entered multiple times; based on the information flow, verify whether there are multiple entries, which means that the amount entered into the customer's account is greater than the successful payment amount; based on the information flow, verify whether there are wrong entries, which means that the funds that should be given to customer A are entered into customer B; based on the information flow, verify whether there are repeated refunds, which means that when a transaction is refunded, the merchant account balance is deducted once but the cardholder is refunded multiple times; based on the information flow, verify whether there are In the case of a refund without deduction of payment, a refund without deduction of payment means that the transaction refund did not deduct the merchant account balance but multiple refunds were made to the cardholder; based on the information flow, check whether there is any missed entry, which means that the order payment was successful but not credited to the customer; based on the information flow, check whether there is any under-entry, which means that the amount credited to the customer is less than the successful payment amount; based on the information flow, check whether there is any wrong refund, which means that the refund that should be given to cardholder A was returned to cardholder B; based on the information flow, check whether there is any failed refund and the funds have not been refunded, which means that the amount credited to the customer is less than the successful payment amount.

[0043] It is also possible to verify anomalies in the capital chain when making payments based on the information flow, such as: verifying whether there are repeated withdrawals based on the information flow, which means that the merchant account balance is deducted once but the customer is paid multiple times; verifying whether there are over-withdrawals based on the information flow, which means that the amount paid to the customer is greater than the amount deducted from the account; verifying whether there are erroneous payments based on the information flow, which means that the amount that should be paid to customer A is paid to customer B; verifying whether there are repeated returns of failed payments based on the information flow, which means that the funds of a failed transaction are returned to the merchant account multiple times; verifying whether there are undeducted withdrawals based on the information flow, which means that the customer account balance is not deducted but the cardholder is refunded multiple times; verifying whether there are successful deductions but no payments based on the information flow, which means that the merchant account balance is deducted but no payments are made to the customer; verifying whether there are under-withdrawals based on the information flow, which means that the amount paid to the customer is less than the amount deducted from the account.

[0044] Step S206: The fund security system triggers the rule system to generate an alarm notification of a corresponding level according to the verification result.

[0045] Step S208: The fund security system pushes the alarm notification to the corresponding business owner through the early warning system.

[0046] Through the above steps S202 to S208, in the system consistency verification solution of the present application, the business system is connected to the fund security system message queue to push data to the fund security system. The fund security system conducts timely warning and response based on the information flow and quickly locates the problem. Compared with each business system performing its own fund accounting, production efficiency is effectively improved, making it an effective fund security prevention strategy, which can solve the technical problem that related technologies cannot detect data consistency.

[0047] As an optional embodiment, the technical solution of the present application is further described in detail below in combination with specific implementation methods:

[0048] The working plan of the fund security engine is as follows Figure 1 As shown in FIG. 1 , the message queues between the gateway system, the cashier system, the bank channel system, and the fund account system (i.e., the system where the fund security engine is located) are as follows: Figure 3 As shown, it includes: business system message queue queue: / / fundsafety.bussioness.queue, cashier message queue queue: / / fundsafety.cashier.queue, bank channel queue queue: / / fundsafety.bankchannel.queue, and accounting system queue queue: / / fundsafety.account.queue.

[0049] In this solution, the capital information flow is highly integrated, and each business system only needs to implement a simple interface docking. The information flow of the transaction process sends the complete message output point to the capital security work engine through the docking node. After receiving the message, the work engine matches the information of the entire information chain to achieve the purpose of consistency verification. The business logic coupling of the business system is relatively loose and does not affect the original business and performance. Under comprehensive pressure, the measured performance reaches 800TPS (the full name is Transactions Per Second, the number of transactions processed per second, that is, the number of transactions processed by the server per second).

[0050] The implementation of the whole solution is as follows:

[0051] Step 1: Connect to the business system through the fundsafetyBusinessProducer method to synchronize message parameters. The message parameter content includes the following fields:

[0052] Dna: DNA information; requestId: merchant request number; merchantId: merchant number; memberId: transaction member number; orderStatus: order status; Fee: transaction fee; orderAmount: order amount; createDateTime: transaction time; completeDateTime: transaction completion time; Currency: currency; businessSource: business source; tradeType: transaction type.

[0053] The above information is packaged into an MQ message and sent to the fund security engine (fundsafety). This message is the first message FristMsg sent when creating an order.

[0054] Step 2: After the fund security engine receives the message from the business system, it creates a data chain for the fund information flow. The complete data chain includes the following contents: Figure 4 This information chain contains complete transaction data information, including the gateway, cashier, bank channel, account balance and status in the fund account, etc.

[0055] Step 3: The cashier calls the fundsafetyCashReceiptProducer method in turn to send a cashier message to the fund security system. The information includes:

[0056] Dna: DNA information; merchantId: merchant ID; memberId: transaction member number; payerMemberId: payer number; orderStatus: order status; requestNumber: request number; businessSource: business source; orderAmount: transaction amount; Currency: currency; createDateTime: creation time; completeDateTime: transaction completion time.

[0057] The above information is packaged into an MQ message and sent to the fund security engine (fundsafety). This message is the second message TwoMsg sent when creating an order.

[0058] Step 4: After the bank channel payment transaction is completed, the fundsafetyBankChannelProducer method is called to send a packaged message to the fund security engine. The message content includes:

[0059] Dna: DNA order information; bankChannelId: bank channel number; Status: transaction status; reqeustId: request number; memberId: member number; merchantId: merchant number; orderAmount: order amount; bankOrderNumber: bank order number.

[0060] This message is the third part of the message component ThreeMsg.

[0061] Step 5: After receiving the three-way information chain, the fund security engine starts to call the doFillAndHandler method to check the integrity of the information chain.

[0062] Step 6: Fund security calls the getRules method from the database to obtain the configured alarm levels, which include:

[0063] RISK_LEVEL_01: The status of the business system, cashier counter, and bank channel are inconsistent;

[0064] RISK_LEVEL_02: The amounts in the business system, cashier counter, and bank channel are inconsistent;

[0065] RISK_LEVEL_03: Duplicate transactions in the business system;

[0066] RISK_LEVEL_04: Duplicate transactions at the cash register;

[0067] RISK_LEVEL_05: Duplicate orders in bank channel;

[0068] RISK_LEVEL_06: Daily reconciliation amounts are inconsistent;

[0069] RISK_LEVEL_07: Daily reconciliation status is inconsistent;

[0070] RISK_LEVEL_08: The merchant number for daily reconciliation is inconsistent;

[0071] RISK_LEVEL_09: The member number of daily reconciliation is inconsistent;

[0072] RISK_LEVEL_10: Illegal changes in account history;

[0073] RISK_LEVEL_11: The amount of historical account entries is inconsistent with the amount of information flow.

[0074] Step 7: When the fund security engine matches the fund amount, status, or inconsistency between the business code and the member number, the corresponding alarm level and method will be triggered.

[0075] Step 8: The early warning system obtains the information of the relevant alarm recipient through the FundSafetyMonitor.sendMonitorMsg method and sends the alarm email to the corresponding inbox.

[0076] The business system code identification enumeration class is shown in Table 1 below:

[0077] Table 1

[0078]

[0079]

[0080] The name of the business system message queue is queue: / / fundsafety.bussioness.queue, and the business entity corresponding to the message queue is com.ehking.fundsafety.entity.BusinessQueueEntity. The business field description is shown in Table 2:

[0081] Table 2

[0082] Field Name Field Type Is it required? (Y means yes, N means no) Field requirements DNA Varchar(32) Y DNA information Request_id Varchar(50) Y Merchant order number Merchant_id Varchat(50) Y Merchant Number Member_id Varchat(32) N Member Number Business_type Varchant(100) Y Business Type Order_status Varchat(30) Y Order Status Order_amount Decimal(18,2) Y Order transaction amount Fee Decimal(18,2) Y Handling Fees Fund_direction Varchat(30) Y Funding direction Currency Varchat(20) Y Trading Currency Create_date_time Datetime Y Creation time Complete_date_time Datetime Y Transaction completion time Business_source Varchant(100) Y Business source, enumeration class

[0083] The name of the fund account message queue is queue: / / fundsafety.fundaccount.queue, and the corresponding business entity is com.ehking.fundsafety.entity.FundAccountQueueEntity. The business field description is shown in Table 3:

[0084] Table 3

[0085]

[0086]

[0087] The business system order flow details are shown in Table 4:

[0088] Table 4

[0089]

[0090] The fields of the business summary file are shown in Table 5:

[0091] Table 5

[0092] Business Field Name Description Field Type Total_count The number of orders that occurred on the trading day Int Total_fee Total transaction fee per day BigDecimal Total_amount Total transaction volume on trading day BigDecimal

[0093] In the access process, each business system completes the access fields according to the access rules. The collection of each field requires the specified requirements of the service field. The process is as follows: the project relies on the basic message of fund security to push jms messages, and the producer corresponds to the message entity; in the relevant configuration, the scan path can be configured in the spring configuration file, such as "com.ehking.fundsafety.event"; enable the relevant code; the project relies on the message queue service and sftp service to introduce relevant resources; the business system needs T+1 statistics of transaction details and summary statistics submitted to the fund security system, so that the fund security work engine can compare data consistency. For example, in the sftp verification strategy, the verification file will be pushed to the designated sftp server from 1 to 5 am every day. The verification file name is business system code (refer to the business system number)_yyyyMMdd.csv.

[0094] After adopting the new encryption and decryption method, the performance and security of the application system have completely changed. The comprehensive performance is as follows: through 4 HA-based distributed servers, the system can process encryption and decryption requests up to 3000TPS. The performance of a single server meets 800TPS requests and can meet the needs of subsequent distributed expansion. Theoretically, it can be added indefinitely according to business demand.

[0095] In the traditional encryption and decryption processing of application systems, the development difficulty and cycle are tightly coupled, which increases the development cycle cost compared to the new method, and has lower security and maintainability.

[0096] The new method achieves 99.999% system stability, is simple to operate and maintain, and does not require replacement of keys and certificates. The replacement of certificates and keys supports dual support and dual strategies for new and old keys.

[0097] The new method reduces the consumption of system performance and greatly improves the stability and security of the application system. It is a significant decoupling method.

[0098] It should be noted that, for the aforementioned method embodiments, for the sake of simplicity, they are all expressed as a series of action combinations, but those skilled in the art should be aware that the present application is not limited by the described order of actions, because according to the present application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the present application.

[0099] Through the description of the above implementation methods, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a number of instructions for a terminal device (which can be a mobile phone, computer, server, or network device, etc.) to execute the methods described in each embodiment of the present application.

[0100] According to another aspect of an embodiment of the present application, a data consistency verification device for implementing the above-mentioned data consistency verification method is also provided. Figure 5 is a schematic diagram of an optional data consistency verification device according to an embodiment of the present application, such as Figure 5 As shown, the device may include:

[0101] A receiving unit 51, configured to receive information flows of multiple business systems through a business interface system;

[0102] A verification unit 53, configured to verify the consistency of the amount and status of the capital chain based on the information flow;

[0103] An alarm unit 55 is used to trigger the rule system to generate an alarm notification of a corresponding level according to the verification result;

[0104] The push unit 57 is used to push the alarm notification to the corresponding service owner through the early warning system.

[0105] It should be noted that the receiving unit 51 in this embodiment can be used to execute step S202 in the embodiment of the present application, the verification unit 53 in this embodiment can be used to execute step S204 in the embodiment of the present application, the alarm unit 55 in this embodiment can be used to execute step S206 in the embodiment of the present application, and the push unit 57 in this embodiment can be used to execute step S208 in the embodiment of the present application.

[0106] It should be noted that the examples and application scenarios implemented by the above modules and corresponding steps are the same, but are not limited to the contents disclosed in the above embodiments. It should be noted that the above modules as part of the device can be run in Figure 1 In the hardware environment shown, it can be implemented by software or by hardware.

[0107] It should be noted that the examples and application scenarios implemented by the above modules and corresponding steps are the same, but are not limited to the contents disclosed in the above embodiments. It should be noted that the above modules as part of the device can be run in Figure 1 In the hardware environment shown, it can be implemented by software or by hardware, wherein the hardware environment includes a network environment.

[0108] According to another aspect of an embodiment of the present application, a server or terminal for implementing the above-mentioned data consistency verification method is also provided.

[0109] Figure 6 is a structural block diagram of a terminal according to an embodiment of the present application, such as Figure 6 As shown, the terminal may include: one or more (only one is shown) processors 201, a memory 203, and a transmission device 205, such as Figure 6 As shown, the terminal may also include an input and output device 207.

[0110] Among them, the memory 203 can be used to store software programs and modules, such as the program instructions / modules corresponding to the data consistency verification method and device in the embodiment of the present application. The processor 201 executes various functional applications and data processing by running the software programs and modules stored in the memory 203, that is, realizing the above-mentioned data consistency verification method. The memory 203 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 203 may further include a memory remotely arranged relative to the processor 201, and these remote memories may be connected to the terminal via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0111] The above-mentioned transmission device 205 is used to receive or send data via a network, and can also be used for data transmission between a processor and a memory. Specific examples of the above-mentioned network may include a wired network and a wireless network. In one example, the transmission device 205 includes a network adapter (Network Interface Controller, NIC), which can be connected to other network devices and routers via a network cable so as to communicate with the Internet or a local area network. In one example, the transmission device 205 is a radio frequency (Radio Frequency, RF) module, which is used to communicate with the Internet wirelessly.

[0112] Specifically, the memory 203 is used to store application programs.

[0113] The processor 201 may call the application stored in the memory 203 through the transmission device 205 to perform the following steps:

[0114] Receive information flows from multiple business systems through a business interface system;

[0115] Based on the information flow, the consistency verification of the amount and status of the capital chain is performed;

[0116] According to the verification results, the rule system is triggered to generate an alarm notification of the corresponding level;

[0117] The alarm notification is pushed to the corresponding business party through the early warning system.

[0118] Optionally, the specific examples in this embodiment may refer to the examples described in the above embodiments, and this embodiment will not be described in detail here.

[0119] It can be understood by those skilled in the art that Figure 6 The structure shown is for illustration only, and the terminal may be a smart phone (such as an Android phone, an iOS phone, etc.), a tablet computer, a PDA, a mobile Internet device (Mobile Internet Devices, MID), a PAD, or other terminal devices. Figure 6 It does not limit the structure of the above electronic device. For example, the terminal may also include Figure 6 More or fewer components (such as network interfaces, display devices, etc.) shown in, or having Figure 6 Different configurations are shown.

[0120] A person of ordinary skill in the art can understand that all or part of the steps in the various methods of the above embodiments can be completed by instructing the hardware related to the terminal device through a program, and the program can be stored in a computer-readable storage medium, and the storage medium may include: a flash drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.

[0121] The embodiment of the present application further provides a storage medium. Optionally, in this embodiment, the storage medium can be used to execute the program code of the data consistency verification method.

[0122] Optionally, in this embodiment, the storage medium may be located on at least one network device among a plurality of network devices in the network shown in the above embodiment.

[0123] Optionally, in this embodiment, the storage medium is configured to store program codes for executing the following steps:

[0124] Receive information flows from multiple business systems through a business interface system;

[0125] Based on the information flow, the consistency verification of the amount and status of the capital chain is performed;

[0126] According to the verification results, the rule system is triggered to generate an alarm notification of the corresponding level;

[0127] The alarm notification is pushed to the corresponding business party through the early warning system.

[0128] Optionally, the specific examples in this embodiment may refer to the examples described in the above embodiments, and this embodiment will not be described in detail here.

[0129] Optionally, in this embodiment, the above-mentioned storage medium may include but is not limited to: a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk, and other media that can store program codes.

[0130] The serial numbers of the above-mentioned embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0131] If the integrated units in the above embodiments are implemented in the form of software functional units and sold or used as independent products, they can be stored in the above computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for enabling one or more computer devices (which may be personal computers, servers, or network devices, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application.

[0132] In the above embodiments of the present application, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, please refer to the relevant description of other embodiments.

[0133] In the several embodiments provided in the present application, it should be understood that the disclosed client can be implemented in other ways. Among them, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0134] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0135] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0136] The above is only a preferred implementation of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A data consistency verification system, characterized in that: include: A fund security system, which is used to verify the consistency of data between multiple business systems; A business interface system, which is in communication with the fund security system and the multiple business systems, and is used to provide docking solutions and interface packaging services to the multiple business systems; A rule system, which is in communication with the fund security system and is used to trigger corresponding alarm notifications according to the verification results of the fund security system; An early warning system, which is in communication with the rule system and the fund security system, and is used to push the alarm notification to the business owner; The multiple business systems include four business systems, namely, a gateway, a cash register, a bank channel and a fund account system. The fund security system compares the funds and status flags of the four business systems. When the status is inconsistent or the fund amount is inconsistent, a response alarm is triggered according to the rule level of the rule system. The four business systems push messages to the fund security system through the JMS message of the business interface system. When an order based on the information flow flows through the four business systems, a corresponding message is triggered to the fund security system. The fund security system is used to verify the data consistency between multiple business systems in the following manner: Based on the information flow, verify the abnormality of the capital chain during the collection process; Based on the information flow, the abnormalities in the capital chain during withdrawal are verified.

2. The verification system according to claim 1, characterized in that: The fund security system is also used to: Receive the information flows of the multiple business systems pushed by the business interface system, and perform consistency verification of the amount and status of the capital chain based on the information flow, trigger the rule system to generate an alarm notification of the corresponding level according to the verification result, and push the alarm notification to the corresponding business attribution party through the early warning system.

3. A method for verifying data consistency, characterized in that: include: Receive information flows from multiple business systems through a business interface system; Based on the information flow, the consistency verification of the amount and status of the capital chain is performed, including: based on the information flow, verifying the abnormality of the capital chain during the collection process; based on the information flow, verifying the abnormality of the capital chain during the withdrawal process; According to the verification results, the rule system is triggered to generate an alarm notification of the corresponding level; Push the alarm notification to the corresponding business owner through the early warning system; The multiple business systems include four business systems, namely, a gateway, a cash register, a bank channel and a fund account system. The fund security system compares the funds and status flags of the four business systems. When the status is inconsistent or the fund amount is inconsistent, a response alarm is triggered according to the rule level of the rule system. The four business systems push messages to the fund security system through the JMS message of the business interface system. When an order based on the information flow flows through the four business systems, a corresponding message is triggered to the fund security system. Wherein, based on the information flow, verifying the abnormality of the capital chain during the acquisition process includes: Based on the information flow, the abnormalities in the capital chain during withdrawal are verified.

4. The method according to claim 3, characterized in that The information flows received from multiple business systems through the business interface system include: receiving the information flow of the gateway through the service interface system; receiving the information flow from the cashier via the business interface system; Receiving the information flow of the bank channel through the business interface system; The information flow of the fund account is received through the business interface system.

5. A data consistency verification device, characterized in that: include: A receiving unit, used for receiving information flows of multiple business systems through a business interface system; A verification unit, used to verify the consistency of the amount and status of the capital chain based on the information flow, including: verifying the abnormality of the capital chain when acquiring a bill based on the information flow; verifying the abnormality of the capital chain when withdrawing money based on the information flow; An alarm unit is used to trigger the rule system to generate an alarm notification of a corresponding level according to the verification results; A push unit, used to push the alarm notification to the corresponding business owner through the early warning system; The multiple business systems include four business systems, namely, a gateway, a cash register, a bank channel and a fund account system. The fund security system compares the funds and status flags of the four business systems. When the status is inconsistent or the fund amount is inconsistent, a response alarm is triggered according to the rule level of the rule system. The four business systems push messages to the fund security system through the JMS message of the business interface system. When an order based on the information flow flows through the four business systems, a corresponding message is triggered to the fund security system. Among them, based on the information flow, the abnormality of the capital chain during the collection process is verified; Based on the information flow, the abnormalities in the capital chain during withdrawal are verified.

6. A storage medium, characterized in that: The storage medium includes a stored program, wherein the program executes the method described in any one of claims 3 to 4 when executed.

7. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein: The processor executes the method described in any one of claims 3 to 4 through the computer program.

Images