NIC-Based Firmware Update Patching for Multi-Protocol Endpoints
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for firmware and configuration updates fail to efficiently support multiple file types and protocols for endpoint systems in power distribution networks, particularly for components like network interface cards (NIC) and metrology boards, which require different file formats and large data handling.
Innovation Solution
A method for updating endpoint systems by using a network interface card (NIC) to compare the current and desired system states, generate upgrade instructions, and deliver a patch file to recreate the desired state, with support for various file types and protocols, including XML schema modifications for firmware and configuration data.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a single firmware download process is used for local network interface card (NIC), then the process is simple and reliable, but it cannot support multiple file types and protocols for different endpoint systems
Solution Approach 1:
The patent implements a universal firmware download process that can handle multiple file types (NIC firmware, metrology board firmware, configuration files) and protocols through a single integrated system. The network interface card serves multiple functions by supporting both legacy local downloads and new network-based downloads, as well as handling different file formats through a unified processing architecture.
Solution Approach 2:
The patent segments the firmware download process into distinct phases: compatibility verification phase, file transfer phase, and installation phase. It also segments the handling of different file types through separate processing paths within the unified system, allowing each component to be optimized independently while maintaining overall system simplicity.
2Reliability
If firmware updates are performed without comparing current and desired states, then the update process is faster, but compatibility issues and installation failures occur
Solution Approach 1:
The patent performs compatibility verification as a preliminary action before the actual firmware installation. The system compares the current endpoint state with the desired state, generates compatibility information, and validates the patch before transfer. This preliminary verification ensures reliability and prevents installation failures, though it does add some time to the overall process.
Solution Approach 2:
The patent implements feedback mechanisms where the network interface card receives compatibility information from the endpoint, verifies the patch against the desired state, and provides status feedback throughout the process. This feedback loop ensures that updates are reliable and can be adjusted if compatibility issues are detected, balancing time consumption with success rate improvement.
3Adaptability or versatility
If network-based firmware transfer is implemented, then remote updates and multiple protocol support are enabled, but data transmission time and network dependency increase
Solution Approach 1:
The patent implements a dynamic firmware download process that can adapt between network-based and local-based transfer methods. The system dynamically selects the appropriate transfer mechanism based on network availability, endpoint capabilities, and update requirements. This allows the system to leverage remote updates when beneficial while falling back to local methods when faster or more reliable.
Solution Approach 2:
The patent performs preliminary compatibility verification and patch generation before network transmission. By preparing all necessary files and validating compatibility in advance on the network interface card, the system minimizes the actual data transmission time and ensures that only necessary data is transferred over the network, reducing overall transmission time while maintaining remote update capability.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A method of adaptably allowing an upgrade to firmware or a configuration of target endpoint hardware to be at least one of replaced or modified by way of instructions generated by a patch generator and executed by target endpoint hardware to generate an upgrade file, install the upgrade file, and audit the installation of the upgrade file is disclosed.