LAN Controller Firmware Update via Network Packets

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current methods for updating firmware on Network Interface Cards (NICs) in data centers are time-consuming and require local intervention, leading to significant network downtimes and associated costs, as they do not allow for vendor-agnostic or network-based updates.

Innovation Solution

A system and method for remotely updating LAN controller firmware on multiple heterogeneous servers without local intervention, using packets and network services to maintain network connectivity during firmware updates by switching between firmware versions stored in memory banks, ensuring seamless operation and security.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional local firmware update methods are used on NICs, then firmware can be updated, but network downtime occurs and update process is time-consuming

Engineering Contradiction:
Improvefirmware update reliabilityVSAvoidnetwork downtime
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by downloading and storing multiple firmware images in advance in the firmware storage module. This allows the firmware update process to switch between pre-stored images without needing to download during the update, thereby avoiding network downtime and ensuring continuous network operation while maintaining firmware update reliability

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces a firmware update module as an intermediary that manages the firmware update process. This module coordinates between the network interface, firmware storage, and authentication mechanisms, enabling seamless transitions between firmware versions without disrupting network operations, thus resolving the contradiction between update reliability and time loss

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If vendor-specific firmware update methods are used, then firmware can be updated, but the system lacks adaptability to different vendors and network interfaces

Engineering Contradiction:
Improvefirmware update capabilityVSAvoidvendor-agnostic support
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The system implements a universal firmware update mechanism that can work with multiple vendors and network interface types. The firmware storage module and update module are designed to handle firmware images from different vendors through a standardized interface, enabling the same system to update firmware for various network interfaces without vendor-specific customization, thus achieving both reliability and adaptability

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Productivity

If remote firmware updates are implemented, then network connectivity is maintained, but security risks may increase

Engineering Contradiction:
Improvenetwork operation continuityVSAvoidsecurity risks
Core Design Contradiction:
ProductivityVSObject-affected harmful factors

Solution Approach 1:

The system implements feedback mechanisms through authentication processes that verify firmware image integrity before and during updates. The firmware update module checks authentication information and validates firmware images, providing feedback on update status and security verification. This ensures that remote updates maintain network connectivity while security risks are mitigated through continuous verification and validation

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system prepares cushioning measures in advance by implementing multiple authentication checks and validation processes before firmware updates are applied. The firmware storage module stores authenticated firmware images, and the update module performs security verification beforehand, cushioning against potential security risks while enabling continuous network operation during updates

Inventive Principle:
Principle #11Beforehand cushioning (Prior cushioning)

Data Source

PatentUS12001826B2Device firmware update techniques
Publication Date: 2024.06.04 INTEL CORP
  • US12001826B2 patent drawing
  • US12001826B2 patent drawing
  • US12001826B2 patent drawing

AI summary

Examples described herein relate to a network interface receiving a firmware update from one or more packets. In some examples, the one or more packets indicate a start of a firmware update. In some examples, the network interface can also perform authenticating the start of firmware update indication and based on authentication of the firmware update, permit a firmware update of a device. In some examples, the device is one or more of: Board Management Controller (BMC), central processing unit (CPU), network interface, Ethernet controller, storage controller, memory controller, display engine, graphics processing unit (GPU), accelerator device, or peripheral device. In some examples, an end of firmware update indicator is received in the one or more packets. In some examples, communications are maintained through a port during a firmware change.