Multi-level Data Pipeline for High-speed Packet Inspection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing digital packet inspection (DPI) methods are slow and bandwidth-consumptive, limiting their effectiveness, especially for high-bandwidth applications, and there is a need for architectures that enhance speed and performance while reducing bandwidth consumption.

Innovation Solution

A multi-level data channel and inspection architecture that includes a pipeline with multiple pipes, each equipped with mechanisms such as a data manager, data ingestor, data processor, data extractor, data attribute updater, query selector, and visualizer, allowing for tiered inspection and efficient data processing across different levels, with the ability to coordinate data passage and bypass mechanisms based on review results.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If traditional digital packet inspection methods are used, then data inspection capability is provided, but processing speed is slow and bandwidth consumption is high

Engineering Contradiction:
Improvedata processing speedVSAvoidbandwidth consumption
Core Design Contradiction:
SpeedVSLoss of energy

Solution Approach 1:

The patent divides the data inspection system into multiple specialized pipes (protocol pipe, payload pipe, heuristic pipe, statistics pipe), each handling specific inspection tasks. This segmentation allows parallel processing of different data aspects, improving overall processing speed while reducing the bandwidth burden on any single inspection mechanism.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The architecture creates a universal inspection framework where a single multi-level pipeline can handle various inspection types (protocol validation, payload analysis, heuristic detection, statistics gathering) through configurable pipes. This multi-functionality eliminates the need for separate inspection systems for each task, reducing total bandwidth consumption while maintaining comprehensive inspection capabilities.

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

2Reliability

If comprehensive data inspection is performed, then data security and integrity are improved, but processing efficiency decreases

Engineering Contradiction:
Improvedata integrityVSAvoidinspection throughput
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system dynamically configures which pipes are activated based on data characteristics and security requirements. Not all inspection pipes are always active - the system adapts the inspection depth and breadth to match the actual threat level and data type, maintaining high reliability when needed while preserving throughput during normal operations.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

Different pipes apply different levels of inspection quality to different data portions. For example, the protocol pipe performs strict validation on header structures while the payload pipe may apply more flexible heuristic analysis. This localized quality approach ensures data integrity where critical while maintaining throughput where possible.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS11290356B2Multi-level data channel and inspection architectures
Publication Date: 2022.03.29 BANK OF AMERICA CORP
  • US11290356B2 patent drawing
  • US11290356B2 patent drawing
  • US11290356B2 patent drawing

AI summary

Aspects of the disclosure relate to a method for inspecting a data stream. The method may include conveying the data stream through a multi-level data channel and inspection architecture. The architecture includes a multi-level data pipeline. The pipeline is formed from pipes arranged serially such that each output of one pipe provides an input to a successive one of the plurality of pipes. The pipeline receives the data stream at an upstream portion of the pipeline, and inspects the data in the data stream. Thereafter, the pipeline outputs inspected data at a downstream portion of the pipeline. The outputted inspected data becomes inputted date for a successive one of the pipes. A data manager may be configured to coordinate passage of the data into and out of the pipeline, and between one or more of the group of mechanisms. Each pipe is configured to inspect the data on a different level of data channel inspection, each level of data channel inspection having individual data attribute and/or metadata extracting capabilities, from any of the other of the plurality of pipes.