Cloud Communication Reconfiguration for Availability Zone Outages

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Software complexity and increased customer demands for flexibility and high availability in cloud environments lead to challenges in managing recovery reconfigurations when network connectivity or infrastructure failures occur, causing disruptions in service availability and performance.

Innovation Solution

Implementing a system that identifies outages in multiple availability zones of a cloud platform by selecting flags mapped to entities, determining affected entities, and initiating recovery procedures to reconfigure communication flows, using load balancers or central services to execute recovery plans and manage health status monitoring with red button agents.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual recovery procedures are used for cloud component outages, then service availability is maintained through human intervention, but response time increases and operational complexity rises

Engineering Contradiction:
Improveservice availabilityVSAvoidresponse time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by pre-configuring recovery procedures and automatically detecting outages through health checks and flag selections. When an outage is detected, the system immediately initiates recovery by reconfiguring communication flows to healthy zones without waiting for manual intervention, thus reducing response time while maintaining service availability.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If comprehensive monitoring and recovery systems are implemented across all cloud components, then service reliability is improved, but system complexity and maintenance overhead increase

Engineering Contradiction:
Improveservice reliabilityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system applies segmentation by dividing the cloud platform into discrete availability zones with independent health monitoring and recovery capabilities. Each zone can be monitored and recovered independently through flag-based identification, allowing comprehensive coverage without requiring centralized control of the entire system, thus managing complexity while improving reliability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system implements local quality by enabling targeted recovery operations at specific availability zones or components rather than requiring system-wide recovery. The flag selection mechanism allows operators to identify and recover only the affected components, reducing maintenance overhead while maintaining high service reliability through localized interventions.

Inventive Principle:
Principle #3Local quality

3Loss of time

If automated recovery procedures are implemented, then response time is reduced and service availability is maintained, but operational flexibility and control are diminished

Engineering Contradiction:
Improveresponse timeVSAvoidoperational flexibility
Core Design Contradiction:
Loss of timeVSAdaptability or versatility

Solution Approach 1:

The system incorporates feedback mechanisms that allow operators to monitor the health status of cloud components through flags and health checks. This feedback enables operators to maintain operational flexibility by selecting which components to recover and how, while the automated system responds promptly to initiate recovery procedures, thus balancing speed with control.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system implements dynamics by allowing the recovery process to adapt based on the selected flags and current system state. Operators can dynamically choose which availability zones or components to recover, and the system adjusts the recovery procedure accordingly, maintaining operational flexibility while ensuring rapid automated response to outages.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentEP4703890A1Reconfiguring communication for entities running on a multiple availability zone cloud platform
Publication Date: 2026.03.04 SAP SE
  • EP4703890A1 patent drawingFigure 1
  • EP4703890A1 patent drawingFigure 2
  • EP4703890A1 patent drawingFigure 3

AI summary

Methods, systems, and apparatus, including medium-encoded computer program products for recovery procedures on a multiple availability zone cloud platform include: identifying a selection of a flag from a set of flags defined at a cloud platform including multiple availability zones, wherein the flag is selected to identify an outage at a first zone of the cloud platform, and wherein each flag of the set of flags is mapped to an entity from a plurality of entities defined for the cloud platform; determining one or more entities from the plurality of entities defined for the cloud platform associated with recovering the outage based on identifying an entity corresponding to the selected flag; and in response to determining the one or more entities associated with recovering the outage, initiating a recovery procedure to reconfigure communication flows at the cloud platform associated with the determined one or more entities.