Network Traffic Packet Verification System

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional traffic checking systems lack the ability to identify and automatically verify the content of network traffic at high data rates, fail to detect packet modifications, and are often expensive and inflexible, not utilizing the features of devices under test like switching chips for cost savings.

Innovation Solution

A method that accesses pre-registered expected results for network traffic checking, using content verification information to identify and verify individual packets, employing content addressable memory and logic components to compare expected and actual packet content, and forward unexpected packets for analysis.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional traffic checking systems are used, then basic packet forwarding verification is possible, but the systems cannot detect packet modifications, are expensive, and lack flexibility

Engineering Contradiction:
Improvepacket verification accuracyVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the verification process into two independent parts: a simple FCS validation step and a content verification step using pre-registered expected results. This allows basic verification to remain simple while adding modification detection capability through the segmentation of verification functions.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary mechanism using pre-registered expected packet contents stored in memory. This intermediary allows the system to compare actual packet contents against expected values without requiring complex real-time analysis, thereby improving reliability while maintaining manageable system complexity.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If conventional traffic checking systems are used, then packet forwarding can be monitored, but the systems cannot automatically verify packet content at high data rates

Engineering Contradiction:
Improveverification speedVSAvoidcontent verification accuracy
Core Design Contradiction:
ProductivityVSMeasurement precision

Solution Approach 1:

The patent applies preliminary action by pre-registering expected packet contents in memory before the verification process begins. This allows the system to perform rapid comparison of actual versus expected contents at high data rates without performing complex calculations during the verification process, thereby achieving both high productivity and measurement precision.

Inventive Principle:
Principle #10Preliminary action

3Ease of manufacture

If conventional traffic checking systems are used, then basic traffic monitoring is possible, but the systems are expensive and do not utilize DUT features for cost savings

Engineering Contradiction:
Improvecost effectivenessVSAvoidsystem flexibility
Core Design Contradiction:
Ease of manufactureVSAdaptability or versatility

Solution Approach 1:

The patent implements self-service by utilizing the DUT's own switching chip features to perform verification functions. The system leverages existing hardware capabilities within the DUT rather than requiring separate expensive verification equipment, thereby reducing costs while maintaining adaptability through configurable verification parameters.

Inventive Principle:
Principle #25Self-service

4Reliability

If additional verification fields are added to stimulus packets, then packet modification detection is improved, but the packet generation becomes more constrained

Engineering Contradiction:
Improvemodification detection capabilityVSAvoidpacket generation complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts the verification function from the stimulus packet structure itself and places it in the verification system through pre-registered expected results. This allows modification detection without adding constraints to packet generation, as the verification logic is separated from the packet formation process.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS7869367B2Methods and systems for checking expected network traffic
Publication Date: 2011.01.11 HEWLETT PACKARD ENTERPRISE DEV LP
  • US7869367B2 patent drawing
  • US7869367B2 patent drawing
  • US7869367B2 patent drawing

AI summary

A method for checking expected network traffic is disclosed. The method for checking expected network traffic includes accessing pre-registered expected results of a network traffic checking exercise that include expected packet content verification information for individual packets of the network traffic. In addition, the method includes accessing network traffic where individual packets of the network traffic include actual packet content verification information. Individual packets are identified that have expected packet content verification information that does not match their actual packet content verification information and individual packets are identified that have expected packet content verification information that does match their actual packet content verification information.