Digital Data Certification Ledger With Multi-Attestation Verification
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing data certification systems rely solely on user authentication, which is based on a single source of information and requires high technical knowledge, making them unreliable and difficult to implement.
Innovation Solution
A module for processing certifying instances of digital data, incorporating a user identifier, storage address, and a non-repudiable ledger with an ordered list of elements including attestations, time stamps, and electronic signatures, ensuring file integrity verification through multiple attestation checks.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If existing data certification systems rely solely on user authentication, then the system structure remains simple, but the reliability and robustness of the certification are insufficient
Solution Approach 1:
The patent combines multiple independent certification sources (user authentication, device attestation, software verification) into a unified multi-factor certification system. Each source generates a separate attestation that is merged into a single certifying instance, creating robust multi-dimensional verification while maintaining modular system architecture
Solution Approach 2:
The certifying instance is constructed as a composite data structure integrating multiple types of attestations (user authentication, device hardware, software integrity) into a single unified object. This composite structure provides diverse verification capabilities while being managed through a single processing interface
2Ease of operation
If existing systems such as PGP and S/MIME are used for encryption and signing, then data security can be achieved, but the ease of operation and accessibility are poor due to high technical knowledge requirements
Solution Approach 1:
The system automatically generates and manages multiple attestations without requiring user intervention for complex cryptographic operations. The processing module autonomously collects attestation data from different sources, generates the certifying instance, and manages verification, making the system as easy to use as simple authentication while maintaining high reliability
Solution Approach 2:
The processing module acts as an intermediary that abstracts complex cryptographic operations from users. It automatically manages the generation, collection, and verification of multiple attestations, shielding users from technical complexity while ensuring robust multi-factor certification
3Reliability
If a single source of information is used for data certification, then the system is easier to implement, but the solidity and trustworthiness of the certification are compromised
Solution Approach 1:
The certification process is segmented into independent attestation sources (user authentication, device hardware, software verification), each generating separate verification data. This segmentation allows each component to be verified independently while contributing to the overall certification solidity
Solution Approach 2:
The certifying instance structure is designed to universally accept multiple types of attestations from different sources through a standardized format. This multi-functional design enables diverse verification methods to be integrated without increasing operational complexity for users
Data Source
AI summary
A module for processing certifying instances of digital data comprises a public key of the user and of certifying systems, wherein each of the certifying instances is associated with a storage address, with a user terminal, and with a non-repudiable ledger comprising an ordered list of elements. Each of the elements comprises: an attestation generated by one of the certifying systems, an attestation comprising a type of attestation, a document hash, a time stamp by the certifying system of the time at which the attestation was generated; an electronic signature of the attestation; a time stamp by the processing module of the time at which the element was added to the ordered list; and possibly a pointer to the document.