Hotspot account control method and device, equipment, medium and product

Abstract

The invention discloses a hotspot account control method, device, equipment, medium and product, which are applied to the financial science and technology field, and comprise the following steps: establishing a connection with a target server through a client, and initiating a batch payment request to the target server; determining a concurrent number flow limiting result of the batch payment request through the target server side, and when the concurrent number flow limiting result is unlimited, determining an availability flow limiting result through the target server side; and when the availability traffic limiting result is unlimited, issuing a pass token to the client through the target server, and performing batch payment of the hotspot accounts through the client based on the pass token. By determining a concurrent number flow limiting result, simultaneous processing of excessive batch payment requests can be avoided, the stability of a system and reasonable allocation of resources are guaranteed, more accurate flow limiting is realized by determining availability flow limiting, the service quality and the user experience are improved, special token issuing and control can be performed for a hotspot account, and the user experience is improved. The risk is reduced; and the transaction compliance is ensured.

Description

Technical Field

[0001] The present invention relates to the field of financial technology, and in particular to a hotspot account control method, device, equipment, medium and product. Background Art

[0002] In today's highly digitalized and globalized economic environment, the scale and complexity of financial transactions are growing exponentially. With the rise of emerging business models such as e-commerce and mobile payments, batch payments have become a common and important transaction method in the financial field. However, when processing batch payment business, especially transactions involving hot accounts, there are a series of severe challenges.

[0003] The existing technology adopts a flow limiting solution based on redis database storage, but this method stores data in the cloud. If the cloud data cannot be obtained, the request is released by default, which cannot completely solve the hot account problem. It also lacks the ability to accurately identify and personalize hot accounts, and cannot be dynamically adjusted according to the real-time transaction status of hot accounts, resulting in low payment efficiency and service quality that is difficult to meet user needs. Summary of the invention

[0004] The present invention provides a hotspot account control method, device, equipment, medium and product to solve the problem of downstream timeout and suspicious account being easily triggered under high concurrent transactions, thereby increasing the transaction success rate.

[0005] According to one aspect of the present invention, a hotspot account control method is provided, which is applied to a transaction system, including: a client and a target server, and the method includes:

[0006] Establishing a connection with a target server through a client, and initiating a batch payment request to the target server, wherein the batch payment request includes a hotspot account identifier;

[0007] The target server is used to determine the result of the concurrent number limit of batch payment requests. When the concurrent number limit result is unlimited, the target server is used to determine the result of the availability limit.

[0008] When the availability limiting result is unlimited, a pass token is issued to the client through the target server, and batch payments to the hotspot account are made by the client based on the pass token.

[0009] Optionally, a connection is established between the client and the target server, including: determining the hotspot account identifier, and determining a list of alternative servers based on the hotspot account identifier; initiating a connection request to the first server in the list of alternative servers, and determining a corresponding first connection response time; when the first connection response time does not exceed a preset time threshold, using the first server as the target server, and determining to establish a connection with the target server.

[0010] Optionally, after determining the corresponding first connection response time, the method also includes: when the first response time exceeds a preset time threshold, initiating a connection request to the next server in the list of alternative servers, and determining the corresponding second connection response time; judging whether the second connection response time exceeds the preset time threshold, and if so, taking the next server as the target server, and determining to establish a connection with the target server; otherwise, determining that the connection has failed and degenerating into single-machine current limiting.

[0011] Optionally, the concurrent number limiting result of the batch payment request is determined through the target server, including: determining the query rate per second corresponding to the batch payment request; judging whether the query rate per second is greater than the query rate threshold, and if so, determining that the concurrent number limiting result is limited; otherwise, determining that the concurrent number limiting result is unlimited.

[0012] Optionally, determining the availability limiting result through the target server includes: obtaining the payment result fed back by the client through the target server, wherein the payment result includes normal payment results and abnormal payment results; determining whether the proportion of abnormal payment results in the payment results is greater than a preset proportion threshold, and if so, determining that the availability limiting result is limited; otherwise, determining that the availability limiting result is unlimited.

[0013] Optionally, the method also includes: when the concurrent number limiting result or the availability limiting result is that there is a limit, issuing a rejection token to the client through the target server; receiving the rejection token through the client, and initiating a batch payment request to the target server again after self-suspending waiting according to a preset time.

[0014] According to another aspect of the present invention, a hotspot account control device is provided, the device comprising:

[0015] A batch payment request initiation module is used to establish a connection with a target server through a client and initiate a batch payment request to the target server, wherein the batch payment request includes a hotspot account identifier;

[0016] Availability current limiting result determination module, used to determine the concurrent current limiting result of batch payment requests through the target server. When the concurrent current limiting result is unlimited, the availability current limiting result is determined through the target server.

[0017] The hotspot account batch payment module is used to issue a pass token to the client through the target server when the availability limiting result is unlimited, and the client makes batch payments to the hotspot account based on the pass token.

[0018] According to another aspect of the present invention, there is provided an electronic device, the electronic device comprising:

[0019] at least one processor;

[0020] and a memory communicatively coupled to the at least one processor;

[0021] The memory stores a computer program that can be executed by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute a hotspot account control method described in any embodiment of the present invention.

[0022] According to another aspect of the present invention, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement a hotspot account control method described in any embodiment of the present invention when executed.

[0023] According to another aspect of the present invention, a computer program product is provided. The computer program product includes a computer program. When the computer program is executed by a processor, the hotspot account control method described in any embodiment of the present invention is implemented.

[0024] The technical solution of the embodiment of the present invention can avoid too many batch payment requests from being processed simultaneously by determining the result of concurrent flow limiting, ensure the stability of the system and the reasonable allocation of resources, and achieve more accurate flow limiting by determining the availability flow limiting, ensuring that batch payments are made only when the flow limiting rules are met, reducing potential risks and errors, and improving service quality and user experience. Special token issuance and control can be performed for hot accounts to reduce risks and ensure compliance of transactions.

[0025] It should be understood that the contents described in this section are not intended to identify the key or important features of the embodiments of the present invention, nor are they intended to limit the scope of the present invention. Other features of the present invention will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0027] Figure 1 is a flow chart of a hotspot account control method provided according to Embodiment 1 of the present invention;

[0028] Figure 2 is a flow chart of another hotspot account control method provided according to Embodiment 2 of the present invention;

[0029] Figure 3is a structural diagram of a hotspot account control device provided according to Embodiment 3 of the present invention;

[0030] Figure 4 It is a structural schematic diagram of an electronic device for implementing a hotspot account control method according to an embodiment of the present invention. DETAILED DESCRIPTION

[0031] In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.

[0032] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0033] Embodiment 1

[0034] Figure 1 A flowchart of a hotspot account control method is provided for the first embodiment of the present invention. This embodiment is applicable to the scenario of controlling hotspot accounts for batch payment. The method can be executed by a hotspot account control device. The hotspot account control device can be implemented in the form of hardware and / or software. The hotspot account control device can be configured in a computer controller. Figure 1 As shown, the method includes:

[0035] S110, establishing a connection with the target server through the client, and initiating a batch payment request to the target server, wherein the batch payment request includes a hotspot account identifier.

[0036] Among them, the hot account refers to an account with a high transaction frequency in a financial transaction scenario. The embodiment of the present invention is applied to a transaction system, including: a client and a target server, the client is the party that initiates a batch payment request, such as an online banking APP or corporate financial software used by a user, and communicates with the server through a network. The target server refers to the party that receives and processes the batch payment request from the client, which can be a bank's payment processing server or a server of a third-party payment platform. A batch payment request refers to a request sent by the client to the server to perform multiple payment operations. For example, a corporate financial staff selects a batch of supplier payment information through the corporate online banking client, and sends it to the bank server at one time, requesting batch payment of goods. The hot account identifier is used to clarify the specific hot account involved in this payment operation. The hot account identifier can be an account number, user ID, etc. The server can determine which hot account the request is for through the hot account identifier, so as to perform special concurrent number and availability checks on the account.

[0037] Optionally, a connection is established between the client and the target server, including: determining the hotspot account identifier, and determining a list of alternative servers based on the hotspot account identifier; initiating a connection request to the first server in the list of alternative servers, and determining a corresponding first connection response time; when the first connection response time does not exceed a preset time threshold, using the first server as the target server, and determining to establish a connection with the target server.

[0038] It should be noted that different hot accounts may correspond to different server resource configuration requirements due to their business characteristics, geographical distribution, affiliated institutions and other factors. The system will pre-establish a mapping relationship, that is, when a hot account identifier is identified, a group of servers that may be suitable for processing the hot account business will be screened from a large number of servers according to pre-set rules to form a list of candidate servers. For example, some hot accounts may need to be connected to a server with strong cross-border payment processing capabilities due to large transaction volumes and cross-border business, while some hot accounts mainly conduct frequent small transactions locally, and may be more suitable for connecting to local servers that focus on processing small and high-frequency transactions.

[0039] Specifically, the client will first initiate a connection request to the first server in the list of alternative servers in the order of the list. The client will package its own relevant information and hotspot account identification into a suitable data packet and send it to the first server through the network to try to establish a connection. From the moment the client sends a connection request, the timer will start until the response information returned by the first server is received to determine the first connection response time. The system will pre-set a time threshold. When the first connection response time recorded by the client does not exceed this preset time threshold, it means that the first server can respond to the client's connection request more quickly under the current circumstances, and its processing capacity and current status are relatively good, which can meet the timeliness requirements of business processing. At this time, the client will use the first server as the target server and determine to establish a connection with the target server.

[0040] Optionally, after determining the corresponding first connection response time, the method also includes: when the first response time exceeds a preset time threshold, initiating a connection request to the next server in the list of alternative servers, and determining the corresponding second connection response time; judging whether the second connection response time exceeds the preset time threshold, and if so, taking the next server as the target server, and determining to establish a connection with the target server; otherwise, determining that the connection has failed and degenerating into single-machine current limiting.

[0041] Specifically, when the first connection response time exceeds the preset time threshold, it indicates that the first server fails to respond to the client's connection request in time under the current situation, which may be due to the server's own overload, network congestion, or other temporary performance problems. At this time, in order to find a server that can respond and establish a connection in time to handle the business related to the hotspot account, the client will turn to the next server to initiate a connection request in the order of the candidate server list.

[0042] Similarly, starting from sending a connection request to the next server in the list of candidate servers, the client will start the timing mechanism again to determine the second connection response time. Similar to determining the first connection response time, the second connection response time is determined until the response information returned by the next server is received. If the second connection response time does not exceed the preset time threshold, it means that the next server can respond to the client's connection request in a timely manner within an acceptable time range, and its processing capacity and current status are relatively good, which can meet the timeliness requirements of business processing. At this time, the client will use the next server as the target server and establish a connection with the target server.

[0043] It should be noted that if the first connection response time exceeds the preset time threshold, the client may continue to initiate a connection request to the next server in the order of the alternative server list, and repeat the above operations such as determining the connection response time until a server that meets the time threshold requirements is found as the target server.

[0044] Furthermore, if the client cannot establish a connection with all the clients in the list of candidate servers, the client will determine that the connection has failed and degenerate into single-machine flow control, which is a way to limit the flow on the client itself or the local device. When the connection fails, in order to avoid wasting resources or affecting other services due to continuous attempts to connect, the client will start the single-machine flow control mechanism. For example, it may limit the frequency of subsequent connection requests, or limit the flow of some existing local business operations, to ensure that when it is unable to connect to a suitable server, its own business processing can still remain orderly to a certain extent, avoiding problems such as local resource exhaustion due to excessive attempts to connect.

[0045] S120. Determine the concurrent number limiting result of the batch payment request through the target server. When the concurrent number limiting result is unlimited, determine the availability limiting result through the target server.

[0046] Among them, concurrency refers to the number of requests processed at the same time. The concurrency limit result is the result obtained by the target server after checking the received batch payment requests based on its own processing capacity and configuration limitations. If the number of batch payment requests currently being processed does not reach the maximum concurrent processing number set by the server, the concurrency limit result is unlimited. Availability refers to whether the server and downstream payment channels can process requests normally. The availability limit result is the result obtained by the target server after checking the response of the downstream system.

[0047] Optionally, the concurrent number limiting result of the batch payment request is determined through the target server, including: determining the query rate per second corresponding to the batch payment request; judging whether the query rate per second is greater than the query rate threshold, and if so, determining that the concurrent number limiting result is limited; otherwise, determining that the concurrent number limiting result is unlimited.

[0048] It should be noted that the query rate per second (QPS) is an indicator that measures the number of query requests that the system can process within one second. When the client initiates a batch payment request to the target server, the target server will disassemble and analyze the batch payment request, count the number of all payment-related operation requests involved in a unit of time, and thus determine the query rate per second corresponding to the batch payment request. Specifically, a special counter can be set inside the target server or related monitoring tools can be used. For example, in the program code that processes payment requests, a counting statement will be set at the key operation node, and each time a new payment sub-operation request arrives, the corresponding counter will be increased by 1. Then, every second, the server will obtain the value of this counter as the number of query requests in this second, that is, the query rate per second corresponding to the batch payment request.

[0049] The query rate threshold is a critical value set in advance based on the performance, resource status, and load that the business can bear of the target server. The query rate threshold represents the maximum number of query requests that can be accepted per second while ensuring the stable operation of the system, being able to process payment services normally, and without performance bottlenecks or failures. For example, after performance testing and business analysis, the target server found that when processing more than 500 payment-related query requests per second, problems such as excessive CPU usage and slow database response may occur, affecting the normal operation of payment services. At this time, 500 can be set as the query rate threshold.

[0050] Specifically, when the target server determines the query rate per second corresponding to the batch payment request, it will compare it with the query rate threshold. If the query rate per second is greater than the query rate threshold, it indicates that the number of query requests brought by the current batch payment request has exceeded the reasonable range that the system can bear. At this time, too many requests may cause server resource tension, such as excessive occupation of CPU, memory and other resources, which in turn affects the stability of the system and the normal processing of payment services. At this time, the target client will determine that the concurrent number limit result is limited. If the query rate per second is not greater than the query rate threshold, it means that the query rate brought by the current batch payment request is within the range that the system can bear, and the system currently has sufficient resources and capabilities to process these requests. At this time, the target client will determine that the concurrent number limit result is unlimited.

[0051] S130: When the availability limiting result is unlimited, a pass token is issued to the client through the target server, and batch payments are made to the hotspot account based on the pass token through the client.

[0052] The pass token is a payment authorization certificate. When the batch payment request passes the concurrent number and availability checks, the target server will issue the token to the client. When the client makes batch payments to hotspot accounts, it needs to provide this pass token to prove that it has been approved by the server and ensure that the payment operation is legal and compliant.

[0053] Optionally, the method also includes: when the concurrent number limiting result or the availability limiting result is that there is a limit, issuing a rejection token to the client through the target server; receiving the rejection token through the client, and initiating a batch payment request to the target server again after self-suspending waiting according to a preset time.

[0054] Specifically, when the target server determines that the concurrent number limiting result is limited, it means that the concurrent number of batch payment requests received by the current system has exceeded the system's tolerance. In order to protect the stability and normal operation of the system, the target server will issue a rejection token to the client at this time. Similarly, when the availability limiting result is limited, it means that the system has encountered a large number of abnormal payment results in the process of processing payment requests, and their proportion has exceeded the preset ratio threshold. At this time, the availability of the system is affected, and continuing to process a large number of payment requests may further deteriorate the system status and cause more abnormal situations, so the target server will also issue a rejection token to the client.

[0055] Furthermore, after receiving the rejection token, the client will not immediately initiate a batch payment request to the target server again, but will wait for a preset time. The preset time is set based on system characteristics and business requirements. For example, it may be considered that the system may not be able to quickly solve the problem that leads to the issuance of rejection tokens in a short period of time, such as the high concurrency may take some time to process some requests to return to the normal range, or the system failure needs time to repair, so a waiting time is set to give the system a certain amount of time to adjust its own state. The preset time can be 5 minutes. During the self-suspended waiting period, the client will suspend operations related to this batch payment request, such as suspending the display of the request progress to the user, so as to avoid misleading the user. At the same time, the client itself is also in a relatively "dormant" state, reducing the occupation of system resources and waiting for the preset time to end. When the preset time ends, the client will initiate a batch payment request to the target server again. At this time, the target server will again check the concurrency limit result and availability limit result of the new batch payment request to determine whether the batch payment is carried out normally, thereby ensuring the stability of the system and the normal development of the payment business.

[0056] The technical solution of the embodiment of the present invention can avoid too many batch payment requests from being processed simultaneously by determining the result of concurrent flow limiting, ensure the stability of the system and the reasonable allocation of resources, and achieve more accurate flow limiting by determining the availability flow limiting, ensuring that batch payments are made only when the flow limiting rules are met, reducing potential risks and errors, and improving service quality and user experience. Special token issuance and control can be performed for hot accounts to reduce risks and ensure compliance of transactions.

[0057] Embodiment 2

[0058] Figure 2 This is a flowchart of a hotspot account control method provided in the second embodiment of the present invention. This embodiment adds a specific process of determining the availability flow limiting result through the target server on the basis of the above-mentioned first embodiment. Among them, the specific contents of steps S210-S220 are roughly the same as steps S110-S120 in the first embodiment, so they will not be repeated in this embodiment. Figure 2 As shown, the method includes:

[0059] S210. Establish a connection with the target server through the client, and initiate a batch payment request to the target server, wherein the batch payment request includes a hotspot account identifier.

[0060] Optionally, a connection is established between the client and the target server, including: determining the hotspot account identifier, and determining a list of alternative servers based on the hotspot account identifier; initiating a connection request to the first server in the list of alternative servers, and determining a corresponding first connection response time; when the first connection response time does not exceed a preset time threshold, using the first server as the target server, and determining to establish a connection with the target server.

[0061] Optionally, after determining the corresponding first connection response time, the method also includes: when the first response time exceeds a preset time threshold, initiating a connection request to the next server in the list of alternative servers, and determining the corresponding second connection response time; judging whether the second connection response time exceeds the preset time threshold, and if so, taking the next server as the target server, and determining to establish a connection with the target server; otherwise, determining that the connection has failed and degenerating into single-machine current limiting.

[0062] S220. Determine the result of the concurrent flow limit of the batch payment request through the target server.

[0063] Optionally, the concurrent number limiting result of the batch payment request is determined through the target server, including: determining the query rate per second corresponding to the batch payment request; judging whether the query rate per second is greater than the query rate threshold, and if so, determining that the concurrent number limiting result is limited; otherwise, determining that the concurrent number limiting result is unlimited.

[0064] S230. When the result of the concurrent number limiting is unlimited, the payment result fed back by the client is obtained through the target server, where the payment result includes a normal payment result and an abnormal payment result.

[0065] Specifically, when the client receives the pass token, it will execute batch payment and generate corresponding payment results. The payment results include normal payment results, indicating that the payment operation is successfully completed and the funds have been successfully transferred, and abnormal payment results, such as payment failure, which may be caused by insufficient account balance, incorrect recipient information, system failure, etc.

[0066] S240, determine whether the proportion of abnormal payment results in the payment results is greater than a preset ratio threshold, if so, execute S250, otherwise, execute S260.

[0067] The preset ratio threshold refers to the maximum ratio of abnormal payment results that can be tolerated in all payment results under the premise of ensuring the normal operation of the system and the normal development of business. The preset ratio threshold can be set comprehensively based on factors such as the performance of the target server, the acceptable risk level of the business, and the system stability requirements. For example, for a payment system with high stability requirements and relatively low business risk tolerance, the preset ratio threshold may be set relatively low, such as 5%. At this time, if the proportion of abnormal payment results in all payment results exceeds 5%, it may have a significant impact on the availability of the system and the normal development of the business.

[0068] S250: Determine that the availability current limiting result is that there is a limitation.

[0069] Specifically, after obtaining the payment results fed back by the client, the target server will conduct statistical analysis on the abnormal payment results and calculate the ratio of abnormal payment results to the payment results. If the ratio is greater than the preset ratio threshold, it means that the system currently has a serious abnormal payment situation, which may be caused by a variety of reasons such as system failure, network instability, and abnormal downstream services. At this time, a large number of abnormal payment results will affect the availability of the system, which may lead to problems such as reduced user experience and obstruction of business processes. The target server will determine that the availability limit result is limited, that is, it is necessary to limit the availability of subsequent payment requests, such as delaying the processing of some requests, putting some requests in the waiting queue, or directly rejecting them, in order to ensure the stability and availability of the system. If the ratio of abnormal payment results to the payment results is not greater than the preset ratio threshold, it means that the current payment situation of the system is relatively stable. Although there may be some individual abnormal payment situations, they do not exceed the acceptable range of the business as a whole. At this time, the availability limit result will be determined as unlimited.

[0070] S260: Determine that the availability current limiting result is unlimited, issue a pass token to the client through the target server, and make batch payments to the hotspot account based on the pass token through the client.

[0071] Optionally, the method also includes: when the concurrent number limiting result or the availability limiting result is that there is a limit, issuing a rejection token to the client through the target server; receiving the rejection token through the client, and initiating a batch payment request to the target server again after self-suspending waiting according to a preset time.

[0072] The technical solution of the embodiment of the present invention can accurately judge the actual availability of the service by analyzing the payment results fed back by the client, and dynamically determine the availability flow limiting result according to the comparison between the proportion of abnormal payment results and the preset proportion threshold, so that the flow limiting strategy can adapt to the actual operation of the system in real time. When the proportion of abnormal payment results is too high, timely restriction is carried out, which helps to reduce the risk of financial transactions and ensure the safety of funds and the normal progress of transactions.

[0073] Embodiment 3

[0074] Figure 3 This is a schematic diagram of the structure of a hotspot account control device provided by Embodiment 3 of the present invention. Figure 3 As shown, the device includes: a batch payment request initiating module 310, which is used to establish a connection with a target server through a client and initiate a batch payment request to the target server, wherein the batch payment request includes a hotspot account identifier;

[0075] An availability flow limiting result determination module 320 is used to determine the concurrent flow limiting result of the batch payment request through the target server, and when the concurrent flow limiting result is unlimited, determine the availability flow limiting result through the target server;

[0076] The hotspot account batch payment module 330 is used to issue a pass token to the client through the target server when the availability limiting result is unlimited, and to make batch payments to the hotspot accounts based on the pass token through the client.

[0077] Optionally, the batch payment request initiation module 310 specifically includes: a connection establishment unit, used to: determine the hotspot account identifier, and determine the list of alternative servers based on the hotspot account identifier; initiate a connection request to the first server in the list of alternative servers, and determine the corresponding first connection response time; when the first connection response time does not exceed the preset time threshold, use the first server as the target server, and determine to establish a connection with the target server.

[0078] Optionally, the batch payment request initiation module 310 also includes: a next server connection unit, which is used to: after determining the corresponding first connection response time, when the first response time exceeds a preset time threshold, initiate a connection request to the next server in the alternative server list, and determine the corresponding second connection response time; determine whether the second connection response time produces the preset time threshold, and if so, use the next server as the target server and determine to establish a connection with the target server; otherwise, determine that the connection has failed and degenerate into single-machine current limiting.

[0079] Optionally, the availability flow limiting result determination module 320 specifically includes: a concurrent flow limiting result determination unit, used to: determine the query rate per second corresponding to the batch payment request; determine whether the query rate per second is greater than the query rate threshold, and if so, determine that the concurrent flow limiting result is limited; otherwise, determine that the concurrent flow limiting result is unlimited.

[0080] Optionally, the availability flow limiting result determination module 320 specifically includes: an availability flow limiting result determination unit, which is used to: obtain the payment result fed back by the client through the target server, wherein the payment result includes normal payment results and abnormal payment results; determine whether the proportion of abnormal payment results in the payment results is greater than a preset proportion threshold, and if so, determine that the availability flow limiting result is limited; otherwise, determine that the availability flow limiting result is unlimited.

[0081] Optionally, the device also includes: a self-suspended waiting module, which is used to: when the concurrent number limiting result or the availability limiting result is that there is a limit, issue a rejection token to the client through the target server; receive the rejection token through the client, and initiate a batch payment request to the target server again after self-suspending waiting for a preset time.

[0082] The technical solution of the embodiment of the present invention can avoid too many batch payment requests from being processed simultaneously by determining the result of concurrent flow limiting, ensure the stability of the system and the reasonable allocation of resources, and achieve more accurate flow limiting by determining the availability flow limiting, ensuring that batch payments are made only when the flow limiting rules are met, reducing potential risks and errors, and improving service quality and user experience. Special token issuance and control can be performed for hot accounts to reduce risks and ensure compliance of transactions.

[0083] A hotspot account control device provided in an embodiment of the present invention can execute a hotspot account control method provided in any embodiment of the present invention, and has functional modules and beneficial effects corresponding to the execution method.

[0084] Embodiment 4

[0085] Figure 4A schematic diagram of the structure of an electronic device 10 that can be used to implement an embodiment of the present invention is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital assistants, cellular phones, smart phones, wearable devices (such as helmets, glasses, watches, etc.) and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present invention described and / or required herein.

[0086] like Figure 4 As shown, the electronic device 10 includes at least one processor 11, and a memory connected to the at least one processor 11, such as a read-only memory (ROM) 12, a random access memory (RAM) 13, etc., wherein the memory stores a computer program that can be executed by at least one processor, and the processor 11 can perform various appropriate actions and processes according to the computer program stored in the read-only memory (ROM) 12 or the computer program loaded from the storage unit 18 to the random access memory (RAM) 13. In the RAM 13, various programs and data required for the operation of the electronic device 10 can also be stored. The processor 11, the ROM 12, and the RAM 13 are connected to each other through a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0087] A number of components in the electronic device 10 are connected to the I / O interface 15, including: an input unit 16, such as a keyboard, a mouse, etc.; an output unit 17, such as various types of displays, speakers, etc.; a storage unit 18, such as a disk, an optical disk, etc.; and a communication unit 19, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 19 allows the electronic device 10 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks.

[0088] The processor 11 may be a variety of general and / or special processing components with processing and computing capabilities. Some examples of the processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any appropriate processor, controller, microcontroller, etc. The processor 11 executes the various methods and processes described above, such as a hotspot account control method.

[0089] In some embodiments, a hotspot account control method may be implemented as a computer program, which is tangibly contained in a computer-readable storage medium, such as a storage unit 18. In some embodiments, part or all of the computer program may be loaded and / or installed on the electronic device 10 via the ROM 12 and / or the communication unit 19. When the computer program is loaded into the RAM 13 and executed by the processor 11, one or more steps of a hotspot account control method described above may be performed. Alternatively, in other embodiments, the processor 11 may be configured to perform a hotspot account control method in any other appropriate manner (e.g., by means of firmware).

[0090] Various implementations of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various implementations can include: being implemented in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0091] Computer programs for implementing the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that when the computer program is executed by the processor, the functions / operations specified in the flow chart and / or block diagram are implemented. The computer program may be executed entirely on the machine, partially on the machine, partially on the machine and partially on a remote machine as a stand-alone software package, or entirely on a remote machine or server.

[0092] In the context of the present invention, a computer-readable storage medium may be a tangible medium that may contain or store a computer program for use by or in combination with an instruction execution system, device or equipment. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices or equipment, or any suitable combination of the foregoing. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0093] To provide interaction with a user, the systems and techniques described herein may be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and a pointing device (e.g., a mouse or trackball) through which the user can provide input to the electronic device. Other types of devices may also be used to provide interaction with the user; for example, the feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form (including acoustic input, voice input, or tactile input).

[0094] The systems and techniques described herein may be implemented in a computing system that includes backend components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes frontend components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such backend components, middleware components, or frontend components. The components of the system may be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), a blockchain network, and the Internet.

[0095] A computing system may include a client and a server. The client and the server are generally remote from each other and usually interact through a communication network. The client and server relationship is generated by computer programs running on the corresponding computers and having a client-server relationship with each other. The server may be a cloud server, also known as a cloud computing server or cloud host, which is a host product in the cloud computing service system to solve the defects of difficult management and weak business scalability in traditional physical hosts and VPS services.

[0096] It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps described in the present invention can be executed in parallel, sequentially or in different orders, as long as the desired results of the technical solution of the present invention can be achieved, and this document does not limit this.

[0097] The above specific implementations do not constitute a limitation on the protection scope of the present invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A hotspot account control method, characterized in that: Applied to the trading system, including: client and target server, the method includes: Establishing a connection with a target server through a client, and initiating a batch payment request to the target server, wherein the batch payment request includes a hotspot account identifier; Determine the concurrent number limiting result of the batch payment request through the target server, and when the concurrent number limiting result is unlimited, determine the availability limiting result through the target server; When the availability flow limiting result is unlimited, a pass token is issued to the client through the target server, and batch payments of hotspot accounts are made by the client based on the pass token.

2. The method according to claim 1, characterized in that The step of establishing a connection between the client and the target server includes: Determine the hotspot account identifier, and determine a list of candidate servers according to the hotspot account identifier; Initiate a connection request to the first server in the candidate server list, and determine a corresponding first connection response time; When the first connection response time does not exceed a preset time threshold, the first server is used as a target server, and it is determined to establish a connection with the target server.

3. The method according to claim 2, characterized in that After determining the corresponding first connection response time, the method further includes: When the first response time exceeds a preset time threshold, initiating a connection request to the next server in the candidate server list, and determining a corresponding second connection response time; Determine whether the second connection response time exceeds a preset time threshold, and if so, take the next server as a target server and determine to establish a connection with the target server; Otherwise, the connection is determined to have failed and the system degenerates into single-machine current limiting.

4. The method according to claim 1, characterized in that: The determining, by the target server, a result of the concurrent number limiting of the batch payment request includes: Determine a query rate per second corresponding to the batch payment request; Determine whether the query rate per second is greater than the query rate threshold, and if so, determine that the concurrent number limiting result is that there is a limit; Otherwise, the concurrent limit result is determined to be unlimited.

5. The method according to claim 4, characterized in that The determining of the availability current limiting result by the target server includes: Obtaining, through the target server, a payment result fed back by the client, wherein the payment result includes a normal payment result and an abnormal payment result; Determine whether the proportion of the abnormal payment results in the payment results is greater than a preset proportion threshold, and if so, determine that the availability flow limiting result is limited; Otherwise, the availability throttling result is determined to be unlimited.

6. The method according to claim 5, characterized in that The method further comprises: When the concurrent number limiting result or the availability limiting result is that there is a limit, issuing a rejection token to the client through the target server; The client receives the rejection token, and after self-suspending waiting for a preset time, a batch payment request is initiated to the target server again.

7. A hotspot account control device, characterized in that: include: A batch payment request initiating module, used to establish a connection with a target server through a client, and initiate a batch payment request to the target server, wherein the batch payment request includes a hotspot account identifier; An availability flow limiting result determination module, used to determine the concurrent number flow limiting result of the batch payment request through the target server, and when the concurrent number flow limiting result is unlimited, determine the availability flow limiting result through the target server; The hotspot account batch payment module is used to issue a pass token to the client through the target server when the availability limiting result is unlimited, and to make batch payments to the hotspot account based on the pass token through the client.

8. An electronic device, characterized in that: The electronic device comprises: at least one processor; and a memory communicatively coupled to the at least one processor; The memory stores a computer program that can be executed by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute the method according to any one of claims 1 to 6.

9. A computer storage medium, characterized in that: The computer storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the method according to any one of claims 1 to 6 when executed.

10. A computer program product, characterized in that The computer program product comprises a computer program which, when executed by a processor, implements the method according to any one of claims 1 to 6.

Images