Multi-Device OS Upgrade via Collaboration Plan

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In multi-device ecosystems, upgrading operating software (OS) often disrupts user activities due to downtime, as existing methods require devices to be inaccessible during the upgrade process, complicating management in complex schedules and daily activities.

Innovation Solution

A collaboration plan is generated between connected computing devices to execute OS upgrades without interrupting user activities, utilizing machine learning to predict usage patterns and prioritize upgrades, ensuring minimal disruption by sharing tasks and resources across devices.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional OS upgrade methods are used, then upgrade reliability is improved, but user activity continuity deteriorates due to device unavailability during upgrade

Engineering Contradiction:
Improveupgrade reliabilityVSAvoiduser activity continuity
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent segments the upgrade process into multiple phases: background verification, foreground activity capture, collaborative planning, and phased execution. By dividing the upgrade into discrete segments that can be executed independently across different devices, the system maintains user activity continuity while ensuring upgrade reliability. The foreground activity capture segment allows recording of user interactions before upgrade, enabling restoration after upgrade completes.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements preliminary actions by verifying OS versions and capturing foreground activities before actual upgrade execution. The system pre-verifies which devices need upgrading and pre-captures user activities that must be preserved. This preliminary preparation allows the upgrade to proceed without interrupting ongoing user tasks, as the necessary information is already gathered and stored.

Inventive Principle:
Principle #10Preliminary action

2Device complexity

If devices are upgraded simultaneously, then upgrade management is simplified, but system complexity increases due to coordination requirements in multi-device ecosystems

Engineering Contradiction:
Improveupgrade management complexityVSAvoidcollaboration plan execution
Core Design Contradiction:
Device complexityVSEase of manufacture

Solution Approach 1:

The patent merges multiple devices into a collaborative ecosystem where upgrade decisions are made collectively. Instead of managing devices independently, the system combines their upgrade requirements into a unified collaboration plan. This merging approach simplifies management by treating the device fleet as a single coordinated unit, while the system automatically handles the complexity of individual device execution.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent implements feedback mechanisms where devices provide information about their OS versions, user activities, and upgrade status. This feedback loop enables the system to dynamically adjust the collaboration plan based on real-time device conditions. The feedback from foreground activity capture allows the system to modify upgrade timing to avoid disrupting user tasks.

Inventive Principle:
Principle #23Feedback

3Loss of time

If upgrade downtime is minimized, then user experience is improved, but upgrade precision requirements increase to ensure seamless transition

Engineering Contradiction:
Improveupgrade downtimeVSAvoidupgrade timing precision
Core Design Contradiction:
Loss of timeVSManufacturing precision

Solution Approach 1:

The patent applies dynamics by making the upgrade timing flexible rather than fixed. The collaboration plan dynamically adjusts upgrade schedules based on real-time device availability, user activity patterns, and system conditions. This dynamic approach minimizes downtime by finding optimal upgrade windows, while the system handles the precision requirements through adaptive scheduling that responds to actual device state changes.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent ensures continuity of useful action by capturing foreground activities before upgrade and preserving them during the upgrade process. The system maintains user activity continuity by recording interactions beforehand and ensuring they can be restored after upgrade completes. This continuous capture and preservation mechanism eliminates interruption to useful user actions during the upgrade process.

Inventive Principle:
Principle #20Continuity of useful action

Data Source

PatentUS12153912B2Upgrading operating software (“OS”) for devices in a multi-device ecosystem
Publication Date: 2024.11.26 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US12153912B2 patent drawing
  • US12153912B2 patent drawing
  • US12153912B2 patent drawing

AI summary

Embodiments are provided for upgrading operating application in a multi-device ecosystem in a computing environment. Various types of computing devices are determined to be connected to a multi-device computing network. A collaboration plan is generated between the computing devices to execute an operating application operation event on each of the computing devices without interrupting user activities executing on each of the computing devices. Operating applications on each of the computing devices are upgraded according to the collaboration plan without interrupting each of the f user activities on each of the computing devices.