Network Processor Packet Traffic Control via Pipe ID Counters

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing network processors face challenges in effectively managing and controlling packet traffic, leading to potential congestion and inefficiencies due to the lack of proactive measures to prevent excessive packet transmission, even when backpressure commands are received.

Innovation Solution

A system that assigns a pipe identifier to each packet and uses counters to track packet and byte counts per network interface, comparing these counts against thresholds to limit traffic proactively and prevent congestion by refraining from scheduling further packets when thresholds are exceeded, thereby controlling packet traffic more efficiently.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If network processors transmit packets without proactive traffic control, then packet transmission speed is improved, but network congestion occurs and efficiency deteriorates

Engineering Contradiction:
Improvepacket transmission speedVSAvoidnetwork efficiency
Core Design Contradiction:
SpeedVSProductivity

Solution Approach 1:

The patent applies preliminary action by implementing traffic control measures before congestion occurs. Counters track packet and byte counts for each pipe identifier, and when thresholds are exceeded, the control circuit proactively limits further packet transmission through that pipe. This prevents congestion before it degrades network efficiency, while still allowing high-speed transmission within acceptable limits.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If backpressure commands are used to control packet traffic, then packet congestion is prevented, but traffic control is delayed and network performance is reduced

Engineering Contradiction:
Improvecongestion preventionVSAvoidtraffic control delay
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary traffic control by monitoring packet and byte counts against thresholds before congestion occurs. When a counter exceeds its threshold, the control circuit immediately limits packet transmission through the associated pipe identifier, eliminating the delay inherent in traditional backpressure mechanisms that react only after congestion is detected.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements feedback through counters that continuously monitor packet and byte counts for each pipe identifier. When thresholds are exceeded, this feedback triggers the control circuit to limit further transmission, creating a closed-loop control system that maintains reliable congestion prevention without delay.

Inventive Principle:
Principle #23Feedback

3Productivity

If packet traffic is limited by threshold counters, then network congestion is prevented and efficiency is improved, but device complexity increases

Engineering Contradiction:
Improvenetwork efficiencyVSAvoidtraffic control structure
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent applies segmentation by dividing traffic control into separate counters for each pipe identifier, with distinct packet counters and byte counters. This modular approach allows independent threshold monitoring and control for multiple pipes, improving network efficiency through fine-grained traffic management while keeping each counter unit relatively simple in structure.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS9906468B2Packet traffic control in a network processor
Publication Date: 2018.02.27 MARVELL ASIA PTE LTD
  • US9906468B2 patent drawing
  • US9906468B2 patent drawing
  • US9906468B2 patent drawing

AI summary

A network processor controls packet traffic in a network by maintaining a count of pending packets. In the network processor, a pipe identifier (ID) is assigned to each of a number of paths connecting a packet output to respective network interfaces receiving those packets. A corresponding pipe ID is attached to each packet as it is transmitted. A counter employs the pipe ID to maintain a count of packets to be transmitted by a network interface. As a result, the network processor manages traffic on a per-pipe ID basis to ensure that traffic thresholds are not exceeded.