Metaverse Knowledge Graph for Cross-Platform Interoperability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The industrial metaverse lacks interoperability across various platforms, leading to scattered data and different hardware/software requirements, making it difficult to connect and synchronize data, and there is a need for real-time interactivity and reusability of virtual entities and environments across platforms.

Innovation Solution

A metaverse knowledge graph is used to describe the semantics and relationships between entities, enabling seamless integration and synchronization across platforms by storing information in a graph database, allowing for bidirectional communication and updates without requiring a full re-run of the development pipeline.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If data is scattered across multiple platforms with different data models and terminologies, then each platform can maintain its own specialized functionality, but interoperability and data connection between platforms become difficult

Engineering Contradiction:
Improveplatform specializationVSAvoiddata interoperability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces an intermediary layer (translation service, ontology mapping, or standardized interface) between different metaverse platforms to enable data exchange. This intermediary translates data models and terminologies between platforms, allowing specialized platforms to maintain their functionality while achieving interoperability through the mediating translation layer.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of manufacture

If different platforms require different hardware and software, then each platform can be optimized for its specific function, but system complexity and integration difficulty increase

Engineering Contradiction:
Improveplatform optimizationVSAvoidsystem integration
Core Design Contradiction:
Ease of manufactureVSDevice complexity

Solution Approach 1:

The patent implements a universal interface standard or common protocol that allows different platforms to communicate through a standardized method. This enables each platform to be optimized for its specific function while the universal interface handles the complexity of integration, reducing overall system complexity.

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

3Reliability

If synchronization requires re-running the entire development pipeline, then data consistency can be ensured, but time consumption and processing efficiency decrease

Engineering Contradiction:
Improvedata consistencyVSAvoidsynchronization time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent implements preliminary actions by pre-establishing data validation rules, conflict resolution strategies, and incremental synchronization protocols. This allows the system to perform targeted updates rather than re-running entire pipelines, maintaining data consistency while reducing synchronization time through pre-prepared synchronization mechanisms.

Inventive Principle:
Principle #10Preliminary action

4Productivity

If virtual entities and environments are created for one platform, then development efficiency for that platform improves, but reusability across other platforms is limited

Engineering Contradiction:
Improvedevelopment efficiencyVSAvoidcross-platform reusability
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The patent segments virtual entities and environments into modular, platform-agnostic components that can be independently developed and then assembled on different platforms. This segmentation allows entities to be created efficiently for one platform while maintaining the ability to reuse them elsewhere through modular composition.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS20240037292A1Knowledge graph for interoperability in industrial metaverse for engineering and design applications
Publication Date: 2024.02.01 SIEMENS CORP
  • US20240037292A1 patent drawing
  • US20240037292A1 patent drawing
  • US20240037292A1 patent drawing

AI summary

System and method enable development of an industrial metaverse used in engineering by computer aided design. A metaverse pipeline includes a plurality of metaverse entities including at least one design application and one simulation application configured to develop a virtual environment metaverse representation of an industrial facility. A metaverse knowledge graph describes semantics and relationships between the metaverse pipeline entities and is configured to exchange information across the software applications of the metaverse pipeline entities of various platforms while developing the virtual environment metaverse. The metaverse knowledge graph enables synchronization across metaverse development platforms, such that updates to one platform are transferrable, whereby the virtual entities and environment can be assimilated according to new edits.