Graph Management System for Multi-Database Integration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing graph databases face challenges in efficiently generating and maintaining graphs from multiple databases or data sources, particularly due to differences in data information and maintaining a readable and searchable format for vertices and edges.

Innovation Solution

A graph management system is developed to identify attribute types of interest across multiple databases, generate vertices for unique attribute values, and connect vertices associated with the same entity, using entity vertices to represent corresponding entities.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If data from multiple databases with different information is integrated into a single graph, then the comprehensiveness of the graph increases, but the complexity of maintaining consistent formats and readable searchable structures increases

Engineering Contradiction:
Improvegraph data integration capabilityVSAvoidgraph format maintenance complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the graph structure into distinct vertex types (entity vertices and attribute vertices) and edge types. This segmentation allows different databases with different data formats to be integrated by mapping their data to appropriate vertex and edge types, while maintaining consistent internal structure for readability and searchability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces attribute vertices as intermediary elements that connect entity vertices. These attribute vertices serve as mediators that standardize the representation of attributes from different databases, enabling consistent format maintenance while integrating diverse data sources.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Loss of information

If vertices are created for every unique attribute value from multiple databases, then the detail and searchability of the graph improves, but the number of vertices and edges increases, making the graph more complex to manage

Engineering Contradiction:
Improvedata searchabilityVSAvoidgraph structure complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The patent segments vertices into entity vertices (representing core entities) and attribute vertices (representing attributes). This segmentation organizes the large number of vertices created from multiple databases into a structured hierarchy, improving manageability while preserving detailed information for searchability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent adds a dimensional organization to the graph by introducing the attribute vertex layer between entity vertices. This creates a two-dimensional structure (entity-attribute-entity relationships) that manages complexity through layered organization while maintaining comprehensive data representation.

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

3Productivity

If the graph structure is optimized for readable and searchable format, then query efficiency improves, but the flexibility to accommodate different database formats decreases

Engineering Contradiction:
Improvequery efficiencyVSAvoiddatabase format flexibility
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The patent creates a universal graph structure where entity vertices and attribute vertices can represent data from any database format. The standardized vertex-edge relationship model serves multiple functions: it accommodates diverse input formats while providing consistent optimized structure for reading and searching.

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

Solution Approach 2:

The patent establishes a pre-defined graph structure with standardized entity vertices, attribute vertices, and relationship edges before data integration. This preliminary structural framework enables efficient queries while accommodating different database formats during the data mapping phase.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12277172B2Graph creation from multiple databases
Publication Date: 2025.04.15 TIGERGRAPH INC
  • US12277172B2 patent drawing
  • US12277172B2 patent drawing
  • US12277172B2 patent drawing

AI summary

Systems, methods, and software described herein provide operations to generate and manage a graph. In one implementation, a graph management system may identify a request to generate a graph from multiple databases. In response to the request, the graph management system may identify attributes of interest in the databases and generate vertices that correspond to the attributes of interest. As the new vertices are generated, the graph management system may determine attributes that are related to the same entity, generate entity vertices that correspond to the entities identified in the databases, and generate edges that connect the attribute vertices to the corresponding entity vertices.