Flow-Driven Forwarding for Information-Centric Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current information-centric networking (ICN) forwarding solutions are not optimized to efficiently handle flow-based traffic, leading to high processing overhead during forwarding lookups, which limits achieving targeted transmission rates, especially for high-speed applications like 100+ Gbps content routers.
Innovation Solution
A flow-driven forwarding strategy is implemented, where Interest packets include a flow state indicator flag, allowing for the extraction of forwarding information from a flow state table or the Interest packet, reducing the need for costly lookups and leveraging previous forwarding metrics to speed up packet processing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If conventional ICN forwarding lookup methods are used, then forwarding accuracy is maintained, but processing overhead is high and transmission rate is limited
Solution Approach 1:
The patent performs preliminary actions by checking content locality and creating flow state entries before actual forwarding decisions are made. The flow state table is pre-populated with forwarding information, allowing subsequent packets in the same flow to bypass expensive longest prefix matching lookups and directly use the pre-computed forwarding paths.
Solution Approach 2:
The patent introduces dynamic flow state management where the forwarding behavior adapts based on packet flow characteristics. The system dynamically creates, updates, and removes flow state entries in the flow state table based on incoming Interest packets, allowing the forwarding mechanism to transition between detailed LPM lookup and simplified flow-based forwarding.
2Productivity
If each Interest packet is treated as a separate entity with independent lookup, then forwarding accuracy is ensured, but processing efficiency decreases
Solution Approach 1:
The patent merges multiple independent forwarding decisions into a unified flow state entry. By combining packets belonging to the same flow into a single flow state record, the system performs one lookup to establish the flow state, then reuses that information for all subsequent packets in the flow, rather than performing separate lookups for each packet.
Solution Approach 2:
The patent creates simplified copies of forwarding information in the flow state table that can be quickly referenced. Instead of repeatedly performing complex LPM lookups, the system copies essential forwarding data into the flow state entry during the first packet of a flow, then uses this copied information for rapid subsequent forwarding decisions.
3Speed
If flow state table is used for active flows, then lookup speed is improved, but memory usage increases
Solution Approach 1:
The patent extracts only the essential forwarding information needed for active flows into the flow state table, rather than storing complete routing tables or all possible forwarding paths. The flow state entries contain minimal necessary data (forwarding interface, hop count, flow identifier) to enable fast forwarding decisions, reducing memory consumption while maintaining lookup speed.
Data Source
AI summary
A flow-driven forwarding strategy includes receiving an Interest packet, where the interest packet includes a flow state indicator. The content associated with the Interest packet is checked to determine whether that content is locally stored. Another check is performed to determine whether any previously received Interest packet has requested the content. In response to the content not being locally stored and no related Interest packet has been previously received, the flow state indicator is checked in the Interest packet. In response to the flow state indicator indicating that the Interest packet is associated with an active flow, forwarding information is extracted from a flow state table if a hop count has a value of zero or from the Interest packet if the hop count has a value greater than zero. The Interest packet is then forwarded to a next hop in accordance with the forwarding information.