Distributed Conference Bridge Conflict Resolution
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional methods for providing status updates in distributed systems, such as VoIP systems, face issues with network traffic overload and reliability due to the need for frequent status messages, and the central server method introduces a single point of failure.
Innovation Solution
A method that minimizes network traffic by circulating status messages between devices using a sequence and unique identifiers, and resolves conflicts between conference bridges by determining which bridge should provide a meeting resource using a hash function-based process, ensuring fair resource distribution and eliminating single points of failure.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If the broadcast method is used for status updates, then all devices receive current status information, but network traffic increases geometrically as N*(N-1) messages per update
Solution Approach 1:
The patent extracts the status update mechanism from the broadcast model to a selective model. Instead of every device broadcasting to every other device, only the device whose status has changed sends updates to specific devices that need that information. This extracts the essential function (status information delivery) while removing the harmful geometric growth of traffic.
Solution Approach 2:
The patent implements dynamic status update transmission where the sending and receiving of status messages is not fixed but adapts based on actual status changes and device needs. Devices dynamically determine whether to send or receive status updates based on current system state, transforming the static N*(N-1) broadcast pattern into a dynamic, demand-driven communication pattern.
2Loss of energy
If the central server method is used for status updates, then network traffic is reduced to 2*N messages per update, but the central server becomes a single point of failure
Solution Approach 1:
The patent segments the centralized status update function into distributed peer-to-peer updates. Instead of one central server handling all status information, the system divides the function across multiple devices, each maintaining and propagating their own status information. This segmentation eliminates the single point of failure while maintaining efficient traffic patterns.
Solution Approach 2:
The patent uses status data packets as intermediaries that carry status information between devices. These packets act as mediators that enable devices to exchange status information directly without requiring a central server, thus eliminating the single point of failure while maintaining organized and efficient information flow.
3Reliability
If extra resources are allocated for backup devices, then system reliability improves by eliminating single points of failure, but device complexity and resource requirements increase
Solution Approach 1:
The patent implements a self-service backup mechanism where devices automatically identify and assume backup roles for failed devices without requiring complex pre-configuration. When a device fails, other devices self-organize to provide backup services, eliminating the need for manually configured backup systems while maintaining high reliability.
Solution Approach 2:
The patent prepares backup capability in advance by having all devices capable of providing backup services and maintaining necessary configuration information. This preliminary preparation ensures that when a failure occurs, backup can immediately begin without complex real-time decision-making, simplifying the overall system while ensuring reliability.
4Loss of time
If configuration information is stored centrally or in all devices, then backup devices can quickly assume failed device functions, but memory requirements and device complexity increase
Solution Approach 1:
The patent applies local quality by having devices store configuration information locally only when needed for backup purposes. Instead of every device storing every configuration, each device stores configuration information locally only for the specific backup scenarios it may need, optimizing the balance between quick backup activation and memory usage.
Data Source
AI summary
A method for resolving conflicts between conference bridges in a distributed conferencing system includes determining that a conflict exists between a first conference bridge and a second conference bridge. The conflict may arise from the first conference bridge and the second conference bridge independently providing a meeting resource for a first meeting. The method also includes determining at the first conference bridge and at the second conference bridge that the meeting resource is to be provided by the first conference bridge. In determining that the meeting resource is to be provided by the first conference bridge, there is a probability of determining that the meeting resource is to be provided by the second conference bridge. The method also includes, providing the meeting resource for the first meeting at the first conference bridge and stopping providing the meeting resource for the first meeting at the second conference bridge.