Software Component Tree Rebuilding for Cross-Database Update Mirroring

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing methods, such as PTL 1, fail to efficiently mirror update information of software components across databases of multiple projects and products, particularly for project-specific component groups with different sharing ranges, requiring significant manual effort.

Innovation Solution

A software component update system that includes a component tree rebuilding unit to rebuild software component trees based on tag information, a component extraction unit to specify components needing update mirroring, and a file update unit to update the specified components, facilitating efficient mirroring of update information across databases with different sharing ranges.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual mirroring of update information is performed across multiple projects and products, then configuration management can be maintained, but the number of man-hours and time required increases significantly

Engineering Contradiction:

Improveconfiguration managementVSAvoidman-hours

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The system enables automatic self-updating by having the target database automatically retrieve and apply update information from the source database. The update information includes instructions that the target database executes to replicate changes, eliminating the need for manual intervention and reducing time consumption while maintaining configuration integrity.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The patent replaces manual mechanical operations with an automated information processing system. Update information is transmitted electronically between databases, and the target database automatically processes this information to mirror changes, substituting manual mirroring work with automated data transmission and processing mechanisms.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

2Stability of the object's composition

If update information is mirrored across all projects and products, then consistency is maintained, but unnecessary updates are propagated to project-specific component groups that should not be shared

Engineering Contradiction:

ImproveconsistencyVSAvoidsharing ranges

Core Design Contradiction:

Stability of the object's compositionVSAdaptability or versatility

Solution Approach 1:

The system applies different update propagation rules to different component groups based on their sharing ranges. Core assets with broad sharing ranges receive updates automatically, while project-specific components with restricted sharing ranges are excluded from automatic propagation. This localized quality control ensures consistency where appropriate while respecting project-specific boundaries.

Inventive Principle:

Principle #3Local quality

Solution Approach 2:

The patent segments the software component database into different categories (core assets vs. project-specific components) based on sharing ranges. This segmentation allows the system to apply different update mirroring strategies to different segments, propagating updates to core assets while preventing unnecessary propagation to project-specific components.

Inventive Principle:

Principle #1Segmentation

3Ease of operation

If multiple software component trees are managed manually, then each asset's configuration can be controlled, but the complexity of managing and synchronizing updates across trees increases

Engineering Contradiction:

Improveconfiguration controlVSAvoidsoftware component tree management

Core Design Contradiction:

Ease of operationVSDevice complexity

Solution Approach 1:

The system introduces update information as an intermediary mechanism between source and target software component trees. This intermediary carries the necessary change data and instructions, allowing automated synchronization without requiring complex manual coordination. The intermediary simplifies the management complexity while maintaining configuration control.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS12602221B2Software component update system, and software component update method

Publication Date: 2026.04.14 ASTEMO LTD

AI summary

A software component update system is connected to a first database and a second database and includes a component tree rebuilding unit that rebuilds a software component tree of the second database on the basis of tag information and software component tree information of the first database; a component extraction unit that specifies the software components of the second database requiring update mirroring, on the basis of the rebuilt software component tree; and a file update unit that updates the software component file of the specified software components.