Dynamic Forwarding Plane Adaptation for Network Elements
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Network elements often require pre-configured forwarding plane resources that may not be fully utilized, leading to dropped unknown traffic and increased latency, as initial configurations do not account for evolving network needs or new protocols, and static configurations fail to optimize forwarding behavior across the network.
Innovation Solution
Implementing a dynamic forwarding plane that allows network elements to automatically add or remove features based on actual traffic patterns by sending packet information to a network controller, which selects and downloads necessary packet handling modules, enabling flexible and optimized forwarding behavior without restarting the forwarding instance.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If network elements use pre-configured static forwarding plane resources, then device complexity is reduced and ease of operation is improved, but adaptability to new protocols and traffic patterns deteriorates and resource utilization efficiency worsens
Solution Approach 1:
The forwarding plane transitions from a static pre-configured state to a dynamic state where features are automatically added or removed based on actual traffic patterns. The network element continuously monitors traffic and adjusts its forwarding capabilities in real-time, allowing adaptation to new protocols and optimization of resource utilization without requiring manual reconfiguration.
Solution Approach 2:
The network element autonomously detects unknown traffic types and automatically requests and installs appropriate packet handling modules without human intervention. The system self-manages its forwarding plane configuration by monitoring its own traffic patterns and independently making decisions about feature installation, eliminating the need for manual planning and configuration.
2Adaptability or versatility
If network elements pre-configure all possible packet handling features, then adaptability to various protocols is improved, but resource utilization efficiency deteriorates and device complexity increases
Solution Approach 1:
Instead of maintaining all possible packet handling features statically, the forwarding plane dynamically installs and removes features based on actual traffic demands. This allows the system to have high adaptability when needed while maintaining efficient resource utilization by only activating features that are currently required by the traffic flow.
Solution Approach 2:
The network element is designed with a universal architecture that can handle multiple protocol types through a common framework. Rather than dedicating specific resources to each protocol, a single multi-functional forwarding plane can be dynamically configured to handle different protocols as traffic patterns require, improving both adaptability and resource efficiency.
3Device complexity
If network elements use static forwarding plane configuration, then device complexity is reduced, but latency increases when handling unknown traffic types
Solution Approach 1:
The system performs preliminary monitoring of traffic patterns and proactively installs packet handling modules before they are absolutely necessary. By detecting emerging traffic types early and pre-installing the required handling capabilities, the system minimizes latency for unknown traffic while maintaining a relatively simple base forwarding plane configuration.
Solution Approach 2:
The forwarding plane implements a feedback mechanism where traffic patterns are continuously monitored and analyzed. When unknown traffic types are detected, the system automatically triggers the installation of appropriate packet handling modules. This closed-loop feedback system reduces latency by ensuring that handling capabilities are installed quickly in response to actual traffic needs while keeping the base configuration simple.
Data Source
AI summary
A network element dynamically adjusts the forwarding plane based on a received packet. The network element receives a packet that is formatted according to a packet type. The network element determines whether the network element is configured to process the packet type. Responsive to a determination that that network element is not configured to process the packet type, the network element sends packet information to a network controller. The network element receives at least one packet handling module that includes instructions for processing the packet type of the received packet. Installing the at least one packet handling module on the network element configures the network element to process the packet type. The network element processes the packet according to the instructions in the at least one packet handling module.