Selective Node Firmware Updates in Wireless Networks

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing nodal wireless networks face inefficiencies in software updates, particularly when dealing with multiple node types requiring different firmware updates, leading to time-consuming and bandwidth-intensive processes.

Innovation Solution

A system where a wireless enabled computing device acts as an update controller, sending announcements and packets with identifiers to specific node types, allowing each node to accumulate and install only relevant software updates while discarding irrelevant packets, leveraging a flooding protocol for efficient distribution.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If all firmware update packets are transmitted to all nodes in the network, then all nodes receive the update, but nodes with incompatible hardware waste bandwidth storing and processing irrelevant update packets

Engineering Contradiction:
Improveupdate delivery completenessVSAvoidbandwidth consumption
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent applies local quality by making each node's update reception behavior specific to its hardware type. Nodes filter incoming update packets based on whether the update is intended for their specific hardware variant, allowing compatible nodes to receive updates while incompatible nodes discard them. This selective reception optimizes bandwidth usage by preventing unnecessary data transmission to nodes that cannot utilize the update.

Inventive Principle:
Principle #3Local quality

2Manufacturing precision

If manual update initiation is required at each node, then update accuracy is high, but the update process becomes time-consuming and labor-intensive

Engineering Contradiction:
Improveupdate application accuracyVSAvoidupdate deployment time
Core Design Contradiction:
Manufacturing precisionVSLoss of time

Solution Approach 1:

The patent implements self-service by enabling nodes to autonomously determine whether they should apply received update packets. Each node checks its hardware type against the update's intended target hardware type and automatically decides whether to store and install the update or discard it. This automated self-determination eliminates the need for manual intervention at each node while maintaining accurate application of updates only to compatible devices.

Inventive Principle:
Principle #25Self-service

3Adaptability or versatility

If multiple firmware images are transmitted to support different node types, then all node types can be updated, but the transmission time and bandwidth usage increase significantly

Engineering Contradiction:
Improvenode type compatibilityVSAvoidupdate transmission duration
Core Design Contradiction:
Adaptability or versatilityVSDuration of action of moving object

Solution Approach 1:

The patent applies segmentation by dividing the firmware update process into separate transmissions for different hardware types. Instead of transmitting all firmware images simultaneously to all nodes, the system segments the update traffic so that each node type receives only its designated firmware image. This segmentation reduces overall transmission time and bandwidth consumption compared to broadcasting all firmware images to every node.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS11432167B2Selective updating of nodes of a nodal wireless network
Publication Date: 2022.08.30 ABL IP HLDG LLC
  • US11432167B2 patent drawing
  • US11432167B2 patent drawing
  • US11432167B2 patent drawing

AI summary

A network has wireless enabled nodes of more than one hardware type. A computing device obtains a software update for one of the node types and sends an announcement of availability through the network. The announcement includes a node type identifier. A node that recognizes the identifier as matching its own hardware type collects the software update through a series of one or more requested packet transfers from the controller. Each packet carrying part of the update also includes the node type identifier. A node of a different type that has received the packets may serve as a source of missing packets to other nodes. Alternatively, nodes needing missing packets can fetch them from the computing device. When the software update is completely received by a node of the identified type, that node reboots and executes the updated software. Any node of another type discards the packets.