OpenFlow Hybrid Network Device Architecture for Dynamic Traffic Adaptation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing network switch architectures struggle to adapt to dynamic traffic patterns and bandwidth demands due to their static, hierarchical structure, especially with the rise of virtualization, cloud computing, and mobile devices, making effective management of data communication networks challenging.
Innovation Solution
A hybrid network device architecture that integrates OpenFlow functionality with conventional networking components, allowing for a separation of control and data forwarding planes, enabling sophisticated traffic management while leveraging existing switch functionality by using a control plane for control protocol packets and multiple forwarding planes for packet processing with flow tables configured by an external controller.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a static, hierarchical network switch architecture is used, then the structure is simple and stable, but it cannot adapt to dynamic traffic patterns and bandwidth demands
Solution Approach 1:
The network device is segmented into multiple forwarding planes (first forwarding plane, second forwarding plane, third forwarding plane) with distinct functions. The first forwarding plane handles ingress packets, the second handles packet processing with flow tables, and the third handles egress packets. This segmentation allows each plane to be optimized for its specific function while collectively providing adaptability to dynamic traffic patterns without requiring complete architectural redesign.
Solution Approach 2:
The patent implements dynamic adaptability through the control plane's ability to programmatically configure flow tables in the second forwarding plane. The control plane can dynamically adjust flow entries, match fields, and packet processing rules based on real-time traffic patterns and bandwidth demands, enabling the architecture to adapt dynamically without physical reconfiguration.
2Adaptability or versatility
If OpenFlow architecture is implemented, then sophisticated traffic management is enabled, but existing switch functionality cannot be leveraged and distributed algorithms must be re-implemented
Solution Approach 1:
The patent merges OpenFlow functionality with conventional networking components in a hybrid architecture. The first and third forwarding planes use conventional switching mechanisms, while the second forwarding plane implements OpenFlow flow tables. This merging allows the system to leverage existing switch functionality for basic forwarding while incorporating OpenFlow for sophisticated traffic management, avoiding complete re-implementation of distributed algorithms.
Solution Approach 2:
The control plane serves multiple functions: it manages OpenFlow flow tables, configures packet processing rules, and coordinates between conventional and OpenFlow forwarding planes. This multi-functional control plane enables both traditional switching operations and SDN-based traffic management through a single unified controller, reducing the need for separate distributed algorithm implementations.
3Productivity
If multiple forwarding planes are used, then packet processing capability is enhanced, but the device complexity increases
Solution Approach 1:
The forwarding functionality is segmented into three specialized planes: ingress handling, packet processing, and egress handling. Each plane contains specific components optimized for its function, such as the first forwarding plane for receiving and initial processing, the second for flow table-based processing, and the third for transmission. This segmentation enhances packet processing capability by distributing workload across specialized units while maintaining manageable complexity through clear functional boundaries.
Data Source
AI summary
A method, system and apparatus for an OpenFlow hybrid architecture network device. In one embodiment, a hybrid approach is enabled by a network device that brackets an OpenFlow forwarding plane with conventional forwarding planes. Interfaces between the OpenFlow forwarding plane is provided via logical ports that pass packets along with associated metadata.