OpenFlow Switch Flow Table Insertion via Cookie Field

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

The existing OpenFlow protocol does not directly support specifying into which flow table an OpenFlow flow entry should be inserted, hindering the effective management of software-defined networks (SDNs) when transitioning from traditional network architectures.

Innovation Solution

A method is introduced to receive a flow mod message at an OpenFlow-enabled switch, decode the OpenFlow flow entry, and identify the appropriate flow table using the cookie field, allowing for the insertion of the flow entry into either a system flow table or a service flow table.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If Hybrid OpenFlow switches are introduced to facilitate communication between traditional network switches and SDN switches, then communication compatibility is improved, but the ability to manage traditional network switch functionality using OpenFlow protocol deteriorates

Engineering Contradiction:

Improvecommunication compatibilityVSAvoidmanageability of traditional network switch functionality

Core Design Contradiction:

Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent introduces a flow table identification mechanism that acts as an intermediary layer between the OpenFlow protocol and traditional network switch functionality. By embedding flow table identifiers within the protocol messages and using cookie fields to map to specific flow tables, the system enables OpenFlow controllers to manage traditional network switches through a standardized interface, thus resolving the manageability issue while maintaining communication compatibility

Inventive Principle:

Principle #24Intermediary (Mediator)

2Extent of automation

If the OpenFlow protocol is used to manage flow entries, then centralized control and flexibility are improved, but the capability to specify insertion of flow entries into specific flow tables deteriorates

Engineering Contradiction:

Improvecentralized controlVSAvoidflow entry insertion capability

Core Design Contradiction:

Extent of automationVSEase of operation

Solution Approach 1:

The patent segments the flow table management by introducing distinct flow table identifiers (e.g., system flow table vs. service flow table) that can be specified within the OpenFlow protocol messages. This segmentation allows the centralized controller to precisely direct flow entry insertion to the appropriate flow table, thereby maintaining centralized control while enhancing the flow entry insertion capability through structured identification

Inventive Principle:

Principle #1Segmentation

3Adaptability or versatility

If traditional network architectures are replaced with SDN architectures, then switching flexibility is improved, but adoption cost and complexity increase

Engineering Contradiction:

Improveswitching flexibilityVSAvoidadoption complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a universal flow table identification mechanism that works across both traditional network switches and SDN switches through the Hybrid OpenFlow architecture. By using standardized cookie fields and flow table identifiers that can represent multiple flow table types (system, service, etc.), the system provides multi-functional management capability that reduces adoption complexity while maintaining switching flexibility across heterogeneous network environments

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS9660904B2Method and system for inserting an openflow flow entry into a flow table using openflow protocol

Publication Date: 2017.05.23 ALCATEL LUCENT SA

AI summary

A method for inserting an OpenFlow flow entry into a flow table is disclosed. In the embodiment, the method involves receiving a flow mod message at an OpenFlow-enabled switch, the flow mod message including a cookie field, decoding an OpenFlow flow entry from the flow mod message, identifying a flow table from the cookie field, and inserting the decoded flow entry into the flow table.