Shared File Platform Storage Optimization via Event Log Analysis

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing shared file platforms lack efficient organization and storage optimization capabilities, leading to storage capacity bottlenecks and inefficient user experiences due to unorganized and difficult-to-manage files.

Innovation Solution

A system and method that utilize a shared file organization application with a search engine to automatically sort and display non-actioned parent folders, allowing users to easily remove unnecessary files and optimize storage capacity by analyzing user interactions and events associated with files.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If users manually manage and download files to local storage, then users can access files locally, but local storage resources are quickly occupied and productivity is hampered

Engineering Contradiction:
Improvefile accessibilityVSAvoidlocal storage capacity
Core Design Contradiction:
ReliabilityVSQuantity of substance

Solution Approach 1:

The system creates virtual copies of files in the cloud storage platform rather than requiring physical copies on local devices. Users access files through the shared file platform which provides file-like access (viewing, editing, sharing) without needing to download and store actual file copies locally, thus preserving local storage capacity while maintaining file accessibility.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The shared file platform acts as an intermediary between users and file storage. Instead of users directly managing files on their local devices, all file operations are mediated through the cloud-based platform which handles storage, retrieval, and file management, eliminating the need for local storage occupation while maintaining access.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If users are added as contributors to numerous files, then users can collaborate on more projects, but users accumulate unnecessary files that fill storage space

Engineering Contradiction:
Improvecollaboration capabilityVSAvoidstorage space utilization
Core Design Contradiction:
Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The system automatically identifies and manages unnecessary files through event log analysis and machine learning algorithms. The platform self-services by detecting when users are no longer active contributors to files and automatically removing those files from user profiles and local devices, eliminating manual intervention while maintaining collaboration capabilities.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system continuously monitors user interactions with files through event logs and provides feedback to determine file necessity. By analyzing access patterns, edit history, and collaboration activity, the system dynamically adjusts which files are retained in user profiles, automatically removing files that no longer serve collaborative purposes while preserving actively used files.

Inventive Principle:
Principle #23Feedback

3Quantity of substance

If shared file platforms store vast amounts of information, then storage capacity is maximized, but data becomes unorganized and difficult to sort

Engineering Contradiction:
Improvestorage capacityVSAvoidfile organization
Core Design Contradiction:
Quantity of substanceVSEase of operation

Solution Approach 1:

The system segments the vast storage space into organized hierarchies of folders, teams, and projects. Files are automatically categorized and placed into appropriate segments based on metadata, user relationships, and content analysis, making large volumes of data manageable and navigable while preserving total storage capacity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system replaces manual file organization mechanics with automated intelligent sorting algorithms and machine learning models. Instead of users physically dragging and dropping files into folders, the system automatically analyzes file content, metadata, and usage patterns to organize files into appropriate locations, dramatically improving ease of operation while handling large storage volumes.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

4Ease of operation

If users manually sort and manage files, then storage organization is achieved, but user time and productivity are reduced

Engineering Contradiction:
Improvestorage organizationVSAvoidfile management time
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The system performs file organization autonomously without requiring user intervention. Event log analysis, machine learning algorithms, and automated sorting mechanisms handle file management tasks independently, continuously organizing and optimizing storage structures while users focus on productive work, eliminating time loss associated with manual file management.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system performs preliminary organization actions by pre-categorizing files as they are uploaded or shared, rather than requiring post-upload sorting. Files are automatically tagged, categorized, and placed in appropriate locations during the initial ingestion process, preventing organization backlog and eliminating the need for subsequent manual sorting efforts.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12298943B2Technologies for organizing and optimizing storage capacity of shared file platforms
Publication Date: 2025.05.13 MCKINSEY & CO INC
  • US12298943B2 patent drawing
  • US12298943B2 patent drawing
  • US12298943B2 patent drawing

AI summary

Technologies for organizing and optimizing storage capacity of shared file platforms are disclosed. An example method includes pulling a set of events associated with a user from an event log. Each event in the set of events includes a respective parent folder identification (ID). The example method further includes analyzing, by a search engine, the set of events to determine one or more actioned parent folders corresponding to the set of events; and comparing the one or more actioned parent folders to a list of parent folders associated with the user to determine a non-actioned parent folder. The example method also includes displaying, at a user interface, the non-actioned parent folder to the user; and receiving an input from the user indicating a removal request corresponding to the non-actioned parent folder. The example method may then include removing the user from a collaborator list associated with the non-actioned parent folder.