A method, device and electronic device for processing account limit data

By determining the quota batch in the transaction server and generating operation requests, the problem that the distributed account system is difficult to accurately calculate the daily end quota under high concurrent transactions is solved, and the continuous progress of transactions and data reliability is achieved.

CN114648402BActive Publication Date: 2025-02-28NETSUNION CLEARING CORP
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202011494088.9
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2020-12-17
Publication Date
2025-02-28
Estimated Expiration
2040-12-17

AI Technical Summary

Technical Problem

It is difficult for distributed account systems to accurately calculate the daily end quota under high concurrent transaction requests, resulting in problems such as not accepting transactions or transaction timeouts and rejection in some time.

Method used

The transaction server determines the quota batches associated with the account transaction request, generates the account quota data operation request, and sends it to the database server for modification, ensuring the accurate calculation of each quota batch.

Benefits of technology

It realizes uninterrupted processing of high concurrent transaction requests, ensures the continuous progress of transactions, and obtains accurate quota data for each batch by isolating transactions and quotas from the batch dimension, meeting the data reliability needs of the financial industry.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114648402B_ABST
    Figure CN114648402B_ABST
Patent Text Reader

Abstract

The present application discloses a method, device and electronic device for processing account limit data, which is executed by a transaction server. The database server associated with the transaction server stores account limit data corresponding to multiple limit batches. The method includes: determining a limit batch associated with a transaction batch of an account transaction request; generating an account limit data operation request for the corresponding account limit data according to the determined limit batch; sending the account limit data operation request to the database server so that the database server modifies the corresponding account limit data. The present application can process high-concurrency and uninterrupted transaction requests without suspending business transactions, thereby ensuring the continuous progress of transactions; in addition, by isolating transactions and limits from the batch dimension, accurate account limit data for each batch can be obtained, which meets the data reliability requirements of the financial industry and provides an accurate data basis for subsequent verification of the amount of occurrence and provision of bills to the outside world.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of financial business technology, and in particular to a method, device and electronic device for processing account limit data. Background Art

[0002] In financial business scenarios, for real-time deduction transactions, deducting account limits is a core function. Traditional banks or other financial institutions generally use centralized databases to update account dates and obtain account limits through pessimistic locking. In order to solve the problem of hot accounts under high concurrent transaction requests, the existing technology also uses a distributed account system to process real-time deduction transactions.

[0003] However, although the distributed account system can solve the problem of hot accounts under high-concurrency transaction requests, it also brings new problems. When it comes to account transactions, it is necessary to consider how to end the day and settle accounts. The existing daily cut and end-of-day quota calculation solutions can only be applied to centralized databases and cannot be applied to distributed account systems. In addition, some banks or financial institutions do not accept transactions or transaction timeouts or rejections at certain times due to excessive data volume. Summary of the invention

[0004] The embodiments of the present application provide a method, device and electronic device for processing account limit data to achieve accurate calculation of data such as the end-of-day limit of a distributed account system.

[0005] The present application embodiment adopts the following technical solutions:

[0006] In a first aspect, an embodiment of the present application provides a method for processing account limit data, which is executed by a transaction server, wherein a database server associated with the transaction server stores account limit data corresponding to multiple limit batches, and the method includes:

[0007] Determine the quota batch associated with the transaction batch of the account transaction request;

[0008] Generate an account limit data operation request for corresponding account limit data according to the determined limit batch;

[0009] The account limit data operation request is sent to the database server so that the database server modifies the corresponding account limit data.

[0010] Optionally, each transaction batch and quota batch corresponds to a predetermined time interval.

[0011] Optionally, the account limit data corresponding to each limit batch includes an account batch limit and a limit batch number, which are stored in a limit account summary table of the database server, and the determining of the limit batch associated with the transaction batch of the account transaction request includes:

[0012] Determine the quota batch number that is not less than the transaction batch number of the account transaction request;

[0013] The content of the account limit data operation request includes: modifying the account batch limit corresponding to the limit batch number determined in the limit account summary table according to the transaction content included in the account transaction request.

[0014] Optionally, if the credit limit batch numbers stored in the credit limit account summary table are all smaller than the transaction batch number, the content of the account credit limit data operation request includes:

[0015] Generate account limit data corresponding to the new limit batch in the limit account summary table, wherein the transaction batch number is used as the limit batch number of the new limit batch, and the account batch limit of the new limit batch is determined by the account batch limit of the most recent limit batch in the limit account summary table and the transaction content included in the account transaction request.

[0016] Optionally, the database server is provided with a quota account table and a final quota table of the account,

[0017] The credit account table stores dynamic data of the current credit batch and dynamic data of the previous credit batch, and the final credit table records static data of historical credit batches;

[0018] The dynamic data of the previous quota batch can be saved in the batch final quota table as a group of static data of historical quota batches when the preset time condition is met.

[0019] Optionally, the method further comprises:

[0020] If no account transaction request is received within a predetermined time interval, an account limit data operation request containing at least the following content is generated and sent to the database server:

[0021] In the credit account table, the credit batch number and account batch limit in the dynamic data of the previous credit batch are replaced with the credit batch number and account batch limit in the dynamic data of the current credit batch;

[0022] Replace the quota batch number in the dynamic data of the current quota batch with the quota batch number corresponding to the current time.

[0023] Optionally, determining a quota batch associated with a transaction batch of the account transaction request includes:

[0024] Compare the transaction batch number of the account transaction request with the quota batch number in the dynamic data of the current quota batch;

[0025] If the transaction batch number is consistent with the credit limit batch number, the current credit limit batch is used as the associated credit limit batch;

[0026] The content of the account limit data operation request at least includes: modifying the account batch limit in the dynamic data of the current limit batch according to the transaction content included in the account transaction request.

[0027] Optionally, the determining of a quota batch associated with a transaction batch of the account transaction request further includes:

[0028] If the transaction batch number is smaller than the credit limit batch number, the current credit limit batch and the previous credit limit batch are both used as associated credit limit batches;

[0029] The content of the account limit data operation request at least includes: modifying the account batch limit in the dynamic data of the current limit batch and the account batch limit in the dynamic data of the previous limit batch according to the transaction content included in the account transaction request.

[0030] Optionally, the determining of a quota batch associated with a transaction batch of the account transaction request further includes:

[0031] If the transaction batch number is greater than the credit limit batch number, the current credit limit batch and the previous credit limit batch are both considered as associated credit limit batches;

[0032] The content of the account limit data operation request at least includes:

[0033] Replace the quota batch number and account batch quota in the dynamic data of the previous quota batch with the quota batch number and account batch quota in the dynamic data of the current quota batch;

[0034] Modify the account batch quota in the dynamic data of the current quota batch according to the transaction content included in the account transaction request;

[0035] The quota batch number in the dynamic data of the current quota batch is replaced with the transaction batch number.

[0036] Optionally, a transaction flow table is provided in the database server for storing the content of the account limit data operation request;

[0037] The content of the account limit data operation request includes: account number, transaction serial number, limit batch number, account batch limit adjustment quantity, and account batch limit adjustment form.

[0038] Optionally, the account balance data stored in the database server may be used to verify the amount incurred and / or provide external bills.

[0039] In a second aspect, an embodiment of the present application further provides a device for processing account limit data, which is applied to a transaction server, wherein the device is used to implement any of the aforementioned methods.

[0040] In a third aspect, an embodiment of the present application further provides an electronic device, including:

[0041] Processor; and

[0042] A memory arranged to store computer executable instructions which, when executed, cause the processor to perform any of the methods described above.

[0043] In a fourth aspect, an embodiment of the present application further provides a computer-readable storage medium, which stores one or more programs. When the one or more programs are executed by an electronic device including multiple application programs, the electronic device executes any of the aforementioned methods.

[0044] At least one of the above technical solutions adopted in the embodiment of the present application can achieve the following beneficial effects: the processing method of the account limit data in the embodiment of the present application can be executed by a separately deployed transaction server, and a database server corresponding to the transaction server is also provided, in which the account limit data corresponding to multiple quota batches are stored as the basis for processing the account limit data. Before processing the account limit data, the transaction server will receive an account transaction request, and then determine the quota batch associated with it in the database server according to the transaction batch of the account transaction request; then generate an account limit data operation request for the corresponding account limit data according to the determined quota batch; finally, send the account limit data operation request to the database server, so that the database server can adjust the corresponding account limit data according to the account limit data operation request. The processing method of the account limit data in the embodiment of the present application can process high-concurrency and uninterrupted transaction requests without suspending business transactions, ensuring the continuous progress of transactions; in addition, by isolating transactions and quotas from the batch dimension, accurate quota data for each batch can be obtained, which meets the data reliability requirements of the financial industry, and provides an accurate data basis for subsequent functions such as amount verification and external bill provision. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0046] Figure 1 A schematic diagram of the structure of a distributed account system according to an embodiment of the present application;

[0047] Figure 2 A flowchart of a method for processing account limit data according to an embodiment of the present application;

[0048] Figure 3 A numerical axis diagram for adjusting the account batch limit in an embodiment of the present application;

[0049] Figure 4 A schematic diagram of the structure of a device for processing account limit data according to an embodiment of the present application;

[0050] Figure 5 This is a schematic diagram of the structure of an electronic device in an embodiment of the present application. DETAILED DESCRIPTION

[0051] In order to make the purpose, technical solution and advantages of the present application clearer, the technical solution of the present application will be clearly and completely described below in combination with the specific embodiments of the present application and the corresponding drawings. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present application.

[0052] The technical solutions provided by various embodiments of the present application are described in detail below in conjunction with the accompanying drawings.

[0053] like Figure 1 As shown, a structural diagram of a distributed account system is provided. The distributed account system includes multiple data centers (Internet Data Center, referred to as IDC) distributed in different regions. Each data center has a unified data access module and an account limit management module. Each account limit management module can manage one or more account limit databases. The distributed account system allocates the limit to a large number of accounts, which are scattered in different account limit databases, so that the program that processes transactions can evenly distribute the transactions on different accounts, and then adjust the account limit of the corresponding account, which greatly improves the processing efficiency of transaction requests.

[0054] However, since account limit data changes in real time and there is a time difference between different servers, in order to obtain accurate limit data for each business date or time batch, it is necessary to dynamically adjust the account limit data for each business date or time batch to ensure the accuracy and reliability of the data.

[0055] Based on this, an embodiment of the present application provides a method for processing account limit data, which is executed by a transaction server, wherein a database server associated with the transaction server stores account limit data corresponding to multiple limit batches, such as Figure 2 As shown, the method includes the following steps S210 to S230:

[0056] Step S210, determining a credit limit batch associated with a transaction batch of the account transaction request.

[0057] The method for processing the account limit data of the embodiment of the present application can be executed by a separate transaction server, and a database server also corresponds to the transaction server, and the database server stores account limit data corresponding to multiple limit batches, that is, the account limit data to be processed by the present application. Before processing the account limit data, the transaction server will receive the user's account transaction request, which can be a batch of high-concurrency account transaction requests received, or a small amount or a single account transaction request, which can be a deduction request for a certain account, or a repayment request. The type of specific requested transaction can be flexibly set by those skilled in the art according to actual conditions, and is not specifically limited here.

[0058] In specific implementation, the account transaction request usually carries the timestamp of the transaction request, which can be understood as the server time of accepting the account transaction request. The transaction batch of the account transaction request can be set according to the time interval of the time. Here, the time period between the start time point and the end time point of each hour can be used as a time batch. For example, 9:00 to 9:59 is the 9th batch, 10:00 to 10:59 is the 10th batch... Assuming that the server accepts an account transaction request at 11:15, the transaction batch of the account transaction request can be recorded as the 11th batch. Transactions on a business date can be divided into 24 batches.

[0059] The essence of a credit limit batch is also a time interval, which can be understood as a credit limit batch determined based on the transaction batch of the account transaction request received in real time. For example, at the time of initialization, the time when the first account transaction request is received is 9:00, and the corresponding transaction batch is the 9th batch. At this time, it is considered that the transaction data of the 9th batch has begun to be received one after another, and the current credit limit batch is recorded as the 9th batch. The embodiment of the present application subdivides the statistics of the account credit limit data into multiple time batches, so that accurate credit limit data for each time batch can be obtained later. Of course, in addition to dividing the batches according to the above-mentioned hourly division, those skilled in the art can also flexibly set other division methods according to actual needs, which are not specifically limited here.

[0060] Therefore, after obtaining the transaction batch in the above account transaction request, the credit limit batch associated with it can be determined. The "associated" here can be understood as the transaction batch carried in the account transaction request, and the transaction batch will affect the credit limit batch that needs to adjust the credit limit. And since the account credit limit data corresponding to multiple credit limit batches are stored in the database server as mentioned above, that is, the account credit limit data corresponds to multiple credit limit batches, it is also possible to determine which credit limit batches need to be modified, and the credit limit batches corresponding to these account credit limit data are considered to be associated with the transaction batch.

[0061] For example, each quota batch records the result of quota processing according to the corresponding transaction batch. It is easy to understand that each time a new quota batch is processed, the initial quota is the same as the final quota of the previous quota batch. However, due to the time difference of the server, it may be the 12th quota batch, but the account transaction request of the 11th transaction batch is received. At this time, the account batch quota of the 11th quota batch needs to be adjusted. But not only that, because the account batch quota of the 12th quota batch is inherited from the 11th batch, the adjustment should also be inherited, that is, the account batch quota of the 12th batch needs to be adjusted accordingly, and so on.

[0062] Step S220: generating an account limit data operation request for corresponding account limit data according to the determined limit batch.

[0063] After obtaining the credit limit batch associated with the transaction batch of the currently received account transaction request, an account credit limit data operation request for the account credit limit data of the corresponding credit limit batch can be generated according to the determined credit limit batch. The account credit limit data operation request here can be understood as a request to adjust the account credit limit data of the associated credit limit batch. Different associated credit limit batches may have different corresponding adjustment methods.

[0064] Step S230: sending the account limit data operation request to the database server so that the database server modifies the corresponding account limit data.

[0065] After receiving the above-mentioned account limit data operation request, the account limit data operation request is sent to the database server for adjustment of the corresponding data and other processing, so that the processed account limit data meets the requirements of data accuracy and reliability of the financial business industry.

[0066] The method for processing account limit data in the embodiment of the present application can process high-concurrency and uninterrupted transaction requests without suspending business transactions, thereby ensuring the continuous progress of transactions; in addition, by isolating transactions and limits from the batch dimension, accurate limit data for each batch can be obtained, meeting the data reliability requirements of the financial industry, and providing an accurate data basis for subsequent functions such as verification of the amount incurred and provision of bills to the outside world.

[0067] In one embodiment of the present application, the account limit data corresponding to each limit batch includes an account batch limit and a limit batch number, which are stored in the limit account summary table of the database server, and the determination of the limit batch associated with the transaction batch of the account transaction request includes: determining a limit batch number that is not less than the transaction batch number of the account transaction request; the content of the account limit data operation request includes: modifying the account batch limit corresponding to the limit batch number determined in the limit account summary table according to the transaction content contained in the account transaction request.

[0068] The account limit data of the embodiment of the present application can be uniformly managed by a total limit account table in the database server, and the total limit account table can include account limit data such as the limit batch number and the corresponding account batch limit. Then as mentioned above, if the account transaction request is generated at 11:15, then it corresponds to the 11th transaction batch, which will inevitably affect the account batch limit of the 11th limit batch, and may also affect the account batch limit of the 12th, 13th, and... limit batches (if any). Then you only need to find the limit batch number of the transaction batch that is not less than the 11th batch in the total limit account table, and modify the corresponding account batch limit.

[0069] Of course, according to the previous analysis, due to the time difference between servers, there may be a situation where the corresponding quota batch number does not exist in the quota account summary table, then a new quota batch needs to be created, such as the following embodiment.

[0070] In one embodiment of the present application, if the credit limit batch numbers stored in the credit limit account summary table are all smaller than the transaction batch number, the content of the account credit limit data operation request includes: generating account credit limit data corresponding to a new credit limit batch in the credit limit account summary table, wherein the transaction batch number is used as the credit limit batch number of the new credit limit batch, and the account batch limit of the new credit limit batch is determined by the account batch limit of the most recent credit limit batch in the credit limit account summary table and the transaction content contained in the account transaction request.

[0071] If the transaction batch number currently received is greater than the maximum value of the credit limit batch numbers stored in the credit limit account summary table, it means that the credit limit data of the transaction batch has not been stored in the current credit limit account summary table. Therefore, the corresponding account credit limit data operation request can be to generate account credit limit data corresponding to the new credit limit batch in the credit limit account summary table, use the currently received transaction batch number as the credit limit batch number of the new credit limit batch, and determine the account batch limit of the new credit limit batch by using the account batch limit of the most recent credit limit batch in the credit account summary table and the transaction content contained in the account transaction request.

[0072] For example, the maximum value of the credit limit batch number stored in the credit limit account summary table is batch 11, and the received transaction batch number is batch 12. At this time, a new credit limit batch for the 12th batch can be created in the credit limit account summary table. The account credit limit for the 12th batch here can be determined based on the account credit limit for the 11th batch and the credit limit adjustment quantity in the currently received account transaction request.

[0073] In one embodiment of the present application, a credit limit account table and a batch-end credit limit table of an account are provided in the database server, the credit limit account table stores dynamic data of a current credit limit batch and dynamic data of a previous credit limit batch, and the batch-end credit limit table records static data of historical credit limit batches; the dynamic data of the previous credit limit batch can be saved in the batch-end credit limit table as a group of static data of historical credit limit batches when a preset time condition is met.

[0074] Different from the above-mentioned embodiment, the account limit data stored in the database server of the embodiment of the present application can also be managed separately by multiple data tables with different functions, for example, it can include a limit account table and a batch-end limit table, as shown in Tables 1 and 2 below. The limit account table in Table 1 is mainly used to record the dynamic data of the current limit batch and the previous limit batch, including the account number, the account batch limit of the current limit batch and the previous limit batch, etc. The batch-end limit table in Table 2 is mainly used to record the static data of each limit batch, including the account number and the final limit data of each limit batch. The advantage of this is that only the limit account table needs to be modified according to each transaction, while the batch-end limit table can be modified regularly without frequent access, thereby ensuring data stability.

[0075] The time difference of the server is usually no more than 5 seconds. Therefore, in order to obtain accurate batch-end quota data, the previous batch quota in the quota account table can be saved to the batch-end quota table at the 30th minute of each hour. At this time, it is considered that the batch quota of the quota batch will basically not change. Of course, the specific time node to synchronize the previous batch quota data in the quota account table to the batch-end quota table can be flexibly set by technicians in this field according to actual conditions, and no specific limitation is made here.

[0076] Table 1

[0077]

[0078] Table 2

[0079]

[0080] In one embodiment of the present application, the method also includes: if no account transaction request is received within a predetermined time interval, generating an account limit data operation request containing at least the following content and sending it to the database server: replacing the limit batch number and account batch limit in the dynamic data of the previous limit batch in the limit account table with the limit batch number and account batch limit in the dynamic data of the current limit batch; replacing the limit batch number in the dynamic data of the current limit batch with the limit batch number corresponding to the current time.

[0081] In actual financial business scenarios, there may be a situation where no account transaction request is received within a time batch. At this time, an operation request for batch switching of the dynamic data of the current credit batch and the previous credit batch in the above credit account table can be generated and sent to the database server for processing. For example, the current credit batch is the 11th batch, and no new account transaction request is received during the time interval from 11:00 to 11:59 corresponding to the credit batch. At this time, the database server can be informed to switch the current credit batch from the original 11th batch to the 12th batch, and the previous credit batch from the original 10th batch to the 11th batch, so that the batch switching can be completed automatically to facilitate the processing of subsequent batches of data.

[0082] In one embodiment of the present application, determining the credit limit batch associated with the transaction batch of the account transaction request includes: comparing the transaction batch number of the account transaction request with the credit limit batch number in the dynamic data of the current credit limit batch; if the transaction batch number and the credit limit batch number are consistent, then taking the current credit limit batch as the associated credit limit batch; the content of the account credit limit data operation request at least includes: modifying the account batch credit limit in the dynamic data of the current credit limit batch according to the transaction content contained in the account transaction request.

[0083] As mentioned above, the dynamic data of the current credit limit batch and the dynamic data of the previous credit limit batch are stored in the credit limit account table. After receiving a new account transaction request, the transaction batch number of the account transaction request can be compared with the credit limit batch number in the dynamic data of the current credit limit batch to determine the associated credit limit batch. If the transaction batch number and the determined credit limit batch number are equal, it means that the received account transaction request is a request to adjust the account credit limit data of the current credit limit batch. Then, the account batch credit limit in the dynamic data of the current credit limit batch can be adjusted directly according to the transaction content contained in the account transaction request, such as the adjustment credit limit.

[0084] For example, assuming that an account transaction request x1 is currently received, the corresponding transaction batch number is batch 12, and the request for deduction is 1000. The current credit limit batch number is also batch 12, and the corresponding account credit limit is 10000. The database server can deduct the account credit limit of the 12th batch, and the account credit limit with credit limit batch number batch 12 is 10000-1000=9000.

[0085] In one embodiment of the present application, the determining of the credit limit batch associated with the transaction batch of the account transaction request also includes: if the transaction batch number is less than the credit limit batch number, then both the current credit limit batch and the previous credit limit batch are regarded as associated credit limit batches; the content of the account credit limit data operation request at least includes: based on the transaction content contained in the account transaction request, modifying the account batch credit limit in the dynamic data of the current credit limit batch and the account batch credit limit in the dynamic data of the previous credit limit batch.

[0086] If the transaction batch number is smaller than the quota batch number, it means that the quota data of the previous quota batch of the current quota batch has not been fully processed due to the time difference of the server, and the account quota data of the previous quota batch needs to be adjusted. Since the quota data of the current quota batch is associated with the quota data of the previous quota batch, it will change with the change of the quota data of the previous quota batch. Therefore, if the transaction batch number is smaller than the quota batch number, the account data of the current quota batch will also be adjusted. The specific adjustment method can be to adjust the account batch quota in the dynamic data of the current quota batch and the previous quota batch at the same time according to the transaction content contained in the account transaction request, such as the adjustment quota.

[0087] For example, based on the above embodiment, assuming that an account transaction request x2 is currently received, the corresponding transaction batch number is batch 11, and a deduction of 2000 is requested. The current credit limit batch number is batch 12, and the corresponding account limit is 9000. The previous credit limit batch number is batch 11, and the corresponding account limit is 10000. The database server can deduct the account limits of the 12th and 11th batches respectively, and the account limit of the credit limit batch number is batch 12 is 9000-2000=7000, and the account limit of the credit limit batch number is batch 11 is 10000-2000=8000.

[0088] In order to facilitate the understanding of the above embodiments, Figure 3 As shown, a numerical axis diagram for adjusting the account batch limit is provided. Specifically, transactions on a business date can be divided into 24 batches. If the current limit batch number is batch 12, then for the account transaction request received for batch 12, only the account limit of the 12th batch needs to be adjusted. For the account transaction request received for batch 11, the account limits of the 11th and 12th batches need to be adjusted.

[0089] In one embodiment of the present application, the determination of the credit limit batch associated with the transaction batch of the account transaction request also includes: if the transaction batch number is greater than the credit limit batch number, then both the current credit limit batch and the previous credit limit batch are regarded as associated credit limit batches; the content of the account credit limit data operation request at least includes: replacing the credit limit batch number and the account batch limit in the dynamic data of the previous credit limit batch with the credit limit batch number and the account batch limit in the dynamic data of the current credit limit batch; modifying the account batch limit in the dynamic data of the current credit limit batch according to the transaction content contained in the account transaction request; replacing the credit limit batch number in the dynamic data of the current credit limit batch with the transaction batch number.

[0090] If the transaction batch number is greater than the credit limit batch number, it means that the account credit limit data of the transaction batch number has not been stored in the credit limit account table. At this time, the credit limit batch number and account batch limit of the current credit limit batch can be switched to the credit limit batch number and account batch limit of the previous credit limit batch, and then the account batch limit of the current credit limit batch can be determined based on the account batch limit of the previous credit limit batch and the transaction content in the currently received account transaction request, such as adjustment limit.

[0091] For example, the transaction batch number is batch 12, the deduction requested is 2000, the credit limit batch number is batch 11, and the corresponding account batch credit limit is 7000. At this time, the current credit limit batch in the credit limit account table can be switched from the 11th batch to the 12th batch, and the previous credit limit batch can be switched from the 10th batch to the 11th batch, and the corresponding account credit limit is 7000. Then, based on the account credit limit of the 11th batch and the transaction content in the currently received account transaction request, such as adjusting the credit limit, it can be determined that the account credit limit of the 12th batch is 7000-2000=5000.

[0092] It should be noted that in actual application scenarios, the time difference between servers will be checked through a clock server (Network Time Protocol, abbreviated as NTP). If the time difference exceeds the preset time difference, such as 5 seconds, an alarm will be issued and the servers with large time differences will be eliminated, thereby ensuring that the server time difference involved in the technical solution of this application will not exceed 5 seconds.

[0093] Since the time difference between servers is relatively short, generally only the quota data of adjacent quota batches will be affected, and there will almost never be a situation where cross-quota batches are affected. That is to say, if you have started to receive account transaction requests after 12 o'clock, it is unlikely that you will receive account transaction requests at 10 o'clock later.

[0094] In one embodiment of the present application, a transaction flow table is provided in the database server for storing the content of the account limit data operation request; the content of the account limit data operation request includes: account number, transaction flow number, limit batch number, account batch limit adjustment quantity, and account batch limit adjustment form.

[0095] In addition to storing the credit limit account table and the batch final credit limit table, the database server of the embodiment of the present application can also store a transaction flow table for recording transaction flow information, as shown in Table 3 below. The transaction flow table can specifically include information such as account number, transaction flow number, credit limit batch number, adjustment credit limit and adjustment type. These transaction flow information can be obtained from the received account transaction request.

[0096] Table 3

[0097]

[0098] In one embodiment of the present application, the account limit data stored in the database server can be used to verify the amount incurred and / or provide external bills.

[0099] Through the processing flow of the account limit data of the above embodiments, accurate and reliable account limit data of each batch can be finally obtained. Based on this, the final limit (batch end limit) of one of the batches can be selected as the final limit (day-end limit) of a business date according to actual business needs, thereby realizing the daily switching of the distributed account system. For example, the batch end limit at 22:00 on September 1 is used as the day-end limit on September 1, and the limit data after 22:00 on September 1 will be used as the limit data for the next business date, September 2.

[0100] In actual business scenarios, the account limit data of each batch obtained in the above embodiment can also be used to check the amount of occurrence and provide bills to the outside. The amount of occurrence can be understood as the sum of all current accounts incurred on the debit or credit side of a certain business within a certain period of time. In the embodiment of the present application, all transaction flows of the same batch can be summarized and netted, and compared with the final batch limit of each account and the difference in the final batch limit between the two batches, so as to check whether the amount of occurrence of each batch is accurate. In addition, the transaction flow details can be provided according to the batch dimension, and the sum of the final batch limit of all accounts in the corresponding batch can be provided to the requester to meet the different business needs of the requester.

[0101] It should be noted that the batch numbering rules mentioned in the above embodiments are only simplified for the convenience of description. In actual application scenarios, more complex numbering rules can be set according to different business needs. For example, if an account transaction request is received at 10:10 am on September 1, 2020, the transaction batch number can be 202009010010, where the last two digits can represent the 10th transaction batch. The specific setting can be flexibly selected by technicians in this field according to actual needs, as long as each transaction batch or quota batch on each business date can be distinguished.

[0102] The embodiment of the present application also provides an account limit data processing device 400, which is applied to a transaction server, wherein a database server associated with the transaction server stores account limit data corresponding to multiple limit batches, such as Figure 4 As shown, the device 400 includes:

[0103] A determination unit 410, configured to determine a quota batch associated with a transaction batch of an account transaction request;

[0104] A generating unit 420, configured to generate an account limit data operation request for corresponding account limit data according to the determined limit batch;

[0105] The sending unit 430 is used to send the account limit data operation request to the database server, so that the database server modifies the corresponding account limit data.

[0106] Figure 5 This is a schematic diagram of the structure of an electronic device according to an embodiment of the present application. Figure 5 At the hardware level, the electronic device includes a processor, and optionally also includes an internal bus, a network interface, and a memory. The memory may include a memory, such as a high-speed random access memory (RAM), and may also include a non-volatile memory (non-volatile memory), such as at least one disk storage. Of course, the electronic device may also include hardware required for other services.

[0107] The processor, network interface and memory can be interconnected through an internal bus, which can be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 5 Only one bidirectional arrow is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0108] The memory is used to store the program. Specifically, the program may include a program code, and the program code includes a computer operation instruction. The memory may include a memory and a non-volatile memory, and provides instructions and data to the processor.

[0109] The processor reads the corresponding computer program from the non-volatile memory into the memory and then runs it, forming a processing device for the account limit data at the logical level. The processor executes the program stored in the memory and is specifically used to perform the following operations:

[0110] Determine the quota batch associated with the transaction batch of the account transaction request;

[0111] Generate an account limit data operation request for corresponding account limit data according to the determined limit batch;

[0112] The account limit data operation request is sent to the database server so that the database server modifies the corresponding account limit data.

[0113] The above application Figure 4The method performed by the processing device for the account limit data disclosed in the illustrated embodiment can be applied to a processor or implemented by a processor. The processor may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by an integrated logic circuit of hardware in the processor or an instruction in the form of software. The above processor can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc. The steps of the method disclosed in the embodiments of the present application can be directly embodied as a hardware decoding processor for execution, or a combination of hardware and software modules in the decoding processor for execution. The software module can be located in a storage medium mature in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, or an electrically erasable programmable memory, a register, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0114] The electronic device may also perform Figure 4 A method for executing an account limit data processing device in a Figure 4 The functions of the illustrated embodiment will not be described in detail in the embodiments of the present application.

[0115] The present application also provides a computer-readable storage medium, which stores one or more programs, wherein the one or more programs include instructions, which, when executed by an electronic device including multiple application programs, enable the electronic device to execute Figure 4 The method executed by the processing device for the account limit data in the illustrated embodiment is specifically used to execute:

[0116] Determine the quota batch associated with the transaction batch of the account transaction request;

[0117] Generate an account limit data operation request for corresponding account limit data according to the determined limit batch;

[0118] The account limit data operation request is sent to the database server so that the database server modifies the corresponding account limit data.

[0119] Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, systems, or computer program products. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0120] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0121] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0122] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0123] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0124] The memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0125] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0126] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0127] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.

[0128] The above is only an embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.

Claims

1. A method for processing account limit data, executed by a transaction server, wherein: The database server associated with the transaction server stores account limit data corresponding to multiple limit batches, and the method includes: Determine the quota batch associated with the transaction batch of the account transaction request; Generate an account limit data operation request for corresponding account limit data according to the determined limit batch; Sending the account limit data operation request to the database server so that the database server modifies the corresponding account limit data; The account credit data corresponding to each credit batch includes the account batch credit and credit batch number, which are stored in the credit account summary table of the database server. The credit batch associated with the transaction batch of the account transaction request includes: Determine the quota batch number that is not less than the transaction batch number of the account transaction request; The content of the account limit data operation request includes: modifying the account batch limit corresponding to the limit batch number determined in the limit account summary table according to the transaction content included in the account transaction request.

2. The method of claim 1, wherein: Each transaction batch and quota batch corresponds to a predetermined time interval.

3. The method of claim 1, wherein: If the credit batch numbers stored in the credit account summary table are all smaller than the transaction batch number, the content of the account credit data operation request includes: Generate account limit data corresponding to the new limit batch in the limit account summary table, wherein the transaction batch number is used as the limit batch number of the new limit batch, and the account batch limit of the new limit batch is determined by the account batch limit of the most recent limit batch in the limit account summary table and the transaction content included in the account transaction request.

4. The method of claim 2, wherein: The database server is provided with an account quota table and a final quota table of the account. The credit account table stores dynamic data of the current credit batch and dynamic data of the previous credit batch, and the final credit table records static data of historical credit batches; The dynamic data of the previous quota batch can be saved in the batch final quota table as a group of static data of historical quota batches when the preset time condition is met.

5. The method of claim 4, wherein: The method further includes: If no account transaction request is received within a predetermined time interval, an account limit data operation request containing at least the following content is generated and sent to the database server: In the credit account table, the credit batch number and account batch limit in the dynamic data of the previous credit batch are replaced with the credit batch number and account batch limit in the dynamic data of the current credit batch; Replace the quota batch number in the dynamic data of the current quota batch with the quota batch number corresponding to the current time.

6. The method of claim 4, wherein: Determining a quota batch associated with a transaction batch of an account transaction request includes: Compare the transaction batch number of the account transaction request with the quota batch number in the dynamic data of the current quota batch; If the transaction batch number is consistent with the credit limit batch number, the current credit limit batch is used as the associated credit limit batch; The content of the account limit data operation request at least includes: modifying the account batch limit in the dynamic data of the current limit batch according to the transaction content included in the account transaction request.

7. The method of claim 4, wherein: The step of determining a quota batch associated with a transaction batch of an account transaction request further includes: If the transaction batch number is smaller than the credit limit batch number, the current credit limit batch and the previous credit limit batch are both used as associated credit limit batches; The content of the account limit data operation request at least includes: modifying the account batch limit in the dynamic data of the current limit batch and the account batch limit in the dynamic data of the previous limit batch according to the transaction content included in the account transaction request.

8. The method of claim 4, wherein: The step of determining a quota batch associated with a transaction batch of an account transaction request further includes: If the transaction batch number is greater than the credit limit batch number, the current credit limit batch and the previous credit limit batch are both considered as associated credit limit batches; The content of the account limit data operation request at least includes: Replace the quota batch number and account batch quota in the dynamic data of the previous quota batch with the quota batch number and account batch quota in the dynamic data of the current quota batch; Modify the account batch quota in the dynamic data of the current quota batch according to the transaction content included in the account transaction request; The quota batch number in the dynamic data of the current quota batch is replaced with the transaction batch number.

9. The method of claim 1, wherein: The database server is provided with a transaction flow table for storing the content of the account limit data operation request; The content of the account limit data operation request includes: account number, transaction serial number, limit batch number, account batch limit adjustment quantity, and account batch limit adjustment form.

10. The method of claim 1, wherein: The account balance data stored in the database server can be used to check the amount incurred and / or provide external bills.

11. A device for processing account limit data, applied to a transaction server, wherein: The database server associated with the transaction server stores account limit data corresponding to multiple limit batches, and the device is used to implement any method described in claims 1 to 10.

12. An electronic device comprising: processor; as well as A memory arranged to store computer executable instructions, which when executed cause the processor to perform the method of any one of claims 1 to 10.

13. A computer-readable storage medium storing one or more programs, which, when executed by an electronic device including a plurality of application programs, causes the electronic device to execute any one of the methods of claims 1 to 10.

Citation Information

Patent Citations

  • Account data management method and device, and server

    CN106934025A

  • Transaction data processing method and system

    CN111353781A