Session Border Controller Host Name Redundancy
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Carrier-side application servers face configuration limitations that restrict the number of host names end devices can be mapped to, preventing customers from benefiting from geographic redundancy, leading to service rejection during network failures.
Innovation Solution
Implementing geographic redundancy by having geographically redundant network devices share a common host name or multiple host names, allowing session border controllers to rewrite domain headers and provision unique or shared host names to ensure seamless service continuity across alternate SBCs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of manufacture
If carrier-side application servers use access lists with single host name mappings, then configuration simplicity is maintained, but geographic redundancy capability is lost
Solution Approach 1:
The patent segments the host name mapping functionality by separating the access list configuration from the actual host name provisioning. The application server maintains a simplified access list that does not contain host names, while the session border controller handles the complex host name mapping and redirection logic. This segmentation allows the application server to remain simple while enabling geographic redundancy through the SBC's capability to rewrite domain headers with appropriate host names based on geographic location.
2Measurement precision
If session border controllers are assigned unique host names, then device identification accuracy is improved, but service continuity during network failures is disrupted
Solution Approach 1:
The patent introduces the session border controller as an intermediary between the application server and the end devices. The SBC receives requests with domain headers, rewrites them with the appropriate host name based on geographic location and failure conditions, and forwards them to the application server. This intermediary role allows the system to maintain accurate device identification while enabling seamless failover, as the SBC can transparently redirect traffic to alternate SBCs without the application server needing to know about multiple host names or failover logic.
3Device complexity
If access lists are configured with single host name mappings, then configuration complexity is reduced, but adaptability to network failures is compromised
Solution Approach 1:
The patent implements dynamic host name mapping where the SBC determines the appropriate host name based on real-time conditions such as geographic location and network failure status. Instead of static access list entries, the system dynamically rewrites domain headers with appropriate host names. This dynamic approach allows the system to adapt to network failures automatically while keeping the access list configuration simple and static, as the SBC handles all the dynamic decision-making.
Data Source
AI summary
A method including provisioning geographically redundant network devices with a shared host name or provisioning each of geographically redundant network devices with multiple host names in correspondence to each geographically redundant network device, wherein one of the multiple host names include a primary host name associated with one of the geographically redundant network devices and one or more secondary host names associated with the other geographically redundant network devices; receiving one or more packets; inspecting one or more headers associated with the one or more packets; determining a host name based on the one or more headers inspected; rewriting the one or more headers to include the shared host name or one of the multiple host names; and forwarding the one or more packets to another device.