Dynamic Header Binding in SDN Control Protocols
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing network control protocols, such as OpenFlow, are inflexible in supporting new or unassigned header fields, requiring modifications to the protocol specification, which hinders innovation and flexibility in managing network traffic forwarding.
Innovation Solution
The method involves dynamically binding header field identifiers in a network control protocol by sending a binding request to an SDN switch to establish a dynamic header definition, allowing for the use of a first header field identifier to identify the header field in messages, and optionally updating tables to associate the header field with the identifier, enabling the recognition and manipulation of header fields without modifying the protocol specification.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If protocol specification is modified to support new header fields, then support for new header fields is achieved, but protocol complexity and modification requirements increase
Solution Approach 1:
The patent implements dynamic binding of header field identifiers at runtime through binding requests and responses between SDN controller and switches. This allows the system to adapt to new header fields dynamically without requiring static protocol specification modifications, resolving the contradiction between adaptability and protocol complexity.
Solution Approach 2:
The patent changes the binding state from static (defined in protocol specification) to dynamic (established through runtime binding requests). By using binding requests to establish dynamic header definitions, the system can support new header fields without modifying the protocol specification, thus maintaining protocol simplicity while improving adaptability.
2Adaptability or versatility
If protocol specification is modified to add header field identifiers, then new header fields can be recognized, but innovation speed is reduced due to modification requirements
Solution Approach 1:
The patent enables dynamic creation of header field identifiers through binding requests at runtime. This eliminates the time-consuming process of protocol specification modification and standardization reviews, allowing immediate recognition and use of new header fields without waiting for protocol updates.
Solution Approach 2:
The patent allows SDN controllers to pre-define binding requests for new header fields before they are formally standardized. This preliminary action enables early adoption and testing of new header fields without requiring formal protocol specification changes, accelerating innovation while maintaining backward compatibility.
3Device complexity
If static header field identifiers are used, then protocol specification is simple, but flexibility in supporting new header fields is reduced
Solution Approach 1:
The patent introduces dynamic binding mechanisms that operate on top of the static protocol specification. Binding requests allow the system to dynamically associate header fields with identifiers at runtime, maintaining the simplicity of the base protocol while adding flexibility through the dynamic binding layer.
Solution Approach 2:
The patent introduces a binding request/response mechanism as an intermediary layer between the static protocol specification and the need for dynamic header field support. This intermediary allows new header fields to be associated with identifiers without modifying the core protocol specification, preserving simplicity while enabling flexibility.
Data Source
Figure 1~2
Figure 3
Figure 4
AI summary
Header field identifiers can be dynamically bound to header fields in software defined networks via signaling between software defined network(SDN)controllers and switches. Dynamically establishing header binding definitions may allow new header fields to be recognized and manipulated(e.g.,matched,modified,etc.)by SDN switches without having to update the corresponding standard. To achieve this,an SDN controller sends a binding request to an SDN switch to propose that a header field identifier be dynamically associated with a header field type. If the SDN switch acknowledges the binding request,then the header field identifier is used to identify the header field type in messages(e.g.,control messages,etc.)transmitted to the SDN switch.