IoT Network Logic Auto-Rollback Driver Regression

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

IoT devices often experience network connectivity issues after firmware updates, leading to 'regression' where the device can no longer connect to the network, requiring user intervention like factory resets, which may not restore the latest firmware version and can disrupt functionality.

Innovation Solution

A network communication logic that automatically detects impaired connectivity post-upgrade and replaces the current connection driver with a previous functional version, ensuring seamless operation without user intervention by erasing the current driver and triggering the previous version, with adjustable thresholds for connection attempts and failure reporting.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If firmware updates are applied to improve functionality, then device capabilities are enhanced, but network connectivity may be impaired due to regression bugs

Engineering Contradiction:
Improvedevice functionalityVSAvoidnetwork connectivity
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The firmware is segmented into functional components, with the connection driver separated as an independent module that can be updated and rolled back separately from the rest of the firmware, allowing functionality improvements while maintaining connectivity stability

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary actions by maintaining backup versions of connection drivers and establishing automatic detection mechanisms before connectivity issues manifest, enabling proactive restoration rather than reactive recovery

Inventive Principle:
Principle #10Preliminary action

2Reliability

If automatic rollback mechanisms are implemented to restore connectivity, then network connection is restored, but device complexity increases

Engineering Contradiction:
Improvenetwork connectivityVSAvoidfirmware management
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system implements self-service by automatically detecting connectivity failures, identifying the problematic firmware version, and restoring previous working versions without requiring user intervention or external assistance

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system establishes feedback loops where connectivity status is continuously monitored, and automatic corrective actions are triggered based on detected failures, creating a closed-loop system that self-corrects without external input

Inventive Principle:
Principle #23Feedback

3Reliability

If factory reset is performed to fix connectivity issues, then device can reconnect to network, but user-defined parameters are lost and latest firmware version is not restored

Engineering Contradiction:
Improvenetwork connectivityVSAvoidconfiguration parameters
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The connection driver is extracted as a separate, independently manageable component from the main firmware and configuration parameters, allowing selective restoration of connectivity functionality while preserving user-defined settings and maintaining latest firmware version

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentEP3481032B1Regression safe network communication logic for an IoT device and method of managing the same
Publication Date: 2022.11.02 NETATMO
  • EP3481032B1 patent drawingFigure 1
  • EP3481032B1 patent drawingFigure 2
  • EP3481032B1 patent drawingFigure 3

AI summary

The invention discloses a network communication logic that is configured to have an access to one or more previous versions of a connection driver. The network communication logic is capable to generate and evaluate connections/configuration tests and, if the tests fail for a predefined duration or number of times, the network communication logic is configured to automatically trigger a replacement of a current version of the connection driver by one of the previous versions. Thanks to the invention, the loT device in which this type of network communication logic is embedded, may become operative again, even if an update has disseminated a version that does not work in the configuration of the device.