Inter-Carrier ENUM Apex Domain System for VoLTE Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current telecommunications systems face challenges in enabling seamless inter-carrier communications for VoLTE calls, particularly when private ENUMs do not return matching IP addresses for called devices on different carrier networks, leading to communication breakdowns.
Innovation Solution
The implementation of an inter-carrier ENUM apex domain system that uses IPX Tier 1 and Tier 2 ENUMs to query and convert NAPTR records from intra-carrier to inter-carrier formats, allowing for routing of VoLTE calls between carriers by modifying ENUM queries and using load balancing to optimize server usage.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If private ENUM queries are used for inter-carrier communication, then carrier-specific address resolution is achieved, but communication fails when called devices are on different carrier networks
Solution Approach 1:
The patent introduces a public ENUM database as an intermediary between carriers. When private ENUM queries fail to resolve addresses for devices on other carriers, the system automatically queries the public ENUM database which contains cross-carrier address mappings. This intermediary resolves the incompatibility between carrier-specific private ENUMs and inter-carrier communication needs.
Solution Approach 2:
The system implements a dual-query mechanism that first checks the private ENUM database for carrier-specific optimizations, then falls back to the public ENUM database for universal cross-carrier resolution. This multi-functionality ensures both carrier-specific reliability and broad network compatibility without requiring separate systems.
2Productivity
If multiple ENUM servers are deployed for load balancing, then system scalability is improved, but query routing complexity increases
Solution Approach 1:
The patent segments the ENUM server infrastructure into multiple independent servers that can be distributed across different locations. Each server handles a portion of the query load, and the system uses domain-based routing (e.g., different apex domains for different carriers) to distribute queries appropriately. This segmentation improves scalability while keeping individual server complexity manageable.
Solution Approach 2:
The system performs preliminary configuration of ENUM server mappings and load balancing rules before operation. Routing policies and server capabilities are pre-established, allowing queries to be distributed efficiently without real-time decision complexity. This preliminary setup enables scalable deployment with manageable operational complexity.
Data Source
AI summary
Aspects of the subject disclosure may include, for example, receiving, from a private telephone number mapping server, a first database comprising address records associated with subscriber devices of a first carrier, storing, at an inter-carrier server system, an inter-carrier mapping database comprising the address records converted to an inter-carrier format, receiving new address records associated with new subscriber devices registered with the first carrier, updating the inter-carrier mapping database with the address records converted to the inter-carrier format, receiving a first query for an address record associated with a called number of a first device of the first carrier for initiating an internet protocol call between the first device and a second device of the second carrier, querying the inter-carrier mapping database of the inter-carrier server system for the address record, and transmitting the address record to the second carrier for routing the internet protocol call. Other embodiments are disclosed.