GATEWAYS INTEGRATING NAME-BASED NETWORKS WITH HOST-BASED NETWORKS

• US 20120327931A1
• Filed: 06/21/2011
• Published: 12/27/2012
• Est. Priority Date: 06/21/2011
• Status: Abandoned Application

• Current Assignee: Alcatel-Lucent SA (Nokia Corporation)
• Original Assignee: Alcatel-Lucent USA, Inc. (Nokia Corporation)
• Inventors: Beck, Andre, Benno, Steven A., Hilt, Volker F., Varvello, Matteo, Esteban, Jario O., Rimac, Ivica
• Application Number:
  US13/165,243
• Publication Number:
  US 20120327931A1
• Time in Patent Office: Days
• US Class Current: 370/389
• CPC Class Codes: G06F 16/9566 URL specific, e.g. using aliases, detecting broken or misspelled links
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]

Abstract

A method of retrieving content from a network with a host-based network and a name-based network includes receiving, at a network node, a first message including at least one of a first host-based request and a first name-based interest, and transmitting, from the network node, a second message based on the at least one of the first host-based request and the first name-based interest.

Claims

1. A method of retrieving content from a network, the method comprising:

receiving, at a network node, a first message including at least one of a first host-based request and a first name-based interest; and

transmitting, from the network node, a second message based on the at least one of the first host-based request and the first name-based interest.

2. The method of claim 1, wherein the first message includes the first host-based request,

the first host-based request is received from a requesting node, and

the second message is different from the first message.

3. The method of claim 2, further comprising:

applying filtering rules to determine if a second name-based interest corresponding to the first host-based request will be transmitted to a name-based network; and

upon determining that the second name-based interest will be transmitted to a name-based network;

applying conversion rules to the first host-based request to determine the second name-based interest; and

assembling the second name-based interest, the second message including the second name-based interest,

wherein the transmitting a second message includes transmitting the second message to the name-based network.

4. The method of claim 3, further comprising:

receiving, at the network node, a name-based data message in response to the second message;

applying reverse conversion rules to the name-based data message to determine a host-based response;

assembling the host-based response based on the applying reverse conversion rules; and

transmitting the host-based response to the requesting node.

5. The method of claim 1, wherein the first message includes the first name-based interest,

the first name-based interest is received from a requesting node, and

the transmitting a second message includes transmitting the first name-based interest to a name-based network.

6. The method of claim 5, further comprising:

determining, by the network node, that a time period has elapsed without receiving a name-based data message from the name-based network;

applying reverse conversion rules to the name-based interest to determine a second host-based request;

assembling the second host-based request; and

transmitting the second host-based request to a host-based network.

7. The method of claim 6, further comprising:

receiving a host-based response to the host-based request;

applying conversion rules to the host-based response to determine a name-based data message;

assembling the name-based data message; and

transmitting the name-based data message to the requesting node.

8. The method of claim 3, further comprising:

transmitting a third message including the first host-based request to a host-based network.

9. The method of claim 8, further comprising:

receiving, at the network node, a name-based data message in response to the second message prior to receiving a first host-based response to the third message;

applying reverse conversion rules to the name-based data message to determine a second host-based response;

assembling the second host-based response based on the applying reverse conversion rules; and

transmitting the second host-based response from the network node.

10. The method of claim 5, further comprising:

applying reverse conversion rules to the first name-based interest to determine a second host-based request;

assembling the second host-based request; and

transmitting a third message including the second host-based request to a host-based network.

11. The method of claim 10, further comprising:

receiving, at the network node, a host-based response to the third message prior to receiving a first name-based data message in response to the second message;

applying conversion rules to the host-based response to determine a second name-based data message;

assembling the second name-based data message based on the applying conversion rules; and

transmitting the second name-based data message to a requesting node.

12. The method of claim 10, wherein the second host-based request is a byte-range request.

13. The method of claim 4, wherein the requesting node is a client.

14. The method of claim 2, further comprising:

applying filtering rules to determine if a second name-based interest corresponding to the first host-based request will be transmitted to a name-based network; and

upon determining that the second name-based interest will not be transmitted to the name based network;

forwarding the first host-based request to a host-based network;

receiving a host-based response to the first host-based request;

transmitting the host-based response from the network node to the requesting node; and

transmitting a copy of a data object included in the host-based response to the name-based network.

15. The method of claim 3, wherein the applying filtering rules includes using Regular Expressions.

16. The method of claim 3, wherein the applying conversion rules includes mapping the first host-based request to a unique name resolvable by the name-based network.

17. A network, comprising:

a network node configured to receive a name-based interests and host-based requests from a plurality of requesting nodes, to retrieve data from name-based and host-based networks in response to the interests and requests, and to transmit host-name responses and name-based data messages to the requesting nodes.

18. The network of claim 17, wherein the network node is configured to apply filtering rules in order to determine if one of the host-based requests will be at least one of transmitted to a host-based network and converted into a name-based interest and transmitted to a name-based network, and

the network node is configured to, upon determining that the one of the first-host based requests will be converted, to apply conversion rules and convert the one of the host-based requests into the name-based interest.

19. The network of claim 18, wherein the filtering rules are based on a subset of requests serviceable by the name-based network.

20. The network of claim 17, wherein the network node is a proxy server.