Router Flow Modification with Shared Context
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current Internet routing protocols struggle to efficiently route packets between private networks with overlapping IP address spaces, and they lack the capability to meet emerging requirements such as dynamic private-network connections, service-specific Quality of Service, authenticated directional routing, and integrated Deep Packet Inspection (DPI) and flow analytics, necessitating complex architectures with middleboxes and overlay networking.
Innovation Solution
Implement a method in routers to establish and modify flows dynamically based on conditions, allowing for stateful routing by deactivating existing flows and establishing new ones, and utilizing a service path for special packet processing, including shared context information and action chains to manage packet forwarding.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If current Internet routing protocols are used to forward packets between private networks with overlapping IP address spaces, then packet forwarding can be performed, but routing efficiency deteriorates and complex architectures with middleboxes and overlay networking are required
Solution Approach 1:
The patent segments the network architecture by introducing a control plane that separates routing control from data forwarding. The control plane establishes flows and manages context information, while the data plane efficiently forwards packets using established flows. This segmentation eliminates the need for complex middleboxes and overlay networking, directly resolving the contradiction between routing efficiency and architectural complexity.
Solution Approach 2:
The control plane performs preliminary actions by pre-establishing flows and storing context information about packet sequences between network elements. This preliminary setup enables the data plane to efficiently forward subsequent packets without requiring complex real-time routing decisions, thereby improving productivity while maintaining simple architecture.
2Ease of operation
If stateless IP routing is used, then simple forwarding based on destination address is possible, but session continuity and stateful routing capabilities are lost
Solution Approach 1:
The patent introduces a control plane as an intermediary between the simple forwarding mechanism and session continuity requirements. The control plane maintains flow context information that enables stateful routing decisions, while the data plane continues to operate with simple forwarding rules. This intermediary layer provides session continuity without compromising forwarding simplicity, resolving the contradiction between ease of operation and reliability.
3Adaptability or versatility
If flows are modified dynamically in response to network conditions, then network adaptability is improved, but flow management complexity increases
Solution Approach 1:
The patent implements dynamic flow modification where the control plane can deactivate existing flows and establish new flows in response to changing network conditions. This dynamic approach improves network adaptability by allowing flows to be adjusted based on current state, while the automated control plane manages the complexity of flow transitions, preventing manual management overhead.
Solution Approach 2:
The system incorporates feedback mechanisms where the control plane monitors network conditions and packet flows, then adjusts flow configurations accordingly. This feedback loop enables automatic adaptation to network changes without manual intervention, improving versatility while the automated nature of the feedback process prevents complexity from escalating.
Data Source
Figure 1~2
Figure 3
Figure 4
AI summary
Routing packets by a router involves establishing a first flow configured for forwarding the packets from a first ingress interface to a first egress interface of the router; determining a condition to modify the first flow; deactivating the first flow; establishing a second flow configured for forwarding the packets from at least one of (1) the first ingress interface to a second egress interface, (2) a second ingress interface to the first egress interface, or (3) a second ingress interface to a second egress interface; and activating the second flow.