Sketch Table for Local Traffic Profiling in Network Nodes

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Network nodes in distributed routing systems are not easily reprogrammable once deployed, and software-defined networking (SDN) introduces latency by requiring a centralized controller for every modification in forwarding behavior, losing local decision-making capabilities and relying on an out-of-band network for control plane programming.

Innovation Solution

A sketch table system that includes a 'heavy' and 'light' data flow counting section, organized as a single data structure with cache-aligned memory sections, allowing for efficient cache read operations and promoting, demoting, and ejecting entries to manage packet flow count data, enabling local traffic profiling and management at network nodes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If software-defined networking (SDN) is used to provide programmability in network nodes, then ease of operation is improved, but loss of time increases due to centralized controller involvement in every forwarding behavior modification

Engineering Contradiction:
ImproveprogrammabilityVSAvoidlatency
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The patent segments the forwarding behavior into two categories: common behavior handled by the centralized SDN controller and exception behavior handled locally by the network node's state machine. This segmentation allows most operations to be managed centrally while enabling rapid local response to exceptions, thus maintaining programmability without incurring centralized latency for every modification.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent pre-configures exception handling rules and state machine logic in the network node before deployment. When exceptional conditions occur, the node can immediately execute pre-programmed responses without waiting for centralized controller instructions, thereby eliminating the latency that would otherwise be incurred for every forwarding behavior modification.

Inventive Principle:
Principle #10Preliminary action

2Measurement precision

If a traditional flow table is used to store packet flow information, then measurement precision is improved, but device complexity increases due to separate data structures for different packet rates

Engineering Contradiction:
Improvepacket flow counting accuracyVSAvoiddata structure complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The patent merges multiple separate counting mechanisms into a single unified sketch table data structure that can handle different packet rates simultaneously. Instead of maintaining separate flow tables for high-rate and low-rate packets, the sketch table uses a unified structure with shared memory sections that dynamically adapts to different traffic patterns, thereby reducing device complexity while preserving measurement precision.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The sketch table is designed as a universal data structure that can serve multiple functions: counting high-rate packet flows, counting low-rate packet flows, and providing cache-aligned memory access patterns. This multi-functional design eliminates the need for separate specialized data structures, reducing overall system complexity while maintaining accurate measurement capabilities across different traffic scenarios.

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

Data Source

PatentUS11601531B2Sketch table for traffic profiling and measurement
Publication Date: 2023.03.07 INTEL CORP
  • US11601531B2 patent drawing
  • US11601531B2 patent drawing
  • US11601531B2 patent drawing

AI summary

One embodiment provides a network system. The network system includes an application layer to execute one or more networking applications to generate or receive data packets having flow identification (ID) information; and a packet processing layer having profiling circuitry to generate a sketch table indicative of packet flow count data; the sketch table having a plurality of buckets, each bucket includes a first section including a plurality of data fields, each data field of the first section to store flow ID and packet count data, each bucket also having a second section having a plurality of data fields, each data field of the second section to store packet count data.