Remote File Fetch via Roaming List and Intermediary Server

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems face challenges in accessing application files saved on one device from another device remotely due to differences in local memory, requiring users to anticipate file needs and use servers or synchronize files peer-to-peer, which wastes resources and requires forethought.

Innovation Solution

An electronic file fetch system that allows users to register devices with a web service, generating a roaming file list of application files on one device, enabling seamless access and download of these files to another device by checking the machine state and establishing communication connections.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If application files are saved locally to a hard drive or memory component of a first machine, then the files are easily accessible via the first machine, but the files are not easily accessible via a second remote machine

Engineering Contradiction:
Improvefile accessibilityVSAvoidcross-device access capability
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent introduces a server as an intermediary between client devices and stored files. The server receives a roaming file list from a first client device, stores this list, and enables second client devices to access files remotely through the server, eliminating the need for direct peer-to-peer connections or local storage on multiple devices

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent transitions from local file storage (two-dimensional: device and folder structure) to a three-dimensional architecture by adding the server layer. Files are accessible through multiple dimensions: locally on any device, remotely via the server, and through the roaming file list mechanism that bridges devices without requiring physical file transfer

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Ease of operation

If the user saves the application file to a server hosted location, then the user can access the file via the second machine, but this requires forethought and sufficient server space

Engineering Contradiction:
Improveremote file accessVSAvoiduser action requirements
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The system performs preliminary action by automatically capturing the roaming file list from the first client device and storing it on the server. This eliminates the need for users to manually anticipate file needs or perform save operations to server locations, as the system proactively prepares the file list for future remote access

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system enables self-service by automatically managing the file list storage and retrieval process. The server automatically receives and stores the roaming file list, and automatically provides file access to registered devices without requiring user intervention in the storage or retrieval operations

Inventive Principle:
Principle #25Self-service

3Adaptability or versatility

If the application file is synched between machines peer-to-peer, then the user can access the file from either machine, but this requires additional resources and wastes device resources

Engineering Contradiction:
Improvemulti-device file accessVSAvoiddevice resource consumption
Core Design Contradiction:
Adaptability or versatilityVSUse of energy by moving object

Solution Approach 1:

The server acts as an intermediary that consolidates the roaming file list from the first client device and makes it available to second client devices. This eliminates the need for peer-to-peer synchronization between devices, reducing the computational and network resources that would otherwise be required for direct device-to-device file sharing

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the file access function into separate components: the first client device stores the actual application files locally, the server stores and manages the roaming file list, and second client devices access files through the server. This segmentation eliminates the need for continuous peer-to-peer synchronization while maintaining multi-device accessibility

Inventive Principle:
Principle #1Segmentation

4Adaptability or versatility

If the application file is synched peer-to-peer, then the user can access the file from either machine, but this requires the file to be saved in a specific location on the hard drive

Engineering Contradiction:
Improvecross-machine file accessVSAvoidfile location requirements
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The server mediates between client devices by receiving the roaming file list from the first device and providing it to second devices. This intermediary approach eliminates the need for users to specify or remember specific hard drive locations, as the server manages the mapping between devices and files abstractly

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent adds a dimensional layer by introducing the server as an abstract intermediary that decouples physical file locations on specific devices from the logical file access interface. Users interact with files through the server's unified interface rather than navigating specific local paths, providing location-independent access

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

Data Source

PatentUS8965958B2File fetch from a remote client device
Publication Date: 2015.02.24 MICROSOFT TECHNOLOGY LICENSING LLC
  • US8965958B2 patent drawing
  • US8965958B2 patent drawing
  • US8965958B2 patent drawing

AI summary

Techniques for an electronic file fetch system are described. A method may comprise sending a request for a roaming file list to a file fetch server from a first client device and receiving the roaming file list from the file fetch server by the first client device. The roaming file list includes a unique identifier associated with an application file stored on a second client device. The unique identifier includes a machine identifier identifying the second client device and a local file path portion identifying the file path of the application file stored on the second client device. Based on the machine state of the second client device as indicated in the roaming file list, the application file stored on the second client device may be downloaded to the first client device. Other embodiments are described and claimed.