Meta-Tag Configuration Transformation for Heterogeneous Vendor Equipment

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Cloud computing deployments with heterogeneous vendor equipment face challenges in provisioning and lifecycle management due to vendor-specific configuration models, leading to inefficiencies and a lack of scalability in configuring network fabrics with diverse terminology.

Innovation Solution

Implementing a meta-tagging technique that clusters similar network function terms using natural language processing (NLP) and knowledge graphs to create a vendor-agnostic configuration, allowing for a declarative approach to provisioning by abstracting vendor-specific details and enabling seamless policy enforcement across heterogeneous systems, using a meta-tagging based configuration transformation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If vendor-specific configuration models are used for heterogeneous equipment, then each vendor's equipment can be configured according to its native terminology, but the system complexity increases and scalability decreases when managing diverse vendor equipment

Engineering Contradiction:
Improvecompatibility with vendor-specific equipmentVSAvoidconfiguration management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary layer consisting of meta-tags and knowledge graphs that mediate between the generic configuration requests and vendor-specific equipment. This intermediary translates generic terms into vendor-specific terminology through semantic matching, allowing the system to manage heterogeneous equipment without directly handling each vendor's native configuration models, thus reducing system complexity while maintaining adaptability

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the configuration management system into distinct layers: a generic configuration layer using standardized terms, a translation layer using meta-tags and knowledge graphs, and vendor-specific equipment layers. This segmentation allows each layer to operate independently with its own terminology, reducing the complexity of managing vendor-specific configurations while maintaining compatibility through the segmented architecture

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If vendor-specific configuration models are used for heterogeneous equipment, then each vendor's equipment can be configured according to its native terminology, but the provisioning process becomes less efficient and automated

Engineering Contradiction:
Improvecompatibility with vendor-specific equipmentVSAvoidprovisioning efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The intermediary translation layer using meta-tags and knowledge graphs enables automated translation between generic configuration requests and vendor-specific commands. This automation eliminates manual intervention required for vendor-specific configuration, thereby improving provisioning efficiency while maintaining compatibility with diverse vendor equipment through the intermediary translation mechanism

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent changes the parameter representation from vendor-specific native terms to generic standardized terms in the configuration requests. By transforming the configuration parameters into a vendor-agnostic format and using semantic matching to map to vendor-specific implementations, the system achieves automated provisioning across heterogeneous equipment without sacrificing compatibility

Inventive Principle:
Principle #35Parameter changes

3Adaptability or versatility

If vendor-specific configuration models are used for heterogeneous equipment, then each vendor's equipment can be configured according to its native terminology, but the lack of uniform configuration interface deteriorates user experience

Engineering Contradiction:
Improvecompatibility with vendor-specific equipmentVSAvoidconfiguration interface uniformity
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The intermediary translation layer provides a uniform configuration interface to users by accepting generic standardized terms and automatically translating them to vendor-specific terminology. Users interact with a consistent, vendor-agnostic interface while the intermediary handles the complexity of vendor-specific variations, thereby improving ease of operation while maintaining compatibility with diverse equipment

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent creates a universal configuration interface that can handle multiple vendor-specific equipment types through a single standardized interface. The generic configuration terms and meta-tag system provide multi-functionality, allowing the same interface to work across different vendors by translating to their respective native terminologies, thus achieving both uniformity and adaptability

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

Data Source

PatentUS20250371270A1Meta-Tagging Based Configuration Transformation for Heterogeneous Systems
Publication Date: 2025.12.04 DELL PROD LP
  • US20250371270A1 patent drawing
  • US20250371270A1 patent drawing
  • US20250371270A1 patent drawing

AI summary

A system can identify respective computer function terms utilized by respective vendor equipment of computer function vendors; tag the respective computer function terms in a latent space based on natural language processing, to produce respective clusters; associate respective metatags with the respective clusters based on respective semantic meanings; receive a request to perform a computer function, wherein the request comprises a generic term; identify hardware with which to perform the computer function based on the respective metatags; identify equipment of a computer function vendor, of the vendor equipment of the respective computer function vendors, which corresponds to the hardware; based on the respective metatags and respective clusters, identify a computer function term of the respective computer function terms used by the equipment of the computer function vendor, wherein the computer function term corresponds to the generic term; and carry out the request using the hardware with the computer function term.