Flex-Algorithm Routing in Non-Segment-Routing Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Non-segment-routing networks lack the ability to utilize flex-algorithms for routing traffic efficiently, as they are not configured to support segment routing protocols, limiting their capacity to calculate and manage least-cost paths for traffic transmission.
Innovation Solution
Network devices in non-segment-routing networks advertise flex-algorithm definitions and associated addresses, allowing them to configure routing tables that map flex-algorithm IDs to specific addresses, enabling the calculation of least-cost paths and routing of traffic based on these addresses, even without segment routing capabilities.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If non-segment-routing networks use traditional routing protocols, then network compatibility is maintained, but the ability to calculate and manage least-cost paths for traffic transmission is limited
Solution Approach 1:
The patent introduces a loopback address as an intermediary between non-segment-routing networks and flex-algorithm routing. The loopback address serves as a mediator that allows traditional routing protocols to interact with segment routing capabilities without requiring full segment routing configuration. Network devices advertise the loopback address alongside flex-algorithm information, enabling other devices to route traffic to the flex-algorithm destination through this intermediary address while maintaining compatibility with existing routing protocols.
Solution Approach 2:
The patent enables loopback addresses to serve multiple functions: they continue to provide their traditional role as a stable routing target for network devices, while simultaneously serving as the destination address for flex-algorithm traffic in non-segment-routing networks. This multi-functionality allows a single address to support both traditional routing and advanced flex-algorithm routing capabilities without requiring separate infrastructure.
2Productivity
If network devices advertise flex-algorithm definitions and associated addresses, then traffic routing using flex-algorithms is enabled, but routing table complexity increases
Solution Approach 1:
The patent segments routing information by introducing separate routing table entries for different flex-algorithm types. Instead of mixing all routing information uniformly, the routing table is organized with distinct entries for segment routing destinations (using segment routing paths) and non-segment-routing destinations (using loopback addresses). This segmentation allows the routing device to efficiently select the appropriate routing method based on the destination type, improving traffic management while keeping the routing table structure manageable through clear separation of concerns.
Data Source
AI summary
In some implementations, a first network device may receive an advertisement from a second network device. The advertisement may be associated with indicating that the second network device is configured to support a particular flex-algorithm. The first network device may identify, in the advertisement, an address of the second network device. The first network device may configure a routing table of the first network device to indicate that the second network device is capable of receiving traffic associated with the particular flex-algorithm based on the address. The first network device may perform, using the routing table, an action associated with routing the traffic associated with the particular flex-algorithm.