Adaptive Tunneling Protocol for Network Virtualization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing tunnel protocols in network virtualization are inflexible and quickly become obsolete due to changing control plane implementations and advancements, failing to efficiently adapt to evolving metadata requirements across software and hardware components.
Innovation Solution
The Next Generation Encapsulation (NGE) protocol introduces a variable length header that allows for adaptive specification of zero or more logical context tags, using a Type-Length-Value format to embed rich logical context data, enabling flexible encapsulation of data packets and supporting evolving control plane needs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a fixed length header is used to specify a particular logical context tag, then the protocol structure is simple and easy to implement, but the protocol becomes inflexible and quickly obsolete when control plane implementations change
Solution Approach 1:
The header structure transitions from a static fixed-length format to a dynamic variable-length format. The NGE header includes a base portion with fixed fields and an optional portion that can be dynamically added or removed based on the specific control plane implementation requirements, allowing the protocol to adapt to changing needs without fundamental redesign
Solution Approach 2:
The header is segmented into distinct functional portions: a base header portion containing essential fields (version, type, length, critical option, control flags) and an optional portion that can be divided into multiple logical context tags. This segmentation allows flexible composition of header content while maintaining a consistent structural framework
2Adaptability or versatility
If a variable length header with multiple logical context tags is used, then the protocol can adapt to evolving control plane needs, but the header processing complexity increases
Solution Approach 1:
The length field acts as an intermediary that mediates between the variable number of logical context tags and the fixed-size buffer allocation. By storing the total length of the optional portion in this intermediary field, the system can efficiently manage variable content without requiring complex dynamic memory operations at each processing stage
Solution Approach 2:
The protocol uses parameter changes in the header fields to convey different meanings and functions. The type field identifies the specific logical context tag format, the length field controls the size of the optional portion, and the critical option and control flags modify processing behavior, allowing a single variable-length structure to serve multiple evolving requirements
3Adaptability or versatility
If existing tunnel protocols are used, then implementation is straightforward with fixed structures, but they fail to efficiently adapt to changing metadata requirements across software and hardware components
Solution Approach 1:
The NGE protocol creates a universal header structure that can serve multiple control plane implementations and metadata requirements. The base header provides universal functionality while the optional portion with multiple logical context tags allows customization for specific hardware or software component needs, making the protocol universally applicable yet highly adaptable
Data Source
AI summary
Some embodiments of the invention provide a novel method of tunneling data packets. The method establishes a tunnel between a first forwarding element and a second forwarding element. For each data packet directed to the second forwarding element from the first forwarding element, the method encapsulates the data packet with a header that includes a tunnel option. The method then sends the data packet from the first forwarding element to the second forwarding element through the established tunnel. In some embodiments, the data packet is encapsulated using a protocol that is adapted to change with different control plane implementations and the implementations' varying needs for metadata.