Route processing method, device and system and computer readable storage medium

Abstract

The embodiment of the invention discloses a route processing method, device and system and a computer readable storage medium, and belongs to the technical field of communication. In the method, when a first network device receives a first aggregation route from a second network device, if the first aggregation route is not stored in a routing table of the first network device, it is indicated that the first aggregation route is a newly generated aggregation route, that is, the first aggregation route is in an aggregation process; in order to prevent traffic from being drained to the second network device in the aggregation process, the first network device sets the attribute of the first aggregation route to reduce the priority of the first aggregation route, so that the first network device does not preferably select the first aggregation route in the aggregation process of the first aggregation route, and the priority of the first aggregation route is reduced. And the problem of traffic packet loss in the aggregation process is correspondingly avoided. Accordingly, the first network device can automatically improve the priority of the first aggregation route when aggregation of the first aggregation route is completed, so that the first aggregation route normally participates in route selection.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of communication technology, and in particular to a routing processing method, device, system and computer-readable storage medium. Background Art

[0002] In large-scale networks, to avoid a very large routing table, multiple detailed routes can be aggregated into an aggregate route. When advertising routes later, only the aggregate route can be advertised without advertising specific detailed routes to save network resources.

[0003] In the related art, when a route aggregation end receives the first detailed route, it starts to generate an aggregated route and notifies the generated aggregated route to the neighbor. After receiving the aggregated route, the neighbor can use the aggregated route for route selection. However, since it is still in the aggregation process, if the neighbor selects the aggregated route when selecting a route, traffic will be transmitted to the route aggregation end, while the route aggregation end currently only receives a small number of detailed routes. This will cause most of the traffic to be discarded at the route aggregation end because the corresponding detailed route cannot be found. Summary of the invention

[0004] The embodiments of the present application provide a routing processing method, device, system and computer-readable storage medium, which can avoid the problem of traffic packet loss during the aggregation process of aggregate routing. The technical solution is as follows:

[0005] In a first aspect, a method for route processing is provided. In the method, a first network device receives a route advertisement message sent by a second network device, the route advertisement message includes a first aggregate route; in response to the first aggregate route not being stored in a route table of the first network device, the first network device sets an attribute of the first aggregate route to a first attribute value, the first attribute value indicating that the priority of the first aggregate route is a first priority; the first network device updates the attribute of the first aggregate route to a second attribute value, the second attribute value indicating that the priority of the first aggregate route is a second priority, and the second priority is greater than the first priority.

[0006] In an embodiment of the present application, when the first network device receives the first aggregate route from the second network device, if the first aggregate route is not stored in the routing table of the first network device, it indicates that the first aggregate route is a newly generated aggregate route, that is, the first aggregate route is in the aggregation process. At this time, in order to avoid the traffic being diverted to the second network device during the aggregation process, the first network device sets the attributes of the first aggregate route to reduce the priority of the first aggregate route, so that the first network device does not prefer the first aggregate route during the aggregation process of the first aggregate route, and accordingly avoids the problem of traffic packet loss during the aggregation process. Accordingly, the first network device can automatically increase the priority of the first aggregate route when the aggregation of the first aggregate route is completed, so that the first aggregate route can participate in the route selection normally.

[0007] Based on the method provided in the first aspect, in a possible implementation, a second aggregate route is stored in the routing table of the first network device, the first aggregate route and the second aggregate route have the same prefix, the priority of the second aggregate route is a third priority, and the third priority is greater than the first priority.

[0008] Since the third priority is greater than the first priority, the first network device will preferably use the second aggregate route to forward the message when selecting a route, thereby avoiding directing traffic to the second network device through the first aggregate route during the aggregation process, thereby avoiding packet loss at the second network device.

[0009] Based on the method provided in the first aspect, in a possible implementation manner, the second priority is greater than or equal to the third priority.

[0010] In this scenario, after the first network device updates the priority of the first aggregate route, since the second priority is greater than or equal to the third priority, the first network device can preferably forward the message by the first aggregate route, thereby achieving that the first aggregate route is not preferably forwarded during the aggregation process of the first aggregate route, but the first aggregate route is preferably forwarded after the first aggregate route aggregates a large number of detailed routes.

[0011] Based on the method provided in the first aspect, in a possible implementation manner, the first network device updates the attribute of the first aggregate route to the second attribute value. The implementation process may be: after a predetermined time, the first network device updates the attribute of the first aggregate route to the second attribute value.

[0012] By means of the above method, the first network device can automatically increase the priority of the first aggregate route after receiving the first aggregate route for a period of time.

[0013] Based on the method provided in the first aspect, in a possible implementation, the route announcement message also includes the first attribute of the first aggregate route, and the first attribute in the route announcement message is the second attribute value. In this scenario, the implementation process of the first network device setting the attribute of the first aggregate route to the first attribute value can be: adjusting the first attribute of the first aggregate route from the second attribute value to the first attribute value; accordingly, the implementation process of the first network device updating the attribute of the first aggregate route to the second attribute value can be: calling back the first attribute of the first aggregate route from the first attribute value to the second attribute value.

[0014] In the embodiment of the present application, after receiving the newly generated aggregate route, the first network device can adjust the attribute value of the existing route attribute (ie, the first attribute) in the aggregate route to reduce the priority of the first aggregate route. The first attribute can indicate the priority of the first aggregate route.

[0015] Based on the method provided in the first aspect, in a possible implementation, the first attribute includes a routing weight. In this scenario, the implementation process of adjusting the routing priority attribute of the first aggregate route from the second attribute value to the first attribute value may be: reducing the routing weight of the first aggregate route from the second attribute value to the first attribute value.

[0016] When the first attribute includes a route weight, the larger the route weight attribute value is, the more preferred the first aggregate route will be during route selection. Therefore, in order to avoid the first aggregate route being preferred during the aggregation process, the route weight attribute value in the first aggregate route may be lowered.

[0017] Based on the method provided in the first aspect, in a possible implementation, the first attribute includes a multi-exit identification MED. In this scenario, the implementation process of adjusting the route priority attribute of the first aggregate route from the second attribute value to the first attribute value may be: increasing the MED of the first aggregate route from the second attribute value to the first attribute value.

[0018] When the first attribute includes MED, the smaller the MED attribute value is, the more preferred the first aggregate route will be during route selection. Therefore, in order to avoid the first aggregate route being preferred during the aggregation process, the MED attribute value in the first aggregate route may be increased.

[0019] Based on the method provided in the first aspect, in a possible implementation, the first attribute includes a local priority. In this scenario, the implementation process of adjusting the route priority attribute of the first aggregate route from the second attribute value to the first attribute value may be: reducing the local priority of the first aggregate route from the second attribute value to the first attribute value.

[0020] When the first attribute includes local priority, the first aggregate route will be preferred when selecting a route because the larger the attribute value of the local priority is, the more preferred the first aggregate route will be. Therefore, in order to avoid the first aggregate route being preferred during the aggregation process, the attribute value of the local priority in the first aggregate route can be lowered.

[0021] Based on the method provided in the first aspect, in a possible implementation manner, the implementation process of the first network device setting the attribute of the first aggregate route to the first attribute value can be: adding a routing tag attribute to the first aggregate route, and setting the routing tag attribute of the first aggregate route to the first attribute value, the first attribute value indicating that the first network device delays using the first aggregate route for routing; accordingly, the implementation process of the first network device updating the attribute of the first aggregate route to the second attribute value can be: updating the routing tag attribute of the first aggregate route to the second attribute value, the second attribute value indicating that the first network device uses the first aggregate route for routing.

[0022] In an embodiment of the present application, after receiving the newly generated aggregate route, the first network device can add a new attribute (i.e., a routing tag attribute) to the aggregate route and set the attribute value of the routing tag attribute so that the first network device delays the use of the first aggregate route for routing, i.e., lowers the priority of the first aggregate route.

[0023] Based on the method provided in the first aspect, in a possible implementation manner, the routing advertisement message is a BGP update message.

[0024] Through the above manner, the first aggregate route may be an aggregate route based on the BGP protocol.

[0025] In a second aspect, a method for routing processing is provided, in which a second network device sends a first routing announcement message to a first network device, the first routing announcement message includes a first aggregate route and a first attribute value, and the first attribute value indicates that the priority of the first aggregate route is a first priority; the second network device adjusts the first attribute value to a second attribute value, and sends a second routing announcement message to the first network device, the second routing announcement message includes the first aggregate route and the second attribute value, and the second attribute value indicates that the priority of the first aggregate route is a second priority, and the second priority is greater than the first priority.

[0026] In the embodiment of the present application, when the second network device publishes the first aggregate route, it can set the attribute of the first aggregate route to the first attribute value during the aggregation process of the first aggregate route to reduce the priority of the first aggregate route, thereby avoiding the problem of traffic packet loss during the aggregation process. When the aggregation of the first aggregate route is completed, the attribute of the first aggregate route is automatically adjusted to the second attribute value to increase the priority of the first aggregate route, so that the first aggregate route can participate in route selection normally.

[0027] Based on the method provided in the second aspect, in a possible implementation manner, the second network device adjusts the first attribute value to the second attribute value and sends a second routing announcement message to the first network device. The implementation process can be: after a predetermined time, the second network device adjusts the first attribute value to the second attribute value and sends a second routing announcement message to the first network device.

[0028] By means of the above method, the second network device can automatically increase the priority of the first aggregate route after publishing the first aggregate route for a period of time.

[0029] Based on the method provided in the second aspect, in a possible implementation manner, the first attribute value and the second attribute value are attribute values ​​corresponding to the routing weight; wherein the first attribute value is smaller than the second attribute value.

[0030] When the first attribute value and the second attribute value are attribute values ​​corresponding to the route weight, the priority of the first aggregate route can be improved by increasing the attribute value of the route weight in the first aggregate route.

[0031] Based on the method provided in the second aspect, in a possible implementation manner, the first attribute value and the second attribute value are attribute values ​​corresponding to a multi-exit authentication MED; wherein the first attribute value is greater than the second attribute value.

[0032] When the first attribute value and the second attribute value are attribute values ​​corresponding to MED, the priority of the first aggregate route may be increased by reducing the attribute value of MED in the first aggregate route.

[0033] Based on the method provided in the second aspect, in a possible implementation manner, the first attribute value and the second attribute value are attribute values ​​corresponding to the local priority; wherein the first attribute value is smaller than the second attribute value.

[0034] When the first attribute value and the second attribute value are attribute values ​​corresponding to the local priority, the priority of the first aggregate route may be increased by increasing the attribute value of the local priority in the first aggregate route.

[0035] According to a third aspect, a method for routing processing is provided, in which a first network device receives a routing announcement message sent by a second network device, the routing announcement message including a first aggregate route and attribute information, the attribute information indicating the number of detailed routes corresponding to the first aggregate route; the first network device stores the first aggregate route in a routing table of the first network device.

[0036] In the embodiment of the present application, a new attribute information indicating the number of detailed routes corresponding to the first aggregate route is added for the first aggregate route, which is hereinafter referred to as the detailed route quantity attribute. Since the first aggregate route corresponds to the detailed route quantity attribute, the first network device can refer to the detailed route quantity to determine whether to use the first aggregate route to forward traffic when selecting a route later, so as to avoid diverting traffic to the second network device during the aggregation process of the first aggregate route, thereby causing packet loss.

[0037] Based on the method provided in the third aspect, in a possible implementation, the routing table of the first network device also stores a second aggregate route, and the first aggregate route and the second aggregate route have the same prefix. In this scenario, in the method, based on the number of detailed routes corresponding to the first aggregate route and the number of detailed routes corresponding to the second aggregate route, a preferred route is determined from the first aggregate route and the second aggregate route, and the preferred route is used to guide message forwarding.

[0038] In an embodiment of the present application, when selecting a route for current traffic, the number of detailed routes corresponding to the aggregate route may be considered to avoid directing the current traffic to an aggregate route with fewer detailed routes.

[0039] Based on the method provided in the third aspect, in a possible implementation manner, based on the number of detail routes corresponding to the first aggregate route and the number of detail routes corresponding to the second aggregate route, the implementation process of determining the preferred route from the first aggregate route and the second aggregate route can be: if the difference between the number of detail routes corresponding to the first aggregate route and the number of detail routes corresponding to the second aggregate route exceeds a difference threshold, the first aggregate route is determined as the preferred route.

[0040] Through the above method, traffic can be directed to the aggregate route with more detailed routes through direct comparison to avoid packet loss.

[0041] Based on the method provided in the third aspect, in a possible implementation manner, based on the number of detail routes corresponding to the first aggregate route and the number of detail routes corresponding to the second aggregate route, the implementation process of determining the preferred route from the first aggregate route and the second aggregate route can be: if the difference ratio between the number of detail routes corresponding to the first aggregate route and the number of detail routes corresponding to the second aggregate route exceeds a difference ratio threshold, the first aggregate route is determined as the preferred route.

[0042] Through the above method, traffic can be directed to the aggregate route with more detailed routes through range comparison to avoid packet loss.

[0043] Based on the method provided in the third aspect, in a possible implementation, a second aggregate route is also stored in the routing table of the first network device, and the first aggregate route and the second aggregate route have the same prefix. In this scenario, in the method, based on the number of detailed routes corresponding to the first aggregate route and the number of detailed routes corresponding to the second aggregate route, the message is forwarded through the first aggregate route and the second aggregate route in a load sharing manner.

[0044] In the above manner, the number of detailed routes of each aggregate route can also be considered during load balancing.

[0045] Based on the method provided in the third aspect, in a possible implementation manner, the community attribute or extended community attribute of the routing advertisement message carries attribute information.

[0046] Through the above method, the newly added detailed route quantity attribute can be flexibly carried in the route advertisement message.

[0047] In a fourth aspect, a method for routing processing is provided, in which the second network device sends a routing announcement message to the first network device, the routing announcement message includes a first aggregate route and attribute information, and the attribute information indicates the number of detailed routes corresponding to the first aggregate route.

[0048] In the embodiment of the present application, a new attribute information indicating the number of detailed routes corresponding to the first aggregate route is added for the first aggregate route, which is hereinafter referred to as the detailed route quantity attribute. Since the first aggregate route corresponds to the detailed route quantity attribute, the first network device can refer to the detailed route quantity to determine whether to use the first aggregate route to forward traffic when selecting a route later, so as to avoid diverting traffic to the second network device during the aggregation process of the first aggregate route, thereby causing packet loss.

[0049] In a fifth aspect, a routing processing device is provided, wherein the routing processing device has the function of implementing the routing processing method in the first aspect. The routing processing device includes at least one module, and the at least one module is used to implement the routing processing method provided in the first aspect.

[0050] In a sixth aspect, a routing processing device is provided, wherein the routing processing device has the function of implementing the routing processing method in the second aspect. The routing processing device includes at least one module, and the at least one module is used to implement the routing processing method provided in the second aspect.

[0051] In a seventh aspect, a routing processing device is provided, wherein the routing processing device has the function of implementing the routing processing method in the third aspect. The routing processing device includes at least one module, and the at least one module is used to implement the routing processing method provided in the third aspect.

[0052] In an eighth aspect, a routing processing device is provided, wherein the routing processing device has the function of implementing the routing processing method in the fourth aspect. The routing processing device includes at least one module, and the at least one module is used to implement the routing processing method provided in the fourth aspect.

[0053] In a ninth aspect, a routing processing device is provided, wherein the structure of the routing processing device includes a processor and a memory, wherein the memory is used to store a program that supports the routing processing device to execute the routing processing method provided in the first aspect, and to store data involved in implementing the routing processing method provided in the first aspect. The processor is configured to execute the program stored in the memory.

[0054] In a tenth aspect, a routing processing device is provided, wherein the structure of the routing processing device includes a processor and a memory, wherein the memory is used to store a program that supports the routing processing device to execute the routing processing method provided in the second aspect, and to store data involved in implementing the routing processing method provided in the second aspect. The processor is configured to execute the program stored in the memory.

[0055] In an eleventh aspect, a routing processing device is provided, wherein the structure of the routing processing device includes a processor and a memory, wherein the memory is used to store a program that supports the routing processing device to execute the routing processing method provided in the third aspect, and to store data involved in implementing the routing processing method provided in the third aspect. The processor is configured to execute the program stored in the memory.

[0056] In a twelfth aspect, a routing processing device is provided, wherein the structure of the routing processing device includes a processor and a memory, wherein the memory is used to store a program that supports the routing processing device to execute the routing processing method provided in the fourth aspect, and to store data involved in implementing the routing processing method provided in the fourth aspect. The processor is configured to execute the program stored in the memory.

[0057] In the thirteenth aspect, a computer-readable storage medium is provided, wherein instructions are stored in the computer-readable storage medium, and when the computer-readable storage medium is executed on a computer, the computer executes the routing processing method described in the first aspect, or the routing processing method described in the second aspect, or the routing processing method described in the third aspect, or the routing processing method described in the fourth aspect.

[0058] In a fourteenth aspect, a computer program product comprising instructions is provided, which, when executed on a computer, enables the computer to execute the routing processing method described in the first aspect, or the routing processing method described in the second aspect, or the routing processing method described in the third aspect, or the routing processing method described in the fourth aspect.

[0059] In a fifteenth aspect, a routing processing system is provided, which includes a first network device and a second network device.

[0060] The second network device is used to send a route advertisement message to the first network device, where the route advertisement message includes the first aggregate route;

[0061] A first network device, configured to receive a routing advertisement message sent by a second network device;

[0062] The first network device is further configured to, in response to the first aggregate route not being stored in the routing table of the first network device, set an attribute of the first aggregate route to a first attribute value, wherein the first attribute value indicates that a priority of the first aggregate route is a first priority;

[0063] The first network device is further used to update the attribute of the first aggregate route to a second attribute value, where the second attribute value indicates that the priority of the first aggregate route is a second priority, and the second priority is greater than the first priority.

[0064] In a sixteenth aspect, a routing processing system is provided, which includes a first network device and a second network device.

[0065] The second network device is used to send a first route advertisement message to the first network device, wherein the first route advertisement message includes a first aggregate route and a first attribute value, and the first attribute value indicates that the priority of the first aggregate route is a first priority;

[0066] A first network device, configured to receive a first routing advertisement message;

[0067] The second network device is also used to adjust the first attribute value to a second attribute value, and send a second route announcement message to the first network device, the second route announcement message includes the first aggregate route and the second attribute value, the second attribute value indicates that the priority of the first aggregate route is a second priority, and the second priority is greater than the first priority.

[0068] The first network device is further configured to receive a second routing advertisement message;

[0069] In a seventeenth aspect, a routing processing system is provided, wherein the routing processing system includes a first network device and a second network device.

[0070] The second network device is used to send a route advertisement message to the first network device, where the route advertisement message includes the first aggregate route and attribute information, where the attribute information indicates the number of detailed routes corresponding to the first aggregate route;

[0071] The first network device is used to receive a route advertisement message sent by the second network device, where the route advertisement message includes the first aggregate route and attribute information, where the attribute information indicates the number of detailed routes corresponding to the first aggregate route;

[0072] The first network device is further configured to store the first aggregate route in a routing table of the first network device.

[0073] The technical effects obtained in the above-mentioned fifth to seventeenth aspects are similar to the technical effects obtained by the corresponding technical means in the first to fourth aspects, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0074] Figure 1 It is a schematic diagram of a scenario for generating an aggregated route provided in an embodiment of the present application;

[0075] Figure 2 It is a schematic diagram of a network architecture provided by an embodiment of the present application;

[0076] Figure 3 It is a flow chart of a routing processing method implemented by a routing receiving end provided in an embodiment of the present application;

[0077] Figure 4 is another flow chart of a routing processing method implemented by a routing receiving end provided in an embodiment of the present application;

[0078] Figure 5 is another flow chart of a routing processing method implemented by a routing receiving end provided in an embodiment of the present application;

[0079] Figure 6 is another flow chart of a routing processing method implemented by a routing receiving end provided in an embodiment of the present application;

[0080] Figure 7 is another flow chart of a routing processing method implemented by a routing receiving end provided in an embodiment of the present application;

[0081] Figure 8 is another flow chart of a routing processing method implemented by a routing receiving end provided in an embodiment of the present application;

[0082] Fig. 9 is another flow chart of a routing processing method implemented by a routing receiving end provided in an embodiment of the present application;

[0083] Fig.10It is a flow chart of a routing processing method implemented by a routing aggregation terminal provided in an embodiment of the present application;

[0084] Fig.11 It is a flow chart of a routing processing method implemented by a routing aggregation terminal provided in an embodiment of the present application;

[0085] Fig.12 It is a flow chart of a routing processing method implemented by a routing aggregation terminal provided in an embodiment of the present application;

[0086] Fig.13 It is a flow chart of a routing processing method implemented by a routing aggregation terminal provided in an embodiment of the present application;

[0087] Fig.14 It is a flow chart of a routing processing method implemented by a routing aggregation terminal provided in an embodiment of the present application;

[0088] Fig.15 It is a flow chart of a routing processing method implemented by a routing aggregation terminal provided in an embodiment of the present application;

[0089] Fig.16 It is a structural diagram of a routing processing device provided in an embodiment of the present application;

[0090] Fig.17 is a structural diagram of another routing processing device provided in an embodiment of the present application;

[0091] Fig.18 is a structural diagram of another routing processing device provided in an embodiment of the present application;

[0092] Fig.19 is a structural diagram of another routing processing device provided in an embodiment of the present application;

[0093] Fig. 20 is a structural schematic diagram of a computer device provided in an embodiment of the present application;

[0094] Fig.21 It is a schematic diagram of the architecture of a routing processing system provided in an embodiment of the present application. DETAILED DESCRIPTION

[0095] In order to make the purpose, technical solutions and advantages of the present application more clear, the implementation mode of the present application will be further described in detail below with reference to the accompanying drawings.

[0096] Before explaining the embodiments of the present application, the application scenarios of the embodiments of the present application are first introduced.

[0097] Routes aggregation can be understood as the process of merging multiple detailed routes into one aggregated route. For example, the common part of the prefixes of multiple detailed routes can be used as the prefix of the aggregated route.

[0098] Route aggregation is divided into two categories: manual aggregation and automatic aggregation. Regardless of manual aggregation or automatic aggregation, the aggregated route is generated based on the aggregation of detailed routes, and only one detailed route is needed to generate an aggregated route. For example, a network device will receive 10,000 detailed routes from another network device, and generate one or more aggregated routes based on these 10,000 detailed routes. Assume that the aggregation rule (hereinafter referred to as the aggregation rule) is to aggregate the detailed routes with the same first 24-bit prefix into an aggregated route. When the network device receives the first detailed route, it can generate an aggregated route based on the first 24-bit prefix of the detailed route, and then continue to receive other detailed routes, and aggregate other detailed routes with the same first 24-bit prefix as the first 24-bit prefix of the first detailed route into the aggregated route.

[0099] Based on the above route aggregation process, it can be seen that route aggregation is not completed immediately, but starts from the first detailed route and ends with the last detailed route. For the convenience of subsequent explanation, the stage in route aggregation when the route aggregation end has not received all the detailed routes is called the aggregation process. The stage in route aggregation when the route aggregation end receives all the detailed routes is called the aggregation completion.

[0100] In addition, since the aggregate route is obtained from multiple detailed routes, deleting a detailed route will not cause the aggregate route to be deleted. Deleting all detailed routes will cause the aggregate route to be deleted.

[0101] In addition, route aggregation can be applied to protocols such as the Border Gateway Protocol (BGP) and the Interior Gateway Protocol (IGP).

[0102] Figure 1 Schematic diagram of a scenario for generating an aggregated route provided by an embodiment of the present application. Figure 1 As shown, four routers are deployed in the network, which are marked as RTA, RTB, RTC and RTD. RTD is connected to RTB and RTC for communication, and RTB and RTC are connected to RTA for communication.

[0103] For example, when any one of RTB and RTC communicates with RTA based on BGP, any one of RTB and RTC and RTA are in a BGP peer relationship. In other words, any one of RTB and RTC and RTA are in a BGP neighbor relationship.

[0104] When any one of RTB and RTC communicates with RTD based on IGP, any one of RTB and RTC and RTD are in an IGP peer relationship. In other words, any one of RTB and RTC and RTD are in an IGP neighbor relationship.

[0105] like Figure 1 As shown in the figure, RTD publishes 10,000 detailed routes to RTB and RTC respectively. RTB and RTC aggregate the first 24-bit prefixes of the 10,000 detailed routes into one or more aggregated routes through automatic or manual aggregation. Every time RTB and RTC generate an aggregated route, they can publish the generated aggregated route to RTA without publishing the detailed routes. After receiving the aggregated route, RTA selects a route based on the aggregated route from RTB and RTC to direct the traffic to RTB or RTC, or to both RTB and RTC through load balancing.

[0106] Since aggregate routes are generated based on detailed routes and only one detailed route is needed to generate an aggregate route and advertise it to neighbors, the problem of early aggregate route advertising leading to premature diversion often occurs in the network.

[0107] For example, in Figure 1 In the example, when the neighbor relationship between RTD and RTC is reestablished, RTC receives the first detailed route from RTD, which triggers the generation of an aggregate route and publishes the aggregate route to RTA. After receiving the aggregate route, RTA selects a route, assuming that the aggregate route received from RTC is preferred, or the aggregate route is selected to participate in load sharing. In this way, traffic is diverted from RTA to RTC, and RTC currently only receives a small number of detailed routes from RTD. This may cause the traffic to fail to find the corresponding detailed route at RTC, resulting in most of the traffic being discarded. RTC may not be able to stop packet loss until it receives all the detailed routes from RTD.

[0108] When the RTC performance is normal, the total completion time of route aggregation may be in the order of seconds to tens of seconds; when the RTC receives routes slowly, the total completion time of route aggregation may be in the order of hours. This will cause packet loss at the RTC for a long period of time.

[0109] In addition, other scenarios can also cause the above-mentioned packet loss problem during the aggregation process. For example, when the neighbor RTD modifies the routing policy and causes RTD to withdraw the previously published routes and resend them to RTC, in this scenario RTC will also regenerate the aggregated routes and publish them to RTA, which will cause the traffic to be diverted to RTC during the aggregation process, resulting in packet loss.

[0110] For example, when RTD has multiple new detailed routes to send to RTC, but the speed of sending the detailed routes is very slow, while the speed of sending the detailed routes to RTB is faster, in this scenario, RTC will also generate an aggregated route based on the newly received detailed routes and publish it to RTA, which will cause the traffic to be diverted to RTC during the aggregation process, resulting in packet loss.

[0111] For example, when RTC itself introduces a new detailed route and generates an aggregate route, in this scenario, RTC will also regenerate the aggregate route and publish it to RTA, which will cause the traffic to be diverted to RTC during the aggregation process, resulting in packet loss.

[0112] Based on this, an embodiment of the present application provides a routing processing method. In an embodiment of the present application, after receiving a newly generated aggregate route, the route receiving end can set the attributes of the aggregate route so that the route receiving end does not prefer the aggregate route to forward messages in the recent period of time, thereby avoiding the problem of traffic packet loss during the aggregation process. Alternatively, the generating end of the aggregate route (that is, the route aggregation end) can set the attributes of the aggregate route generated during the aggregation process so that the network device that receives the aggregate route does not prefer the aggregate route to forward messages, thereby avoiding the problem of traffic packet loss during the aggregation process.

[0113] The networking, routing processing methods and devices involved in the embodiments of the present application are explained in detail below.

[0114] Figure 2 Schematic diagram of a network architecture provided by an embodiment of the present application. Figure 2 As shown, the network 20 includes a first network device 21 and a second network device 22. The first network device 21 and the second network device 22 are connected to each other via a wired or wireless method for communication.

[0115] The second network device 22 can serve as a route aggregation terminal to generate an aggregated route and publish the aggregated route to the first network device 21. In other words, the first network device 21 can receive the aggregated route generated by the second network device 22. Figure 1 In the networking shown, the first network device 21 may be RTA, and the second network device 22 may be RTC.

[0116] In this scenario, in some embodiments, the first network device 21 may set the attributes of the received aggregate route to avoid the first network device 21 directing traffic to the second network device 22 during the aggregation process of the aggregate route, thereby causing packet loss.

[0117] In other embodiments, when the second network device 22 generates an aggregate route as a route aggregation end and publishes the aggregate route to the first network device 21, some attributes can be set in the published aggregate route to avoid the first network device 21 directing traffic to the second network device 22 during the aggregation process of the aggregate route, thereby causing packet loss.

[0118] In the embodiment of the present application, the first network device 21 and the second network device 22 may be any device that uses routing aggregation technology, such as a switch, a router, a controller (ie, a network management device), or a virtual switch.

[0119] In addition, the first network device 21 and the second network device 22 may use the BGP protocol to implement route aggregation, or may use other protocols to implement route aggregation, which will not be described one by one here.

[0120] In addition, if Figure 2 As shown, the first network device 21 may include a configuration unit, a route aggregation unit, and other processing units. Among them, the configuration unit is used to configure commands such as automatic aggregation or manual aggregation. The route aggregation unit is used to aggregate detailed routes into aggregate routes, or process received aggregate routes to implement the method provided in the embodiment of the present application. Other processing units are used to perform route selection or neighbor publishing of aggregate routes, etc.

[0121] Among them, the configuration unit, routing aggregation unit and other processing units are software units configured on the first network device 21. When applying the embodiment of the present application, the first network device may include more or fewer units to implement the method provided by the embodiment of the present application.

[0122] In addition, the second network device 22 may also be configured with software units such as a configuration unit, a routing aggregation unit, and other processing units, which will not be described in detail here.

[0123] Based on the foregoing, it can be known that in the embodiment of the present application, the routing receiving end can set the attributes of the aggregated route to avoid the problem of traffic packet loss during the aggregation process of the aggregated route. The routing aggregation end can also set the attributes of the aggregated route to avoid the problem of traffic packet loss during the aggregation process of the aggregated route. The following two methods are explained respectively.

[0124] Figure 31 is a flowchart of a route processing method implemented by a route receiving end provided in an embodiment of the present application. The method is used to illustrate how the route receiving end sets the attributes of the aggregated route to avoid the problem of traffic packet loss during the aggregation process of the aggregated route. Figure 3 As shown, the method includes the following steps.

[0125] Step 301: A first network device receives a route advertisement message sent by a second network device, where the route advertisement message includes a first aggregate route.

[0126] After generating the aggregated route, the second network device may publish the aggregated route to the first network device through a route advertisement message.

[0127] In some embodiments, the route advertisement message is a BGP update message. That is, the first aggregate route may be an aggregate route based on the BGP protocol.

[0128] In addition, when the first network device receives a route advertisement message from another network device, it can determine whether the route in the route advertisement message is an aggregate route by using the route attribute carried in the route advertisement message. If the route in the route advertisement message is an aggregate route, the route processing method provided in the embodiment of the present application is executed.

[0129] In some embodiments, if the route attributes carried by the route advertisement message include the device autonomous system (AS) number of the route aggregator and the device internet protocol (IP) address of the route aggregator, it can be determined that the route carried by the route advertisement message is an aggregated route. The device IP address of the route aggregator can also be referred to as the device identity (ID) of the route aggregator.

[0130] Step 302: In response to the first network device not storing the first aggregate route in the routing table, the first network device sets the attribute of the first aggregate route to a first attribute value, where the first attribute value indicates that the priority of the first aggregate route is a first priority.

[0131] When the first network device receives the first aggregate route from the second network device, if the first aggregate route is not stored in the routing table of the first network device, it indicates that the first aggregate route is a newly generated aggregate route, that is, the first aggregate route is in the aggregation process. At this time, in order to avoid the traffic being diverted to the second network device during the aggregation process, the first network device sets the attribute of the first aggregate route to reduce the priority of the first aggregate route, so that the first network device does not prefer the first aggregate route during the aggregation process of the first aggregate route, and accordingly avoids the problem of traffic packet loss during the aggregation process.

[0132] After executing step 302, the first network device may send the processed first aggregate route to the routing table of the first network device, so that the first network device can select a route based on the routing table.

[0133] In some embodiments, the routing table of the first network device stores a second aggregate route, the first aggregate route and the second aggregate route have the same prefix, the priority of the second aggregate route is the third priority, and the third priority is greater than the first priority.

[0134] Since the third priority is greater than the first priority, the first network device will preferably use the second aggregate route to forward the message when selecting a route, thereby avoiding directing traffic to the second network device through the first aggregate route during the aggregation process, thereby avoiding packet loss at the second network device.

[0135] Step 303: The first network device updates the attribute of the first aggregate route to a second attribute value, where the second attribute value indicates that the priority of the first aggregate route is a second priority, and the second priority is greater than the first priority.

[0136] After the first network device receives the first aggregate route, the number of detailed routes summarized to the first aggregate route at the second network device gradually increases. Therefore, the first network device can automatically increase the priority of the first aggregate route when the first aggregate route is aggregated, so that the first aggregate route can participate in route selection normally.

[0137] In some embodiments, the implementation process of step 303 may be: after a predetermined time, the first network device updates the attribute of the first aggregate route to a second attribute value.

[0138] By means of the above method, the first network device can automatically increase the priority of the first aggregate route after receiving the first aggregate route for a period of time.

[0139] The scheduled time can be understood as: taking step 302 as the starting time point, starting timing from the starting time point, and the timing duration is the duration of the scheduled time.

[0140] For example, the first network device may start a timer after step 302, and when the timing duration of the timer reaches a predetermined time, step 303 is executed to automatically increase the priority of the first aggregate route.

[0141] The predetermined time is a preset duration, which can be set by relevant technicians based on experience, such as by referring to the aggregation capability of the second network device. For example, the second network device normally takes about 10 minutes to complete the aggregation process of an aggregated route, so the predetermined time can be set to 10 minutes.

[0142] Optionally, in other embodiments, the first network device may also respond to other instructions to execute step 303. For example, after completing the aggregation of the first aggregated route, the second network device sends an aggregation completion instruction to the first network device, and the first network device executes step 303 in response to the aggregation completion instruction.

[0143] In addition, a second aggregate route is stored in the routing table of the first network device, the first aggregate route and the second aggregate route have the same prefix, and the priority of the second aggregate route is the third priority, and the second priority is greater than or equal to the third priority.

[0144] In this scenario, after the first network device updates the priority of the first aggregate route, since the second priority is greater than or equal to the third priority, the first network device can preferably forward the message by the first aggregate route, thereby achieving that the first aggregate route is not preferably forwarded during the aggregation process of the first aggregate route, but the first aggregate route is preferably forwarded after the first aggregate route aggregates a large number of detailed routes.

[0145] There are multiple implementations for the first network device to set and update the attributes of the first aggregate route. Figure 4 and Figure 5 It should be noted that the method for setting and updating the attributes of the first aggregate route is not limited to Figure 4 and Figure 5 The two types shown are not described one by one here.

[0146] Figure 4 FIG. 1 is another flow chart of a routing processing method implemented by a routing receiving end provided in an embodiment of the present application. Figure 4 As shown, the method includes the following steps.

[0147] Step 401: a first network device receives a route advertisement message sent by a second network device, wherein the route advertisement message includes a first aggregate route and a first attribute of the first aggregate route, and the first attribute in the route advertisement message is a second attribute value.

[0148] In the embodiment of the present application, after receiving the newly generated aggregate route, the first network device may adjust the attribute value of the existing route attribute (ie, the first attribute) in the aggregate route to reduce the priority of the first aggregate route. The first attribute may indicate the priority of the first aggregate route.

[0149] Step 402: In response to the first network device not storing the first aggregate route in the routing table, adjusting the first attribute of the first aggregate route from the second attribute value to the first attribute value.

[0150] For example, when the first attribute includes a route weight, the first aggregate route will be preferred when selecting a route because the larger the attribute value of the route weight is, the more preferred the first aggregate route will be. Therefore, in order to avoid the first aggregate route being preferred during the aggregation process, the attribute value of the route weight in the first aggregate route can be lowered. That is, the route weight of the first aggregate route is reduced from the second attribute value to the first attribute value.

[0151] For another example, when the first attribute includes MED, the smaller the attribute value of MED is, the more preferred the first aggregate route will be when selecting a route. Therefore, in order to avoid the first aggregate route being preferred during the aggregation process, the attribute value of MED in the first aggregate route can be increased. That is, the MED of the first aggregate route is increased from the second attribute value to the first attribute value.

[0152] For another example, when the first attribute includes a local priority, since the larger the attribute value of the local priority is, the first aggregate route will be preferred during route selection, so in order to avoid the first aggregate route being preferred during the aggregation process, the attribute value of the local priority in the first aggregate route can be lowered. That is, the local priority of the first aggregate route is reduced from the second attribute value to the first attribute value.

[0153] It should be noted that the above is used to illustrate how to adjust the attribute value of the first attribute in the first aggregate route to reduce the priority of the first aggregate route. Optionally, the first attribute may also be other attributes that can indicate the priority of the route, which will not be illustrated one by one here.

[0154] In addition, when the second attribute value is adjusted to the first attribute value, the adjustment range may be any range, for example, the local priority may be directly adjusted to 0, the MED may be adjusted to the maximum, or the length of the AS path (AS-Pash) may be increased by multiples.

[0155] In addition, the first network device may also be configured with an automatic priority reduction command and an attribute adjustment rule, the attribute adjustment rule being used to indicate how to adjust the attribute value of the first attribute. Based on this, when the first aggregate route is not stored in the routing table of the first network device, it may continue to be determined whether an automatic priority reduction command is configured. If an automatic priority reduction command is configured, the attribute value of the first attribute in the first aggregate route is adjusted according to the attribute adjustment rule, thereby obtaining the processed first aggregate route.

[0156] After performing the above processing (i.e., lowering the priority) on the received first aggregate route, the first network device can send the first aggregate route with the lowered priority to the routing table so as to select a route based on the processed first aggregate route and publish the first aggregate route with the lowered priority to its neighbors.

[0157] In addition, when the first network device publishes the first aggregate route, if the current routing table stores a route with the same prefix as the first aggregate route, since the priority of the first aggregate route is lowered, if the priority of the first aggregate route after processing is less than the priority of the route, the first aggregate route is not published. Correspondingly, if the current routing table does not store a route with the same prefix as the first aggregate route, the first aggregate route and the adjusted first attribute value are published.

[0158] In addition, after the first network device sends the processed first aggregate route to the routing table, as the first aggregate route aggregation process proceeds, the attribute value of the first attribute in the first aggregate route in the routing table can be called back through the following steps so that the first aggregate route can participate in route selection normally.

[0159] Step 403: The first attribute of the first aggregate route is recalled from the first attribute value to the second attribute value.

[0160] In some embodiments, step 403 may be performed a predetermined time after step 402 is performed.

[0161] For example, a first timer may be started, and when the timing duration of the first timer reaches a first reference duration, the first attribute of the first aggregate route in the routing table is called back from the first attribute value to the second attribute value.

[0162] For example, when the first attribute includes a routing weight, the attribute value of the routing weight in the first aggregate route can be increased when the timing duration of the first timer reaches the first reference duration, that is, the routing weight of the first aggregate route is increased from the first attribute value to the second attribute value.

[0163] As another example, when the first attribute includes MED, the attribute value of MED in the first aggregate route may be lowered when the timing duration of the first timer reaches the first reference duration, that is, the MED of the first aggregate route is reduced from the first attribute value to the second attribute value.

[0164] As another example, when the first attribute includes local priority, the attribute value of the local priority in the first aggregate route can be increased when the timing duration of the first timer reaches the first reference duration, that is, the local priority of the first aggregate route is increased from the first attribute value to the second attribute value.

[0165] It should be noted that the above is used to illustrate how to call back the attribute value of the first attribute in the first aggregate route in the routing table. Optionally, the first attribute may also be other attributes that can indicate the priority of the route, which will not be illustrated one by one here.

[0166] In addition, in some embodiments, the route advertisement message includes the first aggregate route and the first attribute of the first aggregate route, and the first attribute in the route advertisement message may not be the second attribute value, but any other attribute value greater than the first attribute value, which is not described in detail here.

[0167] In addition, the above-mentioned attribute adjustment rule may include a first reference duration. In other words, the user can configure the first reference duration required for calling back the first attribute by configuring the attribute adjustment rule.

[0168] In addition, after the first network device calls back the first attribute of the first aggregate route to the second attribute value in the above manner, the priority of the first aggregate route is increased, thus triggering the first network device to select a route and publish the updated first aggregate route to its neighbors.

[0169] Below Figure 5 For example Figure 4 The embodiments shown are illustrative only.

[0170] like Figure 5 As shown, the configuration unit of the first network device is configured with a priority automatic reduction command and attribute adjustment rules for the newly generated aggregated route. Figure 5 As shown in the figure, the attribute adjustment rule is: reduce the local priority by 1000, increase the MED by 1000, and restore the attribute value after 10 minutes.

[0171] When receiving a new route, the route aggregation unit of the first network device determines whether the route is an aggregated route based on the route attributes carried by the route. If the route is determined to be an aggregated route, it continues to determine whether the priority automatic reduction command is configured. If the priority automatic reduction command is configured, the attribute value of the first attribute of the received aggregated route is adjusted according to the configured attribute adjustment rule. Specifically, the attribute value of the local priority in the received aggregated route is subtracted by 1000, and the attribute value of the MED in the received aggregated route is increased by 1000. The other processing units in the first network device publish the aggregated route with the adjusted attribute value to the neighbors, and use the aggregated route with the adjusted attribute value for route selection.

[0172] The first network device starts the first timer, and after the first timer reaches 10 minutes, the attribute value of the first attribute of the aggregate route is called back, that is, the attribute value of the first attribute of the aggregate route is restored to update the aggregate route. Specifically, the attribute value of the local priority in the aggregate route is increased by 1000, and the attribute value of the MED in the aggregate route is subtracted by 1000. The other processing units in the first network device publish the updated aggregate route to the neighbors, and use the updated aggregate route for route selection.

[0173] Below Figure 1The network shown in the figure is used as an example. Figure 4 The embodiments shown are illustrative only.

[0174] like Figure 6 As shown, when the neighbor relationship between RTD and RTC is interrupted and needs to be rebuilt, RTD will republish a large number of detailed routes to RTC. When RTC receives the first detailed route from RTD, it generates an aggregate route and publishes the aggregate route to RTA. When RTA receives the aggregate route, it adjusts the attribute value of the first attribute of the aggregate route, such as lowering the attribute value of the local priority and / or increasing the attribute value of the MED, so as to lower the priority of the aggregate route. Since the priority of the aggregate route is lower, the aggregate route is not preferred when selecting a route. In this way, during the aggregation process of the aggregate route, the probability of traffic being diverted by RTA to RTC can be reduced, thereby avoiding traffic loss at RTC.

[0175] After a period of time, RTA can call back the attribute value of the first attribute of the aggregate route, such as increasing the attribute value of the local priority and / or reducing the attribute value of the MED, to increase the priority of the aggregate route. Since the priority of the updated aggregate route is improved, the aggregate route may be preferred when selecting a route. In this way, when the aggregation of the aggregate route is completed, the traffic can be normally directed to RTC by RTA. At this time, since the aggregation of the aggregate route has been completed, that is, a large number of detailed routes corresponding to the aggregate route can be found at RTC, the traffic can be forwarded normally from RTC.

[0176] Figure 7 FIG. 1 is another flow chart of a routing processing method implemented by a routing receiving end provided in an embodiment of the present application. Figure 7 As shown, the method includes the following steps.

[0177] Step 701: A first network device receives a route advertisement message sent by a second network device, where the route advertisement message includes a first aggregate route.

[0178] The implementation of step 701 can refer to Figure 3 Step 301 in the embodiment will not be described in detail here.

[0179] Step 702: In response to the first network device not storing the first aggregate route in the routing table, the first network device adds a routing tag attribute to the first aggregate route and sets the routing tag attribute of the first aggregate route to a first attribute value, wherein the first attribute value indicates that the first network device delays using the first aggregate route for routing.

[0180] In an embodiment of the present application, after receiving the newly generated aggregate route, the first network device can add a new attribute (i.e., a routing tag attribute) to the aggregate route and set the attribute value of the routing tag attribute so that the first network device delays the use of the first aggregate route for routing, i.e., lowers the priority of the first aggregate route.

[0181] In addition, the first attribute value indicates that the first network device delays using the first aggregate route for routing, so when the routing tag attribute is set to the first attribute value, the routing tag attribute can also be called delayed routing tag information.

[0182] In addition, after the first network device sends the processed first aggregate route to the routing table, as the aggregation process of the first aggregate route proceeds, the attribute value of the routing mark attribute in the first aggregate route in the routing table can be called back through the following steps so that the first aggregate route can participate in routing normally.

[0183] Step 703: The first network device updates the routing tag attribute of the first aggregate route to a second attribute value, where the second attribute value indicates that the first network device uses the first aggregate route for routing.

[0184] In some embodiments, step 703 may be performed a predetermined time after step 702 is performed.

[0185] For example, a second timer may be started, and when the timing duration of the second timer reaches a second reference duration, the routing tag attribute of the first aggregate route in the routing table is adjusted from the first attribute value to the second attribute value.

[0186] Below Figure 8 For example Figure 7 The embodiments shown are illustrative only.

[0187] like Figure 8 As shown, the configuration unit of the first network device is configured with an aggregate route delay routing command and a delay routing rule for the newly generated aggregate route. Figure 8 As shown, the delayed route selection rule is: delay route selection for 3 minutes.

[0188] When receiving a new route, the route aggregation unit of the first network device determines whether the route is an aggregated route based on the route attribute carried by the route. If the route is determined to be an aggregated route, it continues to determine whether the aggregated route delayed routing command is configured. If the aggregated route delayed routing command is configured, it adds delayed routing mark information to the aggregated route, that is, sets the routing mark attribute to the first attribute value (i.e., delayed routing), and starts the second timer. After the timing duration of the second timer reaches 3 minutes, the delayed routing mark information is deleted, that is, the routing mark attribute is set to the second attribute value (i.e., no delayed routing), so that the aggregated route can participate in routing.

[0189] Below Figure 1 The network shown in the figure is used as an example. Figure 7 The embodiments shown are illustrative only.

[0190] like Fig. 9 As shown in the figure, when the neighbor relationship between RTD and RTC is interrupted and needs to be rebuilt, RTD will republish a large number of detailed routes to RTC. When RTC receives the first detailed route from RTD, it generates an aggregate route and publishes the aggregate route to RTA. When RTA receives the aggregate route, it implements delayed routing for the aggregate route. Since the aggregate route is not considered during routing. In this way, during the aggregation process of the aggregate route, it can avoid that the traffic is diverted from RTA to RTC, thereby avoiding packet loss at RTC.

[0191] To sum up, in an embodiment of the present application, after receiving the newly generated aggregate route, the route receiving end can set the attributes of the aggregate route to lower the priority of the aggregate route, so that the route receiving end does not prefer to forward messages using the aggregate route in the recent period of time, thereby avoiding traffic packet loss problems during the aggregation process.

[0192] The following embodiments are used to explain how a route aggregation end sets the attributes of an aggregated route to avoid traffic packet loss during the aggregation process of the aggregated route.

[0193] In the embodiment of the present application, when the first network device generates a new aggregate route based on the detailed route, considering that it is currently in the aggregation process, it sets the attribute values ​​of some route attributes (hereinafter referred to as target route attributes) in the new aggregate route, so that the attribute values ​​of the target route attributes in the new aggregate route can indicate that the aggregate route is a newly generated aggregate route, that is, it is currently in the aggregation process. In this way, after receiving the aggregate route, other network devices determine whether to route the aggregate route based on the attribute values ​​of the target route attributes, thereby avoiding the problem of traffic packet loss during the aggregation process.

[0194] The target route attribute may be any route attribute that can indicate the first aggregate route aggregation process through an attribute value.

[0195] In an embodiment of the present application, the attribute value of the route attribute in the BGP protocol can be extended to indicate the aggregation process of the first aggregate route. For example, the target route attribute can be an attribute that can indicate the route priority, that is, a route priority attribute, such as route weight (preferred-value), multi exit discriminator (MED) and local preference. In this scenario, during the aggregation process of the first aggregate route, the attribute value of the route priority attribute of the first aggregate route can be set lower, and when the aggregation is completed, the attribute value of the route priority attribute of the first aggregate route can be adjusted higher. The aggregation process of the first aggregate route is indicated by the change in the attribute value of the route priority attribute.

[0196] Optionally, some new route attributes may be added to indicate the aggregation process of the first aggregate route. For example, the target route attribute may be a detail route quantity attribute, and the attribute value of the detail route quantity attribute may indicate the number of detail routes currently aggregated to the first aggregate route. In the aggregation process of the first aggregate route, there are fewer detail routes aggregated to the first aggregate route, so the attribute value of the detail route quantity attribute will be lower. When the aggregation is completed, there are more detail routes aggregated to the first aggregate route, so the attribute value of the detail route quantity attribute will be higher.

[0197] The above target route attribute is used for illustration, and the embodiment of the present application does not limit the specific form of the target route attribute. For example, a special aggregation process attribute can be extended, and the attribute value of the aggregation process attribute can directly indicate the current aggregation process.

[0198] Below Fig.10 and Fig.13 Take this as an example to illustrate.

[0199] Fig.10 1 is a flow chart of a routing processing method implemented by a routing aggregation terminal provided in an embodiment of the present application. Fig.10 As shown, the method includes the following steps.

[0200] Step 1001: The second network device sends a first route advertisement message to the first network device, where the first route advertisement message includes a first aggregate route and a first attribute value, where the first attribute value indicates that the priority of the first aggregate route is a first priority.

[0201] Step 1002: The second network device adjusts the first attribute value to a second attribute value, and sends a second route announcement message to the first network device, where the second route announcement message includes the first aggregate route and the second attribute value, where the second attribute value indicates that the priority of the first aggregate route is the second priority, which is greater than the first priority.

[0202] In the embodiment of the present application, when the second network device publishes the first aggregate route, it can set the attribute of the first aggregate route to the first attribute value during the aggregation process of the first aggregate route to reduce the priority of the first aggregate route, thereby avoiding the problem of traffic packet loss during the aggregation process. When the aggregation of the first aggregate route is completed, the attribute of the first aggregate route is automatically adjusted to the second attribute value to increase the priority of the first aggregate route, so that the first aggregate route can participate in route selection normally.

[0203] In some embodiments, before issuing the first route advertisement message, the second network device further generates a first aggregate route based on at least one detailed route and determines a first attribute value.

[0204] The second network device generating the first aggregate route based on at least one detailed route can be understood as: the first aggregate route is an aggregate route aggregated for the first time by the second network device, that is, a new aggregate route.

[0205] In addition, the second network device is configured with a routing table, which stores routes generated by the second network device or obtained from other network devices. Therefore, after the second network device generates the first aggregated route, if the first aggregated route is not in the routing table, the first aggregated route can be determined as a new aggregated route.

[0206] In addition, the implementation process of the second network device generating the first aggregate route based on at least one detailed route and determining the first attribute value may be: generating the first aggregate route based on at least one detailed route, the first aggregate route corresponding to the initial attribute value, in response to the absence of the first aggregate route in the routing table of the second network device, adjusting the initial attribute value to obtain the first attribute value. The priority indicated by the first attribute value is less than the priority indicated by the initial attribute value.

[0207] Among them, at least one detailed route can be a route published by other network devices and received by the first network device, or a route introduced by the first network device itself from other protocols. In addition, when the first network device obtains at least one detailed route, it can also check whether it is configured with automatic aggregation or manual aggregation commands. If it is configured with automatic aggregation or manual aggregation commands, a first aggregated route is generated based on at least one detailed route.

[0208] When each network device in the network generates an aggregate route, the initial attribute value corresponding to the aggregate route is usually a default reference value. In other words, when different network devices in the network generate an aggregate route, the initial attribute value corresponding to the aggregate route is the same.

[0209] In addition, the initial attribute value may be an attribute value corresponding to one or more of the routing weight, MED, and local priority.

[0210] For example, when the initial attribute value is the attribute value of the route weight, the larger the attribute value of the route weight is, the more likely the first aggregate route will be preferred during route selection. Therefore, in order to avoid the first aggregate route being preferred during the aggregation process, the initial attribute value corresponding to the first aggregate route can be lowered. That is, the first attribute value is smaller than the initial attribute value.

[0211] For another example, when the initial attribute value is the attribute value corresponding to MED, since the smaller the attribute value of MED is, the first aggregate route will be preferred when selecting a route, so in order to avoid the first aggregate route being preferred during the aggregation process, the initial attribute value corresponding to the first aggregate route can be increased. That is, the first attribute value is greater than the initial attribute value.

[0212] For another example, when the initial attribute value is the attribute value corresponding to the local priority, the larger the attribute value of the local priority is, the more preferred the first aggregate route will be when selecting a route. Therefore, in order to avoid the first aggregate route being preferred during the aggregation process, the initial attribute value corresponding to the first aggregate route can be lowered. That is, the first attribute value is smaller than the initial attribute value.

[0213] It should be noted that the above is used to illustrate how to adjust the initial attribute value of the first aggregate route to obtain the first attribute value. Optionally, the initial attribute value may also be an attribute value of other attributes that can indicate the priority of the route, which will not be illustrated one by one here.

[0214] In addition, when the initial attribute value is adjusted to the first attribute value, the adjustment range may be any range, for example, the local priority may be directly adjusted to 0, the MED may be adjusted to the maximum, or the length of the AS path (AS-Pash) may be increased by multiples.

[0215] In addition, the second network device may also be configured with an automatic priority reduction command and an attribute adjustment rule, and the attribute adjustment rule is used to indicate how to adjust the initial attribute value of the route priority. Based on this, when the second network device does not find the first aggregate route in the routing table, it may continue to determine whether an automatic priority reduction command is configured. If an automatic priority reduction command is configured, the initial attribute value of the first aggregate route is adjusted according to the attribute adjustment rule, thereby obtaining the first attribute value.

[0216] After obtaining the first aggregate route and the first attribute value, the second network device publishes the first aggregate route to the first network device through a first route advertisement message.

[0217] The above is to adjust the initial attribute value of the first aggregate route when generating the first aggregate route to reduce the priority of the first aggregate route. Optionally, in the embodiment of the present application, the initial attribute value of the first aggregate route can also be adjusted in the above manner when publishing the first aggregate route to reduce the priority of the first aggregate route. No further details are given here.

[0218] In addition, after generating the first aggregate route, the second network device also sends the first aggregate route and the corresponding at least one detailed route to the routing table of the second network device. Subsequently, detailed routes that meet the same aggregation rule as the at least one detailed route can also be summarized into the first aggregate route.

[0219] In addition, when the second network device publishes the first aggregate route, if the current routing table stores a route with the same prefix as the first aggregate route, since the priority of the first aggregate route is reduced, if the priority of the adjusted first aggregate route is less than the priority of the route, the first aggregate route is not published. Correspondingly, if the current routing table does not store a route with the same prefix as the first aggregate route, the first aggregate route and the adjusted first attribute value are published.

[0220] In addition, after publishing the first aggregate route, the second network device can also adjust the first attribute value of the first aggregate route through step 1002 as the aggregation process of the first aggregate route proceeds to obtain a second attribute value to update the priority of the first aggregate route, thereby allowing the first aggregate route to participate in route selection normally.

[0221] In some embodiments, step 1002 may be performed a predetermined time after step 1001 is performed.

[0222] By means of the above method, the second network device can automatically increase the priority of the first aggregate route after publishing the first aggregate route for a period of time.

[0223] For example, after executing step 1001, a third timer is started, and when the timing duration of the third timer reaches a third reference duration, the first attribute value in the first aggregate route is called back, the second attribute value is obtained, and the first aggregate route and the second attribute value are published through a second route announcement message. The priority indicated by the second attribute value is greater than the priority indicated by the first attribute value.

[0224] The second attribute value may be equal to or different from the aforementioned initial attribute value.

[0225] For example, when the first attribute value is the attribute value corresponding to the routing weight, the attribute value of the routing weight in the first aggregate route can be increased when the timing duration of the third timer reaches the third reference duration. In other words, the attribute value of the routing weight in the first aggregate route after the update (i.e., the second attribute value) is greater than the attribute value of the routing weight in the first aggregate route before the update (i.e., the first attribute value).

[0226] As another example, when the first attribute value is the attribute value corresponding to MED, the attribute value of MED in the first aggregate route can be lowered when the timing duration of the third timer reaches the third reference duration. In other words, the attribute value of MED in the updated first aggregate route (i.e., the second attribute value) is less than the attribute value of MED in the first aggregate route before the update (i.e., the first attribute value).

[0227] As another example, when the first attribute value is an attribute value corresponding to the local priority, the attribute value of the local priority in the first aggregate route can be increased when the timing duration of the third timer reaches the third reference duration. In other words, the attribute value of the local priority in the first aggregate route after the update (i.e., the second attribute value) is greater than the attribute value of the local priority in the first aggregate route before the update (i.e., the first attribute value).

[0228] It should be noted that the above is used to illustrate how to call back the first attribute value of the first aggregate route. Optionally, the first attribute value may also be an attribute value of other attributes that can indicate the priority of the route, which will not be illustrated one by one here.

[0229] In addition, the above-mentioned property adjustment rule may include a third reference duration. In other words, the user can configure the third reference duration required for calling back the first property value by configuring the property adjustment rule.

[0230] In addition, the above is used to illustrate when to update the first attribute value of the first aggregate route. Optionally, in an embodiment of the present application, the second network device may also determine whether to update the first aggregate route based on a change in the number of detailed routes corresponding to the first aggregate route. For example, when it is determined that the number of detailed routes corresponding to the first aggregate route reaches a certain threshold, the first attribute value of the first aggregate route may be called back. This will not be described in detail here.

[0231] After the second network device calls back the attribute of the first aggregate route to the second attribute value in the above manner, the priority of the first aggregate route is increased, so the second network device is triggered to select a route and publish the updated first aggregate route in step 1002 .

[0232] Below Fig.11 For example Fig.10 The embodiments shown are illustrative only.

[0233] like Fig.11 As shown, the configuration unit of the second network device is configured with an automatic aggregation or manual aggregation command, and is also configured with an automatic priority reduction command and attribute adjustment rules for the newly generated aggregated route. Fig.11 As shown in the figure, the attribute adjustment rule is: reduce the local priority by 1000, increase the MED by 1000, and restore the attribute value after 10 minutes.

[0234] When receiving or introducing detailed routes, the route aggregation unit of the second network device first aggregates the detailed routes into aggregate routes through automatic aggregation or manual aggregation commands, and then determines whether the automatic priority reduction command is configured. If the automatic priority reduction command is configured, the attribute value of the route priority attribute of the generated aggregate route is adjusted according to the configured attribute adjustment rule. Specifically, the attribute value of the local priority in the generated aggregate route is subtracted by 1000, and the attribute value of the MED in the generated aggregate route is increased by 1000. The other processing units in the second network device publish the aggregated route with the adjusted attribute value to the neighbors, and use the aggregated route with the adjusted attribute value for route selection.

[0235] The second network device starts the third timer. After the third timer reaches 10 minutes, the attribute value of the route priority attribute of the aggregate route is called back, that is, the attribute value of the route priority attribute of the aggregate route is restored to update the aggregate route. Specifically, the attribute value of the local priority in the aggregate route is increased by 1000, and the attribute value of the MED in the generated aggregate route is subtracted by 1000. The other processing units in the second network device publish the updated aggregate route to the neighbors and use the updated aggregate route for route selection.

[0236] Below Figure 1 The network shown in the figure is used as an example. Fig.10 The embodiments shown are illustrative only.

[0237] like Fig.12 As shown, when the neighbor relationship between RTD and RTC is interrupted and needs to be rebuilt, RTD will republish a large number of detailed routes to RTC. When RTC receives the first detailed route from RTD, it generates an aggregate route and adjusts the attribute value of the route priority attribute of the aggregate route, such as reducing the attribute value of the local priority and / or increasing the attribute value of the MED to reduce the priority of the aggregate route, and publishes the aggregate route with reduced priority to RTA. When RTA receives the aggregate route, since the priority of the aggregate route is lower, the aggregate route is not preferred when selecting the route. In this way, during the aggregation process of the aggregate route, the probability of traffic being diverted by RTA to RTC can be reduced, thereby avoiding traffic packet loss at RTC.

[0238] After a period of time, RTC can call back the attribute value of the route priority attribute of the aggregate route, such as increasing the attribute value of the local priority and / or reducing the attribute value of the MED, to improve the priority of the aggregate route, and publish the updated aggregate route to RTA. When RTA receives the updated aggregate route, since the priority of the updated aggregate route is improved, the aggregate route may be preferred when selecting the route. In this way, when the aggregation of the aggregate route is completed, the traffic can be normally directed to RTC by RTA. At this time, since the aggregation of the aggregate route is completed, that is, a large number of detailed routes corresponding to the aggregate route can be found at RTC, the traffic can be forwarded normally from RTC.

[0239] Fig.13 FIG. 1 is another flow chart of a routing processing method implemented by a routing aggregation terminal provided in an embodiment of the present application. Fig.13 As shown, the method includes the following steps.

[0240] Step 1301: The second network device sends a route advertisement message to the first network device. The route advertisement message includes a first aggregate route and attribute information. The attribute information indicates the number of detailed routes corresponding to the first aggregate route.

[0241] The attribute information can indicate the number of detailed routes corresponding to the first aggregate route, so the attribute information is also called a detailed route quantity attribute.

[0242] In the embodiment of the present application, a new attribute information indicating the number of detailed routes corresponding to the first aggregate route is added for the first aggregate route, which is hereinafter referred to as the detailed route quantity attribute. Since the first aggregate route corresponds to the detailed route quantity attribute, the first network device can refer to the detailed route quantity to determine whether to use the first aggregate route to forward traffic when selecting a route later, so as to avoid diverting traffic to the second network device during the aggregation process of the first aggregate route, thereby causing packet loss.

[0243] In some embodiments, the second network device first generates a first aggregate route based on at least one specific route and determines a specific route quantity attribute.

[0244] The implementation of step 1301 may refer to step 401 , except that, in step 1301 , a detailed route quantity attribute is added to the generated first aggregate route.

[0245] In some embodiments, the attribute of the number of specific routes indicates the total number of at least one specific route, or indicates the total number of specific routes in at least one specific route that are sent to the routing table.

[0246] The attribute of the number of detailed routes indicates the total number of at least one detailed route, which can be understood as: the total number of detailed routes currently aggregated by the second network device to the first aggregate route. The attribute of the number of detailed routes indicates the total number of detailed routes sent to the routing table from at least one detailed route, which can be understood as: the number of detailed routes that have been sent to the routing table from all detailed routes currently aggregated by the second network device to the first aggregate route.

[0247] For example, the total number of detailed routes currently aggregated by the second network device to the first aggregate route is 100. Since it takes a certain amount of time to send the detailed routes to the routing table, only 80 of the 100 detailed routes may be sent to the routing table. In this scenario, if the attribute of the number of detailed routes indicates the total number of at least one detailed route, the attribute value of the attribute of the number of detailed routes is 100. If the attribute of the number of detailed routes indicates the total number of detailed routes sent to the routing table in at least one detailed route, the attribute value of the attribute of the number of detailed routes is 80.

[0248] When applying the embodiments of the present application, the specific attribute of the number of detailed routes can be selected based on network requirements. For example, for a scenario with high packet loss requirements, the attribute of the number of detailed routes can be specified as the total number of detailed routes sent to the routing table in at least one detailed route. Correspondingly, for a scenario with low packet loss requirements, the attribute of the number of detailed routes can be specified as the total number of at least one detailed route.

[0249] In addition, the attribute of the number of detailed routes can be a newly added common route attribute or a newly added extended group attribute, which is not limited in the embodiment of the present application. In other words, the group attribute or the extended group attribute in the route announcement message carries the attribute information in step 1301. In this way, the newly added attribute of the number of detailed routes can be flexibly carried in the route announcement message.

[0250] Step 1302: The first network device receives a routing advertisement message sent by the second network device.

[0251] Step 1303: The first network device stores the first aggregate route in a routing table of the first network device.

[0252] After the second network device publishes the first aggregate route to the first network device, the first network device receives the first aggregate route from the second network device, the first aggregate route corresponding to the detailed route quantity attribute; the second network device sends the first aggregate route to the routing table.

[0253] Since the first aggregate route corresponds to a specific route quantity attribute, the first network device can refer to the attribute value of the specific route quantity attribute when selecting a route to determine whether the first aggregate route needs to be used to forward traffic, so as to avoid directing traffic to the second network device during the aggregation process of the first aggregate route, thereby causing packet loss.

[0254] The routing table of the first network device is used to store routes. When the first network device needs to forward a message, it can select a preferred route from the routing table to forward the message through the preferred route.

[0255] In some embodiments, the routing table of the first network device also stores a second aggregate route, and the first aggregate route and the second aggregate route have the same prefix. In this scenario, based on the number of detailed routes corresponding to the first aggregate route and the number of detailed routes corresponding to the second aggregate route, a preferred route is determined from the first aggregate route and the second aggregate route, and the preferred route is used to guide message forwarding.

[0256] In an embodiment of the present application, when selecting a route for current traffic, the number of detailed routes corresponding to the aggregate route may be considered to avoid directing the current traffic to an aggregate route with fewer detailed routes.

[0257] For example, based on the number of detail routes corresponding to the first aggregate route and the number of detail routes corresponding to the second aggregate route, determining the preferred route from the first aggregate route and the second aggregate route may be implemented as follows: if the difference between the number of detail routes corresponding to the first aggregate route and the number of detail routes corresponding to the second aggregate route exceeds a difference threshold, determining the first aggregate route as the preferred route.

[0258] Through the above method, traffic can be directed to the aggregate route with more detailed routes through direct comparison to avoid packet loss.

[0259] For example, based on the number of detailed routes corresponding to the first aggregate route and the number of detailed routes corresponding to the second aggregate route, the implementation method of determining the preferred route from the first aggregate route and the second aggregate route may be: if the difference ratio between the number of detailed routes corresponding to the first aggregate route and the number of detailed routes corresponding to the second aggregate route exceeds a difference ratio threshold, the first aggregate route is determined as the preferred route.

[0260] Through the above method, traffic can be directed to the aggregate route with more detailed routes through range comparison to avoid packet loss.

[0261] The difference ratio threshold is a preset value. For example, the difference ratio threshold can be 20%. If the difference ratio between the number of detailed routes corresponding to the first aggregate route and the number of detailed routes corresponding to the second aggregate route exceeds 20%, the first aggregate route can be determined as the preferred route. Correspondingly, if the difference ratio between the number of detailed routes corresponding to the first aggregate route and the number of detailed routes corresponding to the second aggregate route does not exceed 20%, it is necessary to determine the preferred route by other means.

[0262] Assume that the first aggregate route corresponds to 10,000 detailed routes and the second aggregate route corresponds to 9,000 detailed routes. The difference ratio between the two is calculated as |10,000–9,000| / MAX(10,000, 9,000)=10%.

[0263] The above-mentioned route selection takes into account the attribute of the number of detailed routes. Optionally, the attribute of the number of detailed routes and other route attributes can also be considered at the same time to select routes for traffic. For example, the attribute of the number of detailed routes and the local priority can be considered at the same time to select routes for current traffic. That is, when the first network device selects a route, the route selection conditions include the number of detailed routes and other route attributes.

[0264] In addition, the routing table of the first network device also stores a second aggregate route. In a scenario where the first aggregate route and the second aggregate route have the same prefix, the first network device can also forward the message through the first aggregate route and the second aggregate route in a load balancing manner based on the number of detailed routes corresponding to the first aggregate route and the number of detailed routes corresponding to the second aggregate route. In this manner, the attribute of the number of detailed routes of each aggregate route can also be considered during load balancing.

[0265] Among them, based on the number of detailed routes corresponding to the first aggregate route and the number of detailed routes corresponding to the second aggregate route, in accordance with the load sharing method, forwarding messages through the first aggregate route and the second aggregate route can be understood as: the ratio between the amount of messages forwarded through the first aggregate route and the amount of messages forwarded through the second aggregate route is the same as the ratio between the number of detailed routes corresponding to the first aggregate route and the number of detailed routes corresponding to the second aggregate route.

[0266] For example, based on the number of specific routes corresponding to the first aggregate route and the number of specific routes corresponding to the second aggregate route, according to the load balancing method, the implementation process of forwarding messages through the first aggregate route and the second aggregate route can be: if the number of specific routes corresponding to the first aggregate route and the number of specific routes corresponding to the second aggregate route both exceed the quantity threshold, load balancing is performed through the first aggregate route and the second aggregate route.

[0267] Through the above method, the attribute of the number of detailed routes of each aggregate route can also be considered during load balancing, so that when the number of detailed routes corresponding to each aggregate route reaches a certain order of magnitude, the load balancing method is used to forward the message, thereby avoiding the packet loss problem of the current traffic.

[0268] The quantity threshold may be a preset value, for example, 1000. If the number of detailed routes corresponding to the first aggregate route and the number of detailed routes corresponding to the second aggregate route both exceed 1000, load balancing may be performed through the first aggregate route and the second aggregate route.

[0269] In addition, after the second network device publishes the first aggregate route, as the aggregation process of the first aggregate route proceeds, it can also adjust the attribute value of the detailed route quantity attribute in the first aggregate route through the following steps, and publish the updated first aggregate route, so that the first aggregate route can participate in route selection normally.

[0270] Specifically, when the number of detailed routes corresponding to the first aggregate route changes, it is determined whether the change in the number of detailed routes meets the reference condition. In response to the change in the number of detailed routes meeting the reference condition, the attribute value (i.e., attribute information) of the attribute of the number of detailed routes corresponding to the first aggregate route is updated to obtain an updated first aggregate route, and the updated first aggregate route is published to the first network device.

[0271] During the aggregation process of the first aggregate route, the number of detailed routes corresponding to the first aggregate route gradually increases. In order to avoid too frequent route updates, when the attribute value of the detailed route quantity attribute changes, it is determined whether the change in the attribute value of the detailed route quantity attribute satisfies the reference condition. If it is determined that the change in the attribute value of the detailed route quantity attribute satisfies the reference condition, the first aggregate route is updated.

[0272] The reference condition can be set by using the BGP update interval mechanism. Specifically, the aggregate route can be updated once every 1 minute. Optionally, the reference condition can also be: update the aggregate route once when the change ratio of the number of detailed routes exceeds 3%, and update the aggregate route at the latest once every 5 seconds if the change ratio does not reach 3%. Optionally, the reference condition can also be other conditions, which will not be illustrated one by one here.

[0273] After updating the first aggregate route, the second network device may publish the updated first aggregate route to the first network device, so that the first network device sends the updated first aggregate route to the routing table to select a route for the current traffic through the updated first aggregate route.

[0274] Below Fig.14For example Fig.13 The embodiments shown are illustrative only.

[0275] like Fig.14 As shown, the configuration unit of the second network device is configured with an automatic aggregation or manual aggregation command, and is also configured with a reference condition for the newly generated aggregate route. Fig.14 As shown, the reference condition is: if the number of detailed routes changes by more than 3%, the aggregate route is updated once.

[0276] When receiving or introducing a detailed route, if an aggregated route corresponding to the detailed route has not been generated in advance, the route aggregation unit of the second network device first aggregates the detailed routes into an aggregated route through automatic aggregation or manual aggregation commands, and counts the number of detailed routes participating in the aggregated route, and sets the attribute value of the detailed route quantity attribute in the aggregated route based on the number. Other processing units in the second network device publish the aggregated route to neighbors.

[0277] Accordingly, when the route aggregation unit of the second network device receives or introduces a detailed route, if an aggregated route corresponding to the detailed route has been generated in advance, the detailed route is aggregated into the aggregated route, and the number of detailed routes participating in the aggregated route is counted, and then it is determined whether the quantity transformation meets the reference condition. If so, the attribute value of the detailed route quantity attribute in the aggregated route is updated. The other processing units in the first network device publish the updated aggregated route to the neighbors.

[0278] Below Figure 1 The network shown in the figure is used as an example. Fig.13 The embodiments shown are illustrative only.

[0279] like Fig.15 As shown, when the neighbor relationship between RTD and RTC is interrupted and needs to be rebuilt, RTD will republish a large number of detailed routes to RTC. When RTC receives the first detailed route from RTD, it generates an aggregate route that carries the attribute of the number of detailed routes and publishes the aggregate route to RTA. When RTA receives the aggregate route, it selects a route according to the attribute of the number of detailed routes carried by the aggregate route. Specifically, the larger the number of corresponding detailed routes, the greater the probability that the aggregate route will be preferred. Therefore, during the aggregation process, if the number of detailed routes corresponding to the aggregate route is small, RTA will not prefer the aggregate route when selecting the route. In this way, during the aggregation process of the aggregate route, the probability of traffic being diverted by RTA to RTC can be reduced, thereby avoiding traffic packet loss at RTC.

[0280] In summary, in the embodiment of the present application, when the route aggregation end publishes the aggregated route, the attribute of the aggregated route can be set during the aggregation process of the aggregated route to reduce the priority of the first aggregated route, thereby avoiding the problem of traffic packet loss during the aggregation process. When the aggregation of the aggregated route is completed, the attribute of the aggregated route is automatically adjusted to increase the priority of the aggregated route so that the aggregated route can participate in the route selection normally. Alternatively, a detailed route quantity attribute can be added to the published aggregated route to avoid the problem of traffic packet loss during the aggregation process.

[0281] Fig.16 Schematic diagram of a routing processing device provided in an embodiment of the present application. The device is deployed on a first network device, such as Fig.16 As shown, the device 1600 includes the following modules.

[0282] The receiving module 1601 is used to receive a routing advertisement message sent by a second network device, where the routing advertisement message includes a first aggregated route. Figure 3 Step 301 in the embodiment.

[0283] The setting module 1602 is used to set the attribute of the first aggregate route to a first attribute value in response to the first network device not storing the first aggregate route in the routing table, and the first attribute value indicates that the priority of the first aggregate route is the first priority; the specific implementation method can refer to Figure 3 Step 302 in the embodiment.

[0284] The updating module 1603 is used to update the attribute of the first aggregate route to a second attribute value, where the second attribute value indicates that the priority of the first aggregate route is a second priority, and the second priority is greater than the first priority. Figure 3 Step 303 in the embodiment.

[0285] Optionally, a second aggregate route is stored in the routing table of the first network device, the first aggregate route and the second aggregate route have the same prefix, the priority of the second aggregate route is a third priority, and the third priority is greater than the first priority.

[0286] Optionally, the second priority is greater than or equal to the third priority.

[0287] Optionally, the update module is used to:

[0288] After a predetermined time, the attribute of the first aggregate route is updated to a second attribute value.

[0289] Optionally, the route advertisement message further includes a first attribute of the first aggregate route, and the first attribute in the route advertisement message is a second attribute value;

[0290] The settings module is used to:

[0291] Adjusting the first attribute of the first aggregate route from the second attribute value to the first attribute value;

[0292] Update modules are used to:

[0293] The first attribute of the first aggregate route is recalled from the first attribute value to the second attribute value.

[0294] Optionally, the first attribute includes a routing weight;

[0295] The modules are set up for:

[0296] The route weight of the first aggregate route is reduced from the second attribute value to the first attribute value.

[0297] Optionally, the first attribute includes a multi-exit identification MED;

[0298] The settings module is used to:

[0299] The MED of the first aggregate route is increased from the second attribute value to the first attribute value.

[0300] Optionally, the first attribute comprises a local priority;

[0301] The settings module is used to:

[0302] The local priority of the first aggregate route is reduced from the second attribute value to the first attribute value.

[0303] Optionally, the module is set to:

[0304] Adding a routing tag attribute to the first aggregate route, and setting the routing tag attribute of the first aggregate route to a first attribute value, the first attribute value indicating that the first network device delays using the first aggregate route for routing;

[0305] Update modules are used to:

[0306] The routing tag attribute of the first aggregate route is updated to a second attribute value, where the second attribute value indicates that the first network device uses the first aggregate route for routing.

[0307] Optionally, the routing advertisement message is a BGP update message.

[0308] In an embodiment of the present application, when the first network device receives the first aggregate route from the second network device, if the first aggregate route is not stored in the routing table of the first network device, it indicates that the first aggregate route is a newly generated aggregate route, that is, the first aggregate route is in the aggregation process. At this time, in order to avoid the traffic being diverted to the second network device during the aggregation process, the first network device sets the attributes of the first aggregate route to reduce the priority of the first aggregate route, so that the first network device does not prefer the first aggregate route during the aggregation process of the first aggregate route, and accordingly avoids the problem of traffic packet loss during the aggregation process. Accordingly, the first network device can automatically increase the priority of the first aggregate route when the aggregation of the first aggregate route is completed, so that the first aggregate route can participate in the route selection normally.

[0309] It should be noted that: the routing processing device provided in the above embodiment only uses the division of the above functional modules as an example when processing routing. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. In addition, the routing processing device provided in the above embodiment and the routing processing method embodiment belong to the same concept. The specific implementation process is detailed in the method embodiment and will not be repeated here.

[0310] Fig.17 is a schematic diagram of the structure of another routing processing device provided in an embodiment of the present application. The device is deployed on a second network device, such as Fig.17 As shown, the device 1700 includes the following modules.

[0311] The first sending module 1701 is used to send a first route announcement message to the first network device, where the first route announcement message includes a first aggregate route and a first attribute value, where the first attribute value indicates that the priority of the first aggregate route is the first priority. For specific implementation methods, please refer to Fig.10 Step 1001 in the embodiment.

[0312] The second sending module 1702 is used to adjust the first attribute value to the second attribute value, and send a second route announcement message to the first network device, the second route announcement message includes the first aggregate route and the second attribute value, the second attribute value indicates that the priority of the first aggregate route is the second priority, and the second priority is greater than the first priority. For specific implementation methods, please refer to Fig.10 Step 1002 in an embodiment.

[0313] Optionally, the second sending module is used for:

[0314] After a predetermined time, the first attribute value is adjusted to a second attribute value, and a second routing advertisement message is sent to the first network device.

[0315] Optionally, the first attribute value and the second attribute value are attribute values ​​corresponding to the routing weight;

[0316] The first attribute value is smaller than the second attribute value.

[0317] Optionally, the first attribute value and the second attribute value are attribute values ​​corresponding to the multi-exit identification MED;

[0318] Among them, the first attribute value is greater than the second attribute value.

[0319] Optionally, the first attribute value and the second attribute value are attribute values ​​corresponding to the local priority;

[0320] The first attribute value is smaller than the second attribute value.

[0321] In the embodiment of the present application, when the second network device publishes the first aggregate route, it can set the attribute of the first aggregate route to the first attribute value during the aggregation process of the first aggregate route to reduce the priority of the first aggregate route, thereby avoiding the problem of traffic packet loss during the aggregation process. When the aggregation of the first aggregate route is completed, the attribute of the first aggregate route is automatically adjusted to the second attribute value to increase the priority of the first aggregate route, so that the first aggregate route can participate in route selection normally.

[0322] It should be noted that: the routing processing device provided in the above embodiment only uses the division of the above functional modules as an example when processing routing. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. In addition, the routing processing device provided in the above embodiment and the routing processing method embodiment belong to the same concept. The specific implementation process is detailed in the method embodiment and will not be repeated here.

[0323] Fig.18 is a schematic diagram of the structure of another routing processing device provided in an embodiment of the present application. The device is deployed on a first network device, such as Fig.18 As shown, the device 1800 includes the following modules.

[0324] The receiving module 1801 is used to receive a route announcement message sent by the second network device, where the route announcement message includes a first aggregate route and attribute information, where the attribute information indicates the number of detailed routes corresponding to the first aggregate route; the specific implementation method can refer to Fig.13 Step 1302 in an embodiment.

[0325] The storage module 1802 is used to store the first aggregated route in the routing table of the first network device. Fig.13 Step 1303 in the embodiment.

[0326] Optionally, the routing table of the first network device further stores a second aggregate route, and the first aggregate route and the second aggregate route have the same prefix;

[0327] The device also includes:

[0328] The routing module is used to determine a preferred route from the first aggregate route and the second aggregate route based on the number of detailed routes corresponding to the first aggregate route and the number of detailed routes corresponding to the second aggregate route, wherein the preferred route is used to guide message forwarding.

[0329] Optionally, the routing module is used to:

[0330] If the difference between the number of detailed routes corresponding to the first aggregate route and the number of detailed routes corresponding to the second aggregate route exceeds a difference threshold, the first aggregate route is determined as the preferred route.

[0331] Optionally, the routing module is used to:

[0332] If the difference ratio between the number of detailed routes corresponding to the first aggregate route and the number of detailed routes corresponding to the second aggregate route exceeds a difference ratio threshold, the first aggregate route is determined as the preferred route.

[0333] Optionally, the routing table of the first network device further stores a second aggregate route, and the first aggregate route and the second aggregate route have the same prefix;

[0334] The device also includes:

[0335] The load sharing module is used to forward the message through the first aggregate route and the second aggregate route in a load sharing manner based on the number of detailed routes corresponding to the first aggregate route and the number of detailed routes corresponding to the second aggregate route.

[0336] Optionally, the community attribute or extended community attribute of the routing advertisement message carries attribute information.

[0337] In the embodiment of the present application, a new attribute information indicating the number of detailed routes corresponding to the first aggregate route is added for the first aggregate route, which is hereinafter referred to as the detailed route quantity attribute. Since the first aggregate route corresponds to the detailed route quantity attribute, the first network device can refer to the detailed route quantity to determine whether to use the first aggregate route to forward traffic when selecting a route later, so as to avoid diverting traffic to the second network device during the aggregation process of the first aggregate route, thereby causing packet loss.

[0338] It should be noted that: the routing processing device provided in the above embodiment only uses the division of the above functional modules as an example when processing routing. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. In addition, the routing processing device provided in the above embodiment and the routing processing method embodiment belong to the same concept. The specific implementation process is detailed in the method embodiment and will not be repeated here.

[0339] Fig.19 is a schematic diagram of the structure of another routing processing device provided in an embodiment of the present application. The device is deployed on a second network device, such as Fig.19 As shown, the device 1900 includes the following modules.

[0340] The sending module 1901 is used to send a route announcement message to the first network device, where the route announcement message includes the first aggregate route and attribute information, where the attribute information indicates the number of detailed routes corresponding to the first aggregate route. Fig.13 Step 1301 in the embodiment.

[0341] In the embodiment of the present application, a new attribute information indicating the number of detailed routes corresponding to the first aggregate route is added for the first aggregate route, which is hereinafter referred to as the detailed route quantity attribute. Since the first aggregate route corresponds to the detailed route quantity attribute, the first network device can refer to the detailed route quantity to determine whether to use the first aggregate route to forward traffic when selecting a route later, so as to avoid diverting traffic to the second network device during the aggregation process of the first aggregate route, thereby causing packet loss.

[0342] It should be noted that: the routing processing device provided in the above embodiment only uses the division of the above functional modules as an example when processing routing. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. In addition, the routing processing device provided in the above embodiment and the routing processing method embodiment belong to the same concept. The specific implementation process is detailed in the method embodiment and will not be repeated here.

[0343] Fig. 20 is a schematic diagram of the structure of a computer device provided in an embodiment of the present application. Fig. 20 The computer device shown is implemented. Fig. 20 The computer device includes at least one processor 2001, a communication bus 2002, a memory 2003 and at least one communication interface 2004.

[0344] The processor 2001 may be a general-purpose central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the present application.

[0345] Communication bus 2002 may include a pathway for transmitting information between the above-mentioned components.

[0346] The memory 2003 may be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical disc, laser disc, optical disc, digital versatile disc, Blu-ray disc, etc.), a disk or other magnetic storage device, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory 2003 may exist independently and be connected to the processor 2001 via the communication bus 2002. The memory 2003 may also be integrated with the processor 2001.

[0347] The memory 2003 is used to store the program code for executing the solution of the present application, and the execution is controlled by the processor 2001. The processor 2001 is used to execute the program code stored in the memory 2003. The program code may include one or more software modules. Any network device in the aforementioned embodiment can determine the data for developing an application through the processor 2001 and one or more software modules in the program code in the memory 2003.

[0348] The communication interface 2004 uses any transceiver-like device for communicating with other devices or communication networks, such as Ethernet, radio access network (RAN), wireless local area networks (WLAN), etc.

[0349] In a specific implementation, as an embodiment, a computer device may include multiple processors, such as Fig. 202001 and processor 2005 shown in FIG. Each of these processors may be a single-CPU processor or a multi-CPU processor. A processor herein may refer to one or more devices, circuits, and / or processing cores for processing data (e.g., computer program instructions).

[0350] In a specific implementation, as an embodiment, the computer device may further include an output device 2006 and an input device 2007. The output device 2006 communicates with the processor 2001 and may display information in a variety of ways. For example, the output device 2006 may be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector. The input device 2007 communicates with the processor 2001 and may receive user input in a variety of ways. For example, the input device 2007 may be a mouse, a keyboard, a touch screen device, or a sensor device.

[0351] The above-mentioned computer device may be a general-purpose computer device or a special-purpose computer device. In a specific implementation, the computer device may be a communication device such as a router or a switch. The embodiment of the present application does not limit the type of computer device.

[0352] Fig.21 Schematic diagram of the architecture of a routing processing system provided by an embodiment of the present application. Fig.21 As shown, the routing processing system includes Figure 2 A first network device 21 and a second network device 22 are shown.

[0353] The second network device 22 is used to send a route advertisement message to the first network device, where the route advertisement message includes the first aggregate route;

[0354] The first network device 21 is used to receive a routing advertisement message sent by the second network device;

[0355] The first network device 21 is further configured to, in response to the first aggregate route not being stored in the routing table of the first network device, set an attribute of the first aggregate route to a first attribute value, wherein the first attribute value indicates that a priority of the first aggregate route is a first priority;

[0356] The first network device 21 is further configured to update the attribute of the first aggregate route to a second attribute value, where the second attribute value indicates that the priority of the first aggregate route is a second priority, and the second priority is greater than the first priority.

[0357] The implementation of the first network device 21 and the second network device 22 can refer to Figure 3 , Figure 4 as well as Figure 7 The embodiments shown will not be described in detail here.

[0358] in addition, Fig.21 The routing processing system shown can also implement the following functions.

[0359] The second network device 22 is used to send a first route advertisement message to the first network device, where the first route advertisement message includes a first aggregate route and a first attribute value, where the first attribute value indicates that a priority of the first aggregate route is a first priority;

[0360] The first network device 21 is used to receive a first routing advertisement message;

[0361] The second network device 22 is further used to adjust the first attribute value to a second attribute value, and send a second route announcement message to the first network device, the second route announcement message includes the first aggregate route and the second attribute value, the second attribute value indicates that the priority of the first aggregate route is the second priority, and the second priority is greater than the first priority.

[0362] The first network device 21 is further configured to receive a second routing advertisement message;

[0363] The implementation of the first network device 21 and the second network device 22 can refer to Fig.10 The embodiments shown will not be described in detail here.

[0364] in addition, Fig.21 The routing processing system shown can also implement the following functions.

[0365] The second network device 22 is used to send a route advertisement message to the first network device, where the route advertisement message includes the first aggregate route and attribute information, where the attribute information indicates the number of detailed routes corresponding to the first aggregate route;

[0366] The first network device 21 is used to receive a route advertisement message sent by the second network device, where the route advertisement message includes the first aggregate route and attribute information, where the attribute information indicates the number of detailed routes corresponding to the first aggregate route;

[0367] The first network device 21 is further configured to store the first aggregate route in a routing table of the first network device.

[0368] The implementation of the first network device 21 and the second network device 22 can refer to Fig.13 The embodiments shown will not be described in detail here.

[0369] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital versatile disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

[0370] A person skilled in the art will understand that all or part of the steps to implement the above embodiments may be accomplished by hardware or by instructing related hardware through a program, and the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a disk or an optical disk, etc.

[0371] The above content is not intended to limit the embodiments of the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the embodiments of the present application should be included in the protection scope of the embodiments of the present application.

Claims

1. A routing processing method, characterized in that: The method comprises: The first network device receives a route advertisement message sent by the second network device, wherein the route advertisement message includes a first aggregate route; In response to the first aggregate route not being stored in the routing table of the first network device, the first network device sets an attribute of the first aggregate route to a first attribute value, where the first attribute value indicates that a priority of the first aggregate route is a first priority; The first network device updates the attribute of the first aggregate route to a second attribute value, where the second attribute value indicates that the priority of the first aggregate route is a second priority, and the second priority is greater than the first priority.

2. The method according to claim 1, characterized in that The routing table of the first network device stores a second aggregate route, the first aggregate route and the second aggregate route have the same prefix, the priority of the second aggregate route is a third priority, and the third priority is greater than the first priority.

3. The method according to claim 2, characterized in that The second priority is greater than or equal to the third priority.

4. The method according to any one of claims 1 to 3, characterized in that: The first network device updates the attribute of the first aggregate route to a second attribute value, including: After a predetermined time, the first network device updates the attribute of the first aggregate route to the second attribute value.

5. The method according to any one of claims 1 to 4, characterized in that: The route advertisement message further includes a first attribute of the first aggregate route, and the first attribute in the route advertisement message is the second attribute value; The first network device sets the attribute of the first aggregate route to a first attribute value, including: adjusting the first attribute of the first aggregate route from the second attribute value to the first attribute value; The first network device updates the attribute of the first aggregate route to a second attribute value, including: The first attribute of the first aggregate route is recalled from the first attribute value to the second attribute value.

6. The method according to claim 5, characterized in that The first attribute includes a routing weight; The adjusting the route priority attribute of the first aggregate route from the second attribute value to the first attribute value includes: The route weight of the first aggregate route is reduced from the second attribute value to the first attribute value.

7. The method according to claim 5, characterized in that The first attribute includes a multi-exit identification MED; The adjusting the route priority attribute of the first aggregate route from the second attribute value to the first attribute value includes: The MED of the first aggregate route is increased from the second attribute value to the first attribute value.

8. The method according to claim 5, characterized in that The first attribute includes a local priority; The adjusting the route priority attribute of the first aggregate route from the second attribute value to the first attribute value includes: The local priority of the first aggregate route is reduced from the second attribute value to the first attribute value.

9. The method according to any one of claims 1 to 4, characterized in that: The first network device sets the attribute of the first aggregate route to a first attribute value, including: adding a routing tag attribute to the first aggregate route, and setting the routing tag attribute of the first aggregate route to the first attribute value, wherein the first attribute value indicates that the first network device delays using the first aggregate route for routing; The first network device updates the attribute of the first aggregate route to a second attribute value, including: The routing tag attribute of the first aggregate route is updated to the second attribute value, where the second attribute value indicates that the first network device uses the first aggregate route for routing.

10. The method according to any one of claims 1 to 9, characterized in that: The routing advertisement message is a BGP update message.

11. A routing processing method, characterized in that: The method comprises: The second network device sends a first route advertisement message to the first network device, where the first route advertisement message includes a first aggregate route and a first attribute value, where the first attribute value indicates that the priority of the first aggregate route is a first priority; The second network device adjusts the first attribute value to a second attribute value, and sends a second route announcement message to the first network device, wherein the second route announcement message includes the first aggregate route and the second attribute value, and the second attribute value indicates that the priority of the first aggregate route is a second priority, and the second priority is greater than the first priority.

12. The method according to claim 11, characterized in that The second network device adjusts the first attribute value to a second attribute value, and sends a second routing advertisement message to the first network device, including: After a predetermined time, the second network device adjusts the first attribute value to a second attribute value, and sends the second route advertisement message to the first network device.

13. The method according to claim 11 or 12, characterized in that The first attribute value and the second attribute value are attribute values ​​corresponding to the routing weight; The first attribute value is smaller than the second attribute value.

14. The method according to claim 11 or 12, characterized in that: The first attribute value and the second attribute value are attribute values ​​corresponding to multi-exit identification MED; The first attribute value is greater than the second attribute value.

15. The method according to claim 11 or 12, characterized in that The first attribute value and the second attribute value are attribute values ​​corresponding to the local priority; The first attribute value is smaller than the second attribute value.

16. A routing processing method, characterized in that: The method comprises: The first network device receives a route advertisement message sent by the second network device, where the route advertisement message includes a first aggregate route and attribute information, where the attribute information indicates the number of detailed routes corresponding to the first aggregate route; The first network device stores the first aggregate route in a routing table of the first network device.

17. The method according to claim 16, characterized in that The routing table of the first network device also stores a second aggregate route, and the first aggregate route and the second aggregate route have the same prefix; The method further comprises: Based on the number of detailed routes corresponding to the first aggregate route and the number of detailed routes corresponding to the second aggregate route, a preferred route is determined from the first aggregate route and the second aggregate route, and the preferred route is used to guide message forwarding.

18. The method according to claim 17, characterized in that The determining a preferred route from the first aggregate route and the second aggregate route based on the number of detailed routes corresponding to the first aggregate route and the number of detailed routes corresponding to the second aggregate route includes: If the difference between the number of detailed routes corresponding to the first aggregate route and the number of detailed routes corresponding to the second aggregate route exceeds a difference threshold, the first aggregate route is determined as the preferred route.

19. The method according to claim 17, characterized in that The determining a preferred route from the first aggregate route and the second aggregate route based on the number of detailed routes corresponding to the first aggregate route and the number of detailed routes corresponding to the second aggregate route includes: If the difference ratio between the number of detailed routes corresponding to the first aggregate route and the number of detailed routes corresponding to the second aggregate route exceeds a difference ratio threshold, the first aggregate route is determined as the preferred route.

20. The method of claim 16, wherein: The routing table of the first network device also stores a second aggregate route, and the first aggregate route and the second aggregate route have the same prefix; The method further comprises: Based on the number of specific routes corresponding to the first aggregate route and the number of specific routes corresponding to the second aggregate route, the message is forwarded through the first aggregate route and the second aggregate route in a load balancing manner.

21. The method according to any one of claims 16 to 20, characterized in that: The community attribute or extended community attribute of the routing advertisement message carries the attribute information.

22. A routing processing method, characterized in that: The method comprises: The second network device sends a route advertisement message to the first network device, where the route advertisement message includes the first aggregate route and attribute information, where the attribute information indicates the number of detailed routes corresponding to the first aggregate route.

23. A routing processing device, characterized in that: The device is deployed on a first network device, and includes: A receiving module, configured to receive a route advertisement message sent by a second network device, wherein the route advertisement message includes a first aggregate route; A setting module, configured to, in response to the first aggregate route not being stored in the routing table of the first network device, set an attribute of the first aggregate route to a first attribute value, wherein the first attribute value indicates that a priority of the first aggregate route is a first priority; An updating module is used to update the attribute of the first aggregate route to a second attribute value, where the second attribute value indicates that the priority of the first aggregate route is a second priority, and the second priority is greater than the first priority.

24. The device according to claim 23, characterized in that The routing table of the first network device stores a second aggregate route, the first aggregate route and the second aggregate route have the same prefix, the priority of the second aggregate route is a third priority, and the third priority is greater than the first priority.

25. The device according to claim 24, characterized in that The second priority is greater than or equal to the third priority.

26. The device according to any one of claims 23 to 25, characterized in that: The update module is used to: After a predetermined time, the attribute of the first aggregate route is updated to the second attribute value.

27. The device according to any one of claims 23 to 26, characterized in that: The route advertisement message further includes a first attribute of the first aggregate route, and the first attribute in the route advertisement message is the second attribute value; The setting module is used to: adjusting the first attribute of the first aggregate route from the second attribute value to the first attribute value; The update module is used to: The first attribute of the first aggregate route is recalled from the first attribute value to the second attribute value.

28. The device according to claim 27, characterized in that The first attribute includes a routing weight; The modules are set up for: The route weight of the first aggregate route is reduced from the second attribute value to the first attribute value.

29. The device according to claim 27, characterized in that The first attribute includes a multi-exit identification MED; The setting module is used to: The MED of the first aggregate route is increased from the second attribute value to the first attribute value.

30. The device according to claim 27, characterized in that The first attribute includes a local priority; The setting module is used to: The local priority of the first aggregate route is reduced from the second attribute value to the first attribute value.

31. The device according to any one of claims 23 to 26, characterized in that: The setting module is used to: adding a routing tag attribute to the first aggregate route, and setting the routing tag attribute of the first aggregate route to the first attribute value, wherein the first attribute value indicates that the first network device delays using the first aggregate route for routing; The update module is used to: The routing tag attribute of the first aggregate route is updated to the second attribute value, where the second attribute value indicates that the first network device uses the first aggregate route for routing.

32. The device according to any one of claims 23 to 31, characterized in that: The routing advertisement message is a BGP update message.

33. A routing processing device, characterized in that: The device is deployed on a second network device, and includes: A first sending module, configured to send a first route advertisement message to a first network device, wherein the first route advertisement message includes a first aggregate route and a first attribute value, wherein the first attribute value indicates that a priority of the first aggregate route is a first priority; The second sending module is used to adjust the first attribute value to a second attribute value, and send a second route announcement message to the first network device, wherein the second route announcement message includes the first aggregate route and the second attribute value, and the second attribute value indicates that the priority of the first aggregate route is a second priority, and the second priority is greater than the first priority.

34. The device according to claim 33, characterized in that The second sending module is used for: After a predetermined time, the first attribute value is adjusted to a second attribute value, and the second routing advertisement message is sent to the first network device.

35. The device according to claim 33 or 34, characterized in that The first attribute value and the second attribute value are attribute values ​​corresponding to the routing weight; The first attribute value is smaller than the second attribute value.

36. The device according to claim 33 or 34, characterized in that The first attribute value and the second attribute value are attribute values ​​corresponding to multi-exit identification MED; The first attribute value is greater than the second attribute value.

37. The device according to claim 33 or 34, characterized in that The first attribute value and the second attribute value are attribute values ​​corresponding to the local priority; The first attribute value is smaller than the second attribute value.

38. A routing processing device, characterized in that: The device is deployed on a first network device, and includes: A receiving module, configured to receive a route advertisement message sent by a second network device, wherein the route advertisement message includes a first aggregate route and attribute information, wherein the attribute information indicates the number of detailed routes corresponding to the first aggregate route; A storage module is used to store the first aggregate route in a routing table of the first network device.

39. The device according to claim 38, characterized in that The routing table of the first network device also stores a second aggregate route, and the first aggregate route and the second aggregate route have the same prefix; The device also includes: A routing module is used to determine a preferred route from the first aggregate route and the second aggregate route based on the number of specific routes corresponding to the first aggregate route and the number of specific routes corresponding to the second aggregate route, wherein the preferred route is used to guide message forwarding.

40. The device according to claim 39, characterized in that The routing module is used for: If the difference between the number of detailed routes corresponding to the first aggregate route and the number of detailed routes corresponding to the second aggregate route exceeds a difference threshold, the first aggregate route is determined as the preferred route.

41. The device according to claim 39, characterized in that The routing module is used for: If the difference ratio between the number of detailed routes corresponding to the first aggregate route and the number of detailed routes corresponding to the second aggregate route exceeds a difference ratio threshold, the first aggregate route is determined as the preferred route.

42. The device according to claim 38, characterized in that The routing table of the first network device also stores a second aggregate route, and the first aggregate route and the second aggregate route have the same prefix; The device also includes: The load sharing module is used to forward the message through the first aggregate route and the second aggregate route in a load sharing manner based on the number of specific routes corresponding to the first aggregate route and the number of specific routes corresponding to the second aggregate route.

43. The device according to any one of claims 38 to 42, characterized in that: The community attribute or extended community attribute of the routing advertisement message carries the attribute information.

44. A routing processing device, characterized in that: The device is deployed on a second network device, and includes: The sending module is used to send a route announcement message to the first network device, wherein the route announcement message includes a first aggregate route and attribute information, and the attribute information indicates the number of detailed routes corresponding to the first aggregate route.

45. A routing processing device, characterized in that: The device includes a memory and a processor; The memory is used to store a program that supports the device to execute the method described in any one of claims 1 to 10, and to store data involved in implementing the method described in any one of claims 1 to 10; The processor is configured to execute the program stored in the memory.

46. ​​A routing processing device, characterized in that: The device includes a memory and a processor; The memory is used to store a program that supports the device to execute the method described in any one of claims 11 to 15, and to store data involved in implementing the method described in any one of claims 11 to 15; The processor is configured to execute the program stored in the memory.

47. A routing processing device, characterized in that: The device includes a memory and a processor; The memory is used to store a program that supports the device to execute the method described in any one of claims 16 to 21, and to store data involved in implementing the method described in any one of claims 16 to 21; The processor is configured to execute the program stored in the memory.

48. A routing processing device, characterized in that: The device includes a memory and a processor; The memory is used to store a program that supports the device to execute the method according to claim 22, and to store data involved in implementing the method according to claim 22; The processor is configured to execute the program stored in the memory.

49. A computer-readable storage medium, characterized in that The computer-readable storage medium stores instructions, which, when executed on a computer, enable the computer to execute the method described in any one of claims 1 to 10, or the method described in any one of claims 11 to 15, or the method described in any one of claims 16 to 21, or the method described in claim 22.

50. A routing processing system, characterized in that: The routing processing system includes a first network device and a second network device; Wherein, the first network device is used to implement the method according to any one of claims 1 to 10; or, The second network device is used to implement the method according to any one of claims 11 to 15; or, The second network device is used to implement the method described in claim 22, and the first network device is used to implement the method described in any one of claims 16-21.

Images