Distributed Component Model Architecture for SoIP Network Resilience
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional Session Border Controller (SBC) deployments in Session over Internet Protocol (SoIP) networks suffer from poor network resiliency and scalability, leading to inefficiencies in bandwidth use and increased complexity and cost due to dedicated point-to-point circuits and limited routing capabilities.
Innovation Solution
A Distributed Component Model Architecture (DCMA) system that includes multiple SBC clusters connected to Session Routing Engines (SREs), allowing for dynamic routing decisions, improved scalability, and enhanced resiliency by distributing routing information and call processing across multiple SREs, thereby reducing the burden on SBCs and enhancing network resilience.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional SBC deployments use single independent clusters with limited routing capabilities, then device complexity is reduced, but network resiliency deteriorates because a denial of service attack or malformed packets at one node can cause the entire cluster to fail
Solution Approach 1:
The patent segments the SBC functionality into distributed SBC clusters, where each cluster operates independently with its own routing capabilities. This segmentation ensures that a failure in one cluster does not propagate to other clusters, thereby improving network resiliency while maintaining manageable complexity through modular architecture
Solution Approach 2:
The patent introduces intermediary components including a distributed routing table and load balancers that mediate between multiple SBC clusters. These intermediaries enable clusters to work together while maintaining independence, allowing the system to achieve high resiliency without excessive complexity by managing inter-cluster communication through standardized interfaces
2Productivity
If conventional SBC deployments add new clusters to increase traffic capacity, then productivity is improved, but device complexity increases due to extensive provisioning and additional routing plans required for inter-cluster traffic
Solution Approach 1:
The patent implements a universal distributed routing table that serves all SBC clusters simultaneously. This single routing infrastructure provides multi-functionality by handling routing for all clusters in a standardized manner, eliminating the need for separate routing plans for each cluster and significantly reducing provisioning complexity when adding new clusters
Solution Approach 2:
The patent merges the routing functionality of multiple independent clusters into a unified distributed routing table. By combining routing resources across clusters, the system achieves improved traffic capacity while reducing overall complexity, as the shared routing infrastructure eliminates redundant routing configurations that would otherwise be required in each individual cluster
3Adaptability or versatility
If conventional SBCs store limited number of routes, then device complexity is minimized, but adaptability deteriorates when networks need to scale and add new routing destinations
Solution Approach 1:
The patent transitions from storing routes in a single-dimensional local memory of each SBC to a multi-dimensional distributed routing table spread across multiple clusters. This dimensional change allows the system to scale routing capacity by adding clusters rather than increasing individual SBC complexity, providing adaptability while keeping each node's complexity manageable
Data Source
AI summary
Methods, systems, and computer readable media for distributed component model architecture (DCMA) in a session over Internet protocol (SoIP) network is disclosed. According to one system, the system includes at least one session routing engine (SRE) for routing calls in an SoIP network. The system also includes at least one session border controller (SBC) for receiving, from a message source, a first message associated with a call in a SoIP network. The SBC is further configured for identifying a call source, wherein the call source is information, other than a calling party identifier, that identifies a source of the first message. The SBC is also configured for selecting one of the at least one SRE and sending to the selected SRE information associated with the message, the information including the call source. The SRE routes messages associated with the call according to a calling plan associated with the identified call source.