Model Integration Layer for ML Deployment

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Developing software applications that utilize machine learning models is a programming-intensive and time-consuming process, posing challenges in model selection, development, and integration, especially for low-code and no-code software developers.

Innovation Solution

A model integration layer that standardizes the usage of machine learning models within software applications, providing a framework for interconnection and offering capabilities like data format standardization, model selection based on runtime attributes, and transparent model implementation details to software developers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If machine learning models are integrated directly into software applications, then model functionality and accuracy are improved, but development time and programming complexity increase significantly

Engineering Contradiction:
Improvemodel functionalityVSAvoiddevelopment time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

A model integration layer is introduced as an intermediary component between software applications and machine learning models. This layer provides standardized interfaces and abstraction mechanisms that enable applications to utilize model capabilities without direct integration complexity. The integration layer handles model selection, parameter configuration, and inference orchestration, thereby reducing development time while preserving model functionality.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If multiple models are made available for selection, then model accuracy and capability are improved, but model selection complexity and integration effort increase

Engineering Contradiction:
Improvemodel accuracyVSAvoidintegration complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The model integration layer implements universal interfaces and standardized capability descriptions that work across multiple different machine learning models. By defining common abstraction layers and unified interaction protocols, the system enables applications to access diverse model capabilities through a single consistent interface, thereby reducing integration complexity while maintaining access to multiple accurate models.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Productivity

If model-specific data formats are used, then model processing efficiency is improved, but compatibility and ease of use for developers are reduced

Engineering Contradiction:
Improvemodel processing efficiencyVSAvoiddeveloper ease of use
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

The integration layer serves as a format conversion intermediary between application data and model-specific data requirements. It automatically performs data format transformation, feature engineering, and preprocessing tasks, allowing developers to use standardized data formats while models receive optimally formatted input. This maintains processing efficiency while improving ease of use.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Reliability

If models are updated or modified, then model accuracy and performance are improved, but software application stability and consistency are affected

Engineering Contradiction:
Improvemodel accuracyVSAvoidapplication stability
Core Design Contradiction:
ReliabilityVSStability of the object's composition

Solution Approach 1:

The system segments the model lifecycle into independent components: model definition, model training, model selection, and model execution. The integration layer manages model updates by selecting appropriate models based on runtime attributes without requiring application modifications. This segmentation allows model improvements while maintaining application stability through consistent interface contracts.

Inventive Principle:
Principle #1Segmentation

5Adaptability or versatility

If runtime model selection is implemented, then adaptability to different conditions is improved, but system complexity and selection overhead increase

Engineering Contradiction:
Improvemodel adaptabilityVSAvoidselection system complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The integration layer implements runtime model selection by evaluating attribute values and selecting models based on parameter matching. The mapping between attribute values and model selections is configured through declarative specifications rather than complex algorithms. This approach enables adaptability to different runtime conditions while keeping the selection mechanism relatively simple and maintainable.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS12299419B2Unified framework for configuration and deployment of platform intelligence
Publication Date: 2025.05.13 SERVICENOW INC
  • US12299419B2 patent drawing
  • US12299419B2 patent drawing
  • US12299419B2 patent drawing

AI summary

A method includes determining a definition of a capability, where the definition indicates an input, an output, and an operation performed by the capability on the input to generate the output. The method also includes determining models configured to provide the capability, providing the definition of the capability to an application builder configured to provide a model-independent representation of the capability, and determining a mapping that indicates, for each respective model of the models, one or more attribute values that cause the respective model to be executed to provide at runtime the capability to a software application defined using the application builder, where the mapping is unmodifiable by the application builder. The method further includes, in response to reception from the software application of a request to provide the capability, providing the capability to the software application in accordance with the mapping.