Systems and methods for operating system deployment and lifecycle management of a smart network interface card
US-2021226846-A1 · Jul 22, 2021 · US
US2020257518A1 · US · A1
| Field | Value |
|---|---|
| Publication number | US-2020257518-A1 |
| Application number | US-202016858504-A |
| Country | US |
| Kind code | A1 |
| Filing date | Apr 24, 2020 |
| Priority date | Apr 24, 2020 |
| Publication date | Aug 13, 2020 |
| Grant date | — |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
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.
Opening claim text (preview).
What is claimed is: 1 . A method comprising: at a network interface, receiving a firmware update for a network interface in one or more packets. 2 . The method of claim 1 , comprising: authenticating the firmware update and based on authentication of the firmware update, permitting a firmware update of the network interface. 3 . The method of claim 1 , comprising: at the network interface, receiving a firmware update for a device in one or more packets, wherein the device comprises one or more of: Board Management Controller (BMC), central processing unit (CPU), storage controller, memory controller, display engine, graphics processing unit (GPU), accelerator device, or peripheral device; authenticating the firmware update for the device; and based on authentication of the firmware update for the device, permitting a firmware update of the device. 4 . The method of claim 1 , comprising: indicating a status of the firmware update as either successful or unsuccessful at a network address. 5 . The method of claim 1 , comprising: storing the firmware update in a firmware memory region for access; selecting a second interface for use to access the firmware update and connection to a network interface port; and de-selecting a first interface that uses a current firmware from connection to the network interface port. 6 . The method of claim 5 , comprising maintaining communication using the network interface port during a firmware change. 7 . The method of claim 5 , wherein the network interface port is allocated for manageability communications, the manageability communications comprising one or more of: heartbeat packets, probe messages, telemetry collection, and various keep alive packets, Address Resolution Protocol (ARP) messages, acknowledgements (ACKs), or neighbor solicitation. 8 . The method of claim 1 , comprising: initiating transmission of a firmware update from a remote trusted source; and storing the received firmware update into a volatile memory device. 9 . The method of claim 8 , comprising: one or more devices accessing firmware from the volatile memory device, the one or more devices comprising: a Board Management Controller (BMC), central processing unit (CPU), the network interface, storage controller, memory controller, display engine, graphics processing unit (GPU), accelerator device, or peripheral device. 10 . The method of claim 8 , comprising: erasing the firmware update from the volatile memory device based on removal of power to the volatile memory device. 11 . An apparatus comprising: a network interface to receive a firmware update for the network interface from one or more packets. 12 . The apparatus of claim 11 , comprising at least one processor to: authenticate a firmware update and based on authentication of the firmware update, permit a firmware update of the network interface. 13 . The apparatus of claim 11 , comprising at least one processor and wherein at the network interface, receive a firmware update for a device in one or more packets, wherein the device comprises one or more of: Board Management Controller (BMC), central processing unit (CPU), storage controller, memory controller, display engine, graphics processing unit (GPU), accelerator device, or peripheral device; the at least one processor is to authenticate the firmware update for the device; and based on authentication of the firmware update for the device, the at least one processor is to permit a firmware update of the device. 14 . The apparatus of claim 11 , comprising at least one processor to: indicate a status of the firmware update as either successful or unsuccessful at a network address. 15 . The apparatus of claim 11 , comprising at least one processor to: store the firmware update in a firmware memory region for access; select a second interface for use to access the firmware update and connection to a network interface port; and de-select a first interface that uses a current firmware from connection to the network interface port. 16 . The apparatus of claim 15 , wherein the network interface is to maintain communication using the network interface port during a firmware change. 17 . The apparatus of claim 15 , wherein the port is allocated for manageability communications, the manageability communications comprising one or more of: heartbeat packets, probe messages, telemetry collection, and various keep alive packets, Address Resolution Protocol (ARP) messages, acknowledgements (ACKs), or neighbor solicitation. 18 . The apparatus of claim 11 , comprising at least one processor to: initiate transmission of a firmware update from a remote trusted source; and store the received firmware update into a volatile memory device. 19 . The apparatus of claim 18 , wherein one or more devices are to access firmware from the volatile memory device, the one or more devices comprising: a Board Management Controller (BMC), central processing unit (CPU), the network interface, a storage controller, memory controller, display engine, graphics processing unit (GPU), accelerator device, or peripheral device. 20 . The apparatus of claim 19 , wherein the firmware update is erased from the volatile memory device based on removal of power to the volatile memory device. 21 . The apparatus of claim 11 , comprising a server, data center, or rack.
Updates (security arrangements therefor G06F21/57) · CPC title
Secure firmware programming, e.g. of basic input output system [BIOS] · CPC title
Test or assess software · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.