WO2023169364A1 - Procédé et appareil de génération de routage, et procédé et appareil de transfert de message de données - Google Patents

Procédé et appareil de génération de routage, et procédé et appareil de transfert de message de données Download PDF

Info

Publication number
WO2023169364A1
WO2023169364A1 PCT/CN2023/079852 CN2023079852W WO2023169364A1 WO 2023169364 A1 WO2023169364 A1 WO 2023169364A1 CN 2023079852 W CN2023079852 W CN 2023079852W WO 2023169364 A1 WO2023169364 A1 WO 2023169364A1
Authority
WO
WIPO (PCT)
Prior art keywords
network device
protocol stack
address information
link
network
Prior art date
Application number
PCT/CN2023/079852
Other languages
English (en)
Chinese (zh)
Inventor
庞东磊
王海波
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from CN202210459509.7A external-priority patent/CN116781618A/zh
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2023169364A1 publication Critical patent/WO2023169364A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/74—Address processing for routing
    • H04L45/741—Routing in networks with a plurality of addressing schemes, e.g. with both IPv4 and IPv6

Definitions

  • 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.
  • IPv4 Internet Protocol version 4
  • IPv6 Internet protocol version 6
  • 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.
  • 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.
  • 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.
  • IP Internet protocol
  • 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 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 network topology includes a dual-stack link
  • 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.
  • 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.
  • the address information corresponding to the first protocol stack is the address information of the user equipment accessed by the second network device.
  • 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 route advertisement message is a BGP SPF message.
  • the first protocol stack is an IPv4 protocol stack
  • the second protocol stack is an IPv6 protocol stack
  • the first protocol stack is an IPv6 protocol stack
  • the second protocol stack is an IPv4 protocol stack.
  • 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 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.
  • the first protocol stack is an IPv4 protocol stack
  • the second protocol stack is an IPv6 protocol stack
  • the first protocol stack is an IPv6 protocol stack
  • the second protocol stack is an IPv4 protocol stack.
  • a route generation device 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.
  • 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.
  • 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.
  • a 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.
  • 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.
  • a network device in a fifth aspect, 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.
  • a network device in a sixth aspect, 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.
  • the network equipment please refer to the above-mentioned second aspect or any optional method of the second aspect, and will not be described again here.
  • a computer-readable storage medium stores at least one instruction.
  • the 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.
  • a computer-readable storage medium stores at least one instruction.
  • the 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.
  • a computer program product includes one or more computer program instructions.
  • the 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.
  • a computer program product includes one or more computer program instructions.
  • the computer program product includes one or more computer program instructions.
  • the 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.
  • a chip 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.
  • a chip 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.
  • a network device in a thirteenth aspect, 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.
  • the network device includes a unit for performing the method in the first aspect or any possible implementation of the first aspect.
  • a network device in a fourteenth aspect, 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.
  • the network device includes a unit for performing the method in the second aspect or any possible implementation of the second aspect.
  • 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;
  • FIG. 12 is a schematic diagram of an IPv4 topology provided by an embodiment of the present application.
  • FIG. 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.
  • 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).
  • CE custom 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.
  • 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.
  • network device E and network device F are both connected to CE.
  • 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 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.
  • IPv4 protocol stack and IPv6 protocol stack as an example
  • IPv6 protocol stack 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.
  • IP Internet protocol
  • 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.
  • the scale of the network becomes larger and larger, which undoubtedly requires a large number of IP addresses.
  • 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.
  • the two protocol stacks are the IPv4 protocol stack and the IPv6 protocol stack as an example.
  • the outgoing interface is one of the network device itself configured with an IPv6 address.
  • 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.
  • the next hop is the IPv4 address configured for an interface of the peer network device.
  • the types of IP protocol stacks corresponding to the three things: prefix, next hop, and outbound interface are inconsistent.
  • the address family type of the prefix and the address family type of the next hop are different.
  • the prefix is an IPv4 prefix and the next hop is an IPv6 address
  • the prefix is an IPv6 prefix and the next hop is an IPv4 address.
  • this method reduces the number of IP addresses that network devices need to configure to support dual-stack services, and saves IP address resources.
  • 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.
  • 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.
  • first protocol stack and “second protocol stack” are used to describe multiple different protocol stacks.
  • the first protocol stack is an IPv4 protocol stack
  • the second protocol stack is an IPv6 protocol stack.
  • the first protocol stack is an IPv6 protocol stack
  • the second protocol stack is an IPv4 protocol stack.
  • the type of protocol stack is not limited in this application.
  • 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.
  • the first network device in the method shown in FIG. 2 is the network device D in FIG. 1
  • the second network device in the method shown in FIG. 2 is the network device E in FIG. 1 .
  • the first network device obtains the network topology.
  • Network topology indicates the network devices and links that exist in a routing domain.
  • the network topology includes address information for endpoint network devices of at least one link.
  • 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.
  • all links in the network topology are IPv6 links.
  • the address information of the endpoint network devices of all links in the network topology is IPv6 address.
  • 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.
  • link 1 is an IPv6 link
  • 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.
  • 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.
  • the address information of the endpoint network devices of all links in the network topology is IPv4 address.
  • all links in the network topology are IPv4 links.
  • 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
  • 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.
  • link 1 is an IPv4 link
  • 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.
  • 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.
  • 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.
  • 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
  • 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.
  • link 1 is an IPv4 link
  • 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.
  • link 1 is an IPv6 link
  • 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.
  • the network topology includes a dual-stack link
  • 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.
  • 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.
  • the above address information includes at least one of a prefix or an IP address.
  • the above address information is IPv4 address information.
  • the above address information includes at least one of an IPv4 prefix or an IPv4 address.
  • the above address information is IPv6 address information.
  • 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.
  • 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.
  • 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.
  • 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.
  • the above-mentioned first routing domain is an IGP routing domain
  • the second routing domain is a BGP SPF routing domain.
  • the above-mentioned first routing domain is a BGP SPF routing domain
  • 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.
  • the route advertisement message includes an identification of the second network device and address information corresponding to the first protocol stack.
  • 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.
  • route advertisement messages are BGP SPF messages.
  • the route advertisement message is an IGP message.
  • route advertisement messages are open shortest path first (OSPF) messages or intermediate system to intermediate system (IS-IS) protocol messages.
  • OSPF open shortest path first
  • IS-IS intermediate system to intermediate system protocol
  • the route advertisement message includes BGP SPF prefix network layer reachability information (network layer reachability information, NLRI).
  • BGP SPF prefix network layer reachability information network layer reachability information, NLRI.
  • 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 is the protocol stack.
  • the first network device receives the route advertisement message from the second network device.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the route includes a destination prefix, and the destination prefix in the route is a prefix corresponding to the first protocol stack.
  • the route includes a destination address, and the destination address in the route is an address corresponding to the first protocol stack.
  • the address information corresponding to the second protocol stack in the route is obtained based on the network topology.
  • 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.
  • a route includes a next hop and an outbound interface.
  • 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.
  • the next hop is included in the route but not the outbound interface.
  • network device D 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
  • 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).
  • 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.
  • the first network device receives the data message.
  • the data packet includes address information corresponding to the first protocol stack.
  • the destination address field of the data message includes an IP address corresponding to the first protocol stack.
  • 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.
  • 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.
  • the object of route calculation is the address information corresponding to the first protocol stack
  • 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
  • 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 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.
  • 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.
  • the link advertisement message includes the BGP SPF link NLRI.
  • 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 first network device further obtains the network topology based on the identity of at least one network device.
  • 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.
  • the node advertisement message includes the BGP SPF node NLRI shown in Figure 6.
  • node information, link information, and prefix information are advertised through three different messages.
  • the node advertisement message, the link advertisement message and the route advertisement message are three different messages.
  • node information, link information, and prefix information are advertised through the same packet.
  • 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.
  • the BGP SPF protocol is briefly described below.
  • 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.
  • 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.
  • 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.
  • mechanisms in the BGP protocol please refer to the introduction of RFC4271 and RFC7606.
  • 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.
  • route calculation based on the BGP SPF 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • TCP transmission control protocol
  • 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.
  • 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.
  • 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.
  • 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.
  • 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).
  • the local node descriptor field carries the AS number (autonomous system number) of the network device and the router ID. (router-ID).
  • 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.
  • the prefix descriptor field has a TLV encoding structure.
  • 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.
  • the prefix descriptor field specifically includes a type field, a length field, a prefix length field and an IP prefix field.
  • the value of the type field in the prefix descriptor field that is, TLV type is 265.
  • the IP prefix field carries a specific IPv4 prefix
  • the prefix length field carries the length of the IPv4 prefix.
  • the IP prefix field carries a specific IPv6 prefix
  • the prefix length field carries the length of the IPv6 prefix.
  • 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.
  • 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.
  • protocol ID protocol-ID
  • identifier identifier
  • descriptors local node descriptors
  • remote node descriptors remote node descriptors
  • link descriptors link descriptors
  • 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.
  • 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
  • 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.
  • 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.
  • 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.
  • the local node descriptor field includes the identity of network device A
  • the remote node descriptor field includes the identity of network device B
  • the link descriptor field includes the IP address of interface A and the IP address of interface B. .
  • 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.
  • protocol ID protocol-ID
  • identifier identifier
  • local node descriptors local node descriptors
  • 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.
  • FIG. 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.
  • each link between network devices in the IGP routing domain is an IPv4 link
  • 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.
  • the inter-domain splicing node 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.
  • IPv6 prefix destination routes or IPv6 prefix destination routes with the IPv6 address as the next hop 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.
  • FIG 8 is a schematic diagram of another splicing deployment scenario of BGP SPF routing domain and IGP routing domain provided in this embodiment.
  • 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.
  • inter-domain splicing nodes between the BGP SPF routing domain and the IGP routing domain such as network device C and network device D
  • 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.
  • network device E is an illustration of the second network device in the method shown in Figure 2
  • 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).
  • 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.
  • BGP SPF prefix-NLRI 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • BGP SPF prefix-NLRI 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 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.
  • 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.
  • 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.
  • 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.
  • the network device generates IPv4 topology and IPv6 topology respectively.
  • the network device generates a topology that includes IPv4 links and IPv6 links. This topology may be called a hybrid dual-stack topology.
  • 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
  • the hybrid dual-stack topology generated by the network device is shown in Figure 14.
  • IPv4 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.
  • 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.
  • IPv4 links 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.
  • 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.
  • 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. .
  • the methods provided by the above four examples can save IPv4/IPv6 address resources.
  • the single-stack network supports dual-stack business requirements, simplifies network operation and maintenance, and reduces network equipment overhead.
  • it provides a smooth evolution solution for the upgrade and transformation of the existing IPv4 basic network to IPv6 network.
  • FIG 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.
  • the route generating device 600 further includes a sending unit 604.
  • 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.
  • 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.
  • 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.
  • the division of the above units is only a logical function division. In actual implementation, there may be other division methods.
  • 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.
  • 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.
  • the above-mentioned units in Figure 16 are respectively implemented by different hardware in the network device.
  • 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.
  • FIG 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.
  • 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.
  • the division of the above units is only a logical function division. In actual implementation, there may be other division methods.
  • 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.
  • 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.
  • the above-mentioned units in FIG. 17 are respectively implemented by different hardware in the network device.
  • the receiving unit 701 and the sending unit 702 are implemented by the network interface 803 in FIG. 18 .
  • FIG 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.
  • the network device 800 shown in Figure 18 is the network device D in Figure 1.
  • 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.
  • the processor 801 includes an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof.
  • ASIC application-specific integrated circuit
  • PLD programmable logic device
  • 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.
  • ROM read-only memory
  • RAM random access memory
  • 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.
  • the memory 802 exists independently and is connected to the processor 801 through an internal connection 804 .
  • 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.
  • WLAN wireless local area network
  • processor 801 includes one or more CPUs, such as CPU0 and CPU1 as shown in Figure 18.
  • 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).
  • 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.
  • internal connection 804 is a single board or bus.
  • the internal connections 804 are divided into address bus, data bus, control bus, etc.
  • network device 800 also includes an input and output interface 806. Input/output interface 806 is connected to internal connection 804.
  • 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.
  • 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.
  • processor 801 implements the above functions, please refer to the descriptions in the previous method embodiments, which will not be repeated here.
  • the network device 900 includes: a main control board 910 and an interface board 930 .
  • the network device 900 shown in Figure 19 is the network device D in Figure 1.
  • 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.
  • 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.
  • 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.
  • 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.
  • the network device 900 includes multiple interface boards.
  • 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.
  • the network device 900 also includes a switching network board 920.
  • the switching fabric unit 920 is also called a switching fabric unit (SFU).
  • SFU switching fabric unit
  • the switching network board 920 is used to complete data exchange between the interface boards.
  • 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.
  • 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.
  • 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.
  • IPC inter-process communication protocol
  • 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.
  • 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.
  • 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.
  • the control plane and the forwarding plane are, for example, completely separate and not on the same device.
  • 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.
  • the functions of the first network device and/or the various steps performed will not be described again here.
  • main control boards 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.
  • 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.
  • 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.
  • A refers to B, which means that A is the same as B or that A is a simple transformation of B.
  • 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.
  • 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.
  • signals involved in the embodiments of this application are all processed.
  • the above embodiments may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • software 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.
  • the computer program 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

La présente demande a trait au domaine technique des communications. Elle concerne un procédé et un appareil de génération de routage, ainsi qu'un procédé et un appareil de transfert de message de données. Selon la présente demande, un objet de calcul de routage comprend des informations d'adresse correspondant à une première pile de protocoles, et un résultat de calcul de routage comprend des informations d'adresse correspondant à une seconde pile de protocoles, c'est-à-dire qu'il est permis que l'objet de calcul de routage et le résultat de calcul de routage aient des types de famille d'adresses différents. De cette manière, un procédé de prise en charge d'un calcul de routage hybride à double pile est mis en œuvre. Par rapport à un mode de calcul de routage à pile unique dans l'état de la technique, le procédé permet, en configurant une adresse IPv4 et une adresse IPv6 sur une interface correspondant à une liaison, de répondre aux exigences d'un service à double pile, sans qu'il soit nécessaire de configurer les adresses de deux piles de protocole, ce qui permet d'économiser les ressources d'adresse IP.
PCT/CN2023/079852 2022-03-11 2023-03-06 Procédé et appareil de génération de routage, et procédé et appareil de transfert de message de données WO2023169364A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN202210239542 2022-03-11
CN202210239542.9 2022-03-11
CN202210459509.7A CN116781618A (zh) 2022-03-11 2022-04-27 路由生成方法、数据报文的转发方法及装置
CN202210459509.7 2022-04-27

Publications (1)

Publication Number Publication Date
WO2023169364A1 true WO2023169364A1 (fr) 2023-09-14

Family

ID=87935992

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/079852 WO2023169364A1 (fr) 2022-03-11 2023-03-06 Procédé et appareil de génération de routage, et procédé et appareil de transfert de message de données

Country Status (1)

Country Link
WO (1) WO2023169364A1 (fr)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2001031888A1 (fr) * 1999-10-26 2001-05-03 3Com Corporation Procede et systeme pour l'utilisation d'adresses en double reseau par tunnellisation virtuelle
CN1972295A (zh) * 2006-12-01 2007-05-30 清华大学 BGP协议软件的IPv4 over IPv6扩展方法
US7246175B1 (en) * 2001-12-07 2007-07-17 Cisco Technology, Inc. IPv6 over MPLS IPv4 core
CN101667968A (zh) * 2009-09-11 2010-03-10 华为技术有限公司 一种IPv6报文的转发方法、设备和系统
CN110601982A (zh) * 2019-09-27 2019-12-20 新华三信息安全技术有限公司 路由传递方法、装置及路由器
CN111130978A (zh) * 2019-12-03 2020-05-08 杭州迪普科技股份有限公司 网络流量转发方法、装置、电子设备及机器可读存储介质

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2001031888A1 (fr) * 1999-10-26 2001-05-03 3Com Corporation Procede et systeme pour l'utilisation d'adresses en double reseau par tunnellisation virtuelle
US7246175B1 (en) * 2001-12-07 2007-07-17 Cisco Technology, Inc. IPv6 over MPLS IPv4 core
CN1972295A (zh) * 2006-12-01 2007-05-30 清华大学 BGP协议软件的IPv4 over IPv6扩展方法
CN101667968A (zh) * 2009-09-11 2010-03-10 华为技术有限公司 一种IPv6报文的转发方法、设备和系统
CN110601982A (zh) * 2019-09-27 2019-12-20 新华三信息安全技术有限公司 路由传递方法、装置及路由器
CN111130978A (zh) * 2019-12-03 2020-05-08 杭州迪普科技股份有限公司 网络流量转发方法、装置、电子设备及机器可读存储介质

Similar Documents

Publication Publication Date Title
US10375193B2 (en) Source IP address transparency systems and methods
WO2021233267A1 (fr) Procédé de transfert de message dans une chaîne de fonctions de service srv6, sff et dispositif sf
CN111510378A (zh) Evpn报文处理方法、设备及系统
WO2021164258A1 (fr) Procédé de génération d'entrée de transfert, procédé d'envoi de message, dispositif de réseau et système
US9467374B2 (en) Supporting multiple IEC-101/IEC-104 masters on an IEC-101/IEC-104 translation gateway
US11863454B2 (en) Systems and methods for scalable validation of multiple paths in a network using segment routing
WO2023274083A1 (fr) Procédé et appareil de publication de route, procédé et appareil de réacheminement de paquets, dispositif, et support de stockage
WO2022028216A1 (fr) Système, appareil et procédé de transmission d'informations accessibles de couche réseau, et dispositif de réseau
CN115865769A (zh) 报文处理方法、网络设备及系统
US20230269164A1 (en) Method and apparatus for sending route calculation information, device, and storage medium
WO2021147357A1 (fr) Procédé, dispositif et système de distribution d'informations de routage
US20230353479A1 (en) Edge Computing Data and Service Discovery Using an Interior Gateway Protocol (IGP)
WO2022188530A1 (fr) Procédé de traitement d'itinéraire et dispositif de réseau
WO2022111666A1 (fr) Procédé, appareil et système d'annonce d'itinéraire
WO2023169364A1 (fr) Procédé et appareil de génération de routage, et procédé et appareil de transfert de message de données
WO2022088685A1 (fr) Procédé et appareil d'acquisition de nom sémantique, dispositif, et support de stockage
CN114422415B (zh) 在分段路由中的出口节点处理流
CN114513485A (zh) 获取映射规则的方法、装置、设备、系统及可读存储介质
CN113285878A (zh) 负载分担的方法、第一网络设备
CN116781618A (zh) 路由生成方法、数据报文的转发方法及装置
US20240187346A1 (en) Systems and methods for scalable validation of multiple paths in a network using segment routing
WO2023116226A1 (fr) Procédé d'annonce d'itinéraire et dispositif associé
WO2022012690A1 (fr) Procédé d'annonce de routeur et dispositif associé
US10924395B2 (en) Seamless multipoint label distribution protocol (mLDP) transport over a bit index explicit replication (BIER) core
CN109861912B (zh) 优化用于电子设备内的虚拟节点的结构路径转发

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23765942

Country of ref document: EP

Kind code of ref document: A1