ENUM-Based Call Routing Bypassing IMS Core
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current Internet Protocol Multimedia Subsystem (IMS) systems face challenges in efficiently routing traffic and providing value-added services, particularly in scenarios where calls do not involve IMS subscriber endpoints or IMS-based applications, as they often require bypassing the IMS core, leading to inefficiencies in service invocation and routing.
Innovation Solution
The implementation of a system that includes a serving call session control function (S-CSCF), interrogating call session control function (I-CSCF), proxy call session control function (P-CSCF), and a telephone number mapping server (ENUM) to determine the appropriate routing path for calls, either through the IMS core or bypassing it, based on the presence of IMS subscribers and applications, utilizing infrastructure ENUM for network routing mechanisms.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If calls are routed through the IMS core for all types of traffic, then IMS services can be provided to all calls, but routing efficiency deteriorates for non-IMS related calls
Solution Approach 1:
The system segments call routing into two distinct paths: IMS core routing for IMS-related calls and alternative routing for non-IMS calls. The ENUM server acts as a segmentation point that divides incoming calls based on their type, directing them to appropriate routing paths. This resolves the contradiction by providing selective service coverage only where needed while maintaining high routing efficiency for non-IMS traffic.
Solution Approach 2:
Different routing qualities are applied to different call types. IMS-related calls receive the full service quality of core routing with access to all IMS services, while non-IMS calls receive optimized direct routing without unnecessary core processing. This local differentiation of routing quality resolves the contradiction between comprehensive service coverage and routing efficiency.
2Reliability
If the IMS core processes all calls, then service control is centralized and consistent, but system complexity and processing overhead increase
Solution Approach 1:
The system extracts non-IMS calls from the IMS core processing path and routes them through an alternative path. This removal of unnecessary calls from the core system reduces processing overhead and system complexity while maintaining centralized service control for actual IMS-related calls. The ENUM server performs the extraction by identifying and separating non-IMS traffic before it reaches the core.
Solution Approach 2:
The ENUM server performs preliminary routing determination before calls enter the IMS core. By pre-identifying non-IMS calls and routing them away in advance, the system avoids the complexity of processing these calls through the core while maintaining consistent service control for IMS calls that do require core processing.
3Device complexity
If routing decisions are made without infrastructure ENUM, then routing can be simplified, but routing precision and service appropriateness deteriorate
Solution Approach 1:
The ENUM server acts as an intermediary component that provides precise routing decisions without significantly complicating the overall routing mechanism. It mediates between the simple alternative routing path and the IMS core, making accurate routing determinations based on ENUM lookups. This intermediary approach maintains routing simplicity while improving routing accuracy through infrastructure ENUM.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A method includes receiving a telephone number mapping query associated with a call. The method may also include generating routing information based on the query and forwarding the routing information to a control device. The routing information may indicate that processing associated with routing the call is to bypass a core portion (Fig. 1, 102, 104, 106) of an Internet multimedia subsystem (Fig. 1) when a calling party associated with the call does not invoke and IMS service, the called party associated with the call does not invoke and IMS service and the called party is not an IMS subscriber.