Server-Mediated Device Authentication Without User-Side Key Storage

Resolve Bottlenecks,
Find Innovative Solutions
Generate 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 encrypts a random number using an encryption key and sends a cryptogram and the random number back to the user device. The user device decrypts the cryptogram using a predefined decryption key and verifies the random number to authenticate the device, without needing to store or manage cryptographic keys.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If public key authentication is used for device authentication, then authentication security is improved, but deployment and maintenance complexity increases

Engineering Contradiction:
Improveauthentication securityVSAvoiddeployment and maintenance complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a server as an intermediary that holds the encryption key and performs the cryptographic operations. The server receives data requests from user devices, generates encrypted random numbers using the encryption key, and sends them to user devices. This mediator approach allows authentication without requiring user devices to store or manage cryptographic keys, thus maintaining security while reducing complexity at the user device level.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent extracts the cryptographic key management functionality from the user device and relocates it to the server. By taking out the key storage and key-based encryption operations from the user device, the system eliminates the need for user devices to handle sensitive cryptographic materials, thereby simplifying deployment and maintenance while preserving authentication security through server-side key management.

Inventive Principle:
Principle #2Taking out (Extraction)

2Adaptability or versatility

If cryptographic keys are stored on user devices for authentication, then authentication capability is improved, but memory footprint and security requirements increase

Engineering Contradiction:
Improveauthentication capabilityVSAvoidmemory footprint
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The server acts as an intermediary that provides cryptographic services to user devices without requiring keys to be stored on the user devices. The server generates encrypted random numbers on-demand in response to data requests, allowing user devices to perform authentication operations with minimal local storage requirements while maintaining full authentication capability through server-supported cryptographic operations.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent employs ephemeral random numbers that are generated on-demand by the server and used temporarily for authentication purposes. These short-lived cryptographic values are discarded after use, eliminating the need for persistent key storage on user devices. The encrypted random numbers serve their authentication purpose and are then discarded, reducing memory footprint while maintaining authentication versatility.

Inventive Principle:
Principle #27Cheap short-living objects (Disposable)

Data Source

PatentEP4179443B1Method, user device, server, device and system for authenticating a device
Publication Date: 2026.03.11 THALES DIS FRANCE SA
  • EP4179443B1 patent drawingFigure 1~2

AI summary

A method (20) for authenticating a device (12), comprising: - sending (22), from a user device (14) to a server (18), a data request; - retrieving (24) a predetermined encryption key; - generating (26) and (28) at least a random and a cryptogram using the encryption key and the random; - sending (210), to the or another user device, the cryptogram and the random, as a data request response; - extracting (212), from the data request response, the random and storing (214), at least in a temporary manner, the reference random; - sending (216), to at least the device, the cryptogram; - decrypting (218) the cryptogram using a predetermined decryption key and obtaining (220) a random; - sending (222), to the user device, the random; - verifying (224) whether the received random matches or not the reference random; and - authenticating (226), only if yes, the device.