Machine Learning Model Registry for Cross-Environment Reuse

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing machine learning model management systems face challenges in efficiently sharing and reusing models across different users and environments due to splintered deployment and the need for retraining, leading to increased costs and inefficiencies.

Innovation Solution

A model registry system that stores and manages machine learning models with metadata and metrics, allowing seamless integration and retrieval across various development environments, supporting both container-based and distributed computing technologies, and operating in an offline mode to reduce network resource consumption.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If machine learning models are deployed in different environments and frameworks across an enterprise, then models can be customized for specific use cases, but it becomes difficult to identify and reuse appropriate models

Engineering Contradiction:
Improvemodel customizationVSAvoidmodel identification
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent introduces a centralized model registry as an intermediary system that stores metadata about machine learning models deployed across different environments. This registry enables users to search and identify appropriate models without needing to know their specific deployment locations, frameworks, or environments. The model registry acts as a mediator between model creators and model consumers, solving the identification problem while preserving deployment flexibility.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If machine learning models are placed in different environments through various phases of the model life cycle, then models can be developed and tested independently, but network resources are consumed during model retrieval

Engineering Contradiction:
Improveindependent developmentVSAvoidnetwork resource consumption
Core Design Contradiction:
ProductivityVSLoss of energy

Solution Approach 1:

The patent implements offline model retrieval capability where the model registry system can download and cache models locally before they are needed. This preliminary action of pre-fetching and storing models locally eliminates the need for network access during model retrieval operations, reducing network resource consumption while maintaining the ability to access models from different development environments.

Inventive Principle:
Principle #10Preliminary action

3Productivity

If machine learning models are stored in a centralized registry, then model reusability increases, but the system requires integration across multiple development frameworks

Engineering Contradiction:
Improvemodel reusabilityVSAvoidsystem integration
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent segments the model management system into distinct functional components: a model registry for storage and metadata management, framework-agnostic interfaces for access, and optional offline caching mechanisms. This segmentation allows the centralized registry to handle model storage and reusability while separate interface layers handle the complexity of integrating with multiple development frameworks, isolating the complexity from the core reusability functionality.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS12393709B2Methods and systems for model management
Publication Date: 2025.08.19 TARGET BRANDS INC
  • US12393709B2 patent drawing
  • US12393709B2 patent drawing
  • US12393709B2 patent drawing

AI summary

Methods, systems, and platforms for managing machine learning models are described. A model registry system receives first data including a model and second data including metadata and at least one metric of the model. Via a local network, the first data is stored to a data storage device and the second data is sent to an application programming interface (API). The first data is retrieved from the data storage device to a model use case program operating in a software development environment native to where the model registry system stores the model. The second data, including the metadata and the at least one metric of the model, is sent to a user interface (UI) via the API. The stored model can be deployed from the model use case program via the API.