Inter-Telecommunications Edge Cloud Protocols

• US 20180041578A1
• Filed: 08/08/2016
• Published: 02/08/2018
• Est. Priority Date: 08/08/2016
• Status: Abandoned Application

• Current Assignee: Futurewei Technologies Incorporated (Huawei Investment & Holding Co., Ltd.)
• Original Assignee: Futurewei Technologies Incorporated (Huawei Investment & Holding Co., Ltd.)
• Inventors: Lee, Young, Wei, Wei, Kanonakis, Konstantinos
• Application Number:
  US15/231,364
• Publication Number:
  US 20180041578A1
• Time in Patent Office: Days
• CPC Class Codes: H04L 47/70 Admission control; Resource allocation
• CPC Class Codes: H04L 47/829 Topology based
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/1097 for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services

Abstract

A first telecommunications edge cloud (TEC) element deployed between a client and a packet network includes a TEC hardware layer including storage resources, networking resources, and computing resources, wherein the computing resources include a plurality of processors. The networking resources are configured to transmit a first general update message to a plurality of second TEC elements within a federation, transmit a first application-specific update message to the second TEC elements within the federation, and receive a plurality of second update messages from the second TEC elements that are associated with the federation. The federation includes the second TEC elements and the first TEC element and shares resources to provide data and services to a requesting client. The storage resources are coupled to the computing resources and the networking resources and configured to store a second generic resource container and second application-specific resource container for each of the second TEC elements.

Claims

1. A first telecommunications edge cloud (TEC) element within a federation, comprising:

computing resources comprising a plurality of processors;

networking resources coupled to the computing resources and comprising a plurality of network input and output ports, wherein the networking resources are configured to;

transmit a first general update message to a plurality of second TEC elements within the federation, wherein the first general update message comprises a first generic resource container of the first TEC element, wherein the first generic resource container identifies a total amount of resource capacity of the first TEC element, and wherein the federation containing the second TEC elements and the first TEC element share resources to provide at least one of data and services to a requesting client;

transmit a first application-specific update message to the second TEC elements within the federation, wherein the first application-specific update message comprises a first application-specific resource container of the first TEC element, and wherein the first application-specific resource container identifies an amount of resources reserved by the first TEC element for an application; and

receive a plurality of second resource update messages from the second TEC elements within the federation, wherein each of the second resource update messages comprise a second generic resource container and a second application-specific resource container, wherein the second generic resource container identifies a total amount of resource capacity of each of the second TEC elements, and wherein the second application-specific resource container identifies an amount of resources reserved by the each of the second TEC elements for the application; and

storage resources coupled to the computing resources and the networking resources and configured to store the second generic resource container and the second application-specific resource container for each of the second TEC elements,

wherein the first TEC element and the second TEC elements are deployed between the client and a packet network.

2. The first TEC element of claim 1, wherein the networking resources are further configured to receive a federation creation request from a second TEC element, wherein the second TEC element is the master TEC element in the federation and is the only TEC element in the federation that is permitted to add new TEC elements to the federation and remove TEC elements from the federation.

3. The first TEC element of claim 2, wherein the networking resources are further configured to receive a master assignment request from the second TEC element, wherein the master assignment request is a request for the first TEC element to assume the role of the master TEC element in the federation.

4. The first TEC element of claim 1, wherein the first TEC element sends a federation creation request to a second TEC element, wherein the first TEC element is the only TEC element in the federation that is permitted to add new TEC elements to the federation and remove TEC elements from the federation.

5. The first TEC element of claim 1, wherein the first TEC element comprises an application layer, a TEC operating system (TECOS), and a hardware layer, wherein the hardware layer comprises the computing resources, the networking resources, and the storage resources, wherein the TECOS comprises an inter-TEC federation manager configured to manage communication and sharing resources with the second TEC elements of the federation, and wherein the application layer comprises an application that receives a request from the requesting client for the data or the services.

6. The first TEC element of claim 1, wherein the networking resources further comprises at least one of a provider edge (PE) router, an optical line terminal (OLT), a broadband network gateway (BNG), wireless access point equipment, and an optical transport network (OTN) switch.

7. The first TEC element of claim 1, further comprising an application layer configured to receive a request from the requesting client for the data or the services corresponding to an application on the application layer, wherein the computing resources are configured to select one of the second TEC elements in the federation that has sufficient resource capacity to provide the data or services to the client according to at least one of the second generic resource container and the second application-specific resource container for each of the second TEC elements, and wherein the networking resources are configured to redirect the request to the selected one of the second TEC elements in the federation.

8. An apparatus for providing cloud computing services to a client, comprising:

computing resources comprising a plurality of processors;

networking resources coupled to the computing resources and comprising a plurality of network input and output ports, wherein the networking resources are configured to;

transmit a first general update message to a plurality of second TEC elements that within a federation, wherein the first general update message comprises a first generic resource container of the apparatus, wherein the first generic resource container identifies a total amount of resource capacity of the apparatus, and wherein the federation containing the second TEC elements and the apparatus share resources to provide at least one of data and services to a requesting client;

transmit a first application-specific update message to the second TEC elements within the federation, wherein the first application-specific update message comprises a first application-specific resource container of the apparatus, and wherein the first application-specific resource container identifies an amount of resources reserved by the first TEC for an application;

receive a plurality of second update messages from the second TEC elements within the federation, wherein each of the second update messages comprise at least one of a second generic resource container and a second application-specific resource container, wherein the second generic resource container identifies a total amount of resource capacity of each of the second TEC elements, and wherein the second application-specific resource container identifies an amount of resources reserved by the each of the second TEC elements for the application; and

storage resources coupled to the computing resources and the networking resources and configured to store the second generic resource container and the second application-specific resource container for each of the second TEC elements,

wherein the first TEC element and the second TEC elements are deployed between the client and a packet network.

9. The apparatus of claim 8, wherein the first general update message comprises an identifier of the apparatus, an identifier of the federation, and a resource container, wherein the resource container comprises at least one of a server load, a power consumption, a virtual central processing unit (vCPU) load, a hypervisor capacity, a computing hosts capacity, a number of vCPUs available for execution, a status of a hypervisor, a number of computing hosts available for execution, a number of virtual machines (VMs) that are capable of running an instance for each host, a number of VMs that are running instances for each host, and a number of VMs that are idle.

10. The apparatus of claim 8, wherein the first application-specific update message comprises an identifier of the apparatus, an identifier of the federation, an identifier of the application, and an application-specific resource container, wherein the application specific resource container comprises at least one of a server load assigned to the application, a power consumption assigned to the application, a virtual central processing unit (vCPU) load assigned to the application, a hypervisor capacity assigned to the application, a computing hosts capacity assigned to the application, a number of vCPUs available for execution assigned to the application, a status of a hypervisor for the application, a number of computing hosts available for execution assigned to the application, a number of virtual machines (VMs) that are capable of running an instance for each host assigned to the application, a number of VMs that are running instances for each host assigned to the application, and a number of VMs that are idle assigned to the application.

11. The apparatus of claim 8, further comprising an application layer configured to receive a request from the requesting client for the data or the services corresponding to an application on the application layer, wherein the computing resources are configured to select one of the second TEC elements in the federation that has sufficient resource capacity to provide the data or the services to the client, and wherein the networking resources are configured to:

transmit a redirection request to redirect the request from the client to the selected one of the second TEC elements in the federation;

receive an acceptance of the redirection request from the selected one of the second TEC elements in the federation; and

redirect the request from the client to the selected on of the second TEC elements in the federation.

12. The apparatus of claim 8, further comprising comprises an application layer, a TEC operating system (TECOS), and a hardware layer, wherein the hardware layer comprises the computing resources, the networking resources, and the storage resources, wherein the TECOS comprises an inter-TEC federation manager configured to manage communication and sharing resources with the second TEC elements of the federation, and wherein the application layer comprises an application that receives a request from the requesting client for data or a service.

13. A method implemented by a first telecommunications edge cloud (TEC) element within a federation, comprising:

receiving, using networking resources of the first TEC element, a plurality of resource update messages from a plurality of second TEC elements within the federation, wherein the resource update message comprises at least one of a generic resource container and an application-specific resource container, wherein the generic resource container comprises information about a total amount of resources available at each of the second TEC elements, wherein the application-specific resource container comprises information about an amount of resources reserved for an application at each of the second TEC elements, wherein the federation comprises the second TEC elements and the first TEC element that share resources and provide requested data or services to a client;

storing, in storage resources coupled to the networking resources of the first TEC element, the generic resource container and the application-specific resource container; and

sharing the storage resources, computing resources, and the networking resources of the first TEC element with the second TEC elements in the federation according to the generic resource container and the application-specific resource container,

wherein the first TEC element and the second TEC elements are deployed between the client and a packet network.

14. The method implemented by the TEC element of claim 13, wherein the storage resources are further configured to store a federation policy identifying with the federation, wherein the federation policy comprises a rank of the second TEC elements in the federation according to a resource capacity of each of the second TEC elements.

15. The method implemented by the TEC element of claim 13, wherein the resource update messages are received from the second TEC elements of the federation periodically according to a pre-defined schedule stored in the storage resources.

16. The method implemented by the TEC element of claim 13, wherein the resource update messages only comprise the application-specific resource container, wherein the application-specific resource container only comprises information about a single resource that has exceeded a threshold indicating that the single resource is unavailable to be shared.

17. The method implemented by the TEC element of claim 16, wherein the resource update message including the application-specific resource container only comprises information about the single resource.

18. The method implemented by the TEC element of claim 13, wherein sharing the storage resources, the computing resources, and the networking resources of the TEC element with the second TEC elements in the federation further comprises:

receiving a request from the client for the data or the services provided by an application on an application layer of the first TEC element; and

selecting, using the computing resources, one of the second TEC elements when the storage resources indicates that the one of the second TEC elements has sufficient resources to accommodate the request from the client.

19. The method implemented by the first TEC element of claim 18, wherein sharing the storage resources, computing resources, and the networking resources of the TEC element with the second TEC elements in the federation further comprises:

transmitting, using the networking resources, a redirection request to redirect the request from the client to the selected one of the TEC elements; and

transmitting, using the networking resources, the request from the client to the selected one of the TEC elements in response to receiving an acceptance of the redirection from the selected one of the TEC elements.

20. The method implemented by the TEC element of claim 13, wherein the first TEC element is a master TEC element of the first TEC element, and wherein the first TEC element is the only TEC element in the federation permitted to request additional TEC elements to join the federation.