Indirect Addressing for Detachable Data Library ID Mapping

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Archived content created with one content management system is difficult to retrieve and access using a different system due to compatibility issues and file identifier collisions.

Innovation Solution

A detachable library system is implemented using a layer of indirect addressing with both library scope IDs and node scope IDs, allowing data files to be decoupled from their original database instance, preventing file identifier collisions and enabling efficient attachment to new databases without modifying file pointers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Duration of action of stationary object

If archived content is stored using a different content management system, then long-term storage and archival capabilities are improved, but retrieval and access using a new content management system becomes difficult

Engineering Contradiction:

Improvearchival storage durationVSAvoidcontent retrieval ease

Core Design Contradiction:

Duration of action of stationary objectVSEase of operation

Solution Approach 1:

The system segments the identifier space into two independent components: library scope IDs (embedded in file pointers within the archived content) and node scope IDs (assigned by the database instance). This segmentation allows the archived content to maintain its original library scope IDs while the new database assigns its own node scope IDs, enabling seamless retrieval without compatibility issues.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary mapping mechanism that translates between library scope IDs and node scope IDs. When content is archived, the system creates a mapping between the original library scope IDs and the new database's node scope IDs, allowing the new content management system to access archived content through this intermediary layer without direct dependency on the original system's identifier scheme.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Adaptability or versatility

If file pointers are updated to adapt archived content to a new system, then compatibility with the new content management system is improved, but the complexity and risk of data modification increases

Engineering Contradiction:

Improvesystem compatibilityVSAvoidpointer modification complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system performs preliminary action by pre-assigning node scope IDs to all data files during the archiving process, before the content needs to be accessed by the new system. This preliminary assignment of identifiers and creation of mapping relationships eliminates the need for complex pointer updates later, as the translation layer is already in place.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The mapping mechanism serves as an intermediary that translates library scope IDs to node scope IDs, allowing the system to achieve compatibility without modifying the original file pointers. The intermediary layer handles the translation transparently, preserving the original content structure while enabling access through the new system.

Inventive Principle:

Principle #24Intermediary (Mediator)

3Ease of manufacture

If a simple identifier system is used, then ease of implementation is improved, but file identifier collisions occur when attaching libraries to different databases

Engineering Contradiction:

Improveimplementation simplicityVSAvoididentifier collision avoidance

Core Design Contradiction:

Ease of manufactureVSReliability

Solution Approach 1:

The identifier system is segmented into two independent components: library scope IDs (simple, embedded in file pointers) and node scope IDs (assigned by database instance). This segmentation maintains implementation simplicity for file pointers while ensuring reliability through the combined two-level namespace that prevents collisions across different databases.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent adds another dimension to the identifier system by introducing node scope IDs as a second level of identification. Instead of relying on a single identifier that must be globally unique, the system uses a two-dimensional namespace (library scope ID, node scope ID), which prevents collisions while maintaining simplicity in each individual component.

Inventive Principle:

Principle #17Another dimension (Dimensionality change)

Data Source

PatentUS10678856B1System and method to represent physical data pointers of movable data library

Publication Date: 2020.06.09 EMC IP HLDG CO LLC

AI summary

In general, embodiments of the technology relates to a method for attaching a detachable library. The method includes obtaining a detachable library, wherein the detachable library comprises a plurality of data files and each of the data files comprises a library scope identifier (ID), and where the library scope IDs are unique within the detachable library and reattaching the detachable library to a database. The method further includes assigning a node scope ID to each of the data files in the detachable library, where the node scope IDs are unique within the database, creating a mapping index using the node scope IDs and the library scope IDs, and processing a request from a client using the mapping index, where the request includes a library scope ID.