Mobile Software Deployment via Distributed Repositories

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The limitations of mobile networks in providing comprehensive software deployment for devices in motion, due to limited bandwidth and dynamic IP address changes, as well as the complexity introduced by diverse hardware requirements, hinder efficient mass software deployment in mobile environments.

Innovation Solution

A client-server deployment architecture that utilizes a deployment orchestrator to manage software deployment across mobile devices, where end devices with support package repositories offload download traffic, dynamically adjust for IP address changes, and select appropriate software packages based on hardware requirements, minimizing reliance on central repositories and optimizing bandwidth usage.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Area of stationary object

If software deployment is performed through mobile network from central repository, then coverage area is improved, but bandwidth consumption increases and deployment time extends

Engineering Contradiction:
Improvecoverage areaVSAvoiddeployment time
Core Design Contradiction:
Area of stationary objectVSLoss of time

Solution Approach 1:

The patent segments the centralized repository into distributed support package repositories located on multiple end devices throughout the network. Each end device hosts a local repository, dividing the deployment function across multiple nodes rather than relying on a single central repository. This segmentation enables parallel deployment operations and reduces the distance data must travel, thereby decreasing deployment time while maintaining broad coverage.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a spatial dimension to the deployment architecture by positioning support package repositories on geographically distributed end devices. Instead of a single centralized location, repositories are distributed across multiple physical locations in the network, creating a multi-dimensional deployment topology. This allows devices to download from the nearest available repository, reducing network traversal time and improving overall deployment efficiency.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Adaptability or versatility

If mobile network is used for software deployment, then device mobility is supported, but network bandwidth is limited causing slow deployment

Engineering Contradiction:
Improvedevice mobility supportVSAvoiddeployment speed
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent implements preliminary action by having end devices download and cache support packages locally before they are needed for deployment. The support package repository on each end device pre-stores necessary software packages, so when deployment is required, the packages are already available locally or can be quickly obtained from nearby nodes. This eliminates the need for large-volume downloads during the actual deployment process, significantly improving deployment speed while maintaining mobile network usage.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent uses copying by replicating support packages across multiple end devices that serve as repository hosts. Instead of all devices downloading from a single central source, each repository node contains copies of the necessary support packages. This replication strategy distributes the bandwidth load across multiple connections and allows parallel downloads, thereby increasing overall deployment speed while supporting device mobility throughout the network coverage area.

Inventive Principle:
Principle #26Copying

3Adaptability or versatility

If devices move between locations during deployment, then mobility is enabled, but IP address changes cause deployment interruptions

Engineering Contradiction:
ImprovemobilityVSAvoiddeployment reliability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent implements feedback mechanisms where end devices continuously monitor and report their location and network status to the deployment orchestrator. The orchestrator receives real-time feedback about device movement and IP address changes, allowing it to dynamically adjust deployment strategies. When a device moves to a new location with a different IP address, the feedback loop enables the orchestrator to re-establish connections and maintain deployment continuity, thereby preserving reliability while supporting mobility.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent applies dynamics by making the deployment architecture adaptive to changing network conditions. The system dynamically adjusts repository selection based on current device locations and network topology. When devices move and IP addresses change, the deployment orchestrator dynamically reroutes deployment operations to maintain connectivity. This dynamic adaptation allows the system to maintain high reliability even as devices move freely throughout the mobile network coverage area.

Inventive Principle:
Principle #15Dynamics

4Adaptability or versatility

If diverse hardware components are added to devices, then functionality is enhanced, but deployment complexity increases

Engineering Contradiction:
Improvehardware functionalityVSAvoiddeployment complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent applies local quality by tailoring the support packages deployed to each end device according to its specific hardware configuration. The deployment orchestrator analyzes the hardware capabilities of each device and selects appropriate software packages that match the local hardware characteristics. This ensures that each device receives customized software optimized for its specific components (such as cameras, microphones, Wi-Fi adaptors), enhancing functionality while managing deployment complexity through automated hardware-aware package selection.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent uses parameter changes by adapting deployment parameters based on detected hardware configurations. The system changes deployment parameters such as package selection, installation paths, and configuration settings according to the specific hardware parameters of each end device. This parameter adaptation allows the deployment process to automatically adjust to diverse hardware setups without requiring manual intervention, thereby enhancing hardware functionality while keeping deployment complexity manageable through automated parameter adjustment.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS20240319977A1Method and system for centralized software deployment to mobile devices
Publication Date: 2024.09.26 QUANTA CLOUD TECH INC
  • US20240319977A1 patent drawing
  • US20240319977A1 patent drawing
  • US20240319977A1 patent drawing

AI summary

A system and method for deploying software packages for end devices that communicate through a mobile network is disclosed. A deployment orchestrator is coupled to the mobile network. End devices communicate with each other through the mobile network. At least one of end devices includes a support package repository storing software packages. When a new end device requires software package deployment, the deployment orchestrator locates at least one of the end devices with the support package repository. The new end device receives software packages from the end device including the support package repository through the mobile network.