BR112018077485B1 - METHOD PERFORMED BY A CLIENT-SIDE NETWORK CONNECTION POINT, AND CLIENT-SIDE NETWORK CONNECTION POINT - Google Patents

Abstract

This involves the use of proxy rule identifiers to ensure the integrity of content delivered to an HTTP system through ICN. An exemplary method is performed by a client-side network connection point (cNAP) in an information-centric network (ICN). cNAP receives an HTTP request that includes a resource identifier and at least one header field. cNAP generates a proxy rule identifier (PRID) based on the header field (or fields) and a content identifier (CID) based on the resource identifier. The PRID can be generated by applying a hash function to a string that includes header field data. cNAP sends an outbound ICN message that includes the CID and PRID. In response, cNAP receives an inbound ICN message that includes an HTTP response, a PRID, and a CID. cNAP directs the HTTP response to the appropriate client (or clients) based on the PRID and CID.

Description

CROSS REFERENCE TO RELATED DEPOSIT ORDERS

[001] The present application is a non-provisional filing of and claims the benefit set forth in title 35 of USC §119(e) of US provisional patent application serial no. 62/357,868, entitled "ENABLING HTTP CONTENT INTEGRITY FOR CO- INCIDENTAL MULTICAST DELIVERY IN SURROGATE-ENABLED INFORMATION-CENTRIC NETWORKS", filed on July 1, 2016, the entirety of which is incorporated herein by reference.

BACKGROUND

[002] Information Centric Networking (ICN) constitutes a new paradigm in which content is exchanged through information addressing, while connecting appropriate networked entities that are suitable to act as a source of information towards the networked entity that requested the content.

[003] Innovative architectures have been proposed in this space, requiring partial replacement of current network infrastructure to realize the desired network-level functions of these solutions. The migration scenarios envisage that the new proposed architectures can be realized as an overlay on existing architectures, for example, based on local IP or Ethernet. This migration, however, would still require transitioning the user equipment (UE) to an ICN-based solution. With IP-based applications providing a wide variety of internet services in use today, transitioning all of these applications can easily be seen as a much more difficult task than simply transitioning network-level functionality, e.g. of protocol stack, in the UE, as it also requires the transition of server-side components, for example, e-commerce web servers and the like. Therefore, it can be assumed that IP-based services, and with them purely IP-based UEs, will continue to exist for some time.

[004] The transition to ICN at the network level, on the other hand, promises many benefits, such as greater efficiency through the use of network caches and spatial/temporal decoupling of the sender/receiver, in general, the use of SDN updates to better flow management, etc.

[005] The disclosure "Methods and Systems for Anchoring Hypertext Transfer Protocol (HTTP) Level Services in an Information Centric Network (ICN)", presented in document WO2016123516A1, incorporated herein by reference in its entirety, describes systems and methods for providing data transfer services. HTTP level over an ICN network, the mapping of HTTP request and response methods into suitable ICN packets, published to suitable ICN names. Said mapping is performed at the Network Attachment Point (NAP) of the client and server, respectively, as well as at the ICN edge GW for cases of HTTP methods that are sent to and from of peering networks. With these methods, a growing portion of today's Internet-based service can be mapped onto ICN architectures.

[006] The disclosure "Elastic Service Provisioning via HTTP-level Surrogate Management", presented in US provisional patent application serial number 62/309,610, filed on March 17, 2016, incorporated herein by reference by reference, reveals a HTTP surrogate referring to HTTP-level service endpoints that act on behalf of and with the authority of an origin server. In RFC 3040, "Internet Web Replication & Caching Taxonomy", January 2001, a surrogate is a communications port co-located with a source server, or at a different point on the network, that is delegated the authority to operate on behalf of, and typically working in close cooperation with, one or more origin servers. Devices commonly known as "reverse proxies" and "(origin) server accelerators" are both considered more suitable as replacements. Surrogates can be deployed close to the origin server, close to the location, or across the entire network - a setup similar to a content delivery network (CDN). By placing the replacement servers in distributed network locations, the service can potentially be accessed with a much shorter path and greater accessible bandwidth without needing to contact the service at its origin servers. In addition to all the benefits of direct local content access, surrogates act on behalf of the origin server (and therefore the content owner) and give content owners greater control over their behavior than normal proxies, e.g. , edge caches, or traditional CDNs. As a result, they offer greater potential to improve performance by offloading processing/network load from the origin server with transparent user experiences. Surrogates work similarly to mirror servers in that a fully qualified copy of the entire website is stored; however, it is expected that the user will be able to access a fallback service using the same FQDN/URL rather than being redirected to different FQDN/URL as mirror servers are implemented. Unlike standard HTTP intermediaries, fallbacks offer finer-grained control by the origin server and content owner due to their implicit relationship.

[007] The reintroduction of multicast to clients that occurs to retrieve the same web resource at approximately the same time is based on the mechanisms described in document WO2016123516A1. As the entire network and transport layer is removed to exchange HTTP requests and their responses between one or more client NAPs (cNAPs) and a server NAP (sNAP), the mapping of an incoming HTTP response from a sNAP, delivered via coincident multicast, to multiple specific IP endpoints is an open question. Situations that have two IP clients requesting the same URL at approximately the same time have been described in WO2016123516A1. However, problems remain unresolved when the content in a web server's HTTP response differs depending on the specific information provided in the HTTP client's HTTP request header. For example, if a web client cannot read an HTTP response properly due to internal HTTP application issues, the client can issue an HTTP request for the same resource again, but using a "Range" HTTP header field requesting a specific range of bytes from the response only. Another type of header information is the HTTP request method type, with different request methods generally resulting in different HTTP responses (HTTP GET vs. HTTP PUT or PUSH).

[008] Additionally, there are certain techniques possible when programming a fully responsive web presence in which the web server provides specific MIME-tagged content at different quality levels depending on the client requesting the content. A range of available HTTP header fields are available, for example those described in RFC 4229, which can affect the content of an HTTP response.

SUMMARY

[009] The systems and methods disclosed in the present invention seek to address the integrity of HTTP content delivered on an HTTP system via ICN. In connection with the scenario in which additional information in an HTTP request header determines the content that a web server provides under a given response URL, the present disclosure addresses the integrity of content provided through coincident multicast and the formation of a corresponding selective broadcast group within sNAP. Furthermore, the present disclosure addresses the issue of providing collocated surrogates and their extended NAPs (eNAPs) with information about how to treat an HTTP message in a manner equivalent to the treatment of that message by the original competent server.

[0010] An exemplary method is performed by a client network attachment point (cNAP) in an information-centric network (ICN). cNAP receives an HTTP request from a client that includes a resource identifier and at least one header field. cNAP generates a proxy rule identifier (PRID) based on the header field (or fields), and generates a request content identifier (CID) based on in the resource identifier. cNAP sends an outbound ICN message that requests data. The message includes the request CID, request PRID, and a cNAP node identifier. In response to the outgoing ICN message, cNAP receives an incoming ICN message that includes an HTTP response, a received PRID, and a received CID. In response to a determination that the received PRID is the same as the request PRID and the received CID is the same as the request CID, cNAP provides the HTTP response to the client.

[0011] In some embodiments, proxy rules are provided to each cNAP that instruct the cNAP on how PRIDs should be generated from the header field (or fields). Some proxy rules are FQDN-specific rules that are applicable only to resources requested using specific FQDNs (fully qualified domain names). Other proxy rules are generic proxy rules that are applicable regardless of the FQDN. In some embodiments, proxy rules indicate how header data should be arranged in a data structure from which a PRID is determined. For example, a proxy rule can indicate how header data should be arranged in attribute-value pairs of a string, such as an XML data structure, and a hash function can be applied to the resulting string to generate a PRID.

[0012] In some embodiments, a method is performed by a client-side network connection point (cNAP) in an information-centric network (ICN). In such a method, cNAP receives an HTTP request from a client that includes a resource identifier and at least one header field. cNAP generates a proxy rule identifier (PRID) based on at least one header field, generates a content identifier (CID) based on the host identifier (FQDN), and generates a reverse content identifier (rCID) , from "reverse content identifier") based on the URL. cNAP maintains an rCID to PRID mapping that includes the communication identifier for how to reach the client. cNAP sends an outgoing ICN message that requests data, where the message includes the CID, the generated PRID, and a cNAP node identifier and the HTTP request. In response to the outgoing ICN message, cNAP receives an incoming ICN message that includes an HTTP response, a PRID, and an rCID. In response to a determination that the received rCID and PRID are the same as the request PRID and rCID, cNAP provides the HTTP response to the client using the stored communication identifier.

[0013] In some embodiments, a method is performed by a server-side network attachment point (sNAP) in an information-centric network (ICN). In such a method, sNAP receives an incoming ICN message that includes an HTTP request, a CID, an rCID, a PRID, and a NID. In response to the ICN message, sNAP creates a potential multicast group using the rCID and the PRID and NID as group members. sNAP sends the HTTP request to a suitable server using a pre-stored IP address and transport layer port identifier for that server. Upon receiving the HTTP response, sNAP obtains the potential multicast group, which is still open for new members based on the rCID and PRID information, and sNAP then closes the multicast group. sNAP subsequently publishes the HTTP response, rCID, and PRID to all members of the multicast group.

BRIEF DESCRIPTION OF THE DRAWINGS

[0014] A more detailed understanding can be obtained from the following description, presented by way of example in conjunction with the attached drawings, in which: Figure 1A shows an exemplary communications system, in which one or more embodiments disclosed can be implemented.

[0015] Figure 1B shows an exemplary wireless transmit/receive unit (WTRU) that can be used within the communications system of Figure 1A.

[0016] Figure 1C shows an exemplary radio access network (RAN) and an exemplary core network that can be used in the communications system of Figure 1A.

[0017] Figure 2 shows one embodiment of a system overview of the different types of NAP that may exist in a surrogate-enabled flexible routing system.

[0018] Figure 3 shows an embodiment of a namespace with scope identifiers for use with proxy rules.

[0019] Figure 4 shows a message sequence graph for one embodiment of distributing proxy rules from the primary sNAP to a cNAP or eNAP using the namespace shown in relation to Figure 3.

[0020] Figure 5 shows a message sequence graph for an embodiment of an eNAP that obtains proxy rules for the FQDN(s) it is to serve.

[0021] Figure 6 shows a message sequence graph for an embodiment of an sNAP that forwards updated proxy rules to all NAPs that previously retrieved rules for the specific FQDN.

[0022] Figure 7 shows a message sequence graph for one embodiment of an HTTP request and an HTTP response sequence between a client connected to a cNAP and a web server connected to an sNAP, which operates under rules of proxy.

DETAILED DESCRIPTION

[0023] A detailed description of illustrative embodiments will now be provided with reference to the various figures. Although this description provides detailed examples of possible implementations, it should be noted that the details provided are intended to be by way of example and in no way limit the scope of the application.

[0024] Note that various hardware elements of one or more of the described embodiments are called "modules" that perform (i.e., perform, perform, and the like) various functions that are described herein in conjunction with the respective modules. For use in the present invention, a module includes hardware (e.g., one or more processors, one or more microprocessors, one or more microcontrollers, one or more microcircuits, one or more application-specific integrated circuits (ASICs). specific integrated circuits"), one or more field programmable gate arrays (FPGA), one or more memory devices) deemed suitable by those skilled in the art relevant to a given implementation. Each described module may also include executable instructions for performing one or more functions described as being performed by the respective module, and it is noted that such instructions may take the form of or include hardware (i.e., wired) instructions, firmware, software instructions and/or similar, and may be stored on any computer-readable non-transitory medium or media, commonly called RAM, ROM, etc.

Exemplary network hardware.

[0025] Figure 1A is a diagram of an exemplary communications system 100 in which one or more disclosed embodiments can be implemented. The communications system 100 may be a multiple access system that provides content, such as voice, data, video, messaging, broadcasting, etc., to multiple wireless users. Communications system 100 may enable multiple wireless users to access such content by sharing system resources, including wireless bandwidth. For example, communications systems 100 may employ one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA - Frequency Division Multiple Access), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA - Single-Carrier Frequency Division Multiple Access) and similar.

[0026] As shown in Figure 1A, the communications system 100 may include wireless transmit/receive units (WTRUs) 102a, 102b, 102c, 102d, a radio access network (RAN). Access Network) 104, a core network 106, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, although it will be recognized that the disclosed embodiments contemplate any number of WTRUs, base stations, networks and/or network elements. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and/or communicate in a wireless environment. By way of example, the WTRUs 102a, 102b, 102c, 102d may be configured to transmit and/or receive wireless signals and may include user equipment (UE - User Equipment), a mobile station, a fixed or mobile subscriber unit, a pager, a cell phone, a personal digital assistant (PDA), a smartphone, a laptop-type computer, a netbook-type computer, a personal computer, a wireless sensor, consumer electronics, and the like.

[0027] The communications system 100 may also include a base station 114a and a base station 114b. Each of the base stations 114a, 114b may be any type of device configured to interface wirelessly with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as the main network 106 , the Internet 110 and/or the networks 112. By way of example, the base stations 114a, 114b may be a base transceiver station (BTS), a node B, an eNodeB, a source Node B , a source eNodeB, a location controller, an access point (AP - Access Point), a wireless router and the like. Although base stations 114a, 114b are each shown as a single element, it will be recognized that base stations 114a, 114b may include any number of interconnected base stations and/or network elements.

[0028] Base station 114a may be part of the RAN (Radio Access Network) 104, which may also include other base stations and/or network elements (not shown), such as a station controller -base (BSC - Base Station Controller), a radio network controller (RNC - Radio Network Controller), relay nodes, etc. Base station 114a and/or base station 114b may be configured to transmit and/or receive wireless signals within a specific geographic region, which may be called a cell (not shown). The cell can also be divided into cell sectors. For example, the cell associated with base station 114a may be divided into three sectors. Thus, in one embodiment, base station 114a may include three transceivers, for example, one for each sector of the cell. In another embodiment, the base station 114a may employ Multiple Input Multiple Output (MIMO) technology and, therefore, may utilize multiple transceivers for each sector of the cell.

[0029] Base stations 114a, 114b may communicate with one or more of WTRUs 102a, 102b, 102c, 102d via an air interface 116, which may be any wireless communication link (e.g., radio frequency (RF) ), microwaves, infrared (IR, "infrared"), ultraviolet (UV), visible light, etc.). The air interface 116 may be established using any suitable radio access technology (RAT).

[0030] More specifically, as indicated above, the communications system 100 may be a multiple access system and may employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and the like. For example, base station 114a in RAN 104 and WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS), universal terrestrial radio access (UTRA, for "Universal Terrestrial Radio Access") which can establish air interface 116 using wideband CDMA (WCDMA). WCDMA may include communication protocols such as High-Speed Packet Access (HSPA) and/or evolved HSPA (HSPA+). HSPA may include High-Speed Downlink Packet Access (HSDPA) and/or High-Speed Uplink Packet Access (HSUPA).

[0031] In another embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology, such as evolved UMTS radio terrestrial access (E-UTRA), which may establish the air interface 116 through the use of long term evolution (LTE) and/or LTE advanced (LTE-A).

[0032] In other embodiments, the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX) ), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile Communications (GSM - Global System for Mobile Communications), Enhanced Data Rates for GSM Evolution (EDGE - Enhanced Data Rates for GSM Evolution), GSM EDGE (GERAN) and similar.

[0033] The base station 114b in Figure 1A may be a wireless router, a source node B, a source eNodeB, or an access point, for example, and may utilize any RAT ("Radio Access Technology" - Radio Access Technology) suitable for facilitating wireless connectivity in a localized area such as a workplace, a home, a vehicle, a campus, and the like. In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology, such as IEEE 802.11, to establish a wireless local area network (WLAN). In another embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology, such as IEEE 802.15, to establish a wireless personal area network (WPAN). In yet another embodiment, the base station 114b and the WTRUs 102c, 102d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, etc.) to establish a picocell or a femtocell . As shown in Figure 1A, the base station 114b may have a direct connection to the Internet 110. Therefore, the base station 114b may not be necessary to access the Internet 110 through the main network 106.

[0034] The RAN 104 may be in communication with the core network 106, which may be any type of network configured to provide voice, data, applications and/or Voice Over Internet Protocol (VoIP) services to one or more of WTRUs 102a, 102b, 102c, 102d. For example, the core network 106 may provide call control, billing services, location-based mobile services, prepaid calling, Internet connectivity, video distribution, etc., and/or perform high-level security functions. , such as user authentication. Although not shown in Figure 1A, it will be recognized that RAN 104 and/or core network 106 may be in direct or indirect communication with other RANs employing the same RAT, such as RAN 104, or a different RAT. For example, in addition to being connected to RAN 104, which may utilize an E-UTRA radio technology, the core network 106 may also be in communication with another RAN (not shown) that employs a GSM radio technology.

[0035] The main network 106 can also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN ("Public Switched Telephone Network") 108, the Internet 110 and/or other networks 112. The PSTN 108 may include circuit-switched telephone networks that provide conventional telephone service (POTS - Plain Old Telephone Service). The Internet 110 may include a global system of computer networks and interconnected devices that use common communication protocols, such as Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and User Datagram Protocol (UDP). and the Internet Protocol (IP) in the TCP/IP suite of Internet protocols. Networks 112 may include wired or wireless communications networks owned and/or operated by other service providers. For example, networks 112 may include another core network connected to one or more RANs, which may employ the same RAT, such as RAN 104, or a different RAT.

[0036] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communications system 100 may include multi-mode capabilities, that is, the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with wireless networks. different wires over different wireless links. For example, the WTRU 102c shown in Figure 1A may be configured to communicate with the base station 114a, which may employ a cellular-based radio technology, and the base station 114b, which may employ a cellular-based radio technology. IEEE 802.

[0037] Figure 1B is a system diagram of an exemplary WTRU 102. As shown in Figure 1B, the WTRU 102 may include a processor 118, a transceiver 120, a transmit/receive element 122, a speaker/microphone 124, a key block 126, a monitor/touchpad 128, a memory no. removable memory 130, a removable memory 132, a power source 134, a global positioning system (GPS) electronic circuitry 136, and other peripherals 138. It will be recognized that the WTRU 102 may include any subcombination of the aforementioned elements while remaining consistent with a modality.

[0038] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP - Digital Signal Processor), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Array (FPGA) circuits, any other type of integrated circuit (IC). Integrated Circuit), a state machine and the like. The processor 118 may perform signal encoding, data processing, power control, input/output processing, and/or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit/receive element 122. Although Figure 1B depicts the processor 118 and the transceiver 120 as separate components, it will be recognized that the processor 118 and the transceiver 120 may be integrated together in an electronic package or electronic circuit.

[0039] The transmit/receive element 122 may be configured to transmit signals to, or receive signals from, a base station (e.g., base station 114a) via air interface 116. For example, in one embodiment, the transmit/receive element 122 may be an antenna configured to transmit and/or receive RF signals. In another embodiment, the transmit/receive element 122 may be an emitter/detector configured to transmit and/or receive IR, UV or visible light signals, for example. In yet another embodiment, the transmit/receive element 122 may be configured to transmit and receive both RF and light signals. It will be recognized that the transmit/receive element 122 may be configured to transmit and/or receive any combination of wireless signals.

[0040] Furthermore, although the transmit/receive element 122 is depicted in Figure 1B as a single element, the WTRU 102 may include any number of transmit/receive elements 122. More specifically, the WTRU 102 may employ MIMO technology . Thus, in one embodiment, the WTRU 102 may include two or more transmit/receive elements 122 (e.g., multiple antennas) to transmit and receive wireless signals over the air interface 116.

[0041] The transceiver 120 may be configured to modulate the signals that are to be transmitted by the transmit/receive element 122 and to demodulate the signals that are received by the transmit/receive element 122. As indicated above, the WTRU 102 may have capabilities in multiple mode. In this way, transceiver 120 may include multiple transceivers to enable WTRU 102 to communicate via multiple RATs, such as UTRA and IEEE 802.11, for example.

[0042] The processor 118 of the WTRU 102 may be coupled to the speaker/microphone 124, the keypad 126, and/or the monitor/touchpad 128 (e.g., a liquid crystal display (LCD) display unit. "Liquid Crystal Display") or an organic light-emitting diode (OLED) display unit, and may receive user input from the same. Processor 118 may also output user data to speaker/microphone 124, key pad 126, and/or monitor/touchpad 128. Additionally, processor 118 may access information from any suitable memory type, such as the non-removable memory 130 and/or removable memory 132, and storing data therein. The non-removable memory 130 may include a random access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital memory (SD) card, and the like. In other embodiments, the processor 118 may access information from memory that is not physically located in the WTRU 102, such as in a server or a home computer (not shown), and store data therein.

[0043] Processor 118 may receive power from power source 134 and may be configured to distribute and/or control power to other components in WTRU 102. Power source 134 may be any device suitable for powering WTRU 102. For example, the power source 134 may include one or more dry cell batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel-metal hydride (NiMH), lithium-ion (Li-Ion ), etc.), solar cells, fuel cells and the like.

[0044] Processor 118 may also be coupled to the electronic circuitry of GPS 136, which may be configured to provide location information (e.g., longitude and latitude) relative to the current location of WTRU 102. In addition to, or Instead of GPS electronic circuitry information 136, the WTRU 102 may receive location information via air interface 116 from a base station (e.g., base stations 114a, 114b) and/or determine its location with based on the timing of signals received from two or more nearby base stations. It will be recognized that the WTRU 102 can acquire location information through any suitable location determination method, while remaining compatible with one modality.

[0045] The processor 118 may also be coupled to other peripherals 138, which may include one or more software and/or hardware modules that provide additional features, functionality and/or wireless or wired connectivity. For example, peripherals 138 may include an accelerometer, an electronic compass, a satellite transceiver, a digital camera (for photographs or video), a Universal Serial Bus (USB) port, a vibration device, a television transceiver, a hands-free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser and similar.

[0046] Figure 1C is a system diagram of the RAN 104 and the core network 106 according to one embodiment. As indicated above, RAN 104 may employ an E-UTRA radio technology to communicate with WTRUs 102a, 102b, 102c via air interface 116. RAN 104 may also be in communication with core network 106.

[0047] RAN 104 may include eNodeBs 140a, 140b, 140c, although it should be recognized that RAN 104 may include any number of eNodeBs, while remaining consistent with one embodiment. The eNodeBs 140a, 140b, 140c may each include one or more transceivers to communicate with the WTRUs 102a, 102b, 102c via the air interface 116. In one embodiment, the eNodeBs 140a, 140b, 140c may implement MIMO technology . Thus, the eNodeB 140a, for example, may use multiple antennas to transmit and receive wireless signals from the WTRU 102a.

[0048] Each of the eNodeBs 140a, 140b, 140c may be associated with a specific cell (not shown) and may be configured to handle radio resource management decisions, auto-switch decisions, uplink user scheduling, and/or or downlink and similar. As shown in Figure 1C, eNodeBs 140a, 140b, 140c can communicate with each other via an X2 interface.

[0049] The core network 106 shown in Figure 1C may include a mobility management communication port (MME) 142, a server communication port 144, and a packet data network (PDN) communication port ) 146. Although each of the foregoing elements is shown as part of the core network 106, it will be recognized that any of these elements may be owned and/or operated by an entity other than the core network operator.

[0050] The MME 142 may be connected to each of the eNodeBs 140a, 140b, 140c in the RAN 104 via an S1 interface, and may serve as a control node. For example, the MME 142 may be responsible for user authentication of WTRUs 102a, 102b, 102c, bearer activation/deactivation, selection of a specific server communication port during an initial pinning of WTRUs 102a, 102b, 102c, and the like. . The MME 142 may also provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM or WCDMA.

[0051] The server communication port 144 may be connected to each of the eNodeBs 140a, 140b, 140c in the RAN 104 via the S1 interface. The serving communication port 144 may generally route and forward user data packets to/from the WTRUs 102a, 102b, 102c. The server communication port 144 may also perform other functions, such as anchoring user planes during automatic changes between eNodeBs, triggering paging when downlink data is available to the WTRUs 102a, 102b, 102c, managing and storing the contexts of the WTRUs 102a , 102b, 102c and similar.

[0052] The serving communications port 144 may also be connected to the PDN communications port 146, which may provide the WTRUs 102a, 102b, 102c with access to packet switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.

[0053] The core network 106 can facilitate communications with other networks. For example, the core network 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional terrestrial communications devices. For example, the backbone network 106 may include, or may communicate with, an IP communications port (e.g., an IP Multimedia Subsystem (IMS) server) that serves as an interface between the core network 106 and the PSTN network 108. Additionally, the core network 106 may provide the WTRUs 102a, 102b, 102c with access to other networks 112, which may include other wired or wireless networks that are owned or operated by others. service providers.

HTTP systems and methods through ICN.

[0054] The exemplary systems and methods disclosed in the present invention utilize an HTTP infrastructure through ICN, such as that described in document WO2016123516A1 in which network connection points (NAPs) provide standard IP connectivity to IP-enabled devices. NAPs then encapsulate incoming IP traffic into an appropriate ICN packet, which is then published under a structured named information item. Figure 2 shows one embodiment of a system overview of the different NAP types in a surrogate-enabled flexible routing system 200 with a Path Computation Element (PCE) 202 that combines the meeting (RV, for "rendezvous") of ICN network elements and the topology manager (TM, for "topology manager").

[0055] Server-side NAPs (sNAPs) 204 are NAPs that serve a specific FQDN by subscribing to the ICN CID/http/fqdn and have the ability to form coincidental multicast groups based on, for example, the methods described in document WO2016123516A1. Extended NAPs (eNAPs) 206 enable surrogates to be used as primary web servers. Extended NAPs provide an authorized mirror resource of the primary web server, which in some cases may be a fully virtualized resource environment. Client-side NAPs (cNAPs) 208 are NAPs that serve IP-only clients (e.g., client 210) and enable them to communicate with a web server (e.g., primary web server 212 or surrogate web server 214 ) through ICN 200 in a transparent way.

[0056] In the exemplary systems and methods disclosed in the present invention, each NAP behaves as a transparent HTTP proxy that terminates the TCP session for HTTP traffic toward its IP endpoints (e.g., client and server). The HTTP proxy (e.g. NAP) has the ability to additionally inspect the incoming HTTP message using two types of proxy rules, namely generic and FQDN-specific rules.

[0057] In some exemplary embodiments, generic proxy rules are required fields that the proxy (e.g., a NAP) needs to check, as otherwise the response is likely to be not what the HTTP client was requesting. and the integrity of the entire web resource request is at risk. For example, in such embodiments, the "Range" field or the HTTP request method in the HTTP request is taken into consideration when creating a multicast group in an sNAP, or otherwise the HTTP response from the associated web server to sNAP would not be accepted by the web client associated with a cNAP.

[0058] In exemplary embodiments, FQDN-specific rules are customizable rules that NAPs can take into account and that enable content providers to tune multicast creation to their needs. For example, audio/video/media content in HTTP responses may be encoded at a lower quality for mobile endpoints that the web server determines based on a "User Agent" field in the HTTP header. This behavior can be communicated to NAP by providing a precise FQDN-specific proxy rule.

[0059] In exemplary embodiments, proxy rule instances to be applied are generated in cNAPs when receiving the HTTP request from the UE (e.g., client 210). The same applies to HTTP responses received from a web server in sNAPs and eNAPs. Note that proxy rules are not tied to a specific HTTP/TCP session, making it possible for sNAP to create multicast groups using a single PRID that can be used by all cNAPs to map them back to their TCP sessions currently open. These proxy rule cases are represented as a unique identifier across all NAPs for identical HTTP sessions (same PRID). If sNAPs and eNAPs then provide HTTP responses via multicast, this proxy rule instance identifier serves as the single identifier used for all cNAPs to map them back to the clients that requested this response. Said proxy rule instance identifier is carried along with each HTTP request and HTTP response publication.

Populating generic and FQDN-specific proxy rules.

[0060] For all types of NAPs (client, server, and fallback/extended NAPs), as shown in Figure 2, FQDN-specific proxy rules are populated, and if a proxy rule update is available on the primary NAP , all cNAPs and eNAPs promptly update their existing rule (or rules).

[0061] In some embodiments, distribution of proxy rules is accomplished through a dedicated namespace that enables all NAPs to retrieve a FQDN-specific proxy rule from the primary server, while rules within that namespace names may be distributed through the underlying ICN's publish/subscribe network. The integrity of HTTP content delivery through the disclosed coincident multicast systems and methods described in WO2016123516A1 can be ensured with logic within NAPs and the transfer of a unique proxy rule identifier in each HTTP publication in the ICN network.

Proxy rules namespace.

[0062] To enable distribution of proxy rules from the primary NAP serving a specific FQDN, a dedicated namespace is revealed under the /management root scope identifier. Said root scope is shown here as a symbolic name and may be subject to agreement or standardization, represented as a specific identifier or numbered name in specific embodiments. Figure 3 shows one embodiment of the namespace with scope identifiers illustrated as white circles and information identifiers - under which data can be published - as shaded circles. Under the /management/proxyRules scope path, each FQDN is represented as an item of information with the value being a hash over the string representation of an FQDN, in one possible embodiment. This information item can be used to exchange first-time proxy rules between the primary sNAP and a NAP that has not received proxy rules for a specific FQDN, as well as updated proxy rules for a specific FQDN. Detailed operations on how the proposed proxy rules namespace is used can be found below.

[0063] It is understood that the namespace in Figure 3 may also utilize dedicated proxy rule items under each FQDN for initial and updated propagation by interpreting the FQDN as a scope and adding information items /initial and / update under each FQDN scope. In this case, the initial item can be used to communicate an initial set of rules whenever a NAP attempts to obtain such rules, while the update item can be used for future updates. Such an alternative namespace could, for example, be used for publish/subscribe systems that do not notify the addition of subscribers separately to the publisher, therefore requiring the suggested separation of transmitting the initial state separately from any updated state.

[0064] In the following disclosure, the operations and messages exchanged based on the name space of Figure 3 are presented for the sake of simplicity. However, it will be apparent to one skilled in the art that it is possible to modify the various embodiments discussed throughout the document to utilize alternative namespace and/or others as appropriate for specific scenarios.

Populating proxy rules for cNAPs.

[0065] An embodiment of the distribution of proxy rules from the primary sNAP to a cNAP or eNAP using the namespace shown in relation to Figure 3 is shown in Figure 4 using a message sequence graph (MSC, from " Message Sequence Chart"). The network elements shown in Figure 4 are an IP endpoint (client 422) that is served by a cNAP 424, a trajectory computing element (PCE) 426 that combines the rendezvous point (RV) of ICN elements, and a topology manager (TM), as well as an sNAP 428, as shown in Figure 2.

[0066] All mandatory generic proxy rules may be distributed prior to initialization of a NAP, for example, through a configuration file that accompanies each NAP deployment. The methods and their meanings behind the message flows enumerated in Figure 4 are described as follows.

[0067] In steps 401a and 401b, cNAP and sNAP respectively read their generic proxy rules independently of each other in their initialization phase, when reading the configuration file or when subscribing to the appropriate information item in the namespace .

[0068] In step 402, a new web server for the fully qualified domain name (FQDN) foo.com is registered with sNAP 428 using a specific registration interface. The registry interface can receive the related IP information on which sNAP can reach the computing entities to provide the requested resource such as a single fixed IP endpoint (web server) or a hypervisor that maintains and operates a server farm.

[0069] In step 403, the sNAP 428 receives FQDN-specific proxy rules provided by an external entity. These proxy rules may be provided by some management entity, e.g., operator or service provider, or directly through the FQDN provider (which may require awareness for the support of such rules for the FQDN service provider).

[0070] In step 404, sNAP 428 announces the availability of proxy rules for FQDNfoo.com under the path /management/proxyRules by hashing the FQDN and places the value as an information identifier under the said scope path.

[0071] This completes the initialization of the primary sNAP 428 and any cNAP 424 in the ICN network. The remaining message sequence in Figure 4 illustrates the retrieval of FQDN-specific proxy rules by a cNAP upon the arrival of an HTTP request for FQDN foo.com for the first time.

[0072] In step 405, an IP endpoint 422 served by cNAP 424 issues an HTTP request to foo.com/resource that cNAP receives through its transparent HTTP proxy functionality, which terminates the TCP session initiated by the client.

[0073] In step 406, upon arrival of each HTTP request, cNAP checks whether FQDN-specific proxy rules exist for the host from which a resource is requested. If cNAP cannot find any of these rules, it subscribes to the foo.com information item (for example, using a hashed FQDN) under the /management/proxyRules parent scope.

[0074] The PCE 426 corresponds to the cNAP 424 as a subscriber to the sNAP 428 as a publisher (see step 404) for the Content Identifier (CID) /management/proxyRules/foo.com. Accordingly, the PCE in step 407 issues an initial publish event to the sNAP for that specific CID.

[0075] In step 408, sNAP publishes the proxy rules received at 403 to cNAP using a predefined format, which is described in more detail below.

[0076] In step 409, cNAP updates its local proxy rules for foo.com and can continue its operations to publish the HTTP request to sNAP, as described below. This completes the operations on cNAPs and sNAPs in this example embodiment to retrieve generic and FQDN-specific proxy rules.

Populating proxy rules for eNAPs.

[0077] NAPs that enable an authorized copy of a primary web server in a different location within the ICN network (e.g., surrogates) are called extended NAPs (eNAPs). A message sequence graph for one embodiment of the procedures for eNAPs to obtain proxy rules for the FQDN (the FQDNs) they are supposed to serve is depicted in Figure 5. This illustration shows three network elements, namely, an eNAP 430 , a PCE 426, and the primary NAP (sNAP) 428 serving the foo.com FQDN.

[0078] In step 501, an external element triggers the activation of a specific IP endpoint as a surrogate in the eNAP 430. This activation command for the eNAP comprises, among other data, the FQDN that the eNAP is to serve. The operation of such activation and other eNAP functionality may be implemented as described in more detail in provisional application No. 62/309,610.

[0079] In step 502, following the same general procedure for cNAPs, the eNAP subscribes to CID/management/proxyRules/foo.com to receive the proxy rules from the primary sNAP.

[0080] In step 503, PCE informs sNAP that a new subscriber has become available under /management/proxyRules/foo.com. Note: Following the procedure described above in relation to Figure 3, the eNAP was subscribed to the previously mentioned CID to trigger a publish/subscribe match in the PCE.

[0081] In step 504, the sNAP publishes the proxy rules to the eNAP using a predefined format, an example of which is described below.

[0082] In step 505, eNAP updates its proxy rules for foo.com, which allows coinciding multicast groups to form without compromising the integrity of the HTTP content provided.

[0083] In step 506, eNAP subscribes to the information item foo.com under the root namespace identifier /http, enabling only IP clients to request web resources. This step can be carried out using techniques described in document No. WO2016123516A1. This completes the retrieval of FQDN-specific proxy rules from an eNAP in one embodiment of a surrogate activation in that exemplary embodiment. As noted above, the namespace can also utilize dedicated proxy rule items under each FQDN for initial and updated propagation by interpreting the FQDN as a scope and adding /initial and /update information items in each namespace scope. FQDN, thus accommodating publish/subscribe systems that do not notify the addition of subscribers separately to the publisher.

Update of operations in all NAPs.

[0084] In one embodiment, illustrated in Figure 6, an sNAP receives an update of FQDN-specific proxy rules and the information is forwarded to all NAPs that have retrieved these rules for the specific FQDN before. At the end of the initial retrieval of FQDN-specific proxy rules, cNAPs and eNAPs remain subscribed to the /management/proxyRules/foo.com CID as described above. Therefore, sNAP no longer needs to advertise the availability of information under /management/proxyRules/foo.com to be able to publish data to all subscribers.

[0085] In step 601, sNAP receives an update of the proxy rules for a specific foo.com FQDN. The format of the rules can be identical to the initial retrieval of the rules.

[0086] In step 602, the sNAP publishes the received FQDN-specific proxy rules to all NAPs subscribed to it, for example, cNAP 424 and eNAP 430, using CID/management/proxyRules/foo.com.

[0087] As noted above, a separate update information item may alternatively be used. In this case, cNAP and eNAP can subscribe to this dedicated update item after receiving the initial proxy rule as described previously.

[0088] This completes the exchange of messages in this exemplary embodiment between sNAP and client NAPs and extended to obtain updated FQDN-specific proxy rules.

Sample proxy rules format.

[0089] To describe proxy rules, one embodiment for storing and exchanging generic and FQDN-specific proxy rules is XML following the W3C DOM specifications for that specific file format. Alternative formats that enable structured information may be used in some embodiments. XML is an example that is widely used and supported. Other solutions include relational databases, for example SQL.

[0090] Proxy rules act on the existence of header fields in the HTTP request and their values. Header fields that are mandatory to ensure the correct HTTP response is released are provided within a rule element encapsulated in the generic markup element, for example in the following format.

[0091] <generic> <rule>Range</rule> <rule>HTTP</rule> </generic>

[0092] FQDN-specific proxy rules can be declared in an fqdn element with the actual FQDN as the attribute id. Within the fqdn element, both host and headerfields elements can be presented. Within headerfields, there can be a name element, and if the value of the header field is not to be used in every occurrence as a proxy rule, a value element allows the value to be used only with predefined values. Furthermore, it should be noted that each <name> entry is optional in the rule with several cases being possible using only several optional headerfields (see introductory example in partial requests). A specific embodiment of the format may be, but is not limited to, the following.

[0093] <fqdn id="foo.com"> <host>foo.com</host> <headerfields> <name>User-Agent</name> <value>Mozilla</value> </headerfields> </ fqdn>

[0094] Both FQDN-specific elements and generic elements are not limited to their number of occurrences, and if a rule is not found in the HTTP header, it can be ignored.

Operating on proxy rules.

[0095] The use of proxy rules allows multiple identical HTTP clients to be served by the same cNAP requesting the same content, while maintaining integrity. Figure 7 shows one embodiment of an exemplary message sequence between a client 422 connected to a cNAP 424 and a web server 432 connected to a sNAP 428, during an HTTP request/response sequence. It is assumed that the proxy rules have been populated according to the above methods and that the ICN network is fully operational. Additionally, the PCE communication used to enable HTTP publish/subscribe correspondences is not shown in Figure 7.

[0096] In step 701, the IP client 422 served by the cNAP 424 is issuing an HTTP request to retrieve http://foo.com/resource.

[0097] In step 702, cNAP parses the HTTP header and applies the generic and FQDN-specific proxy rules prior to this action to generate the proxy rule identifier (PRID). A PRID is a fingerprint for the combination of proxy rules and their values. In one embodiment, a PRID can be conceived as a concatenation of all header fields and their values that are provided as a string to a hash function. As the PRID is part of the packet that is sent to another NAP, any format that can be "encoded" as a unique stream of bit fields can be used.

[0098] In step 703, cNAP stores a mapping that identifies the requesting client 422 and the corresponding reverse CID (rCID) (/http/url) of the request and the PRID of the request. The identifier of the client waiting for the response can be, for example, an IP address together with the port or a socket file descriptor, or similar.

[0099] In step 704, cNAP publishes the HTTP request using CID /http/fqdn, /http/url as the rCID, and includes the PRID in the message, so that all three elements are received by sNAP. The cNAP may also include your node ID (NID).

[00100] In step 705, upon arrival of the message, the sNAP adds the cNAP (more precisely, its NID) to a list of nodes that are waiting for the response, as forming a coincident multicast group (CMC, from " coincidental multicast"). This group creation is based on an identical rCID and PRID.

[00101] In step 706, the HTTP request is sent to the web server 432 associated with the FQDN and the sNAP.

[00102] In step 707, web server 432 provides the requested web resource via an HTTP response that is received by sNAP 428.

[00103] The sNAP 428 has information indicating from which CMC group the HTTP request was sent. Using this information, in step 708, sNAP publishes the HTTP response to all NIDs that requested the web resource (e.g., the CMC group) and includes the PRID again. Therefore, there can be as many publish operations as there are different PRIDs for a given rCID.

[00104] In step 709, based on the mapping stored in step 703 (rCID, PRID, Clients), cNAP 424 identifies the IP endpoint or endpoints (e.g., clients) that expect this specific response.

[00105] In step 710, the HTTP response is sent to all clients with the same proxy rule fingerprint (PRID) that requested the same resource from the same FQDN.

[00106] In some embodiments, before publishing an HTTP request (step 704), cNAP 424 determines whether an HTTP request for the same FQDN, web resource, and PRID has already been published. If so, cNAP 424 may refuse to publish a duplicate HTTP request.

[00107] For example, avoiding sending unnecessary HTTP requests to the server (and therefore avoiding receiving unnecessary HTTP responses from the server in sNAP) can be accomplished as follows. Upon receiving an HTTP response from the server, after previously sending the appropriate HTTP request, sNAP checks the number of subscribers for the appropriate ICN name for the URL provided in the HTTP response (for example, ICN request message count Inbound HTTP to the same URL, subscribing to group size metadata information at a rendezvous point, etc.). sNAP sends the HTTP response, for example, according to the methods outlined in WO2016123516A1. In some embodiments, sNAP stores the PRID of said HTTP response in an internal table, along with the previously determined count. (In some embodiments, for example, where the PRID does not include the URL, the URL and PRID may be stored together as a pair.) sNAP receives incoming HTTP request messages from the ICN network and performs a check whether the corresponding PRID is equivalent to any PRID stored in its internal table. If the PRID is not found, the HTTP request message is handled according to the methods described in WO2016123516A1. If the PRID is found, i) the HTTP request message is suppressed, i.e. not sent to the server; ii) the count in the corresponding table entry is reduced by 1; iii) if the count has reached zero, the table entry is removed; iv) if the count has not yet reached zero, the modified count is stored in the appropriate table entry. The method is similarly performed on an ICN edge communication port in scenarios where the server resides in an IP peering network. In this case, the term "server" in the steps above is replaced by the term "IP peering network".

[00108] In additional embodiments, the disclosed systems and methods may incorporate a surrogate manager (or eNAP), as disclosed in provisional application No. 62/309,610, to enable provisioning of elastic services through intelligent activation and management of surrogate eNAPs based on dynamic statistics reported from the network and servers. For example, a surrogate manager can consider various metrics such as server state, server statistics, network statistics, etc., and determine an optimal or preferred eNAP, or primary sNAP, for responding to an HTTP request. In some embodiments, the namespace may be extended or otherwise modified to allow a surrogate manager to determine a scope path to be published for an HTTP request or other message (e.g., publish-level operation/ subscription, in some modalities integrated with the PCE). Consequently, the surrogate manager and/or the PCE can determine whether or not to direct a specific request from a cNAP to an eNAP that is currently "better" than the primary sNAP.

[00109] Although the features and elements are described above in specific combinations, one skilled in the art will understand that each feature or element can be used alone or in any combination with other features and elements. Furthermore, the methods of the present invention described herein may be implemented in a computer program, software, or firmware embodied in a computer-readable medium for execution by a computer or processor. Examples of computer-readable storage media include, but are not limited to, read-only memories (ROM), random access memories (RAM), registers, cache memories, semiconductor memory devices, magnetic media such as internal hard drives, and removable disks, magneto-optical media, and optical media such as CD-ROM disks and/or digital versatile discs (DVDs). A processor in association with software can be used to implement a radio frequency transceiver for use in a WTRU, UE, terminal, base station, RNC and/or any host computer.

Claims (20)

1. Method performed by a client-side network connection point (cNAP) in an information-centric network (ICN), the method being characterized by the fact that it comprises: receiving an HTTP request from a client, being that the HTTP request is associated with a fully qualified domain name (FQDN) of a host, and that the HTTP request includes a uniform resource locator (URL) and at least one header field; generate (i) a request proxy rule identifier (PRID) based on at least one header field, (ii) a request content identifier (CID) based on the FQDN, and (iii) a reverse content identifier request code (rCID) based on URL; sending an outgoing ICN message requesting data, wherein the outgoing ICN message comprises the request CID, the request PRID and the HTTP request; in response to the outgoing ICN message, receiving an incoming ICN message comprising an HTTP response, a received PRID and a received rCID; and in response to a determination that the received rCID and the received PRID are equal to the requesting rCID and the requesting PRID, respectively, providing the HTTP response to the client. 2. Method, according to claim 1, characterized by the fact that generating the request PRID comprises: identifying an FQDN-specific proxy rule corresponding to the FQDN; and generate the request PRID according to the identified FQDN specific proxy rule. 3. The method of claim 2, further comprising subscribing to a dedicated management namespace to receive FQDN-specific proxy rules associated with the FQDN. 4. The method of claim 3, wherein the subscription to receive the FQDN-specific proxy rules associated with the FQDN is performed in response to a determination that the cNAP has not yet received the FQDN-specific proxy rules. FQDN associated with the FQDN. 5. Method according to claim 1, characterized by the fact that the request PRID is generated using at least one generic proxy rule. 6. Method, according to claim 1, characterized by the fact that generating the request PRID comprises: generating a string comprising the at least one header field; and apply a hash function to the string. 7. Method, according to claim 6, characterized by the fact that generating the character string comprises arranging attributes and values of at least one header field in an XML structure. 8. The method of claim 1, wherein the output ICN message is a publication message. 9. Method, according to claim 1, characterized by the fact that it further comprises storing a mapping between (i) a client identifier and (ii) the request rCID and the request PRID; whereby the determination that the received PRID is equal to the request PRID and the received rCID is equal to the request rCID is made using the stored mapping. 10. Method according to claim 9, characterized by the fact that the customer identifier comprises an internet protocol (IP) address. 11. Method according to claim 1, characterized by the fact that the cNAP receives, from a plurality of clients, a plurality of HTTP requests from which a same request PRID, a same request CID and a same rCID are generated, and cNAP sends a single outgoing ICN message to the plurality of HTTP requests from which the same request PRID and the same request CID are generated. 12. Method according to claim 1, characterized by the fact that the client is an internet protocol (IP) client. 13. The method of claim 1, wherein the output ICN message further comprises a cNAP node identifier. 14. Customer Network Attachment Point (cNAP) over an Information Centric Network (ICN), wherein the cNAP is characterized by the fact that it comprises a processor and a non-transitory computer storage medium that stores operational instructions to perform functions comprising: receiving an HTTP request from a client, wherein the HTTP request is associated with a host's fully qualified domain name (FQDN), and wherein the HTTP request includes a uniform resource locator (URL ) and at least one header field; generate (i) a request proxy rule identifier (PRID) based on at least one header field, (ii) a request content identifier (CID) based on the FQDN, and (iii) a reverse content identifier request code (rCID) based on URL; sending an outgoing ICN message requesting data, wherein the outgoing ICN message comprises the request CID, the request PRID and the HTTP request; in response to the outgoing ICN message, receiving an incoming ICN message comprising an HTTP response, a received PRID and a received rCID; and in response to a determination that the received rCID and the received PRID are equal to the requesting rCID and the requesting PRID, respectively, providing the HTTP response to the client. 15. The client network connection point of claim 14, wherein the outgoing ICN message further comprises a cNAP node identifier. 16. The client network connection point of claim 14, wherein generating the request PRID comprises: identifying an FQDN-specific proxy rule corresponding to the FQDN; and generate the request PRID according to the identified FQDN specific proxy rule. 17. The client network connection point of claim 14, wherein generating the request PRID comprises: generating a string comprising the at least one header field; and apply a hash function to the string. 18. Client network connection point according to claim 14, characterized in that the functions further comprise receiving, from a plurality of clients, a plurality of HTTP requests from which a same request PRID, a single request CID and a single rCID are generated, and wherein cNAP sends a single outgoing ICN message to the plurality of HTTP requests from which a single request PRID and a single request CID are generated. 19. A method performed by a server-side network connection point (sNAP) in an information-centric network (ICN), the method characterized by the fact that it comprises: receiving a message including a node identifier (NID), a content identifier (CID), a proxy rule identifier (PRID), and an HTTP request, wherein the HTTP request includes a uniform resource locator (URL) and at least one header field, the PRID being based at least one header field; communicating the HTTP request to a network server associated with the CID; receiving an HTTP response from the web server, wherein the HTTP response includes a resource requested in the HTTP request; and publishing the HTTP response to the NID using a message that includes the PRID and a reverse content identifier (rCID) based on the URL. 20. The method of claim 19, wherein it comprises adding the NID to a coincident multicast group (CMC) associated with the PRID and the rCID, wherein publishing the HTTP response to the NID comprises publishing the HTTP response to a plurality of NIDs in the CMC group.