Flow-Based Switching Device Data Plane Segmentation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current information handling systems face challenges in efficiently processing and routing data packets, particularly in handling flow-based traffic, as they often rely on packet-based routing methods that are not adaptable to the specific needs of applications and users, leading to inefficiencies and scalability issues.

Innovation Solution

The implementation of a flow-based switching device with a split data plane comprising a macroflow sub-plane for packet-based routing and a microflow sub-plane for flow-based routing, along with a software-defined network controller for remote management and visibility, allows for adaptable and scalable handling of data packets by distinguishing between packet-based and flow-based routing rules.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If packet-based routing methods are used, then routing simplicity is maintained, but adaptability to application-specific needs deteriorates

Engineering Contradiction:
Improveadaptability to application needsVSAvoidrouting mechanism complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The data plane is segmented into two distinct sub-planes: a packet-based sub-plane for general routing and a flow-based sub-plane for application-specific routing. This segmentation allows each sub-plane to handle different routing requirements independently, improving adaptability while managing complexity through functional separation.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The flow-based switching device is designed to perform multiple routing functions simultaneously - both packet-based routing for general traffic and flow-based routing for application-specific needs. The controller can programmatically select which routing method to apply based on traffic characteristics, making the system universally adaptable to different network requirements.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If flow-based routing is implemented, then adaptability to user traffic patterns improves, but device complexity increases

Engineering Contradiction:
Improvehandling of flow-based trafficVSAvoiddata plane structure complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The data plane is divided into macroflow sub-plane and microflow sub-plane, each handling different aspects of flow-based routing. The macroflow sub-plane manages broader flow classifications while the microflow sub-plane handles detailed packet routing, reducing overall complexity through hierarchical organization.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The controller acts as an intermediary between the flow-based routing decisions and the data plane execution. It receives flow information, processes routing decisions, and programs the appropriate sub-planes, simplifying the overall system architecture by centralizing the complex decision-making logic.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Productivity

If packet-based routing is used, then routing speed is maintained, but scalability for application-specific flows deteriorates

Engineering Contradiction:
Improverouting speedVSAvoidscalability for application flows
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

By segmenting the data plane into packet-based and flow-based sub-planes, the system can simultaneously maintain high-speed packet routing for general traffic while adding flow-based routing capabilities for application-specific needs without compromising the performance of either path.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system dynamically selects between packet-based and flow-based routing methods based on traffic characteristics and application requirements. This dynamic adaptability allows the system to optimize routing speed for each specific traffic type while maintaining scalability across different application scenarios.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS9509597B2System and method for dataplane extensibility in a flow-based switching device
Publication Date: 2016.11.29 DELL SOFTWARE INC
  • US9509597B2 patent drawing
  • US9509597B2 patent drawing
  • US9509597B2 patent drawing

AI summary

A network switching device includes a macroflow sub-plane that performs packet-based routing, a microflow routing module that performs flow-based routing, and a software defined network (SDN) agent. The microflow routing module includes a packet processing module and a virtual port, and is operable to determine that the packet processing module is to be utilized to process a flow, direct the flow to the packet processing module via the virtual port in response to determine that the packet processing module is to be utilized to process the flow, process the flow using the packet processing module, and direct the flow to a destination associated with the flow. The SDN agent sends a port status message to a SDN controller indicating that the microflow routing module includes the virtual port and that the virtual port is associated with the packet processing module.