Unified SDN Header for OpenFlow Packet Encapsulation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current OpenFlow technologies face challenges in efficiently routing and encapsulating data flows across software-defined networks (SDNs) due to the lack of a unified header that can support multiple network abstraction types, leading to inefficiencies in forwarding data packets across different network routing schemes.
Innovation Solution
The extension of the OpenFlow protocol to include a unified SDN header that facilitates data flow routing by defining match fields, masks, and actions, allowing network elements to perform specific actions based on the header, enabling the encapsulation and decapsulation of data flows across various network types such as MPLS, IP, and MAC protocols.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a unified SDN header is introduced to support multiple network abstraction types, then adaptability and versatility are improved, but device complexity increases
Solution Approach 1:
The patent applies universality by designing a unified SDN header structure that can accommodate multiple network abstraction types (MPLS, IP, MAC protocols) within a single protocol framework. This multi-functional header enables the same OpenFlow extension to handle diverse data flow types without requiring separate handling mechanisms for each network abstraction, thereby improving adaptability while managing complexity through standardization.
2Productivity
If packet encapsulation is implemented for transport over SDN, then productivity is improved, but device complexity increases
Solution Approach 1:
The patent applies segmentation by dividing the packet processing function into distinct components: the unified SDN header contains specific fields for match information, mask values, and action instructions. This segmentation allows network elements to process different aspects of packet routing independently - matching fields for routing decisions, masks for selective matching, and actions for specific operations - thereby improving routing efficiency while managing complexity through functional decomposition.
3Measurement precision
If match fields and masks are added to OpenFlow instructions, then measurement precision is improved, but device complexity increases
Solution Approach 1:
The patent applies local quality by introducing mask values that can be selectively applied to specific match fields based on the network abstraction type and routing requirements. Rather than requiring all fields to be treated uniformly, the mask mechanism allows precise control over which fields require exact matching and which allow partial matching, thereby improving measurement precision for different data flow types while managing instruction structure complexity through conditional application.
Data Source
AI summary
A method for controlling a data flow in a domain of an OpenFlow protocol controlled software-defined network (SDN) comprising receiving a request from a network element for instructions to route the data flow through the OpenFlow SDN, determining a route for the data flow through the OpenFlow SDN, transmitting a unified header to the network element in the OpenFlow SDN, wherein the unified header facilitates transmission of data flows through the OpenFlow SDN that are encoded according to a plurality of network abstraction types, and transmitting instructions for forwarding the data flow along the route through the OpenFlow SDN, wherein the instructions for forwarding the data flow along the route through the OpenFlow SDN comprise one or more match fields, one or more mask values corresponding to the match fields, and one or more actions for the network element in the OpenFlow SDN to perform on the data flow.