Loader-Installer Segmentation for Automatic Download Provisioning

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional methods cannot embed user information (UserInfo) into downloadable software programs that connect to and operate Internet services, as doing so would corrupt the installer or require separate file handling, leading to user errors and authentication issues.

Innovation Solution

An automatic download provisioning system that appends an installer to a loader, gathers and injects UserInfo into a static buffer, and uses the loader to write the information into the user's computer registry, allowing seamless installation and operation of Internet services without manual user input.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Extent of automation

If UserInfo is embedded into the Installer during download, then automatic provisioning is achieved, but the Installer becomes corrupted and breaks

Engineering Contradiction:
Improveautomatic provisioningVSAvoidInstaller integrity
Core Design Contradiction:
Extent of automationVSReliability

Solution Approach 1:

The system divides the download package into two separate components: a Loader executable and an Installer executable. The Loader contains a static buffer for UserInfo injection, while the Installer remains intact and unmodified. This segmentation allows automatic provisioning through the Loader without corrupting the Installer, resolving the contradiction between automation and reliability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The Loader acts as an intermediary component between the download system and the Installer. It receives the UserInfo, injects it into its own static buffer, and then passes control to the Installer. This intermediary approach enables automatic provisioning while preserving the Installer's integrity, as the Loader handles all modifications and communications with the user.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If UserInfo is displayed on a web page or sent via email, then service provisioning is achieved, but manual user input is required

Engineering Contradiction:
Improveservice provisioningVSAvoidmanual input time
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The system implements self-service by automatically gathering UserInfo through the web form submission and injecting it into the Loader without requiring any manual copying or pasting by the user. The Loader executable contains built-in functionality to read the UserInfo from the injected buffer and use it for automatic provisioning, eliminating the need for manual user input and reducing time loss.

Inventive Principle:
Principle #25Self-service

3Reliability

If separate file handling is used for UserInfo and Installer, then data integrity is maintained, but user errors increase

Engineering Contradiction:
Improvedata integrityVSAvoiduser operation
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system merges the UserInfo and Installer into a single integrated download package, where the Loader contains both the injected UserInfo and the embedded Installer. This unified approach eliminates the need for separate file handling, reducing user errors while maintaining data integrity through the Loader's controlled injection mechanism. The user receives one file instead of multiple separate files that need to be manually coordinated.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS7882171B1Automatic download provisioning
Publication Date: 2011.02.01 AVAYA INC
  • US7882171B1 patent drawing
  • US7882171B1 patent drawing
  • US7882171B1 patent drawing

AI summary

An automatic download provisioning system and method that includes appending an Installer into a Loader, gathering UserInfo, injecting the UserInfo into the Loader, and using the Loader to write the UserInfo into a Registry of a user computer. One preferred embodiment includes the steps of appending an Installer to a Loader having a Static Buffer, posting the Loader on the Web Server, gathering UserInfo, injecting the UserInfo into the Static Buffer, and transmitting the Loader to the user computer. Another preferred embodiment includes means for receiving a Loader having a Static Buffer and an appended Installer, means for gathering UserInfo, means for injecting the UserInfo into the Static Buffer, and means for transmitting the Loader to the user computer.