Transaction Data Signature for Device Notarization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Ensuring device and application integrity, as well as user authentication, becomes challenging as users access network systems with various devices, necessitating enhanced assurance mechanisms.

Innovation Solution

Concatenating integrity values to generate a transaction data signature (TDS), which includes device integrity, application integrity, application encryption module, and authentication generation module values, with a seed value incorporating device integrity, application integrity, user-specific, and pseudo-random numbers, to create a notarization code for initial device state verification and subsequent authorization checks.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional authentication methods are used, then ease of operation is maintained, but device and application integrity assurance deteriorates

Engineering Contradiction:
Improvedevice and application integrity assuranceVSAvoidauthentication mechanism complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The authentication mechanism is segmented into multiple independent integrity checks: device integrity verification, application integrity verification, and combined verification. Each segment generates separate integrity values that are then concatenated to form a comprehensive authentication signature, allowing systematic verification of each component's integrity

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent creates a composite authentication signature by concatenating multiple integrity values (device integrity value, application integrity value, and their combination) to form a Transaction Data Signature. This composite signature provides multi-layered assurance of integrity without requiring a single complex verification system

Inventive Principle:
Principle #40Composite materials

2Reliability

If multiple integrity values are concatenated to generate TDS, then information security is improved, but computational complexity increases

Engineering Contradiction:
Improveinformation securityVSAvoidcomputation complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

Integrity values for device and application are pre-calculated and stored before the authentication transaction occurs. When authentication is needed, these pre-computed values are simply concatenated and signed, avoiding the need for complex real-time computations during the actual authentication process

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent uses cryptographic hashing to create compact representations (copies) of large amounts of device and application data. These hash values serve as simplified proxies for the actual integrity verification, reducing computational complexity while maintaining security

Inventive Principle:
Principle #26Copying

Data Source

PatentUS9560046B2Device notarization
Publication Date: 2017.01.31 KAISER FOUNDATION HOSPITALS
  • US9560046B2 patent drawing
  • US9560046B2 patent drawing
  • US9560046B2 patent drawing

AI summary

Methods and systems for device notarization and verification are provided. In one implementation, various integrity values are concatenated to generate a concatenated value that is used to generate a transaction data signature (TDS). In one implementation, the concatenated value is a concatenation of a device value, an application value, an application encryption (AE) module value, and an authentication generation (AG) module value. The TDS or notarization code is generated by applying the concatenated value to the AG module. In one implementation, subsequent use of the application on the device involves generation of a new TDS, which is compared against the notarization code to determine whether use of the application on the device is authorized. In one implementation, the AE module and the AG module are seeded with a seed value which includes a device value, an application value, a user specific value, and a pseudo random number.