Distributed Personal Metadata for Cloud Storage Scalability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional cloud storage systems lack a personalized approach to metadata, leading to scalability issues when multiple users access and modify resources, as all users access a single centralized master copy, which limits flexibility and efficiency in managing user relationships and resource updates.
Innovation Solution
A server system with a manager function that establishes secondary copies of resources for each user, including personal metadata describing the relationship between users and resources, allowing for personalized metadata management and scalable distribution across multiple server units, enabling modular expansion and secure storage within organizations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If a single centralized master copy of a resource is stored for all users, then storage space is optimized and data consistency is maintained, but scalability is limited and personalized metadata management becomes difficult
Solution Approach 1:
The patent segments the centralized metadata into multiple distributed metadata instances, each stored locally at user terminals. Each metadata instance contains user-specific information about the resource, allowing personalized metadata management while maintaining access to the same resource content. This segmentation resolves the contradiction by enabling both storage efficiency (through shared resource content) and personalized metadata management (through distributed metadata instances).
Solution Approach 2:
The patent implements local quality by allowing each user terminal to maintain its own customized metadata instance with user-specific attributes, relationships, and preferences. Each user can have different metadata about the same resource based on their local context, while the resource content itself remains centrally managed. This enables personalized metadata management without sacrificing storage efficiency for the resource content.
2Stability of the object's composition
If all users access the same centralized master copy, then data consistency is maintained, but system scalability and flexibility are reduced
Solution Approach 1:
The patent segments the monolithic centralized access model into a distributed architecture where resource content and metadata are separated. The resource content remains centrally stored for consistency, while metadata is distributed to user terminals. This segmentation allows the system to scale by adding users without requiring changes to the central resource storage, thus improving scalability while maintaining data consistency through the centralized content repository.
Solution Approach 2:
The patent introduces metadata as an intermediary layer between users and the centralized resource content. This metadata layer absorbs the complexity of personalized user interactions, relationships, and preferences, allowing users to access and interact with resources in customized ways without affecting the centralized content storage. The metadata acts as a mediator that enables scalability and flexibility while the centralized content maintains data consistency.
3Device complexity
If metadata is centralized for all users, then synchronization is simplified, but user-specific relationship tracking becomes inefficient
Solution Approach 1:
The patent segments metadata into user-specific instances stored locally at each terminal, with each instance containing only the metadata relevant to that user. This segmentation eliminates the need to synchronize complete metadata sets across all users, reducing synchronization complexity to only essential resource content updates. Meanwhile, user-specific relationship tracking becomes highly efficient since each user has direct access to their customized metadata without querying a centralized system.
Solution Approach 2:
The patent performs preliminary action by pre-populating each user terminal with their own customized metadata instance before the user needs to access resources. This metadata is prepared in advance with user-specific relationships, preferences, and contextual information, enabling immediate efficient access and tracking without requiring real-time synchronization or querying during user operations.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A server system comprising: a respective storage area for each of a plurality of respective parties including a first party and a second party, and a manager function for managing the storage. Each of at least some of the storage areas stores a primary instance of one or more data resources of the respective party. The manager function is configured so as, in response to the second party forming a relationship with one of the resources of the first party, to establish a secondary copy of that one of the resources of the first party in the respective storage area of the second party. In the secondary copy, the manager function also includes personal metadata describing one or more attributes of the relationship between the second party and the resource.