Information processing method and device

Abstract

The embodiment of the invention provides an information processing method. A first network device can receive a first bandwidth value sent by a second network device and receive a second bandwidth value sent by a third network device. The first bandwidth value indicates the bandwidth for the second network device to send the traffic to the target prefix, and the second bandwidth value indicates the bandwidth for the third network device to send the traffic to the target prefix. And according to the first bandwidth value and the second bandwidth value, the first network device determines the weight of the traffic which takes the destination prefix as the destination to be respectively sent to the second network device and the third network device. Therefore, when the first network device forwards the flow taking the destination prefix as the destination, the flow can be sent to the second network device and the third network device based on the weight. Therefore, the traffic actually received by the second network equipment and the third network equipment is matched with the bandwidth for sending the traffic to the target prefix by the second network equipment and the third network equipment, so that packet loss of the service traffic is effectively avoided.

Description

Technical Field

[0001] The present application relates to the field of communications, and in particular to an information processing method and device. Background Art

[0002] In a communication network, service traffic can be transmitted to its destination through multiple paths to achieve the purpose of rationally utilizing network resources and maximizing the quality of service provided to the business. For example, in some scenarios, service traffic can be transmitted to its destination through multiple paths that share load.

[0003] Although multiple paths are used to transmit business traffic, the current solution for network equipment to forward business traffic still has the problem of serious business traffic packet loss.

[0004] Therefore, a solution is urgently needed to solve the above problems. Summary of the invention

[0005] The embodiment of the present application provides an information processing method, which can effectively reduce the packet loss of business traffic.

[0006] In the first aspect, the embodiment of the present application provides an information processing method, which can be applied to a first network device. The first network device can receive a first bandwidth value sent by a second network device and a second bandwidth value sent by a third network device. Among them, the second network device and the third network device can both send traffic to the target prefix, the first bandwidth value indicates the bandwidth of the second network device sending traffic to the target prefix, and the second bandwidth value indicates the bandwidth of the third network device sending traffic to the target prefix. After the first network device receives the first bandwidth value and the second bandwidth value, it can determine the weight of sending traffic with the destination prefix as the destination to the second network device and the third network device respectively according to the first bandwidth value and the second bandwidth value. In this way, when forwarding traffic with the destination prefix as the destination, the first network device can send the aforementioned traffic to the second network device and the third network device based on the aforementioned weight, so that the traffic actually received by the second network device and the third network device matches the bandwidth at which it can send traffic to the target prefix, thereby reasonably utilizing the bandwidth provided by the second network device and the third network device to send traffic to the target prefix, so as to avoid the bandwidth provided by the second network device to send traffic to the target prefix being insufficient to carry the traffic received by itself with the destination prefix as the destination, thereby effectively avoiding business traffic packet loss.

[0007] In a possible implementation, the first network device, the second network device, and the third network device all belong to the first network domain, and the second network device and the third network device are border devices connected to the second network domain. In this case, the aforementioned first bandwidth value is the bandwidth corresponding to the cross-domain link connecting the second network device to the second network domain, and the second bandwidth value is the bandwidth corresponding to the cross-domain link connecting the third network device to the second network domain. In this case, the first network device in the first network domain can determine the weight of sending traffic with the destination prefix as the destination to the border device based on the bandwidth of the cross-domain link between the border device of the first network domain and the second network domain.

[0008] In a possible implementation, the first network device sends traffic with the destination prefix as the destination to the third network device through the fourth network device, and the first network device and the fourth network device are equal-cost load sharing devices. In this case, the first network device can send part of the traffic to the fourth network device which is an equal-cost load sharing device with itself, thereby avoiding service traffic packet loss.

[0009] In a possible implementation, if the first network device and the fourth network device are load sharing devices for each other, and in a possible implementation, the first network device may determine that the weight of sending the destination traffic with the destination prefix as the destination to the second network device is: Determine the weight for sending the traffic with the destination prefix as the destination to the third network device as follows: Wherein: m is determined to be the first bandwidth value, and n is determined to be the second bandwidth value. In this way, the first bandwidth value that the second network device can use to send traffic can match the traffic received by itself, and the second bandwidth value that the third network device can use to send traffic can match the traffic received by itself, thereby effectively avoiding service traffic packet loss.

[0010] In a possible implementation, considering that the link bandwidth between the first network device and the fourth network device is limited, when determining the weight of sending traffic to the third network device, the bandwidth of the link between the first network device and the fourth network device may also be considered, so as to avoid sending too much traffic to the fourth network device and causing packet loss when the traffic is transmitted between the first network device and the fourth network device. As a specific example, assuming that the bandwidth of the link between the first network device and the fourth network device is j, and the bandwidth of the link between the first network device and the second network device is k, if the weight of sending traffic to the third network device is j, the bandwidth of the link between the first network device and the fourth network device is k. This means that the weight of diverting traffic to the fourth network device is reasonable, so the weight of sending traffic to the third network device can be determined as Determine the weight for sending traffic to the second network device as If the This means that the weight of the traffic diverted to the fourth network device is too large, so the weight of sending traffic to the third network device can be determined to be Determine the weight for sending traffic to the second network device as

[0011] In a possible implementation, before determining the weight of sending the traffic with the destination prefix as the destination to the second network device and the third network device respectively, the first network device may also determine whether the first traffic tuning condition is satisfied. When the aforementioned first traffic tuning condition is satisfied, the weight of sending the traffic with the destination prefix as the destination to the second network device and the third network device respectively is determined. Among them, the aforementioned first traffic tuning condition refers to the condition that if equal-cost load sharing is continued, it will cause serious packet loss of traffic. In an example, when the first bandwidth value is less than the second bandwidth value, and the first bandwidth value is not 0, and the difference between the first bandwidth value and the second bandwidth value is large, continuing to use the traditional equal-cost load sharing scheme will cause serious packet loss. Therefore, in an example, the first traffic tuning condition can be: the first bandwidth value is less than the second bandwidth value, the first bandwidth value is not 0, and the difference between the first bandwidth value and the second bandwidth value is greater than or equal to the first bandwidth threshold. In other words, the first network device can determine the weight of sending traffic with the destination prefix as the destination to the second network device and the third network device respectively when it is determined that the first bandwidth value is less than the second bandwidth value, the first bandwidth value is not 0, and the difference between the first bandwidth value and the second bandwidth value is greater than or equal to the first bandwidth threshold.

[0012] In one possible implementation, after determining the weights for sending traffic with the destination prefix as the destination to the second network device and the third network device respectively, the first network device may also save the weights for sending traffic with the destination prefix as the destination to the second network device and the third network device respectively in a forwarding table entry, so that in the traffic forwarding stage, the weights for sending traffic to the second network device and the third network device can be determined based on the forwarding table entry, so as to forward the received traffic based on the weight.

[0013] In a possible implementation, in addition to receiving the aforementioned first bandwidth value and second bandwidth value, the first network device may also receive a third bandwidth value sent by the fifth network device and a fourth bandwidth value sent by the sixth network device. The third bandwidth value indicates the bandwidth of the traffic sent by the fifth network device to the destination prefix, and the fourth bandwidth value indicates the bandwidth of the traffic sent by the sixth network device to the destination prefix. Wherein: the fifth network device and the aforementioned second network device are both connected to the first network device, and the fifth network device and the second network device are load sharing devices for each other. In other words, the traffic received by the first network device can be load shared to the second network device and the fifth network device for forwarding. The third network device and the sixth network device are both connected to the fourth network device, and the third network device and the sixth network device can be load sharing devices for each other. In other words, the traffic received by the fourth network device can be load shared to the third network device and the sixth network device for forwarding. Accordingly, the first network device may determine the weight of sending the traffic with the destination prefix as the destination to the second network device, the fifth network device, and the fourth network device according to the first bandwidth value, the second bandwidth value, the third bandwidth value, and the fourth bandwidth value. That is, the traffic originally load-shared by the second network device and the fifth network device is load-shared by the second network device, the fifth network device and the fourth network device, thereby reducing the traffic received by the second network device. Accordingly, it avoids serious packet loss due to the bandwidth value provided by the second network device being insufficient to carry the traffic it receives.

[0014] In a possible implementation, before determining the weight of sending the traffic with the destination prefix as the destination to the second network device, the fifth network device, and the fourth network device, the first network device may also determine whether the second traffic tuning condition is met. When the second traffic tuning condition is met, the weight of sending the traffic with the destination prefix as the destination to the second network device, the fifth network device, and the fourth network device is determined. Wherein, the second traffic tuning condition refers to the condition that if equal load sharing is continued, it will cause serious packet loss of traffic. In an example, when the first total bandwidth provided by the first network device is less than the second total bandwidth provided by the fourth network device, and the first total bandwidth is not equal to 0, and the difference between the first total bandwidth and the second total bandwidth is greater than or equal to the second bandwidth threshold, continuing to use the traditional equal load sharing scheme will cause serious packet loss. Wherein, the first total bandwidth is: the sum of the first bandwidth value and the third bandwidth value, and the second total bandwidth is: the sum of the second bandwidth value and the fourth bandwidth value. Therefore, in one example, the second traffic tuning condition may be: the first total bandwidth provided by the first network device is less than the second total bandwidth provided by the fourth network device, and the first total bandwidth is not equal to 0, and the difference between the first total bandwidth and the second total bandwidth is greater than or equal to the second bandwidth threshold. In other words, the first network device may determine the weight of sending traffic with the destination prefix as the destination to the second network device, the fifth network device, and the fourth network device when it is determined that the first total bandwidth provided by the first network device is less than the second total bandwidth provided by the fourth network device, and the first total bandwidth is not equal to 0, and the difference between the first total bandwidth and the second total bandwidth is greater than or equal to the second bandwidth threshold.

[0015] In a possible implementation manner, the first network device may determine that the weight of sending traffic with the destination prefix as the destination to the fourth network device is: Determine the weight of sending traffic with the destination prefix as the destination to the second network device as follows: Determine the weight of sending traffic with the destination prefix as the destination to the fifth network device as follows: Wherein: a is the first bandwidth value, b is the second bandwidth value, c is the third bandwidth value, and d is the fourth bandwidth value. In this way, the first bandwidth value that the second network device can use to send traffic can match the traffic it receives, the third bandwidth value that the fifth network device can use to send traffic can match the traffic it receives, and the second total bandwidth that the fourth network device can use to send traffic can match the traffic it receives, thereby effectively avoiding service traffic packet loss.

[0016] In a possible implementation, considering that the bandwidth of the link between the first network device and the fourth network device is limited, the bandwidth of the link between the first network device and the fourth network device may also be considered when determining the weight of sending traffic to the fourth network device, so as to avoid sending too much traffic to the fourth network device and causing packet loss when the traffic is transmitted between the first network device and the fourth network device. As a specific example, assuming that the bandwidth of the link between the first network device and the fourth network device is e, and the bandwidth of the link between the first network device and the second network device is f, if the weight of the traffic sent to the fourth network device is This means that the weight of the traffic diverted to the fourth network device is reasonable, so the weight of sending traffic to the fourth network device can be determined as Determine the weight for sending traffic to the second network device as And determine the weight of sending traffic to the fifth network device as If the This means that the weight of the traffic diverted to the fourth network device is too large, so the weight of sending traffic to the fourth network device can be determined to be Determine the weight of sending traffic with the destination prefix as the destination to the second network device as follows: Determine the weight of sending traffic with the destination prefix as the destination to the fifth network device as follows:

[0017] In a possible implementation, the second network device and the third network device are connected to the first network device respectively, and the first network device can also be connected to the seventh network device. Among them, the second network device, the third network device and the seventh network device can be load sharing devices. The traffic received by the first network device can be load shared to the second network device, the third network device and the seventh network device for forwarding. In this case, the first network device can also receive the fifth bandwidth value sent by the seventh network device, and the fifth bandwidth value indicates the bandwidth of the seventh network device to send traffic to the destination prefix. Correspondingly, according to the first bandwidth value, the second bandwidth value and the fifth bandwidth value, the weight of sending the traffic with the destination prefix as the destination to the second network device, the third network device and the seventh network device is determined respectively. That is: when the traffic received by the first network device can be load shared to the three network devices (the second network device, the third network device and the seventh network device) for forwarding, the weight of sending traffic to the three network devices can be determined according to the bandwidth values ​​provided by the three network devices, so that the bandwidth actually provided by the three network devices matches the traffic actually carried by them, avoiding traffic packet loss.

[0018] In a possible implementation, the sum of the first bandwidth value, the second bandwidth value and the fifth bandwidth value is called the third total bandwidth. In order to match the bandwidth actually provided by the above three network devices with the traffic actually carried by them, the weight of sending the traffic with the target prefix as the destination to the second network device can be determined as: the ratio of the first bandwidth value to the third total bandwidth, the weight of sending the traffic with the target prefix as the destination to the third network device can be determined as: the ratio of the second bandwidth value to the third total bandwidth; the weight of sending the traffic with the target prefix as the destination to the seventh network device can be determined as: the ratio of the fifth bandwidth value to the third total bandwidth.

[0019] In a possible implementation, the first network device receives the first bandwidth value sent by the second network device by receiving an intermediate system to intermediate system (IS-IS) message announced by the second network device, wherein the IS-IS message includes the first bandwidth value.

[0020] In a possible implementation, the IS-IS message may include a prefix type length value (TLV), the prefix TLV includes a first sub-TLV, and the first sub-TLV includes the first bandwidth value. In other words, the prefix TLV of the IS-IS message may be extended, and the extended first sub-TLV is used to carry the first bandwidth value.

[0021] In a possible implementation, the first network device receives the first bandwidth value sent by the second network device by receiving an open shortest path first (OSPF) message announced by the second network device, wherein the OSPF message includes the first bandwidth value.

[0022] In a possible implementation, the OSPF message includes a prefix TLV, the prefix TLV includes a second sub-TLV, and the second sub-TLV includes the first bandwidth value. In other words, the prefix TLV of the OSPF message can be extended to extend the second sub-TLV for carrying the first bandwidth value.

[0023] In a second aspect, an embodiment of the present application provides an information processing device, which is applied to a first network device, and the device includes: a receiving unit, which is used to receive a first bandwidth value sent by a second network device, the first bandwidth value indicating the bandwidth of the second network device sending traffic to a destination prefix; receiving a second bandwidth value sent by a third network device, the second bandwidth value indicating the bandwidth of the third network device sending traffic to the destination prefix; a processing unit, which is used to determine the weight of sending traffic with the destination prefix as the destination to the second network device and the third network device respectively according to the first bandwidth value and the second bandwidth value.

[0024] In a possible implementation manner, the first network device, the second network device, and the third network device all belong to a first network domain, and the second network device and the third network device are boundary devices connected to a second network domain.

[0025] In a possible implementation, the first network device sends traffic with the destination prefix as the destination to the third network device through the fourth network device, and the first network device and the fourth network device are equal-cost load sharing devices.

[0026] In a possible implementation, the processing unit is configured to determine a weight for sending traffic with the destination prefix as the destination to the second network device as follows: Determine the weight for sending the traffic with the destination prefix as the destination to the third network device as follows: Wherein: it is determined that m is the first bandwidth value, and n is the second bandwidth value.

[0027] In a possible implementation, the processing unit is configured to: send to the second network device a weight of the destination traffic with the destination prefix as: The weight for sending the destination traffic with the destination prefix as the destination to the third network device is: Wherein: the k is the bandwidth of the link between the first network device and the second network device, and the j is the bandwidth of the link between the first network device and the fourth network device.

[0028] In one possible implementation, the processing unit is further used to determine that the first bandwidth value is less than the second bandwidth value, the first bandwidth value is not 0, and the difference between the first bandwidth value and the second bandwidth value is greater than or equal to a first bandwidth threshold before determining the weight of sending traffic with the destination prefix as the destination to the second network device and the third network device respectively.

[0029] In a possible implementation, the receiving unit is further used to receive a third bandwidth value sent by a fifth network device, the third bandwidth value indicating a bandwidth for the fifth network device to send traffic to a destination prefix; and to receive a fourth bandwidth value sent by a sixth network device, the fourth bandwidth value indicating a bandwidth for the sixth network device to send traffic to the destination prefix; and the processing unit is used to determine, based on the first bandwidth value, the second bandwidth value, the third bandwidth value and the fourth bandwidth value, a weight for sending traffic with the destination prefix as a destination to the second network device, the fifth network device and the fourth network device, respectively; wherein: the second network device and the fifth network device are respectively connected to the first network device, the third network device and the sixth network device are respectively connected to the fourth network device, and the traffic with the destination prefix as a destination received by the fourth network device is forwarded via the third network device and the sixth network device.

[0030] In a possible implementation manner: the processing unit is further used to determine, before determining the weights of sending traffic with the destination prefix as the destination to the second network device, the fifth network device, and the fourth network device respectively, that a first total bandwidth provided by the first network device is less than a second total bandwidth provided by the fourth network device, and that the first total bandwidth is not equal to 0, and that a difference between the first total bandwidth and the second total bandwidth is greater than or equal to a second bandwidth threshold, wherein the first total bandwidth is: the sum of the first bandwidth value and the third bandwidth value, and the second total bandwidth is: the sum of the second bandwidth value and the fourth bandwidth value.

[0031] In a possible implementation, the processing unit is configured to determine a weight for sending traffic with the destination prefix as a destination to the fourth network device as follows: Determine the weight of sending traffic with the destination prefix as the destination to the second network device as follows: Determine the weight of sending traffic with the destination prefix as the destination to the fifth network device as follows: Wherein: a is the first bandwidth value, b is the second bandwidth value, c is the third bandwidth value, and d is the fourth bandwidth value.

[0032] In a possible implementation, the processing unit is configured to determine a weight for sending traffic with the destination prefix as a destination to the fourth network device as follows: Determine the weight of sending traffic with the destination prefix as the destination to the second network device as follows: Determine the weight of sending traffic with the destination prefix as the destination to the fifth network device as follows: Wherein: f is the sum of the bandwidth of the link between the first network device and the second network device and the bandwidth of the link between the first network device and the fifth network device, and e is the bandwidth of the link between the first network device and the fourth network device.

[0033] In a possible implementation, the second network device and the third network device are connected to the first network device respectively, and the first network device is also connected to the seventh network device. The receiving unit is further used to receive a fifth bandwidth value sent by the seventh network device, and the fifth bandwidth value indicates the bandwidth of the seventh network device for sending traffic to the destination prefix; the processing unit is used to determine the weight of sending traffic with the destination prefix as the destination to the second network device, the third network device and the seventh network device respectively according to the first bandwidth value, the second bandwidth value and the fifth bandwidth value.

[0034] In one possible implementation, according to the processing unit, it is used to: determine the weight of sending traffic with the target prefix as the destination to the second network device as: the ratio of the first bandwidth value to the third total bandwidth, the third total bandwidth being the sum of the first bandwidth value, the second bandwidth value and the fifth bandwidth value; determine the weight of sending traffic with the target prefix as the destination to the third network device as: the ratio of the second bandwidth value to the third total bandwidth; determine the weight of sending traffic with the target prefix as the destination to the seventh network device as: the ratio of the fifth bandwidth value to the third total bandwidth.

[0035] In a possible implementation manner, the receiving unit is configured to: receive an Intermediate System to Intermediate System (IS-IS) message advertised by the second network device, wherein the IS-IS message includes the first bandwidth value.

[0036] In a possible implementation manner, the IS-IS message includes a prefix type length value TLV, the prefix TLV includes a first sub-TLV, and the first sub-TLV includes the first bandwidth value.

[0037] In a possible implementation manner, the receiving unit is configured to receive an Open Shortest Path First (OSPF) message advertised by the second network device, wherein the OSPF message includes the first bandwidth value.

[0038] In a possible implementation manner, the OSPF message includes a prefix type length value TLV, the prefix TLV includes a second sub-TLV, and the second sub-TLV includes the first bandwidth value.

[0039] In a possible implementation manner, the processing unit is further configured to: store in a forwarding table entry a weight for sending traffic with the destination prefix as a destination to the second network device and the third network device respectively.

[0040] In a third aspect, an embodiment of the present application provides a device. The device includes a processor and a memory. The memory is used to store instructions or computer programs. The processor is used to execute the instructions or computer programs in the memory to perform any method described in the first aspect above.

[0041] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, including instructions or a computer program, which, when executed on a computer, enables the computer to execute any one of the methods described in the first aspect above.

[0042] In a fifth aspect, an embodiment of the present application provides a computer program product comprising instructions or a computer program, which, when executed on a computer, enables the computer to execute any one of the methods described in the first aspect above. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0044] Figure 1a A schematic diagram of an exemplary application scenario provided for an embodiment of the present application;

[0045] Figure 1b A schematic diagram of another exemplary application scenario provided for an embodiment of the present application;

[0046] Figure 1c A schematic diagram of another exemplary application scenario provided for an embodiment of the present application;

[0047] Figure 1d A schematic diagram of another exemplary application scenario provided for an embodiment of the present application;

[0048] Figure 2 A flowchart of an information processing method provided in an embodiment of the present application;

[0049] Figure 3 A schematic diagram of the structure of a sub-TLV provided in an embodiment of the present application;

[0050] Figure 4a A schematic diagram of an exemplary application scenario provided for an embodiment of the present application;

[0051] Figure 4b A schematic diagram of another exemplary application scenario provided for an embodiment of the present application;

[0052] Figure 4c A schematic diagram of another exemplary application scenario provided for an embodiment of the present application;

[0053] Figure 5 A schematic diagram of the structure of an information processing device provided in an embodiment of the present application;

[0054] Figure 6 A schematic diagram of the structure of a device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0055] The embodiment of the present application provides an information processing method, which can effectively reduce the packet loss of business traffic.

[0056] At present, although multiple paths are used to transmit business traffic, the current solution for network equipment to forward business traffic still has the problem of serious business traffic packet loss. Next, the specific scenario where business traffic packet loss is serious is introduced.

[0057] See also Figure 1a , which is a schematic diagram of an exemplary application scenario provided by an embodiment of the present application. Figure 1a As shown:

[0058] RT1 and RT2 are the boundary devices used by network domain A to connect to network domain B. RTA and RTB are the boundary devices used by network domain B to connect to network domain A. RT1 is connected to RTA, and RT2 is connected to RTB. In addition to RTA and RTB, network domain B also includes RTC and RTD. RTC and RTD are the boundary devices used by network domain B to connect to network domain G.

[0059] The connection relationship between the network devices in network domain B is not described in detail here.

[0060] In one example, RT1 and RT2 may publish routes with the same destination prefix, for example, RT1 and RT2 may use virtual next hop technology to publish routes including the same virtual next hop destination prefix. As a specific example, an External Border Gateway Protocol (EBGP) neighbor may be established between RT1 and RTA based on a loopback interface address, RT1 publishes routes to RTA, EBGP neighbors may be established between RT2 and RTB based on the loopback interface address, and RT2 publishes routes to RTB, and the routes published by RT1 to RTA and the routes published by RT2 to RTB may include the same destination prefix.

[0061] Accordingly, in the traffic forwarding phase, the service traffic with the aforementioned destination prefix as the destination can be sent to RT1 via RTA, and RT1 forwards the service traffic to its destination. The service traffic with the aforementioned destination prefix as the destination can also be sent to RT2 via RTB, and RT2 forwards the service traffic to its destination.

[0062] In a specific example, the network device in network domain G can send the service traffic with the destination prefix as the destination to its destination via network domain B and network domain A. The transmission paths of the service traffic in network domain B and network domain A can include two, namely: RTC-RTA-RT1 and RTD-RTB-RT2. In an example, the two paths can be equal-cost load sharing paths. That is: Figure 1a The two paths represented by the dotted lines carry the same traffic, both X. That is, link RTA-RT1 and link RTB-RT2 share the same bandwidth of service traffic. In this case, RTC and RTD are equal-cost load sharing devices, and RTA and RTB are also equal-cost load sharing devices. Under normal circumstances, link RTA-RT1 and link RTB-RT2 can provide the same bandwidth for forwarding the aforementioned service traffic.

[0063] However, if some of the links in link RTA-RT1 fail, for example, 4 of the 5 100G links are broken. At this time, since the EBGP neighbor between RTA and RT1 is not broken, the route publishing process between RT1 and RTA is the same as the route publishing process before some of the links in link RTA-RT1 fail. Accordingly, the transmission paths of the aforementioned service traffic in network domain B and network domain A can still include the two paths RTC-RTA-RT1 and RTD-RTB-RT2. Similarly, in the forwarding phase of service traffic, the service traffic with the aforementioned destination prefix as the destination is evenly distributed to the two paths RTC-RTA-RT1 and RTD-RTB-RT2 for forwarding. However, since some of the links in link RTA-RT1 fail, the bandwidth actually provided by link RTA-RT1 for forwarding the aforementioned service traffic is insufficient to carry the service traffic it receives, thereby causing traffic congestion on link RTA-RT1 and resulting in serious packet loss of service traffic.

[0064] See also Figure 1b , which is a schematic diagram of another exemplary application scenario provided by the embodiment of the present application. Figure 1b As shown:

[0065] RT1, RT2, RT3 and RT4 are the boundary devices used by network domain A to connect to network domain B. RTA, RTB, RTC and RTD are the boundary devices used by network domain B to connect to network domain A. RT1 is connected to RTA, RT2 is connected to RTB, RT3 is connected to RTC, and RT4 is connected to RTD. In addition to RTA, RTB, RTC and RTD, network domain B also includes RTE, RTF, RTG and RTH. RTG and RTH are the boundary devices used by network domain B to connect to network domain G.

[0066] The connection relationship between the network devices in network domain B is not described in detail here.

[0067] In one example, RT1, RT2, RT3, and RT4 can publish routes with the same destination prefix. For example, RT1, RT2, RT3, and RT4 can use virtual next-hop technology to publish routes including the same virtual next-hop destination prefix. Specifically, RT1 publishes a route including a certain destination prefix to RTA, RT2 publishes a route including the destination prefix to RTB, RT3 publishes a route including the destination prefix to RTC, and RT4 publishes a route including the destination prefix to RTD. Among them, the way RT1 publishes routes to RTA, the way RT2 publishes routes to RTB, the way RT3 publishes routes to RTC, and the way RT4 publishes routes to RTD are the same. Regarding the way RT1 publishes routes to RTA, please refer to the relevant description in the previous text, and no repeated description is made here.

[0068] Accordingly, in the traffic forwarding stage, the service traffic with the aforementioned destination prefix as the destination can be sent to RT1 via RTA, and RT1 will forward the service traffic to its destination. The service traffic with the aforementioned destination prefix as the destination can also be sent to RT2 via RTB, and RT2 will forward the service traffic to its destination. The service traffic with the aforementioned destination prefix as the destination can also be sent to RT3 via RTC, and RT3 will forward the service traffic to its destination. The service traffic with the aforementioned destination prefix as the destination can also be sent to RT4 via RTD, and RT4 will forward the service traffic to its destination.

[0069] In a specific example, the network equipment in network domain G can send the service traffic with the aforementioned destination prefix as the destination to its destination via network domain B and network domain A. Among them, the transmission paths of the aforementioned service traffic in network domain B and network domain A may include four, namely: RTG-RTE-RTA, RTG-RTE-RTC, RTH-RTF-RTB and RTH-RTF-RTD. In an example, RTG-RTE and RTH-RTF can be equal-cost load sharing paths. That is to say, RTG-RTE and RTH-RTF share the service traffic of the same bandwidth, and the service traffic received by RTE is the same as the service traffic received by RTF. In this case, RTE and RTF are equal-cost load sharing devices, and RTG and RTH are also equal-cost load sharing devices. That is: if Figure 1b The two paths represented by the dotted lines carry the same traffic, both X. Under normal circumstances, the bandwidth that RTE can provide for forwarding the aforementioned business traffic is the same as the bandwidth that RTF can provide for forwarding the aforementioned business traffic. Among them: The bandwidth that RTE can provide for forwarding the aforementioned business traffic is the sum of the bandwidth that link RTA-RT1 and link RTC-RT3 can provide for forwarding the aforementioned business traffic. The bandwidth that RTF can provide for forwarding the aforementioned business traffic is the sum of the bandwidth that link RTB-RT2 and link RTD-RT4 can provide for forwarding the aforementioned business traffic.

[0070] However, if the bandwidth that RTE can provide for forwarding the aforementioned service traffic becomes smaller, for example, when the link RTA-RT1 fails. During the forwarding phase of the service traffic, the service traffic with the aforementioned destination prefix as the destination is evenly distributed to the two paths RTG-RTE and RTH-RTF for forwarding. Since the bandwidth that RTE can provide for forwarding the aforementioned service traffic becomes smaller, the bandwidth actually provided by RTE for forwarding the aforementioned service traffic is insufficient to carry the service traffic it receives, thereby causing traffic congestion on the links RTE-RTA and / or RTE-RTC, resulting in severe packet loss of the service traffic.

[0071] See also Figure 1c , which is a schematic diagram of another exemplary application scenario provided by the embodiment of the present application. Figure 1c As shown:

[0072] RT1, RT2, RT3, RT4, RT5 and RT6 are the boundary devices used by network domain A to connect to network domain B. RTA, RTB, RTC, RTD, RTE and RTF are the boundary devices used by network domain B to connect to network domain A. RT1 is connected to RTA, RT2 is connected to RTB, RT3 is connected to RTC, RT4 is connected to RTD, RT5 is connected to RTE, and RT6 is connected to RTF. In addition to RTA, RTB, RTC and RTD, network domain B also includes RTG, RTH, RTI and RTJ. RTI and RTJ are the boundary devices used by network domain B to connect to network domain G.

[0073] The connection relationship between the network devices in network domain B is not described in detail here.

[0074] In one example, RT1, RT2, RT3, RT4, RT5 and RT6 can publish routes with the same destination prefix. For example, RT1, RT2, RT3, RT4, RT5 and RT6 can use virtual next hop technology to publish routes including the same virtual next hop destination prefix. Specifically, RT1 publishes a route including a certain destination prefix to RTA, RT2 publishes a route including the destination prefix to RTB, RT3 publishes a route including the destination prefix to RTC, RT4 publishes a route including the destination prefix to RTD, RT5 publishes a route including the destination prefix to RTE, and RT6 publishes a route including the destination prefix to RTF. Among them, the way RT1 publishes routes to RTA, the way RT2 publishes routes to RTB, the way RT3 publishes routes to RTC, the way RT4 publishes routes to RTD, the way RT5 publishes routes to RTE, and the way RT6 publishes routes to RTF are the same. For the way RT1 publishes routes to RTA, please refer to the relevant description in the previous text, and no repeated description is made here.

[0075] Correspondingly, in the traffic forwarding stage, the service traffic with the aforementioned destination prefix as the destination can be sent to RT1 via RTA, and RT1 will forward the service traffic to its destination. The service traffic with the aforementioned destination prefix as the destination can also be sent to RT2 via RTB, and RT2 will forward the service traffic to its destination. The service traffic with the aforementioned destination prefix as the destination can also be sent to RT3 via RTC, and RT3 will forward the service traffic to its destination. The service traffic with the aforementioned destination prefix as the destination can also be sent to RT4 via RTD, and RT4 will forward the service traffic to its destination. The service traffic with the aforementioned destination prefix as the destination can also be sent to RT5 via RTE, and RT5 will forward the service traffic to its destination. The service traffic with the aforementioned destination prefix as the destination can also be sent to RT6 via RTF, and RT6 will forward the service traffic to its destination.

[0076] In a specific example, the network devices in network domain G can send the service traffic with the aforementioned destination prefix as the destination to its destination via network domain B and network domain A. Among them, the transmission paths of the aforementioned service traffic in network domain B and network domain A may include six paths, namely: RTI-RTG-RTA, RTI-RTG-RTC, RTI-RTG-RTE, RTJ-RTH-RTB, RTJ-RTH-RTD and RTJ-RTH-RTF. In an example, the link RTI-RTG and the link RTJ-RTH can be equal-cost load sharing paths. In this case, RTG and RTH are equal-cost load sharing devices, and RTI and RTJ are also equal-cost load sharing devices. That is: if Figure 1c The two paths represented by the dotted lines carry the same amount of traffic, both X.

[0077] exist Figure 1c In the network scenario shown:

[0078] RTG can be forwarded through links RTG-RTA, RTG-RTC and RTG-RTE. In an example, the aforementioned links RTG-RTA, RTG-RTC and RTG-RTE can be equal-cost load sharing paths. That is, links RTA-RT1, RTC-RT3 and RTE-RT5 share the same bandwidth of service traffic. Under normal circumstances, links RTA-RT1, RTC-RT3 and RTE-RT5 can provide the same bandwidth for forwarding the aforementioned service traffic.

[0079] However, if some links in link RTA-RT1 fail, RTG will still evenly distribute the service traffic with the aforementioned destination prefix as the destination to links RTG-RTA, RTG-RTC and RTG-RTE for forwarding. Since some links in link RTA-RT1 fail, the bandwidth actually provided by link RTA-RT1 for forwarding the aforementioned service traffic is insufficient to carry the service traffic it receives, resulting in traffic congestion on link RTA-RT1 and severe packet loss of service traffic.

[0080] Similarly, RTH can be forwarded through links RTH-RTB, RTH-RTD, and RTH-RTF. In one example, the aforementioned links RTH-RTB, RTH-RTD, and RTH-RTF can be equal-cost load sharing paths. That is, links RTB-RT2, RTD-RT4, and RTF-RT6 share the same bandwidth of service traffic. Under normal circumstances, links RTB-RT2, RTD-RT4, and RTF-RT6 can provide the same bandwidth for forwarding the aforementioned service traffic.

[0081] However, if some links in link RTB-RT2 fail, RTH will still evenly distribute the service traffic with the aforementioned destination prefix as the destination to links RTH-RTB, RTH-RTD and RTH-RTF for forwarding. Since some links in link RTB-RT2 fail, the bandwidth actually provided by link RTB-RT2 for forwarding the aforementioned service traffic is insufficient to carry the service traffic it receives, resulting in traffic congestion on link RTB-RT2 and severe packet loss of service traffic.

[0082] See also Figure 1d , which is a schematic diagram of another exemplary application scenario provided by the embodiment of the present application. Figure 1d As shown:

[0083] Network domain A includes network devices RT1, RTA, RTB, RTC and RTD. RTC and RTD are boundary devices used by network domain A to connect to network domain G.

[0084] In one example, RT1 can publish routes with the same destination prefix to RTA and RTB. Accordingly, in the traffic forwarding phase, the service traffic with the aforementioned destination prefix as the destination can be sent to RT1 via RTA, and RT1 forwards the service traffic to its destination. The service traffic with the aforementioned destination prefix as the destination can also be sent to RT1 via RTB, and RT1 forwards the service traffic to its destination.

[0085] In a specific example, the network device in network domain G can send the service traffic with the destination prefix as the destination to its destination via network domain A. The transmission paths of the service traffic in network domain A may include two, namely: RTC-RTA-RT1 and RTD-RTB-RT1. In an example, the two paths may be equal-cost load sharing paths. That is: Figure 1d The two paths represented by the dotted lines carry the same traffic, both X. That is, link RTA-RT1 and link RTB-RT1 share the same bandwidth of service traffic. In this case, RTA and RTB are equal-cost load sharing devices, and RTC and RTD are also equal-cost load sharing devices. Under normal circumstances, link RTA-RT1 and link RTB-RT1 can provide the same bandwidth for forwarding the aforementioned service traffic.

[0086] However, if some links in link RTA-RT1 fail, for example, 4 of the 5 100G links are broken. At this time, in the forwarding stage of service traffic, the service traffic with the aforementioned destination prefix as the destination is evenly distributed to the two paths RTC-RTA-RT1 and RTD-RTB-RT1 for forwarding. However, since some links in link RTA-RT1 fail, the bandwidth actually provided by link RTA-RT1 for forwarding the aforementioned service traffic is insufficient to carry the service traffic it receives, resulting in traffic congestion on link RTA-RT1 and severe packet loss of service traffic.

[0087] In the embodiment of the present application, the network domain may be an Interior Gateway Protocol (IGP) domain.

[0088] In order to solve the problem of serious packet loss in the above-mentioned business traffic, an embodiment of the present application provides an information processing method, which is described below in conjunction with the accompanying drawings. In the following description, "business traffic" may also be referred to as "traffic".

[0089] See also Figure 2 , which is a flow chart of an information processing method provided in an embodiment of the present application. Figure 2 The method shown can be applied to the first network device.

[0090] The information processing method provided in the embodiment of the present application can be applied to the above Figure 1a or Figure 1b or Figure 1c or Figure 1d The network scenario shown. When this method is applied to Figure 1a In the network scenario shown, the first network device can correspond to Figure 1a When this method is applied to the RTC Figure 1b In the network scenario shown, the first network device can correspond to Figure 1b When this method is applied to Figure 1c In the network scenario shown, the first network device can correspond to Figure 1c When this method is applied to Figure 1d In the network scenario shown, the first network device can correspond to Figure 1d The RTC shown.

[0091] Figure 2 The method shown may include the following S101-S103.

[0092] S101: Receive a first bandwidth value sent by a second network device, where the first bandwidth value indicates a bandwidth for the second network device to send traffic to a destination prefix.

[0093] S102: Receive a second bandwidth value sent by a third network device, where the second bandwidth value indicates a bandwidth for the third network device to send traffic to the destination prefix.

[0094] In the embodiment of the present application, the first network device, the second network device and the third network device all belong to the first network domain, wherein the first network domain may correspond to the aforementioned Figure 1a to Figure 1d In network domain B.

[0095] when Figure 2 The information processing method shown is applied to Figure 1a or Figure 1b or Figure 1c In the network scenario shown in FIG. 1 , the second network device and the third network device are boundary devices connected to a second network domain, wherein the second network domain may be Figure 1a to Figure 1c In network domain A.

[0096] when Figure 2 The method shown is applied to Figure 1a In the application scenario shown in the figure, the second network device and the third network device may correspond to Figure 1a RTA and RTB are shown. Figure 2 The method shown is applied to Figure 1b In the application scenario shown in the figure, the second network device and the third network device may correspond to Figure 1b RTA and RTB are shown. Figure 2 The method shown is applied to Figure 1c In the application scenario shown in the figure, the second network device and the third network device may correspond to Figure 1c RTA and RTC are shown. Figure 2 The method shown is applied to Figure 1dIn the application scenario shown in the figure, the second network device and the third network device may correspond to Figure 1d RTA and RTB shown.

[0097] when Figure 2 The method shown is applied to Figure 1a In the application scenario shown in FIG. 1 , the first bandwidth value may be Figure 1a The link RTA-RT1 shown in the figure provides a bandwidth for sending traffic to the target prefix. The second bandwidth value may be Figure 1a The bandwidth provided by link RTB-RT2 for sending traffic to the target prefix is ​​shown.

[0098] when Figure 2 The method shown is applied to Figure 1b In the application scenario shown in FIG. 1 , the first bandwidth value may be Figure 1b The link RTA-RT1 shown in the figure provides a bandwidth for sending traffic to the target prefix. The second bandwidth value may be Figure 1b The bandwidth provided by link RTB-RT2 for sending traffic to the target prefix is ​​shown.

[0099] when Figure 2 The method shown is applied to Figure 1c In the application scenario shown in FIG. 1 , the first bandwidth value may be Figure 1c The link RTA-RT1 shown in the figure provides a bandwidth for sending traffic to the target prefix. The second bandwidth value may be Figure 1c The bandwidth provided by link RTC-RT3 for sending traffic to the target prefix is ​​shown.

[0100] when Figure 2 The method shown is applied to Figure 1d In the application scenario shown in FIG. 1 , the first bandwidth value may be Figure 1d The link RTA-RT1 shown in the figure provides a bandwidth for sending traffic to the target prefix. The second bandwidth value may be Figure 1d The bandwidth provided by link RTB-RT1 for sending traffic to the target prefix is ​​shown.

[0101] Next, the specific implementation method of S101 is introduced.

[0102] In one example, the first network device may receive an IS-IS message announced by the second network device, and the IS-IS message carries the first bandwidth value. After receiving the IS-IS message, the first network device may parse the IS-IS message to obtain the first bandwidth value. The embodiment of the present application does not specifically limit the carrying position of the first bandwidth value in the IS-IS message. The first bandwidth value may, for example, be carried by any available field in the IS-IS message. In a specific example, the IS-IS message may include a prefix TLV, and the prefix TLV may include a first sub-TLV. The first sub-TLV may, for example, be used to carry the first bandwidth value.

[0103] Regarding the first sub-TLV, its structure can be referred to Figure 3 , Figure 3 This is a schematic diagram of the structure of a sub-TLV provided in an embodiment of the present application. Figure 3 As shown, the first TLV includes a type field 310, a length field 320 and a value field 330, wherein the value field 330 further includes a type field 331, a greatest common divisor (GCD) field 332 and a bandwidth value field 333. Wherein:

[0104] The type field 310 is used to indicate that the first sub-TLV is used to carry a bandwidth value.

[0105] The length field 320 indicates the length of the value field 330 .

[0106] The type field 331 may be used to indicate the purpose of the bandwidth value. For example, the type field 331 may indicate non-equal load sharing. The first network device may perform S103 based on the value of the type field 331 to implement non-equal load sharing.

[0107] The GCD field 332 may be used to indicate the unit of the bandwidth value. For example, the value of the GCD field 332 is 100, indicating that the unit of the bandwidth value is one hundred bytes.

[0108] The bandwidth value field 333 is used to carry a specific bandwidth value. For example, if the value carried by the bandwidth value field 333 is 100, then the first bandwidth value is identified as: 100 bytes.

[0109] Figure 3 It is only shown for the purpose of understanding the present solution and does not constitute a limitation on the specific structure of the first sub-TLV. For example, in another example, the value field 330 may not include the type field 331, but include the GCD field 332 and the bandwidth value field 333, and the first bandwidth value is carried through the GCD field 332 and the bandwidth value field 333.

[0110] Regarding the prefix TLV, it can be an extended Internet Protocol Reachability (Extended IP reachability) prefix TLV, it can be a multi-topology IP Reach (Multi-Topology IP Reach, MT IP Reach) prefix TLV, it can also be an Internet Protocol version 6 IP Reach (Internet Protocol version 6 IP Reach, IPv6 IP Reach) prefix TLV, or it can be an MT IPv6 IP Reach prefix TLV.

[0111] In another example, the first network device may receive an OSPF message announced by the second network device, and the OSPF message carries the first bandwidth value. After receiving the OSPF message, the first network device may parse the OSPF message to obtain the first bandwidth value. The embodiment of the present application does not specifically limit the carrying position of the first bandwidth value in the OSPF message. The first bandwidth value may, for example, be carried by any available field in the OSPF message. In a specific example, the OSPF message may include a prefix TLV, and the prefix TLV may include a second sub-TLV, which may, for example, be used to carry the first bandwidth value. Among them, the structure of the second sub-TLV may be the same as the structure of the aforementioned first sub-TLV. Therefore, regarding the structure of the second sub-TLV, reference may be made to the previous description of the first sub-TLV, and no repeated description will be made here.

[0112] Regarding the prefix TLV, it can be an inter-area-prefix TLV (Inter-Area-Prefix TLV), an extended prefix TLV (External-Prefix TLV), or an intra-area-prefix TLV (Intra-Area-Prefix TLV), which is not specifically limited in the embodiments of the present application.

[0113] The specific implementation of S102 is similar to the specific implementation of S101. In one example, the first network device may receive an IS-IS message sent by a third network device, the IS-IS message including the second bandwidth value, and the second bandwidth value may be carried, for example, by the third sub-TLV of the prefix TLV included in the IS-IS message. In another example, the first network device may receive an OSPF message sent by a third network device, the OSPF message including the second bandwidth value, and the second bandwidth value may be carried, for example, by the fourth sub-TLV of the prefix TLV included in the OSPF message.

[0114] S103: Determine, according to the first bandwidth value and the second bandwidth value, weights for sending traffic with the destination prefix as a destination to the second network device and the third network device respectively.

[0115] After the first network device receives the first bandwidth value and the second bandwidth value, it can determine the weight of sending the traffic with the destination prefix as the destination to the second network device and the third network device respectively according to the first bandwidth value and the second bandwidth value. In an embodiment of the present application, in order to avoid the serious packet loss after the traffic is sent to the second network device due to the reduction of the bandwidth that the second network device can provide for sending traffic to the destination prefix. The first network device can send the received traffic with the destination prefix as the destination to the second network device and the third network device respectively, thereby reducing the traffic received by the second network device, thereby avoiding traffic packet loss. Specifically, the first network device can determine the weight of sending the traffic with the destination prefix as the destination to the second network device and the third network device respectively according to the first bandwidth value and the second bandwidth value. In this way, when the first network device forwards traffic with the destination prefix as the destination, it can send the aforementioned traffic to the second network device and the third network device based on the aforementioned weight, so that the traffic actually received by the second network device and the third network device matches the bandwidth at which they can send traffic to the target prefix, thereby reasonably utilizing the bandwidth provided by the second network device and the third network device for sending traffic to the target prefix, so as to avoid the situation where the bandwidth provided by the second network device for sending traffic to the target prefix is ​​insufficient to carry the traffic received by itself with the destination prefix as the destination, thereby effectively avoiding service traffic packet loss.

[0116] As before for Figure 1a , Figure 1b and Figure 1d As can be seen from the description, in the conventional technology, the first network device will send the traffic with the destination prefix as the destination to the second network device, but will not send the traffic with the destination prefix as the destination to the fourth network device with which it has an equal load sharing relationship. Figure 2 The method shown is applied to Figure 1a , Figure 1b or Figure 1dIn the application scenario shown, the first network device sends traffic with the destination prefix as the destination to the third network device through the fourth network device. That is, the first network device can send part of the traffic to the fourth network device which is an equivalent load sharing device to itself. It is precisely because the first network device sends traffic with the destination prefix as the destination to the third network device through the fourth network device, therefore, the weight of the traffic with the destination prefix as the destination sent by the first network device to the third network device refers to the weight of the traffic with the destination prefix as the destination sent by the first network device to the fourth network device. Among them, when Figure 2 The method shown is applied to Figure 1a In the application scenario shown, the fourth network device may be an RTD. Figure 2 The method shown is applied to Figure 1b In the application scenario shown, the fourth network device may be RTF. Figure 2 The method shown is applied to Figure 1d In the application scenario shown, the fourth network device may be an RTD.

[0117] Next, the specific implementation method of S103 is introduced.

[0118] For the convenience of description, in the following description, "traffic with the aforementioned target prefix as the destination" is referred to as "traffic".

[0119] when Figure 2 The method shown is applied to Figure 1a or Figure 1d In the application scenario shown, the weight of sending traffic with the destination prefix as the destination to the second network device can be determined as: And determine the weight of sending the traffic with the destination prefix as the destination to the third network device as: Where: m is the first bandwidth value, n is the second bandwidth value. Figure 2 The method shown is applied to Figure 1a In the application scenario shown, it can be combined with Figure 4a To understand, Figure 4a A schematic diagram of an exemplary application scenario provided in an embodiment of the present application. Figure 2 The method shown is applied to Figure 1d In the application scenario shown, it can be combined with Figure 4b To understand, Figure 4b A schematic diagram of an exemplary application scenario provided for an embodiment of the present application.

[0120] like Figure 4a and 4bAs shown in the figure, RTC and RTD are equivalent load sharing nodes. The traffic received by RTC from network domain G is X, and the traffic received by RTD from network domain G is also X. Correspondingly, the traffic received by RTB from RTD is X. Assuming that a part (Y) of the traffic X received by RTC is forwarded to RTB through RTD, then: the weight of sending traffic to the third network device RTB is The weight of sending traffic to the second network device RTA is:

[0121] If RTC sends traffic Y to RTD, then the traffic transmitted by the link RTC-RTA is XY, and the traffic transmitted by the link RTD-RTB is X+Y. That is, the traffic received by RTA is XY, and the traffic received by RTB is X+Y. In order to match the traffic forwarded by RTA and RTB with the bandwidth of the forwarded traffic they provide, the following formula (1) should be satisfied:

[0122]

[0123] By transforming formula (1), we can get the following formula (2):

[0124] (nm)*X=(n+m)*Y Formula (2)

[0125] Furthermore, by transforming formula (2), we can obtain formula (3):

[0126]

[0127] According to formula (3), the weight of sending traffic to the third network device is Further, the weight of sending traffic to the second network device is determined to be In one example, considering that the link bandwidth between the first network device and the fourth network device is limited, when determining the weight of sending traffic to the third network device, the bandwidth of the link between the first network device and the fourth network device may also be considered, thereby avoiding sending too much traffic to the fourth network device and causing packet loss when the traffic is transmitted between the first network device and the fourth network device.

[0128] As a specific example, assuming that the bandwidth of the link between the first network device and the fourth network device is j, and the bandwidth of the link between the first network device and the second network device is k, then if the This means that the weight of diverting traffic to the fourth network device is reasonable, so the weight of sending traffic to the third network device can be determined as Determine the weight for sending traffic to the second network device as If the This means that the weight of the traffic diverted to the fourth network device is too large, so the weight of sending traffic to the third network device can be determined to be Determine the weight for sending traffic to the second network device as

[0129] In one example, before executing S103, the first network device may also determine whether the first traffic tuning condition is satisfied, and when the aforementioned first traffic tuning condition is satisfied, S103 is executed again. The aforementioned first traffic tuning condition refers to a condition that if equal-cost load balancing is continued, serious packet loss of traffic will occur. In one example, when the first bandwidth value is less than the second bandwidth value, the first bandwidth value is not 0, and the difference between the first bandwidth value and the second bandwidth value is large, continuing to use the traditional equal-cost load balancing solution will cause serious packet loss in the link RTA-RT1. Therefore, in one example, the first traffic tuning condition may be: the first bandwidth value is less than the second bandwidth value, the first bandwidth value is not 0, and the difference between the first bandwidth value and the second bandwidth value is greater than or equal to the first bandwidth threshold. In other words, the first network device may execute S103 again when it is determined that the first bandwidth value is less than the second bandwidth value, the first bandwidth value is not 0, and the difference between the first bandwidth value and the second bandwidth value is greater than or equal to the first bandwidth threshold.

[0130] The embodiment of the present application does not specifically limit the first bandwidth threshold. The first bandwidth threshold can be determined according to actual conditions. For example, the first bandwidth threshold can be 0.4 times the second bandwidth value, that is, the first bandwidth value<the second bandwidth value*0.6.

[0131] In a specific example, after executing S103, the first network device may also save in the forwarding table entries the weights of sending traffic with the destination prefix as the destination to the second network device and the third network device, respectively, so that in the traffic forwarding stage, the weights of sending traffic to the second network device and the third network device can be determined based on the forwarding table entries, so as to forward the received traffic based on the weights.

[0132] when Figure 2 The method shown is applied to Figure 1b In the application scenario shown, in addition to receiving the aforementioned first bandwidth value and second bandwidth value, the first network device can also receive a third bandwidth value sent by the fifth network device and a fourth bandwidth value sent by the sixth network device. The third bandwidth value indicates the bandwidth of the traffic sent by the fifth network device to the destination prefix, and the fourth bandwidth value indicates the bandwidth of the traffic sent by the sixth network device to the destination prefix.

[0133] The specific implementation of the first network device receiving the third bandwidth value and the fourth bandwidth value is based on the same principle as the principle of the first network device receiving the first bandwidth value. Therefore, for the specific implementation of the first network device receiving the third bandwidth value and the fourth bandwidth value, reference can be made to the description of the first network device receiving the first bandwidth value in the previous text, and no repeated description is given here.

[0134] Wherein: the fifth network device and the aforementioned second network device are both connected to the first network device, and the fifth network device and the second network device are mutually load-sharing devices. In other words, the traffic received by the first network device can be load-shared to the second network device and the fifth network device for forwarding. The third network device and the sixth network device are both connected to the fourth network device, and the third network device and the sixth network device can be mutually load-sharing devices. In other words, the traffic received by the fourth network device can be load-shared to the third network device and the sixth network device for forwarding. Figure 1b In the scenario shown, the first network device, the second network device, the third network device, the fourth network device, the fifth network device and the sixth network device may correspond to: RTE, RTA, RTB, RTF, RTC and RTD respectively.

[0135] Accordingly, when S103 is specifically implemented, the weight of sending the traffic with the destination prefix as the destination to the second network device, the fifth network device, and the fourth network device can be determined according to the first bandwidth value, the second bandwidth value, the third bandwidth value, and the fourth bandwidth value. That is, the traffic originally load-shared by the second network device and the fifth network device is load-shared by the second network device, the fifth network device, and the fourth network device, thereby reducing the traffic received by the second network device, and accordingly, avoiding serious traffic packet loss due to the bandwidth value provided by the second network device being insufficient to carry the traffic received by itself.

[0136] In one example, before executing S103, the first network device may also determine whether the second traffic tuning condition is met, and when the second traffic tuning condition is met, S103 is executed again. The second traffic tuning condition refers to a condition that if equal-cost load balancing is continued, serious packet loss will occur. In one example, when the first total bandwidth provided by the first network device is less than the second total bandwidth provided by the fourth network device, and the first total bandwidth is not equal to 0, and the difference between the first total bandwidth and the second total bandwidth is greater than or equal to the second bandwidth threshold, continuing to use the traditional equal-cost load balancing solution will cause serious packet loss in the link RTA-RT1. The first total bandwidth is: the sum of the first bandwidth value and the third bandwidth value, and the second total bandwidth is: the sum of the second bandwidth value and the fourth bandwidth value. Therefore, in one example, the second traffic tuning condition may be: the first total bandwidth provided by the first network device is less than the second total bandwidth provided by the fourth network device, and the first total bandwidth is not equal to 0, and the difference between the first total bandwidth and the second total bandwidth is greater than or equal to the second bandwidth threshold. In other words, the first network device may execute S103 again if it is determined that the first total bandwidth provided by the first network device is less than the second total bandwidth provided by the fourth network device, and the first total bandwidth is not equal to 0, and the difference between the first total bandwidth and the second total bandwidth is greater than or equal to the second bandwidth threshold.

[0137] The embodiment of the present application does not specifically limit the second bandwidth threshold. The second bandwidth threshold can be determined according to actual conditions. For example, the second bandwidth threshold can be 0.4 times the second total bandwidth, that is, the first total bandwidth < the second total bandwidth*0.6.

[0138] In a specific example, “determining, according to the first bandwidth value, the second bandwidth value, the third bandwidth value, and the fourth bandwidth value, the weight of sending traffic with the destination prefix as the destination to the second network device, the fifth network device, and the fourth network device” may include:

[0139] Determine the weight of sending traffic with the destination prefix as the destination to the fourth network device as:

[0140] Determine the weight of sending traffic with the destination prefix as the destination to the second network device as follows:

[0141] Determine the weight of sending traffic with the destination prefix as the destination to the fifth network device as follows: in:

[0142] a is the first bandwidth value, b is the second bandwidth value, c is the third bandwidth value, and d is the fourth bandwidth value.

[0143] Can be combined Figure 4c To understand, Figure 4c A schematic diagram of an exemplary application scenario provided for an embodiment of the present application.

[0144] like Figure 4c As shown in the figure, the link RTG-RTE and the link RTH-RTF are equal-cost load-sharing links. The traffic received by RTE via the link RTG-RTE is X, and the traffic received by RTF via the link RTH-RTF is also X. Assume that part (Y) of the traffic X received by RTE is forwarded to RTF, which forwards it to the destination of the traffic via RTB and RTD. Then: The weight of sending traffic to the first network device RTF is The weight of sending traffic to the second network device RTA is: Weight of sending traffic to the fifth network device RTC

[0145] for:

[0146] If RTE sends traffic Y to RTF, then the traffic transmitted by links RTE-RTA and RTE-RTC is XY, and the traffic transmitted by links RTF-RTB and RTF-RTD is X+Y. In order to match the traffic forwarded by RTA, RTB, RTC, and RTD with the bandwidth of the forwarded traffic they provide, the following formula (4) should be satisfied:

[0147]

[0148] By transforming formula (4), we can get the following formula (5):

[0149] (b+dac)*X=(a+b+c+d)*Y Formula (5)

[0150] Furthermore, by transforming formula (5), we can obtain formula (6):

[0151]

[0152] According to formula (6), the weight of sending traffic to the fourth network device is Further, the weight of sending traffic to the second network device is determined to be The weight for sending traffic to the fourth network device is determined as:

[0153] In one example, considering that the link bandwidth between the first network device and the fourth network device is limited, when determining the weight of sending traffic to the fourth network device, the bandwidth of the link between the first network device and the fourth network device may also be considered, thereby avoiding sending too much traffic to the fourth network device and causing packet loss when the traffic is transmitted between the first network device and the fourth network device.

[0154] As a specific example, assuming that the bandwidth of the link between the first network device and the fourth network device is e, and the bandwidth of the link between the first network device and the second network device is f, then if the This means that the weight of the traffic diverted to the fourth network device is reasonable, so the weight of sending traffic to the fourth network device can be determined as Determine the weight for sending traffic to the second network device as And determine the weight of sending traffic to the fifth network device as If the This means that the weight of the traffic diverted to the fourth network device is too large, so the weight of sending traffic to the fourth network device can be determined to be Determine the weight of sending traffic with the destination prefix as the destination to the second network device as follows: Determine the weight of sending traffic with the destination prefix as the destination to the fifth network device as follows:

[0155] when Figure 2 The method shown is applied to Figure 1c In the application scenario shown, the second network device and the third network device are connected to the first network device respectively. In addition, the first network device can also be connected to the seventh network device. Among them, the second network device, the third network device and the seventh network device can be load sharing devices. The traffic received by the first network device can be load shared to the second network device, the third network device and the seventh network device for forwarding. The first network device, the second network device, the third network device and the seventh network device can correspond to Figure 1c In the scenario shown: RTG, RTA, RTC and RTE.

[0156] In this case, in addition to receiving the aforementioned first bandwidth value and second bandwidth value, the first network device can also receive the fifth bandwidth value sent by the seventh network device. The fifth bandwidth value indicates the bandwidth of the traffic sent by the seventh network device to the destination prefix. The implementation principle of the first network device receiving the fifth bandwidth value is the same as the principle of the first network device receiving the first bandwidth value. Therefore, for the specific implementation of the first network device receiving the fifth bandwidth value, please refer to the description of the first network device receiving the first bandwidth value in the previous text, and no repeated description will be made here.

[0157] Accordingly, in this scenario, when S103 is specifically implemented, the weights of sending the traffic with the destination prefix as the destination to the second network device, the third network device, and the seventh network device can be determined according to the first bandwidth value, the second bandwidth value, and the fifth bandwidth value. That is, when the traffic received by the first network device can be load-shared and forwarded to three network devices (the second network device, the third network device, and the seventh network device), the weights of sending the traffic to the three network devices can be determined according to the bandwidth values ​​provided by the three network devices, so that the bandwidth actually provided by the three network devices matches the traffic actually carried by them, avoiding traffic packet loss.

[0158] In a specific example, the sum of the first bandwidth value, the second bandwidth value and the fifth bandwidth value is called the third total bandwidth. In order to match the bandwidth actually provided by the above three network devices with the traffic actually carried by them, the weight of sending traffic with the target prefix as the destination to the second network device can be determined as: the ratio of the first bandwidth value to the third total bandwidth, the weight of sending traffic with the target prefix as the destination to the third network device can be determined as: the ratio of the second bandwidth value to the third total bandwidth; the weight of sending traffic with the target prefix as the destination to the seventh network device can be determined as: the ratio of the fifth bandwidth value to the third total bandwidth.

[0159] In a specific example, after executing S103, the first network device may also save in the forwarding table entries the weights of sending traffic with the destination prefix as the destination to the second network device, the third network device, and the seventh network device, respectively, so that in the traffic forwarding stage, the weights of sending traffic to the second network device, the third network device, and the seventh network device are determined based on the forwarding table entries, so as to forward the received traffic based on the weights.

[0160] Based on the information processing method provided in the above embodiment, the present application embodiment also provides a corresponding device, see Figure 5 , which is a structural schematic diagram of an information processing device provided in an embodiment of the present application. Figure 5 The information processing device 500 shown can be applied to a first network device to execute the information processing method provided by the above method embodiment and executed by the first network device. The information processing device 500 may include a receiving unit 501 and a processing unit 502 .

[0161] The receiving unit 501 is configured to receive a first bandwidth value sent by a second network device, the first bandwidth value indicating a bandwidth for the second network device to send traffic to a destination prefix; and receive a second bandwidth value sent by a third network device, the second bandwidth value indicating a bandwidth for the third network device to send traffic to the destination prefix;

[0162] The processing unit 502 is configured to determine, according to the first bandwidth value and the second bandwidth value, weights for sending traffic with the destination prefix as a destination to the second network device and the third network device respectively.

[0163] In a possible implementation manner, the first network device, the second network device, and the third network device all belong to a first network domain, and the second network device and the third network device are boundary devices connected to a second network domain.

[0164] In a possible implementation, the first network device sends traffic with the destination prefix as the destination to the third network device through the fourth network device, and the first network device and the fourth network device are equal-cost load sharing devices.

[0165] In a possible implementation, the processing unit 502 is configured to determine a weight for sending the traffic with the destination prefix as the destination to the second network device as follows: Determine the weight for sending the traffic with the destination prefix as the destination to the third network device as follows: Wherein: it is determined that m is the first bandwidth value, and n is the second bandwidth value.

[0166] In a possible implementation, the processing unit 502 is configured to: send to the second network device a weight of the destination traffic with the destination prefix as: The weight for sending the destination traffic with the destination prefix as the destination to the third network device is: Wherein: the k is the bandwidth of the link between the first network device and the second network device, and the j is the bandwidth of the link between the first network device and the fourth network device.

[0167] In a possible implementation: the processing unit 502 is further used to determine that the first bandwidth value is less than the second bandwidth value, the first bandwidth value is not 0, and the difference between the first bandwidth value and the second bandwidth value is greater than or equal to a first bandwidth threshold before determining the weight of sending traffic with the destination prefix as the destination to the second network device and the third network device respectively.

[0168] In a possible implementation, the receiving unit 501 is further used to receive a third bandwidth value sent by a fifth network device, the third bandwidth value indicating a bandwidth for the fifth network device to send traffic to a destination prefix; and receive a fourth bandwidth value sent by a sixth network device, the fourth bandwidth value indicating a bandwidth for the sixth network device to send traffic to the destination prefix; the processing unit 502 is used to determine, based on the first bandwidth value, the second bandwidth value, the third bandwidth value and the fourth bandwidth value, a weight for sending traffic with the destination prefix as a destination to the second network device, the fifth network device and the fourth network device, respectively; wherein: the second network device and the fifth network device are respectively connected to the first network device, the third network device and the sixth network device are respectively connected to the fourth network device, and the traffic with the destination prefix as a destination received by the fourth network device is forwarded via the third network device and the sixth network device.

[0169] In a possible implementation, the processing unit 502 is further used to determine, before determining the weights of sending traffic with the destination prefix as the destination to the second network device, the fifth network device, and the fourth network device respectively, that a first total bandwidth provided by the first network device is less than a second total bandwidth provided by the fourth network device, and that the first total bandwidth is not equal to 0, and that a difference between the first total bandwidth and the second total bandwidth is greater than or equal to a second bandwidth threshold, wherein the first total bandwidth is: the sum of the first bandwidth value and the third bandwidth value, and the second total bandwidth is: the sum of the second bandwidth value and the fourth bandwidth value.

[0170] In a possible implementation, the processing unit 502 is configured to determine a weight for sending traffic with the destination prefix as a destination to the fourth network device as follows: Determine the weight of sending traffic with the destination prefix as the destination to the second network device as follows: Determine the weight of sending traffic with the destination prefix as the destination to the fifth network device as follows: Wherein: a is the first bandwidth value, b is the second bandwidth value, c is the third bandwidth value, and d is the fourth bandwidth value.

[0171] In a possible implementation, the processing unit 502 is configured to determine a weight for sending traffic with the destination prefix as a destination to the fourth network device as follows: Determine the weight of sending traffic with the destination prefix as the destination to the second network device as follows: Determine the weight of sending traffic with the destination prefix as the destination to the fifth network device as follows: Wherein: f is the sum of the bandwidth of the link between the first network device and the second network device and the bandwidth of the link between the first network device and the fifth network device, and e is the bandwidth of the link between the first network device and the fourth network device.

[0172] In a possible implementation, the second network device and the third network device are connected to the first network device respectively, and the first network device is also connected to the seventh network device. The receiving unit 501 is further used to receive a fifth bandwidth value sent by the seventh network device, where the fifth bandwidth value indicates a bandwidth for the seventh network device to send traffic to a destination prefix; and the processing unit 502 is used to determine, based on the first bandwidth value, the second bandwidth value, and the fifth bandwidth value, a weight for sending traffic with the destination prefix as a destination to the second network device, the third network device, and the seventh network device, respectively.

[0173] In one possible implementation, according to processing unit 502, it is used to: determine the weight of sending traffic with the target prefix as the destination to the second network device as: the ratio of the first bandwidth value to the third total bandwidth, the third total bandwidth being the sum of the first bandwidth value, the second bandwidth value and the fifth bandwidth value; determine the weight of sending traffic with the target prefix as the destination to the third network device as: the ratio of the second bandwidth value to the third total bandwidth; determine the weight of sending traffic with the target prefix as the destination to the seventh network device as: the ratio of the fifth bandwidth value to the third total bandwidth.

[0174] In a possible implementation manner, the receiving unit 501 is configured to: receive an Intermediate System to Intermediate System (IS-IS) message advertised by the second network device, where the IS-IS message includes the first bandwidth value.

[0175] In a possible implementation manner, the IS-IS message includes a prefix type length value TLV, the prefix TLV includes a first sub-TLV, and the first sub-TLV includes the first bandwidth value.

[0176] In a possible implementation, the receiving unit 501 is configured to receive an Open Shortest Path First (OSPF) message advertised by the second network device, where the OSPF message includes the first bandwidth value.

[0177] In a possible implementation manner, the OSPF message includes a prefix type length value TLV, the prefix TLV includes a second sub-TLV, and the second sub-TLV includes the first bandwidth value.

[0178] In a possible implementation, the processing unit 502 is further configured to: store in a forwarding table entry the weights of sending traffic with the destination prefix as the destination to the second network device and the third network device respectively.

[0179] It should be noted that the hardware structure of the information processing device mentioned above can be as follows: Figure 6 The structure shown, Figure 6 A schematic diagram of the structure of a device provided in an embodiment of the present application.

[0180] See also Figure 6 As shown, the device 600 includes: a processor 610, a communication interface 620 and a memory 630. The number of the processor 610 in the device 600 can be one or more. Figure 6 In the embodiment of the present application, the processor 610, the communication interface 620 and the memory 630 may be connected via a bus system or other means, wherein: Figure 6 The connection via bus system 640 is taken as an example.

[0181] The processor 610 may be a central processing unit (CPU), a network processor (NP) or a combination of a CPU and a NP. The processor 610 may further include a hardware chip. The hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD) or a combination thereof. The PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL) or any combination thereof.

[0182] The memory 630 may include a volatile memory (English: volatile memory), such as a random-access memory (RAM); the memory 630 may also include a non-volatile memory (English: non-volatile memory), such as a flash memory (English: flash memory), a hard disk drive (HDD) or a solid-state drive (SSD); the memory 630 may also include a combination of the above-mentioned types of memory. The memory 630 may, for example, store the weight of sending the traffic with the destination prefix as the destination to the second network device and the third network device respectively.

[0183] Optionally, the memory 630 stores an operating system and a program, an executable module or a data structure, or a subset thereof, or an extended set thereof, wherein the program may include various operating instructions for implementing various operations. The operating system may include various system programs for implementing various basic services and processing hardware-based tasks. The processor 610 may read the program in the memory 630 to implement the information processing method provided in the embodiment of the present application.

[0184] The bus system 640 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus. The bus system 640 may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 6 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0185] The embodiment of the present application also provides a computer-readable storage medium, including instructions or computer programs, which, when executed on a computer, enable the computer to execute the information processing method provided in the above embodiment.

[0186] The embodiments of the present application also provide a computer program product including instructions or a computer program, which, when executed on a computer, enables the computer to execute the information processing method provided in the above embodiments.

[0187] The terms "first", "second", "third", "fourth", etc. (if any) in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments described herein can be implemented in an order other than that illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0188] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0189] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of units is only a logical business division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

[0190] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0191] In addition, each business unit in each embodiment of the present application can be integrated into a processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of software business units.

[0192] If the integrated unit is implemented in the form of a software business unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk and other media that can store program codes.

[0193] Those skilled in the art will appreciate that in one or more of the above examples, the services described in the present invention may be implemented using hardware, software, firmware, or any combination thereof. When implemented using software, the services may be stored in a computer-readable medium or transmitted as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein communication media include any media that facilitates the transmission of computer programs from one place to another. Storage media may be any available media that can be accessed by a general-purpose or special-purpose computer.

[0194] The above specific implementation modes further describe the objectives, technical solutions and beneficial effects of the present invention in detail. It should be understood that the above are only specific implementation modes of the present invention.

[0195] The above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, a person of ordinary skill in the art should understand that the technical solutions described in the aforementioned embodiments may still be modified, or some of the technical features thereof may be replaced by equivalents. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the scope of the technical solutions of the embodiments of the present application.

Claims

1. An information processing method, characterized in that: Applied to a first network device, the method comprises: Receiving a first bandwidth value sent by a second network device, where the first bandwidth value indicates a bandwidth for the second network device to send traffic to a destination prefix; receiving a second bandwidth value sent by a third network device, where the second bandwidth value indicates a bandwidth at which the third network device sends traffic to the destination prefix; According to the first bandwidth value and the second bandwidth value, weights for sending traffic with the destination prefix as a destination to the second network device and the third network device respectively are determined.

2. The method according to claim 1, characterized in that The first network device, the second network device and the third network device all belong to a first network domain, and the second network device and the third network device are boundary devices connected to a second network domain.

3. The method according to claim 1 or 2, characterized in that: The first network device sends traffic with the destination prefix as the destination to the third network device through the fourth network device, and the first network device and the fourth network device are equal-cost load sharing devices.

4. The method according to claim 3, characterized in that Determining, according to the first bandwidth value and the second bandwidth value, weights for sending traffic with the destination prefix as a destination to the second network device and the third network device, respectively, includes: Determine the weight for sending the traffic with the destination prefix as the destination to the second network device as follows: Determine the weight for sending the traffic with the destination prefix as the destination to the third network device as follows: in: Determine that m is the first bandwidth value, and n is the second bandwidth value.

5. The method according to claim 3, characterized in that: Determining, according to the first bandwidth value and the second bandwidth value, weights for sending traffic with the destination prefix as a destination to the second network device and the third network device, respectively, includes: The weight for sending the destination traffic with the destination prefix as the destination to the second network device is: The weight for sending the destination traffic with the destination prefix as the destination to the third network device is: in: The k is the bandwidth of the link between the first network device and the second network device, and the j is the bandwidth of the link between the first network device and the fourth network device.

6. The method according to claim 4 or 5, characterized in that: Before determining the weights for sending traffic with the destination prefix as the destination to the second network device and the third network device respectively, the method further includes: It is determined that the first bandwidth value is less than the second bandwidth value, the first bandwidth value is not 0, and a difference between the first bandwidth value and the second bandwidth value is greater than or equal to a first bandwidth threshold.

7. The method according to claim 3, characterized in that The method further comprises: receiving a third bandwidth value sent by a fifth network device, wherein the third bandwidth value indicates a bandwidth for sending traffic by the fifth network device to a destination prefix; receiving a fourth bandwidth value sent by a sixth network device, wherein the fourth bandwidth value indicates a bandwidth for the sixth network device to send traffic to the destination prefix; Determining, according to the first bandwidth value and the second bandwidth value, weights for sending traffic with the destination prefix as a destination to the second network device and the third network device, respectively, includes: Determine, according to the first bandwidth value, the second bandwidth value, the third bandwidth value, and the fourth bandwidth value, weights for sending traffic with the destination prefix as a destination to the second network device, the fifth network device, and the fourth network device, respectively; in: The second network device and the fifth network device are connected to the first network device respectively, the third network device and the sixth network device are connected to the fourth network device respectively, and the traffic with the target prefix as the destination received by the fourth network device is forwarded via the third network device and the sixth network device.

8. The method according to claim 7, characterized in that Before determining the weights of sending traffic with the destination prefix as the destination to the second network device, the fifth network device, and the fourth network device respectively, the method further includes: Determine that a first total bandwidth provided by the first network device is less than a second total bandwidth provided by the fourth network device, and that the first total bandwidth is not equal to 0, and that a difference between the first total bandwidth and the second total bandwidth is greater than or equal to a second bandwidth threshold, wherein the first total bandwidth is: the sum of the first bandwidth value and the third bandwidth value, and the second total bandwidth is: the sum of the second bandwidth value and the fourth bandwidth value.

9. The method according to claim 7 or 8, characterized in that: Determining weights for sending traffic with the destination prefix as a destination to the second network device, the fifth network device, and the fourth network device, respectively, includes: Determine the weight of sending traffic with the destination prefix as the destination to the fourth network device as: Determine the weight of sending traffic with the destination prefix as the destination to the second network device as follows: Determine the weight of sending traffic with the destination prefix as the destination to the fifth network device as follows: in: a is the first bandwidth value, b is the second bandwidth value, c is the third bandwidth value, and d is the fourth bandwidth value.

10. The method according to claim 7 or 8, characterized in that: Determining weights for sending traffic with the destination prefix as a destination to the second network device, the fifth network device, and the fourth network device, respectively, includes: Determine the weight of sending traffic with the destination prefix as the destination to the fourth network device as: Determine the weight of sending traffic with the destination prefix as the destination to the second network device as follows: Determine the weight of sending traffic with the destination prefix as the destination to the fifth network device as follows: in: The f is the sum of the bandwidth of the link between the first network device and the second network device and the bandwidth of the link between the first network device and the fifth network device, and the e is the bandwidth of the link between the first network device and the fourth network device.

11. The method according to claim 1 or 2, characterized in that: The second network device and the third network device are connected to the first network device respectively, the first network device is also connected to a seventh network device, and the method further includes: receiving a fifth bandwidth value sent by the seventh network device, wherein the fifth bandwidth value indicates a bandwidth for the seventh network device to send traffic to a destination prefix; The determining, according to the first bandwidth value and the second bandwidth value, the weight of sending the traffic with the destination prefix as the destination to the second network device and the third network device respectively includes: According to the first bandwidth value, the second bandwidth value, and the fifth bandwidth value, weights for sending traffic with the destination prefix as a destination to the second network device, the third network device, and the seventh network device, respectively, are determined.

12. The method according to claim 11, characterized in that Determining, according to the first bandwidth value, the second bandwidth value, and the fifth bandwidth value, weights for sending traffic with the destination prefix as a destination to the second network device, the third network device, and the seventh network device, respectively, includes: Determine a weight for sending traffic with the target prefix as a destination to the second network device as: a ratio of the first bandwidth value to a third total bandwidth, where the third total bandwidth is a sum of the first bandwidth value, the second bandwidth value, and the fifth bandwidth value; Determine a weight for sending traffic with the target prefix as a destination to the third network device as: a ratio of the second bandwidth value to a third total bandwidth; The weight for sending traffic with the target prefix as a destination to the seventh network device is determined to be: a ratio of the fifth bandwidth value to the third total bandwidth.

13. The method according to any one of claims 1 to 12, characterized in that: Receiving a first bandwidth value sent by a second network device includes: An Intermediate System to Intermediate System (IS-IS) message announced by the second network device is received, where the IS-IS message includes the first bandwidth value.

14. The method according to claim 13, characterized in that The IS-IS message includes a prefix type length value TLV, the prefix TLV includes a first sub-TLV, and the first sub-TLV includes the first bandwidth value.

15. The method according to any one of claims 1 to 13, characterized in that: Receiving a first bandwidth value sent by a second network device includes: An Open Shortest Path First (OSPF) message announced by the second network device is received, where the OSPF message includes the first bandwidth value.

16. The method according to claim 15, characterized in that The OSPF message includes a prefix type length value TLV, the prefix TLV includes a second sub-TLV, and the second sub-TLV includes the first bandwidth value.

17. The method according to any one of claims 1 to 16, characterized in that: The method further comprises: The weights of sending the traffic with the destination prefix as the destination to the second network device and the third network device respectively are stored in the forwarding table entry.

18. An information processing device, characterized in that: Applied to a first network device, the apparatus comprises: A receiving unit, configured to receive a first bandwidth value sent by a second network device, the first bandwidth value indicating a bandwidth for the second network device to send traffic to a destination prefix; and receive a second bandwidth value sent by a third network device, the second bandwidth value indicating a bandwidth for the third network device to send traffic to the destination prefix; A processing unit is used to determine, according to the first bandwidth value and the second bandwidth value, a weight for sending traffic with the destination prefix as a destination to the second network device and the third network device respectively.

19. A device, characterized in that include: Processor and memory; The memory is used to store instructions or computer programs; The processor is used to execute the instructions or computer programs to perform the method according to any one of claims 1 to 17.

20. A computer-readable storage medium, characterized in that: The method comprises instructions or computer programs, which, when executed on a computer, cause the computer to execute the method according to any one of claims 1 to 17.

Images