MCU Failure Detection and Rollover in Conference Systems
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current collaboration systems face delays and a drop-off in user experience when a collaboration server becomes unavailable, as the new server cannot recreate the exact virtual meeting environment, and maintaining redundant servers increases costs.
Innovation Solution
A conference system that detects MCU failures by sending and receiving 'heartbeat' messages, performs a rollover of conferences to another available MCU, and notifies clients of the change, allowing seamless reconnection and maintaining conference state information on a shared conference store.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If redundant servers are maintained to ensure high availability, then system reliability is improved, but operational costs increase
Solution Approach 1:
The patent implements virtualization to create virtual copies of server resources. Instead of maintaining physical redundant servers, the system creates virtual instances that can be rapidly deployed and migrated. Virtual machine snapshots and templates enable quick replication of server states without requiring duplicate physical hardware, thus improving availability while reducing the quantity of physical servers needed.
Solution Approach 2:
The patent employs resource pooling and virtualization to make server resources universal and multi-functional. A single physical server can host multiple virtual machines that serve different functions and can be dynamically allocated to different services. This consolidation reduces the total number of physical servers while maintaining the ability to provide redundant services through virtual instances.
2Speed
If collaboration server maintains all conferencing information locally, then data access speed is improved, but system reliability deteriorates when server becomes unavailable
Solution Approach 1:
The patent introduces a distributed storage dimension by implementing a clustered architecture where conferencing information is replicated across multiple servers. Instead of single-point local storage, data exists in multiple locations (primary server, backup servers, distributed file system), providing both fast local access and redundancy. The system maintains local caches for speed while implementing cross-server replication for reliability.
Solution Approach 2:
The patent implements a load balancer and session management intermediary that coordinates between multiple servers. This intermediary layer manages session state distribution, handles failover routing, and maintains a unified view of conferencing information across the cluster. It enables fast local access by directing requests to the appropriate server while ensuring reliability through automated failover to backup servers.
3Reliability
If client reconnects to a different collaboration server, then system availability is maintained, but user experience deteriorates due to loss of meeting state
Solution Approach 1:
The patent implements session state pre-synchronization and proactive replication. Before a failover occurs, the system continuously synchronizes meeting state information to backup servers and distributed storage. When connection failure is detected, the backup server already possesses the current meeting state, enabling immediate restoration without information loss. This preliminary preparation ensures both availability and state preservation.
Solution Approach 2:
The patent implements a session state validation and recovery feedback mechanism. Upon reconnection, the system automatically verifies meeting state integrity, detects any discrepancies, and initiates restoration procedures. The feedback loop continuously monitors session state across servers and triggers automated recovery actions, ensuring that users reconnect to a fully restored meeting environment without manual intervention or information loss.
Data Source
AI summary
A method, system, and architecture for detecting MCU failures is provided. The conference system detects the failure of MCUs that have been allocated to provide shared conference resources to conferences that are being hosted by the conference system. The conference system utilizes the sending and receiving of “heartbeat” messages between the MCUs and the conference server pool to detect failed MCUs. Upon detecting the failure of an MCU, the conference system performs a “rollover” of the conferences which were being serviced by the failed MCU to another available MCU. The conference system may then identify the clients which were connected to the failed MCU and notifies the clients that an MCU rollover has occurred and a new (replacement) MCU is available in order that these clients can reconnect and reestablish their media sessions.