SDN Route Prioritization in Switch Routing Tables
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional SDN technologies lack the flexibility to prioritize and override traditional routing protocols, limiting their ability to seamlessly integrate with existing network infrastructure and routing algorithms.
Innovation Solution
Implementing a system where SDN routes are classified and prioritized within the Routing Information Base (RIB) of network switches, allowing them to override traditional routes learned via protocols like RIP, OSPF, and BGP, by using an SDN controller that determines and sends SDN routes to switches, which store and indicate these routes as distinct from traditional configurations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Speed
If SDN routes are programmed into the FIB using OpenFlow layer 3 forwarding element programming, then fast longest prefix match lookup and data path forwarding are optimized, but the flexibility to learn routes via traditional routing protocols is lost and no method exists to prioritize between traditional and calculated routes
Solution Approach 1:
The routing table is segmented into multiple sections: a first section for storing traditional routes learned via routing protocols and a second section for storing SDN-calculated routes. This segmentation allows both route types to coexist while maintaining fast forwarding for SDN routes through the optimized FIB structure, simultaneously achieving high speed and flexibility.
Solution Approach 2:
The patent introduces an intermediary mechanism where the SDN controller receives flow requests, calculates optimal paths, and programs routes into the FIB. This intermediary role allows traditional routing protocols to continue operating while SDN provides centralized control and prioritization, resolving the conflict between speed optimization and route learning flexibility.
2Extent of automation
If SDN completely replaces traditional routing protocols, then centralized control and programmability are achieved, but migration pains and barriers to adoption increase due to incompatibility with existing infrastructure
Solution Approach 1:
The patent merges traditional routing protocols with SDN control by allowing both to operate simultaneously within the same routing infrastructure. Traditional routes from protocols like OSPF and BGP coexist with SDN-calculated routes in the routing table, enabling gradual migration and reducing barriers to adoption while maintaining centralized control capabilities.
Solution Approach 2:
The system dynamically adapts to different routing scenarios by allowing the routing table to contain both static traditional routes and dynamic SDN-calculated routes. This dynamic structure enables the network to transition smoothly from traditional to SDN-controlled operation, making migration easier while maintaining automation benefits.
3Adaptability or versatility
If traditional routing protocols are used, then route learning and network adaptability are maintained, but the ability to prioritize and override routes for specific applications is limited
Solution Approach 1:
The patent applies local quality by allowing different priority levels for different route types within the routing table. SDN-calculated routes can be marked with higher priority than traditional routes, enabling application-specific prioritization control while maintaining the ability to learn routes through traditional protocols. This resolves the contradiction by providing fine-grained control over route selection.
Data Source
AI summary
In one embodiment, an apparatus includes a memory, a hardware processor, and logic integrated with and/or executable by the processor. The logic is configured to receive one or more software defined network (SDN) routes dictating a path through a network comprising a plurality of devices. The logic is also configured to store the one or more SDN routes to the memory along with one or more traditional routes learned by the apparatus and/or configured by an administrator, and indicate the one or more SDN routes as being of a type different from the traditional routes. Moreover, the logic is configured to receive a priority ordering for a plurality of routes stored in the memory from the SDN controller, the plurality of routes including at least one SDN route, and construct a route information base (RIB) based on the plurality of routes and the priority ordering.