Cloud Content Recognition via Local Storage Registration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current file storage and synchronization systems do not adequately distinguish between locally maintained content and cloud content, failing to recognize cloud content, associate it with corresponding providers, and enable customized handling.

Innovation Solution

A path name or identifier of a designated storage location for cloud content is registered locally, allowing files to be recognized as cloud content and handled accordingly, with visual identifiers and relative paths used to customize the user experience and roam file activities between devices.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If files are handled uniformly without distinction between local and cloud content, then system simplicity is maintained, but cloud content recognition and customized handling capability is lost

Engineering Contradiction:
Improvecloud content recognition capabilityVSAvoidfile handling mechanism complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a cloud content indicator as an intermediary element that marks cloud content files. This indicator acts as a mediator between the file system and applications, enabling recognition of cloud content without fundamentally changing the uniform file handling architecture. The indicator is stored alongside file data and can be read by applications to identify cloud content, thus adding recognition capability while maintaining relative system simplicity.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the file handling process into two independent parts: the uniform file system handling mechanism and the cloud content indicator. By separating the identification function (performed by reading the indicator) from the handling function (performed by the file system), the system achieves cloud content recognition without complicating the core file handling architecture. Applications can selectively read the indicator and apply customized handling only when needed.

Inventive Principle:
Principle #1Segmentation

2Ease of operation

If visual identifiers are added to represent cloud content association, then user experience customization is improved, but interface complexity increases

Engineering Contradiction:
Improveuser experience customizationVSAvoiduser interface complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent employs visual identifiers including color-coded icons or markings that change or differ from standard file icons to indicate cloud content association. These color changes provide immediate visual distinction between local and cloud content, enabling customized user experience without requiring complex interface elements. The visual identifiers are simple graphical markers that can be rendered by existing operating system frameworks, adding clarity without significant interface complexity.

Inventive Principle:
Principle #32Color changes

3Adaptability or versatility

If registered storage locations are used to obtain relative paths, then file activity roaming between devices is enabled, but system complexity increases

Engineering Contradiction:
Improvefile activity synchronization capabilityVSAvoidpath management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent uses relative paths as a copy or reference representation of file locations rather than storing complete absolute paths. By storing only the relative path structure (e.g., 'folder/file.txt') instead of the full path (e.g., 'C:/Users/Name/folder/file.txt'), the system enables file activity to be copied and reproduced on different devices. The actual absolute paths are constructed dynamically by combining the relative path with the device-specific registered storage location, thus enabling roaming while avoiding the need to store and manage complex absolute path information across devices.

Inventive Principle:
Principle #26Copying

Data Source

PatentEP2805252B1Recognizing cloud content
Publication Date: 2020.02.19 MICROSOFT TECHNOLOGY LICENSING LLC
  • EP2805252B1 patent drawingFigure 1
  • EP2805252B1 patent drawingFigure 2
  • EP2805252B1 patent drawingFigure 3

AI summary

Recognizing cloud content techniques are described herein. A designated storage location for cloud content corresponding to a service is registered locally at a device. Files stored in association with the registered storage location may be recognized as cloud content of the corresponding service. The recognized cloud content may be handled in various ways to customize the user experience and tailor interaction with cloud content. For example, icons or other visual identifiers may be used within device, operating system and/or application user interfaces to represent an association of files with a particular service based on recognition of the files as cloud content. Additionally, a registered storage location for a device may be employed to obtain relative paths to files that may be used to roam file activity lists between different devices.