IP Library Granted Patent US 11,711,256
Granted Patent B2
US 11,711,256 · App. 17/168,684 · Granted Jul 25, 2023

Autonomous server agents

Inventors: Rajat Bhargava (Boulder, CO); James Brown (Boulder, CO); Christopher Marie (Boulder, CO)
Assignee: JumpCloud, Inc.
H04L41/046H04L41/28H04L63/04H04L63/166
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,711,256
App. No.
17/168,684
Granted
Jul 25, 2023
Kind
B2
Abstract

Methods, systems, and devices are described for orchestrating server management in a modern IT network. The described techniques may be implemented to manage any number of networked severs, whether local, remote, or both. Server orchestration may leverage a central, cloud-based management system and/or one or more autonomous agents installed on servers with the network. The autonomous agents may each be registered with the supervisory server and may have awareness of one another.

Claims (52)

1. A method for device management, comprising:

registering a unique identifier of an agent with a first device;

establishing a secure connection between the agent and the first device based at least in part on the registering;

receiving, at the agent and based at least in part on establishing the secure connection, a task to manage a second device, wherein the task is a disk space management task, a log monitoring task, a system configuration task, an email communication task, an information transfer task, an information storage task, a security threat identification task, a security threat neutralization task, a user management task, or any combination thereof; and

accepting, at the agent, the task.

2. The method of claim 1 , wherein the task comprises a command that an operating system of the second device supports.

3. The method of claim 1 , further comprising:

executing the task on the second device with the agent, wherein the agent is running on the second device.

4. The method of claim 3 , wherein the secure connection between the agent and the first device is lost, and wherein the task is executed on the second device after or while the secure connection is lost.

5. The method of claim 3 , further comprising:

determining, by the agent, an additional task to execute based at least in part on executing the task; and

executing the additional task on the second device with the agent.

6. The method of claim 5 , wherein the secure connection between the agent and the first device is lost, and wherein at least one of the task or the additional task is executed on the second device after or while the secure connection is lost.

7. The method of claim 1 , wherein accepting the task comprises executing a script comprising a command associated with the task, the command being supported by an operating system of the second device.

8. The method of claim 1 , further comprising:

identifying, by the agent, another task execution by another agent on a third device; and

executing the task on the second device with the agent based at least in part on the identifying.

9. The method of claim 1 , wherein the receiving comprises receiving a plurality of tasks that includes the task, the method further comprising:

accepting, at the agent, the plurality of tasks; and

executing the plurality of tasks on the second device with the agent according to a schedule or on an ad hoc basis.

10. The method of claim 1 , wherein the secure connection comprises a transport layer security (TLS) protocol, wherein the first device comprises a cloud-hosted server, or both.

11. The method of claim 1 , wherein:

the first device comprises a first server or a first computing device;

the second device comprises a second server or a second computing device, or

any combination thereof.

12. The method of claim 1 , wherein, after receiving a security task, the agent continuously executes the security task at the second device, the security task comprising the security threat identification task, the security threat neutralization task, or both.

13. A system to manage devices, comprising:

a first hardware-implemented device that manages tasks on a second hardware-implemented device that has a network connection to the first hardware-implemented device; and

an agent, wherein a unique identifier of the agent is registered at the first hardware-implemented device and a secure connection is established between the agent and the first hardware-implemented device, the agent configured to receive and accept a task to manage the second hardware-implemented device, wherein the task is a disk space management task, a log monitoring task, a system configuration task, an email communication task, an information transfer task, an information storage task, a security threat identification task, a security threat neutralization task, a user management task, or any combination thereof.

14. The system of claim 13 , further comprising:

a console that provides access to the first hardware-implemented device for management of the second hardware-implemented device via the agent.

15. The system of claim 14 , further comprising:

a third hardware-implemented device, wherein the first hardware-implemented device manages tasks on the third hardware-implemented device; and

another agent, wherein the console provides access to the first hardware-implemented device for management of the third hardware-implemented device via the other agent.

16. The system of claim 13 , wherein the agent comprises:

a task cache module that accepts one or more tasks in response to a script or a command executed at the first hardware-implemented device;

a processing module that executes the tasks accepted by the task cache module, wherein the processing module is in communication with the task cache module;

a timing module that directs the processing module to execute the tasks accepted by the task cache module within a time period, upon expiration of a timer; or

any combination thereof.

17. The system of claim 13 , wherein the first hardware-implemented device comprises:

an orchestration module that manages, schedules, or executes tasks on the second hardware-implemented device;

a command execution module that executes commands utilizing the agent based at least in part on an output of the orchestration module;

a scheduler module that executes tasks according to a schedule based at least in part on the output of the orchestration module; or

any combination thereof.

18. The system of claim 13 , wherein the first hardware-implemented device comprises:

a user management module that stores user credentials, user preferences, a location of the second hardware-implemented device, or any combination thereof, wherein the user management module is in communication with a hardware-implemented data store.

19. The system of claim 13 , further comprising:

a hardware-implemented data store in communication with the first hardware-implemented device, wherein the hardware-implemented data store comprises content, scripts, tasks, event logs, or user data, or any combination thereof.

20. The system of claim 13 , wherein:

the first hardware-implemented device comprises a first hardware-implemented server or a first hardware-implemented computing device;

the second hardware-implemented device comprises a second hardware-implemented server or a second hardware-implemented computing device, or

any combination thereof.

Assignments (2)
SECURITY INTEREST Recorded Apr 30, 2022
From: JUMPCLOUD INC.
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 059744/0884 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 5, 2021
From: BHARGAVA, RAJAT; BROWN, JAMES; MARIE, CHRISTOPHER
To: JUMPCLOUD, INC.
Reel/Frame 055163/0415 →
Continuity (8)
Continuation 16831267 · Mar 26, 2020
Continuation 16363240 · Mar 25, 2019
Continuation 14728708 · Jun 2, 2015
Provisional Application 62011087 · Jun 12, 2014
Provisional Application 62007278 · Jun 3, 2014
Provisional Application 62007285 · Jun 3, 2014
Provisional Application 62007281 · Jun 3, 2014
Related Publication 20210168017A1 · Jun 3, 2021