Service template generation and deployment based on service level agreement requirements
US-9385926-B2 · Jul 5, 2016 · US
US10230798B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10230798-B2 |
| Application number | US-201815863565-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jan 5, 2018 |
| Priority date | Jan 11, 2016 |
| Publication date | Mar 12, 2019 |
| Grant date | Mar 12, 2019 |
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.
Techniques are described for distributed processing of Internet of Things (IoT) device data by edge systems co-located within a globally-distributed set of co-location facilities deployed and managed by a co-location facility provider. For example, a method includes selecting, by at least one of a plurality of edge computing systems co-located within respective co-location facilities each deployed and managed by a single co-location facility provider, a selected edge computing system of the plurality of edge computing systems to process data associated with events generated by an IoT device. The method also includes provisioning, at the selected edge computing system, an application programming interface (API) endpoint for communication with the IoT device, receiving, by the selected edge computing system at the endpoint, the data associated with the events generated by the IoT device, and processing, by the selected edge computing system, the data associated with the events generated by the IoT device.
Opening claim text (preview).
What is claimed is: 1. A method comprising: selecting, by at least one of a plurality of edge computing systems co-located within respective co-location facilities each deployed and managed by a single co-location facility provider, a selected edge computing system of the plurality of edge computing systems to process data generated by an Internet of Things (IoT) device; provisioning, by the at least one of the plurality of edge computing systems, a proxy executing on one or more computing devices for processing the data at the selected edge computing system; provisioning, at a gateway device of the selected edge computing system, an application programming interface (API) endpoint associated with the proxy for communication with the IoT device; receiving, by the selected edge computing system at the API endpoint, the data generated by the IoT device; and processing, by the proxy of the selected edge computing system, the data generated by the IoT device and received at the API endpoint. 2. The method of claim 1 , further comprising: by the proxy, filtering the data generated by the IoT device based on configured policies; and by the proxy, discarding a subset of the data generated by the IoT device without forwarding the subset of the data to a core processing system. 3. The method of claim 1 , further comprising: by the proxy, performing network protocol translation on the data generated by the IoT device. 4. The method of claim 1 , further comprising: establishing a communication channel between the IoT device and the API endpoint, wherein receiving comprises receiving, by the selected edge computing system at the API endpoint, the data generated by the IoT device via the communication channel. 5. The method of claim 1 , wherein processing the data comprises routing, by the selected edge computing system, the data to a core processing system. 6. The method of claim 1 , wherein selecting the selected edge computing system comprises selecting the selected edge computing system in response to an IoT device registration manager of one of the edge computing systems receiving a device registration request from the IoT device, the method further comprising: managing registration and authentication of the IoT device by the IoT device registration manager. 7. The method of claim 1 , wherein selecting the selected edge computing system comprises selecting based on IoT device type and configured policies. 8. The method of claim 1 , wherein selecting the selected edge computing system comprises selecting based on IoT device location and configured policies, wherein the second edge computing system is located geographically closest to the IoT device. 9. The method of claim 1 , wherein processing the data comprises processing the data by a core processing center operated by the co-location provider. 10. The method of claim 1 , wherein processing the data comprises processing the data by one or more computing devices of an enterprise associated with the IoT device. 11. The method of claim 1 , wherein processing the data comprises processing the data by one or more computing devices of a cloud service provider. 12. A system comprising: a plurality of edge computing systems co-located within respective co-location facilities each deployed and managed by a single co-location facility provider, wherein at least one of the plurality of edge systems is configured to select a selected edge computing system of the plurality of edge computing systems to process data generated by an Internet of Things (IoT) device and provision a proxy on one or more computing devices for processing the data; and a gateway device of the selected edge computing system configured to provision an application programming interface (API) endpoint for communication with the IoT device, wherein the API endpoint is associated with the of the selected edge computing system, receive, at the API endpoint, the data generated by the IoT device, and process the data generated by the IoT device and received at the API endpoint. 13. The system of claim 12 , wherein each of the edge computing systems comprises: an Internet of Things (IoT) device registration manager configured to manage registration and authentication of IoT devices; an IoT edge processor configured to provision application programming interface (API) endpoints for communication with the IoT devices; and an IoT edge configurator configured to process data generated by the IoT devices, wherein the data is received via the API endpoints. 14. The system of claim 12 , wherein the proxy filters the data generated by the IoT devices based on configured policies, and discards a subset of the data generated by the IoT devices without forwarding the subset of the data to a core processing system. 15. The system of claim 12 , wherein the selected edge computing system comprises: an IoT traffic analytics engine configured to provide information regarding a state of one or more of the computing devices of the proxy. 16. A computer-readable storage device comprising instructions that when executed cause one or more processors of an edge computing system to: select the edge computing system, from among a plurality of edge computing systems co-located within respective co-location facilities each deployed and managed by a single co-location facility provider, to process data generated by an Internet of Things (IoT) device; provision a proxy executing on one or more computing devices of the edge computing system for processing the data at the selected edge computing system; provision an application programming interface (API) endpoint associated with the proxy at a gateway device of the edge computing system for communication with the IoT device; receive at the API endpoint the data generated by the IoT device; and process, by the proxy of the edge computing system, the data generated by the IoT device and received at the API endpoint.
based on client or server locations · CPC title
for collecting sensor information · CPC title
involving the movement of software or configuration parameters (network booting or remote initial program loading [RIPL] G06F9/4416) · CPC title
Distributed intermediate devices, i.e. intermediate devices for interaction with other intermediate devices on the same level · CPC title
Load balancing of requests to servers for services different from user content provisioning, e.g. load balancing across domain name servers · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.