IP Library Granted Patent US 10,462,212
Granted Patent B2
US 10,462,212 · App. 15/337,483 · Granted Oct 29, 2019

Hybrid clouds

Inventors: Brian Amento (Morris Plains, NJ); Robert J. Hall (Berkeley Heights, NJ); Kaustubh Joshi (Scotch Plains, NJ); Kermit Hal Purdy (Bernardsville, NJ)
Assignee: AT&T Intellectual Property I, L.P.
H04L67/10H04L41/0806H04L41/5041H04L63/1441H04L67/1097H04W24/02G06F9/541G06F16/24568H04W84/18
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 10,462,212
App. No.
15/337,483
Granted
Oct 29, 2019
Kind
B2
Abstract

Systems and methods are disclosed for creating and managing hybrid clouds including both standard compute nodes and edge devices. Edge devices can be enrolled in a hybrid cloud by deploying a lightweight container to the edge device.

Claims (43)

1. A method, comprising:

identifying an edge device in network communication with a cloud extension component of a managed hybrid cloud, wherein the edge device is located outside a core network supporting the managed hybrid cloud;

deploying a lightweight management container to the edge device, the lightweight management container sharing a common control plane with a standard management container used on a traditional compute node in the managed hybrid cloud;

enrolling the edge device in the managed hybrid cloud using the lightweight management container; and

satisfying a resource request directed to the managed hybrid cloud using a resource of the edge device.

2. The method of claim 1 , further comprising:

receiving the resource request, the resource request associated with a standard management container before deploying the lightweight management container; and

determining requirements of the resource request, the lightweight management container provides functionality to respond to the resource request without duplicating all modules of the standard management container.

3. The method of claim 1 , further comprising:

controlling the edge device using a conductor component associated with the cloud extension component of the managed hybrid cloud; and

controlling the traditional compute node using the conductor component, the conductor component compatible for both edge device control and traditional compute node control.

4. The method of claim 1 ,

wherein the edge device is identified based on a constraint, and

wherein the constraint is one of a geographic location, velocity, acceleration, sensor capability, processing capability, memory capability, or verification of affirmative participation in the managed hybrid cloud.

5. The method of claim 1 , further comprising managing communication in the managed hybrid cloud to or from the edge device, communication being transmitted using a long range technique or an ad hoc technique.

6. The method of claim 1 , further comprising running at least a portion of an application satisfying the resource request on the edge device using the lightweight management container.

7. The method of claim 6 , the application is distributed among a plurality of edge devices having the lightweight management container.

8. The method of claim 1 , the lightweight management container and the standard management container communicate within the managed hybrid cloud using a common messaging protocol.

9. The method of claim 1 , further comprising monitoring the edge device for changes using a monitor component.

10. The method of claim 1 , wherein the edge device is a mobile device.

11. A system, comprising:

a non-transitory computer-readable medium storing instructions; and

a processor operatively coupled to the non-transitory computer-readable medium and configured to execute the instructions, wherein the instructions when executed by the processor effectuate:

a cloud extension component of a managed hybrid cloud, the cloud extension component configured to communicate with edge devices located outside datacenters and traditional compute nodes within datacenters,

wherein the cloud extension component deploys a standard management container to traditional compute nodes,

wherein the cloud extension component deploys a lightweight management container to the edge devices, the lightweight management container sharing a common control plane with the standard management container used on a traditional compute node in the managed hybrid cloud, the lightweight management container enrolls one or more of the edge devices in the managed hybrid cloud; and

a conductor component of the cloud extension component, the conductor component controls the edge devices, and the conductor component controls the traditional compute nodes,

wherein the conductor component controls the edge devices to satisfy a resource request directed to the managed hybrid cloud.

12. The system of claim 11 , the edge devices communicate in the managed hybrid cloud using a long range technique or an ad hoc technique.

13. The system of claim 11 , wherein at least a portion of a cloud application satisfying the resource request is run on the edge devices using the lightweight management container.

14. The system of claim 11 , the lightweight management container and the standard management container communicate using a common messaging protocol.

15. The system of claim 11 , wherein the non-transitory computer-readable medium stores instructions that when executed by the processor effectuate:

a monitor component that monitors the edge devices for changes.

16. A system comprising a processor and computer readable media storing instructions configured to:

identify an edge device in network communication with a cloud extension component of a managed hybrid cloud;

deploy a lightweight management container to the edge device, the lightweight management container sharing a common control plane with a standard management container used on a traditional compute node in the managed hybrid cloud, wherein the traditional compute node is located in a datacenter and the edge device is located outside any datacenter;

enroll the edge device in the managed hybrid cloud using the lightweight management container; and

satisfy a resource request directed to the managed hybrid cloud using a resource of the edge device.

17. The system of claim 16 , the instructions further configured to:

receive the resource request satisfied by the edge device, the resource request associated with a standard management container before deploying the lightweight management container; and

determine requirements of the resource request, the lightweight management container provides functionality to respond to the resource request without duplicating all modules of the standard management container.

18. The system of claim 16 , the instructions further configured to monitor the edge device for changes using a monitor component.

19. The system of claim 18 , the instructions further configured to identify the edge device based on a constraint, the constraint is monitored as one of the changes.

Assignments (2)
CORRECTIVE ASSIGNMENT TO CORRECT THE ASSIGNEE'S NAME PREVIOUSLY RECORDED AT REEL: 040337 FRAME: 0790. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Jun 27, 2019
From: AMENTO, BRIAN; HALL, ROBERT J; JOSHI, KAUSTUBH; PURDY, KERMIT HAL
To: AT&T INTELLECTUAL PROPERTY I, L.P.
Reel/Frame 049605/0448 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 16, 2016
From: AMENTO, BRIAN; JOSHI, KAUSTUBH; PURDY, KERMIT HAL; HALL, ROBERT J
To: AT&T INTELLECTUAL PROPERTY, I, L.P.
Reel/Frame 040337/0790 →
Continuity (1)
Related Publication 20180124158A1 · May 3, 2018