Abstraction Engine for Heterogeneous Database Connectivity

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems face challenges in sharing data manipulations across different database connectivity technologies, such as ODBC and JDBC, due to embedded communication information, leading to costly, time-consuming, and error-prone manual re-writing and modification processes.

Innovation Solution

An abstraction engine analyzes data manipulation definitions to extract connectivity parameters, storing them as meta-connections in a metadata repository, allowing for automated translation and use across various connection protocols, enabling flexible and automated artifact sharing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If data manipulation embeds required communication information for a particular database connectivity technology, then the data manipulation can be executed by software using that specific technology, but it cannot be used or consumed by software that does not use the same database technology

Engineering Contradiction:
Improvecompatibility across different database connectivity technologiesVSAvoidcomplexity of manual re-writing and modification processes
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the data manipulation into two distinct parts: connectivity parameters (communication information) and query logic (data manipulation definition). This separation allows each part to be independently managed - connectivity parameters can be translated between different database technologies (ODBC, JDBC, etc.) while the query logic remains unchanged, enabling portability across different connectivity technologies without manual re-writing

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary component (translation service or abstraction layer) that sits between the data manipulation definition and the database connectivity. This intermediary automatically translates connectivity parameters between different database technologies, eliminating the need for manual re-writing and enabling seamless compatibility across ODBC, JDBC, and other connectivity standards

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If manual re-writing and modification of data manipulations is performed when connectivity parameters change, then the data manipulation can be adapted to new connectivity requirements, but the process is costly, time-consuming, and error prone

Engineering Contradiction:
Improveadaptability to new connectivity parametersVSAvoidtime required for manual re-writing and modification
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent performs preliminary action by pre-defining connectivity parameters and their translations in a standardized format. When connectivity requirements change, the system automatically applies pre-established translation rules rather than requiring manual re-writing, significantly reducing the time and effort required to adapt to new connectivity parameters

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements self-service by automatically detecting connectivity parameter changes and performing the necessary translations and adaptations without human intervention. The translation service autonomously updates data manipulations to work with new connectivity requirements, eliminating manual re-writing processes and reducing both time and error rates

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS10896174B2Sharing artifacts with heterogeneous database connectivity
Publication Date: 2021.01.19 BUSINESS OBJECTS SOFTWARE
  • US10896174B2 patent drawing
  • US10896174B2 patent drawing
  • US10896174B2 patent drawing

AI summary

According to some embodiments, an abstraction engine may determine a data manipulation definition generated by a creator platform to accesses a database via a first connection protocol (e.g., ODBC). The abstraction engine may then automatically analyze the data manipulation definition to discover a connectivity parameter (e.g., a DSN, a DBMS type, a DBMS host name, a port, etc.) associated with the access to the database via the first connection protocol. The data manipulation definition may then be stored along with the connectivity parameter as a meta-connection into a metadata repository. A consuming platform may retrieve the meta-connection from the metadata repository translate the meta-connection into the database manipulation definition to accesses the database via a second connection protocol (e.g., JDBC).