Signal transmission method and device, equipment, storage medium and program product

Abstract

The invention discloses a signal transmission method, device and equipment, a storage medium and a program product, relates to the technical field of communication, and is used for reducing the cost of PFC (Power Factor Correction) back voltage signal cross-wide area network transmission. The method is applied to first network equipment, and comprises the following steps: acquiring a pre-defined segment identifier in a domain, the segment identifier being used for identifying an equipment interface supporting a priority-based flow control technology, and the segment identifier supporting intra-domain flooding through an internal gateway protocol; a first back pressure signal is sent to the second network device based on a tunnel between a device interface of the first network device and a device interface of the second network device, the tunnel is created by the first network device or the controller based on a segment identifier, and the device interface of the first network device supports a priority-based flow control technology. The device interface of the second network device supports a priority-based flow control technology, the second network device is an upstream network device of the first network device, and the tunnel is used for bearing the back pressure signal.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a signal transmission method, apparatus, device, storage medium, and program product. Background Technology

[0002] With the development of communication technology and the continuous advancement of technologies such as intelligent computing, generative artificial intelligence (AI), and large-scale model training, cross-regional computing-computer collaboration and computing-storage collaboration scenarios have become new development directions, and scenarios such as inter-computation collaboration and remote storage-computation have received increasing attention. In traditional intelligent computing centers, within Remote Direct Memory Access over Converged Ethernet (ROCE) networks, Priority Flow Control (PFC) is a key technology used for lossless network flow control and congestion management. ROCE networks are a network technology within Internet Data Centers (IDCs). When transmitting across Wide Area Networks (WANs), signals need to be transmitted between different data centers, and how to transmit signals across WANs becomes a challenge. Currently, upgrading all WAN equipment enables the cross-WAN transmission of PFC backpressure signals.

[0003] However, upgrading all WAN equipment is costly and risky. Therefore, reducing the cost of transmitting PFC backvoltage signals across WANs has become an urgent problem to be solved. Summary of the Invention

[0004] This application provides a signal transmission method, apparatus, device, storage medium, and program product for reducing the cost of transmitting PFC reverse voltage signals across wide area networks.

[0005] To achieve the above objectives, this application adopts the following technical solution:

[0006] In a first aspect, a signal transmission method is provided, applied to a first network device. The method includes: obtaining a predefined segment identifier within a domain, the segment identifier being used to identify a device interface supporting priority-based flow control technology, and the segment identifier supporting flooding within the domain via an interior gateway protocol; sending a first backpressure signal to a second network device based on a tunnel between the device interfaces of the first network device and the device interfaces of a second network device, the tunnel being created by the first network device or a controller based on the segment identifier, the device interface of the first network device supporting priority-based flow control technology, the device interface of the second network device supporting priority-based flow control technology, the second network device being an upstream network device of the first network device, and the tunnel being used to carry the backpressure signal.

[0007] In one possible implementation, before sending the first backpressure signal to the second network device based on the tunnel between the device interfaces of the first network device and the second network device, the method further includes: acquiring a second backpressure signal from the next-hop network device of the first network device; and sending the first backpressure signal to the second network device based on the tunnel between the device interfaces of the first network device and the second network device, including: if the first network device acquires the second backpressure signal, sending the first backpressure signal to the second network device based on the tunnel between the device interfaces of the first network device and the second network device.

[0008] In one possible implementation, before sending the first backpressure signal to the second network device based on the tunnel between the device interfaces of the first network device and the second network device, the method further includes: receiving a third backpressure signal from a fourth network device based on the tunnel between the device interfaces of the first network device and the fourth network device, wherein the fourth network device is a downstream network device of the first network device and the device interface of the fourth network device supports priority-based flow control technology; sending the first backpressure signal to the second network device based on the tunnel between the device interfaces of the first network device and the second network device includes: if the first network device receives the third backpressure signal, sending the first backpressure signal to the second network device based on the tunnel between the device interfaces of the first network device and the second network device.

[0009] In one possible implementation, sending a first backpressure signal to the second network device based on the tunnel between the device interfaces of the first network device and the second network device includes: parsing the third backpressure signal to obtain the destination address of the third backpressure signal; and if the destination address of the third backpressure signal is the first network device, sending the first backpressure signal to the second network device based on the tunnel between the device interfaces of the first network device and the second network device.

[0010] In one possible implementation, the method further includes reporting the segment identifier to the controller via the link status of the border gateway protocol.

[0011] In one possible implementation, at least one third network device is connected between the first network device and the second network device, and the at least one third network device includes a network device that does not support priority-based flow control technology.

[0012] In one possible implementation, device interfaces that support priority-based flow control technology are allowed to deploy group-level slices.

[0013] Secondly, a signal transmission method is provided, applied to a second network device; the method includes: receiving a first backpressure signal from the first network device based on a tunnel between the device interfaces of the first network device and the second network device, wherein the tunnel is created by the first network device or a controller based on a predefined segment identifier within the domain, the segment identifier is used to identify a device interface that supports priority-based flow control technology, the second network device is an upstream network device of the first network device, the device interface of the first network device supports priority-based flow control technology, the device interface of the second network device supports priority-based flow control technology, the segment identifier supports flooding within the domain via an interior gateway protocol, and the tunnel is used to carry the backpressure signal.

[0014] In one possible implementation, the first backpressure signal is sent by the first network device to the second network device after the first network device receives a second backpressure signal from the next-hop network device of the first network device.

[0015] In one possible implementation, the first backpressure signal is sent by the first network device to the second network device upon acquiring the third backpressure signal, and the third backpressure signal is sent by the fourth network device to the first network device based on the tunnel between the device interfaces of the first and fourth network devices. The fourth network device is a downstream network device of the first network device, and the device interface of the fourth network device supports priority-based flow control technology.

[0016] In one possible implementation, the first reverse pressure signal is sent to the second network device when the destination address of the third reverse pressure signal is the first network device, and the destination address of the third reverse pressure signal is obtained by parsing the third reverse pressure signal.

[0017] In one possible implementation, the method further includes reporting the segment identifier to the controller via the link status of the border gateway protocol.

[0018] In one possible implementation, at least one third network device is connected between the first network device and the second network device, and the at least one third network device includes a network device that does not support priority-based flow control technology.

[0019] In one possible implementation, device interfaces that support priority-based flow control technology are allowed to deploy group-level slices.

[0020] Thirdly, a signal transmission device is provided, applied to a first network device. The first network device includes a receiving unit and a transmitting unit. The receiving unit is used to acquire a predefined segment identifier within a domain. The segment identifier is used to identify a device interface that supports priority-based flow control technology, and the segment identifier supports flooding within the domain via an interior gateway protocol. The transmitting unit is used to send a first backpressure signal to a second network device based on a tunnel between the device interfaces of the first network device and the device interfaces of a second network device. The tunnel is created by the first network device or a controller based on the segment identifier. The device interfaces of the first network device and the second network device both support priority-based flow control technology. The second network device is an upstream network device of the first network device, and the tunnel is used to carry the backpressure signal.

[0021] In one possible implementation, the receiving unit is further configured to acquire a second backpressure signal from the next-hop network device of the first network device. The transmitting unit is further configured to, upon the first network device acquiring the second backpressure signal, transmit a first backpressure signal to the second network device based on the tunnel between the device interfaces of the first and second network devices.

[0022] In one possible implementation, the receiving unit is further configured to receive a third backpressure signal from a fourth network device via a tunnel between the device interfaces of the first network device and the fourth network device, wherein the fourth network device is a downstream network device of the first network device, and the device interface of the fourth network device supports priority-based flow control technology. The sending unit is further configured to, upon the first network device acquiring the third backpressure signal, send a first backpressure signal to the second network device via a tunnel between the device interfaces of the first network device and the second network device.

[0023] In one possible implementation, the sending unit is further configured to parse the third backpressure signal to obtain its destination address. If the destination address of the third backpressure signal is the first network device, the first backpressure signal is sent to the second network device based on the tunnel between the device interfaces of the first and second network devices.

[0024] In one possible implementation, the sending unit is also used to report the segment identifier to the controller via the link status of the border gateway protocol.

[0025] In one possible implementation, at least one third network device is connected between the first network device and the second network device, and the at least one third network device includes a network device that does not support priority-based flow control technology.

[0026] In one possible implementation, device interfaces that support priority-based flow control technology are allowed to deploy group-level slices.

[0027] Fourthly, a signal transmission device is provided, applied to a second network device; the signal transmission device includes: a receiving unit; the receiving unit is used to receive a first backpressure signal from the first network device based on a tunnel between the device interface of the first network device and the device interface of the second network device, the tunnel being created by the first network device or a controller based on a predefined segment identifier within a domain, the segment identifier being used to identify a device interface supporting priority-based flow control technology, the second network device being an upstream network device of the first network device, the device interface of the first network device supporting priority-based flow control technology, the device interface of the second network device supporting priority-based flow control technology, the segment identifier supporting flooding within a domain via an internal gateway protocol, and the tunnel being used to carry the backpressure signal.

[0028] In one possible implementation, the first backpressure signal is sent by the first network device to the second network device after the first network device receives a second backpressure signal from the next-hop network device of the first network device.

[0029] In one possible implementation, the first backpressure signal is sent by the first network device to the second network device upon acquiring the third backpressure signal, and the third backpressure signal is sent by the fourth network device to the first network device based on the tunnel between the device interfaces of the first and fourth network devices. The fourth network device is a downstream network device of the first network device, and the device interface of the fourth network device supports priority-based flow control technology.

[0030] In one possible implementation, the first reverse pressure signal is sent to the second network device when the destination address of the third reverse pressure signal is the first network device, and the destination address of the third reverse pressure signal is obtained by parsing the third reverse pressure signal.

[0031] In one possible implementation, the signal transmission device further includes: a transmitting unit; the transmitting unit is used to report segment identifiers to the controller via the link status of the border gateway protocol.

[0032] In one possible implementation, at least one third network device is connected between the first network device and the second network device, and the at least one third network device includes a network device that does not support priority-based flow control technology.

[0033] In one possible implementation, device interfaces that support priority-based flow control technology are allowed to deploy group-level slices.

[0034] Fifthly, an electronic device includes: a processor and a memory; wherein the memory is used to store one or more programs, the one or more programs including computer-executable instructions, and when the electronic device is running, the processor executes the computer-executable instructions stored in the memory to cause the electronic device to perform a signal transmission method as described in the first or second aspect.

[0035] A sixth aspect provides a computer-readable storage medium for storing one or more programs, the one or more programs including instructions that, when executed by a computer, cause the computer to perform a signal transmission method as described in the first or second aspect.

[0036] In a seventh aspect, a computer program product is provided, wherein when computer instructions are executed on an electronic device, the electronic device performs a signal transmission method as described in the first or second aspect.

[0037] This application provides a signal transmission method, apparatus, device, storage medium, and program product, applied in signal transmission scenarios. When signal transmission is required, a first network device obtains a predefined segment identifier within the domain to identify device interfaces supporting priority-based flow control (PFC). This segment identifier supports flooding within the domain via an interior gateway protocol. Further, based on a tunnel created by the first network device or controller based on the segment identifier between the device interfaces of the first and second network devices, a first backpressure signal is sent to the second network device. Both the first and second network devices support PFC, and the second network device is an upstream network device of the first network device. This tunnel carries the backpressure signal. In other words, the backpressure signal can be directly sent through a tunnel between two network devices supporting PFC, without needing to be forwarded by network devices connected between these two devices that do not support PFC. Thus, when transmitting across a wide area network (WAN), only some WAN devices need to be upgraded to support PFC, thereby reducing the cost of transmitting PFC backpressure signals across WANs. Attached Figure Description

[0038] Figure 1A schematic diagram of a signal transmission system provided for an embodiment of this application;

[0039] Figure 2 A flowchart illustrating a signal transmission method provided for embodiments of this application. Figure 1 ;

[0040] Figure 3 A schematic diagram illustrating an example of reverse pressure signal transmission across a wide area network, provided as an embodiment of this application;

[0041] Figure 4 A flowchart illustrating a signal transmission method provided for embodiments of this application. Figure 2 ;

[0042] Figure 5 A flowchart illustrating a signal transmission method provided for embodiments of this application. Figure 3 ;

[0043] Figure 6 A flowchart illustrating a signal transmission method provided for embodiments of this application. Figure 4 ;

[0044] Figure 7 A flowchart illustrating a signal transmission method provided for embodiments of this application. Figure 5 ;

[0045] Figure 8 A flowchart illustrating a signal transmission method provided for embodiments of this application. Figure 6 ;

[0046] Figure 9 A flowchart illustrating a signal transmission method provided for embodiments of this application. Figure 7 ;

[0047] Figure 10 A flowchart illustrating a signal transmission method provided for embodiments of this application. Figure 8 ;

[0048] Figure 11 A schematic diagram of the business processing flow of a controller solution provided for an embodiment of this application;

[0049] Figure 12 A schematic diagram illustrating an example of backpressure signal transmission across a wide area network for a controller scheme provided in an embodiment of this application;

[0050] Figure 13 A schematic diagram of a controllerless solution provided for an embodiment of this application;

[0051] Figure 14 A schematic diagram of the structure of a signal transmission device provided for embodiments of this application. Figure 1;

[0052] Figure 15 A schematic diagram of the structure of a signal transmission device provided for embodiments of this application. Figure 2 ;

[0053] Figure 16 This is a schematic diagram of the structure of an electronic device provided as an embodiment of this application. Detailed Implementation

[0054] The technical solutions in the embodiments of this application will now be described with reference to the accompanying drawings.

[0055] In the description of this application, unless otherwise stated, " / " means "or". For example, A / B can mean A or B. "And / or" in this document is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone. Furthermore, "at least one" and "multiple" refer to two or more. The terms "first," "second," etc., do not limit the quantity or order of execution, and "first," "second," etc., do not necessarily imply differences.

[0056] Wide area network (WAN) transmission based on the Remote Direct Memory Access (RDMA) protocol is a technology that has emerged in recent years. Its main technical methods are:

[0057] 1. The current mainstream solution is for WAN devices to support PFC technology. Since the traditional backpressure signal is transmitted hop by hop, it can also be called single-hop transmission. When deploying WAN tenant-level slicing scenarios, it is necessary to upgrade the entire WAN equipment, which is risky, very costly, and difficult to promote quickly.

[0058] 2. The message is converted into a Transmission Control Protocol (TCP) message via the RDMA protocol for transmission over a wide area network (WAN). Since TCP messages can be transmitted over a WAN, the Ethernet frame payload data of the ROCE protocol message can be directly transmitted over a WAN after being encapsulated into TCP messages, thus enabling the transmission of ROCE protocol message data over a WAN. However, this solution still results in a lossy WAN environment, lacks a backpressure mechanism and reliable bandwidth guarantee, leading to unstable transmission efficiency, especially in high-load, high-burst scenarios where transmission efficiency is extremely low.

[0059] To address the aforementioned issues, this application provides a signal transmission method. By using small-granular slicing and partially supporting PFC technology network devices, a new segment routing over Internet Protocol Version 6 (IPv6) segment identifier (SID) is defined. This SID primarily announces the PFC capability of device interfaces and allows network devices to flood the SRv6 SID within the domain via the Interior Gateway Protocol (IGP). Through either controller-issued SIDs or active creation by network devices, tunnels for transmitting backpressure signals are built between network devices supporting flow control technology within the WAN. This achieves efficient transmission of backpressure signals between data centers across the WAN without upgrading all WAN devices, requiring only the upgrade of a portion of them. This results in lossless cross-WAN transmission of backpressure signals, constructing a low-cost and easily deployable WAN bearer solution for cross-intelligent computing center services.

[0060] The signal transmission method provided in this application embodiment can be applied to signal transmission systems. Figure 1 A schematic diagram of a signal transmission system is shown. Figure 1 As shown, the signal transmission system includes a first network device 11, a second network device 12, and a third network device 13. The first network device 11, the second network device 12, and the third network device 13 can be connected via a wired or wireless connection; this embodiment of the invention does not limit the connection. The number of third network devices 13 is at least one; this disclosure does not limit the number of third network devices 13.

[0061] The first network device 11 is used to obtain a predefined segment identifier within the domain for identifying device interfaces supporting priority-based flow control technology. This segment identifier supports flooding within the domain via an interior gateway protocol. Further, based on the tunnel between the device interface of the first network device 11 and the device interface of the second network device 12, created by the first network device 11 or the controller based on the segment identifier, a first backpressure signal is sent to the second network device 12. Both the device interface of the first network device 11 and the device interface of the second network device 12 support priority-based flow control technology. The second network device 12 is an upstream network device of the first network device 11, and this tunnel is used to carry the backpressure signal.

[0062] At least one third network device 13 is connected between the first network device 11 and the second network device 12, and the at least one third network device 13 includes a network device that does not support priority-based flow control technology.

[0063] The first network device 11, the second network device 12, and the third network device 13 can be devices in a communication network, including: physical layer devices, data link layer devices, network layer devices, higher-layer and dedicated devices, etc. Among them, physical layer devices can be repeaters, hubs, etc. Data link layer devices can be bridges, switches, etc. Network layer devices can be routers, Layer 3 switches, etc. Higher-layer and dedicated devices can be gateways, firewalls, virtual private network (VPN) servers, etc. This disclosure does not limit these aspects.

[0064] It should be noted that, Figure 1 This is just an example framework diagram. Figure 1 The number of devices included and the names of each device are unlimited.

[0065] The following description, in conjunction with the accompanying drawings, describes a signal transmission method provided by an embodiment of this application. For example... Figure 2 As shown in the embodiment of this application, a signal transmission method is provided and applied to a first network device. The method includes S201:

[0066] S201. Obtain a predefined segment identifier within the domain. The segment identifier is used to identify device interfaces that support priority-based flow control technology.

[0067] Among them, the segment identifier supports flooding within the domain via the internal gateway protocol.

[0068] Optionally, since traditional PFC backpressure signals are transmitted hop-by-hop, meaning the PFC backpressure signal needs to be forwarded on every adjacent network device, to achieve cross-hop transmission, i.e., the PFC backpressure signal does not need to be forwarded on every adjacent network device, this disclosure needs to add the following function: defining the segment identifier of the network device's interface, namely End.X.PFC SID, which can also be called SRv6 SID, End.X.PFC, End.X.PFC tag, priority-based flow control SID in SRv6, etc. End.X.PFCSID is a new SRv6 SID type extended from the End SID type in related technologies: End.X.PFC. End.X.PFC SID is used to identify device interfaces that support PFC technology, and End.X.PFC SID supports flooding within the domain via the IGP protocol. At the same time, End.X.PFC SID supports reporting the PFC technology capabilities of the device interface to the controller.

[0069] End.X.PFC refers to an endpoint with L3 cross-connection and priority flow control, and is a variant of End. X SID carries additional meaning to facilitate the identification of interfaces in the network capable of handling PFC packets. Its primary purpose is to identify interfaces with PFC functionality in a wide area network. By publishing this information on the network, it makes it easier for other devices and controllers in the network to implement flow control policies.

[0070] It supports the device interface corresponding to the End.X.PFC SID to flood its own End.X.PFC SID within the domain. This allows network devices within the domain to notify each other of their End.X.PFC SIDs, facilitating the creation of tunnels later.

[0071] S202. Based on the tunnel between the device interface of the first network device and the device interface of the second network device, a first back pressure signal is sent to the second network device. The tunnel is created by the first network device or controller based on the segment identifier.

[0072] The first network device's interface supports priority-based flow control technology, and the second network device's interface also supports priority-based flow control technology. The second network device is an upstream network device of the first network device, and the tunnel is used to carry backpressure signals.

[0073] As can be understood, a backpressure signal is a signal sent by a downstream device to an upstream device when a data transmission anomaly occurs (such as network congestion), to notify the upstream device to stop sending service data to the downstream device. Backpressure signals can also be called backpressure messages, PFC backpressure signals, PFC backpressure messages, PFC flow control messages, PFC messages, backpressure frame messages, etc.

[0074] Optionally, this disclosure provides two methods for creating tunnels based on End.X.PFC SIDs. One method involves the network device itself creating the tunnel. The method of creating tunnels based on End.X.PFC SIDs by the network device itself is described below: After service traffic transmission begins between two data centers (IDCs), when the device interface of a network device supporting PFC technology connected between the two IDCs receives a service packet for the first time, the network device can check if a tunnel has been generated locally for that device interface. If so, it dynamically creates a tunnel. The destination address of the tunnel is obtained by parsing the segment routing header (SRH) of the service packet. This allows the segment identifier of the device interface supporting PFC technology within the domain to be obtained, and the device interface can be selected from among them to establish a tunnel.

[0075] The following describes the method for creating tunnels by the controller: After calculating the forward SRv6 policy tunnel, the controller searches for End.X.PFC in the segment-list of the SRH header, and establishes an SRv6 tunnel from the upstream PFC-enabled node to the network device that may transmit backpressure signals, based on the upstream and downstream relationships, to carry backpressure frame packets.

[0076] In one possible implementation, at least one third network device is connected between the first network device and the second network device, and the at least one third network device includes a network device that does not support priority-based flow control technology.

[0077] Optionally, the network device can find the nearest device interface from the segment identifiers of device interfaces supporting PFC technology within the domain and establish a tunnel with it. Then, the network devices connected between these two network devices are all network devices that do not support PFC technology; that is, each of at least one third network device between the first and second network devices is a network device that does not support PFC technology.

[0078] Optionally, it is assumed that the first, second, and third network devices are all network devices connecting two data centers (IDCs). The two IDCs and the network devices connecting them constitute a wide area network (WAN). All network devices within the WAN can be referred to as WAN devices. WAN devices can be categorized into two types: one type supports backpressure flow control, meaning its interface supports priority-based flow control technology; the other type does not support backpressure flow control, meaning its interface does not support priority-based flow control technology.

[0079] IDC can also be called a data center (DC) side, which can be an intelligent computing center or a ROCE network. A tunnel can also be called an SRv6 tunnel or a backpressure tunnel, etc.

[0080] In other words, backpressure signals can be sent directly through a tunnel between two network devices that support priority-based flow control technology, without having to be forwarded through a network device connected between these two network devices that does not support priority-based flow control technology. Thus, when transmitting across wide area networks, only some wide area network devices need to be upgraded to support priority-based flow control technology, thereby reducing the cost of transmitting PFC backpressure signals across wide area networks.

[0081] For example, such as Figure 3 As shown, assume that two data centers (IDC1 and IDC2) are connected to five WAN devices: device A, device B, device C, device D, and device E. Devices A, C, and E are all network devices supporting PFC technology, meaning their interfaces all support PFC. Devices B and D are network devices that do not support PFC technology, meaning their interfaces all support PFC. The data transmission direction is A->B->C->D->E. For example, when queue C is congested, if the backpressure signal can be transmitted to the corresponding interface of B in a timely manner, packet loss can be prevented. Therefore, a mechanism is needed to enable C to detect the closest upstream device and interface supporting backpressure signal processing for the current traffic.

[0082] In this way, device E can receive the backpressure signal from IDC2. Furthermore, device C can send a backpressure signal to device C through the tunnel between the device interfaces of device E and device C, provided the backpressure signal transmission conditions are met. Furthermore, device C can send a backpressure signal to device A through the tunnel between the device interfaces of device C and device A, provided the backpressure signal transmission conditions are met. Furthermore, device A can send a backpressure signal to IDC1, provided the backpressure signal transmission conditions are met. Thus, by upgrading only devices A, C, and E, transmission across IDC1 and IDC2 can be completed, achieving cross-WAN transmission.

[0083] In a design, such as Figure 4 As shown, the signal transmission method provided in this application embodiment further includes S301 before step S202, and the step S302 of "sending a first backpressure signal to the second network device based on the tunnel between the device interface of the first network device and the device interface of the second network device" specifically includes S302:

[0084] S301. Obtain the second back pressure signal from the next-hop network device of the first network device.

[0085] S302, when the first network device obtains the second back pressure signal, the first back pressure signal is sent to the second network device based on the tunnel between the device interface of the first network device and the device interface of the second network device.

[0086] Optionally, the next-hop network device of the first network device can be a device in the IDC. If the next-hop network device of the first network device experiences a data transmission anomaly, then that device can send a backpressure signal, i.e., a second backpressure signal, to the first network device.

[0087] Furthermore, when the first network device receives the backpressure signal, and if the first network device meets the conditions for transmitting the backpressure signal, the first network device can transmit the backpressure signal to the upstream remote device through a pre-set tunnel. That is, the first network device can send the first backpressure signal to the second network device based on the tunnel between the device interfaces of the first network device and the second network device. In this way, cross-hop transmission of the backpressure signal can be achieved when the upstream device of the WAN device is a device in the IDC.

[0088] For example, the first network device can be Figure 3 In the context of device E, the next-hop network device for the first network device can be a device in IDC2, and the second network device can be... Figure 3 Device C in the example. That is, when the interface between device E and IDC2 becomes congested, or when device E receives a backpressure signal from IDC2 and its buffer exceeds a set threshold, device E needs to transmit a backpressure signal to the upstream device.

[0089] The conditions for transmitting reverse voltage signals are described below.

[0090] Optionally, the condition for sending the backpressure signal can be that the network device's buffer exceeds a preset threshold (also known as a predetermined waterline). After receiving the backpressure signal, the first network device can continuously monitor its buffer. When the buffer exceeds the preset threshold, it transmits the backpressure signal to the upstream remote device through a pre-defined tunnel. This avoids the upstream device continuing to send signals to the network device when the network device's buffer is too large, thus preventing excessive network load and network congestion.

[0091] In a design, such as Figure 5As shown, the signal transmission method provided in this application embodiment further includes S401 before step S202, and the step S402 of "sending a first backpressure signal to the second network device based on the tunnel between the device interface of the first network device and the device interface of the second network device" specifically includes S402:

[0092] S401, Based on the tunnel between the device interface of the first network device and the device interface of the fourth network device, receive the third back pressure signal from the fourth network device.

[0093] The fourth network device is a downstream network device of the first network device, and the device interface of the fourth network device supports priority-based flow control technology.

[0094] S402, when the first network device obtains the third reverse pressure signal, the first reverse pressure signal is sent to the second network device based on the tunnel between the device interface of the first network device and the device interface of the second network device.

[0095] Optionally, the first, second, and fourth network devices are all devices connecting two IDCs. The first network device can receive a third backpressure signal from the fourth network device through a tunnel between its device interface and the fourth network device's device interface. Furthermore, upon receiving the backpressure signal, the first network device can enter a backpressure processing procedure if it meets the backpressure processing conditions. The backpressure processing procedure involves continuously monitoring the cache, also known as a cache queue, and transmitting the backpressure signal to the upstream remote device through a pre-defined tunnel when the cache exceeds a preset threshold. This enables hop-crossing transmission of the backpressure signal when all WAN devices are devices between IDCs.

[0096] For example, the first network device can be Figure 3 Device C in the middle, the second network device can be Figure 3 Device A in the middle, the fourth network device can be Figure 3 Device E in the middle.

[0097] The back pressure treatment conditions are described below.

[0098] In a design, such as Figure 6 As shown in the embodiment of this application, a signal transmission method is provided. Step S402, "sending a first backpressure signal to the second network device based on the tunnel between the device interface of the first network device and the device interface of the second network device," specifically includes steps S501-S502:

[0099] S501. Analyze the third reverse voltage signal to obtain the destination address of the third reverse voltage signal.

[0100] S502. When the destination address of the third reverse pressure signal is the first network device, the first reverse pressure signal is sent to the second network device based on the tunnel between the device interface of the first network device and the device interface of the second network device.

[0101] Optionally, the first network device can parse the packet encapsulation of the third backpressure signal to obtain its destination address. The destination address can be the destination Internet Protocol (IP) address. If the destination address of the third backpressure signal is the first network device, it indicates that the backpressure signal was transmitted correctly, and the first network device can enter the backpressure processing procedure. If the destination address of the third backpressure signal is not the first network device, it indicates that the backpressure signal was transmitted incorrectly, and the first network device will not enter the backpressure processing procedure. This ensures the correct transmission of the backpressure signal during hop transmission.

[0102] In one possible implementation, the steps for implementing the backpressure mechanism on devices within the domain that support PFC are as follows:

[0103] a. Devices that support PFC have multiple priority queues on the transmit interface and an equal number of receive buffers on the receive interface.

[0104] b. When the receive buffer on the downstream device (such as device C) becomes congested, that is, when the queue buffer is rapidly consumed and exceeds a certain threshold (such as 1 / 2 or 3 / 4 of the port queue buffer), that is, when the buffer exceeds the preset threshold, the corresponding mechanism will be triggered.

[0105] c. Device B detects congestion and sends a back pressure signal to the upstream device (Device B) in the data input direction.

[0106] d. Upon receiving the backpressure signal, the upstream device (Device B) stops sending data packets for the corresponding priority queue according to the signal indication and stores the data in its local interface buffer. If the consumption of Device B's local interface buffer also exceeds the threshold, it will continue to send backpressure signals to the upstream device (Device A).

[0107] e. When the congestion in the receive buffer is relieved, that is, when the used buffer of the queue is reduced to below the threshold, the receiving device (device B) will send a backpressure signal stop message to the upstream device (device A) to notify the upstream device to send data packets again and restore the traffic transmission of the corresponding priority queue.

[0108] The following describes the method for creating a tunnel based on the End.X.PFC SID by the controller.

[0109] In a design, such as Figure 7 As shown, an embodiment of this application provides a signal transmission method, which further includes step S701 before step S202:

[0110] S701. Report the segment identifier to the controller through the link status of the border gateway protocol.

[0111] Optionally, each network device within the domain can report the collected End.X.PFC SID of its device interface to the controller via Border Gateway Protocol-Link State (BGP-LS). Furthermore, the controller can create tunnels between two PFC-enabled device interfaces based on the End.X.PFC SIDs of all device interfaces within the domain.

[0112] In some embodiments, device interfaces that support priority-based flow control technologies are allowed to deploy group-level slices.

[0113] Optionally, network devices supporting PFC technology can enable small-granularity slicing, i.e., group-level slicing, to ensure dedicated network resources. When there is cross-datacenter data flow between two data centers, all WAN devices enable SRv6-based small-granularity slicing. When backpressure signals exist within a data center, these signals can be transmitted across hops within the WAN via tunnels. In other words, in a WAN scenario, physical links can simultaneously carry services from multiple tenants. To avoid traffic interference between different tenants, backpressure signals should support tenant-level granularity, which can be achieved using SRv6 and network slicing technologies. To prevent packet loss on devices that do not support PFC technology, tenant-level slicing can be used. Tenant-level slices can be deployed on SRv6-traversed interfaces to provide lossless guarantees.

[0114] Devices supporting backpressure flow control can also be called network devices supporting PFC technology, or devices supporting lossless flow control. Devices not supporting backpressure flow control can be called existing devices, which only need to support small-granularity slicing. This disclosure does not restrict the device interface; it can be a main interface, a slicing port, or a sub-interface.

[0115] In a design, such as Figure 8 As shown in the embodiment of this application, a signal transmission method is provided and applied to a second network device. The method includes S801:

[0116] S801, Based on the tunnel between the device interface of the first network device and the device interface of the second network device, receive a first back pressure signal from the first network device. The tunnel is created by the first network device or controller based on a predefined segment identifier within the domain. The segment identifier is used to identify the device interface that supports priority-based flow control technology.

[0117] The second network device is an upstream network device of the first network device. The device interface of the first network device supports priority-based flow control technology. The device interface of the second network device also supports priority-based flow control technology. The segment identifier supports flooding within the domain through the internal gateway protocol. The tunnel is used to carry backpressure signals.

[0118] For a description of the first network device, the second network device, the segment identifier, the tunnel, and the first backpressure signal, please refer to the above embodiments S201-S202, which will not be repeated here.

[0119] In some embodiments, the first backpressure signal is sent by the first network device to the second network device upon acquiring the third backpressure signal, the third backpressure signal is sent by the fourth network device to the first network device based on the tunnel between the device interface of the first network device and the device interface of the fourth network device, the fourth network device is a downstream network device of the first network device, and the device interface of the fourth network device supports priority-based flow control technology.

[0120] The description of the fourth network device and the third reverse voltage signal can be found in the above embodiments, and will not be repeated here.

[0121] In some embodiments, the first reverse pressure signal is sent to the second network device when the destination address of the third reverse pressure signal is the first network device, and the destination address of the third reverse pressure signal is obtained by parsing the third reverse pressure signal.

[0122] The destination address of the third reverse voltage signal can be referred to in the above embodiments, and will not be repeated here.

[0123] In a design, such as Figure 9 As shown, the signal transmission method provided in this application embodiment further includes step S901 before step S801:

[0124] S901. Report the segment identifier to the controller through the link status of the border gateway protocol.

[0125] In some embodiments, device interfaces that support priority-based flow control technologies are allowed to deploy group-level slices.

[0126] For an introduction to household-level slicing, please refer to the above embodiments, which will not be repeated here.

[0127] The following describes the signal transmission method provided in the above embodiments using the interaction between the first network device and the second network device as an example. Figure 10 As shown, it includes:

[0128] S1101. The first network device sends a first backpressure signal to the second network device through the tunnel between the device interfaces of the first and second network devices. Correspondingly, the second network device receives the first backpressure signal from the first network device through the tunnel between the device interfaces of the first and second network devices, thereby realizing the hop-crossing transmission of the backpressure signal.

[0129] The following describes the service processing flow of the signal transmission method provided in this disclosure, using two specific embodiments:

[0130] Example 1: The backpressure tunnel (i.e., the tunnel in this disclosure) is deployed by the controller, and the service processing flow is as follows: Figure 11 As shown:

[0131] S1. Devices supporting PFC technology generate an End.X.PFC SID for each device interface. For example... Figure 12 As shown, devices A, C, and E are devices that support PFC technology. Each device publishes a new type of SRv6 SID: End.X.PFC on the interface that interconnects with other devices (the interface is not limited and can be a main interface, a slice port, or a sub-interface).

[0132] S2. Devices supporting PFC technology flood End.X.PFC via IGP and report it to the controller. That is, devices supporting PFC technology flood the End.X.PFC interface via IGP and report the collected End.X.PFC via BGP-LS.

[0133] S3, the controller handles service delivery and routing for cross-DC services. Specifically, the controller delivers services to tenants across intelligent computing centers, including slice creation and SRv6 tunnel delivery.

[0134] S4. The controller pre-configures backpressure tunnels on devices that support PFC technology. This means that because the controller learns which device interfaces support backpressure flow control technology through the End.X.PFC tag, it can assign a backpressure tunnel to the previous hop device for each device interface that may receive a backpressure signal when issuing services.

[0135] After the controller distributes the on-demand slicing small particles, it pre-deploys a backpressure tunnel (i.e., an SRv6 tunnel) on devices supporting PFC technology. This backpressure tunnel points to the interface of the previous-hop device supporting PFC technology. Thus, upon receiving a backpressure signal from the next-hop device, it transmits the backpressure signal through the backpressure tunnel to the nearest previous-hop device supporting PFC technology. For example... Figure 12As shown, device A is labeled A.End.X.PFC, device C is labeled C.End.X.PFC, device E is labeled E.End.X.PFC, device B is labeled B.End.X, and device D is labeled D.End.X. The controller can deploy a backpressure tunnel on device C pointing to device A, and on device E pointing to device C. Specifically, the controller sends the slice ID and backpressure adjacency interface information (A.End.X.PFC) to device C, and sends the slice ID and backpressure adjacency interface information (C.End.X.PFC) to device E.

[0136] S5. When the device receives a backpressure message and the buffer queue exceeds the predetermined waterline, it constructs a new backpressure signal and encapsulates it into a pre-built backpressure tunnel, pointing it to the upstream device. That is, the backpressure signal is transmitted to the upstream remote device through the pre-built tunnel.

[0137] S6. After receiving the End.X.PFC SID, the upstream device enters the backpressure processing procedure. That is, when the upstream device receives the backpressure signal, it parses the packet encapsulation of the backpressure signal, finds that its destination IP is the local End.X.PFC SID, and enters the backpressure processing procedure.

[0138] Example 2: Deployment of a backpressure tunnel by network devices; the service processing flow is as follows. Figure 13 As shown:

[0139] S1. Devices supporting PFC technology generate an End.X.PFC SID for each device interface. For example... Figure 3 As shown, devices A, C, and E are devices that support PFC technology. Each device publishes a new type of SRv6 SID: End.X.PFC on the interface that interconnects with other devices (the interface is not limited and can be a main interface, a slice port, or a sub-interface).

[0140] S2. Devices supporting PFC technology flood End.X.PFC via IGP. End.X.PFC information for devices that will soon support PFC technology is flooded via IGP.

[0141] S3. The network head node performs path orchestration and routing. That is, the network head node in the physical link performs path orchestration and configures SRv6 tunnels.

[0142] S4. Upon receiving the first service packet, a device supporting PFC technology parses the packet to determine the nearest hop's End.X.PFC and creates a backpressure tunnel. That is, after service traffic begins, when an interface of a PFC-enabled device receives a service packet for the first time, it checks if a backpressure tunnel has been generated locally for that interface. If not, a backpressure tunnel is dynamically created. The destination address of the backpressure tunnel is obtained by parsing the nearest End.X.PFC in the SRH header.

[0143] S5. When a device supporting PFC technology receives a backpressure signal, it enters the backpressure signal processing flow. When the buffer queue exceeds the predetermined waterline, it sends a backpressure signal to the upstream device through the backpressure tunnel. That is, when a device supporting PFC technology receives a backpressure signal and the buffer exceeds the predetermined waterline, the backpressure signal is transmitted to the upstream remote device through a preset tunnel.

[0144] S6. After receiving the End.X.PFC SID, the upstream device enters the backpressure processing procedure. That is, upon receiving the backpressure signal, the upstream device parses the packet encapsulation, discovers that the destination IP is the End.X.PFC SID of the local machine, and then enters the backpressure processing procedure.

[0145] The foregoing mainly describes the solutions provided by the embodiments of this application from a methodological perspective. To achieve the above functions, it includes corresponding hardware structures and / or software modules for executing each function. Those skilled in the art should readily recognize that, in conjunction with the units and algorithm steps of the various examples described in the embodiments disclosed herein, the embodiments of this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0146] This application embodiment can divide a signal transmission method into functional modules based on the above method example. For example, each function can be divided into its own functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. Optionally, the module division in this application embodiment is illustrative and only represents one logical functional division; other division methods may be used in actual implementation.

[0147] Figure 14 This is a schematic diagram of a signal transmission device provided in an embodiment of this application. Figure 14 As shown, a signal transmission device 150 is used to reduce the cost of transmitting PFC reverse voltage signals across a wide area network, for example, for performing... Figure 2 The diagram illustrates a signal transmission method. The signal transmission device 150 includes a transmitting unit 1501 and a receiving unit 1502.

[0148] The receiving unit 1502 is used to obtain a predefined segment identifier within the domain. The segment identifier is used to identify the device interface that supports priority-based flow control technology. The segment identifier can be flooded within the domain via the interior gateway protocol.

[0149] The sending unit 1501 is used to send a first backpressure signal to the second network device based on the tunnel between the device interface of the first network device and the device interface of the second network device. The tunnel is created by the first network device or the controller based on the segment identifier. The device interface of the first network device supports priority-based flow control technology. The device interface of the second network device also supports priority-based flow control technology. The second network device is an upstream network device of the first network device. The tunnel is used to carry the backpressure signal.

[0150] In one possible implementation, the receiving unit 1502 is further configured to acquire a second backpressure signal from the next-hop network device of the first network device. The sending unit 1501 is further configured to, when the first network device acquires the second backpressure signal, send a first backpressure signal to the second network device based on the tunnel between the device interfaces of the first network device and the second network device.

[0151] In one possible implementation, the receiving unit 1502 is further configured to receive a third backpressure signal from a fourth network device, which is a downstream network device of the first network device, through a tunnel between the device interfaces of the first network device and the fourth network device. The device interface of the fourth network device supports priority-based flow control technology. The sending unit 1501 is further configured to, when the first network device receives the third backpressure signal, send a first backpressure signal to the second network device through a tunnel between the device interfaces of the first network device and the second network device.

[0152] In one possible implementation, the sending unit 1501 is further configured to parse the third backpressure signal to obtain the destination address of the third backpressure signal. If the destination address of the third backpressure signal is the first network device, the first backpressure signal is sent to the second network device based on the tunnel between the device interfaces of the first network device and the second network device.

[0153] In one possible implementation, the sending unit 1501 is also used to report the segment identifier to the controller via the link status of the border gateway protocol.

[0154] Figure 15This is a schematic diagram of a signal transmission device provided in an embodiment of this application. Figure 15 As shown, a signal transmission device 160 is used to reduce the cost of transmitting PFC reverse voltage signals across a wide area network. For example, it is used to perform... Figure 8 A signal transmission method is shown. The signal transmission device 160 includes a receiving unit 1601.

[0155] The receiving unit 1601 is used to receive a first backpressure signal from the first network device based on the tunnel between the device interface of the first network device and the device interface of the second network device. The tunnel is created by the first network device or controller based on a predefined segment identifier within the domain. The segment identifier is used to identify the device interface that supports priority-based flow control technology. The second network device is an upstream network device of the first network device. The device interface of the first network device supports priority-based flow control technology. The device interface of the second network device supports priority-based flow control technology. The segment identifier can be flooded within the domain through the internal gateway protocol. The tunnel is used to carry the backpressure signal.

[0156] In one possible implementation, the first backpressure signal is sent by the first network device to the second network device after the first network device receives a second backpressure signal from the next-hop network device of the first network device.

[0157] In one possible implementation, the first backpressure signal is sent by the first network device to the second network device upon acquiring the third backpressure signal, and the third backpressure signal is sent by the fourth network device to the first network device based on the tunnel between the device interfaces of the first and fourth network devices. The fourth network device is a downstream network device of the first network device, and the device interface of the fourth network device supports priority-based flow control technology.

[0158] In one possible implementation, the first reverse pressure signal is sent to the second network device when the destination address of the third reverse pressure signal is the first network device, and the destination address of the third reverse pressure signal is obtained by parsing the third reverse pressure signal.

[0159] In one possible implementation, the signal transmission device 160 further includes a transmitting unit 1602; the transmitting unit 1602 is used to report the segment identifier to the controller through the link status of the border gateway protocol.

[0160] In the case where the functions of the integrated modules described above are implemented in hardware, this application provides a possible structural schematic diagram of the electronic device involved in the above embodiments. For example... Figure 16 As shown, an electronic device 200 is used to reduce the cost of transmitting PFC reverse voltage signals across a wide area network, for example, for performing... Figure 2The diagram illustrates a signal transmission method. The electronic device 200 includes a processor 2001, a memory 2002, and a bus 2003. The processor 2001 and the memory 2002 can be connected via the bus 2003.

[0161] Processor 2001 is the control center of the communication device. It can be a single processor or a collective term for multiple processing elements. For example, processor 2001 can be a general-purpose central processing unit (CPU) or other general-purpose processors. The general-purpose processor can be a microprocessor or any conventional processor.

[0162] As one embodiment, the processor 2001 may include one or more CPUs, for example... Figure 16 CPU 0 and CPU 1 are shown in the diagram.

[0163] The memory 2002 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or electrically erasable programmable read-only memory (EEPROM), disk storage media or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but is not limited thereto.

[0164] As one possible implementation, the memory 2002 can exist independently of the processor 2001. The memory 2002 can be connected to the processor 2001 via the bus 2003 and is used to store instructions or program code. When the processor 2001 calls and executes the instructions or program code stored in the memory 2002, it can implement the signal transmission method provided in the embodiments of this application.

[0165] In another possible implementation, the memory 2002 can also be integrated with the processor 2001.

[0166] The bus 2003 can be an industry standard architecture (ISA) bus, a peripheral component interconnect (PCI) bus, or an extended industry standard architecture (EISA) bus. This bus can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 16 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0167] It should be pointed out that, Figure 16 The structure shown does not constitute a limitation on the electronic device 200. Except... Figure 16 In addition to the components shown, the electronic device 200 may include more or fewer components than illustrated, or combine certain components, or have different component arrangements.

[0168] As an example, combined Figure 14 The functions implemented by the transmitting unit 1501 and the receiving unit 1502 in the signal transmission device 150 are the same as those of the transmitting unit 1501 and the receiving unit 1502. Figure 16 The processor in it has the same function as the 2001.

[0169] Optional, such as Figure 16 As shown, the electronic device 200 provided in this application embodiment may further include a communication interface 2004.

[0170] Communication interface 2004 is used to connect with other devices via a communication network. This communication network can be Ethernet, a wireless access network, a wireless local area network (WLAN), etc. Communication interface 2004 may include a receiving unit for receiving data and a transmitting unit for transmitting data.

[0171] In one design, the communication interface in the electronic device provided in this application embodiment can also be integrated into the processor.

[0172] Through the above description of the embodiments, those skilled in the art will clearly understand that, for the sake of convenience and brevity, only the division of the above functional units is used as an example. In practical applications, the above functions can be assigned to different functional units as needed, that is, the internal structure of the device can be divided into different functional units to complete all or part of the functions described above. The specific working process of the system, device, and unit described above can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0173] This application also provides a computer-readable storage medium storing instructions. When a computer executes these instructions, the computer performs each step of the method flow shown in the above-described method embodiments.

[0174] The embodiments of this application provide a computer program product in which, when computer instructions are run on an electronic device, the electronic device executes a signal transmission method according to the above method embodiments.

[0175] The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of computer-readable storage media (a non-exhaustive list) include: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), registers, hard disks, optical fibers, compact disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing, or any other form of computer-readable storage medium in the art.

[0176] An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium can also be a component of the processor. The processor and storage medium can reside within an application-specific integrated circuit (ASIC).

[0177] In the embodiments of this application, the computer-readable storage medium can be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.

[0178] Since the electronic devices, computer-readable storage media, and computer program products in the embodiments of this application can be applied to the above methods, the technical effects they can achieve can also be referred to the above method embodiments. The embodiments of this application will not be repeated here.

[0179] The above are merely specific embodiments of this application, but the scope of protection of this application is not limited thereto. Any changes or substitutions within the technical scope disclosed in this application should be covered within the scope of protection of this application.

Claims

1. A signal transmission method, characterized in that, Applied to a first network device, the method includes: Obtain a predefined segment identifier within the domain. The segment identifier is used to identify device interfaces that support priority-based flow control technology. The segment identifier supports flooding within the domain via the Interior Gateway Protocol. Based on the tunnel between the device interface of the first network device and the device interface of the second network device, a first backpressure signal is sent to the second network device. The tunnel is created by the first network device or controller based on the segment identifier. The device interface of the first network device supports priority-based flow control technology, and the device interface of the second network device also supports priority-based flow control technology. The second network device is an upstream network device of the first network device, and the tunnel is used to carry the backpressure signal.

2. The method according to claim 1, characterized in that, Before sending the first backpressure signal to the second network device through the tunnel between the device interface of the first network device and the device interface of the second network device, the method further includes: Obtain the second back pressure signal from the next-hop network device of the first network device; The step of sending a first backpressure signal to the second network device based on the tunnel between the device interfaces of the first network device and the second network device includes: When the first network device acquires the second back pressure signal, it sends the first back pressure signal to the second network device based on the tunnel between the device interface of the first network device and the device interface of the second network device.

3. The method according to claim 2, characterized in that, Before sending the first backpressure signal to the second network device through the tunnel between the device interface of the first network device and the device interface of the second network device, the method further includes: Based on the tunnel between the device interface of the first network device and the device interface of the fourth network device, a third back pressure signal is received from the fourth network device, wherein the fourth network device is a downstream network device of the first network device, and the device interface of the fourth network device supports priority-based flow control technology. The step of sending a first backpressure signal to the second network device based on the tunnel between the device interfaces of the first network device and the second network device includes: When the first network device acquires the third back pressure signal, it sends the first back pressure signal to the second network device based on the tunnel between the device interface of the first network device and the device interface of the second network device.

4. The method according to claim 3, characterized in that, The step of sending the first backpressure signal to the second network device through the tunnel between the device interfaces of the first network device and the second network device includes: The destination address of the third reverse voltage signal is obtained by parsing the third reverse voltage signal; When the destination address of the third back pressure signal is the first network device, the first back pressure signal is sent to the second network device based on the tunnel between the device interface of the first network device and the device interface of the second network device.

5. The method according to claim 1, characterized in that, The method further includes: The segment identifier is reported to the controller based on the link status of the Border Gateway Protocol.

6. The method according to claim 1, characterized in that, At least one third network device is connected between the first network device and the second network device, and the at least one third network device includes a network device that does not support priority-based flow control technology.

7. The method according to claim 1, characterized in that, Allows deployment of group-level slices on device interfaces that support priority-based flow control technology.

8. A signal transmission method, characterized in that, Applied to a second network device, the method includes: Based on the tunnel between the device interfaces of the first network device and the second network device, a first backpressure signal is received from the first network device. The tunnel is created by the first network device or controller based on a predefined segment identifier within the domain. The segment identifier is used to identify a device interface that supports priority-based flow control technology. The second network device is an upstream network device of the first network device. The device interfaces of the first and second network devices both support priority-based flow control technology. The segment identifier supports flooding within the domain via an interior gateway protocol. The tunnel is used to carry the backpressure signal.

9. The method according to claim 8, characterized in that, The first back pressure signal is sent by the first network device to the second network device after the first network device receives the second back pressure signal from the next-hop network device of the first network device.

10. The method according to claim 8, characterized in that, The first backpressure signal is sent by the first network device to the second network device upon acquiring the third backpressure signal. The third backpressure signal is sent by the fourth network device to the first network device based on the tunnel between the device interface of the first network device and the device interface of the fourth network device. The fourth network device is a downstream network device of the first network device, and the device interface of the fourth network device supports priority-based flow control technology.

11. The method according to claim 10, characterized in that, The first reverse pressure signal is sent to the second network device when the destination address of the third reverse pressure signal is the first network device, and the destination address of the third reverse pressure signal is obtained by parsing the third reverse pressure signal.

12. The method according to claim 8, characterized in that, The method further includes: The segment identifier is reported to the controller based on the link status of the Border Gateway Protocol.

13. The method according to claim 8, characterized in that, At least one third network device is connected between the first network device and the second network device, and the at least one third network device includes a network device that does not support priority-based flow control technology.

14. The method according to claim 8, characterized in that, Allows deployment of group-level slices on device interfaces that support priority-based flow control technology.

15. A signal transmission device, characterized in that, Applied to a first network device, the signal transmission device includes: a receiving unit and a transmitting unit; The receiving unit is used to obtain a predefined segment identifier within the domain. The segment identifier is used to identify a device interface that supports priority-based flow control technology. The segment identifier supports flooding within the domain via an interior gateway protocol. The sending unit is used to send a first backpressure signal to the second network device based on the tunnel between the device interface of the first network device and the device interface of the second network device. The tunnel is created by the first network device or the controller based on the segment identifier. The device interface of the first network device supports priority-based flow control technology, the device interface of the second network device supports priority-based flow control technology, the second network device is an upstream network device of the first network device, and the tunnel is used to carry the backpressure signal.

16. A signal transmission device, characterized in that, Applied to a second network device, the signal transmission device includes: a receiving unit; The receiving unit is configured to receive a first backpressure signal from the first network device based on a tunnel between the device interfaces of the first network device and the second network device. The tunnel is created by the first network device or controller based on a predefined segment identifier within the domain. The segment identifier is used to identify a device interface that supports priority-based flow control technology. The second network device is an upstream network device of the first network device. The device interfaces of the first and second network devices both support priority-based flow control technology. The segment identifier supports flooding within the domain via an interior gateway protocol. The tunnel is used to carry the backpressure signal.

17. An electronic device, characterized in that, include: Processor and memory; The memory is used to store one or more programs, the one or more programs including computer execution instructions. When the electronic device is running, the processor executes the computer execution instructions stored in the memory to cause the electronic device to perform the method of any one of claims 1-14.

18. A computer-readable storage medium for storing one or more programs, characterized in that, The one or more programs include instructions that, when executed by a computer, cause the computer to perform the method as described in any one of claims 1-14.

19. A computer program product, characterized in that, The computer program product includes computer instructions that, when executed on an electronic device, cause the electronic device to perform the method as described in any one of claims 1-14.

Images