Remote Route Injection Server Bypasses IP Network Routing Constraints
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current IP address mobility techniques in IP networks are restrictive due to requirements that nodes must already have routes in their routing tables to advertise them, limiting the injection of IP routes and hindering mobility within the network.
Innovation Solution
A remote and dynamic route injection server (RDRIS) is provisioned as a peer or neighbor node within the IP network, using BGP UPDATE messages to advertise IP routes and bypass conventional route advertisement rules, allowing for the remote and dynamic injection of routes into the network.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If conventional BGP route advertisement rules are used, then routing table consistency is maintained, but IP route injection flexibility is restricted
Solution Approach 1:
The patent introduces a route injection server as an intermediary component that mediates between the need for flexible route injection and the requirement for routing table consistency. This server acts as a trusted authority that can advertise routes to the network without requiring them to pre-exist in local routing tables, thereby enabling flexible IP route injection while maintaining overall network routing consistency through controlled route propagation
Solution Approach 2:
The patent inverts the conventional route advertisement paradigm by allowing route advertisement without requiring the advertising node to have the route in its routing table. Instead of requiring 'route existence before advertisement,' the system enables 'advertisement before route installation,' fundamentally reversing the traditional BGP route injection sequence and enabling dynamic IP mobility
2Adaptability or versatility
If nodes require routes to exist in routing tables before advertising, then routing stability is maintained, but IP address mobility is hindered
Solution Approach 1:
The route injection server serves as a mediator that handles the complexity of dynamic route advertisement, allowing mobile nodes to change IP addresses without requiring complex route table updates at each node. The intermediary manages route propagation centrally, simplifying the advertisement process while enabling IP mobility
Solution Approach 2:
The system performs preliminary route advertisement by the route injection server before the mobile node actually moves or changes IP addresses. This preliminary action prepares the network for upcoming mobility events, allowing routes to be injected in advance and eliminating the requirement for routes to pre-exist in traditional routing tables
3Ease of operation
If synchronous techniques are used for route learning, then route availability is improved, but operational complexity increases
Solution Approach 1:
The patent extracts the synchronization complexity from individual node operations and centralizes it in the route injection server. By removing the need for distributed synchronization between peer nodes and enabling independent route advertisement by the server, the system simplifies operational procedures while maintaining route consistency through centralized control
Data Source
AI summary
Systems and methods are described herein for remotely and dynamically injecting or installing routes into an Internet Protocol (IP) network. In some embodiments, the systems and methods provide a route injection server as a peer or neighbor node with an IP network. The systems and methods then utilize the route injection server (e.g., remote and dynamic route injection server, or RDRIS) to advertise IP routes to other nodes within the IP network. For example, the RDRIS may send UPDATE messages to other nodes within an IP network, such as via the Border Gateway Protocol (BGP) in order to advertise the IP routes to the other nodes of the IP network.