Infrastructure Area Disaster Recovery via Dynamic Binding Unbinding

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing disaster recovery processing solutions for infrastructure areas lack flexibility and are difficult to implement in complex service clusters and architectures, making them ineffective in adjusting to faults within infrastructure areas.

Innovation Solution

A method and apparatus for disaster recovery processing that involves monitoring systems detecting faulty infrastructure areas and unbinding their identifiers from service requests, allowing traffic to be rerouted to unaffected infrastructure areas based on remaining binding relationships, facilitating quick recovery and damage mitigation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If existing disaster recovery processing solutions are implemented, then infrastructure area fault isolation is achieved, but flexibility and adaptability to complex service architectures are insufficient

Engineering Contradiction:
Improvefault isolation capabilityVSAvoidadaptability to complex service architectures
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent segments the disaster recovery mechanism into multiple independent binding relationships between service requests and infrastructure area identifiers. Each service request can be bound to multiple infrastructure areas, and each infrastructure area can serve multiple service requests, creating a many-to-many segmented structure that enhances both reliability and adaptability

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements dynamic binding relationships where the association between service requests and infrastructure area identifiers can be flexibly established, modified, and removed based on runtime conditions. The monitoring system dynamically detects faults and triggers unbinding operations, allowing the system to adapt to changing service architectures and fault conditions

Inventive Principle:
Principle #15Dynamics

2Reliability

If multiple IPs are bound to the same domain name for fault isolation, then initial stage disaster recovery is achieved, but flexibility for adjusting to faults in existing service clusters is limited

Engineering Contradiction:
Improvedisaster recovery capabilityVSAvoidease of adjusting to faults
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The monitoring system automatically detects faulty infrastructure areas and triggers the unbinding of service requests from affected infrastructure area identifiers without manual intervention. The system self-manages the disaster recovery process by automatically rerouting service requests to healthy infrastructure areas based on the pre-established binding relationships

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The binding relationship mechanism serves multiple functions: it establishes service request routing, enables fault detection, facilitates automatic disaster recovery, and supports flexible adaptation to different service architectures. This multi-functional approach eliminates the need for separate adjustment mechanisms for different fault scenarios

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

Data Source

PatentUS11362885B2Method, apparatus, device and readable medium for disaster recovery processing for infrastructure areas
Publication Date: 2022.06.14 BEIJING BAIDU NETCOM SCI & TECH CO LTD
  • US11362885B2 patent drawing
  • US11362885B2 patent drawing
  • US11362885B2 patent drawing

AI summary

A method, an apparatus, a device and a readable medium for disaster recovery processing for infrastructure areas which relate to the technical field of infrastructure area management are disclosed. The method includes: receiving a request for the service; under the condition that a monitoring system detects that there is an identifier of a faulty infrastructure area in identifiers of at least two infrastructure areas having a binding relationship with the request for the service, unbinding the binding relationship between the identifier of the faulty infrastructure area and the service; scheduling traffic for the request for the service to an unfaulty infrastructure area, according to a remaining unbound binding relationship between the service and the identifier of the unfaulty infrastructure area. According to the technical solutions, the damages may be stopped in time when the fault occurs in the infrastructure area.