Asymmetric Key Registration Resumption Without Client-Side Data Caching

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for resuming device registration processes, such as those involving virtual SIMs for network access, face security risks due to reliance on client-side caching or time-constrained access tokens, leading to potential loss of engagement with customers who pause the registration process.

Innovation Solution

A service registers a user device using an asymmetric key pair, storing the public key with a session identifier, and authenticates digital signatures from the user device to securely resume the registration process across multiple sessions, ensuring data integrity and continuity.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If the service provider caches user data on the client side using cookies, then the customer can resume registration without reentering data, but the security of sensitive user data is compromised

Engineering Contradiction:
ImproveRegistration resumption convenienceVSAvoidData security
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent introduces a session identifier as an intermediary element that enables registration resumption without exposing sensitive user data. The session ID acts as a mediator between the service provider's server-side storage and the client device, allowing the customer to resume registration conveniently while the actual sensitive data remains securely stored on the server, not cached on the client side.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If the service provider uses OAuth access tokens to cache user-specific data on the server side, then data security is improved, but the registration process must restart when the token expires

Engineering Contradiction:
ImproveData securityVSAvoidRegistration session duration
Core Design Contradiction:
ReliabilityVSDuration of action of moving object

Solution Approach 1:

The patent changes the temporal parameter of session validity by implementing persistent session identifiers that remain valid indefinitely or for extended periods, unlike time-constrained OAuth tokens. This allows the registration session to maintain its validity across days or weeks, enabling customers to resume registration at their convenience without being constrained by token expiration timelines.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If the service requires immediate account creation during registration, then security is maintained, but customer engagement is lost when customers pause the process

Engineering Contradiction:
ImproveAccount securityVSAvoidRegistration completion rate
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent implements preliminary action by creating a temporary registration session with a session identifier before requiring full account creation. This allows customers to begin the registration process, provide some information, and pause without completing full account setup. The session is preserved on the server, enabling customers to resume later and complete registration when ready, thereby improving engagement while maintaining security through server-side validation.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12604291B2Secure process for device registration with a service
Publication Date: 2026.04.14 T MOBILE INNOVATIONS LLC
  • US12604291B2 patent drawing
  • US12604291B2 patent drawing
  • US12604291B2 patent drawing

AI summary

Technology is disclosed herein for registering a user device with a service. In an implementation, a service receives a request from a user device to begin a registration process. The request includes registration data and the public key of an asymmetric key pair. The service stores the public key in association with a session identifier and sends the session identifier to the user device. The service receives a later request from the user device to continue the registration process. The later request includes the session identifier and a digital signature created using the private key of the key pair. The service authenticates the digital signature based on the public key which is retrieved based on the session identifier. In response to authenticating the digital signature, the service sends the registration data associated with the request to the user device and registers the user device based on the registration data.