CN107800645B - Cloud host data sending, receiving and transmitting method and device - Google Patents
Cloud host data sending, receiving and transmitting method and device Download PDFInfo
- Publication number
- CN107800645B CN107800645B CN201610803755.4A CN201610803755A CN107800645B CN 107800645 B CN107800645 B CN 107800645B CN 201610803755 A CN201610803755 A CN 201610803755A CN 107800645 B CN107800645 B CN 107800645B
- Authority
- CN
- China
- Prior art keywords
- queue
- cloud host
- public network
- target queue
- information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/50—Queue scheduling
- H04L47/52—Queue scheduling by attributing bandwidth to queues
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/40—Support for services or applications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
Abstract
The invention provides a method and a device for sending, receiving and transmitting cloud host data, and relates to the field of cloud computing. The cloud host data receiving method comprises the following steps: acquiring destination address information of downlink flow of the cloud host, wherein the destination address information is public network address information of the cloud host; determining a target queue according to destination address information based on the corresponding relation between the queue and the public network address; and performing downlink transmission through the target queue based on the bandwidth limit of the target queue. By the method, the queue can be distributed for the downlink flow of the cloud host according to the destination address, and the limitation of the bandwidth of the downlink flow is realized by using the bandwidth limitation of the queue, so that the limitation of the downlink flow of the cloud host based on the public network address is realized, the network bandwidth is prevented from being occupied by individual users due to the fact that overlarge flow flows are gushed, and the stability of the cloud host is improved.
Description
Technical Field
The invention relates to the field of cloud computing, in particular to a method and a device for sending, receiving and transmitting cloud host data.
Background
At present, in an IaaS (Infrastructure as a Service) mode in the field of OpenStack cloud computing, a cloud computing Service platform provides virtual cloud hosts for users through the cloud computing virtualization hosts, and uplink and downlink bandwidths of the hosts created by the cloud computing virtualization hosts need to be limited according to specific situations of the users, so that network bandwidth is prevented from being occupied by individual users due to the fact that excessive traffic flows are flooded. In addition, the corresponding fee is charged according to the bandwidth applied by the user, so that economic benefits can be generated.
In the prior art, the OpenStack G version supports QoS (Quality of service) setting through Nova navigator, and QoS setting through navigator is not very flexible, which requires maintaining a plurality of ventilators to ensure different QoS requirements; the OpenStack L version supports ML2-QoS function, the characteristic can be used for setting flow QoS for L2-port and L2-net, ML2-QoS can only be used for flow limitation of a two-layer network, intranet flow and public network flow cannot be distinguished, hardware resources of the intranet cannot be fully utilized, and great resource waste is caused.
Disclosure of Invention
One objective of the present invention is to provide a scheme for performing bandwidth limitation on public network traffic of a cloud host.
According to an aspect of the present invention, a cloud host data receiving method is provided, including: acquiring destination address information of downlink flow of the cloud host, wherein the destination address information is public network address information of the cloud host; determining a target queue according to destination address information based on the corresponding relation between the queue and the public network address; and performing downlink transmission through the target queue based on the bandwidth limit of the target queue.
Optionally, the obtaining destination address information of the cloud host downlink traffic includes: an IFB (intermediate function Block device) acquires downlink flow entering a network card and acquires destination address information; obtaining destination address information by the IFB; determining the target queue according to the destination address information based on the corresponding relationship between the queue and the public network address comprises: the IFB determines a target queue according to the corresponding relation between the queue and the public network address, wherein the target queue has bandwidth limiting information; based on the bandwidth limitation of the target queue, the downlink transmission through the target queue comprises the following steps: and returning the downlink flow to the network card under the bandwidth limitation action of the target queue, and performing downlink transmission through the network card.
Optionally, the method further comprises: connecting a network card of the cloud host with the IFB; adding a TC (Traffic Control) rule in the IFB, setting queues through the TC rule, and specifying bandwidth limitation information of each queue; and establishing a corresponding relation between the queue and the public network address in the IFB.
Optionally, the method further comprises: and if the target queue cannot be determined according to the destination address information based on the corresponding relation between the queue and the public network address, selecting a preset default queue as the target queue.
Optionally, the method further comprises: when the public network address of the cloud host is deleted, the target queue matched with the public network address is deleted, and the corresponding relation between the public network address and the queue is deleted.
By the method, the queue can be distributed for the downlink flow of the cloud host according to the destination address, and the limitation of the bandwidth of the downlink flow is realized by using the bandwidth limitation of the queue, so that the limitation of the downlink flow of the cloud host based on the public network address is realized, the network bandwidth is prevented from being occupied by individual users due to the fact that overlarge flow flows are gushed, and the stability of the cloud host is improved.
According to another aspect of the present invention, a cloud host data sending method is provided, including: obtaining source address information of the uplink flow of the cloud host, wherein the source address information is public network address information of the cloud host; matching source address information with flow table information to determine a target queue, wherein the flow table information comprises a corresponding relation between public network address information and the queue; and performing uplink transmission through the target queue based on the bandwidth limit of the target queue.
Optionally, the obtaining source address information of the cloud host uplink traffic includes: a network bridge of a cloud host acquires source address information of uplink flow; matching the source address information with the flow table information, determining the target queue comprising: the bridge matches the source address information with flow table information in the bridge, and determines a target queue in the QoS function module, wherein the exit of the queue is bound with an uplink port of the bridge, and each queue has bandwidth limitation information; based on the bandwidth limitation of the target queue, the uplink transmission through the target queue comprises the following steps: and calling a QoS function module, and carrying out uplink transmission on the uplink flow through an uplink port under the bandwidth limitation action of a target queue of the QoS function module.
Optionally, the method further comprises: binding a network bridge of a cloud host with a QoS function module; generating queues in a QoS functional module, setting a flow control TC classification for each queue, and specifying bandwidth limitation information through the TC classification; flow table information is added in the bridge.
Optionally, the method further comprises: and if the source address information is not successfully matched with the flow table information, selecting a preset default queue as a target queue.
Optionally, the method further comprises: when the public network address of the cloud host is deleted, deleting the target queue in the flow table information matched with the public network address, and deleting the flow table information including the public network address.
By the method, the queue can be distributed for the uplink flow of the cloud host according to the source address, and the limitation of the bandwidth of the uplink flow is realized by using the bandwidth limitation of the queue, so that the limitation of the uplink flow of the cloud host based on the public network address is realized, the network bandwidth is prevented from being occupied by individual users due to the fact that overlarge flow flows are poured in, and the stability of the cloud host is improved.
According to another aspect of the present invention, a cloud host data transmission method is provided, which includes any one of the above mentioned cloud host data receiving methods; and/or any one of the cloud host data sending methods mentioned above.
By the method, the queue can be allocated for the downlink flow of the cloud host according to the destination address, and the limitation of the bandwidth of the downlink flow is realized by using the bandwidth limitation of the queue; the queues can be distributed for the uplink traffic of the cloud host according to the source address, and the limitation of the bandwidth of the uplink traffic is realized by using the bandwidth limitation of the queues, so that the bidirectional traffic bandwidth limitation of the cloud host based on the public network address is realized, the network bandwidth is prevented from being occupied by individual users due to the fact that overlarge traffic flows are gushed, and the stability of the cloud host is improved.
According to still another aspect of the present invention, a cloud host data receiving apparatus is provided, including: the destination address acquisition module is used for acquiring destination address information of the downlink flow of the cloud host, wherein the destination address information is public network address information of the cloud host; the target queue determining module is used for determining a target queue according to the destination address information based on the corresponding relation between the queue and the public network address; and the downlink transmission module is used for performing downlink transmission through the target queue based on the bandwidth limitation of the target queue.
Optionally, the destination address obtaining module is configured to obtain downlink traffic entering the network card in the IFB, and obtain destination address information; the target queue determining module is used for determining a target queue according to the corresponding relation between the queue and the public network address in the IFB, wherein the target queue has bandwidth limiting information; and the downlink transmission module is used for returning the downlink flow to the network card under the bandwidth limitation action of the target queue and performing downlink transmission through the network card.
Optionally, the method further comprises: the network card connecting module is used for connecting the network card of the cloud host with the IFB; a downlink queue generating module, configured to add a TC rule to the IFB, set queues according to the TC rule, and specify bandwidth limitation information of each queue; and the corresponding relation generating module is used for establishing the corresponding relation between the queue and the public network address in the IFB.
Optionally, the target queue determining module is further configured to select a predetermined default queue as the target queue when the target queue cannot be determined according to the destination address information based on the correspondence between the queue and the public network address.
Optionally, the method further comprises: and the deleting module is used for deleting the target queue matched with the public network address and deleting the corresponding relation between the public network address and the queue when the public network address of the cloud host is deleted.
The device can distribute the queue for the downlink flow of the cloud host according to the destination address, and limit the bandwidth of the downlink flow by using the bandwidth limit of the queue, so that the limitation of the downlink flow of the cloud host based on the public network address is realized, the phenomenon that the network bandwidth is occupied by individual users due to the fact that overlarge flow flows are gushed is prevented, and the stability of the cloud host is improved.
In addition, according to an aspect of the present invention, there is provided a cloud host data transmission device, including: the source address acquisition module is used for acquiring source address information of the uplink flow of the cloud host, wherein the source address information is public network address information of the cloud host; the target queue determining module is used for matching the source address information with the flow table information to determine a target queue, wherein the flow table information comprises the corresponding relation between the public network address information and the queue; and the uplink transmission module is used for carrying out uplink transmission through the target queue based on the bandwidth limitation of the target queue.
Optionally, the source address obtaining module is configured to obtain source address information of the uplink traffic at a bridge of the cloud host; the target queue determining module is used for the bridge to match the source address information with the flow table information in the bridge and determine a target queue in the QoS function module, wherein the exit of the queue is bound with the uplink port of the bridge, and each queue has bandwidth limiting information; the uplink transmission module is used for calling the QoS function module and carrying out uplink transmission on the uplink flow through the uplink port under the bandwidth limitation action of the target queue of the QoS function module.
Optionally, the method further comprises: the network bridge binding module is used for binding the network bridge of the cloud host to the QoS function module; an uplink queue generating module, configured to generate queues in the QoS function module, set a traffic control TC classification for each queue, and specify bandwidth limitation information through the TC classification; and the flow table adding module is used for adding flow table information in the bridge.
Optionally, the target queue determining module is further configured to select a predetermined default queue as the target queue when the source address information and the flow table information are not successfully matched.
Optionally, the method further comprises: and the deleting module is used for deleting the target queue in the flow table information matched with the public network address and deleting the flow table information comprising the public network address when the public network address of the cloud host is deleted.
The device can distribute the queue for the uplink flow of the cloud host according to the source address, and limit the bandwidth of the uplink flow by using the bandwidth limit of the queue, so that the limitation of the uplink flow of the cloud host based on the public network address is realized, the phenomenon that the network bandwidth is occupied by individual users due to the fact that overlarge flow flows are gushed is prevented, and the stability of the cloud host is improved.
In addition, according to a further aspect of the present invention, there is provided a cloud host data transmission apparatus, comprising the cloud host data reception apparatus of any one of the above-mentioned; and/or the cloud host data transmitting apparatus of any of the above.
The device can allocate the queue for the downlink flow of the cloud host according to the destination address, and limit the bandwidth of the downlink flow by using the bandwidth limit of the queue; the queues can be distributed for the uplink traffic of the cloud host according to the source address, and the limitation of the bandwidth of the uplink traffic is realized by using the bandwidth limitation of the queues, so that the bidirectional traffic bandwidth limitation of the cloud host based on the public network address is realized, the network bandwidth is prevented from being occupied by individual users due to the fact that overlarge traffic flows are gushed, and the stability of the cloud host is improved.
In addition, according to still another aspect of the present invention, there is provided a cloud host data transmission apparatus, including: a memory; and a processor coupled to the memory, the processor configured to perform a method as any one of those mentioned above based on instructions stored in the memory.
The device can allocate the queue for the downlink flow of the cloud host according to the destination address, and limit the bandwidth of the downlink flow by using the bandwidth limit of the queue; the queues can be distributed for the uplink traffic of the cloud host according to the source address, and the limitation of the bandwidth of the uplink traffic is realized by using the bandwidth limitation of the queues, so that the bidirectional traffic bandwidth limitation of the cloud host based on the public network address is realized, the network bandwidth is prevented from being occupied by individual users due to the fact that overlarge traffic flows are gushed, and the stability of the cloud host is improved. Because speed limitation is carried out based on the public network address, intranet flow and public network flow can be distinguished, so that hardware resources of an intranet are fully utilized while speed limitation is carried out, and the performance of the cloud host is improved.
Drawings
The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the invention and together with the description serve to explain the invention without limiting the invention. In the drawings:
fig. 1 is a flowchart of an embodiment of a cloud host data receiving method according to the present invention.
Fig. 2 is a flowchart of another embodiment of a cloud host data receiving method according to the present invention.
Fig. 3 is a flowchart of a cloud host data receiving method according to another embodiment of the present invention.
Fig. 4 is a flowchart of an embodiment of a cloud host data transmission method according to the present invention.
Fig. 5 is a flowchart of another embodiment of a cloud host data transmission method according to the present invention.
Fig. 6 is a flowchart of a cloud host data transmission method according to another embodiment of the present invention.
Fig. 7 is a schematic diagram of an embodiment of a cloud host data transmission method according to the present invention.
Fig. 8 is a schematic diagram of an embodiment of a cloud host data receiving device according to the present invention.
Fig. 9 is a schematic diagram of another embodiment of a cloud host data receiving device according to the present invention.
Fig. 10 is a schematic diagram of an embodiment of a cloud host data transmission apparatus according to the present invention.
Fig. 11 is a schematic diagram of another embodiment of the cloud host data sending apparatus according to the present invention.
Fig. 12 is a schematic diagram of an embodiment of a cloud host data transmission apparatus according to the present invention.
Fig. 13 is a schematic diagram of another embodiment of a cloud host data transmission apparatus according to the present invention.
Fig. 14 is a schematic diagram of a cloud host data transmission apparatus according to another embodiment of the present invention.
Detailed Description
The technical solution of the present invention is further described in detail by the accompanying drawings and embodiments.
Fig. 1 is a flowchart of an embodiment of a cloud host data receiving method according to the present invention.
In step 101, destination address information of the cloud host downlink traffic is obtained, where the destination address information is public network address information of the cloud host.
In step 102, a target queue is determined according to destination address information based on a corresponding relationship between the queue and a public network address. Each queue is pre-configured with public network address information for traffic that can be transmitted, and each queue has a bandwidth limit.
In step 103, downlink transmission is performed through the target queue based on the bandwidth limit of the target queue. Since the target queue has a bandwidth limitation, when the downstream traffic is transmitted through the target queue, it needs to be transmitted under the bandwidth limitation of the queue.
By the method, the queue can be distributed for the downlink flow of the cloud host according to the destination address, and the limitation of the bandwidth of the downlink flow is realized by using the bandwidth limitation of the queue, so that the limitation of the downlink flow of the cloud host based on the public network address is realized, the network bandwidth is prevented from being occupied by individual users due to the fact that overlarge flow flows are gushed, and the stability of the cloud host is improved. Because speed limitation is carried out based on the public network address, intranet flow and public network flow can be distinguished, so that hardware resources of an intranet are fully utilized while speed limitation is carried out, and the performance of the cloud host is improved.
Fig. 2 is a flowchart of another embodiment of a cloud host data receiving method according to the present invention.
In step 201, the IFB acquires the downlink traffic entering the network card, and the IFB acquires the destination address information. In one embodiment, an IFB may be invoked, which is loaded with an IFB0 virtual network card. The virtual network card ifb0 can acquire destination address information of the downstream traffic by using the loaded TC rule.
In step 202, the IFB determines the target queue according to the correspondence between the queue and the public network address. In one embodiment, a plurality of queues may be configured in the IFB, with a target queue having bandwidth limitation information. The target queue of the downlink flow can be determined through the corresponding relation between the queue and the address. In one embodiment, a TC rule is set at a port of the virtual network card ifb0, a plurality of queues are set in the TC rule, and bandwidth limitation information specifying the plurality of queues is set in the TC rule.
In step 203, the downlink traffic is returned to the network card under the bandwidth limitation of the target queue, and downlink transmission is performed through the network card.
In a Linux operating system, a TC is used for flow control of a Linux kernel, and the flow control of the kernel is mainly realized by establishing a queue at an output port. The IFB can be regarded as a virtual network card with only TC filtering function, which does not change the direction of the data packet, i.e. the data packet sent out is redirected to the IFB, and is still sent out through the network card before redirection after TC filtering by the IFB, and the data packet received by a network card is redirected to the IFB, and is still received by the network card before redirection after TC filtering by the IFB. By the method, the IFB function in Linux can be utilized for improvement, the bandwidth limitation of the downlink flow of the cloud host is realized, and the application is favorably implemented.
Fig. 3 is a flowchart of another embodiment of a cloud host data receiving method according to the present invention.
In step 301, the network card of the cloud host is connected to the IFB, so that when downstream traffic arrives, the traffic is redirected to the IFB. In one embodiment, the IFB driver may be loaded and the virtual network card IFB0 may be launched.
In step 302, a TC rule is added to the IFB, queues are set by the TC rule, and bandwidth limitation information of each queue is specified. In one embodiment, multiple queues may be set up according to downstream bandwidth requirements. In one embodiment, a root queue may be set for the ifb0 network card first, and then several sub-queues may be added, each sub-queue corresponding to a TC class. Each TC class sets a maximum rate, a lowest rate available, a priority, and the like.
In step 303, a corresponding relationship between the queue and the public network address is established in the IFB. In one embodiment, the queues may be specified according to public network addresses, and the queues with different destination public network addresses of the downstream traffic are different, and the maximum bandwidth of the queues is set by TC classification, thereby completing the exit bandwidth limitation of ifb 0.
In step 304, the downstream traffic entering the network card is forwarded to the IFB, and the IFB obtains the destination address information. In one embodiment, downstream data entering the network card may be redirected to the root queue of the ifb0, and the ifb0 obtains destination address information.
In step 305, the IFB determines the target queue according to the correspondence between the queue and the public network address.
In step 306, the downlink traffic is returned to the network card under the bandwidth limitation of the target queue, and downlink transmission is performed through the network card.
By the method, the IFB function in the Linux can be improved and applied to the current limiting of the downlink flow of the cloud host, and the method is stable and reliable and is beneficial to practical application. Meanwhile, the bandwidth is set according to the IP address of the public network, so that the setting and the management are convenient.
In one embodiment, the bandwidth modification function can be opened, and the bandwidth interface and the bandwidth modification interface are specified when the user applies for the public network address, so that the queue bandwidth limitation can be conveniently modified. In one embodiment, the charging may be by flow control, with higher selected bandwidth charged more, resulting in economic benefits.
In one embodiment, a default queue may be set, the default queue having a lower priority than the other queues. And when the downlink flow arrives, matching the public network address according to the priority level. And when the matching is not successful, determining the default queue as the target queue, and transmitting under the bandwidth limit of the default queue.
By the method, abnormal conditions such as incapability of transmitting downlink flow and possible congestion caused by untimely update of the public network address can be prevented, normal operation of the system is guaranteed, and robustness of the system is improved.
In one embodiment, when the cloud host deletes the public network address, the queue corresponding to the public network address may be deleted, and the corresponding relationship may be deleted at the same time, so as to implement efficient utilization of resources, prevent the failure information from occupying system resources to cause efficiency reduction, and facilitate maintaining efficient operation of the cloud host.
A flowchart of an embodiment of a cloud host data sending method according to the present invention is shown in fig. 4.
In step 401, source address information of the cloud host uplink traffic is obtained, where the source address information is public network address information of the cloud host.
In step 402, the source address information is matched with the flow table information to determine a target queue, where the flow table information includes a correspondence between the public network address information and the queue. Each queue is pre-configured with public network address information for traffic that can be transmitted, and each queue has a bandwidth limit.
In step 403, uplink transmission is performed through the target queue based on the bandwidth limitation of the target queue. Since the target queue has a bandwidth limitation, when the upstream traffic is transmitted through the target queue, it needs to be transmitted under the bandwidth limitation of the queue.
By the method, the queue can be distributed for the uplink flow of the cloud host according to the source address, and the limitation of the bandwidth of the uplink flow is realized by using the bandwidth limitation of the queue, so that the limitation of the uplink flow of the cloud host based on the public network address is realized, the network bandwidth is prevented from being occupied by individual users due to the fact that overlarge flow flows are poured in, and the stability of the cloud host is improved. Because speed limitation is carried out based on the public network address, intranet flow and public network flow can be distinguished, so that hardware resources of an intranet are fully utilized while speed limitation is carried out, and the performance of the cloud host is improved.
Fig. 5 is a flowchart of another embodiment of a cloud host data transmission method according to the present invention.
In step 501, a bridge of a cloud host acquires source address information of upstream traffic.
In step 502, the bridge matches the source address information with flow table information in the bridge, determining a target queue in the QoS function. In one embodiment, a plurality of queues may be configured in the QoS function, the exits of the queues bind upstream ports of the bridge, and each queue has bandwidth limitation information.
In step 503, the QoS function module is invoked, and the uplink traffic is transmitted through the uplink port under the bandwidth limitation of the target queue of the QoS function module.
The QoS function module is a functional interface provided by OpenvSwitch. The OpenvSwitch is a piece of virtual switching software, is mainly used in a virtual machine VM environment, is used as a virtual switch, supports various virtualization technologies, can well support control of uplink flow in the field of virtual machines, and has an undesirable effect of limiting downlink flow. The QoS function module is integrated to the cloud platform, so that the uplink flow control function can be well applied, the implementation efficiency is improved, the implementation effect is guaranteed, and practical application is facilitated.
In one embodiment, the bandwidth modification function can be opened, and the bandwidth interface and the bandwidth modification interface are specified when the user applies for the public network address, so that the queue bandwidth limitation can be conveniently modified. In one embodiment, the charging may be by flow control, with higher selected bandwidth charged more, resulting in economic benefits.
A flowchart of another embodiment of the cloud host data sending method according to the present invention is shown in fig. 6.
In step 601, the bridge of the cloud host is bound to the QoS function module, and when the upstream traffic arrives, the QoS function module is called.
In step 602, queues are generated in the QoS function, a TC class is set for each queue, and bandwidth limitation information is specified by the TC class. In one embodiment, multiple queues may be set up according to upstream bandwidth requirements. In one embodiment, a QoS root queue may be added to a network card, and the total available bandwidth is set to the maximum bandwidth of the network card; and then adding a plurality of sub queues under the root queue, setting each sub queue to correspond to one TC classification, and appointing the maximum bandwidth, the minimum guaranteed bandwidth and the like by the TC classification, wherein each sub queue can correspond to different bandwidths.
In step 603, adding flow table information in the bridge, where the flow table information includes a correspondence between a public network address of the cloud host and the queue. In one embodiment, a flow table may be added to the bridge br-ex, which matches packets according to source address and lets the matched packets pass through the destination queue, because the queue sets the highest rate, the purpose of throttling may be achieved. When a plurality of public network IPs are used, a plurality of flow tables are added, and each flow table points to a corresponding QoS queue.
In step 604, the bridge of the cloud host obtains source address information of the upstream traffic.
In step 605, the source address information is matched with the flow table information in the bridge to determine the target queue.
In step 606, the QoS function module is invoked, and the uplink traffic is transmitted through the uplink port under the bandwidth limitation of the target queue of the QoS function module.
By the method, the QoS function module in the OVS can be improved and applied to bandwidth limitation of the upstream flow of the cloud host, and the method is stable and reliable and is beneficial to practical application.
In one embodiment, a default queue may be set, the default queue having a lower priority than the other queues. And when the uplink flow comes, matching the public network address according to the priority level. And when the matching is not successful, determining the default queue as the target queue, and transmitting under the bandwidth limit of the default queue.
By the method, abnormal conditions such as incapability of transmitting downlink flow and possible congestion caused by untimely update of the public network address can be prevented, normal operation of the system is guaranteed, and robustness of the system is improved.
In one embodiment, when the cloud host deletes the public network address, the queue corresponding to the public network address may be deleted, and the flow table entry related to the public network address may be deleted at the same time, so as to implement efficient utilization of resources, prevent efficiency reduction caused by occupation of system resources by failure information, and facilitate maintaining efficient operation of the cloud host.
The cloud host data transmission method of the invention may include any one of the cloud host data transmission method and the cloud host data reception method mentioned above. In one embodiment, as shown in FIG. 7.
In 701, downstream traffic reaches the network card.
In 702, the network card redirects traffic to the IFB. The IFB extracts the destination address of the downlink flow, then determines a target queue according to the preset corresponding relation between the queue and the public network address, and realizes bandwidth limitation through the TC function.
At 703, the IFB returns the downstream traffic. Because the limitation of the downstream traffic bandwidth is realized in the IFB, the traffic returned to the network card can also realize the limitation of the downstream traffic bandwidth.
At 704, the bridge receives upstream traffic.
In 705, the bridge performs address matching based on the flow table information according to the source address of the uplink traffic, determines a target queue, invokes the QoS function module, and realizes the limitation of the uplink traffic bandwidth by using the bandwidth limitation of the target queue in the QoS function module.
At 706, the upstream traffic that is subject to the bandwidth limitation of the target queue is sent to the external network through the upstream network card interface.
At present, OpenStack does not provide a good bidirectional speed limiting method. By the method, the flow is limited aiming at the public network IP address, the host can achieve the purpose of limiting the flow by using the public network IP with set bandwidth, the flexibility of limiting the cloud host bandwidth is improved, the bidirectional speed limiting function of the cloud host based on the public network address is well realized, the intranet flow and the public network flow can be distinguished, the hardware resource of the intranet is fully utilized while the speed is limited, and the performance of the cloud host is improved.
Fig. 8 is a schematic diagram of an embodiment of a cloud host data receiving apparatus according to the present invention. The destination address obtaining module 801 may obtain destination address information of the cloud host downlink traffic, where the destination address information is public network address information of the cloud host. The target queue determining module 802 can determine the target queue according to the destination address information based on the correspondence between the queue and the public network address. Each queue is pre-configured with public network address information for traffic that can be transmitted, and each queue has a bandwidth limit. In one embodiment, the target queue may be determined by using a flow table matching method, where the flow table includes a correspondence between a public network address and a queue. The downlink transmission module 803 can perform downlink transmission through the target queue based on the bandwidth limitation of the target queue. Since the target queue has a bandwidth limitation, when the downstream traffic is transmitted through the target queue, it needs to be transmitted under the bandwidth limitation of the queue.
The device can distribute the queue for the downlink flow of the cloud host according to the destination address, and limit the bandwidth of the downlink flow by using the bandwidth limit of the queue, so that the limitation of the downlink flow of the cloud host based on the public network address is realized, the phenomenon that the network bandwidth is occupied by individual users due to the fact that overlarge flow flows are gushed is prevented, and the stability of the cloud host is improved. Because speed limitation is carried out based on the public network address, intranet flow and public network flow can be distinguished, so that hardware resources of an intranet are fully utilized while speed limitation is carried out, and the performance of the cloud host is improved.
In one embodiment, the destination address obtaining module 801 can obtain downlink traffic entering the network card at the IFB, and obtain destination address information by the IFB. The target queue determining module 802 can determine the target queue in the IFB according to the corresponding relationship between the queue and the public network address. In one embodiment, a plurality of queues may be configured in the IFB, with a target queue having bandwidth limitation information. The target queue of the downlink flow can be determined through the corresponding relation between the queue and the address. The downlink transmission module 803 can return the downlink traffic to the network card under the bandwidth limitation of the target queue, and perform downlink transmission through the network card.
The device is improved by utilizing the IFB function in Linux, realizes the bandwidth limitation of the downlink flow of the cloud host and is beneficial to implementation and application.
Fig. 9 is a schematic diagram of another embodiment of the cloud host data receiving apparatus according to the present invention. The structure and function of the destination address obtaining module 901, the target queue determining module 902 and the downlink transmission module 903 are similar to those in the embodiment of fig. 8. The cloud host data receiving apparatus further includes a network card connection module 904, a downlink queue generating module 905, and a correspondence generating module 906. The network card connection module 904 can connect the network card of the cloud host with the IFB, so that when downlink traffic arrives, the traffic is redirected to the IFB. The downlink queue generating module 905 can add a TC rule to the IFB, set queues according to the TC rule, and specify bandwidth limitation information of each queue. In one embodiment, multiple queues may be set up according to downstream bandwidth requirements. The correspondence generating module 906 can establish a correspondence of the queue with the public network address in the IFB.
The device can improve the IFB function in Linux and is applied to the current limiting of the downlink flow of the cloud host, is stable and reliable, and is beneficial to practical application.
In one embodiment, the queues include a default queue that is lower priority than the other queues. When the downlink flow comes, the target queue determining module can match the public network address according to the priority level. And when the matching is not successful, determining the default queue as the target queue, and transmitting under the bandwidth limit of the default queue.
The device can prevent abnormal conditions such as downlink flow transmission failure and possible congestion caused by untimely update of the public network address, ensure normal operation of the system and improve the robustness of the system.
In one embodiment, the cloud host data receiving device further includes a deleting module, which is capable of deleting the queue corresponding to the public network address when the cloud host deletes the public network address, and deleting the corresponding relation, so as to achieve efficient utilization of resources, prevent efficiency reduction caused by occupation of system resources by failure information, and facilitate maintaining efficient operation of the cloud host.
Fig. 10 is a schematic diagram of an embodiment of a cloud host data transmission apparatus according to the present invention. The source address obtaining module 1001 is configured to obtain source address information of the uplink traffic of the cloud host, where the source address information is public network address information of the cloud host. The target queue determining module 1002 is configured to match source address information with flow table information, and determine a target queue, where the flow table information includes a correspondence between public network address information and a queue. Each queue is pre-configured with public network address information for traffic that can be transmitted, and each queue has a bandwidth limit. The uplink transmission module 1003 is configured to perform uplink transmission through the target queue based on the bandwidth limitation of the target queue. Since the target queue has a bandwidth limitation, when the upstream traffic is transmitted through the target queue, it needs to be transmitted under the bandwidth limitation of the queue.
The device can distribute the queue for the uplink flow of the cloud host according to the source address, and limit the bandwidth of the uplink flow by using the bandwidth limit of the queue, so that the limitation of the uplink flow of the cloud host based on the public network address is realized, the phenomenon that the network bandwidth is occupied by individual users due to the fact that overlarge flow flows are gushed is prevented, and the stability of the cloud host is improved. Because speed limitation is carried out based on the public network address, intranet flow and public network flow can be distinguished, so that hardware resources of an intranet are fully utilized while speed limitation is carried out, and the performance of the cloud host is improved.
In one embodiment, the source address obtaining module 1001 may obtain source address information of the upstream traffic at a bridge of the cloud host. The target queue determining module 1002 can determine the target queue in the QoS function module by the bridge matching the source address information with the flow table information in the bridge. In one embodiment, a plurality of queues may be configured in the QoS function, the exits of the queues bind upstream ports of the bridge, and each queue has bandwidth limitation information. The uplink transmission module 1003 can call the QoS function module, and perform uplink transmission on the uplink traffic through the uplink port under the bandwidth limitation action of the target queue of the QoS function module.
The device integrates the QoS function module into the cloud platform, can well apply the uplink flow control function of the cloud platform, improves the implementation efficiency, ensures the implementation effect and is beneficial to practical application.
Fig. 11 is a schematic diagram of another embodiment of the cloud host data transmission apparatus according to the present invention. The structure and function of the source address obtaining module 1101, the target queue determining module 1102 and the upstream transmission module 1103 are similar to those in the embodiment of fig. 10. The cloud host data transmitting apparatus further includes a bridge binding module 1104, an upstream queue generating module 1105, and a flow table adding module 1106. The bridge binding module 1104 can bind the bridge of the cloud host to the QoS function module, and when the upstream traffic arrives, the QoS function module is called. The uplink queue generating module 1105 can generate queues in the QoS function module, set a TC classification for each queue, and specify bandwidth limitation information by the TC classification. In one embodiment, multiple queues may be set up according to upstream bandwidth requirements. The flow table adding module 1106 can add flow table information in the bridge, where the flow table information includes a correspondence between a public network address of the cloud host and the queue.
The device improves the QoS function module in OpenvSwitch, is applied to bandwidth limitation of the upstream flow of the cloud host, is stable and reliable, and is beneficial to practical application.
In one embodiment, a default queue may be set, the default queue having a lower priority than the other queues. When the uplink flow comes, the target queue determining module matches the public network address according to the priority level. And when the matching is not successful, determining the default queue as the target queue, and transmitting under the bandwidth limit of the default queue.
The device can prevent abnormal conditions such as downlink flow transmission failure and possible congestion caused by untimely update of the public network address, ensure normal operation of the system and improve the robustness of the system.
In one embodiment, the cloud host data sending device further includes a deleting module, which is capable of deleting a queue corresponding to a public network address when the cloud host deletes the public network address, and deleting a flow table entry related to the public network address at the same time, so that efficient utilization of resources is achieved, efficiency reduction caused by occupation of system resources by failure information is prevented, and efficient operation of the cloud host is maintained.
The cloud host data transmission device of the present invention may include any one of the cloud host data transmission device and the cloud host data reception device mentioned above. In one embodiment, as shown in fig. 12, the cloud host data transmission apparatus includes a cloud host data reception apparatus 1200 and a cloud host data transmission apparatus 1210. The cloud host data receiving device 1200 includes a destination address obtaining module 1201, a target queue determining module 1202, and a downlink transmission module 1203; the cloud host data transmitting apparatus 1210 includes a source address obtaining module 1211, a target queue determining module 1212, and an upstream transmission module 1213. The cloud host data receiving apparatus 1200 can implement downlink traffic bandwidth limitation based on the public network address; the cloud host data sending device 1210 can implement the limitation of the upstream traffic bandwidth based on the public network address.
The device can allocate the queue for the downlink flow of the cloud host according to the destination address, and limit the bandwidth of the downlink flow by using the bandwidth limit of the queue; the queues can be distributed for the uplink traffic of the cloud host according to the source address, and the limitation of the bandwidth of the uplink traffic is realized by using the bandwidth limitation of the queues, so that the bidirectional traffic bandwidth limitation of the cloud host based on the public network address is realized, the network bandwidth is prevented from being occupied by individual users due to the fact that overlarge traffic flows are gushed, and the stability of the cloud host is improved.
Fig. 13 is a schematic diagram of another embodiment of the cloud host data transmission apparatus according to the present invention, which includes a memory 1301 and a processor 1302. Wherein:
the memory 1301 may be a magnetic disk, flash memory, or any other non-volatile storage medium. The memory 1301 is used to store operation instructions, queues, bandwidth restrictions, flow table information, and the like of the system.
Processor 1302 is coupled to memory 1301 and may be implemented as one or more integrated circuits, such as a microprocessor or microcontroller. The processor 1302 is configured to execute instructions stored in a memory, so as to implement data operations, transmission, and the like.
In one embodiment, as also shown in fig. 14, 1400 is a cloud host data transmission apparatus, including a memory 1401 and a processor 1402. The processor 1402 may include processors 1402a, 1402b … 1402 n. The processors 1402a-1402n are coupled to the memory 1401 via a BUS BUS 1403. The system based on the distributed structure can carry out quick operation, and improves the operation efficiency. Cloud host data transfer device 1400 may also be connected to external storage device 1405 through storage interface 1404 for the purpose of retrieving external data or transferring data to external storage device 1405, and may also be connected to a network or another computer system (not shown) through network interface 1406. And will not be described in detail herein.
In the embodiment, the data instructions are stored in the memory, and the instructions are processed by the processor, so that bidirectional traffic bandwidth limitation of the cloud host based on the public network address can be realized, the situation that the network bandwidth is occupied by individual users due to the fact that too large traffic is flooded is prevented, and the stability of the cloud host is improved.
Finally, it should be noted that: the above examples are only intended to illustrate the technical solution of the present invention and not to limit it; although the present invention has been described in detail with reference to preferred embodiments, those skilled in the art will understand that: modifications to the specific embodiments of the invention or equivalent substitutions for parts of the technical features may be made; without departing from the spirit of the present invention, it is intended to cover all aspects of the invention as defined by the appended claims.
Claims (20)
1. A cloud host data receiving method is characterized by comprising the following steps:
the method for acquiring the destination address information of the downlink flow of the cloud host comprises the following steps: the intermediate function block device IFB acquires the downlink traffic entering the network card and acquires the destination address information, where the destination address information is public network address information of the cloud host;
determining a target queue according to the destination address information based on the corresponding relationship between the queue and the public network address, including: the IFB determines the target queue according to the corresponding relation between the queue and the public network address, wherein the target queue has bandwidth limitation information, and a plurality of queues are configured in the IFB;
based on the bandwidth limitation of the target queue, performing downlink transmission through the target queue, including: and returning the downlink flow to the network card under the bandwidth limitation action of the target queue, and performing downlink transmission through the network card.
2. The method of claim 1, further comprising:
connecting a network card of the cloud host with the IFB;
adding a TC rule in the IFB, setting queues through the TC rule, and specifying bandwidth limitation information of each queue;
and establishing the corresponding relation between the queue and the public network address in the IFB.
3. The method of claim 1 or 2, further comprising:
and if the target queue cannot be determined according to the destination address information based on the corresponding relation between the queue and the public network address, selecting a preset default queue as the target queue.
4. The method of claim 1 or 2, further comprising: and when the public network address of the cloud host is deleted, deleting the target queue matched with the public network address, and deleting the corresponding relation between the public network address and the queue.
5. A method for sending cloud host data is characterized by comprising the following steps:
obtaining source address information of the cloud host uplink flow, including: the network bridge of the cloud host acquires source address information of the uplink flow, wherein the source address information is public network address information of the cloud host;
matching the source address information with flow table information to determine a target queue, comprising: the network bridge matches the source address information with flow table information in the network bridge, and determines to call a target queue in a QoS (quality of service) function module, wherein the flow table information comprises a corresponding relation between the public network address information and the queue, a plurality of queues are configured in the QoS function module, an uplink port of the network bridge is bound to an outlet of each queue, and each queue has bandwidth limitation information;
based on the bandwidth limitation of the target queue, performing uplink transmission through the target queue, including: and the QoS functional module is used for carrying out uplink transmission on the uplink flow through the uplink port under the bandwidth limitation action of the target queue of the QoS functional module.
6. The method of claim 5, further comprising:
binding the bridge of the cloud host to the QoS function module;
generating queues in the QoS functional module, setting a flow control TC classification for each queue, and appointing bandwidth limitation information through the TC classification;
adding flow table information in the bridge.
7. The method of claim 5 or 6, further comprising:
and if the source address information and the flow table information are not successfully matched, selecting a preset default queue as a target queue.
8. The method of claim 5 or 6, further comprising:
when the public network address of the cloud host is deleted, deleting a target queue in flow table information matched with the public network address, and deleting flow table information including the public network address.
9. A cloud host data transmission method comprises the cloud host data receiving method of any one of claims 1-4; and/or the presence of a gas in the gas,
the cloud host data transmission method according to any one of claims 5 to 8.
10. A cloud host data receiving apparatus, comprising:
the destination address acquisition module is used for acquiring destination address information of downlink flow of the cloud host, and comprises: acquiring the downlink flow entering a network card through an intermediate function block device (IFB), and acquiring the destination address information, wherein the destination address information is public network address information of the cloud host;
a target queue determining module, configured to determine a target queue according to the destination address information based on a correspondence between the queue and the public network address, including: determining the target queue according to the corresponding relation between the queue and the public network address in the IFB, wherein the target queue has bandwidth limitation information, and a plurality of queues are configured in the IFB;
and the downlink transmission module is used for performing downlink transmission through the target queue based on the bandwidth limitation of the target queue, and comprises the steps of returning the downlink flow to the network card under the bandwidth limitation action of the target queue and performing downlink transmission through the network card.
11. The apparatus of claim 10, further comprising:
the network card connecting module is used for connecting the network card of the cloud host with the IFB;
a downlink queue generating module, configured to add a TC rule to the IFB, set queues according to the TC rule, and specify bandwidth limitation information of each queue;
and the corresponding relation generating module is used for establishing the corresponding relation between the queue and the public network address in the IFB.
12. The apparatus of claim 10 or 11,
the target queue determining module is further configured to select a predetermined default queue as the target queue when the target queue cannot be determined according to the destination address information based on the correspondence between the queue and the public network address.
13. The apparatus of claim 10 or 11, further comprising:
and the deleting module is used for deleting the target queue matched with the public network address and deleting the corresponding relation between the public network address and the queue when the public network address of the cloud host is deleted.
14. A cloud host data transmission device, comprising:
the source address acquisition module is used for acquiring source address information of the upstream flow of the cloud host, and comprises the following steps: acquiring source address information of the uplink flow at a network bridge of a cloud host, wherein the source address information is public network address information of the cloud host;
a target queue determining module, configured to match the source address information with flow table information, and determine a target queue, including: the network bridge matches the source address information with flow table information in the network bridge, and determines to call a target queue in a QoS (quality of service) function module, wherein the flow table information comprises a corresponding relation between the public network address information and the queue, a plurality of queues are configured in the QoS function module, an uplink port of the network bridge is bound to an outlet of each queue, and each queue has bandwidth limitation information;
an uplink transmission module, configured to perform uplink transmission through the target queue based on the bandwidth limitation of the target queue, including: and the QoS functional module is used for carrying out uplink transmission on the uplink flow through the uplink port under the bandwidth limitation action of the target queue of the QoS functional module.
15. The apparatus of claim 14, further comprising:
the network bridge binding module is used for binding the network bridge of the cloud host to the QoS function module;
an uplink queue generating module, configured to generate queues in the QoS function module, set a flow control TC classification for each queue, and specify bandwidth limitation information through the TC classification;
and the flow table adding module is used for adding flow table information in the bridge.
16. The apparatus according to claim 14 or 15, wherein the target queue determining module is further configured to select a predetermined default queue as the target queue when the source address information and the flow table information are not successfully matched.
17. The apparatus of claim 14 or 15, further comprising:
and the deleting module is used for deleting the target queue in the flow table information matched with the public network address and deleting the flow table information comprising the public network address when the public network address of the cloud host is deleted.
18. A cloud host data transmission device, comprising the cloud host data reception device according to any one of claims 10 to 13; and/or
The cloud host data transmission device according to any one of claims 14 to 17.
19. A cloud host data transmission device, comprising:
a memory; and
a processor coupled to the memory, the processor configured to perform the method of any of claims 1-8 based on instructions stored in the memory.
20. A computer readable storage medium having stored thereon computer program instructions which, when executed by a processor, implement the steps of the method of any one of claims 1 to 8.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610803755.4A CN107800645B (en) | 2016-09-06 | 2016-09-06 | Cloud host data sending, receiving and transmitting method and device |
| PCT/CN2017/092571 WO2018045821A1 (en) | 2016-09-06 | 2017-07-12 | Methods and devices for sending, receiving, and transmitting cloud host data |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610803755.4A CN107800645B (en) | 2016-09-06 | 2016-09-06 | Cloud host data sending, receiving and transmitting method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107800645A CN107800645A (en) | 2018-03-13 |
| CN107800645B true CN107800645B (en) | 2020-05-01 |
Family
ID=61530392
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610803755.4A Active CN107800645B (en) | 2016-09-06 | 2016-09-06 | Cloud host data sending, receiving and transmitting method and device |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN107800645B (en) |
| WO (1) | WO2018045821A1 (en) |
Families Citing this family (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108683607B (en) * | 2018-06-14 | 2020-02-21 | 新华三云计算技术有限公司 | Virtual machine flow control method and device and server |
| CN110868364B (en) * | 2018-08-28 | 2023-04-18 | 阿里巴巴集团控股有限公司 | Bandwidth isolation device and method |
| CN109120454B (en) * | 2018-09-04 | 2021-06-15 | 浪潮云信息技术股份公司 | QoS flow rate limiting system and method |
| CN111049669A (en) * | 2019-10-30 | 2020-04-21 | 烽火通信科技股份有限公司 | Distributed storage system and method for realizing flow control |
| CN110932998B (en) * | 2019-11-28 | 2022-11-01 | 杭州迪普科技股份有限公司 | Message processing method and device |
| CN112671668B (en) * | 2020-12-17 | 2023-03-24 | 中盈优创资讯科技有限公司 | Neutron virtual network flow control method and device |
| CN112866019B (en) * | 2021-01-11 | 2022-08-05 | 科大讯飞股份有限公司 | Method for limiting bandwidth of elastic IP address, related equipment and readable storage medium |
| CN113300978A (en) * | 2021-02-05 | 2021-08-24 | 阿里巴巴集团控股有限公司 | Data transmission method and device |
| CN113783797B (en) * | 2021-09-13 | 2023-11-07 | 京东科技信息技术有限公司 | Network flow control method, device and equipment of cloud primary container and storage medium |
| CN114338546A (en) * | 2021-12-24 | 2022-04-12 | 中国联合网络通信集团有限公司 | Virtual machine speed limiting method and device, electronic equipment and readable storage medium |
| CN114900470B (en) * | 2022-06-17 | 2023-10-31 | 中国联合网络通信集团有限公司 | Flow control method, device, equipment and storage medium |
| CN116723162B (en) * | 2023-08-10 | 2023-11-03 | 浪潮电子信息产业股份有限公司 | Network first packet processing method, system, device, medium and heterogeneous equipment |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102801636A (en) * | 2012-09-05 | 2012-11-28 | 成都国腾实业集团有限公司 | Method for limiting bandwidth of cloud hosting network of cloud computing platform |
| CN103634235A (en) * | 2013-11-01 | 2014-03-12 | 国云科技股份有限公司 | Method for limiting speed of network interface of virtual machine |
| CN105915387A (en) * | 2016-05-31 | 2016-08-31 | 新浪网技术(中国)有限公司 | External network bandwidth speed limiting method, device and system of cloud host in IaaS cloud platform |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101841451B (en) * | 2009-12-30 | 2013-01-02 | 北京世纪互联宽带数据中心有限公司 | Virtual local area network-based speed limiting method and system for cloud hosts |
| US8477610B2 (en) * | 2010-05-31 | 2013-07-02 | Microsoft Corporation | Applying policies to schedule network bandwidth among virtual machines |
| US8837483B2 (en) * | 2011-04-11 | 2014-09-16 | Alcatel Lucent | Mapping private and public addresses |
| CN103188086B (en) * | 2011-12-27 | 2015-11-11 | 中国移动通信集团公司 | A kind of method, Apparatus and system of management and control intranet and extranet bandwidth |
| CN102546444B (en) * | 2012-03-28 | 2014-08-13 | 杭州华三通信技术有限公司 | Method for accessing private network through layer 2 tunneling protocol and server |
| CN105915470B (en) * | 2016-01-27 | 2019-05-21 | 无锡华云数据技术服务有限公司 | A kind of elastic bandwidth configuration method based on Linux flow control |
-
2016
- 2016-09-06 CN CN201610803755.4A patent/CN107800645B/en active Active
-
2017
- 2017-07-12 WO PCT/CN2017/092571 patent/WO2018045821A1/en active Application Filing
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102801636A (en) * | 2012-09-05 | 2012-11-28 | 成都国腾实业集团有限公司 | Method for limiting bandwidth of cloud hosting network of cloud computing platform |
| CN103634235A (en) * | 2013-11-01 | 2014-03-12 | 国云科技股份有限公司 | Method for limiting speed of network interface of virtual machine |
| CN105915387A (en) * | 2016-05-31 | 2016-08-31 | 新浪网技术(中国)有限公司 | External network bandwidth speed limiting method, device and system of cloud host in IaaS cloud platform |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2018045821A1 (en) | 2018-03-15 |
| CN107800645A (en) | 2018-03-13 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107800645B (en) | Cloud host data sending, receiving and transmitting method and device | |
| US10673760B2 (en) | Method, apparatus, and system for load balancing of service chain | |
| US10103972B2 (en) | Managing data flows in software-defined network using network interface card | |
| US9800502B2 (en) | Quantized congestion notification for computing environments | |
| US9244817B2 (en) | Remote debugging in a cloud computing environment | |
| KR101593463B1 (en) | Native cloud computing via network segmentation | |
| US9692706B2 (en) | Virtual enhanced transmission selection (VETS) for lossless ethernet | |
| CN108322467B (en) | OVS-based virtual firewall configuration method, electronic equipment and storage medium | |
| CN111490949A (en) | Method, network card, host device and computer system for forwarding data packets | |
| CN106557444B (en) | Method and device for realizing SR-IOV network card and method and device for realizing dynamic migration | |
| CN106105119B (en) | Method of operating a network entity, network entity and network | |
| US11729108B2 (en) | Queue management in a forwarder | |
| JP6783850B2 (en) | Methods and systems for limiting data traffic | |
| EP3029897A1 (en) | Network packet transmission method and device | |
| CN111371694B (en) | Shunting method, device and system, processing equipment and storage medium | |
| CN103634235A (en) | Method for limiting speed of network interface of virtual machine | |
| CN112437023A (en) | Virtualized security network element data processing method, system, medium and cloud platform | |
| WO2019033891A1 (en) | Rdma-based network traffic determination method and device | |
| CN108028806A (en) | The method and apparatus that virtual resource is distributed in network function virtualization NFV networks | |
| CN113553137B (en) | DPDK-based access capability network element high-speed data processing method under NFV architecture | |
| WO2018057165A1 (en) | Technologies for dynamically transitioning network traffic host buffer queues | |
| US11477122B2 (en) | Technologies for selecting non-minimal paths and throttling port speeds to increase throughput in a network | |
| WO2021120933A1 (en) | Resource adjusting method and apparatus | |
| US11228532B2 (en) | Method of executing QoS policy and network device | |
| KR101493933B1 (en) | Method, appratus, system and computer-readable recording medium for assisting communication of virtual machine using hardware switch and software switch |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |