Firmware Update Timing for M2M Devices in Roaming Networks

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current M2M device management systems face challenges in efficiently and cost-effectively managing firmware updates for devices located in roaming partner networks or satellite-connected networks, as these updates can be expensive and disrupt network operations, especially when considering airtime costs and network connectivity types.

Innovation Solution

A firmware control management device and method that determine whether to push firmware updates to M2M devices based on configuration information, firmware details, and network connectivity, optimizing updates by considering costs and network conditions, and allowing devices to operate in minimal function mode until a suitable network is connected for updates.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If firmware updates are pushed to M2M devices in roaming partner networks or satellite-connected networks, then device functionality and performance are improved, but network costs and airtime expenses increase significantly

Engineering Contradiction:
Improvedevice functionalityVSAvoidnetwork costs
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The system changes the parameter of update timing by evaluating network cost parameters and device location parameters. It determines optimal update moments when devices are in low-cost networks rather than pushing updates regardless of network conditions. This resolves the contradiction by maintaining device functionality while minimizing network costs through parameter-based decision making.

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The system performs preliminary evaluation of network conditions and device states before initiating firmware updates. By assessing airtime costs and connectivity types in advance, it prevents costly updates in satellite or roaming networks, thereby improving device functionality only when cost-effective opportunities arise.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If firmware updates are pushed to M2M devices, then device performance and security are improved, but network operations are disrupted

Engineering Contradiction:
Improvedevice performanceVSAvoidnetwork operations
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system dynamically adjusts update scheduling based on real-time network conditions and device operational states. Rather than static update policies, it adapts timing and prioritization to minimize disruption to network operations while ensuring device performance improvements are achieved during appropriate windows.

Inventive Principle:
Principle #15Dynamics

3Loss of energy

If firmware updates are delayed for cost optimization, then network costs are reduced, but device security vulnerabilities increase

Engineering Contradiction:
Improvenetwork costsVSAvoidsecurity vulnerabilities
Core Design Contradiction:
Loss of energyVSObject-affected harmful factors

Solution Approach 1:

The system implements feedback mechanisms that continuously monitor device security status, vulnerability levels, and network cost conditions. When security vulnerabilities exceed thresholds, the system triggers urgent update evaluations that may override cost considerations, ensuring security is maintained while still optimizing costs for non-critical updates.

Inventive Principle:
Principle #23Feedback

Data Source

PatentEP2912863B1Cost optimization for firmware updates for globally mobile machine-to-machine devices
Publication Date: 2016.12.14 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
  • EP2912863B1 patent drawing
  • EP2912863B1 patent drawing
  • EP2912863B1 patent drawing

AI summary

A firmware control management device and a method implemented by the firmware control management device are described herein which are configured to determine whether or not to push a firmware update to a machine-to-machine (M2M) device.