CN112581134A - Data verification method, device and system - Google Patents
Data verification method, device and system Download PDFInfo
- Publication number
- CN112581134A CN112581134A CN202011563787.4A CN202011563787A CN112581134A CN 112581134 A CN112581134 A CN 112581134A CN 202011563787 A CN202011563787 A CN 202011563787A CN 112581134 A CN112581134 A CN 112581134A
- Authority
- CN
- China
- Prior art keywords
- data
- server
- transaction
- verified
- transaction data
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims description 51
- 238000013524 data verification Methods 0.000 title claims description 24
- 238000012795 verification Methods 0.000 claims abstract description 133
- 238000007726 management method Methods 0.000 claims description 73
- 238000012545 processing Methods 0.000 claims description 30
- 208000011580 syndromic disease Diseases 0.000 claims description 20
- 238000007781 pre-processing Methods 0.000 claims description 6
- 230000004044 response Effects 0.000 claims description 2
- 238000005516 engineering process Methods 0.000 description 5
- 238000006243 chemical reaction Methods 0.000 description 3
- 238000010586 diagram Methods 0.000 description 3
- 238000012546 transfer Methods 0.000 description 3
- 238000004590 computer program Methods 0.000 description 2
- 230000003247 decreasing effect Effects 0.000 description 2
- 238000004364 calculation method Methods 0.000 description 1
- 238000004140 cleaning Methods 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000010801 machine learning Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/389—Keeping log of transactions for guaranteeing non-repudiation of a transaction
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/28—Databases characterised by their database models, e.g. relational or object models
- G06F16/283—Multi-dimensional databases or data warehouses, e.g. MOLAP or ROLAP
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/28—Databases characterised by their database models, e.g. relational or object models
- G06F16/284—Relational databases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/08—Payment architectures
- G06Q20/10—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
- G06Q20/102—Bill distribution or payments
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Business, Economics & Management (AREA)
- Databases & Information Systems (AREA)
- Accounting & Taxation (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Finance (AREA)
- General Engineering & Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Strategic Management (AREA)
- General Business, Economics & Management (AREA)
- Computational Linguistics (AREA)
- Development Economics (AREA)
- Economics (AREA)
- Debugging And Monitoring (AREA)
Abstract
When a management server of a first system verifies first transaction data generated by the first system according to a transaction request and second transaction data generated by a second system according to the same transaction request, the management server can acquire data to be verified, wherein the data to be verified comprises the first transaction data and the second transaction data, and the second transaction data comprises an identifier of the second system. According to the identifier of the second system, the management server can determine a target verification rule corresponding to the second system by combining the corresponding relation, and send the target verification rule and the data to be verified to the verification server of the first system, and the verification server verifies the data to be verified according to the target verification rule. Therefore, the corresponding verification rules can be determined according to the identification of the third-party system, so that the corresponding verification rules are utilized to verify the transaction data in different formats, and the third-party transaction data in different formats is verified.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a data verification method, apparatus, and system.
Background
Reconciliation refers to a process of verifying self-generated transaction flow data and transaction flow data generated by a third party by a bank (or other financial institutions). By reconciling, the bank can determine if there is an erroneous transaction. For example, after processing a transaction request "transfer money from an account of bank a to an account of bank B", both bank a and bank B will generate corresponding transaction flow data. To ensure that the transaction request is successfully executed, transaction flow data generated by bank a, bank B and a third party institution (e.g., a clearing institution such as a union of bank) may be compared with each other. This process is the bank reconciliation process.
At present, in the reconciliation process of a bank, a bank system can acquire locally stored transaction flow data and acquire corresponding transaction flow data from a third-party system, and the local transaction flow data and the third-party transaction flow data are compared by using a preset check rule, so that whether the transaction data corresponding to each transaction request is normal or not is determined, and whether each transaction is successful or not is determined.
However, with the development of computer technology, payment methods are more and more diversified, data formats of transaction data generated by different payment methods may be different, and a conventional reconciliation method is not suitable for a scenario of verifying third-party transaction data in multiple formats.
Disclosure of Invention
In view of this, embodiments of the present application provide a data verification method, apparatus, and system, and aim to provide a method capable of adapting to verification of third party transaction data in different formats.
In a first aspect, an embodiment of the present application provides a data verification method, where the method includes:
the method comprises the steps that a management server obtains data to be verified, wherein the data to be verified comprises first transaction data and second transaction data; the first transaction data is generated by the first system according to a transaction request, the second transaction data is generated by the second system according to the transaction request, the second transaction data comprises an identifier of the second system, and the management server belongs to the first system;
the management server determines a target verification rule corresponding to the second system according to the identifier of the second system and a corresponding relationship, wherein the corresponding relationship comprises the corresponding relationship between the identifier of the second system and the identifier of the target verification rule;
the management server sends the data to be verified and the target verification rule to a verification server so that the verification server can verify the data to be verified according to the target verification rule, and the verification server belongs to a first system.
Optionally, the acquiring, by the management server, the data to be verified includes:
the management server acquires the first transaction data from a transaction server of the first system;
the management server obtains the second transaction data from a transaction server of the second system.
Optionally, the acquiring, by the management server, the second transaction data from the transaction server of the second system includes:
and the management server receives second transaction data sent by the processing server, wherein the second transaction data is obtained by preprocessing the transaction data generated by the transaction server of the second system by the processing server.
Optionally, the receiving, by the management server, the second transaction data sent by the processing server includes:
and the management server receives the identification of the second system sent by the processing server, wherein the identification of the second system is acquired by the processing server from the transaction server of the second system.
Optionally, the verification server comprises a first verification sub-server and a second verification sub-server;
the step of sending the data to be verified and the target verification rule to a verification server by the management server comprises the following steps:
the management server detects the size of the transaction data to be verified in the first verification sub-server;
in response to the size of the transaction data to be verified exceeding a target threshold, the management server sends the target verification rule and the data to be verified to the second verification sub-server.
In a second aspect, an embodiment of the present application provides a data verification apparatus, where the apparatus is applied to a management server, and includes:
the data acquisition module is used for acquiring data to be verified, wherein the data to be verified comprises first transaction data and second transaction data; the first transaction data is generated by the first system according to a transaction request, the second transaction data is generated by the second system according to the transaction request, the second transaction data comprises an identifier of the second system, and the management server belongs to the first system;
a rule determining module, configured to determine a target verification rule corresponding to the second system according to an identifier of the second system and a corresponding relationship, where the corresponding relationship includes a corresponding relationship between the identifier of the second system and an identifier of the target verification rule;
and the sending module is used for sending the data to be verified and the target verification rule to a verification server so that the verification server can verify the data to be verified according to the target verification rule, and the verification server belongs to a first system.
Optionally, the data obtaining module is configured to obtain the first transaction data from a transaction server of the first system; obtaining the second transaction data from a transaction server of the second system.
Optionally, the data obtaining module is configured to receive second transaction data sent by a processing server, where the second transaction data is obtained by preprocessing, by the processing server, transaction data generated by a transaction server of the second system.
Optionally, the data obtaining module is configured to receive an identifier of the second system sent by the processing server, where the identifier of the second system is obtained by the processing server from a transaction server of the second system.
Optionally, the verification server comprises a first verification sub-server and a second verification sub-server; the sending module is used for detecting the size of the data to be verified stored in the first syndrome server; and responding to the stored data to be verified exceeding a target threshold value, and sending the target verification rule and the data to be verified to the second verification sub-server.
In a third aspect, an embodiment of the present application provides a data verification system, where the data verification system belongs to a first system, and includes a management server and a verification server;
the management server is used for acquiring data to be verified, the data to be verified comprises first transaction data and second transaction data, determining a target verification rule corresponding to the second system according to the identification and the corresponding relation of the second system, and sending the data to be verified and the target verification rule to the verification server; the first transaction data is generated by the first system according to a transaction request, the second transaction data is generated by the second system according to the transaction request, the second transaction data comprises an identifier of the second system, and the corresponding relationship comprises a corresponding relationship between the identifier of the second system and the identifier of the target verification rule;
and the verification server is used for verifying the data to be verified according to the target verification rule.
Optionally, the verification server comprises a first verification sub-server and a second verification sub-server;
the management server is further configured to detect the size of the data to be verified stored in the first syndrome server; and responding to the stored data to be verified exceeding a target threshold value, and sending the target verification rule and the data to be verified to the second verification sub-server.
In a fourth aspect, an embodiment of the present application further provides a management server, where the server includes a memory and a processor, where the memory is used to store instructions, and the processor is used to execute the instructions stored in the memory, so as to enable the first device to execute the data verification method according to the foregoing first aspect.
In a fourth aspect, an embodiment of the present application further provides a computer-readable storage medium, where the computer-readable storage mechanism is configured to store a computer program, where the computer program is configured to control a first device to execute the data verification method according to the foregoing first aspect.
When a management server of a first system verifies first transaction data generated by the first system according to a transaction request and second transaction data generated by a second system according to the same transaction request, the management server may first acquire data to be verified, where the data to be verified includes the first transaction data and the second transaction data, and the second transaction data includes an identifier of the second system. According to the identifier of the second system, the management server can determine a target verification rule corresponding to the second system by combining the corresponding relation, and send the target verification rule and the data to be verified to the verification server of the first system, and the verification server verifies the data to be verified according to the target verification rule. Therefore, when the transaction data of the plurality of third-party systems need to be verified, the corresponding verification rules can be determined according to the identification of each third-party system, so that the transaction data in different formats can be verified by using different verification rules. Compared with the traditional technology, the method can be used for verifying the third-party transaction data in different formats. In addition, when the transaction data is verified, the transaction data generated by the first system and the second system is verified by taking the transaction request as a basic unit, and the larger transaction data can be divided into a plurality of transaction subdata, so that the transaction data is processed in parallel on a plurality of processors.
Drawings
To illustrate the technical solutions in the present embodiment or the prior art more clearly, the drawings needed to be used in the description of the embodiment or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1 is a flowchart of a method of a data verification method according to an embodiment of the present application;
fig. 2 is a schematic structural diagram of a data verification apparatus according to an embodiment of the present disclosure;
fig. 3 is a schematic structural diagram of a data verification system according to an embodiment of the present application.
Detailed Description
Conventional bank reconciliation is mostly only performed between different banks. Because the similarity of transaction data generated by a bank system is higher, the traditional reconciliation method does not need to process the transaction data, and the reconciliation is directly carried out on the transaction running data line by line. However, with the advent of online payment methods, a large amount of transaction data is generated based on online payment methods, and the formats of transaction data generated by online payment methods and transaction data generated by banks are mostly different, for example, the formats of transaction data generated by unionpay transfers and transaction data generated by online bank transfers are different. Due to different formats of transaction data, the traditional line-by-line comparison method cannot be used for reconciliation.
In order to solve the problem, an application program can be added in a server responsible for reconciliation and used for converting the transaction data of the third party into the transaction data with the same format as the transaction data of the system and then comparing the transaction data line by line. However, although this method can be used for the same format of transaction data, performing format conversion will undoubtedly bring extra processing load to the server.
In addition, the traditional reconciliation mode needs to sequence the local transaction data and the third party transaction data, and then can compare the local transaction data and the third party transaction data line by line. When the data amount of the transaction data is large, the time required for sorting increases significantly. Therefore, the traditional reconciliation method is fashionable when the transaction data is less, and the calculation complexity of the traditional reconciliation method is greatly increased along with the increase of the transaction data amount. Therefore, the conventional reconciliation method is not suitable for large banks or other large financial institutions.
In order to provide a method for verifying third-party transaction data capable of adapting to different formats, the embodiment of the application provides a data verification method, a device and a system. The data verification method provided by the embodiment of the present application is described below from the perspective of the management server with reference to the drawings of the specification. The management server is a server belonging to a first system, and the data verification object is first transaction data generated by the first system and second transaction data generated by a second system. The first system may be a system composed of all servers of a bank or other financial institution, and the second system may be a system composed of all servers of a bank or other financial institution different from the first system. It should be noted that the management server may be an independent server, or may be a software platform running on the server. It should be apparent that the described embodiments are only some of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
Referring to fig. 1, fig. 1 is a flowchart of a method of a data verification method provided in an embodiment of the present application, including:
s101: and the management server acquires the data to be verified, wherein the data to be verified comprises the identifier of the second system.
When the management server performs data verification (i.e. bank reconciliation), the data to be verified can be acquired first. The data to be verified may include first transaction data and second transaction data. The first transaction data is generated by the first system when processing the transaction request, and the second transaction data is generated by the second system when processing the same transaction request, i.e. the first transaction data and the second transaction data are generated by the two systems when processing the same transaction request. The second system and the first system belong to different organizations, for example, the second system and the first system belong to a bank and a clearing organization respectively, or two systems respectively composed of servers of two banks.
For example. Suppose user X has transferred one hundred dollars from account a at bank a to account B at bank B through the union of the bank. After the transaction is finished, the bank a may generate transaction data of "the balance of the account a is decreased by one hundred," that is, the first transaction data in the embodiment of the present application, and the union of banking may generate transaction data of "the balance of the bank a is decreased by one hundred, and the balance of the bank B is increased by one hundred," that is, the second transaction data in the embodiment of the present application.
In some possible implementations, the management server may obtain the first transaction data from a transaction server of the first system, and may also obtain the first transaction data from a data repository of the first system. The management server may also obtain the second transaction data from a transaction server or data repository of the second system if a network connection has been established between the management server and the server of the second system. The transaction server may be a server for processing transaction requests, and the data warehouse may be a database for storing transaction data, for example, a relational database.
If no network connection is established between the management server and the server of the second system, the processing server in the first system can extract the transaction data generated by the second system from the transaction server or the data warehouse of the second system, and perform preprocessing such as cleaning and conversion on the transaction data to obtain the second transaction data. The management server may receive the second transaction data sent by the processing server, so as to verify the second transaction data. The processing server may be an independent server in the first system, and is configured to obtain the transaction data from the third-party system and perform preprocessing, or may be a software module running on a server (e.g., a management server) in the first system, which is not limited in this embodiment of the present application.
In an embodiment of the present application, the second transaction data may include an identifier of the second system, and the identifier of the second system may include information that can uniquely identify the second system, such as a company name or a company code corresponding to the second system. Optionally, the identifier of the second system may also indicate a type corresponding to the second system, for example, information such as a type of a company corresponding to the second system may be included.
When the management server receives the second transaction data through the processing server, the processing server may obtain the identifier of the second system from the transaction server of the second system, and add the identifier of the second system to the second transaction data to send to the management server.
S102: and the management server determines a target verification rule corresponding to the second system according to the identification and the corresponding relation of the second system.
After obtaining the identifier of the second system, the management server may determine the target verification rule according to the identifier of the second system and the corresponding relationship. The corresponding relationship comprises the corresponding relationship between the identifier of the second system and the target verification rule, and can also comprise the corresponding relationship between the identifiers of other third-party systems and the verification rules. The check rule represents a correspondence between a transaction data format generated by the first system and a transaction data format generated by the third-party system, and may include, for example, a correspondence between each field in the transaction data generated by the first system and each field in the transaction data generated by the third-party system, and may further include a conversion relationship between a field value of any one field in the transaction data generated by the first system and a field value of any one field in the transaction data generated by the third-party system.
In this embodiment of the present application, the corresponding relationship may be obtained by comparing a format of the transaction data generated by the first system with a format of the transaction data generated by the second system in advance by a technician, or may be obtained by performing machine learning on the test case by a computer or a server.
S103: and the management server sends the data to be verified and the target verification rule to a verification server.
After determining the target verification rule corresponding to the second system, the management server may send the data to be verified and the target verification rule to the verification server of the first system. Therefore, the verification server can verify the first transaction data and the second transaction data according to the received target verification rule, and automatic verification and account checking of the transaction data are achieved.
In the embodiment of the present application, the verification server is a physical device or a virtual device for verifying the transaction data, and may be, for example, an independent server in the first system, or a software platform running on another server. In some possible implementations, the verification server may be a server cluster composed of a plurality of servers. Optionally, the verification server is a Flink framework-based distributed processing system, and includes a plurality of servers for verifying the transaction data.
When the verification server is a server cluster composed of a plurality of servers, the management server may send the data to be verified to any one of the servers, or may send the data to be verified to a specific server according to the identifier of the second system, for example, send the data to be verified including the identifier of the second system to the same server. In some possible implementations, the management server may send the data to be verified based on the load of the server.
The verification server includes a first sub server and a second sub server. When sending the data to be verified, the management server may preferentially send the server to be verified to the first sub-server. The management server may detect the size of the transaction data to be verified by the first syndrome server, i.e. the transaction data that has not yet been processed has been received by the first syndrome server. If the size of the transaction data to be verified stored by the first syndrome server exceeds the target threshold, which indicates that the load of the first syndrome service is high, the management server may send the target verification rule and the data to be verified to the second syndrome server.
When a management server of a first system verifies first transaction data generated by the first system according to a transaction request and second transaction data generated by a second system according to the same transaction request, the management server may first acquire data to be verified, where the data to be verified includes the first transaction data and the second transaction data, and the second transaction data includes an identifier of the second system. According to the identifier of the second system, the management server can determine a target verification rule corresponding to the second system by combining the corresponding relation, and send the target verification rule and the data to be verified to the verification server of the first system, and the verification server verifies the data to be verified according to the target verification rule. Therefore, when the transaction data of the plurality of third-party systems need to be verified, the corresponding verification rules can be determined according to the identification of each third-party system, so that the transaction data in different formats can be verified by using different verification rules. Compared with the traditional technology, the method can be used for verifying the third-party transaction data in different formats. In addition, when the transaction data is verified, the transaction data generated by the first system and the second system is verified by taking the transaction request as a basic unit, and the larger transaction data can be divided into a plurality of transaction subdata, so that the transaction data is processed in parallel on a plurality of processors.
The foregoing provides some specific implementation manners of the data verification method for the embodiments of the present application, and based on this, the present application also provides a corresponding apparatus. The above-mentioned device provided by the embodiments of the present application will be described in terms of functional modularity.
Referring to fig. 2, a schematic structural diagram of a data verification apparatus 200 includes:
a data obtaining module 210, configured to obtain data to be verified, where the data to be verified includes first transaction data and second transaction data; the first transaction data is generated by the first system according to a transaction request, the second transaction data is generated by the second system according to the transaction request, the second transaction data comprises an identifier of the second system, and the management server belongs to the first system.
The rule determining module 220 is configured to determine a target verification rule corresponding to the second system according to the identifier of the second system and a corresponding relationship, where the corresponding relationship includes a corresponding relationship between the identifier of the second system and the identifier of the target verification rule.
The sending module 230 is configured to send the data to be verified and the target verification rule to a verification server, so that the verification server verifies the data to be verified according to the target verification rule, where the verification server belongs to a first system.
When a management server of a first system verifies first transaction data generated by the first system according to a transaction request and second transaction data generated by a second system according to the same transaction request, the management server may first acquire data to be verified, where the data to be verified includes the first transaction data and the second transaction data, and the second transaction data includes an identifier of the second system. According to the identifier of the second system, the management server can determine a target verification rule corresponding to the second system by combining the corresponding relation, and send the target verification rule and the data to be verified to the verification server of the first system, and the verification server verifies the data to be verified according to the target verification rule. Therefore, when the transaction data of the plurality of third-party systems need to be verified, the corresponding verification rules can be determined according to the identification of each third-party system, so that the transaction data in different formats can be verified by using different verification rules. Compared with the traditional technology, the method can be used for verifying the third-party transaction data in different formats. In addition, when the transaction data is verified, the transaction data generated by the first system and the second system is verified by taking the transaction request as a basic unit, and the larger transaction data can be divided into a plurality of transaction subdata, so that the transaction data is processed in parallel on a plurality of processors.
Optionally, in some possible implementations, the data obtaining module 210 is configured to obtain the first transaction data from a transaction server of the first system; obtaining the second transaction data from a transaction server of the second system.
Optionally, in some possible implementation manners, the data obtaining module 210 is configured to receive second transaction data sent by a processing server, where the second transaction data is obtained by preprocessing, by the processing server, transaction data generated by a transaction server of the second system.
Optionally, in some possible implementations, the data obtaining module 210 is configured to receive the identifier of the second system sent by the processing server, where the identifier of the second system is obtained by the processing server from a transaction server of the second system.
Optionally, in some possible implementations, the check server includes a first check sub-server and a second check sub-server;
the sending module 230 is configured to detect a size of the data to be verified stored in the first syndrome server; and responding to the stored data to be verified exceeding a target threshold value, and sending the target verification rule and the data to be verified to the second verification sub-server.
Referring to fig. 3, an embodiment of the present application further provides a data verification system 310, where the data verification system 310 belongs to the first system 300 and may include a management server 311 and a verification server 312. In fig. 3, the first system 300 may further include a transaction server 321, and the second system 400 may include a transaction server 411
The management server 311 is configured to obtain data to be verified, where the data to be verified includes first transaction data and second transaction data, determine a target verification rule corresponding to the second system 400 according to an identifier and a corresponding relationship of the second system 400, and send the data to be verified and the target verification rule to the verification server 312; wherein the first transaction data is generated by the first system 300 according to a transaction request, the second transaction data is generated by the second system 400 according to a transaction request, the second transaction data includes an identifier of the second system 400, and the correspondence includes a correspondence between the identifier of the second system 400 and an identifier of the target verification rule.
The verification server 312 is configured to verify the data to be verified according to the target verification rule.
Optionally, in some possible implementations, the check server 321 includes a first check sub server and a second check sub server.
The management server 320 is further configured to detect a size of the data to be verified stored in the first syndrome server; and responding to the stored data to be verified exceeding a target threshold value, and sending the target verification rule and the data to be verified to the second verification sub-server.
For a detailed description of other devices and systems in fig. 3, reference may be made to the foregoing method embodiments, and details are not repeated here.
In the embodiments of the present application, the names "first" and "second" in the names "first transaction data", "second transaction data", and the like are used merely as name labels, and do not represent the first and second in sequence.
As can be seen from the above description of the embodiments, those skilled in the art can clearly understand that all or part of the steps in the above embodiment methods can be implemented by software plus a general hardware platform. Based on such understanding, the technical solution of the present application may be embodied in the form of a software product, which may be stored in a storage medium, such as a read-only memory (ROM)/RAM, a magnetic disk, an optical disk, or the like, and includes several instructions for enabling a computer device (which may be a personal computer, a server, or a network communication device such as a router) to execute the method according to the embodiments or some parts of the embodiments of the present application.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the apparatus embodiment, since it is substantially similar to the method embodiment, it is relatively simple to describe, and reference may be made to some descriptions of the method embodiment for relevant points. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.
The above description is only an exemplary embodiment of the present application, and is not intended to limit the scope of the present application.
Claims (10)
1. A method for data verification, the method comprising:
the method comprises the steps that a management server obtains data to be verified, wherein the data to be verified comprises first transaction data and second transaction data; the first transaction data is generated by the first system according to a transaction request, the second transaction data is generated by the second system according to the transaction request, the second transaction data comprises an identifier of the second system, and the management server belongs to the first system;
the management server determines a target verification rule corresponding to the second system according to the identifier of the second system and a corresponding relationship, wherein the corresponding relationship comprises the corresponding relationship between the identifier of the second system and the identifier of the target verification rule;
the management server sends the data to be verified and the target verification rule to a verification server so that the verification server can verify the data to be verified according to the target verification rule, and the verification server belongs to a first system.
2. The method of claim 1, wherein the obtaining of the data to be verified by the management server comprises:
the management server acquires the first transaction data from a transaction server of the first system;
the management server obtains the second transaction data from a transaction server of the second system.
3. The method of claim 2, wherein the managing server obtaining the second transaction data from the transaction server of the second system comprises:
and the management server receives second transaction data sent by the processing server, wherein the second transaction data is obtained by preprocessing the transaction data generated by the transaction server of the second system by the processing server.
4. The method of claim 3, wherein the receiving, by the management server, the second transaction data sent by the processing server comprises:
and the management server receives the identification of the second system sent by the processing server, wherein the identification of the second system is acquired by the processing server from the transaction server of the second system.
5. The method of claim 1, wherein the syndrome server comprises a first syndrome server and a second syndrome server;
the step of sending the data to be verified and the target verification rule to a verification server by the management server comprises the following steps:
the management server detects the size of the transaction data to be verified in the first verification sub-server;
in response to the size of the transaction data to be verified exceeding a target threshold, the management server sends the target verification rule and the data to be verified to the second verification sub-server.
6. A data verification device, which is applied to a management server, includes:
the data acquisition module is used for acquiring data to be verified, wherein the data to be verified comprises first transaction data and second transaction data; the first transaction data is generated by the first system according to a transaction request, the second transaction data is generated by the second system according to the transaction request, the second transaction data comprises an identifier of the second system, and the management server belongs to the first system;
a rule determining module, configured to determine a target verification rule corresponding to the second system according to an identifier of the second system and a corresponding relationship, where the corresponding relationship includes a corresponding relationship between the identifier of the second system and an identifier of the target verification rule;
and the sending module is used for sending the data to be verified and the target verification rule to a verification server so that the verification server can verify the data to be verified according to the target verification rule, and the verification server belongs to a first system.
7. The apparatus of claim 6,
the data acquisition module is used for acquiring the first transaction data from a transaction server of the first system; obtaining the second transaction data from a transaction server of the second system.
8. The method of claim 6, wherein the syndrome server comprises a first syndrome server and a second syndrome server;
the sending module is used for detecting the size of the data to be verified stored in the first syndrome server; and responding to the stored data to be verified exceeding a target threshold value, and sending the target verification rule and the data to be verified to the second verification sub-server.
9. A data checking system is characterized in that the data checking system belongs to a first system and comprises a management server and a checking server;
the management server is used for acquiring data to be verified, the data to be verified comprises first transaction data and second transaction data, determining a target verification rule corresponding to the second system according to the identification and the corresponding relation of the second system, and sending the data to be verified and the target verification rule to the verification server; the first transaction data is generated by the first system according to a transaction request, the second transaction data is generated by the second system according to the transaction request, the second transaction data comprises an identifier of the second system, and the corresponding relationship comprises a corresponding relationship between the identifier of the second system and the identifier of the target verification rule;
and the verification server is used for verifying the data to be verified according to the target verification rule.
10. The system of claim 9, wherein the syndrome server comprises a first syndrome server and a second syndrome server;
the management server is further configured to detect the size of the data to be verified stored in the first syndrome server; and responding to the stored data to be verified exceeding a target threshold value, and sending the target verification rule and the data to be verified to the second verification sub-server.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011563787.4A CN112581134A (en) | 2020-12-25 | 2020-12-25 | Data verification method, device and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011563787.4A CN112581134A (en) | 2020-12-25 | 2020-12-25 | Data verification method, device and system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112581134A true CN112581134A (en) | 2021-03-30 |
Family
ID=75139663
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011563787.4A Pending CN112581134A (en) | 2020-12-25 | 2020-12-25 | Data verification method, device and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112581134A (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103577571A (en) * | 2013-10-31 | 2014-02-12 | 北京奇虎科技有限公司 | Data processing method and device |
| CN108809896A (en) * | 2017-04-28 | 2018-11-13 | 阿里巴巴集团控股有限公司 | A kind of information calibration method, device and electronic equipment |
| CN109543942A (en) * | 2018-10-16 | 2019-03-29 | 平安普惠企业管理有限公司 | Data verification method, device, computer equipment and storage medium |
-
2020
- 2020-12-25 CN CN202011563787.4A patent/CN112581134A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103577571A (en) * | 2013-10-31 | 2014-02-12 | 北京奇虎科技有限公司 | Data processing method and device |
| CN108809896A (en) * | 2017-04-28 | 2018-11-13 | 阿里巴巴集团控股有限公司 | A kind of information calibration method, device and electronic equipment |
| CN109543942A (en) * | 2018-10-16 | 2019-03-29 | 平安普惠企业管理有限公司 | Data verification method, device, computer equipment and storage medium |
Non-Patent Citations (1)
| Title |
|---|
| 彭土有 等: "《新编Linux系统基础教程》", 30 June 2015, 北京交通大学出版社, pages: 159 * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110263024B (en) | Data processing method, terminal device and computer storage medium | |
| CN110782240B (en) | Business data processing method and device, computer equipment and storage medium | |
| CN105389488B (en) | Identity identifying method and device | |
| CN106101179B (en) | Resource processing method, device and system | |
| CN111738709B (en) | Transaction processing method and device | |
| CN108537520B (en) | Method and device for accessing third-party payment transaction | |
| CN110033348A (en) | Storage, checking method and the device of business datum | |
| CN109615384B (en) | Method, device and server for generating timeliness check rule | |
| CN108961034A (en) | System and method, storage medium based on user behavior certification | |
| CN106875184B (en) | Abnormal scene simulation method, device and equipment | |
| CN110781134A (en) | Data processing method and device, computer storage medium and electronic equipment | |
| CN109165947B (en) | Account information determination method and device and server | |
| CN110689424B (en) | Funds supply and demand matching method and system | |
| CN114971598B (en) | Wind-controlled approval system, method, equipment and medium | |
| CN112581134A (en) | Data verification method, device and system | |
| CN113450084A (en) | Group client signing approval circulation device and method | |
| CN111797590A (en) | Data checking method, device and equipment | |
| CN111415245A (en) | Account opening method and device | |
| CN109150996A (en) | A kind of block chain method of reseptance and system | |
| CN111242592B (en) | Resource transfer detection method, device, server and computer readable storage medium | |
| CN112651772B (en) | Event touch method, device, equipment and storage medium | |
| US11625698B2 (en) | Intelligent distributed ledger consent optimizing apparatus for asset transfer | |
| TWI831114B (en) | Integrity verifying method, system and computer device of separated cross-platform trade and accounting, computer-readable medium | |
| CN111127003B (en) | Wallet account payment method, device and storage medium | |
| TWI778271B (en) | Method for electronic trading examination and system for electronic trading |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |