Object Addressable Storage Content Lineage Tracking
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional file systems and web content tracking methods are inadequate for reliably identifying the lineage of content units due to modifications, deletions, and location changes, making it difficult to prove source content derivation.
Innovation Solution
An object addressable storage system uses unique object identifiers independent of storage location, allowing metadata to identify source content units regardless of storage changes, and employs architectures like CDF/blob or XAM X-Set to associate metadata with content units, tracking lineage through object identifiers and algorithms.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traditional file systems or web content tracking methods are used to identify content lineage, then the system is simpler to implement, but the reliability of lineage identification deteriorates due to modifications, deletions, and location changes
Solution Approach 1:
The system segments content identification into two independent parts: content-addressable identifiers (hashes of actual content) and metadata identifiers. This segmentation allows the content itself to serve as the reliable key, while metadata stores auxiliary information about lineage relationships, thereby improving reliability without requiring a completely complex new system architecture.
Solution Approach 2:
The patent introduces metadata as an intermediary layer between content units and their lineage relationships. Instead of directly tracking content through fragile file paths or web URLs, the system uses metadata objects that reference content-addressable identifiers, providing a stable intermediary that maintains lineage information even when physical storage locations change.
2Adaptability or versatility
If content location changes in block I/O storage systems, then storage flexibility improves, but the ease of operation deteriorates because host computers must be made aware of location changes
Solution Approach 1:
The system implements self-service through content-addressable storage where the content itself (via its hash) serves as the identifier. When content moves locations, the content-addressable identifier remains unchanged, and the system automatically updates internal mappings without requiring host computers to be aware of or manually update location information, thus maintaining ease of operation while improving adaptability.
Solution Approach 2:
The patent transitions from one-dimensional file path or URL-based identification to a multi-dimensional system where content is identified by its cryptographic hash (content dimension) while metadata stores location and lineage information (storage dimension). This dimensional separation allows location changes in one dimension without affecting identification in another dimension.
3Measurement precision
If metadata is stored to track content lineage, then lineage verification capability improves, but the loss of information increases due to additional storage requirements
Solution Approach 1:
The system changes the parameter of content identification from human-readable filenames or URLs to cryptographic hashes of the actual content. This parameter change enables precise lineage verification through deterministic hashing while minimizing metadata storage requirements, as the hash serves both as a compact content identifier and a verification mechanism without requiring separate large-scale indexing structures.
Data Source
AI summary
Embodiments of the invention relate to determining the lineage of a content unit stored on an object addressable storage (OAS) system. When a content unit that is derived from at least one other content unit is stored on an OAS system, metadata that identifies the source content unit(s) from which the at least one content unit was derived may be stored. This metadata may be subsequently used to determine the lineage of the content unit.