NODE AND COMMUNICATION METHOD FOR SUPPORTING CONTENT MOBILITY

• US 20140365550A1
• Filed: 06/11/2014
• Published: 12/11/2014
• Est. Priority Date: 06/11/2013
• Status: Active Grant

• Current Assignee: Samsung Electronics Co. Ltd.
• Original Assignee: Samsung Electronics Co. Ltd.
• Inventors: JANG, Myeong Wuk, BAE, Young In, SEO, Seog Chung, LEE, Byoung Joon, HONG, Seong Ik
• Granted Patent: US 9,800,682 B2
• Time in Patent Office: Days
• US Class Current: 709/201
• 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

Provided is a node and a communication method of the node in a content oriented network (CON) in which the communication method of the node included in the CON may include receiving, at a receiver, a content request packet having a content name comprising hierarchical name components and flat name components, extracting the hierarchical name components and the flat name components from the content request packet, and processing the content request packet using the hierarchical name components and the flat name components.

Claims

1. A communication method of a node in a content oriented network (CON), the communication method comprising:

receiving, at a receiver, a content request packet having a content name comprising hierarchical name components and flat name components;

extracting the hierarchical name components and the flat name components from the content request packet; and

processing the content request packet using the hierarchical name components and the flat name components.

2. The communication method of claim 1, wherein the processing of the content request packet comprises verifying, using the flat name components, whether the content is stored in a content cache of the node.

3. The communication method of claim 2, further comprising:

determining whether an entry comprising the flat name components is included in a request management table of the node, in response to the content being absent in the content cache.

4. The communication method of claim 3, further comprising:

in response to the entry comprising the flat name components being included in the request management table, adding, to the entry, information associated with a route through which the content request packet is received.

5. The communication method of claim 2, further comprising:

in response to the content not being included in the content cache and the node not using a content request table,

determining whether an entry based on a prefix of the hierarchical name components is included in a forwarding table of the node.

6. The communication method of claim 3, further comprising:

in response to the entry including the same flat name components not being included in the request management table,

determining whether an entry based on a prefix of the hierarchical name components is included in a forwarding table of the node.

7. The communication method of claim 6, further comprising:

in response to the entry based on the prefix of the hierarchical name components being included in the forwarding table,

transmitting the content request packet using the hierarchical name components.

8. The communication method of claim 7, further comprising:

in response to the entry based on the prefix of the hierarchical name components being included in the forwarding table and the node using the request management table,

adding the entry based on the flat name components to the request management table.

9. The communication method of claim 1, wherein the hierarchical name components are used to forward the content request packet.

10. The communication method of claim 1, wherein the flat name components are used to identify the content.

11. A non-transitory computer-readable medium comprising a program for instructing a computer to perform the method of claim 1.

12. A node in a content oriented network (CON), the node comprising:

a receiver configured to receive a content request packet having a name of a content comprising hierarchical name components and flat name components;

an extractor configured to extract the hierarchical name components and the flat name components from the content request packet; and

a processor configured to process the content request packet using the hierarchical name components and the flat name components.

13. The node of claim 12, further comprising:

a content cache configured to store the content, and

wherein the processor is further configured to verify, using the flat name components, whether the content is stored in the content cache.

14. The node of claim 13, further comprising:

a request management table configured to index entries including the flat name components of the content, and

wherein the processor is further configured to determine whether an entry including the flat name components is included in the request management table, in response to the content being absent in the content cache.

15. The node of claim 14, wherein the processor is further configured to add, to the entry, information associated with a route through which the content request packet is received, in response to the entry comprising the flat name components being included in the request management table.

16. The node of claim 13, further comprising:

a forwarding table configured to index entries including the hierarchical name components,

wherein the processor is further configured to determine whether an entry based on a prefix of the hierarchical name components is included in the forwarding table, in response to the node not using a request management table.

17. The node of claim 14, further comprising:

a forwarding table configured to index entries including the hierarchical name components, and

wherein the processor is further configured to determine whether an entry based on a prefix of the hierarchical name components is included in the forwarding table, in response to the entry including the flat name components being absent in the request management table, or the node not using a content request table.

18. The node of claim 17, wherein the processor is further configured to transmit the content request packet using the hierarchical name components, in response to the entry based on the prefix of the hierarchical name components being included in the forwarding table.

19. The node of claim 18, wherein the processor is further configured to add the entry based on the flat name components to the request management table, in response to the entry based on the prefix of the hierarchical name components being included in the forwarding table and the node using a request management table.

20. The node of claim 12, wherein the hierarchical name components are used to forward the content request packet, and the flat name components are used to identify the content.