Allocating cloud-hosted application resources using end-user metrics
US-9356883-B1 · May 31, 2016 · US
US2018041578A1 · US · A1
| Field | Value |
|---|---|
| Publication number | US-2018041578-A1 |
| Application number | US-201615231364-A |
| Country | US |
| Kind code | A1 |
| Filing date | Aug 8, 2016 |
| Priority date | Aug 8, 2016 |
| Publication date | Feb 8, 2018 |
| Grant date | — |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
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.
Opening claim text (preview).
W hat is claimed is: 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 contain
Admission control; Resource allocation · CPC title
Electricity · mapped topic
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 title
Electricity · mapped topic
Discovery or management thereof, e.g. service location protocol [SLP] or web services · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.