SIP Routing Rule Replication for Failover Reliability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional server-based systems face challenges in managing user-defined routing rules in primary/backup architectures, particularly in processing calls without degrading user experience when primary and/or backup clusters are down or experiencing network partitioning, requiring automated and seamless dissemination of routing rule changes.
Innovation Solution
User-defined routing rules are stored and published by a designated server, with changes synchronized through version comparison and batch exchange between the storing server and registrars, ensuring that each registrar determines necessary updates to maintain consistent routing without manual intervention.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If primary/backup relationships are established for user clustering, then system reliability is improved, but call processing complexity increases during failures and network partitioning
Solution Approach 1:
The patent pre-establishes backup registrar relationships and replicates routing rules to backup registrars before failures occur. When the primary registrar becomes unavailable, the backup registrar is already positioned and configured to immediately take over call processing, eliminating the need for complex real-time decision-making during failures.
Solution Approach 2:
The patent introduces a centralized routing rule repository that acts as an intermediary between registrars and users. This repository stores and manages routing rules, allowing registrars to retrieve rules without complex peer-to-peer coordination, thereby simplifying call processing during normal operation and failure scenarios.
2Measurement precision
If manual intervention is used to manage routing rules during failures, then control precision is improved, but operational time increases
Solution Approach 1:
The patent implements automated failover mechanisms where backup registrars automatically detect primary registrar failures and take over routing responsibilities without manual intervention. The system self-manages the transition by comparing routing rule versions and automatically synchronizing updates, eliminating operational delays while maintaining precise control through version comparison algorithms.
Solution Approach 2:
The patent establishes feedback loops where registrars continuously monitor the availability of primary registrars and automatically adjust their operational state. When failures are detected, the system receives feedback about the failure condition and automatically triggers failover procedures, ensuring rapid response without manual intervention while maintaining control through structured decision protocols.
3Stability of the object's composition
If routing rules are synchronized between primary and backup registrars, then consistency is improved, but data exchange overhead increases
Solution Approach 1:
The patent extracts only the essential routing rule data elements that need to be synchronized between registrars, rather than transmitting complete routing rule sets. By identifying and transmitting only the critical components needed for failover, the system maintains routing rule consistency while minimizing data exchange overhead and energy consumption.
Solution Approach 2:
The patent implements asymmetric synchronization where the primary registrar pushes routing rule updates to backup registrars, rather than maintaining bidirectional symmetric communication. This asymmetric approach reduces the overall data exchange overhead while ensuring consistency, as backups receive updates from the primary without needing to continuously query or synchronize back.
Data Source
AI summary
User defined routing rules are managed within a primary/backup architecture through continuous replication between home servers and their corresponding presence servers in an automatic manner. User set-up rules are stored and published by a designated presence server to home servers on which the user can register including the user's home registrar and any backup registrars. Changes to the rules may be disseminated and synchronized through comparison of versions and exchange of batches between the presence server and registrars.