OpenFlow Controller Dynamic Flow Table Updates
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In networks with mixed vendor devices, managing access control lists for strict data transfer control is complicated, especially when network managers do not understand the specific configuration, and integrating Open Flow devices with conventional devices adds to the complexity.
Innovation Solution
A data transferring system with an Open Flow Controller that sets and updates tentative flow tables based on route information, allowing for strict white-listed control without requiring specific knowledge of the network configuration, using a setter to create and an updater to modify flow tables dynamically.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a conventional network device uses vendor-specific commands to set access control lists, then the transferring control can be strictly performed, but the management becomes complicated and it is difficult to perform timely control in mixed vendor environments
Solution Approach 1:
The patent applies universality by creating a vendor-neutral configuration method that works across different network device types. The flow table configuration approach using standardized protocols (OpenFlow, NETCONF, RESTCONF) allows the same control logic to be applied universally across mixed vendor devices, eliminating the need for vendor-specific command sequences while maintaining strict transfer control.
Solution Approach 2:
The patent introduces an intermediary controller that mediates between the management system and network devices. This controller translates high-level flow table configurations into device-specific actions, simplifying management by providing a unified interface while maintaining the ability to enforce strict control policies across heterogeneous devices.
2Ease of operation
If Open Flow technology is used to simplify management with uniform protocols, then mixed vendor devices can be managed easier, but the flow table cannot be created without preliminary understanding of specific network configuration
Solution Approach 1:
The patent applies preliminary action by pre-configuring flow tables with placeholder entries that direct traffic to the controller before route information is available. This allows the system to start with simplified configurations and automatically update flow tables once the controller learns the actual network topology through packet inspection and route discovery mechanisms.
Solution Approach 2:
The patent implements feedback mechanisms where the controller continuously monitors network traffic and automatically updates flow table configurations based on discovered route information. This closed-loop approach allows the system to adapt to the actual network configuration dynamically, eliminating the need for manual preliminary configuration knowledge while maintaining ease of operation.
3Adaptability or versatility
If conventional network devices and Open Flow devices are mixed in the network, then network flexibility is improved, but the management becomes further complicated due to different management requirements
Solution Approach 1:
The patent applies segmentation by separating control plane functions from data plane operations. The controller handles high-level policy management and flow table configuration for both conventional and OpenFlow devices, while the devices themselves focus on packet forwarding. This segmentation allows mixed vendor devices to coexist under unified management without requiring complex device-specific management procedures.
Solution Approach 2:
The patent creates a universal management architecture that can handle both conventional ACL-based devices and OpenFlow-based devices through standardized protocols. The controller translates unified flow table configurations into appropriate device-specific formats, allowing flexible mixing of vendor devices while maintaining simplified management through a single management interface.
Data Source
AI summary
A data transferring system includes a switch and a controller. The switch transfers data from a transmission source to a transmission destination with reference to a table in which a first information and a second information are associated. The controller includes a setter configured to set a tentative table to the switch, the tentative table storing the second information for outputting data, which is matched with the condition represented by the first information, to the controller, an obtainer configured to obtain a route information representing a route between the transmission source and the transmission destination, and an updater configured to update the tentative table to a table in which an outputting destination of data, which is matched with the condition represented by the first information, is changed in accordance with the route information.