CAS Metadata Replication for Searchable Content Retrieval

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current CAS systems fail to enable efficient searching for content stored in content addressable storage by application servers that did not initially store the content, as they lack searchable metadata and require direct knowledge of GUIDs.

Innovation Solution

Implement a system where metadata associated with content is stored and replicated across multiple CAS servers, allowing application servers to search locally and query CAS servers for content, with results compiled and returned to the user.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If content is stored in CAS systems with only GUID-based indexing, then storage efficiency and data integrity are improved, but searchability and data retrieval capability deteriorate

Engineering Contradiction:
Improvedata integrityVSAvoidsearchability
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent introduces metadata as an intermediary layer between the CAS storage system and application servers. This metadata contains searchable attributes (author, date, description) that act as a mediator, allowing application servers to search for content without needing to know the underlying GUIDs or storage locations in the CAS system.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the data retrieval function into two independent parts: (1) CAS servers maintain GUID-based indexing for data integrity and storage efficiency, and (2) application servers use metadata for searching and retrieval operations. This segmentation allows each component to optimize for its specific function without compromising the other.

Inventive Principle:
Principle #1Segmentation

2Speed

If application servers store content locally, then retrieval speed is improved, but system complexity and data redundancy increase

Engineering Contradiction:
Improveretrieval speedVSAvoidsystem complexity
Core Design Contradiction:
SpeedVSDevice complexity

Solution Approach 1:

Instead of requiring application servers to store complete copies of all content (excessive action), the system allows them to store only necessary metadata (partial action). This enables fast local search and retrieval for recently accessed content while avoiding the complexity and redundancy of storing entire content files at multiple locations.

Inventive Principle:
Principle #16Partial or excessive action

3Ease of operation

If metadata is stored with CAS content, then searchability is improved, but storage requirements and system complexity increase

Engineering Contradiction:
ImprovesearchabilityVSAvoidstorage requirements
Core Design Contradiction:
Ease of operationVSQuantity of substance

Solution Approach 1:

The patent extracts metadata from the content storage system and stores it separately in a dedicated metadata repository. This separation allows the CAS system to maintain its simple GUID-based indexing for content storage while the metadata is indexed separately for search operations, avoiding the complexity of integrating metadata into the CAS storage structure.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS20260072991A1System and methods for metadata management in content addressable storage
Publication Date: 2026.03.12 DATCARD SYST
  • US20260072991A1 patent drawing
  • US20260072991A1 patent drawing
  • US20260072991A1 patent drawing

AI summary

Provided is a content addressable storage (CAS) system that allows a user to request, either through an application server or directly to one or more CAS servers, files and content related to a query. In some embodiments, the content can be discovered by searching previously-stored metadata related to each file at the content addressable storage server. The search can also be replicated across multiple content addressable storage servers in order to obtain varied results and redundant results. Duplicate results may be flagged or omitted, ˜d the results are returned to the requester.