Remote Package Deployment for Device Provisioning

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing computing device provisioning methods often result in devices not being immediately ready for use due to infrequent software updates, leading to prolonged configuration times when users first log on.

Innovation Solution

The described solution involves remotely deploying applications and updates to computing devices prior to the user's first logon, utilizing a network environment with a management service, management console, and agents to manage device policies and application installations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If software updates are applied at factory provisioning, then devices are ready for immediate use, but software updates cannot be applied frequently enough to keep up with release schedules

Engineering Contradiction:
Improvedevice readinessVSAvoidsoftware update frequency
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent applies preliminary action by downloading and staging software updates in the background before the user's first logon, so that updates are already prepared and ready to be applied immediately when the device is first used, eliminating the need for lengthy updates during initial setup

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent segments the software update process into distinct phases: background download phase, staging phase, and application phase. This allows the update process to be separated from the user's first logon experience, enabling frequent updates without impacting device readiness

Inventive Principle:
Principle #1Segmentation

2Adaptability or versatility

If additional applications are installed upon first logon, then devices have complete functionality, but configuration time is significantly extended

Engineering Contradiction:
Improveapplication completenessVSAvoidconfiguration time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent performs the action of downloading and preparing additional applications in advance, before the user's first logon, so that when the user logs on, the applications are already staged and ready for rapid installation, dramatically reducing configuration time

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent enables continuous background operations (downloading, staging) to occur while the device is being prepared, so that useful work continues during the provisioning period without interrupting the user's first logon experience

Inventive Principle:
Principle #20Continuity of useful action

3Reliability

If large application updates are applied at first logon, then applications are up to date, but the process takes a significant period of time

Engineering Contradiction:
Improveapplication currencyVSAvoidupdate installation time
Core Design Contradiction:
ReliabilityVSDuration of action of moving object

Solution Approach 1:

The patent downloads and stages large application updates in the background before first logon, breaking the update process into preliminary download/staging phases followed by rapid application, thereby maintaining application currency while minimizing the time users experience during update installation

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12204888B2Remote deployment of provisioned packages
Publication Date: 2025.01.21 OMNISSA LLC
  • US12204888B2 patent drawing
  • US12204888B2 patent drawing
  • US12204888B2 patent drawing

AI summary

Disclosed are various approaches for remotely deploying provisioned packages. An installer for an application is stored in a cache location of the client device. A hash of the installer is then written to a registry of the client device. The installer is then executed to install the application on the client device. Then, the client device is registered with a management service. Subsequently, a registration confirmation is received from the management service. The hash of the installer is then confirmed and the installed application is identified to the management service as a managed application installed on the client device.