Method and system for anchoring hypertext transfer protocol (http) level services in an information centric network (icn)

Abstract

Methods and systems anchor Hypertext Transfer Protocol (HTTP) level communications in an Information Center Networking (ICN) network. Content requests and responses to servers within the ICN network and to servers located outside the ICN network (eg in IP networks) are disclosed. Communication can be between two IP-only capable devices at HTTP level, one connected to the ICN network and the other connected to the ICN or IP network. The disclosed namespace 200 enables IP-based HTTP communications within the ICN network. An Information Center Networking (ICN) Network Attachment Point (NAP) or Border Gateway (BGW) may receive HTTP request packets and encapsulate the received HTTP request packets. The ICN NAP / BGW can then forward the HTTP request packet to the local ICN network server. The HTTP request packet can be issued to a named content identifier (CID), which can be determined by a hash function on the qualified domain name (FQDN). The ICN NAP may receive an HTTP response packet for subscribing to an information item, which may be included in the named rCID. The named rCID can be determined by a hash function of a Uniform Resource Locator (URL). Instead of directly using the URL and the hash of the FQDN, a separate scope identifier (which may be the root identifier) ​​can also be chosen for HTTP communication over the ICN of the overall ICN namespace. The scope identifier contains specific structures for the ICN namespace being constructed. The use of root identifiers may allow separation of HTTP communications on ICNs from communications to other ICNs, for example for operational or migration reasons. Under the root scope identifier, there may be two subscope identifiers, a first subscope identifier (I) for communications within the ICN network and a second subscope identifier for communications to IP addresses outside the ICN network symbol (O). This ICN can be based on the PURSUIT publish-subscribe architecture or on the Named Data Networking (NDN) project, etc.

Description

[0001] Cross-references to related applications [0002] This application claims the benefit of U.S. Provisional Application Serial No. 62 / 110,210, filed January 30, 2015, the contents of which are incorporated herein by reference. Background technique [0003] Information-centric networking (ICN) enables new networking paradigms where content is exchanged by way of message addressing. Different architectures may be used to implement ICN, which may require partial replacement of current network infrastructure and equipment (eg, routers, gateways, etc.) to achieve the desired network-level functionality of these schemes. ICN can provide improvements to current networking including, for example, better performance, multicast support, in-network caching, and the like. [0004] The scenario of migrating from the current network architecture to ICN foresees that the new architecture can be implemented as an overlay on top of an existing architecture, such as an Internet Protocol (...

AI Technical Summary

Problems solved by technology

In addition to being difficult to modify the application, modifications to the Integrated Development Environment (IDE), Software Development Kit (SDK), etc. may also be required and difficult

Images