Data management in an edge network

Patent metadata

Field	Value
Publication number	US-10979522-B2
Application number	US-201916362946-A
Country	US
Kind code	B2
Filing date	Mar 25, 2019
Priority date	Nov 21, 2016
Publication date	Apr 13, 2021
Grant date	Apr 13, 2021

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 rCDN node comprising:
a memory including instructions; and
processing circuitry that, when in operation, is configured by the instructions to:
receive a first communication from a first downstream node;
receive a second communication from a second downstream node;
create an upstream communication from the first communication and the second communication; and
transmit the upstream communication to an upstream node.

2. The rCDN node of claim 1 , wherein, to create the upstream communication from the first communication and the second communication, the processing circuitry is configured by the instructions to:
determine that the first communication and the second communication are contextually related to a context from several contexts; and
apply a computation selected by the context, the computation accepting data from the first communication and data from the second communication as input and producing a result that is included in the upstream communication.

3. The rCDN node of claim 2 , wherein the computation is at least one of a transformation or analytics.

4. The rCDN node of claim 2 , wherein the rCDN node caches the result.

5. The rCDN node of claim 4 , wherein the processing circuitry is configured by the instructions to respond to a request for the result with a cached copy of the result.

6. The rCDN node of claim 2 , wherein the processing circuitry is configured by the instructions to request a portion of the computation be satisfied by another rCDN node.

7. A method for a reverse content data network (rCDN) node, the method comprising:
receiving a first communication from a first downstream node;
receiving a second communication from a second downstream node;
creating an upstream communication from the first communication and the second communication; and
transmitting the upstream communication to an upstream node.

8. The method of claim 7 , wherein creating the upstream communication from the first communication and the second communication includes:
determining that the first communication and the second communication are contextually related to a context from several contexts; and
applying a computation selected by the context, the computation accepting data from the first communication and data from the second communication as input and producing a result that is included in the upstream communication.

9. The method of claim 8 , wherein the computation is at least one of a transformation or analytics.

10. The method of claim 8 , wherein the rCDN node caches the result.

11. The method of claim 10 , comprising responding to a request for the result with a cached copy of the result.

12. The method of claim 8 , comprising requesting a portion of the computation be satisfied by another rCDN node.

13. At least one non-transitory machine-readable medium including instructions for a reverse content data network (rCDN) node, the instructions, when executed by processing circuitry of the rCDN node, cause the rCDN node to perform operations comprising:
receiving a first communication from a first downstream node;
receiving a second communication from a second downstream node;
creating an upstream communication from the first communication and the second communication; and
transmitting the upstream communication to an upstream node.

14. The at least one non-transitory machine-readable medium of claim 13 , wherein creating the upstream communication from the first communication and the second communication includes:
determining that the first communication and the second communication are contextually related to a context from several contexts; and
applying a computation selected by the context, the computation accepting data from the first communication and data from the second communication as input and producing a result that is included in the upstream communication.

15. The at least one non-transitory machine-readable medium of claim 14 , wherein the computation is at least one of a transformation or analytics.

16. The at least one non-transitory machine-readable medium of claim 14 , wherein the rCDN node caches the result.

17. The at least one non-transitory machine-readable medium of claim 16 , wherein the operations comprise responding to a request for the result with a cached copy of the result.

18. The at least one non-transitory machine-readable medium of claim 14 , wherein the operations comprise requesting a portion of the computation be satisfied by another rCDN node.

Assignees

• Intel Corp

Inventors

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

Classifications

• H04L67/568

  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

• H04L67/63

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

• H04L43/091

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

• H04L67/51

  Discovery or management thereof, e.g. service location protocol [SLP] or web services · CPC title