Encrypted Data Content Authenticity Verification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In data distribution scenarios where data is stored in non-trusted locations, such as third-party caches or peer-to-peer networks, verifying the integrity and authenticity of data content is challenging, especially when the data publisher does not provide digital signatures or cryptographic hashes.

Innovation Solution

A method where data content is encrypted with a secret symmetric key shared among receiving devices, and a small subset of the encrypted content is downloaded from the data publisher to verify its authenticity by comparing it with a received subset, ensuring that the content originates from a trusted source.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If data content is distributed through third-party caches or peer-to-peer networks, then data distribution efficiency is improved, but data integrity and authenticity verification becomes difficult

Engineering Contradiction:
Improvedata distribution efficiencyVSAvoiddata integrity verification
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent segments the encrypted data content into multiple chunks for distribution across peer-to-peer networks. Each chunk is independently verified using cryptographic hash functions, allowing verification of individual segments without requiring verification of the entire data set. This segmentation enables efficient parallel distribution while maintaining verification capability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies preliminary cryptographic hashing to the encrypted data content before distribution. Hash values are calculated in advance and distributed alongside the data chunks, enabling receiving devices to verify integrity immediately upon receipt without requiring complex post-distribution verification processes. This preliminary action simplifies the verification mechanism.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If digital signatures or cryptographic hashes are provided for data verification, then data authenticity is improved, but system complexity increases

Engineering Contradiction:
Improvedata authenticityVSAvoidverification system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts the verification function into a separate cryptographic hashing operation that is applied to the encrypted data content. Rather than embedding complex verification logic within the distribution system, the solution uses standalone hash functions that can be independently calculated and compared. This extraction simplifies the overall system architecture while maintaining strong verification capabilities.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent uses cryptographic hash functions to create simplified copies (hash values) of the encrypted data content. These hash copies are much smaller than the original data and can be easily transmitted and verified. Receiving devices verify authenticity by comparing calculated hashes against distributed hash values, avoiding the need to handle complex cryptographic signatures while maintaining verification integrity.

Inventive Principle:
Principle #26Copying

3Reliability

If the data publisher changes distribution chains to enable verification, then data security is improved, but distribution flexibility is reduced

Engineering Contradiction:
Improvedata securityVSAvoiddistribution chain flexibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent introduces cryptographic hash functions as intermediary verification mechanisms that work independently of the distribution chain structure. These hash-based verification systems can operate at any point in the distribution network, whether data flows through centralized servers, third-party caches, or peer-to-peer nodes. This intermediary approach maintains security without constraining distribution flexibility.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent implements a universal verification mechanism using cryptographic hashing that functions across multiple distribution scenarios. The same hash-based verification approach works for direct publisher-to-client distribution, third-party cache distribution, and peer-to-peer distribution. This multi-functional verification system adapts to different distribution chains without requiring modification, preserving both security and flexibility.

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

Data Source

PatentEP4331180B1Cipher text validation
Publication Date: 2025.04.02 HIVE STREAMING
  • EP4331180B1 patent drawingFigure 1
  • EP4331180B1 patent drawingFigure 2
  • EP4331180B1 patent drawingFigure 3

AI summary

The present disclosure relates to a method of a data publishing device (10) of distributing data content to receiving devices (11, 12) in a network and a method of a device (12) of receiving data content in a network, as well as devices (10, 12) performing the methods. In an aspect, a method of a device (12) of receiving data content in a network is provided. The method comprises receiving (S303, S307) encrypted data content from another device (11, 14) in the network, the data content having been encrypted with a symmetric key shared with a trusted data content publisher device (10), requesting (S304), from the trusted data content publisher device (10), a subset of the encrypted data content received from said another device (11) in the network, and verifying (S305) whether or not the subset of the encrypted data content received from the trusted data content publisher device (10) matches a selected section of the encrypted data content received from said another device (11, 14) in the network, wherein a match indicates that the encrypted data content received from said another device (11) can be trusted.