Virtual Application Publishing via Web Server Intermediary

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

There is a need for a method and system to efficiently publish virtual application files on a server for distribution over the Internet, as existing solutions lack a streamlined process for uploading and managing virtual application files, including configuration and execution on web servers.

Innovation Solution

A system and method for publishing virtual applications involve a client computing device uploading virtual application files to a server, which includes a wizard tool for creating a publisher account, adding application information, and uploading files to a website server, with databases for tracking user accounts and application versions, allowing for distribution and execution by other devices.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If virtual application files are uploaded to a web server for distribution, then accessibility and distribution capability are improved, but system complexity and management overhead increase

Engineering Contradiction:
Improvedistribution capabilityVSAvoidsystem complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a web server as an intermediary component between the virtual application files and end users. The web server receives uploads from client devices, stores the files in its file system, and serves them to users for download or execution. This intermediary handles the complexity of file management, authentication, and distribution protocols, allowing simple client devices to publish applications without needing complex server management capabilities.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If a wizard tool is used to streamline the uploading process, then ease of operation is improved, but processing time and steps increase

Engineering Contradiction:
Improveuploading easeVSAvoidprocessing time
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The wizard tool performs preliminary actions by pre-configuring upload parameters, authentication credentials, and file metadata before the actual upload begins. The system prepares the upload session in advance, validates file formats, and sets up the transfer protocol parameters beforehand. This preliminary preparation consolidates multiple configuration steps into a single automated process, reducing the perceived time burden on users despite the additional processing steps.

Inventive Principle:
Principle #10Preliminary action

3Loss of information

If databases are implemented for tracking user accounts and application versions, then information management is improved, but device complexity increases

Engineering Contradiction:
Improvetracking accuracyVSAvoiddatabase complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The patent segments the database system into separate functional components: a user account database for storing publisher credentials and permissions, an application metadata database for tracking virtual application files and their versions, and a download log database for recording user activity. Each database table is designed with specific fields relevant to its function, allowing independent management and optimization of each data storage component without requiring a monolithic complex database structure.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS10110663B2Method and system for publishing virtual applications to a web server
Publication Date: 2018.10.23 CODE SYSTEMS CORP
  • US10110663B2 patent drawing
  • US10110663B2 patent drawing
  • US10110663B2 patent drawing

AI summary

A method and system for publishing virtual applications on the Internet. The method includes obtaining a list of applications associated with a publisher from a server computing device and displaying the list to a user via a user interface. Next, a selection by the user of one of the applications is received from the user interface. A new virtualized version of the selected application is built. The virtualized version includes at least one application file that at least partially implements the new virtualized version of the selected application. Then, the application file is uploaded to the server computing device. An application address is received from the server computing device and a link to the application address is displayed to the user via the user interface. The virtualized version of the application is available at the application address for download and execution over a network (e.g., the Internet).