Local File Sharing Record for On-Demand Transfer

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Storing shared files on a third-party device consumes communication and networking resources, and users without network access cannot access these files, while also consuming memory resources on the third-party device.

Innovation Solution

Storing files only locally on the computing devices accessed by users and initiating sharing or sending files only after they have been modified, thereby reducing the need for communication when files are not being modified and avoiding the need for storage on additional devices.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If shared files are stored on a third-party device, then file accessibility is improved, but communication and networking resources are consumed continuously and memory resources on the third-party device are used

Engineering Contradiction:
Improvefile accessibilityVSAvoidcommunication resources consumption
Core Design Contradiction:
Ease of operationVSLoss of energy

Solution Approach 1:

The system performs preliminary actions by storing sharing records locally before any file access occurs. When a file is modified, the system proactively initiates the transfer to the recipient device, eliminating the need for continuous communication checks or server-mediated access. This preliminary local record-keeping enables on-demand transfers only when necessary.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent creates a local copy of the sharing metadata (sharing record) on the user's device, which contains essential information about shared files and recipients. This copying eliminates the need to continuously query or access the third-party server, as all necessary sharing information is locally available and can be acted upon independently.

Inventive Principle:
Principle #26Copying

2Adaptability or versatility

If shared files are stored on a third-party device, then file sharing capability is improved, but device memory resources are consumed on the third-party device

Engineering Contradiction:
Improvefile sharing capabilityVSAvoidmemory resources on third-party device
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The patent extracts only the essential sharing metadata (file identifier, recipient information, sharing permissions) from the complete file and stores it locally as a sharing record. The actual file content remains on the user's device or is transferred only when needed, eliminating the need to store large files on third-party servers and reducing memory consumption on external devices.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system segments the file sharing functionality into two parts: (1) local storage of sharing records with minimal metadata, and (2) on-demand transfer of actual file content. This segmentation allows the system to maintain file sharing capability while avoiding continuous occupation of third-party device memory, as files are transferred only when modification occurs.

Inventive Principle:
Principle #1Segmentation

3Stability of the object's composition

If files are transferred immediately upon every modification, then file synchronization is improved, but communication resources are consumed unnecessarily when files are not modified

Engineering Contradiction:
Improvefile synchronizationVSAvoidcommunication resource efficiency
Core Design Contradiction:
Stability of the object's compositionVSProductivity

Solution Approach 1:

Instead of continuous or immediate transfer upon every minor change, the system implements periodic action by triggering file transfers only at specific intervals or under specific conditions - namely, when the user explicitly saves or finalizes modifications. This periodic transfer approach maintains synchronization when needed while avoiding unnecessary communication during idle periods or minor edits.

Inventive Principle:
Principle #19Periodic action

Solution Approach 2:

The system performs preliminary local processing of file modifications, tracking changes in the local sharing record, and only initiates communication with the recipient when the modification is complete and ready to be shared. This preliminary local action ensures synchronization is maintained efficiently without premature or unnecessary communication.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS11449471B2Sharing a modified file
Publication Date: 2022.09.20 GOOGLE LLC
  • US11449471B2 patent drawing
  • US11449471B2 patent drawing
  • US11449471B2 patent drawing

AI summary

A method can include, in response to receiving sharing input from a local user into a local computing device, sending a file from the local computing device to a recipient, in response to sending the file, storing a sharing record on the local computing device, the sharing record identifying the file and the recipient, in response to receiving modification input from the local user into the local computing device to modify the file, determining that the sharing record identifies the file and the recipient, and based on determining that the sharing record identifies the file and the recipient, initiating sending at least a portion of the file to the recipient.