Batch transaction request processing method and device, equipment, medium and product

Abstract

The invention relates to the technical field of data processing, and provides a batch transaction request processing method and device, equipment, a medium and a product. The method comprises the following steps: acquiring a batch transaction request; the batch transaction request comprises target transaction attribute information of a target transaction account; under the condition that a target control element exists in control elements corresponding to at least one piece of transaction attribute information included in the parameter table according to the target transaction attribute information, determining whether an enabling mark in the target control element indicates that the target transaction account is an enabled hotspot transaction account or not; the target control element corresponds to the target transaction attribute information; and under the condition that the starting mark in the target control element is determined to indicate that the target transaction account is the started hotspot transaction account, processing the batch transaction request according to the control concurrency quantity in the target control element. The processing efficiency of the batch transaction requests is improved by using the mode of controlling the concurrency quantity matched with the actual condition of the transaction account.

Description

Technical Field

[0001] This application relates to the field of data processing technology, and in particular to a method, apparatus, device, medium and product for processing batch transaction requests. Background Technology

[0002] Trading accounts under the same real-time cash pool group are prone to hotspots, which can lead to longer overall service response times and even database lock timeouts due to long waiting times.

[0003] In related technologies, to reduce the probability of trading accounts experiencing hotspot issues, a control over the number of concurrent transactions can be set for each trading account. When the actual number of concurrent transactions for a trading account exceeds the control limit, subsequent transactions will need to wait in a queue.

[0004] However, in related technologies, the method of setting the same control over the number of concurrent transactions for all trading accounts can lead to some trading accounts becoming hot trading accounts due to high-frequency trading. This results in the problem of low processing efficiency for batch trading requests in the related technologies. Summary of the Invention

[0005] This application provides a method, apparatus, device, medium, and product for processing batch transaction requests, which can control the number of concurrent transactions to match the actual situation of the transaction account, thereby improving the processing efficiency of batch transaction requests.

[0006] In a first aspect, embodiments of this application provide a method for processing batch transaction requests, including:

[0007] Obtain batch transaction requests; wherein, the batch transaction requests include the target transaction attribute information of the target transaction account;

[0008] Based on the target transaction attribute information, determine whether a target control element exists in the control elements corresponding to at least one transaction attribute information included in the parameter table; wherein, the target control element corresponds to the target transaction attribute information;

[0009] If at least one control element included in the parameter table is found to contain a target control element, determine whether the enable flag in the target control element indicates that the target trading account is an enabled hot trading account.

[0010] Once the enable flag in the target control element is determined, indicating that the target trading account is an enabled hot trading account, the batch trading requests are processed according to the control concurrency limit in the target control element.

[0011] In one implementation, based on the target transaction attribute information, it is determined whether a target control element exists among the control elements corresponding to at least one transaction attribute information included in the parameter table, including:

[0012] Retrieve the target transaction account and target parameter type from the target transaction attribute information; where the target parameter type is a hot parameter type;

[0013] Based on the target transaction account and hotspot parameter type, determine whether a target control element exists in the control element corresponding to at least one transaction attribute information included in the parameter table; wherein the target control element corresponds to the target transaction account and hotspot parameter type.

[0014] In one implementation, based on the target transaction account and hotspot parameter type, it is determined whether a target control element exists in the control element corresponding to at least one transaction attribute information included in the parameter table, including:

[0015] Obtain the target business scenario type from the target transaction attribute information;

[0016] Based on the target transaction account, hotspot parameter type, and target business scenario type, determine whether a target control element exists in the control element corresponding to at least one transaction attribute information included in the parameter table; wherein the target control element corresponds to the target transaction account, hotspot parameter type, and target business scenario type.

[0017] In one implementation, the method also includes:

[0018] For any given trading account, retrieve the account's historical transaction data; this historical transaction data includes the number of concurrent transactions for the trading account and the type of business scenario associated with the trading account.

[0019] Determine whether a trading account is a high-frequency trading account based on the number of concurrent transactions associated with that account.

[0020] Once a trading account is identified as a high-frequency trading account, the control limit for concurrent transactions for that trading account is determined based on the number of concurrent transactions associated with that account.

[0021] Determine that the parameter type corresponding to the transaction account is a hot parameter type;

[0022] Based on the transaction account, the parameter type corresponding to the transaction account, and the business scenario type corresponding to the transaction account, assemble the transaction attribute information corresponding to the transaction account;

[0023] The activation flag corresponding to the trading account is determined to indicate that the trading account is a hot trading account, and the control elements corresponding to the trading account are assembled according to the activation flag and the control concurrency of the trading account.

[0024] The parameter table is updated based on the transaction attribute information and control elements corresponding to the transaction account.

[0025] In one implementation, the control concurrency level for a transaction account is determined based on the transaction concurrency level corresponding to that account, including:

[0026] Obtain the priority information corresponding to the trading account;

[0027] Based on the priority information of the transaction account and the number of concurrent transactions for the transaction account, determine the control concurrency level for the transaction account.

[0028] In one implementation, when an enable flag in the target control element is determined, indicating that the target trading account is an enabled hot trading account, the batch trading requests are processed according to the control concurrency level in the target control element, including:

[0029] Once the activation flag of the target control element is determined, indicating that the target transaction account is an activated hot transaction account, the contract information table is queried based on the target transaction attribute information of the target transaction account to determine the main account associated with the target transaction account.

[0030] Determine if the main account is a corporate account used for frequent transactions;

[0031] Once it is determined that the main account is a public account with high transaction volume, batch transaction requests are processed according to the control of concurrency in the target control elements.

[0032] In one implementation, based on the target transaction attribute information of the target transaction account, the contract information table is queried to determine the main account associated with the target transaction account, including:

[0033] Obtain the currency identifier and currency / exchange identifier from the target transaction attribute information;

[0034] Among the multiple sub-contractual information tables included in the contractual information table, the sub-contractual information table corresponding to the currency identifier and the cash / exchange identifier is identified as the target sub-contractual information table.

[0035] Based on the target transaction account, query the target sub-contract information table to determine the main account associated with the target transaction account.

[0036] In one implementation, the method also includes:

[0037] Based on the target transaction attribute information, query the parameter table to determine the locking order corresponding to the target transaction attribute information;

[0038] Accordingly, batch transaction requests are processed according to the control concurrency level in the target control element, including:

[0039] Batch transaction requests are processed based on the locking order corresponding to the target transaction attribute information and the control concurrency quantity in the target control element.

[0040] Secondly, embodiments of this application provide a processing apparatus for batch transaction requests, comprising:

[0041] The send / receive module is used to acquire batch transaction requests; these batch transaction requests include target transaction attribute information of the target transaction account.

[0042] The processing module is used to determine, based on the target transaction attribute information, whether a target control element exists among the control elements corresponding to at least one transaction attribute information included in the parameter table; wherein, the target control element corresponds to the target transaction attribute information;

[0043] The processing module is also used to determine, when it is determined that at least one of the control elements included in the parameter table contains a target control element, whether the enable flag in the target control element indicates that the target trading account is an enabled hot trading account.

[0044] The processing module is also used to process batch transaction requests based on the control concurrency limit in the target control element when the enable flag in the target control element indicates that the target transaction account is an enabled hot transaction account.

[0045] In one implementation, the processing module is specifically used for:

[0046] Retrieve the target transaction account and target parameter type from the target transaction attribute information; where the target parameter type is a hot parameter type;

[0047] Based on the target transaction account and hotspot parameter type, determine whether a target control element exists in the control element corresponding to at least one transaction attribute information included in the parameter table; wherein the target control element corresponds to the target transaction account and hotspot parameter type.

[0048] In one implementation, the processing module is specifically used for:

[0049] Obtain the target business scenario type from the target transaction attribute information;

[0050] Based on the target transaction account, hotspot parameter type, and target business scenario type, determine whether a target control element exists in the control element corresponding to at least one transaction attribute information included in the parameter table; wherein the target control element corresponds to the target transaction account, hotspot parameter type, and target business scenario type.

[0051] In one implementation, the processing module is also used for:

[0052] For any given trading account, retrieve the account's historical transaction data; this historical transaction data includes the number of concurrent transactions for the trading account and the type of business scenario associated with the trading account.

[0053] Determine whether a trading account is a high-frequency trading account based on the number of concurrent transactions associated with that account.

[0054] Once a trading account is identified as a high-frequency trading account, the control limit for concurrent transactions for that trading account is determined based on the number of concurrent transactions associated with that account.

[0055] Determine that the parameter type corresponding to the transaction account is a hot parameter type;

[0056] Based on the transaction account, the parameter type corresponding to the transaction account, and the business scenario type corresponding to the transaction account, assemble the transaction attribute information corresponding to the transaction account;

[0057] The activation flag corresponding to the trading account is determined to indicate that the trading account is a hot trading account, and the control elements corresponding to the trading account are assembled according to the activation flag and the control concurrency of the trading account.

[0058] The parameter table is updated based on the transaction attribute information and control elements corresponding to the transaction account.

[0059] In one implementation, the processing module is specifically used for:

[0060] Obtain the priority information corresponding to the trading account;

[0061] Based on the priority information of the transaction account and the number of concurrent transactions for the transaction account, determine the control concurrency level for the transaction account.

[0062] In one implementation, the processing module is specifically used for:

[0063] Once the activation flag of the target control element is determined, indicating that the target transaction account is an activated hot transaction account, the contract information table is queried based on the target transaction attribute information of the target transaction account to determine the main account associated with the target transaction account.

[0064] Determine if the main account is a corporate account used for frequent transactions;

[0065] Once it is determined that the main account is a public account with high transaction volume, batch transaction requests are processed according to the control of concurrency in the target control elements.

[0066] In one implementation, the processing module is specifically used for:

[0067] Obtain the currency identifier and currency / exchange identifier from the target transaction attribute information;

[0068] Among the multiple sub-contractual information tables included in the contractual information table, the sub-contractual information table corresponding to the currency identifier and the cash / exchange identifier is identified as the target sub-contractual information table.

[0069] Based on the target transaction account, query the target sub-contract information table to determine the main account associated with the target transaction account.

[0070] In one implementation, the processing module is also used for:

[0071] Based on the target transaction attribute information, query the parameter table to determine the locking order corresponding to the target transaction attribute information;

[0072] The processing module is specifically used for:

[0073] Batch transaction requests are processed based on the locking order corresponding to the target transaction attribute information and the control concurrency quantity in the target control element.

[0074] Thirdly, embodiments of this application provide a computing device, including:

[0075] The processor, and the memory that is in communication with the processor;

[0076] Memory is used to store instructions that the computer executes;

[0077] The processor is used to execute computer execution instructions stored in memory to implement the method of the first aspect.

[0078] Fourthly, 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 method of the first aspect.

[0079] Fifthly, embodiments of this application provide a computer program product, including a computer program, which, when executed by a processor, is used to implement the method of the first aspect.

[0080] This application provides a method, apparatus, device, medium, and product for processing batch transaction requests. In this method, a computing device can acquire batch transaction requests, where each batch transaction request includes target transaction attribute information of a target transaction account. The computing device can determine, based on the target transaction attribute information, whether a target control element exists among the control elements corresponding to at least one transaction attribute information included in a parameter table; wherein the target control element corresponds to the target transaction attribute information. If the computing device determines that a target control element exists among the at least one control element included in the parameter table, it can determine whether an enable flag in the target control element indicates that the target transaction account is an enabled hot transaction account. If the computing device determines that the enable flag in the target control element indicates that the target transaction account is an enabled hot transaction account, it can process the batch transaction requests based on the control concurrency quantity in the target control element. Through this method, even when the target transaction account is an enabled hot transaction account, batch transaction requests can be processed based on a control concurrency quantity matched to the actual situation of the target transaction account, reducing the lock waiting time of the target transaction account and thus improving the processing efficiency of batch transaction requests. Attached Figure Description

[0081] To more clearly illustrate the technical solutions in the embodiments or related technologies of this application, the accompanying drawings used in the description of the embodiments or related technologies will be briefly introduced below. Obviously, the accompanying drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0082] Figure 1 This is a schematic diagram illustrating an application scenario applicable to an embodiment of this application;

[0083] Figure 2a A flowchart illustrating a method for processing batch transaction requests provided in this application;

[0084] Figure 2b A schematic diagram illustrating the processing of batch transaction requests provided in an embodiment of this application;

[0085] Figure 3 A flowchart illustrating a second embodiment of a batch transaction request processing method provided in this application.

[0086] Figure 4 A flowchart illustrating a third embodiment of a batch transaction request processing method provided in this application;

[0087] Figure 5 A schematic diagram of the structure of a batch transaction request processing device provided in an embodiment of this application;

[0088] Figure 6 A structural diagram of a computing device provided in this application. Detailed Implementation

[0089] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments made by those skilled in the art under the guidance of these embodiments are within the scope of protection of this application.

[0090] The terms “first,” “second,” “third,” “fourth,” etc. (if present) in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a particular order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms “comprising” and “having,” and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0091] The collection, storage, use, processing, transmission, provision, and disclosure of financial data or user data involved in the technical solution of this application all comply with the provisions of relevant laws and regulations and do not violate public order and good morals.

[0092] It should be noted that in the embodiments of this application, certain software, components, models and other existing solutions in the industry may be mentioned. These should be regarded as exemplary and are only intended to illustrate the feasibility of implementing the technical solution of this application. However, it does not mean that the applicant has used or necessarily used the solution.

[0093] Trading accounts under the same real-time cash pool group are prone to hotspots, which can lead to longer overall service response times and even database lock timeouts due to long waiting times.

[0094] In related technologies, to reduce the probability of trading accounts experiencing hotspot issues, a control over the number of concurrent transactions can be set for each trading account. When the actual number of concurrent transactions for a trading account exceeds the control limit, subsequent transactions will need to wait in a queue.

[0095] However, in related technologies, the method of setting the same control over the number of concurrent transactions for all trading accounts can lead to some trading accounts becoming hotspots due to high-frequency trading. This results in the method having low processing efficiency for batch trading requests.

[0096] Based on the aforementioned technical problems, this application provides a method for processing batch transaction requests. In this method, a computing device can acquire batch transaction requests, where each request includes target transaction attribute information of a target transaction account. The computing device can determine whether a target control element exists among the control elements corresponding to at least one transaction attribute information included in a parameter table, based on the target transaction attribute information; wherein the target control element corresponds to the target transaction attribute information. If the computing device determines that a target control element exists among the at least one control element included in the parameter table, it can determine whether an enable flag in the target control element indicates that the target transaction account is an enabled hot transaction account. If the computing device determines that the enable flag in the target control element indicates that the target transaction account is an enabled hot transaction account, it can process the batch transaction requests based on the control concurrency level in the target control element. Through this method, even when the target transaction account is an enabled hot transaction account, batch transaction requests can be processed based on a control concurrency level matched to the actual situation of the target transaction account, reducing the lock waiting time of the target transaction account and thus improving the processing efficiency of batch transaction requests.

[0097] To facilitate understanding, the following will be combined with... Figure 1 The examples illustrate the application scenarios applicable to the embodiments of this application.

[0098] For example, Figure 1 This is a schematic diagram illustrating an application scenario to which this application's embodiments apply. For example... Figure 1 As shown, the application scenario includes: computing device 10 and terminal device 20.

[0099] The computing device 10 is communicatively connected to the terminal device 20.

[0100] In this application scenario:

[0101] The computing device 10 can acquire batch transaction requests; wherein, the batch transaction request includes target transaction attribute information of the target transaction account. In one implementation, the computing device 10 can acquire batch transaction requests sent by the terminal device 20.

[0102] The computing device 10 can determine whether a target control element exists in the control element corresponding to at least one transaction attribute information included in the parameter table, based on the target transaction attribute information; wherein the target control element corresponds to the target transaction attribute information.

[0103] The computing device 10 can determine whether the enable flag in the target control element indicates that the target trading account is an enabled hot trading account if it is determined that at least one control element included in the parameter table contains a target control element.

[0104] The computing device 10 can process batch transaction requests based on the control concurrency level in the target control element, provided that the target transaction account is an enabled hot transaction account. In one implementation, the computing device 10 can also send a result file to the terminal device 20.

[0105] The embodiments in this application do not... Figure 1 The document does not limit the actual form of the equipment included, nor does it specify the type of equipment. Figure 1 The interaction methods between devices are limited, and can be set according to actual needs when applying the solution.

[0106] The technical solution of this application will now be described in detail through specific embodiments. It should be noted that the following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments.

[0107] Figure 2a This is a flowchart illustrating an embodiment of a batch transaction request processing method provided in this application. See also... Figure 2a The method specifically includes the following steps:

[0108] S201: Get batch transaction request.

[0109] In this embodiment, the computing device can acquire batch transaction requests. These batch transaction requests may include target transaction attribute information for the target transaction account.

[0110] In one implementation, Figure 2b This is a schematic diagram illustrating the processing of batch transaction requests, provided as an embodiment of this application. Figure 2b As shown, the computing device can obtain batch transaction requests (also known as batch application requests) sent by the terminal device. In one implementation, the batch transaction request may include a file uploaded by the terminal device. The file may include target transaction attribute information of the target transaction account.

[0111] The target transaction attribute information includes the target transaction account. In one implementation, the target transaction attribute information may also include the target parameter type (hotspot parameter type). In another implementation, the target transaction attribute information may also include the target transaction scenario type.

[0112] S202: Based on the target transaction attribute information, determine whether there is a target control element among the control elements corresponding to at least one transaction attribute information included in the parameter table.

[0113] In this embodiment, the computing device can obtain a parameter table (also referred to as a database table).

[0114] The parameter table includes at least one control element corresponding to a transaction attribute. This transaction attribute information may include the transaction account. In one implementation, the transaction attribute information may also include parameter types (such as hotspot parameter types). In another implementation, the transaction attribute information may also include the transaction scenario type.

[0115] In one implementation, the transaction attribute information may also include the contract type.

[0116] It should be noted that control elements may include the enabled status, the number of concurrent connections, and the transaction account.

[0117] The following section explains the process of updating the parameter table for computing devices.

[0118] In one implementation:

[0119] For any one of multiple trading accounts, the computing device can obtain the historical transaction data of that trading account. This historical transaction data includes the number of concurrent transactions corresponding to the trading account and the business scenario type associated with that account. In one implementation, the trading account can be a target trading account. In another implementation, the computing device can periodically obtain the historical transaction data of that trading account. Understandably, the historical transaction data can correspond to a historical time period. The historical time period can be the time between the first historical moment and the current moment. The duration between the first historical moment and the current moment can be a preset duration. Through these methods, the parameter table can be updated periodically.

[0120] The computing device can determine whether a trading account is a hot trading account based on the number of concurrent transactions corresponding to that account.

[0121] The computing device can determine the control concurrency level for a trading account based on the number of concurrent transactions associated with that account, once it is determined that the trading account is a hot trading account.

[0122] The computing device can determine that the parameter type corresponding to the transaction account is a hot parameter type.

[0123] The computing device can assemble the transaction attribute information corresponding to the transaction account based on the transaction account, the parameter type corresponding to the transaction account, and the business scenario type corresponding to the transaction account.

[0124] The computing device can determine that the activation flag corresponding to the transaction account indicates that the transaction account is a hot transaction account, and assemble the control elements corresponding to the transaction account based on the activation flag and the control concurrency of the transaction account.

[0125] The computing device can add new data to the parameter table based on the transaction attribute information and control elements corresponding to the transaction account.

[0126] The following section explains the process by which the computing device determines the control concurrency level corresponding to a transaction account based on the transaction concurrency level corresponding to that transaction account.

[0127] In one implementation:

[0128] The computing device can obtain the priority information corresponding to the transaction account.

[0129] The computing device can determine the control concurrency level for a transaction account based on its priority information and the number of concurrent transactions. Understandably, in one implementation, the control concurrency level can be less than the number of concurrent transactions. In another implementation, the computing device can query the correspondence between priority information and the reduction amount to determine the reduction amount. The computing device can then determine the control concurrency level for the transaction account by subtracting the reduction amount from the number of concurrent transactions. In yet another implementation, the computing device can query the correspondence between priority information and a reduction factor to determine the reduction factor. The computing device can then determine the control concurrency level for the transaction account by multiplying the number of concurrent transactions by the reduction factor.

[0130] In this embodiment, the computing device can determine whether a target control element exists in the control element corresponding to at least one transaction attribute information included in the parameter table, based on the target transaction attribute information.

[0131] In one implementation, the computing device can run a hotspot account query component to determine whether a target control element exists in the control element corresponding to at least one transaction attribute information included in the parameter table, based on the target transaction attribute information.

[0132] In one implementation, the computing device can generate a transaction generation task upon receiving a batch transaction request. Based on this task, the computing device can run a batch payment preparation program and invoke an account query transaction function. The computing device can then run the account query transaction function and invoke a hotspot account query component. Finally, the computing device can run the hotspot account query component and, based on the target transaction attribute information, determine whether a target control element exists among the control elements corresponding to at least one transaction attribute information included in the parameter table.

[0133] Among them, the target control elements correspond to the attribute information of the target transaction account.

[0134] The computing device can execute S203 if it determines that there is a target control element among the control elements corresponding to at least one transaction attribute information included in the parameter table.

[0135] or,

[0136] The computing device may execute S205 if it determines that there is no target control element among the control elements corresponding to at least one transaction attribute information included in the parameter table.

[0137] The following describes the process by which the computing device determines whether a target control element exists among the control elements corresponding to at least one transaction attribute information included in the parameter table, based on the target transaction attribute information.

[0138] In one implementation:

[0139] The computing device can obtain the target transaction account and target parameter type from the target transaction attribute information. Among them, the target parameter type is a hot parameter type.

[0140] The computing device can determine whether a target control element exists in the control elements corresponding to at least one transaction attribute information included in the parameter table, based on the target transaction account and hotspot parameter type. The target control element corresponds to the target transaction account and hotspot parameter type.

[0141] S203: Determine whether the enable flag in the target control element indicates that the target trading account is an enabled hot trading account.

[0142] In this embodiment, if the computing device determines that a target control element corresponding to the target transaction attribute information exists in the parameter table, it can determine whether the enable flag in the target control element indicates that the target transaction account is an enabled hot-spot transaction account. In one implementation, the computing device can run a hot-spot account query component, and if the computing device determines that a target control element corresponding to the target transaction attribute information exists in the parameter table, it can determine whether the enable flag in the target control element indicates that the target transaction account is an enabled hot-spot transaction account.

[0143] The computing device can execute S204 if it determines the enable flag in the target control element, indicating that the target trading account is an enabled hot trading account.

[0144] or,

[0145] The computing device can execute S205 if it determines the enable flag in the target control element, indicating that the target trading account is not an enabled hot trading account.

[0146] The following section explains the process by which the computing device determines whether the enable flag in the target control element indicates that the target trading account is an enabled hot trading account.

[0147] In one implementation, the computing device can determine whether the enable flag in the target control element is enabled.

[0148] The computing device can determine the enable flag in the target control element if it finds that the enable flag is enabled, and indicate that the target trading account is an enabled hot trading account. Alternatively,

[0149] The computing device can determine the enable flag in the target control element if it finds that the enable flag in the target control element is not enabled, and indicate that the target trading account is a hot trading account that is not enabled.

[0150] S204: Process batch transaction requests according to the control concurrency level in the target control element.

[0151] In this embodiment, the computing device can process batch transaction requests based on the control concurrency level in the target control element, provided that the target transaction account is an enabled hot transaction account.

[0152] For example, the concurrency limit can be set to 7.

[0153] In one implementation:

[0154] The computing device can assemble transaction input messages based on the target control elements, provided that the target transaction account is an enabled, frequently used transaction account. The computing device can determine whether the transaction input messages include the target control elements. If the computing device determines that the transaction input messages include the target control elements, it can process batch transaction requests based on the control concurrency level specified in the target control elements.

[0155] In one implementation:

[0156] like Figure 2b As shown, the computing devices include distributed clusters, high-frequency clusters, and parameter clusters.

[0157] The distributed cluster can run batch payment preparation programs, call account query transactions, and send query requests to the parameter cluster.

[0158] The distributed cluster can run batch collection and payment preparation programs, call account queries to retrieve transactions, and obtain parameter tables sent by the parameter cluster.

[0159] A distributed cluster can run batch payment preparation programs, call account query transactions, query parameter tables, and obtain target control elements. In one implementation, the distributed cluster can run account query transactions, call hot account query components, query parameter tables, and obtain target control elements.

[0160] Distributed clusters can run batch collection and payment preparation programs, assembling transaction input messages (accounting transaction input messages) according to target control elements.

[0161] High-frequency clusters can run polling batch processing processes to obtain transaction input messages sent by the distributed cluster.

[0162] High-frequency clusters can run polling batch processing processes, generating high-frequency tasks once the transaction input message includes target control elements (enable flag, target transaction account, and control concurrency). The high-frequency task includes the control concurrency from the target control elements.

[0163] High-frequency clusters can run polling batch processing processes, controlling the distributed cluster to execute account transactions based on high-frequency tasks, in order to process batch transaction requests.

[0164] The high-frequency cluster can run a polling batch processing process to obtain the response messages corresponding to account transactions, and obtain the task data corresponding to the high-frequency task based on the response messages.

[0165] High-frequency clusters can run polling batch processing processes, sending write-back requests to the distributed cluster based on the task data corresponding to the high-frequency tasks.

[0166] The distributed cluster can update high-frequency files based on write-back requests, and parse the updated high-frequency files to obtain the result files.

[0167] Distributed clusters can send result files to terminal devices.

[0168] S205: Process batch transaction requests according to the preset control of the concurrency level.

[0169] In this embodiment, the computing device can obtain a preset control concurrency level. For example, the preset control concurrency level can be 5.

[0170] The computing device can process batch transaction requests according to a preset control of the concurrent number.

[0171] In one implementation, the computing device can process batch transaction requests according to a preset control concurrency number if it determines that there is no target control element corresponding to the target transaction attribute information among the control elements corresponding to at least one transaction attribute information included in the parameter table.

[0172] In one implementation, the computing device can process batch transaction requests according to a preset control concurrency level, provided that the enable flag in the target control element indicates that the target transaction account is not an enabled hot transaction account.

[0173] The beneficial effects of this embodiment are as follows: In this embodiment, the computing device can acquire batch transaction requests; wherein, the batch transaction request includes target transaction attribute information of the target transaction account. The computing device can determine whether a target control element exists among the control elements corresponding to at least one transaction attribute information included in the parameter table, based on the target transaction attribute information; wherein, the target control element corresponds to the target transaction attribute information. If the computing device determines that a target control element exists among at least one control element included in the parameter table, it can determine whether the enable flag in the target control element indicates that the target transaction account is an enabled hot-spot transaction account. If the computing device determines that the enable flag in the target control element indicates that the target transaction account is an enabled hot-spot transaction account, it can process the batch transaction requests according to the control concurrency quantity in the target control element. Through the above method, even when the target transaction account is an enabled hot-spot transaction account, the batch transaction requests can be processed based on the control concurrency quantity matched to the actual situation of the target transaction account, reducing the lock waiting time of the target transaction account and thus improving the processing efficiency of batch transaction requests.

[0174] Figure 3 This is a flowchart illustrating a second embodiment of a method for processing batch transaction requests provided in this application. See also... Figure 3 The method specifically includes the following steps:

[0175] S301: Get batch transaction requests.

[0176] In this embodiment, the computing device can acquire batch transaction requests. In one implementation, the batch transaction request can be sent by a terminal device.

[0177] The batch transaction request includes the target transaction attribute information corresponding to the target transaction account.

[0178] S302: Obtain the target transaction account and target parameter type from the target transaction attribute information.

[0179] In this embodiment, the computing device can obtain the target transaction account and target parameter type from the target transaction attribute information.

[0180] The target parameter type is a hotspot parameter type.

[0181] S303: Based on the target transaction account and hotspot parameter type, determine whether the target control element exists in the control element corresponding to at least one transaction attribute information included in the parameter table.

[0182] In this embodiment, the computing device can determine whether a target control element exists in the control element corresponding to at least one transaction attribute information included in the parameter table, based on the target transaction account and hotspot parameter type.

[0183] Among them, the target control elements correspond to the target trading account and hotspot parameter types.

[0184] The computing device may execute S304 if a target control element exists among the control elements corresponding to at least one transaction attribute information included in the parameter table.

[0185] or,

[0186] The computing device may execute S306 if it determines that there is no target control element among the control elements corresponding to at least one transaction attribute information included in the parameter table.

[0187] In one implementation:

[0188] The computing device can obtain the target business scenario type from the target transaction attribute information.

[0189] The computing device can determine whether a target control element exists in the control element corresponding to at least one transaction attribute information included in the parameter table, based on the target transaction account, hotspot parameter type, and target business scenario type.

[0190] Among them, the target control elements correspond to the target transaction account, hot parameter type, and target business scenario type.

[0191] The computing device may execute S304 if a target control element exists among the control elements corresponding to at least one transaction attribute information included in the parameter table.

[0192] or,

[0193] The computing device may execute S306 if it determines that there is no target control element among the control elements corresponding to at least one transaction attribute information included in the parameter table.

[0194] S304: Determine whether the enable flag in the target control element indicates that the target trading account is an enabled hot trading account.

[0195] In this embodiment, if the computing device determines that there is a target control element among the control elements corresponding to at least one transaction attribute information included in the parameter table, it can determine whether the enable flag in the target control element indicates that the target transaction account is an enabled hot transaction account.

[0196] The computing device can execute S305 if it determines the enable flag in the target control element, indicating that the target trading account is an enabled hot trading account.

[0197] or,

[0198] The computing device can execute S306 without indicating that the target trading account is an enabled hot trading account when it determines the enable flag in the target control element.

[0199] S305: Process batch transaction requests according to the control concurrency level in the target control element.

[0200] In this embodiment, the computing device can process batch transaction requests based on the control concurrency level specified in the target control element, provided that the target transaction account is an enabled, frequently used transaction account. In other words, the computing device can process batch transaction requests based on the Redis distributed lock mechanism and the control concurrency level specified in the target control element, provided that the target transaction account is an enabled, frequently used transaction account.

[0201] Additionally, it should be noted that in one implementation:

[0202] The computing device can query the parameter table based on the target transaction attribute information to determine the locking order corresponding to the target transaction attribute information.

[0203] The computing device can process batch transaction requests based on the locking order corresponding to the target transaction attribute information and the control concurrency level in the target control element. In other words, the computing device processes batch transaction requests based on the control concurrency level. Furthermore, during the processing of these batch transaction requests, the computing device can perform locking based on the locking order corresponding to the target transaction attribute information to reduce lock conflicts and thus lower the probability of deadlock.

[0204] S306: Process batch transaction requests according to the preset control of the concurrent number.

[0205] In this embodiment, the computing device can obtain a preset control concurrency level. For example, the preset control concurrency level can be 5.

[0206] The computing device can process batch transaction requests according to a preset control of the concurrent number.

[0207] In one implementation, the computing device can process batch transaction requests according to a preset control concurrency number if it determines that there is no target control element corresponding to the target transaction attribute information among the control elements corresponding to at least one transaction attribute information included in the parameter table.

[0208] In one implementation, the computing device can process batch transaction requests according to a preset control concurrency level, provided that the enable flag in the target control element indicates that the target transaction account is not an enabled hot transaction account.

[0209] The beneficial effects of this embodiment are as follows: In this embodiment, the computing device can obtain the target transaction account and target parameter type from the target transaction attribute information; wherein, the target parameter type is a hotspot parameter type. The computing device can determine whether a target control element exists among the control elements corresponding to at least one transaction attribute information included in the parameter table, based on the target transaction account and hotspot parameter type; wherein, the target control element corresponds to the target transaction account and hotspot parameter type. If the computing device determines that a target control element exists among at least one control element included in the parameter table, it can determine whether the enable flag in the target control element indicates that the target transaction account is an enabled hotspot transaction account. If the computing device determines that the enable flag in the target control element indicates that the target transaction account is an enabled hotspot transaction account, it can process batch transaction requests based on the control concurrency quantity in the target control element. By determining whether a target control element exists in the parameter table based on the target transaction account and hotspot parameter type, the accuracy of determining the target control element can be improved, thereby improving the accuracy of determining the control concurrency quantity, and thus improving the processing efficiency of batch transaction requests.

[0210] Figure 4 This is a flowchart illustrating a third embodiment of a method for processing batch transaction requests provided in this application. See also... Figure 4 The method specifically includes the following steps:

[0211] S401: Get batch transaction request.

[0212] In this embodiment, the computing device can acquire batch transaction requests. These batch transaction requests include target transaction attribute information for the target transaction account.

[0213] The specific implementation process is the same as that of S201, and will not be described in detail here.

[0214] S402: Based on the target transaction attribute information, determine whether there is a target control element among the control elements corresponding to at least one transaction attribute information included in the parameter table.

[0215] In this embodiment, the computing device can determine whether a target control element exists in the control element corresponding to at least one transaction attribute information included in the parameter table, based on the target transaction attribute information.

[0216] Among them, the target control elements correspond to the target transaction attribute information.

[0217] The computing device can execute S403 if it determines that there is a target control element among the control elements corresponding to at least one transaction attribute information included in the parameter table.

[0218] or,

[0219] The computing device can execute S407 if it determines that there is no target control element among the control elements corresponding to at least one transaction attribute information included in the parameter table.

[0220] S403: Determine whether the enable flag in the target control element indicates that the target trading account is an enabled hot trading account.

[0221] In this embodiment, if the computing device determines that a target control element exists among at least one control element included in the parameter table, it can determine whether the enable flag in the target control element indicates that the target transaction account is an enabled hot transaction account.

[0222] The computing device can execute S404 if it determines that the enable flag in the target control element indicates that the target trading account is an enabled hot trading account.

[0223] or,

[0224] The computing device can execute S407 without indicating that the target trading account is an enabled hot trading account when it determines the enable flag in the target control element.

[0225] S404: Based on the transaction attribute information of the target transaction account, query the contract information table to determine the main account associated with the target transaction account.

[0226] In this embodiment, the computing device can store a contract information table. The contract information table includes the main account corresponding to the transaction attribute information of each transaction account. The main account is associated with the transaction account.

[0227] The computing device, upon determining the activation flag in the target control element, indicating that the target transaction account is an active, frequently used transaction account, can query the contract information table based on the transaction attribute information of the target transaction account to determine the primary account associated with the target transaction account. It should be noted that, when the target transaction account is the primary account, the primary account associated with the target transaction account is the target transaction account itself.

[0228] In one implementation:

[0229] The computing device can obtain the currency identifier and cash / exchange identifier from the target transaction attribute information.

[0230] The computing device can query the contract information table based on the target transaction account, currency identifier, and banknote / exchange identifier to determine the primary account associated with the target transaction account. In one implementation, the computing device can run a corporate deposit contract information query component to query the contract information table based on the target transaction account, currency identifier, and banknote / exchange identifier to determine the primary account associated with the target transaction account.

[0231] In one implementation:

[0232] The contract information can include multiple sub-contract information tables. For any given sub-contract information table, it corresponds to a currency identifier and a currency exchange identifier.

[0233] The computing device can obtain the currency identifier (also known as the currency code) and the cash / exchange identifier (also known as the cash / exchange code) from the target transaction attribute information.

[0234] The computing device can identify the target sub-signing information table from among the multiple sub-signing information tables included in the signing information table, the sub-signing information table that corresponds to the currency identifier and cash / exchange identifier in the target transaction attribute information.

[0235] The computing device can query the target sub-contract information table based on the target transaction account to determine the main account associated with the target transaction account. This target sub-contract information table includes the correspondence (or association) between the target transaction account and the main account.

[0236] S405: Determine if the main account is a corporate hot trading account.

[0237] In this embodiment, the computing device can determine whether the main account is a corporate hot transaction account.

[0238] The computing device can execute S406 if it determines that the main account is a corporate hot trading account.

[0239] or,

[0240] The computing device can execute S407 if it determines that the primary account is not a public hot trading account.

[0241] S406: If the main account is determined to be a public account with high transaction volume, process the batch transaction requests according to the control of the number of concurrent transactions in the target control elements.

[0242] In this embodiment, the computing device can process batch transaction requests based on the control concurrency level in the target control element, provided that the primary account is determined to be a corporate hot transaction account. In one implementation, the computing device can run a hot account query component to process batch transaction requests based on the control concurrency level in the target control element, provided that the primary account is determined to be a corporate hot transaction account.

[0243] S407: Process batch transaction requests according to the preset control of the concurrency level.

[0244] In this embodiment, the computing device can obtain a preset control concurrency level. For example, the preset control concurrency level can be 5.

[0245] The computing device can process batch transaction requests according to a preset control of the concurrent number.

[0246] In one implementation, the computing device can process batch transaction requests according to a preset control concurrency number if it determines that there is no target control element corresponding to the target transaction attribute information among the control elements corresponding to at least one transaction attribute information included in the parameter table.

[0247] In one implementation, the computing device can process batch transaction requests according to a preset control concurrency level, provided that the enable flag in the target control element indicates that the target transaction account is not an enabled hot transaction account.

[0248] In one implementation, the computing device can process batch transaction requests based on a preset control of the concurrency level, provided that the main account is not a public account with high transaction activity.

[0249] The beneficial effects of this embodiment are as follows: In this embodiment, the computing device can acquire batch transaction requests; wherein, the batch transaction request includes target transaction attribute information of the target transaction account. The computing device can determine whether a target control element exists among the control elements corresponding to at least one transaction attribute information included in the parameter table, based on the target transaction attribute information; wherein, the target control element corresponds to the target transaction attribute information. If the computing device determines that a target control element exists among at least one control element included in the parameter table, it can determine whether the activation flag in the target control element indicates that the target transaction account is an enabled hot transaction account. If the computing device determines that the activation flag of the target control element indicates that the target transaction account is an enabled hot transaction account, it can query the contract information table based on the transaction attribute information of the target transaction account to determine the main account associated with the target transaction account. If the computing device determines that the main account is a corporate hot transaction account, it can process the batch transaction requests according to the control concurrency quantity in the target control element. By using the above method, when the main account associated with the target transaction account is a public hot account and the target transaction account is an enabled hot account, the computing device can process batch transaction requests based on the control of the number of concurrent requests matched with the actual situation of the target transaction account, thereby reducing the lock waiting time of the target transaction account and improving the processing efficiency of batch transaction requests.

[0250] Figure 5 This is a schematic diagram of a batch transaction request processing device provided in an embodiment of this application. Figure 5 As shown, the batch transaction request processing device 50 includes a transceiver module 51 and a processing module 52. Among them,

[0251] The transceiver module 51 is used to obtain batch transaction requests; wherein, the batch transaction request includes the target transaction attribute information of the target transaction account;

[0252] Processing module 52 is used to determine whether a target control element exists in the control elements corresponding to at least one transaction attribute information included in the parameter table, based on the target transaction attribute information; wherein the target control element corresponds to the target transaction attribute information.

[0253] The processing module 52 is further configured to, when it is determined that at least one control element included in the parameter table contains a target control element, determine whether the enable flag in the target control element indicates that the target trading account is an enabled hot trading account.

[0254] The processing module 52 is also used to process batch transaction requests according to the control concurrency quantity in the target control element when the enable flag in the target control element indicates that the target transaction account is an enabled hot transaction account.

[0255] The batch transaction request processing device provided in this application embodiment can execute the technical solution shown in the above method embodiment. Its implementation principle and beneficial effects are similar, and will not be repeated here.

[0256] In one implementation, the processing module 52 is specifically used for:

[0257] Retrieve the target transaction account and target parameter type from the target transaction attribute information; where the target parameter type is a hot parameter type;

[0258] Based on the target transaction account and hotspot parameter type, determine whether a target control element exists in the control element corresponding to at least one transaction attribute information included in the parameter table; wherein the target control element corresponds to the target transaction account and hotspot parameter type.

[0259] The batch transaction request processing device provided in this application embodiment can execute the technical solution shown in the above method embodiment. Its implementation principle and beneficial effects are similar, and will not be repeated here.

[0260] In one implementation, the processing module 52 is specifically used for:

[0261] Obtain the target business scenario type from the target transaction attribute information;

[0262] Based on the target transaction account, hotspot parameter type, and target business scenario type, determine whether a target control element exists in the control element corresponding to at least one transaction attribute information included in the parameter table; wherein the target control element corresponds to the target transaction account, hotspot parameter type, and target business scenario type.

[0263] The batch transaction request processing device provided in this application embodiment can execute the technical solution shown in the above method embodiment. Its implementation principle and beneficial effects are similar, and will not be repeated here.

[0264] In one implementation, the processing module 52 is further configured to:

[0265] For any given trading account, retrieve the account's historical transaction data; this historical transaction data includes the number of concurrent transactions for the trading account and the type of business scenario associated with the trading account.

[0266] Determine whether a trading account is a high-frequency trading account based on the number of concurrent transactions associated with that account.

[0267] Once a trading account is identified as a high-frequency trading account, the control limit for concurrent transactions for that trading account is determined based on the number of concurrent transactions associated with that account.

[0268] Determine that the parameter type corresponding to the transaction account is a hot parameter type;

[0269] Based on the transaction account, the parameter type corresponding to the transaction account, and the business scenario type corresponding to the transaction account, assemble the transaction attribute information corresponding to the transaction account;

[0270] The activation flag corresponding to the trading account is determined to indicate that the trading account is a hot trading account, and the control elements corresponding to the trading account are assembled according to the activation flag and the control concurrency of the trading account.

[0271] The parameter table is updated based on the transaction attribute information and control elements corresponding to the transaction account.

[0272] The batch transaction request processing device provided in this application embodiment can execute the technical solution shown in the above method embodiment. Its implementation principle and beneficial effects are similar, and will not be repeated here.

[0273] In one implementation, the processing module 52 is specifically used for:

[0274] Obtain the priority information corresponding to the trading account;

[0275] Based on the priority information of the transaction account and the number of concurrent transactions for the transaction account, determine the control concurrency level for the transaction account.

[0276] The batch transaction request processing device provided in this application embodiment can execute the technical solution shown in the above method embodiment. Its implementation principle and beneficial effects are similar, and will not be repeated here.

[0277] In one implementation, the processing module 52 is specifically used for:

[0278] Once the activation flag of the target control element is determined, indicating that the target transaction account is an activated hot transaction account, the contract information table is queried based on the target transaction attribute information of the target transaction account to determine the main account associated with the target transaction account.

[0279] Determine if the main account is a corporate account used for frequent transactions;

[0280] Once it is determined that the main account is a public account with high transaction volume, batch transaction requests are processed according to the control of concurrency in the target control elements.

[0281] The batch transaction request processing device provided in this application embodiment can execute the technical solution shown in the above method embodiment. Its implementation principle and beneficial effects are similar, and will not be repeated here.

[0282] In one implementation, the processing module 52 is specifically used for:

[0283] Obtain the currency identifier and currency / exchange identifier from the target transaction attribute information;

[0284] Among the multiple sub-contractual information tables included in the contractual information table, the sub-contractual information table corresponding to the currency identifier and the cash / exchange identifier is identified as the target sub-contractual information table.

[0285] Based on the target transaction account, query the target sub-contract information table to determine the main account associated with the target transaction account.

[0286] The batch transaction request processing device provided in this application embodiment can execute the technical solution shown in the above method embodiment. Its implementation principle and beneficial effects are similar, and will not be repeated here.

[0287] In one implementation, the processing module 52 is further configured to:

[0288] Based on the target transaction attribute information, query the parameter table to determine the locking order corresponding to the target transaction attribute information;

[0289] Processing module 52 is specifically used for:

[0290] Batch transaction requests are processed based on the locking order corresponding to the target transaction attribute information and the control concurrency quantity in the target control element.

[0291] The batch transaction request processing device provided in this application embodiment can execute the technical solution shown in the above method embodiment. Its implementation principle and beneficial effects are similar, and will not be repeated here.

[0292] Figure 6 A structural diagram of a computing device provided in this application. Figure 6 As shown, the computing device 60 includes a processor 61 and a memory 62. The processor 61 is communicatively connected to the memory 62, which stores computer execution instructions. The processor 61 is configured to execute the technical solutions in any of the foregoing method embodiments via the computer execution instructions stored in the memory 62.

[0293] Optionally, the memory 62 can be either standalone or integrated with the processor 61. Optionally, when the memory 62 is a device independent of the processor 61, the computing device 60 may further include a bus 63 for connecting the aforementioned devices.

[0294] The computing device is used to execute the technical solutions in any of the foregoing method embodiments. Its implementation principle and technical effect are similar, and will not be described again here.

[0295] This application also provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the technical solutions provided in any of the foregoing method embodiments.

[0296] This application also provides a computer program product, including a computer program, which, when executed by a processor, is used to implement the technical solutions provided in the foregoing method embodiments.

[0297] 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.

[0298] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features therein. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.

Claims

1. A method for processing batch transaction requests, characterized in that, include: Obtain batch transaction requests; wherein, the batch transaction requests include target transaction attribute information of the target transaction account; Based on the target transaction attribute information, determine whether a target control element exists among the control elements corresponding to at least one transaction attribute information included in the parameter table; wherein the target control element corresponds to the target transaction attribute information; If the target control element is found to exist in at least one control element included in the parameter table, determine whether the enable flag in the target control element indicates that the target trading account is an enabled hot trading account. If the activation flag in the target control element is determined to indicate that the target transaction account is an activated hot transaction account, the batch transaction request is processed according to the control concurrency level in the target control element.

2. The method according to claim 1, characterized in that, The step of determining whether a target control element exists in the control elements corresponding to at least one transaction attribute information included in the parameter table, based on the target transaction attribute information, includes: Obtain the target transaction account and target parameter type from the target transaction attribute information; wherein, the target parameter type is a hotspot parameter type; Based on the target transaction account and the hotspot parameter type, determine whether the target control element exists among the control elements corresponding to at least one transaction attribute information included in the parameter table; wherein the target control element corresponds to the target transaction account and the hotspot parameter type.

3. The method according to claim 2, characterized in that, The step of determining whether the target control element exists in the control elements corresponding to at least one transaction attribute information included in the parameter table, based on the target transaction account and the hotspot parameter type, includes: Obtain the target business scenario type from the target transaction attribute information; Based on the target transaction account, the hotspot parameter type, and the target business scenario type, determine whether the target control element exists among the control elements corresponding to at least one transaction attribute information included in the parameter table; wherein, the target control element corresponds to the target transaction account, the hotspot parameter type, and the target business scenario type.

4. The method according to claim 3, characterized in that, The method further includes: For any given transaction account, obtain the historical transaction data of that transaction account; wherein, the historical transaction data includes the number of concurrent transactions corresponding to the transaction account and the business scenario type corresponding to the transaction account; Based on the number of concurrent transactions corresponding to the transaction account, determine whether the transaction account is a hot transaction account; If the trading account is determined to be a hot trading account, the control concurrency level corresponding to the trading account is determined based on the number of concurrent transactions corresponding to the trading account. The parameter type corresponding to the transaction account is determined to be a hotspot parameter type; Assemble the transaction attribute information corresponding to the transaction account based on the transaction account, the parameter type corresponding to the transaction account, and the business scenario type corresponding to the transaction account; The activation flag corresponding to the transaction account is determined to indicate that the transaction account is a hot transaction account, and the control elements corresponding to the transaction account are assembled according to the activation flag corresponding to the transaction account and the control concurrency number corresponding to the transaction account. The parameter table is updated based on the transaction attribute information and control elements corresponding to the transaction account.

5. The method according to claim 4, characterized in that, The step of determining the control concurrency level corresponding to the transaction account based on the transaction concurrency level corresponding to the transaction account includes: Obtain the priority information corresponding to the transaction account; Based on the priority information corresponding to the transaction account and the transaction concurrency number corresponding to the transaction account, the control concurrency number corresponding to the transaction account is determined.

6. The method according to claim 1, characterized in that, When the activation flag in the target control element is determined to indicate that the target transaction account is an activated hot transaction account, the batch transaction request is processed according to the control concurrency level in the target control element, including: Once the activation flag of the target control element is determined, indicating that the target transaction account is an activated hot transaction account, the contract information table is queried based on the target transaction attribute information of the target transaction account to determine the main account associated with the target transaction account; Determine whether the main account is a corporate hot trading account; Once it is determined that the main account is the corporate hotspot transaction account, the batch transaction request is processed according to the control concurrency quantity in the target control element.

7. The method according to claim 6, characterized in that, The step of querying the contract information table based on the target transaction attribute information of the target transaction account to determine the main account associated with the target transaction account includes: Obtain the currency identifier and cash / exchange identifier from the target transaction attribute information; The sub-signing information table corresponding to the currency identifier and the cash / exchange identifier among the multiple sub-signing information tables included in the signing information table is determined as the target sub-signing information table; Based on the target transaction account, query the target sub-contract information table to determine the main account associated with the target transaction account.

8. The method according to claim 1, characterized in that, The method further includes: Based on the target transaction attribute information, query the parameter table to determine the locking order corresponding to the target transaction attribute information; Accordingly, processing the batch transaction requests based on the control concurrency level in the target control element includes: The batch transaction request is processed according to the locking order corresponding to the target transaction attribute information and the control concurrency quantity in the target control element.

9. A processing apparatus for batch transaction requests, characterized in that, include: The transceiver module is used to acquire batch transaction requests; wherein, the batch transaction request includes target transaction attribute information of the target transaction account; The processing module is used to determine, based on the target transaction attribute information, whether a target control element exists among the control elements corresponding to at least one transaction attribute information included in the parameter table; wherein the target control element corresponds to the target transaction attribute information; The processing module is further configured to, when it is determined that at least one of the control elements included in the parameter table contains the target control element, determine whether the enable flag in the target control element indicates that the target trading account is an enabled hot trading account; The processing module is further configured to process the batch transaction request according to the control concurrency quantity in the target control element when it is determined that the enable flag in the target control element indicates that the target transaction account is an enabled hot transaction account.

10. A computing device, characterized in that, include: A processor, and a memory communicatively connected to the processor; The memory is used to store computer-executed instructions; The processor is configured to execute computer execution instructions stored in the memory to implement the method of any one of claims 1-8.

11. 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 of any one of claims 1-8.

12. A computer program product, characterized in that, Includes a computer program, which, when executed by a processor, is used to implement the method of any one of claims 1-8.

Images