Fleet Application Deployment via Base Group Request Filtering

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Efficiently updating application definitions across a large fleet of devices in remote program execution and storage systems is challenging due to the need for simultaneous updates across multiple machines, which can be time-consuming and inefficient.

Innovation Solution

Deploying application definitions using request filters and base groups, where a deployment system notifies fleet machines of available definitions, allowing them to retrieve and process service requests only when equipped with the necessary definitions, reducing communication overhead and enabling per-service-request updates.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If application definitions are updated across a large fleet of devices simultaneously, then all devices can process service requests with the latest definitions, but the update process becomes time-consuming and inefficient

Engineering Contradiction:
Improveconsistency of application definitionsVSAvoidupdate deployment time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent segments the fleet of devices into different groups based on their capabilities and requirements. Instead of updating all devices simultaneously, the system divides the update process into manageable segments that can be deployed independently to different device groups, reducing overall update time while maintaining consistency within each segment.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements preliminary action by pre-loading and caching application definitions on devices before they are actually needed. The system anticipates future service requests and proactively deploys relevant application definitions to devices in advance, so that when service requests arrive, the definitions are already available, eliminating update delays.

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If application definitions are deployed to all fleet machines, then service requests can be processed anywhere in the fleet, but networking overhead increases

Engineering Contradiction:
Improveservice request processing flexibilityVSAvoidnetworking overhead
Core Design Contradiction:
Adaptability or versatilityVSLoss of energy

Solution Approach 1:

The patent applies local quality by tailoring the deployment of application definitions to the specific characteristics of each fleet machine. Instead of uniformly deploying all definitions to all machines, the system analyzes each machine's capabilities, location, and expected workload, then deploys only the relevant definitions locally. This reduces networking overhead by minimizing unnecessary data transmission while maintaining the flexibility to process service requests across the fleet.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent introduces an intermediary component that acts as a broker between service requests and fleet machines. This intermediary intelligently routes service requests to the most appropriate machines that already have the required application definitions cached, avoiding the need to deploy definitions across the entire fleet. The intermediary mediates between the need for flexibility and the cost of networking overhead.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Speed

If application definitions are cached on fleet machines for quick access, then service requests can be processed faster, but storage space is consumed on each machine

Engineering Contradiction:
Improveservice request processing speedVSAvoidstorage space on fleet machines
Core Design Contradiction:
SpeedVSVolume of stationary object

Solution Approach 1:

The patent applies partial action by caching only the subset of application definitions that are most likely to be needed by each specific fleet machine, rather than caching all definitions. The system analyzes historical data and usage patterns to determine which definitions should be cached locally on each machine. This approach achieves fast processing speed for the majority of service requests while minimizing storage space consumption by caching only necessary definitions.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS9705755B1Application definition deployment with request filters employing base groups
Publication Date: 2017.07.11 AMAZON TECH INC
  • US9705755B1 patent drawing
  • US9705755B1 patent drawing
  • US9705755B1 patent drawing

AI summary

A method and apparatus for application definition deployment using base groups are provided. In the method and apparatus, service requests are received at a request queue and queued by the request queue. The request queue also receives an availability message from a fleet device indicating application definitions available to the fleet device using base groups. The request queue provides a service request to the fleet device, whereby the service request is identified based on the base groups indicated by the fleet device.