IoT Platform Firmware Scheduling for M2M Connectivity

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

The growth of machine-to-machine (M2M) devices in home networks increases network traffic and energy consumption, leading to network congestion and inefficiencies in firmware updates, as conventional mechanisms often require complete shutdowns or standby modes, which can disconnect devices from remote access and prolong activation times.

Innovation Solution

An Internet of Things (IoT) platform intercepts activity messages from M2M devices to determine firmware update availability, schedules updates based on usage frequency and power source, and routes updates through optimized communication paths, ensuring devices remain connected and energy-efficient.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Use of energy by moving object

If conventional firmware update mechanisms are used (complete shutdown or standby mode), then energy consumption is reduced, but device connectivity and activation time are worsened

Engineering Contradiction:

Improveenergy consumptionVSAvoiddevice connectivity

Core Design Contradiction:

Use of energy by moving objectVSReliability

Solution Approach 1:

The system performs preliminary actions by scheduling firmware updates in advance during periods of low device usage and low network traffic. The scheduler analyzes historical usage patterns to identify optimal update windows before the device enters high-activity modes, ensuring updates are queued and executed proactively rather than reactively during shutdown or standby transitions.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system dynamically adjusts the firmware update scheduling based on real-time conditions including device usage patterns, network traffic levels, and power source status. The scheduler continuously monitors these parameters and adapts update timing accordingly, transitioning from static scheduled updates to dynamic condition-based scheduling that optimizes both energy consumption and connectivity reliability.

Inventive Principle:

Principle #15Dynamics

2Ease of operation

If firmware updates are scheduled during high usage periods, then device availability is improved, but network congestion increases

Engineering Contradiction:

Improvedevice availabilityVSAvoidnetwork congestion

Core Design Contradiction:

Ease of operationVSObject-generated harmful factors

Solution Approach 1:

The system implements feedback mechanisms where the scheduler continuously monitors network traffic conditions and device usage patterns. Based on this feedback, the scheduler dynamically adjusts update scheduling decisions, delaying updates during periods of high network congestion or high device usage, and accelerating updates during low-traffic periods. This closed-loop control ensures updates occur at optimal times without causing network overload.

Inventive Principle:

Principle #23Feedback

Solution Approach 2:

The system employs periodic scheduling of firmware updates based on predicted low-usage intervals. Rather than attempting updates continuously or on-demand, the scheduler divides update opportunities into periodic windows aligned with historical usage cycles, concentrating update activities during naturally occurring low-traffic periods to minimize network congestion impact.

Inventive Principle:

Principle #19Periodic action

3Use of energy by moving object

If devices are placed in standby mode to conserve energy, then power consumption is reduced, but activation time increases

Engineering Contradiction:

Improvepower consumptionVSAvoidactivation time

Core Design Contradiction:

Use of energy by moving objectVSLoss of time

Solution Approach 1:

The system performs preliminary actions by pre-loading firmware updates and preparing device systems during low-usage periods before standby mode is activated. Update packages are downloaded and staged in advance, and system components are pre-configured for update execution, so that when the device wakes from standby, the update can begin immediately without prolonged activation delays.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The system maintains continuity of useful action by keeping firmware update processes active across standby transitions. Update downloads and preparations continue in the background during low-activity periods, and the update execution is seamlessly resumed or initiated immediately upon device activation, eliminating gaps in the update workflow that would otherwise extend activation time.

Inventive Principle:

Principle #20Continuity of useful action

Data Source

PatentUS20190324737A1Internet of Things Platform for Handling Firmware Transfer on Machine-to-Machine Devices

Publication Date: 2019.10.24 AT&T MOBILITY II LLC

AI summary

Concepts and technologies of handling firmware for machine to machine devices via a service provider network are provided herein. In an embodiment, a computer system can provide an Internet of Things platform. The computer system may include a processor configured to intercept, via a service provider network, an activity message sent from a machine-to-machine device. The processor can obtain a firmware version identifier and an equipment identifier from the activity message. The processor can determine that a firmware update package is available for the machine-to-machine device, and in response, generate a schedule command that instructs a firmware scheduler to send a firmware update request to a firmware-over-the-air server. The processor can provide the schedule command to the firmware scheduler on behalf of the machine-to-machine device.