Distributed Knowledge Graph Sub-graph Reintegration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Managing large knowledge graphs with millions of vertices and edges is challenging due to limitations in remote access, processing power, and memory capacity, especially for mobile devices with limited resources, and existing solutions fail to provide efficient methods for quick and reliable access to expert skilled knowledge.

Innovation Solution

The method involves dividing the knowledge graph into sub-graphs, generating local sub-graphs as copies with surrounding structures, modifying their content, and reintegrating changes back into the main graph using the surrounding structure as an aid, allowing for remote editing and synchronization without manual intervention.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If the knowledge graph is divided into sub-graphs for remote access, then accessibility and ease of operation are improved, but device complexity and data management complexity increase

Engineering Contradiction:
Improveremote access to knowledge graphVSAvoidknowledge graph management structure
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The knowledge graph is divided into multiple sub-graphs that can be independently accessed and managed on remote devices. Each sub-graph represents a portion of the overall knowledge graph, allowing users to access specific domains or datasets without loading the entire graph. This segmentation enables remote devices with limited resources to efficiently access and process knowledge graph data.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

A server acts as an intermediary between the central knowledge graph and remote devices. The server manages the division into sub-graphs, handles synchronization, and coordinates reintegration operations. This intermediary abstracts the complexity of distributed graph management from end users, providing a simplified interface while maintaining the sophisticated underlying structure.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If local sub-graphs are generated as copies for remote editing, then productivity and speed of access are improved, but memory usage and data redundancy increase

Engineering Contradiction:
Improvespeed of access and editingVSAvoidmemory usage and data duplication
Core Design Contradiction:
ProductivityVSQuantity of substance

Solution Approach 1:

Local sub-graphs are generated as copies of the relevant portions of the central knowledge graph, stored on remote devices. These copies enable fast local access and editing without requiring continuous network connectivity. The copying mechanism allows users to work offline and only synchronize changes when needed, improving productivity while managing memory usage through selective replication of only necessary sub-graphs.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

Instead of copying the entire knowledge graph to remote devices, only specific sub-graphs relevant to particular users or tasks are replicated. This partial copying approach minimizes memory usage and data redundancy while still providing the speed benefits of local access for the required portions of the knowledge graph.

Inventive Principle:
Principle #16Partial or excessive action

3Reliability

If changes are reintegrated automatically upon trigger events, then reliability and data consistency are improved, but processing overhead and system complexity increase

Engineering Contradiction:
Improvedata consistency between local and central graphsVSAvoidreintegration mechanism
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system implements automatic feedback mechanisms where changes made to local sub-graphs are detected and triggered for reintegration to the central knowledge graph. When specific events occur (such as completion of editing tasks or synchronization intervals), the system automatically initiates the reintegration process, ensuring data consistency without requiring manual intervention. This feedback loop maintains reliability while automating the complexity of synchronization.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The reintegration mechanism operates autonomously based on predefined trigger events and conditions. The system self-manages the synchronization process, automatically detecting when changes need to be pushed back to the central graph and executing the reintegration without user involvement. This self-service approach improves reliability through consistent synchronization while hiding the underlying system complexity from users.

Inventive Principle:
Principle #25Self-service

4Ease of operation

If the surrounding graph is included in local copies as anchor points, then ease of reintegration is improved, but storage requirements and data size increase

Engineering Contradiction:
Improvereintegration processVSAvoidlocal sub-graph data size
Core Design Contradiction:
Ease of operationVSVolume of stationary object

Solution Approach 1:

The surrounding graph context is pre-loaded into local sub-graph copies along with the target sub-graph. This preliminary action includes adding anchor points and contextual vertices that will facilitate future reintegration operations. By preparing this structural framework in advance, the system simplifies the reintegration process, making it easier to match and merge changes back to the central knowledge graph.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The surrounding graph context is selectively included only to the extent necessary for facilitating reintegration. Rather than copying entire connected components or excessive contextual data, the system identifies and includes only the specific anchor points and minimal surrounding structure needed to enable accurate matching and merging during reintegration. This local quality approach provides sufficient contextual information while minimizing storage overhead.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS11294958B2Managing a distributed knowledge graph
Publication Date: 2022.04.05 KYNDRYL INC
  • US11294958B2 patent drawing
  • US11294958B2 patent drawing
  • US11294958B2 patent drawing

AI summary

A knowledge graph is divided into a plurality of sub-graphs, each sub-graph comprising a plurality of vertices and a plurality of edges. The knowledge graph is represented as a summary graph comprising for each of the sub-graphs a summary-graph vertex. A local sub-graph is generated as a copy of one of the sub-graphs together with a copy of a surrounding graph to the one of the sub-graphs. The content of the local sub-graph is modified. The local sub-graph is reintegrated, upon a reintegration trigger event, back into the knowledge graph, wherein a structure of the surrounding graph is used as a reintegration aid, by overlaying the structure and the knowledge graph, thereby identifying identical vertices of the surrounding structure and the knowledge graph as anchor points from where changes in the local sub-graph are reintegrated into the knowledge graph.