Network Switch Packet Replication Resource Sharing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Network switches face inefficiencies due to limited hardware resource capabilities, leading to increased resource consumption and reduced performance in packet forwarding operations.

Innovation Solution

Implementing a network switch system that shares packet replication resources by creating entities for each packet forwarding event, using static random access memory (SRAM) to store destination port masks and per-port packet replication information, and optimizing resource use through multicasting, flooding, and load balancing algorithms.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If each packet forwarding event has its own assigned hardware resources, then packet forwarding can be performed independently and reliably, but resource consumption increases and hardware capabilities are limited

Engineering Contradiction:
Improvepacket forwarding reliabilityVSAvoidhardware resource consumption
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The patent merges packet replication resources by introducing a shared pool mechanism where multiple packet forwarding entities can utilize the same hardware resources concurrently. Instead of dedicating separate resources to each forwarding event, the system combines resources into a common pool that serves multiple entities, thereby reducing overall resource consumption while maintaining forwarding reliability through coordinated access management.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent implements universality by designing hardware resources that can serve multiple packet forwarding entities simultaneously. The shared packet replication resources are configured to handle different forwarding tasks through dynamic allocation, allowing the same physical resources to perform multiple functions and serve various forwarding entities based on current network conditions and requirements.

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

2Device complexity

If hardware resources are limited, then device complexity is reduced and cost is lowered, but network switch performance efficiency is reduced

Engineering Contradiction:
Improvehardware resource complexityVSAvoidnetwork switch performance
Core Design Contradiction:
Device complexityVSProductivity

Solution Approach 1:

The patent applies dynamics by implementing a flexible resource allocation mechanism that dynamically adjusts the distribution of packet replication resources among different forwarding entities based on real-time network conditions, traffic patterns, and entity requirements. This dynamic configuration allows the system to optimize performance continuously without requiring additional hardware complexity, as resources are allocated adaptively rather than statically.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent utilizes parameter changes by modifying the operational parameters of shared hardware resources to optimize performance for different forwarding scenarios. By adjusting parameters such as resource allocation weights, priority levels, and configuration settings, the system can maintain high performance efficiency with limited hardware capabilities, effectively transforming the same physical resources to serve different performance requirements through parameter optimization.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS11469915B2Technologies for sharing packet replication resources in a switching system
Publication Date: 2022.10.11 INTEL CORP
  • US11469915B2 patent drawing
  • US11469915B2 patent drawing
  • US11469915B2 patent drawing

AI summary

Technologies include a network switch configured to perform packet replication. The network switch includes a network communicator, an entity manager, and a tag manager. The network communicator is to receive a data packet, and the entity manger is to identify an entity associated with the data packet and determine a tag associated with the entity. Additionally, the tag manager is to determine a packet replication configuration associated with the tag, and perform one or more per-port forwarding actions based on the packet replication configuration. The packet replication configuration includes one or more destination ports to be masked and a number of copies to be replicated to be sent out on of at least one destination port.