Dynamic Network Device Configuration via Segmented Firmware
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for updating firmware in network devices within wireless utility distribution networks require devices to be taken offline, leading to downtime and increased overhead, as different devices often require separate updates due to incompatible firmware, and frequent updates are necessary to respond to changing customer requests.
Innovation Solution
A computer-implemented method that dynamically modifies the operational behavior of nodes by using a configuration file to specify conditions and actions, allowing nodes to detect and respond to events without updating firmware, and enabling different types of nodes to be updated using a single configuration file.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If firmware is updated to modify operational behavior of network devices, then the operational characteristics can be changed to meet customer requests, but the device must be taken offline causing downtime and loss of monitoring capability
Solution Approach 1:
The patent segments the firmware into two independent components: a persistent firmware core that remains unchanged and continues to execute, and a separate configuration file that contains modifiable operational parameters. This segmentation allows the configuration file to be updated and applied without stopping the execution of the persistent firmware, thereby eliminating device downtime while still enabling operational behavior modification.
Solution Approach 2:
The patent introduces a configuration file as an intermediary layer between the control center and the persistent firmware. The configuration file acts as a mediator that carries operational parameters and can be applied dynamically without requiring changes to the persistent firmware itself. This intermediary mechanism enables operational behavior changes while the device remains online and functional.
2Ease of manufacture
If separate firmware updates are applied to different types of network devices, then each device can be optimized for its specific function, but the overhead and complexity of managing multiple firmware versions increases
Solution Approach 1:
The patent creates a universal configuration file format that can be applied across multiple types of network devices (smart meters, smart gates, smart valves) without requiring device-specific firmware modifications. The persistent firmware maintains device-specific functionality, while the standardized configuration file provides a unified mechanism for operational parameter management, thereby reducing the complexity of managing multiple firmware versions while preserving device-specific optimization.
3Productivity
If frequent firmware updates are deployed to respond to changing customer requests, then the system can adapt quickly to new requirements, but the frequency of offline updates and associated downtime increases
Solution Approach 1:
The patent implements a dynamic configuration update mechanism where operational parameters can be modified by applying new configuration files without requiring device restart or offline mode. The persistent firmware continues to execute continuously, and configuration changes are applied dynamically, allowing frequent updates in response to customer requests without incurring cumulative downtime losses.
Solution Approach 2:
The patent ensures continuous operation of the network device by maintaining persistent firmware execution while allowing configuration file updates. The device continues to perform its monitoring and control functions without interruption, ensuring continuity of useful action even as operational parameters are updated frequently to meet changing customer requirements.
Data Source
AI summary
A network device includes one or more processors and a memory storing firmware that when executed by the one or more processors causes the network device to perform operations including executing the firmware according to a configuration file, wherein the executing includes receiving one or more commands updating the configuration file to become a modified configuration file; and executing the firmware according to the modified configuration file. Wherein executing the firmware according to the modified configuration file includes: extracting a mode from the modified configuration file, the mode indicating a condition, a set of parameters, and a rule mapping the condition to an action; evaluating the condition based on one or more parameter values associated with the set of parameters; and in response to determining that the condition has been met, performing the action, wherein performing the action modifies how a resource is distributed at a location.