Semantic Information Integrator Using RDF Templates for Model Mapping

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for mapping between multiple semantic models are inefficient and cumbersome, especially when updating mappings for evolving standardized information models or changing use cases, and languages like RML are verbose and difficult to manage.

Innovation Solution

A method for declarative mapping of domain-specific data into standardized information models using mapping templates, involving a semantic information integrator module that utilizes RDF templates to convert data between different models, including validation and enrichment processes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If mapping rules are implemented programmatically to map between N semantic models and M semantic models, then data exchange between devices is enabled, but the complexity and effort increase significantly when updating mappings for evolving standardized information models or changing use cases

Engineering Contradiction:
Improveadaptability of mapping rulesVSAvoidcomplexity of mapping implementation
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary mapping language layer between the source and target semantic models. This mapping language serves as a mediator that simplifies the mapping definition process, allowing mappings to be updated without complex programmatic changes. The intermediary layer absorbs the complexity of model evolution and provides a stable interface for data exchange.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent enables parameter changes in mapping configurations to adapt to evolving standardized information models. By making mapping parameters configurable and modifiable, the system can accommodate changes in data models, semantics, and use cases without requiring complete remapping or complex reprogramming.

Inventive Principle:
Principle #35Parameter changes

2Reliability

If a common semantic model is implemented to achieve semantic interoperability, then devices can understand exchanged data correctly, but the complexity of defining and maintaining the semantic model increases

Engineering Contradiction:
Improvesemantic interoperabilityVSAvoidcomplexity of semantic model
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent creates a universal semantic model framework that can serve multiple devices and use cases. This universal model is designed to be multi-functional, accommodating various data types, relationships, and semantic interpretations while maintaining a consistent structure. The framework can be instantiated and adapted for different specific applications without requiring separate complex models for each case.

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

Data Source

PatentEP4647927A1Method of operating a semantic information integrator module, semantic information integrator module, system, computer program product and computer readable memory
Publication Date: 2025.11.12 SIEMENS AG
  • EP4647927A1 patent drawingFigure 1~2
  • EP4647927A1 patent drawingFigure 3~4
  • EP4647927A1 patent drawingFigure 5

AI summary

The invention relates to a method of operating a semantic information integrator module (12), comprising the following steps performed by the semantic information integrator module (12): receiving an input message (13), the input message (13) comprising data (15) of a first data model (4); extracting the data (15) of the first data model (4) and mapping the data (15) to a RDF (16) of a predefined information model (17) using a first RDF (16) template specific to the first data model (4); extracting the data (15) of the RDF (16) of the predefined information model (17) and mapping the data (15) to a second data model (5) using a second RDF (16) template specific to the second data model (5); and sending an output message (14), the output message (14) comprising data (15) of the second data model (5).