Method of implementing content-centric network (CCN) using internet protocol (IP)-based network in gateway, and gateway

• US 9,185,186 B2
• Filed: 07/20/2012
• Issued: 11/10/2015
• Est. Priority Date: 12/28/2011
• Status: Active Grant

• Current Assignee: Samsung Electronics Co. Ltd.
• Original Assignee: Samsung Electronics Co. Ltd.
• Inventors: Hong, Seong Ik, Lee, Byoung Joon, Jang, Myeong Wuk
• Primary Examiner(s): Vostal, O. C.
• Application Number:
  US13/554,161
• Publication Number:
  US 20130173822A1
• Time in Patent Office: 1,208 Days
• Field of Search: 709/232, 709/238
• US Class Current: 1/1
• CPC Class Codes: H04L 45/306 Route determination based on the nature of the carried application
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching
• CPC Class Codes: H04L 67/63 Routing a service request depending on the request content or context

Abstract

A method of implementing a Content-Centric Network (CCN) using an Internet Protocol (IP)-based network, and a gateway that may implement such a method, are provided. A method of implementing a CCN using an IP-based network may involve: determining an application protocol and a packet type corresponding to the application protocol of an IP-based network, the application protocol being included in an IP packet of an IP-based network, and generating a content name corresponding to the IP packet, based on the application protocol and the packet type.

Claims

1. A method of implementing a Content-Centric Network (CCN) using an Internet Protocol (IP)-based network, the method comprising:

determining an application protocol and a packet type corresponding to the application protocol, the application protocol being included in an IP packet of the IP-based network;

determining a naming rule based on the application protocol and the packet type corresponding to the application protocol; and

generating a content name based on the naming rule.

2. The method of claim 1, further comprising:

converting the IP packet to a content-request packet for the CCN, using the generated content name.

3. The method of claim 1, wherein the determining the naming rule comprises looking up a naming-rule server that includes at least one naming rule.

4. The method of claim 1, wherein if the application protocol is a Hyper-text Transfer Protocol, and if the packet type indicates a request packet, the naming rule can be set to use a Uniform Resource Locator as a content name.

5. The method of claim 3, further comprising:

storing, in a local router, at least one part of the at least one naming rule included in the naming-rule server.

6. The method of claim 1, further comprising:

determining whether a two-way transfer scheme or a one-way transfer scheme is used by the application protocol.

7. The method of claim 6, wherein:

the IP packet is an IP packet requesting a content;

the method further comprises converting the IP packet requesting the content to a content-request packet for the CCN, using the content name, in response to determining that the two-way transfer scheme is used by the application protocol; and

the method further comprises converting an IP packet responding to the IP packet requesting the content to a data-response packet for the CCN, in response to determining that the two-way transfer scheme is used by the application protocol.

8. The method of claim 7, further comprising:

transmitting the content-request packet or the data-response packet.

9. The method of claim 6, further comprising:

generating a request packet for a content-request packet, using the generated content name, in response to a determination that the one-way transfer scheme is used by the application protocol;

transmitting the generated request packet to a router included in the CCN;

receiving the content-request packet from the router; and

transmitting the IP packet to the router, in response to the content-request packet.

10. The method of claim 9, wherein the content-request packet is transmitted to the gateway, based on a Pending Interest Table (PIT) generated by the request packet for the content-request packet.

11. The method of claim 1, further comprising:

storing a payload of the IP packet in a content cache of the gateway, based on whether the payload includes data.

12. The method of claim 11, further comprising:

generating a content name corresponding to the stored payload, by looking up the naming-rule server.

13. The method of claim 1, wherein the application protocol includes one or more of HTTP, FTP and SMTP.

14. A gateway for implementing a Content-Centric Network (CCN) using an Internet Protocol (IP)-based network, the gateway comprising:

at least one processor device;

a determining unit of the at least one processor device configured to determine an application protocol and a packet type corresponding to the application protocol, the application protocol being included in an IP packet of the IP-based network, and to determine a naming rule based on the application protocol and the packet type corresponding to the application protocol; and

a generating unit of the at least one processor device configured to generate a content name based on the naming rule.

15. The gateway of claim 14, further comprising:

a transfer scheme determining unit configured to determine whether a two-way transfer scheme or a one-way transfer scheme is used by the application protocol.

16. The gateway of claim 15, wherein:

the IP packet is an IP packet requesting a content;

the gateway comprises a first converter configured to convert the IP packet requesting the content to a content-request packet for the CCN, using the content name, in response to a determination that the two-way transfer scheme is used by the application protocol; and

the gateway comprises a second converter configured to convert an IP packet responding to the IP packet requesting the content to a data-response packet for the CCN, in response to a determination that the two-way transfer scheme is used by the application protocol.

17. The gateway of claim 16, further comprising:

a transmitter configured to transmit the content-request packet or the data-response packet.

18. The gateway of claim 15, further comprising:

a request packet generator configured to generate a request packet for a content-request packet, using the generated content name, in response to a determination that the one-way transfer scheme is used by the application protocol; and

a transmission and reception managing unit configured to transmit the generated request packet to a router included in the CCN, and configured to receive the content-request packet from the router, and to transmit the IP packet to the router, in response to the content-request packet.

19. The gateway of claim 18, wherein the content-request packet is transmitted to the gateway, based on a Pending Interest Table (PIT) generated by the request packet for the content-request packet.

20. The gateway of claim 14, further comprising:

a content cache to store a payload of the IP packet, based on whether the payload includes data.

21. The gateway of claim 14, wherein the application protocol includes one or more of HTTP, FTP and SMTP.

22. A router for converting an IP packet to a CCN-compatible packet, the router comprising:

a packet generator configured to convert an IP packet received from an IP-based network to a CCN-compatible packet by generating a content name based on a naming rule; and

a transmitter configured to transmit the CCN-compatible packet to a second router in a CCN,

wherein the naming rule is determined based on an application protocol included in a payload of the IP packet and a packet type corresponding to the application protocol.

23. The router of claim 22, wherein the CCN-compatible packet is a content-request packet or a data-response packet.

24. The router of claim 22, wherein the packet generator converts the IP packet to the CCN-compatible packet by adding a header that includes a content name to the IP packet.

25. The router of claim 22, wherein the packet generator converts the IP packet to the CCN-compatible packet by replacing a header of the IP packet with a header that includes a content name.

26. The router of claim 22, further comprising:

a content name generator configured to generate the content name based on the application protocol and the packet type of the IP packet.

27. The router of claim 22, further comprising:

a content cache to store a payload of the IP packet, based on whether the payload includes data.

28. The router of claim 26, wherein the application protocol includes one or more of HTTP, FTP and SMTP.