Centralized Parameter Store for Automated Software Deployment

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Software deployment and updates for remote computing devices often require manual reconfiguration and user intervention, as existing systems lack a centralized mechanism for managing device-specific settings and updating applications efficiently across multiple devices.

Innovation Solution

A system and method for continuous publishing of applications, where a manifest file and parameters file are stored in a central data store, enabling the recreation and republishing of software deployment packages with device-specific settings, allowing automatic updates to remote computing devices without prompting users for configuration information.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If manual reconfiguration is used for each device during software deployment, then device-specific settings can be customized, but user intervention time and deployment complexity increase significantly

Engineering Contradiction:

Improvedevice-specific settings customizationVSAvoiduser intervention time

Core Design Contradiction:

Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by pre-configuring device-specific settings in a parameters file before deployment. The system extracts destination-dependent parameters from the software deployment package and stores them in a centralized data store, so that when the application is re-published to remote devices, these parameters are automatically applied without requiring user input during each deployment operation.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent uses copying by creating a centralized repository of device-specific parameters that can be copied and applied across multiple deployment instances. The parameters file containing destination-dependent settings is stored centrally and reused for each re-publication operation, eliminating the need to manually re-enter the same configuration information for each device.

Inventive Principle:

Principle #26Copying

2Reliability

If software updates are deployed to multiple remote devices, then application functionality is improved, but requiring user reconfiguration at each device increases operational complexity

Engineering Contradiction:

Improveapplication update deliveryVSAvoiddeployment operation simplicity

Core Design Contradiction:

ReliabilityVSEase of operation

Solution Approach 1:

The patent implements self-service by enabling the deployment system to automatically retrieve and apply device-specific parameters from the centralized data store during re-publication operations. The system autonomously configures each remote device with the appropriate destination-dependent settings without requiring user intervention, thereby maintaining ease of operation while ensuring reliable update delivery.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The patent introduces an intermediary mechanism in the form of a centralized data store that mediates between the software deployment package and remote devices. This intermediary stores device-specific parameters and automatically supplies them during deployment, simplifying the operational process while ensuring that each device receives the correct configuration for reliable update installation.

Inventive Principle:

Principle #24Intermediary (Mediator)

3Loss of information

If device-specific parameters are stored locally at each remote device, then configuration information is preserved, but centralized management and update efficiency are reduced

Engineering Contradiction:

Improveconfiguration information preservationVSAvoidupdate deployment efficiency

Core Design Contradiction:

Loss of informationVSProductivity

Solution Approach 1:

The patent merges device-specific parameter storage into a single centralized data store located at the publishing destination. Instead of distributing configuration information across multiple local devices, the system consolidates all destination-dependent parameters in one central location, enabling efficient retrieval and application during re-publication operations while preserving all configuration information.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The centralized data store serves multiple functions: it stores device-specific parameters for different remote devices, manages configuration information for various application versions, and provides automated parameter retrieval for deployment operations. This universal storage mechanism improves productivity by enabling efficient update deployment while maintaining comprehensive configuration information preservation.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS11989544B2Software deployment to multiple computing devices

Publication Date: 2024.05.21 MICROSOFT TECHNOLOGY LICENSING LLC

AI summary

A particular method includes storing a manifest file and a parameters file at a data store. The manifest file and the parameters file are associated with a software deployment package. An application associated with the software deployment package is published to a first remote computing device and to a second remote computing device. The method includes receiving first parameter values from the first remote computing device and receiving second parameter values from the second remote computing device. The first parameter values are stored in a first region of the data store that is specific to the first computing device. The second parameter values are stored in a second region of the data store that is specific to the second computing device.