CN108243117B - Flow monitoring method and device and electronic equipment - Google Patents

Flow monitoring method and device and electronic equipment Download PDF

Info

Publication number
CN108243117B
CN108243117B CN201810002681.3A CN201810002681A CN108243117B CN 108243117 B CN108243117 B CN 108243117B CN 201810002681 A CN201810002681 A CN 201810002681A CN 108243117 B CN108243117 B CN 108243117B
Authority
CN
China
Prior art keywords
congestion
message
tag
priority
qcn
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
CN201810002681.3A
Other languages
Chinese (zh)
Other versions
CN108243117A (en
Inventor
戎衍博
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.)
New H3C Technologies Co Ltd
Original Assignee
New H3C 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 New H3C Technologies Co Ltd filed Critical New H3C Technologies Co Ltd
Priority to CN201810002681.3A priority Critical patent/CN108243117B/en
Publication of CN108243117A publication Critical patent/CN108243117A/en
Application granted granted Critical
Publication of CN108243117B publication Critical patent/CN108243117B/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
    • 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/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
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/50—Reducing energy consumption in communication networks in wire-line communication networks, e.g. low power modes or reduced link rate

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

The embodiment of the application provides a flow monitoring method, a flow monitoring device and electronic equipment, which are applied to the technical field of computer communication, wherein the method comprises the following steps: adding a congestion tag in a currently received message which does not carry the congestion tag; sending the message added with the congestion label to downstream QCN equipment; receiving a pause frame sent by downstream QCN equipment when a message in a sending port is congested, wherein the pause frame carries a congestion label of the congestion message and the priority of the congestion message; and carrying out speed reduction forwarding on the messages with the congestion labels of the congestion messages and the priority of the congestion messages in the messages to be sent to the downstream QCN equipment. According to the embodiment of the application, the message sending rate of the upstream QCN equipment is reduced, so that the message in the sending port of the downstream QCN equipment is not congested any more, and meanwhile, the message sending rates of other sending ports of the downstream QCN equipment are not reduced.

Description

Flow monitoring method and device and electronic equipment
Technical Field
The present application relates to the field of computer communication technologies, and in particular, to a method and an apparatus for monitoring traffic and an electronic device.
Background
QCN (Quantized Congestion Notification) is an end-to-end Congestion Notification mechanism applied to a two-layer network, and reduces packet loss rate and delay of a packet in the network through active reverse Notification, thereby improving network performance. Referring to FIG. 1, FIG. 1 is a schematic view of the operation principle of QCN, CP
A (Congestion Point) end periodically samples a queue using a QCN, and when the queue is congested, a CP end generates a CNM (Congestion Notification Message) Message to notify a data source end, that is, an RP (Reaction Point) end, that is, a MAC (Media Access Control) address of the CP end is a source MAC address of the CNM Message, and a MAC address of an RP end generating the Congestion Message is a destination MAC address of the CNM Message, and the CNM Message is sent to the RP end. And the RP end reduces the flow sending rate after receiving the CNM message, and performs flow speed reduction. Meanwhile, the RP end also periodically detects the bandwidth, and then improves the flow sending rate when the CNM message is not received within a certain time.
Referring to fig. 2, fig. 2 is a schematic view of traffic forwarding of a QCN network, all QCN devices (CP1, CP2, and CP3) monitor data traffic dot1p4 and dot1p5, and if a queue corresponding to dot1p4 and dot1p5 on CP3 is congested, CP3 returns a CNM message to notify RP1 of reducing the rate of related messages in the queue. However, if the queues corresponding to the data traffic volumes dot1p2 and dot1p3 on the CP3 are congested, since the data traffic volumes dot1p2 and dot1p3 belong to CND (Congestion Notification Domain) out-of-Domain data traffic volumes, the queues corresponding to the data traffic volumes dot1p2 and dot1p3 are not monitored by the QCN, and the rate cannot be reduced by the QCN mechanism. At this time, a large number of messages are discarded on the Eth1/1 port of the CP3, and the upstream QCN device CP2 of the CP3 still forwards the messages in the queues corresponding to the dot1p2 and the dot1p3, where the queues occupy the bandwidth of the upstream QCN device, and affect the traffic forwarding of the RP 1. To inform the upstream QCN device of CP3 to reduce the rate of dot1p2, dot1p3, a flow control function, i.e., a flow-control function, may be configured on the Eth1/2 port of CP3 and the Eth1/3 port of CP 2. The flow-control function is specifically that, if the Eth1/1 port of the CP3 is congested, the CP3 extracts the priority of a congestion message from the Eth1/1 port, discards the congestion message, and then sends a pause frame to the CP2, where the pause frame includes the priority of the congestion message. After receiving the pause frame, the CP2 reduces the sending rate of the message with the priority, and sends the message with the reduced rate to the CP 3. Therefore, the message loss caused by the congestion of the CP3 can be avoided through the flow-control function.
However, the messages in the queues corresponding to dot1p2 and dot1p3 are not only forwarded to RP2 but also to RP3 through CP3, and the Eth1/3 port connected to RP3 is not congested, and theoretically, it is not necessary to reduce the speed of the messages forwarded to RP 3. The flow-control function of CP2 slows down the message with the assigned priority (i.e. the priority of the congested message), which finally results in that the message forwarded to RP3 is also slowed down, i.e. the rate of the message in the sending port without congestion is reduced.
Disclosure of Invention
The present application aims to provide a flow monitoring method, a flow monitoring device, and an electronic device, which, when a packet is congested in a sending port of a QCN device, enable the packet to be no longer congested in the sending port of the QCN device, and at the same time, do not reduce the rate of the packet in other sending ports of the QCN device. The specific technical scheme is as follows:
the application provides a flow monitoring method, which is applied to upstream QCN equipment and comprises the following steps:
adding a congestion tag in a currently received message which does not carry the congestion tag, wherein the added congestion tag is different from the congestion tag of the received message carrying the congestion tag;
sending the message added with the congestion label to downstream QCN equipment;
receiving a pause frame sent by the downstream QCN equipment when a message in a sending port is congested, wherein the pause frame carries a congestion label of the congested message and the priority of the congested message, and the congested message is a message discarded by the downstream QCN equipment in a message from the upstream QCN equipment;
and carrying out speed reduction forwarding on the message with the congestion label of the congestion message and the priority of the congestion message in the message to be sent to the downstream QCN equipment.
The application provides a flow monitoring method, which is applied to downstream QCN equipment and comprises the following steps:
receiving a message which is sent by upstream QCN equipment and added with a congestion label;
when the message in the sending port is congested by the downstream QCN equipment, identifying a congestion label of the congestion message in the sending port and the priority of the congestion message, wherein the congestion message is a message discarded by the downstream QCN equipment in the message from the upstream QCN equipment;
sending a congestion tag carrying the congestion message and a pause frame of the priority of the congestion message to the upstream QCN equipment;
and receiving a speed reduction message forwarded by the upstream QCN equipment, wherein the speed reduction message is a message obtained after the upstream QCN equipment performs speed reduction on a message to be sent to the downstream QCN equipment, a congestion label of the congestion message and a message with the priority of the congestion message.
The application provides a flow monitoring device, is applied to upstream QCN equipment, and the device includes:
the congestion tag adding module is used for adding a congestion tag in a currently received message which does not carry the congestion tag, wherein the added congestion tag is different from the congestion tag of the received message carrying the congestion tag;
the message sending module is used for sending the message added with the congestion label to downstream QCN equipment;
a pause frame receiving module, configured to receive a pause frame sent by the downstream QCN device when a packet in a sending port is congested, where the pause frame carries a congestion tag of a congestion packet and a priority of the congestion packet, and the congestion packet is a packet discarded by the downstream QCN device in a packet from the upstream QCN device;
and the speed reduction forwarding module is used for carrying out speed reduction forwarding on the message which is to be sent to the downstream QCN equipment and has the congestion label of the congestion message and the priority of the congestion message.
The application provides a flow monitoring device, is applied to downstream QCN equipment, and the device includes:
the message receiving module is used for receiving the message which is added with the congestion tag and sent by the upstream QCN equipment;
a congestion tag identification module, configured to identify a congestion tag of a congestion packet in a sending port and a priority of the congestion packet when a packet in the sending port is congested by the downstream QCN device, where the congestion packet is a packet discarded by the downstream QCN device in a packet from the upstream QCN device;
a pause frame sending module, configured to send a pause frame carrying the congestion tag of the congestion packet and the priority of the congestion packet to the upstream QCN device;
and a speed reduction message receiving module, configured to receive a speed reduction message forwarded by the upstream QCN device, where the speed reduction message is a message obtained by the upstream QCN device reducing speed of a message to be sent to the downstream QCN device, the message having a congestion tag of the congestion message and a priority of the congestion message.
According to the traffic monitoring method, the traffic monitoring device and the electronic equipment, the congestion tag is added to the currently received message which does not carry the congestion tag; sending the message added with the congestion label to downstream QCN equipment; receiving a pause frame sent by downstream QCN equipment when a message is congested in a sending port; and carrying out speed reduction forwarding on the message with the congestion label of the congestion message in the message to be sent to the downstream QCN equipment. When the message is congested in the sending port of the downstream QCN equipment, the rate of the message sent to the downstream QCN equipment by the upstream QCN equipment is reduced, so that the message is not congested any more in the sending port of the downstream QCN equipment, and meanwhile, the rate of the message in other sending ports of the downstream QCN equipment is not reduced. Of course, not all advantages described above need necessarily be achieved at the same time by any one product or method of the present application.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
FIG. 1 is a schematic view of the working principle of QCN;
fig. 2 is a schematic view of traffic forwarding of the QCN network;
fig. 3 is a flowchart of a traffic monitoring method according to an embodiment of the present application;
fig. 4 is another flowchart of a traffic monitoring method according to an embodiment of the present application;
fig. 5 is another flowchart of a traffic monitoring method according to an embodiment of the present application;
fig. 6 is another flowchart of a traffic monitoring method according to an embodiment of the present application;
fig. 7 is another flowchart of a traffic monitoring method according to an embodiment of the present application;
FIG. 8 is a block diagram of a flow monitoring device according to an embodiment of the present application;
fig. 9 is another structural diagram of a flow rate monitoring device according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
When monitoring the data flow in the network, if the message in the sending port of the QCN equipment is congested, the flow can be decelerated through the flow-control function, so that the message is prevented from being lost due to congestion. However, the flow-control function only slows down the packets with the priority of the congested packets, and when the QCN device sends the received packets to the plurality of RP terminals through the plurality of sending ports, the rate of the packets in the sending ports where the QCN device is not congested will also be reduced. In order to solve the problem, embodiments of the present application provide a flow monitoring method and apparatus, and an electronic device, so that when a packet in a sending port of a QCN device is congested, the packet in the sending port of the QCN device is no longer congested, and meanwhile, the rate of the packet in other sending ports of the QCN device is not reduced.
Referring to fig. 3, fig. 3 is a flowchart of a traffic monitoring method according to an embodiment of the present application, applied to an upstream QCN device, including the following steps:
s301, adding a congestion tag in a currently received message which does not carry the congestion tag, wherein the added congestion tag is different from the congestion tag of the received message carrying the congestion tag.
In the embodiment of the present application, a QCN device and a set of RP terminals using the QCN form a CDN, where an upstream QCN device and a downstream QCN device mentioned in the embodiment of the present application are both QCN devices and both have a function of forwarding a message, the upstream QCN device belongs to a transmitting end of data traffic with respect to the downstream QCN device, and the downstream QCN device belongs to a receiving end of the data traffic. In the CDN domain, in order to distinguish different messages when the RP end sends the messages, a congestion TAG is added in the Ethernet message, the congestion TAG can be represented by a CN-TAG field, and different congestion TAGs are used for identifying different congestion control flows. The CN-TAG field includes: the message Type Ether Type and RP ID, Ether Type can take the value as 0x22E9, the value of message Ether Type in CND domain is the same, RP ID is distributed by each RP end, RP ID is used for distinguishing the messages of different flows. The CNM message contains the congestion label, so that the RP end can analyze the congestion label after receiving the CNM message and determine which message in the data flow causes congestion, thereby reducing the speed of the congested data message flow. CN-TAG is added in the message by RP end, and the devices in CND domain can analyze the message carrying CN-TAG. When the message leaves the CND domain, the CN-TAG needs to be deleted.
As can be seen from the above, the packets in the CND domain usually carry the congestion label, while the packets outside the CND domain do not carry the congestion label. Then, in order to reduce the speed of the message outside the CND domain, in the embodiment of the present application, a congestion tag may be added to the message that does not carry the congestion tag. Meanwhile, in order to distinguish the message in the CND domain from the message outside the CND domain, the added congestion label can be different from the congestion label of the received message carrying the congestion label. The added congestion tag is different from the congestion tag of the received message carrying the congestion tag, and specifically comprises the following steps: the message type in the added congestion tag is different from the message type in the congestion tag of the received message carrying the congestion tag. For example, the value of the Ether Type of the message in the CND domain is 0x22E9, the value of the Ether Type of the message outside the CND domain may be 0x00EA, and the values of the Ether Type of the message outside the CND domain are the same. Thus, whether the message is a message in the CND domain or a message outside the CND domain can be distinguished through the value of the Ether Type.
In addition, when adding a congestion tag to a packet that does not carry a congestion tag, because the RP ID field is limited, the congestion tag may be added only to a traffic that exceeds the port bandwidth rate by more than a preset threshold, for example, the preset threshold may be 1% or 2%, and is not limited herein. Of course, the preset threshold may also be a flow monitoring value set by the user.
S302, sending the message with the congestion tag to the downstream QCN device.
Specifically, after the upstream QCN device adds the congestion tag to the message not carrying the congestion tag, the message added with the congestion tag is sent to the downstream QCN device.
S303, receiving a pause frame sent by the downstream QCN device when the packet in the sending port is congested, where the pause frame carries a congestion tag of the congestion packet and a priority of the congestion packet, and the congestion packet is a packet discarded by the downstream QCN device in a packet from the upstream QCN device.
Specifically, after the downstream QCN device receives, through the receiving port, the packet added with the congestion tag and sent by the upstream QCN device, the downstream QCN device forwards, through one or more sending ports, the received packet added with the congestion tag to the RP terminal or other downstream QCN devices. When the message in the sending port is congested by the downstream QCN equipment, the message from the upstream QCN equipment is discarded, and the congested message is the message discarded by the downstream QCN equipment in the message from the upstream QCN equipment. The congestion message carries a congestion tag and a priority, wherein the priority carried in the congestion message is carried by a message not carrying the congestion tag or a message carrying the congestion tag, and the congestion tag carried in the congestion message is added by the application. Therefore, the pause frame sent by the downstream QCN device to the upstream QCN device carries the congestion label and the priority of the congestion message, and after receiving the pause frame, the upstream QCN device can determine which messages are congested according to the congestion label and the priority of the congestion message.
S304, the messages with the congestion labels of the congestion messages and the priority of the congestion messages in the messages to be sent to the downstream QCN equipment are subjected to speed reduction forwarding.
In this embodiment of the present application, after determining which packets are congested, an upstream QCN device performs speed reduction forwarding on a packet to be sent to a downstream QCN device, where the speed reduction forwarded packet refers to a packet having a congestion label of a congested packet. Because the message forwarded at the reduced speed is the designated message, after the downstream QCN device receives the message forwarded at the reduced speed, the sending port with congestion will not be congested any more, and the rate of the message in the sending port without congestion will not be reduced.
Therefore, the traffic monitoring method provided by the embodiment of the application adds the congestion tag in the currently received message which does not carry the congestion tag; sending the message added with the congestion label to downstream QCN equipment; receiving a pause frame sent by downstream QCN equipment when a message is congested in a sending port; and carrying out speed reduction forwarding on the messages with the congestion labels of the congestion messages and the priority of the congestion messages in the messages to be sent to the downstream QCN equipment. According to the embodiment of the application, when the message is congested in the sending port of the downstream QCN equipment, the rate of the message which is sent by the upstream QCN equipment to the downstream QCN equipment and has the congestion label of the congested message and the priority of the congested message is reduced, so that the message is not congested any more in the sending port of the downstream QCN equipment. The rate of the messages which are sent by the upstream QCN equipment to the downstream QCN equipment and do not have the congestion labels of the congestion messages and the priorities of the congestion messages cannot be reduced, and the messages which do not have the congestion labels of the congestion messages and the priorities of the congestion messages are forwarded to other QCN equipment or RP (RP) ends through other sending ports of the downstream QCN equipment, so that the rate of the messages in other sending ports of the downstream QCN equipment cannot be reduced.
Corresponding to the embodiment in fig. 3, an embodiment of the present application further provides a traffic monitoring method applied to a downstream QCN device, referring to fig. 4, where fig. 4 is another flowchart of the traffic monitoring method in the embodiment of the present application, and includes the following steps:
s401, receiving the message added with the congestion label and sent by the upstream QCN equipment.
In the embodiment of the application, when the message currently received by the upstream QCN device does not carry the congestion tag, the congestion tag is added to the currently received message not carrying the congestion tag, and then the message added with the congestion tag is sent to the downstream QCN device, so that the downstream QCN device receives the message added with the congestion tag sent by the upstream QCN device.
S402, when a packet in a sending port of a downstream QCN device is congested, identifying a congestion tag of the congested packet in the sending port and a priority of the congested packet, where the congested packet is a packet discarded by a downstream QCN device in a packet from an upstream QCN device.
It should be noted that the added congestion tag is added by the upstream QCN device, and therefore the upstream QCN device may identify the added congestion tag. Then, in order to forward the message to which the congestion tag is added between different QCN devices and enable a downstream QCN device to feed back the congestion message to an upstream QCN device, in this embodiment of the present application, the QCN devices in the CND domain may all recognize the added congestion tag. Therefore, when the message is congested in the sending port, the downstream QCN device may identify a congestion tag of the congested message and a priority of the congested message.
S403, send a pause frame carrying the congestion label of the congestion message and the priority of the congestion message to the upstream QCN device.
Specifically, after the downstream QCN device identifies the congestion tag of the congestion message, the congestion tag of the congestion message and the priority of the congestion message are filled into the pause frame, and the pause frame is sent to the upstream QCN device, so that the upstream QCN device can determine which messages are congested according to the congestion tag of the congestion message and the priority of the congestion message.
S404, receiving a speed reduction message forwarded by the upstream QCN device, where the speed reduction message is a message obtained by the upstream QCN device reducing speed of a message to be sent to the downstream QCN device, the message having a congestion tag of the congestion message and a priority of the congestion message.
Specifically, after receiving the pause frame, the upstream QCN device performs speed reduction on a packet having a congestion tag of the congestion packet and a priority of the congestion packet in a packet to be sent to the downstream QCN device, and then sends the speed reduction packet to the downstream QCN device.
As can be seen, in the flow monitoring method provided in the embodiment of the present application, after receiving a packet, which is sent by an upstream QCN device and to which a congestion tag is added, a downstream QCN device identifies, when a packet in a sending port of the downstream QCN device is congested, the congestion tag of the congestion packet in the sending port and a priority of the congestion packet; sending a congestion label carrying the congestion message and a pause frame carrying the priority of the congestion message to upstream QCN equipment; and receiving the speed reduction message forwarded by the upstream QCN equipment. Therefore, the message congestion in the sending port of the downstream QCN equipment is avoided by reducing the rate of the message sent by the upstream QCN equipment to the downstream QCN equipment. Since the speed reduction packet refers to a packet obtained by an upstream QCN device after speed reduction is performed on a packet having a congestion tag of a congestion packet and a priority of the congestion packet in a packet to be sent to a downstream QCN device, the rate of the packet having no congestion tag of the congestion packet and no priority of the congestion packet in the upstream QCN device to be sent to the downstream QCN device is not reduced, and since the packet having no congestion tag of the congestion packet and no priority of the congestion packet is forwarded to other QCN devices or an RP terminal through other sending ports of the downstream QCN device, the rate of the packet in other sending ports of the downstream QCN device is not reduced in the embodiment of the present application.
Referring to fig. 5, fig. 5 is another flowchart of a flow monitoring method according to an embodiment of the present application, including the following steps:
s501, the upstream QCN device adds a congestion tag to a currently received packet that does not carry a congestion tag, where the added congestion tag is different from a congestion tag of a received packet that carries a congestion tag.
S502, the upstream QCN device sends the packet with the congestion tag added thereto to the downstream QCN device.
S503, receiving the message with the congestion tag sent by the upstream QCN device.
S504, when the downstream QCN device is congested in the packet at the sending port, the downstream QCN device identifies a congestion tag of the congestion packet and a priority of the congestion packet in the sending port, where the congestion packet is a packet discarded by the downstream QCN device in the packet from the upstream QCN device.
And S505, the downstream QCN equipment sends a pause frame carrying the congestion label of the congestion message and the priority of the congestion message to the upstream QCN equipment.
S506, the upstream QCN device receives the pause frame sent by the downstream QCN device.
And S507, the upstream QCN equipment performs speed reduction forwarding on the messages with the congestion labels of the congestion messages and the priority of the congestion messages in the messages to be sent to the downstream QCN equipment.
And S508, the downstream QCN equipment receives the speed reduction message forwarded by the upstream QCN equipment, wherein the speed reduction message is the message obtained after the upstream QCN equipment performs speed reduction on the message to be sent to the downstream QCN equipment, the message with the congestion label of the congestion message and the priority of the congestion message.
As can be seen from fig. 5, S501, S502, S506, and S507 in the embodiment of fig. 5 are respectively the same as S301, S302, S303, and S304 in the embodiment of fig. 3, and S503, S504, S505, and S508 in the embodiment of fig. 5 are respectively the same as S401, S402, S403, and S404 in the embodiment of fig. 4, so that all implementation manners of the embodiments of fig. 3 and 4 are applicable to fig. 5, and can achieve the same or similar beneficial effects, and are not described again.
Therefore, in the traffic monitoring method provided by the embodiment of the present application, the upstream QCN device adds the congestion tag to the currently received message that does not carry the congestion tag; sending the message added with the congestion label to downstream QCN equipment; the downstream QCN equipment identifies a congestion label of a congestion message in a sending port and the priority of the congestion message when the message in the sending port is congested, and sends a pause frame to the upstream QCN equipment; after receiving the pause frame, the upstream QCN equipment performs speed reduction forwarding on a message with a congestion label of a congestion message and a priority of the congestion message in a message to be sent to the downstream QCN equipment; and the downstream QCN equipment receives the speed reduction message forwarded by the upstream QCN equipment. According to the embodiment of the application, the speed of the messages which are sent by the upstream QCN equipment to the downstream QCN equipment and have the congestion labels of the congestion messages and the priority of the congestion messages is reduced, and the messages in the sending port of the downstream QCN equipment are not congested any more. The rate of the messages which are sent by the upstream QCN equipment to the downstream QCN equipment and do not have the congestion labels of the congestion messages and the priorities of the congestion messages cannot be reduced, and the messages which do not have the congestion labels of the congestion messages and the priorities of the congestion messages are forwarded to other QCN equipment or RP ends through other sending ports of the downstream QCN equipment, so that the rate of the messages in other sending ports of the downstream QCN equipment cannot be reduced in the embodiment of the application.
Referring to fig. 6, fig. 6 is another flowchart of a traffic monitoring method according to an embodiment of the present application, where an execution subject of each step in the embodiment of fig. 6 is an upstream QCN device, and the method includes the following steps:
s601, when the priority of the message not carrying the congestion tag is the same as the priority monitored by the upstream QCN equipment, modifying the priority of the message not carrying the congestion tag into an isolation priority to obtain the message with the modified priority, wherein the isolation priority is different from the priority monitored by the upstream QCN equipment.
In this embodiment of the present application, each port on the QCN device needs to select a protection mode to be set in the CND, and the protection mode may be statically configured, or may be negotiated through a Link Layer Discovery Protocol (LLDP). The protection mode includes: the edg protection mode is that the priority of the modified message is the isolation priority.
For a CND domain boundary port, that is, a port (for example, Eth1/2 of CP2 in fig. 2) connected to an external network, an edge protection mode needs to be configured, that is, if a priority carried by a packet (a packet without a congestion tag) entering from outside the CND domain is the same as a priority monitored by an upstream QCN device, the priority of the packet without the congestion tag needs to be modified to an isolation priority, so as to prevent the packet outside the CND domain from interfering with the packet monitored by the QCN device. Only one isolation priority can be assigned to different QCN device configurations, that is, if the priority of the CND out-of-domain message is the same as the priority monitored by the upstream QCN device, all of the priorities of the CND out-of-domain message can be set as the isolation priority. Generally, the priority levels monitored by the QCN devices in the CND domain may be the same, so that the priority level of the message with the modified priority level is prevented from being the same as the priority levels monitored by other QCN devices in the CND domain, and the message with the modified priority level can be prevented from interfering with the messages in other QCN devices.
For example, if the priority monitored by the upstream QCN device is 2 and 3, the isolation priority configured on the CND domain boundary port is 5, and the priority of the received CND out-of-domain message is 2 and 3, then both the priorities 2 and 3 of the CND out-of-domain message are modified to 5. If the priority of the received CND out-of-domain message is 4, the priority of the CND out-of-domain message does not need to be modified, namely the priority of the CND out-of-domain message is still 4.
S602, adding a congestion tag to the message with the modified priority.
Specifically, after modifying the priority of the CND out-of-domain packet, the CND out-of-domain packet will not interfere with the CND in-domain packet, and a congestion tag may be added to the packet with the modified priority.
S603, send the message added with the congestion tag to the downstream QCN device.
S604, receiving a pause frame sent by the downstream QCN device when the packet in the sending port is congested, where the pause frame carries a congestion tag of the congestion packet and a priority of the congestion packet, and the congestion packet is a packet discarded by the downstream QCN device in a packet from the upstream QCN device.
S605, the message with the congestion label of the congestion message and the priority of the congestion message in the message to be sent to the downstream QCN equipment is subjected to speed reduction forwarding.
Since S603, S604, and S605 are respectively the same as S302, S303, and S304 in the embodiment of fig. 3, the implementation manners of S302, S303, and S304 in fig. 3 are all applicable to fig. 6, and all can achieve the same or similar beneficial effects, and are not described herein again.
Therefore, the traffic monitoring method provided by the embodiment of the application modifies the priority of the message not carrying the congestion tag into the isolation priority different from the priority of the message carrying the congestion tag; adding a congestion label to the message with the modified priority; sending the message added with the congestion label to downstream QCN equipment; receiving a pause frame sent by downstream QCN equipment when a message is congested in a sending port; and carrying out speed reduction forwarding on the messages with the congestion labels of the congestion messages and the priority of the congestion messages in the messages to be sent to the downstream QCN equipment. According to the embodiment of the application, the priority of the message not carrying the congestion label is modified, so that the message not carrying the congestion label does not interfere with the message carrying the congestion label; and reducing the rate of the messages with the congestion labels of the congestion messages and the priority of the congestion messages sent by the upstream QCN equipment to the downstream QCN equipment, so that the messages in the sending port of the downstream QCN equipment are not congested any more. The rate of the messages which are sent by the upstream QCN equipment to the downstream QCN equipment and do not have the congestion labels of the congestion messages and the priorities of the congestion messages cannot be reduced, and the messages which do not have the congestion labels of the congestion messages and the priorities of the congestion messages are forwarded to other QCN equipment or RP ends through other sending ports of the downstream QCN equipment, so that the rate of the messages in other sending ports of the downstream QCN equipment cannot be reduced in the embodiment of the application.
In the embodiment S301 shown in fig. 3 and the embodiment S501 shown in fig. 5, a method for adding a congestion tag to a currently received packet that does not carry a congestion tag, and in the embodiment S602 shown in fig. 6, a method for adding a congestion tag to a packet after modifying a priority may refer to fig. 7, where fig. 7 is another flow chart of a traffic monitoring method according to the embodiment of the present application, and an execution main body of each step in the embodiment of fig. 7 is an upstream QCN device, and includes the following steps:
s701, judging whether the message added with the congestion tag has a message with the priority same as that of the message without the congestion tag.
In the embodiment of the application, 8 forwarding queues exist in each port on the QCN device, and messages with different priorities are forwarded in different queues. Because the messages with different priorities are independent, when the congestion label is added to the message which does not carry the congestion label, the congestion labels of the messages with different priorities are also independent. Then, after receiving the packet without the congestion tag, the upstream QCN device first needs to determine whether a packet with the same priority as the packet without the congestion tag exists in the packet to which the congestion tag is added.
S702, judging whether a message with the destination MAC address same as the destination MAC address of the message without the congestion label exists in the message with the congestion label added and the message with the priority same as the priority of the message without the congestion label.
Specifically, in this embodiment of the present application, since the packets in each queue in the port of the upstream QCN device may be sent to multiple RP terminals, that is, the packets with the same priority may be sent to multiple RP terminals, and since the destination MACs of the packets sent to the multiple RP terminals are different, the packets in each queue in the port of the upstream QCN device may be further distinguished by the destination MAC addresses of the packets. Therefore, after determining that there is a packet with the priority same as that of a packet without a congestion tag in the packet to which the congestion tag is added, it is determined whether there is a packet with the destination MAC address same as that of the packet without the congestion tag in the packet to which the congestion tag is added. If yes, executing S703; if not, go to S704
And S703, determining the congestion label of the message with the priority being the same as that of the message without the congestion label and the destination MAC address being the same as that of the message without the congestion label in the message with the congestion label, as the congestion label of the message without the congestion label.
Specifically, when there is a packet with a destination MAC address that is the same as the destination MAC address of the packet without the congestion tag in the packet with the congestion tag having the priority that is the same as the priority of the packet without the congestion tag, the congestion tag of the packet with the congestion tag having the priority that is the same as the priority of the packet without the congestion tag and the destination MAC address that is the same as the destination MAC address of the packet without the congestion tag in the packet with the congestion tag may be determined as the congestion tag of the packet without the congestion tag. Therefore, congestion labels added to messages with the same priority and the same destination MAC address are the same, and the number of the congestion labels occupied by the messages is reduced.
S704, determining the congestion label of the message not carrying the congestion label according to a first preset strategy. The congestion tag added to the message not carrying the congestion tag is different from the congestion tag of the message which has the same priority as the message not carrying the congestion tag but has a different destination MAC address from the destination MAC address of the message not carrying the congestion tag.
Specifically, when there is no packet with the destination MAC address identical to the destination MAC address of the packet without the congestion tag in the packet to which the congestion tag is added, the congestion tag of the packet without the congestion tag may be determined according to a first preset policy in order to distinguish the packets with the different destination MAC addresses. The first preset strategy specifically comprises: and setting the congestion label of the message without the congestion label as the congestion label which has the same priority as the message without the congestion label in the message added with the congestion label and has different congestion labels of the message with different destination MAC addresses from the destination MAC address of the message without the congestion label. The congestion tag added to the message not carrying the congestion tag is different from the congestion tag of the message, which has the priority same as that of the message not carrying the congestion tag but has a destination MAC address different from that of the message not carrying the congestion tag, in the message to which the congestion tag is added, specifically: the type of the message in the congestion tag added to the message without the congestion tag is the same as the type of the message in the congestion tag added to the message without the congestion tag, but the priority of the message with the congestion tag is the same as the priority of the message without the congestion tag, but the destination MAC address of the message is different from the destination MAC address of the message without the congestion tag, and the ID of the message in the congestion tag added to the message without the congestion tag is different from the ID of the message in the congestion tag of the message with the congestion tag, but the priority of the message with the congestion tag is the same as the priority of the message without the congestion tag, but the destination MAC address of the message is different from the destination MAC address of the message without the congestion tag.
For example, as shown in the embodiment of fig. 3, the congestion TAG may be represented by a CN-TAG field, which includes: the message types Ether Type and RP ID, and the Ether Type values of the added congestion labels are the same, so that the added congestion labels are different by setting the RP ID to different values. If the destination MAC addresses of the messages added with the congestion labels are respectively as follows: the MAC address A, MAC, address B, MAC, address C, and the congestion labels of the messages of the different destination MAC addresses are: 0x00EA |1, 0x00EA |2, 0x00EA |3, then when the destination MAC address of the message not carrying a congestion tag is MAC D, the congestion tag of the message not carrying a congestion tag may be set to 0x00EA | 4.
S705, determining the congestion label of the message not carrying the congestion label according to a second preset strategy.
In the embodiment of the application, if there is no message with the priority same as that of the message without the congestion tag in the message with the congestion tag, which indicates that the message without the congestion tag and the message with the congestion tag are in different queues, the congestion tag of the message without the congestion tag is determined according to a second preset strategy. The second preset strategy specifically comprises: setting the message type in the congestion tag added to the message not carrying the congestion tag as the same message type as the message type in the congestion tag of the message added with the congestion tag, and setting the message ID in the congestion tag added to the message not carrying the congestion tag as an arbitrary value. For example, the congestion label added to the message that does not carry the congestion label is 0x00EA | n, where n is any positive integer.
In the traffic monitoring method of the embodiment of the application, if there is a packet with a destination MAC address identical to a destination MAC address of a packet without a congestion tag in a packet with a congestion tag added and having a priority identical to a priority of a packet without a congestion tag, a congestion tag of a packet with a priority identical to a priority of a packet without a congestion tag and having a destination MAC address identical to a destination MAC address of a packet without a congestion tag in a packet with a congestion tag added is determined as a congestion tag of a packet without a congestion tag; if there is no message with the same destination MAC address as the destination MAC address of the message without the congestion tag in the message with the congestion tag added and the message with the same priority as the message without the congestion tag, determining the congestion tag of the message without the congestion tag according to a first preset strategy; and if the message added with the congestion label does not have the message with the priority same as that of the message not carrying the congestion label, determining the congestion label of the message not carrying the congestion label according to a second preset strategy. Therefore, the messages needing to be decelerated can be judged according to the priority of the messages and the added congestion label, and flow monitoring is achieved.
Corresponding to the above method embodiment, an embodiment of the present application further provides a flow monitoring device, referring to fig. 8, where fig. 8 is a structural diagram of the flow monitoring device according to the embodiment of the present application, applied to an upstream QCN device, and includes:
a congestion tag adding module 801, configured to add a congestion tag to a currently received message that does not carry a congestion tag, where the added congestion tag is different from a congestion tag of a received message that carries a congestion tag.
A message sending module 802, configured to send the message with the congestion tag added thereto to a downstream QCN device.
A pause frame receiving module 803, configured to receive a pause frame sent by a downstream QCN device when a packet in a sending port is congested, where the pause frame carries a congestion tag of a congestion packet and a priority of the congestion packet, and the congestion packet is a packet discarded by the downstream QCN device in a packet from an upstream QCN device.
A speed reduction forwarding module 804, configured to perform speed reduction forwarding on a packet with a congestion tag of a congestion packet and a priority of the congestion packet in a packet to be sent to a downstream QCN device.
Therefore, the traffic monitoring device provided in the embodiment of the present application adds a congestion tag to a currently received message that does not carry a congestion tag; sending the message added with the congestion label to downstream QCN equipment; receiving a pause frame sent by downstream QCN equipment when a message is congested in a sending port; and carrying out speed reduction forwarding on the messages with the congestion labels of the congestion messages and the priority of the congestion messages in the messages to be sent to the downstream QCN equipment. According to the embodiment of the application, when the message is congested in the sending port of the downstream QCN equipment, the rate of the message which is sent by the upstream QCN equipment to the downstream QCN equipment and has the congestion label of the congested message and the priority of the congested message is reduced, so that the message is not congested any more in the sending port of the downstream QCN equipment. The rate of the messages which are sent by the upstream QCN equipment to the downstream QCN equipment and do not have the congestion labels of the congestion messages and the priorities of the congestion messages cannot be reduced, and the messages which do not have the congestion labels of the congestion messages and the priorities of the congestion messages are forwarded to other QCN equipment or RP (RP) ends through other sending ports of the downstream QCN equipment, so that the rate of the messages in other sending ports of the downstream QCN equipment cannot be reduced.
It should be noted that, the apparatus in the embodiment of the present application is an apparatus applying the flow monitoring method, and all embodiments of the flow monitoring method are applicable to the apparatus and can achieve the same or similar beneficial effects.
In an implementation manner of the present application, the flow monitoring apparatus according to the embodiment of the present application further includes:
the priority modification module is used for modifying the priority of the message not carrying the congestion tag into an isolation priority when the priority of the message not carrying the congestion tag is the same as the priority monitored by the upstream QCN equipment to obtain a message with the modified priority, wherein the isolation priority is different from the priority monitored by the upstream QCN equipment;
the congestion tag adding module 801 is specifically configured to add a congestion tag to the message with the modified priority.
In an implementation manner of the present application, the congestion tag adding module 801 is configured to, if there is a packet with a priority that is the same as a priority of a packet without a congestion tag in a packet to which a congestion tag is added, determine whether there is a packet with a destination MAC address that is the same as a destination MAC address of a packet without a congestion tag in a packet to which a congestion tag is added and a packet with a priority that is the same as a priority of a packet without a congestion tag in a packet to which a congestion tag is added;
if a message with the destination MAC address identical to the destination MAC address of the message without the congestion tag exists in the message with the congestion tag added and the message with the priority identical to the priority of the message without the congestion tag, determining the congestion tag of the message with the congestion tag added and the message with the priority identical to the priority of the message without the congestion tag and the destination MAC address identical to the destination MAC address of the message without the congestion tag as the congestion tag of the message without the congestion tag;
if the message with the priority level the same as that of the message without the congestion tag in the message with the congestion tag added thereto does not have the message with the destination MAC address the same as that of the message without the congestion tag, determining the congestion tag of the message without the congestion tag according to a first preset strategy, wherein the congestion tag added to the message without the congestion tag is different from the congestion tag of the message with the priority level the same as that of the message without the congestion tag in the message with the congestion tag added thereto but different from that of the message with the destination MAC address different from that of the message without the congestion tag.
The congestion tag adding module 801 is further configured to determine, according to a second preset strategy, a congestion tag of a packet that does not carry a congestion tag if there is no packet to which a congestion tag is added, where the priority of the packet is the same as the priority of a packet that does not carry a congestion tag.
In an implementation manner of the present application, congestion tags added to a packet without a congestion tag are different from congestion tags of packets, in which a priority of the packet with the congestion tag added is the same as a priority of the packet without the congestion tag, but a destination MAC address of the packet with the congestion tag is different from a destination MAC address of the packet without the congestion tag, specifically: the type of the message in the congestion tag added to the message without the congestion tag is the same as the type of the message in the congestion tag added to the message without the congestion tag, but the priority of the message with the congestion tag is the same as the priority of the message without the congestion tag, but the destination MAC address is different from the destination MAC address of the message without the congestion tag, and the ID of the message in the congestion tag added to the message without the congestion tag is different from the ID of the message in the congestion tag of the message with the congestion tag, but the priority of the message with the congestion tag is the same as the priority of the message without the congestion tag, but the destination MAC address is different from the destination MAC address of the message without the congestion tag.
In an implementation manner of the present application, the added congestion tag is different from a congestion tag of a received packet with the congestion tag, and specifically includes: the message type in the added congestion label is different from the message type in the congestion label of the received message carrying the congestion label.
An embodiment of the present application further provides a flow monitoring device, which is applied to a downstream QCN device, and referring to fig. 9, fig. 9 is another structural diagram of the flow monitoring device according to the embodiment of the present application, and includes:
a message receiving module 901, configured to receive a message, which is sent by an upstream QCN device and to which a congestion tag is added.
A congestion tag identification module 902, configured to identify a congestion tag of a congestion packet in a sending port and a priority of the congestion packet when a packet in the sending port is congested by a downstream QCN device, where the congestion packet is a packet discarded by a downstream QCN device in a packet from an upstream QCN device.
A pause frame sending module 903, configured to send a pause frame carrying the congestion label of the congestion message and the priority of the congestion message to the upstream QCN device.
A speed reduction message receiving module 904, configured to receive a speed reduction message forwarded by an upstream QCN device, where the speed reduction message is a message obtained by the upstream QCN device reducing the speed of a message to be sent to a downstream QCN device, the message having a congestion tag of a congestion message and a priority of the congestion message.
As can be seen, in the traffic monitoring apparatus provided in this embodiment of the present application, after receiving a message, which is sent by an upstream QCN device and to which a congestion tag is added, when a packet in a sending port of the downstream QCN device is congested, a congestion tag of the congestion packet in the sending port and a priority of the congestion packet are identified; sending a congestion label carrying the congestion message and a pause frame carrying the priority of the congestion message to upstream QCN equipment; and receiving the speed reduction message forwarded by the upstream QCN equipment. Therefore, the message congestion in the sending port of the downstream QCN equipment is avoided by reducing the rate of the message sent by the upstream QCN equipment to the downstream QCN equipment. Since the speed reduction message refers to a message obtained by an upstream QCN device after speed reduction is performed on a message having a congestion tag of a congestion message and a priority of the congestion message in a message to be sent to a downstream QCN device, the rate of the message having no congestion tag of the congestion message and no priority of the congestion message in the upstream QCN device to be sent to the downstream QCN device is not reduced, and the message having no congestion tag of the congestion message is forwarded to other QCN devices or an RP terminal through other sending ports of the downstream QCN device.
An embodiment of the present application further provides an upstream QCN device, including: a processor and a machine-readable storage medium storing machine-executable instructions executable by the processor, the processor being caused by the machine-executable instructions to: and implementing any steps of the flow monitoring method applied to the upstream QCN equipment.
An embodiment of the present application further provides a downstream QCN device, including: a processor and a machine-readable storage medium storing machine-executable instructions executable by the processor, the processor caused by the machine-executable instructions to: and implementing any steps of the flow monitoring method applied to the downstream QCN equipment.
It should be noted that the machine-readable storage medium and the computer-readable storage medium may include a RAM (Random Access Memory) and may also include a non-volatile Memory (non-volatile Memory), such as at least one disk Memory. The machine-readable storage medium may also be at least one memory device located remotely from the aforementioned processor. The processor may be a general purpose processor comprising: CPU, NP (Network Processor), and the like; but also a DSP (Digital Signal Processing), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array) or other Programmable logic device, discrete Gate or transistor logic device, discrete hardware component.
It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
All the embodiments in the present specification are described in a related manner, and the same and similar parts among the embodiments may be referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, as for the embodiments of the flow monitoring device and the electronic device, since they are substantially similar to the embodiments of the method, the description is simple, and the relevant points can be referred to the partial description of the embodiments of the method.
The above description is only for the preferred embodiment of the present application, and is not intended to limit the scope of the present application. Any modification, equivalent replacement, improvement and the like made within the spirit and principle of the present application are included in the protection scope of the present application.

Claims (16)

1. A traffic monitoring method applied to an upstream QCN device, the method comprising:
adding a congestion tag in a currently received message which does not carry the congestion tag, wherein the message which does not carry the congestion tag comes from outside a CND domain, and the added congestion tag is different from the congestion tag of the received message which carries the congestion tag;
sending the message added with the congestion label to downstream QCN equipment;
receiving a pause frame sent by the downstream QCN equipment when a message in a sending port is congested, wherein the pause frame carries a congestion label of a congestion message and the priority of the congestion message, and the congestion message is a message discarded by the downstream QCN equipment in a message from the upstream QCN equipment;
carrying out speed reduction forwarding on a message which is to be sent to the downstream QCN equipment and has a congestion label of the congestion message and the priority of the congestion message;
before adding a congestion tag in the currently received message not carrying the congestion tag, the method further includes:
and when the priority of the message not carrying the congestion label is the same as the priority monitored by the upstream QCN equipment, modifying the priority of the message not carrying the congestion label into an isolation priority to obtain the message with the modified priority, wherein the isolation priority is different from the priority monitored by the upstream QCN equipment.
2. The traffic monitoring method according to claim 1, wherein the adding a congestion tag to a currently received packet that does not carry a congestion tag comprises:
and adding a congestion label to the message with the modified priority.
3. The traffic monitoring method according to claim 1 or 2, wherein the adding a congestion tag to a currently received packet that does not carry a congestion tag comprises:
if the message with the congestion label added has the message with the priority same as that of the message without the congestion label, judging whether a message with the destination MAC address same as that of the message without the congestion label exists in the message with the congestion label added and the message with the priority same as that of the message without the congestion label;
if so, determining the congestion label of the message with the priority being the same as that of the message without the congestion label and the destination MAC address being the same as that of the message without the congestion label in the message with the congestion label as the congestion label of the message without the congestion label;
if not, determining the congestion label of the message not carrying the congestion label according to a first preset strategy, wherein the congestion label added to the message not carrying the congestion label is different from the congestion label of the message with the same priority as the message not carrying the congestion label in the message with the congestion label added, and the congestion label of the message with the different destination MAC address from the destination MAC address of the message not carrying the congestion label.
4. The traffic monitoring method according to claim 1 or 2, wherein the adding a congestion tag to a currently received packet that does not carry a congestion tag comprises:
and if the message with the congestion label added does not have the message with the priority same as that of the message without the congestion label, determining the congestion label of the message without the congestion label according to a second preset strategy.
5. The traffic monitoring method according to claim 3, wherein the congestion tag added to the message without the congestion tag is different from the congestion tag of the message with the congestion tag added thereto, the message with the congestion tag added thereto having the same priority as the message without the congestion tag in priority, and the congestion tag of the message with the destination MAC address different from the destination MAC address of the message without the congestion tag, specifically: the message type in the congestion label added in the message without the congestion label is the same as the message type in the message with the congestion label, the priority of the message with the congestion label is the same as the priority of the message without the congestion label, the message type in the congestion label of the message with the destination MAC address different from the destination MAC address of the message without the congestion label is the same as the message type in the congestion label added in the message without the congestion label, the message ID of the message with the congestion label is different from the message ID of the message with the priority of the message with the congestion label, and the message ID of the message with the destination MAC address different from the destination MAC address of the message without the congestion label.
6. The traffic monitoring method according to claim 1, wherein the congestion tag added is different from a congestion tag of a received packet with the congestion tag, and specifically includes: the message type in the added congestion label is different from the message type in the congestion label of the received message carrying the congestion label.
7. A traffic monitoring method applied to a downstream QCN device, the method comprising:
receiving a message which is sent by an upstream QCN device and added with a congestion label, wherein the message added with the congestion label is the message which is sent by the upstream QCN device and not carried with the congestion label, modifying the priority of the message not carried with the congestion label into an isolation priority when the priority of the message not carried with the congestion label is the same as the priority monitored by the upstream QCN device, and adding the congestion label to the message with the modified priority, wherein the message not carried with the congestion label comes from the outside of a CND (content-centric domain), the added congestion label is different from the congestion label of the received message carried with the congestion label, and the isolation priority is different from the priority monitored by the upstream QCN device;
when the message in the sending port is congested by the downstream QCN equipment, identifying a congestion label of the congestion message in the sending port and the priority of the congestion message, wherein the congestion message is a message discarded by the downstream QCN equipment in the message from the upstream QCN equipment;
sending a congestion tag carrying the congestion message and a pause frame carrying the priority of the congestion message to the upstream QCN equipment;
and receiving a speed reduction message forwarded by the upstream QCN equipment, wherein the speed reduction message is the message obtained after the upstream QCN equipment reduces the speed of a message to be sent to the downstream QCN equipment, a congestion tag of the congestion message and a message with the priority of the congestion message.
8. A traffic monitoring apparatus, for use in upstream QCN devices, the apparatus comprising:
a congestion tag adding module, configured to add a congestion tag to a currently received message that does not carry a congestion tag, where the message that does not carry a congestion tag comes from outside a CND domain, and the added congestion tag is different from a congestion tag of a received message that carries a congestion tag;
the message sending module is used for sending the message added with the congestion label to downstream QCN equipment;
a pause frame receiving module, configured to receive a pause frame sent by the downstream QCN device when a packet in a sending port is congested, where the pause frame carries a congestion tag of a congestion packet and a priority of the congestion packet, and the congestion packet is a packet discarded by the downstream QCN device in a packet from the upstream QCN device;
the speed reduction forwarding module is used for carrying out speed reduction forwarding on a message which is to be sent to the downstream QCN equipment and has a congestion label of the congestion message and the priority of the congestion message;
the device further comprises:
and the priority modifying module is used for modifying the priority of the message not carrying the congestion tag into an isolation priority when the priority of the message not carrying the congestion tag is the same as the priority monitored by the upstream QCN equipment to obtain the message with the modified priority, wherein the isolation priority is different from the priority monitored by the upstream QCN equipment.
9. The traffic monitoring device according to claim 8, wherein the congestion tag adding module is specifically configured to add a congestion tag to the message with the modified priority.
10. The traffic monitoring device according to claim 8 or 9, wherein the congestion tag adding module is configured to, if there is a packet with a priority that is the same as the priority of the packet without the congestion tag in the packet to which the congestion tag is added, determine whether there is a packet with a destination MAC address that is the same as the destination MAC address of the packet without the congestion tag in the packet to which the congestion tag is added;
if a message with the destination MAC address identical to the destination MAC address of the message without the congestion label exists in the message with the priority identical to the priority of the message without the congestion label in the message with the congestion label, determining the congestion label of the message with the priority identical to the priority of the message without the congestion label and the destination MAC address identical to the destination MAC address of the message without the congestion label in the message with the congestion label as the congestion label of the message without the congestion label;
if there is no message with the destination MAC address same as the destination MAC address of the message without the congestion tag in the message with the congestion tag added with the priority same as the priority of the message without the congestion tag, determining the congestion tag of the message without the congestion tag according to a first preset strategy, wherein the congestion tag added in the message without the congestion tag is different from the congestion tag of the message with the congestion tag added with the priority same as the priority of the message without the congestion tag in the message with the congestion tag added with the priority same as the priority of the message without the congestion tag, and the congestion tag of the message with the destination MAC address different from the destination MAC address of the message without the congestion tag.
11. The traffic monitoring device according to claim 8 or 9, wherein the congestion tag adding module is further configured to determine, according to a second preset policy, the congestion tag of the packet without the congestion tag if there is no packet with the same priority as that of the packet without the congestion tag in the packet to which the congestion tag is added.
12. The traffic monitoring device according to claim 10, wherein the congestion tag added to the message not carrying the congestion tag is different from the congestion tag of the message having the same priority as the message not carrying the congestion tag in the message to which the congestion tag is added, and the congestion tag of the message having a different destination MAC address from the destination MAC address of the message not carrying the congestion tag, specifically: the message type in the congestion label added in the message without the congestion label is the same as the message type in the message with the congestion label, the priority of the message with the congestion label is the same as the priority of the message without the congestion label, the message type in the congestion label of the message with the destination MAC address different from the destination MAC address of the message without the congestion label is the same as the message type in the congestion label added in the message without the congestion label, the message ID of the message with the congestion label is different from the message ID of the message with the priority of the message with the congestion label, and the message ID of the message with the destination MAC address different from the destination MAC address of the message without the congestion label.
13. The traffic monitoring device according to claim 8, wherein the added congestion tag is different from a congestion tag of a received packet with the congestion tag, and specifically includes: the message type in the added congestion label is different from the message type in the congestion label of the received message carrying the congestion label.
14. A traffic monitoring apparatus for use with downstream QCN devices, the apparatus comprising:
a message receiving module, configured to receive a message with a congestion tag, which is sent by an upstream QCN device, where the message with the congestion tag is a message that is sent by the upstream QCN device and that does not carry a congestion tag, and modify the priority of the message with no congestion tag into an isolation priority when the priority of the message with no congestion tag is the same as the priority monitored by the upstream QCN device, and add a congestion tag to the message with the modified priority, where the message with no congestion tag is from outside a CND domain, the congestion tag added is different from the congestion tag of the received message with the congestion tag, and the isolation priority is different from the priority monitored by the upstream QCN device;
a congestion tag identification module, configured to identify a congestion tag of a congestion packet in a sending port and a priority of the congestion packet when the downstream QCN device is congested in a packet in the sending port, where the congestion packet is a packet discarded by the downstream QCN device in a packet from the upstream QCN device;
a pause frame sending module, configured to send a pause frame carrying a congestion tag of the congestion packet and a priority of the congestion packet to the upstream QCN device;
and the speed reduction message receiving module is used for receiving a speed reduction message forwarded by the upstream QCN equipment, wherein the speed reduction message is the message obtained by reducing the speed of a message to be sent to the downstream QCN equipment, a congestion tag of the congestion message and a message with the priority of the congestion message by the upstream QCN equipment.
15. An upstream QCN device, comprising: a processor and a machine-readable storage medium storing machine-executable instructions executable by the processor, the processor being caused by the machine-executable instructions to: carrying out the method steps of any one of claims 1 to 6.
16. A downstream QCN device, comprising: a processor and a machine-readable storage medium storing machine-executable instructions executable by the processor, the processor being caused by the machine-executable instructions to: implementing the method steps of claim 7.
CN201810002681.3A 2018-01-02 2018-01-02 Flow monitoring method and device and electronic equipment Active CN108243117B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201810002681.3A CN108243117B (en) 2018-01-02 2018-01-02 Flow monitoring method and device and electronic equipment

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201810002681.3A CN108243117B (en) 2018-01-02 2018-01-02 Flow monitoring method and device and electronic equipment

Publications (2)

Publication Number Publication Date
CN108243117A CN108243117A (en) 2018-07-03
CN108243117B true CN108243117B (en) 2022-05-24

Family

ID=62698523

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201810002681.3A Active CN108243117B (en) 2018-01-02 2018-01-02 Flow monitoring method and device and electronic equipment

Country Status (1)

Country Link
CN (1) CN108243117B (en)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109347761B (en) * 2018-11-29 2022-08-26 新华三技术有限公司 Flow forwarding control method and device
CN113872885B (en) * 2021-09-30 2024-02-09 新华三信息安全技术有限公司 Method and equipment for controlling message forwarding

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102025617A (en) * 2010-11-26 2011-04-20 中兴通讯股份有限公司 Method and device for controlling congestion of Ethernet
CN102440030A (en) * 2010-04-20 2012-05-02 华为技术有限公司 Service implementation method, device and system
CN104105131A (en) * 2013-04-07 2014-10-15 华为终端有限公司 Congestion control method and device
CN104185213A (en) * 2013-05-20 2014-12-03 华为终端有限公司 Data stream transmission control method and device thereof
CN104836744A (en) * 2015-05-29 2015-08-12 杭州华三通信技术有限公司 Message processing method and device

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9954781B2 (en) * 2013-03-15 2018-04-24 International Business Machines Corporation Adaptive setting of the quantized congestion notification equilibrium setpoint in converged enhanced Ethernet networks

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102440030A (en) * 2010-04-20 2012-05-02 华为技术有限公司 Service implementation method, device and system
CN102025617A (en) * 2010-11-26 2011-04-20 中兴通讯股份有限公司 Method and device for controlling congestion of Ethernet
CN104105131A (en) * 2013-04-07 2014-10-15 华为终端有限公司 Congestion control method and device
CN104185213A (en) * 2013-05-20 2014-12-03 华为终端有限公司 Data stream transmission control method and device thereof
CN104836744A (en) * 2015-05-29 2015-08-12 杭州华三通信技术有限公司 Message processing method and device

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
无损以太网关键技术研究;罗鉴等;《中兴通讯技术》;20120831;第18卷(第4期);第27-31页 *

Also Published As

Publication number Publication date
CN108243117A (en) 2018-07-03

Similar Documents

Publication Publication Date Title
CN109412964B (en) Message control method and network device
CN107204931B (en) Communication device and method for communication
CN108243116B (en) Flow control method and switching equipment
US9762491B2 (en) Dynamic thresholds for congestion control
US10135735B2 (en) Method and system for managing flows in a network
WO2018210117A1 (en) Congestion control method, network device, and network interface controller thereof
US20190014053A1 (en) Network Flow Control Method And Network Device
CN108989235B (en) Message forwarding control method and device
EP2068511A1 (en) Controlling congestion in a packet switched data network
CN110061923B (en) Flow control method, flow control device, switch, sending end server and medium
WO2021244240A1 (en) Network congestion control method and apparatus, device, system, and storage medium
US20070183332A1 (en) System and method for backward congestion notification in network
JP5867188B2 (en) Information processing apparatus, congestion control method, and congestion control program
CN110943933A (en) Method, device and system for realizing data transmission
US9614777B2 (en) Flow control in a network
WO2021008562A1 (en) Flow rate control method and apparatus
WO2021148020A1 (en) Service class adjustment method, apparatus, device and storage medium
WO2021083160A1 (en) Data transmission method and apparatus
WO2019128649A1 (en) Data stream sending method, device and system
CN114157609B (en) PFC deadlock detection method and device
CN108243117B (en) Flow monitoring method and device and electronic equipment
CN111224888A (en) Method for sending message and message forwarding equipment
US11025551B2 (en) Weighted fair queueing using severity-based window in reliable packet delivery network
US7471630B2 (en) Systems and methods for performing selective flow control
US8724458B2 (en) Methods and devices for controlling data unit handling

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