Congestion signaling processing method, forwarding device and readable storage medium

Abstract

The invention discloses a congestion signaling processing method, forwarding equipment and a readable storage medium, and belongs to the technical field of communication. The method comprises the following steps: a forwarding device receives a service message; the forwarding equipment obtains congestion signaling configuration information matched with the service message, and the congestion signaling configuration information is used for indicating a configuration parameter for processing a congestion signaling; and the forwarding equipment executes corresponding congestion signaling processing on the service message based on the congestion signaling configuration information.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a congestion signaling processing method, a forwarding device, and a readable storage medium. Background Technology

[0002] Currently, with the development of networks, network congestion detection, congestion information transmission signaling, and flow control have become enduringly popular technologies. Related technologies include In-band Operation, Administration and Maintenance (In-band OAM), In-situ Operation, Administration and Maintenance (In-situ OAM), and Congestion Signaling (CSIG).

[0003] In this process, CSIG collects information on the network, and its initiation and termination are handled by the host, meaning the network essentially only provides the data. If the operator does not have management authority over the end-side devices, the forwarding devices in the network cannot proactively perform CSIG-related processing on service packets. Summary of the Invention

[0004] This application provides a congestion signaling processing method, a forwarding device, and a readable storage medium, which can solve the problem that the forwarding device cannot actively perform CSIG-related processing on service packets.

[0005] To solve the above-mentioned technical problems, this application is implemented as follows:

[0006] In a first aspect, a congestion signaling processing method is provided, the method comprising: a forwarding device receiving a service packet; the forwarding device acquiring congestion signaling configuration information matching the service packet, wherein the congestion signaling configuration information is used to indicate configuration parameters for processing congestion signaling; and the forwarding device performing corresponding congestion signaling processing on the service packet based on the congestion signaling configuration information.

[0007] Secondly, a method for configuring congestion signaling is provided. The method includes: for a target service, a controller determines congestion signaling configuration information of a forwarding device, wherein the congestion signaling configuration information is used to instruct the forwarding device on configuration parameters for processing congestion signaling of the target service; the controller sends a target configuration to the forwarding device, wherein the target configuration includes identification information of the target service and the congestion signaling configuration information corresponding to the target service.

[0008] Thirdly, a forwarding device is provided, the forwarding device including a processor and a memory, the memory storing programs or instructions that can run on the processor, the programs or instructions implementing the above-described congestion signaling processing method when executed by the processor.

[0009] Fourthly, a controller is provided, the controller including a processor and a memory, the memory storing programs or instructions that can run on the processor, the programs or instructions implementing the congestion signaling configuration method described above when executed by the processor.

[0010] Fifthly, a readable storage medium is provided, characterized in that a program or instruction is stored on the readable storage medium, and when the program or instruction is executed by a processor, it implements the above-described congestion signaling processing method or the above-described congestion signaling configuration method.

[0011] In a sixth aspect, a computer program product is provided, the computer program product comprising a computer program stored on a non-transitory computer-readable storage medium, the computer program comprising program instructions that, when executed by a computer, cause the computer to perform the congestion signaling processing method or the congestion signaling configuration method described above.

[0012] In this embodiment, the forwarding device can receive service packets, then obtain congestion signaling configuration information matching the service packets, and then perform corresponding congestion signaling processing on the service packets based on the congestion signaling configuration information. This can solve the problem in related technologies that the forwarding device cannot actively perform CSIG-related processing on service packets, and facilitate network flow control at the edge.

[0013] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and do not limit this application. Attached Figure Description

[0014] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0015] Figure 1A A schematic diagram of a CSIG compression format provided in the embodiments of this application;

[0016] Figure 1B A schematic diagram of a CSIG extended format provided in the embodiments of this application;

[0017] Figure 2A A schematic diagram illustrating the basic working principle of CSIG provided for embodiments of this application;

[0018] Figure 2BA schematic diagram illustrating another basic working principle of CSIG provided for an embodiment of this application;

[0019] Figure 3 A flowchart of a congestion signaling processing method provided in Embodiment 1 of this application;

[0020] Figure 4A A schematic diagram of a CSIG compression format provided in Embodiment 1 of this application;

[0021] Figure 4B A schematic diagram of a CSIG extended format provided in Embodiment 1 of this application;

[0022] Figure 5 A flowchart of another congestion signaling processing method provided in Embodiment 2 of this application;

[0023] Figure 6 A flowchart illustrating yet another congestion signaling processing method provided in Embodiment 3 of this application;

[0024] Figure 7 A flowchart illustrating yet another congestion signaling processing method provided in Embodiment 4 of this application;

[0025] Figure 8 A flowchart illustrating a congestion signaling configuration method provided in Embodiment 5 of this application;

[0026] Figure 9 This is a flowchart illustrating the blocking signaling processing method in Embodiment Six of this application;

[0027] Figure 10 This is a schematic diagram of a process for implementing end-to-end network collaboration in Embodiment 7 of this application;

[0028] Figure 11 This is a schematic diagram of a network topology provided in Embodiment 8 of this application;

[0029] Figure 12 This is a schematic diagram of a network topology provided in Embodiment 9 of this application;

[0030] Figure 13 This is a schematic diagram of a CSIG-initiated method as described in an embodiment of this application;

[0031] Figure 14 A schematic diagram illustrating an inter-system interaction relationship provided in an embodiment of this application;

[0032] Figure 15 This is a structural block diagram of an electronic device provided in an embodiment of this application. Detailed Implementation

[0033] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0034] Network congestion detection, congestion information transmission signaling, and flow control are capabilities that Quality of Service (QoS) is constantly evolving and improving, and are enduringly popular technologies.

[0035] Currently, there are various technical solutions for congestion signaling, including In-Band Operation, Administration and Maintenance (In-Band OAM), In-situ Operation, Administration and Maintenance (In-situ OAM), and Congestion Signaling (CSIG).

[0036] Among related technologies, CSIG is a recently launched technology. It not only has the advantages of carrying information along the flow and following the same path as the service, but also has the advantages of flexible and configurable measurable information, less information carried, and less bandwidth loss. The basic principle of CSIG is briefly introduced below.

[0037] In related technologies, the CSIG compression format is as follows: Figure 1A As shown in Table 1, the meaning and placeholders of each field are as follows:

[0038] Table 1

[0039]

[0040] In related technologies, the CSIG extended format is as follows: Figure 1B As shown in Table 2, the meaning and placeholders of each field are as follows:

[0041] Table 2

[0042]

[0043]

[0044] It is important to note that CSIG signaling is encapsulated together with the service message. There are several encapsulation methods, as shown below:

[0045] Ethernet encapsulation: dstmac / srcmac / csig-tag / ethertype / payload

[0046] VLAN-encapsulated: dstmac / srcmac / vlan-tag / csig-tag / ethertype / payload

[0047] Encapsulation with Layer 2 VLAN: dstmac / srcmac / vlan-tag / vlan-tag / csig-tag / ethertype / payload Encapsulation with Multi-Layer VLAN: dstmac / srcmac / vlan-tag / vlan-tag / vlan-tag / csig-tag / ethertype / payload

[0048] Encapsulation with MACSEC: dstmac / srcmac / security-tag / vlan-tag / csig-tag / ethertype / payload

[0049] In the above encapsulation methods:

[0050] dstmac --- Destination Media Access Control (MAC) address

[0051] Srcmac --- Source MAC address

[0052] csig-tag --- CSIG information, is like... Figure 1A as well as Figure 1B The information shown

[0053] Ethertype --- Ethernet type

[0054] Payload – Upper-layer information and data (effective payload)

[0055] vlan-tag --- Virtual Local Area Network (VLAN) encapsulation

[0056] security-tag --- Media Access Control Security (MACsec) header (MACsec is a MAC layer encryption technology).

[0057] The congestion signaling (CSIG signaling) involved in the embodiments of this application refers to the content and format of the csig-tag encapsulated in the service message.

[0058] In related technologies, the basic working principle of CSIG is as follows: Figure 2A as well as Figure 2B As shown, Figure 2A As shown, the CSIG signaling originates from Host1, travels through ToR1->Aggr1->Core->Aggr2->ToR2, and arrives at Host2. It measures information such as available bandwidth, available bandwidth ratio (available bandwidth / link bandwidth), and node processing latency at each node along the path. At each node, the measured values ​​specified in the CSIG signaling are compared, and updated as necessary. Figure 2A As shown, the first round measures the minimum available bandwidth, and the final record is the information of the ToR2 node, port, and 20G, which is then sent to Host2; the second round measures the percentage of the minimum available bandwidth, and the final record is the information of the ToR1 node, port, and 12.5%, which is then sent to Host2; the third round measures the maximum latency, and the final record is the information of the Core node and 18us, which is then sent to Host2.

[0059] For handling nodes in the network that do not support CSIG, one approach is to strip the CSIG encapsulation information from the preceding node, such as... Figure 2B As shown, Aggr2 does not support CSIG. Therefore, on the Core node, the CSIG encapsulation can be stripped away, so that the information measured earlier will not reach Host2.

[0060] Therefore, in related technologies, the initiation and termination of CSIG signaling are handled by the host, meaning that the forwarding devices (also known as forwarding nodes) in the network only provide data. If the operator does not have management authority over the end-side devices, the forwarding devices in the network cannot proactively perform CSIG-related processing on service packets. To address this issue, this application provides an improved technical solution to solve the above-mentioned technical problem. The technical solution provided by this application embodiment will be described below with reference to the accompanying drawings.

[0061] Example 1

[0062] like Figure 3 As shown in the figure, this application provides a congestion signaling processing method, executed by the forwarding device, the method including:

[0063] S301: Forwarding device receives service messages.

[0064] In this embodiment of the application, the forwarding device includes a forwarding node in the network. The forwarding device may receive service packets from a host or from an upstream node. The received service packets may or may not contain congestion signaling.

[0065] S302: The forwarding device obtains congestion signaling configuration information that matches the service message, wherein the congestion signaling configuration information is used to indicate the configuration parameters for processing congestion signaling.

[0066] In this embodiment of the application, the forwarding device can pre-store congestion signaling configuration information for at least one service. After receiving a service packet, it can obtain congestion signaling configuration information that matches the received service packet. The congestion signaling configuration information is used to indicate the configuration parameters for processing congestion signaling, so that the forwarding device can perform corresponding processing on the service packet according to the congestion signaling configuration information.

[0067] In an optional implementation, before the forwarding device obtains the congestion signaling configuration information matching the service message, the method may further include: the forwarding device receiving a target configuration, wherein the target configuration includes service identification information of at least one service and the congestion signaling configuration information corresponding to each of the at least one service.

[0068] In some implementations, a separate controller can be added to the existing network architecture, and the forwarding device can receive the target configuration sent by the controller. However, this is not the only possibility; the forwarding device can also acquire the target configuration from external input.

[0069] In an optional implementation, the forwarding device obtaining congestion signaling configuration information matching the service packet may include the following steps:

[0070] Step 1: The forwarding device searches for service identifier information that matches the service identifier of the service packet from the target configuration;

[0071] Step 2: The forwarding device obtains the congestion signaling configuration information corresponding to the found service identifier information from the target configuration.

[0072] In some implementations, the service identification information can be a service ID. It's important to note that the service ID parameter doesn't necessarily have to be a single parameter; multiple parameters can be used to jointly identify a service. The primary purpose of the service identification information is to identify the service; flow-id or other wildcard formats can also be used as service identification information.

[0073] In one optional implementation, the congestion signaling may include a send-to-controller flag, which indicates whether the service message is a message that sends congestion signaling probe information to the controller.

[0074] In some implementations, the reserved bit of CSIG can be used to indicate whether to send to the controller, that is, the reserved bit of CSIG in the related art is used as the send to controller flag bit (U).

[0075] In some implementations, it is possible to Figure 1A The CSIG compression format shown is improved, and the improved congestion signaling message format is as follows: Figure 4A As shown in Table 3, the meaning and placeholder of each field are as follows.

[0076] Table 3

[0077]

[0078] In some implementation methods, it is also possible to Figure 1B The CSIG extended format shown is improved, and the improved congestion signaling message format is as follows: Figure 4B As shown in Table 4, the meaning and placeholders of each field are as follows:

[0079] Table 4

[0080]

[0081] It should be noted that the U flag can be on any reserved bit, not just the 31st bit.

[0082] In one optional implementation, the congestion signaling configuration information includes at least one of the following:

[0083] 1) The first indication information (isOrigin) is used to indicate whether the forwarding device initiates congestion signaling as the starting point. For example, if the forwarding device is an edge node of the service, the congestion signaling configuration information may include the first indication information, which indicates that the forwarding device can initiate congestion signaling as the starting point. That is, it can encapsulate CSIG signaling for the service packet even if it does not encapsulate CSIG signaling in the received service packet. For example, if isOrigin is a first preset value (e.g., 1), it means that the forwarding device initiates congestion signaling as the starting point.

[0084] 2) The second indication information (isModify) is used to indicate whether the forwarding device modifies the congestion signaling uploading controller flag. For example, if the forwarding device is an edge node or an intermediate node, the congestion signaling configuration information may include the second indication information, and the second indication information may indicate that the forwarding device can modify the congestion signaling uploading controller flag. For example, assuming that the congestion signaling uploading controller flag encapsulated in the received service message indicates that the service message is not a message for sending congestion signaling probe information to the controller, the forwarding device can modify the value of the uploading controller flag so that the uploading controller flag indicates that the service message is a message for sending congestion signaling probe information to the controller.

[0085] For example, if isModify is the second preset value (e.g., 1), it indicates that the forwarding device can modify the congestion signaling sender controller flag.

[0086] 3) Third indication information (isNotify) is used to indicate whether the forwarding device should send congestion signaling probe information; for example, for CSIG stripping nodes and edge nodes in the network, the congestion signaling configuration information may include third indication information, and the third indication information may indicate that the forwarding device should send congestion signaling probe information.

[0087] For example, if isNotify is the third preset value (e.g., 1), it indicates that the forwarding device sends congestion signaling probe information.

[0088] 4) Service type and initial value for congestion signaling detection. For example, for a forwarding device that serves as the starting point for congestion signaling, the congestion signaling configuration information may include the service type and initial value for congestion signaling detection, so that the forwarding device can encapsulate congestion signaling based on the service type and initial value.

[0089] S303: The forwarding device performs corresponding congestion signaling processing on the service packet based on the congestion signaling configuration information.

[0090] In this embodiment, the forwarding device can perform corresponding congestion signaling processing on service packets based on congestion signaling configuration information. For example, if the congestion signaling configuration information includes first indication information, and the first indication information indicates that the forwarding device can initiate congestion signaling as a starting point, and the forwarding device detects whether the service packet encapsulates CSIG signaling, if not, the forwarding device can encapsulate the service packet with CSIG signaling before forwarding the service packet. As another example, if the congestion signaling configuration information includes second indication information, and the second indication information indicates that the forwarding device modifies the congestion signaling send-to-controller flag, then after detecting that the service packet encapsulates CSIG signaling, the forwarding device determines whether the CSIG signaling send-to-controller flag is a preset value. If not, it modifies the CSIG signaling send-to-controller flag to the preset value, where the preset value indicates that the service packet is a packet sending congestion signaling probe information to the controller.

[0091] The technical solution provided in this application embodiment enables the forwarding device to obtain congestion signaling configuration information matching the service packet after receiving the service packet, and then perform corresponding congestion signaling processing on the service packet based on the congestion signaling configuration information. This allows the forwarding device to proactively process congestion signaling for the service packet, facilitating network flow control at the edge.

[0092] Example 2

[0093] In this embodiment of the application, the congestion signaling configuration information includes at least the first indication information. That is, the congestion signaling configuration information includes first indication information (isOrigin) used to indicate whether the forwarding device initiates congestion signaling as the starting point.

[0094] like Figure 5 As shown in the embodiment of this application, another congestion signaling processing method is provided, which is executed by the forwarding device side. The method includes:

[0095] S501: Forwarding device receives service messages.

[0096] This step is the same as S301 in Embodiment 1. For details, please refer to the above description, which will not be repeated here.

[0097] S502: The forwarding device obtains congestion signaling configuration information that matches the service message, wherein the congestion signaling configuration information is used to indicate the configuration parameters for processing congestion signaling.

[0098] This step is the same as S302 in Embodiment 1, and you can refer to the relevant description above for details, which will not be repeated here.

[0099] S5031: Corresponding to the determination that the service message does not contain congestion signaling and the first indication information indicates that congestion signaling is initiated as the starting point, the forwarding device encapsulates the target congestion signaling into the service message.

[0100] In this embodiment of the application, if the forwarding device determines that the service message does not encapsulate congestion signaling and the first indication information indicates that congestion signaling is initiated as the starting point (e.g., isOrigin is 1), the forwarding device can encapsulate the target congestion signaling for the service message.

[0101] In one optional implementation, the forwarding device encapsulating the target congestion signaling in the service packet may include: the forwarding device encapsulating the target congestion signaling in the service packet and setting the information type and initial value of the target congestion signaling to the service type and initial value in the congestion signaling configuration information.

[0102] In the above-mentioned optional implementation, when the forwarding device encapsulates the target congestion signaling for the service message, the information type and initial value of the target congestion signaling can be set to the service type and initial value in the congestion signaling configuration information. That is, the information type and initial value of the target congestion signaling are determined by the information type and initial value in the congestion signaling configuration information configured in the control plane.

[0103] In one optional implementation, the target congestion signaling includes a send-to-controller flag bit; the forwarding device encapsulates the target congestion signaling into the service packet, and may further include: the forwarding device setting the send-to-controller flag in the target congestion signaling to a preset value, wherein the preset value indicates that the service packet is a packet that sends congestion signaling probe information to the controller.

[0104] In the above-mentioned optional implementation, if the target congestion signaling encapsulated by the forwarding device for the service message includes a send-to-controller flag, the forwarding device can set the send-to-controller flag in the target congestion signaling to a preset value. The preset value can be 1 or other values. This application embodiment does not make specific limitations, so that subsequent nodes can know that the service message is a message that sends congestion signaling detection information to the controller, and then can send congestion signaling detection information to the controller.

[0105] S5032: The forwarding device sends a service message encapsulating the target congestion signaling.

[0106] In this embodiment of the application, the forwarding device can send service packets encapsulated with target congestion signaling. That is, the service packets initially received by the forwarding device are not encapsulated with congestion signaling, but after determining that the forwarding device is the starting point and encapsulating the service packets with target congestion signaling, the forwarding device can eventually send service packets encapsulated with target congestion signaling.

[0107] In the technical solution provided in this application embodiment, after receiving a service packet, the forwarding device obtains congestion signaling configuration information matching the service packet. If the service packet does not encapsulate congestion signaling and the first indication information in the congestion signaling configuration information indicates that the forwarding device initiates congestion signaling as the starting point, the forwarding device can encapsulate the target congestion signaling for the service packet and send the service packet after encapsulating the target congestion signaling. This allows the forwarding device to encapsulate the target congestion signaling as the starting point and send it, thereby improving the flexibility of the network, making full use of congestion signaling, and enhancing the stability of the network.

[0108] Example 3

[0109] In this embodiment of the application, the congestion signaling configuration information includes at least the second indication information. The second indication information (isModify) can be used to indicate whether the forwarding device modifies the congestion signaling uploading controller flag (U). If isModify is a second preset value (e.g., 1), it indicates that the forwarding device can modify the congestion signaling uploading controller flag.

[0110] like Figure 6 As shown in the embodiment of this application, another congestion signaling processing method is provided, which is executed by the forwarding device side. The method includes:

[0111] S601: Forwarding device receives service messages.

[0112] This step is the same as S301 in Embodiment 1. For details, please refer to the above description, which will not be repeated here.

[0113] S602: The forwarding device obtains congestion signaling configuration information that matches the service message.

[0114] The congestion signaling configuration information is used to indicate the configuration parameters for processing congestion signaling.

[0115] This step is the same as S302 in Embodiment 1, and you can refer to the relevant description above for details, which will not be repeated here.

[0116] S6031: Corresponding to the determination that the service message encapsulates a target congestion signaling, the second indication information indicates that the uplink controller flag of the congestion signaling is modified, and the uplink controller flag in the target congestion signaling is not a preset value, the forwarding device sets the uplink controller flag in the target congestion signaling to a preset value.

[0117] The preset value indicates that the service message is a message that sends congestion signaling detection information to the controller.

[0118] In this embodiment of the application, if the service message received by the forwarding device contains a target congestion signaling, and the obtained second indication information indicates that the send-to-controller flag of the congestion signaling is modified (e.g., isModify is 1), and the send-to-controller flag in the target congestion signaling is not a preset value (U is not 1), then the forwarding device can set the send-to-controller flag in the target congestion signaling to a preset value (modify U to 1), which facilitates the control of whether to send congestion signaling detection information to the controller. The implementation of the scheme is more flexible and helps to save resources.

[0119] S6032: The forwarding device sends the service message encapsulated with the modified target congestion signaling.

[0120] In the technical solution provided in this application embodiment, the forwarding device can send service packets encapsulated with modified target congestion signaling. Transmitting these service packets helps ensure uninterrupted service and improves service reliability. Although the send-to-controller flag in the target congestion signaling received by the forwarding device is not a preset value (meaning it does not send congestion signaling detection information to the controller), the forwarding device can modify and send service packets encapsulated with the modified target congestion signaling, so that the send-to-controller flag in the target congestion signaling received by the next forwarding device is a preset value (meaning it can send congestion signaling detection information to the controller). This allows the forwarding device to perform corresponding optimization processing based on the congestion signaling, facilitating flow control at the network edge.

[0121] Example 4

[0122] In this embodiment of the application, the forwarding device can send the congestion information detected by the target congestion signaling to the controller under certain conditions.

[0123] like Figure 7 As shown in the embodiment of this application, another congestion signaling processing method is provided, which is executed by the forwarding device side. The method includes:

[0124] S701: Forwarding device receives service messages.

[0125] This step is the same as S301 in Embodiment 1. For details, please refer to the above description, which will not be repeated here.

[0126] S702: The forwarding device obtains congestion signaling configuration information that matches the service message.

[0127] The congestion signaling configuration information is used to indicate the configuration parameters for processing congestion signaling.

[0128] This step is the same as S302 in Embodiment 1, and you can refer to the relevant description above for details, which will not be repeated here.

[0129] S703: The forwarding device sends the congestion information detected by the target congestion signaling to the controller.

[0130] In this embodiment of the application, the forwarding device can send the congestion information detected by the target congestion signaling to the controller based on the service message and the congestion signaling configuration information, so that the controller can make corresponding decisions.

[0131] In this embodiment of the application, the forwarding device may send the congestion information detected by the target congestion signaling to the controller under the following circumstances:

[0132] (i) The congestion signaling configuration information includes at least the third indication information, which corresponds to the information that the service message contains a target congestion signaling, the target congestion signaling does not include a send-to-controller flag, and the third indication information indicates the information of sending congestion signaling detection. The forwarding device sends the congestion information detected by the target congestion signaling to the controller.

[0133] In the above-mentioned optional implementations, the congestion signaling configuration information includes at least third indication information (isNotify). If it is determined that the service message encapsulates target congestion signaling, the target congestion signaling does not include the send-to-controller flag (U), and the third indication information indicates information for sending congestion signaling detection, the forwarding device can send the congestion information detected by the target congestion signaling to the controller.

[0134] It is important to note that the third indication information (isNotify) is stored in the congestion signaling configuration information and configured on the node (forwarding device) to determine whether the current node is a node that sends data to the controller. The send-to-controller flag (U) is stored in the congestion signaling and forwarded with the service message to determine whether the message needs to send the collected information. In this embodiment, without the send-to-controller flag, all service messages carrying congestion signaling can be sent. Adding the send-to-controller flag optimizes the sent messages and allows the sender to mark only some messages for sending, increasing implementation flexibility.

[0135] (ii) The congestion signaling configuration information includes at least the third indication information. Corresponding to the information that the service message is encapsulated with target congestion signaling, the target congestion signaling includes a send-to-controller flag bit and the send-to-controller flag bit is a preset value, and the third indication information indicates that congestion signaling detection is sent, the forwarding device sends the congestion information detected by the target congestion signaling to the controller. The preset value indicates that the congestion information detected by the congestion signaling is sent to the controller.

[0136] In the above-mentioned optional implementation methods, the congestion signaling configuration information includes at least a third indication information (isNotify). When the target congestion signaling is encapsulated in the service message, and the target congestion signaling includes a send-to-controller flag bit with a preset value (U is 1), and the third indication information indicates the information detected by the congestion signaling to be sent (isNotify is 1), the forwarding device sends the congestion information detected by the target congestion signaling to the controller. That is, when the current node (forwarding device) is the node that sends to the controller and the U flag bit is 1, the sending operation is performed.

[0137] (iii) In accordance with the determination that the service message contains a target congestion signaling, the target congestion signaling does not include a send-to-controller flag, and the determination that the forwarding device needs to strip the target congestion signaling encapsulated in the service message, the forwarding device sends the congestion information detected by the target congestion signaling to the controller.

[0138] In the above optional implementations, if it is determined that the service message encapsulates a target congestion signaling, the target congestion signaling does not include a send-to-controller flag, and the forwarding device determines that the target congestion signaling encapsulated in the service message needs to be stripped, the forwarding device sends the congestion information detected by the target congestion signaling to the controller. That is, the current node has received the target congestion signaling and is the stripping node. Although the target congestion signaling does not include a send-to-controller flag, the sending operation still needs to be performed to avoid the controller failing to receive the congestion information detected by the target congestion signaling. In practice, there are two situations requiring stripping: one is when the message reaches its destination normally, i.e., the destination host; the other is when subsequent nodes do not support CSIG resolution and are configured for stripping.

[0139] (iv) In accordance with the determination that the service message contains a target congestion signaling, the target congestion signaling includes a send-to-controller flag bit and the send-to-controller flag bit is a preset value, and the forwarding device determines that the target congestion signaling encapsulated in the service message needs to be stripped, the forwarding device sends the congestion information detected by the target congestion signaling to the controller, wherein the preset value indicates that the congestion information detected by the congestion signaling is sent to the controller.

[0140] In the above-mentioned optional implementation methods, when it is determined that the service message contains target congestion signaling and the target congestion signaling includes a send-to-controller flag bit with a preset value, and the forwarding device determines that the target congestion signaling encapsulated in the service message needs to be stripped, the forwarding device can send the congestion information detected by the target congestion signaling to the controller. That is, when U is 1 (preset value) and the forwarding device is a stripping node, the uploading operation can be performed.

[0141] In one or more alternative implementations, the congestion information detected by the forwarding device and sent to the controller by the target congestion signaling may include at least one of the following:

[0142] 1) When the forwarding device determines that the information detected by the target congestion signaling has been updated, it sends the congestion information detected by the target congestion signaling to the controller. In this implementation, the forwarding device can send the congestion information detected by the target congestion signaling to the controller when it determines that the information detected by the target congestion signaling has been updated. In practice, if the newly collected data is compared with the data in the congestion information table stored by the sending node and there is no deterioration, it can be left unsent, thereby avoiding frequent sending.

[0143] 2) The forwarding device sends the congestion information detected by the target congestion signaling to the controller after a preset time interval. In this implementation, the forwarding device sends the congestion information detected by the target congestion signaling to the controller after a preset time interval. The preset time interval can be determined according to the actual situation. This embodiment of the application does not impose a specific limitation, and frequent sending can also be avoided.

[0144] It should be noted that the congestion information entries stored in the uplink node are only related to the topology and not to the service flow, and the entries are not large. Therefore, the forwarding device does not bear much pressure, and the controller does not bear much pressure when receiving uplink data packets.

[0145] In this embodiment, when the service packets and congestion signaling configuration information obtained by the forwarding device meet certain conditions, the congestion information detected by the target congestion signaling can be sent to the controller. By controlling the forwarding device to send the congestion information detected by the congestion signaling to the controller, the processing load of the controller can be reduced, which is beneficial to saving resources and improving the working efficiency of the controller.

[0146] Example 5

[0147] In this embodiment of the application, the controller configures congestion signaling configuration information for each forwarding device in the network.

[0148] like Figure 8 As shown in the figure, this application embodiment provides a congestion signaling configuration method, executed by the controller side, the method including:

[0149] S801: For the target service, the controller determines the congestion signaling configuration information of the forwarding device.

[0150] The congestion signaling configuration information is used to instruct the forwarding device on the configuration parameters for handling the congestion signaling of the target service.

[0151] In this embodiment of the application, for a target service, the controller can determine the congestion signaling configuration information of the forwarding device. The congestion signaling configuration information is used to instruct the forwarding device on the configuration parameters for handling the congestion signaling of the target service.

[0152] In one optional implementation, the congestion signaling configuration information includes at least one of the following:

[0153] 1) First indication information, used to indicate whether the forwarding device initiates congestion signaling as the starting point;

[0154] 2) Second indication information, used to indicate whether the forwarding device modifies the congestion signaling uploading controller flag;

[0155] 3) Third indication information, used to indicate whether the forwarding device should send congestion signaling detection information;

[0156] 4) The service type and initial value of congestion signaling detection.

[0157] In this embodiment of the application, the congestion signaling configuration information of the forwarding device determined by the controller may include first indication information (isOrigin), which is used to indicate whether the forwarding device initiates congestion signaling as the starting point. That is, the controller can configure whether the forwarding device enables the CSIG first node behavior for a certain service (which can be identified by serviceID). If so (isOrigin is the first preset value, for example, 1), it is also necessary to configure which information types (T) to be probed and their initial values ​​(S). The current information types T are (0: minimum available bandwidth, 1: minimum available bandwidth percentage, 2: maximum processing latency), which may be expanded in the future.

[0158] Optionally, the congestion signaling configuration information may include a second indication information (isModify), which is used to indicate whether the forwarding device modifies the congestion signaling uploading controller flag. The controller can configure the forwarding device to enable the modification of the CSIG signaling uploading controller flag (U) for a certain service (identified by serviceID). If so (isModify is a second preset value, such as 1), the corresponding serviceID's isModify configuration information can be sent.

[0159] Optionally, the congestion signaling configuration information may include a third indication information (isNotify), which is used to indicate whether the forwarding device should send congestion signaling probe information. Typically, for network edge nodes or end nodes of CSIG signaling transmission, the configuration determines whether to send CSIG signaling probe information to the controller for a certain service (identified by serviceID). If so (isNotify is a third preset value, such as 1), the isNotify configuration information corresponding to the serviceID can be sent.

[0160] S802: The controller sends the target configuration to the forwarding device.

[0161] The target configuration includes the identification information of the target service and the congestion signaling configuration information corresponding to the target service.

[0162] In this embodiment of the application, the controller can send a target configuration to the forwarding device, wherein the target configuration includes the identification information of the target service (e.g., serviceID) and the congestion signaling configuration information (isOrigin, isModify, etc.) corresponding to the target service.

[0163] In this embodiment, for a target service, the controller can determine the congestion signaling configuration information of the forwarding device, and then send a target configuration including the identification information of the target service and the congestion signaling configuration information corresponding to the target service to the forwarding device, so that the forwarding device can perform corresponding optimization operations based on the congestion signaling configuration information, which helps the network to perform traffic control at the edge.

[0164] Example 6

[0165] In this embodiment of the application, the congestion signaling configuration information includes the aforementioned first indication information, second indication information, third indication information, and the service type and initial value of the congestion signaling detection. Furthermore, the congestion signaling includes a flag bit sent to the controller.

[0166] like Figure 9 As shown, the congestion signaling processing method provided in this application mainly includes the following steps:

[0167] Step 901: The forwarding device receives the service message.

[0168] Step 902: Perform CSIG configuration check and serviceID check (note that the forwarding device here includes the host and network forwarding node), and determine whether the serviceID can be matched (note that the serviceID can be a wildcard). If the serviceID does not match, it means that this service does not need to be measured by CSIG, and the process ends; if the serviceID matches, proceed to step 903.

[0169] Step 903: Check if the message has CSIG encapsulation. If there is no CSIG encapsulation, proceed to step 904. If there is CSIG encapsulation, proceed to step 906.

[0170] Step 904: Check if isOrigin is 1 (if it is 1, it means that this node is configured as the initiator of CSIG signaling for this service); if it is not, end the process, indicating that this node does not need additional processing; if it is, proceed to step 905.

[0171] Step 905: Encapsulate this service message with CSIG according to the format provided in the embodiments of this application ( Figure 4A or Figure 4B Set the U flag to 1 (U is the send controller flag), and the initial encapsulation information type and initial information value are determined by the information type (T) and initial value (S) configured from the control plane above; after encapsulation is completed, send the message and end the processing.

[0172] Step 906: Since the service has already encapsulated CSIG signaling, we can determine whether isModify is 1 (if it is 1, it means that this node is configured to modify the CSIG signaling encapsulation of this service); if yes, proceed to step 907; if no, proceed to step 909.

[0173] Step 907: Check if the U flag bit in the CSIG package is 1. If not, proceed to step 908; if yes, proceed to step 909.

[0174] Step 908: Modify the U flag of CSIG to 1 according to the above format. Continue sending and end processing.

[0175] Step 909: Check if isNotify is 1 (if it is 1, it means that this node is configured to send to the controller); if it is not, proceed to step 910; if it is, proceed to step 911.

[0176] Step 910: Check if CSIG signaling needs to be stripped. If yes, proceed to step 911; otherwise, end the process.

[0177] In the embodiments of this application, the stripping operation can be determined in the following two situations: one is that the destination is reached normally, that is, the destination host; the other is that the subsequent node does not support CSIG resolution and is configured to perform a stripping operation.

[0178] Step 911: Check if the U flag in the CSIG message is 1. If it is not 1, end the process. If it is 1, proceed to step 912.

[0179] Step 912: Send the information collected by CSIG to the controller.

[0180] Through the technical solutions provided in this application, network operators can proactively initiate CSIG measurements and collect congestion information from CSIG measurements through control. Various forwarding devices on the network side can take corresponding optimization measures. In addition, when there are nodes in the network that do not support CSIG, the information from the previous measurements can be sent to the controller before being stripped away, so as not to lose the information from the previous measurements.

[0181] Example 7

[0182] End-to-end collaboration refers to the collaborative allocation of computing resources and tasks between the cloud and terminal devices in the context of distributed computing and edge computing, enabling more efficient computing and data processing. This application's embodiments illustrate the interaction flow between the controller, forwarding plane, and host.

[0183] like Figure 10 As shown, the implementation process of this application embodiment mainly includes the following steps:

[0184] 1. Host 1 issues a CSIG signaling message;

[0185] 2. The forwarding plane performs CSIG signaling processing, which can be carried out using the solutions described in the above embodiments;

[0186] 3. Forward the CSIG information report to the controller; the controller receives the information collected by CSIG.

[0187] 4. Upon receiving the CSIG, host 2 sends the CSIG message back to host 1.

[0188] 5. Host 1 can adjust the transmission rate;

[0189] 6. The controller optimizes service paths and scheduling strategies based on CSIG information;

[0190] 7. The controller distributes the new forwarding policy to the forwarding plane;

[0191] 8. Adjust the forwarding strategy.

[0192] In this way, during the next round of CSIG information measurement, because both sides take action, the path will be improved, and the transmission rate can be restored more quickly.

[0193] It should be noted that the above processing steps are not in a strict order, and appropriate actions can be taken based on the actual situation.

[0194] In the following embodiments, specific examples are used to illustrate the technical solutions provided in the embodiments of this application.

[0195] Example 8

[0196] In the embodiments of this application, the following methods can be used: Figure 11 The network structure shown is for reference. Figure 11 The implementation process of this embodiment is as follows.

[0197] 1. The controller sends the following configuration to node ToR1:

[0198] Service ID: Source IP: 10.168.1.1, Destination IP: 10.168.10.1;

[0199] isOrigin: 1

[0200] Information type (T): 0; Corresponding initial value (S): 20G

[0201] Information type (T): 1; Corresponding initial value (S): 20%

[0202] ToR1 internally forms a configuration table, as shown in Table 5:

[0203] Table 5

[0204]

[0205]

[0206] 2. The controller sends the following configuration to node ToR2:

[0207] Service ID: Source IP: *, Destination IP: 10.168.10.1;

[0208] isNotify: 1

[0209] ToR2 internally generates a configuration table, as shown in Table 6:

[0210] Table 6

[0211]

[0212] The forwarding process is as follows:

[0213] (1) ToR1 receives a message from host 1 to host 2 and matches it with Table 5. It finds that the serviceID is matched.

[0214] (2) Upon checking the message encapsulation, it was found that CSIG signaling was not encapsulated;

[0215] (3) The check found that the isOrigin corresponding to this serviceID is 1, indicating that CSIG encapsulation is required;

[0216] (4) Encapsulate CSIG and the corresponding T / S information according to the format provided in the embodiments of this application;

[0217] (5) There are no restrictions on the method of encapsulating CSIG. Several CSIG signaling messages with T=0 can be encapsulated first, and then CSIG signaling messages with T=1 can be encapsulated. There are no restrictions on the interleaving method. CSIG signaling can also be stopped according to certain strategies.

[0218] (6) When encapsulating CSIG signaling with T=0, the internal S is filled with 20G; when encapsulating CSIG signaling with T=1, the internal S is filled with 20%.

[0219] (7) When the CSIG signaling with T=0 is propagated downstream, it can be seen that the available bandwidth of Aggr2 is 15G, which is lower than the 20G carried in the message. At this time, Aggr2 will update the message content, change S to 15G, and fill in the local node identifier and port identifier in the CSIG signaling.

[0220] (8) When the message modified by Aggr2 arrives at ToR2, it is matched with Table 6 and found to match the serviceID;

[0221] (9) The check found that the isNotify corresponding to this serviceID is 1, and the U flag of the CSIG message is 1. It was also found that the content has been updated. The measurement content in CSIG is sent to the controller.

[0222] (10) When host 2 receives the message, there are several possibilities because CSIG needs to be stripped:

[0223] In the first case, if U-mark recognition is not supported, proceed as usual.

[0224] In the second scenario, U-mark recognition is supported, but the controller address is not configured or the controller cannot manage it; in this case, it is handled in the usual way.

[0225] The third scenario supports U-mark recognition and is also configured to send information collected by CSIG to the controller.

[0226] (11) When the encapsulated CSIG signaling with T=1 is propagated downstream, the available bandwidth of Core1 is 50 / 400=12.5%, which is lower than the initial 20%. At this time, Core1 will update the message content, change S to 12.5%, and fill in the local node identifier and port identifier into the CSIG signaling.

[0227] (12) When the message modified by Core1 arrives at ToR2, it is matched with Table 6 and a serviceID is found.

[0228] (13) The check found that the isNotify corresponding to this serviceID is 1, and the U flag of the CSIG message is 1. It was also found that the content has been updated. The measurement content in CSIG is sent to the controller.

[0229] (14) When host 2 receives the message, it needs to strip CSIG and is processed as described in (10).

[0230] Example 9

[0231] Figure 12 The network structure of this application embodiment is shown, with reference to Figure 12 The implementation process of this embodiment is as follows.

[0232] 1. The controller sends the following configuration to node ToR1:

[0233] Service ID: Source IP: 10.168.1.1, Destination IP: 10.168.10.1;

[0234] isModify: 1

[0235] ToR1 internally forms a configuration table, as shown in Table 7:

[0236] Table 7

[0237]

[0238] 2. The controller sends the following configuration to node ToR2:

[0239] Service ID: Source IP: *, Destination IP: 10.168.10.1;

[0240] isNotify: 1

[0241] ToR2 internally generates a configuration table, as shown in Table 8:

[0242] Table 8

[0243]

[0244] The forwarding process is as follows:

[0245] (1) ToR1 receives a message from host 1 to host 2, matches it with Table 7, and finds that it matches the serviceID.

[0246] (2) Upon checking the message encapsulation, it was found that CSIG signaling had been encapsulated;

[0247] (3) The inspection found that the U flag in the CSIG signaling was not 1, and the isModify corresponding to this serviceID was 1, indicating that CSIG needs to be modified;

[0248] (4) Set the U flag of CSIG to 1 according to the format provided in the embodiments of this application;

[0249] (5) For example, in a CSIG signaling where T is 1, the internal S is filled with 20%;

[0250] (6) When this message arrives at Core1, the available bandwidth of Core1 is 50 / 400 = 12.5%, which is lower than the initial 20%. At this time, Core1 will update the message content, change S to 12.5%, and fill in the local node identifier and port identifier in the CSIG signaling.

[0251] (7) When the message modified by Core1 arrives at Aggr2, Aggr2 needs to strip the CSIG signaling because the ToR2 node does not support CSIG signaling;

[0252] (8) Aggr2 finds that the U flag of the CSIG message is 1 and that the content has been updated. It then sends the measurement content in the CSIG message to the controller and strips the CSIG signaling.

[0253] (9) When host 2 receives a message, it will be processed as a normal message since there is no CSIG signaling in the message.

[0254] In the technical solution provided by the embodiments of this application, not only can the host initiate CSIG detection (such as...) Figure 13 As shown in line 1), edge nodes can also initiate CSIG detection (e.g., ...). Figure 13 As shown in line 2), and moreover, the CSIG message sent by the host can be modified at edge nodes or intermediate nodes (e.g., Figure 13 As shown in line 3, it indicates that CSIG information can be sent to the controller; at the same time, CSIG information can be sent to the CSIG stripping node, edge node, and host (e.g., Figure 13 (As shown in lines 4 / 5 / 6).

[0255] Figure 14This diagram illustrates the interaction between the controller and the forwarding plane node (i.e., the forwarding device) according to an embodiment of this application. The system includes the forwarding plane node (forwarding device) and the controller. The controller can configure the forwarding plane node via netconf, RESTful, or a private protocol, specifying whether to perform congestion signaling configuration for a specific service (serviceID): whether to initiate CSIG signaling as the starting point (isOrigin); whether to modify the CSIG signaling's upload flag to the controller (isModify), with the upload flag set to U; whether to upload CSIG signaling probe information to the controller (isNotify); and when acting as the signaling initiation point, the service type (T) and initial value (S) to be probed. The forwarding plane node can upload the congestion information (T, S, L, M) detected by CSIG signaling to the controller according to the configuration via netconf or a private protocol.

[0256] Optionally, such as Figure 15 As shown in the figure, this application embodiment also provides an electronic device 1500, including a processor 1501 and a memory 1502, wherein the memory 1502 stores a program or instructions that can run on the processor 1501.

[0257] In one implementation, when the program or instruction is executed by the processor 1501, it implements each step of the above-described congestion signaling processing method and achieves the same technical effect. To avoid repetition, it will not be described again here.

[0258] In other words, the electronic device can act as the aforementioned forwarding device and execute the aforementioned congestion signaling processing method.

[0259] In another implementation, when the program or instruction is executed by the processor 1601, it implements the various steps of the above-described congestion signaling configuration method and achieves the same technical effect. To avoid repetition, it will not be described again here.

[0260] In other words, the electronic device can act as the controller described above and execute the congestion signaling configuration method described above.

[0261] In an exemplary embodiment of this application, a computer-readable storage medium is also provided, which stores at least one computer program. This computer program is loaded and executed by a processor to implement all or part of the steps in the congestion signaling processing method or congestion signaling configuration method described above. For example, the computer-readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a compact disc read-only memory (CD-ROM), magnetic tape, floppy disk, or optical data storage device, etc.

[0262] In an exemplary embodiment of this application, a computer program product is also provided, which includes at least one computer program that is loaded by a processor and executes all or part of the steps of the congestion signaling processing method or congestion signaling configuration method shown in the above embodiments.

[0263] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this application are indicated by the claims.

[0264] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is limited only by the appended claims.

Claims

1. A method of congestion signaling processing, the method comprising: The method comprises the following steps: The forwarding device receives a service packet; The forwarding device acquires congestion signaling configuration information matched with the service packet, wherein the congestion signaling configuration information is used to indicate configuration parameters for processing congestion signaling; The forwarding device performs corresponding congestion signaling processing on the service packet based on the congestion signaling configuration information.

2. The method of claim 1, wherein, Before the forwarding device acquires the congestion signaling configuration information matched with the service packet, the method further comprises the following steps: The forwarding device receives target configuration, wherein the target configuration comprises service identification information of at least one service and the congestion signaling configuration information corresponding to each of the at least one service.

3. The method of claim 2, wherein, The forwarding device acquires the congestion signaling configuration information matched with the service packet, comprising the following steps: The forwarding device searches for service identification information matched with service identification of the service packet from the target configuration; The forwarding device acquires the congestion signaling configuration information corresponding to the searched service identification information from the target configuration.

4. The method of claim 1, wherein, The congestion signaling comprises a controller upload flag, which is used to indicate whether the service packet is a packet for uploading congestion signaling detection information to the controller.

5. The method according to any one of claims 1 to 4, characterized in that, The congestion signaling configuration information comprises at least one of the following: First indication information, which is used to indicate whether the forwarding device initiates congestion signaling as a starting point; Second indication information, which is used to indicate whether the forwarding device modifies the controller upload flag of congestion signaling; Third indication information, which is used to indicate whether the forwarding device uploads congestion signaling detection information; Service type and initial value of congestion signaling detection.

6. The method of claim 5, wherein, The congestion signaling configuration information at least comprises the first indication information, and the forwarding device performs corresponding congestion signaling processing on the service packet based on the congestion signaling configuration information, comprising the following steps: When it is determined that the service packet does not encapsulate congestion signaling and the first indication information indicates that congestion signaling is initiated as a starting point, the forwarding device encapsulates target congestion signaling for the service packet; The forwarding device sends the service packet encapsulating the target congestion signaling.

7. The method of claim 6, wherein, The forwarding device encapsulates target congestion signaling for the service packet, comprising the following steps: The forwarding device sets information type and initial value of the target congestion signaling to service type and initial value in the congestion signaling configuration information.

8. The method of claim 7, wherein, The target congestion signaling comprises a controller upload flag; and the forwarding device encapsulates target congestion signaling for the service packet, further comprising the following steps: The forwarding device sets the controller upload flag in the target congestion signaling to a preset value, wherein the preset value indicates that the service packet is a packet for uploading congestion signaling detection information to the controller.

9. The method of claim 5, wherein, The congestion signaling configuration information at least comprises the second indication information, and the forwarding device performs corresponding congestion signaling processing on the service packet based on the congestion signaling configuration information, comprising the following steps: corresponding to a determination that the service packet encapsulates target congestion signaling, the second indication information indicates that the modified congestion signaling is to be sent to the controller, and a sending controller flag bit in the target congestion signaling is not the preset value, the forwarding device sets the sending controller flag bit in the target congestion signaling to the preset value, where the preset value indicates that the service packet is a packet for sending congestion signaling detection information to the controller; the forwarding device sends the service packet encapsulating the modified target congestion signaling.

10. The method of claim 5, wherein, The congestion signaling configuration information at least includes the third indication information, and the forwarding device performs corresponding congestion signaling processing on the service packet based on the congestion signaling configuration information, including: determining that the service packet encapsulates target congestion signaling, the target congestion signaling does not include a sending controller flag bit, and the third indication information indicates that congestion signaling detection information is to be sent to the controller, the forwarding device sends congestion information detected by the target congestion signaling to the controller.

11. The method of claim 5, wherein, The congestion signaling configuration information at least includes the third indication information, and the forwarding device performs corresponding congestion signaling processing on the service packet based on the congestion signaling configuration information, including: corresponding to a determination that the service packet encapsulates target congestion signaling, the target congestion signaling includes a sending controller flag bit, the sending controller flag bit is the preset value, and the third indication information indicates that congestion signaling detection information is to be sent to the controller, the forwarding device sends congestion information detected by the target congestion signaling to the controller, where the preset value indicates that congestion signaling detection information is to be sent to the controller.

12. The method according to any one of claims 1 to 4, characterized in that, The forwarding device performs corresponding congestion signaling processing on the service packet based on the congestion signaling configuration information, including: corresponding to a determination that the service packet encapsulates target congestion signaling, the target congestion signaling does not include a sending controller flag bit, and the forwarding device determines that the target congestion signaling encapsulated in the service packet needs to be stripped, the forwarding device sends congestion information detected by the target congestion signaling to the controller.

13. The method according to any one of claims 1 to 4, characterized in that, The forwarding device performs corresponding congestion signaling processing on the service packet based on the congestion signaling configuration information, including: corresponding to a determination that the service packet encapsulates target congestion signaling, the target congestion signaling includes a sending controller flag bit, the sending controller flag bit is the preset value, and the forwarding device determines that the target congestion signaling encapsulated in the service packet needs to be stripped, the forwarding device sends congestion information detected by the target congestion signaling to the controller, where the preset value indicates that congestion signaling detection information is to be sent to the controller.

14. The method of claim 10 or 11, wherein, The forwarding device sends the congestion information detected by the target congestion signaling to the controller, including at least one of the following: the forwarding device sends the congestion information detected by the target congestion signaling to the controller in a case where it is determined that the information detected by the target congestion signaling is updated; The forwarding device uploads congestion information detected by the target congestion signaling to the controller after a preset time interval.

15. A method of configuring congestion signaling, the method comprising: Comprise: For a target service, a controller determines congestion signaling configuration information of a forwarding device, wherein the congestion signaling configuration information is used to indicate configuration parameters of the forwarding device for processing congestion signaling of the target service; The controller sends target configuration to the forwarding device, wherein the target configuration includes identification information of the target service and the congestion signaling configuration information corresponding to the target service.

16. The method of claim 15, wherein, The congestion signaling configuration information includes at least one of the following: First indication information, used to indicate whether the forwarding device initiates congestion signaling as a starting point; Second indication information, used to indicate whether the forwarding device modifies the upload controller flag bit of congestion signaling; Third indication information, used to indicate whether the forwarding device uploads information detected by congestion signaling; Service type and initial value of congestion signaling detection.

17. A forwarding device, characterized in that, The forwarding device comprises a processor and a memory, the memory stores programs or instructions executable on the processor, and the programs or instructions are executed by the processor to implement the steps of the congestion signaling processing method according to any one of claims 1 to 14.

18. A controller characterized by comprising: The controller comprises a processor and a memory, the memory stores programs or instructions executable on the processor, and the programs or instructions are executed by the processor to implement the steps of the congestion signaling configuration method according to claim 15 or 16.

19. A readable storage medium, characterized by, The readable storage medium stores programs or instructions, and the programs or instructions are executed by the processor to implement the method according to any one of claims 1 to 16.

20. A computer program product, comprising a computer program stored on a non-transitory computer-readable storage medium, the computer program comprising program instructions that, when executed by a computer, cause the computer to perform the steps of the method according to any one of claims 1 to 16.

Images