Semantic Layer for Heterogeneous Data Navigation

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Conventional relational database management systems (RDBMS) are inflexible and inefficient for handling large volumes of rapidly evolving heterogeneous data, particularly in generating reports that require access to many records and data fields, and updating historical data overwrites long-term trend analysis.

Innovation Solution

The system employs a faceted navigation approach with a semantic layer that interprets synthetic data to facilitate user interaction with heterogeneous data, allowing for dynamic adaptation and generation of subsets based on user selections, and supports the creation of synthetic data objects and groups that can be used to refine and augment query results.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional RDBMS systems are used to manage heterogeneous data, then data consistency and transactional efficiency are improved, but flexibility and adaptability to rapidly evolving data formats deteriorate

Engineering Contradiction:

Improvedata consistencyVSAvoidflexibility to evolving data formats

Core Design Contradiction:

ReliabilityVSAdaptability or versatility

Solution Approach 1:

The system segments data management into two distinct layers: a rigid RDBMS layer for maintaining data consistency and a flexible semantic layer for adapting to evolving data formats. This segmentation allows each layer to specialize in its strength without compromising the other.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent introduces a semantic layer as an intermediary between the RDBMS and the user/application. This intermediary translates and adapts heterogeneous data formats, allowing the rigid database to remain consistent while providing flexible access to evolving data structures.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Productivity

If RDBMS systems are used for aggregate information and reporting, then transactional processing efficiency is improved, but report generation performance and analysis capabilities deteriorate

Engineering Contradiction:

Improvetransactional processing efficiencyVSAvoidreport generation time

Core Design Contradiction:

ProductivityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by pre-computing and storing aggregate information in the semantic layer. This allows report generation to retrieve pre-prepared data rather than computing it on-demand, significantly reducing report generation time while maintaining efficient transactional processing in the RDBMS.

Inventive Principle:

Principle #10Preliminary action

3Productivity

If update-in-place operations are used in RDBMS, then transactional efficiency is improved, but historical data preservation and trend analysis capabilities deteriorate

Engineering Contradiction:

Improvetransactional efficiencyVSAvoidhistorical data loss

Core Design Contradiction:

ProductivityVSLoss of information

Solution Approach 1:

The patent implements a copying mechanism where historical data is preserved in the semantic layer while the RDBMS performs update-in-place operations. The semantic layer maintains copies of historical states, enabling trend analysis without compromising transactional efficiency in the underlying database.

Inventive Principle:

Principle #26Copying

4Device complexity

If rigid database schemas are used, then data organization and query performance are improved, but ease of operation and user interaction with heterogeneous data deteriorate

Engineering Contradiction:

Improvedata organization structureVSAvoiduser interaction with heterogeneous data

Core Design Contradiction:

Device complexityVSEase of operation

Solution Approach 1:

The semantic layer serves as an intermediary that presents a user-friendly, flexible interface to heterogeneous data while the underlying RDBMS maintains its rigid schema. This intermediary translates complex schema-less data access into structured database operations, improving ease of operation without compromising data organization.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS10289720B2Information retrieval and navigation using a semantic layer and dynamic objects

Publication Date: 2019.05.14 ORACLE INT CORP

AI summary

Systems and methods for information retrieval are provided that permit users and/or processing entities to access and define synthetic data, synthetic objects, and/or synthetic groupings of data in one or more collections of information. In one embodiment, data access on an information retrieval system can occur through an interpretation layer which interprets any synthetic data against data physically stored in the collection. Synthetic data can define virtual data objects, virtual data elements, virtual data attributes, virtual data groupings, and/or data entities that can be interpreted against data that may be stored physically in the collection of information. The system and methods for information retrieval can return results from the one or more collections of information based not only on the data stored, but also on the virtual data generated from interpretation of the stored data.