Enhanced Gateway Routing for IMS Messaging Traffic
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current IMS networks face inefficiencies in routing messaging traffic, often requiring multiple network elements and leading to overloads, which increases costs and maintenance issues due to the lack of direct routing mechanisms for messaging applications.
Innovation Solution
The implementation of an enhanced gateway function that uses a telephone number mapping (ENUM)/Domain Name System (DNS) database to determine a direct destination server for messaging traffic, allowing for direct routing based on service type or content type, and fallback mechanisms through Breakout Gateway Control Function when ENUM/DNS queries are unsuccessful.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If traditional routing mechanisms are used in IMS networks, then messaging traffic can be routed through multiple network elements, but this leads to network overloads and increased operational costs
Solution Approach 1:
The patent extracts the routing intelligence from the traditional multi-element network path and concentrates it in the gateway function. By querying the ENUM/DNS database directly at the gateway, the system eliminates unnecessary intermediate network elements and achieves direct routing to the destination server, thereby reducing network overload and operational complexity
Solution Approach 2:
The gateway function acts as an intermediary that mediates between the messaging application and the ENUM/DNS database. It performs the routing decision by querying the database and then directs traffic along the optimal path, replacing the need for multiple network elements while maintaining proper routing functionality
2Device complexity
If direct routing mechanisms are implemented using ENUM/DNS database, then the number of network elements is reduced, but this requires successful database queries which may not always be available
Solution Approach 1:
The patent implements a fallback mechanism that cushions against the potential failure of ENUM/DNS database queries. When direct routing via database query fails or is unavailable, the system automatically switches to alternative routing paths throughBreakout Gateway Control Function (BGCF), ensuring continuous service availability and preventing complete routing failure
Solution Approach 2:
The routing mechanism is made dynamic by allowing the system to switch between direct routing (when ENUM/DNS query succeeds) and alternative routing (when query fails). This dynamic adaptation ensures reliability while maintaining the benefits of direct routing when available
Data Source
AI summary
Exemplary method and apparatuses for routing messaging traffic from a calling party in an Internet Protocol Multimedia Subsystem (IMS) network to a server in a destination network that serves a called party via the most direct route are provided. A telephone number mapping (ENUM)/Domain Name System (DNS) database, pre-provisioned to receive and respond to query messages based on an identifier of the called party and an application specific service type, e.g., short message service (SMS) or instant messaging (IM), may be accessed by a node in the calling party's IMS network to determine an address of the server in the destination network. Messaging traffic may be routed to the destination network or server based on content type or destination digits when ENUM/DNS database based routing mechanisms fail. Furthermore, routing of messaging traffic originating in an enterprise network and routing through the public switched telephone network (PSTN) is enabled.