CN112783845A - Data reconciliation system, method, device and medium - Google Patents
Data reconciliation system, method, device and medium Download PDFInfo
- Publication number
- CN112783845A CN112783845A CN202110057573.8A CN202110057573A CN112783845A CN 112783845 A CN112783845 A CN 112783845A CN 202110057573 A CN202110057573 A CN 202110057573A CN 112783845 A CN112783845 A CN 112783845A
- Authority
- CN
- China
- Prior art keywords
- reconciliation
- data
- file
- server
- client
- 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.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/17—Details of further file system functions
- G06F16/172—Caching, prefetching or hoarding of files
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/14—Details of searching files based on file metadata
- G06F16/148—File search 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/10—File systems; File servers
- G06F16/16—File or folder operations, e.g. details of user interfaces specifically adapted to file systems
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Library & Information Science (AREA)
- Human Computer Interaction (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The embodiment of the invention provides a data reconciliation system, a method, equipment and a medium, wherein in the data reconciliation system, an SDK (software development kit) module acquires a first reconciliation file to be collated from a third-party server, and transmits the first reconciliation file to the reconciliation server according to a preset transmission strategy, wherein the first reconciliation file comprises preset type data; the reconciliation server stores a first reconciliation file from the SDK module; responding to a data acquisition request of a client, inquiring a second account checking file corresponding to the data acquisition request from the stored first account checking file, and feeding back the second account checking file to the client; the client sends a data acquisition request to the account checking server; and receiving a second account checking file fed back by the account checking server, and performing data checking based on the second account checking file. Need not the interactive interface between the server and call among this data reconciliation system, reduce data transmission time delay, promote the user experience of APP side, avoid the data uniformity of third party SDK side and APP side because of the inconsistent problem of data.
Description
Technical Field
The invention relates to the technical field of internet, in particular to a data reconciliation system, a method, equipment and a medium.
Background
A Software Development Kit (SDK) is embedded in Application Software (APP) for independent Development or fast access to each functional module in APP.
At present, when embedding the third party SDK in the APP, there is network isolation between the third party server providing service for the third party SDK and the background server providing service for the APP, and for ensuring the data security of the server, both the servers do not have extranet interfaces. For example, the third-party server and the background server of the APP are servers of different companies, such as a third-party server providing payment service and a background server providing transaction platform service.
In this case, an interactive interface is usually built in the SDK according to the calling requirement of the APP, so that when a user operates a specific function in the APP, the user can obtain corresponding data from the third-party server by calling the interactive interface provided by the SDK, and synchronize the data to the background server of the APP via the interactive interface. In the data transmission mode, interactive interface calling failure or data synchronization failure caused by network reasons easily occurs, and the failure phenomena can cause the problem that data of a third-party server and a background server of the APP are inconsistent.
Therefore, how to ensure the data consistency between the third-party SDK side and the APP side becomes a technical problem to be solved urgently in the development scenario of embedding the third-party SDK into the APP at present.
Disclosure of Invention
The embodiment of the invention provides a data reconciliation system, a data reconciliation method, data reconciliation equipment and a data reconciliation medium, which are used for ensuring the data consistency of a third-party SDK side and an APP side.
In a first aspect, an embodiment of the present invention provides a data reconciliation system, where the data reconciliation system includes a reconciliation server, an SDK module of a software development kit accessing the reconciliation server, and a client equipped with the SDK module; wherein
The SDK module is also accessed to a third-party server and is used for acquiring a first reconciliation file to be collated from the third-party server, and the first reconciliation file comprises preset type data; transmitting the first reconciliation file to a reconciliation server according to a preset transmission strategy;
the account checking server is used for storing a first account checking file from the SDK module; responding to a data acquisition request of a client, inquiring a second account checking file corresponding to the data acquisition request from the stored first account checking file, and feeding back the second account checking file to the client;
the client is used for sending a data acquisition request to the account checking server; and receiving a second account checking file fed back by the account checking server, and performing data checking based on the second account checking file.
In a second aspect, an embodiment of the present invention provides a data reconciliation method, where the data reconciliation method is applied to a reconciliation server in a data reconciliation system, the system further includes an SDK module and a client that access the reconciliation server, and the SDK module is further accessed to a third-party server; the method comprises the following steps:
receiving and storing a first reconciliation file to be collated from the SDK module, wherein the first reconciliation file comprises preset type data and is acquired from a third-party server through the SDK module;
and responding to a data acquisition request of the client, inquiring a second account checking file corresponding to the data acquisition request from the stored first account checking file, and feeding back the second account checking file to the client so that the client performs data checking based on the second account checking file.
In a third aspect, an embodiment of the present invention provides a data reconciliation method, where the data reconciliation method is applied to an SDK module in a data reconciliation system; the SDK module also accesses a third party server, wherein
Acquiring a first reconciliation file to be collated from a third-party server, wherein the first reconciliation file comprises preset type data;
and transmitting the first reconciliation file to the reconciliation server according to a preset transmission strategy so that the reconciliation server stores the first reconciliation file.
In a fourth aspect, an embodiment of the present invention provides a data reconciliation method, where the data reconciliation method is applied to a client in a data reconciliation system, and the client is equipped with an SDK module; wherein
Sending a data acquisition request to an account checking server; the data acquisition request is used for enabling the account checking server to respond to the data acquisition request, inquiring a second account checking file corresponding to the data acquisition request from the stored first account checking file, and feeding back the second account checking file to the client;
and receiving a second account checking file fed back by the account checking server, and performing data checking based on the second account checking file.
An embodiment of the present invention provides an electronic device, which includes a processor and a memory, where the memory stores executable code thereon, and when the executable code is executed by the processor, the processor is enabled to implement at least the data reconciliation system in the first aspect.
An embodiment of the present invention provides a non-transitory machine-readable storage medium having stored thereon executable code, which when executed by a processor of an electronic device, causes the processor to implement at least the data reconciliation system of the first aspect.
In the embodiment of the invention, through the cooperation of the reconciliation server, the SDK module and the client, the first reconciliation file to be collated in the third-party server can be obtained and synchronized to the reconciliation server for storage. And then, the account checking server responds to the data acquisition request of the client, inquires a second account checking file corresponding to the data acquisition request from the stored first account checking file, and feeds the second account checking file back to the client. Through the system architecture, a first account checking file to be checked in the third-party server can be synchronized to the account checking server through the SDK module, the account checking file is directly pulled from the account checking server by the client side with the SDK module to perform data checking, an interactive interface between the servers is not required to be called, data transmission time delay can be reduced, user experience of the APP side is improved, the problem of data inconsistency caused by interface calling failure or network data synchronization failure can be avoided, and data consistency of the SDK side and the APP side of the third party is guaranteed.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and those skilled in the art can also obtain other drawings according to the drawings without creative efforts.
Fig. 1 is a flow chart of a structure of a data reconciliation system according to an embodiment of the present invention;
fig. 2 is a schematic flow chart of a data reconciliation method according to an embodiment of the present invention;
fig. 3 is a schematic flow chart of another data reconciliation method according to an embodiment of the present invention;
fig. 4 is a schematic flowchart of another data reconciliation method according to an embodiment of the present invention;
fig. 5 is a schematic structural diagram of an electronic device according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. 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 invention.
The terminology used in the embodiments of the invention is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used in this embodiment of the invention, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise, and "the" generally includes at least two.
The words "if", as used herein, may be interpreted as "at … …" or "at … …" or "in response to a determination" or "in response to a detection", depending on the context. Similarly, the phrases "if determined" or "if detected (a stated condition or event)" may be interpreted as "when determined" or "in response to a determination" or "when detected (a stated condition or event)" or "in response to a detection (a stated condition or event)", depending on the context.
It is also noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a good or system that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such good or system. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a commodity or system that includes the element.
In addition, the sequence of steps in each method embodiment described below is only an example and is not strictly limited.
At present, when embedding the third party SDK in the APP, there is network isolation between the third party server providing service for the third party SDK and the background server providing service for the APP, and for ensuring the data security of the server, both the servers do not have extranet interfaces. For example, the third-party server and the background server of the APP are servers of different companies, such as a third-party server providing payment service and a background server providing transaction platform service.
In this case, an interactive interface is usually built in the SDK according to the calling requirement of the APP, so that when a user operates a specific function in the APP, the user can obtain corresponding data from the third-party server by calling the interactive interface provided by the SDK, and synchronize the data to the background server of the APP via the interactive interface. In the data transmission mode, interactive interface calling failure or data synchronization failure caused by network reasons easily occurs, and the failure phenomena can cause the problem that data of a third-party server and a background server of the APP are inconsistent.
Therefore, how to ensure the data consistency between the third-party SDK side and the APP side becomes a technical problem to be solved urgently in the development scenario of embedding the third-party SDK into the APP at present.
In order to solve at least one technical problem, embodiments of the present invention provide a data reconciliation system, method, device, and medium. The core idea for solving the technical problems in the embodiment of the invention is mainly as follows:
through the cooperation of the account checking server, the SDK module and the client, a first account checking file to be checked in the third-party server can be obtained and is synchronized to the account checking server for storage. And then, the account checking server responds to the data acquisition request of the client, inquires a second account checking file corresponding to the data acquisition request from the stored first account checking file, and feeds the second account checking file back to the client. Through the system architecture, a first account checking file to be checked in the third-party server can be synchronized to the account checking server through the SDK module, the account checking file is directly pulled from the account checking server by the client side with the SDK module to perform data checking, an interactive interface between the servers is not required to be called, data transmission time delay can be reduced, user experience of the APP side is improved, the problem of data inconsistency caused by interface calling failure or network data synchronization failure can be avoided, and data consistency of the SDK side and the APP side of the third party is guaranteed.
Having described the basic concepts of the data reconciliation scheme, various non-limiting embodiments of the present invention are described in detail below.
The data reconciliation scheme provided by the embodiment of the invention is suitable for various service systems. In practical applications, the data reconciliation scheme is suitable for a home service reservation scenario, an online shopping scenario, a company reconciliation scenario, a bank reconciliation scenario, and the like. In these scenarios, assuming that the APP needs to use the service provided by the third-party SDK to implement some functional modules of the APP, the data transmission and the data collation between the third-party SDK side and the APP side can be implemented through the data reconciliation scheme.
The following describes the implementation of the data reconciliation scheme with reference to the following embodiments.
Fig. 1 is a schematic diagram of a data reconciliation system according to an embodiment of the present invention. As shown in fig. 1, the data reconciliation system comprises a reconciliation server 110, an SDK module 120, and a client 130.
The reconciliation server 110 is implemented as a cloud server, and in a specific implementation form, for example, the reconciliation server 110 may be implemented as one or more service devices, may be installed on a cloud (for example, a computer or a server of a reconciliation service management center, a server cluster, etc.) as an application, or may be developed as a website.
The SDK module 120 refers to a software development kit provided by a third-party server, and in a specific implementation form, for example, the software development kit may be distributed to a terminal device side as a configuration file via a client installation package, so that after the installation of the installation package is completed, the SDK module serves as a functional module loaded in a client to provide a corresponding functional service for the client. In practical applications, the SDK module may be a functional module of various types of application software, such as a housekeeping service application, a shipping application, an instant messaging application, and the like. Optionally, the SDK module 120 accesses a third party server, and the SDK module 120 may have data call capability for the third party server.
The client 130 refers to a client on the application software side, and in implementation form, for example, the client 130 may be implemented as an application installed on a terminal device, or as an applet in an instant messaging application.
In implementation, the SDK module 120 and the client 130 are adapted to each other. That is, the reconciliation server 110 is installed on the cloud server, the client 130 can be a client establishing a communication connection with the cloud server, and the SDK module 120 can be a functional module in the client 130.
The following description is made with reference to specific examples, and is directed to various components of the data reconciliation system.
First, the SDK module 120 included in the data reconciliation system is introduced.
Because the SDK module 120 has a data call capability for the third-party server, the SDK module 120 is mainly configured to obtain a first reconciliation file to be collated from the third-party server, and further transmit the first reconciliation file to the reconciliation server according to a preset transmission policy.
In an embodiment of the present invention, the first reconciliation file includes preset type data. Optionally, the preset type data is a data file in a preset format. In practical application, data files with different preset formats and different types of contents in the data files can be set according to actual requirements of different application scenes, so that the data reconciliation requirements under various application scenes can be met.
In the mobile payment scenario, the preset type data includes, for example, payment data, recharge information, bank card information, order information, and the like. In the government scene, the preset type data includes, for example, identity information, government affair data circulation information, and the like.
In some optional embodiments, the preset transmission policy for the SDK module 120 to transmit the first reconciliation file to the reconciliation server may be to automatically trigger a transmission process of the first reconciliation file according to the detected event. The event that automatically triggers the first reconciliation file transmission process may be a timing event, a counting event, or other monitoring event, which is not limited in this embodiment.
If the event is a timing event, a transmission instruction of the first reconciliation file may be issued to the SDK module 120 according to the timing task. Specifically, in a set period of time, a transmission instruction for a certain type of first reconciliation file may be automatically triggered and issued to the SDK module 120. The set period may be periodic or single, and is not limited herein.
For example, in a mobile payment scenario, the reconciliation period is set to five pm daily. At five pm each day, a transmission instruction of the first reconciliation file associated with the mobile payment service may be automatically triggered and issued to the SDK module 120, so that the SDK module 120 uploads the first reconciliation file associated with the mobile payment service to the reconciliation server 110 associated with the mobile payment service according to the transmission instruction. Therefore, the data consistency of the third-party SDK side and the APP side can be further ensured through timing account checking.
In practice, the reconciliation server 110 associated with the mobile payment service is, for example, a reconciliation server corresponding to the SDK module 120 for implementing the mobile payment service functionality. The SDK module 120 for implementing the mobile payment service function is implemented as, for example, a payment popup in an application, a payment interface, and a payment module, which are not limited herein.
If the counting event is a counting event, a transmission instruction of the first reconciliation file may be issued to the SDK module 120 according to a certain counting task. For example, a threshold value of the number of the first reconciliation files of each type is set, when the newly added number of the first reconciliation files of a certain type reaches the set threshold value of the number, a transmission instruction for the newly added first reconciliation files of the type can be automatically triggered, and the transmission instruction is sent to the SDK module 120, so that the SDK module 120 uploads the newly added first reconciliation files of the type to the reconciliation server 110 according to the transmission instruction. Are not listed one by one.
Further, the data reconciliation system further comprises a reconciliation server 110.
The reconciliation server 110 is mainly used for storing a first reconciliation file from the SDK module 120; and responding to the data acquisition request of the client 130, inquiring a second account checking file corresponding to the data acquisition request from the stored first account checking file, and feeding back the second account checking file to the client 130.
In practical applications, the SDK module 120 in communication with the reconciliation server 110 can be piggybacked on one or more clients 130 to implement corresponding functional modules in the clients 130.
Specifically, the SDK module 120 establishes a communication connection with the reconciliation server 110. Thus, after acquiring the first reconciliation file to be collated from the third-party server, the SDK module 120 transmits the first reconciliation file to the reconciliation server 110 via the communication connection. The reconciliation file is uploaded to the reconciliation server 110, for example, by ftp. The method for uploading the reconciliation file is, for example, that the SDK backend server uploads the reconciliation file to the reconciliation server every day at regular time.
In an alternative embodiment, it is assumed that the SDK modules 120 in communication with the reconciliation server 110 are respectively mounted in the plurality of clients 130. Assume that a plurality of first reconciliation files are stored in the reconciliation server 110.
Based on this, the reconciliation server 110 is further configured to configure data acquisition permissions corresponding to the plurality of clients 130; and according to the respective corresponding data acquisition authorities of the plurality of clients 130, a plurality of first reconciliation files fed back by the SDK module are identified.
Further, it is assumed that the SDK modules 120 communicating with the reconciliation server 110 are mounted in the plurality of clients 130, respectively. Assume that a plurality of first reconciliation files are stored in the reconciliation server 110.
Based on this, when the reconciliation server 110 queries the second reconciliation file corresponding to the data acquisition request from the stored first reconciliation file and feeds back the second reconciliation file to the client 130, the method is specifically configured to:
determining a target client 130 corresponding to the data acquisition request from the plurality of clients 130; verifying the data acquisition authority of the target client 130; for the target client 130 that passes the verification, the first reconciliation file that matches the data acquisition permission of the target client 130 is queried from the plurality of first reconciliation files as a second reconciliation file, and the second reconciliation file is fed back to the target client 130.
For example, a corresponding account is opened for each client 130, and a corresponding data acquisition right is configured for the account.
Wherein, in particular, the plurality of clients 130 establish communication connection with the reconciliation server 110. Accordingly, the plurality of clients 130 acquire the second reconciliation file to be collated from the reconciliation server 110 through the communication connection.
Optionally, when the tie-out server 110 determines the target client 130 corresponding to the data obtaining request from the multiple clients 130, the method is specifically configured to:
the client identification information is acquired from the data acquisition request, and the client 130 corresponding to the client identification information among the plurality of clients 130 is taken as the target client 130.
The first reconciliation file matched with the data acquisition permission of the target client 130 includes: and the first account checking file carries the client identification information.
Finally, a client 130 comprised by the data reconciliation system is introduced.
The client 130 is mainly used for sending a data acquisition request to the reconciliation server 110; and receiving a second account checking file fed back by the account checking server, and performing data checking based on the second account checking file.
In some embodiments, when performing data calibration based on the second account calibration file, the client 130 is specifically configured to:
acquiring first data to be collated from the second reconciliation file; judging whether the first data is matched with second data to be corrected in the client 130; and if the first data is matched with the second data, executing the client function corresponding to the first data.
In the above steps, in some embodiments, the preset type data is assumed to be a data file in a preset format. Based on this, when the client 130 acquires the first data to be collated from the second reconciliation file, the method is specifically configured to: and analyzing the first data from the second account checking file based on an analysis rule corresponding to the preset format.
In the data reconciliation system provided by the embodiment, through the cooperation of the reconciliation server, the SDK module and the client, a first reconciliation file to be collated in the third-party server can be acquired and synchronized to the reconciliation server for storage. And then, the account checking server responds to the data acquisition request of the client, inquires a second account checking file corresponding to the data acquisition request from the stored first account checking file, and feeds the second account checking file back to the client. Through the system architecture, a first account checking file to be checked in the third-party server can be synchronized to the account checking server through the SDK module, the account checking file is directly pulled from the account checking server by the client side with the SDK module to perform data checking, an interactive interface between the servers is not required to be called, data transmission time delay can be reduced, user experience of the APP side is improved, the problem of data inconsistency caused by interface calling failure or network data synchronization failure can be avoided, and data consistency of the SDK side and the APP side of the third party is guaranteed.
Fig. 2 is a schematic flow chart of a data reconciliation method according to an embodiment of the present invention. The data reconciliation method is applied to a reconciliation server in a data reconciliation system. The data reconciliation system comprises an SDK module and a client, wherein the SDK module is accessed to a reconciliation server. As shown in fig. 2, the data reconciliation method includes:
201. and receiving and storing a first reconciliation file to be collated from the SDK module.
The first reconciliation file comprises preset type data, and is acquired from the third-party server through the SDK module.
202. And responding to a data acquisition request of the client, inquiring a second account checking file corresponding to the data acquisition request from the stored first account checking file, and feeding back the second account checking file to the client so that the client performs data checking based on the second account checking file.
Optionally, the SDK module is respectively installed in a plurality of clients, and the reconciliation server stores a plurality of first reconciliation files.
When the reconciliation server queries a second reconciliation file corresponding to the data acquisition request from the stored first reconciliation file and feeds the second reconciliation file back to the client, the reconciliation server is specifically configured to:
determining a target client corresponding to the data acquisition request from a plurality of clients; verifying the data acquisition authority of the target client; and for the target client side passing the verification, inquiring the first account-checking file matched with the data acquisition permission of the target client side from the plurality of first account-checking files to serve as a second account-checking file, and feeding back the second account-checking file to the target client side.
Optionally, when the tie-out server determines the target client corresponding to the data obtaining request from the multiple clients, the tie-out server is specifically configured to:
acquiring client identification information from the data acquisition request, and taking a client corresponding to the client identification information in the plurality of clients as a target client; the first reconciliation file matched with the data acquisition permission of the target client comprises: and the first account checking file carries the client identification information.
Optionally, the reconciliation server is further configured to configure data acquisition permissions corresponding to the plurality of clients; and according to the data acquisition permission corresponding to the plurality of clients, a plurality of first reconciliation files fed back by the SDK module are identified.
Fig. 3 is a schematic flow chart of another data reconciliation method according to an embodiment of the present invention. The data reconciliation method is applied to an SDK module in a data reconciliation system. The data reconciliation system also comprises a reconciliation server and a client terminal accessed to the reconciliation server. The SDK module also accesses a third party server. As shown in fig. 3, the data reconciliation method includes:
301. and acquiring a first reconciliation file to be collated from the third-party server, wherein the first reconciliation file comprises preset type data.
302. And transmitting the first reconciliation file to a reconciliation server according to a preset transmission strategy so that the reconciliation server stores the first reconciliation file.
Fig. 4 is a flowchart illustrating a further data reconciliation method according to an embodiment of the present invention. The data reconciliation method is applied to the client in the data reconciliation system. The data reconciliation system also comprises a reconciliation server and an SDK module accessed to the reconciliation server. The SDK module also accesses a third party server. As shown in fig. 3, the data reconciliation method includes:
401. and sending a data acquisition request to the account checking server.
The data acquisition request is used for enabling the account checking server to respond to the data acquisition request, inquiring a second account checking file corresponding to the data acquisition request from the stored first account checking file, and feeding back the second account checking file to the client.
402. And receiving a second account checking file fed back by the account checking server, and performing data checking based on the second account checking file.
Optionally, when the client performs data calibration based on the second reconciliation file, the client is specifically configured to: acquiring first data to be collated from the second reconciliation file; judging whether the first data is matched with second data to be collated in the client; and if the first data is matched with the second data, executing the client function corresponding to the first data.
Optionally, the preset type data is a data file in a preset format. When the client acquires the first data to be collated from the second reconciliation file, the client is specifically configured to: and analyzing the first data from the second account checking file based on an analysis rule corresponding to the preset format.
In the data reconciliation method provided by the embodiment, through the cooperation of the reconciliation server, the SDK module and the client, the first reconciliation file to be collated in the third-party server can be acquired and synchronized to the reconciliation server for storage. And then, the account checking server responds to the data acquisition request of the client, inquires a second account checking file corresponding to the data acquisition request from the stored first account checking file, and feeds the second account checking file back to the client. Through the system architecture, a first account checking file to be checked in the third-party server can be synchronized to the account checking server through the SDK module, the account checking file is directly pulled from the account checking server by the client side with the SDK module to perform data checking, an interactive interface between the servers is not required to be called, data transmission time delay can be reduced, user experience of the APP side is improved, the problem of data inconsistency caused by interface calling failure or network data synchronization failure can be avoided, and data consistency of the SDK side and the APP side of the third party is guaranteed.
The following devices may execute the systems or methods provided in the foregoing embodiments, and details of the embodiments may refer to the related descriptions of the foregoing embodiments, which are not repeated herein.
In one possible design, the structure of the data reconciliation system described above in FIG. 1 may be implemented as an electronic device.
As shown in fig. 5, the electronic device may include: a processor 21 and a memory 22. Wherein the memory 22 has stored thereon executable code which, when executed by the processor 21, at least makes the processor 21 capable of implementing the data reconciliation method as provided in the previous embodiments. The electronic device may further include a communication interface 23 for communicating with other devices or a communication network.
In addition, an embodiment of the present invention provides a non-transitory machine-readable storage medium having stored thereon executable code, which, when executed by a processor of a wireless router, causes the processor to execute the data reconciliation method provided in the foregoing embodiments.
The above-described apparatus embodiments are merely illustrative, wherein the various modules illustrated as separate components may or may not be physically separate. 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.
Through the above description of the embodiments, those skilled in the art will clearly understand that each embodiment can be implemented by adding a necessary general hardware platform, and of course, can also be implemented by a combination of hardware and software. With this understanding in mind, the above-described aspects may well be embodied in the form of a computer program product, which may be embodied on one or more computer-usable storage media having computer-usable program code embodied therein (including, but not limited to, disk storage, CD-ROM, optical storage, etc.).
Finally, it should be noted that: the above examples are only intended to illustrate the technical solution of the present invention, but not to limit it; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions of the embodiments of the present invention.
Claims (11)
1. A data reconciliation system is characterized by comprising a reconciliation server, an SDK (software development kit) module accessed to the reconciliation server, and a client loaded with the SDK module; wherein
The SDK module is also accessed to a third-party server, and is used for acquiring a first reconciliation file to be collated from the third-party server, wherein the first reconciliation file comprises preset type data; transmitting the first reconciliation file to the reconciliation server according to a preset transmission strategy;
the reconciliation server is used for storing the first reconciliation file from the SDK module; responding to a data acquisition request of the client, inquiring a second account checking file corresponding to the data acquisition request from the stored first account checking file, and feeding back the second account checking file to the client;
the client is used for sending the data acquisition request to the reconciliation server; and receiving the second account checking file fed back by the account checking server, and performing data checking based on the second account checking file.
2. The system according to claim 1, wherein the SDK module is respectively installed in a plurality of clients, and the reconciliation server stores a plurality of first reconciliation files;
when the reconciliation server queries a second reconciliation file corresponding to the data acquisition request from the stored first reconciliation file and feeds back the second reconciliation file to the client, the reconciliation server is specifically configured to:
determining a target client corresponding to the data acquisition request from a plurality of clients;
verifying the data acquisition authority of the target client;
and for the target client which passes the verification, inquiring a first account-checking file matched with the data acquisition permission of the target client from the plurality of first account-checking files to serve as the second account-checking file, and feeding back the second account-checking file to the target client.
3. The system according to claim 2, wherein when the reconciliation server determines the target client corresponding to the data acquisition request from the plurality of clients, the reconciliation server is specifically configured to:
acquiring client identification information from the data acquisition request, and taking a client corresponding to the client identification information in a plurality of clients as the target client;
the first reconciliation file matched with the data acquisition permission of the target client comprises: and the first reconciliation file carries the client identification information.
4. The system of claim 2, wherein the reconciliation server is further configured to configure data acquisition permissions corresponding to the plurality of clients; and are
And identifying the plurality of first reconciliation files fed back by the SDK module according to the data acquisition authorities corresponding to the plurality of clients respectively.
5. The system of claim 1, wherein the client, when performing data verification based on the second reconciliation file, is specifically configured to:
acquiring first data to be collated from the second reconciliation file;
judging whether the first data is matched with second data to be collated in the client;
and if the first data is matched with the second data, executing a client function corresponding to the first data.
6. The system according to claim 5, wherein the preset type data is a data file with a preset format;
when the client acquires the first data to be collated from the second reconciliation file, the client is specifically configured to:
and analyzing the first data from the second reconciliation file based on an analysis rule corresponding to a preset format.
7. A data reconciliation method is characterized in that the method is applied to a reconciliation server in a data reconciliation system, the system also comprises an SDK module and a client which are accessed to the reconciliation server, and the SDK module is also accessed to a third-party server; the method comprises the following steps:
receiving and storing a first reconciliation file to be collated from the SDK module, wherein the first reconciliation file comprises preset type data, and the first reconciliation file is acquired from a third-party server through the SDK module;
responding to a data acquisition request of the client, inquiring a second account registration file corresponding to the data acquisition request from the stored first account registration file, and feeding back the second account registration file to the client, so that the client performs data proofreading based on the second account registration file.
8. A data reconciliation method is characterized in that the method is applied to an SDK module in a data reconciliation system; the SDK module is also accessed to a third party server, wherein
Acquiring a first reconciliation file to be collated from a third-party server, wherein the first reconciliation file comprises preset type data;
and transmitting the first reconciliation file to the reconciliation server according to a preset transmission strategy so that the reconciliation server stores the first reconciliation file.
9. A data reconciliation method is characterized in that the method is applied to a client in a data reconciliation system, and the client is provided with an SDK module; wherein
Sending a data acquisition request to an account checking server; the data acquisition request is used for enabling the reconciliation server to respond to the data acquisition request, inquiring a second reconciliation file corresponding to the data acquisition request from the stored first reconciliation file, and feeding back the second reconciliation file to the client;
and receiving the second account checking file fed back by the account checking server, and performing data checking based on the second account checking file.
10. An electronic device, comprising: a memory, a processor; wherein the memory has stored thereon executable code which, when executed by the processor, causes the processor to perform the data reconciliation system of any of claims 1 to 6.
11. A readable storage medium, characterized in that a computer program is enabled to implement the data reconciliation system of any one of claims 1-6 when executed.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110057573.8A CN112783845B (en) | 2021-01-15 | 2021-01-15 | Data reconciliation system, method, device and medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110057573.8A CN112783845B (en) | 2021-01-15 | 2021-01-15 | Data reconciliation system, method, device and medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112783845A true CN112783845A (en) | 2021-05-11 |
| CN112783845B CN112783845B (en) | 2023-04-07 |
Family
ID=75756617
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110057573.8A Active CN112783845B (en) | 2021-01-15 | 2021-01-15 | Data reconciliation system, method, device and medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112783845B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113421163A (en) * | 2021-07-13 | 2021-09-21 | 北京沃东天骏信息技术有限公司 | Account checking method, account checking application cluster and related client |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2016062199A1 (en) * | 2014-10-21 | 2016-04-28 | 阿里巴巴集团控股有限公司 | Method, apparatus, client, server, and system for checking security of account |
| CN110599354A (en) * | 2019-08-15 | 2019-12-20 | 中国平安财产保险股份有限公司 | Online reconciliation method, system, computer device and computer-readable storage medium |
| CN111163155A (en) * | 2019-12-26 | 2020-05-15 | 深圳乐信软件技术有限公司 | Account checking file transmission method, account checking file transmission system, account checking file transmission server and storage medium |
| CN112035665A (en) * | 2020-08-31 | 2020-12-04 | 京东数字科技控股股份有限公司 | Account checking file generating and acquiring method, device, system and server |
-
2021
- 2021-01-15 CN CN202110057573.8A patent/CN112783845B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2016062199A1 (en) * | 2014-10-21 | 2016-04-28 | 阿里巴巴集团控股有限公司 | Method, apparatus, client, server, and system for checking security of account |
| CN110599354A (en) * | 2019-08-15 | 2019-12-20 | 中国平安财产保险股份有限公司 | Online reconciliation method, system, computer device and computer-readable storage medium |
| CN111163155A (en) * | 2019-12-26 | 2020-05-15 | 深圳乐信软件技术有限公司 | Account checking file transmission method, account checking file transmission system, account checking file transmission server and storage medium |
| CN112035665A (en) * | 2020-08-31 | 2020-12-04 | 京东数字科技控股股份有限公司 | Account checking file generating and acquiring method, device, system and server |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113421163A (en) * | 2021-07-13 | 2021-09-21 | 北京沃东天骏信息技术有限公司 | Account checking method, account checking application cluster and related client |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112783845B (en) | 2023-04-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10812314B2 (en) | Methods and apparatuses for pushing a message | |
| WO2019024161A1 (en) | Block chain-based data management method, block chain system, server and readable storage medium | |
| CN109783249B (en) | Platform access method and device, terminal and computer readable storage medium | |
| CN111355752A (en) | File transmission method, device and equipment based on gatekeeper | |
| CN112953745B (en) | Service calling method, system, computer device and storage medium | |
| CN112783845B (en) | Data reconciliation system, method, device and medium | |
| CN109241712B (en) | Method and device for accessing file system | |
| CN112651044B (en) | Business transaction method, system and storage medium based on block chain technology | |
| CN113904847A (en) | Cloud platform binding method, system, equipment and medium of Internet of things card | |
| CN107707939B (en) | Video access method, access balance server, central server and system | |
| CN108696864B (en) | Virtual number request and transmission method, device and storage medium | |
| CN115242433B (en) | Data processing method, system, electronic device and computer readable storage medium | |
| US9723436B2 (en) | Mobile device location | |
| US10742802B2 (en) | Methods and devices for verifying a communication number | |
| CN114915454A (en) | Data acquisition method and system | |
| CN114048457A (en) | Multi-platform user relationship creation method, device, system and storage medium | |
| CN111383003B (en) | Method, device, computer equipment and storage medium for fast platform access | |
| CN113596600A (en) | Security management method, device, equipment and storage medium for live broadcast embedded program | |
| CN116467062A (en) | Block chain-based data processing method, equipment and readable storage medium | |
| CN107528797B (en) | Data processing method, device and system | |
| CN107566211B (en) | Method, device and system for accessing test equipment | |
| CN114567509B (en) | Web application access system and method | |
| CN111552907A (en) | Message processing method, device, equipment and storage medium | |
| CN114302349B (en) | Method and system for extracting number by client | |
| CN115134405B (en) | Data processing method and device, electronic equipment and computer readable storage medium |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |