Middleware Checkpoint Agent for State-Aware Application Availability

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current high availability middleware solutions require complex configurations and deep knowledge of SA Forum specifications, making it difficult for applications to manage state continuity and redundancy, and often rely on proxies that can fail, disrupting communication with applications.

Innovation Solution

A method and system for automatically configuring middleware to manage high availability by receiving user inputs specifying availability requirements, identifying a checkpoint agent with dual interfaces, and generating a middleware configuration that offers checkpoint services directly to applications, enabling state saving and retrieval without requiring applications to implement SA Forum APIs.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If applications implement SA Forum APIs to interact with HA middleware, then high availability management is achieved, but system complexity and difficulty of implementation increase

Engineering Contradiction:
Improvehigh availabilityVSAvoidconfiguration complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a service unit as an intermediary layer between the application and the HA middleware. This service unit implements the SA Forum APIs on behalf of the application, allowing the application to interact with the middleware without directly implementing the complex API requirements. The service unit acts as a mediator that handles the complexity of HA configuration and API implementation, while the application remains simple and focused on its core functionality.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If proxies are used to communicate with applications, then middleware can interact with applications, but communication reliability decreases due to potential proxy failures

Engineering Contradiction:
Improvemiddleware-application interactionVSAvoidcommunication reliability
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent extracts the proxy function from the communication path and eliminates it. Instead of using a separate proxy component to relay communications between the middleware and applications, the service unit is designed to be directly accessible by the middleware. This removes the additional failure point that a proxy would introduce, while still maintaining the ability of the middleware to interact with applications through the service unit's standardized interface.

Inventive Principle:
Principle #2Taking out (Extraction)

3Reliability

If complex AMF configuration is required to manage service availability, then high availability is achieved, but ease of deployment and operation deteriorates

Engineering Contradiction:
Improveservice availabilityVSAvoiddeployment ease
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent implements self-service mechanisms where the service unit automatically performs configuration and registration with the HA middleware without requiring manual intervention from system integrators. The service unit is designed to self-configure by discovering available services and automatically establishing the necessary connections and configurations with the middleware, thereby eliminating the need for complex manual AMF configuration while maintaining service availability.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS9292278B2Providing high availability for state-aware applications
Publication Date: 2016.03.22 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
  • US9292278B2 patent drawing
  • US9292278B2 patent drawing
  • US9292278B2 patent drawing

AI summary

A middleware that manages high availability of a software application is automatically configured when the software application is added to a system. The method of automatic configuration includes receiving a user input that specifies availability requirements and information of the software application, where the availability requirements include at least a checkpoint service that enables the software application to save and retrieve its state. The method also includes identifying a checkpoint agent for providing the checkpoint service to the software application. The checkpoint agent includes a first interface to the software application and a second interface, different from the first interface, to the middleware. A middleware configuration is generated that satisfies the availability requirements, based on the information of the software application such that the middleware offers the checkpoint service to the software application through the checkpoint agent and directly manages lifecycles of the software application.