Credit limit control methods, devices, readable storage media and program products

By using a multi-replica architecture for the quota service, deploying across data centers and allocating quotas on demand, the problems of network latency and low quota utilization in the transaction system of the distributed quota management architecture are solved, achieving more efficient quota management and more stable transaction processing.

CN123118231APending Publication Date: 2026-11-17CHINA UNIONPAY
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611369449.4
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-09-03
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

In a distributed quota management architecture, the transaction system suffers from increased transaction rejections or processing delays due to network latency or jitter, and there is a coexistence of idle and scarce quotas, resulting in low account quota utilization.

Method used

Adopting a multi-replica architecture for quota services, quota service replicas are deployed across data centers. The same account data is maintained through a consistency protocol, and quotas are allocated across centers as needed. By combining the quotas to be allocated for the target account with the available quotas in other data centers, quota scheduling and overall management across data centers can be achieved.

Benefits of technology

It reduces the impact of network latency and jitter on transactions, improves the efficiency of quota utilization, reduces quota fragmentation, and ensures the continuous availability of quota services when some data centers are not functioning properly.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123118231A_ABST
    Figure CN123118231A_ABST
Patent Text Reader

Abstract

This application provides a quota control method, device, readable storage medium, and program product. The method includes: receiving a quota request sent by a first business system; obtaining a quota to be allocated for a target account from first account data, wherein the target account is the account indicated by the account information; wherein the first account data includes quota data for multiple accounts, the quota data including a total quota and a quota to be allocated; determining a second quota to be allocated to the first business system based on the quota to be allocated, or the quota to be allocated and the available quota of the target account in at least one second business system; the first business system and the second business system are deployed in different data centers; the available quota is the quota already allocated to the second business system but not used; the second quota is greater than or equal to the first quota; allocating the second quota to the target account in the first business system, and synchronously updating the first account data in multiple quota service copies.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a quota control method, device, readable storage medium, and program product. Background Technology

[0002] In high-frequency transaction scenarios such as payment clearing and e-commerce transactions, the high availability, low latency, and reasonable allocation of transaction quotas are essential for ensuring transaction continuity. To guarantee transaction continuity and avoid data center-level anomalies, some related technologies can adopt a distributed quota management architecture, which involves splitting the account into multiple sub-accounts based on the total transaction quota, with each sub-account maintained by an independent data center.

[0003] However, as the business scale expands and the number of data centers increases, the above-mentioned distributed quota management architecture faces the following problems: On the one hand, since each transaction in the transaction processing business system needs to be verified, if joint verification across data centers is adopted, transaction rejection or processing delay may be increased due to network latency or jitter; on the other hand, fragmentation problems may occur where some data centers have both idle and scarce quotas, resulting in both idle and scarce quotas and a low overall utilization rate of account quotas. Summary of the Invention

[0004] This application provides a limit control method, device, readable storage medium, and program product to improve at least some of the above-mentioned problems.

[0005] In a first aspect, embodiments of this application provide a quota control method applied to a quota service replica, wherein the quota service replica is any one of multiple replicas of a quota service, the quota service centrally provides quota management services for multiple business systems, and the multiple quota service replicas have the same first account data; the method includes: receiving a quota request sent by a first business system, the quota request including data center information, account information, and a first quota; obtaining a quota to be allocated for a target account from the first account data, the target account being the account indicated by the account information; wherein the first account data includes quota data for each of multiple accounts, the quota data including a total quota and a quota to be allocated; determining a second quota to be allocated to the first business system based on the quota to be allocated, or the quota to be allocated and the available quota of the target account in at least one second business system; the first business system and the second business system are deployed in different data centers; the available quota is the quota already allocated to the second business system but not used; the second quota is greater than or equal to the first quota; allocating the second quota to the target account in the first business system, and synchronously updating the first account data in the multiple quota service replicas.

[0006] Secondly, embodiments of this application provide a credit limit control method applied to a first business system, comprising: responding to insufficient local available credit limit for a target account, sending a credit limit request to a corresponding credit limit service copy; wherein the credit limit service copy is one of multiple credit limit service copies, the multiple credit limit service copies include the same first account data, the first account data includes credit limit data for each of the multiple accounts, the credit limit data includes a total credit limit and a credit limit to be allocated, the credit limit request includes account information of the target account, data center information where the first business system is located, and a first credit limit; receiving a second credit limit allocated by the corresponding credit limit service copy, the second credit limit being determined by the corresponding credit limit service copy based on the credit limit to be allocated for the target account in the first account data, or the credit limit to be allocated and the available credit limit of the target account in at least one second business system; the first business system and the at least one second business system are deployed in different data centers; and updating the available credit limit in the local second account data according to the second credit limit.

[0007] Thirdly, embodiments of this application provide a credit limit control device, configured in a credit limit service. The credit limit service includes multiple credit limit service copies distributed across different data centers. The credit limit service centrally provides credit limit management services to multiple business systems, and the multiple credit limit service copies have the same first account data. The device includes: a first receiving unit, configured to receive a credit limit request sent by a first business system, the credit limit request including data center information, account information, and a first credit limit; and a first obtaining unit, configured to obtain the credit limit to be allocated for a target account from the first account data, the target account being the account indicated by the account information; wherein, the first account data includes multiple accounts. Each has its own credit limit data, including a total credit limit and a credit limit to be allocated; a first determining unit is configured to determine a second credit limit to be allocated to the first business system based on the credit limit to be allocated, or the credit limit to be allocated and the available credit limit of the target account in at least one second business system; the first business system and the second business system are deployed in different data centers; the available credit limit is the credit limit that has been allocated to the second business system but has not been used; the second credit limit is greater than or equal to the first credit limit; an allocation unit is configured to allocate the second credit limit to the target account in the first business system and synchronously update the first account data in multiple credit limit service copies.

[0008] Fourthly, embodiments of this application provide a credit limit control device, configured in a first business system, comprising: a first sending unit, configured to send a credit limit request to a corresponding credit limit service copy in response to insufficient local available credit limit of a target account; wherein the credit limit service copy is one of multiple credit limit service copies, the multiple credit limit service copies include the same first account data, the first account data includes credit limit data of each of the multiple accounts, the credit limit data includes a total credit limit and a credit limit to be allocated, and the credit limit request includes account information of the target account, data center information where the first business system is located, and a first credit limit; a second receiving unit, configured to receive a second credit limit allocated by the corresponding credit limit service copy, the second credit limit being determined by the corresponding credit limit service copy based on the credit limit to be allocated of the target account in the first account data, or the credit limit to be allocated and the available credit limit of the target account in at least one second business system; the first business system and the at least one second business system are deployed in different data centers; and an updating unit, configured to update the available credit limit in the local second account data according to the second credit limit.

[0009] Fifthly, embodiments of this application provide a credit limit control system, including multiple business systems and a credit limit service. The credit limit service provides centralized services for the credit limits of the multiple business systems. The credit limit service includes multiple credit limit service copies, which have the same first account data. The first account data includes the total credit limit, the credit limit to be allocated, and the credit limit used by each of the multiple accounts. In response to insufficient local available credit limit for a target account, a first business system sends a credit limit request to the corresponding credit limit service copy. The credit limit request includes a first credit limit, information about the data center where it is located, and account information of the target account. The first business system can be any one of the multiple business systems. The corresponding credit limit service copy determines a second credit limit based on the credit limit to be allocated for the target account in the first account data, or the available credit limit of the target account in at least one second business system. The second credit limit is then allocated to the first business system. The multiple credit limit service copies simultaneously update the first account data. The first business system receives the second credit limit, updates its local second account data, and processes pending business based on the updated second account data.

[0010] Sixthly, embodiments of this application provide a limit control device, including: a memory and a processor;

[0011] The memory stores the instructions that the computer executes;

[0012] The processor executes computer execution instructions stored in memory, causing the processor to perform the first aspect, the second aspect, and / or various possible implementations of the first and second aspects as described above.

[0013] In a seventh aspect, embodiments of this application provide a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the first aspect, the second aspect, and / or various possible implementations of the first and second aspects described above.

[0014] Eighthly, embodiments of this application provide a computer program product, including a computer program that, when executed by a processor, implements the first aspect, the second aspect, and / or various possible implementations of the first and second aspects described above.

[0015] The quota control method, device, readable storage medium, and program product provided in this application embodiment provide centralized quota services to multiple business systems by having multiple copies of the quota service, each copy maintaining the same first account data. The quota service copies can achieve unified quota scheduling among business systems deployed across data centers. When a quota request carrying data center information, account information, and a first quota is received from a first business system, a second quota not less than the first quota can be determined and allocated to the first business system by combining the target account's pending quota, or by combining the pending quota with the available but unused quota of the target account in other data center second business systems. Compared to the business system performing cross-center quota sharing, quota aggregation calculation, and quota scheduling logic for each transaction, this solution only initiates a cross-center, on-demand centralized allocation to obtain a second quota when the available quota in the business system's local environment is insufficient. After allocation, subsequent quota deductions for multiple transactions are directly executed locally in the first business system, eliminating the need for each transaction to access the quota service across centers, thus reducing network latency or jitter-induced business rejections or increased processing delays. Furthermore, in this solution, quota scheduling and cross-center available quota aggregation calculation are all handled by the quota service. The primary business system only needs to focus on whether the business is compliant and whether the local quota is sufficient. The complex logic of cross-center quota coordination, quota consistency maintenance, and cross-center synchronization is all handled by the quota service, reducing the complexity of the business system. In addition, the quota service alleviates the problem of both idle and scarce quotas by allocating unused quotas on demand and adjusting them between business systems in different data centers, thus improving the overall utilization efficiency of account quotas. Moreover, the quota service can maintain continuous availability when some replicas or data centers are abnormal through multi-replica cross-center deployment. Attached Figure Description

[0016] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0017] Figure 1 A schematic diagram of the system architecture in which the quota control method provided in this application is applied;

[0018] Figure 2 A flowchart illustrating the quota control method provided in some embodiments of this application;

[0019] Figure 3 A flowchart illustrating the quota control method provided in other embodiments of this application;

[0020] Figure 4 A flowchart illustrating the quota control method provided in some embodiments of this application;

[0021] Figure 5 A schematic diagram of the credit limit control device provided in this application;

[0022] Figure 6 A schematic diagram of the credit limit control device provided in this application;

[0023] Figure 7 A schematic diagram of the credit limit control device provided in this application.

[0024] The accompanying drawings have illustrated specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to specific embodiments. Detailed Implementation

[0025] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application.

[0026] A single account can be involved in different types of business, such as credit business based on the payment institution's credit, payment business, fund transfer business, and clearing and settlement business based on the payment institution's reserve funds, prepayment and settlement business, and collection and payment on behalf of others business based on the prepayment and payment model, as well as carry-over business based on cross-cycle or revolving use rules. Different types of business correspond to different types of credit limits, such as credit limits, reserve fund mapping limits, prepayment and payment limits, and carry-over limits. In the distributed credit limit management architecture, a single account is split into multiple sub-accounts, and the account's credit limit is statically divided into multiple sub-limits, with each sub-account corresponding to one sub-limit. Each sub-account is managed and maintained by an independent data center; when any data center experiences an anomaly, the remaining centers can still continue to process transactions based on their local sub-accounts, thus handling data center-level anomalies.

[0027] In a distributed quota management architecture, when a transaction request enters the business system of the corresponding data center, the data center verifies and deducts the quota for the transaction based on the sub-quota of the local sub-account. When the local quota is insufficient, in addition to deducting the remaining sub-quota of the local data center, it can also deduct the available quota of other data centers. That is, when the local quota is insufficient, a joint quota verification and deduction across data centers will be initiated to meet the transaction quota requirements. The above process is completed by the transaction system.

[0028] However, with the increase in transaction frequency and the number of data centers, the following problems arise: Severe fragmentation of credit limits: Because different types of credit limits for the same account are split across multiple data center sub-accounts, it's possible for an account to have idle credit limits in one center while experiencing a shortage in others. In a multi-center scenario, if a sub-account in one center has insufficient credit limits, frequent cross-center joint verification is required, which may lead to false transaction rejections or significant latency issues during network fluctuations.

[0029] Figure 1 A schematic diagram of the system architecture in which the quota control method provided in this application is applied is shown, for example. Figure 1 As shown, the system architecture includes multiple data centers 1, 2, ..., N, each deploying one business system and one credit limit service replica. Each of the business systems 1, 2, ..., N can contain local credit limit data. Local credit limit data can include used credit and available credit. The business systems in each data center are independent and do not communicate directly. The credit limit service is deployed in a multi-replica cross-data center cluster, with each credit limit service replica 1, 2, ..., N maintaining the same account credit limit data. Multiple credit limit service replicas 1, 2, ..., N form a cross-data center cluster through a consistency protocol, providing logically centralized credit limit management capabilities. Each credit limit service replica 1, 2, ..., N can handle read and write requests. Business systems 1, 2, ..., N can receive business requests, use their local available credit to complete the credit limit deduction indicated by the business request, or obtain credit from credit limit service replicas 1, 2, ..., N to complete the credit limit deduction.

[0030] Taking data center 1 as an example, business system 1 can perform business processing and manage local credit limit data. When a business request arrives, business system 1 prioritizes using the local available credit limit corresponding to the account to complete the business request verification and credit limit deduction, without needing to make cross-data center calls. When the local available credit limit of the aforementioned account is insufficient, a credit limit request can be initiated to credit limit service replica 1. After receiving the credit limit request, credit limit service replica 1 first reads the global available credit limit of the account. If the global available credit limit is sufficient, it allocates the corresponding credit limit to business system 1; at the same time, multiple credit limit service replicas 1, 2, ..., N simultaneously update the global available credit limit of the account. If the global available credit limit of the account is insufficient, but business systems in other data centers (such as data center N) have sufficient available credit limit corresponding to the account, credit limit service replica 1 can reclaim the available credit limit of the account in business system N through credit limit service replica N of data center N, merge the reclaimed credit limit with the global available credit limit, and then extract the corresponding credit limit from the merged credit limit and allocate it to business system 1. Business system N updates the local available credit limit for this account, and credit service replicas 1, 2, ..., N update the global available credit limit for this account. If the global available credit limit for this account is insufficient, and the available credit limit for this account and the global available credit limit in each of business systems 2, ..., N are insufficient to meet the credit limit indicated in the business request, then the credit limit deduction indicated in the business request is rejected, and a prompt message is returned, which may indicate that the account has insufficient credit limit, etc.

[0031] Figure 1 The architecture demonstrates that a quota service replica and a business system can be deployed simultaneously in the same data center. It is understandable that in other scenarios, a quota service replica or a business system can be deployed separately in the same data center. The data center deploying the business system can communicate with the data center deploying the quota service replica to obtain quotas.

[0032] Figure 2 A flowchart illustrating the credit limit control method provided in this application is shown below. Figure 2 As shown, this method can be applied to a credit limit service, which includes multiple copies of the credit limit service distributed across different data centers. The credit limit service centrally provides credit limit management services to multiple business systems, and the multiple copies of the credit limit service have the same first account data. The method includes the following steps:

[0033] S201: Receive a credit limit request sent by the first business system. The credit limit request includes data center information, account information, and a first credit limit.

[0034] The entity executing the credit limit control method in this application can be a credit limit service, specifically any one of multiple copies of the credit limit service. A credit limit service refers to a service used to centrally manage account credit limits for multiple business systems. It can be a standalone credit limit management system or a credit limit management component running in a cluster. Multiple copies of the credit limit service can be deployed in different data centers; for example, credit limit service copy 1 is deployed in data center 1, and credit limit service copy 2 is deployed in data center 2. Multiple copies of the credit limit service have the same first account data. The first account data can include the total credit limit, allocated credit limit, used credit limit, and pending credit limit for each account. A business system refers to a system that needs to consume account credit limits to process business transactions, such as a payment business system or a credit business system. Business systems can be deployed in different data centers. The first business system is the business system that initiates the credit limit request; its local available credit limit is insufficient, requiring the credit limit service to supplement the credit limit. Pending credit limit is the globally available credit limit recorded in the credit limit service that can still be allocated to business systems; for example, pending credit limit can be obtained by subtracting the allocated credit limit from the total account credit limit. Data center information refers to the information of the data center where the first business system is located, such as data center number, name, and computer room location identifier. Account information refers to the information of the account for which the credit limit of the first business system will be deducted in this transaction, including but not limited to account number, account type, and account entity identifier. The first credit limit refers to the amount of credit limit to be deducted from the first business system for this transaction.

[0035] The business system can maintain second account data locally. The second account data includes the used quota and unused quota (i.e. the available quota of the business system) that have been allocated to the business system for multiple accounts.

[0036] When the first business system detects insufficient local available credit, it sends a credit request to the credit service. Illustratively, this credit request can be sent to a copy of the credit service located in the same data center as the first business system. The first credit limit may be, for example, the credit limit to be replenished, and the credit request may also include information about the data center where the first business system is located, such as the data center's identifier or number. Account information indicates the target account for which credit replenishment is to be performed.

[0037] The aforementioned credit limit service may receive the aforementioned credit limit request through the copy of the credit limit service.

[0038] S202: Obtain the quota to be allocated for the target account from the first account data, where the target account is the account indicated by the account information; wherein, the first account data includes quota data for each of the multiple accounts, and the quota data includes the total quota and the quota to be allocated.

[0039] In some scenarios, upon receiving a credit limit request, the aforementioned credit limit service parses the account information from the request. The credit limit service can then use the account indicated by the account information as the target account and read the target account's pending credit limit from the first account data. The pending credit limit can be understood as the total amount of credit that the target account can currently be allocated by the credit limit service. For example, if the target account has a total available credit limit of 1000 and an allocated credit limit of 700 (including used and unused credit), then the pending credit limit is 300.

[0040] S203: Determine a second quota to be allocated to the first business system based on the quota to be allocated, or the quota to be allocated and the available quota of the target account in at least one second business system; the first business system and the second business system are deployed in different data centers; the available quota is the quota that has been allocated to the second business system but has not been used; the second quota is greater than or equal to the first quota.

[0041] The second business system refers to a business system other than the first business system that may hold the target account's available credit limit, and the second business system is deployed in a different data center than the first business system. Available credit limit refers to the credit limit that has been allocated to the second business system but has not yet been used.

[0042] The second limit is the amount of credit allocated to the first business system by the credit service. The second limit is greater than or equal to the first limit.

[0043] If the target account has sufficient available credit, the credit limit service can determine a second credit limit based on the available credit limit. For example, if the available credit limit is 300 and the first credit limit is 50, the credit limit service can directly determine a second credit limit of 50 or more, such as 100, from the available credit limit. When determining the second credit limit, the credit limit service can ensure that the second credit limit at least covers the first credit limit, based on the size of the first credit limit.

[0044] If the aforementioned unallocated quota is insufficient, available quotas from multiple secondary business systems can be combined to obtain the aforementioned secondary quota. After determining the secondary quota, the quota service records the quota source corresponding to the secondary quota, including the usage of the unallocated quota and the usage of the available quotas in each secondary business system.

[0045] In some implementations, determining the second quota to be allocated to the first business system based on the quota to be allocated includes:

[0046] Based on the business processing characteristics of the target account within the historical time window, predict the third quota consumed by the target account in the first business system within the future time window;

[0047] The second quota is determined based on the third quota, the quota to be allocated, and the quota limit corresponding to a single business system.

[0048] The aforementioned historical time window refers to a past period used to collect the business processing characteristics of the target account, such as the past 7 days, the past 24 hours, or the past 1 hour. Business processing characteristics refer to information related to credit limit consumption generated by the target account on the first business system, such as the number of transactions, the amount involved in each transaction, the distribution of transaction types, and the credit limit consumption rate at different times. The third credit limit refers to the total credit limit that the target account may need to consume on the first business system within a future time window, predicted based on historical business processing characteristics. The future time window can be pre-configured, such as the next 10 minutes, the next hour, or the next day. The credit limit limit corresponding to a single business system refers to the maximum available credit limit for the target account that the business system can hold locally, set for the business system, to prevent a single business system from holding too much credit limit, leading to a shortage of credit limit in other business systems.

[0049] The credit limit service can first obtain the transaction processing characteristics of the target account within a historical time window on the first business system. These characteristics can be asynchronously collected by the first business system during operation and reported to the credit limit service replica. For example, the first business system can collect historical transaction processing data by capturing network packets or collecting transaction processing logs; this collection process does not affect online transaction processing. After cleaning and aggregating the collected raw data by account, a transaction processing profile of the target account can be formed. This profile can include basic characteristics, transaction processing characteristics, and time-series characteristics. Basic characteristics include account number and data center number; transaction processing characteristics include the amount involved, the number of transactions, the distribution of transaction types, and the usage percentage of various credit limits; and time-series characteristics can be aggregated at multiple time granularities such as hourly, daily, weekly, and monthly.

[0050] In some implementations, predicting the third credit limit of the target account in the first business system in a future time window based on the business processing characteristics of the target account in the historical time window includes: inputting the account information and business processing characteristics of the target account into the corresponding prediction model, and outputting the third credit limit by the prediction model.

[0051] Credit limit services can train predictive models based on the historical transaction characteristics of each account. The training process for these predictive models can be supervised or unsupervised, which will not be elaborated here. The aforementioned predictive models can be of various types, such as gradient boosting tree models and time-series models. In some scenarios, different models can be used depending on the account's transaction activity and the amount of historical data. For example, for accounts with relatively stable transaction behavior and a small amount of historical data, a gradient boosting tree model can be used by default. This type of model has fast inference speed, good interpretability, and is less prone to overfitting when the amount of data is small. For accounts with stronger time-series transaction characteristics and a larger sample size, a time-series model can be used to handle complex multi-period patterns.

[0052] Upon receiving a credit limit request from the first business system, the credit limit service can parse the account information and the initial credit limit from the request. The account information indicates the target account. The credit limit service can then invoke a prediction model matching the target account to predict the target account's third credit limit within a future time window. This future time window can be pre-configured, such as the next 10 minutes or the next hour. During the prediction process, the credit limit service can extract information such as the account information, data center number, and initial credit limit from the credit limit request as input, and the prediction model will output the expected credit limit consumption value for the target account within the future time window.

[0053] In these implementations, by inputting account information and historical business processing characteristics into the corresponding prediction model, the model outputs a third credit limit for a future time window. This allows credit limit allocation to no longer rely solely on the current application amount, but rather to dynamically predict based on the account's business processing behavior. This enables a quick and reasonable estimation of the account's credit limit needs over a future period, making the second credit limit closer to actual consumption. This reduces the likelihood of repeated applications due to frequent depletion of local credit limits and also lowers the possibility of excessive allocation leading to idle credit. Furthermore, it helps improve the response speed to credit limit requests.

[0054] After obtaining the third credit limit, the credit limit service can read the target account's current pending credit limit and the single-business system credit limit limit corresponding to the first business system. The credit limit service determines the second credit limit based on the third credit limit, the pending credit limit, and the single-business system credit limit limit. In some examples, the second credit limit can be the smaller value among the third credit limit, the pending credit limit, and the single-business system credit limit limit.

[0055] By predicting the business processing needs within a future time window, quota applications are made as infrequent as possible; the quota to be allocated is constrained to ensure that a single allocation does not exceed the total currently available global quota; and the quota limit for a single business system is set to prevent a single business system from accumulating too much quota, thus reducing quota fragmentation from the source.

[0056] For example, if the target account has an allocated credit limit of 200, and the single-system credit limit of the first business system is 150, the credit service predicts that the target account's third credit limit in the first business system within the next hour will be 120, and the first credit limit will be 80. The credit service compares the predicted credit limit of 120, the allocated credit limit of 200, and the single-system credit limit of 150, and takes the smaller value of 120. Since 120 is greater than the first credit limit of 80, the credit service can determine that the second credit limit is 120. After the first business system obtains a credit limit of 120, it can deduct the first credit limit of 80 and retain 40 of locally available credit to support subsequent business processing.

[0057] If the smaller of the three values ​​is less than the first limit, for example, if the allocated limit is 50, the predicted limit is 120, the single business system limit is 150, and the first limit is 80, then the smaller of the three values ​​is the allocated limit of 50, which is less than the first limit of 80. In this case, the limit service can determine the second limit as 50 based solely on the allocated limit, and continue to supplement it with at least 30 from the available limit of the target account in at least one second business system to ensure that the second limit is not less than the first limit; or, the limit service can combine the available limit of the second business system with the allocated limit to calculate and finally determine the second limit as 80 or greater.

[0058] When the prediction model is unavailable or inference times out, the credit limit service can automatically degrade to rule-based fallback calculation. For example, the credit limit service can determine the second credit limit by a fixed multiple of the first credit limit, such as 1x, 2x, etc. This way, even if the prediction function malfunctions, the credit limit service can still respond to credit limit requests, avoiding blocking business processing due to prediction failure.

[0059] Using the above method, the credit limit service can predict the third credit limit for future time windows based on the target account's historical business processing characteristics, and determine the second credit limit by combining the pending credit limit and the single business system's credit limit cap. This approach changes credit limit allocation from a fixed-quantity issuance to dynamic adjustment based on the account's corresponding business processing behavior. This makes credit limit applications a relatively low-frequency operation, allowing most business processing to complete credit limit verification and deduction locally. Furthermore, the dual constraints of the pending credit limit and the single business system's holding cap reduce fragmentation caused by issuing too much credit at once, thus improving the efficiency of account credit limit utilization.

[0060] In some scenarios, the available credit limit in the first account data is less than the first credit limit. The credit limit service can obtain the available credit limit of the target account in at least one second business system. The second business system is a business system deployed in a different data center than the first business system. In some scenarios, the credit limit service can read the available credit limit of the target account corresponding to multiple second business systems other than the first business system from the first account data. Then, it sends a credit limit reclamation instruction to at least one second business system, which can return the reclaimable actual available credit limit to the credit limit service and subtract the aforementioned actual available credit limit from its local available credit limit.

[0061] The credit limit service can merge the pending credit limit with the actual available credit limit returned by at least one second business system to obtain a total adjustable credit limit, and then determine a second credit limit from the total adjustable credit limit. For example, the pending credit limit for the target account is 20, and the first credit limit is 50. The credit limit service finds that the available credit limit for the target account in second business system B is 30, and the available credit limit for the target account in second business system C is 40. The credit limit service merges the pending credit limit of 20, the available credit limit of second business system B of 30, and the available credit limit of second business system C of 40, resulting in a total adjustable credit limit of 90. The credit limit service determines a second credit limit of 60 from the total adjustable credit limit and allocates it to the first business system.

[0062] In some implementations, step S203 includes: determining at least one second business system from a plurality of candidate business systems other than the first business system, based on at least one of local available quota, business processing activity and network latency.

[0063] Candidate business systems refer to business systems other than the primary business system that may hold available credit for the target account. Multiple candidate business systems can be deployed in different data centers. Local available credit refers to the target account credit available locally to a candidate business system. Generally, the larger this credit, the more sufficient the credit can be allocated to that candidate business system. Business processing activity (or transaction activity) refers to the frequency or rate of credit consumption of target account-related business processed by the candidate business system in a recent period. The lower the business processing activity, the less likely the candidate business system is to use the target account credit in the near future, and the less impact it will have on its business after credit is reclaimed. Network latency refers to the communication latency between the credit service and the data center where the candidate business system is located. The lower the network latency, the more reliable the credit reclamation interaction, and the lower the probability of reclamation failure or timeout.

[0064] The credit limit service can identify at least one second business system from multiple candidate business systems. In some scenarios, the credit limit service can select the second business system solely based on the locally available credit limit, for example, prioritizing the candidate business system with the largest locally available credit limit for the target account. In other scenarios, it can also select solely based on business processing activity, for example, prioritizing the candidate business system with the lowest business processing activity. Furthermore, it can select solely based on network latency, for example, prioritizing the candidate business system with the lowest network latency to the credit limit service.

[0065] In some scenarios, the quota service replica can also combine multiple indicators. For example, weights can be set for local available quota, business processing activity and network latency, a comprehensive score can be calculated for each candidate business system, and at least one candidate business system can be selected as the second business system according to the comprehensive score from high to low.

[0066] For example, the target account has a pending credit limit of 20, and the first business system requests a first credit limit of 50. The credit limit service obtains candidate business systems B and C from the first account data. Candidate business system B has a target account local available credit limit of 30, high business activity, and a network latency of 10 milliseconds; candidate business system C has a target account local available credit limit of 40, low business activity, and a network latency of 20 milliseconds. The credit limit service prioritizes candidate business system C with lower business activity as the second business system, obtaining 30 from its available credit limit, which, combined with the pending credit limit of 20, totals 50, thus determining the second credit limit to be 50, sufficient to satisfy the deduction of the first credit limit. If the credit limit service requires a larger second credit limit, such as 60, it can continue to select 10 from candidate business system B, also making candidate business system B the second business system.

[0067] Once the credit limit service identifies the second business system, it can record the selected second business system and the available credit limit value to be used from each second business system for subsequent updates to the first account data. For each second business system, the recovered credit limit can be subtracted from the locally maintained local available credit limit to obtain the latest local credit limit data.

[0068] In these implementations, by selecting a second business system from multiple candidate business systems based on factors such as local available quota, business processing activity, and network latency, the quota service can prioritize business systems with relatively abundant quotas, lower business processing pressure, and better communication conditions as the source of quota allocation when adjusting quotas across centers. This can reduce the interference of quota adjustment on highly active business systems to a certain extent, lower the probability of quota recovery failure or timeout, and improve the success rate of cross-center quota adjustment. This more stably replenishes the local available quota of the first business system, ensuring the smooth completion of subsequent quota deductions.

[0069] S204: Allocate a second credit limit to the target account in the first business system and simultaneously update the first account data in multiple credit limit service copies.

[0070] After determining the second credit limit, the credit limit service can allocate it to the corresponding first business system. This can be achieved by sending a response message to the first business system, carrying the second credit limit within the message. Upon receiving the second credit limit, the first business system adds it to its local available credit limit, thus updating its local available credit limit.

[0071] Once the credit limit service determines the second credit limit, it can record the source of each portion of the second credit limit, such as how much of the pending credit limit was used, which available credit limits from which second business systems were used, and the usage amount of each. This facilitates subsequent updates to the first account data, such as reducing the pending credit limit, reducing the corresponding available credit limit records from the second business systems, and adding records of allocated but unused credit limits from the first business systems. The credit limit service can maintain data consistency across all replicas through consistency protocols or other synchronization mechanisms; therefore, when the credit limit service updates the first account data, multiple replicas can be updated synchronously.

[0072] In some scenarios, after the primary business system updates its local available credit limit, it can use the updated local available credit limit to deduct from the initial credit limit. After the initial credit limit is deducted, the primary business system can continue to process subsequent business without having to apply for a new credit limit from the credit limit service again, until the local available credit limit becomes insufficient again.

[0073] In this embodiment, a centralized quota service is provided to multiple business systems by deploying multiple replicas of the quota service, with each replica maintaining the same first account data. This quota service enables unified quota allocation across business systems deployed across data centers. When a quota request is received from a first business system carrying data center information, account information, and a first quota, a second quota not less than the first quota can be determined and allocated to the first business system by combining the target account's pending quota, or by combining the pending quota with the available but unused quota of the target account in other data center second business systems. Compared to the business system performing cross-center quota sharing, quota aggregation calculation, and quota scheduling logic for each transaction, this solution only initiates a cross-center, on-demand centralized allocation to obtain a second quota when the business system's local available quota is insufficient. After allocation, subsequent quota deductions for multiple business processes are executed directly on the first business system, eliminating the need for cross-center access to the quota service for each transaction. This reduces the risk of false rejections or increased processing time due to network latency or jitter. Furthermore, in this solution, quota scheduling and cross-center available quota aggregation calculation are all handled by the quota service. The primary business system only needs to focus on whether the business is compliant and whether the local quota is sufficient, while the complex logic of cross-center quota coordination, quota consistency maintenance, and cross-center synchronization are all handled by the quota service, significantly reducing the complexity of the business system. In addition, the quota service in the above solution allocates unused quotas on demand and adjusts them between business systems in different data centers, alleviating the problem of both quota idleness and shortage, and improving the overall utilization efficiency of account quotas. Moreover, the above solution relies on multi-replica cross-center deployment to maintain the continuous availability of the quota service when some replicas or data centers are abnormal.

[0074] In some implementations, the method further includes:

[0075] If the sum of the available quota to be allocated and the available quota of all other business systems outside the first business system is less than the first quota, the allocation of quota to the first business system according to the quota request is refused, and a first prompt message is returned to the first business system; the first prompt message indicates that the quota is insufficient.

[0076] The credit limit service can obtain the pending credit limit of the target account and sum it with the available credit limits of the target account in all other business systems. Here, "all other business systems" refers to all business systems other than the first business system. The credit limit service can compare this sum with the first credit limit in the credit limit request. If the sum is less than the first credit limit, the credit limit service determines that the total available credit limit is insufficient to meet the current credit limit request of the first business system. In this case, the credit limit service refuses to allocate a second credit limit to the first business system according to the credit limit request and returns a first prompt message to the first business system, indicating insufficient credit limit. After receiving the first prompt message, the first business system can either return the result of insufficient credit limit to the party that initiated the original request, or wait for subsequent credit limit replenishment and re-initiate the credit limit request.

[0077] When the sum of the available credit limit to be allocated and the available credit limits of all other business systems (excluding the first business system) is less than the first credit limit, the credit limit service refuses to allocate credit and returns an insufficient credit limit warning. This process, combined with the credit limit service's features such as maintaining multiple copies of the same account credit limit data, on-demand applications, and cross-business system adjustments, ensures that the credit limit service will not forcibly allocate credit when the available credit limit cannot meet the application, thereby reducing the risk of inconsistent account credit limit data and over-limit usage caused by over-allocation. At the same time, the first business system can receive timely feedback on insufficient credit limit, thereby terminating or postponing the credit limit deduction for the corresponding business, avoiding long waiting times or repeated attempts in business processing, and helping to improve the accuracy of credit limit control and overall processing efficiency.

[0078] In some implementations, the credit limit data for each account in the first account data further includes the total used credit limit and allocated but unused credit limit across multiple business systems; the method also includes:

[0079] Receive the used quota increment of the target account for the current period from each of the multiple business systems;

[0080] Based on the incremental amount of used credit, update the total allocated but unused credit and the total used credit of the target account in the first account data of multiple credit service copies.

[0081] The incremental amount of used credit in the business system refers to the amount of credit that has been newly used and deducted from the previous period to the current period.

[0082] The business systems here can include the first and second business systems mentioned above. Each business system can periodically check the credit limit usage of its target account. At the periodic check time, the business system can check the locally used credit limit and determine the credit limit increment by comparing it with the locally used credit limit checked in the previous period. The corresponding used credit limit increment for the current period can be sent to the credit limit service. For example, if a business system sent the used credit limit increment in the previous period, and the local used credit limit is accumulated to 100; then two deductions occur, 30 and 20 respectively; then the increment reported this time will be 50, instead of reporting the current accumulated used credit limit of 150.

[0083] The business system can also send the update when the locally used credit limit increment reaches a certain value. The update information sent by the business system can include account information, credit limit category information, and the used credit limit increment.

[0084] The credit limit service receives the used credit limit increments for target accounts from various business systems. Based on these increments, the credit limit service updates the total allocated but unused credit limit and the total used credit limit for the target account in the first account data. For example, if the credit limit service receives a report from a business system that the used credit limit increment for a target account under the general credit limit category is 30, then it reduces the total allocated but unused credit limit for the target account in the first account data by 30, and simultaneously increases the total used credit limit for that target account by 30. It is understood that when the credit limit service updates the first account data, multiple credit limit service replicas synchronously update the first account data to ensure consistency across all credit limit service replicas.

[0085] In these implementations, the business system sends the incremental amount of used quota, which avoids the full value of used quota being overwritten when different business systems report concurrently, compared to sending the full value of used quota. This reduces the possibility that the target account statistics in the first account data will be overwritten by old data.

[0086] In some implementations, the method further includes: receiving a limit modification operation, the limit modification operation being used to modify the total limit of the target account; the modification operation includes either increasing or decreasing;

[0087] In response to the modification operation to increase the limit, the total limit in the first account data is increased by the limit value indicated by the modification operation;

[0088] In response to a modification operation that reduces the limit, the limit value indicated by the modification operation is reduced in the first account data; if the limit to be allocated is less than the limit value, the available limits of each business system are reclaimed.

[0089] The credit limit service receives credit limit modification operations, which include increasing or decreasing the total credit limit of the target account. In some scenarios, decreasing or increasing the total credit limit of the target account can be a direct instruction to increase the total credit limit of the target account. In some scenarios, the increase or decrease can be determined by resetting the total credit limit of the target account. Resetting refers to setting the total credit limit of the target account to a preset value. This preset value may be greater than the current total credit limit of the target account maintained in the first account data; in this case, the reset can cause an increase in the total credit limit of the target account. If this preset value is less than the current total credit limit of the target account, the reset can cause a decrease in the total credit limit of the target account.

[0090] If the modification operation instructs an increase in the credit limit, the credit limit service can retrieve the amount to be increased from the modification operation and add that amount to the total credit limit of the target account in the first account data. Alternatively, it can retrieve the target total credit limit from the modification operation and use the difference between the target total credit limit and the current total credit limit as the amount to be increased. The credit limit service can then add the increased amount to the target account's pending credit limit, enabling this portion of the credit limit to be allocated to the business system later. For example, if the original total credit limit is 1000, and an increase of 200 brings the total credit limit to 1200, the pending credit limit will increase by 200 accordingly. The credit limit service updates the first account data in multiple replicas to ensure consistency across all replicas.

[0091] If the modification operation is to reduce the credit limit, the credit limit service obtains the credit limit value to be reduced from the modification operation and first deducts it from the target account's pending credit limit in the first account data. If the current pending credit limit is greater than or equal to this credit limit value, the credit limit service directly reduces this credit limit value from the pending credit limit, and simultaneously reduces the total credit limit by this credit limit value. For example, if the pending credit limit is 300 and the reduction value is 100, then the pending credit limit becomes 200, and the total credit limit decreases by 100. The credit limit service updates the first account data in multiple copies. If the current pending credit limit is less than this credit limit value, the credit limit service first deducts all pending credit limits and calculates the difference. The difference is the credit limit value minus the deducted pending credit limit. Then, the credit limit service can reclaim the target account's available credit limit from multiple business systems, with the total reclaimed amount equal to the difference. During reclamation, the credit limit service can determine the business systems to be reclaimed and the amount of credit limit to be reclaimed for each based on the available credit limit size, business processing activity, or preset priority of each business system. The credit limit service sends a recovery instruction to these business systems; the corresponding business systems deduct the corresponding amount from their local available credit limit and return the recovery result to the credit limit service; the credit limit service adjusts the available credit limit of these business systems under the target account based on the recovery result. When the pending credit limit is reduced to zero, the total credit limit is reduced by this amount.

[0092] For example, the target account has a total credit limit of 1000, an allocated credit limit of 80, an available credit limit of 100 in business system A, and an available credit limit of 50 in business system B. The modification operation instructs to reduce the credit limit by 200. The credit limit service first deducts the allocated credit limit of 80, leaving a difference of 120. Based on the available credit limit, the credit limit service recovers 100 from business system A and 20 from business system B, totaling 120. After completion, the total credit limit is reduced to 800, the allocated credit limit is 0, the available credit limit in business system A is 0, and the available credit limit in business system B is 30.

[0093] In these implementations, from the perspective of quota modification operations, the quota service centrally maintains account quota data, enabling the operation of increasing or decreasing the total quota to be completed uniformly on the quota service side. When reducing the quota, the quota service first deducts the quota to be allocated, and if insufficient, it reclaims the allocated but unused available quota from multiple business systems. This approach eliminates the need for business systems in each data center to adjust sub-account quotas separately, nor does it require re-coordinating the split ratio. Business systems also do not need to actively modify their own quota records; they only need to cooperate with the reclamation. Compared to related technologies that require modifying sub-account quotas or re-dividing quotas across multiple centers, this solution reduces the coordination complexity of quota adjustments to a certain extent, reduces the possibility of manual intervention and misoperation, and utilizes consistent first account data across multiple copies, enabling the quota adjustment results to be automatically synchronized to each quota service copy, improving the convenience of account quota management and maintenance.

[0094] In some embodiments, the first account data includes first credit data for multiple accounts under a first credit limit category and at least one second credit limit category;

[0095] Each second credit limit category corresponds to at least one designated business type; the first credit limit category corresponds to multiple business types, which include each designated business type.

[0096] The first quota data includes the total used quota (also known as the global used quota) of multiple business systems, the quota to be allocated, and the used quota and available quota of each business system.

[0097] Business type refers to a classification label used to identify the category to which a business belongs in terms of credit limit control. The classification of business types is based on fund processing procedures and credit limit control rules. Business types may include, but are not limited to, the following: regular payment business, prepayment business, carry-over business, credit usage business, and reserve fund transfer business. The credit limit service can map different business types to a first credit limit category and at least one second credit limit category according to preset mapping relationships or mapping rules.

[0098] The first credit limit category refers to a credit limit category that can be used for multiple business types and can be considered a general credit limit category. The second credit limit category refers to a credit limit category that can be used for a specific business type and can be considered a dedicated credit limit category. Each second credit limit category can correspond to at least one specific business type. For example, the credit limit category corresponds to credit payment business, and the prepayment credit limit category corresponds to collection and payment on behalf of others and prepayment settlement business. The multiple business types corresponding to the first credit limit category can include these specific business types. That is to say, the first credit limit category can be used for the business types corresponding to the second credit limit category, as well as other business types.

[0099] The first credit limit data refers to the credit limit record of a specific account under a specific credit limit category. The first credit limit data for a credit limit category can include the globally used credit limit, the credit limit to be allocated, the used credit limit for each business system, and the available credit limit for that credit limit category. The globally used credit limit refers to the total credit limit of this account under that credit limit category that has been used and deducted by all business systems. The credit limit to be allocated refers to the total credit limit of this account under that credit limit category that can currently be redistributed by the credit limit service to business systems. The used credit limit for each business system refers to the credit limit of this account under that category that has been used and deducted by that business system. The available credit limit for each business system refers to the credit limit of this account under that business system that has been acquired but not yet used.

[0100] For example, an account has first-level credit limit data under the first credit limit category, where the globally used credit limit is 800, the pending credit limit is 200, the used credit limit in business system A is 300, and the available credit limit is 50; the used credit limit in business system B is 500, and the available credit limit is 40. This account also has another set of first-level credit limit data under the second credit limit category, where the globally used credit limit is 200, the pending credit limit is 100, the used credit limit in business system A is 150, and the available credit limit is 20; the used credit limit in business system B is 50, and the available credit limit is 10. Through this data structure, the credit limit service can maintain data for different credit limit categories separately, keeping general and dedicated credit limits isolated in use. Simultaneously, by recording the used and available credit limits of each business system, it supports credit limit adjustments across business systems. After processing a credit limit request, the credit limit service will update the first credit limit data under the corresponding credit limit category. For example, it will reduce the credit limit to be allocated, reduce the available credit limit of the business system being adjusted, and increase the allocated but unused credit limit of the first business system, while keeping the first account data consistent across multiple credit limit service copies.

[0101] In these implementations, account quota records are organized in the first account data according to a first quota category and at least one second quota category. The first quota category corresponds to multiple business types, while the second quota category corresponds only to a specified business type. The first quota data simultaneously records the globally used quota, the quota to be allocated, and the used and available quotas of each business system. When the quota service receives a quota request from a first business system, it can allocate quotas and perform cross-data center adjustments based on this quota data aggregated by category. This avoids, to some extent, the excessive detail and fragmentation of quotas caused by splitting quotas according to specific business types, allowing quotas of the same category to be combined and adjusted across multiple business systems, thereby reducing quota fragmentation. Simultaneously, the quota service provides a relatively small number of quota categories, eliminating the need for business systems to make separate quota requests for different business types. This simplifies the interaction between business systems and the quota service, reduces the frequency of cross-center joint adjustments caused by overly detailed quota classifications, and can also improve situations where quota idleness and quota shortage coexist.

[0102] Furthermore, since account quota data is centrally maintained by the quota service, business systems only cache the allocated available quota locally. When a new data center or a new business system is added, there is no need to reallocate a fixed quota ratio for the account. The newly added business system only needs to submit a quota application to the quota service as the primary business system. The quota service then adjusts the quota as needed based on the global quota to be allocated and the available quota of existing business systems, thus completing the quota replenishment. This avoids the problem of needing to re-coordinate the splitting ratio with existing data centers, as required by the existing sub-account splitting scheme.

[0103] Figure 3 This is a flowchart illustrating a credit limit control method provided in other embodiments of this application. The method is applied to a credit limit service, which includes multiple copies of the credit limit service distributed across different data centers. The credit limit service centrally provides credit limit management services to multiple business systems, and the multiple copies of the credit limit service have the same first account data, such as... Figure 3 As shown, the method includes the following steps:

[0104] S301: Receive a credit limit request sent by the first business system. The credit limit request includes data center information, account information, first credit limit, and target credit limit category. The target credit limit category includes either the first credit limit category or the second credit limit category.

[0105] The credit limit request includes a target credit limit category, which may include a first credit limit category or a second credit limit category; the first credit limit category corresponds to multiple business types; and the second credit limit category corresponds to at least one specified business type among the multiple business types.

[0106] The specific implementation process of step S301 above can be referred to the description of step S201 above. Furthermore, the quota request sent by the first business system also includes the target quota category.

[0107] In some scenarios, when the first business system is processing a business and deducting credit limits, it may initiate a credit limit request if its local available credit limit is insufficient. In this case, the target credit limit category can be determined by the first business system based on the business type corresponding to the business being processed.

[0108] In some scenarios, if the credit limit category corresponding to the business type is the second credit limit category, when the first business system determines that the available credit limit of the local first credit limit category is greater than the first credit limit, it can use the available credit limit of the local first credit limit category to complete the deduction, and at the same time send the aforementioned credit limit request including the aforementioned second credit limit category to the credit limit service. In other scenarios, if the credit limit category corresponding to the business type is the second credit limit category, the first business system directly sends the aforementioned credit limit request including the aforementioned second credit limit category to the credit limit service.

[0109] In some scenarios, the first business system can periodically check whether its local available credit limit is less than a preset threshold. If it is, it initiates a credit limit request. In these scenarios, the first business system can maintain the available credit limits for a first credit limit category and a second credit limit category, each category having its own preset threshold. When it is detected that the available credit limit corresponding to any credit limit category is less than the corresponding preset threshold, a credit limit request including that credit limit category can be initiated; this credit limit category is the target credit limit category.

[0110] S302: Obtain the target account's available credit limit under the target credit limit category from the first account data.

[0111] After receiving a credit limit request, the credit limit service can determine the target account based on the account information and, according to the target credit limit category, retrieve the credit limit to be allocated for the target account under that target credit limit category from the first account data. If the target credit limit category is the first credit limit category, the credit limit service retrieves the credit limit to be allocated for the target account under the first credit limit category; if the target credit limit category is the second credit limit category, the credit limit service retrieves the credit limit to be allocated for the target account under the corresponding second credit limit category.

[0112] For example, account Z has an allocated credit limit of 80 under the first credit limit category and an allocated credit limit of 30 under the second credit limit category. Since the target credit limit category is the first credit limit category, the credit limit service obtains an allocated credit limit of 80.

[0113] Since the first account data stores the unallocated quotas for each quota category according to the quota category, the quota service can quickly obtain the unallocated quotas for the target quota category from the first account data through the target quota category, which can improve the accuracy and efficiency of quota allocation decisions.

[0114] S303: In response to the fact that the amount to be allocated under the target amount category is greater than or equal to the first amount, a second amount is determined from the amount to be allocated.

[0115] The credit limit service compares the target account's pending credit limit under the target credit limit category with the first credit limit. If the pending credit limit is greater than or equal to the first credit limit, it means that the current pending credit limit is sufficient to meet the local credit limit request of the first business system. The credit limit service can determine a second credit limit from the pending credit limit. The second credit limit can be equal to the first credit limit; the second credit limit can also be greater than the first credit limit, so that the first business system can still retain some locally available credit limit after completing this deduction. After determining the second credit limit, the credit limit service can allocate the second credit limit to the first business system, reduce the target account's pending credit limit under the target credit limit category accordingly, and update the first account data.

[0116] For example, the target account has an allocated credit limit of 80 under the first credit limit category, and the first credit limit is 50. After comparison, the credit limit service determines that the allocated credit limit is greater than the first credit limit. The credit limit service can determine a second credit limit of 70 from the allocated credit limit of 80, and allocate 70 credit limit to the first business system. After the first business system receives the 70 credit limit, its local available credit limit increases, which can complete the deduction of the first credit limit of 50, leaving a local available credit limit of 20.

[0117] S304: In response to the fact that the amount to be allocated under the target amount category is less than the first amount, obtain the available amount of the target account under the target amount category in at least one second business system.

[0118] If the available credit limit for the target account under the target credit limit category is less than the first credit limit, it means that the available credit limit alone cannot satisfy the local credit limit request of the first business system. The credit limit service can obtain at least one available credit limit for the target account under the target credit limit category from the first account data in at least one second business system. The second business system is a business system deployed in a different data center than the first business system, and the second business system may hold allocated but unused target credit limit categories for the target account. The credit limit service can obtain the available credit limits of these second business systems to supplement the insufficient available credit limit.

[0119] For example, the target account has an allocated credit limit of 20 under the first credit limit category, and the first credit limit is 50. The credit limit service obtains an available credit limit of 30 for account Z in the second business system B under the first credit limit category, and an available credit limit of 10 for account Z in the second business system C under the first credit limit category. The credit limit service can use these available credit limits as a source of adjustable credit limits.

[0120] S305: Determine the second quota based on the quota to be allocated and the available quota corresponding to at least one second business system.

[0121] The credit limit service can recover the credit limit from the second business system, and then determine the second credit limit based on the credit limit to be allocated and the recovered credit limit.

[0122] In some implementations, determining the second quota based on the quota to be allocated and the available quota corresponding to at least one second business system includes:

[0123] Recover at least a portion of the available credit limit of the target account under the target credit limit category from at least one secondary business system;

[0124] The second quota is determined based on at least a portion of the recovered available quota and the quota to be allocated.

[0125] When the credit limit service determines that a portion of the available credit limit needs to be reclaimed from the second business system, it will first determine the amount of credit limit to be reclaimed. This amount can be the difference between the first credit limit and the target account's pending credit limit under the target credit limit category, or it can be the result after adding a certain margin to the first credit limit. For example, if the first credit limit applied for in the first business system is 100, and the target account's pending credit limit under the target credit limit category is 40, then the credit limit service can determine that 60 of the available credit limit needs to be reclaimed from the second business system.

[0126] The credit limit service reclaims at least a portion of the available credit limit of a target account under a target credit limit category from at least one secondary business system. The credit limit service may initiate a reclamation request to one or more secondary business systems. The reclamation request may include account information, the target credit limit category, and the amount of credit limit to be reclaimed. Upon receiving the reclamation request, the secondary business system locally checks the available credit limit of the target account under that target credit limit category. If the local available credit limit is greater than or equal to the amount of credit limit to be reclaimed, the secondary business system may deduct that amount from its local available credit limit and return a successful reclamation and the actual amount reclaimed to the credit limit service. If the local available credit limit is less than the amount of credit limit to be reclaimed, the secondary business system may return the actual amount of credit limit that can be reclaimed, or return a message indicating that reclamation is not possible.

[0127] After receiving the results from the second business system, the credit limit service aggregates the actually recovered available credit limit with the target account's pending credit limit under the target credit limit category to obtain the total credit limit available for allocation to the first business system. The credit limit service then determines the second credit limit based on this total credit limit. The second credit limit can be equal to or greater than the first credit limit, ensuring that the first business system retains a portion of its local available credit limit after this deduction. For example, if the pending credit limit is 40, and the credit limit recovered from at least one second business system is 60, the credit limit service can determine the second credit limit to be 100. If the credit limit recovered from the second business system is 30, and the total credit limit is 70, the credit limit service can determine the second credit limit to be 50 and return this credit limit to the first business system; if the second credit limit is still less than the first credit limit, it can continue to attempt to recover the shortfall from other second business systems.

[0128] After determining the second credit limit, the credit limit service allocates it to the first business system. The first business system receives the second credit limit and updates its local available credit limit. Simultaneously, the credit limit service updates the first account data, for example, reducing the target account's pending credit limit under that target credit limit category, reducing the available credit limit record in the relevant second business system, and increasing the available credit limit record in the first business system. The updated first account data remains consistent across multiple copies of the credit limit service.

[0129] Through the above process, when the allocated credit limit is insufficient, the credit limit service reclaims unused credit limit of the target account under the target credit limit category from at least one second business system, forming a second credit limit together with the allocated credit limit. This allows the first business system to obtain sufficient credit limit to complete the deduction. This can improve the utilization efficiency of the target account's existing credit limit under the target credit limit category and reduce the situation where some business systems have idle credit limit while other business systems have insufficient credit limit.

[0130] In this embodiment, the credit limit service locates the available credit limit for the target account within the category specified in the credit limit request. It prioritizes determining a second credit limit from the available credit limit within that category. If insufficient, it supplements the limit with available credit limits from other second business systems within the same target credit limit category, thus forming a credit limit control process based on credit limit category allocation and adjustment. This approach confines credit limit allocation and cross-business system adjustments within the target credit limit category, reducing the rule complexity and usage conflicts caused by mixing different credit limit categories. Furthermore, since the credit limit service uses categorized data for judgment and adjustment, it can utilize unused credit limits of the same category in other business systems to fill gaps. This reduces situations where a certain type of credit limit is scarce in some business systems while similar credit limits are idle in others, helping to reduce fragmentation caused by overly detailed credit limit splitting and improving the overall utilization efficiency of the credit limit for that category of accounts.

[0131] Please refer to Figure 4 , Figure 4 This is a flowchart illustrating a quota control method provided in some embodiments of this application. The method is applied to a first business system, which is any one of multiple distributed business systems. Each business system is deployed in a corresponding data center. The first business system runs in the first data center. In some scenarios, quota service replicas are also deployed in each data center. Figure 4 As shown, the method includes the following steps:

[0132] S401: In response to insufficient local available credit for the target account, a credit request is sent to the corresponding credit service copy; wherein, the credit service copy is one of multiple credit service copies, the multiple credit service copies include the same first account data, the first account data includes the credit data of each of the multiple accounts, the credit data includes the total credit limit and the credit limit to be allocated, and the credit request includes the account information of the target account, the data center information where the first business system is located, and the first credit limit.

[0133] The target account mentioned above can be any one of the multiple accounts maintained by the first account data.

[0134] The first business system can maintain secondary account data for different accounts. Each account's secondary account data is locally stored within the business system and can be used for credit limit deductions. For example, it may include the available credit limit already obtained by the business system. Available credit limit can be credit limit obtained by the business system from the credit limit service but not yet used. When the first business system needs to deduct credit limit from an account locally, it can first use the available credit limit from the corresponding secondary account data.

[0135] The first business system can detect whether the available credit limit of the local target account is sufficient. If the available credit limit is insufficient, a credit limit request can be generated. The account information of the target account may include, for example, an identifier for the target account. The account identifier may include one or more of letters, numbers, and alphanumeric characters to distinguish different accounts. In some embodiments, step S401 above includes:

[0136] In response to the target account's local available credit limit being less than the deductible amount indicated in the pending transaction, a credit limit request is sent; the first credit limit is determined based on the difference between the local available credit limit and the deductible amount; or,

[0137] In response to the detection that the local available quota is less than the preset threshold in the current detection period, a quota request is sent; the first quota is determined based on the difference between the local available quota and the preset threshold.

[0138] In some scenarios, the first business system receives a pending transaction. Based on this transaction, it needs to deduct credit from the target account's credit limit. The first business system determines the amount to be deducted based on the pending transaction. Then, it compares the local available credit limit with the amount to be deducted. If the local available credit limit is less than the amount to be deducted, the first business system determines that the local available credit limit is insufficient. In this case, the first business system determines a first credit limit based on the difference between the local available credit limit and the amount to be deducted. The first credit limit can be the difference itself or a value obtained by adding a buffer to the difference. For example, if the local available credit limit is 50 and the amount to be deducted is 120, the difference is 70. The first business system can determine the first credit limit as either 70 or 100. The first business system generates a credit limit request including account information, data center information, and the first credit limit. It then sends the credit limit request to the corresponding credit limit service copy. The aforementioned data center information includes the identifier or number of the first data center on which the first business system is deployed. The account information includes the identifier or number of the target account. In some examples, the available credit limit for the target account can also be further subdivided into credit limit categories, which may include, for example, a first credit limit category and at least one second credit limit category. Descriptions of the first and second credit limit categories can be found in [reference needed]. Figure 3 The description of the relevant parts of the illustrated embodiment is as follows. Accordingly, the credit limit request may also include a target credit limit category, which may include a first credit limit category or a second credit limit category.

[0139] In other scenarios, the first business system can periodically check the available credit limit of the target account in the local second account data to see if it is less than a preset threshold for the target account corresponding to the first business system. This period can be set according to the specific application scenario; for example, it could include 30 seconds or every minute. Within the current detection period, the first business system obtains the local available credit limit and compares it with the preset threshold. The preset threshold can be a lower limit set by the first business system for the account, used to trigger credit replenishment in advance. If the detected local available credit limit is less than the preset threshold, the first business system can also determine that the local available credit limit is insufficient and actively generate a credit limit request. In this case, the first credit limit can be determined based on the difference between the local available credit limit and the preset threshold, or it can be determined based on the difference between the local available credit limit and a preset replenishment value. For example, if the preset threshold is 100 and the current local available credit limit is 60, the difference is 40, and the first business system can determine the first credit limit as 40; if the preset replenishment value is 200, then the first credit limit can be determined as 140. Similarly, the second account data can also include the first credit limit category and the preset thresholds corresponding to each second credit limit category. The first business system can periodically check whether the available credit limit corresponding to each credit limit category is less than the corresponding preset threshold.

[0140] In these implementations, the first business system triggers a credit limit request when its local available credit limit is less than the credit limit to be deducted, or when it detects that its local available credit limit is lower than a preset threshold within the detection period. This combination of two credit limit request triggering methods ensures that credit limit replenishment not only occurs when there is a shortage of credit limit during business processing, but also allows for advance application when the local credit limit is close to the lower limit. This reduces the waiting time caused by temporary credit limit requests for pending business processes and mitigates the impact of credit limit requests on the critical path of business processing.

[0141] The aforementioned corresponding credit service copy can be a credit service copy deployed in the same data center as the first business system. If the credit service copy in the same data center is unavailable, the first business system can also send the credit request to a credit service copy in another data center. The credit request includes account information, data center information, and a first credit limit. The account information indicates the target account involved in this transaction; the data center information indicates the data center where the first business system is located; the first credit limit can be the amount of credit limit to be deducted in this transaction, or it can be the amount of credit limit to be deducted in this transaction plus a certain buffer. For example, the first business system can include a first credit limit of 100 in the credit request to request the credit service to allocate at least 100 credit limit. In some cases, after receiving the credit service request, the aforementioned corresponding credit service copy can determine a second credit limit, then allocate the second credit limit to the first business system, and simultaneously send a first account data update instruction to multiple credit service copies, so that multiple credit service copies update the first account data simultaneously. S402: Receive a second quota allocated by the quota service through a corresponding quota service copy. The second quota is determined by the corresponding quota service copy based on the quota to be allocated to the target account in the first account data, or the quota to be allocated and the available quota of the target account in at least one second business system. The first business system and at least one second business system are deployed in different data centers.

[0142] After receiving a credit limit request, the credit limit service can determine a secondary credit limit. Details on determining the secondary credit limit can be found in [link to relevant documentation]. Figure 2 or Figure 3 The relevant descriptions of the illustrated embodiments are not repeated here. After determining the second credit limit, the credit limit service can allocate the second credit limit to the first business system through the corresponding credit limit service copy. For example, the second credit limit is allocated to the first business system by the aforementioned corresponding credit limit service copy. The first business system receives the second credit limit allocated by the credit limit service.

[0143] S403: Update the available credit in the local second account data based on the second credit limit.

[0144] The first business system updates the available credit in the second account data based on the second credit limit, for example, by adding the second credit limit to the available credit in the second account data.

[0145] For example, the first business system has a local available credit limit of 60, a first credit limit of 100, and a second credit limit of 150 allocated by the credit service. After the first business system adds the second credit limit of 150 to its local available credit limit, the local available credit limit becomes 210.

[0146] In some implementations, step S401 includes: sending a quota request in response to a local available quota being less than the quota to be deducted as indicated by the pending service; and the method further includes:

[0147] The amount to be deducted will be deducted from the updated local available credit limit;

[0148] Update the used and available credit in the local second account data.

[0149] In these implementations, the aforementioned quota request is generated when processing pending business transactions and detecting that the locally available quota is less than the quota to be deducted. In these implementations, after receiving the second quota allocated by the quota service, the first business system updates its locally available quota to obtain an updated locally available quota. The first business system can then deduct the quota to be deducted from the updated locally available quota.

[0150] After the first business system completes the deduction of the pending amount, it updates the used amount and available amount in the second account data. Specifically, the first business system adds the used amount to the pending amount and reduces the available amount to the pending amount. For example, before the deduction, the used amount was 200 and the available amount was 80; after deducting the pending amount of 80, the used amount becomes 280 and the available amount becomes 0.

[0151] Through the above process, when the first business system detects insufficient local available credit while processing pending transactions, it obtains supplementary credit through a credit request and deducts the amount to be deducted from the updated local available credit. The used credit and available credit maintained locally by the first business system are updated synchronously, enabling the second account data to reflect the latest credit usage of the business system, facilitating the continuous processing of subsequent credit applications and local credit deductions.

[0152] In this embodiment, the first business system only sends a quota request to the corresponding quota service replica when its local available quota is insufficient. The quota service maintains the same first account data across multiple replicas, and determines and allocates the second quota by combining the target account's unallocated quota with the unused available quota of the second business system in other data centers. The first business system then updates its local available quota accordingly. This processing method allows multiple quota deductions to be completed locally in the first business system, interacting with the quota service only when the local quota is insufficient. This reduces the number of remote calls between the business system and the quota service, mitigating the impact of network latency or jitter on business processing. Simultaneously, by allocating unused quota from other business systems to the first business system with insufficient quota, it alleviates the situation where quotas are idle in some data centers while shortages exist in others, improving the overall utilization efficiency of account quotas. Furthermore, multiple quota service replicas store the same first account data, ensuring that other replicas can continue to provide quota services even when a single replica or data center is abnormal, enhancing the continuous availability of quota management functions.

[0153] In some implementations, the method further includes: determining the used quota increment of the first business system in the current period.

[0154] Send the used credit limit increment to the corresponding credit limit service copy so that the credit limit service updates the first account data.

[0155] The first business system can periodically send used credit increments to the credit limit service. The used credit increment refers to the amount of credit newly generated and deducted from the local available credit limit between the last time the first business system sent a used credit increment and the current time. For example, if the local used credit limit was 200 when the first business system last sent a credit increment, and the current local used credit limit is 260, then the used credit increment is 60. The aforementioned period can be a preset time period, such as every 30 seconds, every minute, or every 5 minutes. In some scenarios, it can also be a sending period triggered after the increment reaches a certain threshold. At the end of the current period, the first business system can read the accumulated used credit limit value in the local second account data and compare it with the accumulated used credit limit value at the end of the previous period, using the difference as the used credit increment.

[0156] The first business system generates incremental information and sends it to the credit limit service. This incremental information may include account information and the used credit limit increment. The account information indicates the target account to which the used credit limit increment belongs. In some examples, the incremental information may also include credit limit category information, indicating whether the increment belongs to a first credit limit category or a second credit limit category. For example, if the first business system increases the used credit limit of account Z by 40 in a certain period for the first credit limit category, the reporting message will carry account Z, the first credit limit category, and the increment of 40.

[0157] The credit limit service receives the used credit limit increment sent by the first business system. The credit limit service updates the first account data based on this increment. It increases the used credit limit of the target account corresponding to the first business system by this increment; simultaneously, it decreases the total allocated but unused credit limit of the target account under the corresponding credit limit category by this increment. In some examples, it also increases the global used credit limit of the target account under the corresponding credit limit category by this increment. After this update, the balance between the account's total credit limit, pending credit limit, allocated but unused credit limit, and used credit limit is maintained. For example, if the target account's used credit limit under the general credit limit category was originally 500, and a business system reports an incremental credit limit of 40, the credit limit service updates the global used credit limit to 540, updates the used credit limit of that business system to its original value plus 40, and decreases the total allocated but unused credit limit by 40.

[0158] After the credit limit service updates the primary account data, the primary account data across multiple credit limit service replicas can remain consistent. Updates between credit limit service replicas can be achieved through consistency protocols or synchronization mechanisms, ensuring that credit limit service replicas in different data centers all receive the latest used credit limit information.

[0159] By sending the incremental amount of used credit to the credit service, the credit service does not need to obtain the total cumulative value of the used credit in the business system. Instead, it adds or subtracts from the existing records based on the increment, thereby reducing the possibility of old data overwriting new data due to concurrent reporting or out-of-order arrival. After the first business system reports the increment, the local used credit and available credit can remain unchanged, without affecting subsequent local business processing.

[0160] In some implementations, the method further includes:

[0161] Receive a credit limit recovery request sent by the credit limit service, the recovery request including the first credit limit to be recovered;

[0162] The second recovery amount is determined based on the first recovery amount and the locally available amount;

[0163] The second recovery amount is deducted from the available local credit limit and returned to the credit limit service.

[0164] In the second account data maintained locally by the first business system, the available credit is the credit that the first business system has acquired but not yet used. When the credit service needs to allocate credit across business systems, it may send a reclamation request to the first business system. For example, when a business system deployed in another data center has insufficient credit, while the first business system holds a large amount of unused available credit, the credit service can send a reclamation request to the first business system to reclaim some credit and redistribute it to other business systems.

[0165] The first business system can receive a credit limit recovery request sent by the credit limit service. The recovery request includes the first amount of credit limit to be recovered, which is the amount of credit limit the credit limit service wishes to recover from the first business system. The recovery request may also include account information and credit limit category information, indicating which account and which credit limit category's available credit limit needs to be recovered.

[0166] The second recovery limit is the actual amount recovered from the first business system. For example, the first business system can compare the first recovery limit with the local available limit and take the smaller of the two as the second recovery limit. For example, if the first recovery limit is 100 and the local available limit in the first business system is 80, then the second recovery limit is determined to be 80; if the first recovery limit is 100 and the local available limit is 150, then the second recovery limit is determined to be 100.

[0167] After determining the second recovery amount, the first business system deducts the second recovery amount from the local available credit limit and updates the available credit limit in the second account data. For example, if the local available credit limit of the first business system was originally 80 and the second recovery amount is 80, the local available credit limit becomes 0 after the deduction; if the local available credit limit was originally 150 and the second recovery amount is 100, the local available credit limit becomes 50 after the deduction.

[0168] After the first business system completes the deduction, it returns the second recovered amount to the credit limit service. The credit limit service can update the data of the first account based on the second recovered amount, for example, by reducing the available credit limit record corresponding to the first business system, supplementing the recovered amount to the pending credit limit of the target account, or distributing the recovered amount to other business systems that initiated the credit limit application.

[0169] Through the above process, the credit limit service can reclaim unused credit from one business system and use it to supplement the credit limit needs of other business systems. The first business system only deducts its local unused available credit; it does not affect its already used credit, nor does it need to modify the total account credit limit. If the first business system's local available credit is insufficient after reclamation, it can resend a credit limit request to the credit limit service during subsequent business processing without requiring additional rollback operations during this reclamation process.

[0170] Through these implementation methods, when the first business system receives a recovery request, it can determine the actual recoverable second recovery amount based on its local available credit limit, avoiding over-recovery caused by the recovery amount requested by the credit limit service exceeding the local actual available credit limit. At the same time, the first business system returns the actual recovery amount to the credit limit service, allowing the credit limit service to update the first account data based on the actual recovery result, reducing data deviations caused by concurrent use of local credit limits during the recovery process, and improving the reliability of cross-business system credit limit adjustment and the accuracy of subsequent credit limit allocation.

[0171] In some implementations, the method further includes:

[0172] In response to the first prompt sent by the quota service, the processing of pending business is stopped. The first prompt indicates that the quota is insufficient.

[0173] Upon receiving a credit limit request, the credit limit service calculates the sum of the allocated credit limit for the target account and the available credit limits for the target accounts in multiple second business systems. If this sum is less than the first credit limit, the credit limit is insufficient, and a first notification can be sent to the first business system. Upon receiving the first notification, the first business system stops processing the pending transaction. In some cases, the first business system can also send a second notification to the requester of the pending transaction, indicating that the transaction cannot be completed due to insufficient credit limit.

[0174] Some embodiments of this application also provide a credit limit control system, including multiple business systems and a credit limit service. The credit limit service is used to provide centralized services for the credit limits of the multiple business systems. The credit limit service includes multiple credit limit service copies. The multiple business systems and multiple copies are deployed in different data centers. The multiple credit limit service copies have the same first account data, which includes the total credit limit, the credit limit to be allocated, and the credit limit used by each of the multiple accounts.

[0175] In response to insufficient local available credit for the target account, the first business system sends a credit request to the corresponding credit service. The credit request includes a first credit limit, information about the data center where it is located, and account information of the target account. The first business system can be any one of multiple business systems. Upon receiving a second credit limit allocated by the credit service according to the credit request, the system updates the local second account data to process the pending business based on the updated second account data.

[0176] The credit limit service determines the second credit limit based on the target account's pending credit limit in the first account data, or the target account's available credit limit in at least one second business system; and allocates the second credit limit to the first business system; multiple credit limit service copies simultaneously update the first account data.

[0177] The operations related to the credit limit service can be referred to the description in the foregoing method embodiments, and will not be repeated here. The operations related to the first business system can be referred to the description in the foregoing method embodiments, and will not be repeated here.

[0178] Because the credit limit service has multiple copies distributed across different data centers, and each copy maintains the same primary account data, it provides centralized credit limit services to multiple business systems. The credit limit service can coordinate and schedule credit limits across business systems deployed across data centers. When it receives a credit limit request from a primary business system carrying data center information, account information, and the primary credit limit, it can determine a secondary credit limit, not less than the primary limit, by combining the target account's pending credit limit, or by combining the pending credit limit with the available but unused credit limit of the target account in other data center secondary business systems, and allocate it to the primary business system. Compared to the business system performing cross-center credit limit splitting, summarizing, and scheduling logic for each transaction, this solution only initiates a cross-center, on-demand centralized allocation to obtain a secondary credit limit when the business system's local available credit limit is insufficient. After allocation, subsequent credit limit deductions for a large number of transactions are executed directly on the primary business system, eliminating the need for cross-center access to the credit limit service for each transaction, thus reducing the impact of network latency or jitter on business processing. Furthermore, in this solution, quota scheduling and cross-center available quota aggregation calculation are all handled by the quota service. The primary business system only needs to focus on whether the business is compliant and whether the local quota is sufficient, without needing to implement complex cross-center quota coordination logic. Complex logic such as quota consistency maintenance and cross-center synchronization is all handled by the quota service, significantly reducing the complexity of the business system. In addition, the quota service in the above solution allocates unused quotas on demand and adjusts them between business systems in different data centers, alleviating the problem of both quota idleness and shortage, and improving the overall utilization efficiency of account quotas. Moreover, the above solution relies on multi-replica cross-center deployment to maintain the continuous availability of the quota service when some replicas or data centers are abnormal.

[0179] Please refer to Figure 5 , Figure 5 This is a schematic diagram of the structure of a credit limit control device provided in some embodiments of this application. The device is deployed in a credit limit service, specifically in a credit limit replica. The credit limit service replica is any one of multiple replicas of the credit limit service. The credit limit service centrally provides credit limit management services to multiple business systems, and the multiple credit limit service replicas have the same first account data; such as... Figure 5 As shown, the device includes:

[0180] The first receiving unit 501 is used to receive a quota request sent by the first business system. The quota request includes data center information, account information, and a first quota.

[0181] The first acquisition unit 502 is used to acquire the unallocated quota of the target account from the first account data, wherein the target account is the account indicated by the account information; wherein, the first account data includes quota data of multiple accounts, and the quota data includes the total quota and the unallocated quota;

[0182] The first determining unit 503 is used to determine a second quota to be allocated to the first business system based on the quota to be allocated, or the quota to be allocated and the available quota of at least one target account in the second business system; the first business system and the second business system are deployed in different data centers; the available quota is the quota that has been allocated to the second business system but has not been used; the second quota is greater than or equal to the first quota;

[0183] The allocation unit 504 is used to allocate a second quota to a target account in the first business system and update the first account data in multiple quota service copies.

[0184] In some implementations, the first account data includes first credit limit data for multiple accounts under a first credit limit category and at least one second credit limit category;

[0185] Each second credit limit category corresponds to at least one designated business type; the first credit limit category corresponds to multiple business types, which include each designated business type.

[0186] The first quota data includes the total used quota, the quota to be allocated, and the used quota and available quota of each business system.

[0187] In some implementations, the credit limit request includes a target credit limit category, which includes a first credit limit category or a second credit limit category; the first credit limit category corresponds to multiple service types; and the second credit limit category corresponds to at least one specified service type among the multiple service types.

[0188] The first acquisition unit 502 is further used to: acquire the target account's unallocated quota under the target quota category from the first account data.

[0189] In some embodiments, the first determining unit 503 is further configured to:

[0190] In response to the fact that the amount to be allocated under the target amount category is greater than or equal to the first amount, a second amount is determined from the amount to be allocated;

[0191] In response to the fact that the amount to be allocated under the target amount category is less than the first amount, obtain the available amount of the target account under the target amount category in at least one second business system;

[0192] The second quota is determined based on the quota to be allocated and the available quota corresponding to at least one second business system.

[0193] In some implementations, the first determining unit 503 is further configured to: recover at least a portion of the available credit limit of the target account under the target credit limit category from at least one second business system;

[0194] The second quota is determined based on at least a portion of the recovered available quota and the quota to be allocated.

[0195] In some implementations, the first determining unit 503 is further configured to: predict the third quota consumed by the target account in the first business system in a future time window based on the business processing characteristics of the target account in the historical time window;

[0196] The second quota is determined based on the third quota, the quota to be allocated, and the quota limit corresponding to a single business system.

[0197] In some embodiments, the first determining unit 503 is further configured to:

[0198] Based on at least one of the following factors: local available quota, business processing activity, and network latency, at least one second business system is determined from a plurality of candidate business systems other than the first business system.

[0199] In some embodiments, the device 50 further includes an incremental processing unit (not shown), which is used for:

[0200] Receive the used quota increment of the target account for the current period from each of the multiple business systems;

[0201] Based on the incremental amount of used credit, update the total allocated but unused credit and the total used credit of the target account in the first account data of multiple credit service copies.

[0202] In some embodiments, the device 50 further includes a prompting unit (not shown in the figure), which is used for:

[0203] If the sum of the available quota to be allocated and the available quota of all business systems other than the first business system is less than the first quota, the allocation of quota to the first business system according to the quota request is refused, and a first prompt message is returned to the first business system; the first prompt message indicates that the quota is insufficient.

[0204] In some embodiments, the apparatus further includes a modification unit (not shown in the figures), the modification unit being used for:

[0205] Receive credit limit modification requests. Credit limit modification requests are used to change the total credit limit of the target account. Modification requests can include either increasing or decreasing the credit limit.

[0206] In response to the modification operation to increase the limit, the total limit in the first account data is increased by the limit value indicated by the modification operation;

[0207] In response to a modification operation that reduces the limit, the limit value indicated by the modification operation is reduced in the first account data. If the limit to be allocated is less than the limit value, the available limits of each business system are reclaimed.

[0208] In some implementations, the first determining unit 503 is further configured to: input the account information and business processing characteristics of the target account into the corresponding prediction model, and output the third limit by the prediction model.

[0209] The quota control device provided in this embodiment can execute the method provided in the above method embodiment. Its implementation principle and technical effect are similar, and will not be described in detail here.

[0210] Please refer to Figure 6 , Figure 6 This is a schematic diagram illustrating the structure of a quota control device provided in some embodiments of this application. The device is installed in a first business system, which is one of multiple business systems. Figure 6 As shown, the device includes:

[0211] The first sending unit 601 is used to send a quota request to the corresponding quota service copy in response to insufficient local available quota of the target account; wherein, the quota service copy is one of multiple quota service copies, the multiple quota service copies include the same first account data, the first account data includes the quota data of each of the multiple accounts, the quota data includes the total quota and the quota to be allocated, and the quota request includes the account information of the target account, the data center information where the first business system is located, and the first quota;

[0212] The second receiving unit 602 is used to receive a second quota allocated by the quota service through a corresponding quota service copy. The second quota is determined by the corresponding quota service copy based on the quota to be allocated to the target account in the first account data, or the quota to be allocated and the available quota of the target account in at least one second business system. The first business system and at least one second business system are deployed in different data centers.

[0213] Update unit 603 is used to update the available credit in the local second account data according to the second credit limit.

[0214] In some implementations, the first sending unit 601 is further configured to: send a quota request in response to the target account's local available quota being less than the quota to be deducted in the pending service instruction; the first quota is determined based on the difference between the local available quota and the quota to be deducted; or,

[0215] In response to the detection that the local available quota is less than the preset threshold in the current detection period, a quota request is sent; the first quota is determined based on the difference between the local available quota and the preset threshold.

[0216] In some embodiments, the device 60 further includes a second transmitting unit (not shown), the second transmitting unit being used for:

[0217] Determine the used quota increment of the first business system in the current cycle.

[0218] Send the used credit limit increment to the corresponding credit limit service copy so that the credit limit service updates the first account data.

[0219] In some embodiments, the first transmitting unit 601 is further configured to:

[0220] In response to a situation where the locally available credit limit is less than the credit limit to be deducted as indicated by the pending service request, a credit limit request is sent; and the method also includes:

[0221] The amount to be deducted will be deducted from the updated local available credit limit;

[0222] Update the local second account data, which includes the used and available credit limits of the first business system.

[0223] In some embodiments, the device 60 further includes a recycling processing unit (not shown), which is used for:

[0224] Receive a credit limit recovery request sent by the credit limit service, the recovery request including the first credit limit to be recovered;

[0225] The second recovery amount is determined based on the first recovery amount and the locally available amount;

[0226] The second recovery amount is deducted from the available local credit limit and returned to the credit limit service.

[0227] In some embodiments, device 60 further includes a stop unit (not shown), the stop unit being used for:

[0228] In response to the first prompt sent by the quota service, the processing of pending business is stopped. The first prompt indicates that the quota is insufficient.

[0229] The quota control device provided in this embodiment can execute the method provided in the above method embodiment. Its implementation principle and technical effect are similar, and will not be described in detail here.

[0230] Figure 7 A schematic diagram of the credit limit control device provided in this application. Figure 7 As shown, the data processing device 70 provided in this embodiment includes at least one processor 701 and a memory 702. Optionally, the device 70 further includes a communication component 703. The processor 701, memory 702, and communication component 703 are connected via a bus 70.

[0231] In a specific implementation, at least one processor 701 executes computer execution instructions stored in memory 702, causing at least one processor 701 to perform the above-described method.

[0232] The specific implementation process of processor 701 can be found in the above method embodiments, and its implementation principle and technical effect are similar. It will not be repeated here.

[0233] In the above embodiments, it should be understood that the processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in this invention can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules within the processor.

[0234] The memory may include random access memory (RAM) and may also include non-volatile memory (NVM), such as at least one disk storage device.

[0235] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, the buses shown in the accompanying drawings are not limited to a single bus or a single type of bus.

[0236] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the above-described method.

[0237] This application also provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, implement the above-described method.

[0238] The aforementioned readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. The readable storage medium can be any available medium accessible to a general-purpose or special-purpose computer.

[0239] An exemplary readable storage medium is coupled to a processor, enabling the processor to read information from and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can reside in an Application Specific Integrated Circuit (ASIC). Alternatively, the processor and the readable storage medium can exist as discrete components in the device.

[0240] The division of units is merely a logical functional division; in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be indirect coupling or communication connection through some interfaces, devices, or units, and may be electrical, mechanical, or other forms.

[0241] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0242] In addition, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0243] If a function is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this invention, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0244] Those skilled in the art will understand that all or part of the steps of the above-described method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When executed, the program performs the steps of the above-described method embodiments; and the aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disks, or optical disks.

[0245] Finally, it should be noted that other embodiments of the invention will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This invention is intended to cover any variations, uses, or adaptations of the invention that follow the general principles of the invention and include common knowledge or customary techniques in the art not disclosed herein, and is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of the invention is limited only by the appended claims.

Claims

1. A method for controlling credit limits, characterized in that, The method is applied to a credit limit service, which includes multiple copies of the credit limit service distributed across different data centers. The credit limit service centrally provides credit limit management services to multiple business systems, and the multiple copies of the credit limit service have the same first account data. Receive a credit limit request sent by the first business system, the credit limit request including data center information, account information and a first credit limit; The unallocated quota of the target account is obtained from the first account data, wherein the target account is the account indicated by the account information; wherein, the first account data includes quota data of each of multiple accounts, and the quota data includes total quota and unallocated quota; Based on the quota to be allocated, or the quota to be allocated and the available quota of the target account in at least one second business system, a second quota to be allocated to the first business system is determined; the first business system and the second business system are deployed in different data centers; the available quota is the quota that has been allocated to the second business system but has not been used; the second quota is greater than or equal to the first quota; The second credit limit is allocated to the target account in the first business system, and the first account data in multiple credit limit service copies is updated synchronously.

2. The method according to claim 1, characterized in that, The first account data includes first credit data for multiple accounts under a first credit limit category and at least one second credit limit category; Each second credit limit category corresponds to at least one designated business type; the first credit limit category corresponds to multiple business types, and the multiple business types include each of the designated business types; The first quota data includes the total used quota and the quota to be allocated for multiple business systems, as well as the used quota and available quota for each business system.

3. The method according to claim 1, characterized in that, The credit limit request includes a target credit limit category, which includes a first credit limit category or a second credit limit category; the first credit limit category corresponds to multiple business types; the second credit limit category corresponds to at least one specified business type among the multiple business types. The step of obtaining the target account's allocated quota from the first account data includes: Obtain the target account's unallocated quota under the target quota category from the first account data.

4. The method according to claim 3, characterized in that, Based on the allocated quota and the available quota of the target account in at least one second business system, determine the second quota to be allocated to the first business system, including: In response to the fact that the amount to be allocated under the target amount category is greater than or equal to the first amount, the second amount is determined from the amount to be allocated; In response to the fact that the amount to be allocated under the target amount category is less than the first amount, the available amount of the target account under the target amount category in the at least one second business system is obtained; The second quota is determined based on the quota to be allocated and the available quota corresponding to the at least one second business system.

5. The method according to claim 4, characterized in that, The step of determining the second quota based on the quota to be allocated and the available quota corresponding to the at least one second business system includes: Recover at least a portion of the available credit limit of the target account under the target credit limit category from the at least one second business system; The second quota is determined based on the recovered at least part of the available quota and the quota to be allocated.

6. The method according to claim 1, characterized in that, The step of determining the second quota to be allocated to the first business system based on the quota to be allocated includes: Based on the business processing characteristics of the target account within a historical time window, predict the third quota consumed by the target account in the first business system within a future time window; The second quota is determined based on the third quota, the quota to be allocated, and the quota limit corresponding to a single business system.

7. The method according to claim 1, characterized in that, The step of determining the second quota to be allocated to the first business system based on the quota to be allocated and the available quota of the target account in at least one second business system includes: Based on at least one of local available quota, business processing activity, and network latency, the at least one second business system is determined from a plurality of candidate business systems other than the first business system.

8. The method according to claim 1, characterized in that, The credit limit data for each account in the first account data also includes the total used credit limit and allocated but unused credit limit across multiple business systems; the method further includes: Receive the used quota increment of the target account for the current period sent by each of the multiple business systems; Based on the incremental amount of used credit, update the total allocated unused credit and the total used credit of the target account in the first account data of multiple credit service copies.

9. The method according to claim 1, characterized in that, Also includes: If the sum of the available quota to be allocated and the available quota of all business systems other than the first business system is less than the first quota, the allocation of quota to the first business system according to the quota request is refused, and a first prompt message is returned to the first business system; the first prompt message indicates that the quota is insufficient.

10. The method according to claim 2, characterized in that, Also includes: The system receives a limit modification operation, which is used to modify the total limit of the target account; the modification operation includes either increasing or decreasing the limit. In response to the modification operation being to increase the limit, the total limit in the first account data is increased by the limit value indicated by the modification operation; In response to the modification operation being to reduce the quota, the quota to be allocated in the first account data is reduced by the quota value indicated by the modification operation. If the quota to be allocated is less than the quota value, the available quotas of each of the multiple business systems are reclaimed.

11. The method according to claim 6, characterized in that, The step of predicting the third credit limit of the target account in the first business system within a future time window based on the business processing characteristics of the target account within a historical time window includes: The account information of the target account and the business processing characteristics are input into the corresponding prediction model, and the prediction model outputs the third limit.

12. A method for controlling credit limits, characterized in that, Applied to the first business system, including: In response to insufficient local available credit for the target account, a credit request is sent to the corresponding credit service copy; wherein, the credit service copy is one of multiple credit service copies, the multiple credit service copies include the same first account data, the first account data includes the credit data of each of the multiple accounts, the credit data includes the total credit limit and the credit limit to be allocated, and the credit request includes the account information of the target account, the data center information where the first business system is located, and the first credit limit; The system receives a second credit limit allocated by the credit limit service through the corresponding credit limit service copy. The second credit limit is determined by the corresponding credit limit service copy based on the unallocated credit limit of the target account in the first account data, or the unallocated credit limit and the available credit limit of the target account in at least one second business system. The first business system and the at least one second business system are deployed in different data centers. Update the available credit in the local second account data according to the second credit limit.

13. The method according to claim 12, characterized in that, The step of responding to insufficient local available credit by sending a credit request to the corresponding credit service copy includes: In response to the target account's local available credit limit being less than the deductible amount indicated by the pending transaction, the credit limit request is sent; the first credit limit is determined based on the difference between the local available credit limit and the deductible amount; or, In response to the detection that the local available quota is less than a preset threshold in the current detection cycle, the quota request is sent; the first quota is determined based on the difference between the local available quota and the preset threshold.

14. The method according to claim 12, characterized in that, The method further includes: Determine the used quota increment of the first business system in the current period. The used credit limit increment is sent to the corresponding credit limit service copy so that the credit limit service updates the first account data.

15. The method according to claim 12, characterized in that, The step of responding to insufficient local available credit by sending a credit request to the corresponding credit service copy includes: In response to a local available credit limit being less than the credit limit to be deducted as indicated by a pending service, the credit limit request is sent; and the method further includes: The amount to be deducted is deducted from the updated local available credit limit; Update the local second account data, which includes the used and available credit limits of the first business system.

16. The method according to claim 12, characterized in that, The method further includes: Receive a recovery request sent by the quota service, the recovery request including a first recovery quota; The second recovery amount is determined based on the first recovery amount and the locally available amount; The second recovery amount is deducted from the local available credit limit and returned to the credit limit service.

17. The method according to claim 15, characterized in that, The method further includes: In response to a first prompt sent by the quota service, the processing of the pending service is stopped, whereby the first prompt indicates insufficient quota.

18. A credit limit control system, characterized in that, It includes multiple business systems and a credit limit service. The credit limit service is used to provide centralized services for the credit limits of the multiple business systems. The credit limit service includes multiple credit limit service copies. The multiple credit limit service copies have the same first account data. The first account data includes the total credit limit, the credit limit to be allocated, and the credit limit used by each of the multiple accounts. In response to insufficient local available credit for the target account, the first business system sends a credit request to the corresponding credit service; the credit request includes a first credit limit, information about the data center where it is located, and account information of the target account; the first business system can be any one of the plurality of business systems; And upon receiving the second quota allocated by the quota service according to the quota request, update the local second account data to process the pending business based on the updated second account data; The credit limit service determines a second credit limit based on the unallocated credit limit of the target account in the first account data, or the available credit limit of the target account in at least one second business system; and allocates the second credit limit to the first business system; the multiple credit limit service copies simultaneously update the first account data.

19. A quota control device, characterized in that, The device is configured to be used for a credit limit service, which includes multiple copies of the credit limit service distributed across different data centers. The credit limit service centrally provides credit limit management services to multiple business systems, and the multiple copies of the credit limit service have the same first account data. The device includes: The first receiving unit is used to receive a quota request sent by the first business system. The quota request includes data center information, account information, and a first quota. The first acquisition unit is configured to acquire the unallocated quota of a target account from the first account data, wherein the target account is the account indicated by the account information; wherein the first account data includes quota data of multiple accounts, and the quota data includes a total quota and an unallocated quota; The first determining unit is configured to determine a second quota to be allocated to the first business system based on the quota to be allocated, or the quota to be allocated and the available quota of the target account in at least one second business system; the first business system and the second business system are deployed in different data centers; the available quota is the quota that has been allocated to the second business system but has not been used; the second quota is greater than or equal to the first quota; The allocation unit is used to allocate the second quota to the target account in the first business system and to synchronously update the first account data in multiple quota service copies.

20. A quota control device, characterized in that, Located in the first business system, including: The first sending unit is configured to send a quota request to a corresponding quota service copy in response to insufficient local available quota of the target account; wherein the quota service copy is one of multiple quota service copies, the multiple quota service copies include the same first account data, the first account data includes quota data of each of the multiple accounts, the quota data includes total quota and quota to be allocated, and the quota request includes account information of the target account, data center information of the first business system, and first quota; The second receiving unit is configured to receive a second quota allocated by the corresponding quota service copy. The second quota is determined by the corresponding quota service copy based on the quota to be allocated to the target account in the first account data, or the quota to be allocated and the available quota of the target account in at least one second business system. The first business system and the at least one second business system are deployed in different data centers. An update unit is used to update the available credit in the local second account data according to the second credit limit.

21. An electronic device, characterized in that, include: Memory, processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory, causing the processor to perform the method as described in any one of claims 1-17.

22. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the method as described in any one of claims 1-17.

23. A computer program product, characterized in that, Includes a computer program that, when executed by a processor, implements the method described in any one of claims 1-17.