Traffic control method, device and system for elastic IP of public cloud platform

Through the dual-layer gateway design, the traffic control and address conversion of elastic IP in the public cloud platform are separately handled, which solves the problem of inefficiency of gateway nodes, and realizes efficient traffic management and address conversion, improving the stability and flexibility of the system.

CN115714748BActive Publication Date: 2024-11-08DOUYIN VISION CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202110957203.X
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2021-08-19
Publication Date
2024-11-08
Estimated Expiration
2041-08-19

AI Technical Summary

Technical Problem

Traffic control and address conversion between virtual machines and elastic IP in public cloud platforms lead to inefficient gateway nodes and difficult management, making it difficult to effectively separate traffic control and address conversion functions in the existing technology.

Method used

The two-layer gateway design is adopted. The first gateway is responsible for traffic control and the second gateway is responsible for address conversion. The packet processing is carried out through the pre-generated traffic control policy and address correspondence relationship, so that the separate settings of traffic control and address conversion are realized.

Benefits of technology

It improves the working efficiency of gateway nodes, is easy to manage, realizes personalized traffic control and address conversion of elastic IP, and improves the stability and flexibility of the system.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN115714748B_ABST
    Figure CN115714748B_ABST
Patent Text Reader

Abstract

The present disclosure relates to a method, device and system for controlling the flow of elastic IP in a public cloud platform. The method includes: receiving a first message sent by a public network gateway, obtaining a destination IP address of a first elastic IP address carried by the first message; judging whether the flow of the first message exceeds the inbound speed limit value of the first elastic IP address according to a pre-generated first flow control strategy, and obtaining a first judgment result, wherein the first flow control strategy is used to set each inbound speed limit value of each elastic IP address, and each inbound speed limit value is determined according to the bandwidth of each elastic IP address and the number of first gateways; if the first judgment result is that the flow of the first message does not exceed the inbound speed limit value of the first elastic IP address, the first message is sent to the second gateway, so that the second gateway processes the first message according to the preset correspondence between each elastic IP address and each intranet IP address. The present disclosure can control the flow of elastic IP and improve the working efficiency of gateway nodes.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The disclosed embodiments relate to the field of communication technology, and in particular to a method, device and system for controlling traffic of an elastic IP address of a public cloud platform. Background Art

[0002] When a user binds a virtual machine on a public cloud to a purchased elastic IP (EIP), and the virtual machine uses the EIP as a public IP address to communicate with the Internet, the message traffic used for communication will occupy a certain amount of network bandwidth. Therefore, the user also needs to purchase network bandwidth from the public cloud service provider to achieve information exchange between the public cloud and the Internet within the agreed network bandwidth range. Based on this, the public cloud service provider will set data inbound and outbound bandwidth speed limit rules based on the network bandwidth purchased by the user to control the traffic of the EIP purchased by the user.

[0003] In addition, when a virtual machine is bound to an EIP, a mapping is actually used to establish a correspondence between the virtual machine's intranet IP address and the bound EIP. Therefore, when the virtual machine communicates with the Internet through a gateway node using the EIP as the public IP address, the gateway node is also required to perform address conversion between the virtual machine's intranet IP address and the EIP as the public IP address.

[0004] With the continuous development of public cloud technology, the amount of data in cloud services is increasing, resulting in an increasing amount of computation required for flow control and address translation at gateway nodes. However, performing flow control and address translation at the same time makes the work efficiency of gateway nodes low and difficult to manage. Summary of the invention

[0005] The purpose of the embodiments of the present disclosure is to provide a method, device and system for controlling the traffic of an elastic IP of a public cloud platform, which can control the traffic of an elastic IP and improve the working efficiency of a gateway node.

[0006] To solve the above technical problems, the embodiments of the present disclosure provide a method for controlling traffic of an elastic IP of a public cloud platform, which is applied to a first gateway for the public cloud platform to communicate with a public network gateway. The method includes:

[0007] Receive a first message sent by the public network gateway, and obtain a destination IP address carried by the first message, wherein the destination IP address is a first elastic IP address;

[0008] According to a pre-generated first flow control strategy, determine whether the flow of the first message exceeds the inbound speed limit value of the first elastic IP address, and obtain a first judgment result, wherein the first flow control strategy is used to set each inbound speed limit value of each elastic IP address, and each inbound speed limit value is determined according to the bandwidth of each elastic IP address and the number of the first gateways;

[0009] If the first judgment result is that the traffic of the first message does not exceed the inbound rate limit of the first elastic IP address, the first message is sent to the second gateway so that the second gateway processes the first message according to the preset correspondence between each elastic IP address and each intranet IP address.

[0010] Optionally, the method further includes:

[0011] Receive a second message sent by the second gateway, and obtain a source IP address carried by the second message, wherein the source IP address is a second elastic IP address;

[0012] According to a pre-generated second traffic control policy, the second message is sent to the egress control gateway of the second elastic IP address, so that the egress control gateway sends the second message to the public network gateway when the traffic of the second message does not exceed the egress speed limit value of the second elastic IP address, wherein the second traffic control policy is used to set each egress control gateway and each egress speed limit value of each elastic IP address, and each egress control gateway is determined according to a preset rule.

[0013] Optionally, the method further includes:

[0014] Receive multiple messages sent by the public network gateway, and obtain destination IP addresses respectively carried by the multiple messages, wherein the destination IP addresses are elastic IP addresses;

[0015] Determine whether the bandwidth of the first gateway is less than the sum of the traffic of the multiple messages, and obtain a second determination result;

[0016] If the second judgment result is that the bandwidth of the first gateway is less than the sum of the traffic of the multiple messages, then according to the pre-set priority information of each elastic IP address, the first traffic control strategy is used to process the multiple messages in order of priority.

[0017] Optionally, the method further includes:

[0018] Receive multiple messages sent by the second gateway, and obtain source IP addresses respectively carried by the multiple messages, wherein the source IP addresses are elastic IP addresses;

[0019] Determine whether the bandwidth of the first gateway is less than the sum of the traffic of the multiple messages, and obtain a third determination result;

[0020] If the third judgment result is that the bandwidth of the first gateway is less than the sum of the traffic of the multiple messages, then according to the pre-set priority information of each elastic IP address, the second traffic control strategy is used to process the multiple messages in order of priority.

[0021] The embodiment of the present disclosure further provides a traffic control method for an elastic IP of a public cloud platform, which is applied to a second gateway for the public cloud platform to communicate with a first gateway, and the method includes:

[0022] After the first gateway controls the flow of the first message according to the pre-generated first flow control strategy:

[0023] Receive the first message sent by the first gateway, and obtain the destination IP address carried by the first message, wherein the destination IP address is a first elastic IP address;

[0024] According to the preset correspondence between each elastic IP address and each intranet IP address, determine whether there is a first intranet IP address corresponding to the first elastic IP address, and obtain a fourth determination result;

[0025] If the fourth judgment result is that there is a first intranet IP address corresponding to the first elastic IP address, then obtaining the first intranet IP address, and converting the destination IP address of the first message into the first intranet IP address;

[0026] The first message after address conversion is sent to the terminal corresponding to the first intranet IP address.

[0027] Optionally, the method further includes:

[0028] Receive a second message sent by the terminal, and obtain a source IP address carried by the second message, wherein the source IP address is a second intranet IP address;

[0029] According to the preset correspondence between each elastic IP address and each intranet IP address, determine whether there is a second elastic IP address corresponding to the second intranet IP address, and obtain a fifth judgment result;

[0030] If the fifth judgment result is that there is a second elastic IP address corresponding to the second intranet IP address, obtaining the second elastic IP address, and converting the source IP address of the second message into the second elastic IP address;

[0031] The second message after address conversion is sent to the first gateway, so that the first gateway controls the flow of the second message after address conversion according to a pre-generated second flow control policy.

[0032] The embodiment of the present disclosure further discloses a traffic control device for an elastic IP of a public cloud platform, the device comprising:

[0033] A first receiving module, used to receive a first message sent by the public network gateway, and obtain a destination IP address carried by the first message, wherein the destination IP address is a first elastic IP address;

[0034] A first judgment module is used to judge whether the flow of the first message exceeds the inbound speed limit value of the first elastic IP address according to a pre-generated first flow control policy, and obtain a first judgment result, wherein the first flow control policy is used to set each inbound speed limit value of each elastic IP address, and each inbound speed limit value is determined according to the bandwidth of each elastic IP address and the number of the first gateways;

[0035] The first sending module is used to send the first message to the second gateway when the first judgment result is that the traffic of the first message does not exceed the inbound rate limit value of the first elastic IP address, so that the second gateway processes the first message according to the preset correspondence between each elastic IP address and each intranet IP address.

[0036] Optionally, the first receiving module is further used to receive a second message sent by the second gateway, and obtain a source IP address carried by the second message, wherein the source IP address is a second elastic IP address;

[0037] The first sending module is also used to send the second message to the egress control gateway of the second elastic IP address according to a pre-generated second traffic control strategy, so that the egress control gateway sends the second message to the public network gateway when the traffic of the second message does not exceed the egress speed limit value of the second elastic IP address, wherein the second traffic control strategy is used to set each egress control gateway and each egress speed limit value of each elastic IP address, and each egress control gateway is determined according to a preset rule.

[0038] Optionally, the first receiving module is further used to receive multiple messages sent by the public network gateway, and obtain the destination IP addresses respectively carried by the multiple messages, wherein the destination IP addresses are elastic IP addresses;

[0039] The first judgment module is further used to judge whether the bandwidth of the first gateway is less than the sum of the traffic of the multiple messages, and obtain a second judgment result;

[0040] If the second judgment result is that the bandwidth of the first gateway is less than the sum of the traffic of the multiple messages, then according to the pre-set priority information of each elastic IP address, the first traffic control strategy is used to process the multiple messages in order of priority.

[0041] Optionally, the first receiving module is further used to receive multiple messages sent by the second gateway, and obtain each source IP address carried by the multiple messages, wherein each source IP address is a respective elastic IP address;

[0042] The first judgment module is further used to judge whether the bandwidth of the first gateway is less than the sum of the traffic of the multiple messages, and obtain a third judgment result;

[0043] If the third judgment result is that the bandwidth of the first gateway is less than the sum of the traffic of the multiple messages, then according to the pre-set priority information of each elastic IP address, the second traffic control strategy is used to process the multiple messages in order of priority.

[0044] The embodiment of the present disclosure further discloses a traffic control device for an elastic IP of a public cloud platform, the device comprising a second receiving module, a second judging module, an address conversion module, and a second sending module, wherein:

[0045] After the first gateway controls the flow of the first message according to the pre-generated first flow control strategy:

[0046] The second receiving module is used to receive the first message sent by the first gateway, and obtain the destination IP address carried by the first message, wherein the destination IP address is a first elastic IP address;

[0047] The second judgment module is used to judge whether there is a first intranet IP address corresponding to the first elastic IP address according to the preset correspondence between each elastic IP address and each intranet IP address, and obtain a fourth judgment result;

[0048] The address conversion module is used to obtain the first intranet IP address and convert the destination IP address of the first message into the first intranet IP address when the fourth judgment result is that there is a first intranet IP address corresponding to the first elastic IP address;

[0049] The second sending module is used to send the first message after address conversion to the terminal corresponding to the first intranet IP address.

[0050] Optionally, the second receiving module is further used to receive a second message sent by the terminal, and obtain a source IP address carried by the second message, wherein the source IP address is a second intranet IP address;

[0051] The second judgment module is further used to judge whether there is a second elastic IP address corresponding to the second intranet IP address according to the preset correspondence between each elastic IP address and each intranet IP address, and obtain a fifth judgment result;

[0052] The address conversion module is further configured to, when the fifth judgment result is that there is a second elastic IP address corresponding to the second intranet IP address, obtain the second elastic IP address and convert the source IP address of the second message into the second elastic IP address;

[0053] The second sending module is further used to send the second message after address conversion to the first gateway, so that the first gateway controls the flow of the second message after address conversion according to a pre-generated second flow control strategy.

[0054] The embodiment of the present disclosure further discloses a traffic control system of a public cloud platform elastic IP, the system comprising a first gateway and a second gateway applied to the public cloud platform for communicating with a public network gateway, wherein:

[0055] The first gateway is used to receive the first message sent by the public network gateway, and obtain the destination IP address carried by the first message, wherein the destination IP address is a first elastic IP address;

[0056] According to a pre-generated first flow control strategy, determine whether the flow of the first message exceeds the inbound speed limit value of the first elastic IP address, and obtain a first judgment result, wherein the first flow control strategy determines the inbound speed limit value of each elastic IP address according to the bandwidth of each elastic IP address and the number of the first gateways;

[0057] If the first judgment result is that the traffic of the first message does not exceed the inbound rate limit of the first elastic IP address, the first message is sent to the second gateway, so that the second gateway processes the first message according to the preset correspondence between each elastic IP address and each intranet IP address;

[0058] After the first gateway controls the flow of the first message according to the first flow control policy:

[0059] The second gateway is used to receive the first message and obtain the destination IP address, wherein the destination IP address is the first elastic IP address;

[0060] According to the preset correspondence between each elastic IP address and each intranet IP address, determine whether there is a first intranet IP address corresponding to the first elastic IP address, and obtain a determination result;

[0061] If the judgment result is that there is a first intranet IP address corresponding to the first elastic IP address, the first intranet IP address is obtained, and the destination IP address of the first message is converted to the first intranet IP address;

[0062] The first message after address conversion is sent to the terminal corresponding to the first intranet IP address.

[0063] An embodiment of the present disclosure further provides an electronic device, including:

[0064] at least one processor; and,

[0065] a memory communicatively connected to the at least one processor; wherein,

[0066] The memory stores instructions that can be executed by the at least one processor. The instructions are executed by the at least one processor so that the at least one processor can perform the above-mentioned method.

[0067] The embodiments of the present disclosure further provide a computer-readable storage medium storing a computer program, which implements the above-mentioned method when executed by a processor.

[0068] Compared with the prior art, the disclosed implementation mode adopts a two-layer gateway design, implements the flow control function of the elastic IP address through the first gateway, and implements the address translation function of the elastic IP address through the second gateway, realizes the separate setting of the flow control function and the address translation function, facilitates the management of each gateway node, and can effectively improve the working efficiency of the gateway node; after receiving the first message sent by the public network gateway, the first gateway can judge whether the flow of the first message exceeds the inbound speed limit value of the first elastic IP address according to the first elastic IP address corresponding to the first message and the pre-generated first flow control policy, and When the inbound speed limit value of the first elastic IP address is output, the first message is sent to the second gateway, so that the second gateway can send the first message to the terminal where the intranet IP address corresponding to the first elastic IP address is located according to the correspondence between each elastic IP address and each intranet IP address, thereby achieving the purpose of controlling the traffic of the elastic IP; the first traffic control strategy is used to set each inbound speed limit value of each elastic IP address, and each inbound speed limit value is determined according to the bandwidth of each elastic IP address and the number of first gateways, so that the inbound speed limit values ​​can be set for different elastic IP addresses respectively, realizing personalized control of the traffic of multiple elastic IP addresses. BRIEF DESCRIPTION OF THE DRAWINGS

[0069] One or more embodiments are exemplarily described by pictures in the corresponding drawings, and these exemplified descriptions do not constitute limitations on the embodiments. Elements with the same reference numerals in the drawings represent similar elements, and unless otherwise stated, the figures in the drawings do not constitute proportional limitations.

[0070] Figure 1 It is a flow chart of a method for controlling traffic of an elastic IP of a public cloud platform provided by an embodiment of the present disclosure;

[0071] Figure 2 is a flow chart of a method for controlling traffic of an elastic IP of a public cloud platform provided by another embodiment of the present disclosure;

[0072] Figure 3 is a flow chart of a method for controlling traffic of an elastic IP of a public cloud platform provided by another embodiment of the present disclosure;

[0073] Figure 4 is a flow chart of a method for controlling traffic of an elastic IP of a public cloud platform provided by another embodiment of the present disclosure;

[0074] Figure 5 is a flow chart of a method for controlling traffic of an elastic IP of a public cloud platform provided by another embodiment of the present disclosure;

[0075] Figure 6is a flow chart of a method for controlling traffic of an elastic IP of a public cloud platform provided by another embodiment of the present disclosure;

[0076] Figure 7 It is an interactive flow chart of a traffic control method of a public cloud platform elastic IP provided by another embodiment of the present disclosure;

[0077] Figure 8 It is an interactive flow chart of a traffic control method of a public cloud platform elastic IP provided by another embodiment of the present disclosure;

[0078] Fig. 9 is a schematic diagram of a flow chart of address conversion performed by a second gateway provided by another embodiment of the present disclosure;

[0079] Fig.10 It is a structural schematic diagram of a traffic control device for elastic IP of a public cloud platform provided by another embodiment of the present disclosure;

[0080] Fig.11 It is a structural schematic diagram of a traffic control device for elastic IP of a public cloud platform provided by another embodiment of the present disclosure;

[0081] Fig.12 It is a structural schematic diagram of a traffic control system of a public cloud platform elastic IP provided by another embodiment of the present disclosure;

[0082] Fig.13 It is a system structure diagram of a traffic control system of a public cloud platform elastic IP provided by another embodiment of the present disclosure;

[0083] Fig.14 It is a topology diagram of a traffic control system of a public cloud platform elastic IP provided by another embodiment of the present disclosure;

[0084] Fig.15 It is a schematic structural diagram of an electronic device provided by another embodiment of the present disclosure. DETAILED DESCRIPTION

[0085] In order to make the purpose, technical scheme and advantages of the embodiments of the present disclosure clearer, each embodiment of the present disclosure will be described in detail below in conjunction with the accompanying drawings. However, it will be appreciated by those skilled in the art that in each embodiment of the present disclosure, many technical details are proposed in order to enable 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 scheme claimed in the present application can be implemented. The division of the following embodiments is for the convenience of description and should not constitute any limitation on the specific implementation of the present disclosure. The various embodiments can be combined and referenced with each other without contradiction.

[0086] One embodiment of the present disclosure relates to a method for controlling traffic of an elastic IP of a public cloud platform, which is applied to a first gateway for communicating between a public cloud platform and a public network gateway. The process is as follows: Figure 1 As shown, including:

[0087] Step 101: receive a first message sent by the public network gateway, and obtain a destination IP address carried by the first message, wherein the destination IP address is a first elastic IP address.

[0088] Specifically, the first gateway can access the Internet and establish a network connection with the public network gateway to achieve communication with the public network gateway through the Internet. The first elastic IP address can be a public IP address purchased by the user from the public cloud service provider. The user binds the purchased first elastic IP address to the virtual terminal on the public cloud platform, so that the virtual terminal can communicate with the Internet using the first elastic IP address as the public IP address.

[0089] Step 102: determine, based on a pre-generated first traffic control policy, whether the traffic of the first message exceeds the inbound speed limit value of the first elastic IP address, and obtain a first judgment result, wherein the first traffic control policy is used to set each inbound speed limit value of each elastic IP address, and each inbound speed limit value is determined according to the bandwidth of each elastic IP address and the number of the first gateways.

[0090] Specifically, when using each elastic IP address, the user needs to configure the bandwidth of each elastic IP address. After the configuration is completed, the first traffic control strategy can set the inbound speed limit value of each first gateway for each elastic IP address according to the bandwidth of each elastic IP address and the number of first gateways. In addition, in order to make the traffic passing through each first gateway more stable, the number of first gateways can be set to an even number.

[0091] It should be noted that when the first message as an inbound message passes through each first gateway with the same probability through the equal-cost multi-path routing method, the inbound speed limit values ​​of each first gateway for the same elastic IP address can be the same. For example, assuming that there are N first gateways, N is a positive integer greater than 1, and the bandwidth of the first elastic IP address is X Mbps, then the bandwidth of the first elastic IP address X Mbps can be evenly distributed among the N first gateways, so that the inbound speed limit value of each first gateway for the first elastic IP address is X / N Mbps, thereby controlling the traffic of the first elastic IP address in an average speed limit manner.

[0092] Of course, the inbound rate limits of the first gateways for the same elastic IP address may also be different, as long as the sum of the inbound rate limits of the same elastic IP address is equal to the bandwidth of the elastic IP address. This embodiment does not limit this.

[0093] Step 103: If the first judgment result is that the traffic of the first message does not exceed the inbound rate limit of the first elastic IP address, the first message is sent to the second gateway so that the second gateway processes the first message according to the preset correspondence between each elastic IP address and each intranet IP address.

[0094] Specifically, since the IP address of each virtual terminal bound to each elastic IP address is an intranet IP address, when the user binds each elastic IP address to each virtual terminal, he actually binds each elastic IP address to the intranet IP address of each virtual terminal, thereby determining the correspondence between each elastic IP address and each intranet IP address. When receiving the first message with the first elastic IP address as the destination IP address, the second gateway can forward the first message to the virtual terminal where the intranet IP address corresponding to the first elastic IP address is located according to the correspondence between each elastic IP address and each intranet IP address.

[0095] Compared with the prior art, the disclosed implementation mode adopts a two-layer gateway design, implements the flow control function of the elastic IP address through the first gateway, and implements the address translation function of the elastic IP address through the second gateway, realizes the separate setting of the flow control function and the address translation function, facilitates the management of each gateway node, and can effectively improve the working efficiency of the gateway node; after receiving the first message, i.e., the inbound message sent by the public network gateway, the first gateway can determine whether the flow of the first message exceeds the inbound speed limit value of the first elastic IP address according to the first elastic IP address corresponding to the first message and the pre-generated first flow control policy, and When the inbound speed limit value does not exceed the inbound speed limit value of the first elastic IP address, the first message is sent to the second gateway, so that the second gateway can send the first message to the terminal where the intranet IP address corresponding to the first elastic IP address is located according to the correspondence between each elastic IP address and each intranet IP address, thereby achieving the purpose of controlling the traffic of the elastic IP; the first traffic control strategy is used to set each inbound speed limit value of each elastic IP address, and each inbound speed limit value is determined according to the bandwidth of each elastic IP address and the number of first gateways, so that the inbound speed limit values ​​can be set for different elastic IP addresses respectively, realizing personalized control of the traffic of multiple elastic IP addresses.

[0096] Another embodiment of the present invention relates to a method for controlling traffic of an elastic IP of a public cloud platform. Figure 1 The traffic control method of the public cloud platform elastic IP involved in one embodiment of the present disclosure is basically the same, the difference is that, Figure 2 As shown, it may also include:

[0097] Step 201: Receive a second message sent by the second gateway, and obtain a source IP address carried by the second message, wherein the source IP address is a second elastic IP address.

[0098] Specifically, in this step, the second elastic IP address may be the same as the first elastic IP address, or may be different from the first elastic IP address, and this embodiment does not limit this.

[0099] Step 202: According to a pre-generated second traffic control policy, the second message is sent to the egress control gateway of the second elastic IP address, so that the egress control gateway sends the second message to the public network gateway when the traffic of the second message does not exceed the egress speed limit value of the second elastic IP address, wherein the second traffic control policy is used to set each egress control gateway and each egress speed limit value of each elastic IP address, and each egress control gateway is determined according to preset rules.

[0100] Specifically, the first gateway receiving the second message may be the outbound control gateway of the second elastic IP address, or may not be the outbound control gateway of the second elastic IP address.

[0101] When the first gateway receiving the second message is the outbound control gateway of the second elastic IP address, the first gateway can directly determine whether the traffic of the second message exceeds the outbound rate limit of the second elastic IP address, and send the second message to the public network gateway when the traffic of the second message does not exceed the outbound rate limit of the second elastic IP address.

[0102] When the first gateway receiving the second message is not the egress control gateway of the second elastic IP address, the first gateway can use the unique identity information of the second elastic IP address through a hash algorithm or other algorithms to find out the egress control gateway of the second elastic IP address, and send the second message to the egress control gateway of the second elastic IP address. Determining the egress control gateway of each elastic IP address through a hash algorithm or other algorithms can avoid the tediousness of manually setting each egress control gateway and the conflicts and errors that may be caused by manual settings, thereby improving the flexibility of traffic control of elastic IP addresses.

[0103] It should be noted that since the outbound messages of each elastic IP address can be sent to the public network gateway by the outbound control gateway of each elastic IP address, the outbound speed limit value of each elastic IP address on its corresponding outbound control gateway can be set to the bandwidth of each elastic IP address, thereby controlling the traffic of each elastic IP address in a single-point speed limit manner.

[0104] It should be noted that this embodiment does not limit the specific execution locations of step 201 and step 202. For example, step 201 and step 202 may be before step 101 or after step 103, and each case will not be described one by one here.

[0105] By receiving the second message, i.e., the outbound message, carrying the second elastic IP address, sent by the second gateway, and sending the second message to the outbound control gateway of the second elastic IP address determined by the second flow control policy, the outbound control gateway can perform flow control on the second message according to the outbound speed limit value of the second elastic IP address determined by the second flow control policy, thereby realizing flow control of the outbound message of the elastic IP address in a single-point speed limit manner.

[0106] Another embodiment of the present invention relates to a method for controlling traffic of an elastic IP of a public cloud platform. Figure 1 The traffic control method of the public cloud platform elastic IP involved in one embodiment of the present disclosure is basically the same, the difference is that, Figure 3 As shown, it may also include:

[0107] Step 301: Receive multiple messages sent by the public network gateway, and obtain the destination IP addresses respectively carried by the multiple messages, wherein the destination IP addresses are elastic IP addresses.

[0108] Step 302: Determine whether the bandwidth of the first gateway is less than the sum of the traffic of the multiple messages, and obtain a second determination result.

[0109] In this step, since the bandwidth of the first gateway may be greater than or equal to the sum of the traffic of multiple inbound messages, or may be less than the sum of the traffic of multiple inbound messages, and the first gateway cannot send multiple inbound messages to the second gateway at the same time when its bandwidth is less than the sum of the traffic of multiple inbound messages, after receiving multiple inbound messages, it is necessary to judge whether the bandwidth of the first gateway is less than the sum of the traffic of multiple inbound messages.

[0110] Step 303: If the second judgment result is that the bandwidth of the first gateway is less than the sum of the traffic of the multiple messages, then according to the pre-set priority information of each elastic IP address, the first traffic control strategy is used to process the multiple messages in order of priority.

[0111] Specifically, the priority information of each elastic IP address can be pre-set by the user or the public cloud service provider, or dynamically adjusted during the use of each elastic IP address. This embodiment does not limit this, as long as each elastic IP address is set to a high or low priority.

[0112] It should be noted that this embodiment does not limit the specific execution location of step 301 to step 303. For example, step 301 to step 303 can be before step 101 or after step 103, and each case will not be described one by one here.

[0113] When the bandwidth of the first gateway is less than the sum of the traffic of multiple inbound messages, the first traffic control strategy is used to process multiple inbound messages in order of priority of the elastic IP address carried by each inbound message. When the first gateway cannot transmit multiple inbound messages at the same time, the multiple inbound messages can be transmitted separately in order of priority, thereby realizing control of the inbound traffic of the elastic IP address according to priority.

[0114] Another embodiment of the present invention relates to a method for controlling traffic of an elastic IP of a public cloud platform. Figure 2 The traffic control method of the public cloud platform elastic IP involved in one embodiment of the present disclosure is basically the same, the difference is that, Figure 4 As shown, it may also include:

[0115] Step 401: Receive multiple messages sent by the second gateway, and obtain source IP addresses respectively carried in the multiple messages, wherein the source IP addresses are elastic IP addresses.

[0116] Step 402: Determine whether the bandwidth of the first gateway is less than the sum of the traffic of the multiple messages, and obtain a third determination result.

[0117] In this step, since the bandwidth of the first gateway may be greater than or equal to the sum of the traffic of multiple outgoing messages, or may be less than the sum of the traffic of multiple outgoing messages, and the first gateway cannot send multiple outgoing messages to the public network gateway at the same time when its bandwidth is less than the sum of the traffic of multiple outgoing messages, after receiving multiple outgoing messages, it is necessary to judge whether the bandwidth of the first gateway is less than the sum of the traffic of multiple outgoing messages.

[0118] Step 403: If the third judgment result is that the bandwidth of the first gateway is less than the sum of the traffic of the multiple messages, then according to the pre-set priority information of each elastic IP address, the second traffic control strategy is used to process the multiple messages in order of priority.

[0119] It should be noted that this embodiment does not limit the specific execution location of steps 401 to 403. For example, steps 401 to 403 may be before step 101, or after step 103, or before step 201, or after step 202, and each case will not be described one by one here.

[0120] When the bandwidth of the first gateway is less than the sum of the traffic of multiple outbound messages, the second traffic control strategy is used to process multiple outbound messages in order of priority of the elastic IP address carried by each outbound message. When the first gateway cannot transmit multiple outbound messages at the same time, the multiple outbound messages can be transmitted separately in order of priority, thereby realizing control of the outbound traffic of the elastic IP address according to priority.

[0121] Another embodiment of the present disclosure relates to a traffic control method for an elastic IP of a public cloud platform, which is applied to a second gateway for the public cloud platform to communicate with a first gateway. The process is as follows: Figure 5 As shown, including:

[0122] After the first gateway controls the flow of the first message according to the pre-generated first flow control strategy:

[0123] Step 501: Receive the first message sent by the first gateway, and obtain the destination IP address carried by the first message, wherein the destination IP address is a first elastic IP address.

[0124] Step 502: Based on the preset correspondence between each elastic IP address and each intranet IP address, determine whether there is a first intranet IP address corresponding to the first elastic IP address, and obtain a fourth determination result.

[0125] Specifically, the correspondence between each elastic IP address and each intranet IP address may be preset by a user or a public cloud service provider, or dynamically adjusted during the use of each elastic IP address, and this embodiment does not limit this.

[0126] Step 503: If the fourth judgment result is that there is a first intranet IP address corresponding to the first elastic IP address, obtain the first intranet IP address and convert the destination IP address of the first message into the first intranet IP address.

[0127] Step 504: Send the first message after address conversion to the terminal corresponding to the first intranet IP address.

[0128] Specifically, the terminal corresponding to the intranet IP address may be a virtual machine on the public cloud, and each virtual machine uniquely corresponds to its intranet IP address.

[0129] Compared with the prior art, the disclosed implementation adopts a two-layer gateway design, in which the first gateway uses a first flow control strategy to control the incoming traffic of the elastic IP address, and the second gateway implements the address conversion of the incoming message of the elastic IP address, thereby realizing the separation of the flow control function and the address conversion function in the downlink direction of data, facilitating the management of each gateway node, and effectively improving the working efficiency of the gateway node.

[0130] Another embodiment of the present invention relates to a method for controlling traffic of an elastic IP of a public cloud platform. Figure 5 The traffic control method of the public cloud platform elastic IP involved in one embodiment of the present disclosure is basically the same, the difference is that, Figure 6 As shown, it may also include:

[0131] Step 601: Receive a second message sent by the terminal, and obtain a source IP address carried in the second message, wherein the source IP address is a second intranet IP address.

[0132] Step 602: Based on the preset correspondence between each elastic IP address and each intranet IP address, determine whether there is a second elastic IP address corresponding to the second intranet IP address, and obtain a fifth determination result.

[0133] In this step, since some intranet IP addresses may not be bound to the elastic IP address, the terminals corresponding to these intranet IP addresses cannot access the Internet using the elastic IP address as the public IP address. Therefore, when the second gateway receives an outbound message carrying the intranet IP address, it needs to determine whether the intranet IP address in the outbound message has been bound to the elastic IP address.

[0134] Step 603: If the fifth judgment result is that there is a second elastic IP address corresponding to the second intranet IP address, the second elastic IP address is obtained, and the source IP address of the second message is converted into the second elastic IP address.

[0135] Specifically, when there is a second elastic IP address corresponding to the second intranet IP address, the second elastic IP address is used as the source IP address of the second message, so that the terminal can communicate with the Internet.

[0136] Step 604: Send the second message after address translation to the first gateway, so that the first gateway controls the flow of the second message after address translation according to a pre-generated second flow control policy.

[0137] It should be noted that this embodiment does not limit the specific execution location of step 601 to step 604. For example, step 601 to step 604 may be before step 501 or after step 504, and each case will not be described one by one here.

[0138] By converting the source IP address of the second message from the intranet IP address to the corresponding elastic IP address, the first gateway can use the second flow control strategy to control the flow of outgoing messages of the elastic IP address, thereby realizing the separation of the flow control function and the address conversion function in the data uplink direction, facilitating the management of each gateway node, and effectively improving the working efficiency of the gateway node.

[0139] In order to enable those skilled in the art to more clearly understand the traffic control method of the public cloud platform elastic IP disclosed in the above embodiment of the present disclosure, the following is explained using the data downlink direction and the data uplink direction as examples.

[0140] In the data downlink direction, such as Figure 7 As shown, another embodiment of the present disclosure provides a method for controlling traffic of an elastic IP of a public cloud platform, including:

[0141] Step 701: The public network gateway sends a first message to a first gateway, wherein the destination IP address of the first message is a first elastic IP address.

[0142] Step 702: The first gateway determines whether the traffic of the first message exceeds the inbound rate limit of the first elastic IP address according to the pre-generated first traffic control policy, and obtains a determination result A.

[0143] Step 703: When the judgment result A is that the traffic of the first message does not exceed the inbound rate limit of the first elastic IP address, the first gateway sends the first message to the second gateway.

[0144] Step 704: The second gateway determines whether there is a first intranet IP address corresponding to the first elastic IP address based on the preset correspondence between each elastic IP address and each intranet IP address, and obtains a determination result B.

[0145] Step 705: When the judgment result B is that there is a first intranet IP address corresponding to the first elastic IP address, the second gateway obtains the first intranet IP address and converts the destination IP address of the first message into the first intranet IP address.

[0146] Step 706: The second gateway sends the first message after address conversion to the terminal corresponding to the first intranet IP address.

[0147] In the data uplink direction, such as Figure 8As shown, another embodiment of the present disclosure provides a method for controlling traffic of an elastic IP of a public cloud platform, including:

[0148] Step 801: The terminal sends a second message to a second gateway, wherein the source IP address of the second message is a second intranet IP address corresponding to the terminal.

[0149] Step 802: The second gateway determines whether there is a second elastic IP address corresponding to the second intranet IP address based on the preset correspondence between each elastic IP address and each intranet IP address, and obtains a determination result C.

[0150] Step 803: When the judgment result C is that there is a second elastic IP address corresponding to the second intranet IP address, the second gateway obtains the second elastic IP address and converts the source IP address of the second message into the second elastic IP address.

[0151] Step 804: The second gateway sends the second message after the address conversion to the first gateway.

[0152] Step 805: The first gateway sends the second message after address conversion to the outbound control gateway of the second elastic IP address among the multiple first gateways according to the pre-generated second traffic control policy.

[0153] Step 806: When the traffic of the second message after address conversion does not exceed the outbound rate limit value of the second elastic IP address, the outbound control gateway of the second elastic IP address among the multiple first gateways sends the second message after address conversion to the public network gateway.

[0154] For example, Fig. 9As shown, assuming that the intranet IP address corresponding to a terminal is 10.20.30.40, and the elastic IP address corresponding to the intranet IP address is 119.100.50.30, the terminal can communicate with the Internet using the elastic IP address 119.100.50.30 as the public IP address. For example, the IP address in the Internet can be 8.8.8.8. In the downstream direction of data, when the destination IP address carried in the inbound message sent by the IP address 8.8.8.8 in the Internet is the elastic IP address 119.100.50.30, the source IP address of the inbound message is 8.8.8.8. After the first gateway performs flow control on the inbound message according to the first flow control policy and sends the inbound message to the second gateway, the second gateway performs destination address translation on the inbound message, translates the destination IP address of the inbound message into the intranet IP address 10.20.30.40 corresponding to the elastic IP address 119.100.50.30, and sends the inbound message after the address translation to the terminal corresponding to the intranet IP address 10.20.30.40. In the upstream direction of data, when the second gateway receives an outbound message sent by the terminal corresponding to the intranet IP address 10.20.30.40, requesting to access the IP address 8.8.8.8 on the Internet, the source IP address of the outbound message is 10.20.30.40, and the destination IP address is 8.8.8.8. At this time, the second gateway performs source address translation on the outbound message, converts the source IP address of the outbound message from the intranet IP address 10.20.30.40 to the elastic IP address 119.100.50.30 corresponding to the intranet IP address 10.20.30.40, and sends the outbound message after the address translation to the first gateway, so that the first gateway performs flow control on the outbound message according to the second flow control policy.

[0155] Another embodiment of the present disclosure relates to a traffic control device for an elastic IP of a public cloud platform, such as Fig.10 As shown, including:

[0156] The first receiving module 1001 is used to receive a first message sent by the public network gateway, and obtain a destination IP address carried in the first message, wherein the destination IP address is a first elastic IP address.

[0157] The first judgment module 1002 is used to determine whether the traffic of the first message exceeds the inbound speed limit value of the first elastic IP address according to a pre-generated first traffic control policy, and obtain a first judgment result, wherein the first traffic control policy is used to set each inbound speed limit value of each elastic IP address, and each inbound speed limit value is determined according to the bandwidth of each elastic IP address and the number of the first gateways.

[0158] The first sending module 1003 is used to send the first message to the second gateway when the first judgment result is that the traffic of the first message does not exceed the inbound rate limit value of the first elastic IP address, so that the second gateway processes the first message according to the preset correspondence between each elastic IP address and each intranet IP address.

[0159] Another embodiment of the present invention relates to a traffic control device for an elastic IP of a public cloud platform. Fig.10 The traffic control device of the elastic IP of the public cloud platform involved in one embodiment of the present disclosure shown is basically the same, and the difference is that:

[0160] The first receiving module 1001 is further used to receive a second message sent by the second gateway, and obtain a source IP address carried by the second message, wherein the source IP address is a second elastic IP address;

[0161] The first sending module 1003 is also used to send the second message to the egress control gateway of the second elastic IP address according to a pre-generated second traffic control strategy, so that the egress control gateway sends the second message to the public network gateway when the traffic of the second message does not exceed the egress speed limit value of the second elastic IP address, wherein the second traffic control strategy is used to set each egress control gateway and each egress speed limit value of each elastic IP address, and each egress control gateway is determined according to a preset rule.

[0162] Another embodiment of the present invention relates to a traffic control device for an elastic IP of a public cloud platform. Fig.10 The traffic control device of the elastic IP of the public cloud platform involved in one embodiment of the present disclosure shown is basically the same, and the difference is that:

[0163] The first receiving module 1001 is further used to receive multiple messages sent by the public network gateway, and obtain the destination IP addresses respectively carried by the multiple messages, wherein the destination IP addresses are elastic IP addresses;

[0164] The first judgment module 1002 is also used to judge whether the bandwidth of the first gateway is less than the sum of the traffic of the multiple messages, and obtain a second judgment result; if the second judgment result is that the bandwidth of the first gateway is less than the sum of the traffic of the multiple messages, then according to the pre-set priority information of each elastic IP address, the first traffic control strategy is used in turn to process the multiple messages in order of priority.

[0165] Another embodiment of the present invention relates to a traffic control device for an elastic IP of a public cloud platform. Fig.10The traffic control device of the elastic IP of the public cloud platform involved in one embodiment of the present disclosure shown is basically the same, and the difference is that:

[0166] The first receiving module 1001 is further used to receive multiple messages sent by the second gateway, and obtain each source IP address carried by the multiple messages, wherein each source IP address is a respective elastic IP address;

[0167] The first judgment module 1002 is also used to judge whether the bandwidth of the first gateway is less than the sum of the traffic of the multiple messages, and obtain a third judgment result; if the third judgment result is that the bandwidth of the first gateway is less than the sum of the traffic of the multiple messages, then according to the pre-set priority information of each elastic IP address, the second traffic control strategy is used in order of priority to process the multiple messages.

[0168] Another embodiment of the present disclosure relates to a traffic control device for an elastic IP of a public cloud platform, such as Fig.11 As shown, the device includes a second receiving module 1101, a second judging module 1102, an address conversion module 1103 and a second sending module 1104, wherein:

[0169] After the first gateway controls the flow of the first message according to the pre-generated first flow control strategy:

[0170] The second receiving module 1101 is used to receive the first message sent by the first gateway, and obtain the destination IP address carried by the first message, wherein the destination IP address is a first elastic IP address;

[0171] The second judgment module 1102 is used to judge whether there is a first intranet IP address corresponding to the first elastic IP address according to the preset correspondence between each elastic IP address and each intranet IP address, and obtain a fourth judgment result;

[0172] The address conversion module 1103 is used to obtain the first intranet IP address and convert the destination IP address of the first message into the first intranet IP address when the fourth judgment result is that there is a first intranet IP address corresponding to the first elastic IP address;

[0173] The second sending module 1104 is used to send the first message after address conversion to the terminal corresponding to the first intranet IP address.

[0174] Another embodiment of the present invention relates to a traffic control device for an elastic IP of a public cloud platform. Fig.11 The traffic control device of the elastic IP of the public cloud platform involved in one embodiment of the present disclosure shown is basically the same, and the difference is that:

[0175] The second receiving module 1101 is further configured to receive a second message sent by the terminal, and obtain a source IP address carried by the second message, wherein the source IP address is a second intranet IP address;

[0176] The second judgment module 1102 is further used to judge whether there is a second elastic IP address corresponding to the second intranet IP address according to the preset correspondence between each elastic IP address and each intranet IP address, and obtain a fifth judgment result;

[0177] The address conversion module 1103 is further configured to, when the fifth judgment result is that there is a second elastic IP address corresponding to the second intranet IP address, obtain the second elastic IP address and convert the source IP address of the second message into the second elastic IP address;

[0178] The second sending module 1104 is further configured to send the second message after address conversion to the first gateway, so that the first gateway controls the flow of the second message after address conversion according to a pre-generated second flow control strategy.

[0179] The specific implementation method of the traffic control device of the public cloud platform elastic IP provided in the above implementation mode can be referred to the traffic control method of the public cloud platform elastic IP provided in the embodiment of the present disclosure, which will not be repeated here.

[0180] Another embodiment of the present disclosure relates to a traffic control system for an elastic IP of a public cloud platform, such as Fig.12 As shown, the system includes a first gateway 1201 and a second gateway 1202 applied to the public cloud platform to communicate with the public network gateway, wherein:

[0181] The first gateway 1201 is used to receive the first message sent by the public network gateway, and obtain the destination IP address carried by the first message, wherein the destination IP address is a first elastic IP address;

[0182] According to a pre-generated first flow control strategy, determine whether the flow of the first message exceeds the inbound speed limit value of the first elastic IP address, and obtain a first judgment result, wherein the first flow control strategy determines the inbound speed limit value of each elastic IP address according to the bandwidth of each elastic IP address and the number of the first gateways;

[0183] If the first judgment result is that the traffic of the first message does not exceed the inbound rate limit of the first elastic IP address, the first message is sent to the second gateway, so that the second gateway 1202 processes the first message according to the preset correspondence between each elastic IP address and each intranet IP address;

[0184] After the first gateway 1201 controls the flow of the first message according to the first flow control strategy:

[0185] The second gateway 1202 is used to receive the first message and obtain the destination IP address, wherein the destination IP address is the first elastic IP address;

[0186] According to the preset correspondence between each elastic IP address and each intranet IP address, determine whether there is a first intranet IP address corresponding to the first elastic IP address, and obtain a determination result;

[0187] If the judgment result is that there is a first intranet IP address corresponding to the first elastic IP address, the first intranet IP address is obtained, and the destination IP address of the first message is converted to the first intranet IP address;

[0188] The first message after address conversion is sent to the terminal corresponding to the first intranet IP address.

[0189] It should be noted that, in the above implementation, the first gateway, the second gateway and the terminal can all be set at the data layer. Fig.13 As shown, in the data layer, the terminal is communicated with the second gateway, the second gateway is communicated with the first gateway, the first gateway performs traffic control on each elastic IP address, and the second gateway performs address conversion on the message carrying each elastic IP address according to the correspondence between each elastic IP address and each intranet IP address.

[0190] The first flow control strategy, the second flow control strategy, the priority information of each elastic IP address, and the correspondence between each elastic IP address and each intranet IP address can also be set through the control layer that is connected to the data layer in communication.

[0191] For example, Fig.13As shown, the control layer may include an elastic IP object, a terminal object, and a first gateway object. The elastic IP object can configure the bandwidth and priority information of each elastic IP address, and after the configuration is completed, the priority information of each elastic IP address is sent to the first gateway. The elastic IP object can also bind each elastic IP address to each intranet IP address, establish a corresponding relationship between each elastic IP address and each intranet IP address, and send the corresponding relationship to the second gateway, so that the second gateway performs address conversion according to the corresponding relationship between each elastic IP address and each intranet IP address. The terminal object can configure the intranet IP address of each terminal, establish a corresponding relationship between each intranet IP address and each terminal, and send the corresponding relationship to the terminal and the second gateway, so that the terminal and the second gateway communicate using the intranet IP address. The first gateway object can set each inbound speed limit value of each elastic IP address in the first flow control strategy, each outbound control gateway and each outbound speed limit value of each elastic IP address in the second flow control strategy, and send the set elastic IP addresses and their inbound speed limit values, outbound control gateways, and outbound speed limit values ​​to the first gateway. The first gateway object can also send the outbound control gateways of each elastic IP address in the second traffic control policy to the second gateway, so that after completing the address conversion, the second gateway can send the message carrying the elastic IP address directly to the outbound control gateway of the elastic IP address.

[0192] It should be noted that the first gateway and the second gateway may form a network topology structure. In the network topology structure, the first gateway may be connected to the Internet through an external network switch, and the first gateway and the second gateway may communicate with the physical network through an internal network switch.

[0193] For example, in Fig.14 In the network topology shown, two of the four groups of first gateways can be connected to the same external network switch and the same internal network switch. Two of the four groups of second gateways can be connected to the same internal network switch. The internal network switch connected to the second gateway and the internal network switch connected to the first gateway can be connected through a physical network. The physical network can include bridges S1 and S2 to process messages with elastic IP addresses in different network segments respectively. For example, in Fig.14In the figure, it is assumed that the intranet switch 11, the intranet switch 21 and the bridge S1 are used to process the message of the elastic IP address segment 10.23.0.10 / 32, and the intranet switch 12, the intranet switch 22 and the bridge S2 are used to process the message of the elastic IP address segment 10.23.0.12 / 31. When the bridge S1 receives the message carrying the elastic IP address 10.23.0.10 sent by the intranet switch 11, it will give priority to sending the message to the intranet switch 21. Similarly, when the bridge S2 receives the message carrying the elastic IP address 10.23.0.12 sent by the intranet switch 12, it will give priority to sending the message to the intranet switch 22, thereby realizing the separate processing of the messages of the elastic IP addresses in different segments and improving the load balancing.

[0194] Another embodiment of the present disclosure relates to an electronic device, such as Fig.15 As shown, including:

[0195] at least one processor 1501; and,

[0196] A memory 1502 is communicatively connected to the at least one processor 1501; wherein,

[0197] The memory 1502 stores instructions that can be executed by the at least one processor 1501. The instructions are executed by the at least one processor 1501 so that the at least one processor 1501 can execute the method described in the above embodiment of the present disclosure.

[0198] Among them, the memory and the processor are connected in a bus manner, and the bus may include any number of interconnected buses and bridges, and the bus connects various circuits of one or more processors and memories together. The bus can also connect various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface between the bus and the transceiver. The transceiver can be one element or multiple elements, such as multiple receivers and transmitters, providing a unit for communicating with various other devices on a transmission medium. The data processed by the processor is transmitted on a wireless medium via an antenna, and further, the antenna also receives data and transmits the data to the processor.

[0199] The processor is responsible for managing the bus and general processing, and can also provide various functions, including timing, peripheral interfaces, voltage regulation, power management, and other control functions. Memory can be used to store data used by the processor when performing operations.

[0200] Another embodiment of the present disclosure relates to a computer-readable storage medium storing a computer program, which implements the above method embodiment when executed by a processor.

[0201] That is, those skilled in the art can understand that all or part of the steps in the above-mentioned embodiment method can be completed by instructing the relevant hardware through a program, and the program is stored in a storage medium, including several instructions to enable a device (which can be a single-chip microcomputer, chip, etc.) or a processor to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk and other media that can store program codes.

[0202] Those skilled in the art will appreciate that the above-mentioned embodiments are specific examples for implementing the present disclosure, and in actual applications, various changes may be made thereto in form and detail without departing from the spirit and scope of the present disclosure.

Claims

1. A method for controlling the flow of elastic IP of a public cloud platform, applied to a first gateway for the public cloud platform to communicate with a public network gateway, It is characterized in that The method comprises: Receive a first message sent by the public network gateway, and obtain a destination IP address carried by the first message, wherein the destination IP address is a first elastic IP address; According to a pre-generated first flow control strategy, determine whether the flow of the first message exceeds the inbound speed limit value of the first elastic IP address, and obtain a first judgment result, wherein the first flow control strategy is used to set each inbound speed limit value of each elastic IP address, and each inbound speed limit value is determined according to the bandwidth of each elastic IP address and the number of the first gateways; If the first judgment result is that the traffic of the first message does not exceed the inbound rate limit of the first elastic IP address, the first message is sent to the second gateway so that the second gateway processes the first message according to the preset correspondence between each elastic IP address and each intranet IP address.

2. The method according to claim 1, It is characterized in that The method further comprises: Receive a second message sent by the second gateway, and obtain a source IP address carried by the second message, wherein the source IP address is a second elastic IP address; According to a pre-generated second traffic control policy, the second message is sent to the egress control gateway of the second elastic IP address, so that the egress control gateway sends the second message to the public network gateway when the traffic of the second message does not exceed the egress speed limit value of the second elastic IP address, wherein the second traffic control policy is used to set each egress control gateway and each egress speed limit value of each elastic IP address, and each egress control gateway is determined according to a preset rule.

3. The method according to claim 1, It is characterized in that The method further comprises: Receive multiple messages sent by the public network gateway, and obtain destination IP addresses respectively carried by the multiple messages, wherein the destination IP addresses are elastic IP addresses; Determine whether the bandwidth of the first gateway is less than the sum of the traffic of the multiple messages, and obtain a second determination result; If the second judgment result is that the bandwidth of the first gateway is less than the sum of the traffic of the multiple messages, then according to the pre-set priority information of each elastic IP address, the first traffic control strategy is used to process the multiple messages in order of priority.

4. The method according to claim 2, It is characterized in that The method further comprises: Receive multiple messages sent by the second gateway, and obtain source IP addresses respectively carried by the multiple messages, wherein the source IP addresses are elastic IP addresses; Determine whether the bandwidth of the first gateway is less than the sum of the traffic of the multiple messages, and obtain a third determination result; If the third judgment result is that the bandwidth of the first gateway is less than the sum of the traffic of the multiple messages, then according to the pre-set priority information of each elastic IP address, the second traffic control strategy is used to process the multiple messages in order of priority.

5. A method for controlling the flow of elastic IP of a public cloud platform, applied to a second gateway for the public cloud platform to communicate with a first gateway, It is characterized in that The method comprises: After the first gateway controls the flow of the first message according to the pre-generated first flow control strategy: Receive the first message sent by the first gateway, and obtain the destination IP address carried by the first message, wherein the destination IP address is a first elastic IP address; According to the preset correspondence between each elastic IP address and each intranet IP address, determine whether there is a first intranet IP address corresponding to the first elastic IP address, and obtain a fourth determination result; If the fourth judgment result is that there is a first intranet IP address corresponding to the first elastic IP address, then obtaining the first intranet IP address, and converting the destination IP address of the first message into the first intranet IP address; The first message after address conversion is sent to the terminal corresponding to the first intranet IP address.

6. The method according to claim 5, It is characterized in that The method further comprises: Receive a second message sent by the terminal, and obtain a source IP address carried by the second message, wherein the source IP address is a second intranet IP address; According to the preset correspondence between each elastic IP address and each intranet IP address, determine whether there is a second elastic IP address corresponding to the second intranet IP address, and obtain a fifth judgment result; If the fifth judgment result is that there is a second elastic IP address corresponding to the second intranet IP address, obtaining the second elastic IP address, and converting the source IP address of the second message into the second elastic IP address; The second message after address conversion is sent to the first gateway, so that the first gateway controls the flow of the second message after address conversion according to a pre-generated second flow control policy.

7. A traffic control device for elastic IP of a public cloud platform, It is characterized in that The device comprises: A first receiving module, used to receive a first message sent by the public network gateway, and obtain a destination IP address carried by the first message, wherein the destination IP address is a first elastic IP address; A first judgment module is used to judge whether the flow of the first message exceeds the inbound speed limit value of the first elastic IP address according to a pre-generated first flow control policy, and obtain a first judgment result, wherein the first flow control policy is used to set each inbound speed limit value of each elastic IP address, and each inbound speed limit value is determined according to the bandwidth of each elastic IP address and the number of the first gateways; The first sending module is used to send the first message to the second gateway when the first judgment result is that the traffic of the first message does not exceed the inbound rate limit value of the first elastic IP address, so that the second gateway processes the first message according to the preset correspondence between each elastic IP address and each intranet IP address.

8. The device according to claim 7, It is characterized in that The first receiving module is further used to receive a second message sent by the second gateway, and obtain a source IP address carried by the second message, wherein the source IP address is a second elastic IP address; The first sending module is also used to send the second message to the egress control gateway of the second elastic IP address according to a pre-generated second traffic control strategy, so that the egress control gateway sends the second message to the public network gateway when the traffic of the second message does not exceed the egress speed limit value of the second elastic IP address, wherein the second traffic control strategy is used to set each egress control gateway and each egress speed limit value of each elastic IP address, and each egress control gateway is determined according to a preset rule.

9. The device according to claim 7, It is characterized in that The first receiving module is further used to receive multiple messages sent by the public network gateway, and obtain the destination IP addresses respectively carried by the multiple messages, wherein the destination IP addresses are elastic IP addresses; The first judgment module is further used to judge whether the bandwidth of the first gateway is less than the sum of the traffic of the multiple messages, and obtain a second judgment result; If the second judgment result is that the bandwidth of the first gateway is less than the sum of the traffic of the multiple messages, then according to the pre-set priority information of each elastic IP address, the first traffic control strategy is used to process the multiple messages in order of priority.

10. The device according to claim 8, It is characterized in that The first receiving module is further used to receive multiple messages sent by the second gateway, and obtain each source IP address carried by the multiple messages, wherein each source IP address is a respective elastic IP address; The first judgment module is further used to judge whether the bandwidth of the first gateway is less than the sum of the traffic of the multiple messages, and obtain a third judgment result; If the third judgment result is that the bandwidth of the first gateway is less than the sum of the traffic of the multiple messages, then according to the pre-set priority information of each elastic IP address, the second traffic control strategy is used to process the multiple messages in order of priority.

11. A traffic control device for elastic IP of a public cloud platform, It is characterized in that The device comprises a second receiving module, a second judging module, an address converting module and a second sending module, wherein: After the first gateway controls the flow of the first message according to the pre-generated first flow control strategy: The second receiving module is used to receive the first message sent by the first gateway, and obtain the destination IP address carried by the first message, wherein the destination IP address is a first elastic IP address; The second judgment module is used to judge whether there is a first intranet IP address corresponding to the first elastic IP address according to the preset correspondence between each elastic IP address and each intranet IP address, and obtain a fourth judgment result; The address conversion module is used to obtain the first intranet IP address and convert the destination IP address of the first message into the first intranet IP address when the fourth judgment result is that there is a first intranet IP address corresponding to the first elastic IP address; The second sending module is used to send the first message after address conversion to the terminal corresponding to the first intranet IP address.

12. The device according to claim 11, It is characterized in that The second receiving module is further used to receive a second message sent by the terminal, and obtain a source IP address carried by the second message, wherein the source IP address is a second intranet IP address; The second judgment module is further used to judge whether there is a second elastic IP address corresponding to the second intranet IP address according to the preset correspondence between each elastic IP address and each intranet IP address, and obtain a fifth judgment result; The address conversion module is further configured to, when the fifth judgment result is that there is a second elastic IP address corresponding to the second intranet IP address, obtain the second elastic IP address and convert the source IP address of the second message into the second elastic IP address; The second sending module is further used to send the second message after address conversion to the first gateway, so that the first gateway controls the flow of the second message after address conversion according to a pre-generated second flow control strategy.

13. A traffic control system for elastic IP of a public cloud platform. It is characterized in that The system includes a first gateway and a second gateway applied to a public cloud platform for communicating with a public network gateway, wherein: The first gateway is used to receive the first message sent by the public network gateway, and obtain the destination IP address carried by the first message, wherein the destination IP address is a first elastic IP address; According to a pre-generated first flow control strategy, determine whether the flow of the first message exceeds the inbound speed limit value of the first elastic IP address, and obtain a first judgment result, wherein the first flow control strategy determines the inbound speed limit value of each elastic IP address according to the bandwidth of each elastic IP address and the number of the first gateways; If the first judgment result is that the traffic of the first message does not exceed the inbound rate limit of the first elastic IP address, the first message is sent to the second gateway, so that the second gateway processes the first message according to the preset correspondence between each elastic IP address and each intranet IP address; After the first gateway controls the flow of the first message according to the first flow control policy: The second gateway is used to receive the first message and obtain the destination IP address, wherein the destination IP address is the first elastic IP address; According to the preset correspondence between each elastic IP address and each intranet IP address, determine whether there is a first intranet IP address corresponding to the first elastic IP address, and obtain a determination result; If the judgment result is that there is a first intranet IP address corresponding to the first elastic IP address, the first intranet IP address is obtained, and the destination IP address of the first message is converted to the first intranet IP address; The first message after address conversion is sent to the terminal corresponding to the first intranet IP address.

14. An electronic device, It is characterized in that include: at least one processor; as well as, a memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute the method according to any one of claims 1 to 4, or to execute the method according to claim 5 or 6.

15. A computer-readable storage medium storing a computer program, It is characterized in that When the computer program is executed by a processor, the method according to any one of claims 1 to 4 is implemented, or the method according to claim 5 or 6 can be implemented.