D2D Authentication via Sequential Hash Chain

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Device-to-device (D2D) communication in IoT services faces security threats due to data leakage, particularly on low-power and low-specification platforms, where conventional security techniques struggle to effectively manage data security.

Innovation Solution

A system and method for secure D2D communication using a key token hashed multiple times, with a first device transmitting sequential hash values and a second device authenticating using these values, managing a maximum count to ensure secure communication and key token lifecycle management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional security techniques are used in D2D communication, then data transmission can be established, but security against data leakage cannot be ensured

Engineering Contradiction:
Improvedata securityVSAvoiddata leakage risk
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The patent segments the authentication process into multiple stages using a chain of hash values. Instead of using a single authentication credential, the system divides the security verification into sequential steps where each hash value in the chain represents a segment of the authentication process. This segmentation prevents complete data leakage compromise because each segment (hash value) only validates one step in the chain.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent performs preliminary hashing operations to generate a chain of hash values before actual D2D communication begins. The first device pre-computes multiple hash values (H1, H2, H3, ..., Hn) from the authentication credential and stores them in sequential order. This preliminary action ensures that when communication occurs, the devices can quickly verify authenticity without performing complex real-time computations, while the pre-generated chain provides layered security protection.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If multiple hash values are generated and stored for authentication, then security is improved, but device complexity increases

Engineering Contradiction:
Improveauthentication securityVSAvoidstorage and computation requirements
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent employs hash values as disposable, short-living authentication objects. Each hash value in the chain is used once for authentication and then discarded. The first device transmits hash values sequentially from H1 to Hn, and once a hash value is used for verification, it is no longer needed. This approach provides strong authentication security without requiring long-term storage of multiple credentials, as each hash value serves its purpose and is then discarded.

Inventive Principle:
Principle #27Cheap short-living objects (Disposable)

Solution Approach 2:

The patent changes the parameter of authentication from static credentials to dynamic hash values with varying computational states. The authentication credential undergoes repeated hashing transformations to generate a sequence of values with different parameters (H1, H2, H3, ..., Hn). Each hash value in the chain represents a different computational state, allowing the system to maintain security while managing storage requirements through parameter transformation rather than storing multiple independent credentials.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If sequential hash values are transmitted for authentication, then data leakage is prevented, but communication time increases

Engineering Contradiction:
Improvesecurity against data leakageVSAvoidauthentication time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent performs the computationally intensive hashing operations in advance, before actual communication begins. The first device pre-generates the entire chain of hash values (H1 through Hn) from the authentication credential and stores them locally. During D2D communication, the devices simply compare transmitted hash values against the pre-computed chain, which requires minimal computation time. This preliminary action separates the heavy computational workload from the real-time communication process, maintaining both security and speed.

Inventive Principle:
Principle #10Preliminary action

4Reliability

If a maximum count is managed for hash values, then security control is improved, but ease of operation decreases

Engineering Contradiction:
Improvesecurity controlVSAvoidauthentication process simplicity
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent implements feedback mechanisms where the first device tracks the current position in the hash chain by maintaining a maximum count indicator, and the second device verifies authentication by comparing received hash values against its own computed chain. After each successful authentication using a hash value, the maximum count is decremented, providing feedback on the remaining security margin. This automated feedback system manages security control without requiring complex manual intervention, as the devices themselves track and update their authentication state.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS11042954B2System and method for communication between devices
Publication Date: 2021.06.22 SAMSUNG SDS CO LTD
  • US11042954B2 patent drawing
  • US11042954B2 patent drawing
  • US11042954B2 patent drawing

AI summary

A system and method for communication between devices are provided. According to the embodiments of the present disclosure, it is possible to easily authenticate a counterpart device using a one-time key HN(T) for a D2D communication between a first device and a second device, without using a separate secure channel (e.g., secure sockets layer (SSL), transport layer security (TLS), or the like) in an environment where it is difficult to synchronize the first device with the second device without intervention of a server.