A data processing method and system

By merging the day and night databases of the bank's core system, unprocessed batch requests are preferred, and transaction requests are processed after batch processing is completed, the performance loss problem caused by frequent database switching is solved and data processing efficiency is improved.

CN111897839BActive Publication Date: 2024-12-03HUA XIA BANK
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202010789967.8
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2020-08-07
Publication Date
2024-12-03
Estimated Expiration
2040-08-07

AI Technical Summary

Technical Problem

When handling transaction requests and batch processing, the existing bank core system needs to frequently switch between day and night databases, resulting in high performance losses and reducing data processing efficiency.

Method used

Merge the day and night databases into one database. By receiving transaction requests and account information, determine whether there are unprocessed batch requests, prioritize batch requests, and perform transaction data processing after batch processing is completed, reducing cross-database access.

Benefits of technology

It reduces performance losses, improves the data processing efficiency of the bank's core system, and ensures that batch processing and transaction request processing are carried out simultaneously.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN111897839B_ABST
    Figure CN111897839B_ABST
Patent Text Reader

Abstract

The embodiment of the present application provides a data processing method and system, which can first receive a transaction request and the account information corresponding to the transaction request, then obtain the account data corresponding to the account information from the main database, and determine whether the account data includes unprocessed batch requests. When the account data includes unprocessed batch requests, the unprocessed batch requests can be processed first. And the transaction is processed after the processing of the unprocessed batch requests is completed. In this way, when batch processing is required, the account data in the main database can be directly collected for processing. If a new transaction request is received during the batch processing, the transaction request can be processed after the batch processing is completed. In this way, only one main database is required to ensure the batch processing business and the transaction request processing business. The performance loss caused by cross-database access is reduced, thereby improving the speed of business processing.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and in particular to a data processing method and system. Background Art

[0002] In order to ensure that transactions are processed, the core system of the bank needs to process customer transaction requests 24 hours a day, 7 days a week, so as to update account data in real time. In addition, in order to ensure the normal operation of the business, the core system of the bank also needs to process account data in batches after the end of each accounting day, such as calculating the daily interest of the account. When processing in batches, the account data needs to be static data with fixed changes, but the core system of the bank will cause the account data to change continuously when processing transaction requests, which cannot meet the needs of batch processing.

[0003] To this end, the traditional core banking system has two databases: the daytime database and the nighttime database. Banks can store transaction data generated during the day in the daytime database and use the daytime database for batch processing. After starting batch processing, if the system receives a new transaction request, the system can process the new transaction request and store it in the nighttime database. Finally, the data in the nighttime database and the daytime database are synchronized to achieve batch processing and real-time transaction requests.

[0004] However, the existing core banking system needs to constantly switch between the daytime database and the nighttime database, which causes a lot of performance loss and reduces the efficiency of the core banking system in processing data. Summary of the invention

[0005] In view of this, the embodiments of the present application provide an off-line data processing method and system, which aims to merge the existing daytime database and nighttime database into the same database while ensuring the normal operation of the existing batch processing business and transaction request processing business, thereby reducing the performance loss of the bank's core system.

[0006] A data processing method, the method comprising:

[0007] receiving a transaction request and information corresponding to the transaction request, wherein the information corresponding to the transaction request includes account information and transaction data information corresponding to the transaction request;

[0008] Acquire account data corresponding to the account information from a master database, and determine whether the account data includes an unprocessed batch request, wherein the batch request is a request for batch processing of the account data, and the master database is used to store account data corresponding to at least one account information;

[0009] When the account data includes unprocessed batch requests, processing the unprocessed batch requests;

[0010] After the processing of the unprocessed batch requests is completed, the account data is processed according to the transaction data information.

[0011] Optionally, the processing of the unprocessed batch requests includes:

[0012] The processing priority corresponding to the unprocessed batch request is adjusted to a high priority so as to preferentially process the unprocessed batch request.

[0013] Optionally, the method is applied to the first server, and the processing of the unprocessed batch requests includes:

[0014] The first server sends the unprocessed batch request and the account data to the second server, so that the second server processes the account data according to the unprocessed batch request;

[0015] After the processing of the unprocessed batch request is completed, processing the account data according to the transaction data information includes:

[0016] The account data sent by the second server is received, where the account data is account data processed by the second server.

[0017] Optionally, after processing the account data according to the transaction data information, the method further includes:

[0018] The processed account data is updated to the main database, and the data of the main database is synchronized to the first sub-database in real time.

[0019] Optionally, the method further comprises:

[0020] Receiving a static data generation request, and recording a first time of receiving the static data generation request;

[0021] At the first time, data synchronization between the main database and the first sub-database is stopped, and data of the first sub-database is copied to the second sub-database;

[0022] Record the second time when the copying is completed;

[0023] The account data updated in the main database during the time interval between the first time and the second time are added to the second sub-database, and the data in the second sub-database is used as static data.

[0024] A data processing system, the system comprising a main database and a first server;

[0025] The master database is used to store account data corresponding to at least one account information;

[0026] The first server is configured to receive a transaction request and information corresponding to the transaction request, wherein the information corresponding to the transaction request includes account information and transaction data information corresponding to the transaction request; obtain account data corresponding to the account information from a master database, and determine whether the account data includes unprocessed batch requests; when the account data includes unprocessed batch requests, process the unprocessed batch requests; after completing the processing of the unprocessed batch requests, process the account data according to the transaction data information.

[0027] Optionally, the first server is specifically configured to adjust the processing priority corresponding to the unprocessed batch requests to a high priority, so as to preferentially process the unprocessed batch requests.

[0028] Optionally, the system further comprises a second server;

[0029] The first server is specifically configured to send the unprocessed batch request and the account data to the second server; and receive the account data sent by the second server, wherein the account data is the account data obtained after the second server processes the unprocessed batch request;

[0030] The second server is used to process the account data according to the unprocessed batch request.

[0031] Optionally, the system further comprises a first sub-database;

[0032] The first sub-database is used to store the synchronization data of the main database;

[0033] The first server is further configured to update the processed account data to the main database, and synchronize the data of the main database to the first sub-database in real time.

[0034] Optionally, the system further comprises a second sub-database;

[0035] The second sub-database is used to generate static data;

[0036] The first server is further configured to receive a static data generation request and record a first time of receiving the static data generation request; stop data synchronization between the main database and the first sub-database at the first time, and copy the data of the first sub-database to the second sub-database; record a second time when the copying is completed; add the account data updated by the main database in the time interval between the first time and the second time to the second sub-database, and use the data of the second sub-database as static data.

[0037] The embodiment of the present application provides a data processing method and system, which can first receive a transaction request and information corresponding to the transaction request, and the information corresponding to the transaction request can include account information and transaction data information corresponding to the transaction request. Then, the account data corresponding to the account information can be obtained from the main database, and it is determined whether the account data includes unprocessed batch requests. Among them, the main database can be used to store account data corresponding to at least one account information. When the account data includes unprocessed batch requests, it means that the batch processing of the account has not yet ended, and the unprocessed batch requests can be processed first. After the processing of the unprocessed batch requests is completed, the account data is processed according to the transaction data information. In this way, when batch processing is required, the account data in the main database can be directly collected for processing. If a new transaction request is received during the batch processing, the transaction request can be processed after the batch processing is completed. In this way, only one main database is required to ensure the batch processing business and the transaction request processing business. Compared with the prior art, the performance loss caused by cross-database access is reduced, thereby improving the speed of business processing. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] In order to more clearly illustrate the technical solutions in this embodiment or the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0039] Figure 1 A method flow chart of a data processing method provided in an embodiment of the present application;

[0040] Figure 2 A schematic diagram of the structure of a data processing system provided in an embodiment of the present application;

[0041] Figure 3 A schematic diagram of the structure of a data processing system provided in an embodiment of the present application;

[0042] Figure 4A schematic diagram of the structure of a data processing system provided in an embodiment of the present application;

[0043] Figure 5 A schematic diagram of the structure of a data processing system provided in an embodiment of the present application. DETAILED DESCRIPTION

[0044] The core system of a bank can complete the transaction request processing business and batch processing business of an account. Among them, the transaction request processing business refers to the business of processing transaction requests such as transaction transfers of an account, and the batch processing business refers to the business of interest settlement, report preparation, etc. for an account. The transaction request processing business has high requirements for the real-time nature of data and requires real-time update of account data. However, for batch processing business, only fixed static data can be used for batch processing.

[0045] In order to ensure that batch processing and transaction request processing are carried out simultaneously, the traditional core banking system can have two databases, the daytime database and the nighttime database, and complete the corresponding business by switching between the databases. During the day when the number of transaction requests is large, the core banking system can process the transaction requests in real time and update the account data in real time. At night when the number of transaction requests is small, the core banking system can process the account data in batches.

[0046] Specifically, after receiving the batch processing request, the bank core system can stop updating the account data in the daytime database, and copy the data stored in the daytime database to the nighttime database, and use the data stored in the nighttime database to process the transaction request. Then, the account data stored in the daytime database will not be changed due to the transaction request. The bank core system can use the account data stored in the daytime database for batch processing. After the batch processing is completed, the bank core system can update the data in the nighttime database to the daytime database to process the transaction request of the next day.

[0047] Although the traditional core banking system can ensure the normal processing of batch business and transaction requests, it needs to switch between two databases constantly. Switching databases will bring a lot of performance loss, that is, occupy the computing resources of the core banking system, resulting in low data processing efficiency.

[0048] In order to provide a technical solution that can realize both batch processing business and transaction request processing business through a database collection, the present application provides a data processing method. The preferred embodiment of the present application will be described from the perspective of a server, wherein the server can be a background server running a bank core system.

[0049] See also Figure 1 , Figure 1The method flow chart of the data processing method provided in the embodiment of the present application includes:

[0050] S101: Receive a transaction request and information corresponding to the transaction request.

[0051] When a user needs to conduct a transaction, a transaction request and information corresponding to the transaction request can be sent to the server through a mobile terminal or other device. The server can then receive the transaction request and information corresponding to the transaction request for subsequent processing. In an embodiment of the present application, the transaction request may be a transfer transaction request, a payment transaction request, or other related transaction requests that require real-time processing. The information corresponding to the transaction request may include account information and transaction data information corresponding to the transaction request. For example, the information corresponding to the transfer transaction request may include the account information of the customer who initiated the transfer transaction request and the transaction amount corresponding to the transfer transaction.

[0052] S102: Acquire account data corresponding to the account information from the main database, and determine whether the account data includes unprocessed batch requests.

[0053] After receiving the transaction request, the server can retrieve the account data corresponding to the account information from the master database and determine whether the account data includes unprocessed batch requests. The batch request can be a request for batch processing of account data. The master database can be used to store account data corresponding to at least one account information, which is similar to the daytime database and nighttime database in the traditional technology. If the account data includes unprocessed batch requests, it means that the batch processing of the account has not yet ended, the account data is still in the batch processing state, and the transaction request cannot be processed; if the account data does not include unprocessed batch requests, it means that the batch processing of the account has ended and the transaction request can be processed.

[0054] S103: When the account data includes unprocessed batch requests, the unprocessed batch requests are processed.

[0055] When the account data includes unprocessed batch requests, the server can temporarily put aside the transaction requests and give priority to processing the unprocessed batch requests. In this way, the server will not process the transaction requests before the batch processing is completed, and accordingly, the account data in the main database will not change due to the processing of the transaction requests. Then, the account data in the main database is in a fixed state when processing batch requests and is static data, thus meeting the requirements of batch processing.

[0056] Considering that the processing of transaction requests has a high requirement for real-time performance, in some possible implementations, the server can adjust the priority of batch requests so as to give priority to batch processing of accounts that have received transaction requests. The server can adjust the processing priority corresponding to the unprocessed batch requests to a high priority. When processing batch requests, the server can give priority to batch requests with high priority, that is, give priority to batch requests corresponding to the account information. For example, suppose that the server receives a transaction request corresponding to account B during the process of batch processing of three accounts, namely, account A, account B, and account C. Then the server can adjust the batch request of account B to a high priority, and give priority to batch processing of account B, so as to process the transaction request in time. In this way, if the server receives a new transaction request during the process of processing multiple batch requests, the server can adjust the batch request corresponding to the transaction request to a high priority, so as to give priority to batch processing of the account where the transaction occurred, so as to ensure that the transaction request is processed in time.

[0057] Considering that batch processing may occupy more computing resources of the server, in some possible implementations, the account data can be processed by multiple servers. Among them, the server for executing the data processing method can be called the first server, and the other servers of the bank core system can be called the second server.

[0058] In an embodiment of the present application, the first server may receive a transaction request and information corresponding to the transaction request, and determine whether the account data corresponding to the transaction request includes an unprocessed batch request. After determining that the account data includes an unprocessed batch request, the first server may send the account data and the unprocessed batch data to the second server. The second server is normally idle. After receiving the account data and the unprocessed batch request, it may quickly process the batch request, that is, process the account data according to the unprocessed batch request to obtain the processed account data. The second server may send the processed account data to the first server. The first server may receive the processed account data sent by the second server so as to continue the subsequent processing. In this way, if the server receives a new transaction request during the process of processing multiple batch requests, the server may send the batch request corresponding to the transaction request to the second server, thereby utilizing the idle second server to perform batch processing on the accounts where transactions occur, so as to ensure that the transaction requests are processed in a timely manner.

[0059] S104: After the processing of the unprocessed batch requests is completed, the account data is processed according to the transaction data information.

[0060] After the unprocessed batch requests are processed, the batch processing of the account data is completed, and the account data in the main database does not need to remain fixed. The server can process the account data according to the transaction data information to complete the processing of the transaction request.

[0061] The embodiment of the present application provides a data processing method, which can first receive a transaction request and information corresponding to the transaction request, and the information corresponding to the transaction request can include account information and transaction data information corresponding to the transaction request. Then, the account data corresponding to the account information can be obtained from the main database, and it is determined whether the account data includes unprocessed batch requests. Among them, the main database can be used to store account data corresponding to at least one account information. When the account data includes unprocessed batch requests, it means that the batch processing of the account has not yet ended, and the unprocessed batch requests can be processed first. After the processing of the unprocessed batch requests is completed, the account data is processed according to the transaction data information. In this way, when batch processing is required, the account data in the main database can be directly collected for processing. If a new transaction request is received during the batch processing, the transaction request can be processed after the batch processing is completed. In this way, only one main database is required to ensure the batch processing business and the transaction request processing business. Compared with the prior art, the performance loss caused by cross-database access is reduced, thereby improving the speed of business processing.

[0062] In addition, in order to separate static account data from dynamic account data, in some possible implementations, the bank core system may also include at least one sub-database. It should be noted that the sub-database is only a description of the purpose, and does not mean that the sub-database and the main database are hardware-independent databases.

[0063] In an embodiment of the present application, after the server completes the transaction request processing, the server can update the processed account data to the main database, and synchronize the data stored in the main database to the first sub-database. In this way, the data stored in the first sub-database is synchronized with the main database. Then, when performing batch processing or generating reports and other businesses that require static data, it is only necessary to stop the synchronization between the first sub-database and the main data, and the data in the first sub-database is fixed and unchanged static data. In this way, the data stored in the main database is dynamic data, and static data can be stored in the first sub-database, thereby realizing the separation of dynamic data and static data.

[0064] In some possible implementations, the bank core system may further include a second sub-database for generating static data. After receiving a request to generate static data, the server may record the first time of receiving the request to generate static data, and stop data synchronization between the main database and the first sub-database. The server may also copy the data stored in the first sub-database to the second sub-database. The time when the server completes the copying may be the second time. Then at the second time, the data stored in the second sub-database is consistent with the data stored in the first sub-database. The server may add the account data updated in the main database in the time interval between the first time and the second time to the second sub-database. In this way, the data stored in the second sub-database is consistent with the data stored in the main database at the second time, and can be subsequently processed as static data.

[0065] The above are some specific implementations of the data processing method provided in the embodiment of the present application. Based on this, the present application also provides a corresponding system. The data processing system provided in the embodiment of the present application is introduced below. It should be noted that in some possible implementations, the system can be a core system of a bank.

[0066] See also Figure 2 The structural diagram of the data processing system shown in the figure, the system 200 includes a main database 210 and a first server 220.

[0067] The main database 210 is used to store account data corresponding to at least one account information.

[0068] The first server 220 is used to receive a transaction request and information corresponding to the transaction request, wherein the information corresponding to the transaction request includes account information and transaction data information corresponding to the transaction request; obtain account data corresponding to the account information from the main database 210, and determine whether the account data includes unprocessed batch requests; when the account data includes unprocessed batch requests, process the unprocessed batch requests; after the processing of the unprocessed batch requests is completed, process the account data according to the transaction data information.

[0069] The embodiment of the present application provides a data processing system, which can first receive a transaction request and information corresponding to the transaction request, and the information corresponding to the transaction request can include account information and transaction data information corresponding to the transaction request. Then, the account data corresponding to the account information can be obtained from the main database, and it is determined whether the account data includes unprocessed batch requests. Among them, the main database can be used to store account data corresponding to at least one account information. When the account data includes unprocessed batch requests, it means that the batch processing of the account has not yet ended, and the unprocessed batch requests can be processed first. After the processing of the unprocessed batch requests is completed, the account data is processed according to the transaction data information. In this way, when batch processing is required, the account data in the main database can be directly collected for processing. If a new transaction request is received during the batch processing, the transaction request can be processed after the batch processing is completed. In this way, only one main database is required to ensure the batch processing business and the transaction request processing business. Compared with the prior art, the performance loss caused by cross-database access is reduced, thereby improving the speed of business processing.

[0070] Optionally, in some possible implementations, the first server 220 is specifically configured to:

[0071] The processing priority corresponding to the unprocessed batch request is adjusted to a high priority so as to preferentially process the unprocessed batch request.

[0072] In this way, if the server receives a new transaction request while processing multiple batch requests, the server can adjust the batch request corresponding to the transaction request to a high priority, thereby giving priority to batch processing of the accounts where transactions occur, thus ensuring that the transaction requests are processed in a timely manner.

[0073] Alternatively, see Figure 3 ,exist Figure 2 Based on the system shown, the system 200 further includes a second server 230 .

[0074] The second server 230 is configured to process the account data according to the unprocessed batch request.

[0075] The first server 220 is specifically configured to send the unprocessed batch request and the account data to the second server 220 ; and receive the account data sent by the second server 220 , wherein the account data is the account data obtained after the second server 220 processes the unprocessed batch request.

[0076] In this way, if the server receives a new transaction request while processing multiple batch requests, the server can send the batch request corresponding to the transaction request to the second server, thereby using the idle second server to batch process the accounts where transactions occur, thereby ensuring that the transaction requests are processed in a timely manner.

[0077] Alternatively, see Figure 4 ,exist Figure 2 Based on the system shown, the system 200 further includes a first sub-database 240;

[0078] The first sub-database 240 is used to store the synchronization data of the main database.

[0079] The first server 220 is further configured to update the processed account data to the main database 210 , and synchronize the data of the main database 210 to the first sub-database 240 in real time.

[0080] In this way, the data stored in the first sub-database is synchronized with the main database. When performing batch processing or generating reports that require static data, you only need to stop the synchronization between the first sub-database and the main data, and the data in the first sub-database will be fixed and unchanging static data. In this way, the data stored in the main database is dynamic data, and the first sub-database can store static data, thereby achieving the separation of dynamic data and static data.

[0081] Alternatively, see Figure 5 ,exist Figure 4 Based on the system shown, the system 200 further includes a second sub-database 250;

[0082] The second sub-database 250 is used to generate static data.

[0083] The first server 220 is further used to receive a static data generation request and record a first time of receiving the static data generation request; stop data synchronization between the main database 210 and the first sub-database 240 at the first time, and copy the data of the first sub-database 40 to the second sub-database 250; record a second time when the copying is completed; add the account data updated by the main database 210 in the time interval between the first time and the second time to the second sub-database 250, and use the data of the second sub-database 250 as static data.

[0084] In this way, the data stored in the second sub-database is consistent with the data stored in the second time main database and can be used as static data for subsequent processing.

[0085] The "first" and "second" in the names of the "first server" and "second server" mentioned in the embodiments of the present application are only used as name identifiers and do not represent the first or second in order.

[0086] Through the description of the above implementation methods, it can be known that those skilled in the art can clearly understand that all or part of the steps in the above-mentioned embodiment method can be implemented by means of software plus a general hardware platform. Based on such an understanding, the technical solution of the present application can be embodied in the form of a software product, which can be stored in a storage medium, such as a read-only memory (ROM) / RAM, a magnetic disk, an optical disk, etc., including a number of instructions for a computer device (which can be a personal computer, a server, or a network communication device such as a router) to execute the methods described in each embodiment of the present application or some parts of the embodiments.

[0087] Each embodiment in this specification is described in a progressive manner, and the same and similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment. Some or all of the modules can be selected according to actual needs to achieve the purpose of the scheme of this embodiment. Ordinary technicians in this field can understand and implement it without paying creative work.

[0088] The above description is merely an exemplary embodiment of the present application and is not intended to limit the protection scope of the present application.

Claims

1. A data processing method, characterized in that: The method comprises: receiving a transaction request and information corresponding to the transaction request, wherein the information corresponding to the transaction request includes account information and transaction data information corresponding to the transaction request; acquiring account data corresponding to the account information from a main database, and determining whether the account data includes an unprocessed batch request, wherein the batch request is a request for batch processing of the account data, and the main database is used to store account data corresponding to at least one account information; When the account data includes unprocessed batch requests, processing the unprocessed batch requests; After the processing of the unprocessed batch request is completed, processing the account data according to the transaction data information; Wherein, after processing the account data according to the transaction data information, the method further includes: Update the processed account data to the main database, and synchronize the data of the main database to the first sub-database in real time; The method further comprises: Receiving a static data generation request, and recording a first time of receiving the static data generation request; At the first time, data synchronization between the main database and the first sub-database is stopped, and data of the first sub-database is copied to the second sub-database; Record the second time when the copying is completed; The account data updated in the main database during the time interval between the first time and the second time are added to the second sub-database, and the data in the second sub-database is used as static data.

2. The method according to claim 1, characterized in that The processing of the unprocessed batch request comprises: The processing priority corresponding to the unprocessed batch request is adjusted to a high priority so as to preferentially process the unprocessed batch request.

3. The method according to claim 1, characterized in that The method is applied to the first server, and the processing of the unprocessed batch requests includes: The first server sends the unprocessed batch request and the account data to the second server, so that the second server processes the account data according to the unprocessed batch request; After the processing of the unprocessed batch request is completed, processing the account data according to the transaction data information includes: The account data sent by the second server is received, where the account data is account data processed by the second server.

4. A data processing system, characterized in that: The system includes a main database and a first server; The master database is used to store account data corresponding to at least one account information; The first server is configured to receive a transaction request and information corresponding to the transaction request, wherein the information corresponding to the transaction request includes account information and transaction data information corresponding to the transaction request; obtain account data corresponding to the account information from a master database, and determine whether the account data includes unprocessed batch requests; When the account data includes unprocessed batch requests, processing the unprocessed batch requests; after the processing of the unprocessed batch requests is completed, processing the account data according to the transaction data information; Wherein, the system further comprises a first sub-database; The first sub-database is used to store the synchronization data of the main database; The first server is further configured to update the processed account data to the main database, and synchronize the data of the main database to the first sub-database in real time; The system also includes a second sub-database; The second sub-database is used to generate static data; The first server is further configured to receive a static data generation request and record a first time of receiving the static data generation request; stop data synchronization between the main database and the first sub-database at the first time, and copy the data of the first sub-database to the second sub-database; Recording a second time when the replication is completed; adding the account data updated in the main database in the time interval between the first time and the second time to the second sub-database, and using the data in the second sub-database as static data.

5. The system according to claim 4, characterized in that The first server is specifically configured to adjust the processing priority corresponding to the unprocessed batch requests to a high priority, so as to preferentially process the unprocessed batch requests.

6. The system according to claim 4, characterized in that The system also includes a second server; The first server is specifically configured to send the unprocessed batch request and the account data to the second server; and receive the account data sent by the second server, wherein the account data is the account data obtained after the second server processes the unprocessed batch request; The second server is used to process the account data according to the unprocessed batch request.