Database Structure Mapping to Software Identity

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Determining the software identity associated with a database based on its structure is challenging due to the uniqueness of database schema and table layouts across different software products, making it difficult for network administrators to identify the software product linked to a particular database without access to program product information.

Innovation Solution

A computer-implemented method and system that compares structural information of a database with software signatures to generate a match estimate, inferring the software product association by mapping database structure identities to software identities.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If database schema and table layouts are customized for each software product, then the software product can meet its specific needs, but it becomes difficult to identify the software product associated with a database

Engineering Contradiction:
Improvedatabase customizationVSAvoidsoftware identification
Core Design Contradiction:
Adaptability or versatilityVSDifficulty of detecting and measuring

Solution Approach 1:

The patent creates a virtual copy of the database structure by extracting structural metadata (table names, column names, data types, relationships) and storing it in a database signature database. This copy allows comparison with known software product signatures without accessing the actual customized database, enabling identification while preserving customization.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent introduces a database signature database as an intermediary between the customized database structure and the software product identification process. This intermediary stores extracted structural information and enables comparison with software signatures, bridging the gap between customized schemas and software identification.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If network administrators need to identify software products without access to program product information, then troubleshooting can proceed with limited access, but accurate identification becomes challenging

Engineering Contradiction:
Improveadministrative accessVSAvoidsoftware identification accuracy
Core Design Contradiction:
Ease of operationVSMeasurement precision

Solution Approach 1:

The patent extracts key structural metadata from the database (table names, column names, data types, relationships) and stores it in a database signature database. This extracted information serves as a fingerprint that can be compared with software product signatures, enabling accurate identification even without access to program product information.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent replaces the need for direct access to program product information with a computational comparison system. Instead of requiring administrators to manually examine software files or configurations, the system automatically compares database structural signatures with stored software signatures to identify the associated software product.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

3Adaptability or versatility

If database structures are unique to each software product, then each software can be optimized for its specific requirements, but database management and troubleshooting become more complex

Engineering Contradiction:
Improvesoftware-specific optimizationVSAvoiddatabase management complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the database structure into discrete metadata elements (table names, column names, data types, relationships) and stores them separately in a database signature database. This segmentation allows the system to compare specific structural features with software product signatures without analyzing the entire database, simplifying the management and troubleshooting process.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS10248668B2Mapping database structure to software
Publication Date: 2019.04.02 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US10248668B2 patent drawing
  • US10248668B2 patent drawing
  • US10248668B2 patent drawing

AI summary

A first set of metadata may be received, via a network, which includes structural information about a first database. The structural information may be compared with one or more software signatures. Each software signature may include a software identity that is mapped to one or more associated database structure identities. A first match estimate may be generated based on the comparing of the structural information with the one or more software signatures. It may be inferred that the first database is likely included in a first software product based on the generating of the match estimate.