CN117333296A - Cross-system data synchronization method, device, equipment and storage medium - Google Patents

Abstract

The invention discloses a cross-system data synchronization method, a device, equipment and a storage medium. The invention relates to the technical field of big data. The method comprises the following steps: determining target transaction data corresponding to the transaction request in response to the transaction request; invoking tradable data of a transaction account to which the transaction request belongs in a first system; under the condition that the tradable data does not meet the target transaction data, floating data of at least one second account bound with the transaction account is acquired; when the preset condition is detected to be met, processing the transaction request based on the floating data, the tradable data and the target transaction data, and synchronously updating the tradable data of the transaction account and the associated floating data based on the data processing result. According to the technical scheme, the transaction efficiency can be improved, the cost is reduced, and the technical effect of user transaction experience is further improved.

Description

Cross-system data synchronization method, device, equipment and storage medium

Technical Field

The embodiment of the invention relates to the technical field of big data, in particular to a cross-system data synchronization method, device, equipment and storage medium.

Background

With the development of internet financial management, financial projects are increasingly abundant, and many users establish corresponding accounts in a fund management system so as to realize fund management based on the accounts. In the process of carrying out funds management based on accounts, some transaction demands exist, funds in corresponding accounts can be used for settlement at the moment, and when settlement is carried out, the situation that funds in transaction accounts cannot meet the transaction demands possibly exists, and the account data in other funds management systems are generally used for subsidy settlement.

At present, the payment settlement mode is generally to transfer account data in another fund management system into account data of the current fund management system when the account data in the current fund management system cannot finish settlement, and then perform transaction settlement. The method is complex in steps, and has the problems of low transaction efficiency and high cost.

Disclosure of Invention

The embodiment of the invention provides a cross-system data synchronization method, a device, equipment and a storage medium, so that cross-system transaction processing is realized, the transaction efficiency is improved, the cost is reduced, the consistency and the accuracy of data among systems are ensured, and the technical effect of improving the user transaction experience is achieved.

In a first aspect, an embodiment of the present invention provides a method for synchronizing data across systems, where the method includes:

determining target transaction data corresponding to a transaction request in response to the transaction request;

invoking tradable data of a transaction account to which the transaction request belongs in a first system;

acquiring floating data of at least one second account bound with the transaction account under the condition that the target transaction data is not met by the tradable data, wherein the at least one second account is an account in a second system, and the floating data is data recorded in the transaction account;

when the preset condition is detected to be met, the transaction request is processed based on the floating data, the tradable data and the target transaction data, and the tradable data of the transaction account and the associated floating data are synchronously updated based on a data processing result.

In a second aspect, an embodiment of the present invention further provides a cross-system data synchronization apparatus, where the apparatus includes:

a target transaction data determining module for determining target transaction data corresponding to a transaction request in response to the transaction request;

The transaction request comprises a transaction request, a transaction data retrieving module and a transaction data retrieving module, wherein the transaction request comprises transaction data of a transaction account to which the transaction request belongs in a first system;

the floating data acquisition module is used for acquiring floating data of at least one second account bound with the transaction account under the condition that the target transaction data is not met by the tradable data, wherein the at least one second account is an account in a second system, and the floating data is data recorded in the transaction account;

and the transaction processing module is used for processing the transaction request based on the floating data, the tradable data and the target transaction data when the condition that the preset condition is met is detected, and synchronously updating the tradable data of the transaction account and the associated floating data based on a data processing result.

In a third aspect, an embodiment of the present invention further provides an electronic device, including a memory, a processor, and a computer program stored on the memory and capable of running on the processor, where the processor implements a cross-system data synchronization method according to any one of the embodiments of the present invention when the processor executes the program.

In a fourth aspect, embodiments of the present invention further provide a computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements a method for cross-system data synchronization according to any of the embodiments of the present invention.

In a fifth aspect, embodiments of the present invention also provide a computer program product comprising a computer program which, when executed by a processor, implements a method of cross-system data synchronization according to any of the embodiments of the present invention.

In the embodiment of the invention, the target transaction data corresponding to the transaction request is determined, so that the tradable data of the transaction account to which the transaction request belongs in the first system is called; under the condition that the tradable data does not meet the target transaction data, floating data of at least one second account bound with the transaction account is obtained, wherein the at least one second account is an account in a second system, and the floating data is data recorded in the transaction account; when the fact that the preset condition is met is detected, the transaction request is processed based on the floating data, the tradable data and the target transaction data, the tradable data of the transaction account and the associated floating data are synchronously updated based on the data processing result, the problems that in the prior art, account data interaction is needed among systems during the payment settlement, the transaction efficiency is low and the cost is high are solved, the fact that the floating data of the second account in the second system are recorded in the transaction account of the first system, the transaction requirement is not met when the transaction account is not met, the recorded floating data are used for payment settlement, when the transaction processing is carried out among systems, the account data interaction among the systems is avoided, the transaction cost is reduced, the transaction efficiency is improved, and the user transaction experience is improved. Meanwhile, based on the data processing result, the tradable data of the transaction account and the associated floating data are synchronously updated, and the consistency and the accuracy of the data are ensured.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings that are needed in the embodiments will be briefly described below, it being understood that the following drawings only illustrate some embodiments of the present invention and therefore should not be considered as limiting the scope, and other related drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

FIG. 1 is a flow chart of a cross-system data synchronization method provided in accordance with an embodiment of the present invention;

FIG. 2 is a flow chart of a cross-system data synchronization method provided in accordance with an embodiment of the present invention;

FIG. 3 is a flow chart of a cross-system data synchronization method provided in accordance with an embodiment of the present invention;

FIG. 4 is a flow chart of a cross-system data synchronization method provided in accordance with an embodiment of the present invention;

FIG. 5 is a schematic diagram of a cross-system data synchronization device according to an embodiment of the present invention;

fig. 6 is a schematic structural diagram of an electronic device implementing a cross-system data synchronization method according to an embodiment of the present invention.

Detailed Description

The invention is described in further detail below with reference to the drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting thereof. It should be further noted that, for convenience of description, only some, but not all of the structures related to the present invention are shown in the drawings.

It should be noted that: like reference numerals and letters denote like items in the following figures, and thus once an item is defined in one figure, no further definition or explanation thereof is necessary in the following figures. Meanwhile, in the description of the present invention, the terms "first", "second", and the like are used only to distinguish the description, and are not to be construed as indicating or implying relative importance. The data acquisition, storage, use, processing and the like in the technical scheme meet the relevant regulations of national laws and regulations.

Before the present technical solution is introduced, an application scenario may be illustrated. For example, in an actual transaction scenario, the data under the account in the current funds management system may be used to conduct a transaction, and if the data is not able to meet the transaction requirements, the data under the account in the other funds management system may be used to conduct the subsidy settlement, where the current funds management system may be used as the first system, the account under the first system may be used as the transaction account, the other funds management system may be used as the second system, and the account under the second system may be used as the second account, i.e., the first system and the second system are relatively speaking. For example, the first system is a debit card system, and the transaction account underneath may be a debit card current account; the second system is a financial system, and the second account below the second system can be a financial and warehouse-holding account. When the data in the transaction account in the first system can not meet the transaction requirement, the technical scheme provided by the embodiment of the invention can be adopted to implement in order to ensure that the transaction can be successfully completed.

Fig. 1 is a flowchart of a cross-system data synchronization method provided according to an embodiment of the present invention, where the present embodiment is applicable to a case of performing transaction processing across systems, the method may be performed by a cross-system data synchronization device, and the cross-system data synchronization device may be implemented in a form of hardware and/or software. As shown in fig. 1, the method includes:

s110, in response to the transaction request, determining target transaction data corresponding to the transaction request.

Wherein the transaction request may be a program or code for requesting settlement of the transaction.

In this embodiment, a user may initiate a transaction request through a platform or a terminal, and request to use account data of a transaction account in the first system to perform transaction settlement, where the first system is considered to receive the transaction request, that is, to respond to the transaction request. For example, when a user initiates order settlement on an order platform (e.g., shopping, ticketing, hotel reservation, etc.), a transaction request is generated and sent to a first system; or, after identifying the debit card information by using a card reader (such as a POS terminal), generating a transaction request, and sending the transaction request to a first system to which the debit card belongs. When a transaction request is received, the transaction request is analyzed, and target transaction data carried in the transaction request is obtained through analysis. Optionally, the target transaction data includes, but is not limited to, transaction amount, transaction period, transaction amount, settlement account, settlement system, transaction type, etc., so as to perform subsequent transaction operation through the target transaction data.

S120, the tradable data of the transaction account to which the transaction request belongs in the first system is called.

In the actual fund management process, the user can open a transaction account in the first system according to the self demand, deposit corresponding funds in the transaction account, manage the funds based on the first system, and can carry out transaction settlement through the funds under the transaction account, and after settlement, the funds of the transaction account change correspondingly. Funds under the transaction account are the tradable data.

Specifically, when the transaction request is received, the transaction account corresponding to the transaction account identifier is searched from the first system through the transaction account identifier carried in the transaction request, and then the tradable data in the transaction account is called, so that whether the transaction is sufficiently settled or not by using the transaction account is judged through the tradable data.

S130, under the condition that the tradable data does not meet the target transaction data, floating data of at least one second account bound with the transaction account is acquired.

Wherein the at least one second account is an account in the second system and the floating data is data recorded in the transaction account. The float data corresponds to a product held by the second account, and the float data may be determined from a value attribute of the product held by the second account for characterizing a value of the product held by the second account. The floating data is positively correlated with the attributes of the product, for example, the unit price, the yield and other attributes of the product are increased, and the floating data is also increased; the unit price, yield and other attributes of the product are reduced, and the floating data are also reduced.

In practical application, the tradable data and the target transaction data can be compared, if the tradable data is not smaller than the target transaction data, the tradable data is enough to settle the transaction, and the transaction settlement can be performed by using only the tradable data; if the tradable data is less than the target transaction data, it is indicated that the tradable data is insufficient to settle the transaction, i.e., the target transaction data is not satisfied by the tradable data, in which case floating data of at least one second account recorded under the transaction account may be obtained to determine whether settlement is enabled by the floating data.

And S140, when the fact that the preset condition is met is detected, processing the transaction request based on the floating data, the tradable data and the target transaction data, and synchronously updating the tradable data of the transaction account and the associated floating data based on the data processing result.

The preset condition may be a precondition to be satisfied by executing a transaction operation, for example, there is a right to use floating data, and for example, the floating data reaches the data to be refunded.

In this embodiment, data to be detected may be acquired, and the data may be detected according to a preset condition, so as to perform a transaction operation when the preset condition is satisfied. Optionally, the preset condition includes at least one of: invoking authorization information of the data from the floating data; feedback is received to retrieve at least a portion of the floating data. The first system can conduct financial and money-supplementing subscription processing, and can bind with the second account in the second system, and when subscription is successful, the user is authorized to call data from the floating data. Based on this, before the tradable data does not satisfy the target transaction data and the transaction is executed, whether authorization information for calling data from the floating data exists or not can be checked, and if so, the detection result is determined to satisfy the preset condition; or when feedback allowing at least part of floating data to be called is received, determining that the detection result meets the preset condition.

According to the technical scheme provided by the invention, whether the authorization information for calling the data from the floating data is contained or not is verified before the transaction operation is executed, so that the use of resources by a user can be controlled through the authorization information, the use of the floating data under the condition of user authorization is ensured, the subsequent use of the floating data is facilitated, and the transaction efficiency and experience are improved. The benefit of verifying whether feedback is received to retrieve at least part of the floating data is that it is not only ensured that the floating data is used with the user's knowledge, but that the retrieved floating data is user-friendly.

On the basis of the technical scheme, the floating data and the tradable data can be used for carrying out transaction settlement on the target transaction data under the condition that the preset condition is detected to be met, for example, the target transaction data is 100, the tradable data is 80, less than 100, the floating data is 150 and more than 100, and the floating data can be used for carrying out settlement only or part of the floating data can be taken for carrying out settlement on the basis of the tradable data. Still further, specific data processing results, such as how much of an account was used, whether the transaction was successful or unsuccessful, etc., are generated after the transaction is processed. The tradable data of the transaction account and the associated floating data may be synchronously updated according to the data processing results, e.g., 80 for tradable data prior to the transaction, and 0 for tradable data if 80 is used for the transaction.

In order to improve the user transaction experience and ensure the interests of the user, the method can monitor the related information of the products corresponding to the floating data in real time or periodically, such as the unit price fluctuation trend, the yield and the like of the products, further can update the floating data of the products in real time through the information, and can select the floating data of the proper products for transaction settlement according to the information before the floating data is used for transaction.

Based on the technical scheme, the cross-system data synchronization method further comprises the following steps: acquiring the attribute of a product corresponding to the floating data; and feeding back whether to invoke the scheduling prompt of the floating data to the client based on the change trend in the preset duration in the attribute so as to determine feedback based on the triggering operation of the scheduling prompt.

It should be noted that different products may have the same and/or different product attributes including, but not limited to, unit price, investment period, rate of return, risk, etc., and products including, but not limited to, funds, stocks, foreign exchange, futures, etc. The preset time length can be determined according to the attribute of the product, or can be determined by a technician according to the actual working condition, and is not limited herein.

Specifically, the attribute of the product corresponding to the floating data is obtained, the change trend of the attribute in the preset duration is analyzed, the analysis result can be displayed on the client in the form of prompt information, and whether the scheduling prompt of the floating data is called or not is fed back to the client. For example, assuming that the product is fund a, for a certain product, the rate of return for a plurality of consecutive days may be obtained, and whether the trend of change increases or decreases is determined based on the plurality of rates of return; alternatively, future profitability or a trend of change in profitability may be predicted in combination with a plurality of profitability. The change trend can be prompted to a client user for the user to select a proper product, or the system is automatically determined in combination with the change trend. Further, the user can trigger a corresponding scheduling prompt by using the input device, and select which product's floating data to use, so that after the system receives feedback of invoking the selected floating data, transaction settlement is performed based on the floating data. According to the technical scheme provided by the invention, the change trend of the product attribute within the preset time is fed back to the client user, so that the user can conveniently combine with the self demand, whether floating data is called or not is fed back according to the change trend, and the rights and interests of the user can be ensured.

According to the method, target transaction data corresponding to the transaction request are determined, so that the tradable data of the transaction account to which the transaction request belongs in the first system is called; under the condition that the tradable data does not meet the target transaction data, floating data of at least one second account bound with the transaction account is obtained, wherein the at least one second account is an account in a second system, and the floating data is data recorded in the transaction account; when the fact that the preset condition is met is detected, the transaction request is processed based on the floating data, the tradable data and the target transaction data, the tradable data of the transaction account and the associated floating data are synchronously updated based on the data processing result, the problems that in the prior art, account data interaction is needed among systems during the payment settlement, the transaction efficiency is low and the cost is high are solved, the fact that the floating data of the second account in the second system are recorded in the transaction account of the first system, the transaction requirement is not met when the transaction account is not met, the recorded floating data are used for payment settlement, when the transaction processing is carried out among systems, the account data interaction among the systems is avoided, the transaction cost is reduced, the transaction efficiency is improved, and the user transaction experience is improved. Meanwhile, based on the data processing result, the tradable data of the transaction account and the associated floating data are synchronously updated, and the consistency and the accuracy of the data are ensured.

Based on the above embodiment, before determining the target transaction data corresponding to the transaction request in response to the transaction request, the target field of the transaction account in the first system may be synchronously updated by the floating data of at least one second account in the second system, so as to ensure the data synchronization between the two systems, and correspondingly, the invention proposes the following embodiments: fig. 2 is a flowchart of a cross-system data synchronization method according to an embodiment of the present invention. As shown in fig. 2, the data synchronization method across systems includes the following steps:

s210, floating data of at least one second account in the second system is determined.

The second account may be a financial product account, for example, a corresponding financial product may be purchased according to a product contract through funds under the second account, and the funds are managed through the product.

In this embodiment, the value of the product held by the second account may be determined as the floating data by the attribute of the product held by at least one second account in the second system. For example, if 100 products are held and the unit price is 10, the floating data is 1000, which is only one credit value.

S220, determining and binding the transaction account bound with at least one second account, and synchronizing floating data corresponding to the second account into a target field of the transaction account.

Specifically, the transaction account in the first system and the selected second account in the second system can be bound according to the transaction requirement of the user, after the binding is successful, floating data corresponding to the product held by the second account can be synchronized into the target field of the transaction account, and the floating data is recorded through the target field. For example, when the user uses the second account to buy the product in the second system, the financial and the money-making subscription processing is synchronously performed in the first system, and after the subscription is successful, the transaction account and the second account are considered to be mutually bound, so that when the balance of the transaction account is insufficient, the floating data can be automatically used for money-making settlement.

It should be noted that, when the financial and reimbursement subscription is successful, the floating data in the first system can be initially set to 0, and then the floating data in the first system is adjusted through the current product information held by the second account. The floating data in the first system may be dynamically adjusted subsequently when the product held by the second account changes. For example, if product information adjustment occurs in the second account in the second system, such as adding a holding, redeeming a product, or generating a equity, etc., floating data synchronization processing is performed on the first system, so that floating data under a target field of a transaction account in the first system is adjusted to keep synchronization with a product value under the second account in the second system.

In this embodiment, further comprising: and if the floating data corresponding to the at least one second account is detected to be changed, updating the floating data of the transaction account target field based on the changed floating data.

For example, after a customer purchases a financial product at the second system and confirms, the floating data recorded in the first system may be synchronized by an online or batch process. When the customer actively initiates the product to be transferred or redeemed in the second system, the floating data recorded in the first system can be called by an on-line service mode, and then the product warehouse-holding information of the second system can be called. When the customer takes a warehouse in the second system to generate the flushing, the flushing adjustment is carried out daily due to the large data volume, so that the floating data can be synchronized in a batch processing mode. According to the technical scheme provided by the invention, when the transmission change of the floating data corresponding to the second account is detected, the floating data of the target field of the transaction account is updated in time, so that the data synchronization among the cross systems is effectively ensured, the transaction accuracy is improved, and the transaction error is prevented.

In order to ensure that the floating data of the second account can be directly obtained from the transaction account under the first system, the floating data of the second account can be recorded by the transaction account and recorded in a field of the transaction account so as to obtain the floating data from the field. Acquiring floating data of at least one second account bound to the transaction account, comprising: float data of at least one second account recorded under a target field of the transaction account is obtained.

In this embodiment, the destination field may have a unique name corresponding to the floating data of the second account. For example, the target field may be represented by "product value", "Available credit", or "Available limit", or the like. The float data for the at least one second account recorded under the target field may be looked up from under the transaction account via the target field.

According to the method, at least one second account and the transaction account are bound, floating data corresponding to products held by the second account are synchronized to the target field of the transaction account, so that the value of the products can be monitored through the first system, floating data are called to carry out money compensation when the transaction account does not meet the transaction requirement, the transaction requirement of a user is met, the transaction efficiency is improved, and meanwhile, the consistency and accuracy of data among cross systems are guaranteed through a synchronous processing mode.

Based on the above embodiment, when the transaction request is processed based on the floating data, the tradable data and the target transaction data, the difference data may be determined by the target transaction data and the tradable data, and then the floating data is adjusted according to the difference data, so as to obtain a data processing result corresponding to the transaction request, so that the tradable data of the transaction account and the associated floating data are synchronously updated based on the data processing result, and accordingly, the present invention proposes the following embodiments: fig. 3 is a flowchart of a cross-system data synchronization method according to an embodiment of the present invention. As shown in fig. 3, the data synchronization method across systems includes the following steps:

S310, determining difference data according to the target transaction data and the tradable data.

Specifically, difference processing can be performed on the target transaction data and the tradable data, and the obtained difference is difference data, wherein the difference data can reflect the information of using floating data for compensation. For example, the target transaction data is 100, the tradable data is 80, and the difference data is 100-80=20.

S320, adjusting the floating data according to the difference data to obtain a data processing result corresponding to the transaction request.

In this embodiment, when the tradable data does not satisfy the target transaction data, the tradable data and the floating data may be used for the transaction. And (3) for the part which is not satisfied by the tradable data, namely the balance data, settling can be carried out by using the floating data, correspondingly, on the basis of the original floating data, carrying out corresponding deduction on the balance, and adjusting the floating data recorded in the first system. For example, the difference data is 20, the floating data is 150, and after the 20 in 150 is used for the refund, the floating data is adjusted to 130.

In order to ensure the accuracy of floating data adjustment and prevent the situation of unused adjustment, when the floating data is adjusted according to the difference data to obtain a data processing result corresponding to the transaction request, whether the floating data contains the difference data or not can be judged, so that the data adjustment is performed under the condition of containing the difference data. The specific implementation mode of the method can be as follows: if the floating data contains difference data, adjusting the data value of the floating data; if the floating data does not contain the difference data, the feedback data processing result is a failure processing result.

In practical application, the floating data and the differential data can be compared, whether the floating data is larger than or equal to the differential data is judged, if yes, the floating data is considered to contain the differential data, and the floating data can be used for compensation transaction at the moment, and the data value of the floating data is correspondingly reduced. If not, the floating data is considered to not contain difference data, the floating data cannot be used for the refund transaction at the moment, the data value of the floating data is not adjusted, the transaction processing is failed at the moment, and the failed processing result can be fed back to the user as the data processing result, so that the user can know the specific situation of the transaction in time.

Based on the technical scheme, in order to improve the transaction safety, when the comparison verification of the difference data and the floating data is performed based on the first system, the comparison verification of the second system on the difference data and the floating data can be increased, and then whether the transaction processing is performed or not is determined based on the comparison verification result of the difference data and the floating data. For example, when the floating data recorded by the self system is verified based on the first system to include the difference data, and the floating data under the self system is verified based on the second system to include the difference data, the comparison verification is considered to be successful, and the floating data can be used for the compensation settlement at this time, and the data processing result is a successful processing result. When the floating data recorded by the self system is verified based on the first system and the floating data under the self system is verified based on the second system, the comparison verification is considered to be failed, the data between the two systems is asynchronous, the floating data recorded in the first system can be automatically adjusted to 0, the floating data cannot be used for the compensation settlement, the data processing result is a failure processing result, and the floating data is reset to be correct after the manual intervention is confirmed.

According to the embodiment, the difference data is determined according to the target transaction data and the tradable data, so that the floating data is adjusted according to the difference data, the accuracy of the floating data is guaranteed, and transaction errors are avoided.

Based on the above embodiment, when the tradable data of the transaction account and the associated floating data are synchronously updated based on the data processing result, the tradable data of the transaction account in the first system and the floating data of the target field in the transaction account may be updated, and further, based on the asynchronous message queue, the balance data, the transaction flow information corresponding to the transaction request and the transaction account are sent to the second system corresponding to the at least one second account, so that the second system updates the floating data corresponding to the second account based on the balance data, the transaction flow information and the transaction account, and accordingly, the present invention proposes the following embodiments: fig. 4 is a flowchart of a cross-system data synchronization method according to an embodiment of the present invention. As shown in fig. 4, the data synchronization method across systems includes the following steps:

s410, updating tradable data of a transaction account in the first system based on the data processing result, and updating floating data of a target field in the transaction account.

In this embodiment, if the data processing result is a failure processing result, no adjustment is made on the tradable data of the transaction account in the first system and the floating data of the target field in the transaction account; if the data processing result is a successful processing result, representing that the transaction settlement is successful, updating the tradable data of the transaction account in the first system through the result data of the transaction, and the floating data of the target field in the transaction account, wherein the amount of the tradable data is used, the amount of the tradable data is adjusted, the amount of the floating data is used, and the data value of the floating data of the target field is correspondingly adjusted synchronously.

When the floating data is adjusted, only the product value recorded in the first system under the second account is adjusted, and in fact, the product information under the second account is not changed, so that in order to ensure that the floating data between the two systems is kept synchronous, an asynchronous message can be generated to be sent to the second system, and the automatic redemption processing of the product can be performed based on the second system.

S420, based on the asynchronous message queue, the difference data, the transaction flow information corresponding to the transaction request and the transaction account are sent to a second system corresponding to at least one second account.

Specifically, when the first system uses the floating data to conduct transaction, the second system to which the second account belongs can be notified to conduct quick redemption processing of the product through an asynchronous message, wherein the asynchronous message comprises, but is not limited to, information such as a card number, a transaction account, difference data, a transaction serial number, a sub-transaction serial number and the like. So that the second system initiates a quick redemption transaction based on the asynchronous message after receiving the asynchronous message notification.

S430, the second system updates floating data corresponding to the second account based on the difference data, the transaction flow information and the transaction account.

In this embodiment, after the second system receives the notification of the asynchronous message, the information of the product to be redeemed can be calculated through the difference data and the attribute of the product under the second account, so that the corresponding product can be redeemed quickly, and after the redemption is successful, the value of the product under the second account is reduced, and the floating data is also reduced.

It should be noted that, the first system uses each item of floating data, the second system also carries out corresponding product redemption processing, and the transaction operations of the two systems are independent, so that the advantage of the arrangement is that the transaction cost can be reduced, and the transaction efficiency can be improved. In order to improve the synchronism of data between two systems, prevent the problem that there is an error in floating data caused by the condition of message loss or delay, or redemption error, etc., the second system can initiate quick redemption transaction by modifying the transaction flow information generated by the first system after receiving the notification of asynchronous message.

In this embodiment, the transaction serial number and the transaction serial number are included in the transaction serial number information, and the second system updates floating data corresponding to the second account based on the difference data, the transaction serial number information and the transaction account, including: determining quick redemption information according to the difference data, the transaction serial number and the attribute of the product corresponding to at least one second account; the product quantity of the second account is updated based on the redemption information to adjust the float data based on the product quantity.

In practical application, the second system can generate a quick redemption task through the transaction serial number and the transaction serial number, and calculate information to be quickly redeemed, such as products to be quickly redeemed and the quantity of the products, through the difference data and the attribute of the products corresponding to at least one second account. Further, the quick redemption mission can be processed through the quick redemption information, the corresponding product quantity can be redeemed, after the product quantity is reduced, the floating data is reduced in the second system, and the floating data recorded in the first system is kept synchronous. In order to facilitate cross-system monitoring of floating data, after the quick redemption task is completed, the task state corresponding to the transaction serial number and the transaction serial number can be modified, for example, the task state is quick redemption completion.

It should be noted that, because asynchronous message processing exists between the first system and the second system when floating data is used, in order to prevent the problem of data asynchronization caused by message loss, delay and other conditions, a reconciliation mechanism can be established to perform inter-system reconciliation based on the reconciliation mechanism.

In this embodiment, the transaction details corresponding to the transaction request may be recorded in the first system, so as to perform cross-system accounting through the transaction details, ensure accuracy and consistency of data, and improve transaction security. Optionally, the transaction details include difference data using at least one second account, updated float data, and updated available transaction data. For example, the first system records the current available credit, the refund used credit, the financial used credit, and each transaction record of the floating data change.

In practical application, the first system can send the transaction details to the second system, and after the second system receives the transaction details file, the second system can compare floating data between the two systems first, and if the two systems are inconsistent, the two systems can compare one by one according to the details. Or, the transaction details can be acquired periodically, so that the accounting is performed based on an accounting mechanism.

In this embodiment, the transaction details corresponding to the transaction accounts may be obtained based on the timing task and the reconciliation mechanism, so as to determine available transaction data corresponding to the transaction accounts in the first system and floating data of the target fields based on the transaction details, and determine floating data of at least one second account in the second system.

The timing task may include checking frequency, for example, checking according to a natural day for one period.

Specifically, when a timing task is triggered, automatically entering a checking mechanism, wherein floating data of a target field of a transaction account in a first system and floating data of at least one second account in a second system can be compared, whether the floating data of the target field and the floating data of the at least one second account are consistent or not is checked, and if the floating data of the target field and the floating data of the at least one second account are consistent, the checking is considered to be successful; if the transaction records are inconsistent, the account checking is considered to be failed, the account checking needs to be further refined, and the transaction records in the transaction details can be compared one by one, for example, the transaction compensation data can be matched with information such as product delivery, redemption and the like, so that the abnormal position of failure is inquired, for example, the product quick redemption failure or the product delivery failure. Under the condition of checking out failure, the failure records can be classified according to the abnormal positions, and the failure types of the failure records are determined so as to carry out subsequent processing according to the failure types. For example, if the failure type is an asynchronous message loss or delay and sufficient customer holding is detected, then the redemption process is initiated as normal redemption; if the failure type is other anomalies (the anomalies of which the non-asynchronous message is lost or delayed can be all the other anomalies), the floating data recorded in the first system is automatically adjusted to 0, so that the floating data cannot be used for the refund settlement, and the floating data is reset to the correct floating data after the manual intervention is confirmed. The technical scheme provided by the invention is that the transaction record is checked by adopting the checking mechanism, so that the abnormality can be timely and effectively found, the abnormality can be accurately positioned, the abnormality is solved, and the accuracy of account data is ensured.

According to the method, accuracy of data under the transaction account is guaranteed by updating the tradable data of the transaction account in the first system and updating the floating data of the target field in the transaction account based on the data processing result, and further, difference data, transaction flow information corresponding to the transaction request and the transaction account are sent to the second system corresponding to at least one second account based on the asynchronous message queue, so that the second system updates the floating data corresponding to the second account based on the difference data, the transaction flow information and the transaction account, and data synchronization among the systems is achieved.

Fig. 5 is a schematic structural diagram of a cross-system data synchronization device according to an embodiment of the present invention. As shown in fig. 5, the apparatus includes: a target transaction data determination module 510, a tradable data retrieval module 520, a floating data acquisition module 530, and a transaction processing module 540.

Wherein, the target transaction data determining module 510 is configured to determine, in response to a transaction request, target transaction data corresponding to the transaction request; a tradable data retrieving module 520, configured to retrieve tradable data of a transaction account to which the transaction request belongs in the first system; a floating data obtaining module 530, configured to obtain floating data of at least one second account bound to the transaction account, where the at least one second account is an account in a second system, and the floating data is data recorded in the transaction account, under a condition that the tradable data does not meet the target transaction data; the transaction processing module 540 is configured to process the transaction request based on the floating data, the tradable data, and the target transaction data when it is detected that a preset condition is satisfied, and synchronously update the tradable data of the transaction account and the associated floating data based on a data processing result.

According to the technical scheme, target transaction data corresponding to the transaction request are determined, so that the tradable data of the transaction account to which the transaction request belongs in the first system is called; under the condition that the tradable data does not meet the target transaction data, floating data of at least one second account bound with the transaction account is obtained, wherein the at least one second account is an account in a second system, and the floating data is data recorded in the transaction account; when the fact that the preset condition is met is detected, the transaction request is processed based on the floating data, the tradable data and the target transaction data, the tradable data of the transaction account and the associated floating data are synchronously updated based on the data processing result, the problems that in the prior art, account data interaction is needed among systems during the payment settlement, the transaction efficiency is low and the cost is high are solved, the fact that the floating data of the second account in the second system are recorded in the transaction account of the first system, the transaction requirement is not met when the transaction account is not met, the recorded floating data are used for payment settlement, when the transaction processing is carried out among systems, the account data interaction among the systems is avoided, the transaction cost is reduced, the transaction efficiency is improved, and the user transaction experience is improved. Meanwhile, based on the data processing result, the tradable data of the transaction account and the associated floating data are synchronously updated, and the consistency and the accuracy of the data are ensured.

Optionally, the device further comprises a data synchronization module, wherein the data synchronization module comprises a floating data determination unit and a data synchronization unit.

A floating data determining unit, configured to determine floating data of at least one second account in the second system; wherein the floating data corresponds to a product held by the second account, and the floating data is positively correlated with an attribute of the product;

and the data synchronization unit is used for determining and binding the transaction account bound with the at least one second account and synchronizing floating data corresponding to the second account into a target field of the transaction account.

On the basis of the device, optionally, the device further comprises a floating data updating module;

and the floating data updating module is used for updating the floating data of the transaction account target field based on the changed floating data if the floating data corresponding to the at least one second account is detected to be changed.

On the basis of the above device, optionally, the floating data obtaining module 530 is specifically configured to obtain the floating data of the at least one second account recorded under the target field of the transaction account.

On the basis of the device, optionally, the preset condition comprises at least one of the following:

invoking authorization information of data from the floating data;

feedback is received to retrieve at least a portion of the floating data.

On the basis of the device, the device can optionally further comprise a floating data scheduling feedback module;

the floating data scheduling feedback module is used for acquiring the attribute of the product corresponding to the floating data; and feeding back a scheduling prompt for invoking floating data to a client based on the change trend in the preset duration in the attribute, so as to determine the feedback based on the triggering operation of the scheduling prompt.

On the basis of the above arrangement, the transaction processing module 540 optionally includes a balance data determination unit and a floating data adjustment unit.

A difference data determining unit configured to determine difference data according to the target transaction data and the tradable data;

and the floating data adjusting unit is used for adjusting the floating data according to the difference data so as to obtain a data processing result corresponding to the transaction request.

On the basis of the above device, optionally, a floating data adjustment unit is configured to adjust a data value of the floating data if the floating data includes the difference data; and if the floating data does not contain the difference data, the feedback data processing result is a failure processing result.

Based on the above-described apparatus, the transaction processing module 540 may further include an update processing unit and a message transmitting unit.

The updating processing unit is used for updating the tradable data of the transaction account in the first system based on the data processing result and updating the floating data of the target field in the transaction account;

and the message sending unit is used for sending the difference data, the transaction flow information corresponding to the transaction request and the transaction account to a second system corresponding to the at least one second account based on the asynchronous message queue, so that the second system updates the floating data corresponding to the second account based on the difference data, the transaction flow information and the transaction account.

On the basis of the device, optionally, the transaction serial number and the transaction serial number are included in the transaction serial number information, and the message sending unit comprises a quick redemption information determining unit and a product quantity updating unit.

A quick redemption information determining unit, configured to determine quick redemption information according to the difference data, the transaction serial number, and the attribute of the product corresponding to the at least one second account;

a product quantity updating unit for updating the product quantity of the second account based on the quick redemption information to adjust the float data based on the product quantity.

Optionally, the device further comprises a recording module based on the device.

The recording module is used for recording the transaction detail corresponding to the transaction request in the first system, wherein the transaction detail comprises difference data using the at least one second account, updated floating data and updated available transaction data.

On the basis of the device, the device can optionally further comprise a reconciliation module.

And the reconciliation module is used for acquiring transaction details corresponding to the transaction accounts based on the timing tasks and the reconciliation mechanism, determining available transaction data corresponding to the transaction accounts in the first system and floating data of target fields based on the transaction details, and determining floating data of at least one second account in the second system.

The cross-system data synchronization device provided by the embodiment of the invention can execute the cross-system data synchronization method provided by any embodiment of the invention, and has the corresponding functional modules and beneficial effects of the execution method.

Fig. 6 is a schematic structural diagram of an electronic device according to an embodiment of the present invention. Fig. 6 shows a block diagram of an exemplary electronic device 60 suitable for use in implementing the embodiments of the invention. The electronic device 60 shown in fig. 6 is merely an example and should not be construed as limiting the functionality and scope of use of embodiments of the present invention.

As shown in fig. 6, the electronic device 60 is in the form of a general purpose computing device. Components of electronic device 60 may include, but are not limited to: one or more processors or processing units 601, a system memory 602, and a bus 603 that connects the different system components (including the system memory 602 and the processing units 601).

Bus 603 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a processor, and a local bus using any of a variety of bus architectures. By way of example, and not limitation, such architectures include Industry Standard Architecture (ISA) bus, micro channel architecture (MAC) bus, enhanced ISA bus, video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI) bus.

Electronic device 60 typically includes many types of computer system readable media. Such media can be any available media that is accessible by electronic device 60 and includes both volatile and nonvolatile media, removable and non-removable media.

The system memory 602 may include computer system readable media in the form of volatile memory such as Random Access Memory (RAM) 604 and/or cache memory 605. Electronic device 60 may further include other removable/non-removable, volatile/nonvolatile computer system storage media. By way of example only, storage system 606 may be used to read from and write to non-removable, nonvolatile magnetic media (not shown in FIG. 6, commonly referred to as a "hard disk drive"). Although not shown in fig. 6, a magnetic disk drive for reading from and writing to a removable non-volatile magnetic disk (e.g., a "floppy disk"), and an optical disk drive for reading from or writing to a removable non-volatile optical disk (e.g., a CD-ROM, DVD-ROM, or other optical media) may be provided. In such cases, each drive may be coupled to bus 603 through one or more data medium interfaces. Memory 602 may include at least one program product having a set (e.g., at least one) of program modules configured to carry out the functions of embodiments of the invention.

A program/utility 608 having a set (at least one) of program modules 607 may be stored in, for example, memory 602, such program modules 607 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each or some combination of which may include an implementation of a network environment. Program modules 607 generally perform the functions and/or methods of the described embodiments of the invention.

The electronic device 60 may also communicate with one or more external devices 609 (e.g., keyboard, pointing device, display 610, etc.), one or more devices that enable a user to interact with the electronic device 60, and/or any device (e.g., network card, modem, etc.) that enables the electronic device 60 to communicate with one or more other computing devices. Such communication may occur through an input/output (I/O) interface 611. Also, the electronic device 60 may communicate with one or more networks such as a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, such as the Internet, through a network adapter 612. As shown, the network adapter 612 communicates with other modules of the electronic device 60 over the bus 603. It should be appreciated that although not shown in fig. 6, other hardware and/or software modules may be used in connection with electronic device 60, including, but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, data backup storage systems, and the like.

The processing unit 601 executes various functional applications and data processing by running programs stored in the system memory 602, for example, implementing a cross-system data synchronization method provided by an embodiment of the present invention.

Embodiments of the present invention also provide a storage medium containing computer-executable instructions, which when executed by a computer processor, are configured to perform a cross-system data synchronization method, the method comprising:

determining target transaction data corresponding to a transaction request in response to the transaction request;

invoking tradable data of a transaction account to which the transaction request belongs in a first system;

acquiring floating data of at least one second account bound with the transaction account under the condition that the target transaction data is not met by the tradable data, wherein the at least one second account is an account in a second system, and the floating data is data recorded in the transaction account;

when the preset condition is detected to be met, the transaction request is processed based on the floating data, the tradable data and the target transaction data, and the tradable data of the transaction account and the associated floating data are synchronously updated based on a data processing result.

The computer storage media of embodiments of the invention may take the form of any combination of one or more computer-readable media. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples (a non-exhaustive list) of the computer-readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

The computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, either in baseband or as part of a carrier wave. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.

Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

Computer program code for carrying out operations for embodiments of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, smalltalk, C ++ and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computer (for example, through the Internet using an Internet service provider).

Embodiments of the present invention also provide a computer program product comprising a computer program which, when executed by a processor, implements a cross-system data synchronization method as provided by any of the embodiments of the present application.

Computer program product in the implementation, the computer program code for carrying out operations of the present invention may be written in one or more programming languages, including an object oriented programming language such as Java, smalltalk, C ++ and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computer (for example, through the Internet using an Internet service provider).

Note that the above is only a preferred embodiment of the present invention and the technical principle applied. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, while the invention has been described in connection with the above embodiments, the invention is not limited to the embodiments, but may be embodied in many other equivalent forms without departing from the spirit or scope of the invention, which is set forth in the following claims.

Claims (16)

1. A method for synchronizing data across a system, comprising:

determining target transaction data corresponding to a transaction request in response to the transaction request;

invoking tradable data of a transaction account to which the transaction request belongs in a first system;

acquiring floating data of at least one second account bound with the transaction account under the condition that the target transaction data is not met by the tradable data, wherein the at least one second account is an account in a second system, and the floating data is data recorded in the transaction account;

when the preset condition is detected to be met, the transaction request is processed based on the floating data, the tradable data and the target transaction data, and the tradable data of the transaction account and the associated floating data are synchronously updated based on a data processing result.

2. The method of claim 1, further comprising, prior to said determining target transaction data corresponding to a transaction request in response to said transaction request:

determining floating data of at least one second account in the second system; wherein the floating data corresponds to a product held by the second account, and the floating data is positively correlated with an attribute of the product;

Determining and binding a transaction account bound with the at least one second account, and synchronizing floating data corresponding to the second account into a target field of the transaction account.

3. The method as recited in claim 2, further comprising:

and if the floating data corresponding to the at least one second account is detected to have the change, updating the floating data of the transaction account target field based on the changed floating data.

4. The method of claim 1, wherein the obtaining floating data for at least one second account bound to the transaction account comprises:

and acquiring floating data of the at least one second account recorded under a target field of the transaction account.

5. The method of claim 1, wherein the preset conditions include at least one of:

invoking authorization information of data from the floating data;

feedback is received to retrieve at least a portion of the floating data.

6. The method as recited in claim 5, further comprising:

acquiring the attribute of a product corresponding to the floating data;

and feeding back a scheduling prompt for invoking floating data to a client based on the change trend in the preset duration in the attribute, so as to determine the feedback based on the triggering operation of the scheduling prompt.

7. The method of claim 1, wherein the processing the transaction request based on the float data, the tradable data, and the target transaction data comprises:

determining difference data according to the target transaction data and the tradable data;

and adjusting the floating data according to the difference data to obtain a data processing result corresponding to the transaction request.

8. The method of claim 7, wherein said adjusting said floating data based on said difference data to obtain a data processing result corresponding to said transaction request comprises:

if the floating data comprises the difference data, adjusting the data value of the floating data;

and if the floating data does not contain the difference data, the feedback data processing result is a failure processing result.

9. The method of claim 1, wherein the synchronously updating the tradable data of the transaction account and the associated floating data based on data processing results comprises:

updating tradable data of a transaction account in the first system based on the data processing result, and updating floating data of a target field in the transaction account;

And transmitting the difference data, the transaction flow information corresponding to the transaction request and the transaction account to a second system corresponding to the at least one second account based on the asynchronous message queue, so that the second system updates floating data corresponding to the second account based on the difference data, the transaction flow information and the transaction account.

10. The method of claim 9, wherein the transaction flow information includes a transaction flow number and a transaction serial number, and the second system updates floating data corresponding to the second account based on the difference data, the transaction flow information, and the transaction account, comprising:

determining quick redemption information according to the difference data, the transaction serial number and the attribute of the product corresponding to the at least one second account;

updating a product quantity of the second account based on the quick redemption information to adjust the float data based on the product quantity.

11. The method as recited in claim 1, further comprising:

recording transaction details corresponding to the transaction request in the first system, wherein the transaction details comprise difference data using the at least one second account, updated floating data and updated available transaction data.

12. The method as recited in claim 1, further comprising:

and acquiring transaction details corresponding to the transaction accounts based on a timing task and a reconciliation mechanism, so as to determine available transaction data corresponding to the transaction accounts in the first system and floating data of target fields based on the transaction details, and determine floating data of the at least one second account in the second system.

13. A cross-system data synchronization apparatus, comprising:

a target transaction data determining module for determining target transaction data corresponding to a transaction request in response to the transaction request;

the transaction request comprises a transaction request, a transaction data retrieving module and a transaction data retrieving module, wherein the transaction request comprises transaction data of a transaction account to which the transaction request belongs in a first system;

the floating data acquisition module is used for acquiring floating data of at least one second account bound with the transaction account under the condition that the target transaction data is not met by the tradable data, wherein the at least one second account is an account in a second system, and the floating data is data recorded in the transaction account;

and the transaction processing module is used for processing the transaction request based on the floating data, the tradable data and the target transaction data when the condition that the preset condition is met is detected, and synchronously updating the tradable data of the transaction account and the associated floating data based on a data processing result.

14. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable by the processor, wherein the processor implements the cross-system data synchronization method of any one of claims 1-12 when executing the computer program.

15. A computer readable storage medium, on which a computer program is stored, characterized in that the program, when being executed by a processor, implements a cross-system data synchronization method according to any of claims 1-12.

16. A computer program product comprising a computer program which, when executed by a processor, implements the cross-system data synchronization method according to any one of claims 1-12.