Call Routing Controller for Resilient VoIP Session Permission
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing VoIP systems lack high availability and resiliency for voice over IP communications across geographically dispersed areas, leading to potential service outages due to node failures, especially in complex networks like the PSTN.
Innovation Solution
A call routing controller classifies calls as private or public network calls based on caller identifiers, using databases to determine routing messages for private network addresses or public network gateways, and manages concurrent call counts, ensuring efficient communication across multiple nodes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If a single node aggregates all information and traffic in the PSTN network, then call routing and processing can be simplified at that node, but the system becomes vulnerable to complete service outages if that single node fails
Solution Approach 1:
The patent divides the centralized PSTN node into multiple distributed VoIP nodes across different geographical locations. Each node maintains local route tables and can independently process call routing decisions, eliminating the single point of failure while distributing the processing function across multiple segments of the network.
Solution Approach 2:
The patent changes the operational parameters of the network by implementing multiple nodes with identical or mirrored route table data, allowing any node to take over routing functions if another fails. This parameter change from single-node to multi-node architecture resolves the contradiction between simplified processing and system reliability.
2Ease of manufacture
If VoIP services are provided to one location or a small number of locations, then network infrastructure requirements are reduced, but high availability and resiliency across geographically dispersed areas cannot be achieved
Solution Approach 1:
The patent segments the VoIP service delivery into multiple independent nodes distributed across different geographical locations. Each node can operate autonomously, providing service to local areas while contributing to overall network resiliency. This segmentation allows the system to achieve both deployment simplicity and geographical resiliency.
Solution Approach 2:
The patent extends the network architecture from a single-location model to a multi-dimensional distributed architecture. By adding the geographical dimension with nodes spread across multiple locations, the system achieves resiliency without significantly increasing deployment complexity, as each node follows the same standardized architecture.
3Productivity
If all network information is processed at a single PSTN node, then routing decisions can be made centrally, but no other nodes can take up the load if that node fails due to natural disasters
Solution Approach 1:
The patent implements preliminary action by pre-configuring multiple nodes with identical or mirrored route table information before any failure occurs. This allows any node to immediately take over routing functions if another node fails, eliminating the need for complex real-time reconfiguration and ensuring both routing efficiency and disaster recovery capability.
Solution Approach 2:
The patent introduces intermediary nodes that can mediate call routing when primary nodes fail. These nodes serve as backup intermediaries in the call path, maintaining routing efficiency while providing disaster recovery capability through their geographical distribution and redundant functionality.
Data Source
AI summary
A process and apparatus to facilitate communication between callers and callees in a system comprising a plurality of nodes with which callers and callees are associated is disclosed. In response to initiation of a call by a calling subscriber, a caller identifier and a callee identifier are received. Call classification criteria associated with the caller identifier are used to classify the call as a public network call or a private network call. A routing message identifying an address, on the private network, associated with the callee is produced when the call is classified as a private network call and a routing message identifying a gateway to the public network is produced when the call is classified as a public network call.