Peer-assisted image update with self-healing capabilities

US2016337169A1 · US · A1

Patent metadata
FieldValue
Publication numberUS-2016337169-A1
Application numberUS-201514711035-A
CountryUS
Kind codeA1
Filing dateMay 13, 2015
Priority dateMay 13, 2015
Publication dateNov 17, 2016
Grant date

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

In one embodiment, a device in a network receives update recovery data from a neighbor of the device in the network. The device monitors the neighbor during installation of a software update by the neighbor. The device detects an installation failure of the software update by the neighbor. The device causes recovery of the neighbor using the update recovery data, in response to detecting the installation failure of the software update by the neighbor.

First claim

Opening claim text (preview).

What is claimed is: 1 . A method comprising: receiving, at a device in a network, update recovery data from a neighbor of the device in the network, monitoring, by the device, the neighbor during installation of a software update by the neighbor; detecting, by the device, an installation failure of the software update by the neighbor; and causing, by the device, recovery of the neighbor using the update recovery data, in response to detecting the installation failure of the software update by the neighbor. 2 . The method as in claim 1 , wherein the update recovery data identifies a configuration of the neighbor, wherein causing recovery of the neighbor comprises: providing, by the device, the identified configuration to the neighbor. 3 . The method as in claim 1 , wherein the update recovery data identifies an interface or module of the neighbor, wherein causing recovery of the neighbor comprises: causing, by the device, the neighbor to restore the identified interface or module. 4 . The method as in claim 1 , wherein detecting the installation failure comprises: determining, by the device, that the neighbor has not sent a message to the device in a threshold amount of time. 5 . The method as in claim 1 , wherein detecting the installation failure comprises: receiving, at the device, an indication from the neighbor of the installation failure. 6 . The method as in claim 1 , further comprising: receiving, at the device, a request from the neighbor to monitor the installation of the software update by the neighbor; determining, by the device, whether the device has sufficient resources to monitor the installation of the software update by the neighbor; and providing, by the device, an indication as to whether the device has sufficient resources to monitor the installation of the software update by the neighbor. 7 . The method as in claim 1 , further comprising: providing, by the device, a notification regarding the detected installation failure to a user interface device. 8 . A method comprising: providing, by a device in a network, update recovery data to a neighbor of the device in the network; causing, by the device, network traffic to be routed away from the device; attempting, by the device, installation of a software update; and receiving, at the device, the update recovery data from the neighbor, in response to an installation failure of the software update by the device. 9 . The method as in claim 8 , wherein the update recovery data identifies at least one of: a configuration of the device, an interface used by the device, or a module used by the device. 10 . The method as in claim 8 , further comprising: providing, by the device, a notification to the neighbor indicative of whether the installation of the software update by the device was successful. 11 . The method as in claim 8 , further comprising: receiving, at the device, data regarding the software update; and providing, by the device, a notification indicative of whether the device is eligible to install the software update, based on the received data regarding the software update. 12 . The method as in claim 8 , further comprising: selecting, by the device, the neighbor to monitor the device during installation of the software update by the device; notifying, by the device, the neighbor that the neighbor was selected to monitor the device during installation of the software update; and receiving, at the device, an indication as to whether the neighbor has sufficient resources to monitor the installation of the software update by the device. 13 . The method as in claim 8 , wherein causing network traffic to be routed away from the device comprises: setting, by the device, an overload bit in an Intermediate System-to-System (ISIS) message or an Open Shortest Path First (OSPF) max metric parameter. 14 . The method as in claim 8 , further comprising: notifying, by the device, the neighbor that the device is to be restarted after installation of the software update, wherein the neighbor is configured to detect the installation failure based on a timeout. 15 . An apparatus, comprising: one or more network interfaces to communicate with a network; a processor coupled to the one or more network interfaces and configured to execute a process; and a memory configured to store the process executable by the processor, the process when executed operable to: receive update recovery data from a neighbor of the apparatus in the network, monitor the neighbor during installation of a software update by the neighbor; detect an installation failure of the software update by the neighbor; and cause recovery of the neighbor using the update recovery data, in response to detecting the installation failure of the software update by the neighbor. 16 . The apparatus as in claim 15 , wherein the update recovery data identifies a configuration of the neighbor, and wherein the apparatus causes recovery of the neighbor by providing the identified configuration to the neighbor. 17 . The apparatus as in claim 15 , wherein the update recovery data identifies an interface or module of the neighbor, and wherein the apparatus causes recovery of the neighbor by causing the neighbor to restore the identified interface or module. 18 . The apparatus as in claim 15 , wherein the apparatus detects the installation failure by determining that the neighbor has not sent a message to the device in a threshold amount of time. 19 . The apparatus as in claim 15 , wherein the apparatus detects the installation failure by receiving an indication from the neighbor of the installation failure. 20 . The apparatus as in claim 15 , wherein the process when executed is further operable to: receive a request from the neighbor to monitor the installation of the software update by the neighbor; determine whether the apparatus has sufficient resources to monitor the installation of the software update by the neighbor; and provide an indication as to whether the apparatus has sufficient resources to monitor the installation of the software update by the neighbor.

Assignees

Inventors

Classifications

  • Alternate routing · CPC title

  • Electricity · mapped topic

  • the condition being updates or upgrades of network functionality · CPC title

  • using route fault recovery · CPC title

  • by reconfiguring faulty entities · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US2016337169A1 cover?
In one embodiment, a device in a network receives update recovery data from a neighbor of the device in the network. The device monitors the neighbor during installation of a software update by the neighbor. The device detects an installation failure of the software update by the neighbor. The device causes recovery of the neighbor using the update recovery data, in response to detecting the in…
Who is the assignee on this patent?
Cisco Tech Inc
What technology area does this patent fall under?
Primary CPC classification H04L41/0672. Mapped technology areas include Electricity.
When was this patent published?
Publication date Thu Nov 17 2016 00:00:00 GMT+0000 (Coordinated Universal Time) (A1). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 3 related publications on this page (citations in our corpus or others sharing the same primary CPC).