SDN Switch Static Flow Reporting to Controller

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Static flows programmed by a switch administrator in software-defined networks (SDNs) are not reported to the SDN controller, limiting the controller's visibility and control over network traffic, especially during controller connection failures.

Innovation Solution

A mechanism is implemented in network switches to create and send messages to the SDN controller indicating the addition, modification, or deletion of static flows, using a SDN-formatted structure, ensuring the controller is aware of all flows and can manage them effectively, even when connectivity is interrupted.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If static flows are programmed by switch administrator without reporting to SDN controller, then switch can independently manage flows, but SDN controller loses visibility and control over network traffic

Engineering Contradiction:
Improveindependent flow managementVSAvoidcontroller visibility
Core Design Contradiction:
Ease of operationVSLoss of information

Solution Approach 1:

The switch implements a feedback mechanism by sending notifications to the SDN controller whenever static flows are added, modified, or deleted. This allows the controller to maintain visibility and control over network traffic while the switch retains independent flow management capabilities through CLI-configured static flows.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent combines two previously separate flow management approaches: traditional CLI-configured static flows and SDN controller-managed dynamic flows. By merging these systems and implementing notification mechanisms, the switch can handle both types of flows while maintaining controller visibility, resolving the contradiction between independent operation and centralized control.

Inventive Principle:
Principle #5Merging (Combining)

2Device complexity

If static flows are not reported to SDN controller, then switch maintains simpler operation, but network security control is compromised

Engineering Contradiction:
Improveswitch operation simplicityVSAvoidsecurity control
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The notification mechanism provides feedback to the SDN controller about static flow changes, enabling security policies to be enforced without complicating switch operation. The controller can identify security violations and delete unwanted flows based on notifications received from the switch.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The notification system acts as an intermediary between the switch's static flow management and the SDN controller's security control functions. This intermediary mechanism allows the controller to maintain security oversight without directly interfering with the switch's simple operation or requiring complex changes to the switching fabric.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If static flows are programmed locally without notification, then switch can operate autonomously, but traffic loss increases during controller connection failures

Engineering Contradiction:
Improveautonomous operationVSAvoidtraffic loss
Core Design Contradiction:
Adaptability or versatilityVSLoss of energy

Solution Approach 1:

The switch performs preliminary actions by sending notifications to the controller about static flow changes before controller connection failures can occur. This ensures the controller has up-to-date information about network flows, enabling faster recovery and reduced traffic loss when connection failures happen.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

By implementing feedback notifications about static flow changes, the system ensures the controller maintains an accurate view of network state. This reduces traffic loss during controller connection failures because the controller can quickly resume control with accurate flow information when connectivity is restored.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS9692689B2Reporting static flows to a switch controller in a software-defined network (SDN)
Publication Date: 2017.06.27 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US9692689B2 patent drawing
  • US9692689B2 patent drawing
  • US9692689B2 patent drawing

AI summary

In one embodiment, a system includes a switch that has a processor and logic integrated with and/or executable by the processor, the logic being configured to create a message indicating addition, modification, or deletion of a static flow in a software defined network (SDN), wherein the static flow includes the switch and at least one other device in the SDN, and send the message to a SDN controller in a SDN-formatted structure. In another embodiment, a method includes creating a message, using a switch, indicating addition, modification, or deletion of a static flow in a SDN, wherein the static flow includes the switch and at least one other device in the SDN, and sending the message to a SDN controller in a SDN-formatted structure. Other systems and methods for reporting static flows to a SDN controller in a SDN are described according to more embodiments.