Packet Payload Integrity Check via Content Identifier

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional checksums in packet switched networks do not effectively detect changes to packets that occur before or after checksum calculation, limiting the ability to diagnose errors in packet transmission.

Innovation Solution

Implementing a system where packet payloads are filled with known or knowable random data patterns, allowing byte-by-byte integrity checking by including a payload header with a content identifier, and optionally using base 64 encoding for compatibility with 8-bit clean protocols, enabling detection of transmission errors.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional checksums are used in packet switched networks, then packet transmission can be maintained with standard protocols, but the ability to detect changes to packets occurring before or after checksum calculation is limited

Engineering Contradiction:
Improvedata integrity detection capabilityVSAvoidpacket structure complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The payload is divided into multiple blocks, each with its own header containing a CRC checksum. This segmentation allows individual blocks to be verified independently, enabling detection of changes at specific locations within the payload without requiring complex overall verification mechanisms.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Random data patterns are pre-generated and stored in lookup tables before packet transmission. These known patterns serve as the expected payload content, allowing the receiving end to detect any changes to the payload by comparing received blocks against the pre-stored patterns without requiring complex calculation.

Inventive Principle:
Principle #10Preliminary action

2Measurement precision

If byte-by-byte payload integrity checking is implemented, then transmission errors can be effectively detected and diagnosed, but the packet structure becomes more complex

Engineering Contradiction:
Improveerror detection precisionVSAvoidpacket structure complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The payload is segmented into blocks with individual CRC checksums in their headers. This allows byte-by-byte integrity checking to be performed on manageable units, achieving high measurement precision for error detection while keeping each block's structure simple and standardized.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Random data patterns serve as an intermediary reference mechanism. Instead of complex verification algorithms, the system uses pre-stored random patterns as intermediaries to compare against received payload data, simplifying the verification process while maintaining high precision error detection capability.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If random data patterns are used for payload integrity verification, then detection of transmission errors is enabled, but compatibility with 8-bit clean protocols may be affected

Engineering Contradiction:
Improveerror detection capabilityVSAvoidprotocol compatibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The random data patterns are applied locally to specific payload blocks rather than the entire packet. This allows error detection to be implemented in a localized manner that can coexist with existing protocol requirements, maintaining protocol compatibility while enabling enhanced error detection where needed.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

Random data patterns are pre-generated and stored before transmission begins. This preliminary preparation allows the receiving end to verify payload integrity by simple comparison against stored patterns, avoiding complex real-time calculations that might conflict with 8-bit clean protocol constraints.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS9253062B2Byte by byte received data integrity check
Publication Date: 2016.02.02 KEYSIGHT TECH SINGAPORE (SALES) PTE LTD
  • US9253062B2 patent drawing
  • US9253062B2 patent drawing
  • US9253062B2 patent drawing

AI summary

A method and an apparatus for testing a network. A source port unit may generate a packet including a payload, the payload comprising a content identifier and content data in accordance with the content identifier, and transmit the packet via the network. A destination port unit may receive the packet and extract the content identifier and received content data from the received packet. The destination port unit may obtain expected content data in accordance with the extracted content identifier and compare the expected content data and the received content data.