Fractional Router Redundancy via Control Plane Extraction
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In wireless networks, such as WiMax, the redundancy of routers is often limited by the geographic proximity of primary and standby routers, making them vulnerable to natural disasters or power outages, and requiring costly and complex systems for synchronization.
Innovation Solution
The abstraction of the data plane from the control plane allows for decentralized data path management, where a routing device, independent of the control server, performs data routing functions, enabling fractional router redundancy by distributing data routing across multiple, geographically diverse routers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a standby router is located in the same geographic location as the primary router, then synchronization and redundancy are simplified, but the system becomes vulnerable to natural disasters or power outages affecting both routers
Solution Approach 1:
The patent segments the router system into multiple independent routing devices distributed across different geographic locations. Each router operates as an independent unit with its own routing table and control plane, eliminating the dependency between primary and standby routers. This segmentation allows the system to maintain reliability while being geographically dispersed to avoid common failure modes.
Solution Approach 2:
The patent introduces geographic dispersion as a new dimension in the router architecture. Instead of placing standby routers in the same physical location, the system distributes routers across different geographic locations. This dimensional change from spatial proximity to spatial distribution resolves the contradiction by protecting against location-specific failures while maintaining redundancy.
2Reliability
If exact duplicate routers are used for redundancy, then failover capability is ensured, but system complexity and cost increase due to synchronization requirements
Solution Approach 1:
The patent extracts the control plane functions from the data plane routing operations. Each router maintains an independent control plane that independently computes routing tables based on local topology information. This extraction eliminates the need for complex synchronization between primary and standby routers, as each router autonomously performs routing decisions without requiring continuous state synchronization.
Solution Approach 2:
Instead of synchronizing standby routers with the primary router to maintain identical states, the patent inverts the approach by allowing each router to independently compute its own routing table. The failover mechanism works by detecting primary router failure and independently activating standby routers without requiring prior synchronization, thus reducing complexity while maintaining reliability.
3Object-affected harmful factors
If multiple routers are distributed geographically, then vulnerability to localized failures is reduced, but routing complexity and synchronization overhead increase
Solution Approach 1:
Each router performs self-service by independently computing its own routing table based on locally available topology information. The routing protocol enables each router to autonomously detect topology changes and update its routing table without requiring coordination with other routers. This self-service approach simplifies the system despite geographic distribution, as each router manages its own routing decisions independently.
Solution Approach 2:
The patent implements partial synchronization by maintaining only essential routing information locally at each router rather than synchronizing complete router states. Each router keeps a partial view of the network topology sufficient for local routing decisions, eliminating the need for excessive synchronization overhead while still enabling coordinated failover when needed.
Data Source
AI summary
Systems and methods for fractional routing are described. An exemplary method may include receiving, by a first router, data information regarding routing by a first portion of a third router, receiving, by a second router, data information regarding routing by a second portion of a third router, wherein the data information regarding routing by the first portion and data information regarding routing by the second portion is not the same, routing, by the first router, data associated with the routing by the first portion of the third router, and routing by the second router, data associated with the routing by the second portion of the third router.


