Publisher-Subscriber Node Switching for Non-Interruptive Updates

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing software updates for devices, such as mobile devices, often require interruption of operations during installation, as they restrict access until the update is complete.

Innovation Solution

A non-interruptive software update method using a publisher-subscriber framework, where critical nodes continue to operate during the update, and non-critical nodes are temporarily deactivated or squeezed to free computing resources, allowing the update to proceed without disrupting device functionality.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a software update is installed using traditional methods, then the software is updated successfully, but the device operation is interrupted

Engineering Contradiction:

Improvesoftware update completionVSAvoiddevice operation continuity

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The system divides the device operations into critical nodes and non-critical nodes. Critical nodes continue operating during the software update, while non-critical nodes are temporarily deactivated or squeezed to free computing resources. This segmentation allows the software update to proceed without interrupting essential device functionality.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The publisher-subscriber framework acts as an intermediary layer that manages the transition from critical nodes to updated nodes. Subscribers are switched from the critical node to the updated node, allowing seamless replacement without interrupting the overall system operation. This intermediary mechanism enables non-interruptive software updates.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Productivity

If critical nodes continue to operate during software update, then device functionality is maintained, but computing resources are constrained

Engineering Contradiction:

Improvedevice operation continuityVSAvoidcomputing resource availability

Core Design Contradiction:

ProductivityVSUse of energy by moving object

Solution Approach 1:

The system dynamically adjusts resource allocation during the software update process. Non-critical nodes are temporarily deactivated or squeezed to free computing resources for the update installation. After the update is complete, non-critical nodes are reactivated. This dynamic resource management allows the system to balance operational continuity with update requirements.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The software update process is executed in periodic phases: first, non-critical nodes are deactivated to free resources; second, the software update is installed on critical nodes; third, non-critical nodes are reactivated. This periodic action pattern allows resource constraints to be managed while maintaining overall system functionality throughout the update process.

Inventive Principle:

Principle #19Periodic action

Data Source

PatentUS12423091B1Systems and methods for non-interruptive update

Publication Date: 2025.09.23 APPLE INC

AI summary

Implementations described herein provide systems and methods for a non-interruptive software update for a device. In one implementation, a software update for a critical node of a node system network of a controller of the device is detected. The node system network utilizes a publisher-subscriber framework. The software update is installed, and the critical node continues to operate in the publisher-subscriber framework during the software update. The software update creates an updated node. The updated node is subscribed to the publisher-subscriber framework, and the critical node is replaced with the updated node within the publisher-subscriber framework by switching subscriber information from the critical node to the updated node.