WO2024046303A1

WO2024046303A1 - Access request processing method, apparatus, and system

Info

Publication number: WO2024046303A1
Application number: PCT/CN2023/115453
Authority: WO
Inventors: 陈永谦; 龙卉; 龚辉; 张强
Original assignee: 中兴通讯股份有限公司
Priority date: 2022-09-01
Filing date: 2023-08-29
Publication date: 2024-03-07
Also published as: CN117675921A

Abstract

The present application discloses an access request processing method, apparatus, and system. The method comprises: according to a received access request, applying for a forwarding token; in response to the number of forwarding tokens in a token pool being non-zero, forwarding to a background system the access request carrying forwarding token information, the token pool having a preset number of forwarding tokens, and the preset number being determined on the basis of the performance of the background system and the performance of a current gateway; and updating the number of forwarding tokens of the token pool according to the access request carrying the forwarding token information and received response information carrying the forwarding token information.

Description

Access request processing method, device and system

cross reference

This application claims priority to a Chinese patent application filed with the China Patent Office on September 1, 2022, with application number 202211069611.2 and titled "Access Request Processing Method, Device and System". The entire content of this application is incorporated herein by reference. Applying.

Technical field

This application belongs to the technical field of information technology, and specifically relates to an access request processing method, device and system.

Background technique

API (Application Programming Interface, Application Programming Interface) gateway cluster is a multi-machine cluster environment composed of several API gateway servers. It forwards external network access requests to the API interface services provided by the system. During the forwarding process, the API gateway controls the access request. Due to the low complexity of the API gateway business and to ensure that network request traffic is not lost in the API gateway link, the performance of the API gateway is usually much higher than the backend service system (hereinafter referred to as the backend system). In order to protect the backend forwarded by the API gateway The system will not be impacted by large traffic, so it is important to limit access requests to the API gateway.

Currently, API gateway current limiting methods are generally divided into two types:

1. Rate limiting, that is, controlling the number of access requests within a certain period of time, for example, 100 times per second, 200 times every 20 seconds. However, this method uses time as the control dimension and cannot sense the running status of the background system in a timely manner; and, for scenarios where the API time-consuming is variable, this method cannot accurately evaluate the rate limiting configuration of the API gateway.

2. Concurrency limiting, that is, limiting the number of access requests to the backend system at the same time. For example, limiting the number of access requests to 10 means that the number of requests to access the backend system at the same time is 10. However, this method only provides overall control of the backend system and cannot accurately control the current limit of a single API gateway.

At the same time, for access requests that are restricted by the above two methods, the usual approach is to wait for the scheduled time After a certain period of time, the access request is directly forwarded to the backend system or the API gateway blocks the polling current limit. These methods do not consider the performance of the backend system and can easily lead to the downtime of the backend system.

In other words, the API gateway current limiting method in related technologies does not take into account the performance of the gateway and the backend system, and can easily lead to the downtime of the backend system.

Contents of the invention

The purpose of the embodiments of this application is to provide an access request processing method, device and system that can solve the problem in related technologies that the API gateway current limiting method does not take into account the performance of the gateway and the backend system, and easily leads to the downtime of the backend system.

In the first aspect, embodiments of the present application provide a method for processing access requests. The method includes: applying for a forwarding token according to the received access request; in response to the number of forwarding tokens in the token pool being non-zero, the method carrying the The access request for forwarding token information is forwarded to the backend system, where the token pool has a preset number of forwarding tokens, and the preset number is determined based on the performance of the backend system and the current gateway performance; The access request for token information and the received response information carrying the forwarding token information are updated to update the number of forwarding tokens in the token pool.

In the second aspect, embodiments of the present application provide an access request processing device. The device includes: a token application unit, configured to apply for a forwarding token according to the received access request; and a forwarding unit, configured to respond to the token pool. The number of forwarding tokens in is non-zero, and the access request carrying the forwarding token information is forwarded to the backend system, where the token pool has a preset number of forwarding tokens, and the preset number is based on the backend system performance and Current gateway performance is determined; a token update unit is configured to update the forwarding token of the token pool according to the access request carrying the forwarding token information and the received response information carrying the forwarding token information. quantity.

In the third aspect, embodiments of the present application provide an access request processing system, which includes: the above-mentioned access request processing device, a backend system, and a gateway cluster including at least one gateway, wherein the access request processing device is located at Describe the gateway cluster side.

In a fourth aspect, embodiments of the present application provide an electronic device. The electronic device includes a processor, a memory, and a program or instructions stored on the memory and executable on the processor. The program or instructions are When executed by the processor, the steps of the method described in the first aspect are implemented.

In the fifth aspect, embodiments of the present application provide a readable storage medium. Programs or instructions are stored on the readable storage medium. When the programs or instructions are executed by a processor, the method described in the first aspect is implemented. Method steps.

Description of drawings

Figure 1 is an example structural diagram of an API gateway cluster in related technologies;

Figure 2 is a schematic flow chart of an access request processing method provided by an embodiment of the present application;

Figure 3 is a schematic flowchart of the current limiting flow of the access request processing method provided by the embodiment of the present application;

Figure 4 is a schematic diagram of the request response flow of the access request processing method provided by the embodiment of the present application;

Figure 5 is a schematic diagram of another current limiting flowchart of the access request processing method provided by the embodiment of the present application;

Figure 6 is another schematic flowchart of an access request processing method provided by an embodiment of the present application;

Figure 7 is a structural block diagram of the access request processing system provided by the embodiment of the present application;

Figure 8 is a structural block diagram of the access request processing device 1 provided by the embodiment of the present application;

Figure 9 is a structural example diagram of an API gateway current limiting system in related technologies;

Figure 10 is a structural example diagram of the access request processing system provided by the embodiment of the present application;

Figure 11 is a schematic structural diagram of an electronic device provided by an embodiment of the present application.

Detailed ways

The technical solutions in the embodiments of the present application will be clearly described below with reference to the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, but not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by those of ordinary skill in the art fall within the scope of protection of this application.

In the process of implementing this application, the applicant discovered the following related technologies:

Figure 1 is an example structural diagram of an API gateway cluster in related technologies. As shown in Figure 1, the API gateway includes: a configuration module, a current limiting module and a forwarding module. The configuration module is used to set the current limiting configuration information and The flow configuration information is written to the current limiting module. When forwarding the access request, the forwarding module processes the access request according to the current limiting configuration information in the current limiting module and forwards it to the backend system or temporarily limits the flow.

In view of the fact that the API gateway current limiting method in the related art does not take into account the performance of the gateway and the backend system, it is easy to cause the backend system to crash. Based on this, the embodiment of the present application provides an access request processing solution. This solution sets up a token pool based on the performance of the backend system and gateway, and limits forwarding access requests based on the tokens in the token pool, thereby protecting the backend system from being impacted by large traffic and avoiding downtime of the backend system.

The embodiments of the present application will be described in detail below with reference to the accompanying drawings through specific embodiments and application scenarios.

Figure 2 is a schematic flowchart of an access request processing method provided by an embodiment of the present application. As shown in Figure 2, the method may include the following steps S210-S230.

S210: Apply for a forwarding token according to the received access request.

Before performing this step, you need to pre-set a token pool with a preset number of forwarding tokens, which is determined based on background system performance and current gateway performance. The preset number of forwarding tokens here refers to the access requests that can be forwarded through the gateway at the same time.

S220: In response to the number of forwarding tokens in the token pool being non-zero, forward the access request carrying the forwarding token information to the backend system.

That is to say, when there is a forwarding token in the token pool, it means that the access request received at this time can be forwarded, and then the access request carrying the forwarding token information will be forwarded to the backend system, and then the access request in the token pool will be forwarded. The number of forwarding tokens is reduced by one. Until the number of forwarding tokens in the token pool reaches zero, it means that the access request received at this time needs to wait and cannot be forwarded immediately. In this way, the current limiting function of the gateway is achieved.

Since the number of forwarding tokens in the token pool is set based on the backend system performance and the current gateway performance, access requests will not put excessive pressure on the backend system, thereby avoiding backend system downtime and improving the overall System resource utilization.

In one embodiment, when the gateway cluster includes multiple gateways, a token pool with a different preset number of forwarding tokens can be set for each gateway according to the background system performance and the performance of each gateway. That is to say, token pools can be set up for different gateways in the gateway cluster. The number of forwarding tokens in each token pool can be different. Specifically, the number of forwarding tokens in each token pool can be based on the background system performance and respective Determine gateway performance.

In one embodiment, when the number of forwarding tokens in the token pool is zero, the access request may be sent to the waiting queue to wait. At the same time, the notification process can be triggered. This notification process is used to notify access requests in the waiting queue to apply for forwarding tokens when the number of forwarding tokens in the token pool is non-zero.

S230: Update the number of forwarding tokens in the token pool according to the above-mentioned access request carrying forwarding token information and the received response information carrying forwarding token information.

Specifically, according to the above-mentioned access request carrying the forwarding token information, the number of forwarding tokens in the token pool is reduced by one; then, according to the received response information carrying the above-mentioned forwarding token information, the number of forwarding tokens in the token pool is reduced by one. The number of forwarding tokens in is increased by one.

That is to say, when an access request is forwarded, the number of forwarded tokens in the token pool will be reduced by one. When the response request for the access request is returned, it means that the access request has been completed. At this time, the number of forwarded tokens in the token pool will be reduced by one. The number of forwarding tokens is increased by one. In this way, the current limit on the access requests forwarded by the gateway is realized, and the downtime of the backend system is avoided.

In the embodiment of this application, by setting a preset number of forwarding tokens according to the background system performance and the current gateway performance, it is possible to determine whether to forward the access request based on the number of forwarding tokens, because the number of forwarding tokens is based on the background system performance and the current gateway performance. settings, thus protecting the backend system from being impacted by heavy traffic and avoiding downtime of the backend system.

In order to better understand this application, the access request processing flow in the embodiment of this application is described in detail below in conjunction with Figures 3-5.

Figure 3 is a schematic diagram of the current limiting process of the access request processing method according to the embodiment of the present application. As shown in Figure 3, in the current limiting process, a token pool is added. During the current limiting configuration, the configured concurrency limit will be initialized. Number of flows, used to set the number of forwarding tokens (can be referred to as tokens for short). For example, if the number of concurrent current limits is configured to 10, 10 tokens will be initialized in the token pool. When a request needs to be forwarded, it needs to apply for a token from the token pool. When there is a token in the token pool, the request can carry a token (that is, carry the token information) and forward it to the backend system. Access Backend, the token pool will be reduced by 1 token at this time.

Figure 4 is a schematic diagram of the request response flow of the access request processing method according to the embodiment of the present application. As shown in Figure 4, when the response to the access request is returned, the tokens carried will be returned. At this time, the number of tokens in the token pool increases. 1 to provide for subsequent request applications.

Figure 5 is another schematic diagram of the current limiting process of the access request processing method according to the embodiment of the present application. As shown in Figure 5, when the number of tokens in the token pool is zero, the request to apply for a token fails at this time. This request is subject to current limiting processing, and the request is sent to the waiting queue to wait, and the notification process is triggered at the same time. When there are tokens in the token pool, the notification process will notify requests in the waiting queue to continue applying for tokens to facilitate access to the backend system.

In the embodiment of this application, the above-mentioned token pool has the following functions:

(1) The number of tokens remaining in the token pool represents the maximum access capability of the current gateway.

(2) The number of tokens in the token pool determines the process of the access request. When the access request obtains the token If the token is obtained, it can enter the forwarding process of the gateway, and if the token is not obtained, it can enter the waiting queue process of the gateway.

(3) When the number of tokens in the token pool is zero, the notification event will be activated. When the token exists again in the token pool, the token pool will trigger the request in the notification waiting queue to apply for the token again for subsequent access. process. Activating or triggering the notification process. Compared with the access waiting mechanism in related technologies, the active notification in the embodiment of the present application can improve resource utilization.

Taking the gateway as an API gateway as an example, the following describes the access request processing method in the embodiment of the present application in detail in conjunction with the process shown in Figure 6 .

As shown in Figure 6, the access request processing method specifically includes the following steps S601-S606:

S601: Receive the request, and the API gateway forwards the request.

S602: Request to enter the current limiting process and apply for a token from the token pool.

S603: Determine whether there is a token in the token pool. If so, proceed to S604; otherwise, proceed to S605.

S604: Forward the request carrying the applied token to the backend system.

S605: The API gateway is in current limit, and sends the request to the waiting queue, waiting for the token pool to be returned after the request is completed, and then applies for a token.

S606: When the request forwarded to the background system in S604 returns a response, the token carried is returned to the token pool. At this time, it means that the API gateway can forward another request.

The embodiment of this application is based on the token pool function, which reduces the resources occupied by the API gateway during concurrent current limiting in related technologies. The recycling token method increases the control accuracy of current limiting, reduces the time required in related technologies to release a concurrent process after receiving a response, and improves the utilization of the API gateway. At the same time, by recycling tokens, requests waiting in the queue can be actively notified to enter the forwarding process again, which saves access time, increases the utilization of the background system, and improves the ability to forward all unrestricted forwarding or enter the forwarding limit again after passive activation. process, increasing the stability of the entire system.

Based on a similar inventive concept, embodiments of the present application also provide an access request processing system, as shown in Figure 7. The system includes: an access request processing device 1, a backend system 2 and a gateway cluster 3, where the gateway cluster 3 includes At least one gateway, the access request processing device 1 is located at the gateway cluster 3 end.

Figure 8 is a structural block diagram of an access request processing device 1 according to an embodiment of the present application. As shown in Figure 8, the access request processing device 1 includes: a token application unit 11, a forwarding unit 12 and a token update unit 13, where:

The token application unit 11 is used to apply for a forwarding token according to the received access request.

The forwarding unit 12 is configured to forward the access request carrying the forwarding token information to the backend system in response to the non-zero number of forwarding tokens in the token pool, where the token pool has a preset number of forwarding tokens. , the preset number is determined based on the background system performance and the current gateway performance.

The token updating unit 13 is configured to update the number of forwarding tokens in the token pool according to the access request carrying the forwarding token information and the received response information carrying the forwarding token information.

Specifically, the token update unit 13 reduces the number of forwarding tokens in the token pool by one according to the access request carrying the forwarding token information, and reduces the number of forwarding tokens in the token pool by one according to the received access request carrying the forwarding token information. response information, increase the number of forwarding tokens in the token pool by one.

In the embodiment of the present application, by setting a preset number of forwarding tokens according to the background system performance and the current gateway performance, the forwarding unit 12 can determine whether to forward the access request according to the number of forwarding tokens, because the number of forwarding tokens is based on the background system performance and the current gateway performance. The current gateway performance settings can protect the backend system from being impacted by heavy traffic and avoid downtime of the backend system.

In one embodiment, the above-mentioned access request processing device 1 further includes: a request waiting unit, configured to send the access request to the waiting queue in response to the number of forwarding tokens in the token pool being zero.

In one embodiment, the above-mentioned access request processing device 1 further includes: a notification process triggering unit, configured to trigger a notification process. The notification process is used to notify all forwarding tokens when the number of forwarding tokens in the token pool is non-zero. The access request in the waiting queue applies for the forwarding token.

In specific implementation, the above-mentioned access request processing device 1 also includes: a token pool setting unit, configured to respond to the gateway cluster including multiple gateways, and set different presets for each gateway according to the performance of the background system and the performance of each gateway. Let the number of forwarding tokens in the token pool.

The access request processing device in the embodiment of the present application may be a device, or may be a component, integrated circuit, or chip in the system, which is not specifically limited in the embodiment of the present application.

The access request processing device provided by the embodiment of the present application can implement each process in the method embodiments of Figures 2-6 and achieve the same technical effect. To avoid duplication, the details will not be described here.

In order to better understand the present application, the embodiments of the present application will be described in detail below with reference to Figures 9-10.

Figure 9 is a structural example diagram of an API gateway current limiting system in related technologies. As shown in Figure 9, in this system, access requests are forwarded through a current limiting module and a forwarding model. The back-end API provides back-end services for the internal GUI (Graphical User Interface, graphical user interface) channel (used by internal management) and WEB channel (used by external users). Among them, the traffic of the WEB interface is in a certain Sometimes the traffic is much larger than that of the GUI, often causing the GUI access API to be unable to obtain the background system service response, resulting in inability to enter. In related technologies, the API gateway rate limiting module (i.e., the current limiting module in the figure) was introduced, but the effect was not good because the specific configuration of the rate limiting could not be estimated, and the setting was too large to reach the GUI channel. The purpose of being affected by WEB channel access is also unable to achieve the purpose of protecting back-end system services, which may cause greater access pressure on back-end system services and the possibility of downtime; if the setting is too small, the GUI channel access will not be affected by WEB Channel access affects the purpose, but the background system services are often idle, resulting in a waste of resources.

Figure 10 is a structural example diagram of an access request processing system according to an embodiment of the present application. In this system, forwarding and current limiting of access requests are implemented through a token pool. In this example, the background system performance is able to handle 64 access requests at the same time. In order to prevent the internal GUI channel from being affected by the WEB channel, you can set the number of concurrent access requests to 60. After configuring the API gateway, 60 will be initialized in the token pool. A token means that the WEB channel access through the API gateway can handle 60 requests at the same time, leaving 4 requests for the GUI channel. This ensures that the entire system can operate normally for access provided by different channels, and also ensures that the access requests are correct. The background system will not generate excessive pressure and avoid system downtime.

When the background system processes more than 60 requests at the same time, the number of tokens in the token pool is 0. At this time, new requests will enter the waiting queue. When a request is processed and returned, the token will be returned to the token pool when the response is returned through the API gateway. At this time, if there is a token in the token pool, a notification will be triggered for the request in the waiting queue to apply for a token. , thereby forwarding it to the backend system.

In this example, you can also set different current limiting configurations for different API gateways. Each API gateway can correspond to a token pool and waiting queue. Specifically, the number of tokens in each token pool can be based on the actual backend system. and gateway performance, this application does not limit this.

Through the current limiting method in this example, the resource pressure of the API gateway waiting queue on the API gateway can be improved. Through the notification mechanism in this example, the access efficiency and resource utilization of the background system can be improved.

In this example, by setting the number of concurrent current limits based on background system performance, the current limit accuracy is higher compared to the current limit method shown in Figure 9. At the same time, in this example, through the issuance and recycling of tokens, the waiting pressure on the backend system is reduced, and the possibility of downtime of the backend system is reduced.

By adding the design of the token pool, the gateway is prevented from determining the number of concurrent connections through the working process, saving the resources occupied by the API gateway, while improving the current-limited access processing, and changing the openresty gateway (a kind of related technology). API gateway) will limit all traffic after a certain sleep time. All accesses are forwarded to the target background service, leading to the risk of increased operating pressure or even downtime of the background service. At the same time, in the API response process, the token is returned to the token pool through the forwarding module, and the token pool notifies the access waiting queue for access, which improves the situation in related technologies that the concurrent number must be released after receiving the API response, making The concurrent number is released in advance, which increases the access forwarding efficiency of the API gateway.

Regarding the current limiting method of openresty gateway in related technologies, for example, openresty gateway can launch 10 working processes at the same time. When more than 10 working processes are concurrent, API access will sleep for 5 seconds, and after 5 seconds, all access requests will be forwarded to In the background system, this may cause the background system service processing capacity to be insufficient, the background request queue to be long, and the background service to be unstable. In the embodiment of this application, the design of the token pool is added, which prevents the gateway from determining the number of concurrent connections through the working process, saves the resources occupied by the API gateway, and also improves the processing of current-limited access. Compared with the openresty gateway in related technologies that forwards all flow-limited accesses to the target backend system after a certain sleep time, the embodiment of this application makes the waiting requests through the issuance and recycling of tokens and the waiting queue. It can be released in time, which improves the gateway's access request forwarding efficiency.

Optionally, as shown in Figure 11, this embodiment of the present application also provides an electronic device 1100, including a processor 1110 and a memory 1120. The memory 1120 stores programs or instructions that can be run on the processor 1110. For example, when the electronic device 1100 is a terminal, when the program or instruction is executed by the processor 1110, each process of the above access request processing method embodiment is implemented, and the same technical effect can be achieved. To avoid repetition, they will not be repeated here.

Embodiments of the present application also provide a readable storage medium. Programs or instructions are stored on the readable storage medium. When the program or instructions are executed by a processor, each process of the above access request processing method embodiment is implemented, and can achieve The same technical effects are not repeated here to avoid repetition.

Wherein, the processor is the processor in the electronic device described in the above embodiment. The readable storage media includes computer-readable storage media, such as computer read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disks or optical disks, etc.

An embodiment of the present application further provides a chip. The chip includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the above embodiment of the access request processing method. Each process can achieve the same technical effect. To avoid repetition, we will not go into details here.

Furthermore, embodiments of the present application also provide a computer program product. The computer program The product includes a processor, a memory, and a program or instruction stored on the memory and executable on the processor. When the program or instruction is executed by the processor, each process of the above access request processing method embodiment is implemented. , and can achieve the same technical effect, so to avoid repetition, they will not be described again here.

To sum up, the access request processing solution provided by the embodiment of this application comprehensively considers the performance of the backend system and the gateway to set the current limiting configuration. The current limiting configuration can be set for different gateways respectively, which improves the utilization of the backend system and also improves the efficiency of the backend system. The gateway's forwarding rate of access requests. In the scenario of cloud computing and computing power network, this solution can increase the friendliness of access. When the access exceeds the limit, it will not be directly rejected, or it will be directly forwarded to the back-end service after waiting for a certain period of time, but will enter the waiting queue. When the API When the gateway determines that access can continue, it obtains the request from the waiting queue and continues the access process, and the API gateway can also feed back data as information for system optimization, which increases the robustness and self-optimization of the system and avoids system downtime.

It should be noted that, in this document, the terms "comprising", "comprises" or any other variations thereof are intended to cover a non-exclusive inclusion, such that a process, method, article or device that includes a series of elements not only includes those elements, It also includes other elements not expressly listed or inherent in the process, method, article or apparatus. Without further limitation, an element defined by the statement "comprises a..." does not exclude the presence of additional identical elements in a process, method, article or apparatus that includes that element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited. Functions are performed in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in a reverse order according to the functions involved. To perform the functions, for example, the methods described may be performed in an order different from that described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus the necessary general hardware platform. Of course, it can also be implemented by hardware, but in many cases the former is better. implementation. Based on this understanding, the technical solution of the present application can be embodied in the form of a computer software product that is essentially or contributes to the existing technology. The computer software product is stored in a storage medium (such as ROM/RAM, disk , optical disk), including several instructions to cause a terminal (which can be a mobile phone, computer, server, or network device, etc.) to execute the methods described in various embodiments of this application.

The embodiments of the present application have been described above in conjunction with the accompanying drawings, but the present application is not limited to the above. The above-described specific implementations are only illustrative and not restrictive. Those of ordinary skill in the art, inspired by this application, can make any modifications without departing from the purpose of this application and the scope protected by the claims. It can also be made in many forms, all of which fall within the protection of this application.

Claims

An access request processing method, including:

Apply for forwarding tokens based on received access requests;

In response to the non-zero number of forwarding tokens in the token pool, the access request carrying the forwarding token information is forwarded to the backend system, wherein the token pool has a preset number of forwarding tokens, and the preset number Determined based on background system performance and current gateway performance;

The number of forwarding tokens in the token pool is updated according to the access request carrying the forwarding token information and the received response information carrying the forwarding token information.
The method of claim 1, further comprising:

In response to the number of forwarding tokens in the token pool being zero, the access request is sent to a waiting queue.
The method of claim 2, wherein in response to the number of forwarding tokens in the token pool being zero, the method further includes:

A notification process is triggered, and the notification process is used to notify the access request in the waiting queue to apply for the forwarding token when the number of forwarding tokens in the token pool is non-zero.
The method according to claim 1, wherein before applying for a forwarding token according to the received access request, the method further includes:

In response to the gateway cluster including multiple gateways, a token pool with a different preset number of forwarding tokens is set for each gateway according to the background system performance and the performance of each gateway.
The method according to claim 1, wherein the number of forwarding tokens in the token pool is updated according to the access request carrying the forwarding token information and the received response information carrying the forwarding token information. include:

According to the access request carrying forwarding token information, reduce the number of forwarding tokens in the token pool by one;

According to the received response information carrying the forwarding token information, the number of forwarding tokens in the token pool is increased by one.
An access request processing device, including:

A token application unit is used to apply for a forwarding token based on the received access request;

a forwarding unit, configured to forward the access request carrying the forwarding token information to the backend system in response to the non-zero number of forwarding tokens in the token pool, wherein the token pool has a preset number of forwarding tokens, The preset number is determined based on background system performance and current gateway performance;

A token updating unit configured to update the number of forwarding tokens in the token pool according to the access request carrying the forwarding token information and the received response information carrying the forwarding token information.
The device of claim 6, further comprising:

A request waiting unit, configured to send the access request to the waiting queue in response to the number of forwarding tokens in the token pool being zero.
The device of claim 7, further comprising:

A notification process triggering unit is configured to trigger a notification process. The notification process is used to notify the access request in the waiting queue to apply for the forwarding token when the number of forwarding tokens in the token pool is non-zero.
The device of claim 6, further comprising:

A token pool setting unit is configured to, in response to the gateway cluster including multiple gateways, set a token pool with different preset numbers of forwarding tokens for each gateway according to the performance of the background system and the performance of each gateway.
The device according to claim 6, wherein the token update unit is used for:

According to the access request carrying forwarding token information, reduce the number of forwarding tokens in the token pool by one;

According to the received response information carrying the forwarding token information, the number of forwarding tokens in the token pool is increased by one.
An access request processing system, the system includes: the access request processing device according to any one of claims 6 to 10, a backend system and a gateway set including at least one gateway group, wherein the access request processing device is located at the gateway cluster end.
An electronic device, including a processor and a memory. The memory stores programs or instructions that can be run on the processor. When the program or instructions are executed by the processor, the implementation of any one of claims 1-5 is achieved. The steps of the access request processing method.
A readable storage medium on which a program or instructions are stored. When the program or instructions are executed by a processor, the steps of the access request processing method according to any one of claims 1 to 5 are implemented.