Ingress Node Multi-Topology Packet Forwarding
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In multi-topology networks, packets initiated from a default topology network with duplicate destination addresses pose a challenge as the ingress node cannot correctly select the appropriate routing information base (RIB) or forwarding information base (FIB) due to ambiguity in topology selection.
Innovation Solution
The solution involves an ingress node in a multi-topology network receiving packets from a physical or logical topology network, obtaining information about the ingress interface, adding a multi-topology attribute to the packet, and using a pre-stored mapping relationship to determine the corresponding downlink topology's RIB or FIB for forwarding the packet to an egress node.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the ingress node uses multiple RIBs/FIBs for multiple logical topologies, then the network supports service separation and multiple applications, but the ingress node cannot correctly select the appropriate RIB/FIB when packets from the default topology have duplicate destination addresses
Solution Approach 1:
The patent introduces a multi-topology attribute as an intermediary element that is added to packets entering the multi-topology network from the default topology. This attribute acts as a mediator that carries topology identification information through the network, enabling intermediate nodes to correctly identify which logical topology the packet belongs to and select the appropriate RIB/FIB for forwarding, thereby resolving the ambiguity caused by duplicate destination addresses.
Solution Approach 2:
The patent applies preliminary action by adding the multi-topology attribute to packets at the ingress node before they enter the multi-topology network. This pre-marking ensures that downstream nodes can immediately identify the packet's intended topology without needing to perform complex routing decisions at each hop, thus preventing forwarding errors before they occur.
2Reliability
If the ingress node adds multi-topology attribute and uses mapping relationship between ingress interface and downlink topology, then correct topology selection is achieved, but the system complexity increases
Solution Approach 1:
The patent implements self-service by automatically establishing the mapping relationship between ingress interfaces and downlink topologies. The system autonomously configures this mapping based on the network topology structure, eliminating the need for manual configuration of complex routing policies. The ingress node automatically adds the appropriate multi-topology attribute to packets based on the ingress interface used, reducing operational complexity while maintaining high reliability.
Data Source
Figure 1
Figure 2~3
Figure 4~5
AI summary
The present invention discloses a method, an apparatus, and a system for forwarding a packet in a multi-topology network, relating to the field of communications technologies. The method includes: receiving, by an ingress node in the multi-topology network, a packet sent by a first network, and obtaining information of an ingress interface receiving the packet; where the first network is a network except the multi-topology network; obtaining a routing information base RIB or a forwarding information base FIB of a corresponding downlink topology according to the information of the ingress interface; and forwarding the packet to an egress node in the multi-topology network according to the RIB or the FIB of the corresponding downlink topology. According to the present invention, the ingress interface is associated with the downlink topology; after the ingress node receives a packet, the corresponding downlink topology may be found according to the information of the ingress interface so that the problem that the downlink topology fails to be correctly selected in the case of duplicate destination addresses is solved.