Route sending method, outbound route filtering capability negotiation method and route obtaining method
By negotiating outbound routing filtering capabilities and using BGP protocol in the SD-WAN scenario, on-demand subscription and filtering of routing information between devices is realized, the problem of waste of equipment resources is solved, and resource utilization and business security are improved.
Patent Information
- Application Number
- CN202310645650.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-06-01
- Publication Date
- 2024-12-03
AI Technical Summary
In the software-defined wide area network (SD-WAN) scenario, the routing information of each other needs to be obtained when interacting between devices, but the prior art causes the device to receive a large amount of non-essential routing information, causing waste of resources and pressure.
Through the negotiation of outbound routing filtering capabilities between the controller and SD-WAN devices, protocols such as Border Gateway Protocol (BGP) and Virtual Private Network (VPN) ID are used to realize on-demand subscription and filtering of routing information, reducing non-essential Transmission of information.
It effectively reduces the resource occupation of SD-WAN equipment, realizes on-demand acquisition of routing information, reduces the resource pressure of equipment, and improves the service security isolation capability.
Smart Images

Figure CN119071228A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of communication technology, and in particular to a method for sending routes, negotiating outbound route filtering capabilities, and obtaining routes. Background Art
[0002] In the software-defined wide-area network (SD-WAN) scenario, different devices need to obtain each other's routing information before interacting. Routes can be negotiated by the controller based on outbound route filtering (ORF) capabilities, filtered, and sent to each device, so that the device can obtain routing information and interact based on the obtained routing information. Summary of the invention
[0003] This application provides a method for sending routes, negotiating outbound route filtering capabilities, and obtaining routes to achieve on-demand subscription of routes. The technical solution is as follows:
[0004] In a first aspect, a method for sending a route is provided, and the method is applied to a controller, and the method includes: receiving a first ORF request message sent by a first SD-WAN device; obtaining first routing information matching the first ORF request message; and sending the first routing information to the first SD-WAN device. The controller in the present application may be a route reflector (router reflector, RR), or a control device integrated with an RR function, etc. The controller implements on-demand issuance of routing information for the first SD-WAN device by sending the first routing information matching the first ORF request message, thereby avoiding the first SD-WAN device from perceiving unnecessary routing information and reducing resource usage of the first SD-WAN device.
[0005] In a possible implementation, before receiving the first ORF request information sent by the first SD-WAN device, the method further includes: performing ORF capability negotiation with the first SD-WAN device, wherein the ORF capability negotiation is used to negotiate the ORF capability between the controller and the first SD-WAN device. The controller negotiates the ORF capability with the first SD-WAN device, so that the controller has the ability to filter routing information, thereby ensuring that the controller can issue routing information to the first SD-WAN device on demand.
[0006] In one possible implementation, ORF capability negotiation is used to negotiate transport network port (TNP)-ORF capability between the controller and the first SD-WAN device. The controller and the first SD-WAN device can negotiate different types of ORF capabilities based on the type of routing information required by the first SD-WAN to ensure filtering accuracy.
[0007] In one possible implementation, performing ORF capability negotiation with the first SD-WAN device includes: performing TNP-ORF capability negotiation with the first SD-WAN device based on a border gateway protocol (BGP) SD-WAN address family protocol. Performing TNP-ORF capability negotiation based on relevant protocols does not require the creation of a new protocol, which can reduce the difficulty of negotiation and improve the universality of the solution.
[0008] In one possible implementation, performing TNP-ORF capability negotiation with the first SD-WAN device based on the BGP SD-WAN address family protocol includes: carrying an ORF capability negotiation type length value (TLV) in a BGP SD-WAN address family protocol message interacting with the first SD-WAN device, wherein the type field of the ORF capability negotiation TLV indicates that the TLV is used for TNP-ORF capability negotiation. By carrying the ORF capability negotiation TLV in the BGP SD-WAN address family protocol message, the controller can perform TNP-ORF capability negotiation by receiving the BGP SD-WAN address family protocol message, thereby reducing the difficulty of negotiation.
[0009] In a possible implementation, the first routing information matched with the first ORF request information is a TNP route. Clarifying the type of routing information matched with the first ORF request information can ensure the accuracy of the routing information issued on demand to the first SD-WAN device.
[0010] In a possible implementation, the first ORF request message includes the SD-WAN route type. The content of the first ORF request message is clarified so that the controller can ensure the on-demand subscription of the first SD-WAN device to the route information according to the subscription keyword in the first ORF request message.
[0011] In a possible implementation, the first ORF request information also includes TNP information, and the TNP information includes a link ID and a link type. By adding subscription keywords such as TNP information to the first ORF request information, the accuracy of the routing information determined by the controller according to the subscription keywords can be further guaranteed.
[0012] In one possible implementation, receiving a first ORF request message sent by a first SD-WAN device includes: receiving a first Border Gateway Protocol route refresh BGP ROUTE-REFRESH message sent by the first SD-WAN device, the first BGPROUTE-REFRESH message including an outbound route filter type ORF Type field and a first outbound route filter table entry encoding ORF entry encoding field, the ORF Type field is used to indicate that the type of ORF is TNP-ORF, and the first ORF entryencoding field is used to carry the first ORF request message. The first ORF request message is carried by the first BGP ROUTE-REFRESH message, so that the controller can successfully obtain the first ORF request message by receiving the first BGP ROUTE-REFRESH message including the ORF entry encoding field, and according to the ORF type indicated by the ORF Type field as TNP-ORF, the controller clearly knows the ORF capability that needs to be enabled.
[0013] In one possible implementation, the first ORF request information includes a route type field, and the route type field indicates the SD-WAN TNP route. The first ORF request carries the route type field, which can clearly specify the route type to be filtered and realize accurate route information filtering.
[0014] In one possible implementation, ORF capability negotiation is used to negotiate border gateway protocol-link stateshortest path first (BGP-LS SPF) ORF capability between the controller and the first SD-WAN device. The controller and the first SD-WAN device can negotiate different types of ORF capabilities based on the type of routing information required by the first SD-WAN to ensure filtering accuracy.
[0015] In one possible implementation, performing ORF capability negotiation with the first SD-WAN device includes: performing BGP-LS SPF ORF capability negotiation with the first SD-WAN device based on the BGPSD-WAN address family protocol. Performing BGP-LS SPF ORF capability negotiation based on related protocols does not require the creation of a new protocol, can reduce the difficulty of negotiation, and improve the universality of the solution.
[0016] In one possible implementation, BGP-LS SPF ORF capability negotiation is performed with the first SD-WAN device based on the BGP SD-WAN address family protocol, including: carrying an ORF capability negotiation TLV in a BGP-LS SPF address family protocol message interacting with the first SD-WAN device, wherein the type field of the ORF capability negotiation TLV indicates that the TLV is used for BGP-LS SPF ORF capability negotiation. By carrying the ORF capability negotiation TLV in the BGP SD-WAN address family protocol message, the controller can perform BGP-LS SPF ORF capability negotiation by receiving the BGP SD-WAN address family protocol message, thereby reducing the difficulty of negotiation.
[0017] In one possible implementation, receiving the first ORF request information sent by the first SD-WAN device includes: receiving the first BGP ROUTE-REFRESH message sent by the first SD-WAN device, the first BGP ROUTE-REFRESH message including an ORF Type field and a first ORF entry encoding field, the ORF Type field is used to indicate that the type of ORF is BGP-LS SPF ORF, and the first ORF entry encoding field is used to carry the first ORF request information. By carrying the first ORF request information through the first BGPROUTE-REFRESH message, the controller can successfully obtain the first ORF request information by receiving the first BGP ROUTE-REFRESH message including the ORF entry encoding field, and according to the ORF type indicated by the ORF Type field as BGP-LS SPF ORF, the controller can clearly identify the ORF capabilities that need to be enabled.
[0018] In a possible implementation, the first routing information matched with the first ORF request information is a BGP-LSSPF route. Clarifying the type of routing information matched with the first ORF request information can ensure the accuracy of the routing information issued to the first SD-WAN device on demand.
[0019] In one possible implementation, the first ORF request message includes a virtual private network (VPN) ID. The content of the first ORF request message is clarified so that the controller can ensure the on-demand subscription of the first SD-WAN device to the routing information according to the subscription keyword in the first ORF request message.
[0020] In one possible implementation, the method further includes: receiving a second ORF request message sent by the first SD-WAN device; obtaining second routing information matching the second ORF request message; and sending the second routing information to the first SD-WAN device. The controller can issue different routing information according to different ORF request messages, thereby ensuring the accuracy of the routing information issued on demand.
[0021] In a possible implementation, the method further includes: receiving third ORF request information sent by the second SD-WAN device; obtaining third routing information matching the third ORF request information; and sending the third routing information to the second SD-WAN device. The controller can not only interact with the first SD-WAN device and issue routing information to the first SD-WAN device as needed, but also interact with the second SD-WAN device and send second routing information corresponding to the second ORF request information to the second SD-WAN device as needed, thereby ensuring the accurate correspondence between the ORF request information and the routing information.
[0022] In a second aspect, a method for negotiating an outbound route filtering capability is provided, the method comprising: the controller performs ORF capability negotiation with a first SD-WAN device, the ORF capability negotiation being used to negotiate the ORF capability between the controller and the first SD-WAN device. The controller negotiates the ORF capability with the first SD-WAN device, so that the controller has the capability of filtering route information, and ensures that the controller can issue route information to the first SD-WAN device on demand.
[0023] In one possible implementation, ORF capability negotiation is used to negotiate TNP-ORF capabilities between the controller and the first SD-WAN device. The controller and the first SD-WAN device can negotiate different types of ORF capabilities based on the type of routing information required by the first SD-WAN to ensure filtering accuracy.
[0024] In a possible implementation, the controller performs ORF capability negotiation with the first SD-WAN device, including: the controller performs TNP-ORF capability negotiation with the first SD-WAN device based on the BGP SD-WAN address family protocol. Performing TNP-ORF capability negotiation based on relevant protocols does not require the creation of new protocols, can reduce the difficulty of negotiation, and improve the universality of the solution.
[0025] In a possible implementation, the controller performs TNP-ORF capability negotiation with the first SD-WAN device based on the BGP SD-WAN address family protocol, including: the controller carries an ORF capability negotiation TLV in a BGP SD-WAN address family protocol message interacting with the first SD-WAN device, wherein the type field of the ORF capability negotiation TLV indicates that the TLV is used for TNP-ORF capability negotiation. By carrying the ORF capability negotiation TLV in the BGP SD-WAN address family protocol message, the controller can perform TNP-ORF capability negotiation by receiving the BGP SD-WAN address family protocol message, thereby reducing the difficulty of negotiation.
[0026] In one possible implementation, ORF capability negotiation is used to negotiate BGP-LS SPF ORF capabilities between the controller and the first SD-WAN device. The controller and the first SD-WAN device can negotiate different types of ORF capabilities based on the type of routing information required by the first SD-WAN to ensure filtering accuracy.
[0027] In a possible implementation, the controller performs ORF capability negotiation with the first SD-WAN device, including: the controller performs BGP-LS SPF ORF capability negotiation with the first SD-WAN device based on the BGP SD-WAN address family protocol. Performing BGP-LS SPF ORF capability negotiation based on related protocols does not require the creation of a new protocol, can reduce the difficulty of negotiation, and improve the universality of the solution.
[0028] In one possible implementation, the controller performs BGP-LS SPF ORF capability negotiation with the first SD-WAN device based on the BGP SD-WAN address family protocol, including: the controller carries an ORF capability negotiation TLV in the BGP SD-WAN address family protocol message interacting with the first SD-WAN device, wherein the type field of the ORF capability negotiation TLV indicates that the TLV is used for BGP-LS SPF ORF capability negotiation. By carrying the ORF capability negotiation TLV in the BGP SD-WAN address family protocol message, the controller can perform BGP-LS SPF ORF capability negotiation by receiving the BGP SD-WAN address family protocol message, thereby reducing the difficulty of negotiation.
[0029] In a third aspect, a method for obtaining a route is provided, the method being applied to a first SD-WAN device, the method comprising: sending a first ORF request message to a controller; and receiving first route information sent by the controller that matches the first ORF request message. By sending the first ORF request message to the controller, the required first route information is obtained, and the acquisition of other unnecessary route information is avoided, thereby reducing the resource occupation of the first SD-WAN device.
[0030] In a possible implementation, before sending the first ORF request information to the controller, the method further includes: performing ORF capability negotiation with the controller device, wherein the ORF capability negotiation is used to negotiate the ORF capability between the controller and the first SD-WAN device. The controller negotiates the ORF capability with the first SD-WAN device, so that the controller has the ability to filter routing information, and ensures that the controller can issue routing information to the first SD-WAN device on demand.
[0031] In one possible implementation, ORF capability negotiation is used to negotiate TNP-ORF capabilities between the controller and the first SD-WAN device. The controller and the first SD-WAN device can negotiate different types of ORF capabilities based on the type of routing information required by the first SD-WAN to ensure filtering accuracy.
[0032] In a possible implementation, the ORF capability negotiation with the controller device includes: performing TNP-ORF capability negotiation with the controller based on the BGP SD-WAN address family protocol. Performing TNP-ORF capability negotiation based on relevant protocols does not require the creation of a new protocol, which can reduce the difficulty of negotiation and improve the universality of the solution.
[0033] In a possible implementation, TNP-ORF capability negotiation is performed with the controller based on the BGP SD-WAN address family protocol, including: carrying an ORF capability negotiation TLV in a BGP SD-WAN address family protocol message interacting with the controller, wherein the type field of the ORF capability negotiation TLV indicates that the TLV is used for TNP-ORF capability negotiation. By carrying the ORF capability negotiation TLV in the BGP SD-WAN address family protocol message, the controller can perform TNP-ORF capability negotiation by receiving the BGP SD-WAN address family protocol message, thereby reducing the difficulty of negotiation.
[0034] In a possible implementation, the first routing information matched with the first ORF request information is a TNP route. Clarifying the type of routing information matched with the first ORF request information can ensure the accuracy of the routing information issued on demand to the first SD-WAN device.
[0035] In a possible implementation, the first ORF request message includes the SD-WAN route type. The content of the first ORF request message is clarified so that the controller can ensure the on-demand subscription of the first SD-WAN device to the route information according to the subscription keyword in the first ORF request message.
[0036] In a possible implementation, the first ORF request information also includes TNP information, and the TNP information includes a link ID and a link type. By adding subscription keywords such as TNP information to the first ORF request information, the accuracy of the routing information determined by the controller according to the subscription keywords can be further guaranteed.
[0037] In a possible implementation, sending a first ORF request message to a controller includes: sending a first BGP ROUTE-REFRESH message to the controller, the first BGP ROUTE-REFRESH message including an ORF Type field and a first ORFentry encoding field, the ORF Type field being used to indicate that the type of ORF is TNP-ORF, and the first ORF entryencoding field being used to carry the first ORF request message. By carrying the first ORF request message in the first BGP ROUTE-REFRESH message, the controller can successfully obtain the first ORF request message by receiving the first BGP ROUTE-REFRESH message including the ORF entry encoding field, and according to the ORF type indicated by the ORF Type field being TNP-ORF, the controller can clearly identify the ORF capability that needs to be enabled.
[0038] In one possible implementation, the first ORF request information includes a route type field, and the route type field indicates the SD-WAN TNP route. The first ORF request carries the route type field, which can clearly specify the route type to be filtered and realize accurate route information filtering.
[0039] In one possible implementation, ORF capability negotiation is used to negotiate BGP-LS SPF ORF capabilities between the controller and the first SD-WAN device. The controller and the first SD-WAN device can negotiate different types of ORF capabilities based on the type of routing information required by the first SD-WAN to ensure filtering accuracy.
[0040] In one possible implementation, the ORF capability negotiation is performed with the controller device, including: performing BGP-LS SPF ORF capability negotiation with the controller based on the BGP SD-WAN address family protocol. Performing BGP-LS SPF ORF capability negotiation based on related protocols does not require the creation of a new protocol, which can reduce the difficulty of negotiation and improve the universality of the solution.
[0041] In one possible implementation, BGP-LS SPF ORF capability negotiation is performed with the controller based on the BGP SD-WAN address family protocol, including: carrying an ORF capability negotiation TLV in the BGP-LS SPF address family protocol message interacting with the controller, wherein the type field of the ORF capability negotiation TLV indicates that the TLV is used for BGP-LS SPF ORF capability negotiation. By carrying the ORF capability negotiation TLV in the BGP SD-WAN address family protocol message, the controller can perform BGP-LS SPF ORF capability negotiation by receiving the BGP SD-WAN address family protocol message, thereby reducing the difficulty of negotiation.
[0042] In a possible implementation, sending a first ORF request message to a controller includes: sending a first BGP ROUTE-REFRESH message to the controller, the first BGP ROUTE-REFRESH message including an ORF Type field and a first ORFentry encoding field, the ORF Type field being used to indicate that the type of ORF is BGP-LS SPF ORF, and the first ORFentry encoding field being used to carry the first ORF request message. By carrying the first ORF request message in the first BGP ROUTE-REFRESH message, the controller can successfully obtain the first ORF request message by receiving the first BGP ROUTE-REFRESH message including the ORF entry encoding field, and according to the ORF type indicated by the ORF Type field being BGP-LS SPF ORF, the controller can clearly identify the ORF capability that needs to be enabled.
[0043] In a possible implementation, the first routing information matched with the first ORF request information is a BGP-LSSPF route. Clarifying the type of routing information matched with the first ORF request information can ensure the accuracy of the routing information issued to the first SD-WAN device on demand.
[0044] In a possible implementation, the first ORF request information includes a VPN ID. The content of the first ORF request information is clarified so that the controller can ensure the on-demand subscription of the first SD-WAN device to the routing information according to the subscription keyword in the first ORF request information.
[0045] In one possible implementation, the method further includes: sending a second ORF request message to the controller; and receiving second routing information sent by the controller that matches the second ORF request message. The first SD-WAN sends different ORF request messages to the controller to obtain different routing information, thereby ensuring the accuracy of the routing information issued on demand.
[0046] In a fourth aspect, a communication device is provided, the device comprising: a transceiver module, used to perform the reception and / or transmission related operations performed by the communication device in the first aspect and any corresponding possible implementation manner, or used to perform the reception and / or transmission related operations performed by the communication device in the second aspect and any corresponding possible implementation manner, or used to perform the reception and / or transmission related operations performed by the communication device in the third aspect and any corresponding possible implementation manner;
[0047] A processing module, used to perform other operations other than the reception and / or transmission related operations performed by the communication device in the first aspect and any corresponding possible implementation manner, or to perform other operations other than the reception and / or transmission related operations performed by the communication device in the second aspect and any corresponding possible implementation manner, or to perform other operations other than the reception and / or transmission related operations performed by the communication device in the third aspect and any corresponding possible implementation manner.
[0048] In a fifth aspect, another communication device is provided, the device comprising: a network interface, a memory, and a processor. The network interface, the memory, and the processor communicate with each other through an internal connection path, the memory is used to store instructions, and the processor is used to execute the instructions stored in the memory to control the network interface to receive signals and control the network interface to send signals, and when the processor executes the instructions stored in the memory, the processor executes the method in the first aspect, the second aspect, or the third aspect and possible implementations thereof.
[0049] Optionally, there are one or more processors and one or more memories.
[0050] Optionally, the memory may be integrated with the processor, or the memory may be provided separately from the processor.
[0051] In a sixth aspect, a communication device is provided, the device including a processor coupled to a memory; at least one instruction is stored in the memory, and the at least one instruction is loaded and executed by the processor, so that the device implements the method for sending a route in the first aspect and its corresponding possible implementation, or implements the method for negotiating an outbound route filtering capability in the second aspect and its corresponding possible implementation, or implements the method for obtaining a route in the third aspect and its corresponding possible implementation.
[0052] In the seventh aspect, a communication system is provided, which includes a first SD-WAN device and a controller, the controller being used to execute the method executed by the controller in the first aspect, the second aspect or the third aspect and their corresponding possible implementations, and the first SD-WAN device being used to execute the method executed by the first SD-WAN device in the first aspect, the second aspect or the third aspect and their corresponding possible implementations.
[0053] In an eighth aspect, a computer program or product is provided, which includes: computer program code, which, when executed by a computer, enables the computer to execute the methods in the above-mentioned first aspect, second aspect and third aspect and their corresponding possible implementation methods.
[0054] In a ninth aspect, a computer-readable storage medium is provided, which stores programs or instructions. When the programs or instructions are run on a computer, the methods in the above-mentioned first aspect, second aspect and third aspect and their corresponding possible implementation methods are executed.
[0055] In the tenth aspect, a chip is provided, comprising a processor for calling and executing instructions stored in a memory, so that a computer equipped with the chip executes the methods in the above-mentioned first aspect, second aspect and third aspect and their corresponding possible implementation methods.
[0056] In the eleventh aspect, another chip is provided, comprising: an input interface, an output interface, a processor and a memory, wherein the input interface, the output interface, the processor and the memory are connected via an internal connection path, and the processor is used to execute the code in the memory. When the code is executed, a computer equipped with the chip executes the methods in the above-mentioned first aspect, second aspect and third aspect and their corresponding possible implementation methods.
[0057] It should be understood that the beneficial effects achieved by the technical solutions of the fourth to eleventh aspects of the present application and the corresponding possible implementation methods can be referred to the above-mentioned technical effects of the first, second and third aspects and their corresponding possible implementation methods, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS
[0058] Figure 1 A schematic diagram of the structure of an SD-WAN network provided in an embodiment of the present application;
[0059] Figure 2 An implementation scenario diagram provided for an embodiment of the present application;
[0060] Figure 3 A flowchart of a method for sending and obtaining a route provided in an embodiment of the present application;
[0061] Figure 4 A schematic diagram of a partial format of an open message provided in an embodiment of the present application;
[0062] Figure 5 A schematic diagram of the format of a first border gateway protocol routing refresh message provided in an embodiment of the present application;
[0063] Figure 6 A schematic diagram of the structure of an ORF table item encoding field provided in an embodiment of the present application;
[0064] Figure 7 A schematic diagram of the structure of a type-specific partial field provided in an embodiment of the present application;
[0065] Figure 8 A flowchart of a method for negotiating outbound route filtering capabilities provided in an embodiment of the present application;
[0066] Fig. 9 A schematic diagram of the structure of a device for sending a route provided in an embodiment of the present application;
[0067] Fig.10 A schematic diagram of the structure of an outbound route filtering capability negotiation device provided in an embodiment of the present application;
[0068] Fig.11 A schematic diagram of the structure of a device for obtaining a route provided in an embodiment of the present application;
[0069] Fig.12 A schematic diagram of the structure of a device for sending routes, negotiating outbound route filtering capabilities, and obtaining routes provided in an embodiment of the present application;
[0070] Fig.13 A structural diagram of another device for sending routes, negotiating outbound route filtering capabilities, and obtaining routes provided in an embodiment of the present application. DETAILED DESCRIPTION
[0071] The terms used in the implementation section of this application are only used to explain the specific embodiments of this application and are not intended to limit this application.
[0072] With the development of communication technology and cloud computing technology, in cloud service scenarios, enterprises can access multi-cloud services through the infrastructure built on multiple cloud platforms, thus achieving the normal operation of digital business. For example, enterprises can access multi-cloud services through SD-WAN. SD-WAN networking can not only provide enterprises with cloud services such as resource management, resource caching and data computing, but also provide enterprises with service-level agreement (SLA) routing, traffic optimization and scheduling services to meet the diversified commercial demands of enterprises.
[0073] For example, see Figure 1 , Figure 1 A structural diagram of an SD-WAN network is shown, including devices A to I, and devices A to I are connected through a multi-cloud network. Devices A to I can all be network element devices in the SD-WAN network, such as a point of presence (POP) or customer premise equipment (CPE), which is the entry point for enterprise users to access the network that provides cloud services. Different devices can be located in different regions. Depending on the region where the device is located and the cloud service corresponding to the device, the device can be divided into different types of devices, such as provincial core devices and intra-provincial devices. Among them, the provincial core device is a central device within a province, and different provinces communicate with each other through the provincial core device. For example, device A is the provincial core device of Province A, and device B is the provincial core device of Province B. Through the interaction between device A and device B, communication between Province A and Province B can be achieved. The intra-provincial device is a backbone device within a province. A province can include multiple intra-provincial devices, such as Figure 1 Device D and device E are intra-provincial devices in Province A, device F and device G are intra-provincial devices in Province B, and device H and device I are intra-provincial devices in Province C. The provincial core devices in the SD-WAN network constitute the high-speed fully interconnected inter-provincial backbone network in the SD-WAN network. Multiple intra-provincial devices in a province and the provincial core devices constitute a fully interconnected intra-provincial network in a province. The intra-provincial devices in a province can interact directly with each other, and the intra-provincial devices in different provinces need to interact across the inter-provincial backbone network.
[0074] exist Figure 1In the SD-WAN networking scenario shown, the routing information of each device can be spread to any other device reachable by any protocol neighbor through the SD-WAN address family protocol in BGP or the external border gateway protocol (EBGP), but any device in the SD-WAN network does not need to perceive the routing information of each device in the SD-WAN network. For example, the devices in Province A do not need to perceive the routing information of the devices in Province B. Therefore, in the SD-WAN scenario of the related technology, each device receives and processes a large amount of unnecessary routing information, resulting in a waste of resources such as the device's memory and central processing unit (CPU), which puts pressure on the device. Especially when the business demands of enterprises are more diversified, the resource pressure of each device in the SD-WAN network is further increased. Therefore, there is an urgent need for a method for SD-WAN devices to subscribe to routing information on demand to prevent SD-WAN devices from receiving unnecessary routing information, so as to reduce the resource pressure of SD-WAN devices.
[0075] The embodiment of the present application provides a method for sending routes, negotiating outbound route filtering capabilities, and obtaining routes. The method can reduce the resource occupation of SD-WAN devices, realize on-demand subscription of routing information by SD-WAN devices, that is, sending routing information to SD-WAN on demand, reducing the occupation of SD-WAN device resources by unnecessary routing information, and enabling SD-WAN devices to deploy more services based on limited resources to meet more business demands of enterprise users. For example, the method can be applied to Figure 2 In the implementation scenario shown, see Figure 2 , the implementation scenario includes a controller, devices A to E. Among them, the controller is a control device of the management and control plane, and the controller can be, for example, an RR, or a device with an integrated route reflector function. The controller can receive routing information and other information of each device in the SD-WAN network, and filter and reflect the routing information. Devices A to E can be, for example, network engines (NE), access routers (AR), switches or firewalls. Devices A, B and C build a metropolitan area network by accessing the multi-protocol label switching virtual private network (MPLS VPN) of an operator or an Internet service provider (ISP). Devices C, D and E form an inter-provincial backbone network by accessing another MPLS VPN.
[0076] See also Figure 3 , showing a schematic diagram of a method for sending and obtaining routes, which can be applied to Figure 2 The controller and device A to device E in the method include but are not limited to the following S301 to S305, wherein S301 and S305 are methods for obtaining routes, and S302, S303 and S304 are methods for sending routes.
[0077] S301, the first SD-WAN device sends a first ORF request message to the controller.
[0078] The first SD-WAN device may be any device in the SD-WAN network except the controller, for example Figure 2 Device A to device E in. The content of the first ORF request information can be determined according to the type of first routing information that the first SD-WAN device needs to request. For example, the first ORF request information can be divided into ORF request information for requesting TNP routing and ORF request information for requesting BGP-LS SPF routing.
[0079] Regardless of the type of content of the first ORF request information sent by the first SD-WAN device to the controller, the first SD-WAN device can perform ORF capability negotiation with the controller device before sending the first ORF request information to the controller. The ORF capability negotiation is used to negotiate the ORF capability between the controller and the first SD-WAN device. The first SD-WAN device performs ORF capability negotiation with the controller, so that the controller can filter the routing information sent to the first SD-WAN according to the first ORF request information to ensure the on-demand release of the routing information.
[0080] In an embodiment of the present application, the first SD-WAN device and the controller can negotiate multiple ORF capabilities. Exemplarily, the embodiment of the present application divides the process of the first SD-WAN device sending the first ORF request information and the first SD-WAN device negotiating the ORF capabilities with the controller into two different situations: situation A1 and situation A2, according to the type of the first routing information to be obtained by the first SD-WAN device and the different ORF capabilities that the first SD-WAN device and the controller need to negotiate.
[0081] In case A1, the first routing information matched with the first ORF request information is TNP routing, that is, the first ORF request information is request information for requesting TNP routing. In this case, ORF capability negotiation is used to negotiate TNP-ORF capability between the controller and the first SD-WAN device.
[0082] The first ORF request information may include the SD-WAN routing type. Optionally, the first ORF request information may also include TNP information, and the TNP information includes a link identifier (ID) and a link type. Among them, the SD-WAN routing type may include static routing, system routing, or cloud network routing. The TNP information included in the first ORF request information may be the TNP information of a TNP on the first SD-WAN device, or it may be the TNP information of multiple TNPs on the first SD-WAN device, which is not limited in this embodiment of the present application. The link types included in the TNP information may include point-to-point links (peer to peer link, P2P link), point to multipoint links (point to multiple point link, P2MP link), full mesh links (full mesh link) or hub spoke types, and the link ID may include but is not limited to values, characters or strings that can identify the identity of the link. The link type and link ID in the TNP information may have a corresponding relationship. If the link type is P2P link, P2MP link or full mesh link, the link ID may be link ID. If the link type is hub spoke, the link ID may be a hub site ID.
[0083] In one possible implementation, the TNP information is used to establish a link between the first SD-WAN device and the matching device. The matching device refers to a device that needs to establish a link with the first SD-WAN device, that is, the device to which the first TNP route required by the first SD-WAN device belongs. The link established between the first SD-WAN device and the matching device can be, for example, an SD-WAN tunnel. The SD-WAN tunnel can be an overlay tunnel established based on cross-heterogeneous operator lines or dedicated lines. The dedicated line can include an Internet line, a fifth generation mobile communication technology (5G) line, an MPLS VPN dedicated line, a multiple spanning tree algorithm and protocol (MSTP) dedicated line, etc.
[0084] Before the first SD-WAN device sends the first ORF request information to the controller, the first SD-WAN device needs to generate the first ORF request information based on the acquired TNP information and SD-WAN route type. In the embodiment of the present application, there is no limitation on the manner in which the first SD-WAN device acquires the TNP information and the SD-WAN route type. For example, the TNP information and the SD-WAN route type can be sent by the controller to the first SD-WAN device, or can be statically configured on the first SD-WAN device.
[0085] Below, taking the example of sending TNP information from the controller to the first SD-WAN device, the process of the first SD-WAN device acquiring TNP information is explained. The controller can plan the link relationship and topology relationship in the SD-WAN network according to the needs of enterprise users, that is, determine the various SD-WAN tunnels to be established in the SD-WAN network, and the various devices corresponding to each SD-WAN tunnel, and globally distribute the TNP information corresponding to each device to each device, so that each device can be associated with the link relationship corresponding to each device, and each device can acquire the TNP information corresponding to each device, including the acquisition of TNP information by the first SD-WAN device.
[0086] For example, the controller determines that a total of five tunnels need to be established in the SD-WAN network based on the needs of enterprise users, and the tunnel that needs to be established through the first SD-WAN device is Tunnel 1. The controller can send the TNP information of Tunnel 1 to the first SD-WAN device. The first SD-WAN device completes the acquisition of TNP information by receiving the TNP information of Tunnel 1. It should be noted that the controller may not send the TNP information of Tunnel 2 to Tunnel 4 to the first SD-WAN device, so as to reduce the perception of non-essential information by the first SD-WAN device.
[0087] In one possible implementation, the controller will assign matching TNP information to the two devices corresponding to the same SD-WAN tunnel to ensure that the two devices can match based on the matching TNP information and successfully establish the SD-WAN tunnel. For example, the two devices corresponding to tunnel 1 are the first SD-WAN device and the matching device, respectively. The controller can assign the TNP information corresponding to tunnel 1 to the first SD-WAN device, and assign the TNP information that matches the TNP information obtained by the first SD-WAN device to the matching device. Optionally, the same link type in the two TNP information can be regarded as matching the link types in the two TNP information, and the same link IDs in the two TNP information can be regarded as matching the link IDs in the two TNP information if they are the same or are reciprocal or opposite to each other. The embodiment of the present application does not limit the manner in which the link types and link IDs in the two TNP information are matched.
[0088] After obtaining the TNP information and the SD-WAN routing type, the first SD-WAN device may generate the first ORF request information to complete the acquisition of the first ORF request information. Optionally, after obtaining the first ORF request information, the first SD-WAN device may not immediately send the first ORF request information to the controller, but may send the first ORF request information to the controller when the first SD-WAN device needs to start establishing a tunnel. For example, after receiving the service flow, the first SD-WAN device may determine that the first SD-WAN device needs to start establishing a tunnel when confirming that the service flow needs to be forwarded through the tunnel to be established, and then determine that the first SD-WAN device can send the first ORF request information to the controller.
[0089] Because the first SD-WAN device needs to establish a tunnel according to the TNP route of another device corresponding to the tunnel when establishing the SD-WAN tunnel, that is, it needs to establish a tunnel according to the TNP route of the matching device. The first SD-WAN device can use the first ORF request information as the key information for subscribing to the TNP route of the matching device, so that the controller can return the TNP route of the matching device to the first SD-WAN device based on the first ORF request information according to the negotiation result between the first SD-WAN device and the controller. Therefore, before the first SD-WAN device sends the first ORF request information to the controller, the first SD-WAN device can negotiate the TNP-ORF capability with the controller. In a possible implementation, the first SD-WAN device can negotiate the TNP-ORF capability with the controller based on the BGP SD-WAN address family protocol. Optionally, the first SD-WAN device can carry an ORF capability negotiation TLV in the BGP SD-WAN address family protocol message interacting with the controller, wherein the type field of the ORF capability negotiation TLV indicates that the TLV is used for TNP-ORF capability negotiation.
[0090] The BGP SD-WAN address family protocol message can be an open message or an update message. The first SD-WAN device can perform TNP-ORF capability negotiation when the first SD-WAN device establishes a BGP neighbor with the controller, or can perform ORF capability negotiation after the first SD-WAN device establishes a BGP neighbor with the controller. The embodiments of the present application do not limit this.
[0091] In one possible implementation, before the first SD-WAN device and the controller perform ORF capability negotiation information, the first SD-WAN device and the controller can also be enabled to have ORF capabilities through configuration. For example, by configuring the correspondence between the capabilities supported by BGP of the first SD-WAN device and the controller and the capability code (capability code), it is possible to indicate that when the first SD-WAN device and the controller receive a message including the capability code, they can determine the capabilities supported by BGP that need to be negotiated by the message. Exemplarily, if the capability code is 1, it indicates that the supported BGP capability is the address family capability; if the capability code is 2, it indicates that the supported BGP capability is the refresh capability; if the capability code is 3, it indicates that the supported BGP capability is the ORF capability. In this case, the first SD-WAN device can send a BGP SD-WAN address family protocol message to the controller to negotiate the TNP-ORF capability in the ORF capability.
[0092] The ORF capability type, i.e., capability code, carried in the BGP SD-WAN address family protocol message may be 3, indicating that the BGP capability that the first SD-WAN device and the controller need to negotiate is the ORF capability. The value included in the ORF capability length field carried in the BGP SD-WAN address family protocol message may be variable. Optionally, the ORF capability value field may include various fields for negotiating the capability of ORF.
[0093] For example, see Figure 4 , showing a partial format diagram of an open message, Figure 4 All fields in can be used as ORF capability value fields, such as address family identifier (AFI) field, reserved field, subsequent address family identifier (SAFI) field, ORF quantity field, ORF type field, send / receive field, etc. Below, each field is explained separately.
[0094] The address family identification field may also be referred to as the primary address family identification field. The size of the address family identification field may be 2 octets. The address family identification field is used to indicate the address family to which the route belongs, such as a 4-byte address family or a 6-byte address family. If the address family to which the route belongs is a 4-byte address family, the route may be an address of Internet Protocol version 4 (IPv4). If the address family to which the route belongs is a 6-byte address family, the route may be an address of Internet Protocol version 6 (IPv6).
[0095] The reserved field can also be called a reserved field. The size of the reserved field can be 1 octet. The reserved field can be used for protocol extension. For example, when extending the BGP SD-WAN address family protocol, if you need to add new fields related to the address family identifier in the message, you can insert the value corresponding to the field to be added into the reserved field without changing the current format of the message.
[0096] The sub-address family field is used to indicate the sub-address family to which the route belongs. The size of the sub-address family identification field can be 1 octet. The value of the sub-address family identification can indicate the transmission mode of the route. For example, if the sub-address family identification is 1, it means that the transmission mode of the route is unicast. If the sub-address family identification is 2, it means that the transmission mode of the route is multicast. If the sub-address family identification is 74, it means that the transmission mode of the route is to send to the peer.
[0097] The size of the ORF quantity field in the ORF capability negotiation information can be 1 octet, and the value of the ORF quantity field is the number of ORF types included in the ORF capability negotiation information. For example, if the number of ORF types included in the ORF capability negotiation information is 1, the value of the ORF quantity field is 1; if the number of ORF types included in the ORF capability negotiation information is 2, the value of the ORF quantity field is 2.
[0098] The size of the ORF type field can be 1 octet. Different values in the ORF type field can represent different ORF types, and different ORF types can represent different ORF capabilities. In an embodiment of the present application, a specific value can be defined for the ORF type field so that the ORF type field carries the type of route that needs to be filtered, that is, carries TNP-ORF-TYPE. For example, the value of the ORF type field in the ORF capability negotiation information can be set to 415, so that the ORF capability negotiation information instructs the controller to filter out the TNP route of the device that does not correspond to the first ORF request information, and only sends the TNP route of the matching device corresponding to the first ORF request information to the first SD-WAN device, that is, the controller obtains the type of route that meets the filtering condition through filtering, and the filtering condition is that the SD-WAN tunnel information corresponding to the TNP route matches the SD-WAN tunnel information in the first ORF request information.
[0099] The size of the Send / Receive field can be 1 octet, and the value of the Send / Receive field can indicate whether the first SD-WAN device agrees to send a message to the peer or receive a message from the peer. For example, if the value of the Send / Receive field is 1, it means that the first SD-WAN device agrees to receive ORF table items from its peer. If the value of the Send / Receive field is 2, it means that the first SD-WAN device agrees to send ORF table items to the peer. If the value of the Send / Receive field is 3, it means that the first SD-WAN device agrees to both send ORF table items to the peer and receive ORF table items from the peer.
[0100] After the first SD-WAN device completes the TNP-ORF capability negotiation with the controller, the first SD-WAN device may send a first ORF request message to the controller when a tunnel needs to be established. The embodiment of the present application does not limit the manner in which the first SD-WAN device sends the first ORF request message. For example, the first SD-WAN device sending the first ORF request message may include sending a first BGP ROUTE-REFRESH message to the controller, the first BGP ROUTE-REFRESH message including an ORFType field and a first ORF entry encoding field, the ORF Type field is used to indicate that the type of ORF is TNP-ORF, and the first ORF entry encoding field is used to carry the first ORF request information.
[0101] For example, see Figure 5, showing a format diagram of a first BGP ROUTE-REFRESH message. The first BGP ROUTE-REFRESH message includes an address family identification field, a reserved field, a sub-address family identification field, a refresh time field, an ORF type field, an ORF table item length field, a first ORF table item field, a second ORF table item field, and a third ORF table item field, and N can be a positive integer of any size. Among them, since the first BGP ROUTE-REFRESH message may include multiple ORF table item fields, multiple groups of ORF fields can be generated based on the ORF fields of each type according to the ORF type corresponding to the ORF field, and a group of ORF fields corresponds to one ORF type. The first BGP ROUTE-REFRESH message may include one or more groups of ORF fields, and the length of each group of ORF fields may be the same or different.
[0102] The description of the address family identification field, reserved field, sub-address family identification field, and ORF type field of the first BGP ROUTE-REFRESH message can refer to the above description of Figure 4 The remaining fields of the first BGPROUTE-REFRESH message are explained below.
[0103] The size of the refresh time field in the first BGP ROUTE-REFRESH message can be 1 octet, and the value included in the refresh time field is used to indicate when the peer publishes the route. In an embodiment of the present application, the refresh time field in the first BGP ROUTE-REFRESH message is used to indicate when the controller sends the route of the second device to the first SD-WAN device.
[0104] The first BGP ROUTE-REFRESH message may include at least one group of ORF fields, and a group of ORF fields may include an ORF type field and an ORF table entry length field, as well as at least one ORF table entry field from the first ORF table entry field to the second ORF table entry field. The ORF table entry field may also be referred to as an ORF table entry encoding field, i.e., an ORF entry encoding field. The size of the ORF table entry length field may be 2 octets, and the value included in the ORF table entry length field is the total size of the memory occupied by each ORF table entry field in a group of ORF fields. For example, a group of ORF fields includes a first ORF table entry field, a second ORF table entry field, and a third ORF table entry field, and the sizes occupied by the three ORF table entry fields are all 4 octets, and the size of the memory occupied by the group of ORF fields is 12 octets, then the value of the ORF table entry length field corresponding to the group of ORF fields is 12 octets.
[0105] The size of each ORF table entry field can be a variable, and the ORF table entry code field is used to carry the first ORF request information. Figure 6 As shown. An ORF table entry encoding field may include an action field, a match field, a reserved field, and a type specific part field. The address family and sub-address family corresponding to the ORF table entry may be configured in the address family field and the sub-address family field of the first BGP ROUTE-REFRESH message.
[0106] The size of the action field can be 2 bits, and different values included in the action field can indicate different actions. For example, if the value of the action field is 0, the indicated action can be to add a route; if the value of the action field is 1, the indicated action can be to delete a route; if the value of the action field is 2, it can indicate to delete all routes.
[0107] The size of the match field can be 1 bit. If the value of the match field is 0, it means the match is successful, and if the value of the match field is 1, it means the match fails. Optionally, when the value of the action field is 0 or 1, the action of the match field can be executed. If the value of the action field is 2, all routes will be deleted and the action of the match field will not be executed.
[0108] The size of the reserved field can be 5 bits, which is used to modify the ORF table entry field in the first BGP ROUTE-REFRESH message. When the first SD-WAN device sends the first BGP ROUTE-REFRESH message, the value of the reserved field can be 0, and when the controller receives the first BGP ROUTE-REFRESH message, the reserved field can be ignored.
[0109] The size of the type-specific part field can be variable, determined according to the content contained in the type-specific field. In the embodiment of the present application, the type-specific field can be used to carry key information for instructing the controller to filter the TNP route, that is, to carry the first ORF request information. The type-specific part field can include multiple fields, for example, see Figure 7 , shows a schematic diagram of the structure of a type-specific part field. The type-specific part field may include a link type field and a link identification field. The size of the link type field may be 4 octets, and the value of the link type field is used to indicate the type of the link. The size of the link identification field may be 4 octets, and the value of the link identification field is used to indicate the identification of the link.
[0110] Optionally, the first ORF request information includes a routing type field, and the routing type field indicates SD-WAN TNP routing. Figure 7 As shown, the size of the routing type field may be 2 octets, and the value of the networking type field may be a routing type value, for example, 200.
[0111] In case A2, the first routing information matched with the first ORF request information is a BGP-LS SPF route, that is, the first ORF request information is a request information for requesting information of the VPN instance to which the first SD-WAN device belongs. In this case, the ORF capability negotiation is used to negotiate the BGP-LS SPF ORF capability between the controller and the first SD-WAN device.
[0112] Among them, the first ORF request information includes VPN ID, which is an identifier used to identify different VPN instances in the SD-WAN network. The first SD-WAN device can belong to one or more different VPN instances. Therefore, the first SD-WAN device uses VPN ID as the key information for requesting BGP-LS SPF routing, which enables the controller to issue BGP-LS SPF routing to the first SD-WAN device on demand based on VPN ID.
[0113] Before the first SD-WAN device sends the first ORF request information to the controller, the first SD-WAN device can obtain the VPN ID and generate the first ORF request information according to the VPN ID. In an embodiment of the present application, the VPN ID can be sent by the controller to the first SD-WAN device, or it can be statically configured on the first SD-WAN device, which will not be repeated here. Similar to the negotiation of TNP-ORF capabilities between the first SD-WAN device and the controller, the first SD-WAN device and the controller can also negotiate BGP-LS SPF ORF capabilities before the first SD-WAN device sends the first ORF request information to the controller. In one possible implementation, the first SD-WAN device can perform BGP-LS SPF ORF capability negotiation with the controller based on the BGP SD-WAN address family protocol. Optionally, the first SD-WAN device can carry an ORF capability negotiation TLV in the BGP-LS SPF address family protocol message interacting with the controller. Among them, the type field of the ORF capability negotiation TLV indicates that the TLV is used for BGP-LS SPF ORF capability negotiation.
[0114] Similar to situation A1, the BGP SD-WAN address family protocol message in situation A2 can also be an open message or an update message. The timing for the first SD-WAN device and the controller to negotiate the BGP-LS SPF ORF capability can be when the first SD-WAN device and the controller establish a BGP neighbor, or after the first SD-WAN device and the controller establish a BGP neighbor. The embodiment of the present application does not limit this.
[0115] The process of the first SD-WAN device and the controller negotiating the BGP-LS SPF ORF capability can refer to the process of the first SD-WAN device and the controller negotiating the TNP-ORF capability, which will not be repeated here. It should be noted that when the first SD-WAN device negotiates the BGP-LS SPF ORF capability with the controller, the value of the ORF type field in the message exchanged between the first SD-WAN device and the controller may be different from the value of the ORF type field in the message exchanged between the first SD-WAN device and the controller when the first SD-WAN device and the controller negotiate the TNP-ORF capability. In addition, when the first SD-WAN device and the controller negotiate the BGP-LSSPF ORF capability, the value of the sub-address family field in the message exchanged between the first SD-WAN device and the controller may also be different from the value of the sub-address family field in the message exchanged between the first SD-WAN device and the controller when the first SD-WAN device and the controller negotiate the TNP-ORF capability, for example, it may be 80.
[0116] After the first SD-WAN device completes the BGP-LS SPF ORF capability negotiation with the controller, the first SD-WAN device may send a first ORF request message to the controller when VPN information is needed. Exemplarily, the first SD-WAN device may send a first BGP ROUTE-REFRESH message to the controller, the first BGP ROUTE-REFRESH message including an ORF Type field and a first ORF entry encoding field, the ORF Type field being used to indicate that the type of ORF is BGP-LS SPF ORF, and the first ORF entry encoding field being used to carry the first ORF request message.
[0117] The format of the first BGP ROUTE-REFRESH message may refer to the description in case A1, which will not be described again. Optionally, in case A2, the type-specific field in the first BGP ROUTE-REFRESH message may include a VPN ID.
[0118] In the embodiment of the present application, the first SD-WAN device negotiates ORF capabilities with the controller, so that the controller has multiple ORF capabilities. The first SD-WAN device sends the first ORF request information to the controller as the key information for obtaining the first routing information, so as to obtain the first routing information, thereby realizing the on-demand acquisition of the first routing information by the first SD-WAN device.
[0119] S302, the controller receives the first ORF request information sent by the first SD-WAN device.
[0120] In the embodiment of the present application, the process of the controller receiving the first ORF request information sent by the first SD-WAN device can be divided into two different situations, namely, situation B1 and situation B2, according to the different contents of the first ORF request information received by the controller. Moreover, no matter what content the first ORF request information received by the controller includes, the controller can perform ORF capability negotiation with the first SD-WAN device before receiving the first ORF request information sent by the first SD-WAN device. The ORF capability negotiation is used to negotiate the ORF capability between the controller and the first SD-WAN device.
[0121] In case B1, the first ORF request information includes the SD-WAN route type. Optionally, the first ORF request information also includes TNP information, and the TNP information includes a link ID and a link type. In this case, the first route information matching the first ORF request information is a TNP route.
[0122] Corresponding to case A1, in case B1, ORF capability negotiation is used to negotiate TNP-ORF capability between the controller and the first SD-WAN device. Exemplarily, the controller performs ORF capability negotiation with the first SD-WAN device, and can perform TNP-ORF capability negotiation with the first SD-WAN device based on the BGP SD-WAN address family protocol. For example, the controller can carry an ORF capability negotiation type length value TLV in the BGP SD-WAN address family protocol message interacting with the first SD-WAN device, wherein the type field of the ORF capability negotiation TLV indicates that the TLV is used for TNP-ORF capability negotiation.
[0123] In case B1, the controller receives the first ORF request information sent by the first SD-WAN device, which may include: receiving the first BGP ROUTE-REFRESH message sent by the first SD-WAN device, the first BGP ROUTE-REFRESH message including an ORF Type field and a first ORF entry encoding field, the ORF Type field is used to indicate that the type of ORF is TNP-ORF, and the first ORF entry encoding field is used to carry the first ORF request information. Among them, the first ORF request information includes a routing type field, and the routing type field indicates SD-WAN TNP routing.
[0124] The process of TNP-ORF capability negotiation between the controller and the first SD-WAN device, as well as the format of the first ORF request information received by the controller can refer to situation A1 in S301, and will not be repeated here.
[0125] Case B2: The first ORF request information includes a VPN ID. In this case, the first routing information matched with the first ORF request information is a BGP-LS SPF route.
[0126] Corresponding to situation A2, in situation B2, ORF capability negotiation is used to negotiate BGP-LS SPF ORF capabilities between the controller and the first SD-WAN device. Exemplarily, the controller and the first SD-WAN device can perform BGP-LS SPF ORF capability negotiation with the first SD-WAN device based on the BGP SD-WAN address family protocol. For example, the controller can perform BGP-LS SPF ORF capability negotiation with the first SD-WAN device based on the BGP SD-WAN address family protocol, including: carrying an ORF capability negotiation TLV in the BGP-LS SPF address family protocol message interacting with the first SD-WAN device, wherein the type field of the ORF capability negotiation TLV indicates that the TLV is used for BGP-LS SPF ORF capability negotiation.
[0127] In case B2, the controller receives the first ORF request information sent by the first SD-WAN device, including: receiving the first BGP ROUTE-REFRESH message sent by the first SD-WAN device, the first BGP ROUTE-REFRESH message including an ORFType field and a first ORF entry encoding field, the ORF Type field is used to indicate that the type of ORF is BGP-LSSPF ORF, and the first ORF entry encoding field is used to carry the first ORF request information.
[0128] The process of BGP-LS SPF ORF capability negotiation between the controller and the first SD-WAN device, as well as the format of the first ORF request information received by the controller can refer to situation A2 in S301 and will not be repeated here.
[0129] S303: The controller obtains first routing information matching the first ORF request information.
[0130] The embodiment of the present application does not limit the method for the controller to obtain the first routing information. For example, if the first routing information matching the first ORF request information is a TNP route, the controller can determine the TNP route corresponding to the TNP information in the first ORF request information as the first TNP route in the locally stored TNP routes. The TNP routes stored locally by the controller can be TNP routes sent to the controller by each SD-WAN device in the SD-WAN network.
[0131] Since the controller knows the correspondence between each device and each TNP information, the controller can determine two SD-WAN devices corresponding to the TNP information in the first ORF request information in the TNP routes of each device, one of which is the first SD-WAN device and the other is the matching device. The controller can then determine the TNP route of the matching device as the first TNP route to obtain the first route.
[0132] Alternatively, if the first routing information matching the first ORF request information is a BGP-LS SPF route, the controller can determine the VPN corresponding to the VPN ID in the first ORF request information in each VPN in the SD-WAN network, and determine the information of the VPN, that is, the BGP-LS SPF route corresponding to the VPN, as the first routing information.
[0133] S304, the controller sends first routing information to the first SD-WAN device.
[0134] In the embodiment of the present application, there is no limitation on the method by which the controller sends the first routing information to the first SD-WAN device. Exemplarily, the controller may send a matching message including the first routing information to the first SD-WAN device to complete the sending of the first routing information.
[0135] In a possible implementation, the controller may not only send the first routing information to the first SD-WAN device, but also send the security association (SA) information corresponding to the matching device to the first SD-WAN device. The SA information is information that can be used to establish a security association between the first SD-WAN device and the matching device, and is used for the first SD-WAN device and the matching device to negotiate the security protocol used by both parties, the encapsulation mode used for data transmission, the encryption and verification algorithm used by the protocol, the key used for data transmission, etc., so that the first SD-WAN device and the matching device can establish a link based on Internet Protocol Security (IPSec).
[0136] S305, the first SD-WAN device receives the first routing information sent by the controller that matches the first ORF request information.
[0137] The first SD-WAN device can receive the first routing information by receiving a matching message including the first routing information sent by the controller. In one possible implementation, if the first routing information is a TNP route, after receiving the first routing information, the first SD-WAN device can establish an SD-WAN tunnel with the matching device based on the first routing information.
[0138] Exemplarily, the first SD-WAN device may send a request to establish a tunnel to the matching device according to the IP address of the matching device included in the first routing information. If the first SD-WAN device receives information from the matching device agreeing to establish a tunnel, the first SD-WAN device may establish an SD-WAN tunnel with the matching device based on the TNP information. For example, if the link information obtained by the first SD-WAN device includes an SD-WAN tunnel type of P2P and an SD-WAN tunnel identifier of 5, the first SD-WAN device may establish an SD-WAN tunnel of type P2P and identifier 5 with the matching device.
[0139] Optionally, the first SD-WAN device and the matching device can also establish an IPSec SD-WAN tunnel with the matching device based on the SA information sent by the controller to ensure the communication security when the first SD-WAN device and the matching device interact through the SD-WAN tunnel.
[0140] After the controller issues the required TNP routes to each SD-WAN device in the SD-WAN network, each device can establish a link through TNP based on the obtained TNP routes and TNP information to complete the establishment of each VPN in the SD-WAN network. Figure 2In the example, SD-WAN tunnel link 1 with link ID 1 and link type P2MP is established between TNP5 of device A and TNP5 of device C; SD-WAN tunnel link 2 with link ID 2 and link type P2MP is established between TNP5 of device B and TNP5 of device C; SD-WAN tunnel link 3 with link ID 3 and link type full mesh is established between TNP6 of device C and TNP3 of device D; SD-WAN tunnel link 4 with link ID 4 and link type fullmesh is established between TNP6 of device C and TNP4 of device E; SD-WAN tunnel link 5 with link ID 5 and link type full mesh is established between TNP3 of device D and TNP4 of device E. Among them, device A, device B and device C establish VPN1 through tunnel link 1 and tunnel link 2; device C, device D and device E establish VPN2 through tunnel link 3, tunnel link 4 and tunnel link 5.
[0141] Since the VPN in the SD-WAN network can only be established after each device establishes a tunnel link, in an embodiment of the present application, the first SD-WAN device can first obtain the first routing information of the TNP routing type, and then obtain the first routing information of the BGP-LS SPF type.
[0142] In the embodiment of the present application, the first SD-WAN device may have multiple TNPs, each of which may be used to establish a different link. Therefore, in addition to being able to send a first ORF request message to the controller, the first SD-WAN device may also send a second ORF request message to the controller to obtain second routing information, thereby establishing another tunnel through the TNP of the first SD-WAN device.
[0143] The controller receives the second ORF request information sent by the first SD-WAN device, and obtains the second routing information matching the second ORF request. The process of the controller obtaining the second routing information can refer to the process of obtaining the first routing information, which will not be repeated here. The controller sends the second routing information to the first SD-WAN device, and the first SD-WAN device receives the second routing information sent by the controller, so that the first SD-WAN device can obtain the routing information on demand.
[0144] In addition, the controller can also interact with the second SD-WAN device and issue routing information to the second SD-WAN device as needed. For example, the controller can receive the third ORF request information sent by the second SD-WAN device; obtain the third routing information matching the third ORF request; and send the third routing information to the second SD-WAN device. The process of the controller sending the third routing information to the second SD-WAN device can refer to the process of the controller sending the first routing information to the first SD-WAN device, which will not be repeated here.
[0145] See also Figure 8 , Figure 8 A schematic flow chart of a method for negotiating outbound route filtering capability is shown. The method includes S801.
[0146] S801, the controller performs ORF capability negotiation with the first SD-WAN device, and the ORF capability negotiation is used to negotiate the ORF capability between the controller and the first SD-WAN device.
[0147] The implementation method of the outbound route filtering capability negotiation method can refer to the above Figure 3 The related implementations of S301 and S302 shown are not described in detail here.
[0148] In the related art, the routing information of each device is usually exchanged between SD-WAN devices through the standard BGP tunnel encapsulation attribute, so that any SD-WAN device can obtain the routing information of each device in the SD-WAN network, and then select the required route from the TNP route of each device according to the enterprise user business, and establish the SD-WAN tunnel. The SD-WAN devices in the related art perceive a large amount of unnecessary routing information, resulting in a waste of SD-WAN device resources.
[0149] This application implements multiple ORF capability negotiation between SD-WAN devices and controllers based on the BGP SD-WAN address family protocol, so that the controller can diffuse multiple routing information on demand in the SD-WAN network, avoiding the SD-WAN device's perception of non-business-related routing information, enhancing business security isolation capabilities, and reducing resource occupation and waste of SD-WAN devices.
[0150] The above describes the method for sending routes, negotiating outbound route filtering capabilities, and obtaining routes provided by the embodiments of the present application. Corresponding to the above methods, the embodiments of the present application also provide a device for sending routes, a device for negotiating outbound route filtering capabilities, and a device for obtaining routes. The device for sending routes is applied to the controller, and the device for obtaining routes is applied to the first SD-WAN device. Fig. 9 As shown, the device for sending routes provided in the embodiment of the present application includes the following modules.
[0151] The receiving module 901 is used to receive the first ORF request information sent by the first SD-WAN device; the obtaining module 902 is used to obtain the first routing information matching the first ORF request information; the sending module 903 is used to send the first routing information to the first SD-WAN device.
[0152] In one possible implementation, the apparatus further includes a negotiation module, which is used to perform ORF capability negotiation with the first SD-WAN device, and the ORF capability negotiation is used to negotiate the ORF capability between the controller and the first SD-WAN device.
[0153] In one possible implementation, ORF capability negotiation is used to negotiate TNP-ORF capabilities between the controller and the first SD-WAN device.
[0154] In one possible implementation, the negotiation module is used to negotiate TNP-ORF capabilities with the first SD-WAN device based on the BGP SD-WAN address family protocol.
[0155] In one possible implementation, the negotiation module is used to carry an ORF capability negotiation TLV in a BGP SD-WAN address family protocol message interacting with the first SD-WAN device, wherein the type field of the ORF capability negotiation TLV indicates that the TLV is used for TNP-ORF capability negotiation.
[0156] In a possible implementation manner, the first routing information matching the first ORF request information is a TNP route.
[0157] In one possible implementation, the first ORF request information includes the SD-WAN routing type.
[0158] In a possible implementation manner, the first ORF request information further includes TNP information, and the TNP information includes a link ID and a link type.
[0159] In one possible implementation, the receiving module 901 is used to receive a first BGP ROUTE-REFRESH message sent by a first SD-WAN device, the first BGP ROUTE-REFRESH message includes an ORF Type field and a first ORFentry encoding field, the ORF Type field is used to indicate that the type of ORF is TNP-ORF, and the first ORF entryencoding field is used to carry the first ORF request information.
[0160] In one possible implementation, the first ORF request information includes a routing type field, and the routing type field indicates SD-WAN TNP routing.
[0161] In one possible implementation, ORF capability negotiation is used to negotiate BGP-LS SPF ORF capabilities between the controller and the first SD-WAN device.
[0162] In one possible implementation, the negotiation module is used to perform BGP-LS SPF ORF capability negotiation with the first SD-WAN device based on the BGP SD-WAN address family protocol.
[0163] In one possible implementation, the negotiation module is used to carry an ORF capability negotiation TLV in a BGP-LSSPF address family protocol message interacting with the first SD-WAN device, wherein the type field of the ORF capability negotiation TLV indicates that the TLV is used for BGP-LS SPF ORF capability negotiation.
[0164] In one possible implementation, the receiving module 901 is used to receive a first BGP ROUTE-REFRESH message sent by a first SD-WAN device, the first BGP ROUTE-REFRESH message including an outbound route filtering type ORF Type field and a first ORF entry encoding field, the ORF Type field is used to indicate that the ORF type is BGP-LS SPF ORF, and the first ORF entry encoding field is used to carry the first ORF request information.
[0165] In a possible implementation manner, the first routing information matching the first ORF request information is a BGP-LSSPF route.
[0166] In a possible implementation manner, the first ORF request information includes a VPN ID.
[0167] In one possible implementation, the receiving module 901 is also used to receive a second ORF request information sent by the first SD-WAN device; the acquiring module 902 is also used to acquire second routing information matching the second ORF request information; and the sending module 903 is also used to send the second routing information to the first SD-WAN device.
[0168] In one possible implementation, the receiving module 901 is also used to receive the third ORF request information sent by the second SD-WAN device; the obtaining module 902 is also used to obtain the third routing information matching the third ORF request information; and the sending module 903 is also used to send the third routing information to the second SD-WAN device.
[0169] like Fig.10 As shown, the device for outbound route filtering capability negotiation provided in the embodiment of the present application includes the following modules.
[0170] The negotiation module 1001 is used for the controller to perform ORF capability negotiation with the first SD-WAN device, and the ORF capability negotiation is used to negotiate the ORF capability between the controller and the first SD-WAN device.
[0171] In one possible implementation, ORF capability negotiation is used to negotiate TNP-ORF capabilities between the controller and the first SD-WAN device.
[0172] In one possible implementation, the negotiation module 1001 is used for the controller to perform TNP-ORF capability negotiation with the first SD-WAN device based on the BGP SD-WAN address family protocol.
[0173] In one possible implementation, the negotiation module 1001 is used for the controller to carry an ORF capability negotiation type length value TLV in a BGP SD-WAN address family protocol message interacting with the first SD-WAN device, wherein the type field of the ORF capability negotiation TLV indicates that the TLV is used for TNP-ORF capability negotiation.
[0174] In one possible implementation, ORF capability negotiation is used to negotiate BGP-LS SPF ORF capabilities between the controller and the first SD-WAN device.
[0175] In one possible implementation, the negotiation module 1001 is used for the controller to perform BGP-LS SPF ORF capability negotiation with the first SD-WAN device based on the BGP SD-WAN address family protocol.
[0176] In one possible implementation, the negotiation module 1001 is used for the controller to carry the ORF capability negotiation TLV in the BGP SD-WAN address family protocol message interacting with the first SD-WAN device, wherein the type field of the ORF capability negotiation TLV indicates that the TLV is used for BGP-LS SPF ORF capability negotiation.
[0177] like Fig.11 As shown, the device for obtaining a route provided in an embodiment of the present application includes the following modules.
[0178] The sending module 1101 is used to send first ORF request information to the controller; the receiving module 1102 is used to receive first routing information sent by the controller and matching the first ORF request information.
[0179] In one possible implementation, the apparatus further includes a negotiation module, which is used to perform ORF capability negotiation with the controller device, and the ORF capability negotiation is used to negotiate the ORF capability between the controller and the first SD-WAN device.
[0180] In one possible implementation, ORF capability negotiation is used to negotiate TNP-ORF capabilities between the controller and the first SD-WAN device.
[0181] In one possible implementation, the negotiation module is used to negotiate TNP-ORF capabilities with the controller based on the BGP SD-WAN address family protocol.
[0182] In one possible implementation, the negotiation module is used to carry an ORF capability negotiation TLV in a BGP SD-WAN address family protocol message interacting with the controller, wherein the type field of the ORF capability negotiation TLV indicates that the TLV is used for TNP-ORF capability negotiation.
[0183] In a possible implementation, the first routing information matching the first ORF request information is TNP routed.
[0184] In one possible implementation, the first ORF request information includes the SD-WAN routing type.
[0185] In one possible implementation, ORF capability negotiation is used to negotiate TNP-ORF capabilities between the controller and the first SD-WAN device.
[0186] In a possible implementation, the sending module 1101 is used to send a first BGP ROUTE-REFRESH message to the controller, the first BGP ROUTE-REFRESH message includes an ORF Type field and a first ORF entry encoding field, the ORF Type field is used to indicate that the type of ORF is TNP-ORF, and the first ORF entry encoding field is used to carry the first ORF request information.
[0187] In one possible implementation, the first ORF request information includes a routing type field, and the routing type field indicates SD-WAN TNP routing.
[0188] In a possible implementation manner, the first ORF request information further includes TNP information, and the TNP information includes a link ID and a link type.
[0189] In one possible implementation, the negotiation module is used to perform BGP-LS SPF ORF capability negotiation with the controller based on the BGP SD-WAN address family protocol.
[0190] In a possible implementation, the negotiation module is used to carry an ORF capability negotiation TLV in a BGP-LS SPF address family protocol message interacting with the controller, wherein the type field of the ORF capability negotiation TLV indicates that the TLV is used for BGP-LS SPF ORF capability negotiation.
[0191] In a possible implementation, the sending module 1101 is used to send a first BGP ROUTE-REFRESH message to the controller, the first BGP ROUTE-REFRESH message includes an ORF Type field and a first ORF entry encoding field, the ORF Type field is used to indicate that the type of ORF is BGP-LS SPF ORF, and the first ORF entry encoding field is used to carry the first ORF request information.
[0192] In a possible implementation manner, the first routing information matching the first ORF request information is a BGP-LSSPF route.
[0193] In a possible implementation manner, the first ORF request information includes a virtual private network identifier VPN ID.
[0194] In a possible implementation, the sending module 1101 is further used to send second ORF request information to the controller; the receiving module 1102 is further used to receive second routing information sent by the controller and matching the second ORF request information.
[0195] It should be understood that the above Fig. 9 , Fig.10 and Fig.11 The device provided has the following beneficial effects when achieving its function: Figure 3 The beneficial effects of the method in are the same and will not be described here. Fig. 9 , Fig.10 and Fig.11 When the device provided realizes its functions, only the division of the above-mentioned functional modules is used as an example for illustration. In practical applications, the above-mentioned 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 device and method embodiments provided in the above embodiments belong to the same concept, and their specific implementation process is detailed in the method embodiment, which will not be repeated here.
[0196] See also Fig.12 , Fig.12A schematic structural diagram of an exemplary sending route, outbound route filtering capability negotiation and acquisition routing device 1200 of the present application is shown, and the sending route, outbound route filtering capability negotiation and acquisition routing device 1200 includes at least one processor 1201, a memory 1203 and at least one network interface 1204.
[0197] Processor 1201 is, for example, a general-purpose central processing unit (CPU), a digital signal processor (DSP), a network processor (NP), a GPU, a neural-network processing unit (NPU), a data processing unit (DPU), a microprocessor or one or more integrated circuits or application-specific integrated circuits (ASICs) for implementing the solution of the present application, a programmable logic device (PLD), other general-purpose processors or other programmable logic devices, discrete gates, transistor logic devices, discrete hardware components or any combination thereof. PLD is, for example, a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL) or any combination thereof. A general-purpose processor may be a microprocessor or any conventional processor, etc. It is worth noting that the processor may be a processor supporting an advanced RISC machines (ARM) architecture. It may implement or execute various logic blocks, modules and circuits described in conjunction with the disclosure of the present application. The processor may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and so on.
[0198] Optionally, the sending route, outbound route filtering capability negotiation and acquisition route device 1200 also includes a bus 1202. The bus 1202 is used to transmit information between the components of the sending route, outbound route filtering capability negotiation and acquisition route device 1200. The bus 1202 can be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus. The bus 1202 can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Fig.12 The fact that only one line is used in the diagram does not mean that there is only one bus or only one type of bus.
[0199] The memory 1203 is, for example, a volatile memory or a nonvolatile memory, or may include both volatile and nonvolatile memories. Among them, the nonvolatile memory may be a read-only memory (ROM), a programmable ROM (PROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), which is used as an external cache.
[0200] By way of example but not limitation, many forms of ROM and RAM are available. For example, ROM is a compact disc read-only memory (CD-ROM). RAM includes, but is not limited to, static RAM (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM) and direct rambus RAM (DR RAM).
[0201] The memory 1203 may also be other types of storage devices that can store static information and instructions. Or it may be other types of dynamic storage devices that can store information and instructions. Or it may be other optical disk storage, optical disk storage (including compressed optical disk, laser disk, optical disk, digital versatile disk, blue-ray disk, etc.), magnetic disk storage medium 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 the computer, but is not limited to this. The memory 1203, for example, exists independently and is connected to the processor 1201 through the bus 1202. The memory 1203 may also be integrated with the processor 1201.
[0202] The network interface 1204 uses any transceiver-like device to communicate with other devices or communication networks, and the communication network can be Ethernet, radio access network (RAN) or wireless local area network (WLAN), etc. The network interface 1204 may include a wired network interface and may also include a wireless network interface. Specifically, the network interface 1204 may be an Ethernet interface, such as a Fast Ethernet (FE) interface, a Gigabit Ethernet (GE) interface, an Asynchronous Transfer Mode (ATM) interface, a WLAN interface, a cellular network interface or a combination thereof. The Ethernet interface may be an optical interface, an electrical interface or a combination thereof. In some embodiments of the present application, the network interface 1204 may be used to send routes, negotiate outbound route filtering capabilities, and obtain routing equipment 1200 to communicate with other devices.
[0203] In a specific implementation, as some embodiments, the processor 1201 may include one or more CPUs, such as Fig.12 0 and CPU1 shown in FIG. Each of these processors may be a single-core processor or a multi-core processor. A processor herein may refer to one or more devices, circuits, and / or processing cores for processing data (e.g., computer program instructions).
[0204] In a specific implementation, as some implementation methods, the sending route, outbound route filtering capability negotiation and route acquisition device 1200 may include multiple processors, such as Fig.12 1 and 1205. Each of these processors may be a single-core processor or a multi-core processor. A processor herein may refer to one or more devices, circuits, and / or processing cores for processing data (such as computer program instructions).
[0205] In some implementations, the memory 1203 is used to store program instructions 1210 for executing the solution of the present application, and the processor 1201 can execute the program instructions 1210 stored in the memory 1203. That is, the sending route, outbound route filtering capability negotiation and acquisition routing device 1200 can implement the method provided by the method embodiment through the processor 1201 and the program instructions 1210 in the memory 1203, that is, Figure 3 and Figure 8 The method shown. The program instruction 1210 may include one or more software modules. Optionally, the processor 1201 itself may also store program instructions for executing the solution of the present application.
[0206] In the specific implementation process, the processor 1201 in the sending route, outbound route filtering capability negotiation and acquisition routing device 1200 reads the instructions in the memory 1203, so that Fig.12 The illustrated sending routing, outbound routing filtering capability negotiation and acquisition routing device 1200 can execute all or part of the steps in the method embodiment.
[0207] The sending route, outbound route filtering capability negotiation and route acquisition device 1200 may also correspond to the device shown in the above figure sending route, outbound route filtering capability negotiation and route acquisition, Figure 8 , Fig. 9 and Fig.10 Each functional module in the apparatus shown is implemented using software of the sending route, outbound route filtering capability negotiation and acquisition routing device 1200. In other words, Figure 8 , Fig. 9 and Fig.10 The functional modules included in the apparatus shown are generated after the processor 1201 of the routing device 1200 reads the program instructions 1210 stored in the memory 1203 for sending routes, negotiating outbound route filtering capabilities and obtaining routing information.
[0208] in, Figure 3 and Figure 8 Each step of the method shown is completed by sending routes, negotiating outbound route filtering capabilities, and obtaining hardware integrated logic circuits or software instructions in the processor of the routing device 1200. The steps of the method embodiment disclosed in the present application can be directly embodied as being executed by a hardware processor, or can be executed by a combination of hardware and software modules in the processor. The software module can be located in a mature storage medium in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, or an electrically erasable programmable memory, a register, etc. The storage medium is located in the memory, and the processor reads the information in the memory, and completes the steps of the above method embodiment in combination with its hardware. To avoid repetition, it is not described in detail here.
[0209] See also Fig.13 , Fig.13 The schematic diagram of the structure of an exemplary sending route, outbound route filtering capability negotiation and route acquisition device 1300 of the present application is shown. The sending route, outbound route filtering capability negotiation and route acquisition device 1300 includes: a main control board 1310 and an interface board 1330 . Fig.13 The device 1300 for sending routes, negotiating outbound route filtering capabilities and obtaining routes is used to perform the above Figure 3 and Figure 8 The operations involved in the method of sending routes, negotiating outbound route filtering capabilities and obtaining routes are shown. The device 1300 for sending routes, negotiating outbound route filtering capabilities and obtaining routes is, for example, a switch, a router, a controller, etc. The device 1300 for sending routes, negotiating outbound route filtering capabilities and obtaining routes can be an example of the device 1200 for sending routes, negotiating outbound route filtering capabilities and obtaining routes.
[0210] The main control board 1310 is also called a main processing unit (MPU) or a route processor card. The main control board 1310 is used to control and manage various components in the device 1300 for sending routes, negotiating outbound route filtering capabilities, and obtaining routes, including route calculation, device management, device maintenance, and protocol processing functions. The main control board 1310 includes: a central processor 1311 and a memory 1312.
[0211] The interface board 1330 is also called a line processing unit (LPU), a line card or a service board. The interface board 1330 is used to provide various service interfaces and implement data packet forwarding. Service interfaces include but are not limited to Ethernet interfaces, POS (Packet over SONET / SDH) interfaces, etc., and Ethernet interfaces are, for example, flexible Ethernet clients (FlexE Clients). The interface board 1330 includes: a central processing unit 1331, a network processor 1332, a forwarding table entry memory 1334 and a physical interface card (PIC) 1333.
[0212] The central processor 1331 on the interface board 1330 is used to control and manage the interface board 1330 and communicate with the central processor 1311 on the main control board 1310 .
[0213] The network processor 1332 is used to implement the forwarding processing of the message. The network processor 1332 can be in the form of a forwarding chip. Specifically, the network processor 1332 is used to forward the received message based on the forwarding table stored in the forwarding table entry memory 1334. If the destination address of the message is the address of the device 1300 for sending routes, negotiating the filtering capability of outbound routes, and obtaining routes, the message is sent to the CPU (such as the central processor 1311) for processing; if the destination address of the message is not the address of the device 1300 for sending routes, negotiating the filtering capability of outbound routes, and obtaining routes, the next hop and the outbound interface corresponding to the destination address are found in the forwarding table according to the destination address, and the message is forwarded to the outbound interface corresponding to the destination address. Among them, the processing of the uplink message includes: processing of the message input interface, forwarding table search; processing of the downlink message: forwarding table search, etc.
[0214] The physical interface card 1333 is used to implement the connection function of the physical layer, and the original traffic enters the interface board 1330 from it, and the processed message is sent from the physical interface card 1333. The physical interface card 1333 is also called a daughter card, which can be installed on the interface board 1330, and is responsible for converting the optical signal into a message and forwarding the message to the network processor 1332 for processing after checking the legitimacy of the message. In some embodiments, the central processor can also perform the functions of the network processor 1332, such as implementing software forwarding based on a general-purpose CPU, so that the network processor 1332 is not required in the physical interface card 1333.
[0215] Optionally, the device 1300 for sending routes, negotiating outbound route filtering capabilities and obtaining routes includes multiple interface boards. For example, the device 1300 for sending routes, negotiating outbound route filtering capabilities and obtaining routes also includes an interface board 1340, and the interface board 1340 includes: a central processing unit 1341, a network processor 1342, a forwarding table entry memory 1344 and a physical interface card 1343.
[0216] Optionally, the device 1300 for sending routes, negotiating outbound route filtering capabilities, and obtaining routes further includes a switching fabric board 1320. The switching fabric board 1320 may also be referred to as a switch fabric unit (SFU). In the case where the device for sending routes, negotiating outbound route filtering capabilities, and obtaining routes has multiple interface boards 1330, the switching fabric board 1320 is used to complete data exchange between the interface boards. For example, the interface board 1330 and the interface board 1340 may communicate through the switching fabric board 1320.
[0217] The main control board 1310 is coupled to the interface board 1330. For example, the main control board 1310, the interface board 1330, the interface board 1340, and the switching network board 1320 are connected to the system backplane through a system bus to achieve intercommunication. In a possible implementation, an inter-process communication (IPC) channel is established between the main control board 1310 and the interface board 1330, and the main control board 1310 and the interface board 1330 communicate through the IPC channel.
[0218] Logically, the device 1300 for sending routes, negotiating outbound route filtering capabilities, and obtaining routes includes a control plane and a forwarding plane. The control plane includes a main control board 1310 and a central processor 1331, and the forwarding plane includes various components for performing forwarding, such as a forwarding table entry memory 1334, a physical interface card 1333, and a network processor 1332. The control plane performs functions such as a router, generating a forwarding table, processing signaling and protocol messages, and configuring and maintaining the status of the device. The control plane sends the generated forwarding table to the forwarding plane. On the forwarding plane, the network processor 1332 forwards the message received by the physical interface card 1333 based on the forwarding table sent by the control plane. The forwarding table sent by the control plane can be stored in the forwarding table entry memory 1334. In some embodiments, the control plane and the forwarding plane can be completely separated and not on the same device.
[0219] It is worth noting that there may be one or more main control boards, and when there are multiple boards, they may include a master main control board and a standby main control board. There may be one or more interface boards. The stronger the data processing capability of the device that sends routes, negotiates the filtering capability of outbound routes, and obtains routes, the more interface boards are provided. There may also be one or more physical interface cards on the interface board. There may be no switching board, or there may be one or more switching boards. When there are multiple switching boards, they can jointly realize load sharing and redundant backup. In a centralized forwarding architecture, the device that sends routes, negotiates the filtering capability of outbound routes, and obtains routes may not need a switching board, and the interface board is responsible for the processing function of the service data of the entire system. In a distributed forwarding architecture, the device that sends routes, negotiates the filtering capability of outbound routes, and obtains routes may have at least one switching board, and the data exchange between multiple interface boards is realized through the switching board, providing large-capacity data exchange and processing capabilities. Therefore, the data access and processing capabilities of the device that sends routes, negotiates the filtering capability of outbound routes, and obtains routes in a distributed architecture are greater than those of the device in a centralized architecture. Optionally, the device for sending routes, negotiating outbound route filtering capabilities, and obtaining routes can also be in the form of only one board, that is, without a switching network board, and the functions of the interface board and the main control board are integrated on the board. In this case, the central processor on the interface board and the central processor on the main control board can be combined into one central processor on the board to perform the functions of the two superimposed. The data exchange and processing capabilities of this type of device are relatively low (for example, low-end switches or communication devices such as routers). The specific architecture to be adopted depends on the specific networking deployment scenario, and no limitation is made here.
[0220] In an exemplary embodiment, a system is provided, the system comprising a controller and a first SD-WAN device, the controller being configured to execute Figure 3 and Figure 8 The method executed by the controller in the first SD-WAN device is used to execute Figure 3 and Figure 8 A method performed by the first SD-WAN device.
[0221] In an exemplary embodiment, a computer program (product) is provided, the computer program (product) comprising: a computer program code, when the computer program code is executed by a computer, the computer executes Figure 3 and Figure 8 The method shown.
[0222] In an exemplary embodiment, a computer-readable storage medium is provided, the computer-readable storage medium storing a program or instruction, when the program or instruction is executed on a computer, the computer executes the above Figure 3 and Figure 8 The method shown.
[0223] In an exemplary embodiment, a chip is provided, including a processor for calling and executing instructions stored in a memory, so that a computer equipped with the chip executes Figure 3 and Figure 8 The method shown.
[0224] In an exemplary embodiment, another chip is provided, including: an input interface, an output interface, a processor and a memory, wherein the input interface, the output interface, the processor and the memory are connected through an internal connection path, and the processor is used to execute the code in the memory. When the code is executed, the computer equipped with the chip executes Figure 3 and Figure 8 The method shown.
[0225] 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 program instructions are loaded and executed on the computer, the process or function according to the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can 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 can be transmitted from a website site, a computer, a server or a data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or a data center that includes one or more available media integration. The available medium can be a magnetic medium, (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid-state hard disk Solid State Disk), etc.
[0226] In this application, the terms "first", "second", etc. are used to distinguish between identical or similar items with substantially the same effects and functions. It should be understood that there is no logical or temporal dependency between "first", "second", and "nth", nor is there a limitation on the quantity and execution order. It should also be understood that although the following description uses the terms first, second, etc. to describe various elements, these elements should not be limited by the terms. These terms are only used to distinguish one element from another element.
[0227] It should also be understood that in the various embodiments of the present application, the size of the serial number of each process does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.
[0228] The term "at least one" in this application means one or more, and the term "multiple" in this application means two or more, for example, multiple second devices means two or more second devices. The terms "system" and "network" are often used interchangeably herein.
[0229] It should be understood that the terms used in the description of the various examples herein are only for describing specific examples and are not intended to be limiting. As used in the description of the various examples and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.
[0230] It should also be understood that the term "and / or" used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. The term "and / or" is a description of the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this application generally indicates that the associated objects before and after are in an "or" relationship.
[0231] It should also be understood that the terms "if" and "if" may be interpreted to mean "when" or "upon" or "in response to determining" or "in response to detecting." Similarly, the phrases "if it is determined that ..." or "if [a stated condition or event] is detected" may be interpreted to mean "upon determining that ..." or "in response to determining that ..." or "upon detecting [a stated condition or event]" or "in response to detecting [a stated condition or event]," depending on the context.
[0232] The above description is only an embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent substitutions, improvements, etc. made within the principles of the present application shall be included in the protection scope of the present application.
Claims
1. A method for sending a route, characterized in that: The method is applied to a controller, and the method comprises: Receiving a first outbound route filtering ORF request message sent by a first software defined wide area network SD-WAN device; Acquire first routing information matching the first ORF request information; The first routing information is sent to the first SD-WAN device.
2. The method according to claim 1, characterized in that Before receiving the first outbound route filtering ORF request information sent by the first software defined wide area network SD-WAN device, the method further includes: Perform ORF capability negotiation with the first SD-WAN device, wherein the ORF capability negotiation is used to negotiate ORF capability between the controller and the first SD-WAN device.
3. The method according to claim 2, characterized in that The ORF capability negotiation is used to negotiate the transport network port outbound routing filtering TNP-ORF capability between the controller and the first SD-WAN device.
4. The method according to claim 2 or 3, characterized in that: The performing ORF capability negotiation with the first SD-WAN device includes: Based on the Border Gateway Protocol BGPSD-WAN address family protocol, TNP-ORF capability negotiation is performed with the first SD-WAN device.
5. The method according to claim 4, characterized in that The performing TNP-ORF capability negotiation with the first SD-WAN device based on the Border Gateway Protocol BGPSD-WAN address family protocol includes: An ORF capability negotiation type length value TLV is carried in the BGPSD-WAN address family protocol message interacting with the first SD-WAN device, wherein the type field of the ORF capability negotiation TLV indicates that the TLV is used for the TNP-ORF capability negotiation.
6. The method according to any one of claims 1 to 5, characterized in that: The first routing information matched with the first ORF request information is a transmission network port TNP route.
7. The method according to any one of claims 1 to 6, characterized in that: The first ORF request information includes the SD-WAN routing type.
8. The method according to claim 7, characterized in that The first ORF request information also includes TNP information, and the TNP information includes a link identification ID and a link type.
9. The method according to any one of claims 1 to 8, characterized in that: The receiving of first outbound route filtering ORF request information sent by a first software defined wide area network SD-WAN device includes: Receive a first Border Gateway Protocol route refresh BGP ROUTE-REFRESH message sent by the first SD-WAN device, the first BGP ROUTE-REFRESH message including an outbound route filter type ORF Type field and a first outbound route filter table entry encoding ORF entry encoding field, the ORF Type field is used to indicate that the ORF type is TNP-ORF, and the first ORF entry encoding field is used to carry the first ORF request information.
10. The method according to claim 9, characterized in that The first ORF request information includes a routing type field, and the routing type field indicates SD-WAN TNP routing.
11. The method according to claim 2, characterized in that The ORF capability negotiation is used to negotiate Border Gateway Protocol Link State Shortest Path First Outbound Routing Filtering BGP-LSSPF ORF capability between the controller and the first SD-WAN device.
12. The method according to claim 2 or 11, characterized in that: The performing ORF capability negotiation with the first SD-WAN device includes: Based on the Border Gateway Protocol BGPSD-WAN address family protocol, BGP-LS SPF ORF capability negotiation is performed with the first SD-WAN device.
13. The method according to claim 12, characterized in that The performing BGP-LS SPF ORF capability negotiation with the first SD-WAN device based on the Border Gateway Protocol BGPSD-WAN address family protocol includes: An ORF capability negotiation TLV is carried in a BGP-LS SPF address family protocol message interacting with the first SD-WAN device, wherein a type field of the ORF capability negotiation TLV indicates that the TLV is used for the BGP-LS SPF ORF capability negotiation.
14. The method according to any one of claims 1-2, 11-13, characterized in that: The receiving of first outbound route filtering ORF request information sent by a first software defined wide area network SD-WAN device includes: Receive a first Border Gateway Protocol route refresh BGP ROUTE-REFRESH message sent by the first SD-WAN device, the first BGP ROUTE-REFRESH message including an outbound route filter type ORF Type field and a first outbound route filter table entry encoding ORF entry encoding field, the ORF Type field is used to indicate that the ORF type is BGP-LS SPF ORF, and the first ORF entry encoding field is used to carry the first ORF request information.
15. The method according to any one of claims 1-2, 11-14, characterized in that: The first routing information matching the first ORF request information is a Border Gateway Protocol Link State Shortest Path First (BGP-LS SPF) route.
16. The method according to any one of claims 1-2, 11-15, characterized in that: The first ORF request information includes a virtual private network identifier VPN ID.
17. The method according to any one of claims 1 to 16, characterized in that: The method further comprises: Receiving a second ORF request message sent by the first SD-WAN device; Acquire second routing information matching the second ORF request information; Send the second routing information to the first SD-WAN device.
18. The method according to any one of claims 1 to 17, characterized in that: The method further comprises: Receiving a third ORF request message sent by the second SD-WAN device; Acquire third routing information matching the third ORF request information; Send the third routing information to the second SD-WAN device.
19. A method for negotiating outbound route filtering capabilities, characterized in that: The method comprises: The controller performs outbound routing filtering (ORF) capability negotiation with the first software-defined wide area network (SD-WAN) device, and the ORF capability negotiation is used to negotiate the ORF capability between the controller and the first SD-WAN device.
20. The method according to claim 19, characterized in that The ORF capability negotiation is used to negotiate the transport network port outbound routing filtering TNP-ORF capability between the controller and the first SD-WAN device.
21. The method according to claim 19 or 20, characterized in that The controller negotiates the outbound route filtering (ORF) capability with the first software defined wide area network (SD-WAN) device, including: The controller performs TNP-ORF capability negotiation with the first SD-WAN device based on the Border Gateway Protocol BGPSD-WAN address family protocol.
22. The method according to claim 21, characterized in that The controller performs TNP-ORF capability negotiation with the first SD-WAN device based on the Border Gateway Protocol BGP SD-WAN address family protocol, including: The controller carries an ORF capability negotiation type length value TLV in a BGPSD-WAN address family protocol message interacting with the first SD-WAN device, wherein the type field of the ORF capability negotiation TLV indicates that the TLV is used for the TNP-ORF capability negotiation.
23. The method according to claim 19, characterized in that The ORF capability negotiation is used to negotiate Border Gateway Protocol Link State Shortest Path First BGP-LS SPF ORF capabilities between the controller and the first SD-WAN device.
24. The method according to claim 19 or 23, characterized in that The controller negotiates the outbound route filtering (ORF) capability with the first software defined wide area network (SD-WAN) device, including: The controller performs BGP-LS SPF ORF capability negotiation with the first SD-WAN device based on the Border Gateway Protocol BGPSD-WAN address family protocol.
25. The method according to claim 24, characterized in that The controller performs BGP-LS SPF ORF capability negotiation with the first SD-WAN device based on the Border Gateway Protocol BGP SD-WAN address family protocol, including: The controller carries an ORF capability negotiation type length value TLV in a BGPSD-WAN address family protocol message interacting with the first SD-WAN device, wherein the type field of the ORF capability negotiation TLV indicates that the TLV is used for the BGP-LS SPF ORF capability negotiation.
26. A method for obtaining a route, characterized in that: The method is applied to a first software-defined wide area network SD-WAN device, and the method includes: Sending a first outbound route filter ORF request message to the controller; Receive first routing information sent by the controller and matching the first ORF request information.
27. The method according to claim 26, characterized in that Before sending the first outbound route filtering ORF request information to the controller, the method further includes: Perform ORF capability negotiation with the controller device, wherein the ORF capability negotiation is used to negotiate ORF capability between the controller and the first SD-WAN device.
28. The method according to claim 27, characterized in that The ORF capability negotiation is used to negotiate the transport network port outbound routing filtering TNP-ORF capability between the controller and the first SD-WAN device.
29. The method according to claim 27 or 28, characterized in that The performing ORF capability negotiation with the controller device includes: The TNP-ORF capability negotiation is performed with the controller based on the Border Gateway Protocol BGPSD-WAN address family protocol.
30. The method according to claim 29, characterized in that The performing TNP-ORF capability negotiation with the controller based on the border gateway protocol BGPSD-WAN address family protocol includes: The ORF capability negotiation type length value TLV is carried in the BGPSD-WAN address family protocol message interacting with the controller, wherein the type field of the ORF capability negotiation TLV indicates that the TLV is used for the TNP-ORF capability negotiation.
31. The method according to any one of claims 26 to 30, characterized in that: The first routing information matched with the first ORF request information is a transmission network port TNP route.
32. The method according to any one of claims 26 to 31, characterized in that: The first ORF request information includes the SD-WAN routing type.
33. The method according to claim 32, characterized in that The first ORF request information also includes TNP information, and the TNP information includes a link identification ID and a link type.
34. The method according to any one of claims 26 to 33, characterized in that: The sending of the first outbound route filtering ORF request information to the controller includes: A first Border Gateway Protocol route refresh BGP ROUTE-REFRESH message is sent to the controller, wherein the first BGPROUTE-REFRESH message includes an outbound route filter type ORF Type field and a first outbound route filter table entry encoding ORF entry encoding field, wherein the ORF Type field is used to indicate that the type of ORF is TNP-ORF, and the first ORFentry encoding field is used to carry the first ORF request information.
35. The method according to claim 34, characterized in that The first ORF request information includes a routing type field, and the routing type field indicates SD-WAN TNP routing.
36. The method according to claim 27, characterized in that The ORF capability negotiation is used to negotiate Border Gateway Protocol Link State Shortest Path First Outbound Routing Filtering BGP-LSSPF ORF capability between the controller and the first SD-WAN device.
37. The method according to claim 27 or 36, characterized in that The performing ORF capability negotiation with the controller device includes: The BGP-LS SPF ORF capability negotiation is performed with the controller based on the Border Gateway Protocol BGPSD-WAN address family protocol.
38. The method according to claim 37, characterized in that The BGP-LS SPF ORF capability negotiation with the controller based on the Border Gateway Protocol BGPSD-WAN address family protocol includes: An ORF capability negotiation type length value TLV is carried in a BGP-LS SPF address family protocol message interacting with the controller, wherein the type field of the ORF capability negotiation TLV indicates that the TLV is used for the BGP-LS SPF ORF capability negotiation.
39. The method according to any one of claims 26-27 or 36-38, characterized in that: The sending of the first outbound route filtering ORF request information to the controller includes: A first Border Gateway Protocol route refresh BGP ROUTE-REFRESH message is sent to the controller, wherein the first BGPROUTE-REFRESH message includes an outbound route filter type ORF Type field and a first outbound route filter table entry encoding ORF entry encoding field, wherein the ORF Type field is used to indicate that the type of ORF is BGP-LS SPF ORF, and the first ORF entry encoding field is used to carry the first ORF request information.
40. The method according to any one of claims 26-27, 36-39, characterized in that: The first routing information matching the first ORF request information is a Border Gateway Protocol Link State Shortest Path First (BGP-LS SPF) route.
41. The method according to any one of claims 26-27, 36-40, characterized in that: The first ORF request information includes a virtual private network identifier VPN ID.
42. The method according to any one of claims 26 to 41, characterized in that: The method further comprises: Sending a second ORF request message to the controller; Second routing information sent by the controller and matching the second ORF request information is received.
43. A communication device, characterized in that: The device comprises: a transceiver module, used to perform the receiving and / or sending related operations performed by the communication device in any of the methods described in claims 1-18, or used to perform the receiving and / or sending related operations performed by the communication device in any of the methods described in claims 19-25, or used to perform the receiving and / or sending related operations performed by the communication device in any of the methods described in claims 26-42; A processing module, used to perform other operations other than the reception and / or transmission related operations performed by the communication device in any of the methods described in claims 1-18, or used to perform other operations other than the reception and / or transmission related operations performed by the communication device in any of the methods described in claims 19-25, or used to perform other operations other than the reception and / or transmission related operations performed by the communication device in any of the methods described in claims 26-42.
44. A communication device, characterized in that: The communication device includes a processor, which is coupled to a memory; the memory stores at least one instruction, which is loaded and executed by the processor so that the device implements the method for sending a route described in any one of claims 1-18, or the method for negotiating outbound route filtering capabilities described in any one of claims 19-25, or the method for obtaining a route described in any one of claims 26-42.
45. A communication system, characterized in that: The communication system includes a first software-defined wide area network SD-WAN device and a controller, the controller is used to execute the method performed by the controller in any one of the methods described in claims 1-42, and the first SD-WAN device is used to execute the method performed by the first SD-WAN device in any one of the methods described in claims 1-42.
46. A computer-readable storage medium, characterized in that The computer-readable storage medium stores at least one instruction, which is loaded and executed by the processor to implement the method for sending a route described in any one of claims 1-18 or the method for negotiating an outbound route filtering capability described in any one of claims 19-25 or the method for obtaining a route described in any one of claims 26-42.
47. A computer program product, characterized in that The computer program product includes a computer program or instructions, which are executed by a processor to enable a computer to implement the method for sending a route described in any one of claims 1-18 or the method for negotiating an outbound route filtering capability described in any one of claims 19-25 or the method for obtaining a route described in any one of claims 26-42.
