FlowSense Network Manager for OpenFlow Rule Translation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing solutions for managing software-defined networks, particularly those using OpenFlow, are complex and not suited for applications with high-level requirements, as they disconnect the simple interface applications need from the low-level characteristics required by the OpenFlow protocol, making it difficult for distributed applications to interact effectively with the network.
Innovation Solution
FlowSense, a network manager that interacts with applications using a simple API, translates requests into OpenFlow rules, and optimizes rule installation on switches by sensing network topology and utilization, using a sensing module, decision engine, and rule engine to provide a scalable and expressive interface for managing OpenFlow networks.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If OpenFlow protocol is used for network control, then fine-grained control over the network is achieved, but the complexity of interaction increases and simple interfaces needed by applications are lost
Solution Approach 1:
The patent introduces a controller as an intermediary layer between applications and OpenFlow switches. The controller translates high-level application requests into low-level OpenFlow commands, shielding applications from protocol complexity while enabling fine-grained network control. This mediator architecture resolves the contradiction by providing both adaptability to applications and detailed control capability.
Solution Approach 2:
The system segments network control functions into distinct layers: application layer for high-level policies, controller layer for translation and coordination, and switch layer for execution. This segmentation allows each layer to operate independently with appropriate complexity, enabling simple application interfaces while maintaining detailed control capabilities at lower layers.
2Ease of operation
If high-level programming languages are built on top of OpenFlow, then packet-forwarding policies can be expressed more easily, but the complexity of synchronizing rules from different applications increases
Solution Approach 1:
The controller implements a universal rule management system that handles multiple applications through a common interface and centralized rule repository. This universal approach allows different applications to express policies using consistent high-level constructs while the controller manages rule synchronization, conflict resolution, and coordination across all applications, reducing the complexity of inter-application rule management.
3Reliability
If the controller maintains updated network state information, then accurate path setup decisions can be made, but the overhead of continual sensing and processing increases
Solution Approach 1:
The controller implements periodic sensing and state updates at optimized intervals rather than continuous monitoring. This periodic approach maintains reliable network state information for accurate path setup decisions while reducing processing overhead and energy consumption compared to continuous sensing. The controller adjusts sensing frequency based on network dynamics and requirements.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A method implemented in a network apparatus used in a network is disclosed. The method includes sensing network topology and network utilization, receiving a request from an application, deciding path setup requirement using network state information obtained from the network topology and the network utilization, and translating the path setup requirement into a rule to be installed. Other methods, apparatuses, and systems also are disclosed.