Abstract:
A method, operable in a framework wherein resources of a content provider may be delivered to clients from at least two distinct content delivery networks (CDNs). Responsive to a client request, one of the CDNs is selected, the selection being based at least in part on one or more policies set by the content provider. The client is provided with information associated with the selected CDN. The information may be a domain name such as a CNAME for the selected CDN. The policies may include a load share policy that specifies a relative load share for each CDN, and the selecting may attempt to satisfy the load share policy. Updated content provider policies may be obtained, at regular intervals.
Abstract:
Methods, devices and systems are disclosed for dynamically adjusting the load priority of a backup nameserver in a computer network based on the health and responsiveness of primary and backup nameservers.
Abstract:
An aspect of the disclosure is related to prioritizing users during a server failure. A client device or a central non-regional component detects that a server arbitrating a packet-based voice communication service in a first region has failed, and redirects the client device registered to utilize the packet-based voice communication service in the first region to a second server providing the packet-based voice communication service, wherein the redirecting is based on a priority level of a user of the client device. An aspect of the disclosure is related to peer-assisted failover recovery. A first client device detects that a server arbitrating a packet-based voice communication service in a first region has failed, and notifies a second client device in the first region that the server arbitrating the packet-based voice communication service in the first region has failed.
Abstract:
Example methods disclosed herein include, in response to receiving a first message associated with a first registration request for a device, determining whether the device is currently assigned to a first call processor and performing a load balancing procedure to reassign the device to one of a plurality of call processors including the first call processor, the load balancing procedure to bias reassignment to the first call processor in response to the device being determined to be currently assigned to the first call processor. Such example methods further include, in response to receiving a second message associated with a second registration request for the device, causing the first call processor to de-register the device in response to determining that the second message is associated with a pending reassignment of the device from the first call processor to a second call processor included in the plurality of call processors.
Abstract:
Various exemplary embodiments relate to a method performed by a Diameter Routing Agent (DRA) for processing a Diameter message, the method including: receiving a Diameter message at the DRA; evaluating an overload state of the DRA; evaluating a shedding rule based upon the overload state of the DRA; and shedding the received Diameter message based upon the evaluation of the shedding rule.
Abstract:
A redundant array of independent nodes are networked together. Each node executes an instance of an application that provides object-based storage. The nodes are grouped into a plurality of systems each having multiple nodes. The systems have one or more replication links each being formed to indicate replication of data from one system to another system in a replicated environment where each system is configured as a sub-domain in a Domain Name System (DNS) infrastructure. A DNS alias synchronization method comprises maintaining updated information, within each system, of all replication links involving that system and of DNS aliases of other systems associated with all replication links involving that system (S602-S607). This enables that system to process network-based requests, on behalf of the other systems, without redirecting the requests from the other systems to that system.
Abstract:
[Problem] A method by which a content-usage device connected to a network acquires a usable-service list from a server, and provides a service to a user on. the basis of the information shown on the service list, wherein it is not possible to change the services shown in response to conditions, and therefore the service does not conform to the user's needs and is not useful. [Solution] The present invention provides a content service system having a presentation-condition server device for transmitting presentation conditions for identifying a limited content list, the limited content list being a list of the part of the content, from a distributed content list, presented to the user on the content-usage device.
Abstract:
The present application is directed towards systems and methods for a user to configure the backup locations to use by an intermediary device providing Global Server Load Balancing (GSLB) services when a primary location is down. In some embodiments, when GSLB is based on static proximity of the location of the client to the GSLB sites and if the primary location is DOWN, then request may be load balanced among all the other locations. But this may not be desirable in many cases. So we need to provide option to the user to specify the preferred list of backup locations to service a client request. The present solution achieves this configurability by using a GSLB policy based on preferred location. One can configure preferred location(s) via a GSLB policy to redirect the client to preferred location(x). One can configure individual policies for different client locations. Based on implementation requirements, one can configure country level granularity, state level granularity and so on.
Abstract:
The present application is directed towards systems and methods for managing ownership of one or more SSL sessions. A cluster of nodes intermediary between at least one client server may maintain a succession list for at least one session of a first client from the at least one client. The succession list may include a list of nodes within the cluster and an order of succession for the nodes to transfer ownership of the at least one session. A first node of the cluster may enter an operational state for managing one or more sessions between the at least one client and the at least one server. A second node of the cluster may initiate, based on the succession list and responsive to the first node entering the operational state, a transfer of ownership of the at least one session from the second node to the first node.
Abstract:
An embodiment of this invention provides a new LDAP server control to automate load balancing for replication based directory infrastructure. This solution is applicable to both master-master and master-replica based replication topologies. If one or more of the replication servers or the master servers are available for processing, the request is assigned to them based on output of a weighted non-uniform random number generator. This LDAP server control allows gaining very high performance while doing multiple parallel heavy LDAP operations. This LDAP control prevents the exposure of the replication directory server details to the outer world and therefore proves helpful in easing the security concerns.