Embedded System Checksum Offloading to Host Device

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Embedded systems face challenges in managing and monitoring services due to limited I/O connections and processing resources, particularly in generating and verifying checksums for TCP segments, which is computation-intensive and resource-constrained.

Innovation Solution

The system includes an embedded device that generates TCP segments with no checksum values and a host device that calculates and adds checksums, allowing for efficient IP packet generation and transmission, leveraging industry-standard connections and protocols like ADT for serial interconnects.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the embedded device generates TCP segments with checksum values, then data transmission reliability is improved, but processing load and resource consumption increase

Engineering Contradiction:
Improvedata transmission reliabilityVSAvoidprocessing load
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts the checksum calculation function from the embedded device and relocates it to the host device. The embedded device generates TCP segments with checksum fields set to zero, then transmits these segments to the host device which calculates and fills in the appropriate checksum values. This extraction reduces the processing burden on the resource-constrained embedded device while maintaining transmission reliability.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The host device acts as an intermediary between the embedded device and the network. It receives incomplete TCP segments from the embedded device, performs the computation-intensive checksum calculation, and then transmits the completed segments to the network. This intermediary approach allows the embedded device to focus on its primary function while the host handles protocol compliance.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If the embedded device performs full TCP protocol processing, then protocol compliance is improved, but processing resources are consumed

Engineering Contradiction:
Improveprotocol complianceVSAvoidprocessing resources
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent segments the TCP protocol processing responsibilities between two devices. The embedded device handles packet generation and basic TCP segment assembly, while the host device handles checksum calculation and final protocol validation. This segmentation allows each device to perform only the processing necessary for its capabilities, reducing overall resource consumption.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The embedded device generates TCP segments with checksum fields pre-set to zero, essentially preparing the segments for finalization. This self-service approach allows the embedded device to contribute to protocol compliance without performing the most resource-intensive calculations, as it has already done the preparatory work of segment assembly.

Inventive Principle:
Principle #25Self-service

3Device complexity

If the embedded device has limited I/O connections, then device simplicity is maintained, but service management capability is reduced

Engineering Contradiction:
Improvedevice simplicityVSAvoidservice management capability
Core Design Contradiction:
Device complexityVSAdaptability or versatility

Solution Approach 1:

The host device serves multiple functions: it acts as a TCP checksum calculator, an IP packet generator, and a network management interface. By consolidating these functions in the host device, the embedded device can maintain its simplicity while the host provides the versatility needed for service management and monitoring over standard network connections.

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

Data Source

PatentUS10291355B2Embedded system and method thereof
Publication Date: 2019.05.14 SK HYNIX INC
  • US10291355B2 patent drawing
  • US10291355B2 patent drawing
  • US10291355B2 patent drawing

AI summary

An embedded system may include an embedded device and a host device. The embedded device may provide a packet for a service, and generate a first transmission control protocol (TCP) segment including a piece of the packet and a first header with no checksum value. The host device may receive the first TCP segment, generate a second TCP segment including the piece of the packet and a second header with a checksum value based on the piece of the packet and the first header, and generate an Internet protocol (IP) packet based on the second TCP segment.