Structure Checksum Verification for Fail-Safe Data Transmission

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing fail-safe communication protocols, such as Profisafe, fail to reliably detect data transmission errors caused by differing data structures between communication partners, leading to undetected corruption in data transmission.

Innovation Solution

Assigning data-specific representatives to data types in the data structure on both automation components, forming a structure checksum, and transmitting this along with the standard checksum to detect discrepancies upon receipt, ensuring data integrity and error detection.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a standard checksum is formed over the entire telegram including data structure, then transmission errors can be detected, but data type exchanges within the data structure cannot be reliably detected

Engineering Contradiction:
Improveerror detection capabilityVSAvoidundetected data corruption
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The patent segments the checksum verification process into two distinct parts: a standard telegram checksum for general transmission errors and a separate structure checksum specifically for data type verification. This segmentation allows each checksum to focus on its specific detection task, with the structure checksum examining only the data type information within the data structure to identify exchanges or mismatches that the general telegram checksum would miss.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary structure checksum that acts as a mediator between the transmitted data and the receiver's verification process. This structure checksum serves as a dedicated verification layer that specifically targets data type integrity, bridging the gap between general transmission verification and specific data type validation, thereby enabling detection of data type exchanges without interfering with the standard checksum process.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If data structures with different data types are transmitted between communication partners, then communication flexibility is maintained, but data corruption goes undetected

Engineering Contradiction:
Improvedata structure flexibilityVSAvoiddata integrity detection
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent applies preliminary action by pre-calculating and transmitting the structure checksum along with the data structure before the actual data transmission occurs. This allows the receiver to have the verification data ready in advance, enabling immediate detection of data type exchanges upon receipt without requiring complex post-transmission analysis, thus maintaining both flexibility and reliability.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements a feedback mechanism where the structure checksum is transmitted with the data and then verified by the receiver. This creates a feedback loop that provides confirmation of data type integrity, allowing the communication system to detect and report data type exchanges, thereby ensuring that adaptability in data structure handling does not compromise data integrity.

Inventive Principle:
Principle #23Feedback

3Device complexity

If only a single checksum method is used for telegram verification, then the verification process is simple, but it cannot detect all types of transmission errors

Engineering Contradiction:
Improveverification process complexityVSAvoiderror detection completeness
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The patent segments the verification process into two independent but complementary checksum operations: a standard telegram checksum for general error detection and a structure checksum for data type-specific verification. This segmentation maintains relative simplicity by keeping the two checksum methods independent while achieving comprehensive error detection through their combination.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent merges two checksum verification methods into a unified error detection framework. The standard telegram checksum and the structure checksum work together in combination, with each addressing different aspects of error detection. This merging allows the system to detect both general transmission errors and specific data type exchanges, achieving complete error detection without requiring a single complex verification method.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentEP3550748B1Method for detecting data falsification in a data transfer over error-proof communication link
Publication Date: 2021.08.11 SIEMENS AG
  • EP3550748B1 patent drawingFigure 1
  • EP3550748B1 patent drawingFigure 2~3
  • EP3550748B1 patent drawingFigure 4~5

AI summary

To detect data corruption during data transmission via a fail-safe communication link (1) between a first automation component (11) and a second automation component (12) of the industrial control technology, additional structure checksums (CRCstruct) are generated during the transmission of a data structure (20) to secure the data structure (20), whereby representatives (30) are assigned to the data types (21,...,25) and the structure checksum (CRCstruct) is generated via the representatives (30).