# US 9,015,224 B2 · Interactive response of a remote monitoring and management system

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

- Number: US 9,015,224 B2
- Document ID: US9015224B2
- Status: Granted
- Kind: B2
- Application number: 13/647,975
- Filed: 2012-10-09
- Published: 2013-04-11
- Granted: 2015-04-21
- Earliest claimed: 2011-10-09
- Assignees: LabTech LLC
- Applicants: LabTech, LLC
- Inventors: Matthew Nachtrab; Gregory Francis Buerk
- Web page: https://patentgrep.com/patent/US9015224B2

## CPC

- H04L 63/20: {for managing network security; network security policies in general (filtering policies H04L63/0227)}
- H04L 67/125: involving control of end-device applications over a network
- H04L 69/28: Timers or timing mechanisms used in protocols
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A system for providing management functions on remote devices includes a management module, a connection module, an execution module, a timer module, a notification module, and a response module. The management module configures management commands on a central management server. The connection module initiates a connection to the server from an agent on a remote device and retrieves commands. The execution module executes the commands on the device. The timer module controls the initiation of the connection and can be delayed by a timer offset. The notification module uses a local network to send notifications to other agents. The response module responds to the notifications. Some of the commands can modify the timer offset, and other commands can initiate the notifications.

## Claims

### Claim 1

A system for managing remote devices, comprising:
a management module, executing on one or more processors of a central management server, that generates a first management command to modify a timer offset and provides the first management command to a first remote device;
a connection module, executing on the first remote device, that receives the first management command to modify the timer offset and initiates, responsive to expiration of a timer on the first remote device modified by the timer offset, a first connection with the central management server;
the management module provides, to the first remote device, during the first connection, a second management command to initiate a notification, the notification comprising a device identifier of a second remote device, wherein the management module configures the second management command to initiate the notification of the second remote device responsive to identifying that the second remote device has not received the second management command;
a notification module, executing on the first remote device, that receives the second management command during the first connection and broadcasts the notification to one or more remote devices different from the first remote device; and
a response module, executing on the second remote device of the one or more remote devices, that receives the notification with the device identifier broadcast by the first remote device and initiates, responsive to the notification, a second connection with the central management server.

### Claim 2 (depends on 1)

The system of claim 1, further comprising a timer module that initiates the first connection periodically at a frequency determined by a timer period.

### Claim 3 (depends on 2)

The system of claim 2, wherein the first management command is configured to modify the timer period.

### Claim 4 (depends on 1)

The system of claim 1, wherein the response module immediately initiates the second connection to the central management server responsive to the notification.

### Claim 5 (depends on 2)

The system of claim 2, wherein a third management command controls a fast-talk mode of the remote device wherein the timer period is temporarily shortened.

### Claim 6 (depends on 1)

The system of claim 1, wherein the first management command retrieved by the connection module is dependent upon an identity of the first remote device initiating the connection.

### Claim 7 (depends on 1)

The system of claim 1, wherein the first management command retrieved by the connection module does not include commands configured to initiate notification of a remote device of the one or more remote devices that cannot be reached using a local network connecting the one or more remote devices via the notification broadcast by the first remote device.

### Claim 8 (depends on 1)

The system of claim 1, wherein the first management command retrieved by the connection module comprises a command configured to initiate notifications that are prioritized using a priority based on information about the second remote device initiating the second connection.

### Claim 9 (depends on 8)

The system of claim 8, wherein the priority is higher for remote devices that are servers.

### Claim 10 (depends on 8)

The system of claim 8, wherein the priority is higher for remote devices that are currently connected to a local network connecting the one or more remote devices.

### Claim 11 (depends on 1)

The system of claim 1, wherein the timer offset is computed to evenly spread out timing of connections by the one or more remote devices.

### Claim 12 (depends on 1)

The system of claim 1, wherein the notifications are sent using a broadcast message via a local network connecting one or more of the one or more remote devices.

### Claim 13

A method for managing one or more remote devices, comprising:
configuring, by one or more processors of a central management server, a first management command to modify a timer offset;
providing, by the central management server, the first management command to a first remote device;
initiating, by the first remote device, responsive to expiration of a timer on the first remote device modified by the timer offset, a first connection with the central management server;
providing, by the central management server, to the first remote device, during the first connection, a second management command to initiate a notification, the notification comprising a device identifier of a second remote device, wherein the second management command is configured to initiate the notification of the second remote device responsive to identifying that the second remote device of the one or more remote devices has not received the second management command;
receiving, by a notification module executing on the first remote device, the second management command during the first connection;
broadcasting, by the first remote device, the notification to one or more remote devices different from the first remote device;
receiving, by a response module executing on the second remote device of the one or more remote devices, the notification with the device identifier broadcast by the first remote device; and
initiating, by the second remote device responsive to the notification, a second connection with the central management server.

### Claim 14 (depends on 13)

The method of claim 13, further comprising:
initiating the first connection periodically at a frequency determined by a timer period.

### Claim 15 (depends on 14)

The method of claim 14, further comprising:
modifying the timer period as a result of executing the first management command.

### Claim 16 (depends on 14)

The method of claim 14, further comprising:
using a third management command to control a fast-talk mode of the first remote device wherein the timer period is temporarily shortened.

### Claim 17 (depends on 13)

The method of claim 13, further comprising:
responding, by the second remote device, to the notification by immediately initiating the second connection to the central management server.

### Claim 18 (depends on 13)

The method of claim 13, further comprising:
configuring a third management command to initiate notifying the one or more remote devices that have not yet retrieved one or more commands.

### Claim 19 (depends on 13)

The method of claim 13, further comprising:
selecting commands retrieved by the first connection depending upon an identity of the first remote device initiating the first connection.

### Claim 20 (depends on 13)

The method of claim 13, further comprising:
selecting commands retrieved by the first connection that do not include commands configured to initiate notification of a remote device of the one or more remote devices that cannot be reached via the notification broadcast by the first remote device using the network.

### Claim 21 (depends on 13)

The method of claim 13, further comprising:
prioritizing commands configured to initiate notification using a priority based on information about the first remote device initiating the first connection.

### Claim 22 (depends on 21)

The method of claim 21, further comprising:
providing a higher priority for remote devices that are servers.

### Claim 23 (depends on 21)

The method of claim 21, further comprising:
providing a higher priority for remote devices that are currently connected to the network.

### Claim 24 (depends on 13)

The method of claim 13, further comprising:
using the timer offset to evenly spread out a timing of connections by the one or more remote devices.

### Claim 25 (depends on 13)

The method of claim 13, further comprising:
sending the notification using a broadcast message on the network.