Network Interface Firmware Updates During Link Establishment

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Provisioning software and/or firmware updates to network interface devices, such as Ethernet PHY chips, after deployment is difficult or impossible due to the need for coordination with the end market device vendor and limited memory capabilities, leading to time delays and limited debugging opportunities.

Innovation Solution

Providing software and/or firmware updates to a first network interface device from a second network interface device over a network link during the link establishment process, allowing updates without involving the vendor that deploys the first device, and utilizing volatile memory to temporarily store updates for devices without persistent storage.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If software/firmware updates are provided through the end market device vendor, then updates can be applied to deployed network interface devices, but significant time delays occur and coordination complexity increases

Engineering Contradiction:

Improvesoftware update capabilityVSAvoidupdate implementation time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The patent extracts the software update provisioning function from the end market device vendor and transfers it directly to the network interface device itself. The NID can now receive and apply software/firmware updates directly from any source over the network link, eliminating the mandatory coordination chain through the original vendor and dramatically reducing update implementation time.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces a new intermediary mechanism - the ability for the NID to receive updates directly over the network link during link establishment. This bypasses the traditional vendor-mediated update path and creates a direct communication channel for software provisioning, resolving the time delay and coordination issues.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Reliability

If software/firmware updates are provided through vendor coordination, then updates can be implemented, but the process becomes complex and debugging opportunities are limited

Engineering Contradiction:

Improvesoftware update capabilityVSAvoidupdate coordination process

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent removes the complex vendor coordination layer from the update process. The NID gains the capability to independently receive and process software updates directly over the network, extracting the provisioning function from the vendor's control domain and simplifying the overall system architecture.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The NID becomes self-sufficient in the software update process. It can autonomously receive update messages, process them, and apply software/firmware changes without requiring external vendor coordination. This self-service capability dramatically reduces process complexity and enables rapid debugging iterations.

Inventive Principle:

Principle #25Self-service

3Stability of the object's composition

If software/firmware is stored in non-alterable memory, then deployment stability is maintained, but post-deployment updates become impossible without physical replacement

Engineering Contradiction:

Improvememory stabilityVSAvoidsoftware update capability

Core Design Contradiction:

Stability of the object's compositionVSAdaptability or versatility

Solution Approach 1:

The patent introduces volatile memory as an intermediary layer between the non-alterable persistent storage and the software update process. Updates are temporarily held in volatile memory during the link establishment phase, allowing the NID to load and execute new software/firmware without physically replacing the device, thus maintaining both stability and adaptability.

Inventive Principle:

Principle #24Intermediary (Mediator)

4Reliability

If physical replacement of network interface devices is performed for software updates, then updated functionality is achieved, but turnaround time increases and debugging is limited

Engineering Contradiction:

Improvesoftware update capabilityVSAvoiddebugging speed

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The patent replaces the mechanical process of physical device replacement with an electronic/software-based update mechanism. Software/firmware updates are transmitted and applied electronically over the network link during establishment, eliminating the need for physical intervention and enabling rapid debugging and iteration without handling hardware components.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentUS12471154B1Software/firware updates during network link establishment

Publication Date: 2025.11.11 MARVELL ASIA PTE LTD

AI summary

A link establishment process for establishing a network link between the first network interface device and a second network interface device is initiated at the first network interface device. During the link establishment process, the first network interface device receives from the second network interface device via the network link, one or more update messages requesting one or more changes to be applied at the first network interface device, the one or more changes for altering operation of one or both of software and firmware stored in one or more memories included in or coupled to the first network interface device. The one or more changes are applied based on the one or more update messages at the first network interface device.