Automated Failover Application for Network Data Traffic Rerouting

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In complex web service systems with multiple servers and redundant data sources, efficiently rerouting data traffic to address issues is cumbersome and time-consuming, requiring substantial manual effort and complex scripting, which slows down response times.

Innovation Solution

A computerized method involving a failover application that receives requests to reroute data traffic by selecting configuration data sets based on application identifiers, generating failover instructions using address masks, and providing them to a data traffic manager to automatically reroute data traffic between data sources.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual rerouting of data traffic is performed for each application, then data traffic can be routed to redundant data sources, but substantial effort and time are required from developers and engineers

Engineering Contradiction:
Improvedata access reliabilityVSAvoidresponse time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system enables self-service automated failover by implementing a failover application that automatically detects data source failures and reroutes traffic without requiring manual intervention from developers or engineers. The system uses configuration data sets with address masks to automatically identify and switch to redundant data sources, eliminating the need for human effort in routine failover operations.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system performs preliminary action by pre-configuring failover rules and address masks for multiple data sources before failures occur. Configuration data sets are prepared in advance with routing instructions for various applications, enabling immediate automated response when failures are detected without requiring real-time manual configuration decisions.

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If specific scripts are written and maintained for rerouting traffic of each application, then traffic can be rerouted according to specific configuration, but substantial effort is required to write and maintain these scripts

Engineering Contradiction:
Improveapplication-specific routing capabilityVSAvoidscript maintenance effort
Core Design Contradiction:
Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The system implements universality by creating a single failover application that can handle routing for multiple different applications through a unified configuration system. Instead of maintaining separate scripts for each application, the system uses a universal failover mechanism that reads application-specific configuration data sets and address masks to route traffic appropriately for any application in the system.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system introduces an intermediary configuration layer between applications and the failover mechanism. Configuration data sets with address masks serve as intermediaries that translate application-specific routing requirements into standardized failover instructions, eliminating the need for application-specific scripts while maintaining adaptability to different applications.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Productivity

If automated failover is implemented using configuration data sets and address masks, then rerouting effort is reduced and response time is improved, but system complexity increases

Engineering Contradiction:
Improvefailover operation efficiencyVSAvoidsystem architecture complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system manages complexity by changing parameters in a controlled manner - using address masks as configurable parameters that define routing behavior without requiring complex logic. The failover application changes routing parameters dynamically based on configuration data sets, enabling automated operations while keeping the core system architecture relatively simple and maintainable.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS10896094B2Automated failover of data traffic routes for network-based applications
Publication Date: 2021.01.19 MASTERCARD INT INC
  • US10896094B2 patent drawing
  • US10896094B2 patent drawing
  • US10896094B2 patent drawing

AI summary

The disclosure facilitates rerouting data traffic of applications. A failover request is received by a failover application including an application identifier of a main application, the failover application indicating at least one sub-application and a target data source. The failover application selects a configuration data set of the main application based on the application identifier, wherein the selected configuration data set defines an address mask of the target data source associated with the at least one sub-application. The failover application generates failover instructions for activating data traffic routing of the at least one sub-application to the target data source based on the address mask of the target data source. The failover application provides the generated failover instructions to a data traffic manager associated with the main application, whereby data traffic of the at least one sub-application is routed to the target data source by the data traffic manager.