Shared Device Authentication with Remote Apps and Temporary Memory

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

In shared devices, configuring multiple user login methods and applications is cumbersome and creates security risks due to residual login information, making them vulnerable to hacking.

Innovation Solution

Storing authentication modules and applications off-device on a remote server, temporarily loading them into non-resident memory for user authentication and application execution, then deleting them after use to prevent residual data.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple users log into a shared device with different applications, then user accessibility and functionality are improved, but security deteriorates due to residual login information remaining on the device

Engineering Contradiction:

Improveuser accessibilityVSAvoidsecurity risk

Core Design Contradiction:

Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The patent extracts authentication modules and applications from local device storage and relocates them to a remote server. The shared device only temporarily caches these modules in volatile memory during active use, then completely removes them after the user session ends. This extraction eliminates residual login information from persistent storage while maintaining user accessibility during the session.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The system dynamically loads authentication modules and applications into volatile memory only when needed during a user session, and dynamically removes them after use. This dynamic approach allows multiple users to access different applications without leaving residual data, as the memory is cleared between sessions.

Inventive Principle:

Principle #15Dynamics

2Productivity

If authentication modules and applications are stored locally on the shared device, then access speed and functionality are improved, but security deteriorates due to persistent residual data

Engineering Contradiction:

Improveaccess speedVSAvoidresidual data

Core Design Contradiction:

ProductivityVSObject-affected harmful factors

Solution Approach 1:

The patent removes authentication modules and applications from permanent local storage and stores them on a remote server. The shared device uses temporary volatile memory for active sessions, which is automatically cleared after use, eliminating residual data while maintaining fast access during the session.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The system discards authentication modules and applications from volatile memory after the user session ends, preventing residual data from remaining on the device. The modules are recovered from the remote server and reloaded when the next user needs them, ensuring both security and availability.

Inventive Principle:

Principle #34Discarding and recovering

3Adaptability or versatility

If the device is configured to support multiple user login methods and applications, then versatility is improved, but device complexity increases

Engineering Contradiction:

Improvemulti-user compatibilityVSAvoidconfiguration complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a universal architecture where a single shared device can support multiple users and applications through a centralized remote server. The server provides authentication modules and applications as services, allowing the shared device to serve multiple functions without complex local configuration for each user or application type.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

The remote server acts as an intermediary between multiple users and the shared device. It provides a centralized management layer that handles authentication, application distribution, and user-specific configuration, simplifying the shared device's architecture while maintaining multi-user compatibility.

Inventive Principle:

Principle #24Intermediary (Mediator)

4Object-affected harmful factors

If authentication modules and applications are stored on a remote server, then security is improved by eliminating residual data, but access time and connectivity requirements worsen

Engineering Contradiction:

ImprovesecurityVSAvoidauthentication load time

Core Design Contradiction:

Object-affected harmful factorsVSLoss of time

Solution Approach 1:

The system performs preliminary actions by pre-loading authentication modules and applications into volatile memory before the user needs them. This caching strategy reduces authentication load time during active sessions while maintaining security, as the modules are already in memory and only removed after the session ends.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS12355766B2Secure authentication and execution of applications on shared devices

Publication Date: 2025.07.08 XEROX CORP

AI summary

A method is disclosed. For example, the method executed by a processor of a shared device includes receiving an identification of a user, connecting to a remote server that stores authentication modules and applications, requesting an authentication module and an application stored on the remote server that is associated with the identification of the user, storing the authentication module and the application temporarily on a non-resident memory of the shared device, and executing the application in response to authentication of the user based on log-in information that was received via the authentication module.