IP Library › Granted Patent US 11,509,745
Granted Patent B2
US 11,509,745 · App. 16/457,704 · Granted Nov 22, 2022

Efficient remote function execution in an information centric network

Inventors: S. M. Iftekharul Alam (Hillsboro, OR); Yi Zhang (Portland, OR); Satish Chandra Jha (Hillsboro, OR); Kuilin Clark Chen (Hillsboro, OR); Kathiravetpillai Sivanesan (Portland, OR); Stepan Karpenko (Hillsboro, OR); Srikathyayani Srikanteswara (Portland, OR); Venkatesan Nallampatti Ekambaram (Hillsboro, OR)
Assignee: Intel Corporation
H04L67/63H04L43/08H04L43/12H04L43/16H04L67/10H04L67/568
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,509,745
App. No.
16/457,704
Granted
Nov 22, 2022
Kind
B2
Abstract

Systems and techniques for efficient remote function execution in an information centric network (ICN) are described herein. For example, a requestor node may transmit an admission probe interest packet. Here, the admission probe interest packet includes a name that includes a function. The admission probe interest packet also includes a metric of a parameter of the function. In response, the requestor node may receive a manifest data packet. The manifest includes a metric of function execution at a node that created the manifest data packet. The manifest also includes a name of an implementation of the function. The requestor node may then determine that the metric of function execution meets a threshold and transmit an interest packet that includes the name of the implementation of the function.

Claims (43)

1. A device, in a requestor node, for efficient remote function execution in an information centric network (ICN), the device comprising:

processing circuitry; and

memory including instructions that, when the device is in operation, configure the processing circuitry to:

transmit an admission probe interest packet, the admission probe interest packet identified from other interest packets by an admission probe prefix, the admission probe interest packet including a name that includes a function, the admission probe interest packet including a metric of a parameter of the function;

receive a manifest data packet in response to the admission probe interest packet, the manifest including:

names of multiple implementations of the function that meet the metric of the parameter of the function; and

respective metrics of function execution, for each of the multiple implementations of the function, at a provider node that created the manifest data packet, wherein the names of the multiple implementations of the function differentiate different implementations of the function from each other;

determine that one of the metrics of function execution meets a threshold; and

transmit an interest packet that includes the name of the implementation of the function corresponding to the metric of function execution that meets the threshold, the interest packet being a standard ICN interest packet.

2. The device of claim 1 , wherein the metric of the parameter of the function is at least one of a size or a type of data.

3. The device of claim 1 , wherein the metric of function execution is at least one of an estimated execution time, an execution latency, an output type, an implementation of the function, or a publisher of the function.

4. The device of claim 1 , wherein the instructions further configure the processing circuitry to receive a second manifest in response to the admission probe interest packet, the second manifest originating from a second provider node.

5. The device of claim 4 , wherein the instructions further configure the processing circuitry to determine that the metric of function execution in the second manifest does not meet a required threshold.

6. The device of claim 5 , wherein the instructions further configure the processing circuitry to transmit a negative acknowledgment (NACK) in response to the metric of function execution in the second manifest not meeting the required threshold.

7. The device of claim 5 , wherein the requestor node takes no further action with respect to the second manifest.

8. The device of claim 1 , wherein the admission probe interest packet includes a second parameter of the function, the second parameter below a size threshold.

9. A method for efficient remote function execution in an information centric network (ICN), the method comprising:

transmitting, at a requestor node, an admission probe interest packet, the admission probe interest packet identified from other interest packets by an admission probe prefix, the admission probe interest packet including a name that includes a function, the admission probe interest packet including a metric of a parameter of the function;

receiving a manifest data packet in response to the admission probe interest packet, the manifest including:

names of multiple implementations of the function that meet the metric of the parameter of the function; and

respective metrics of function execution, for each of the multiple implementations of the function, at a provider node that created the manifest data packet, wherein the names of the multiple implementations of the function differentiate different implementations of the function from each other;

determining that one of the metrics of function execution meets a threshold; and

transmitting an interest packet that includes the name of the implementation of the function corresponding to the metric of function execution that meets the threshold, the interest packet being a standard ICN interest packet.

10. The method of claim 9 , wherein the metric of the parameter of the function is at least one of a size or a type of data.

11. The method of claim 9 , wherein the metric of function execution is at least one of an estimated execution time, an execution latency, an output type, an implementation of the function, or a publisher of the function.

12. The method of claim 9 , comprising receiving a second manifest in response to the admission probe interest packet, the second manifest originating from a second provider node.

13. The method of claim 12 , comprising determining that the metric of function execution in the second manifest does not meet a required threshold.

14. The method of claim 13 , comprising transmitting a negative acknowledgment (NACK) in response to the metric of function execution in the second manifest not meeting the required threshold.

15. The method of claim 13 , wherein the requestor node takes no further action with respect to the second manifest.

16. The method of claim 9 , wherein the admission probe interest packet includes a second parameter of the function, the second parameter below a size threshold.

17. At least one non-transitory machine-readable medium including instructions for efficient remote function execution in an information centric network (ICN), the instructions, when executed by processing circuitry, cause the processing circuitry to perform operations comprising:

transmitting, at a requestor node, an admission probe interest packet, the admission probe interest packet identified from other interest packets by an admission probe prefix, the admission probe interest packet including a name that includes a function, the admission probe interest packet including a metric of a parameter of the function;

receiving a manifest data packet in response to the admission probe interest packet, the manifest including:

names of multiple implementations of the function that meet the metric of the parameter of the function; and

respective metrics of function execution, for each of the multiple implementations of the function, at a provider node that created the manifest data packet, wherein the names of the multiple implementations of the function differentiate different implementations of the function from each other;

determining that one of the metrics of function execution meets a threshold; and transmitting an interest packet that includes the name of the implementation of the function corresponding to the metric of function execution that meets the threshold, the interest packet being a standard ICN interest packet.

18. The at least one non-transitory machine-readable medium of claim 17 , wherein the metric of the parameter of the function is at least one of a size or a type of data.

19. The at least one non-transitory machine-readable medium of claim 17 , wherein the metric of function execution is at least one of an estimated execution time, an execution latency, an output type, an implementation of the function, or a publisher of the function.

20. The at least one non-transitory machine-readable medium of claim 17 , wherein the operations comprise receiving a second manifest in response to the admission probe interest packet, the second manifest originating from a second provider node.

21. The at least one non-transitory machine-readable medium of claim 20 , wherein the operations comprise determining that the metric of function execution in the second manifest does not meet a required threshold.

22. The at least one non-transitory machine-readable medium of claim 21 , wherein the operations comprise transmitting a negative acknowledgment (NACK) in response to the metric of function execution in the second manifest not meeting the required threshold.

23. The at least one non-transitory machine-readable medium of claim 21 , wherein the requestor node takes no further action with respect to the second manifest.

24. The at least one non-transitory machine-readable medium of claim 17 , wherein the admission probe interest packet includes a second parameter of the function, the second parameter below a size threshold.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 8, 2020
From: ALAM, S. M. IFTEKHARUL; ZHANG, YI; JHA, SATISH CHANDRA; CHEN, KUILIN CLARK; SIVANESAN, KATHIRAVETPILLAI; KARPENKO, STEPAN; SRIKANTESWARA, SRIKATHYAYANI; EKAMBARAM, VENKATESAN NALLAMPATTI
To: INTEL CORPORATION
Reel/Frame 053153/0151 →
Continuity (1)
Related Publication 20190327340A1 · Oct 24, 2019