Forwarding Entry Generation for Loop-Free Backup Path Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Network resource waste and congestion occur due to loop problems during packet forwarding when backup paths are used, particularly in network scenarios involving network devices connected to access and backbone networks.
Innovation Solution
A forwarding entry generation method that includes generating a forwarding entry with a segment identifier of a specified network device, allowing packets to be forwarded directly to that device, thereby avoiding loops and reducing resource waste and congestion.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If the network device stores a separate forwarding entry for each message type in a message queue, then message forwarding accuracy is improved, but device memory consumption increases and forwarding efficiency decreases due to excessive context switching
Solution Approach 1:
The patent merges multiple message types into a single forwarding entry by using message type identification bits within the destination address field. Instead of creating separate forwarding entries for each message type, the system combines them into one unified entry that can handle multiple message types through bit manipulation and masking operations on the destination address.
Solution Approach 2:
The forwarding entry is designed to be universal by incorporating message type identification capabilities directly into the destination address structure. A single forwarding entry can serve multiple message types by interpreting different bit patterns within the same destination address field, making the forwarding mechanism multi-functional rather than requiring separate specialized entries for each message type.
2Measurement precision
If the network device creates specific forwarding entries for different message types, then message routing precision is improved, but device complexity increases due to multiple queue management mechanisms
Solution Approach 1:
The patent combines multiple queue management functions into a single unified forwarding entry structure. By embedding message type identification bits within the destination address and using a single forwarding entry to manage multiple message types, the system reduces the number of separate queue management mechanisms while maintaining precise routing capabilities through bit-level address manipulation.
Solution Approach 2:
The system changes the parameter representation by encoding message type information within the existing destination address parameter rather than creating separate parameters for each message type. This allows the same destination address parameter to represent multiple message types by changing its bit pattern, thereby reducing device complexity while maintaining routing precision.
3Device complexity
If the network device uses a single forwarding entry for multiple message types, then device complexity is reduced, but message forwarding precision may be compromised
Solution Approach 1:
The patent applies local quality by differentiating message types through specific bit positions within the destination address field. While the forwarding entry structure is unified, the actual message type identification is achieved through localized bit manipulation at specific positions in the destination address, allowing precise message type recognition without requiring separate forwarding entries for each message type.
Solution Approach 2:
The system maintains forwarding precision by dynamically changing the interpretation of the destination address parameter based on message type. Through bit masking and manipulation operations, the same destination address parameter can be precisely interpreted to identify different message types, ensuring that forwarding precision is maintained even with a unified forwarding entry structure.
Data Source
Figure 1~2
Figure 3
Figure 4
AI summary
This application discloses a forwarding entry generation method, a packet sending method, a network device, and a system, so that a specified network device cannot use a backup forwarding path to forward a packet, thereby reducing, to some extent, a technical problem such as network resource waste or network congestion caused by a loop problem. The method includes: A first network device obtains routing information advertised by a second network device; and the first network device determines that the routing information advertised by the second network device matches a summary route stored in the first network device, and generates, based on a segment identifier of the second network device, a forwarding entry corresponding to the summary route. The forwarding entry includes the segment identifier of the second network device, and a forwarding path corresponding to the forwarding entry passes through the second network device.