Content Delivery Network Failover via Control Node Flow Table Matching
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Content delivery networks face interruptions when a content node fails, leading to disruptions in content delivery to end users, as existing systems lack effective mechanisms to seamlessly transition communications to alternative nodes.
Innovation Solution
A method and system where a control node identifies service interruptions in content nodes and directs communications to alternative nodes using virtual next hop network addresses and a flow table, ensuring continuous content delivery by adding connection information and matching communications based on stored data.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Speed
If content nodes are grouped in physical locations to provide content to end users, then content delivery speed and accessibility are improved, but service interruptions and failures can cause content delivery disruptions
Solution Approach 1:
The system performs preliminary actions by pre-establishing backup content nodes and pre-configuring failover rules before failures occur. When a content node fails, the system can immediately switch to pre-designated backup nodes without requiring complex real-time decision-making, thus maintaining service continuity while preserving fast content delivery capability
Solution Approach 2:
The patent introduces a control node as an intermediary that manages the failover process between content nodes and end users. The control node receives communications, determines whether they include synchronization packets, and routes them to appropriate content nodes based on flow table information, thereby isolating failures and maintaining reliable content delivery
2Reliability
If a content node experiences service interruption, then content delivery to end users is disrupted, but implementing failover mechanisms increases system complexity
Solution Approach 1:
The system uses copying by maintaining flow table information that replicates connection state data across content nodes. When failover occurs, the backup content node can use copied flow table entries to immediately resume handling communications without requiring complex state synchronization, simplifying the failover mechanism while ensuring reliable content delivery
Solution Approach 2:
The patent applies parameter changes by modifying the state of content nodes from active to inactive and vice versa during failover events. The system changes parameters such as node status, communication routing paths, and flow table associations to enable seamless transitions, managing complexity through standardized parameter transformations rather than complex procedural logic
3Reliability
If communications are redirected to alternative content nodes during failures, then service continuity is maintained, but connection matching and synchronization increase processing overhead
Solution Approach 1:
The system applies partial action by performing synchronization only when necessary - specifically when communications include synchronization packets as indicated in flow table entries. For routine communications, the system uses existing flow table information without additional synchronization overhead, reducing energy consumption while maintaining service continuity during failover events
Data Source
AI summary
Described herein are methods, systems, and software for accommodating failover of a content node in a content delivery network. In one example, a method of operating a content node includes receiving a communication for an end user device from a control node, wherein an interrupted content node previously handled the communication. The method further includes determining if the communication includes a synchronization packet and identifying connection information for the communication. The method also provides, if the communication includes a synchronization packet, accepting the communication and handling delivery for the end user device. The method also includes, if the communication does not include the synchronization packet, determining if a match exists between the connection information for the communication and connection information stored in a flow table, and handling the communication based on the match.