Parallel Synchronous Hash History Authentication

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current authentication processes face challenges in balancing convenience and security, as they often require multiple authentication factors, which can be inconvenient and prone to social engineering attacks, and struggle to distinguish authentication from authorization, leading to potential unauthorized access and data breaches.

Innovation Solution

A method and system for authenticating users and devices through a parallel synchronous update of immutable hash histories, where a device root hash and user profile hash are compared to verify identity, and a new hash is computed with each transaction record, evolving the identity and synchronizing it across devices and profiles.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If multiple authentication factors are used, then security is improved, but user convenience deteriorates

Engineering Contradiction:
Improveauthentication securityVSAvoiduser convenience
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent extracts the authentication verification process from traditional server-dependent methods and implements it locally on the user's device through a state machine that autonomously verifies authentication credentials against stored authentication data, eliminating the need for users to manually manage multiple authentication factors while maintaining security

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces an authentication state machine as an intermediary component that mediates between authentication credentials and the authentication database, automatically managing the verification process and transforming complex multi-factor authentication into a seamless user experience

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If traditional authentication methods are used, then ease of operation is maintained, but susceptibility to social engineering attacks increases

Engineering Contradiction:
Improveauthentication convenienceVSAvoidsocial engineering vulnerability
Core Design Contradiction:
Ease of operationVSObject-affected harmful factors

Solution Approach 1:

The patent applies preliminary anti-action by pre-storing authentication data in an encrypted authentication database on the user's device and using a state machine to verify credentials against this local database, preventing social engineering attacks by ensuring that authentication verification occurs locally rather than through vulnerable network communications

Inventive Principle:
Principle #9Preliminary anti-action

3Device complexity

If authentication and authorization are combined, then device complexity is reduced, but security reliability deteriorates

Engineering Contradiction:
Improveauthentication system complexityVSAvoidsecurity reliability
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The patent segments the authentication system into distinct functional components: an authentication state machine for verification, an authentication database for data storage, and separate authorization logic, allowing each component to be optimized independently while maintaining overall system security and reducing complexity

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS10396992B2Authentication of a user and/or a device through parallel synchronous update of immutable hash histories
Publication Date: 2019.08.27 CLOUDMODE LLC
  • US10396992B2 patent drawing
  • US10396992B2 patent drawing
  • US10396992B2 patent drawing

AI summary

Disclosed is a method, a device, and/or a system of authentication of a user and/or a device through parallel synchronous update of immutable hash histories. In one embodiment, a computer-implemented method for authentication includes receiving an identity claim from a device that includes a device root hash of a hashed history of the device, referred to as a device hastory. Data of a user profile associated with the device that includes a profile root hash of a profile hastory is retrieved. The device root hash and the profile root hash are compared and determined to be identical to verify an identity of a user and/or a device. A transaction record is generated and deposited as a new block in both in the profile hastory and device hastory. A new profile root hash is computed to evolve the identity of the user profile for a prospective authentication request.