Embedded App Component Scaling for IT Asset Resource Constraints

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing embedded enterprise applications have storage space and resource constraints due to their monolithic nature, and they are not device context-aware, leading to inefficient use of IT assets.

Innovation Solution

Implement scalable embedded applications that dynamically adjust components based on predicted future states of IT assets, using device-specific and device-independent components downloaded on an as-needed basis, facilitated by a support platform that analyzes and predicts device states.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If monolithic embedded applications are deployed on IT assets, then the applications can provide comprehensive functionality, but storage space and resource constraints are exacerbated

Engineering Contradiction:

Improvecomprehensive functionalityVSAvoidstorage space

Core Design Contradiction:

Adaptability or versatilityVSQuantity of substance

Solution Approach 1:

The embedded application is divided into a core component that remains on the IT asset and additional components that can be dynamically downloaded. This segmentation allows the application to provide comprehensive functionality when needed while maintaining a small footprint during normal operation, resolving the contradiction between comprehensive functionality and storage space constraints.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The application transitions from a static monolithic structure to a dynamic modular structure where components can be added or removed based on predicted future states. This dynamic adjustment allows the system to adapt its functionality and resource consumption to match actual needs, resolving the contradiction between versatility and storage requirements.

Inventive Principle:

Principle #15Dynamics

2Adaptability or versatility

If monolithic embedded applications are deployed on IT assets, then the applications can provide comprehensive functionality, but resource consumption increases

Engineering Contradiction:

Improvecomprehensive functionalityVSAvoidresource consumption

Core Design Contradiction:

Adaptability or versatilityVSUse of energy by moving object

Solution Approach 1:

By segmenting the application into core and additional components, the system only loads and executes necessary components based on predicted future states. This reduces overall resource consumption while maintaining the capability to provide comprehensive functionality when required, resolving the contradiction between versatility and resource usage.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system changes the operational parameters of the application by dynamically adjusting which components are active based on predicted future states. This allows the application to optimize resource consumption by activating only the necessary functionality, resolving the contradiction between comprehensive functionality and resource consumption.

Inventive Principle:

Principle #35Parameter changes

3Speed

If additional components are pre-loaded on IT assets, then the applications can respond quickly to future states, but storage space is wasted

Engineering Contradiction:

Improveresponse speedVSAvoidstorage space

Core Design Contradiction:

SpeedVSQuantity of substance

Solution Approach 1:

The system performs preliminary analysis of future states using telemetry data and predictive algorithms to determine which components will be needed. This allows components to be downloaded just in time, maintaining fast response speeds without pre-loading unnecessary components that would waste storage space, resolving the contradiction between response speed and storage space utilization.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system uses feedback from telemetry data to continuously update predictions about future states and adjust component loading accordingly. This feedback mechanism ensures that components are loaded based on actual predicted needs rather than static pre-loading, resolving the contradiction between response speed and storage space efficiency.

Inventive Principle:

Principle #23Feedback

4Productivity

If device context-aware embedded applications are implemented, then resource utilization efficiency improves, but device complexity increases

Engineering Contradiction:

Improveresource utilization efficiencyVSAvoidapplication complexity

Core Design Contradiction:

ProductivityVSDevice complexity

Solution Approach 1:

The system introduces a support platform as an intermediary that handles the complexity of predictive analysis and component management. This externalizes the complex decision-making logic, allowing the embedded application on the IT asset to remain relatively simple while still achieving device context-aware resource utilization, resolving the contradiction between productivity and device complexity.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS12536025B2Dynamic adjustment of components running as part of embedded applications deployed on information technology assets

Publication Date: 2026.01.27 DELL PROD LP

AI summary

An apparatus comprises a processing device configured to provide telemetry data from a core component of a scalable embedded application deployed on an information technology asset to a support platform, the telemetry data being utilizable for determining a current state of the information technology asset. The processing device is also configured to receive and parse, at the core component of the scalable embedded application, a component definition data structure to identify a subset of additional components to be run on the scalable embedded application based at least in part on a predicted future state of the information technology asset. The processing device is further configured to dynamically adjust which of the additional components are run as part of the scalable embedded application based at least in part on the parsing of the component definition data structure.