Metadata Server Architecture for Software Package Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The management of metadata in software development and deployment faces challenges such as inefficient data retrieval, duplication, and customization of access rights, particularly in storing and linking metadata across multiple data structures.

Innovation Solution

A metadata server system that utilizes a database model with multiple data structures, mapping rules, and operation rules to authorize access and link metadata, enabling efficient storage and retrieval of metadata without duplication, and customizing access rights for users based on their permissions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If metadata is stored across multiple data structures with complex linking, then metadata can be organized and accessed efficiently, but system complexity increases

Engineering Contradiction:
Improvemetadata retrieval efficiencyVSAvoiddata structure complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent segments metadata into multiple specialized data structures (e.g., package metadata, version metadata, file metadata, vulnerability metadata, license metadata) organized in a hierarchical database model. Each data structure stores specific types of metadata with dedicated fields, allowing efficient retrieval while maintaining clear organizational boundaries that reduce overall system complexity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces mapping rules as intermediary components that define relationships between different data structures. These mapping rules act as mediators that connect package metadata to version metadata, file metadata, vulnerability metadata, and license metadata through standardized linkages, enabling efficient cross-structure queries without requiring complex direct connections between all structures.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If access permissions are customized for different users, then security and user control improve, but system complexity increases

Engineering Contradiction:
Improveaccess control securityVSAvoidpermission management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements local quality by associating access permissions specifically with sensitive data structures such as vulnerability metadata and license metadata, rather than applying uniform permission rules across all metadata. This allows customized access control where only certain users or roles can access specific metadata types, improving security while avoiding the complexity of managing permissions for every metadata element.

Inventive Principle:
Principle #3Local quality

3Quantity of substance

If metadata is aggregated from multiple sources, then data completeness improves, but data duplication and management difficulty increase

Engineering Contradiction:
Improvemetadata completenessVSAvoiddata management complexity
Core Design Contradiction:
Quantity of substanceVSDevice complexity

Solution Approach 1:

The patent merges metadata from multiple sources (package information, version data, file details, vulnerability reports, license information) into a unified hierarchical database model. The mapping rules consolidate relationships between these diverse metadata sources, allowing complete metadata aggregation while preventing duplication through standardized reference linkages that connect related metadata without redundant storage.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS12182295B2Metadata storage architecture and data aggregation
Publication Date: 2024.12.31 JFROG LTD
  • US12182295B2 patent drawing
  • US12182295B2 patent drawing
  • US12182295B2 patent drawing

AI summary

The present disclosure is associated with operation of a metadata server for package management including development and deployment of software. To illustrate, a metadata server stores a database model including multiple data structures that each include one or more entries of multiple data objects and a set of mapping rules defining links between different data structures of the multiple data structure. A method of operating the metadata server includes determining access permissions for an entity. The access permissions correspond to authorization to access a set of the multiple data structures. The method further includes identifying and executing a mapping rule to authorize a link between two or more data structures. The method further includes accessing a portion of requested metadata from the two or more data structures that have an authorized active link, and providing an output of the portion of the requested metadata arranged according to an output format.