Hierarchical Inventory Tree Node Update Optimization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Previous approaches to managing hierarchical inventory trees in datacenters are inefficient, particularly when dealing with large numbers of nodes and child nodes, as they require immediate updates for all nodes, including those not currently visible in the graphical user interface, leading to slow performance.

Innovation Solution

The solution involves delaying updates for nodes that are not displayed in the graphical user interface, flagging them for later updating when they become visible through user interaction, such as expansion or scrolling, thereby processing updates only for nodes that the user is interested in viewing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If updates are processed for all nodes including those not currently visible in the GUI, then data accuracy is maintained, but system performance deteriorates

Engineering Contradiction:
Improvedata accuracyVSAvoidsystem performance
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent segments the node update process by dividing nodes into two categories: visible nodes (currently displayed in GUI) and non-visible nodes (not currently displayed). Updates are selectively applied only to visible nodes, while non-visible nodes are flagged for later updating when they become visible. This segmentation resolves the contradiction by maintaining data accuracy for visible nodes while improving system performance by excluding non-visible nodes from immediate updates.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies partial action by processing updates for only a subset of nodes (those currently visible in the GUI) rather than all nodes. This partial updating approach maintains sufficient data accuracy for the user's current view while significantly improving system performance by reducing the number of update operations performed.

Inventive Principle:
Principle #16Partial or excessive action

2Reliability

If updates are processed for all nodes including hidden ones, then complete data synchronization is achieved, but processing time increases

Engineering Contradiction:
Improvedata synchronizationVSAvoidprocessing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by flagging non-visible nodes for later updating before they become visible. This ensures that when a non-visible node transitions to a visible state, its update is already prepared or can be quickly processed, maintaining data synchronization without requiring immediate processing of all nodes, thus reducing processing time.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent performs partial updating by processing only visible nodes immediately while deferring updates for non-visible nodes. This approach achieves sufficient data synchronization for the current user view while dramatically reducing processing time by excluding unnecessary updates for hidden nodes.

Inventive Principle:
Principle #16Partial or excessive action

3Reliability

If all nodes are updated regardless of visibility, then data consistency is maintained, but computational resources are wasted

Engineering Contradiction:
Improvedata consistencyVSAvoidcomputational resources
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent segments the node population into visible and non-visible categories, applying updates only to visible nodes. This segmentation maintains data consistency for the user's current view while reducing computational resource consumption by excluding non-visible nodes from update processing.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies local quality by differentiating update processing based on node visibility status. Visible nodes receive immediate updates to maintain data consistency, while non-visible nodes are flagged for later updating, optimizing computational resource usage by applying updates only where necessary.

Inventive Principle:
Principle #3Local quality

4Measurement precision

If immediate updates are performed for all nodes, then real-time accuracy is achieved, but user experience deteriorates due to slow performance

Engineering Contradiction:
Improvereal-time accuracyVSAvoiduser experience
Core Design Contradiction:
Measurement precisionVSEase of operation

Solution Approach 1:

The patent segments update processing to apply real-time updates only to visible nodes while deferring updates for non-visible nodes. This maintains real-time accuracy for the user's current view while improving user experience by reducing overall processing time and system responsiveness.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies partial updating by processing only visible nodes immediately, providing real-time accuracy for the user's current view. This partial approach significantly improves user experience by reducing processing delays while maintaining sufficient accuracy for displayed information.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS10572108B2Hierarchical inventory tree operation
Publication Date: 2020.02.25 VMWARE INC
  • US10572108B2 patent drawing
  • US10572108B2 patent drawing
  • US10572108B2 patent drawing

AI summary

Hierarchical inventory tree operation can include receiving an indication of an update made to a hierarchical inventory tree. The tree can represent a hierarchical inventory of objects. The indication can include an identification of at least one object affected by the update and an identification of at least one property of the at least one object affected by the update. The update can be particular to a single node of the tree. Hierarchical inventory tree operation can further include flagging the particular node without updating the particular node in the graphical user interface (GUI) responsive to a determination that a portion of the tree including the particular node is not displayed by the GUI.