Traffic Offload Node Cluster Service Disaster Recovery
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In the context of 5G mobile communication networks, the rapid growth of low-latency and high-bandwidth services poses challenges for service disaster recovery backup in local breakout scenarios, particularly due to the risk of anomalies in wireless traffic offload (TOF) functions disrupting local network data services.
Innovation Solution
A service disaster recovery backup method and system are proposed, utilizing a cluster of traffic offload (TOF) nodes. Each TOF node queries other nodes in the cluster for a service data abstract with its identifier as a keyword. If no activation node is found, the querying node acts as the activation node, selects a backup node, and publishes the service data abstract, enabling seamless service takeover in case of node failure.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a single TOF node is deployed for local breakout, then device complexity is reduced, but service reliability deteriorates due to the risk of node failure interrupting local network data services
Solution Approach 1:
The system segments the TOF function into multiple independent nodes forming a cluster, where each node can independently handle local breakout services. This segmentation allows the system to maintain service availability even when individual nodes fail, as other nodes in the cluster can continue to provide services.
Solution Approach 2:
The system performs preliminary actions by pre-configuring backup relationships between TOF nodes before any failure occurs. Each TOF node pre-identifies backup nodes and establishes data synchronization mechanisms in advance, enabling rapid service recovery when failures happen without requiring complex real-time decision-making.
2Reliability
If TOF nodes form a cluster with backup mechanisms, then service reliability is improved, but device complexity increases due to node coordination and data synchronization requirements
Solution Approach 1:
TOF nodes in the cluster autonomously manage their own backup relationships and data synchronization without requiring external coordination. Each node independently identifies its backup nodes, maintains data consistency, and performs failover operations when needed, eliminating the need for complex centralized cluster management mechanisms.
Solution Approach 2:
Each TOF node in the cluster is designed to be universal and multi-functional, capable of serving as an activation node for some services and a backup node for others simultaneously. This universality simplifies cluster management by allowing nodes to dynamically assume different roles based on service requirements rather than requiring specialized node types.
3Reliability
If service data is synchronized across multiple TOF nodes, then disaster recovery capability is improved, but data consistency management becomes more complex
Solution Approach 1:
The system uses data copying mechanisms where backup TOF nodes maintain copies of service data from activation nodes. This copying approach enables rapid failover by allowing backup nodes to immediately assume service continuity using pre-synchronized data copies, avoiding complex real-time data consistency protocols during failover events.
Solution Approach 2:
The system implements beforehand cushioning by pre-synchronizing service data to backup nodes before failures occur. This creates a data buffer or cushion that ensures service continuity is maintained even during the transition period after failure, as backup nodes already possess the necessary data to immediately resume services without requiring complex real-time data reconciliation.
Data Source
AI summary
Disclosed are a service disaster recovery backup method, a service disaster recovery backup system and a traffic offload (TOF) node. The service disaster recovery backup method includes: after joining a cluster of TOF nodes, querying each TOF node in the cluster for a service data abstract, a keyword in the service data abstract is an identifier of the first TOF node; when the service data abstract is not queried, undertaking, as an activation node, a local breakout service of service data of the first TOF node, selecting a second TOF node as a backup node in the cluster, and publishing the service data abstract with the identifier of the first TOF node as the keyword in the cluster.