CN115002033B

CN115002033B - Flow control method, device, equipment, storage medium and computer product

Info

Publication number: CN115002033B
Application number: CN202210579777.2A
Authority: CN
Inventors: 刘永昆
Original assignee: CCB Finetech Co Ltd
Current assignee: CCB Finetech Co Ltd
Priority date: 2022-05-25
Filing date: 2022-05-25
Publication date: 2023-06-20
Anticipated expiration: 2042-05-25
Also published as: CN115002033A

Abstract

The invention discloses a flow control method, a flow control device, flow control equipment, a storage medium and a computer product, and relates to the technical field of cloud computing. The method comprises the following steps: determining user information, service level and grouping information corresponding to a service request sent by a client; determining identification information according to the user information, the service level and the grouping information, and identifying the service request according to the identification information; and acquiring a network flow control level, and executing a corresponding network flow control strategy on the service request according to the network flow control level and the identification information. The technical scheme of the invention can solve the problem of indiscriminate request rejection of the network flow control mode based on a single operation index in the related technology by marking the service request and determining the network flow control level, achieves the effect of effectively controlling concurrency, and ensures the service processing capability of the system.

Description

Flow control method, device, equipment, storage medium and computer product

Technical Field

The embodiment of the invention relates to the technical field of cloud computing, in particular to a flow control method, a flow control device, flow control equipment, a storage medium and a computer product.

Background

With the maturation of cloud computing and internet of things, distributed computing is widely applied, particularly, the wide application of containerization technology, the concurrency of a system is continuously improved, and in a high concurrency scene, in order to effectively control the load of the system, the concurrency number control is considered at first.

In the related technology, the stability of system service is ensured through flow control, fusing degradation and system load protection, and when the concurrency number of requests exceeds a preset value, the calling of resources is limited through monitoring the running indexes such as QPS, a thread pool, system load and the like in real time, so that the requests fail rapidly, and indiscriminate refusal service is realized.

However, this indiscriminate denial of service greatly reduces user experience, and may cause repeated clicking and retrying by the user, aggravating network resource occupation, and thus affecting the service processing capability of the system. In addition, a single service or a single page application may make multiple service requests, such as bank transfer service, including a series of operations of acquiring account information, payee record, security verification, and the like. If a request is denied, the entire transfer service may not be performed, and the user may be caused to click and retry repeatedly. Therefore, how to ensure the service processing capability of the system on the basis of effectively controlling concurrency is a problem to be solved urgently at present.

Disclosure of Invention

The embodiment of the invention provides a flow control method, a flow control device, flow control equipment, flow control system and a flow control storage medium, which are used for guaranteeing the service processing capacity of a system on the basis of effectively controlling concurrency.

In a first aspect, an embodiment of the present invention provides a flow control method, including:

determining user information, service level and grouping information corresponding to a service request sent by a client;

determining identification information according to the user information, the service level and the grouping information, and identifying the service request according to the identification information;

and acquiring a network flow control level, and executing a corresponding network flow control strategy on the service request according to the network flow control level and the identification information.

In a second aspect, an embodiment of the present invention further provides a flow control device, including:

the information determining module is used for executing the user information, the service level and the grouping information corresponding to the service request sent by the client;

the request identification module is used for determining identification information according to the user information, the service level and the grouping information and identifying the service request according to the identification information;

and the network flow control module is used for executing and acquiring a network flow control level, and executing a corresponding network flow control strategy for the service request according to the network flow control level and the identification information.

In a third aspect, an embodiment of the present invention further provides an electronic device, including a memory, a processor, and a computer program stored in the memory and capable of running on the processor, where the processor implements the flow control method according to any one of the embodiments of the present invention when executing the program.

In a fourth aspect, embodiments of the present invention further provide a computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements a flow control method according to any of the embodiments of the present invention.

In a fifth aspect, embodiments of the present invention also provide a computer program product comprising a computer program which, when executed by a processor, implements a flow control method according to any of the embodiments of the present invention.

In the embodiment of the invention, the user information, the service level and the grouping information corresponding to the service request are determined, the identification information is determined based on the user information, the service level and the grouping information, the service request is identified according to the identification information, the network flow control level is acquired, the corresponding network flow control strategy is executed for the service request according to the network flow control level and the identification information, the network flow control mode of indiscriminate refusing the request based on the simple operation index in the related technology is solved through the identification of the service request and the determination of the network flow control level, the concurrency control effect is achieved, and the service processing capability of the system is ensured.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings that are needed in the embodiments will be briefly described below, it being understood that the following drawings only illustrate some embodiments of the present invention and therefore should not be considered as limiting the scope, and other related drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

FIG. 1 is a flow chart of a flow control method according to an embodiment of the present invention;

fig. 2 is a schematic diagram of a network flow control process in a flow control method according to an embodiment of the present invention;

fig. 3 is a schematic diagram of a network flow control queue management method in a network flow control queue according to an embodiment of the present invention;

fig. 4 is a schematic diagram of implementing network flow control in a flow control method according to an embodiment of the present invention;

fig. 5 is a flowchart of a network flow control method provided by an embodiment of the present invention for a case that service capability of a service end is relatively stable;

FIG. 6 is a block diagram of a flow control device according to an embodiment of the present invention;

fig. 7 is a schematic diagram of a server device according to an embodiment of the present invention;

Fig. 8 is a block diagram of an electronic device according to an embodiment of the present invention.

Detailed Description

The invention is described in further detail below with reference to the drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting thereof. It should be further noted that, for convenience of description, only some, but not all of the structures related to the present invention are shown in the drawings.

It should be noted that: like reference numerals and letters denote like items in the following figures, and thus once an item is defined in one figure, no further definition or explanation thereof is necessary in the following figures. Meanwhile, in the description of the present invention, the terms "first", "second", and the like are used only to distinguish the description, and are not to be construed as indicating or implying relative importance. The data acquisition, storage, use, processing and the like in the technical scheme meet the relevant regulations of national laws and regulations.

Fig. 1 is a flow chart of a flow control method according to an embodiment of the present invention, where the method may be applied to a flow control scenario of a service request, and the method may be performed by a flow control device, where the flow control device may be implemented in a form of hardware and/or software, and the flow control may be configured in an electronic device. As shown in fig. 1, the method includes:

S110, user information, service level and grouping information corresponding to the service request sent by the client are determined.

The client is one or more application clients or Web clients for sending service requests to the server. The service request is one or more access requests initiated by the client. The server is used for executing flow control. Specifically, the server may implement flow control based on a server or a server cluster.

The service request is a request to implement a service function. For example, the service request includes an account information acquisition request, a payee record acquisition request, a security verification request, and the like included in the bank transfer service. A service request may include one sub-request or multiple sub-requests that are executed sequentially. The user information is login user information corresponding to the service request. Specifically, the request header of the service request can be analyzed to obtain the token information, and the corresponding server login user information can be further obtained according to the token information. The service level may be a priority defined in advance by the system for the service request. The packet information is a service packet to which each sub-request determined according to the service request belongs. For example, the account information acquisition request, the payee record acquisition request, and the security verification request may be determined to belong to one service group, that is, the service group is a bank transfer service. Specifically, the packet information and the corresponding service level may be identified by parsing the URL of the service request.

The service end obtains a service request sent by the client end, and analyzes the service request to obtain a request header. The token information in the service request is acquired, and may specifically be the token information in the request header. The user information corresponding to the service request is determined according to the token information, and specifically, login user information in the token information can be obtained and used as the user information corresponding to the service request. And acquiring a resource locator URL in the service request, and determining a service interface path according to the URL. The service interface path is determined according to the URL, and specifically may be the service interface path in the URL. And determining the service level and the grouping information corresponding to the service request based on the service interface path query configuration information. The configuration information comprises the corresponding relation between the service interface paths and the service level and the grouping information respectively. Specifically, the configuration information includes a correspondence between a service interface path and a service level, and also includes a correspondence between a service interface path and packet information.

S120, determining identification information according to the user information, the service level and the grouping information, and identifying the service request according to the identification information.

The identification information is used for identifying the priority of the service request, and the service request enters the network flow control queues with different priorities according to the priority. Specifically, the network traffic control queues include high priority network traffic control sub-queues having different priorities, medium priority network traffic control sub-queues and low priority network traffic control sub-queues. The priority of the service requests in the high priority network flow control sub-queues is highest, the priority of the service requests in the medium priority network flow control sub-queues is lower, and the priority of the service requests in the low priority network flow control sub-queues is lowest. The dequeuing order of service requests in the network traffic control sub-queues of different priorities is different. The network flow control queue is a buffer unit for service requests and is managed according to priority. In the application, the network flow control queue for managing the service request by the server is realized through the cache management unit.

Specifically, determining the identification information according to the user information, the service level, and the grouping information includes: determining request frequency according to the user information; determining request priority according to the request frequency, the service level and the grouping information; and determining the identification information according to the request frequency and the request priority.

For example, statistics is performed on service requests of different users according to user information, and request frequency of service requests of each user is determined.

The method comprises the steps of respectively determining the reference priority of the service request according to the request frequency, the service level and the grouping information, and specifically comprises the following steps: and determining a first reference priority of the service request based on the corresponding relation between the request frequency and the preset priority interval. It should be noted that, a request frequency threshold is set in advance according to an actual service request, and different priority intervals are determined according to the request frequency threshold.

And determining service requests belonging to the same packet according to the packet information. For the service request in the same packet, the first request determines the second reference priority as the medium priority, and the second reference priority as the high priority when the request is repeated. Taking a bank transfer service as an example, the bank transfer service comprises an account information acquisition request, a payee record acquisition request and a security verification request, if the first request is the account information acquisition request, the second reference priority of the account information acquisition request is a medium priority, the payee record acquisition request is received again, the second reference priority of the payee record acquisition request is determined to be a high priority, if the security verification request is received, the third request of the bank transfer service is received, and the second reference priority of the security verification request is determined to be a high priority.

The service level corresponds to a third reference priority defined in advance by the system for the service request. And determining the highest priority reference priority among the first reference priority, the second reference priority and the third reference priority as the request priority of the service request.

For example, the determining identification information according to the request priority may be that the identification information of the service request with the highest request priority is 1, the identification information of the service request with the highest request priority is 0, the identification information of the service request with the lowest request priority is-1, and the identification information is added to the request header of the service request.

S130, acquiring a network flow control level, and executing a corresponding network flow control strategy for the service request according to the network flow control level and the identification information.

The server determines the network flow control level by the ratio of the number of requests received in unit time to the maximum concurrency number acceptable by the server.

Through the application of the containerization technology, the service end has self-adaptive capability, and under the condition of high concurrency, the service capability of the service end can be kept relatively stable through automatic starting and stopping of the container. The relatively stable service capability means that the service end can process the service in a unit time. In the related art, the processing capacity of the server can be kept relatively stable by a distributed technology in combination with the automatic start and stop modes of the container.

The maximum concurrency number acceptable by the server is a stable value, and the maximum concurrency number can be obtained by verification. Under the condition that the maximum concurrency number acceptable by the server is relatively stable, the larger the number of received requests in a specific unit time is, the larger the concurrency number is, and the higher the corresponding network flow control level is. The server does not need to calculate the network flow control level for each service request, and after receiving the service request, the server only needs to directly acquire the network flow control level from the system, and the server calculates the network flow control level at regular time and updates the network flow control level circularly. Specifically, the network traffic control level includes global network traffic control and non-global network traffic control. Wherein the non-global network flow control further comprises hierarchical network flow control and non-hierarchical network flow control. For non-hierarchical network flow control, the method can also be called free circulation, and service requests can be forwarded freely without flow control. The global network flow control is a processing mode that the server executes network flow control on all service requests. The hierarchical network flow control is a processing mode that a server executes forwarding on protection requests in all service requests and executes network flow control on non-protection requests. The non-hierarchical network flow control is a processing mode that a server executes forwarding on all service requests.

The network flow control policy is a response policy to the service request. The method specifically comprises the following steps: if the network traffic control is global network traffic control, adding the service request into a network traffic control queue; and if the network flow control is hierarchical, forwarding the protection request in the service request to a request proxy unit, and adding the non-protection request into a network flow control queue. And if the network flow control is non-hierarchical network flow control, forwarding the service request to the request proxy unit. The request proxy unit is a server component and is used for forwarding the service request to the service application through the proxy by the server.

Specifically, when a service request sent by a client is received, acquiring a network flow control level; if the network flow control level is global network flow control, adding the service request into a network flow control queue based on the request priority, sequentially forwarding the service request to a request proxy unit according to the request priority through the network flow control queue, and forwarding the service request to a service application through the request proxy unit; if the network flow control level is hierarchical network flow control, adding non-protection requests in the service requests into a network flow control queue, forwarding protection requests in the service requests to a request proxy unit, and forwarding the service requests to service applications through the request proxy unit; if the network flow control level is non-hierarchical network flow control, the service request is forwarded to the request agent unit, and the service request is forwarded to the service application through the request agent unit.

Specifically, forwarding the service request to the service application by the request broker unit includes: the service end forwards the service request to the service application through the URL in the service request.

According to the technical scheme of the embodiment of the invention, through determining the user information, the service level and the grouping information corresponding to the service request, determining the identification information based on the user information, the service level and the grouping information, identifying the service request according to the identification information, acquiring the network flow control level, and executing the corresponding network flow control strategy for the service request according to the network flow control level and the identification information, the network flow control mode of indiscriminate rejection of the related technology based on the single operation index is solved through identifying the service request and determining the network flow control level, the concurrency of effective control is achieved, and the service processing capability of the system is ensured.

Fig. 2 is a schematic diagram of a network flow control process in a flow control method according to an embodiment of the present invention. As shown in fig. 2, executing the corresponding network traffic control policy on the service request according to the network traffic control level and the identification information includes:

s201, when receiving a service request sent by a client, acquiring a network flow control level.

S202, judging whether the network flow control level is global network flow control, if so, executing S203, otherwise, executing S204.

S203, the service request is added into a network flow control queue based on the request priority, the service request is sequentially forwarded to the request agent unit through the network flow control queue according to the request priority, and the service request is forwarded to the service application through the request agent unit.

Specifically, service requests are added into a network flow control sub-queue with corresponding priority in a network flow control queue based on request priority, wherein the network flow control queue comprises a plurality of network flow control sub-queues with different priorities. The network flow control queues comprise a high-priority network flow control sub-queue, a medium-priority network flow control sub-queue and a low-priority network flow control sub-queue, and service requests with different priorities enter the network flow control sub-queues with different priorities. For example, high priority service requests enter a high priority network traffic control sub-queue. The medium priority service request enters a medium priority network flow control sub-queue. The low priority service request enters a low priority network traffic control sub-queue. And then, the service requests in the network flow control queue are dequeued in sequence according to the request priority and forwarded to the request proxy unit, and the service requests are forwarded to the service application through the request proxy unit. Fig. 3 is a schematic diagram of a network flow control queue management method in a network flow control queue according to an embodiment of the present invention. As shown in fig. 3, the service requests in the high priority network traffic control sub-queues are dequeued preferentially, followed by the service requests in the medium priority queues, and finally followed by the service requests in the low priority queues. I.e., service requests in the medium priority request queue begin dequeuing after service requests in the high priority network flow control sub-queue are dequeued. The dequeuing of service requests in the low priority network flow control sub-queues is initiated after the dequeuing of service requests in the medium priority network flow control sub-queues is completed.

S204, if the network flow control level is non-global network flow control, judging whether the network flow control level is hierarchical network flow control, if so, executing S205, otherwise, executing S211.

S205, judging whether the service level of the service request meets the service classification requirement, if so, executing S206, otherwise, executing S207.

S206, determining the service request as a protection request.

S207, judging whether the service request is the first request in the belonging grouping requests, if so, executing S208, otherwise, executing S206, wherein the grouping requests comprise a plurality of service requests with the same service category.

S208, judging whether the request frequency exceeds a set threshold, if so, executing S206, otherwise, executing S209.

S209, determining that the service request is a non-protection request.

S210, adding the unprotected request in the service request into a network flow control queue, forwarding the protected request in the service request to a request proxy unit, and forwarding the service request to a service application through the request proxy unit.

S211, forwarding the service request to a request proxy unit, and forwarding the service request to the service application through the request proxy unit.

According to the technical scheme, the flow control is performed on the service request through the combination of the network flow control level and the identification information, the concurrent control is effectively performed under the condition that the service capacity of the service end is relatively stable in a mode of grading, sequencing, frequency control and request caching, and the service processing capacity of the service end is guaranteed.

In an alternative embodiment, before forwarding the service request to the request broker unit in sequence according to the request priority via the network traffic control queue, the method further comprises:

judging whether the service request to be dequeued is overtime;

if yes, returning request timeout information;

otherwise, the service request to be dequeued is forwarded to the request proxy unit.

It should be noted that, when the service request is dequeued, the system response time of the server may be exceeded. In practical applications, the system response time should be lower than the time-out time of the pre-load device, firewall, gateway. After dequeuing, the aggregate service application processing time may exceed the dequeuing timeout time of the service request, and thus the dequeuing timeout time is comprehensively considered in combination with the factors of the system response time, the application processing time and the like. After receiving the service request, the request proxy unit forwards the request to the service application through the proxy.

In an alternative embodiment, when the network traffic control level update condition is satisfied, determining a network traffic control level according to a comparison result of the server load rate and the network traffic control level threshold, wherein the network traffic control level threshold includes a global network traffic control threshold and a hierarchical network traffic control threshold. Specifically, when the load rate of the server side does not reach the hierarchical network flow control threshold, determining that the network flow control level is non-hierarchical network flow control; when the server side reaches that the hierarchical network flow control threshold is smaller than the global network flow control threshold, determining that the network flow control level is hierarchical network flow control; and when the server side reaches the global network flow control threshold, determining the network flow control level as global network flow control.

The server receives one or more service requests from the client, and the number of the service requests may be denoted as n. The server takes the request number n as input, and calculates the load of the server by combining the maximum concurrency number which can be processed. And calculating the load rate according to the ratio of the number of requests to the maximum concurrency number in unit time. Assuming that the ratio of the number of requests in unit time to the maximum concurrency number is 50%, the current concurrency of the server is 1/2 of the maximum processing capacity of the server.

The server sets a two-level network flow control level threshold, namely a global network flow control threshold and a hierarchical network flow control threshold, as network flow control conditions for implementing hierarchical network flow control and global network flow control, respectively. Fig. 4 is a schematic diagram of implementing network flow control in a flow control method according to an embodiment of the present invention. As shown in fig. 4, when the service side load rate is low and the hierarchical network flow control condition is not reached, the non-hierarchical network flow control is implemented, and the free circulation is implemented for any of the n service requests. When the service side load rate rises and reaches the hierarchical network flow control condition but does not reach the global network flow control condition, implementing hierarchical network flow control for any request in the n requests. Further, the high priority request is determined as a protection request, which is forwarded to the request broker unit. Accordingly, the low-medium priority request is determined to be a non-protection request, and the non-protection request enters a network flow control queue to implement flow control on the non-protection request. Further, when the load rate of the server side rises suddenly and reaches the global network flow control condition, global network flow control is implemented for any request in the n service requests, and the service requests are added into a network flow control queue based on the request priority. Optionally, when the number of service requests decreases, according to the network flow control condition corresponding to the load rate of the server, the service request newly sent by the client is applicable to the network flow control level corresponding to the load rate.

Fig. 5 is a flowchart of a network flow control method for a service end in a case where service capability of the service end is relatively stable. As shown in fig. 5, the method includes:

s501, the service end receives the service request of the client end and identifies the service request.

In the embodiment of the invention, the service end marks the service request, specifically adds the mark information in the request head of the service request. Specifically, the token information is obtained from the request header, and the login user information of the corresponding server is further determined according to the token information. Packet information and corresponding service levels are identified by the service request URL. Further, according to the login user information, the request frequency is obtained, the request priority of the service request is judged by combining the grouping information, the service level and the request frequency, and the request priority is added in the request head to be used as a request identification.

The request information of the service request comprises URL information, request header information and request content. In this embodiment, two types of information, namely user information and packet information, are mainly acquired, and the acquisition modes are as follows:

in practical application, the request header information includes Token (Token) information, and user information can be further obtained through login information corresponding to the Token information. And identifying the grouping information by intercepting the URL information and the corresponding grouping information of the service end. In the transfer service, the acquisition of the transfer account information and the transfer request, the acquisition of the receiver information and the transfer security verification should be regarded as the same group.

Alternatively, two types of information may be appended to the request header, including request frequency and request priority per unit time. Wherein the request frequency is the number of times of request sent by the user in unit time. It should be noted that, for malicious frequent requests or crawlers, the identification by a tool such as a firewall does not fall into the scope of the discussion of the present embodiment. Further, request priority is determined based on the preset traffic level and the packet information.

S502, acquiring a network flow control level, and determining the outlet condition of the service request according to the network flow control level.

The server determines the network flow control level by the ratio of the number of requests received in unit time to the maximum concurrency number acceptable by the server. The server calculates the control level of the network flow at regular time and updates the control level circularly. The server does not need to calculate a network traffic control level for each service request. After receiving the service request, the service request only needs to be directly acquired from the system.

The server determines a network flow control level to be implemented for the service request. When the current network flow control level of the server is global network flow control, directly adding the service request into a network flow control queue, and further carrying out hierarchical management on the queue to determine corresponding dequeue conditions. When the current network flow control level of the server is hierarchical network flow control, protecting the service request with high priority, and directly forwarding the protected service request (i.e. protection request) to a request proxy unit; and the low-priority service requests enter a network flow control queue according to the request frequency to carry out network flow control. When the current network flow control level of the server is non-hierarchical network flow control, the service request is directly forwarded to the request proxy unit after the service request is received.

In one embodiment, when a service request from a client reaches or exceeds the maximum processing capacity of the system, all requests from the client enter network traffic control sub-queues of different priorities according to priority due to the use of global network traffic control. In one case, low priority service requests may fail due to time-out, but for global applications, the service processing capacity per unit time is not affected by the increase in requests, but remains at a relatively stable level.

It should be noted that, the server may determine the network flow control level at regular time according to the number of service requests sent by the client. In the embodiment of the invention, the network flow control level is the outlet condition of the service request, and the server determines the network flow control level of the service request according to the concurrency number and the maximum concurrency number of the stable operation of the system. Specifically, the network flow control level is determined by the ratio of the number of requests (i.e., the number of concurrency) received in a unit time to the maximum number of concurrency acceptable by the server. The number of requests is the number of requests in a unit time, and the number of requests can be further counted through an algorithm of a fixed time window or a sliding time window.

Specifically, the client may send the service request to the server one or more times. In the embodiment of the invention, the service request is any request from the client, but does not contain illegal requests. After receiving the service request, the server acquires the current network flow control level and judges whether the network flow control level is global network flow control. Wherein global network traffic control, i.e. all requests require network traffic control, including high priority requests, medium priority requests and low priority requests.

And adding the service request into a network flow control queue if the network flow control level is global network flow control. Further, the network flow control queues include three network flow control sub-queues, namely a high network flow control sub-queue, a medium network flow control sub-queue and a low network flow control sub-queue, and the network flow control sub-queues are determined to be added according to the identification information of the service request.

If the network flow control level is non-global network flow control, further judging whether the current network flow control level is hierarchical network flow control. Hierarchical network flow control, i.e. forwarding high priority requests as protection requests in real time. And further, the requests with medium and low priorities are added into a network flow control queue, so that the concurrency of the system is prevented from being instantaneously improved, and the service processing capacity of the system is prevented from being influenced. For hierarchical network flow control, it is necessary to further determine whether the request is a protection request. If the request is a protection request, the service request is directly forwarded to the request proxy unit. If the request is not protected, the service request is further added into a network flow control queue.

The protection request is a high-priority service request and is determined through the request identification. Optionally, after identifying the user information, the request frequency of the user is determined. A request with a preset value at the request frequency may be regarded as a medium priority request. Alternatively, a service request belonging to the same packet is denoted as a packet request, and a packet request sent by a user for the first time may be regarded as medium-priority or low-priority, but for maintaining the integrity of the service, a second or multiple requests of the same packet sent subsequently will be regarded as high-priority requests. If the control is non-hierarchical network flow control, the request is freely forwarded, and the service request is further forwarded to the request proxy unit. The free forwarding indicates that the concurrency of the server side does not reach the hierarchical network flow control level, and all requests do not need to be subjected to network flow control and are subjected to free forwarding.

In the embodiment of the invention, the network flow control queue is a request cache unit, is managed according to the request priority, and is dequeued in sequence. For example, service requests in a high priority queue are dequeued first, followed by service requests in a medium priority queue, and finally, service requests in a low priority queue. In the global network flow control state, even if the concurrency is multiplied, the processing capacity of the server is not reduced due to the increase of the number of requests.

Further, dequeuing the service request, further judging whether the service request is overtime, and if so, returning overtime requesting information to the client. If not, forwarding to the requesting agent unit further. After receiving the request, the request proxy unit further forwards the service request to the service application through the proxy.

Through the above flow, a complete flow from identification, flow control to exit forwarding of a service request is completed. Similarly, the server side can implement the flow control according to each specific request in the face of multiple concurrent requests.

In the embodiment of the invention, if the network flow control level is hierarchical network flow control, the protection request needs to be further identified. The service request determined as the protection request is directly forwarded to the request proxy unit, and the network flow control is implemented on the service request determined as the non-protection request, so as to prevent the request from further rising to influence the service processing capacity of the server.

When a service request sent by a client is received, the server performs identification, and further determines that the network flow control level is hierarchical network flow control, and then starts judgment of a protection request.

Specifically, the service level is determined according to the URL of the service request. And judging whether the service level meets the service classification requirement. Wherein, the service is classified into a high priority service request defined by the service end. And if the service level meets the service classification requirement, determining the corresponding service request as a protection request. If the service level does not meet the service grouping requirement, further judging whether the service request meets the grouping requirement. Wherein a packet is required to be of higher priority for a certain packet request, the first request having a higher priority, and the next second or more requests. For example, it is determined that a first request has a medium priority and a subsequent second or more requests have a high priority. If the service request meets the grouping requirement, the service request is determined to be a protection request, and if the service request does not meet the grouping requirement, whether the service request meets the request frequency requirement is further judged. The request frequency is the request frequency in the unit time of the user. The server takes the fixed frequency as a preset value, and determines that the service request meets the request frequency requirement if the frequency of the service request reaches the preset value. In an implementation application, such as data entry, frequent data storage is required. If the service request meets the frequency requirement, the service request is determined to be a protection request, and if the service request does not meet the frequency requirement, the service request is determined to be a non-protection request.

In the embodiment of the invention, the network flow control queue is used for caching the service requests and dequeuing the service requests according to the priority of the queue, and the service requests in the same queue follow the first-in first-out principle. Specifically, the network traffic control queues are further divided into a high priority network traffic control sub-queue, a medium priority network traffic control sub-queue and a low priority network traffic control sub-queue according to request priorities.

Specifically, when the server determines that the network flow control level is global network flow control, the request priority is determined according to the identification information in the service request for all the service requests. It is determined that service requests satisfying the service classification requirement, secondary or multiple packet requests, have a high priority. The first packet requests, the service requests meeting the frequency requirements, have medium priority, and the other service requests have low priority.

Optionally, corresponding rules, such as service levels, are formulated according to their own service properties to further determine request priorities.

And after the priority identification is finished, further adding the service request into a corresponding network flow control queue. The high priority service requests enter a high priority network flow control sub-queue. The medium priority service request enters a medium priority network flow control sub-queue. The low priority service request enters a low priority network flow control sub-queue. When dequeuing, the service requests in the high priority comparison are dequeued first, then the service requests in the medium priority, and finally the service requests in the low priority.

When the network flow control level of the server is hierarchical network flow control, the direct forwarding of the protection request is further identified, the service request with low priority is determined as the partial protection request, and the service request directly enters the low-priority network flow control sub-queue.

When the network flow control level of the server is non-hierarchical network flow control, all requests are directly forwarded to the request proxy unit without enqueuing.

Fig. 6 is a block diagram of a flow control device according to an embodiment of the present invention. The flow control device may be implemented in hardware and/or software, and may be configured in an electronic device. As shown in fig. 6, the apparatus includes: an information determination module 610, a request identification module 620, and a network flow control module 630.

An information determining module 610, configured to perform determining user information, service level, and packet information corresponding to a service request sent by a client;

a request identification module 620, configured to determine identification information according to the user information, the service level, and the packet information, and identify the service request according to the identification information;

the network flow control module 630 is configured to perform obtaining a network flow control level, and perform a corresponding network flow control policy on the service request according to the network flow control level and the identification information.

Further, the information determining module 610 is specifically configured to:

obtaining token information in the service request, and determining user information corresponding to the service request according to the token information;

acquiring a resource locator (URL) in the service request, and determining a service interface path according to the URL;

and inquiring setting configuration information based on the service interface path, and determining the service level and grouping information corresponding to the service request, wherein the setting configuration information comprises the corresponding relation between the service interface path and the service level and grouping information respectively.

Further, the request identification module 620 is specifically configured to:

determining request frequency according to the user information;

determining request priority according to the request frequency, the service level and the grouping information;

and determining the identification information according to the request priority.

Further, the request identification module 620 is specifically further configured to:

and respectively determining the reference priority of the service request according to the request frequency, the service level and the grouping information, and determining the reference priority with the highest priority as the request priority of the service request.

And adding the identification information to a request header of the service request.

Optionally, the network flow control module 630 is specifically configured to:

when a service request sent by a client is received, acquiring a network flow control level;

if the network flow control level is global network flow control, adding the service request into a network flow control queue based on the request priority, sequentially forwarding the service request to a request proxy unit according to the request priority through the network flow control queue, and forwarding the service request to a service application through the request proxy unit;

if the network flow control level is hierarchical network flow control, adding a non-protection request in the service request into a network flow control queue, forwarding a protection request in the service request to the request proxy unit, and forwarding the service request to the service application through the request proxy unit;

and if the network flow control level is non-hierarchical network flow control, forwarding the service request to the request proxy unit, and forwarding the service request to the service application through the request proxy unit.

Further, the network flow control module 630 is further configured to:

when the network flow control level is hierarchical network flow control, judging whether the service level of the service request meets the service classification requirement;

if yes, determining the service request as a protection request;

otherwise, judging whether the service request is the first request in the group request, wherein the group request comprises a plurality of service requests with the same service category;

if the service request is not the first request in the group request, determining that the service request is a protection request;

if the service request is the first request in the group request, judging whether the request frequency exceeds a set threshold value;

if the request frequency exceeds the set threshold, determining that the service request is a protection request;

and if the request frequency does not exceed the set threshold value, determining that the service request is a non-protection request.

Further, the network flow control module 630 is specifically further configured to:

before forwarding service requests to a request proxy unit in turn according to request priority through the network flow control queue, judging whether the service requests to be dequeued are overtime;

If yes, returning request timeout information;

otherwise, the service request to be dequeued is forwarded to a request proxy unit.

and adding the service request into a network flow control sub-queue with corresponding priority in the network flow control queue based on the request priority, wherein the network flow control queue comprises a plurality of network flow control sub-queues with different priorities.

Further, the network traffic control queues include a high priority network traffic control sub-queue, a medium priority network traffic control sub-queue, and a low priority network traffic control sub-queue.

Further, the method further comprises the following steps:

and the updating module is used for determining the network flow control level according to the comparison result of the server load rate and the network flow control level threshold when the network flow control level updating condition is met, wherein the network flow control level threshold comprises a global network flow control threshold and a hierarchical network flow control threshold.

Further, the updating module is specifically configured to:

when the service end load rate does not reach the hierarchical network flow control threshold, determining that the network flow control level is non-hierarchical network flow control;

When the server side reaches that the hierarchical network flow control threshold is smaller than the global network flow control threshold, determining that the network flow control level is hierarchical network flow control;

and when the server side reaches the global network flow control threshold, determining the network flow control level as global network flow control.

In one embodiment, a server device is provided. Fig. 7 is a schematic diagram of a server device for controlling network traffic according to an embodiment of the present invention. As shown in fig. 7, the server device includes: a request management unit 710, a network traffic control level management unit 720, a network traffic control processing unit 730, a request agent unit 740, and a cache management unit 750.

The request management unit 710 is configured to identify and identify a client request by a server. The method for implementing network flow control in the embodiment of the application comprises the following steps at a server: after the client sends the request to the server, the server identifies the request header information and further obtains the user information. Further, the service side obtains the service level and the grouping information through the URL. Further, the request frequency is identified based on the user information, and the request priority is further determined based on the service level and the grouping information. The request identification adds the request frequency and request priority to the request header.

The network flow control level management unit 720 is configured to manage a server network flow control level, so as to perform the following steps: detecting the request quantity in unit time to obtain the concurrency of the system; determining a new network flow control level according to the concurrency; updating the global network flow control level.

Optionally, the system concurrency is calculated by determining the number of system concurrency by Query Per Second (QPS), number of Transactions Per Second (TPS), in combination with the maximum number of concurrency that the system can withstand.

The network flow control processing unit 730 is configured to perform a network flow control process by the server, and direct the request from the client to the corresponding outlet. In the embodiment of the invention, in order to adapt to different load rates, after the network flow control level is determined, the network flow control processing unit executes the network flow control process, and different network flow control levels correspond to different execution network flow control paths. Further, corresponding network flow control processes are respectively executed for the three types of network flow control levels, and service requests are led to corresponding outlets. And the global network flow control adds all the requests into queues with different priorities, and further dequeues in turn according to the priorities of the queues, thereby realizing the network flow control. On the other hand, hierarchical network flow control releases protection requests, and network flow control is carried out on non-protection requests, and in addition, all service requests are released directly aiming at non-hierarchical network flow control, namely free circulation.

In some embodiments, the network flow control processing unit 730 may further include a flow processing module and a rule engine module to implement dynamic priority management to meet more flexible flow control requirements.

The request proxy unit 740 is configured to forward the service request from the network flow control processing unit 730 to the service application through proxy. In this embodiment, after receiving the request, the request broker unit 740 further forwards the service request to the service application through the broker.

The buffer management unit 750 is configured to request buffer queue management by the server.

In this embodiment, the request cache queue includes: a high priority request queue, a medium priority queue, and a low priority queue; the buffer management unit 750 adds the service requests to the queue according to the request priority, and dequeues in turn according to the queue priority when dequeues.

The flow control device provided by the embodiment of the invention can execute the flow control method provided by any embodiment of the invention, and has the corresponding functional modules and beneficial effects of the execution method.

Fig. 8 is a block diagram of an electronic device according to an embodiment of the present invention. Electronic devices are intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The components shown herein, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant to limit implementations of the inventions described and/or claimed herein.

As shown in fig. 8, the electronic device 10 includes at least one processor 11, and a memory, such as a Read Only Memory (ROM) 12, a Random Access Memory (RAM) 13, etc., communicatively connected to the at least one processor 11, in which the memory stores a computer program executable by the at least one processor, and the processor 11 may 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 into the Random Access Memory (RAM) 13. In the RAM 13, various programs and data required for the operation of the electronic device 10 may also be stored. The processor 11, the ROM 12 and the RAM 13 are connected to each other via a bus 14. An input/output (I/O) interface 15 is also connected to bus 14.

Various 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, and the like; a storage unit 18 such as a magnetic disk, an optical disk, or the like; and a communication unit 19 such as a network card, modem, wireless communication transceiver, etc. The communication unit 19 allows the electronic device 10 to exchange information/data with other devices via a computer network, such as the internet, and/or various telecommunication networks.

The processor 11 may be a variety of general and/or special purpose processing components having processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various specialized Artificial Intelligence (AI) computing chips, various processors running machine learning model algorithms, digital Signal Processors (DSPs), and any suitable processor, controller, microcontroller, etc. The processor 11 performs the various methods and processes described above, such as flow control methods.

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

A computer program for carrying out 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, special purpose computer, or other programmable data processing apparatus, such that the computer programs, when executed by the processor, cause the functions/acts specified in the flowchart and/or block diagram block or blocks to be implemented. The computer program may execute entirely on the machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.

In the context of the present invention, a computer-readable storage medium may be a tangible medium that can contain, or store a computer program for use by or in connection with an instruction execution system, apparatus, or device. The computer readable storage medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. Alternatively, the computer readable storage medium may be a machine readable signal medium. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, 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 disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

To provide for interaction with a user, the systems and techniques described here can 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 a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) through which a user can provide input to the electronic device. Other kinds of devices may also be used to provide for interaction with a user; for example, 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, speech input, or tactile input.

The systems and techniques described here can be implemented in a computing system that includes a background component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such background, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), wide Area Networks (WANs), blockchain networks, and the internet.

The computing system may include clients and servers. The client and server are typically remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The server can be a cloud server, also called a cloud computing server or a cloud host, and is a host product in a cloud computing service system, so that the defects of high management difficulty and weak service expansibility in the traditional physical hosts and VPS service are overcome.

Embodiments of the present invention also provide a computer program product comprising a computer program which, when executed by a processor, implements a flow control method as provided by any of the embodiments of the present application.

Computer program product in the implementation, the computer program code for carrying out operations of the present invention may be written in one or more programming languages, including an object oriented programming language such as Java, smalltalk, C ++ and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computer (for example, through the Internet using an Internet service provider).

Note that the above is only a preferred embodiment of the present invention and the technical principle applied. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, while the invention has been described in connection with the above embodiments, the invention is not limited to the embodiments, but may be embodied in many other equivalent forms without departing from the spirit or scope of the invention, which is set forth in the following claims.

Claims

1. A flow control method, comprising:

determining request priority according to the user information, the service level and the grouping information; determining identification information according to the request priority, and identifying the service request according to the identification information; acquiring a network flow control level, and executing a corresponding network flow control strategy on the service request according to the network flow control level and the identification information, wherein the method comprises the following steps:

when the network flow control level is hierarchical network flow control, the method further comprises:

judging whether the service level of the service request meets the service classification requirement or not;

if yes, determining the service request as a protection request;

2. The method of claim 1, wherein determining the user information, the service level, and the packet information corresponding to the service request sent by the client includes:

3. The method of claim 1, wherein said determining identification information based on said user information, traffic level, and packet information comprises:

determining request frequency according to the user information;

and determining the request priority according to the request frequency, the service level and the grouping information.

4. The method of claim 3, wherein said determining request priority based on said request frequency, traffic level, and packet information comprises:

5. A method according to claim 3, wherein said identifying said service request according to said identification information comprises:

6. The method of claim 3, wherein the obtaining the network traffic control level, and performing the corresponding network traffic control policy on the service request according to the network traffic control level and the identification information, comprises:

7. The method of claim 1, further comprising, prior to forwarding service requests to the requesting agent unit in sequence according to request priority via the network traffic control queue:

judging whether the service request to be dequeued is overtime;

if yes, returning request timeout information;

8. The method of claim 1, wherein said adding the service request to a network flow control queue based on the request priority comprises:

9. The method of claim 8, wherein the network traffic control queues include a high priority network traffic control sub-queue, a medium priority network traffic control sub-queue, and a low priority network traffic control sub-queue.

10. The method as recited in claim 1, further comprising:

and when the network flow control level updating condition is met, determining a network flow control level according to the comparison result of the server load rate and the network flow control level threshold, wherein the network flow control level threshold comprises a global network flow control threshold and a hierarchical network flow control threshold.

11. The method of claim 10, wherein the determining the network traffic control level according to the comparison of the server load rate and the network traffic control level threshold comprises:

12. A flow control device, comprising:

the request identification module is used for determining the request priority according to the user information, the service level and the grouping information; determining identification information according to the request priority, and identifying the service request according to the identification information;

The network flow control module is used for executing and acquiring a network flow control level, and executing a corresponding network flow control strategy for the service request according to the network flow control level and the identification information;

the network flow control module is specifically configured to:

the network flow control module is further configured to:

If yes, determining the service request as a protection request;

13. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable by the processor, wherein the processor implements the flow control method of any one of claims 1-11 when executing the computer program.

14. A computer readable storage medium, on which a computer program is stored, which computer program, when being executed by a processor, implements a flow control method according to any one of claims 1-11.