Abstract: An example device may determine a fully qualified domain name (FQDN) using a service operation, a producer identifier, and a parent domain, wherein the service operation is associated with a network function, and wherein the producer identifier identifies a producer device that provides the service operation; generate a target address using the FQDN and an event name, wherein the event name indicates a network function event: send a request message to the producer device using the target address, wherein the request message indicates a request to subscribe to the service operation for the network function event; receive a confirmation message from the producer device, wherein the confirmation message indicates that the device is subscribed to the service operation for the network function event; and receive an event message from the service operation provided by the producer device, wherein the event message indicates that the network function event has occurred.

Abstract: Procedures, methods, architectures, apparatuses, systems, devices, and computer program products directed to control throughput performance. In an embodiment, a service communication proxy (SCP) component comprises a programmable interface configured to transmit, to a wireless network element, a message comprising interface specification between a network function consumer and a network function producer.

Abstract: A method, implemented by a wireless transmit/receive unit, WTRU, includes receiving, a first message including information indicating a control plane procedure. According to the control plane procedure, a second message including a publish request is transmitted to a network node. Responsive to the publish request, a third message including information indicating a packet path routing indication is received from the network node. A fourth message, including uplink data, according to the packet path routing indication is transmitted to a data network.

Abstract: Methods, apparatus, systems, architectures, and interfaces for a path computation element (PCE) performing run-time operations for providing isolated service chains in a name-based routing system of communications network, are provided. A method may include any of: receiving, from a client device, a first message requesting a forwarding identifier (FID) associated with a fully qualified domain name (FQDN) of a service function (SF), the first message including information indicating: (1) a first identifier (ID) associated with the FQDN of the SF, and (2) a second ID associated with the FQDN of the SF; on condition that the PCE has determined that the first ID is for a subscriber associated with a namespace known to the PCE, determining the FID associated with the FQDN of the SF according to namespace information; and transmitting information associated with the FID to the client device.

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: Method, apparatus, and systems for transparent switching of service function identifiers in wireless communications are provided. In an example, a method for wireless communications comprises sending configuration information to one or more Service Function Endpoints (SFEs) using a programmable application programming interface (API), implementing the API as a programmable middleware, and registering each of the one or more SFEs with a respective identifier according to a service description at the programable middleware.

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: 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 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: 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: 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: 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: 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: 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: 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: 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.

Abstract: Procedures, methods and architectures for anchoring communication between IP-based devices in an ICN network or across an IP peer network are disclosed. Embodiments may enable the communication between two IP-based devices connected to an ICN, or one IP-based device connected to an ICN network while another IP-based device is connected either to an ICN network or IP network. In an embodiment, IP packets originating from an IP-based device may be encapsulated into ICN packets and forwarded via an ICN network. In an embodiment, IP packets received via an ICN network may be encapsulated in ICN packets and forwarded to an IP-based device. In an embodiment, IP packets originating from an IP-based device may be forwarded and received via an ICN network towards another IP network. In an embodiment, IP packets received by an ICN network may be forwarded towards an IP-based device via the ICN network.

Abstract: Procedures, methods and architectures for anchoring communication between IP-based devices in an ICN network or across an IP peer network are disclosed. Embodiments may enable the communication between two IP-based devices connected to an ICN, or one IP-based device connected to an ICN network while another IP-based device is connected either to an ICN network or IP network. In an embodiment, IP packets originating from an IP-based device may be encapsulated into ICN packets and forwarded via an ICN network. In an embodiment, IP packets received via an ICN network may be encapsulated in ICN packets and forwarded to an IP-based device. In an embodiment, IP packets originating from an IP-based device may be forwarded and received via an ICN network towards another IP network. In an embodiment, IP packets received by an ICN network may be forwarded towards an IP-based device via the ICN network.