Conference Server Failover via Command Replay
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Audio/video conference systems with non-redundant servers lack fault tolerance, leading to service loss upon server failure, and existing fault-tolerant solutions with redundant servers increase costs and reduce scalability.
Innovation Solution
Implementing a high-availability (HA) service module that provides fault tolerance using non-redundant conference servers by detecting failures and seamlessly transferring audio/video conference sessions to backup servers, allowing for cost-effective and scalable systems without modifying application logic or relying on third-party fault-tolerant arrangements.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If redundant conference servers are implemented to provide fault tolerance, then service reliability is improved, but system cost and complexity increase
Solution Approach 1:
An availability service module is introduced as an intermediary component that manages fault tolerance between the application server and conference servers. This module intercepts control messages, logs them, and coordinates failover operations, thereby providing reliability without requiring complex redundant server architectures. The intermediary handles the complexity of fault management centrally rather than distributing it across multiple servers.
Solution Approach 2:
Instead of duplicating entire conference servers with all their state and resources, the patent copies only the essential control messages and session information to a standby conference server. This selective copying approach provides fault tolerance by enabling rapid restoration of service without the overhead of maintaining full server redundancy, thus reducing system complexity while improving reliability.
2Reliability
If redundant conference servers are implemented to provide fault tolerance, then service reliability is improved, but scalability is reduced
Solution Approach 1:
The fault tolerance functionality is extracted from the conference server application logic and placed into a separate availability service module. This extraction allows the conference servers to remain simple, stateless processing units that can be easily scaled horizontally. The complexity of managing reliability is separated into a dedicated component that can operate independently, enabling the system to scale without being constrained by complex fault-tolerant server configurations.
3Reliability
If custom fault-tolerant designs are used, then service reliability is improved, but implementation complexity and cost increase
Solution Approach 1:
The system is segmented into distinct functional components: application servers that handle conference logic, conference servers that process media, and an availability service module that manages fault tolerance. This segmentation allows each component to be developed, deployed, and maintained independently using standard off-the-shelf technologies. The availability service module provides custom fault-tolerant behavior through standardized logging and message replay mechanisms, avoiding the need for custom-designed fault-tolerant conference servers.
Data Source
AI summary
Commands relating to a conference session being handled by a first conference server are logged, where the commands are exchanged between an application server and the first conference server. Failure of the first conference server is detected. In response to detecting the failure, the logged commands are used to transfer the conference session to a second conference server.