Multi-Tier Software Provisioning via Metadata Segmentation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Network-based software delivery faces latency issues due to the time-consuming transfer of large software distributions, which hampers rapid deployment and patching, especially in enterprise environments where significant delays occur when transferring multiple gigabytes of data.

Innovation Solution

A multi-tier architecture that allows software provisioning and access without requiring the entirety of the software distribution to be transferred upfront, utilizing a back-end object store, a middle-tier user space file system, and a front-end namespace unification/layered file system to separate software bits from application data, enabling on-demand file access and caching for efficient deployment and patching.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If network-based delivery is used to distribute software, then cost-effectiveness and provisioning efficiency are improved, but transfer latency increases due to large data volumes

Engineering Contradiction:
Improvesoftware provisioning efficiencyVSAvoidtransfer latency
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent segments the software distribution into two parts: metadata (stored locally on the target system) and actual software bits (stored remotely in object storage). This segmentation allows the provisioning process to complete quickly by only transferring metadata, while the actual software can be accessed on-demand from remote storage, thereby resolving the contradiction between provisioning efficiency and transfer latency.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent performs preliminary action by pre-storing metadata information about the software distribution locally on the target system before actual software access is needed. This metadata contains information about the software's location, structure, and dependencies, enabling immediate software provisioning without waiting for complete data transfer, thus improving productivity while minimizing time loss.

Inventive Principle:
Principle #10Preliminary action

2Speed

If complete software distribution is transferred upfront to target systems, then software access speed is improved, but network bandwidth consumption and deployment time increase

Engineering Contradiction:
Improvesoftware access speedVSAvoidnetwork bandwidth consumption
Core Design Contradiction:
SpeedVSLoss of energy

Solution Approach 1:

The patent applies partial action by transferring only the essential metadata portion of the software distribution upfront, rather than the complete software bits. The metadata is sufficient to enable immediate software access, while the actual software content is retrieved on-demand from remote object storage. This approach achieves fast software access speed while minimizing network bandwidth consumption.

Inventive Principle:
Principle #16Partial or excessive action

3Speed

If software is stored locally on target systems, then access speed is improved, but storage requirements and deployment complexity increase

Engineering Contradiction:
Improvesoftware access speedVSAvoiddeployment complexity
Core Design Contradiction:
SpeedVSDevice complexity

Solution Approach 1:

The patent segments software storage between local and remote locations. Metadata is stored locally on the target system to enable fast access and immediate provisioning, while the actual software bits are stored remotely in object storage to avoid consuming local storage resources. This segmentation reduces deployment complexity compared to storing complete distributions locally, while maintaining fast access speeds.

Inventive Principle:
Principle #1Segmentation

4Loss of time

If traditional media devices are used for software installation, then transfer latency is reduced, but cost and production facility requirements increase

Engineering Contradiction:
Improvetransfer latencyVSAvoidproduction facility requirements
Core Design Contradiction:
Loss of timeVSEase of manufacture

Solution Approach 1:

The patent extracts the essential provisioning function from physical media by using metadata stored locally on target systems. This metadata enables immediate software access without requiring physical media devices or production facilities for media manufacturing. The actual software is retrieved on-demand from object storage, achieving fast provisioning while eliminating the need for complex production facilities.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS11669318B2Rapid software provisioning and patching
Publication Date: 2023.06.06 ORACLE INT CORP
  • US11669318B2 patent drawing
  • US11669318B2 patent drawing
  • US11669318B2 patent drawing

AI summary

Disclosed is an approach to implement an architecture and methodology that allows rapid access to provisioned software without requiring the entirety of the software distribution to be transferred to the target system in an upfront manner. Instead, a multi-tier architecture is used that allows the software to be provisioned and accessed with efficient access and reads of distribution materials from one or more remote storage locations.