Data management in an edge network

Patent metadata

Field	Value
Publication number	US-11601522-B2
Application number	US-202117228386-A
Country	US
Kind code	B2
Filing date	Apr 12, 2021
Priority date	Nov 21, 2016
Publication date	Mar 7, 2023
Grant date	Mar 7, 2023

Abstract

Generally discussed herein are systems, devices, and methods for data management in a reverse content data network (rCDN). A component of the rCDN may include a memory to hold content received from a first sensor device of a plurality of sensor devices of the rCDN and first attributes that describe properties of the content. The component may include processing circuitry to receive second content from a second sensor device of the plurality of sensor devices, the second content including a plurality of second attributes that describe properties of the second content, and forward, in response to a determination, based on the first and second attributes, that there is insufficient space to store the second content on the memory, the second content to a node of the rCDN that is fewer hops away from a backend cloud than the component.

First claim

What is claimed is:

1. An edge device comprising:
storage to hold first data received from a first sensor device of a plurality of sensor devices and first attributes that describe properties of the first data;
a memory including instructions; and
processing circuitry that, when in operation, is configured by the instructions to:
receive second data from a second sensor device of the plurality of sensor devices, the second data including a plurality of second attributes that describe properties of the second data;
determine, based on the first and second attributes, that there is insufficient resource to process the second data on the edge device; and
forward, in response to the determination, the second data to a node of a network that is fewer hops away from a cloud than the edge device, the edge device being connected to the network when in operation.

2. The edge device of claim 1 , wherein the first sensor device or the second sensor device are located in a second edge device.

3. The edge device of claim 1 , wherein the insufficient resource is insufficient space in the storage.

4. The edge device of claim 1 , wherein the insufficient resource is insufficient compute capacity.

5. The edge device of claim 1 , wherein the first and second attributes pertain to a service to process the second data, and wherein, to forward the second data based on the first and second attributes, the processing circuitry is configured by the instructions to offload a service for the second data to the node.

6. The edge device of claim 5 , wherein the service operates as a tenant on hardware of the device or the node.

7. The edge device of claim 1 , wherein the first and second attribute are quality-of-service (QoS) attributes.

8. A method performed by processing circuitry of an edge device, the method comprising:
holding first data, in storage of the edge device, received from a first sensor device of a plurality of sensor devices and first attributes that describe properties of the first data;
receiving second data from a second sensor device of the plurality of sensor devices, the second data including a plurality of second attributes that describe properties of the second data;
determining, based on the first and second attributes, that there is insufficient resource to process the second data on the edge device; and
forwarding, in response to the determination, the second data to a node of a network that is fewer hops away from a cloud than the edge device, the edge device being connected to the network when in operation.

9. The method of claim 8 , wherein the insufficient resource is insufficient space in the storage.

10. The method of claim 8 , wherein the insufficient resource is insufficient compute capacity in the processing circuitry.

11. The method of claim 8 , wherein the first and second attributes pertain to a service to process the second data, and wherein forwarding the second data based on the first and second attributes includes offloading a service for the second data to the node.

12. At least one non-transitory machine readable medium including instructions that, when executed by processing circuitry of an edge device, cause the processing circuitry to perform operations comprising:
holding first data, in storage of the edge device, received from a first sensor device of a plurality of sensor devices and first attributes that describe properties of the first data;
receiving second data from a second sensor device of the plurality of sensor devices, the second data including a plurality of second attributes that describe properties of the second data;
determining, based on the first and second attributes, that there is insufficient resource to process the second data on the edge device; and
forwarding, in response to the determination, the second data to a node of a network that is fewer hops away from a cloud than the edge device, the edge device being connected to the network when in operation.

13. The at least one non-transitory machine readable medium of claim 12 , wherein the first sensor device or the second sensor device are located in a second edge device.

14. The at least one non-transitory machine readable medium of claim 12 , wherein the insufficient resource is insufficient space in the storage.

15. The at least one non-transitory machine readable medium of claim 12 , wherein the insufficient resource is insufficient compute capacity.

16. The at least one non-transitory machine readable medium of claim 12 , wherein the first and second attributes pertain to a service to process the second data, and wherein forwarding the second data based on the first and second attributes includes offloading a service for the second data to the node.

17. The at least one non-transitory machine readable medium of claim 16 , wherein the service operates as a tenant on hardware of the device or the node.

18. The at least one non-transitory machine readable medium of claim 12 , wherein the first and second attribute are quality-of-service (QoS) attributes.

19. The edge device of claim 1 , wherein the insufficient resource is insufficient network resources, insufficient memory capacity, or insufficient redundancy.

20. The edge device of claim 1 , wherein the first and second attribute are uplink attributes, downlink attributes, latency attributes, or connectivity type attributes.

21. The method of claim 8 , wherein the insufficient resource is insufficient network resources, insufficient memory capacity, or insufficient redundancy.

22. The method of claim 8 , wherein the first and second attribute are uplink attributes, downlink attributes, latency attributes, or connectivity type attributes.

23. The at least one non-transitory machine readable medium of claim of claim 12 , wherein the insufficient resource is insufficient network resources, insufficient memory capacity, or insufficient redundancy.

24. The at least one non-transitory machine readable medium of claim of claim 12 , wherein the first and second attribute are uplink attributes, downlink attributes, latency attributes, or connectivity type attributes.

25. An edge appliance comprising:
memory to hold first content from a first sensor of a plurality of sensors and first attributes that describe properties of the first content;
instructions; and
processor circuitry that, when in operation, is configured by the instructions to:
access second content from a second sensor of the plurality of sensors, the second content including a plurality of second attributes that describe properties of the second content;
determine, based on the first and second attributes, that there is insufficient resource to process the second content on the edge device; and
cause, in response to the determination, the second content to be forwarded to a node of a network that is fewer hops away from a cloud than the edge device, the edge device being connected to the network when in operation.

26. The edge appliance of claim 25 , wherein the first sensor or the second sensor are located in different devices.

27. The edge appliance of claim 25 , wherein the insufficient resource is insufficient space in the storage.

28. The edge appliance of claim 25 , wherein the insufficient resource is insufficient compute capacity in the processing circuitry.

29. The edge appliance of claim 25 , wherein th

Assignees

• Intel Corp

Inventors

• Moustafa Hassnaa
• Schooler Eve M
• Zage David John
• Sedayao Jeffrey Christopher
• Cohen David E
• Lee Sung

Classifications

• H04L67/568 Primary

  Storing data temporarily at an intermediate stage, e.g. caching · CPC title

• H04L41/5009 Primary

  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

• H04L45/14

  Routing performance; Theoretical aspects · CPC title

• H04L43/091

  Measuring contribution of individual network components to actual service level · CPC title

• H04L67/63

  Routing a service request depending on the request content or context · CPC title