Alcatel Lucent

Randee Susan Adams

Eric Jonathan Bauer

Daniel Weiler Eustace

Mark Michael Clougherty

Kedar S Namjoshi

Lyle Dean Kipp

Li Erran Li

Iraj Saniee

Yang Guo

Volker Hilt

William David Reents, Jr

William M Reents

Various exemplary embodiments relate to a method of preventing extreme coresidency hazards among application instances in a cloud network. The method includes determining a first failure group of a first instance of an application; establishing a connection with a second instance of a peer application; determining a second failure group of the second instance; comparing the first failure group to the second failure group; and establishing a second connection with a third instance of the peer application if the first failure group and the second failure group share a failure point.

Preventing extreme coresidency hazards in cloud computing

Various exemplary embodiments relate to a method and related network node including one or more of the following: identifying a hardware failure of a failed component of a plurality of hardware components; determining a set of agent devices currently configured to utilize the failed component; reconfiguring an agent device to utilize a working component of the plurality of hardware components. Various exemplary embodiments additionally or alternatively relate to a method and related network node including one or more of the following: projecting a failure date for the hardware module; determining whether the projected failure date is acceptable based on a target replacement date for the hardware module; if the projected failure date is not acceptable: selecting a parameter adjustment for a hardware component, wherein the parameter adjustment is selected to move the projected failure date closer to the target replacement date, and applying the parameter adjustment to the hardware component.

Hardware consumption architecture

A method and system for network element recovery are provided. In one form, frontend servers intelligently proxy error or unavailability messages returned by backend servers and simulate frontend server failure. In at least one form, the frontend server also includes intelligence or logic to determine that directing the client to recover service to an alternate system or site would assure better service availability, reliability, and/or quality-of-experience for the client.

Method and system for network element service recovery

A capability is provided for reducing response variance of virtual processors. A controller receives a processing request. The controller may propagate the processing request toward multiple virtual processors hosted on multiple hardware devices contemporaneously. The controller may propagate the processing request toward a first virtual processor hosted on a first hardware device and propagate the processing request toward a second virtual processor hosted on a second hardware device based on a determination that a timeout period expires before a processing response is received from the first virtual processor. The timeout period may be determined based on one or more response time statistics of the virtual processor and one or more response time statistics of a physical processor.

Reducing response time variance of virtual processors

A capability is provided for improving service availability experienced by a user requesting access to a service via a user device, where the service has multiple service instances available from multiple data centers. A set of servicing data centers is selected for the user device. The set of servicing data centers is selected from a set of candidate data centers. The set of servicing data centers is selected from the set of candidate data centers in a manner for maximizing the independence/orthogonality of the network paths between the user device and the servicing data centers. The set of servicing data centers includes two or more of the candidate data centers from which the user device may access the service, thereby providing the user device with a primary service instance and one or more backup service instances which may be used to access the service.

Apparatus and method for providing service availability to a user via selection of data centers for the user

Various embodiments provide a method and apparatus of providing a rapid disaster recovery preparation in cloud networks that proactively detects disaster events and rapidly allocates cloud resources. Rapid disaster recovery preparation may shorten the recovery time objective (RTO) by proactively growing capacity on the recovery application(s)/resource(s) before the surge of recovery traffic hits the recovery application(s)/resource(s). Furthermore, rapid disaster recovery preparation may shorten RTO by growing capacity more rapidly than during 'normal operation' where the capacity is increased by modest growth after the load has exceeded a utilization threshold for a period of time.

Method and apparatus for rapid disaster recovery preparation in a cloud network

Various exemplary embodiments relate to a method and related network node including one or more of the following: detecting, by a resource allocation device, a failure of server hardware; identifying a first agent device that is configured to utilize the server hardware; and taking at least one action to effect a reconfiguration of the first agent device in response to the server hardware failure. Various embodiments additionally include one or more of the following: identifying a second agent device that is configured to utilize the server hardware; and taking at least one action to effect a reconfiguration of the second agent device in response to the server hardware failure. Various embodiments additionally include one or more of the following: receiving, by the resource allocation device from a second agent device, an indication of the failure of server hardware, wherein the second agent device is different from the first agent device.

Hardware failure mitigation

Various exemplary embodiments relate to a method and related network node including one or more of the following: determining that a diagnostic test should be performed on a hardware component of a plurality of hardware components, wherein the plurality of hardware components support a plurality of agent devices and at least one agent device of the plurality of agent devices is assigned to at least one of the plurality of hardware components; ensuring that no agent device of the plurality of agent devices is assigned to the hardware component; and after ensuring that no agent device of the plurality of agent devices is assigned to the hardware component, performing the diagnostic test on the hardware component, wherein at least one other hardware component of the plurality of hardware components continues operation during performance of the diagnostic test.

Growing community of inventors

Naperville, IL, United States of America

Randee Susan Adams