Distributed OTA Software Updates via Intermediate Mobile Computing Platforms

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Updating software for a large fleet of remote units or MCPs using a limited number of back-end servers results in high traffic load and significant delays.

Innovation Solution

Designating a set of remote units or MCPs to act as intermediate download servers, allowing them to download software updates from a back-end server and then distribute these updates to other units in the fleet, thereby offloading traffic and reducing the burden on the servers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If a limited number of back-end servers are used to update a large fleet of MCPs, then system simplicity is maintained, but traffic load on servers increases and update delays occur

Engineering Contradiction:
Improveserver infrastructure complexityVSAvoidsoftware update speed
Core Design Contradiction:
Device complexityVSProductivity

Solution Approach 1:

The patent introduces intermediary MCPs (mobile computing platforms) that act as intermediate download servers between the back-end server and other MCPs in the fleet. These intermediary MCPs download software updates from the back-end server and then distribute them to other MCPs locally, reducing the traffic load on back-end servers and accelerating update deployment across the fleet.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the software update distribution function by designating specific MCPs as intermediate download servers. This segmentation divides the fleet into groups, each served by a designated intermediary MCP, allowing parallel distribution of updates and reducing the burden on central back-end servers.

Inventive Principle:
Principle #1Segmentation

2Device complexity

If all MCPs download software updates directly from back-end servers, then system architecture remains simple, but network traffic load on servers becomes excessive

Engineering Contradiction:
Improvedownload architecture complexityVSAvoidnetwork bandwidth consumption
Core Design Contradiction:
Device complexityVSLoss of energy

Solution Approach 1:

The patent introduces intermediary MCPs that act as intermediate download servers between the back-end server and other MCPs in the fleet. These intermediary MCPs download software updates from the back-end server and then distribute them to other MCPs locally, reducing the traffic load on back-end servers and accelerating update deployment across the fleet.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent creates local copies of software updates on intermediary MCPs, which then serve as local sources for other MCPs. This copying approach eliminates the need for all MCPs to access the back-end server directly, significantly reducing network bandwidth consumption on the wide area network.

Inventive Principle:
Principle #26Copying

3Productivity

If a distributed download approach is implemented using intermediary MCPs, then update speed increases, but system complexity increases

Engineering Contradiction:
Improvesoftware update speedVSAvoiddownload distribution complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent introduces intermediary MCPs that act as intermediate download servers between the back-end server and other MCPs in the fleet. These intermediary MCPs download software updates from the back-end server and then distribute them to other MCPs locally, reducing the traffic load on back-end servers and accelerating update deployment across the fleet.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent implements a self-service mechanism where intermediary MCPs automatically download software updates from the back-end server and autonomously distribute them to other MCPs in their group. This automation reduces the need for complex centralized coordination while maintaining fast update distribution.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS9454358B1Distributed over the air programming
Publication Date: 2016.09.27 OMNITRACS LLC
  • US9454358B1 patent drawing
  • US9454358B1 patent drawing
  • US9454358B1 patent drawing

AI summary

The present disclosure generally relates to one or more improved systems, methods, and/or devices for leveraging the processing resources of remote units or mobile computing platforms (MCPs) to offload traffic associated with software updates from a back-end server to the one or more MCPs. In some examples, the back-end server may designate a set of remote units or MCPs to act as intermediate download servers for a remaining set of remote units or MCPs in the fleet. Accordingly, the present disclosure improves the overall system performance by distributing the functionalities of the back-end server to a set of remote units or MCPs.