A system designed for increasing network communication speed for users, while lowering network congestion for content owners and ISPs. The system employs network elements including an acceleration server, clients, agents, and peers, where communication requests generated by applications are intercepted by the client on the same machine. The IP address of the server in the communication request is transmitted to the acceleration server, which provides a list of agents to use for this IP address. The communication request is sent to the agents. One or more of the agents respond with a list of peers that have previously seen some or all of the content which is the response to this request (after checking whether this data is still valid). The client then downloads the data from these peers in parts and in parallel, thereby speeding up the Web transfer, releasing congestion from the Web by fetching the information from multiple sources, and relieving traffic from Web servers by offloading the data transfers from them to nearby peers.

A method for multi-layer quality of service (QoS) management in a distributed computing environment includes receiving a workload and identifying a workload QoS class for the workload. The workload is scheduled to be run compute nodes. The workload QoS class is translated to a plurality of different resource layer QoS classes, and the plurality of QoS classes are communicated to a workload execution manager of the compute nodes. The workload execution manager extends the plurality of different resource layer QoS classes to respective resource layers involved in the running of the workload.

A method for processing a super-hot file includes: receiving a download request for a target file sent by a user client, and adding, into the download request, a cache parameter for indicating whether the target file is a super-hot file; matching an identifier of the target file against a super-hot file identifier library, and determining, according to a matching result, whether the target file is a super-hot file; if the target file is a super-hot file, generating a random identification code, and updating the cache parameter to a cache parameter indicating that the target file is a super-hot file; and determining a download server to which the random identification code is mapped, and forwarding the download request including the updated cache parameter to the download server.

A system and method for diameter agent load balancing. The method including: receiving a request from a sending diameter node; parsing at least one Attribute-Value Pair (AVP) from the request; determining a partition-id from the at least one AVP; determining a receiving diameter node, based on the partition-id; and sending the request to the receiving diameter node. The system including: a message module configured to receive a request from a sending diameter node; a parsing module configured to parse at least one Attribute-Value Pair (AVP) of the message from the request and determine a partition-id from the at least one AVP and a receiving diameter node, based on the partition-id; and a forwarding module configured to send the request to the receiving diameter node.

Methods and systems for providing load balancing are provided. Example embodiments provide a Application Workspace System “AWS” which enables users to access remote server-based applications using the same interface that they use to access local applications, without needing to know where the application is being accessed. In one embodiment, a load balancing message bus is provided that performs load balancing and resource discovery within the AWS. For example, the AWS may use a broadcast message-bus based load balancing to determine which servers to use to launch remote application access requests or to perform session management. This abstract is provided to comply with rules requiring an abstract, and it is submitted with the intention that it will not be used to interpret or limit the scope or meaning of the claims.

In one example, a processing system of a mobile computing device including at least one processor may capture visual information of a first location, transmit a recognition request to a first server, the recognition request comprising the visual information, obtain a first recognition result from the first server comprising first annotation content associated with a first item in the visual information of the first location, the first recognition result further comprising visual information of the first item, present at least a portion of first annotation content via the mobile computing device, store the first annotation content and the visual information of the first item in a local cache, detect a first additional mobile computing device via a non-cellular wireless communication modality, and share the first annotation content and the visual information of the first item with the first additional mobile computing device via the non-cellular wireless communication modality.

A general load balancing value for a packet received by a network device is generated based at least in part on information in a header of the packet. The packet is directed to a network interface group comprising a set of network interfaces via which the packet can be transmitted towards a destination of the packet. A group-specific load balancing value for the packet is then determined based on group-specific load balancing configuration corresponding to the network interface group and is used to select a network interface, from among the set of network interfaces, and the packet is transmitted towards the destination of the packet via the selected network interface. The group-specific load balancing configuration corresponding to the network interface group is subsequently reconfigured to redistribute selection of network interfaces, among the set of network interfaces, for transmission of packets subsequently directed to the network interface group.

A method for distributed service management includes; running, by client nodes and service provider nodes, respective instances of a distributed service management unit, wherein the distributed service management unit comprises a distributed hash set table (DHST); providing, by the distributed service management unit, an application programming interface (API), wherein all connections between a client node and a service provider node are tunneled through the API; registering, by a service provider, a service on a network node; storing, by the registering network node, an endpoint of the service in a dataset of the DHST with a key corresponding to the service; requesting, by the client node, the service; and returning, by the distributed service management unit, all endpoints stored in the DHST with the key corresponding to the service.

A method for distributed service management includes; running, by client nodes and service provider nodes, respective instances of a distributed service management unit, wherein the distributed service management unit comprises a distributed hash set table (DHST); providing, by the distributed service management unit, an application programming interface (API), wherein all connections between a client node and a service provider node are tunneled through the API; registering, by a service provider, a service on a network node; storing, by the registering network node, an endpoint of the service in a dataset of the DHST with a key corresponding to the service; requesting, by the client node, the service; and returning, by the distributed service management unit, all endpoints stored in the DHST with the key corresponding to the service.

A string, identifying an item to be assigned to a physical resource, is hashed to obtain a numeric hash value. The numeric hash value is downscaled to obtain a bucket identifier that identifies a bucket that will hold the numeric hash value. The bucket is then deterministically mapped to a physical resource so that it can be retrieved without accessing a stored data structure representative of the mapping.