Configuration Data Tree Merging for Scalable Version Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing configuration management tools are inefficient in handling multiple versions of configuration data from source files, leading to non-scalable solutions with duplicated data when creating separate configuration trees for each version.

Innovation Solution

A system and method for generating a single configuration data tree from multiple source files by identifying and merging different versions, where each node represents multiple nodes from various versions without duplication, and displaying data in a scalable manner.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If separate configuration trees are created for each version permutation, then all version data can be stored, but memory efficiency deteriorates due to large amounts of duplicated data

Engineering Contradiction:
Improvecompleteness of version data storageVSAvoidmemory footprint
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent merges multiple version-specific configuration nodes into a single shared configuration tree structure. Instead of maintaining separate trees for each version permutation, the system combines all version data into one tree where common nodes are shared across versions, eliminating duplicated data storage while preserving complete version information.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The configuration tree nodes are designed to serve multiple versions simultaneously. A single node in the merged tree can represent configuration data that applies to multiple version permutations, making the node universal rather than version-specific. This multi-functionality allows the same node structure to handle diverse version requirements without duplication.

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

2Reliability

If separate configuration trees are created for each version permutation, then all version data can be accessed, but system scalability deteriorates

Engineering Contradiction:
Improvecompleteness of version data storageVSAvoidscalability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

By merging multiple version-specific trees into a single unified configuration tree, the system achieves linear scalability rather than exponential growth. The merged structure allows the system to handle an increasing number of versions efficiently, as new versions can be integrated by adding or modifying nodes in the existing tree rather than creating entirely new tree structures.

Inventive Principle:
Principle #5Merging (Combining)

3Reliability

If multiple configuration trees are maintained in memory, then all version data is available, but operational efficiency deteriorates due to redundant data processing

Engineering Contradiction:
Improveavailability of version dataVSAvoidconfiguration processing efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent combines multiple configuration trees into a single merged tree structure that eliminates redundant data processing. When configuration operations need to be performed, the system operates on the unified tree rather than managing multiple separate trees, significantly reducing the computational overhead of traversing and manipulating duplicated configuration data across multiple version permutations.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS9329857B1System, method, and computer program for generating configuration data trees associated with a plurality of source files
Publication Date: 2016.05.03 AMDOCS DEV LTD
  • US9329857B1 patent drawing
  • US9329857B1 patent drawing
  • US9329857B1 patent drawing

AI summary

A system, method, and computer program product are provided for generating a configuration data tree associated with a plurality of source files. In use, a load of a configuration data tree associated with a plurality of source files is initiated. Further, different versions of the plurality of source files are identified. Additionally, the different versions of the plurality of source files are merged to produce a single configuration data tree, wherein one node in the single configuration data tree is capable of representing a plurality of nodes associated with the different versions of the plurality of source files. Moreover, displayable data associated with the single configuration data tree is generated.