# US 2024/0179049 A1 · Systems and methods for device management in a network

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2024/0179049 A1
- Document ID: US20240179049A1
- Status: Published application
- Kind: A1
- Application number: 18/518,668
- Filed: 2023-11-24
- Published: 2024-05-30
- Earliest claimed: 2022-11-25
- Assignees: Bce Inc.
- Applicants: BCE Inc.
- Inventors: Bruce SHEPPARD; Paul SHERRATT; Cedric CRUPI; Kevin KRATZ
- Web page: https://patentgrep.com/patent/US20240179049A1

## CPC

- H04L 41/0803: Configuration setting
- H04L 41/082: the condition being updates or upgrades of network functionality
- H04L 41/0856: {by backing up or archiving configuration information}
- H04L 41/0863: {by rolling back to previous configuration versions}
- H04L 41/0869: Validating the configuration within one network element
- H04L 41/16: using machine learning or artificial intelligence
- H04L 63/18: {using different networks or channels, e.g. using out of band channels (cryptographic mechanisms or cryptographic arrangements for key distribution involving distinctive intermediate devices or communication paths H04L9/0827; cryptographic mechanisms or cryptographic arrangements for authentication using a plurality of channels H04L9/3215)}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

The present disclosure describes systems and methods for managing devices in a network, including implementing a change to a device on a network, and repairing a device on a network.

## Claims

### Claim 1

A method of implementing a change to a device on a network, comprising:
receiving a change procedure defining the change to be applied to the device;
performing a pre-configuration backup to store a first configuration of the device prior to applying the change;
implementing the change procedure to apply the change to the device; and
performing validation testing to confirm whether the change to the device is successful,
wherein if the validation testing indicates that the change to the device is unsuccessful, reverting the device to the first configuration.

### Claim 2 (depends on 1)

The method of claim 1, wherein reverting the device to the first configuration comprises:
determining if the device is reachable over the network;
if the device is not reachable over the network, connecting to the device via an out-of-band management connection; and
applying a revert change procedure to revert the device to the first configuration.

### Claim 3 (depends on 2)

The method of claim 2, further comprising:
performing the validation testing to confirm whether the revert change procedure is successful,
wherein:
if the revert change procedure is successful, the method further comprises notifying that the change to the device was unsuccessful, and
if the revert change procedure is unsuccessful, the method further comprises triggering a repair script.

### Claim 4 (depends on 3)

The method of claim 3, wherein when the repair script is triggered, the method further comprises:
receiving an indication of a hostname and error type;
determining a device type from the hostname;
determining a repair procedure based on the device type and the error type to resolve the error type and return the device to the first configuration; and
applying the repair procedure to the device in attempt to resolve the error type.

### Claim 5 (depends on 4)

The method of claim 4, wherein determining the repair procedure comprises predicting a best repair procedure using a machine learning model.

### Claim 6 (depends on 4)

The method of claim 4, wherein determining the repair procedure comprises determining one or more known fixes for the device type and the error type.

### Claim 7 (depends on 4)

The method of claim 4, wherein the error type is any one of: device is down, VPN is down, and memory/processing is too high.

### Claim 8 (depends on 4)

The method of claim 4, further comprising:
determining if the error type has been resolved,
wherein:
if the error type has been resolved, the method further comprises storing the repair procedure in association with the device type and error type in the database of known fixes, and sending a notification that the error type has been resolved, and
if the error type has not been resolved, sending a notification that the error type has not been resolved.

### Claim 9 (depends on 8)

The method of claim 8, further comprising, when the error type has not been resolved, determining if the device is critical, and sending a first notification if the device is critical, and sending a second notification if the device is not critical.

### Claim 10 (depends on 1)

The method of claim 1, further comprising:
confirming, before implementing the change procedure, that the device is reachable over the network; and
when the device is not reachable, indicating a change failure.

### Claim 11 (depends on 1)

The method of claim 1, wherein if the validation testing indicates that the change to the device is successful, the method further comprises performing a post-configuration backup to store a second configuration of the device after applying the change.

### Claim 12

A method of repairing a device on a network, comprising:
receiving an indication of a hostname and error type;
determining a device type from the hostname;
determining a repair procedure based on the device type and the error type to resolve the error type and return the device to the configuration prior to applying the change; and
applying the repair procedure to the device in attempt to resolve the error type.

### Claim 13 (depends on 12)

The method of claim 12, wherein determining the repair procedure comprises predicting a best repair procedure using a machine learning model.

### Claim 14 (depends on 12)

The method of claim 12, wherein determining the repair procedure comprises determining one or more known fixes for the device type and the error type.

### Claim 15 (depends on 12)

The method of claim 12, wherein the error type is any one of: device is down, VPN is down, and memory/processing is too high.

### Claim 16 (depends on 12)

The method of claim 12, further comprising:
determining if the error type has been resolved,
wherein:
if the error type has been resolved, the method further comprises storing the repair procedure in association with the device type and error type in the database of known fixes, and sending a notification that the error type has been resolved, and
if the error type has not been resolved, sending a notification that the error type has not been resolved.

### Claim 17 (depends on 16)

The method of claim 16, further comprising, when the error type has not been resolved, determining if the device is critical, and sending a first notification if the device is critical, and sending a second notification if the device is not critical.

### Claim 18 (depends on 14)

The method of claim 14, wherein receiving the indication of the device type and the error type is received from a monitoring system that monitors the device, or from a change system that attempted to apply a change to the device.

### Claim 19 (depends on 1)

A system, comprising:
a processor; and
a non-transitory computer-readable memory storing computer-executable instructions thereon, which when executed by a processor, configure the system to perform the method of claim 1.

### Claim 20 (depends on 1)

A non-transitory computer-readable memory storing computer-executable instructions thereon, which when executed by a processor, configure the processor to perform the method of claim 1.
