OpenFlow Instance Configuration for Wireless APs

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

The implementation of OpenFlow multi-instances on wireless devices is complicated due to frequent changes in wireless virtual interfaces, leading to configuration oscillation and increased workload for the OpenFlow controller.

Innovation Solution

Assigning a dedicated OpenFlow instance to each Access Point (AP) and binding the wireless virtual interface to that instance, allowing the OpenFlow controller to manage instances without re-configuration when the wireless virtual interface changes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If the OpenFlow standard is applied to a wireless network and instances are configured for wireless virtual interfaces, then the control plane can be separated from the data plane, but configuration oscillation occurs and workload increases when terminals frequently connect and disconnect

Engineering Contradiction:

ImproveOpenFlow multi-instance configuration capabilityVSAvoidConfiguration complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the OpenFlow instance configuration by creating a dedicated binding relationship between AP identifiers and OpenFlow instances. This segmentation allows the system to handle multiple APs and their respective wireless virtual interfaces through distinct, pre-configured instances, thereby reducing configuration complexity while maintaining adaptability.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent implements preliminary action by pre-binding AP identifiers to OpenFlow instances before the actual wireless virtual interface is created. This advance configuration ensures that when terminals connect or disconnect, the OpenFlow controller can directly use the pre-established binding without performing complex re-configuration operations, thus eliminating configuration oscillation and reducing workload.

Inventive Principle:

Principle #10Preliminary action

2Adaptability or versatility

If instances are re-configured when wireless virtual interfaces change, then the system adapts to terminal connections and disconnections, but configuration oscillation and increased workload occur

Engineering Contradiction:

ImproveAdaptation to terminal connection changesVSAvoidConfiguration time

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by establishing the binding relationship between AP identifiers and OpenFlow instances in advance, before any terminal connection events occur. This pre-configuration means that when terminals connect or disconnect, the system can directly utilize the existing binding without time-consuming re-configuration operations, thus maintaining adaptability while minimizing configuration time and avoiding oscillation.

Inventive Principle:

Principle #10Preliminary action

3Adaptability or versatility

If the AP creates wireless virtual interfaces for each terminal, then individual terminal management is achieved, but frequent interface changes cause configuration oscillation

Engineering Contradiction:

ImproveIndividual terminal management capabilityVSAvoidConfiguration stability

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The patent segments the configuration management by creating a stable binding layer between AP identifiers and OpenFlow instances, separate from the dynamic wireless virtual interfaces. This segmentation isolates the configuration stability from interface changes, allowing individual terminal management through wireless virtual interfaces while maintaining configuration reliability through the unchanged AP identifier bindings.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary binding relationship between AP identifiers and OpenFlow instances that acts as a stable mediator. This intermediary layer decouples the dynamic wireless virtual interfaces from the static configuration, allowing terminal-specific management while preventing configuration oscillation from propagating to the OpenFlow controller.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentEP3833084B1Openflow instance configuration

Publication Date: 2024.02.28 NEW H3C TECH CO LTD

Figure 1~2
Figure 3~4
Figure 5~6

AI summary

An AC obtains configuration information of a global instance and configuration information of an AP instance corresponding to each AP. The AC sends the configuration information of a corresponding AP instance to each AP respectively, so that each AP creates an AP instance based on the received configuration information of the AP instance, and binds an AP identifier to the created AP instance. The AC creates the global instance based on the configuration information of the global instance. The AC binds an AC identifier and an AP identifier of each AP to the global instance.