Token-Based Secure Message Exchange with Blockchain Integrity Checks

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing data exchange methods lack sufficient security against data attacks, particularly in access-sensitive scenarios, and there is a need for enhanced encryption and integrity monitoring in communications networks and systems.

Innovation Solution

A method utilizing a shared genesis hash and blockchain technology for secure data exchange, where a token is generated by an encryption authority (VA) and used to create a new block in a main chain, with each transaction verified using a private blockchain and integrity checks via Merkle trees, ensuring data integrity and encryption with constantly changing keys.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional data exchange methods are used, then ease of operation is maintained, but security against data attacks is insufficient

Engineering Contradiction:
ImprovesecurityVSAvoidcomplexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

An encryption authority (VA) is introduced as an intermediary to generate and manage encryption tokens. The VA creates tokens that are stored on both sender and receiver devices, enabling secure encryption without requiring the devices to directly manage complex key generation and exchange protocols themselves.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

Encryption tokens are generated and stored in advance by the encryption authority before actual data transmission occurs. This preliminary setup allows devices to immediately encrypt data using pre-established tokens without performing complex cryptographic operations at the moment of transmission.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If encryption is implemented for each data transfer, then security is improved, but processing time increases

Engineering Contradiction:
ImprovesecurityVSAvoidprocessing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

Encryption tokens are generated and stored in advance by the encryption authority before actual data transmission occurs. This preliminary setup allows devices to immediately encrypt data using pre-established tokens without performing complex cryptographic operations at the moment of transmission.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

Devices automatically use their stored tokens to encrypt outgoing data and decrypt incoming data without requiring manual key management or complex authentication protocols. The encryption/decryption process becomes a straightforward operational step rather than a time-consuming procedure.

Inventive Principle:
Principle #25Self-service

3Reliability

If data is encrypted with static keys, then ease of operation is maintained, but vulnerability to attacks increases

Engineering Contradiction:
ImprovesecurityVSAvoidease of use
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system uses dynamic encryption where tokens are generated for specific communication pairs and can be updated or rotated. Rather than using static, long-term encryption keys, the system employs flexible token-based encryption that can adapt to different communication scenarios and security requirements.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The encryption parameters (tokens) are changed based on communication context, including the specific sender-receiver pair and timing. This allows the system to provide strong security for each communication instance while maintaining operational simplicity through automated parameter management.

Inventive Principle:
Principle #35Parameter changes

4Measurement precision

If blockchain technology is used for integrity verification, then detection of data breaches is improved, but device complexity increases

Engineering Contradiction:
Improveintegrity detectionVSAvoidcomplexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The encryption authority (VA) acts as an intermediary that manages the blockchain-based integrity verification system. Rather than requiring each device to independently implement and maintain blockchain functionality, the VA handles token generation, storage, and verification, simplifying the implementation for individual devices.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system uses cryptographic hashes and token references that can be verified without requiring full blockchain implementation on each device. Devices store and verify cryptographic representations (copies) of the integrity information rather than maintaining complete blockchain ledgers, reducing complexity while preserving verification capabilities.

Inventive Principle:
Principle #26Copying

Data Source

PatentEP3954082B1Method for securely exchanging encrypted messages
Publication Date: 2025.09.10 ROIDER OLIVER
  • EP3954082B1 patent drawingFigure 1
  • EP3954082B1 patent drawingFigure 2

AI summary

The invention relates to a method for securely exchanging encrypted messages between a sender and a receiver using an encryption authority (VA), in which method the sender and the receiver exchange common starting data before a first data exchange, which starting data form the basis for the subsequent encryptions, said method comprising the following steps: The sender requests the assignment of a token from the encryption authority, which token is appended to a blockchain of the encryption authority, and the encryption authority returns the created token to the sender. The sender creates a key, which is derived from the token and from data of a past data transmission or starting data, encrypts a message for transmission to the receiver, using the key, and secures the hash of the unencrypted message in a new block of a private blockchain of the sender. Subsequently, the sender transfers the encrypted message to the receiver, preferably creates the hash of the encrypted messaged and transfers said hash to the encryption authority, while the receiver preferably transfers the hash of the encrypted message to the encryption authority and requests an integrity confirmation from the encryption authority. In this case, the encryption authority compares the hashes of the receiver and the sender and transfers the comparison result and the token to the receiver, whereupon, if the integrity is confirmed by the encryption authority, the receiver calculates the key for the subsequent decryption of the message from the token and from the last confirmed hash of the unencrypted message or genesis hash. Thereafter, the receiver decrypts the message using the key and secures the hash of the unencrypted message in a block of the private chain. The receiver transfers a receipt confirmation for the hash of the unencrypted message to the sender and a receipt confirmation of the hash of the encrypted message to the encryption authority for additional transactions.