WO2023169364A1

WO2023169364A1 - Routing generation method and apparatus, and data message forwarding method and apparatus

Info

Publication number: WO2023169364A1
Application number: PCT/CN2023/079852
Authority: WO
Inventors: 庞东磊; 王海波
Original assignee: 华为技术有限公司
Priority date: 2022-03-11
Filing date: 2023-03-06
Publication date: 2023-09-14

Abstract

The present application belongs to the technical field of communications. Provided are a routing generation method and apparatus, and a data message forwarding method and apparatus. In the present application, a routing calculation object is address information corresponding to a first protocol stack, and a routing calculation result comprises address information corresponding to a second protocol stack, that is, it is allowed that the routing calculation object and the routing calculation result have different address family types. In this way, a method for supporting dual-stack hybrid routing calculation is implemented. Compared with a single-stack routing calculation mode in the prior art, in the method, by means of configuring one of an IPv4 address and an IPv6 address on an interface corresponding to a link, the requirements of a dual-stack service can be supported, without the need for configuring the addresses of two protocol stacks, thereby saving on IP address resources.

Description

Route generation method, data message forwarding method and device

This application requires the priority of the Chinese patent application with the application number 202210239542.9 and the invention title "A method for BGP SPF to support V6 and V4 dual-stack hybrid routing calculation" submitted on March 11, 2022, and the application is requested in 2022 The priority of the Chinese patent application with the application number 202210459509.7 and the invention title "Route Generation Method, Data Message Forwarding Method and Device" submitted on April 27, 2020, the entire content of which is incorporated into this application by reference.

Technical field

The present application relates to the field of communication technology, and in particular to a route generation method, a data message forwarding method and a device.

Background technique

Currently, various routing protocols generally adopt a single-stack route calculation method. That is, in the route calculated by the network device for an Internet Protocol version 4 (IPv4) prefix, the outbound interface is an interface configured with an IPv4 address on the network device itself, and the next hop is the peer network device. An IPv4 address configured on an interface; in the route calculated by the network device for an Internet protocol version 6 (IPv6) prefix, the outgoing interface is an interface configured with an IPv6 address on the network device itself, and the next hop is The IPv6 address configured on an interface of the peer network device. That is to say, the protocol stacks (or address families) corresponding to the three things of prefix, next hop, and outbound interface are all of the same type, either IPv4 or IPv6. From the perspective of routing tables and forwarding tables on network devices, in the same entry in the routing table or forwarding table, the address family type of the prefix and the address family type of the next hop are consistent.

However, if the above-mentioned single-stack route calculation method is used to implement dual-stack services, both IPv4 addresses and IPv6 addresses need to be configured on the interface corresponding to each link, resulting in the consumption of a large amount of address resources.

Contents of the invention

Embodiments of the present application provide a route generation method, a data packet forwarding method and a device, which help save address resources. The technical solution is as follows.

The first aspect provides a route generation method, which includes:

The first network device obtains the network topology;

The first network device receives a route advertisement message from the second network device, and the route advertisement message is used to publish address information corresponding to the first protocol stack;

The first network device generates a route, the route includes the address information corresponding to the first protocol stack and the address information corresponding to the second protocol stack, and the address information corresponding to the second protocol stack is the network The address information of the endpoint network device of the first link in the topology.

In the above method, the object of route calculation is the address information corresponding to the first protocol stack, and the result of route calculation includes the address information corresponding to the second protocol stack. That is, the object of route calculation and the result of route calculation are allowed to have different Address family type. In this way, a method to support dual-stack hybrid route computation is implemented. Compared with the single-stack route calculation method in the existing technology, the above method configures the address information of one protocol stack on the interface corresponding to the link to support the needs of dual-stack services without the need to configure two protocol stacks. address, thus saving Internet protocol (IP) addresses resource.

In some implementations, the address information of endpoint network devices of all other links except the first link in the network topology is address information corresponding to the second protocol stack.

Through the above method, it is helpful to support single-stack topology for dual-stack hybrid route calculation in the scenario where all links in the network are deployed based on the second protocol stack.

In some embodiments, the network topology further includes a second link, and an endpoint network device of the second link includes address information corresponding to the first protocol stack.

Through the above method, it is helpful to support dual-stack hybrid route calculation in scenarios where there are links corresponding to different protocol stacks between different network devices.

In some embodiments, the network topology includes a dual-stack link, and an endpoint network device of the dual-stack link includes address information corresponding to a first protocol stack and address information corresponding to a second protocol stack.

Through the above method, it helps to support dual-stack hybrid route calculation in the scenario of dual-stack link deployment.

In some implementations, the second network device belongs to the border gateway protocol shortest path first calculation (shortest path first with border gateway protocol, BGP SPF) routing domain and belongs to the interior gateway protocol (interior gateway protocol, IGP) routing domain, and the corresponding The address information in the first protocol stack is the address information of the third network device in the IGP routing domain.

Through the above method, it is helpful to introduce the address information of network devices in the IGP routing domain into the BGP SPF routing domain in the scenario where the BGP SPF routing domain and the IGP routing domain are spliced to form a basic network.

In some implementations, the address information corresponding to the first protocol stack is the address information of the user equipment accessed by the second network device.

In some implementations, the first network device obtains the network topology, including:

The first network device receives a link advertisement message, and the link advertisement message is used to publish address information of an endpoint network device of the first link;

The first network device obtains the network topology based on address information of an endpoint network device of the first link.

In some implementations, the route advertisement message is a BGP SPF message.

In some implementations, the first protocol stack is an IPv4 protocol stack, and the second protocol stack is an IPv6 protocol stack; or,

The first protocol stack is an IPv6 protocol stack, and the second protocol stack is an IPv4 protocol stack.

In the second aspect, a data packet forwarding method is provided. In this method,

The first network device receives a data packet, where the data packet includes address information corresponding to the first protocol stack;

The first network device forwards the data message to the address information corresponding to the second protocol stack based on the address information corresponding to the first protocol stack and the route. The route includes the address information corresponding to the first protocol stack. The address information and the address information corresponding to the second protocol stack.

In the above method, after receiving the data message containing the address information of the first protocol stack, the route containing the address information of the two protocol stacks is used to forward the data message to the address information corresponding to the second protocol stack, thereby supporting dual communication. Stack service requirements, and there is no need to configure the addresses of the two protocol stacks on the interface corresponding to the link, thus saving IP address resources.

In a third aspect, a route generation device is provided, which has the function of implementing the above-mentioned first aspect or any optional method of the first aspect. The route generation device includes at least one unit, and the at least one unit is used to implement the method provided by the above-mentioned first aspect or any optional manner of the first aspect.

In some embodiments, the units in the route generation device are implemented by software, and the units in the route generation device are program modules. In other embodiments, the units in the route generating device are implemented by hardware or firmware. For specific details of the route generation device provided in the third aspect, please refer to the above-mentioned first aspect or any optional method of the first aspect, and will not be described again here.

In a fourth aspect, a data message forwarding device is provided. The data message forwarding device has the function of implementing the above second aspect or any optional method of the second aspect. The data message forwarding device includes at least one unit, and the at least one unit is used to implement the method provided by the above-mentioned second aspect or any optional manner of the second aspect.

In some embodiments, the units in the device for forwarding data packets are implemented by software, and the units in the device for forwarding data packets are program modules. In other embodiments, the units in the device for forwarding data packets are implemented in hardware or firmware. For specific details of the data packet forwarding device provided in the fourth aspect, please refer to the above-mentioned second aspect or any optional method of the second aspect, and will not be described again here.

In a fifth aspect, a network device is provided. The network device includes a processor and a network interface. The processor is configured to execute instructions so that the network device executes the above-mentioned first aspect or any of the optional methods provided by the first aspect. Method, the network interface is used to receive or send messages. For specific details of the network device provided in the fifth aspect, please refer to the above-mentioned first aspect or any optional method of the first aspect, and will not be described again here.

In a sixth aspect, a network device is provided. The network device includes a processor and a network interface. The processor is configured to execute instructions so that the network device executes the above-mentioned second aspect or any of the optional methods provided by the second aspect. Method, the network interface is used to receive or send messages. For specific details of the network equipment provided in the sixth aspect, please refer to the above-mentioned second aspect or any optional method of the second aspect, and will not be described again here.

In a seventh aspect, a computer-readable storage medium is provided. The storage medium stores at least one instruction. When the instruction is run on a processor, it causes the processor to execute the above-mentioned first aspect or any one of the first optional aspects. method provided.

In an eighth aspect, a computer-readable storage medium is provided. The storage medium stores at least one instruction. When the instruction is run on a processor, it causes the processor to execute the above-mentioned second aspect or any one of the second optional aspects. method provided.

In a ninth aspect, a computer program product is provided. The computer program product includes one or more computer program instructions. When the computer program instructions are loaded and run by a computer, they cause the computer to execute the first aspect or the third aspect. On the one hand, any of the options provided by the method.

In a tenth aspect, a computer program product is provided. The computer program product includes one or more computer program instructions. When the computer program instructions are loaded and run by a computer, they cause the computer to execute the above second aspect or the third aspect. Methods provided by any of the two optional methods.

In an eleventh aspect, a chip is provided, including a memory and a processor. The memory is used to store computer instructions. The processor is used to call and run the computer instructions from the memory to execute the above first aspect and any possibility of the first aspect. method in the implementation.

In a twelfth aspect, a chip is provided, including a memory and a processor. The memory is used to store computer instructions. The processor is used to call and run the computer instructions from the memory to execute the above second aspect or any one of the second aspects. Optional methods provided.

In a thirteenth aspect, a network device is provided. The network device includes: a main control board and an interface board, and may further include a switching network board. The network device is configured to perform the method in the first aspect or any possible implementation of the first aspect. Specifically, the network device includes a unit for performing the method in the first aspect or any possible implementation of the first aspect.

In a fourteenth aspect, a network device is provided. The network device includes: a main control board and an interface board. Further, it may also include a switching network board. The network device is configured to perform the method in the second aspect or any possible implementation of the second aspect. Specifically, the network device includes a unit for performing the method in the second aspect or any possible implementation of the second aspect.

Description of the drawings

Figure 1 is a schematic diagram of a network deployment scenario provided by an embodiment of the present application;

Figure 2 is a flow chart of a route generation method provided by an embodiment of the present application;

Figure 3 is a schematic diagram of the format of a BGP SPF prefix NLRI provided by the embodiment of the present application;

Figure 4 is a schematic diagram of the format of the prefix descriptor field in the BGP SPF prefix NLRI provided by the embodiment of the present application;

Figure 5 is a schematic diagram of the format of a BGP SPF link NLRI provided by the embodiment of this application;

Figure 6 is a schematic diagram of the format of a BGP SPF node NLRI provided by the embodiment of the present application;

Figure 7 is a schematic diagram of a spliced deployment scenario of a BGP SPF routing domain and an IGP routing domain provided by the embodiment of this application;

Figure 8 is a schematic diagram of another splicing deployment scenario of BGP SPF routing domain and IGP routing domain provided by the embodiment of this application;

Figure 9 is a schematic diagram of another splicing deployment scenario of BGP SPF routing domain and IGP routing domain provided by the embodiment of this application;

Figure 10 is a schematic diagram of another splicing deployment scenario of BGP SPF routing domain and IGP routing domain provided by the embodiment of this application;

Figure 11 is a schematic diagram of a scenario where the BGP SPF routing domain is deployed as a dual-stack link provided by the embodiment of this application;

Figure 12 is a schematic diagram of an IPv4 topology provided by an embodiment of the present application;

Figure 13 is a schematic diagram of an IPv6 topology provided by an embodiment of the present application;

Figure 14 is a schematic diagram of a hybrid dual-stack topology provided by an embodiment of the present application;

Figure 15 is a schematic diagram of a scenario where the BGP SPF routing domain is spliced and deployed for IPv4 links and IPv6 links according to the embodiment of the present application;

Figure 16 is a schematic structural diagram of a route generation device 600 provided by an embodiment of the present application;

Figure 17 is a schematic structural diagram of a data message forwarding device 700 provided by an embodiment of the present application;

Figure 18 is a schematic structural diagram of a network device 800 provided by an embodiment of the present application;

Figure 19 is a schematic structural diagram of a network device 900 provided by an embodiment of the present application.

Detailed ways

In order to make the purpose, technical solutions and advantages of the present application clearer, the embodiments of the present application will be further described in detail below with reference to the drawings.

The following describes a network deployment scenario provided by the embodiment of this application.

Figure 1 is a schematic diagram of a network deployment scenario provided by an embodiment of the present application. The scenario shown in Figure 1 includes network devices D. Network equipment C, network equipment E, network equipment F and user network edge equipment (customer edge, CE).

Any network device among network device D, network device C, network device E, and network device F includes but is not limited to routers, switches, and the like. Network device D, network device C, network device E and network device F belong to a routing domain. A routing domain is an autonomous system. In a routing domain, a group of routers exchange routing information through the same routing protocol.

The scenario shown in Figure 1 is a scenario based on IPv6 network deployment. Network device D and network device E are connected through an IPv6 link. Network device C and network device F are connected through an IPv6 link. In addition, network device E and network device F are both connected to CE.

As shown in Figure 1, network device D has interface 3, and interface 3 is configured with IPv6 address 10::20. Network device E has interface 4, which is configured with IPv6 address 10::10. An IPv6 link is established between interface 3 and interface 4. That is, for the IPv6 link between network device D and network device E, the endpoint network devices of this IPv6 link include network device D and network device E, and the information of this IPv6 link includes IPv6 address 10 ::20 and IPv6 address 10::10.

Network device C has interface 6, which is configured with IPv6 address 30::20. Network device F has interface 5, which is configured with IPv6 address 30::10. An IPv6 link is established between interface 6 and interface 5. That is, for the IPv6 link between network device C and network device F, the endpoint network devices of this IPv6 link include network device C and network device F, and the information of this IPv6 link includes IPv6 address 30 ::20 and IPv6 address 30::10.

The inventor of this application discovered that the traditional single-stack topology route calculation technology will have many defects when implementing dual-stack services.

The so-called dual stack refers to two sets of protocol stacks, such as IPv4 and IPv6. The so-called dual-stack service, for a network device, means that the network device can forward data packets corresponding to two protocol stacks. In many scenarios, there is a need to implement dual-stack services. Taking the two protocol stacks as IPv4 protocol stack and IPv6 protocol stack as an example, in an exemplary scenario, when an operator upgrades the underlying network from an IPv4 network to an IPv6 network, a transition is generally required. The process, that is, there are both network devices and IPv4 links that support IPv4, and network devices and IPv6 links that support IPv6 in the underlay network. In another exemplary scenario, in the process of an application gradually upgrading from IPv4-based communication to IPv6-based communication, there will generally be a situation where the terminal device on which the application is installed has both an IPv4 address and an IPv6 address for a long period of time. In these two scenarios, involving the coexistence and interoperability of IPv4 networks and IPv6 networks, network devices are required to be able to forward data packets to an IPv6 network device or IPv6 terminal, and also to forward data packets to an IPv4 network device or IPv4 terminal. .

In traditional technology, when implementing the above dual-stack services, all links need to be configured as dual-stack links, thereby forming a dual-stack physical topology, namely IPv4 network topology and IPv6 network topology. For IPv4 prefixes, network devices calculate routes based on IPv4 network topology. For IPv6 prefixes, network devices calculate routes based on IPv6 network topology.

However, this method consumes a large amount of Internet protocol (internet protocol, IP) address resources. Specifically, when configuring each link in the network as a dual-stack link, you need to configure a pair of IPv4 addresses and a pair of IPv6 addresses. For example, configure a link between interface 1 of device A and interface 2 of device B. If the link is configured as a dual-stack link, it is required to configure the IPv4 address and IPv6 address on interface 1, and also configure the IPv4 address and IPv6 address on interface 2. Then, device A establishes a link based on the IPv4 address of interface 1, and device B establishes a link based on the IPv4 address of interface 2; and, device A establishes a link based on the IPv6 address of interface 1, and device B establishes a link based on the IPv6 address of interface 2. As business develops, the scale of the network becomes larger and larger, which undoubtedly requires a large number of IP addresses. In addition, each network device needs to deploy two protocol stacks of IPv4 and IPv6 protocols to support dual-stack services, resulting in complex deployment and maintenance and high processing pressure on network devices.

Based on this, some embodiments of the present application provide a way to support dual-stack hybrid route calculation. The two protocol stacks are the IPv4 protocol stack and the IPv6 protocol stack as an example. For example, optionally, in the route calculated by the network device for an IPv4 prefix, the outgoing interface is one of the network device itself configured with an IPv6 address. interface, the next hop is the IPv6 address configured on an interface of the peer network device; for another example, optionally, in the route calculated by the network device for an IPv6 prefix, the outgoing interface is an IPv4 address configured on the network device itself. Interface, the next hop is the IPv4 address configured for an interface of the peer network device. That is to say, the types of IP protocol stacks corresponding to the three things: prefix, next hop, and outbound interface are inconsistent. From the perspective of routing tables and forwarding tables on network devices, in the same entry in the routing table or forwarding table, the address family type of the prefix and the address family type of the next hop are different. For example, the prefix is an IPv4 prefix and the next hop is an IPv6 address, or the prefix is an IPv6 prefix and the next hop is an IPv4 address.

Calculating routes in this way is still described by taking the two protocol stacks as IPv4 protocol stack and IPv6 protocol stack as an example. In the data plane forwarding stage, when the network device receives the IPv4 data packet, the network device performs the calculation based on the IPv4 data packet. When the destination IPv4 address in this article searches for a route, it can address the IPv6 next hop and forward the IPv4 data packet to the IPv6 next hop through the configured outbound interface of the IPv6 address without using the local IPv4 address of the network device. , and there is basically no need to require network equipment to establish a link with the peer network equipment based on the IPv4 protocol and maintain communication. It can be seen that this method reduces the number of IP addresses that network devices need to configure to support dual-stack services, and saves IP address resources. In addition, the deployment and maintenance workload caused by maintaining two sets of IP protocol stacks is reduced, and the cost of network equipment is reduced.

Figure 2 is a flow chart of a route generation method provided by an embodiment of the present application. The method shown in Figure 2 includes the following S201 to S204.

The method shown in Figure 2 involves interactions between multiple network devices. In order to distinguish different network devices, "first network device" and "second network device" are used to describe multiple different network devices.

The method shown in Figure 2 involves dual protocol stack hybrid routing calculation. In order to distinguish different protocol stacks, "first protocol stack" and "second protocol stack" are used to describe multiple different protocol stacks. For example, the first protocol stack is an IPv4 protocol stack, and the second protocol stack is an IPv6 protocol stack. For another example, the first protocol stack is an IPv6 protocol stack, and the second protocol stack is an IPv4 protocol stack. It should be understood that the type of protocol stack is not limited in this application. In the following description, the first protocol stack is an IPv4 protocol stack and the second protocol stack is an IPv6 protocol stack as an example.

The network deployment scenario on which the method shown in Figure 2 is based is optionally shown in Figure 1 above. For example, looking at FIG. 1 , the first network device in the method shown in FIG. 2 is the network device D in FIG. 1 , and the second network device in the method shown in FIG. 2 is the network device E in FIG. 1 .

S201. The first network device obtains the network topology.

Network topology indicates the network devices and links that exist in a routing domain. In some embodiments, the network topology includes address information for endpoint network devices of at least one link. Optionally, the network topology also includes an identification of an endpoint network device of at least one link. The first network device obtains the network topology to generate a route based on part or all of the information in the network topology.

The following is an example of the above network topology based on different network deployment scenarios, see Scenario 1 to Scenario 4 below.

Scenario 1. Pure IPv6 basic network deployment scenario.

In scenario 1, all links in the network topology are IPv6 links. In other words, the address information of the endpoint network devices of all links in the network topology is IPv6 address.

For example, network device A and network device B are deployed in the network. Interface A of network device A is configured with an IPv6 Address A, interface B of network device B is configured with an IPv6 address B. Network device A establishes a link 1 based on IPv6 address A and network device B based on IPv6 address B. In this example, link 1 is an IPv6 link, and the endpoint network devices of link 1 include network device A and network device B. The address information of the endpoint network device of link 1 includes IPv6 address A and IPv6 address B. In the same way, every link in the network except link 1 is an IPv6 link, which is equivalent to the network being a pure IPv6 network.

Scenario 2: Pure IPv4 basic network deployment scenario.

In scenario 2, the address information of the endpoint network devices of all links in the network topology is IPv4 address. In other words, all links in the network topology are IPv4 links.

For example, network device A and network device B are deployed in the network. Interface A of network device A is configured with an IPv4 address A, and interface B of network device B is configured with an IPv4 address B. Network device A establishes a link 1 based on IPv4 address A and network device B based on IPv4 address B. In this example, link 1 is an IPv4 link, and the endpoint network devices of link 1 include network device A and network device B. The address information of the endpoint network device of link 1 includes IPv4 address A and IPv4 address B. In the same way, every link in the network except link 1 is an IPv4 link, which is equivalent to the network being a pure IPv4 network.

Scenario 3: IPv6 link and IPv4 link splicing deployment scenario.

In scenario three, links between different network devices have different address family types. The address family types of some links between network devices correspond to the first protocol stack, and the address family types of links between some network devices correspond to the first protocol stack. The type corresponds to the second protocol stack.

For example, network device A, network device B, and network device C are deployed in the network. Interface A of network device A is configured with an IPv6 address A, interface B1 of network device B is configured with an IPv6 address B1, and interface B2 of network device B is configured with an IPv4 address B2. Interface C of network device C is configured with an IPv4 address C. Network device A establishes a link 1 based on IPv6 address A and network device B based on IPv6 address B1. Network device B establishes a link 2 based on IPv4 address B2 and network device C based on IPv4 address C. In this example, link 1 is an IPv4 link, and the endpoint network devices of link 1 include network device A and network device B. The address information of the endpoint network device of link 1 includes IPv4 address A and IPv4 address B. In this example, link 1 is an IPv6 link, and the endpoint network devices of link 1 include network device A and network device B. The address information of the endpoint network device of link 1 includes IPv6 address A and IPv6 address B1. Link 2 is an IPv4 link, and the endpoint network devices of link 2 include network device B and network device C. The address information of the endpoint network device of link 2 is included in IPv4 address B2 and IPv4 address C.

Scenario 4: Dual-stack link deployment scenario.

In scenario four, the network topology includes a dual-stack link, and the endpoint network device of the dual-stack link includes address information corresponding to the first protocol stack and address information corresponding to the second protocol stack.

S202. The second network device generates a route advertisement message based on the address information to be released, and the second network device sends the route advertisement message to the first network device.

There are many possible situations for the above address information to be released. From the perspective of the form of address information, optionally, the above address information includes at least one of a prefix or an IP address. From the perspective of address family type, optionally, the above address information is IPv4 address information. For example, the above address information includes at least one of an IPv4 prefix or an IPv4 address. Alternatively, the above address information is IPv6 address information. For example, the above address information includes at least one of an IPv6 prefix or an IPv6 address.

The device to which the above address information belongs includes many situations. The following is an example of three situations.

Case 1: The above address information is the address information of the user equipment.

In an exemplary scenario, the second network device accesses a user equipment, and the user equipment sends the address information of the user equipment to the second network device. The second network device receives the address information of the user equipment, uses the address information of the user equipment as the address information to be released, carries the address information in the route advertisement message, and sends it to the first network device, thereby triggering the first network device to calculate arrival Routing of user equipment to meet the business requirements of forwarding data packets to user equipment. The user equipment is, for example, a CE or a terminal.

Case 2: The above address information is the address information configured on an interface of the second network device, that is, the address information of the second network device itself.

Case 3: The above address information is the address information of the third network device.

For example, the third network device and the second network device belong to the first routing domain, and the second network device and the first network device belong to the second routing domain. The third network device sends the address information of the third network device to the second network device. The second network device receives the address information from the third network device, uses the address information of the third network device as the address information to be released, carries the address information in the route advertisement message, and sends it to the first network device. In this way, the address information of network devices in one routing domain is introduced to another routing domain, meeting the need for mutual introduction of address information between different routing domains. Optionally, the above-mentioned first routing domain is an IGP routing domain, and the second routing domain is a BGP SPF routing domain. Alternatively, the above-mentioned first routing domain is a BGP SPF routing domain, and the second routing domain is an IGP routing domain.

The route advertisement message is used to publish address information corresponding to the first protocol stack. In some embodiments, the route advertisement message includes an identification of the second network device and address information corresponding to the first protocol stack. For example, please refer to Figure 1. The address information to be published is the CE's IPv4 address 10.1.1.2. Network device E (the second network device) generates a route advertisement message based on the IPv4 address 10.1.1.2 and the identification of network device E. Network device E sends a route advertisement message to network device D through the IPv6 link.

From the perspective of protocol type, optionally, route advertisement messages are BGP SPF messages. Alternatively, the route advertisement message is an IGP message. For example, route advertisement messages are open shortest path first (OSPF) messages or intermediate system to intermediate system (IS-IS) protocol messages. The following takes the route advertisement message as a BGP SPF message as an example to illustrate the format and content of the route advertisement message.

Optionally, the route advertisement message includes BGP SPF prefix network layer reachability information (network layer reachability information, NLRI). For example, please refer to Figure 3. The second network device sends the BGP SPF prefix NLRI shown in Figure 3 to the first network device, where the local node descriptor field includes the identity of the second network device, and the prefix descriptor field includes the identifier corresponding to the first network device. The prefix of the protocol stack.

S203. The first network device receives the route advertisement message from the second network device.

Optionally, the second network device sends the route advertisement message to the first network device through the outbound interface configured with the address information of the second protocol stack. The first network device receives the route advertisement message through the outgoing interface configured with the address information of the second protocol stack. For example, the second network device sends a route advertisement message containing the IPv4 prefix to the first network device through the IPv6 interface. The first network device receives the route advertisement message containing the IPv4 prefix through the IPv6 interface. For another example, the second network device sends a route advertisement message containing the IPv6 prefix to the first network device through the IPv4 interface. The first network device receives the route advertisement message containing the IPv6 prefix through the IPv4 interface.

S204. The first network device generates a route.

The route includes address information corresponding to the first protocol stack and address information corresponding to the second protocol stack.

Regarding the address information corresponding to the first protocol stack in the route, the address information corresponding to the first protocol stack in the route is obtained from the route advertisement message. That is to say, the address information corresponding to the first protocol stack in the route is sent by the second network device to the third Address information published by a network device. For example, the route includes a destination prefix, and the destination prefix in the route is a prefix corresponding to the first protocol stack. For another example, the route includes a destination address, and the destination address in the route is an address corresponding to the first protocol stack.

Regarding the address information corresponding to the second protocol stack in the route, the address information corresponding to the second protocol stack in the route is obtained based on the network topology. For example, the route includes a next hop, and the next hop in the route is an IP address corresponding to the second protocol stack. The address information corresponding to the second protocol stack in the route is, for example, the address information of the endpoint network device of the first link in the network topology.

In some embodiments, a route includes a next hop and an outbound interface. For example, a first link is established between the first outbound interface of the first network device and the second outbound interface of the second network device. The first network device generates a route. The next hop in the route is the peer interface address, that is, the IP address configured on the second outgoing interface corresponding to the second protocol stack. The outbound interface in the route is the first outbound interface. Alternatively, the next hop is included in the route but not the outbound interface.

For example, please refer to Figure 1. After network device D (first network device) receives the IPv4 address 10.1.1.2 issued by network device E (second network device), based on the IPv4 address and the peer of link DE in the network topology, interface address (i.e. IPv6 address 10::10), a route is generated. The destination address in this route is IPv4 address 10.1.1.2, and the next hop is the peer interface address of link DE (i.e. IPv6 address 10::10 ), the outgoing interface is the local interface of link DE (that is, interface 3).

Optionally, the first network device generates the route based on the SPF algorithm. For example, the first network device obtains the identity of the second network device from the route advertisement message. The first network device finds the location of the second network device in the network topology based on the identifier of the second network device. The first network device determines a shortest path from the first network device to the second network device from the network topology. The first network device uses the network device next to the first network device on the shortest path as the next hop, and uses the prefix in the route advertisement message as the destination prefix, thereby generating a route.

The above S201 to S204 describe the route generation process of the control plane. Based on the above route generation process, the method shown in Figure 2 can further include the packet forwarding process of the data plane. See S205 to S206 below.

S205. The first network device receives the data message.

The data packet includes address information corresponding to the first protocol stack. For example, the destination address field of the data message includes an IP address corresponding to the first protocol stack.

S206. The first network device forwards the data packet to the address information corresponding to the second protocol stack based on the address information and routing corresponding to the first protocol stack.

For example, the first network device searches the routing table using the address information corresponding to the first protocol stack as an index, and obtains the address information corresponding to the second protocol stack. The first network device uses the address information corresponding to the second protocol stack as the next hop and forwards the data packet to the address information corresponding to the second protocol stack.

In the method provided by this embodiment, the object of route calculation is the address information corresponding to the first protocol stack, and the result of route calculation includes the address information corresponding to the second protocol stack, that is, the object of route calculation and the result of route calculation are allowed There are different address family types. In this way, a method to support dual-stack hybrid route computation is implemented. Compared with the single-stack route calculation method in the prior art, this embodiment configures an IPv4 address or an IPv6 address on the interface corresponding to the link to support the dual-stack service requirements without the need for configuration. The addresses of the two protocol stacks thus save IP address resources.

The following is an example of the process by which the first network device obtains the network topology in the method shown in Figure 2.

In some embodiments, the first network device obtains the network topology based on information of at least one link. The information of a link includes, for example, a pair of IP addresses. The pair of IP addresses includes the address information of the two endpoint network devices of the link. How the first network device obtains link information includes multiple methods. For example, the first network device obtains information about each link directly connected to the device. Alternatively, a neighbor network device of the first network device advertises the link information to the first network device. Or, by The link information is configured on the first network device in a static configuration manner.

Taking the second network device advertising the information of the first link to the first network device as an example, for example, the second network device generates a link advertisement message, and the second network device sends the link advertisement message to the first network device. The first network device receives a link advertisement message, and the first network device obtains the network topology based on address information of an endpoint network device of the first link.

The link advertisement message is used to publish the address information of the endpoint network device of the first link; in some embodiments, the link advertisement message includes the address information of the two endpoint network devices of the first link. From the perspective of protocol type, optionally, the link advertisement message is a BGP SPF message. Alternatively, the link advertisement message is an IGP message. For example, the link advertisement message is an OSPF message or an IS-IS message.

The following takes the link advertisement message as a BGP SPF message as an example to illustrate the format and content of the link advertisement message.

Optionally, the link advertisement message includes the BGP SPF link NLRI. For example, please refer to Figure 5. The second network device sends the BGP SPF link NLRI shown in Figure 5 to the first network device, where the local node descriptor field includes the identity of the second network device, and the link descriptor field includes the second network device. The IP address of the interface on the network device that corresponds to the first link.

Optionally, the first network device further obtains the network topology based on the identity of at least one network device. For example, the second network device generates a node advertisement message, and the second network device sends the node advertisement message to the first network device. The first network device receives the node advertisement message. The node advertisement message includes the identification of the second network device. The first network device obtains the identity of the second network device from the node advertisement message, and obtains the network topology according to the identity of the second network device. Optionally, the node advertisement message includes the BGP SPF node NLRI shown in Figure 6.

Optionally, node information, link information, and prefix information are advertised through three different messages. In other words, the node advertisement message, the link advertisement message and the route advertisement message are three different messages. Alternatively, node information, link information, and prefix information are advertised through the same packet. For example, node information, link information and prefix information are advertised through three different type length values (TLV) in the same message.

Some optional embodiments of this application involve the application of the BGP SPF protocol. To help understanding, the BGP SPF protocol is briefly described below.

(1)BGP SPF protocol

BGP SPF protocol is a new type of routing protocol. The BGP SPF protocol is based on the shortest path first (SPF) algorithm in the interior gateway protocol (IGP) protocol for path calculation, and uses the BGP link-state (BGP-LS) protocol. Defined NLRI and TLV.

(2) The relationship between the BGP SPF protocol and the border gateway protocol (BGP) protocol

The BGP SPF protocol is an extension of the BGP protocol. The BGP SPF protocol corresponds to a new address family in the BGP protocol.

Regarding the commonalities between the two routing protocols, the BGP SPF protocol uses many mechanisms in the BGP protocol, including but not limited to the finite state machine in the BGP protocol, the encoding format of the BGP message, the processing process of the BGP message, BGP attributes, and BGP NLRI. And error handling mechanism, etc. For these mechanisms in the BGP protocol, please refer to the introduction of RFC4271 and RFC7606.

Regarding the differences between the two routing protocols, the BGP protocol is mainly used to support the transfer of routes between autonomous systems (AS). The BGP protocol is usually not responsible for route calculation. The BGP protocol uses routes provided by other routing protocols to determine paths based on policies and various attributes. The BGP protocol is an overlay protocol, and the underlay protocol of the BGP protocol is generally an interior gateway protocol (IGP) protocol. The BGP SPF protocol supports path calculation. The BGP SPF protocol replaces the path decision-making process in the BGP protocol with path calculation based on the SPF algorithm. The BGP SPF protocol can be used as an underlay protocol. The BGP SPF protocol can replace the IGP protocol to a certain extent.

(3) Advantages of BGP SPF protocol compared to IGP protocol

Compared with route calculation based on IGP, the technical effects achieved by route calculation based on the BGP SPF protocol include but are not limited to the following four aspects.

A. No need for domain division

When applying the IGP protocol in a large network, domain division is usually required, that is, an autonomous system is divided into different areas. Areas logically divide routers into different groups, and each group is identified by an area ID. Area boundaries are routers, not links. For example, the OSPF protocol divides autonomous systems into different types of areas such as normal areas, stub areas, and stub areas (not-so-stubby area, NSSA). The IS-IS protocol divides routing domains into backbone networks. and non-backbone networks. The BGP SPF protocol usually does not have the concept of domain classification and does not require domain classification.

B. Aperiodic link status updates

The IGP protocol usually updates the link status within the entire area periodically. The so-called flooding means that a router advertises its link status to neighboring routers, and the neighboring routers then send the link status to other neighboring routers until all routers in the entire area have the same link status. Because the device needs to update the link status periodically, the device overhead is high. In the BGP SPF protocol, link status updates are usually aperiodic, thus reducing device overhead.

C. Incremental route advertisement

The BGP SPF protocol usually uses an incremental method to advertise routes, that is, if the route does not change, there is no need to send a message to advertise the route. If a route is added, the added route is notified to the neighbor. If a route is deleted, the deleted route is notified to the neighbor. By incrementally advertising routes, it is possible to avoid the huge number of route entries being delivered and affecting efficiency caused by full advertising of routes.

D. Flow control based on transmission control protocol (TCP)

IGP is usually based on non-connection-oriented protocols to transmit routing protocol messages, so some additional mechanisms need to be designed to ensure the transmission reliability of routing protocol messages. For example, the OSPF protocol has a master-slave negotiation mechanism to ensure transmission reliability. The routing information protocol (RIP) is designed with a regular retransmission method to ensure transmission reliability. The BGP SPF protocol is usually based on the TCP protocol to transmit routing protocol messages, so the transmission reliability is high, and there is usually no need to design additional mechanisms to ensure transmission reliability.

(4)BGP SPF NLRI

BGP SPF NLRI is a network layer reachability information (NLRI) in the BGP LS protocol, which is used for route calculation. BGP SPF NLRI has an encapsulation format defined by RFC 7752. BGP SPF NLRI is further divided into three types, namely BGP SPF prefix NLRI, BGP SPF link NLRI and BGP SPF node NLRI.

(5)BGP SPF prefix NLRI (BGP SPF prefix-NLRI)

BGP SPF prefix NLRI is used to publish prefix information. Figure 3 is a schematic diagram of the format of a BGP SPF prefix NLRI provided by this embodiment. As shown in Figure 3, the BGP SPF prefix NLRI includes a protocol ID (protocol-ID) field, an identifier (identifier) field, and a local node descriptor ( local node descriptors) field and prefix descriptors (prefix descriptors) field.

The local node descriptor field is used to carry the identification of the network device that publishes the prefix (or the source device of the prefix). For example, the local node descriptor field carries the AS number (autonomous system number) of the network device and the router ID. (router-ID).

Since the BGP SPF prefix NLRI carries the local node descriptor field and the prefix descriptor field, thereby indicating the binding relationship between the prefix and the network device that publishes the prefix, the receiving end of the BGP SPF prefix NLRI can not only obtain the prefix, but also learn about the prefix. Which network device it comes from, thus triggering the receiving end to perform route calculation with this network device as the destination.

The prefix descriptor field is used to carry the IP address prefix, such as IPv4 prefix or IPv6 prefix. Optionally, the prefix descriptor field has a TLV encoding structure. For example, the prefix descriptor field includes the IP reachability information TLV (IP reachability information TLV) described in RFC7752.

Figure 4 is a schematic diagram of the format of a prefix descriptor field provided in this embodiment. The prefix descriptor field shown in Figure 4 is, for example, the prefix descriptor field in the BGP SPF prefix NLRI shown in Figure 3. As shown in Figure 4, the prefix descriptor field specifically includes a type field, a length field, a prefix length field and an IP prefix field. Optionally, the value of the type field in the prefix descriptor field, that is, TLV type is 265. Optionally, the IP prefix field carries a specific IPv4 prefix, and the prefix length field carries the length of the IPv4 prefix. Optionally, the IP prefix field carries a specific IPv6 prefix, and the prefix length field carries the length of the IPv6 prefix.

(6)BGP SPF link NLRI

BGP SPF link NLRI is used to publish link information. Figure 5 is a schematic diagram of the format of a BGP SPF link NLRI provided in this embodiment. As shown in Figure 5, the BGP SPF link NLRI includes a protocol ID (protocol-ID) field, an identifier (identifier) field, and a local node description. descriptors (local node descriptors) field, remote node descriptors (remote node descriptors) and link descriptors (link descriptors) fields.

The local node descriptor field in the BGP SPF link NLRI is used to carry the identification of the local endpoint (local end) network device of the link. The remote node descriptor field is used to carry the identification of the remote end network device of the link.

For example, the local node descriptor field is used to carry the AS number of the local endpoint network device of the link and the router-ID of the local endpoint network device, while the remote node descriptor field carries the AS number of the remote endpoint network device of the link and The router-ID of the remote endpoint network device. Optionally, the link descriptor field includes a pair of IP addresses, namely the interface address of the local endpoint network device of the link and the interface address of the remote endpoint network device of the link.

For example, network device A sends a BGP SPF link NLRI to advertise link AB between network device A and network device B. Link AB is the link between interface A of network device A and interface B of network device B. In the BGP SPF link NLRI, the local node descriptor field includes the identity of network device A, the remote node descriptor field includes the identity of network device B, and the link descriptor field includes the IP address of interface A and the IP address of interface B. .

(7)BGP SPF node NLRI

BGP SPF node NLRI is used to publish node information. Figure 6 is a schematic diagram of the format of a BGP SPF node NLRI provided in this embodiment. As shown in Figure 6, the BGP SPF node NLRI includes a protocol ID (protocol-ID) field, an identifier (identifier) field and a local node descriptor ( local node descriptors) field.

The following is an example of the method shown in Figure 2 based on a specific scenario. The following scenario shows the splicing deployment scenario of BGP SPF routing domain and IGP routing domain.

Figure 7 is a schematic diagram of a scenario where the BGP SPF routing domain and the IGP routing domain are spliced and deployed in this embodiment. In the scenario shown in Figure 7, each link between network devices in the IGP routing domain is an IPv4 link, and each link between network devices in the BGP SPF routing domain is an IPv6 link. IPv4 users and IPv6 users are connected to CE1, and CE2 is also connected. IPv4 users and IPv6 users.

For inter-domain splicing nodes between BGP SPF routing domain and IGP routing domain, such as network device C and network device D, the inter-domain splicing node will IGP routing prefix 10.1.1.1, 10.1.1.2, 20.1.1.1, 20.1.1.2 and network device The access user address prefixes 200.1.1.2, 200::2 and other routing prefixes on network device A and network device B are introduced into the BGP SPF routing domain; after network device C and network device D introduce these prefixes, they route to BGP SPF through the BGP SPF protocol. Released to other network devices in the domain. After receiving it, other network devices search for the corresponding nodes in the IPv6 topology matching the BGP SPF routing domain based on the network devices that advertise these prefixes, and generate IPv4 prefix destination routes or IPv6 prefix destination routes with the IPv6 address as the next hop.

Figure 8 is a schematic diagram of another splicing deployment scenario of BGP SPF routing domain and IGP routing domain provided in this embodiment. In the scenario shown in Figure 8, the IGP routing domain contains IPv4 links and IPv6 links, which is equivalent to the IGP routing domain being deployed based on a mixed protocol stack. The BGP SPF routing domain also includes IPv4 links and IPv6 links, which is equivalent to the BGP SPF routing domain being deployed based on a mixed protocol stack. IPv4 users and IPv6 users are connected to CE1, and IPv4 users and IPv6 users are also connected to CE2. For the inter-domain splicing nodes between the BGP SPF routing domain and the IGP routing domain, such as network device C and network device D, add the IGP routing prefixes 10.1.1.1, 10.1.1.2, 30::10, 30::20 and network device A and The access user address prefixes 200.1.1.2, 200::2 and other routing prefixes on network device B are introduced into the BGP SPF routing domain; after network device C and network device D introduce these prefixes, they are sent to the BGP SPF routing domain through the BGP SPF protocol. Other nodes publish prefixes. After receiving the prefixes, other nodes search for the corresponding nodes in the mixed topology containing IPv6 links and IPv4 links that match the BGP SPF routing domain according to the nodes publishing these prefixes, and generate a generation with the IPv6 address as the next hop. An IPv4 prefix destination route or an IPv6 prefix destination route, or an IPv6 prefix destination route with an IPv6 address as the next hop, or an IPv4 prefix destination route with an IPv4 address as the next hop.

The above-mentioned method shown in Figure 2 is illustrated below with four examples. In the following examples, network device E is an illustration of the second network device in the method shown in Figure 2, and network device D, network device F, or network device C is an illustration of the first network device in the method shown in Figure 2. . BGP SPF prefix-NLRI is an example of the route advertisement message in the method shown in Figure 2.

Example 1: The BGP SPF routing domain is deployed on a pure IPv6 basic network.

Example 1 includes the following steps 1 to 4.

Step 1. Import the IPv4 prefix 100.1.1.2 from the IPv6 edge network device E in the BGP SPF routing domain. Network device E encapsulates this IPv4 prefix 100.1.1.2 to BGP SPF prefix-NLRI. Network device E publishes BGP SPF prefix-NLRI to network devices other than network device E in the BGP SPF routing domain (including network device D, network device F, and network device C). After receiving the BGP SPF prefix-NLRI, each network device (including network device D, network device F, and network device C) in the BGP SPF routing domain performs route calculations to the destination address 100.1.1.2.

For BGP SPF prefix-NLRI, it is encapsulated according to RFC7752, and the format is shown in Figure 3. The TLV format of prefix descriptors in BGP SPF prefix-NLRI is shown in Figure 4.

Step 2. Each network device in the BGP SPF routing domain calculates the IPv4 route with the destination address 100.1.1.2. Each network device in the BGP SPF routing domain generates IPv4 forwarding entries based on the IPv4 route. The next hop in the IPv4 forwarding table is the IPv6 address, and the outbound interface in the IPv4 forwarding table is the interface to the neighbor node. For example, network device C calculates a route to the destination address 100.1.1.2. The next hop in this route is 30::10, and the outgoing interface is interface 6.

Step 3. A network device in the BGP SPF routing domain receives traffic with the destination address 100.1.1.2. The network device queries the IPv4 forwarding table based on the destination address of the traffic and obtains the IPv6 next hop and outgoing interface. After the network device encapsulates the message based on the IPv6 next hop and outgoing interface, it forwards the traffic to the next network device until the traffic reaches the destination address.

Step 4. For the scenario where the IPv6 type BGP SPF routing domain is spliced with the IPv4 type IGP routing domain as shown in Figure 9, introduce the IPv4 address information of the IGP routing domain into the BGP SPF routing domain on network device D or network device C. The IPv4 route to the IGP routing domain to which the destination address belongs can be calculated on each network device in the BGP SPF routing domain, such as network device E or network device F. The calculation process is the same as described in steps one to three.

Through the method of Example 1, the BGP SPF routing domain is a pure IPv6 basic network deployment scenario, so that the BGP SPF routing protocol supports a single-stack topology for IPv4 and IPv6 dual-stack hybrid routing calculations.

Example 2: The BGP SPF routing domain is deployed on a pure IPv4 basic network.

Example 2 includes the following steps 1 to 4.

Step 1: Import the IPv6 prefix 100::2 from the IPv4 edge network device F of the BGP SPF routing domain. The network device F encapsulates this IPv6 prefix 100::2 to the BGP SPF prefix NLRI (BGP SPF prefix-NLRI). Network device F publishes BGP SPF prefix-NLRI to other network devices other than network device F in the BGP SPF routing domain (including network device D, network device E, and network device C). After receiving the BGP SPF prefix-NLRI, each network device (including network device D, network device E, and network device C) in the BGP SPF routing domain performs route calculations to the destination address 100::2.

Step 2: Each network device in the BGP SPF routing domain calculates the IPv6 route for the destination address 100::2. Each network device in the BGP SPF routing domain generates IPv6 forwarding entries based on the IPv6 route. The next hop in the IPv6 forwarding entry is the IPv4 address, and the outbound interface in the IPv6 forwarding entry is the interface to the neighbor node. For example, network device D calculates a route to the destination address 100::2. The next hop in this route is 50.1.1.1, and the outbound interface is interface 3.

Step 3. A network device in the BGP SPF routing domain receives traffic with the destination address 100::2. The network device queries the IPv6 forwarding table based on the destination address of the traffic and obtains the IPv4 next hop and outgoing interface. After the IPv4 next hop and outbound interface encapsulates the packet, it forwards the traffic to the next network device until the traffic reaches the destination address.

Step 4. For the scenario where the IPv4 type BGP SPF routing domain is spliced with the IPv6 type IGP routing domain as shown in Figure 10, introduce the IPv6 address information of the IGP routing domain to the BGP SPF routing domain on network device D or network device C. The IPv6 route to the IGP routing domain to which the destination address belongs can be calculated on each network device in the BGP SPF routing domain, such as network device E or network device F. The calculation process is the same as described in steps one to three.

Through the method provided in Example 2, the BGP SPF routing domain is a pure IPv4 basic network deployment scenario. The BGP SPF routing protocol supports single-stack topology for IPv4 and IPv6 dual-stack hybrid routing calculations.

Example 3: The BGP SPF routing domain is deployed for dual-stack links, that is, a link interface between network devices is configured with a dual-stack address.

As shown in Figure 11, the interface on the same link between network device C and network device F is configured with an IPv4 address and an IPv6 address, that is, a dual-stack address. BGP SPF routing domains are collected to form a topology. Optionally, the network device generates IPv4 topology and IPv6 topology respectively. Alternatively, the network device generates a topology that includes IPv4 links and IPv6 links. This topology may be called a hybrid dual-stack topology.

Exemplarily, the IPv4 topology generated by the network device is shown in Figure 12, the IPv6 topology generated by the network device is shown in Figure 13, and the hybrid dual-stack topology generated by the network device is shown in Figure 14.

When network devices calculate IPv4 routes or IPv6 routes, they match according to the topology results and use the IPv4 next hop or IPv6 next hop. The processing of routing and forwarding behavior is the same as that of Example 1 and Example 2.

Through the method provided in Example 3, the BGP SPF routing domain is a dual-stack link deployment scenario and can support IPv4 or IPv6 prefix route calculation at the same time. The route next hop is matched according to the topology result and uses IPv4 or IPv6 next hop.

Example 4: The BGP SPF routing domain is deployed for splicing IPv4 links and IPv6 links, that is, there are different link address family types between different network devices.

As shown in Figure 15, there are IPv4 links, IPv6 links, and dual-stack links between different network devices in the BGP SPF routing domain; optionally, network devices calculate independently based on IPv4 links or IPv6 links. Topology, or network equipment calculates topology based on a mixture of IPv4 links and IPv6 links. When network devices calculate IPv4 prefix routes or IPv6 prefix routes, they match according to the topology results and use the IPv4 next hop or IPv6 next hop. The processing of routing and forwarding behavior is the same as that of Example 1 and Example 2.

Through the method provided in Example 4, the BGP SPF routing domain is deployed in a splicing deployment scenario of IPv4 links and IPv6 links. It can support IPv4 or IPv6 prefix route calculation at the same time. The route next hop is matched according to the topology result and uses IPv4 or IPv6 next hop. .

In summary, the methods provided by the above four examples can save IPv4/IPv6 address resources. In addition, the single-stack network supports dual-stack business requirements, simplifies network operation and maintenance, and reduces network equipment overhead. In addition, it provides a smooth evolution solution for the upgrade and transformation of the existing IPv4 basic network to IPv6 network.

Figure 16 is a schematic structural diagram of a route generation device 600 provided by an embodiment of the present application. The route generating device 600 includes an obtaining unit 601, a receiving unit 602 and a generating unit 603. Optionally, the route generating device 600 further includes a sending unit 604.

Optionally, combined with the application scenario shown in Figure 1, the route generation device 600 shown in Figure 16 is provided in the network device D in the method flow shown in Figure 1, and the receiving unit 602 is used to receive the route announcement shown in Figure 1 message, the generating unit 603 is used to generate routes in the routing table or forwarding table shown in Figure 1, and the obtaining unit 601 is used to obtain the network topology shown in Figure 1.

Optionally, combined with the method flow shown in Figure 2, the route generation device 600 shown in Figure 16 is provided in the first network device in the method flow shown in Figure 2, the obtaining unit 601 is used to perform S201, and the receiving unit 602 uses After executing S203, the generating unit 603 is used to execute S204. Optionally, the receiving unit 602 is also configured to perform S205, and the sending unit 604 is further configured to perform S206.

The device embodiment described in Figure 16 is only illustrative. For example, the division of the above units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated. to another system, or some features can be ignored, or not implemented. Each functional unit in various embodiments of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.

Each unit in the route generation device 600 is implemented in whole or in part by software, hardware, firmware, or any combination thereof.

Some possible implementations of using hardware or software to implement each functional unit in the route generation device 600 are described below in conjunction with the network device 800 described later.

In the case of software implementation, for example, the above-mentioned obtaining unit 601 and generating unit 603 are implemented by software functional units generated by at least one processor 801 in FIG. 18 after reading the program code stored in the memory 802.

In the case of hardware implementation, for example, the above-mentioned units in Figure 16 are respectively implemented by different hardware in the network device. For example, the acquisition unit 601 is implemented by a part of the processing resources of at least one processor 801 in Figure 18 (such as a multi-core processor). one core or two cores), while the generation unit 603 is implemented by the remainder of at least one processor 801 in FIG. 18 Processing resources (such as other cores in a multi-core processor), or using programmable devices such as field-programmable gate arrays (FPGAs) or co-processors. The receiving unit 602 is implemented by the network interface 803 in Figure 18.

Figure 17 is a schematic structural diagram of a data packet forwarding device 700 provided by an embodiment of the present application. The data packet forwarding device 700 includes a receiving unit 701 and a sending unit 702.

Optionally, in conjunction with the method flow shown in Figure 2, the data message forwarding device 700 shown in Figure 17 is located on the first network device in the method flow shown in Figure 2, and the receiving unit 701 is used to perform S205 and send Unit 702 is used to perform S206.

The device embodiment described in Figure 17 is only illustrative. For example, the division of the above units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated. to another system, or some features can be ignored, or not implemented. Each functional unit in various embodiments of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.

Each unit in the data packet forwarding device 700 is implemented in whole or in part by software, hardware, firmware, or any combination thereof.

Some possible implementations of using hardware or software to implement each functional unit in the data packet forwarding apparatus 700 are described below in conjunction with the network device 800 described below.

In the case of software implementation, for example, the above-mentioned receiving unit 701 and sending unit 702 are implemented by software functional units generated by at least one processor 801 in FIG. 18 after reading the program code stored in the memory 802.

In the case of hardware implementation, for example, the above-mentioned units in FIG. 17 are respectively implemented by different hardware in the network device. For example, the receiving unit 701 and the sending unit 702 are implemented by the network interface 803 in FIG. 18 .

The following is an example of the basic hardware structure of network equipment.

Figure 18 is a schematic structural diagram of a network device 800 provided by an embodiment of the present application. Network device 800 includes at least one processor 801, memory 802, and at least one network interface 803.

Optionally, combined with the application scenario shown in Figure 1, the network device 800 shown in Figure 18 is the network device D in Figure 1.

Optionally, in conjunction with Figure 2, the network device 800 shown in Figure 18 is the first network device in the method flow shown in Figure 2. The processor 801 is used to execute S201 and S204, and the network interface 803 is used to execute S203, S205 and S206.

The processor 801 is, for example, a general central processing unit (CPU), a network processor (NP), a graphics processing unit (GPU), or a neural network processor (neural-network processing units, NPU). ), a data processing unit (DPU), a microprocessor or one or more integrated circuits used to implement the solution of the present application. For example, the processor 801 includes an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof. PLD is, for example, a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a general array logic (GAL), or any combination thereof.

The memory 802 is, for example, a read-only memory (ROM) or other type of static storage device that can store static information and instructions, or a random access memory (random access memory, RAM) or a static storage device that can store static information and instructions. Other types of dynamic storage devices that store information and instructions, such as electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or Other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store expectations in the form of instructions or data structures program code and any other medium that can be accessed by a computer, without limitation. Optionally, the memory 802 exists independently and is connected to the processor 801 through an internal connection 804 . Alternatively, memory 802 and processor 801 are optionally integrated together.

Network interface 803 uses any transceiver-like device for communicating with other devices or communications networks. The network interface 803 includes, for example, at least one of a wired network interface or a wireless network interface. The wired network interface is, for example, an Ethernet interface. The Ethernet interface is, for example, an optical interface, an electrical interface or a combination thereof. The wireless network interface is, for example, a wireless local area network (WLAN) interface, a cellular network network interface or a combination thereof.

In some embodiments, processor 801 includes one or more CPUs, such as CPU0 and CPU1 as shown in Figure 18.

In some embodiments, network device 800 optionally includes multiple processors, such as processor 801 and processor 805 shown in Figure 18. Each of these processors is, for example, a single-core processor (single-CPU) or a multi-core processor (multi-CPU). Processor here optionally refers to one or more devices, circuits, and/or processing cores for processing data (eg, computer program instructions).

In some embodiments, network device 800 also includes internal connections 804. The processor 801, the memory 802 and at least one network interface 803 are connected through an internal connection 804. Internal connections 804 include pathways that carry information between the components described above. Optionally, internal connection 804 is a single board or bus. Optionally, the internal connections 804 are divided into address bus, data bus, control bus, etc.

In some embodiments, network device 800 also includes an input and output interface 806. Input/output interface 806 is connected to internal connection 804.

Optionally, the processor 801 implements the method in the above embodiment by reading the program code 810 stored in the memory 802, or the processor 801 implements the method in the above embodiment by using the internally stored program code. In the case where the processor 801 implements the method in the above embodiment by reading the program code 810 stored in the memory 802, the memory 802 stores the program code that implements the method provided by the embodiment of the present application.

For more details on how the processor 801 implements the above functions, please refer to the descriptions in the previous method embodiments, which will not be repeated here.

Refer to Figure 19, which is a schematic structural diagram of a network device provided by an embodiment of the present application. The network device 900 includes: a main control board 910 and an interface board 930 .

Optionally, combined with the application scenario shown in Figure 1, the network device 900 shown in Figure 19 is the network device D in Figure 1.

Optionally, combined with Figure 2, the network device 900 shown in Figure 19 is the first network device in the method flow shown in Figure 2. The main control board 910 is used to execute S201, S203 and S204, and the interface board 930 is used to Execute S205 and S206.

The main control board is also called the main processing unit (MPU) or route processor card. The main control board 910 is used to control and manage various components in the network device 900, including route calculation and device management. , equipment maintenance, protocol processing functions. The main control board 910 includes: a central processing unit 911 and a memory 912 .

The interface board 930 is also called a line processing unit (LPU), line card or industry service board. The interface board 930 is used to provide various service interfaces and implement data packet forwarding. The service interface includes but is not limited to an Ethernet interface, a POS (packet over sONET/SDH) interface, etc. The Ethernet interface is, for example, a flexible Ethernet service interface (flexible ethernet clients, FlexE clients). The interface board 930 includes: a central processor 931, a network processor 932, a forwarding entry memory 934, and a physical interface card (physical interface card, PIC) 933.

The central processor 931 on the interface board 930 is used to control and manage the interface board 930 and communicate with the central processor 911 on the main control board 910 .

The network processor 932 is used to implement packet forwarding processing. The network processor 932 is, for example, a forwarding chip. Specifically, the network processor 932 is configured to forward the received message based on the forwarding table stored in the forwarding table memory 934. If the destination address of the message is the address of the network device 900, then upload the message to the CPU ( Such as central processing unit 911) processing; if the destination address of the message is not the address of the network device 900, the next hop and outgoing interface corresponding to the destination address are found from 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 uplink packets includes: processing of packet incoming interfaces, forwarding table search; processing of downlink packets: forwarding table search, etc.

The physical interface card 933 is used to implement the docking function of the physical layer. The original traffic enters the interface card 930 through this, and the processed packets are sent out from the physical interface card 933. The physical interface card 933 is also called a daughter card and can be installed on the interface board 930. It is responsible for converting photoelectric signals into messages and checking the validity of the messages before forwarding them to the network processor 932 for processing. In some embodiments, the central processor can also perform the functions of the network processor 932, such as implementing software forwarding based on a general-purpose CPU, so that the network processor 932 is not required in the physical interface card 933.

Optionally, the network device 900 includes multiple interface boards. For example, the network device 900 also includes an interface board 940. The interface board 940 includes: a central processor 941, a network processor 942, a forwarding entry memory 944, and a physical interface card 943.

Optionally, the network device 900 also includes a switching network board 920. The switching fabric unit 920 is also called a switching fabric unit (SFU). When the network device has multiple interface boards 930, the switching network board 920 is used to complete data exchange between the interface boards. For example, the interface board 930 and the interface board 940 communicate through the switching network board 920, for example.

The main control board 910 and the interface board 930 are coupled. For example. The main control board 910, the interface board 930, the interface board 940, and the switching network board 920 are connected to the system backplane through a system bus to achieve intercommunication. In one possible implementation, an inter-process communication protocol (IPC) channel is established between the main control board 910 and the interface board 930, and the main control board 910 and the interface board 930 communicate through the IPC channel.

Logically, the network device 900 includes a control plane and a forwarding plane. The control plane includes a main control board 910 and a central processor 931. The forwarding plane includes various components that perform forwarding, such as forwarding entry memory 934, physical interface card 933, and network processing. Device 932. The control plane executes functions such as router, generates forwarding tables, processes signaling and protocol messages, configures and maintains device status. The control plane sends the generated forwarding tables to the forwarding plane. On the forwarding plane, the network processor 932 is based on the control plane. The delivered forwarding table looks up the packets received by the physical interface card 933 and forwards them. The forwarding table delivered by the control plane is stored in the forwarding table entry memory 934, for example. In some embodiments, the control plane and the forwarding plane are, for example, completely separate and not on the same device.

The operations on the interface board 940 are the same as those on the interface board 930, and will not be described again for the sake of simplicity. It should be understood that the network device 900 in this embodiment may correspond to the first network device in the above method embodiments, and the main control board 910, interface board 930 and/or 940 in the network device 900 implement, for example, the above method embodiments. For the sake of brevity, the functions of the first network device and/or the various steps performed will not be described again here.

There may be one or more main control boards. When there are multiple main control boards, for example, they include the main main control board and the backup main control board. There may be one or more interface boards. The stronger the data processing capability of the network device, the more interface boards are provided. There can also be one or more physical interface cards on the interface board. There may be no switching network board, or there may be one or more. When there are multiple boards, they can be used together. Implement load sharing and redundant backup. Under the centralized forwarding architecture, network equipment does not need switching network boards, and the interface boards are responsible for processing the business data of the entire system. Under the distributed forwarding architecture, network equipment can have at least one switching network board, which enables data exchange between multiple interface boards through the switching network board, providing large-capacity data exchange and processing capabilities. Therefore, the data access and processing capabilities of network equipment with a distributed architecture are greater than those with a centralized architecture. Optionally, the network device can also be in the form of only one board, that is, there is no switching network board. The functions of the interface board and the main control board are integrated on this board. In this case, the central processor and main control board on the interface board The central processor on the board can be combined into one central processor on this board to perform the superimposed functions of the two. This form of equipment has low data exchange and processing capabilities (for example, low-end switches or routers and other networks equipment). The specific architecture used depends on the specific networking deployment scenario and is not limited here.

Each embodiment in this specification is described in a progressive manner. The same and similar parts between the various embodiments can be referred to each other. Each embodiment focuses on its differences from other embodiments.

A refers to B, which means that A is the same as B or that A is a simple transformation of B.

The terms "first" and "second" in the description and claims of the embodiments of this application are used to distinguish different objects, rather than to describe a specific order of objects, and cannot be understood to indicate or imply relative importance. sex. For example, the first network device and the second network device are used to distinguish different network devices rather than describing a specific order of the network devices, nor can it be understood that the first network device is more important than the second network device.

The information (including but not limited to user equipment information, user personal information, etc.), data (including but not limited to data used for analysis, stored data, displayed data, etc.) and signals involved in the embodiments of this application are all processed. Authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data need to comply with relevant laws, regulations and standards of relevant countries and regions. For example, the address information involved in this application was obtained with full authorization.

The above embodiments may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using software, it may 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 a computer, the processes or functions described in accordance with the embodiments of the present application are generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another, e.g., the computer instructions may be transferred from a website, computer, server, or data center Transmission to another website, computer, server or data center by wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) means. The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains one or more available media integrated therein. The available media may be magnetic media (eg, floppy disk, hard disk, magnetic tape), optical media (eg, DVD), or semiconductor media (eg, Solid State Disk (SSD)), etc.

The above embodiments are only used to illustrate the technical solutions of the present application, but are not intended to limit them. Although the present application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that they can still modify the technical solutions described in the foregoing embodiments. Modifications may be made to the recorded technical solutions, or equivalent substitutions may be made to some of the technical features; however, these modifications or substitutions do not cause the essence of the corresponding technical solutions to depart from the scope of the technical solutions of the embodiments of the present application.

Claims

A route generation method, characterized by including:

The first network device obtains the network topology;

The first network device receives a route advertisement message from the second network device, and the route advertisement message is used to publish address information corresponding to the first protocol stack;

The first network device generates a route, the route includes the address information corresponding to the first protocol stack and the address information corresponding to the second protocol stack, and the address information corresponding to the second protocol stack is the network The address information of the endpoint network device of the first link in the topology.
The method according to claim 1, characterized in that the address information of endpoint network devices of all other links except the first link in the network topology is address information corresponding to the second protocol stack.
The method of claim 1, wherein the network topology further includes a second link, and an endpoint network device of the second link includes address information corresponding to the first protocol stack.
The method of claim 1, wherein the network topology includes a dual-stack link, and the endpoint network device of the dual-stack link includes address information corresponding to the first protocol stack and information corresponding to the second protocol stack. address information.
The method of claim 1, wherein the second network device belongs to the BGP SPF routing domain and belongs to the Interior Gateway Protocol IGP routing domain, and the address information corresponding to the first protocol stack is the IGP routing domain the address information of the third network device; or,

The address information corresponding to the first protocol stack is the address information of the user equipment accessed by the second network device.
The method according to any one of claims 1 to 5, characterized in that the first network device obtains the network topology, including:

The first network device receives a link advertisement message, and the link advertisement message is used to publish address information of an endpoint network device of the first link;

The first network device obtains the network topology based on address information of an endpoint network device of the first link.
The method according to any one of claims 1 to 6, characterized in that the route advertisement message is a Border Gateway Protocol shortest path first calculation BGP SPF message.
The method according to any one of claims 1 to 7, characterized in that the first protocol stack is an Internet Protocol version 4 IPv4 protocol stack, and the second protocol stack is an Internet Protocol version 6 IPv6 protocol stack. ;or,

The first protocol stack is an IPv6 protocol stack, and the second protocol stack is an IPv4 protocol stack.
A method for forwarding data messages, which is characterized by including:

The first network device receives a data packet, where the data packet includes address information corresponding to the first protocol stack;

The first network device forwards the data message to the address information corresponding to the second protocol stack based on the address information corresponding to the first protocol stack and the route. The route includes the address information corresponding to the first protocol stack. The address information and the address information corresponding to the second protocol stack.
The method according to claim 9, wherein the first protocol stack is an Internet Protocol version 4 IPv4 protocol stack, and the second protocol stack is an Internet Protocol version 6 IPv6 protocol stack; or,

The first protocol stack is an IPv6 protocol stack, and the second protocol stack is an IPv4 protocol stack.
A route generation device, characterized by including:

Obtain unit, used to obtain network topology;

A receiving unit configured to receive a route advertisement message from the second network device, where the route advertisement message is used to publish address information corresponding to the first protocol stack;

Generating unit, configured to generate a route, the route including the address information corresponding to the first protocol stack and the address information corresponding to the second protocol stack, the address information corresponding to the second protocol stack being the network topology The address information of the network device at the endpoint of the first link.
The apparatus according to claim 11, wherein the address information of endpoint network devices of all other links except the first link in the network topology is address information corresponding to the second protocol stack.
The apparatus according to claim 11, wherein the network topology further includes a second link, and an endpoint network device of the second link includes address information corresponding to the first protocol stack.
The apparatus according to claim 11, wherein the network topology includes a dual-stack link, and the endpoint network device of the dual-stack link includes address information corresponding to the first protocol stack and information corresponding to the second protocol stack. address information.
The device according to claim 11, characterized in that the second network device belongs to the BGP SPF routing domain and belongs to the Interior Gateway Protocol IGP routing domain, and the address information corresponding to the first protocol stack is the IGP routing domain the address information of the third network device; or,

The address information corresponding to the first protocol stack is the address information of the user equipment accessed by the second network device.
The device according to any one of claims 11 to 15, characterized in that the obtaining unit is configured to receive a link announcement message, and the link announcement message is used to publish the link of the first link. The address information of the endpoint network device; the network topology is obtained according to the address information of the endpoint network device of the first link.
The device according to any one of claims 11 to 16, characterized in that the route advertisement message is a Border Gateway Protocol shortest path first calculation BGP SPF message.
The device according to any one of claims 11 to 17, characterized in that the first protocol stack is an Internet Protocol version 4 IPv4 protocol stack, the second protocol stack is the Internet protocol version 6 IPv6 protocol stack; or,

The first protocol stack is an IPv6 protocol stack, and the second protocol stack is an IPv4 protocol stack.
A data message forwarding device, characterized by including:

A receiving unit, configured to receive a data message, where the data message includes address information corresponding to the first protocol stack;

A sending unit, configured to forward the data message to the address information corresponding to the second protocol stack based on the address information corresponding to the first protocol stack and the route, where the route includes the address information corresponding to the first protocol stack. address information and the address information corresponding to the second protocol stack.
The device according to claim 19, wherein the first protocol stack is an Internet Protocol version 4 IPv4 protocol stack, and the second protocol stack is an Internet Protocol version 6 IPv6 protocol stack; or,

The first protocol stack is an IPv6 protocol stack, and the second protocol stack is an IPv4 protocol stack.
A network device, characterized in that the network device includes a processor and a network interface, and the processor is configured to execute instructions so that the network device executes the method according to any one of claims 1 to 10 , the network interface is used to receive or send messages.
A computer-readable storage medium, characterized in that at least one instruction is stored in the storage medium, and when the instruction is run on a processor, it causes the processor to execute the method described in any one of claims 1-10. method.
A computer program product, characterized in that the computer program product includes one or more computer program instructions, which when the computer program instructions are loaded and run by a computer, cause the computer to execute any one of claims 1-10 method described in the item.