Cloud Storage Mount Point for Stateless Remote Sessions
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional software programs designed for local file systems face challenges in cloud environments, where remote execution requires efficient and secure access to user storage, especially for anonymous users, and existing solutions like data duplication or synchronization are inefficient and insecure, especially with large data sets and across geographical locations.
Innovation Solution
A method that intercepts file enumeration and operation requests to simulate local cloud storage access, allowing users to interact with remote storage as if it were local, with data downloaded only when needed, and securely managed, enabling stateless sessions and minimal trust relationship between users and providers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If user data is duplicated to remote servers before session begins (roaming profiles), then users can access their files in remote execution environments, but network traffic increases proportionally with data size and synchronization time becomes overwhelming
Solution Approach 1:
The patent extracts only the necessary file metadata and indexes from the remote storage system, transferring minimal information to the execution server while leaving the actual file data on the remote storage. This allows the application to access files through the mounted cloud storage drive without transferring the entire user profile or data set, dramatically reducing network traffic while maintaining file access capability.
Solution Approach 2:
The patent introduces a cloud storage drive mount point as an intermediary layer between the application and remote storage. This mount point appears as a standard local drive to the application, providing transparent access to remote files without requiring direct network connections or data transfer. The intermediary handles the abstraction between local file system expectations and remote storage reality.
2Ease of operation
If entire user storage is synchronized between cloud storage and execution server, then users can access and modify their files in remote environments, but security risks increase as copied data becomes the weakest link in data protection
Solution Approach 1:
The patent extracts only the necessary interface and metadata for file access, leaving the actual sensitive data on the secure cloud storage server. By not copying the entire user storage profile to the execution server, the system eliminates the security risk of having replicated data on potentially less secure server infrastructure, while still enabling full file access functionality through the mounted cloud drive.
3Adaptability or versatility
If traditional software applications are run on remote servers with cloud storage access, then software can be accessed from any location, but applications designed for local file systems cannot directly work with cloud storage
Solution Approach 1:
The patent introduces a cloud storage drive mount point as an intermediary that bridges traditional local file system applications and remote cloud storage. This mount point presents itself as a standard local drive letter (e.g., Z:), allowing applications to access cloud files using conventional local file system calls without requiring any modifications to the application or complex cloud-specific API integration.
Solution Approach 2:
The patent creates a virtual copy of the cloud storage interface at the local drive mount point, providing applications with a local-like view of remote files. This copy maintains the same interface and operation model as local storage while dynamically connecting to the actual remote storage backend, enabling seamless compatibility without data duplication.
4Ease of operation
If cloud storage is mounted as a local drive for application access, then applications can interact with cloud storage transparently, but file operations require downloading data which increases network traffic
Solution Approach 1:
The patent segments file operations into two types: metadata operations (directory listing, file information) and data operations (actual file content transfer). Metadata operations can be performed with minimal network traffic by transferring only necessary file descriptors and indexes. Data operations only transfer files when actually opened or modified, rather than pre-downloading everything, thus segmenting and optimizing network usage based on actual application needs.
Data Source
AI summary
A computerized method of managing a computer remote session operation, comprising providing a server for hosting application execution; configuring a number of predefined user accounts with low security permissions on said server, where said user accounts are not tied to any specific real user; Whenever a remote user requests to start a remote session, finding an available user account not currently in use on said computer, allocating it for the remote session and marking it as unavailable for subsequent session requests; Generating a one-time password for said user account; Communicating the assigned user account identifier and temporary password to client component on the user's side, either directly or through an intermediate broker; causing the client component to connect to the server using said user account identifier and temporary password; and, upon termination of the remote session, deleting the assigned user account's data and marking it as available again.