Firmware Update Consistency via Pull-Based Bundling

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Modern applications face issues with maintaining operating consistency across multiple users during firmware updates, as existing push protocols lead to inefficient resource usage and data inconsistencies, causing invalid data sets and reduced processing efficiency.

Innovation Solution

Implementing a method where users request updates at predetermined intervals, creating consistency groups to synchronize session data, allowing each user to pull updates as a bundle, ensuring accurate and timely reflection of changes across all sessions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a push protocol is used to constantly push changes onto the system, then changes are automatically reflected, but resource consumption increases and processing efficiency decreases

Engineering Contradiction:
Improvedata consistencyVSAvoidprocessing efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent inverts the traditional push protocol by implementing a pull mechanism where users actively request updates at predetermined intervals rather than passively receiving pushed changes. This inversion allows the system to reduce constant processing while maintaining data consistency through on-demand updates.

Inventive Principle:
Principle #13The other way round (Inversion)

Solution Approach 2:

The patent implements periodic action by establishing predetermined time intervals for users to request updates. Instead of continuous pushing, the system uses scheduled periodic requests that balance data freshness needs with resource conservation, allowing the system to process updates only when needed rather than constantly.

Inventive Principle:
Principle #19Periodic action

2Reliability

If changes are pushed onto the webpage constantly, then users see updates immediately, but the webpage may reflect changes at different times causing out-of-sync data

Engineering Contradiction:
Improvedata consistencyVSAvoiduser experience
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent merges multiple change packets into a single consolidated update bundle that is delivered atomically to the user's application. This merging ensures that all changes made during a session are reflected together at the next update request, preventing out-of-sync data while maintaining immediate visibility of all changes.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent implements feedback mechanisms where users actively request updates at predetermined intervals, creating a feedback loop that ensures data consistency. The system tracks user requests and delivers consolidated updates in response, ensuring that users always see the most current and consistent state of the data.

Inventive Principle:
Principle #23Feedback

3Reliability

If the system constantly processes changes, then data is always up-to-date, but processing speed decreases and resources are wasted

Engineering Contradiction:
Improvedata freshnessVSAvoidprocessing speed
Core Design Contradiction:
ReliabilityVSSpeed

Solution Approach 1:

The patent applies periodic action by establishing predetermined time intervals for update requests instead of continuous processing. The system processes changes only when users actively request updates at these intervals, significantly reducing processing load while maintaining data freshness within the acceptable time frame of the interval.

Inventive Principle:
Principle #19Periodic action

Solution Approach 2:

The patent implements preliminary action by pre-establishing predetermined time intervals for updates before users actually need them. This allows the system to prepare and bundle changes in advance during low-activity periods, then deliver them efficiently when requested, improving processing speed while maintaining data freshness.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10372436B2Systems and methods for maintaining operating consistency for multiple users during firmware updates
Publication Date: 2019.08.06 LENOVO GLOBAL TECHNOLOGIES SWITZERLAND INTERNATIONAL GMBH
  • US10372436B2 patent drawing
  • US10372436B2 patent drawing
  • US10372436B2 patent drawing

AI summary

Systems and methods for maintaining operating consistency for multiple users during firmware updates. According to an aspect, a method includes receiving, at a predetermined time interval, a request from one or more users of an application to carry out a result on a computing device. The method also includes analyzing a plurality of sessions of the application on the computing device servicing one or more users. The method also includes determining if one of the plurality of sessions contains an updated data. Further, the method includes creating at least one of a plurality of consistency groups based on the updated data. Further, the method includes updating, after the predetermined time interval, the application based on the at least one of the plurality of consistency groups.