63 results about "Availability management" patented technology

Availability manager orchestration systems and methods and, particularly, an open resilience framework for simplified and coordinated orchestration of multiple availability managers.

Techniques are disclosed for determining, for each candidate communication medium, the availability of one or more telecommunications endpoint users for participating in a communication session of interest (i.e., either new or existing) via the evaluated medium. In accordance with the illustrative embodiment of the present invention, an availability manager determines the availability based on (i) one or more discrete rules, or (ii) one or more continuous functions, or both. The continuous functions are specified with respect to the time that has elapsed since a previous session, the time remaining in an active session, and the expected duration of a new session. Once it has determined the availability of one or more participants in the communication session, the availability manager of the illustrative embodiment transmits one or more signals to a call-processing server, which then sets up the participants on the session via the appropriate communication medium such as voice, instant messaging, and so forth.

A method and system that manage upgrades in a high-availability computer system by viewing the upgrade process as driving the system between a succession of stable configurations. The mechanism used by a described embodiment is an availability manager that is capable of ascertaining the state of each component and driving it toward a goal state by driving toward a succession of desired stable configurations. A high-level orchestration agent instructs the availability manager when a stable configuration has been reached and it is time to drive toward a next stable configuration.

The present invention provides a system and method whereby a user having the proper permissions to access a supply chain may check the availability of an item within the supply chain network. There are three different types of availability that can be checked: (1) current inventory availability, (2) available to promise inventory (projected+current inventory), and (3) capable to promise inventory (current inventory+projected inventory+capacity for manufacturing, labor, materials, and transportation). Preferably, the system is accessible over a distributed network such as the Internet, thereby facilitating remote access by allowing remote customers to receive a reliable commitment of delivery. The system further allows businesses to offer improved customer support in multiple commercial channels.

A method and apparatus for managing customer topologies on packet networks are disclosed. For example, the method creates at least two event correlation instances for at least one customer topology, where a first event correlation instance resides in a primary availability management server, and a second event correlation instance resides in a secondary availability management server. The method also creates a test node for the first event correlation instance, where the test node provides at least one test message. The method then receives at least one response generated by the first event correlation instance that is responsive to the at least one test message, where the at least one response is received by the second event correlation instance. The method then performs a fail-over to the second event correlation instance from the first event correlation instance if a failure is detected from the at least one response.

A hierarchical, distributed Availability Management (AM) process for recovering from component failures in a data processing system. The hierarchy of AM elements track a failure modality hierarchy of the data processing system components. For example, the system hierarchy may include system cards, processors, and processes, in which case the associated AM elements may be implemented at a card manager (CM) level, a system manager (SM) level, and a process manager (PM) level. The AM hierarchy is designed to achieve a failure granularity so that failures in the lower levels of the hierarchy have less of an impact on the entire system. Each AM element is responsible for receiving failure notifications from processing system components associated with a next lower level of the hierarchy. Upon such indication, if the AM element determines that the failed component may be restarted, if the failed component may be restarted, the AM element then determines if it can be hot, warm, or cold restarted and it does so without further notification or implication to system availability of other components. Hot restart requires complete integrity of sate information, warm restart causes a recovery of last known good state information, and a cold restart results in the re-initialization of state information. If, the component cannot be restarted, then notification is provided to the next higher level of the hierarchy and the AM element itself terminates. One of the AM processes may execute as an identity management protocol. The identity protocol sets a temporary master state; waits a predetermined amount of time; and then sets a final master state only if no other system card has asserted a temporary master state. The waiting time period is selected to be greater than the longest expected initialization process for peer components in the system.

Server cluster management includes dynamically migrating machines between different server pools within the server cluster. The server pools include an active pool and at least one standby pool. Different standby pools can also be maintained to provide machines in different states of standby, including but not limited to different powered down or hibernation states. Machines are migrated between the different server pools based on network demands and machine status and capabilities. In some instances, the network demands are determined by forecasting future demands. The status and capability of the individual machines is evaluated on a continual basis to determine whether there is adequate capacity of the machines in the active pool to satisfy the one or more network demands, as well as to determine which machine is the most appropriate machine to migrate between server pools. Machines can also be migrated between the different standby pools.

A service framework uses importance ranking information in making call decisions and/or wait-time decisions in connection with service requests. Each of the service requests has an importance ranking which reflects the importance of the information provided by the service to a task being performed. The health of a service may be controlled by permitting fewer (or more) service requests to be made to the service when the service is less (or more) healthy. The likelihood of a service request being made to the service may depend on the importance ranking of the service request. When waiting for a response, a determination whether to continue waiting may be made based on the likelihood that the service has failed and based on the importance of the information to the task being performed.

The invention relates to the field of management systems, in particular to an operation management platform. The system helps users to solve the problems of standardization and automation of the flow in the IT service support and management process, and improves the IT service level and operation work efficiency of enterprises. Meanwhile, in order to meet the requirement on IT operation management of the enterprises, the operation management flow is provided for the users, and ITIL-based post definitions, flow design tools, form design tools, ITIL-based flow templates and various element libraries are provided to help the enterprises to effectively and sequentially perform accident management, problem management, configuration management, change management and publication management during IT operation management work to fulfill the aim of service support and to provide service level management, availability management and capacity management to fulfill the aim of service delivery.

A method is disclosed for automating software availability management based on application program interface (API) versioning. The method includes receiving a call to a first version of an API method from a software application. The method includes retrieving software configuration information for the software application, the software configuration information including a set of supported versions of the API method. The method includes retrieving server configuration information for a server computing device, the server configuration information including a set of available versions of the API method. The method then includes determining availability of the server computing device to support the software application.

The invention discloses a multithread monitoring method and device. A global availability manager monitors running states of at least one local availability manager and subjects the local availability manager to a recovery operation after determining that the local availability manager runs abnormally; wherein the local availability manager is used for monitoring running states of serve threads registered on the local availability manager. Due to the fact that a two-stage monitoring structure that the global availability manager is used for monitoring the local availability managers and the local availability managers are used for monitoring a service thread is used, so that the service thread is monitored effectively, the situation that when the service thread and a monitoring thread are both abnormal and due to the fact that a system can not know the existence of the abnormal service thread, the system can not provide normal services normally is avoided, and accordingly the reliability of the system is improved.

The invention discloses a service operation management system (2000). The service operation management system (2000) is used for cloud computing-infrastructure, namely services. The system (2000) includes a service request management subsystem (2100), an event management subsystem (2200), a problem management subsystem (2300), a service level management subsystem (2400), a capacity management subsystem (2500), an availability management subsystem (2600) and a customer information management subsystem (2700). The service operation management system (2000) is characterized in that software resources, hardware resources, virtual resources and network sources are configured as user self-service and instant-consumption products; and distribution, operation and management, with customer remote operation adopted as a center, can be performed through the subsystems. With the service operation management system adopted, network flow and quality as well as use conditions of hardware equipment resources can be monitored, such that optimized and reasonable allocation of the resources can be realized, and early detection of operation events can be realized. The service operation management system of the invention is applicable to flexible management of cloud computing resources and customer data flow management and has a broad market prospect.

A distributed control protocol dynamically establishes high availability (HA) partner relationships for nodes in a cluster. A HA partner relationship may be established by copying (mirroring) information maintained in a non-volatile random access memory (NVRAM) of a node over a HA interconnect to the NVRAM of a partner node in the cluster. The distributed control protocol leverages a Cluster Liveliness and Availability Manager (CLAM) utility of a storage operating system executing on the nodes to rebalance NVRAM mirroring and alter HA partner relationships of the nodes in the cluster. The CLAM utility is configured to maintain various cluster related issues, such as CLAM quorum events, addition or subtraction of a node in the cluster and other changes in configuration of the cluster. Notably, the CLAM utility is an event based manager that implements the control protocol to keep the nodes informed of any cluster changes through event generation and propagation.

A device management apparatus includes processing circuitry. The processing circuitry is configured to issue management identification information for managing a device; generate mapping information in which the management identification information is associated with device identification information for identifying the individual device; and generate availability management information in which the device identification information is associated with availability indicating whether the device is available or unavailable. The processing circuitry generates the mapping information in which the management identification information associated with the device identification information of a first device is associated with the device identification information of a second device to be identified as the first device when generating, in response to a replacement request to replace the first device with the second device, the availability management information indicating that the first device is unavailable and the availability management information indicating that the second device is available.

The invention provides a resource orchestration entity (171) and a method (300), for enabling end-to-end service reliability and availability with service flow differential deployment of a network service with one or more service flows in a network service chain comprising one or more network function nodes (241, 242, 243), connected via a plurality of intermediate networking nodes. The resource orchestration entity (171) is arranged to: obtain an information element of service availability level (250) in at least one descriptor (223, 224, 226) for defining the service availability level requirements of the service flow from a network service management entity (220); and provide the information element of service availability level (250) together with an identification reference of the service flow, to a resource management entity (173), for assigning resources (151, 152, 153) comprising network function nodes (241, 242, 243) and their inter-connections in Virtual Network (153) layingon the Network hardware (163) comprising networking nodes, when instantiating a network service comprising service flows in the network service chain.

A method for managing availability of channel for adaptive layer service in asynchronous transmission mode includes adding an availability management unit of AAL2 channel in RNC and setting fault state flag and manual state flag on each AAL2 channel, detecting whether there is hardware fault or software fault on AAAL2 channel or not in real time by management unit, executing an unblocking operation and detecting state flag of AAL2 channel on set time when operation of device is stared, executing relevant blocking/unblocking operation and revising relevant state flag for lifting off fault AAL2 resource in system timely.

The present invention relates to a heterogeneous storage disaster recovery management system and a heterogeneous storage disaster recovery management method. The system comprises an application server and a storage server, wherein the storage server is used to store the bottom-layer heterogeneous resources and provide a storage interface to the application server, and the application server comprises a virtual machine, a physical platform, a virtual machine monitor used for virtualizing the physical platform and carrying out life-cycle management, resource management and availability management on the virtual machine. The virtual machine monitor also comprises an RAID1 management module used for realizing the processing of input and output request, the heterogeneous storage backup and the disaster recovery processing in the virtual machine monitor; a storage resource pool management module used for virtualizing the bottom-layer heterogeneous resources in the storage server and a local storage space in the application server into the unified storage resource pool, and providing the heterogeneous storage information to the RAID1 management module. The heterogeneous storage disaster recovery management system and the heterogeneous storage disaster recovery management method of the present invention can provide comprehensive and stable disaster recovery service for the heterogeneous storage management under a cloud computing environment.

Techniques are disclosed for determining, for each candidate communication medium, the availability of one or more telecommunications endpoint users for participating in a communication session of interest (i.e., either new or existing) via the evaluated medium. In accordance with the illustrative embodiment of the present invention, an availability manager determines the availability based on (i) one or more discrete rules, or (ii) one or more continuous functions, or both. The continuous functions are specified with respect to the time that has elapsed since a previous session, the time remaining in an active session, and the expected duration of a new session. Once it has determined the availability of one or more participants in the communication session, the availability manager of the illustrative embodiment transmits one or more signals to a call-processing server, which then sets up the participants on the session via the appropriate communication medium such as voice, instant messaging, and so forth.