Sequential Signed Certificates for Device Authentication
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional information verification techniques for electronic devices are inefficient and unreliable, often requiring third-party services that access personal information and suffer from latency and high costs, especially when verifying the legitimacy of messages or requests across communication networks.
Innovation Solution
A verification system that uses sequences of signed certificates, where devices store public and private keys, and by signing certificates, they create a chain of digital signatures stored on a database, allowing devices to independently verify identities through public keys, reducing reliance on third-party services and minimizing access to personal information.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional third-party services are used for information verification, then verification can be performed, but latency increases and costs increase
Solution Approach 1:
The patent extracts the verification function from third-party services and implements it directly in the electronic device through local storage of ancillary markers and authentication algorithms. This eliminates the need to query external services, thereby reducing verification latency while maintaining accuracy through locally available authentication data.
Solution Approach 2:
The electronic device performs verification operations autonomously using locally stored ancillary markers and authentication algorithms. The device serves itself by maintaining its own authentication credentials and verifying messages without requiring external third-party intervention, thus eliminating verification latency and reducing operational costs.
2Reliability
If third-party services access personal information for verification, then verification can be performed, but privacy is compromised
Solution Approach 1:
The patent extracts personal information from third-party service access and stores it locally in the electronic device as ancillary markers. This allows verification to be performed using only locally stored data without requiring third parties to access personal information, thereby maintaining verification accuracy while protecting user privacy.
Solution Approach 2:
The electronic device autonomously performs verification using its own locally stored ancillary markers and authentication algorithms, eliminating the need for third-party services to access personal information. This self-verification mechanism maintains privacy while ensuring accurate authentication.
3Reliability
If conventional verification techniques are used, then verification can be performed, but costs increase
Solution Approach 1:
The patent extracts the verification function from expensive third-party services and implements it locally in the electronic device using stored ancillary markers and authentication algorithms. This eliminates ongoing verification costs while maintaining accurate authentication through locally available data.
Solution Approach 2:
The electronic device performs verification operations autonomously using its own resources and locally stored authentication data, eliminating the need to pay third-party services for verification. This self-verification approach reduces operational costs while maintaining verification accuracy.
4Reliability
If third-party services are used for verification, then verification can be performed, but the system becomes complex
Solution Approach 1:
The patent extracts the verification functionality from complex third-party service architectures and implements it as a simplified local module in the electronic device. This reduces system complexity by eliminating external service dependencies while maintaining verification accuracy through locally stored ancillary markers and authentication algorithms.
Data Source
AI summary
A method of operation of a first device storing a first private key and a first public key corresponding to the first private key includes receiving, from a second device, an unsigned certificate including a second public key and second identification information associated with the second public key. The method further includes sending, to a server, a signed certificate corresponding to a signed version of the unsigned certificate. The method further includes receiving, from a third device, a third public key and third identification information associated with the third public key, and based on a request for authentication associated with the third identification information, receiving, from the server, a response that indicates whether the server identifies, within a database, a sequence of signed certificates from the first public key to the third public key.