Instance-Specific Plug-in Management Wrappers

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Legacy techniques for deploying plug-ins in computing environments fail to facilitate fine-grained management of plug-in instances, leading to inefficient resource allocation and performance issues, such as excessive resource usage and insufficient computing resources for real-time delivery.

Innovation Solution

The implementation of instance-specific plug-in management wrappers that encapsulate plug-ins to provide fine-grained management capabilities, optimizing resource utilization and performance by configuring each plug-in instance based on specific computing purposes and conditions, using components like security, metering, and optimization components.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If legacy techniques are used to deploy plug-ins, then plug-in instances can be deployed to perform functions, but fine-grained management of individual plug-in instances is not facilitated

Engineering Contradiction:
Improvefine-grained management capabilityVSAvoidmanagement structure
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the management of plug-in instances by introducing instance-specific management wrappers that encapsulate individual plug-in instances. Each wrapper provides fine-grained control over resource allocation, execution parameters, and monitoring for its enclosed plug-in instance, enabling independent management of each instance rather than coarse-grained control of all instances collectively.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces management wrappers as intermediary components between the plug-in instances and the computing environment. These wrappers act as mediators that translate high-level management requirements into instance-specific configurations, enabling fine-grained control without directly modifying the plug-in instances themselves.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Loss of energy

If coarse-grained resource allocation is used, then plug-in instances can execute, but excessive computing resources are allocated leading to increased costs

Engineering Contradiction:
Improvecomputing resource efficiencyVSAvoidexecution speed
Core Design Contradiction:
Loss of energyVSProductivity

Solution Approach 1:

The patent implements dynamic resource allocation through management wrappers that continuously monitor execution progress and adjust resource allocation in real-time. The wrappers can scale resources up or down based on actual needs, transitioning from static coarse-grained allocation to dynamic fine-grained control that optimizes the balance between resource efficiency and execution speed.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent incorporates feedback mechanisms where management wrappers monitor execution metrics and use this information to adjust resource allocation. The wrappers receive feedback about actual resource usage and execution progress, then modify resource allocation accordingly to prevent both over-provisioning and under-provisioning of computing resources.

Inventive Principle:
Principle #23Feedback

3Loss of energy

If insufficient computing resources are allocated, then resource costs are reduced, but real-time delivery of outputs cannot be achieved

Engineering Contradiction:
Improvecomputing resource usageVSAvoidreal-time delivery capability
Core Design Contradiction:
Loss of energyVSReliability

Solution Approach 1:

The patent applies preliminary action by having management wrappers pre-allocate appropriate computing resources based on predicted execution requirements and service level agreements. The wrappers analyze task characteristics and pre-provision resources to ensure real-time delivery capability is maintained while avoiding allocation of excessive resources that would increase costs.

Inventive Principle:
Principle #10Preliminary action

4Adaptability or versatility

If multiple plug-in instances are deployed, then more functions can be performed, but management and monitoring of each instance becomes difficult

Engineering Contradiction:
Improvefunctional capabilityVSAvoidinstance management ease
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent creates a universal management wrapper architecture that can encapsulate and manage any type of plug-in instance through standardized interfaces. The wrappers provide multi-functional capabilities including resource allocation, execution control, monitoring, and optimization that work consistently across different plug-in types, simplifying the management of multiple diverse instances.

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

Data Source

PatentUS10908926B2Plug-in management wrappers
Publication Date: 2021.02.02 BOX INC
  • US10908926B2 patent drawing
  • US10908926B2 patent drawing
  • US10908926B2 patent drawing

AI summary

Systems for fine-grained management of plug-ins. A method embodiment commences upon identifying a plug-in to perform a particular computing function in a computing environment. A set of configuration parameters that correspond to the particular computing function are determined. Based at least in part on the determined configuration parameters, an instance-specific plug-in management wrapper corresponding is generated. The instance-specific plug-in management wrapper includes fine-grained management controls so as to be able to observe performance characteristics, functional characteristics and other runtime characteristics of the plug-in while it operates in the computing system. When a particular plug-in is invoked, its management wrapper is automatically generated so as to encapsulate the particular plug-in. Deployment instructions are generated to instantiate the plug-in management wrapper and its encapsulated plug-in in the computing system. When the plug-in has performed its function, any measurements taken by the management wrapper are saved and the generated management wrapper is destroyed.