Representational state transfer operations using information centric networking

Patent metadata

Field	Value
Publication number	US-2016014234-A1
Application number	US-201514633580-A
Country	US
Kind code	A1
Filing date	Feb 27, 2015
Priority date	Jul 13, 2014
Publication date	Jan 14, 2016
Grant date	—

Abstract

In one implementation, a method includes transmitting, to a server, a first interest message. The first interest message includes a request for a representational state transfer (REST) operation and a name of a first state for the REST operation. The method also includes receiving, from the server, a second interest message. The second interest message includes the name of the first state for the REST operation. The method further includes transmitting, to the server, the first state based on the second interest message and receiving, from the server, a response to the REST operation.

First claim

What is claimed is:

1 . A method comprising:
transmitting, to a server, a first interest message, wherein the first interest message comprises a request for a representational state transfer (REST) operation and a first name of a first state for the REST operation; receiving, from the server, a second interest message, wherein the second interest message comprises the first name of the first state for the REST operation; transmitting, to the server, the first state based on the second interest message; and receiving, from the server, a response to the REST operation.

2 . The method of claim 1 , further comprising:
transmitting, to the server, an initial interest message comprising the first name of the first state for the REST operation; and receiving, from the server, the first state.

3 . The method of claim 1 , wherein the first interest message further comprises one or more additional names.

4 . The method of claim 3 , wherein transmitting the first state comprises:
transmitting, to the server, a plurality of data objects based on the first name and the one or more additional names, wherein each data object of the plurality of data objects comprises a portion of the first state.

5 . The method of claim 1 , wherein transmitting the first state comprises:
transmitting, to the server, a Named Data Networking (NDN) data object comprising the first state or a Content Centric Networking (CCN) data object comprising the first state.

6 . The method of claim 1 , wherein the request for a representational state transfer (REST) operation comprises a second name and wherein the second name identifies the REST operation.

7 . The method of claim 1 , wherein the response comprises a result of the REST operation.

8 . The method of claim 1 , wherein the response comprises data indicating that an updated state is available.

9 . The method of claim 8 , further comprising:
transmitting, to the server, a third interest message, wherein the third interest message comprises a second name for the updated state; and receiving, from the server, the updated state.

10 . The method of claim 1 , wherein the first name comprises a non-routable name.

11 . The method of claim 1 , wherein the first name allows the server to request first state when the first state is used for the REST operation.

12 . A method comprising:
receiving, from a client device, a first interest message, wherein the first interest mess age comprises a request for a representational state transfer (REST) operation and a first name of a first state for the REST operation; transmitting, to the client device, a second interest message, wherein the second interest message comprises the first name of the first state for the REST operation; receiving, from the client device, the first state; and transmitting, to the client device, a response to the REST operation.

13 . The method of claim 12 , further comprising:
receiving, from the client device, an initial interest message comprising the first name of the first state for the REST operation; and transmitting, to the client device, the first state.

14 . The method of claim 12 , wherein the first interest message further comprises one or more additional names.

15 . The method of claim 14 , wherein receiving the first state comprises:
receiving a plurality of data objects based on the first name and the one or more additional names, wherein each data object of the plurality of data objects comprises a portion of the first state.

16 . The method of claim 12 , wherein receiving the first state comprises:
receiving a Named Data Networking (NDN) data object comprising the first state or a Content Centric Networking (CCN) data object comprising the first state.

17 . The method of claim 12 , wherein the request for a representational state transfer (REST) operation comprises a second name and wherein the second name identifies the REST operation.

18 . The method of claim 12 , further comprise:
performing the REST operation based on the first state.

19 . The method of claim 12 , wherein the response comprises a result of the REST operation.

20 . The method of claim 12 , wherein the response comprises data indicating that an updated state is available.

21 . The method of claim 20 , further comprising:
receiving, from the client, a third interest message, wherein the third interest message comprises a second name for the updated state; and transmitting, to the client, the updated state.

22 . The method of claim 12 , wherein the first name comprises a non-routable name.

23 . The method of claim 12 , wherein the first name allows the first state to be requested when the first state is used for the REST operation.

24 . An apparatus, comprising:
a plurality of network interfaces; one or more processors; and a memory comprising instructions that when executed cause the one or more processors to perform operations comprising:
receiving a first interest message on a first network interface of the plurality of network interfaces, wherein the first interest message comprises a request for a representational state transfer (REST) operation and a first name of a first state for the REST operation;
generating a first entry in a pending interest table (PIT), wherein the first entry comprises first data indicative of the request and the first name; and
forwarding the first interest message on a second network interface of the plurality of network interfaces.

25 . The apparatus of claim 24 , wherein the operations further comprise:
receiving a second interest message for a client state, wherein the second interest message comprises the first name; determining whether the first name comprises a non-routable name; generating a second entry in the PIT based on the first entry, wherein the second entry comprises second data indicative of the first name, the first network interface, and the second network interface when the first name comprises the non-routable name; and forwarding the second interest message on the first network interface based on the PIT when the first name comprises the non-routable name.

26 . The apparatus of claim 25 , wherein the operations further comprise:
receiving the client state; forwarding the client state based on the second entry in the PIT; and removing the second entry from the PIT.

27 . The apparatus of claim 25 , wherein the first interest message is associated with a first timeout period, wherein the second interest message is associated with a second timeout period, and wherein the second timeout period is less than or equal to the first timeout period.

28 . The apparatus of claim 25 , wherein the operations further comprise:
forwarding the second interest message on the first network interface based on a forwarding information bas (FIB) when the first name comprises a routable name.

29 . The apparatus of claim 24 , wherein the operations further comprise:
receiving a response to the request for the rest operation on the second interface; forwarding the response on the first interface; and removing the first entry from the PIT.

Assignees

• Cisco Tech Inc

Inventors

• Oran Dave
• Stapp Mark
• Moiseenko Ilya
• So Won

Classifications

• H04L63/102

  Entity profiles · CPC title

• H04L45/306

  Route determination based on the nature of the carried application · CPC title

• H04L63/101 Primary

  Access control lists [ACL] · CPC title

• H04L45/742 Primary

  Route cache; Operation thereof · CPC title

• H04L67/10

  in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46) · CPC title