Segmented Packet Redundancy Encoding for Low-Latency Reliable Transfer

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Modern computing devices face challenges in reliable data transmission over unreliable networks, particularly in IoT devices with limited memory and power resources, where packet loss and latency issues are common due to intermittent connectivity and congestion, making traditional reliability protocols inefficient.

Innovation Solution

Implementing a redundancy encoding scheme that segments data blocks into packets with embedded redundant data, allowing endpoint devices to reconstruct lost or corrupt packets without requiring retransmissions, thereby enhancing data integrity and reducing latency in unreliable network conditions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional reliability protocols (e.g., TCP) are used to ensure reliable data transmission, then data integrity is improved, but latency increases significantly due to frequent two-way communication exchanges for acknowledgements and retransmissions

Engineering Contradiction:
Improvedata integrityVSAvoidlatency
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by pre-calculating and embedding redundant data (parity packets) into the transmitted data stream before actual packet loss occurs. This allows the receiving device to reconstruct lost packets using the pre-prepared redundant data, eliminating the need for time-consuming retransmission requests and acknowledgements that characterize traditional TCP protocols.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces redundant parity packets as an intermediary element between the transmitting and receiving devices. These intermediary packets carry encoded information from multiple original packets, enabling the receiver to recover from packet loss without direct communication with the transmitter, thus bypassing the latency-inducing two-way exchange protocol of traditional reliability mechanisms.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If redundancy encoding schemes are applied to all network packets, then loss tolerance is improved, but device complexity increases due to additional encoding and decoding operations

Engineering Contradiction:
Improveloss toleranceVSAvoidencoding complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent applies segmentation by dividing the data stream into fixed-size packets and applying redundancy encoding at the packet level rather than requiring complex end-to-end error correction codes. Each packet is independently encoded with simple parity information, reducing the computational complexity compared to applying comprehensive redundancy schemes to entire data streams or large data blocks.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent utilizes parameter changes by dynamically adjusting the level of redundancy (number of parity packets) based on network conditions and packet importance. This allows the system to optimize between reliability and complexity by varying the redundancy parameter, applying stronger encoding only when necessary rather than uniformly to all packets.

Inventive Principle:
Principle #35Parameter changes

3Speed

If segmented packets are transmitted over unreliable networks, then data transmission speed is improved, but packet loss increases due to network congestion and intermittent connectivity

Engineering Contradiction:
Improvetransmission speedVSAvoidpacket delivery reliability
Core Design Contradiction:
SpeedVSReliability

Solution Approach 1:

The patent implements beforehand cushioning by embedding redundant parity packets within the data stream in advance, creating a buffer against potential packet loss. This pre-prepared redundancy acts as a cushion that absorbs the impact of packet loss in unreliable networks, allowing reconstruction without retransmission and maintaining both speed and reliability.

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

4Reliability

If retransmission protocols are used to recover lost packets, then data completeness is improved, but latency increases due to waiting for retransmissions

Engineering Contradiction:
Improvedata completenessVSAvoidretransmission delay
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies self-service by enabling the receiving device to autonomously reconstruct lost packets using the embedded redundant parity data from previously received packets. This eliminates the need for the receiver to request retransmissions from the transmitter, allowing the system to self-correct packet loss without external intervention or additional communication rounds, thereby maintaining data completeness while minimizing latency.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS11515890B2Technologies for applying a redundancy encoding scheme to segmented network packets
Publication Date: 2022.11.29 INTEL CORP
  • US11515890B2 patent drawing
  • US11515890B2 patent drawing
  • US11515890B2 patent drawing

AI summary

Technologies for applying a redundancy encoding scheme to segmented portions of a data block include an endpoint computing device communicatively coupled to a destination computing device. The endpoint computing device is configured to divide a block of data into a plurality of data segments as a function of a transmit window size and a redundancy encoding scheme, and generate redundant data usable to reconstruct each of the plurality of data segments. The endpoint computing device is additionally configured to format a series of network packets that each includes a data segment of the plurality of data segments and generated redundant data for at least one other data segment of the plurality of data segments. Further, the endpoint computing device is configured to transport each of the series of network packets to a destination computing device. Other embodiments are described herein.