Database Entity Relationship Visualization Interface

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current methods for visualizing relationships between entity instances in databases are time-consuming, require specialized skills, and produce non-intuitive reports that need modification for different queries, making it difficult to efficiently understand and interpret relationships between various entity types.

Innovation Solution

A computing device with a processor configured to access a data table identifying relationships between entity instances, generating a user interface that depicts overlapping and non-overlapping objects representing entity structures, allowing for intuitive visualization of relationships without requiring modifications for different reports.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Measurement precision

If specialized programs are developed to extract relationship information from the database, then accurate relationship reports can be generated, but the process becomes time-consuming and requires specialized database skills

Engineering Contradiction:
Improveaccuracy of relationship reportsVSAvoidtime required to generate reports
Core Design Contradiction:
Measurement precisionVSLoss of time

Solution Approach 1:

The system automatically generates relationship visualizations by processing data from the database without requiring manual intervention from specialized database users. The automated entity relationship visualization system independently queries the database, processes relationships, and generates intuitive visual representations, eliminating the need for time-consuming manual report generation while maintaining accuracy.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent replaces manual mechanical processes (writing and executing specialized database queries requiring skilled programmers) with an automated computational system. The system uses programmed algorithms to automatically extract relationship data, process entity connections, and generate visualizations, substituting human expertise with automated computational mechanisms that are faster and scalable.

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

2Measurement precision

If specialized programs are developed for each report type, then specific relationship information can be obtained, but the system lacks flexibility for different entity types and queries

Engineering Contradiction:
Improvespecificity of relationship reportsVSAvoidflexibility for different entity types
Core Design Contradiction:
Measurement precisionVSAdaptability or versatility

Solution Approach 1:

The system is designed as a universal platform that can visualize relationships between any combination of entity types stored in the database. Rather than requiring separate specialized programs for different reports, the single automated system processes diverse entity relationships (customer-product, product-store, etc.) through a unified approach, generating appropriate visualizations for each query type without requiring system modification.

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

Solution Approach 2:

The system dynamically adapts its visualization output based on the specific query parameters and entity types provided. Users can input different criteria and entity combinations, and the system automatically adjusts its data extraction and visualization strategies accordingly, providing flexible, customized relationship visualizations for each scenario without requiring pre-programmed specialized solutions.

Inventive Principle:
Principle #15Dynamics

3Loss of information

If textual reports are generated to show entity relationships, then detailed information can be presented, but the information is not intuitive or easily interpreted by humans

Engineering Contradiction:
Improvecompleteness of relationship dataVSAvoidintuitiveness of information presentation
Core Design Contradiction:
Loss of informationVSEase of operation

Solution Approach 1:

The system employs visual elements including color coding, shape variations, and spatial arrangements to represent different entity types and relationship characteristics. By transforming textual data into visually distinguishable elements, the system makes relationship information immediately recognizable and intuitive for human interpretation, allowing users to quickly grasp complex relationships without reading detailed text.

Inventive Principle:
Principle #32Color changes

Solution Approach 2:

The patent transitions relationship information from a one-dimensional textual format to a two-dimensional visual representation. By mapping entity relationships onto spatial arrangements, connections, and graphical structures, the system presents complex data in a format that is both complete and easily perceived, allowing users to understand relationships at a glance through visual patterns rather than reading through text.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

Data Source

PatentUS11954110B2Methods and apparatus for visualizing entity instance relationships in a database
Publication Date: 2024.04.09 SENJALIA BHARGAV
  • US11954110B2 patent drawing
  • US11954110B2 patent drawing
  • US11954110B2 patent drawing

AI summary

A method, apparatus, and non-transitory computer-readable storage medium for presenting information identifying relationships in a database. Entity labels identifying a plurality of different entity types modeled in the database are presented in a user interface. Input identifying one or more selected entity types is received. A plurality of entity instance relationship sets is accessed. Each entity instance relationship set identifies a relationship between entity instances of at least two different entity types. Attribute data of the entity instances identified in only those entity instance relationship sets that identify a relationship between entity instances of the one or more selected entity types are presented, such that attribute data for each unique relationship between entity instances of the one or more selected entity types are presented only once.