Packet Processing Pipeline Domain Segmentation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

As packet processing pipelines grow in size and complexity, programming and managing them becomes challenging, particularly due to conflicts between software components and the difficulty of performing bug fixes without disrupting other programs, leading to potential malfunctions and operational disruptions.

Innovation Solution

The implementation of modular programming and domain-based resource management within packet processing pipelines, where software domains can execute independently, allowing programs to be loaded and unloaded at runtime without affecting other domains, and using compiler and runtime checks to enforce configuration rules and prevent resource conflicts.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If packet processing pipelines grow in size and complexity to handle more functions, then the pipeline's capability and versatility improve, but programming and managing the pipeline becomes more challenging and error-prone

Engineering Contradiction:
Improvepipeline capabilityVSAvoidprogramming complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent divides the packet processing pipeline into multiple independent domains, where each domain can be programmed and managed separately. This segmentation allows complex pipeline functionality to be broken down into manageable, independent units that can be developed, tested, and maintained separately, reducing overall programming complexity while maintaining versatility.

Inventive Principle:
Principle #1Segmentation

2Productivity

If multiple programs execute concurrently on the packet processing pipeline to implement different network functions, then the pipeline's functionality and productivity improve, but conflicts between software components increase

Engineering Contradiction:
Improvepipeline throughputVSAvoidsoftware conflict risk
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent segments the packet processing pipeline into isolated domains, where each domain can execute multiple programs concurrently without interfering with other domains. This domain-based segmentation prevents software conflicts by ensuring that programs in different domains operate independently with dedicated resources, maintaining reliability while enabling high productivity through parallel execution.

Inventive Principle:
Principle #1Segmentation

3Reliability

If bug fixes are performed on software components in the packet processing pipeline, then the reliability of affected functions improves, but other programs may be disrupted

Engineering Contradiction:
Improvebug fix effectivenessVSAvoidpipeline operational continuity
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent organizes software into domain-based modules that can be independently updated. When bug fixes are needed, only the specific domain containing the bug needs to be modified and reloaded, while other domains continue to operate uninterrupted. This modular segmentation enables targeted maintenance that improves reliability of affected functions without disrupting overall pipeline productivity.

Inventive Principle:
Principle #1Segmentation

4Ease of operation

If the packet processing pipeline is programmed in a monolithic manner by a team of developers, then management and coordination are simplified, but the system becomes difficult to maintain and update

Engineering Contradiction:
Improvemanagement simplicityVSAvoidmaintenance difficulty
Core Design Contradiction:
Ease of operationVSEase of repair

Solution Approach 1:

The patent divides the monolithic pipeline into domain-based modules that can be independently developed, managed, and maintained by different teams. Each domain represents a self-contained unit with clear boundaries, making it easier to assign responsibility, track changes, and perform maintenance without affecting the entire system. This modular approach improves ease of repair while maintaining manageable complexity through standardized domain interfaces.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS20220164237A1Configuration of a packet processing pipeline
Publication Date: 2022.05.26 INTEL CORP
  • US20220164237A1 patent drawing
  • US20220164237A1 patent drawing
  • US20220164237A1 patent drawing

AI summary

Examples described herein relate to a packet processing device comprising a programmable packet processing pipeline that is logically partitioned into multiple domains including privileged and unprivileged domains. The multiple domains can span one or more stages of the programmable packet processing pipeline, wherein at least one stage is to perform match action operations.