Abstract: A method and a first network access point (NAP) in an Information Centric Network (ICN) is disclosed. The first NAP is configured to receive a request for a Hypertext Transfer Protocol (HTTP) resource from a wireless transmit/receive unit (WTRU). The first NAP is configured to request the HTTP resource from a first server. The first NAP is configured to receive an error message. The error message may indicate that the HTTP resource is not available from the first server. The first NAP is configured to request the HTTP resource from a second NAP. The first NAP is configured to receive the HTTP resource from the second NAP. The first NAP is configured to send the HTTP resource to the WTRU.

Abstract: Employing proxy rule identifiers to ensure the integrity of content delivered over an HTTP-over-ICN system. An exemplary method is performed by a client-side network attachment point (cNAP) on an information-centric network (ICN). The cNAP receives an HTTP request that includes a resource identifier and at least one header field. The cNAP generates a proxy rule identifier (PRID) based on the header field(s) and a content identifier (CID) based on the resource identifier. The PRID may be generated by applying a hash function to a string that includes header field data. The cNAP sends an outgoing ICN message that includes the CID and the PRID. In response, the cNAP receives an incoming ICN message that includes an HTTP response, a PRID, and a CID. The cNAP and directs the HTTP response to the appropriate client(s) based on the PRID and CID.

Abstract: A first network access point (NAP) of an Information Centric Networking (ICN) network may receive a request for a HTTP resource from a requestor. The first NAP may request the HTTP resource from a first server associated with a fully qualified domain name (FQDN). The first NAP may receive an error message that the HTTP resource is not available. The first NAP may publish a message to a rendezvous point (RVZ) including a list of excluded node identifiers (NIDs) of one or more NAPs that have not provided the HTTP resource. The first NAP may receive a forwarding identifier (FID) of a second NAP associated with the FQDN with a NID not on the list of excluded NIDs from a topology manager (TM). The first NAP may request the HTTP resource from the second NAP. The first NAP may receive the HTTP resource is and send it to the requestor.

Abstract: A device may be configured to receive, process, forward, and/or respond to one or more resource queries. For example, the device may determine whether multiple queries are satisfied by a multicast response. The device may receive a first query and a second query directed to a resource, The first and the second query may comprise a structure proxy rule identifier (sPRID). The device may determine the similarity between the two queries. For example, the similarity determination may be based on the sPRID of the two queries. The device may determine whether a response that satisfies the first query also satisfies the second query, which may be based on a response to the first query and information comprised within the sPRID of the two queries. If the response satisfies both queries, the device may multicast the response.

Abstract: Systems and methods related to a multi-server pull-based HTTP request-response structure over ICN systems. In one embodiment, a method comprises: publishing an ICN content request from a cNAP with identification CIDURI; receiving at the cNAP a response from at least one sNAP indicating the availability of the requested content at the at least one sNAP; identifying at the cNAP an optimal segment number, k*, and a set I* of the server IDs, i*, to participate in a network coding based transmission; transmitting the optimal segment number k* from the cNAP to each sNAP identified in the set I*; receiving, at the cNAP, network coding based transmissions from the sNAPs identified in the set I*, and performing decoding of an overall message at the cNAP.

Abstract: An edge termination point (ETP) transport protocol between two or more ETPs in a network, such as a Layer 2 transport network, may be provided. A device may receive an incoming internet protocol (IP) transaction at an edge termination point (ETP) in a network. The device may terminate the received incoming IP transaction at the ETP. The device may map the terminated incoming IP transaction onto an ETP-to-ETP communication. The device may control the ETP-to-ETP communication. For example, the device may control the ETP-to-ETP communication based on a resource management regime. The device may map the ETP-to-ETP communication onto one or more outgoing IP transactions at the ETP. The device may map the IP transaction onto an ETP-ETP communication. The ETP-ETP communication may include one or more ETP flows and one or more ETP transactions.

Abstract: Some embodiments include systems, methods, and devices for enabling communication between at least two internet protocol (IP)-only wireless transmit/receive units (WTRUs), at least one of which is connected to an information centric network (ICN). The WTRU may send a generic attribute registration multicast registration protocol (GMRP) request on a local IP link to an information centric network (ICN) network attachment point (NAP). The NAP may receive and register the GMRP request with an internal data-base (DB) along with an IP multicast address entry matching the GMRP request. The WTRU may then send an IP multicast packet to the NAP for dissemination to an IP multicast group over an ICN by encapsulating the IP multicast packet in an ICN packet.

Abstract: A network access point (NAP) of a second type of network is configured to receive a first type of packet from a device configured to operate in only a first type of network. The NAP is configured to determine an appropriate namespace for the first type of packet based on an address of an intended destination of the first type of packet. The NAP is configured to encapsulate the first type of packet into a second type of packet for use in the second type of network. The NAP is configured to route the second type of packet to a plurality of devices subscribed to the namespace in the second type of network.

Abstract: A Network Access Point (NAP) in an ICN may have multiple clients requesting the same resource. Instead of sending multiple link-local unicast transmissions, the multiple clients may subscribe to a response bucket based on their unicast address and the NAP may send a multicast response to the group based on previously issued HTTP requests. The response bucket may contain multiple clients attached to the NAP. A multicast address of the response bucket may be used by the NAP to send the multicast response. A class D octet in the multicast group address may be derived from a class C octet of the individual client IP addresses.

Abstract: A delegation server may receive secure content from an origin server. The secure content may be pushed under a request-specific content handle comprising a unique mapping from a specific request to a specific response. The delegation server may receive name registration authority for a fully qualified domain name (FQDN) from the origin server and may register to the FQDN so that one or more Hypertext Transfer Protocol (HTTP) requests destined to the FQDN may be served by the delegation server. The delegation server may receive an HTTP request published to the FQDN by a client network access point (cNAP that includes the request-specific content handle calculated from a Hyper Text Transfer Protocol Secure (HTTPS) request from a client. The delegation server may send the secure content to the cNAP in an HTTP response. The secure content may be inserted into a HTTPS response towards the client.

Abstract: System and methods are described to register FQDN-based IP service endpoints at network attachment points. One embodiment takes the form of a method comprising: receiving, at a server-side network access point (sNAP) in an information-centric network (ICN), a registration request including a first fully qualified domain name (FQDN), a port, a transport protocol, and a service name of an IP server; publishing, at the sNAP, the port, the transport protocol, and the service name to a first content identifier (CID); and subscribing, at the sNAP, to a second CID that is based on the FQDN.

Abstract: Some embodiments include systems, methods, and devices for enabling communication between at least two internet protocol (IP)-only wireless transmit/receive units (WTRUs), at least one of which is connected to an information centric network (ICN). The WTRU may send a generic attribute registration multicast registration protocol (GMRP) request on a local IP link to an information centric network (ICN) network attachment point (NAP). The NAP may receive and register the GMRP request with an internal database (DB) along with an IP multicast address entry matching the GMRP request. The WTRU may then send an IP multicast packet to the NAP for dissemination to an IP multicast group over an ICN by encapsulating the IP multicast packet in an ICN packet.

Abstract: Systems, methods, and instrumentalities are disclosed for enhancing performance of multi-path communications. Multi-path communication performance may be enhanced by determining whether multipath communications share a congested router. A multi-path real-time communication protocol may provide techniques to prevent, detect, communicate and respond to a shared congested router. A shared congested router may be prevented, and/or detected using one or more detection techniques.

Abstract: A first network access point (NAP) of an Information Centric Networking (ICN) network may receive a request for a HTTP resource from a requestor. The first NAP may request the HTTP resource from a first server associated with a fully qualified domain name (FQDN). The first NAP may receive an error message that the HTTP resource is not available. The first NAP may publish a message to a rendezvous point (RVZ) including a list of excluded node identifiers (NIDs) of one or more NAPs that have not provided the HTTP resource. The first NAP may receive a forwarding identifier (FID) of a second NAP associated with the FQDN with a NID not on the list of excluded NIDs from a topology manager (TM). The first NAP may request the HTTP resource from the second NAP. The first NAP may receive the HTTP resource is and send it to the requestor.

Abstract: Procedures, methods and architectures for anchoring communication between devices configured to operate in a first type of network in a second type of network or across a peer first type of network are disclosed. A first type of packet originating from a device in the first type of network may be encapsulated into a second type of packet and forwarded via the second type of network.

Abstract: Systems, methods, and instrumentalities are disclosed for enhancing performance of multi-path communications. Multi-path communication performance may be enhanced by determining whether multi-path communications share a congested router. A multi-path real-time communication protocol may provide techniques to prevent, detect, communicate and respond to a shared congested router. A shared congested router may be prevented, and/or detected using one or more detection techniques.

Abstract: Employing proxy rule identifiers to ensure the integrity of content delivered over an HTTP-over-ICN system. An exemplary method is performed by a client-side network attachment point (cNAP) on an information-centric network (ICN). The cNAP receives an HTTP request that includes a resource identifier and at least one header field. The cNAP generates a proxy rule identifier (PRID) based on the header field(s) and a content identifier (CID) based on the resource identifier. The PRID may be generated by applying a hash function to a string that includes header field data. The cNAP sends an outgoing ICN message that includes the CID and the PRID. In response, the cNAP receives an incoming ICN message that includes an HTTP response, a PRID, and a CID. The cNAP and directs the HTTP response to the appropriate client(s) based on the PRID and CID.

Abstract: Systems and methods related to a multi-server pull-based HTTP request-response structure over ICN systems. In one embodiment, a method comprises: publishing an ICN content request from a cNAP with identification CIDURI; receiving at the cNAP a response from at least one sNAP indicating the availability of the requested content at the at least one sNAP; identifying at the cNAP an optimal segment number, k*, and a set I* of the server IDs, i*, to participate in a network coding based transmission; transmitting the optimal segment number k* from the cNAP to each sNAP identified in the set I*; receiving, at the cNAP, network coding based transmissions from the sNAPs identified in the set I*, and performing decoding of an overall message at the cNAP.

Abstract: Content owners, origin servers, and other entities may wish to use elastic service provisioning to provide users improved service. For example, an origin server may wish to offload processing/network load to a surrogate server such that users of a service may experience improved performance. As another example, a content owner may wish to have content distributed to a number of surrogate servers to lower latency and improve bandwidth.

Abstract: Procedures, methods and architectures for anchoring communication between devices configured to operate in a first type of network in a second type of network or across a peer first type of network are disclosed. A first type of packet originating from a device in the first type of network may be encapsulated into a second type of packet and forwarded via the second type of network.