Aerosol Provision Device Updates via Staged Subset Rollout

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing aerosol provision systems lack efficient methods for updating their functionality and security, necessitating improved software update mechanisms to ensure consistent performance and user safety.

Innovation Solution

A method and system for updating aerosol provision devices using an authorised computing system that sends software update files to subsets of devices, adjusts updates based on implementation data, and adapts software versions accordingly.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If software update files are sent to all aerosol provision devices simultaneously, then update speed is improved, but system reliability deteriorates due to potential implementation failures across the entire fleet

Engineering Contradiction:
Improveupdate speedVSAvoidsystem reliability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent segments the aerosol provision device fleet into multiple subsets and distributes software updates to these subsets at different times rather than simultaneously updating all devices. This segmentation allows the system to maintain reliability by isolating potential implementation failures to specific subsets while preserving overall productivity through continuous updating of other subsets.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements preliminary testing by sending software update files to a first subset of devices before deploying to the entire fleet. The system receives implementation data from the first subset, determines whether the update was successful, and only then proceeds to send updates to subsequent subsets. This preliminary action prevents widespread deployment of faulty software while maintaining efficient update progression.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If software updates are tested extensively before deployment, then system reliability is improved, but update time increases

Engineering Contradiction:
Improvesoftware update reliabilityVSAvoidupdate time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent applies partial action by implementing software updates in staged portions across different device subsets rather than requiring complete testing across the entire fleet before any deployment. The system performs sufficient testing on the first subset to determine update success, then progressively rolls out to additional subsets, achieving reliable deployment without the time cost of exhaustive pre-deployment testing across all devices.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

The patent incorporates feedback mechanisms where the system receives implementation data from each subset after software deployment, determines whether the update was successful, and uses this feedback to guide subsequent deployment decisions. This feedback loop enables the system to maintain high reliability by stopping deployment if failures occur, while minimizing update time by proceeding quickly when feedback indicates success.

Inventive Principle:
Principle #23Feedback

3Productivity

If software updates are sent to large subsets of devices, then productivity is improved, but the ability to detect and measure implementation issues deteriorates

Engineering Contradiction:
Improveupdate throughputVSAvoidimplementation issue detection
Core Design Contradiction:
ProductivityVSDifficulty of detecting and measuring

Solution Approach 1:

The patent segments the device fleet into manageable subsets of specific sizes, allowing the system to maintain productivity by updating multiple subsets sequentially while preserving the ability to detect and measure implementation issues within each subset. The segmentation creates appropriate granularity for monitoring and troubleshooting without sacrificing overall update throughput.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentEP4621559A1Aerosol provision system
Publication Date: 2025.09.24 NICOVENTURES TRADING LTD
  • EP4621559A1 patent drawingFigure 1
  • EP4621559A1 patent drawingFigure 2
  • EP4621559A1 patent drawingFigure 3

AI summary

An authorised computing system 510 for updating functionality of a plurality of aerosol provision devices 515, the plurality of aerosol provision devices 515 having a first subset of aerosol provision devices 520 and a second subset of aerosol provision devices 530. The authorised computing system 510 is configured to: send a first software update file comprising first software to each aerosol provision device of the first subset of aerosol provision devices 520; receive data relating to the attempting to implement the first software of the software update file by the first subset of aerosol provision devices 520; and in dependence of the data relating to the attempting to implement the first software of the first software update file, send a second software update file including second software to the second subset of the aerosol provision devices 530.