Objectification Engine Namespace Translation for Concurrent Storage Access

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing systems face challenges in accessing data simultaneously via both object and NAS protocols without duplicating data, due to differences in storage semantics between object-based and file-based storage systems.

Innovation Solution

An objectification engine creates symbolic links or direct references within an object namespace to enable concurrent access by both object-based and file-based clients, maintaining a single disk representation of data and adhering to access policies.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If data is duplicated to ensure accessibility via both object and NAS protocols, then data accessibility is improved, but storage space and system resources are wasted

Engineering Contradiction:

Improvedata accessibilityVSAvoidstorage space

Core Design Contradiction:

Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The patent introduces a namespace translation layer that acts as an intermediary between object-based clients and file-based storage systems. This translation layer converts object lookup semantics into file system traversal semantics, enabling single data representation to serve both access patterns without duplication.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The system enables a single data storage infrastructure to serve multiple access protocols (object-based and file-based) simultaneously through a unified namespace translation mechanism, making the storage system universal to both access patterns without requiring separate duplicated data copies.

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If data is duplicated to ensure accessibility via both object and NAS protocols, then data accessibility is improved, but system resources are consumed

Engineering Contradiction:

Improvedata accessibilityVSAvoidsystem resources

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The namespace translation layer serves as an intermediary that eliminates the need for separate data copies by translating between object-based and file-based access semantics, thereby reducing system resource consumption while maintaining accessibility via both protocols.

Inventive Principle:

Principle #24Intermediary (Mediator)

3Ease of operation

If object-based storage uses lookup semantics and file storage uses hierarchical traversal, then each protocol operates efficiently, but data duplication is required to maintain both access patterns

Engineering Contradiction:

Improveprotocol efficiencyVSAvoiddata duplication

Core Design Contradiction:

Ease of operationVSQuantity of substance

Solution Approach 1:

The translation layer acts as an intermediary that receives object lookup requests and translates them into file system traversal operations, or receives file system operations and translates them into object lookup semantics, allowing both protocols to operate efficiently on a single data representation.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent introduces a semantic translation dimension between object-based and file-based access patterns, transforming requests from one paradigm to another without requiring physical data duplication, thereby resolving the contradiction between protocol efficiency and data duplication.

Inventive Principle:

Principle #17Another dimension (Dimensionality change)

Data Source

PatentUS11693908B2System and methods for dynamic generation of object storage datasets from existing file datasets

Publication Date: 2023.07.04 INTERNATIONAL BUSINESS MACHINE CORPORATION

AI summary

A computer-implemented method according to one embodiment includes in response to identifying a match between a file and at least one policy, updating details of a container in an object namespace of a file system, where the object namespace of the file system stores object-based representations of files within the file system; creating a symbolic link to the file in the object namespace of the file system; and updating a database to identify the symbolic link and the details of the container.