US11032205B2 - Flow control method and switching device - Google Patents

Flow control method and switching device Download PDF

Info

Publication number
US11032205B2
US11032205B2 US16/448,730 US201916448730A US11032205B2 US 11032205 B2 US11032205 B2 US 11032205B2 US 201916448730 A US201916448730 A US 201916448730A US 11032205 B2 US11032205 B2 US 11032205B2
Authority
US
United States
Prior art keywords
flow
switching device
key flow
key
back pressure
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
Application number
US16/448,730
Other languages
English (en)
Other versions
US20190312816A1 (en
Inventor
Li Shen
Hong Zhou
Heyang Liu
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Publication of US20190312816A1 publication Critical patent/US20190312816A1/en
Assigned to HUAWEI TECHNOLOGIES CO., LTD. reassignment HUAWEI TECHNOLOGIES CO., LTD. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: LIU, HEYANG, SHEN, LI, ZHOU, HONG
Application granted granted Critical
Publication of US11032205B2 publication Critical patent/US11032205B2/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

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/26—Flow control; Congestion control using explicit feedback to the source, e.g. choke packets
    • H04L47/266—Stopping or restarting the source, e.g. X-on or X-off
    • 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/26—Flow control; Congestion control using explicit feedback to the source, e.g. choke packets
    • H04L47/263—Rate modification at the source after receiving feedback
    • 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/11—Identifying congestion
    • 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/10—Flow control; Congestion control
    • H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H04L47/2425—Traffic characterised by specific attributes, e.g. priority or QoS for supporting services specification, e.g. SLA
    • H04L47/2433—Allocation of priorities to traffic types
    • 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
    • H04L47/2483—Traffic characterised by specific attributes, e.g. priority or QoS involving identification of individual flows
    • 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/25—Flow control; Congestion control with rate being modified by the source upon detecting a change of network conditions
    • 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/26—Flow control; Congestion control using explicit feedback to the source, e.g. choke packets
    • 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/30—Flow control; Congestion control in combination with information about buffer occupancy at either end or at transit nodes
    • 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/41—Flow control; Congestion control by acting on aggregated flows or links

Definitions

  • the present disclosure relates to the field of network technologies, and in particular, to a flow control method and a switching device.
  • Flow control can effectively prevent impact on a network caused by an instant large amount of data, and ensure efficient and stable running of a user network.
  • Priority-based flow control is also referred to as per priority pause or class based flow control (CBFC), and is an improvement of an existing Ethernet pause mechanism.
  • CBFC per priority pause or class based flow control
  • the receive end may perform control by using a separate back pressure frame, and the back pressure frame is also referred to as a pause frame. As shown in FIG.
  • the receive end when congestion occurs in a receive queue whose priority is 7 in a receive end (for example, a device B), the receive end sends a back pressure frame to a transmit end (for example, a device A), to instruct the device A to pause sending of a data frame in a send queue whose priority is 7.
  • the device B may send a cancel back pressure frame to the device A, to instruct the device A to normally send the data frame in the send queue whose priority is 7.
  • another send queue and receive queue are not affected.
  • the device A feeds back a pause frame to all input ports that make the port 3 congested. Based on the pause frame fed back by the device A, the device B pauses sending of all data from a port 3 . Even if to-be-sent data in the port 3 of the device B does not aim to the port 3 of the device A, the device B pauses sending of the data. Consequently, header congestion is caused.
  • a downstream switching device sends a back pressure frame to an upstream switching device, so that a large quantity of switching devices pause packet sending in the network. Consequently, congestion diffusion occurs, a throughput rate is reduced, and an average delay is increased. As a result, performance of the entire network is degraded.
  • the present disclosure provides a flow control method and a switching device, to effectively alleviate congestion, avoid packet loss, and effectively control congestion diffusion, thereby improving network data exchange performance.
  • a first aspect provides a flow control method, including: when congestion is detected, determining, by a first switching device, a key flow from a plurality of data flows based on a preset condition; generating a back pressure message including a flow attribute value of the key flow; and sending the back pressure message to an upstream device of the key flow, where the back pressure message is used to instruct the upstream device of the key flow to pause sending of the key flow, and the back pressure message has no impact on sending of another data flow other than the key flow by the upstream device of the key flow.
  • the upstream device of the key flow is a second switching device and is connected to the first switching device.
  • a network device delays only sending of the key flow. Because the key flow includes more flow attributes, a granularity is smaller, and congestion diffusion can be reduced in comparison with pausing all data flows corresponding to priorities in the prior art, thereby improving network data exchange performance.
  • the first switching device before the generating a back pressure message including a flow attribute value of the key flow, creates a key flow virtual channel for the key flow, adds a subsequent packet that belongs to the key flow or a buffer address of the subsequent packet to the key flow virtual channel.
  • the subsequent packet is a packet that is received by the first switching device and that is not added to a send queue.
  • the first switching device can separate the key flow from a non-key flow, and sending of a packet of the non-key flow is not affected when sending of the key flow is paused.
  • the first switching device when a data amount of packets in a send queue corresponding to the key flow does not exceed a first preset threshold, extracts a packet of the key flow from a buffer corresponding to the key flow virtual channel, and adds the extracted packet to the send queue. According to this implementation, when detecting that no congestion occurs, the first switching device may continue to forward the key flow.
  • the first switching device after the packet address of the subsequent packet that belongs to the key flow is added to the key flow virtual channel, when a data amount of packets in the buffer corresponding to the key flow virtual channel exceeds a first preset value, the first switching device generates the back pressure message including the flow attribute value of the key flow. It can be learned that a switch may perform a back pressure procedure in different triggering conditions.
  • the first switching device when the data amount of the packets in the buffer corresponding to the key flow virtual channel does not exceed a second preset value, the first switching device generates a cancel back pressure message, and sends the cancel back pressure message to a second switching device.
  • the second preset value is less than or equal to the first preset value. It can be learned that a switch may perform a cancel back pressure procedure in different triggering conditions.
  • the preset condition is a preset traffic threshold
  • the determining a key flow from a plurality of data flows based on a preset condition may be: when detecting that the data amount of the packets in the send queue exceeds a second preset threshold, taking, by the first switching device, a data flow whose traffic is greater than the preset traffic threshold in the plurality of data flows as the key flow; or when detecting that congestion occurs in the send queue, determining, by the first switching device, a data amount of each data flow in the send queue, and taking a data flow with a largest data amount as the key flow.
  • a second aspect provides a flow control method, including: receiving, by a second switching device, a back pressure message sent by a first switching device; determining a key flow in a plurality of data flows based on a flow attribute value included in the back pressure message; and pausing sending of the key flow to the first switching device.
  • the second switching device pauses sending of the key flow, and the first switching device may forward a data flow by using a pause time, to resolve congestion.
  • the second switching device after the determining, by the second switching device, a key flow in a plurality of data flows based on a flow attribute value, the second switching device creates a key flow virtual channel for the key flow, adds a subsequent packet that belongs to the key flow or a buffer address of the subsequent packet to the key flow virtual channel.
  • the second switching device extracts a packet of the key flow from a buffer corresponding to the key flow virtual channel, and adds the extracted packet to a send queue.
  • the second switching device can separate the key flow from a non-key flow, and sending of a packet of the non-key flow is not affected when sending of the key flow is paused.
  • the second switching device after the receiving, by a second switching device, a back pressure message sent by a first switching device, the second switching device starts a timer based on the back pressure message; and when timing duration of the timer is not less than preset duration, the second switching device extracts the packet of the key flow from the buffer corresponding to the key flow virtual channel.
  • the second switching device when the second switching device does not receive a cancel back pressure message, the second switching device continues to send the key flow to the first switching device. Even if a cancel back pressure frame is lost in a transmission process, the second switching device may continue to send the key flow to the first switching device.
  • the second switching device when receiving the cancel back pressure message sent by the first switching device, extracts the packet of the key flow from the buffer corresponding to the key flow virtual channel. According to this implementation, when receiving the cancel back pressure message, the second switching device may continue to send the key flow to the first switching device.
  • a third aspect provides a switching device, and the switching device has functions of the first switching device that implements the flow control method provided in the first aspect.
  • the functions may be implemented by hardware, or may be implemented by hardware by executing corresponding software.
  • the hardware or the software includes one or more modules corresponding to the functions.
  • a fourth aspect provides a switching device, and the switching device has functions of the second switching device that implements the flow control method provided in the second aspect.
  • the functions may be implemented by hardware, or may be implemented by hardware by executing corresponding software.
  • the hardware or the software includes one or more modules corresponding to the functions.
  • the first switching device may determine, from a plurality of data flows, a key flow that causes congestion; and then send a plurality of attribute values of the key flow to an upstream device of the key flow.
  • the upstream device of the key flow may pause sending of the key flow to the first switching device.
  • a back pressure frame is transmitted to the upstream device, so that a related device in the entire network may pause sending of the key flow.
  • congestion is mainly caused by the key flow, congestion can be effectively alleviated, and packet loss can be avoided.
  • a granularity of data flow-based flow control is smaller than that of priority-based flow control. Only sending of the key flow is delayed in the present disclosure, and congestion diffusion can be reduced in comparison with pausing all data flows corresponding to priorities, thereby improving network data exchange performance.
  • FIG. 1 is a schematic flowchart of a flow control method in the prior art
  • FIG. 2 is another schematic flowchart of a flow control method in the prior art
  • FIG. 3 is a schematic structural diagram of an application scenario according to an embodiment of the present disclosure.
  • FIG. 4 is a schematic flowchart of a flow control method according to an embodiment of the present disclosure.
  • FIG. 5 is a schematic flowchart of a flow control method according to an embodiment of the present disclosure.
  • FIG. 6 is a schematic diagram of a key flow virtual channel and a send queue according to an embodiment of the present disclosure
  • FIG. 7 is a schematic diagram of a key flow virtual channel according to an embodiment of the present disclosure.
  • FIG. 8 is another schematic diagram of a key flow virtual channel according to an embodiment of the present disclosure.
  • FIG. 9 is another schematic flowchart of a flow control method according to an embodiment of the present disclosure.
  • FIG. 10 is another schematic flowchart of a flow control method according to an embodiment of the present disclosure.
  • FIG. 11 is another schematic flowchart of a flow control method according to an embodiment of the present disclosure.
  • FIG. 12 is another schematic flowchart of a flow control method according to an embodiment of the present disclosure.
  • FIG. 13 is another schematic flowchart of a flow control method according to an embodiment of the present disclosure.
  • FIG. 14 is a schematic structural diagram of a switching device according to an embodiment of the present disclosure.
  • FIG. 15 is another schematic structural diagram of a switching device according to an embodiment of the present disclosure.
  • FIG. 16 is another schematic structural diagram of a switching device according to an embodiment of the present disclosure.
  • FIG. 17 is another schematic structural diagram of a switching device according to an embodiment of the present disclosure.
  • FIG. 18 is another schematic structural diagram of a switching device according to an embodiment of the present disclosure.
  • FIG. 19 is another schematic structural diagram of a switching device according to an embodiment of the present disclosure.
  • FIG. 20 is another schematic structural diagram of a switching device according to an embodiment of the present disclosure.
  • a communications network to which the method is applied may be an Ethernet or a network constructed by an infiniBand technology.
  • the Ethernet is a standard Ethernet, a fast Ethernet, or a subsequently evolved Ethernet.
  • the communications network includes a host, a switching device, and a server.
  • the switching device may be a switch or a bridge device.
  • the switch is a network device configured to forward an optical or electrical signal.
  • the switch may provide an exclusive electrical signal path or optical signal path for any two network nodes that access the switch.
  • the host may be a device such as a mobile terminal (including but not limited to a notebook computer, a mobile phone, a tablet, a palmtop computer, a POS machine, an MP3, or a navigator), a fixed terminal (including but not limited to a desktop, a printer, a fax machine, a digital projector, or a digital television), or a wireless access terminal.
  • a mobile terminal including but not limited to a notebook computer, a mobile phone, a tablet, a palmtop computer, a POS machine, an MP3, or a navigator
  • a fixed terminal including but not limited to a desktop, a printer, a fax machine, a digital projector, or a digital television
  • a wireless access terminal including but not limited to a wireless access terminal.
  • the server is a device that provides a computing service.
  • the server is classified into a file server, a database server, an application server, a WEB server, and the like based on different service types provided by the server.
  • a core idea of the method is that sending of a data flow that mainly causes congestion in a network is delayed by using a back pressure frame, to resolve congestion. Because only sending of a key flow is delayed, a network device that does not transmit the key flow is not affected, and can still normally send a packet, thereby effectively reducing congestion diffusion.
  • an embodiment of a flow control method provided in the present disclosure includes the following steps.
  • Step 401 A first switching device determines a data flow to which a received packet belongs, and collects statistics about traffic of each data flow.
  • the switching device may determine, based on attribute values of one or more flow attributes, the data flow to which the received packet belongs.
  • the flow attributes include a source Internet Protocol (IP) address, a destination IP address, a protocol number, a source port number, a destination port number, a packet priority, and the like.
  • IP Internet Protocol
  • the first switching device creates a flow table, and collects statistics about the traffic of each data flow. For a specific method for determining a data flow, refer to the following embodiments.
  • the first switching device determines different data flows based on values of the source IP address and the packet priority. Packets included in each data flow have a same source IP address and packet priority. In another optional embodiment, the first switching device determines different data flows based on values of the source IP address, the destination IP address, and the packet priority. In another optional embodiment, the first switching device determines different data flows based on the source IP address, the destination IP address, the protocol number, the source port number, and the destination port number. In another optional embodiment, the first switching device determines different data flows based on the source IP address and the destination IP address.
  • Step 402 When congestion is detected, the first switching device determines a key flow from a plurality of data flows based on a preset condition.
  • the send queue may be a send queue of a port of the first switching device.
  • the first switching device may determine the key flow from the plurality of data flows based on the preset condition in a plurality of manners. For details, refer to the following embodiments.
  • the first switching device collects statistics about traffic of each data flow in a plurality of data flows that are sent within configuration duration by using the send queue, and takes a data flow whose traffic is greater than a preset traffic threshold in the plurality of data flows as the key flow.
  • a flow table is set in the switching device, the flow table includes a flow entry corresponding to each data flow, and each flow entry is used to record a quantity of bytes of packets that are sent by the switching device within the configuration duration and that belong to the data flow corresponding to the flow entry.
  • the switching device collects, based on the flow table, statistics about a quantity of bytes of each data flow sent within the configuration duration.
  • the preset traffic threshold is used to measure whether a data flow is a key flow, and a value of the preset traffic threshold may be set based on a sending capability of the switching device.
  • the switching device when detecting that congestion occurs in a send queue, collects statistics about a data amount of each data flow in the send queue, and takes a data flow with a largest data amount as the key flow. The data amount is represented by using a quantity of bytes.
  • a flow table is set in the switching device, the flow table includes a flow entry corresponding to each data flow, and the flow entry is used to record a queue corresponding to the data flow and a quantity of bytes in the queue.
  • the switching device Before scheduling a packet to the send queue, the switching device first searches the flow table. If a flow entry corresponding to a data flow to which the packet belongs can be found, a quantity of bytes of the packet is added to a quantity of bytes recorded in the flow entry.
  • a flow entry corresponding to a data flow to which the packet belongs cannot be found, it indicates that the data flow to which the packet belongs is not in any send queue, and the switching device creates the flow entry in the flow table for the data flow to which the packet belongs, and records a quantity of bytes of the packet in the flow entry.
  • the quantity of bytes of the packet is subtracted from a quantity of bytes recorded in the flow entry of the data flow to which the packet belongs. If a quantity of bytes recorded in a flow entry is 0, the flow entry is set to be invalid, and the flow entry is released.
  • a preset data amount is used to measure whether a data flow is a key flow, and a value of the preset data amount may be determined based on a total data capacity of a send queue and a congestion proportion. For example, the preset data amount is obtained by multiplying the total data capacity of the send queue by the congestion proportion.
  • the congestion proportion may be any percentage that is greater than 50% and less than 100%.
  • Step 403 The first switching device generates a back pressure message including a flow attribute value of the key flow.
  • the flow attribute value is attribute values of a plurality of flow attributes of the key flow.
  • the back pressure message may be a back pressure frame.
  • the first switching device may generate the back pressure message based on only a flow attribute value of a key flow with largest traffic. In this way, back pressure is first performed on the key flow with largest traffic, to pause sending of the key flow with largest traffic. If the first switching device is still in a congested state, the first switching device generates another back pressure message based on a flow attribute of a key flow with largest traffic in remaining key flows, and continues to perform back pressure on the remaining key flows until congestion of the first switching device is alleviated.
  • Flow count A quantity of flows carried in a current back pressure frame.
  • Flow Info Flow information, such as a source-destination IP address pair (including a source IP address and a destination IP address) and/or a priority. Pad (transmit Reserved. Its value is 0 during as zero) transmission.
  • Cyclic Redundancy check (Cyclic Redundancy Check, CRC for short).
  • Step 404 The first switching device sends the back pressure message to a second switching device.
  • the second switching device is an upstream device of the key flow for the first switching device.
  • Step 405 The second switching device determines the key flow in the plurality of data flows based on the flow attribute value included in the back pressure message, and pauses sending of the key flow to the first switching device.
  • the upstream device of the key flow is the second switching device connected to the first switching device.
  • the back pressure message is used to instruct the second switching device to pause sending of the key flow, thereby effectively alleviating congestion and avoiding packet loss.
  • the back pressure message has no impact on sending of another data flow other than the key flow by the second switching device. Therefore, in this embodiment of the present disclosure, all or some of data flows can be accurately controlled. Compared with the prior art, traffic is controlled more accurately and flexibly in this embodiment of the present disclosure.
  • step 401 to step 405 are a back pressure procedure between the first switching device and the second switching device.
  • the second switching device may continue to send a pause frame to an upstream device of the key flow. Another switching device may follow such a pattern. It can be learned that, according to this embodiment of the present disclosure, congestion can be resolved, packet loss can be avoided, and congestion diffusion can be effectively lessened.
  • Step 406 When a data amount of packets in a send queue corresponding to the key flow does not exceed a first preset threshold, the first switching device generates a cancel back pressure message.
  • the first preset threshold is less than or equal to the second preset threshold.
  • step 407 may be triggered.
  • Step 407 The first switching device sends the cancel back pressure message to the second switching device.
  • Step 408 The second switching device sends the key flow to the first switching device.
  • the second switching device When receiving the cancel back pressure message from the first switching device, the second switching device determines that a preset cancel back pressure condition is met, and sends the key flow to the first switching device. Alternatively, when receiving the back pressure message, the second switching device starts a timer, and when timing duration of the timer is not less than preset duration, the second switching device sends the key flow to the first switching device.
  • step 406 to step 408 are a cancel back pressure procedure.
  • the second switching device can continue to send the key flow to the first switching device, and may send a cancel back pressure frame to an upstream device of the key flow. Another switching device may follow such a pattern.
  • a switching device provided in the present disclosure may further create a key flow virtual channel for the key flow, to schedule the key flow.
  • FIG. 5 another embodiment of a flow control method provided in the present disclosure includes the following steps.
  • Step 501 A first switching device determines a data flow to which a received packet belongs, and collects statistics about traffic of each data flow.
  • Step 502 When congestion is detected, the first switching device determines a key flow from a plurality of data flows based on a preset condition. Step 501 and step 502 are similar to step 401 and step 402 .
  • Step 503 After determining the key flow from the plurality of data flows based on the preset condition, the first switching device creates a key flow virtual channel for the key flow, adds a subsequent packet that belongs to the key flow or a buffer address of the subsequent packet to the key flow virtual channel, and adds a subsequent packet of another data flow to a send queue corresponding to the another data flow.
  • the another data flow is different from the key flow.
  • the subsequent packet is a packet that is received by the first switching device and that is not added to a send queue.
  • the send queue corresponding to the another data flow may be the same as or different from a send queue corresponding to the key flow.
  • the switching device creates the key flow virtual channel for the key flow
  • the key flow virtual channel is a virtual channel that stores an address of a packet of the key flow.
  • the key flow virtual channel stores an address of a packet, and the packet is still stored in a buffer of the switching device, as shown in FIG. 6 .
  • the key flow virtual channel may be implemented in the following manners.
  • a first manner is shown in FIG. 7 . Only an address of a packet that first enters the key flow virtual channel and a statistics collection result of a quantity of bytes of the packet in the key flow virtual channel are stored in the key flow virtual channel, and packet addresses of subsequent packets are connected by using a packet pointer.
  • a second manner is shown in FIG. 8 . Each location of the key flow virtual channel stores an address of a packet, and statistics about a quantity of bytes of the packet in the key flow virtual channel is collected.
  • the first switching device schedules the subsequent packet. If the packet belongs to the key flow, data plane processing (for example, a table lookup operation or an encapsulation operation) is performed on the packet, and then a packet address of the packet is added to the key flow virtual channel; or a packet address of the packet is directly added to the key flow virtual channel. If the packet does not belong to the key flow, the packet is added to a port send queue after data plane processing is performed on the packet.
  • data plane processing for example, a table lookup operation or an encapsulation operation
  • Step 504 When a data amount of packets in a buffer corresponding to the key flow virtual channel exceeds a first preset value, it indicates that the buffer corresponding to the key flow virtual channel is difficult to accommodate more packets, it is determined that a preset back pressure condition is met, and the first switching device generates a back pressure message including a flow attribute value of the key flow.
  • the flow attribute value is attribute values of a plurality of flow attributes of the key flow.
  • the back pressure message may be a back pressure frame.
  • the key flow virtual channel further needs to reserve headroom for receiving an in-flight packet from an upstream device of the key flow.
  • the in-flight packet is a subsequent packet within a time from a moment of sending the back pressure frame for the key flow to a moment at which the upstream device receives the back pressure frame and the back pressure frame works.
  • Step 505 The first switching device sends the back pressure message to a second switching device. Step 505 is similar to step 404 .
  • Step 506 The second switching device determines the key flow in the plurality of data flows based on the flow attribute value included in the back pressure message, and pauses sending of the key flow to the first switching device.
  • the second switching device after determining the key flow, creates a key flow virtual channel for the key flow, adds a subsequent packet that belongs to the key flow or a buffer address of the subsequent packet to the key flow virtual channel of the second switching device, and adds a subsequent packet of another data flow to a send queue corresponding to the another data flow.
  • the another data flow is different from the key flow.
  • Step 507 When detecting that the data amount of the packets in the buffer corresponding to the key flow virtual channel does not exceed a second preset value, the first switching device generates a cancel back pressure message.
  • a data amount of packets in the send queue corresponding to the key flow does not exceed a first preset threshold, it indicates that the first switching device is in a non-congested state, and the first switching device extracts, based on a packet address in the key flow virtual channel, a packet from the buffer corresponding to the key flow, and adds the extracted packet to the send queue.
  • a second preset threshold is not less than the first preset threshold.
  • Step 508 The first switching device sends the cancel back pressure message to the second switching device.
  • Step 509 The second switching device sends the key flow to the first switching device.
  • the second switching device When receiving the cancel back pressure message sent by the first switching device, the second switching device determines that the preset cancel back pressure condition is met, extracts a packet from the buffer based on a packet address in the key flow virtual channel, and adds the extracted packet to a send queue.
  • the second switching device starts a timer; and when timing duration of the timer is not less than preset duration, the second switching device extracts, based on a packet address in the key flow virtual channel, a packet of the key flow from the buffer corresponding to the key flow, and adds the extracted packet of the key flow to a send queue.
  • FIG. 9 another embodiment of a flow control method provided in the present disclosure includes the following steps.
  • Step 901 A first switching device determines a data flow to which a received packet belongs, and collects statistics about traffic of each data flow.
  • Step 902 When congestion is detected, the first switching device determines a key flow from a plurality of data flows based on a preset condition.
  • Step 903 The first switching device generates a back pressure message including a flow attribute value of the key flow.
  • the flow attribute value is attribute values of a plurality of flow attributes of the key flow.
  • the back pressure message may be a back pressure frame.
  • Step 901 to step 903 are similar to step 401 to step 403 .
  • Step 904 The first switching device sends the back pressure message to a server.
  • the back pressure message is used to instruct the server to pause sending of the key flow, and the back pressure message has no impact on sending of another data flow other than the key flow by the server.
  • An upstream device of the key flow is the server connected to the first switching device.
  • the first switching device converts the back pressure frame in the embodiment in FIG. 4 into a pause frame of standard PFC, and sends the pause frame to the server.
  • a network adapter of the server can trigger a back pressure procedure without supporting the back pressure frame in the present disclosure.
  • Step 905 The server determines the key flow in the plurality of data flows based on the flow attribute value, and pauses sending of the key flow to the first switching device.
  • the server may schedule a packet of the key flow at an application layer.
  • a scheduling method may be pausing sending of the packet of the key flow, or may be reducing a rate of sending the packet of the key flow.
  • Step 906 When a data amount of packets in a send queue corresponding to the key flow does not exceed a first preset threshold, the first switching device generates a cancel back pressure message. When the data amount of the packets in the send queue corresponding to the key flow does not exceed the first preset threshold, it indicates that the send queue is in a non-congested state and has a capability of continuing to send more data, the first switching device generates the cancel back pressure message, and step 937 is triggered.
  • Step 907 The first switching device sends the cancel back pressure message to the server.
  • Step 908 The server sends the key flow to the first switching device.
  • the server determines that a preset cancel back pressure condition is met, and sends the key flow to the first switching device.
  • the server starts a timer; and when timing duration of the timer is not less than preset duration, the server determines that a preset cancel back pressure condition is met, and sends the key flow to the first switching device.
  • a switching device provided in the present disclosure may further create a key flow virtual channel for the key flow, to schedule the key flow.
  • FIG. 10 another embodiment of a flow control method provided in the present disclosure includes the following steps.
  • Step 1001 A first switching device determines a data flow to which a received packet belongs, and collects statistics about traffic of each data flow.
  • Step 1002 When congestion is detected, the first switching device determines a key flow from a plurality of data flows based on a preset condition.
  • Step 1003 After determining the key flow from the plurality of data flows based on the preset condition, the first switching device creates a key flow virtual channel for the key flow, adds a subsequent packet that belongs to the key flow or a buffer address of the subsequent packet to the key flow virtual channel, and adds a subsequent packet of another data flow to a send queue corresponding to the another data flow.
  • the another data flow is different from the key flow.
  • the subsequent packet is a packet that is received by the first switching device and that is not added to a send queue.
  • Step 1004 When a data amount of packets in a buffer corresponding to the key flow virtual channel exceeds a first preset value, the first switching device generates a back pressure message including a flow attribute value of the key flow.
  • the flow attribute value is attribute values of a plurality of flow attributes of the key flow.
  • the back pressure message may be a back pressure frame.
  • Step 1001 to step 1004 are similar to step 501 to step 504 .
  • Step 1005 The first switching device sends the back pressure message to a server.
  • An upstream device of the key flow is the server connected to the first switching device.
  • the first switching device converts the back pressure frame in the embodiment shown in FIG. 4 into a pause frame of standard PFC, and sends the pause frame to the server. In this manner, a network adapter of the server can trigger a back pressure procedure without supporting the back pressure frame in the present disclosure.
  • Step 1006 The server determines the key flow in the plurality of data flows based on the flow attribute value included in the back pressure message, and pauses sending of the key flow to the first switching device.
  • the server After receiving the back pressure frame, the server schedules a packet of the key flow at an application layer.
  • a scheduling method may be pausing sending of the key flow, or may be reducing a rate of sending the packet of the key flow.
  • Step 1007 When detecting that the data amount of the packets in the buffer corresponding to the key flow virtual channel does not exceed a second preset value, the first switching device generates a cancel back pressure message. Step 1007 is similar to step 507 .
  • Step 1008 The first switching device sends the cancel back pressure message to the server.
  • Step 1009 The server sends the key flow to the first switching device.
  • Step 1008 and step 1009 are similar to step 907 and step 908 .
  • sending the key flow in this embodiment of the present disclosure means sending a packet that belongs to the key flow.
  • a switch A has four ports: a port 1 , a port 2 , a port 3 , and a port 4 .
  • a send queue is configured for each port.
  • a flow table is created, where attributes of the flow table include a source IP address, a destination IP address, and a priority, and a queue number is stored.
  • Statistics about an amount of data sent within the configuration duration (for example, 1 ms) is collected, and traffic of each flow is calculated.
  • Manner 1 When a quantity of bytes of packets in a send queue of the port 3 of the switch A exceeds a preset threshold, it indicates that congestion occurs in the port 3 .
  • flows of the queue include a flow 1 , a flow 2 , . . . , and a flow n. If traffic of an i th flow exceeds a preset traffic threshold, the i th flow is the key flow.
  • Manner 2 When a quantity of bytes of packets in a send queue of the port 3 of the switch A exceeds a preset threshold, and flows of the queue include a flow 1 , a flow 2 , . . . , and a flow n in this case, if a quantity of bytes included in an i th flow in the queue is the largest, the i th flow is the key flow.
  • the switch A adds an address of a packet of the i th flow in a buffer to a key flow virtual channel instead of the send queue, and a packet of another flow continues to be added to the send queue of the port 3 .
  • the switch A queries an upstream device, such as a switch B, of the key flow based on a routing table.
  • the switch A sends a back pressure frame to the switch B.
  • the back pressure frame includes a source-destination IP address pair and a priority.
  • An example in which the source-destination IP address pair is x.x.x.3 and x.x.x.100 and the priority is 3 is used.
  • the switch B determines, based on the source-destination IP address pair (namely, x.x.x.3 and x.x.x.100) and the priority (namely, 3) that are included in the back pressure frame, that a flow whose source IP address is x.x.x.3, destination IP address is x.x.x.100, and priority is 3 is the key flow, and adds a packet address of a subsequent packet of the key flow to a key flow virtual channel of the switch B. If a quantity of bytes of packets in a buffer corresponding to the key flow virtual channel of the switch B exceeds a preset value, the switch B continues to send the back pressure frame to an upstream device of the key flow.
  • the source-destination IP address pair namely, x.x.x.3 and x.x.x.100
  • the priority namely, 3
  • the switch A may send a cancel back pressure frame to the switch B.
  • the switch B extracts a packet from the buffer corresponding to the key flow virtual channel, and adds the packet to a send queue of the switch B.
  • the back pressure frame is sent to all transmit ends of packets in the send queue, for example, the switch B, a switch C, and a switch D.
  • the switch B, the switch C, and the switch D each receive the back pressure frame, a queue with a corresponding priority is paused.
  • the back pressure frame is sent to only the switch B.
  • the switch B pauses only sending of the key flow, and a packet that does not belong to the key flow is still normally sent. In this way, sending of a large data flow is delayed and a small data flow is normally sent in a network.
  • the present disclosure on a basis of alleviating congestion and avoiding packet loss, congestion diffusion can be reduced, and header congestion can be resolved.
  • the small data flow is sensitive to a delay, the small data flow is normally sent in the present disclosure, and a delay of the small data flow is not affected.
  • An embodiment of the switching device 1400 includes: a determining module 1401 , configured to: when congestion is detected, determine a key flow from a plurality of data flows based on a preset condition; a first generation module 1402 , configured to generate a back pressure message including a flow attribute value of the key flow; and a sending module 1403 , configured to send the back pressure message to an upstream device of the key flow, where the back pressure message is used to instruct the upstream device of the key flow to pause sending of the key flow, the upstream device of the key flow is connected to the first switching device, and the back pressure message has no impact on sending of another data flow other than the key flow by the upstream device of the key flow.
  • the switching device 1400 further includes a scheduling module 1501 , configured to: before the first generation module 1402 generates the back pressure message including the flow attribute value of the key flow, create a key flow virtual channel for the key flow, add a subsequent packet that belongs to the key flow or a buffer address of the subsequent packet to the key flow virtual channel, and add a subsequent packet of another data flow to a send queue corresponding to the another data flow.
  • a scheduling module 1501 configured to: before the first generation module 1402 generates the back pressure message including the flow attribute value of the key flow, create a key flow virtual channel for the key flow, add a subsequent packet that belongs to the key flow or a buffer address of the subsequent packet to the key flow virtual channel, and add a subsequent packet of another data flow to a send queue corresponding to the another data flow.
  • the scheduling module 1501 is further configured to: when a data amount of packets in a send queue corresponding to the key flow does not exceed a first preset threshold, extract a packet of the key flow from a buffer corresponding to the key flow virtual channel, and add the extracted packet to the send queue.
  • the first generation module 1402 is configured to: when a data amount of packets in the buffer corresponding to the key flow virtual channel exceeds a first preset value, generate the back pressure message including the flow attribute value of the key flow.
  • the switching device 1400 further includes a second generation module 1601 , configured to: when the scheduling module 1501 determines that the data amount of the packets in the buffer corresponding to the key flow virtual channel does not exceed a second preset value, generate a cancel back pressure message.
  • a second generation module 1601 configured to: when the scheduling module 1501 determines that the data amount of the packets in the buffer corresponding to the key flow virtual channel does not exceed a second preset value, generate a cancel back pressure message.
  • the sending module 1403 is further configured to send the cancel back pressure message to a second switching device, where the second preset value is less than or equal to the first preset value.
  • the determining module 1401 is configured to: when detecting that the data amount of the packets in the send queue exceeds a second preset threshold, use a data flow whose traffic is greater than the preset traffic threshold in the plurality of data flows as the key flow; or when detecting that congestion occurs in the send queue, determine a data amount of each data flow in the send queue, and use a data flow with a largest data amount as the key flow.
  • An embodiment of the switching device 1700 includes: a receiving module 1701 , configured to receive a back pressure message sent by a first switching device, where the back pressure message includes a flow attribute value; a determining module 1702 , configured to determine a key flow in a plurality of data flows based on the flow attribute value; and a sending module 1703 , configured to pause sending of the key flow to the first switching device.
  • the switching device 1700 further includes a scheduling module 1801 , configured to: create a key flow virtual channel for the key flow, add a subsequent packet that belongs to the key flow or a buffer address of the subsequent packet to the key flow virtual channel, and add a subsequent packet that does not belong to the key flow to a send queue, where the subsequent packet is a packet that is received by the second switching device and that is not added to the send queue.
  • a scheduling module 1801 configured to: create a key flow virtual channel for the key flow, add a subsequent packet that belongs to the key flow or a buffer address of the subsequent packet to the key flow virtual channel, and add a subsequent packet that does not belong to the key flow to a send queue, where the subsequent packet is a packet that is received by the second switching device and that is not added to the send queue.
  • the scheduling module 1801 is further configured to: when detecting that information meets a preset cancel back pressure condition, extract a packet of the key flow from a buffer corresponding to the key flow virtual channel, and add the extracted packet to the send queue.
  • the switching device 1700 further includes: a timing module 1901 , configured to start a timer based on the back pressure message.
  • the scheduling module 1801 is configured to: when timing duration of the timer is not less than preset duration, extract the packet of the key flow from the buffer corresponding to the key flow virtual channel.
  • the scheduling module 1801 is configured to: when the receiving module 1701 receives a cancel back pressure message sent by the first switching device, extract the packet of the key flow from the buffer corresponding to the key flow virtual channel.
  • the present disclosure provides a switching device 2000 .
  • An embodiment of the switching device 2000 provided in the present disclosure includes one or more network interfaces 2001 , one or more processors 2002 , and one or more memories 2003 .
  • the network interface 2001 , the processor 2002 , and the memory 2003 are connected to and communicate with each other by using a bus.
  • the processor 2002 may include a central processing unit CPU), a network processor NP), or the like; or may be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or another programmable logic device, or the like.
  • CPU central processing unit
  • NP network processor
  • DSP digital signal processor
  • ASIC application-specific integrated circuit
  • FPGA field-programmable gate array
  • the memory 2003 may include a random access memory (RAM) or a read-only memory (ROM), or may include a non-volatile memory (NVM), for example, at least one magnetic disk storage.
  • RAM random access memory
  • ROM read-only memory
  • NVM non-volatile memory
  • the memory 2003 is configured to store data and an operation instruction.
  • the processor 2002 may perform the method performed by the first switching device in the embodiment or the optional embodiment shown in FIG. 4 , FIG. 5 , FIG. 9 , or FIG. 10 , or may perform the method performed by the second switching device in the embodiment or the optional embodiment shown in FIG. 4 or FIG. 5 .
  • the disclosed system, apparatus, and method may be implemented in other manners.
  • the described apparatus embodiment is merely an example.
  • the unit division is merely logical function division and may be other division during actual implementation.
  • a plurality of units or components may be combined or integrated into another system, or some features may be ignored or not performed.
  • the displayed or discussed mutual couplings or direct couplings or communication connections may be implemented by using some interfaces.
  • the indirect couplings or communication connections between the apparatuses or units may be implemented in electrical, mechanical, or other forms.
US16/448,730 2016-12-23 2019-06-21 Flow control method and switching device Active US11032205B2 (en)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
CN201611204785.X 2016-12-23
CN201611204785.XA CN108243116B (zh) 2016-12-23 2016-12-23 一种流量控制方法及交换设备
PCT/CN2017/109376 WO2018113426A1 (zh) 2016-12-23 2017-11-03 一种流量控制方法及交换设备

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/109376 Continuation WO2018113426A1 (zh) 2016-12-23 2017-11-03 一种流量控制方法及交换设备

Publications (2)

Publication Number Publication Date
US20190312816A1 US20190312816A1 (en) 2019-10-10
US11032205B2 true US11032205B2 (en) 2021-06-08

Family

ID=62624527

Family Applications (1)

Application Number Title Priority Date Filing Date
US16/448,730 Active US11032205B2 (en) 2016-12-23 2019-06-21 Flow control method and switching device

Country Status (4)

Country Link
US (1) US11032205B2 (zh)
EP (1) EP3547627A4 (zh)
CN (1) CN108243116B (zh)
WO (1) WO2018113426A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20230061885A1 (en) * 2021-08-24 2023-03-02 Hewlett Packard Enterprise Development Lp Method and system for dynamic quota-based congestion management

Families Citing this family (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP6926953B2 (ja) * 2017-10-31 2021-08-25 富士通株式会社 情報処理装置、情報処理方法及びプログラム
CN110708255B (zh) * 2018-07-09 2021-11-19 华为技术有限公司 一种报文控制方法及节点设备
CN109218308A (zh) * 2018-09-14 2019-01-15 上海赋华网络科技有限公司 一种基于智能网卡的数据高速安全交换方法
CN111431811A (zh) * 2019-01-10 2020-07-17 华为技术有限公司 一种报文传输控制方法、装置和网络设备
CN112054964B (zh) * 2019-06-05 2023-11-28 中兴通讯股份有限公司 队列拥塞控制方法、装置、设备及存储介质
CN113132246B (zh) * 2019-12-30 2024-04-26 华为技术有限公司 一种流量控制方法及相关设备
CN113141311A (zh) * 2020-01-19 2021-07-20 华为技术有限公司 一种用于获取转发信息的方法及装置
CN113452471A (zh) * 2020-03-26 2021-09-28 伊姆西Ip控股有限责任公司 用于数据处理的方法、电子设备以及计算机程序产品
CN114868370A (zh) * 2020-11-20 2022-08-05 柏思科技有限公司 用于减少网络时延的方法和系统
EP4236254A4 (en) * 2020-11-30 2023-11-22 Huawei Technologies Co., Ltd. MESSAGE PROCESSING METHOD AND APPARATUS
CN115378955A (zh) * 2021-05-21 2022-11-22 华为技术有限公司 一种数据处理方法以及相关设备
CN115022243B (zh) * 2022-06-28 2023-05-26 绿盟科技集团股份有限公司 数据流量控制方法、装置、系统、电子设备及存储介质

Citations (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6108713A (en) * 1997-02-11 2000-08-22 Xaqti Corporation Media access control architectures and network management systems
US20030016628A1 (en) * 2001-07-23 2003-01-23 Broadcom Corporation Flow based congestion control
US20030156542A1 (en) * 2002-02-19 2003-08-21 Intel Corporation Congestion indication for flow control
US6628613B1 (en) * 1998-10-12 2003-09-30 Samsung Electronics Co. Ltd Flow control method in packet switched network
US20050089054A1 (en) * 2003-08-11 2005-04-28 Gene Ciancaglini Methods and apparatus for provisioning connection oriented, quality of service capabilities and services
US20050174941A1 (en) 2004-02-09 2005-08-11 Shanley Timothy M. Methods and apparatus for controlling the flow of multiple signal sources over a single full duplex ethernet link
US20060092836A1 (en) * 2004-10-29 2006-05-04 Broadcom Corporation Intelligent congestion feedback apparatus and method
US20090300209A1 (en) * 2008-06-03 2009-12-03 Uri Elzur Method and system for path based network congestion management
CN101854402A (zh) 2010-05-31 2010-10-06 中兴通讯股份有限公司 接口转换装置及流控实现方法
US20120063493A1 (en) * 2009-03-06 2012-03-15 Yohei Hasegawa Transmission rate control method, transmission unit, and communication system
CN102469492A (zh) 2010-11-12 2012-05-23 中兴通讯股份有限公司 一种无线通信网络中接纳控制的方法及装置
US20120254483A1 (en) 2010-11-12 2012-10-04 Huawei Technologies Co., Ltd. Data transmission method, device and system
US20140025837A1 (en) * 2012-07-18 2014-01-23 Skyfire Labs, Inc. Just-In-Time Distributed Video Cache
CN103997465A (zh) 2014-05-27 2014-08-20 华为技术有限公司 一种生成cnm的方法及设备
US20140269319A1 (en) 2013-03-15 2014-09-18 International Business Machines Corporation Network per-flow rate limiting
US8873392B1 (en) 2011-06-09 2014-10-28 Marvell International Ltd. Method and apparatus for controlling the flow of packets in a data network
US10063481B1 (en) * 2015-11-10 2018-08-28 U.S. Department Of Energy Network endpoint congestion management
US20190059023A1 (en) * 2016-02-25 2019-02-21 Telefonaktiebolaget Lm Ericsson (Publ) Back-pressure control in a telecommunications network

Patent Citations (22)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6108713A (en) * 1997-02-11 2000-08-22 Xaqti Corporation Media access control architectures and network management systems
US6628613B1 (en) * 1998-10-12 2003-09-30 Samsung Electronics Co. Ltd Flow control method in packet switched network
US20110110236A1 (en) * 2001-07-23 2011-05-12 Shiri Kadambi Multiple Logical Channels for Use in Network Devices
US20030016628A1 (en) * 2001-07-23 2003-01-23 Broadcom Corporation Flow based congestion control
US20030156542A1 (en) * 2002-02-19 2003-08-21 Intel Corporation Congestion indication for flow control
US20050089054A1 (en) * 2003-08-11 2005-04-28 Gene Ciancaglini Methods and apparatus for provisioning connection oriented, quality of service capabilities and services
US20050174941A1 (en) 2004-02-09 2005-08-11 Shanley Timothy M. Methods and apparatus for controlling the flow of multiple signal sources over a single full duplex ethernet link
CN1918850A (zh) 2004-02-09 2007-02-21 美商传威股份有限公司 用于控制单个全双工以太网链路上的多个信号源流量的方法和设备
US20060092836A1 (en) * 2004-10-29 2006-05-04 Broadcom Corporation Intelligent congestion feedback apparatus and method
US20090300209A1 (en) * 2008-06-03 2009-12-03 Uri Elzur Method and system for path based network congestion management
US20120063493A1 (en) * 2009-03-06 2012-03-15 Yohei Hasegawa Transmission rate control method, transmission unit, and communication system
CN101854402A (zh) 2010-05-31 2010-10-06 中兴通讯股份有限公司 接口转换装置及流控实现方法
US20120254483A1 (en) 2010-11-12 2012-10-04 Huawei Technologies Co., Ltd. Data transmission method, device and system
CN102469492A (zh) 2010-11-12 2012-05-23 中兴通讯股份有限公司 一种无线通信网络中接纳控制的方法及装置
US8873392B1 (en) 2011-06-09 2014-10-28 Marvell International Ltd. Method and apparatus for controlling the flow of packets in a data network
US20140025837A1 (en) * 2012-07-18 2014-01-23 Skyfire Labs, Inc. Just-In-Time Distributed Video Cache
US20140269319A1 (en) 2013-03-15 2014-09-18 International Business Machines Corporation Network per-flow rate limiting
CN103997465A (zh) 2014-05-27 2014-08-20 华为技术有限公司 一种生成cnm的方法及设备
EP2950489A1 (en) 2014-05-27 2015-12-02 Huawei Technologies Co., Ltd. Method and device for generating cnm
US20150350049A1 (en) 2014-05-27 2015-12-03 Huawei Technologies Co., Ltd. Method and device for generating cnm
US10063481B1 (en) * 2015-11-10 2018-08-28 U.S. Department Of Energy Network endpoint congestion management
US20190059023A1 (en) * 2016-02-25 2019-02-21 Telefonaktiebolaget Lm Ericsson (Publ) Back-pressure control in a telecommunications network

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20230061885A1 (en) * 2021-08-24 2023-03-02 Hewlett Packard Enterprise Development Lp Method and system for dynamic quota-based congestion management
US11824792B2 (en) * 2021-08-24 2023-11-21 Hewlett Packard Enterprise Development Lp Method and system for dynamic quota-based congestion management

Also Published As

Publication number Publication date
EP3547627A4 (en) 2019-10-16
EP3547627A1 (en) 2019-10-02
US20190312816A1 (en) 2019-10-10
CN108243116A (zh) 2018-07-03
WO2018113426A1 (zh) 2018-06-28
CN108243116B (zh) 2021-09-14

Similar Documents

Publication Publication Date Title
US11032205B2 (en) Flow control method and switching device
US11190449B2 (en) Packet control method and network apparatus
US9819590B2 (en) Method and apparatus for notifying network abnormality
JP5233504B2 (ja) 経路制御装置およびパケット廃棄方法
US20060203730A1 (en) Method and system for reducing end station latency in response to network congestion
TWI543568B (zh) 用於分封交換網路的系統及其方法、在分封交換網路中用於接收資料包的交換機中的方法
US20220303217A1 (en) Data Forwarding Method, Data Buffering Method, Apparatus, and Related Device
CN107342906B (zh) 一种大象流的检测方法、设备及系统
US20110080834A1 (en) Communication apparatus and communication control method
EP3742688A1 (en) Flow control method and apparatus
JP2021516012A (ja) ネットワークにおけるフロー管理
CN107547442B (zh) 数据传输缓存队列分配方法及装置
US10728156B2 (en) Scalable, low latency, deep buffered switch architecture
JPWO2012147909A1 (ja) ネットワーク装置、通信システム、異常トラヒックの検出方法およびプログラム
CN103281257A (zh) 一种协议报文处理方法和设备
US20220210036A1 (en) Network Measurement System And Method, Device, And Storage Medium
WO2022028342A1 (zh) 一种拥塞流的处理方法及设备
WO2016062067A1 (zh) 一种用户报文的转发控制方法以及处理节点
US20220166721A1 (en) Traffic balancing method, network device, and electronic device
CN107231316B (zh) 报文的传输方法及装置
CN113114578B (zh) 一种流量拥塞隔离方法、装置和系统
CN110336759B (zh) 基于rdma的协议报文转发方法及装置
US11824792B2 (en) Method and system for dynamic quota-based congestion management
CN114765585B (zh) 一种服务质量检测方法、报文处理方法及装置
WO2017041569A1 (zh) 业务数据传输方法及装置

Legal Events

Date Code Title Description
FEPP Fee payment procedure

Free format text: ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: BIG.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

STPP Information on status: patent application and granting procedure in general

Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION

AS Assignment

Owner name: HUAWEI TECHNOLOGIES CO., LTD., CHINA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:SHEN, LI;ZHOU, HONG;LIU, HEYANG;REEL/FRAME:052895/0870

Effective date: 20200609

STPP Information on status: patent application and granting procedure in general

Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER

STPP Information on status: patent application and granting procedure in general

Free format text: NOTICE OF ALLOWANCE MAILED -- APPLICATION RECEIVED IN OFFICE OF PUBLICATIONS

STPP Information on status: patent application and granting procedure in general

Free format text: PUBLICATIONS -- ISSUE FEE PAYMENT RECEIVED

STPP Information on status: patent application and granting procedure in general

Free format text: PUBLICATIONS -- ISSUE FEE PAYMENT VERIFIED

STPP Information on status: patent application and granting procedure in general

Free format text: AWAITING TC RESP, ISSUE FEE PAYMENT VERIFIED

STPP Information on status: patent application and granting procedure in general

Free format text: PUBLICATIONS -- ISSUE FEE PAYMENT VERIFIED

STCF Information on status: patent grant

Free format text: PATENTED CASE