Certains contenus de cette application ne sont pas disponibles pour le moment.
Si cette situation persiste, veuillez nous contacter àObservations et contact
1. (WO2017004508) RÉDUCTION DE LA LATENCE DE BOUT EN BOUT DANS UN SCÉNARIO HTTP SUR ICN
Note: Texte fondé sur des processus automatiques de reconnaissance optique de caractères. Seule la version PDF a une valeur juridique

CLAIMS

What is claimed is:

1. A method for use in a client network attachment point (cNAP) for enabling hypertext transfer protocol (HTTP) communication between an internet protocol (IP)-only device and an information-centric networking (ICN) device, the method comprising:

providing an IP network interface toward the IP-only device;

receiving an HTTP request;

encapsulating the received HTTP request into an ICN packet; and publishing the ICN packet as a named information item.

2. The method according to claim 1, wherein the named information item contains content data corresponding to the received HTTP request.

3. The method according to claim 1, further comprising:

subscribing to one or more named information items, wherein the one or more named information items comprise an information identifier representing an HTTP-exposed service that is exposed to the IP-only device.

4. The method according to claim 1, further comprising:

receiving a second ICN packet at the cNAP;

decapsulating the received second ICN packet; and

forwarding the second ICN packet to the IP-only device.

5. The method according to claim 1, further comprising:

sending the ICN packet to a border gateway (BGW) for transmission toward an IP network.

6. The method according to claim 5, wherein any HTTP request received at the BGW is forwarded to the IP-only device in a local ICN network to the BGW.

7. The method according to claim 1, wherein the named information item is an appropriately formed named information item.

8. A method for use in a server network attachment point (sNAP) for reducing rendezvous (RVZ) delay, the method comprising:

receiving a publication message including information from a client network attachment point (cNAP); and

locally performing an RVZ function in response to receiving the publication message.

9. The method of claim 8, wherein the information includes a node identifier that indicates node information suitable for a receiver of the response.

10. The method of claim 9, wherein the node identifier is assigned to the network attachment point during a bootstrap process of the sNAP or information-centric network (ICN).

11. The method of claim 9, wherein the node identifier is used to determine a suitable path for a response to the received request.

12. The method according to claim 11, wherein the path is provisioned by a topology management server while the sNAP forwards an hypertext transfer protocol (HTTP) request to a locally attached server.

13. The method according to claim 11, the method further comprising:

consulting a node/forwarding table comprising a path information entry corresponding to the node identifier, wherein the node/forwarding table is internal to the sNAP.

14. The method according to claim 13, wherein the node/forwarding table is managed in response to receiving the path information for particular node identifiers from a topology management server.

15. The method according to claim 14, wherein if an entry is found in the node/forwarding table, a request toward a topology management server is suppressed and the found path information is used.

16. The method according to claim 11, wherein the response is a single response sent to a plurality of clients.

17. The method according to claim 11, wherein a proxy-rule is employed wherein a determination of which HTTP requests may be served by a single multicast HTTP response is the same as the rule used in standard HTTP web proxies when locally replying to incoming HTTP requests with a cached HTTP response.

18. A method for use in a client network attachment point (cNAP) for enabling hypertext transfer protocol (HTTP) communication between an internet protocol (IP)-only device and a server device, the method comprising: providing an IP network interface toward the IP-only device;

receiving an indication of a forward path and an indication of a return path to a server network attachment point (sNAP);

encapsulating a received HTTP request into an ICN packet, wherein the ICN packet includes the HTTP request, the indication of the forward path, and the indication of the return path; and

publishing the ICN packet as a named information item.

19. The method according to claim 18, wherein the indication of the forward path and the indication of the return path are stored in a non-volatile memory component of the cNAP.

20. The method according to claim 18, wherein the indication of the return path is used to receive a response message.

21. The method according to claim 18, wherein the ICN packet is published to a forwarding node.

22. The method according to claim 21, wherein the forwarding node is a proxy server.

23. The method according to claim 22, wherein the proxy server checks a set cached field to determine if a matching response exists local to the proxy server.

24. The method according to claim 21, wherein the forwarding node employs a first-in first-out (FIFO) or last-recently-used (LRU) queuing mechanism.

25. The method according to claim 18, wherein the named information item is an appropriately formed named information item.