Dual Flow Tables for Priority Conflict Resolution
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing network switching products face challenges in efficiently storing and managing flow entries with varying priorities, leading to potential priority conflicts and inefficient forwarding decisions in dynamic network environments.
Innovation Solution
Implementing a network device with two flow tables, one with fixed priority and another with flexible priority, where the flexible priority table can override and store entries from the fixed priority table, and controllers determine the best placement of flow entries to maintain priority consistency across tables.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If a single flow table with fixed priority is used, then the table structure is simple and easy to manage, but it cannot effectively handle flow entries with varying priorities leading to priority conflicts
Solution Approach 1:
The patent divides a single flow table into two separate flow tables: a first flow table for storing flow entries with fixed priority, and a second flow table for storing flow entries with flexible priority. This segmentation allows each table to handle specific priority requirements independently, resolving the contradiction between structural simplicity and priority consistency by organizing complexity into manageable segments.
2Device complexity
If a single flow table is used, then the device complexity is low, but the ability to manage flow entries with varying priorities is insufficient
Solution Approach 1:
The patent applies local quality by assigning different priority management characteristics to different flow tables. The first flow table is optimized for fixed priority scenarios while the second flow table handles flexible priority requirements. This allows each table to have specialized properties suited to its specific function, improving overall adaptability without requiring all tables to be universally complex.
3Device complexity
If flow entries are stored in a single table, then storage management is simple, but forwarding decisions become inefficient in dynamic network environments
Solution Approach 1:
By segmenting the flow entry storage into two tables with different priority characteristics, the system can make forwarding decisions more efficiently. The controller can determine whether a flow entry can only be stored in the second table and move overlapping entries accordingly, enabling faster and more accurate forwarding decisions in dynamic network environments while maintaining manageable storage complexity.
Data Source
AI summary
A system and method for storing flow entries in hardware tables includes one or more controllers, memory, a first flow table for storing first flow entries, and a second flow table for storing second flow entries that override the first flow entries. The first flow table implements a fixed priority and the second flow table a flexible priority. The one or more controllers is configured to determine whether a third flow entry with a first priority can only be stored in the second flow table. When the third flow entry can only be stored in the second flow table, the one or more controllers is further configured to add the third flow entry to the second flow table and move any first flow entries with priorities higher than the first priority that overlap the third flow entry to the second flow table.