Cryptogram Challenge Authentication Without Public-Key Storage
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing device authentication methods require deploying and maintaining public keys on user devices, which is cumbersome and resource-intensive.
Innovation Solution
A method where a user device sends a data request to a server, which generates a cryptogram and random number using an encryption key, and sends these to the user device for verification, allowing the user device to authenticate the device without needing to store or manage cryptographic keys.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If public key authentication is implemented between devices, then device authentication security is improved, but deployment and maintenance complexity increases significantly
Solution Approach 1:
The patent introduces a server as an intermediary that manages cryptographic keys centrally. Instead of each device needing to store and manage public keys for every other device, the server acts as a mediator that generates cryptograms using stored encryption keys and delivers them to user devices. This eliminates the need for complex peer-to-peer key management while maintaining authentication security.
Solution Approach 2:
The patent extracts the key management function from individual devices and relocates it to a centralized server. The server stores encryption keys and handles key-related operations, while user devices only need to temporarily store random values and cryptograms during authentication. This extraction of the complex key management function resolves the contradiction by maintaining security while reducing device complexity.
2Adaptability or versatility
If each device stores public keys for authentication, then authentication capability is improved, but storage and processing resources are consumed
Solution Approach 1:
The server serves as an intermediary that provides authentication credentials on-demand. Instead of pre-storing public keys in device memory, the server generates cryptograms containing random values when needed and delivers them to user devices. This approach maintains authentication capability while eliminating the need for substantial key storage in device memory.
Solution Approach 2:
The server performs preliminary actions by pre-storing encryption keys and generating cryptograms before authentication is needed. When a user device requests authentication, the server has already prepared the necessary cryptographic materials, eliminating the need for the device to store and manage multiple public keys in advance.
3Adaptability or versatility
If cryptographic keys are managed on user devices, then authentication independence is improved, but operational simplicity deteriorates
Solution Approach 1:
The server acts as an intermediary that handles the complex cryptographic operations centrally. User devices simply send requests to the server and receive cryptograms, without needing to independently manage key pairs or perform complex cryptographic operations. This maintains authentication functionality while dramatically simplifying device operation.
Solution Approach 2:
The server provides self-service by automatically generating cryptograms, managing encryption keys, and delivering authentication credentials to user devices without human intervention. This automated key management service maintains authentication independence while eliminating the operational burden of manual key management on devices.
Data Source
AI summary
A method for authenticating a device, comprising:sending, from a user device to a server, a data request;retrieving a predetermined encryption key;generating and at least a random and a cryptogram using the encryption key and the random;sending, to the or another user device, the cryptogram and the random, as a data request response;extracting, from the data request response, the random and storing, at least in a temporary manner, the reference random;sending, to at least the device, the cryptogram;decrypting the cryptogram using a predetermined decryption key and obtaining a random;sending, to the user device, the random;verifying whether the received random matches or not the reference random; andauthenticating, only if yes, the device.