Implicit Application Model for Component Boundary Identification

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current computing systems face challenges in identifying and managing application assets due to a lack of clear links between individual components, complicating actions like backup, repair, and application removal.

Innovation Solution

A method is introduced to determine a discrete application boundary by identifying both statically and dynamically related components, using heuristics for static and dynamic discovery, and refinement techniques to build an implicit application model, which can be used for tasks such as moving, verifying, or repairing application installations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If components are placed throughout the system with no clear link between individual pieces, then the system has flexibility in component placement, but identifying application assets becomes complicated

Engineering Contradiction:

Improvecomponent placement flexibilityVSAvoidapplication asset identification difficulty

Core Design Contradiction:

Adaptability or versatilityVSDifficulty of detecting and measuring

Solution Approach 1:

The patent introduces an intermediary data structure (application component model) that acts as a mediator between scattered system components. This model captures relationships and dependencies between components, enabling the system to maintain placement flexibility while providing a structured way to identify and track application assets through the intermediary representation.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent extracts relationship information and component metadata from the scattered system components and consolidates them into a separate application component model. This extraction process separates the identification logic from the physical component placement, allowing assets to be identified through the model rather than by physically tracing component links throughout the system.

Inventive Principle:

Principle #2Taking out (Extraction)

2Measurement precision

If static and dynamic analysis are performed separately, then each analysis can be performed with focused methodology, but the overall analysis process becomes time-consuming

Engineering Contradiction:

Improveanalysis result precisionVSAvoidanalysis process time

Core Design Contradiction:

Measurement precisionVSLoss of time

Solution Approach 1:

The patent merges static analysis and dynamic analysis into a unified process. The static analysis identifies potential application assets and their relationships, while dynamic analysis validates and refines these findings during actual application execution. The results of both analyses are combined to produce a comprehensive application component model, achieving both precision and efficiency through integration rather than separate sequential processing.

Inventive Principle:

Principle #5Merging (Combining)

Data Source

PatentEP2791850B1Identifying application resources through implicit application models

Publication Date: 2019.01.23 MICROSOFT TECHNOLOGY LICENSING LLC

Figure 1
Figure 2

AI summary

Determining a discrete application boundary. A method includes identifying one or more initial components of an application. The method further includes identifying statically and/or dynamically related components of the one or more initial components of the application. Identifying statically related components and identifying dynamically related components is performed iteratively. The method further includes identifying a discrete boundary for the application based on statically related components and dynamically related components.