Communication Channel State Sync for Seamless Cloud Failover

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing cloud service infrastructure (CSPI) systems face challenges in maintaining high availability of communication channels due to complex and time-consuming processes for setting up backup tunnels when primary endpoints fail, leading to potential disruptions and connection losses during failover events.

Innovation Solution

A method for synchronizing communication channel state information across multiple host machines, allowing traffic to be processed using the same communication channel to a backup endpoint, thereby avoiding the complexity of setting up new tunnels and minimizing connection disruptions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If backup tunnels are set up when primary endpoints fail, then service availability is improved, but setup time and complexity increase

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

Solution Approach 1:

The patent applies preliminary action by pre-establishing backup communication channels before primary endpoints fail. The system maintains synchronized state information across multiple host machines, allowing traffic to be immediately redirected to backup endpoints without negotiating new connections. This eliminates the time-consuming tunnel setup process that would otherwise occur after failure, while maintaining high service availability through pre-configured redundancy.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If backup communication channels are configured, then service continuity is improved, but system complexity increases

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

Solution Approach 1:

The patent merges the backup communication channel configuration into the existing communication infrastructure by using the same communication channel for both primary and backup endpoints. Instead of maintaining separate complex backup tunnel configurations, the system synchronizes state information across host machines, allowing seamless failover through state replication rather than through complex multi-channel management.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent uses copying by replicating communication channel state information from primary host machines to backup host machines. This allows the backup endpoint to assume the exact same communication state without requiring complex negotiation or configuration, simplifying the system while maintaining service continuity through state replication rather than complex channel management.

Inventive Principle:
Principle #26Copying

3Reliability

If new tunnels are negotiated during failover, then connection reliability is improved, but connection disruption time increases

Engineering Contradiction:
Improveconnection reliabilityVSAvoiddowntime
Core Design Contradiction:
ReliabilityVSDuration of action of moving object

Solution Approach 1:

The patent applies preliminary action by pre-synchronizing communication channel state information to backup host machines before failover occurs. This eliminates the need for time-consuming tunnel negotiation during failover, as the backup endpoint already possesses the necessary connection state. Traffic can be immediately redirected to the backup endpoint without interruption, achieving both high connection reliability and minimal downtime.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentEP4272413B1Synchronizing communication channel state information for high flow availability
Publication Date: 2025.11.19 ORACLE INT CORP
  • EP4272413B1 patent drawingFigure 1
  • EP4272413B1 patent drawingFigure 2
  • EP4272413B1 patent drawingFigure 3

AI summary

For a communication channel having a first endpoint in a customer on-premise network and a second endpoint on a primary host machine in a cloud service provider infrastructure, the primary host machine determines a change in a state information of the communication channel and identifies a backup host machine for the communication channel. The primary host machine causes the change in the state information to be replicated to the backup host machine, wherein the replicated state information stored by the backup host machine is usable by the backup host machine after a failover causes the backup host machine to become the second endpoint of the communication channel.