Self-Describing Objects With Named Metadata Collections

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current object storage systems face challenges in managing multiple collections of user-defined metadata, as existing methods require coordination among producers and consumers to maintain compatibility, which becomes difficult as the number of entities grows, and lack standardization for metadata formats and access control, leading to incompatibilities and security issues.

Innovation Solution

The system allows for multiple named collections of user-defined metadata to be associated with objects, enabling each consumer or producer to create and format annotations as needed, without requiring a standard layout, and provides access control lists for secure and flexible metadata management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a single entity manages all metadata for objects in storage system, then coordination and compatibility are maintained, but the system becomes difficult to scale and manage as the number of producers and consumers grows

Engineering Contradiction:
Improvemetadata management flexibilityVSAvoidcoordination complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent divides metadata management into separate named collections, each independently manageable. Instead of a single centralized metadata entity, the system segments metadata into multiple independent collections that can be created, modified, and managed separately by different producers and consumers without requiring coordination across the entire metadata space.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent creates a universal metadata framework where named collections serve multiple purposes - they can store different types of metadata, support various access control policies, and be managed by different entities simultaneously. This multi-functional approach allows the same infrastructure to handle diverse metadata needs without requiring separate coordination mechanisms for each type.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Productivity

If multiple entities manage metadata independently, then scalability and flexibility improve, but incompatibilities and security issues arise due to lack of standardization

Engineering Contradiction:
Improvemetadata management efficiencyVSAvoidmetadata compatibility
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

By segmenting metadata into named collections with explicit naming conventions, the system allows independent management while maintaining compatibility through the shared namespace framework. Each collection can be managed independently for efficiency, while the overall structure ensures compatibility through standardized naming and access control mechanisms.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies different access control policies and management approaches to different named collections based on their specific requirements. Each collection can have its own security constraints and management rules tailored to its purpose, while still operating within the unified storage system framework that ensures overall compatibility.

Inventive Principle:
Principle #3Local quality

3Reliability

If standard metadata formats are enforced, then compatibility is ensured, but flexibility and ease of modification are reduced

Engineering Contradiction:
Improvemetadata compatibilityVSAvoidmetadata format flexibility
Core Design Contradiction:
ReliabilityVSEase of manufacture

Solution Approach 1:

The system segments metadata into named collections that can use different formats and structures within each collection. This allows each collection to be optimized for its specific purpose while maintaining overall compatibility through the unified named collection framework. Producers and consumers can work with familiar formats within their designated collections without requiring standardization across all metadata.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent allows parameters such as metadata format, structure, and access control policies to be changed on a per-collection basis. This enables flexibility in modifying metadata approaches for different collections while maintaining compatibility through the stable named collection namespace and overall system framework.

Inventive Principle:
Principle #35Parameter changes

4Ease of operation

If access control is applied to entire objects, then security is simplified, but fine-grained control over specific metadata collections is lost

Engineering Contradiction:
Improveaccess control simplicityVSAvoidaccess control granularity
Core Design Contradiction:
Ease of operationVSAdaptability or versatility

Solution Approach 1:

The patent segments access control from the object level to the named collection level. Instead of applying access control uniformly to entire objects, the system allows separate access control policies to be applied to each named collection within an object. This provides fine-grained control while maintaining simplicity through the consistent named collection interface and standardized access control mechanisms.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS10572466B2Multiple collections of user-defined metadata for self-describing objects
Publication Date: 2020.02.25 HITACHI VANTARA LLC
  • US10572466B2 patent drawing
  • US10572466B2 patent drawing
  • US10572466B2 patent drawing

AI summary

Exemplary embodiments provide the ability to associate multiple collections of metadata to objects. In one embodiment, a storage system comprises: a processor; a memory; at least one object, each object including content data; system metadata associated with each object; and a plurality of named collections of user-defined metadata associated with each object. Each named collection of the plurality of named collections is separately addressable by a request. In some embodiments, at least one named collection of user-defined metadata of one object of the at least one object includes an access control list, and the access control list of a named collection specifies permissible access to the named collection. The one object has an object-level access control list which specifies permissible access to the one object and which is different from the access control list for the named collection associated with the one object.