Cloud computing access gateway and method for providing a user terminal access to a cloud provider
US-9002932-B2 · Apr 7, 2015 · US
US11218538B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11218538-B2 |
| Application number | US-201816234865-A |
| Country | US |
| Kind code | B2 |
| Filing date | Dec 28, 2018 |
| Priority date | Dec 28, 2018 |
| Publication date | Jan 4, 2022 |
| Grant date | Jan 4, 2022 |
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.
Technologies for determining a set of edge resources to offload a workload from a client compute device based on a brokering logic provided by a service provider include a device that includes circuitry that is in communication with edge resources. The circuitry is to receive a brokering logic from a service provider receive a request from a client compute device, wherein the request includes a function to be used to execute the request and one or more parameters associated with the client compute device, determine the one or more parameters, select, as a function of the one or more parameters and the brokering logic, a physical implementation to perform the function, wherein the physical implementation indicates a set of edge resources and a performance level for each edge resource of the set of edge resources, and perform, in response to a selection of the physical implementation, the request using the set of edge resources associated with the physical implementation.
Opening claim text (preview).
What is claimed is: 1. A device comprising: communication circuitry to: access, from a service provider, data indicative of a function, different physical implementations of the function, and a brokering logic; and access a request from a client compute device; processor circuitry in communication with edge resources, wherein the processor circuitry is to: determine the function to be used to execute the request and one or more parameters associated with the client compute device; select, based on the one or more parameters and the brokering logic, a first of the physical implementations, wherein the first physical implementation includes a first set of the edge resources and defines a performance level for a first edge resource of the first set of the edge resources; determine a wait time for the first physical implementation to become available to perform the function; in response to determining the wait time is greater than zero, determine a predicted routing time to find, based on the one or more parameters and the brokering logic, a second physical implementation, wherein the second physical implementation includes a second set of the edge resources and defines a performance level for a second edge resource of the second set of the edge resources; select one of the first physical implementation or the second physical implementation to perform the function based on a comparison of the wait time and the predicted routing time; and perform the function in response to the request using the corresponding one of the first set of the edge resources or the second set of the edge resources associated with the determined one of the first physical implementation or the second physical implementation. 2. The device of claim 1 , wherein the request includes a section of an application to be executed by one or more edge resources. 3. The device of claim 1 , wherein the circuitry is further to receive data indicative of one or more functions and different physical implementations of each function. 4. The device of claim 1 , wherein the one or more parameters include a service level agreement associated with the client compute device, a maximum cost to perform the function, and/or a list of acceptable service providers. 5. The device of claim 1 , wherein the circuitry is further to receive telemetry data of the function to determine a current load or last known load of the function, the different physical implementations of the function, and/or performance of the function. 6. The device of claim 5 , wherein the performance of the function includes a latency of each edge resource associated with the different physical implementations of the function. 7. The device of claim 1 , wherein the circuitry is further to determine whether the first set of the edge resources of the selected physical implementation is available to perform the function. 8. The device of claim 7 , wherein the circuitry is further to determine, in response to a determination that the first set of the edge resources is not available, a next best physical implementation to perform the function. 9. The device of claim 1 , wherein the edge resources include one or more accelerator devices, one or more compute devices, one or more storage devices, and/or one or more memory resources. 10. A method comprising: accessing, by an edge gateway device from a service provider, data indicative of a function, different physical implementations of the function, and a brokering logic; accessing, by the edge gateway device, a request from a client compute device; determining, by the edge gateway device, the function to be used to execute the request and one or more parameters associated with the client compute device; selecting, based on the one or more parameters and the brokering logic, a first of the physical implementations, wherein the first physical implementation includes a first set of edge resources and defines a performance level for a first edge resource of the first set of the edge resources; determining a wait time for the first physical implementation to become available to perform the function; in response to determining the wait time is greater than zero, determining a predicted routing time to find, based on the one or more parameters and the brokering logic, a second physical implementation, wherein the second physical implementation includes a second set of the edge resources and defines a performance level for a second edge resource of the second set of the edge resources; selecting one of the first physical implementation or the second physical implementation to perform the function based on a comparison of the wait time and a the predicted routing time; and performing the function in response to the request using the corresponding one of the first set of the edge resources or the second set of the edge resources associated with the determined one of the first physical implementation or the second physical implementation. 11. The method of claim 10 , wherein the request includes a section of an application to be executed by one or more edge resources. 12. The method of claim 10 , wherein the accessed data is further indicative of one or more functions and different physical implementations of each function. 13. The method of claim 10 , wherein the one or more parameters include a service level agreement associated with the client compute device, a maximum cost to perform the function, and/or a list of acceptable service providers. 14. The method of claim 10 further comprising receiving, by the edge gateway device, telemetry data of the function to determine a current load or last known load of the function, different physical implementations of the function, and/or performance of the function. 15. The method of claim 14 , wherein the performance of the function includes a latency of each edge resource associated with the different physical implementations of the function. 16. The method of claim 10 further comprising determining, by the edge gateway device, whether the first set of the edge resources of the selected physical implementation is available to perform the function. 17. The method of claim 16 further comprising determining, in response to determining that the first set of the edge resources is not available and by the edge gateway device, a next best physical implementation to perform the function. 18. The method of claim 17 , wherein the edge resources include one or more accelerator devices, one or more compute devices, one or more storage devices, and/or one or more memory resources. 19. One or more non-transitory machine-readable storage media comprising a plurality of instructions stored thereon that, in response to being executed, cause a device to: access, from a service provider, data indicative of a function, different physical implementations of the function, and a brokering logic; and access a request from a client compute device; determine the function to be used to execute the request and one or more parameters and associated with the client compute device; select, based on the one or more parameters and the brokering logic, a first of the physical implementations, wherein the first physical implementation includes a first set of edge resources and defines a performance level for a first edge resource of the first set of the edge resources; determine a wait time for the first physical implementation to become available to perform the function; in response to determining the wait time is greater than zero, determine a predicted r
negotiation of tariff · CPC title
Brokering proxy services · CPC title
Routing a service request depending on the request content or context · CPC title
taking into account QoS or priority requirements · CPC title
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.