Graph Transformation via Folding Query for IT Infrastructure

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional graph transformation applications for IT infrastructures are inefficient, complex, and difficult to maintain, often requiring intermediary processes that increase complexity and hinder user access to simple transformation capabilities, making it hard to display and understand large IT infrastructure graphs.

Innovation Solution

The method involves transforming a base graph into a folded graph using a folding query that describes edges and paths, allowing users to generate output in a user-friendly format like a tree structure, eliminating intermediary servers and reducing maintenance costs, while enabling users to easily construct data structures without learning complex rules.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If conventional intermediary processes are used for graph transformation, then transformation functionality is provided, but system complexity increases and maintenance difficulty increases

Engineering Contradiction:
Improvegraph transformation capabilityVSAvoidsystem complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent extracts the graph transformation logic from the intermediary process and places it directly in the client application. The client now performs transformations using local algorithms and data structures, eliminating the need for complex server-side intermediary processes while maintaining transformation functionality.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The client application serves its own transformation needs by implementing transformation algorithms locally. Instead of relying on external intermediary processes, the client independently performs graph-to-tree transformations using its own resources and logic, reducing overall system complexity.

Inventive Principle:
Principle #25Self-service

2Ease of operation

If conventional intermediary processes are used for graph transformation, then transformation is performed, but maintenance requirements increase

Engineering Contradiction:
Improvetransformation functionalityVSAvoidmaintenance difficulty
Core Design Contradiction:
Ease of operationVSEase of repair

Solution Approach 1:

The transformation logic is extracted from the server environment and embedded within the client application. This allows maintenance and updates to be performed independently on the client side without affecting server operations or requiring coordinated system-wide changes.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system is segmented into independent components: the graph database server remains unchanged, while the client application contains its own transformation engine. This segmentation allows independent maintenance of each component without cascading effects on the entire system.

Inventive Principle:
Principle #1Segmentation

3Quantity of substance

If graph data is displayed in conventional formats, then all graph elements can be shown, but understandability decreases for non-technical users

Engineering Contradiction:
Improvegraph information completenessVSAvoiduser understandability
Core Design Contradiction:
Quantity of substanceVSEase of operation

Solution Approach 1:

Instead of requiring users to adapt to graph formats, the system inverts the approach by automatically transforming the graph data into tree formats that are more familiar and understandable to end users. This inversion makes the information accessible to non-technical users without losing completeness.

Inventive Principle:
Principle #13The other way round (Inversion)

Solution Approach 2:

The system changes the structural parameter of the data representation from graph format to tree format. This parameter change transforms the organization of information while preserving the underlying data relationships, making it more comprehensible to users with varying technical backgrounds.

Inventive Principle:
Principle #35Parameter changes

4Manufacturing precision

If complex rule sets are used for graph transformation, then transformation accuracy can be achieved, but user learning time increases

Engineering Contradiction:
Improvetransformation accuracyVSAvoiduser learning time
Core Design Contradiction:
Manufacturing precisionVSLoss of time

Solution Approach 1:

The system copies familiar tree structures that users already understand from common applications and operating systems. By presenting transformed data in these familiar patterns, users can interpret the information immediately without learning new complex rules, while the transformation logic itself maintains accuracy through structured algorithms.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS10909733B2Graph transformation
Publication Date: 2021.02.02 MICRO FOCUS LLC
  • US10909733B2 patent drawing
  • US10909733B2 patent drawing
  • US10909733B2 patent drawing

AI summary

Systems, methods, and other embodiments associated with graph transformation are described. One example method includes transforming a base graph into a folded graph as a function of a folding query.