Method and system for displaying congestion notification markers

Abstract

The application provides a display congestion notification marking method and a stacking system. For each device in the stacking system, after receiving a data packet, the device detects a current congestion state of the device, and when the detected current congestion state indicates that the device is congested, maps the current congestion state into a corresponding self-congestion state parameter. Thus, the self-congestion state parameter can be encapsulated into a stacking header at the front end of the data packet, or the original congestion state parameter in the stacking header at the front end of the data packet is rewritten based on the self-congestion state parameter, and then the data packet is transmitted to a next device. The congestion state parameter in the stacking header can be mapped with each other with the ECN information. The scheme can realize that any device in the stacking system is congested, and the data packet can be marked with the ECN, so as to achieve the purpose of displaying the congestion notification.

Description

Technical Field

[0001] This application relates to the field of communication technology, and more specifically, to a method for displaying congestion notification tags and a stacking system. Background Technology

[0002] With the increasing development of network technology and bandwidth, large networks generally employ switch stacking to meet the high demands on the ports and bandwidth of the entire switch system. Stacking involves connecting multiple switches together via stacking ports, allowing administrators to manage them as a single switch. However, traditional stacked switches, when processing Explicit Congestion Notification (ECN), essentially treat each switch in the stack as an isolated device. That is, each device can determine whether congestion has occurred within its own system, but only the ingress or egress device can modify the packets. Therefore, congestion information detected by some devices ultimately cannot be reflected in the ECN field of the packets.

[0003] Under the current mechanism, each device in the stacking system determines its own congestion status and obtains congestion information. If the device has message editing capabilities, it rewrites the ECN field in the message; otherwise, it discards the congestion information and does not rewrite the ECN field. This existing method is a best-effort congestion detection and marking approach. It cannot truly treat the entire stacking system as a whole. When congestion occurs in the transmission devices of the stacking system, the ECN field in the message cannot be marked in a timely manner, leading to increased congestion and packet loss on the transmission devices. Summary of the Invention

[0004] The purpose of this application includes, for example, providing a method and stacking system for displaying congestion notification tags, which enables any device in the stacking system to be marked with an ECN when congestion occurs, so as to achieve the purpose of displaying congestion notices.

[0005] The embodiments of this application can be implemented as follows:

[0006] In a first aspect, this application provides a method for displaying congestion notification flags, applied to a stacked system including multiple devices, the method comprising:

[0007] When each device receives a data packet, it detects its current congestion status.

[0008] When each device detects that the current congestion state indicates that it is congested, it maps the current congestion state to its corresponding congestion state parameter.

[0009] Each device encapsulates its own congestion status parameters into the stack header of the data packet front end, or rewrites the original congestion status parameters in the stack header of the data packet front end based on its own congestion status parameters, and transmits the data packet to the next device. The congestion status parameters in the stack header can be mapped to the Explicit Congestion Notification (ECN) information.

[0010] In an optional implementation, the plurality of devices includes an inlet device, which serves as the flow inlet for the entire stacked system, and the method further includes:

[0011] For the entry device among the plurality of devices, after receiving a data packet, the entry device parses the ECN information carried in the data packet;

[0012] The entry device maps the parsed ECN information into corresponding congestion status parameters, and then performs the step of detecting the current congestion status of the device.

[0013] In an optional implementation, the plurality of devices further includes an outlet device, which serves as the flow outlet for the entire stacked system, and the method further includes:

[0014] For the egress device among the plurality of devices, after the egress device rewrites the original congestion status parameters in the stack header of the data packet based on its own congestion status parameters, it maps the current congestion status parameters in the stack header back to the ECN information.

[0015] The export device rewrites the ECN information in the data packet based on the mapped ECN information, and then performs the step of transmitting the data packet to the next device, wherein the next device is an external data receiving device.

[0016] In an optional implementation, the plurality of devices further includes a transmission device connected to both the preceding inlet device and the following outlet device, and the method further includes:

[0017] For the transmission device or egress device among the multiple devices, after receiving a data packet, the original congestion status parameters in the stack header of the data packet are parsed out, and then the step of detecting the current congestion status of the device is performed.

[0018] In an optional implementation, each of the devices includes multiple modules, which include a network port congestion state mapping module, a stacking port congestion state mapping module, a congestion determination module, a congestion state encapsulation module, a congestion state rewriting module, and a congestion state reverse mapping module. Each device dynamically selects and starts some of the multiple modules to work according to its role in the stacking system.

[0019] The network port congestion status mapping module is used to map ECN information into corresponding congestion status parameters; the stacking port congestion status mapping module is used to parse the original congestion status parameters in the stacking header; the congestion determination module is used to detect the current congestion status of the device; the congestion status encapsulation module is used to encapsulate its own congestion status parameters into the stacking header; the congestion status rewriting module is used to rewrite the original congestion status parameters in the stacking header of the data packet based on its own congestion status parameters; and the congestion status reverse mapping module is used to map the congestion status parameters in the current stacking header back to ECN information.

[0020] In an optional implementation, the method further includes:

[0021] When the transmission device detects that the current congestion status indicates that the device itself is not congested, it directly transmits the data packet to the next device.

[0022] In an optional implementation, the congestion state parameters include a first state parameter indicating that the data packet does not support congestion detection and ECN marking, a second state parameter indicating that the data packet supports congestion detection and is currently experiencing congestion, and a third state parameter indicating that the data packet supports congestion detection and is currently not experiencing congestion.

[0023] In an optional implementation, the step of detecting the current congestion state of the device includes:

[0024] Obtain the queue length of the data queue at the output port of this device, and determine whether the queue length exceeds a preset length. If it exceeds the preset length, determine that the device is currently experiencing congestion.

[0025] In an optional implementation, the method further includes:

[0026] After receiving a data packet, each device detects the queue length of the data queue at its input port and determines whether the queue length plus the size of the received data packet exceeds a preset maximum length.

[0027] If the received data packet exceeds the preset maximum length, the packet will be dropped; if the received data packet does not exceed the preset maximum length, the packet will be added to the data queue at the input port.

[0028] Secondly, this application provides a stacking system, which includes multiple devices;

[0029] Each of the aforementioned devices is configured to detect its current congestion status upon receiving a data packet;

[0030] Each of the aforementioned devices is further configured to map the current congestion state to a corresponding self-congestion state parameter when it is detected that the current congestion state indicates that the device is congested.

[0031] Each of the aforementioned devices is further configured to encapsulate its own congestion status parameters into the stack header of the data packet front end, or to rewrite the original congestion status parameters in the stack header of the data packet front end based on its own congestion status parameters, and transmit the data packet to the next device, wherein the congestion status parameters in the stack header can be mapped to each other with the Explicit Congestion Notification (ECN) information.

[0032] The beneficial effects of the embodiments of this application include, for example:

[0033] This application provides a method and stacking system for displaying congestion notification marking. For each device in the stacking system, upon receiving a data packet, each device detects its current congestion state. If the detected congestion state indicates that the device is experiencing congestion, it maps the current congestion state to its corresponding self-congestion state parameters. This allows the self-congestion state parameters to be encapsulated in the stacking header at the front end of the data packet, or the existing congestion state parameters in the stacking header at the front end of the data packet to be rewritten based on the self-congestion state parameters before the data packet is transmitted to the next device. The congestion state parameters in the stacking header can be mapped to and from the displayed congestion notification (ECN) information. This solution enables any device in the stacking system to mark data packets with ECN when congestion occurs, achieving the purpose of displaying congestion notification. Attached Figure Description

[0034] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of this application and should not be regarded as a limitation of the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0035] Figure 1 This is a schematic diagram of the architecture of the stacking system provided in the embodiments of this application;

[0036] Figure 2 This is one of the schematic diagrams of the message forwarding path of the stacking system provided in the embodiments of this application;

[0037] Figure 3 This is a second illustration of the message forwarding path of the stacking system provided in the embodiments of this application;

[0038] Figure 4 One of the flowcharts for displaying congestion notification markers provided in the embodiments of this application;

[0039] Figure 5 A second flowchart illustrating the display of congestion notification markers provided in this application embodiment;

[0040] Figure 6 The third flowchart for displaying congestion notification markers provided in the embodiments of this application;

[0041] Figure 7 A schematic diagram of the functional modules of each device in the stacking system provided in the embodiments of this application;

[0042] Figure 8 This is a schematic diagram of the functional modules activated by each device in the stacking system provided in the embodiments of this application. Detailed Implementation

[0043] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. The components of the embodiments of this application described and shown in the accompanying drawings can generally be arranged and designed in various different configurations.

[0044] Therefore, the following detailed description of the embodiments of this application provided in the accompanying drawings is not intended to limit the scope of the claimed application, but merely to illustrate selected embodiments of the application. All other embodiments obtained by those skilled in the art based on the embodiments of this application without inventive effort are within the scope of protection of this application.

[0045] It should be noted that similar labels and letters in the following figures indicate similar items. Therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures.

[0046] In the description of this application, it should be noted that the terms "first" and "second" are used only to distinguish descriptions and should not be construed as indicating or implying relative importance.

[0047] It should be noted that, where there is no conflict, the features in the embodiments of this application can be combined with each other.

[0048] Please see Figure 1 This is a schematic diagram of the architecture of a stacking system provided in an embodiment of this application. The stacking system includes multiple devices, each of which can be such as a switch. Each device can be connected to at least one other device. The connection topology of the multiple devices can be a linear topology. Figure 1 (Structure shown), ring topology, etc. Multiple devices in an IP network are collectively represented as a single network node, managed by only one upper-layer software.

[0049] Based on their roles within the stacking system, devices can be categorized as ingress devices, transmission devices, and egress devices. Ingress devices serve as the overall traffic entry point for the stacking system, while egress devices serve as the overall traffic exit point. There can be one or more transmission devices. A transmission device is generally connected to the preceding ingress device and then to the following egress device. When there are multiple transmission devices, the first transmission device is connected to the preceding ingress device and then to the next transmission device. The last transmission device is connected to the following egress device and then to the preceding transmission device. The remaining transmission devices, excluding the first and last ones, are connected sequentially between them.

[0050] Taking a linear topology stacked system as an example, the role of each device in the stacked system is determined by the actual forwarding path of the data packets. For example, ... Figure 2 As shown, when a data packet is forwarded from device 1 to device 3, device 1 will act as the ingress device, device 2 as the transmission device, and device 3 as the egress device. For example, ... Figure 3 As shown, when a data packet is forwarded from device 3 to device 1, device 3 will act as the egress device, device 2 as the transmission device, and device 1 as the egress device.

[0051] Please see Figure 4 The above is a flowchart of a method for displaying congestion notification marking provided in an embodiment of this application. This method can be applied to the aforementioned stacking system and implemented by multiple devices within the stacking system. Please refer to... Figure 4 As shown below, the implementation of the method for displaying congestion notification flags will be introduced.

[0052] S21, when each device receives a data packet, it detects the current congestion status of the device.

[0053] S22, when each device detects that the current congestion state indicates that the device is congested, it maps the current congestion state to the corresponding self-congestion state parameter.

[0054] S23, each of the devices encapsulates its own congestion status parameters into the stack header of the data packet front end, or rewrites the original congestion status parameters in the stack header of the data packet front end based on its own congestion status parameters, and transmits the data packet to the next device, wherein the congestion status parameters in the stack header can be mapped to the Explicit Congestion Notification (ECN) information.

[0055] In this embodiment, each device in the stacking system has a corresponding role, such as an ingress device, an egress device, or a transmission device. Devices with different roles can have different functionalities in the stacking system, but they can also have common functionalities.

[0056] In this embodiment, the stacking system, as a whole, can communicate with both the data transmitting device and the data receiving device. It can forward data packets sent by the data transmitting device to the data receiving device, enabling data packet interaction between the two. Data packets enter from the ingress port of the ingress device and, after passing through the transmission device, are finally sent out from the egress port of the egress device. Alternatively, data packets may enter from the ingress port of the ingress device and then be sent directly from the egress port. This embodiment primarily focuses on scenarios where data packets pass through the ingress device, transmission device, and egress device; therefore, the application scenario is limited to situations where data packets sequentially pass through the ingress device, transmission device, and egress device.

[0057] Therefore, each device in the stacked system can receive data packets. For example, the data packets received by the ingress device are sent by the data transmitting device, while the data packets received by the transmit and egress devices are sent by the device above them in the stacked system.

[0058] Each device has the ability to determine whether it is experiencing congestion. Therefore, upon receiving a data packet, each device checks its current congestion status to determine whether congestion has occurred. In one possible implementation, when checking its current congestion status, each device can obtain the queue length of the data queue at its output port and determine whether the queue length exceeds a preset length to determine the current congestion status. If the queue length exceeds the preset length, it is determined that the device is currently experiencing congestion; if the queue length does not exceed the preset length, it is determined that the device is not currently experiencing congestion.

[0059] Furthermore, in this embodiment, after receiving a data packet, each device can also detect the queue length of the data queue at its input port and determine whether the queue length plus the size of the received data packet exceeds a preset maximum length. If it exceeds the preset maximum length, the received data packet is dropped; if it does not exceed the preset maximum length, the received data packet is added to the data queue at the output port.

[0060] If a device detects a congestion state indicating that it is experiencing congestion, it maps the current congestion state to its corresponding Congestion Status parameter. This congestion status parameter can be transmitted along with data packets within the stacked system.

[0061] For example, for an ingress device, since the received data packets are sent by the data transmitting device, they have not been processed by the stacking system. After the ingress device determines that it is congested and obtains the corresponding mapped congestion status parameters, it can encapsulate its congestion status parameters into the stacking header at the front end of the data packet and transmit it to the next device along with the data packet.

[0062] For transmission and egress devices, since the received data packets have always been processed by the previous device, meaning they carry congestion status parameters, after a transmission or egress device determines that it is experiencing congestion and obtains its corresponding mapped congestion status parameters, it can rewrite the original congestion status parameters in the stack header of the data packet based on its own congestion status parameters before transmitting the data packet to the next device.

[0063] The congestion status parameters in the stack header can be mapped to Explicit Congestion Notification (ECN) information. That is, the congestion status parameters can be transmitted along with the data packets during internal transmission within the stack system. When the data packets need to be sent to an external data receiving device, the congestion status parameters can be mapped to ECN information and transmitted along with the data packets. This allows the data receiving device to determine the congestion status of the stack system based on the ECN information in the received data packets and to provide feedback to the data sending device. If congestion occurs in the stack system, the data sending device can adjust the data flow accordingly to alleviate the congestion.

[0064] As can be seen, in this embodiment, each device in the stacking system can detect its own congestion status and, upon determining that it is experiencing congestion, map its current congestion status to its own congestion status parameters, which are then carried in the data packet and transmitted along with it. Thus, regardless of which device experiences congestion, the data packet can be marked with an ECN (Enhanced Communication Name) to achieve the purpose of displaying a congestion notice.

[0065] For example, in a scenario where devices with data packet editing capabilities, such as ingress and egress devices, are not congested, while transmission devices, which lack this capability, are congested, the solution in this embodiment allows the transmission device to rewrite this congestion status information. This rewrites the congestion status information, enabling the ECN information to reflect its own congestion status when the congestion status information is subsequently mapped to ECN information. This ensures accurate feedback of the congestion status in the stacking system to the data receiving and sending devices, avoiding the drawback of transmission devices lacking data packet editing capabilities and failing to reflect congestion when only the transmission device is congested, thus preventing exacerbation of congestion.

[0066] As described above, each device in a stacked system shares common functionalities, but can also possess different functionalities due to their different roles. Please refer to [link / reference]. Figure 5 In the marking method provided in the embodiments, for the entry device in the stacking system, the following steps may also be included:

[0067] S11, for the entry device among the plurality of devices, after receiving the data packet, the entry device parses the ECN information carried in the data packet.

[0068] S12, the entry device maps the parsed ECN information into corresponding congestion status parameters, and then performs the step of detecting the current congestion status of the device.

[0069] In this embodiment, the data packets received by the ingress device in the inbound direction have a packet format of EtherNet header + IP header + payload, wherein the IP header contains an ECN field. The ingress device has the ability to map the ECN field information of the IP header to congestion status parameters in the inbound direction.

[0070] The congestion status parameters include a first status parameter indicating that the data packet does not support congestion detection and ECN marking, a second status parameter indicating that the data packet supports congestion detection and is currently experiencing congestion, and a third status parameter indicating that the data packet supports congestion detection and is currently not experiencing congestion.

[0071] For example, when the congestion status parameter CongestionStatus is 0, it indicates that the currently processed data packet does not support congestion detection and ECN marking functions. When CongestionStatus is 1, it indicates that the currently processed data packet supports congestion detection, but congestion has not occurred. When CongestionStatus is 2, it indicates that the currently processed data packet supports congestion detection, and congestion has occurred.

[0072] The mapping rules between ECN field information and congestion status parameters can be configured. For example, the default configuration rules are shown in Table 1 below.

[0073] Table 1. Mapping rules for ECN fields to congestion state parameters

[0074]

[0075] In this embodiment, the ingress device can map the ECN information in the data packet to the corresponding congestion status parameters according to the mapping rules in Table 1 above. Based on this, the ingress device can detect the congestion status of its own device, and if it determines that the device is congested, it maps the current congestion status to the corresponding self-congestion status parameter, for example, the mapped self-congestion status parameter is 2.

[0076] The ingress device rewrites its own congestion status parameters based on the ECN information mapped in the data packet. In the outgoing direction, the ingress device encapsulates its rewritten congestion status parameters into the stacking header at the front end of the data packet. The stacking header is an additional field appended to the front end of the data packet entering the ingress device, where N bits represent its own congestion status parameters. The ingress device sends the stacking header along with the data packet to the transmission chip via the stacking cable within the stacking system.

[0077] Based on the marking method provided in this embodiment, for the transmission device in the stacking system, the following steps may also be included:

[0078] For transmission devices among multiple devices, after receiving a data packet, the original congestion status parameters in the stack header of the data packet are parsed out, and then the step of detecting the current congestion status of the device is performed.

[0079] In this embodiment, the incoming data packets received by the transmission device carry a stacking header of a certain length. The congestion status parameters carried in the stacking header need to be parsed out to be used as the internal congestion status of the device.

[0080] In addition, the transmission device possesses the common functions of the aforementioned devices, such as detecting its own congestion status and, upon determining that it is experiencing congestion, mapping the current congestion status to corresponding congestion status parameters. Based on these congestion status parameters, it rewrites the original congestion status parameters in the stack header of the data packet and then transmits the data packet to the next device.

[0081] In this embodiment, when the transmission device experiences congestion, it directly rewrites the congestion status parameters in the stack header without editing the data packets. The transmission device does not need to perform any deletion or addition operations to the stack header; instead, it directly rewrites the congestion status parameters in the stack header. Thus, the transmission device has low implementation cost, simple logic, and advantages such as high efficiency and low latency.

[0082] Based on this, for the egress device in the stacking system, after receiving the data packet, the egress device parses out the original congestion status parameters in the stacking header of the data packet, and then performs the step of detecting the current congestion status of the device.

[0083] Similarly, the incoming data packets received by the egress device carry a stacking header of a certain length. The congestion status parameters carried in the stacking header need to be parsed out and directly used as the congestion status of this device. Based on this, the egress device performs the above-mentioned detection of its own congestion status until it rewrites the original congestion status parameters in the stacking header of the data packet based on its own congestion status parameters.

[0084] Data packets sent from the output device to the external data receiving device need to include information indicating the congestion status of the stacked system. Therefore, please refer to [link to relevant documentation]. Figure 6 The marking method provided in this embodiment further includes the following steps:

[0085] S31, for the egress device among the plurality of devices, after the egress device rewrites the original congestion status parameters in the stack header of the data packet based on its own congestion status parameters, it maps the current congestion status parameters in the stack header back to the ECN information.

[0086] S32, the export device rewrites the ECN information in the data packet based on the mapped ECN information, and then performs the step of transmitting the data packet to the next device, wherein the next device is an external data receiving device.

[0087] In this embodiment, the egress device may also have the function of mapping congestion status parameters back to ECN information. The mapping rules between congestion status parameters and ECN information are as shown in Table 2.

[0088] Table 2 Mapping Rules for Congestion State Parameters to ECN Fields

[0089]

[0090] In this embodiment, the egress device can ultimately map the congestion status parameters back to the ECN field. It should be noted that, for the egress device, the "next device" refers to the external data receiving device.

[0091] In this embodiment, the ECN field in the IP header of the data packet is edited only on the egress device, without needing to be edited on each device. This reduces the latency of data packet forwarding when forwarding data packets in a stacked system.

[0092] Furthermore, in this embodiment, if the transmission device detects that the current congestion state indicates that the device itself is not congested, it can directly transmit the data packet to the next device. That is, the congestion state parameters in the stack header are not modified.

[0093] For an ingress device, if the current congestion status indicates that the device is not congested, the ingress device will encapsulate the congestion status parameters representing the non-congestion status into the stack header and transmit them to the next device.

[0094] For outgoing equipment, if the current congestion status is detected and it indicates that the equipment is not congested, it is still necessary to parse the stack header in the data packet and map the congestion status parameters in the stack header back to the ECN field.

[0095] In this embodiment, although each device has different functions due to its different role in the stacking system, in order to ensure the uniformity of the chip architecture in the stacking system, each device includes multiple modules in this embodiment. These multiple modules include a network port congestion state mapping module, a stacking port congestion state mapping module, a congestion determination module, a congestion state encapsulation module, a congestion state rewriting module, and a congestion state reverse mapping module.

[0096] like Figure 7 As shown in the diagram, the network port congestion state mapping module and the stacking port congestion state mapping module can be assigned to the inbound congestion state mapping module, while the congestion state encapsulation module, the congestion state rewriting module, and the congestion state reverse mapping module can be assigned to the outbound congestion state mapping module.

[0097] Each device in the stacking system dynamically selects and activates some of the multiple modules based on its role in the stacking system.

[0098] Specifically, the network port congestion state mapping module maps ECN information to corresponding congestion state parameters. The stacking port congestion state mapping module parses the original congestion state parameters in the stacking header. The congestion determination module detects the current congestion state of the device. The congestion state encapsulation module encapsulates its own congestion state parameters into the stacking header. The congestion state rewriting module rewrites the original congestion state parameters in the stacking header of the data packet based on its own congestion state parameters. The congestion state reverse mapping module maps the congestion state parameters in the current stacking header back to ECN information.

[0099] Based on the roles of the ingress, transmission, and egress devices in the stacking system, and the specific functions of each module, the ingress device will activate the aforementioned network port congestion state mapping module, congestion determination module, and congestion state encapsulation module. The transmission device will activate the aforementioned stacking port congestion state mapping module, congestion determination module, and congestion state rewriting module. The egress device will activate the aforementioned stacking port congestion state mapping module, congestion determination module, and congestion state reverse mapping module.

[0100] Please refer to the following: Figure 8 For ingress devices, data packets will be processed via the path indicated by the first arrow. For transmission devices, data packets will be processed via the path indicated by the second arrow. For egress devices, data packets will be processed via the path indicated by the third arrow.

[0101] In summary, the marking method provided in this embodiment firstly ensures that each device has a unified chip architecture. Each device can activate corresponding modules based on its role in the stacking system to achieve the desired functionality. Within the stacking system, each device maintains and carries congestion status parameters, and the ECN field of the data packet is uniformly rewritten on the egress device. On the transmission device, only the congestion status parameters are rewritten, without deleting or adding stack headers.

[0102] Thus, when congestion occurs on any device in the stacked system, the corresponding ECN information can be marked on the data packet to achieve the purpose of displaying congestion notice. Furthermore, the ECN field in the data packet is only edited on the egress device, eliminating the need for editing on each device, thereby reducing latency when forwarding data packets in the stacked system. Since the transmission device only reflects its own congestion status by rewriting the congestion status parameters in the stack header, the device chip implementation is low-cost, logically simple, and highly efficient with low latency.

[0103] In addition, in another embodiment of the present application, a stacking system is provided, wherein each of the multiple devices included in the stacking system is used to detect the current congestion state of the device when a data packet is received;

[0104] Each of the aforementioned devices is further configured to map the current congestion state to a corresponding self-congestion state parameter when it is detected that the current congestion state indicates that the device is congested.

[0105] Each of the aforementioned devices is further configured to encapsulate its own congestion status parameters into the stack header of the data packet front end, or to rewrite the original congestion status parameters in the stack header of the data packet front end based on its own congestion status parameters, and transmit the data packet to the next device, wherein the congestion status parameters in the stack header can be mapped to each other with the Explicit Congestion Notification (ECN) information.

[0106] In one possible implementation, for an ingress device among the plurality of devices, the ingress device is configured to parse the ECN information carried in the data packet after receiving the data packet;

[0107] The entry device is also used to map the parsed ECN information into corresponding congestion status parameters, and then perform the detection of the current congestion status of the device.

[0108] In one possible implementation, for the egress device among the plurality of devices, the egress device is used to rewrite the original congestion status parameters in the stack header of the data packet based on its own congestion status parameters, and then map the congestion status parameters in the current stack header back to ECN information.

[0109] The export device is also used to rewrite the ECN information in the data packet based on the mapped ECN information, and then transmit the data packet to the next device, wherein the next device is an external data receiving device.

[0110] In one possible implementation, for the transmission device or egress device among the plurality of devices, the transmission device or egress device is used to parse out the original congestion status parameters in the stack header of the data packet after receiving the data packet, and then perform the detection of the current congestion status of the device.

[0111] In one possible implementation, each of the devices includes multiple modules, which include a network port congestion state mapping module, a stacking port congestion state mapping module, a congestion determination module, a congestion state encapsulation module, a congestion state rewriting module, and a congestion state reverse mapping module. Each device dynamically selects and starts some of the multiple modules to work according to its role in the stacking system.

[0112] The network port congestion status mapping module is used to map ECN information into corresponding congestion status parameters; the stacking port congestion status mapping module is used to parse the original congestion status parameters in the stacking header; the congestion determination module is used to detect the current congestion status of the device; the congestion status encapsulation module is used to encapsulate its own congestion status parameters into the stacking header; the congestion status rewriting module is used to rewrite the original congestion status parameters in the stacking header of the data packet based on its own congestion status parameters; and the congestion status reverse mapping module is used to map the congestion status parameters in the current stacking header back to ECN information.

[0113] In one possible implementation, the transmission device is further configured to directly transmit the data packet to the next device when it detects that the current congestion state indicates that the device is not congested.

[0114] In one possible implementation, the congestion state parameters include a first state parameter indicating that the data packet does not support congestion detection and ECN marking, a second state parameter indicating that the data packet supports congestion detection and is currently experiencing congestion, and a third state parameter indicating that the data packet supports congestion detection and is currently not experiencing congestion.

[0115] In one possible implementation, each device is used to obtain the queue length of the data queue at its output port, determine whether the queue length exceeds a preset length, and if it exceeds the preset length, determine that the device is currently experiencing congestion.

[0116] In one possible implementation, each of the devices is further configured to, after receiving a data packet, detect the queue length of the data queue at the input port of the device, determine whether the queue length plus the packet size of the received data packet exceeds a preset maximum length, and if it exceeds the preset maximum length, then perform packet loss processing on the received data packet; if it does not exceed the preset maximum length, then add the received data packet to the data queue at the input port.

[0117] It should be noted that in the stacking system provided in this embodiment, the display congestion notification marking method corresponding to the above embodiments can be implemented based on each device. For details not covered in this embodiment, please refer to the description of the relevant parts of the above embodiments. This embodiment will not repeat them here.

[0118] In summary, the display congestion notification marking method and stacking system provided in this application, for each device in the stacking system, after receiving a data packet, each device detects its current congestion state. When the detected current congestion state indicates that the device is congested, it maps the current congestion state to its corresponding self-congestion state parameters. This allows the self-congestion state parameters to be encapsulated in the stacking header at the front end of the data packet, or the existing congestion state parameters in the stacking header at the front end of the data packet to be rewritten based on the self-congestion state parameters before the data packet is transmitted to the next device. The congestion state parameters in the stacking header can be mapped to and from the display congestion notification (ECN) information. This solution enables any device in the stacking system to mark data packets with ECN when congestion occurs, achieving the purpose of displaying congestion notification.

[0119] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for displaying congestion notification markers, characterized in that, Applied to a stacked system comprising multiple devices, the method includes: When each device receives a data packet, it detects its current congestion status. When each device detects that the current congestion state indicates that it is congested, it maps the current congestion state to its corresponding congestion state parameter. Each device encapsulates its own congestion status parameters into the stack header of the data packet front end, or rewrites the original congestion status parameters in the stack header of the data packet front end based on its own congestion status parameters, and transmits the data packet to the next device. The congestion status parameters in the stack header can be mapped to the Explicit Congestion Notification (ECN) information. The plurality of devices includes inlet devices, transmission devices, and outlet devices, and the method further includes: For the entry device among the plurality of devices, after receiving a data packet, the entry device parses the ECN information carried in the data packet; the entry device maps the parsed ECN information into the corresponding congestion status parameters, and then performs the step of detecting the current congestion status of the device. For the egress device among the plurality of devices, after rewriting the original congestion status parameters in the stack header of the data packet based on its own congestion status parameters, the egress device maps the congestion status parameters in the current stack header back to ECN information; the egress device rewrites the ECN information in the data packet based on the mapped ECN information, and then performs the step of transmitting the data packet to the next device, wherein the next device is an external data receiving device.

2. The method for displaying congestion notification markers according to claim 1, characterized in that, The plurality of devices further includes a transmission device connected to both the preceding inlet device and the following outlet device, and the method further includes: For the transmission device or egress device among the multiple devices, after receiving a data packet, the original congestion status parameters in the stack header of the data packet are parsed out, and then the step of detecting the current congestion status of the device is performed.

3. The method for displaying congestion notification markers according to claim 2, characterized in that, Each of the aforementioned devices includes multiple modules, which include a network port congestion state mapping module, a stacking port congestion state mapping module, a congestion determination module, a congestion state encapsulation module, a congestion state rewriting module, and a congestion state reverse mapping module. Each of the aforementioned devices dynamically selects and activates some of the multiple modules according to its role in the stacking system. The network port congestion status mapping module is used to map ECN information into corresponding congestion status parameters; the stacking port congestion status mapping module is used to parse the original congestion status parameters in the stacking header; the congestion determination module is used to detect the current congestion status of the device; the congestion status encapsulation module is used to encapsulate its own congestion status parameters into the stacking header; the congestion status rewriting module is used to rewrite the original congestion status parameters in the stacking header of the data packet based on its own congestion status parameters; and the congestion status reverse mapping module is used to map the congestion status parameters in the current stacking header back to ECN information.

4. The method for displaying congestion notification markers according to claim 2, characterized in that, The method further includes: When the transmission device detects that the current congestion status indicates that the device itself is not congested, it directly transmits the data packet to the next device.

5. The method for displaying congestion notification markers according to claim 1, characterized in that, The congestion status parameters include a first status parameter indicating that the data packet does not support congestion detection and ECN marking, a second status parameter indicating that the data packet supports congestion detection and is currently experiencing congestion, and a third status parameter indicating that the data packet supports congestion detection and is currently not experiencing congestion.

6. The method for displaying congestion notification markers according to claim 1, characterized in that, The step of detecting the current congestion status of this device includes: Obtain the queue length of the data queue at the output port of this device, and determine whether the queue length exceeds a preset length. If it exceeds the preset length, determine that the device is currently experiencing congestion.

7. The method for displaying congestion notification markers according to claim 1, characterized in that, The method further includes: After receiving a data packet, each device detects the queue length of the data queue at its input port and determines whether the queue length plus the size of the received data packet exceeds a preset maximum length. If the received data packet exceeds the preset maximum length, the packet will be dropped; if the received data packet does not exceed the preset maximum length, the packet will be added to the data queue at the input port.

8. A stacking system, characterized in that, For implementing the method of displaying congestion notification marking as described in any one of claims 1-7, the stacking system includes multiple devices; Each of the aforementioned devices is configured to detect its current congestion status upon receiving a data packet; Each of the aforementioned devices is further configured to map the current congestion state to a corresponding self-congestion state parameter when it is detected that the current congestion state indicates that the device is congested. Each of the aforementioned devices is further configured to encapsulate its own congestion status parameters into the stack header of the data packet front end, or to rewrite the original congestion status parameters in the stack header of the data packet front end based on its own congestion status parameters, and transmit the data packet to the next device, wherein the congestion status parameters in the stack header can be mapped to each other with the Explicit Congestion Notification (ECN) information.

Images