IoT Update Control via Server Mediation and State Readiness

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional methods for updating Internet-of-Things (IoT) devices are cumbersome, often requiring direct interaction and specialized hardware or technicians, especially since IoT devices lack a rich user interface and are typically used at specific times, making remote initiation and control of updates challenging.

Innovation Solution

A computer system and method that utilize a switchboard server to remotely manage IoT device updates by receiving selection indications, sending state queries, determining readiness, and initiating updates without direct interaction with the IoT device, allowing users to control when updates occur using a more familiar device.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If conventional update methods are used for IoT devices, then updates can be applied, but the process becomes cumbersome and requires direct device interaction or specialized technicians

Engineering Contradiction:
Improveease of update operationVSAvoidcomplexity of update process
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent introduces a server as an intermediary between the user and the IoT device. The server receives update requests from the user's computing device, manages the update process, and communicates with the IoT device. This intermediary simplifies the user's interaction to basic actions (initiating and confirming updates) while handling the complex communication and coordination with the IoT device in the background.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The IoT device is designed to autonomously provide state information about itself when queried by the server, and to self-update when receiving update instructions. The device can independently determine its readiness state and execute updates without requiring specialized technicians or complex user operations, enabling self-service update capability.

Inventive Principle:
Principle #25Self-service

2Reliability

If IoT devices are updated using portable media and direct interaction, then updates can be applied, but the process is time-consuming and cumbersome

Engineering Contradiction:
Improvereliability of update applicationVSAvoidtime required for update
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system checks the IoT device's state information in advance to determine readiness before initiating the update. The server queries the device's current state (such as operational status, memory availability, and power level) and only proceeds with updates when readiness conditions are met. This preliminary assessment prevents update failures and ensures reliable update application.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The server acts as a mediator that streamlines the update process by automatically managing file transfers, coordinating between the user's computing device and the IoT device, and handling the complex sequence of operations. This reduces the time required by eliminating manual steps and automating the update workflow.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If specialized hardware or technicians are used for IoT device updates, then updates can be applied reliably, but the process becomes complex and requires specialized resources

Engineering Contradiction:
Improvereliability of update applicationVSAvoidease of update operation
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The IoT device is equipped with self-diagnostic and self-update capabilities. It can autonomously provide state information about its readiness, receive update instructions from the server, and execute the update process independently. This self-service approach eliminates the need for specialized technicians while maintaining reliable update application through automated readiness checks and controlled update execution.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The server provides a universal update management platform that can handle multiple IoT devices with different states and requirements. It implements a standardized protocol for checking readiness and applying updates that works across various device types, eliminating the need for device-specific specialized hardware or technician expertise while maintaining reliability through consistent update management.

Inventive Principle:
Principle #6Universality (Multi-functionality)

4Adaptability or versatility

If users must directly interact with IoT devices for updates, then updates can be controlled, but the process is cumbersome since devices lack rich user interfaces

Engineering Contradiction:
Improveflexibility of update controlVSAvoidease of update operation
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The server serves as an intermediary that translates the user's update control requirements into device-specific commands. The user interacts with the server through a familiar computing device interface to initiate and confirm updates, while the server handles the complex communication with the IoT device. This maintains user control flexibility while eliminating the need for direct interaction with the IoT device's limited interface.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS11119756B2System and method for controlling updates to internet-of-things devices
Publication Date: 2021.09.14 MALIKIE INNOVATIONS LTD
  • US11119756B2 patent drawing
  • US11119756B2 patent drawing
  • US11119756B2 patent drawing

AI summary

A computer system includes a processor, a communications subsystem, and a non-transitory computer-readable storage medium. The computer-readable medium stores instructions that when executed by the processor adapt the computer system to receive an indication of a second device selected, at a first device, for update; send an indication signalling the second device to send state information about the second device; receive state information about the second device; determine, based on the state information, that the second device is ready to perform an update; send, to the first device, an indication that the second device is ready to perform the update; receive, from the first device, an indication to update the second device; and, send a corresponding indication to the second device. The second device is configured to begin updating in response to such an indication without any direct interaction with it. Related methods and computer-readable media are also described.