Composite File Virtual File System for Application Deployment

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Deploying and distributing large numbers of executable files for applications, such as MATLAB-based applications, poses challenges in version control and file management, as conventional methods do not support strong encryption or treating these files as a single unit, and hiding human-readable files is impractical.

Innovation Solution

A self-contained virtual file system is created in the form of a distributable composite file that includes executable and data files, allowing for versioning, encryption, and management as a single unit, with an operating system-specific header for automatic execution.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If executable files are stored and deployed individually, then file management flexibility is maintained, but version control becomes impractical and file management complexity increases

Engineering Contradiction:
Improveversion controlVSAvoidfile management
Core Design Contradiction:
Ease of manufactureVSDevice complexity

Solution Approach 1:

The patent combines multiple executable files into a single composite file that can be deployed and managed as one unit. This composite file contains all necessary executable files and their dependencies, eliminating the need to manage individual files separately while maintaining version control through a single versioned package.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The composite file is structured with an organized internal hierarchy that segments executable files into logical groups while maintaining a unified external interface. This internal segmentation allows for structured organization without requiring external file management complexity.

Inventive Principle:
Principle #1Segmentation

2Reliability

If conventional deployment technologies are used, then simplicity is maintained, but strong encryption and content protection are not achieved

Engineering Contradiction:
ImprovesecurityVSAvoiddeployment structure
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The deployment structure uses a composite architecture combining encrypted composite files with an execution engine. The composite file format integrates multiple file types and encryption mechanisms into a unified structure that provides both security and executable functionality.

Inventive Principle:
Principle #40Composite materials

3Reliability

If human readable executable files are concealed, then security is improved, but most conventional technologies do not employ strong encryption

Engineering Contradiction:
Improvecontent protectionVSAvoidencryption implementation
Core Design Contradiction:
ReliabilityVSEase of manufacture

Solution Approach 1:

The patent applies encryption parameters to transform human-readable executable files into protected formats within the composite file. The encryption strength and methods can be adjusted as parameters to achieve the desired level of content protection while maintaining ease of implementation through standardized cryptographic approaches.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS8312423B1Deploying and distributing of applications and software components
Publication Date: 2012.11.13 MATHWORKS INC
  • US8312423B1 patent drawing
  • US8312423B1 patent drawing
  • US8312423B1 patent drawing

AI summary

A self-contained virtual file system is disclosed for deploying and distributing an application and/or software component. Executable files relating to the application are included in a distributable composite file. The composite file and a user front end application are deployed and distributed to an application user where the application is executed. An application provider can tag the composite file with the version information and other useful meta-data of the files for the application. The format of the composite file may support the storage of any kind of file types and associated meta-data. The composite file may contain the hierarchical directory structure of the files for the application so that the hierarchical directory structure is installed in the application user's electronic device.