CN110535776A - Gateway current-limiting method, device, gateway, system and storage medium - Google Patents

Abstract

Embodiments of the present invention relate to the field of information technology, and disclose a gateway current limiting method, device, gateway, system and storage medium. Current-limiting plug-in startup list; wherein, the current-limiting plug-in startup list is used to indicate each current-limiting plug-in to be activated, and each of the current-limiting plug-ins corresponds to a current-limiting strategy; according to the updated current-limiting plug-in startup list , and run each current-limiting plug-in to be activated to limit the current. The gateway current limiting method, device, gateway, system and storage medium provided in the embodiments of the present invention can improve the efficiency of updating the gateway current limiting policy.

Description

Gateway current limiting method, device, gateway, system and storage medium

technical field

Embodiments of the present invention relate to the field of information technology, and in particular, to a gateway current limiting method, device, gateway, system, and storage medium.

Background technique

In order to ensure the stability of the network and the normal use of the database, it is necessary to implement network current limiting when the number of concurrent users is large. Currently, commonly used current limiting methods include token buckets, leaky buckets, and counters.

The inventor found that there are at least the following problems in the prior art: when the current limiting strategy needs to be changed, the traditional method needs to perform an offline test first, and after the offline test is successful, the current limiting strategy is changed after restarting when the system is idle. The update of the flow policy is not flexible enough and the efficiency is low.

SUMMARY OF THE INVENTION

The purpose of the embodiments of the present invention is to provide a gateway current limiting method, device, gateway, system and storage medium, so as to improve the update efficiency of the current limiting policy.

In order to solve the above-mentioned technical problems, embodiments of the present invention provide a gateway current limiting method, including: synchronously updating a locally set current limiting plug-in activation list to a current limiting plug-in activation list set in a database with a preset period; wherein , the current-limiting plugin startup list is used to indicate each current-limiting plugin to be activated, and each current-limiting plugin corresponds to a current-limiting strategy; according to the updated current-limiting plugin startup list, run each current-limiting plugin to be activated for current limiting.

Embodiments of the present invention also provide a gateway current limiting device, comprising: a startup list maintenance module, configured to synchronously update a locally set current limiting plug-in startup list to a current limiting plugin startup list set in a database at a preset period ; Among them, the current-limiting plug-in startup list is used to indicate each current-limiting plug-in that needs to be activated, and each current-limiting plug-in corresponds to a current-limiting strategy; the current-limiting module is used to run the Each current limiting plug-in performs current limiting.

Embodiments of the present invention also provide a gateway, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor. The processor executes, so that at least one processor can execute the above-mentioned gateway current limiting method.

Embodiments of the present invention further provide a gateway current limiting system, including: a database and N above-mentioned gateways communicatively connected to the database, where N is a natural number greater than zero.

Embodiments of the present invention further provide a computer-readable storage medium storing a computer program, and when the computer program is executed by a processor, the foregoing gateway current limiting method is implemented.

Compared with the prior art, the embodiments of the present invention provide a gateway current limiting method, by synchronously updating the current limiting plug-in activation list set locally to the current limiting plug-in activation list set in the database at a preset period; The updated current-limiting plug-in startup list, run each current-limiting plug-in that needs to be started to limit the current. Since each gateway node uses the same list of startup plugins for current limiting, the startup current limiting plugins of each node can always be consistent, and the current limiting plugins that need to be started are indicated by the current limiting plugin startup list. With high flexibility, the update and synchronization of the current limiting policy can be realized without restarting, thus improving the update efficiency of the current limiting policy.

In addition, the running each current-limiting plug-in to be activated to perform current-limiting according to the updated current-limiting plug-in start-up list specifically includes: if the current-limiting plug-in start-up list before the update is compared with the post-update If there is a missing current-limiting plug-in, obtain and start the missing current-limiting plug-in from the database; Stream plugin startup list, if there are redundant current limiting plugins, stop the running of the redundant current limiting plugins. Keep the current-limiting plug-in of the gateway server consistent with the current-limiting plug-in startup list in the database to update the current-limiting policy.

In addition, the current-limiting plug-in is uploaded to the database in the following manner: obtaining the current-limiting plug-in uploaded by the client, and the uploaded current-limiting plug-in includes a pre-defined plug-in startup method; Unique identification; upload the current limiting plug-in after the unique identification to the database. By uniquely identifying the uploaded current-limiting plug-in, even if the user uploads the current-limiting plug-in with the same name, the gateway server can distinguish it; uploading the uniquely identified current-limiting plug-in to the database, the database can also use the unique identification Distinguish each current-limiting plug-in to facilitate subsequent maintenance of the current-limiting plug-in.

In addition, the gateway current limiting method may further include: in response to a current limiting plug-in start command sent by the client, obtaining the name of the current limiting plug-in to be started indicated by the current limiting plug-in start command; if the current limiting plug-in start command indicates The current-limiting plug-in that needs to be started is the current-limiting plug-in stored in the database, then the name of the current-limiting plug-in that needs to be started indicated by the current-limiting plug-in start command is added to the current-limiting plug-in set in the database to start In the list; in response to the current-limiting plug-in stop command sent by the client, obtain the name of the current-limiting plug-in to be stopped indicated by the current-limiting plug-in stop command, and in the current-limiting plug-in startup list set in the database, delete The name of the current limiting plug-in to be stopped. By sending the start or stop command of the current limiting plug-in from the client, the corresponding current limiting policy can be flexibly implemented, which improves the update efficiency of the current limiting policy.

Description of drawings

1 is a schematic flowchart of a gateway current limiting method in a first embodiment of the present invention;

2 is an example diagram of uploading a current limiting plug-in to a database in the first embodiment of the present invention;

3 is a schematic flowchart of a gateway current limiting method in a second embodiment of the present invention;

4 is an exemplary diagram of downloading the missing current limiting plug-in in the second embodiment of the present invention;

5 is an exemplary diagram of loading the downloaded current limiting plug-in in the second embodiment of the present invention;

6 is an exemplary diagram of stopping the operation of redundant current limiting plug-ins in the second embodiment of the present invention;

7 is an exemplary diagram of starting the downloaded current limiting plug-in in the second embodiment of the present invention;

Fig. 8 is a specific example diagram of the gateway server in the second embodiment of the present invention;

9 is a schematic diagram of a structure of a gateway server in a second embodiment of the present invention;

10 is a schematic flowchart of a gateway current limiting method in a third embodiment of the present invention;

11 is a schematic block diagram of the gateway current limiting device in the fourth embodiment of the present invention;

FIG. 12 is a schematic structural diagram of a gateway in a fifth embodiment of the present invention.

Detailed ways

In order to make the objectives, technical solutions and advantages of the embodiments of the present invention clearer, the various embodiments of the present invention will be described in detail below with reference to the accompanying drawings. However, those of ordinary skill in the art can appreciate that, in the various embodiments of the present invention, many technical details are set forth in order for the reader to better understand the present application. However, even without these technical details and various changes and modifications based on the following embodiments, the technical solutions claimed in the present application can be realized. The following divisions of the various embodiments are for the convenience of description, and should not constitute any limitation on the specific implementation of the present invention, and the various embodiments may be combined with each other and referred to each other on the premise of not contradicting each other.

The first embodiment of the present invention relates to a gateway current limiting method. In this embodiment, the locally set current-limiting plug-in startup list is synchronously updated to the current-limiting plug-in startup list set in the database at a preset period; wherein, the current-limiting plug-in startup list is used to indicate each current-limiting plug-in to be activated. , each current-limiting plug-in corresponds to a current-limiting strategy; according to the updated current-limiting plug-in startup list, run each current-limiting plug-in that needs to be activated to limit the current. By updating the current limiting plugin startup list of the local gateway node to the current limiting plugin startup list in the database, and running each current limiting plugin according to the updated local current limiting plugin startup list, the current limiting strategy can be completed without restarting the system. to improve the update efficiency of the current limiting strategy and the inclusiveness of various current limiting methods.

The implementation details of the gateway current limiting method in this embodiment will be specifically described below. The following content is only provided for the convenience of understanding, and is not necessary for implementing this solution.

It should be noted that the database in some embodiments of the present invention may be a distributed key-value pair storage database, such as Redis, or other databases, which are not specifically limited in the embodiments of the present invention.

A schematic flowchart of the gateway current limiting method in this embodiment is shown in FIG. 1 , which specifically includes the following steps:

Step 101: Determine whether a preset time interval is reached.

It should be noted that the execution body of this embodiment may be a gateway server, and optionally, the gateway server may specifically be an API gateway server, wherein the gateway server represents a gateway node, and each gateway node is connected to a database for implementing Access to the database, server access or other current restrictions to ensure the stability of the network and database.

The preset time interval may be set according to actual needs, which is not specifically limited in this embodiment.

Specifically, the gateway server can judge according to the set timer, if the time reaches the preset time interval, then go to step 102, otherwise, continue to execute step 101 until the time reaches the preset time interval.

Step 102: Synchronously update the current limiting plug-in activation list set locally to the current limiting plug-in activation list set in the database.

The current-limiting plug-in refers to a plug-in used to limit current for database access, server access, or other conditions, which is not specifically limited in this embodiment. A current-limiting plug-in corresponds to a current-limiting policy. The current-limiting policy includes token buckets, leaky buckets, counters, etc. The current-limiting plug-in startup list is used to indicate the current-limiting plug-ins that each gateway node needs to start, and the current-limiting plug-ins set locally. The startup list refers to the startup list of the current limiting plug-in set on each gateway node.

Optionally, the current limiting plug-in startup list set in the database is regularly maintained by a user (eg, a gateway administrator) according to a current limiting policy.

Optionally, after the gateway server downloads the current-limiting plug-in startup list in the database, it replaces the downloaded current-limiting plug-in startup list with the current-limiting plug-in startup list of the local gateway node, and completes the current-limiting plug-in startup list of the local gateway node. renew.

Step 103: According to the updated current-limiting plug-in startup list, run each current-limiting plug-in to be activated to limit the current.

Optionally, the gateway server obtains the name of each current-limiting plug-in to be activated according to the updated current-limiting plug-in startup list, and then runs each current-limiting plug-in one by one according to the name of the current-limiting plug-in to implement the current-limiting policy of the database. Wherein, each current limiting plug-in can be downloaded from a designated location by the gateway server and stored in the gateway server, and the gateway server can obtain and run the current limiting plug-in according to the name of the current limiting plug-in.

After the execution of step 103 is completed, the process returns to step 101, that is, it is re-determined whether the preset time interval is reached, and the next cycle is entered.

Compared with the prior art, the present embodiment determines whether the preset time interval is reached, and if so, updates the locally set current-limiting plug-in startup list to the current-limiting plug-in startup list set in the database, and starts the current-limiting plug-in according to the updated current-limiting plug-in startup list. List the limit plug-ins that need to be started to limit the flow. This embodiment implements a hot-swappable plug-in mode. Since each gateway node uses the same list of startup plug-ins to limit the current, the startup current-limiting plug-ins of each node can always be consistent. The method of the flow plugin startup list indicates the current limiting plugins that need to be started, which is highly flexible and can update and synchronize the current limiting policy without restarting, thus improving the update efficiency of the current limiting policy and improving the efficiency of each current limiting method. inclusiveness.

In a specific example, the current limiting plug-in can be uploaded to the database through the following steps:

Step 201: Obtain the current limiting plug-in uploaded by the client, where the uploaded current limiting plug-in includes a predefined plug-in startup method.

Step 202: Uniquely identify the uploaded current limiting plug-in.

Step 203: Upload the uniquely identified current limiting plug-in to the database.

Please refer to FIG. 2 , which is an example diagram of uploading the current limiting plug-in to the database.

Among them, the client refers to the client connected to the gateway server, such as a browser, APP or other applications; the pre-defined plugin startup mode can be set according to actual needs, for example, start the plugin in the stark mode, and the pre-defined plugin startup method The plug-in startup modes may be set to the same mode, or different current-limiting plug-ins may have different activation modes, which are not limited in this embodiment.

The unique identification refers to different identifications for each current limiting plug-in, so that each current limiting plug-in corresponds to an identification. Optionally, a timestamp can be set for the uploaded current limiting plug-in. Since the timestamp varies with time, the current limiting plug-in can be uniquely identified by the timestamp. The uploaded current-limiting plug-in is uniquely identified with a timestamp. Even if the user uploads the current-limiting plug-in with the same name, the gateway server can distinguish it according to the timestamp. Optionally, other identifiers may also be used to uniquely identify the current limiting plug-in, for example, the current limiting plug-in may be identified by a serial number, which is not specifically limited in this embodiment.

Optionally, when the client uploads the current limiting plug-in to the gateway server, it is uploaded through the post interface.

After uniquely identifying the current limiting plug-in uploaded by the client, the gateway server uploads the uniquely identified current limiting plug-in to the database.

It is understandable that, since the user uploads the current limiting plug-in on the client through a node of a gateway server, other gateway nodes do not store the uploaded current limiting plug-in, and other gateway nodes also need to download the uploaded current limiting plug-in from the database. The plugin can be loaded and run.

By uniquely identifying the uploaded current-limiting plug-in, even if the user uploads the current-limiting plug-in with the same name, the gateway server can distinguish it; uploading the uniquely identified current-limiting plug-in to the database, the database can also use the unique identification Distinguish each current-limiting plug-in to facilitate subsequent maintenance of the current-limiting plug-in. At the same time, by making the current-limiting plug-in unique, the current-limiting plug-in startup list maintained in the database can be updated after the current-limiting plug-in is updated to different versions, even if the name of the current-limiting plug-in is not updated. The node can also delete the old version of the current limit plug-in and load the new version of the current limit plug-in according to the current limit plug-in startup list.

The second embodiment of the present invention relates to a gateway current limiting method. As shown in FIG. 3 , the second embodiment is roughly the same as the first embodiment, and the main difference is that in step 103, according to the updated current limiting method Plug-in startup list, run each current-limiting plug-in to be started to limit current, which can include the following steps:

Step 1031: Determine whether the current-limiting plug-in activation list before the update is relative to the updated current-limiting plug-in activation list, and there is a missing current-limiting plug-in. If there is a missing current limiting plug-in, go to step 1032 ; if there is no missing current limiting plug-in, go to step 1033 .

Step 1032: Acquire and start the missing current limiting plug-in from the database.

Step 1033: Determine whether the current-limiting plug-in activation list before the update is compared with the updated current-limiting plug-in activation list, and there are redundant current-limiting plug-ins. If there are redundant current limiting plug-ins, go to step 1034; if there are no redundant current limiting plug-ins, go back to step 101.

Step 1034: Stop the operation of redundant current limiting plug-ins.

Optionally, the gateway server compares its own current-limiting plugin startup list with the current-limiting plugin startup list in the database. If a current-limiting plugin in the current-limiting plugin startup list in the database is in the gateway server's current-limiting plugin startup list If there is no current limiting plug-in, the gateway server determines that the current limiting plug-in is a missing current limiting plug-in, and the gateway server downloads the missing current limiting plug-in from the database and loads and runs it. Optionally, the gateway server stores the current limiting plug-in startup lists before and after the update, and the gateway server can obtain the missing current limiting plug-in after comparing the current limiting plug-in startup lists before and after the update.

Please refer to FIG. 4 , which is an example diagram of downloading the missing current limiting plug-in to the gateway server. Specifically, the gateway server obtains the name of the missing current-limiting plug-in according to the current-limiting plug-in startup list in the database, and then finds the corresponding current-limiting plug-in in the database according to the name of the missing current-limiting plug-in, and stores it in the database specified by the gateway server after downloading. directory, such as the src/Plugins/otherPlugins/ directory.

Please refer to FIG. 5 , which is an example diagram of loading the downloaded current limiting plug-in. Specifically, the gateway server obtains the name of the current limiting plug-in to be loaded (the downloaded missing current limiting plug-in), and loads the current limiting plug-in according to the path specified by the name of the current limiting plug-in to be loaded (the directory specified when downloading).

In step 1031, if the current-limiting plug-in activation list before the update is unchanged from the updated current-limiting plug-in activation list, the gateway server determines that there is no missing current-limiting plug-in, and proceeds to step 1033 to determine that the current-limiting plug-in before the update is activated Whether there are redundant current-limiting plug-ins in the list relative to the updated current-limiting plug-in startup list.

Specifically, the gateway server compares its own current-limiting plugin startup list with the current-limiting plugin startup list in the database. If there is a current-limiting plugin in its own current-limiting plugin startup list, it is in the current-limiting plugin startup list in the database. If not, the gateway server determines that the current limiting plug-in is a redundant current limiting plug-in, and the gateway server stops running the redundant current limiting plug-in.

Please refer to FIG. 6 , which is an example diagram of stopping the operation of redundant current limiting plug-ins. Specifically, the gateway server obtains the names of redundant current-limiting plug-ins according to its own current-limiting plug-in startup list, and then traverses the routing stack table of the gateway server according to the names of the redundant current-limiting plug-ins. If the name of the current limiting plug-in matches, the matching item will be deleted.

In step 1033, if the current-limiting activation list before the update has no redundant current-limiting plug-ins relative to the updated current-limiting plug-in activation list, the process returns to step 101, and the next cycle is entered. After the execution of step 1034 is completed, step 101 is also returned.

Compared with the prior art, this embodiment compares the current-limiting plug-in startup list before and after the gateway server is updated. If there is a missing current-limiting plug-in, download and run it from the database; if there are redundant current-limiting plug-ins, stop running. The redundant current-limiting plug-ins keep the current-limiting plug-ins of the gateway server consistent with the current-limiting plug-in startup list in the database, so as to update the current-limiting policy.

In one example, step 1032, that is, acquiring and starting the missing current limiting plug-in from the database, may specifically include the following steps:

Step 301: Download the missing current limiting plug-in from the database.

Step 302: Change the name of the missing current limiting plug-in to obtain the startup name of the missing current limiting plug-in.

Step 303: Start with the plug-in start-up method of the missing current-limiting plug-in.

Step 304: Adjust the position of the missing current limiting plug-in's startup process in the routing stack.

Please refer to FIG. 7 , which is an example diagram of starting the downloaded current limiting plug-in. Specifically, the gateway server obtains the start-up name of the missing current-limiting plug-in after changing the name according to the name of the missing current-limiting plug-in, and then starts according to the plug-in startup method of the missing current-limiting plug-in, for example, calling the plug-in through app.use The start method is used to start the current-limiting plug-in, and adjust the position of the missing current-limiting plug-in's startup process in the routing stack to the executable position. It can be understood that due to the sequential nature of the routing stack during the execution of the system process, by adjusting the startup process of the missing current limiting plug-in to an executable position, the current limiting policy can be implemented in time, thereby ensuring the network and database stability.

In an example, please refer to FIG. 8 , which is a specific example diagram of the gateway server.

Among them, the upload sub-module in the upload and download module is used to upload the customized current limiting plug-in to the gateway server, and the gateway server uploads it to the database;

The download submodule is used to download the current limiting plug-in from the database;

The trigger unit of the promoter sub-module in the current-limiting plug-in startup module is used to trigger the startup execution unit;

Start the execution unit to run the loaded current limiting plug-in;

The trigger unit of the stop sub-module in the current-limiting plug-in startup module is used to trigger the stop execution unit;

The stop execution unit is used to stop the current-limiting plug-in according to the name of the current-limiting plug-in to be stopped;

The timing sub-module in the synchronization module is used to perform the synchronization operation regularly through the configured preset period;

The synchronization submodule is used to synchronize the startup list of current limiting plug-ins running on each gateway node.

Please refer to FIG. 9 , which is a schematic diagram of the architecture of the gateway server. Specifically, the Redis database is taken as an example in the figure. ApiGateway represents each gateway node, and Client represents the client; the client uploads a customized current limiting plug-in to Redis through the gateway server. database, and update the current-limiting plugin startup list in the database according to the current-limiting policy. Each gateway server checks whether the local current-limiting plugin startup list is consistent with the current-limiting plugin startup list in the Redis database according to the preset period. The throttling plugin startup list starts or stops a throttling plugin.

The third embodiment of the present invention relates to a gateway current limiting method. The flowchart of this embodiment is shown in FIG. 10 , and specifically includes the following steps:

Step 401: Determine whether a current limiting plug-in activation command sent by the client is received, if the current limiting plug-in activation command is received, proceed to step 402; if the current limiting plug-in activation command is not received, proceed to step 405.

Step 402: Obtain the name of the current-limiting plug-in to be started indicated by the current-limiting plug-in start command.

Step 403: Determine whether the current-limiting plug-in to be activated indicated by the current-limiting plug-in activation command is a current-limiting plug-in stored in the database, if the current-limiting plug-in to be activated is a current-limiting plug-in stored in the database, then enter step 404, if necessary If the activated current limiting plug-in is not the current limiting plug-in stored in the database, an error message is returned.

Step 404: Add the name of the current-limiting plug-in to be activated indicated by the current-limiting plug-in activation command to the current-limiting plug-in activation list set in the database.

Step 405: Determine whether the current limiting plug-in stop command sent by the client is received. If the current limiting plug-in stop command is received, go to step 406; if the current limiting plug-in stop command is not received, the step flow ends.

Step 406: Obtain the name of the current limiting plug-in to be stopped indicated by the current limiting plug-in stop command, and delete the name of the current limiting plug-in to be stopped in the current limiting plug-in startup list set in the database.

Specifically, the gateway server may receive commands related to the current limiting plug-in sent by the client. For example, the gateway administrator sends a current limiting plug-in activation command to the gateway server through the client according to the change of the current limiting policy. In step 401 , if it is determined that the current limiting plug-in start command sent by the client is not received, step 405 is entered.

When the gateway server receives the current-limiting plug-in start command sent by the client, it obtains the name of the current-limiting plug-in to be started according to the current-limiting plug-in start command; the gateway server communicates with the database to determine the current-limiting plug-in that needs to be started by the current-limiting plug-in start command. Whether the plug-in is a current-limiting plug-in stored in the database, if so, add the name of the current-limiting plug-in to be started to the current-limiting plug-in startup list set in the database, so that the current-limiting plug-in startup list in the database is updated to Make subsequent gateway nodes compare the locally set current-limiting plugin startup list with the updated current-limiting plugin startup list in the database, so as to add the current-limiting plugin to be started indicated by the current-limiting plugin startup command on the gateway node; if not, Then an error message is returned, so that the user can upload the current limiting plug-in corresponding to the current limiting plug-in start command through the client and then perform subsequent operations.

When receiving the current-limiting plug-in stop command sent by the client, the gateway server obtains the name of the current-limiting plug-in that needs to be stopped according to the current-limiting plug-in stop command, and deletes the current-limiting plug-in start list set in the database. The name of the flow plug-in, so that the current limit plug-in start list in the database is updated, so that the gateway node stops the flow limit plug-in corresponding to the flow limit plug-in stop command according to the flow limit plug-in start list in the database.

Compared with the prior art, this embodiment receives the current-limiting plug-in start command sent by the client through the gateway server, and adds the current-limiting plug-in name corresponding to the current-limiting plug-in start command to the current-limiting plug-in start list in the database; The current-limiting plug-in stop command sent by the client deletes the current-limiting plug-in name corresponding to the current-limiting plug-in stop command from the current-limiting plug-in startup list in the database, thereby realizing the update of the current-limiting plug-in startup list in the database. By sending the start or stop command of the current limiting plug-in from the client, the corresponding current limiting policy can be flexibly implemented, which improves the update efficiency of the current limiting policy.

The steps of the above various methods are divided only for the purpose of describing clearly. During implementation, they can be combined into one step or some steps can be split and decomposed into multiple steps. As long as the same logical relationship is included, they are all within the protection scope of this patent. ;Adding insignificant modifications to the algorithm or process or introducing insignificant designs, but not changing the core design of the algorithm and process are all within the scope of protection of this patent.

The fourth embodiment of the present invention relates to a gateway current limiting device, as shown in FIG. 11 , including:

The startup list maintenance module 501 is configured to synchronously update the locally set current-limiting plug-in startup list with a preset cycle to the current-limiting plugin startup list set in the database; wherein, the current-limiting plugin startup list is used to indicate each limit to be activated. Streaming plug-ins, each current-limiting plug-in corresponds to a current-limiting policy;

The current limiting module 502 is configured to run each current limiting plug-in to be activated to perform current limiting according to the updated current limiting plug-in activation list.

Optionally, the current limiting module 502 is also used for:

If there is a missing current-limiting plug-in in the current-limiting plug-in startup list before the update relative to the updated current-limiting plug-in startup list, the missing current-limiting plug-in is obtained from the database and started;

If there are redundant current-limiting plug-ins in the current-limiting plug-in startup list before the update relative to the updated current-limiting plug-in start-up list, the operation of the redundant current-limiting plug-ins is stopped.

Optionally, the current limiting plug-in can be uploaded to the database in the following ways:

Obtain the current limiting plug-in uploaded by the client, and the uploaded current limiting plug-in includes the pre-defined plug-in startup method;

Uniquely identify the uploaded current limiting plug-in;

Upload the uniquely identified current limiting plug-in to the database.

Optionally, a timestamp can be set for the uploaded throttling plugin.

Optionally, obtain and start the missing current limiting plug-in from the database, including:

Download missing throttling plugins from the database;

Change the name of the missing current limiting plug-in to get the startup name of the missing current limiting plug-in;

Start with the plugin startup method of the missing current limiting plugin;

Adjust the position of the missing current limiting plugin's startup process in the routing stack.

Optionally, the gateway current limiting device in this embodiment is also used for:

In response to the current-limiting plug-in start command sent by the client, obtain the name of the current-limiting plug-in to be started indicated by the current-limiting plug-in start command;

If the current-limiting plug-in to be started indicated by the current-limiting plug-in start command is the current-limiting plug-in stored in the database, the name of the current-limiting plug-in to be started indicated by the current-limiting plug-in start-up command is added to the current-limiting plug-in set in the database. start list;

In response to the current-limiting plug-in stop command sent by the client, obtain the name of the current-limiting plug-in to be stopped indicated by the current-limiting plug-in stop command, and delete the current-limiting plug-in to be stopped in the current-limiting plug-in startup list set in the database. name.

Optionally, the database is specifically a distributed key-value pair storage database.

It is not difficult to find that this embodiment is a system example corresponding to the first embodiment, and this embodiment can be implemented in cooperation with the first embodiment. The relevant technical details mentioned in the first embodiment are still valid in this embodiment, and are not repeated here in order to reduce repetition. Correspondingly, the related technical details mentioned in this embodiment can also be applied to the first embodiment.

It is worth mentioning that each module involved in this embodiment is a logical module. In practical applications, a logical unit may be a physical unit, a part of a physical unit, or multiple physical units. A composite implementation of the unit. In addition, in order to highlight the innovative part of the present invention, this embodiment does not introduce units that are not closely related to solving the technical problem proposed by the present invention, but this does not mean that there are no other units in this embodiment.

The fifth embodiment of the present invention relates to a network device, as shown in FIG. 12 , comprising at least one processor 601; and a memory 602 communicatively connected with the at least one processor 601; wherein, the memory 602 stores data that can be processed by the at least one processor 601. The instructions are executed by the processor 601, and the instructions are executed by the at least one processor 601, so that the at least one processor 601 can execute the above-mentioned gateway current limiting method.

The memory 602 and the processor 601 are connected by a bus, and the bus may include any number of interconnected buses and bridges, and the bus connects one or more processors 601 and various circuits of the memory 602 together. The bus may also connect together various other circuits, such as peripherals, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides the interface between the bus and the transceiver. A transceiver may be a single element or multiple elements, such as multiple receivers and transmitters, providing a means for communicating with various other devices over a transmission medium. The data processed by the processor 601 is transmitted on the wireless medium through the antenna, and further, the antenna also receives the data and transmits the data to the processor 601 .

Processor 601 is responsible for managing the bus and general processing, and may also provide various functions, including timing, peripheral interface, voltage regulation, power management, and other control functions. The memory 602 may be used to store data used by the processor 601 when performing operations.

The sixth embodiment of the present invention relates to a gateway current limiting system, including a database and N gateways in communication and connection with the database as in the fifth embodiment, wherein N is a natural number greater than zero.

A seventh embodiment of the present invention relates to a computer-readable storage medium storing a computer program. The above method embodiments are implemented when the computer program is executed by the processor.

That is, those skilled in the art can understand that all or part of the steps in the method for implementing the above embodiments can be completed by instructing the relevant hardware through a program, and the program is stored in a storage medium and includes several instructions to make a device ( It may be a single chip microcomputer, a chip, etc.) or a processor (processor) to execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: U disk, removable hard disk, Read-Only Memory (ROM, Read-Only Memory), Random Access Memory (RAM, Random Access Memory), magnetic disk or optical disk and other media that can store program codes.

Those skilled in the art can understand that the above-mentioned embodiments are specific examples for realizing the present invention, and in practical applications, various changes in form and details can be made without departing from the spirit and the spirit of the present invention. scope.

Claims (11)

1. a gateway current limiting method, is characterized in that, comprises: The locally set current-limiting plug-in startup list is synchronously updated to the current-limiting plug-in startup list set in the database with a preset period; wherein, the current-limiting plug-in startup list is used to indicate each current-limiting The current limiting plug-ins correspond to a current limiting strategy respectively; According to the updated current-limiting plug-in activation list, run each current-limiting plug-in to be activated to limit the current. 2. The gateway current-limiting method according to claim 1, characterized in that, according to the updated current-limiting plug-in startup list, running each current-limiting plug-in to be started to perform current-limiting, specifically comprising: If there is a missing current-limiting plug-in in the current-limiting plug-in activation list before the update relative to the updated current-limiting plug-in activation list, obtain and activate the missing current-limiting plug-in from the database; If there are redundant current-limiting plug-ins in the current-limiting plug-in activation list before the update relative to the updated current-limiting plug-in activation list, the operation of the redundant current-limiting plug-ins is stopped. 3. The gateway current limiting method according to claim 2, wherein the current limiting plug-in is uploaded to the database in the following manner: Obtain the current-limiting plug-in uploaded by the client, where the uploaded current-limiting plug-in includes a predefined plug-in startup method; uniquely identify the uploaded current limiting plug-in; Upload the current limiting plug-in after the unique identification to the database. 4. The gateway current limiting method according to claim 3, wherein the unique identification of the uploaded current limiting plug-in specifically includes: Set a timestamp for the uploaded throttling plugin. 5. The gateway current limiting method according to claim 3, wherein the acquiring and starting the missing current limiting plug-in from the database specifically comprises: downloading the missing throttling plug-in from the database; Performing a name change on the missing current-limiting plug-in to obtain the startup name of the missing current-limiting plug-in; Start with the plugin startup method of the missing current-limiting plugin; Adjust the position of the startup process of the missing current limiting plug-in in the routing stack. 6. The gateway current limiting method according to any one of claims 1 to 5, further comprising: In response to the current-limiting plug-in start command sent by the client, obtain the name of the current-limiting plug-in to be started indicated by the current-limiting plug-in start command; If the current-limiting plug-in to be started indicated by the current-limiting plug-in start command is the current-limiting plug-in stored in the database, then the name of the current-limiting plug-in to be started indicated by the current-limiting plug-in start command is added to the in the current limiting plug-in startup list set in the database; In response to the current-limiting plug-in stop command sent by the client, obtain the name of the current-limiting plug-in to be stopped indicated by the current-limiting plug-in stop command, and delete the current-limiting plug-in start list set in the database. The name of the stopped throttling plugin. 7. The gateway current limiting method according to any one of claims 1 to 5, wherein, The database is specifically a distributed key-value pair storage database. 8. A gateway current limiting device, characterized in that, comprising: The startup list maintenance module is used to synchronously update the locally set current-limiting plug-in startup list to the current-limiting plugin startup list set in the database with a preset period; wherein, the current-limiting plugin startup list is used to indicate each a current-limiting plug-in, each of the current-limiting plug-ins corresponds to a current-limiting strategy; The current limiting module is configured to run each current limiting plug-in to be activated to perform current limiting according to the updated current limiting plug-in startup list. 9. A gateway, characterized in that, comprising: at least one processor; and, a memory communicatively coupled to the at least one processor; wherein, The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to perform the execution of any of claims 1 to 7 The gateway current limiting method described above. 10 . A gateway current limiting system, comprising: a database and N gateways according to claim 9 that are communicatively connected to the database, wherein the N is a natural number greater than zero. 11 . 11 . A computer-readable storage medium storing a computer program, wherein when the computer program is executed by a processor, the gateway current limiting method according to any one of claims 1 to 7 is implemented. 12 .