SDN Middlebox Tracing via Tag Modification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Managing middleboxes in Software Defined Networks (SDNs) is challenging due to difficulties in locating and determining the operation of both virtual and physical middleboxes within service chains, relying heavily on manual efforts and lacking efficient automated detection methods.
Innovation Solution
An improved SDN controller is implemented to configure switches with packet forwarding rules and trace packets, allowing for automated detection of middlebox locations and functions by analyzing modifications made to trace packets as they pass through middleboxes, using a tracing mechanism that sets a default tag value and modifies it according to middlebox functions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Extent of automation
If manual methods are used to locate and determine middlebox operations, then implementation simplicity is maintained, but management efficiency and automation level deteriorate
Solution Approach 1:
The patent introduces tracing packets as intermediary carriers that transport tag information through the service chain. These packets act as mediators between the SDN controller and middleboxes, enabling automated detection without requiring complex modifications to middlebox infrastructure. The tracing packets carry tags that are modified by middleboxes, creating a simple yet effective communication mechanism.
Solution Approach 2:
The patent utilizes tag field modifications as parameter changes to indicate middlebox functions. Instead of complex detection mechanisms, the system changes the tag parameter within tracing packets as they pass through different middleboxes. The SDN controller analyzes these tag parameter changes to automatically determine middlebox locations and functions, simplifying the overall system while achieving high automation.
2Measurement precision
If tracing packets with tag fields are used to detect middlebox locations, then detection precision is improved, but information processing overhead increases
Solution Approach 1:
The patent extracts only the essential tag field information from tracing packets for middlebox detection purposes. Instead of analyzing entire packet contents, the system focuses specifically on the tag field modifications, extracting minimal necessary information to achieve precise location detection. This reduces information overhead while maintaining high detection precision.
Solution Approach 2:
The SDN controller preliminarily configures tracing packets with specific tag values before injection into the network. This preliminary action allows the controller to predict expected tag states and efficiently compare them with actual received packets, reducing the need for extensive information processing during detection while maintaining precise location identification.
3Productivity
If multiple middleboxes are traced simultaneously, then productivity is improved, but system complexity and resource consumption increase
Solution Approach 1:
The patent creates a universal tracing mechanism where a single tracing packet template with configurable tags can detect multiple different middlebox types. The same basic packet structure and tag modification approach works for firewalls, IDS, proxies, and other middleboxes. This multi-functionality allows simultaneous tracing of multiple middleboxes without requiring separate complex detection systems for each type.
Solution Approach 2:
The system employs periodic injection of tracing packets at controlled intervals to trace multiple middleboxes simultaneously. Rather than continuous monitoring, the periodic action allows the SDN controller to manage multiple trace operations in a structured manner, reducing resource consumption and system complexity while maintaining high detection productivity through efficient time-multiplexed operation.
Data Source
AI summary
At an SDN controller executing using a processor and a memory, a tracing packet is configured with a default value in a tag field. The tracing packet is inserted from the SDN controller into the SDN at a switch in the SDN. A returned packet and a port identifier is received at the controller, from the switch, the returned packet including a modified content in a location of the tracing packet that is different from the tag field. The port identifier corresponds to a port of the switch on which the switch received the returned packet from an middlebox. A function of the middlebox is identified by analyzing a modification applied to the modified content by the middlebox. The function of the middlebox and a location of the middlebox in the SDN are saved. The location includes the port identifier and an identifier of the switch.