Method and system for content distribution among mec networks
US-2021152998-A1 · May 20, 2021 · US
US11546232B1 · US · B1
| Field | Value |
|---|---|
| Publication number | US-11546232-B1 |
| Application number | US-202217586113-A |
| Country | US |
| Kind code | B1 |
| Filing date | Jan 27, 2022 |
| Priority date | Jan 27, 2022 |
| Publication date | Jan 3, 2023 |
| Grant date | Jan 3, 2023 |
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 method for providing data to a client computing device from an edge computing device is discussed herein. The method may include performing a network proximity check regarding the client computing device associated with a request for data captured by the wideband sensor. The method may further include determining, based on at least one proximity metric associated with the client computing device, a route for data responsive to the request for data associated with the network proximity check, where the route is one of a route including the cloud storage or a route that does not include the cloud storage. The method may also include receiving the request for data captured by the wideband sensor associated with the network proximity check. The method may also include transmitting the data responsive to the request for data captured by the wideband sensor associated with the network proximity check to the client computing device through the determined route.
Opening claim text (preview).
What is claimed: 1. A method for providing data to a client computing device from an edge computing device of a system comprising the edge computing device communicatively coupled with a local storage, a wideband sensor, the client computing device, and a cloud storage, the method comprising: performing a network proximity check regarding the client computing device associated with a request for data captured by the wideband sensor; determining, based on at least one proximity metric associated with the client computing device, a route for data responsive to the request for data associated with the network proximity check, wherein the route is one of a route including the cloud storage or a route that does not include the cloud storage; receiving the request for data captured by the wideband sensor associated with the network proximity check; transmitting the data responsive to the request for data captured by the wideband sensor associated with the network proximity check to the client computing device through the determined route; receiving the data captured by the wideband sensor; identifying, based on an analysis of the received data, an event associated with the received least one key performance indicators (KPI) associated with the identified event; storing, in the local storage, the received data associated with the identified event, an identifier of the identified event, and the at least one KPI; and transmitting, to the cloud storage, the at least one KPI, at least one of the identifier of the identified event, and an identifier of a location of the received data associated with the identified event in the local storage. 2. The method of claim 1 , wherein the at least one proximity metric comprises one or more of a latency of a communication between the edge computing device and the client computing device or a number of hops between the edge computing device and the client computing device, wherein when a value associated with the at least one proximity metric is above a threshold value the determined route includes the cloud storage and when the value associated with the at least one proximity metric is below the threshold value the determined route does not include the cloud storage. 3. The method of claim 2 , wherein determining the route for the data responsive to the request for data associated with the network proximity check is further based on a bandwidth available for the communication between the edge computing device and the client computing device, wherein if the bandwidth available for the communication between the edge computing device and the client computing device is below a threshold value the determined route includes the cloud storage. 4. The method of claim 1 , wherein the network proximity check is performed based on one or more of a configured period, a timeout parameter, or a detected event. 5. The method of claim 1 , wherein the identified event is a particular cycle of a process and the at least one KPI is a cycle time associated with the particular cycle of the process. 6. The method of claim 1 , wherein the client computing device (1) receives information relating to a plurality of KPIs associated with a plurality of identified events from the cloud storage, (2) transmits the request for data captured by the wideband sensor, wherein the request for data captured by the wideband sensor is associated with at least one of the plurality of identified events from the cloud storage, and (3) receives an indication of a location of the received data associated with the at least one of the plurality of identified events. 7. The method of claim 6 , wherein the indicated location is a location in the cloud storage, and the request for data captured by the wideband sensor is received from the cloud storage. 8. The method of claim 6 , wherein the indicated location is a location in the local storage and the request for data captured by the wideband sensor is received from the client computing device and comprises the indicated location. 9. The method of claim 1 , wherein the edge computing device and the client computing device are in a same virtual network. 10. An edge computing device for providing data to a client computing device from the edge computing device of a system comprising the edge computing device communicatively coupled with a local storage, a wideband sensor, the client computing device, and a cloud storage, the edge computing device comprising: a memory; and at least one hardware processor coupled to the memory and configured to: perform a network proximity check regarding the client computing device associated with a request for data captured by the wideband sensor; determine, based on at least one proximity metric associated with the client computing device, a route for data responsive to the request for data associated with the network proximity check, wherein the route is one of a route including the cloud storage or a route that does not include the cloud storage; receive the request for data captured by the wideband sensor associated with the network proximity check; transmit the data responsive to the request for data captured by the wideband sensor associated with the network proximity check to the client computing device through the determined route; receiving the data captured by the wideband sensor; identify, based on an analysis of the received data, an event associated with the received least one key performance indicators (KPI) associated with the identified event; store, in the local storage, the received data associated with the identified event, an identifier of the identified event, and the at least one KPI; and transmit, to the cloud storage, the at least one KPI, at least one of the identifier of the identified event, and an identifier of a location of the received data associated with the identified event in the local storage. 11. The edge computing device of claim 10 , wherein the at least one proximity metric comprises one or more of a latency of a communication between the edge computing device and the client computing device or a number of hops between the edge computing device and the client computing device, wherein when a value associated with the at least one proximity metric is above a threshold value the determined route includes the cloud storage and when the value associated with the at least one proximity metric is below the threshold value the determined route does not include the cloud storage. 12. The edge computing device of claim 11 , wherein determining the route for the data responsive to the request for data associated with the network proximity check is further based on a bandwidth available for the communication between the edge computing device and the client computing device, wherein if the bandwidth available for the communication between the edge computing device and the client computing device is below a threshold value the determined route includes the cloud storage. 13. The edge computing device of claim 10 , wherein the network proximity check is performed based on one or more of a configured period, a timeout parameter, or a detected event. 14. The edge computing device of claim 10 , wherein the identified event is a particular cycle of a process and the at least one KPI is a cycle time associated with the particular cycle of the process. 15. The edge computing device of claim 10 , wherein the client computing device (1) receives information relating to a plurality of KPIs associated with a plurality of identified events from the cloud storage, (2) transmits the request for data captured by the wideband sensor, wher
Threshold monitoring · CPC title
by checking functioning · CPC title
Determining service level performance parameters or violations of service level contracts, e.g. violations of agreed response time or mean time between failures [MTBF] · CPC title
Packet rate · CPC title
using filtering, e.g. reduction of information by using priority, element types, position or time · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.