A memory system having one or more memory components and a controller. The controller can receive access requests from a communication connection. The access requests can identify data items associated with the access requests, addresses of the data items, and contexts of the data items in which the data items are used for the access requests. The controller can identify separate memory regions for separate contexts respectively, determine placements of the data items in the separate memory regions based on the contexts of the data items, and determine a mapping between the addresses of the data items and memory locations that are within the separate memory regions corresponding to the contexts of the data items. The memory system stores the data items at the memory locations separated by different memory regions according to different contexts.

A memory system having one or more memory components and a controller. The controller can receive access requests from a communication connection. The access requests can identify data items associated with the access requests, addresses of the data items, and contexts of the data items in which the data items are used for the access requests. The controller can identify separate memory regions for separate contexts respectively, determine placements of the data items in the separate memory regions based on the contexts of the data items, and determine a mapping between the addresses of the data items and memory locations that are within the separate memory regions corresponding to the contexts of the data items. The memory system stores the data items at the memory locations separated by different memory regions according to different contexts.

An intermediary terminal for mediating a communication between a data generation device that generates target data, and a server that controls service content usable with the data generation device, includes circuitry configured to acquire, from the data generation device, device identification information identifying the data generation device; transmit the acquired device identification information to the server via a communication network; receive, from the server, service content information indicating a service content associated with the device identification information; and execute processing on the target data input from the data generation device in accordance with the service content indicated by the service content information.

Novel techniques are described for gateway routing and/or processing of multi-tenant Internet-of-Things (IoT) device data streams. For example, a single IoT routing gateway can be used to route device data streams from IoT devices of multiple customers according to rule-based routing tiers. The routing tiers define routing protocols, including which communication technologies to use for transmission of the device data streams over a cloud network to remote servers. In some cases, the routing tiers further define processing protocols to facilitate rule-based edge processing (and/or remote processing) of some or all device data streams. Some routing tiers can define a primary and one or more secondary solution for routing and/or processing, according to customer-defined rules. In some cases, the routing tiers further enable rule-based control of interconnectivity among IoT devices.

Techniques are disclosed for distributing data in a content delivery network configured to provide edge services using a plurality of service providers. Data indicative of data usage and cost data for the plurality of service providers is accessed. Based on the accessed data, an effective unit cost, multiplex efficiency, and channel utilization are determined for a selected user. A Bayesian optimization algorithm is applied to at least a portion of the accessed data. The content delivery network is configured to redistribute data traffic for the selected user based on a result of the applied Bayesian optimization algorithm.

Embodiments herein describe a CDN where anycast routing is used to identify a load balancer for selecting a cache in the CDN to use to deliver a requested object to a user. In one embodiment, the user performs a DNS lookup to identify an anycast IP address for a plurality of load balancers in the CDN. The user can then initiate anycast routing using the anycast IP address to automatically identify the closest load balancer. Once the identified balancer selects the cache, the load balancer can close the anycast connection with the user device and use an HTTP redirect to provide the user device with a unicast path to the selected cache. The user device can then establish a unicast connection with the cache to retrieve (e.g., stream) the object.

Techniques for using computer networking protocol extensions to route control-plane traffic and data-plane traffic associated with a common application are described herein. For instance, a traffic flow associated with an application may be established such that control-plane traffic is sent to a control-plane node associated with the application and data-plane traffic is sent to a data-plane node associated with the application. When a client device sends an authentication request to connect to the application, the control-plane node may send an indication of a hostname to be used by the client device to send data-plane traffic to the data-node. As such, when a packet including the hostname corresponding with the data-plane node is received, the packet may be forwarded to the data-plane node.

Techniques for using computer networking protocol extensions to route control-plane traffic and data-plane traffic associated with a common application are described herein. For instance, a traffic flow associated with an application may be established such that control-plane traffic is sent to a control-plane node associated with the application and data-plane traffic is sent to a data-plane node associated with the application. When a client device sends an authentication request to connect to the application, the control-plane node may send an indication of a hostname to be used by the client device to send data-plane traffic to the data-node. As such, when a packet including the hostname corresponding with the data-plane node is received, the packet may be forwarded to the data-plane node.

A system and method for publishing and updating policy rules in a network can be based on predictive algorithms and blockchain techniques for network systems (e.g. next generation emergency systems).

Various systems and methods for providing decentralized reputation management in a named-function network are described herein. A compute node is configured to access an information centric network (ICN) interest packet from a user device, the ICN interest packet including a function name and a data name; construct a named-function network (NFN) interest packet using the function name; transmit the NFN interest packet to a function provider; receive an NFN data packet with a version of a function corresponding to the function name; construct a named-data network (NDN) interest packet using the data name; receive an NDN data packet with a data value corresponding to the data name; determine that the version of the function is not on a denylist; and initiate execution of the version of the function with the data value in response to determining that the version of the function is not on the denylist.