Network Routing Based on Terminal Media Path
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In telecommunications networks, the load on the IMS core is increased due to the need for signaling traffic to route through an inbound proxy even for non-IMS calls, leading to inefficiencies in network bandwidth usage and call-setup times.
Innovation Solution
A routing device associated with the originating terminal queries a responder, such as an ENUM server, to determine the serving-network information of the terminating terminal, allowing direct communication with the serving network, thereby bypassing the IMS I-CSCF and reducing the number of network elements involved in connections.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If signaling traffic routes through an inbound proxy (I-CSCF) for all calls including non-IMS calls, then network interconnection and routing control is maintained, but the load on the IMS core increases and network bandwidth usage becomes inefficient
Solution Approach 1:
The patent segments the routing process into two distinct phases: (1) querying the ENUM server to determine whether the destination is an IMS user, and (2) routing through the I-CSCF only if necessary. This segmentation allows non-IMS calls to bypass the I-CSCF while IMS calls continue to route through it, resolving the contradiction between maintaining routing control and improving network bandwidth efficiency.
Solution Approach 2:
The ENUM server acts as an intermediary between the routing device and the I-CSCF. By introducing this intermediary layer that provides destination type information, the system can make informed routing decisions without requiring all traffic to pass through the I-CSCF, thus reducing IMS core load while maintaining proper routing control for IMS calls.
2Reliability
If signaling traffic routes through an inbound proxy (I-CSCF) for all calls, then routing control is maintained, but call-setup times increase due to additional intermediate nodes
Solution Approach 1:
The routing process is segmented to determine destination type before initiating full IMS routing procedures. By dividing the call setup into an ENUM query phase and a routing execution phase, the system avoids unnecessary I-CSCF involvement for non-IMS calls, reducing call-setup time while maintaining routing control for IMS destinations.
Solution Approach 2:
The system performs a preliminary ENUM query to determine the destination type before routing the call. This preliminary action provides advance information that allows the routing device to bypass the I-CSCF for non-IMS calls, thereby reducing call-setup time while ensuring proper routing control is maintained for IMS calls through the preliminary identification step.
3Productivity
If the ENUM server stores comprehensive network-attachment information for all terminals, then direct routing to serving networks is enabled, but the device complexity and memory requirements of the ENUM server increase
Solution Approach 1:
The patent applies local quality by storing different types of information in the ENUM server based on their usage frequency and importance. Currently active terminals have their full network-attachment information stored, while inactive terminals have minimal or no information stored. This selective information storage reduces ENUM server complexity while maintaining routing efficiency for active connections.
Solution Approach 2:
The system changes the parameter of information completeness in the ENUM server based on terminal activity status. For active terminals, the server stores complete network-attachment information enabling direct routing. For inactive terminals, the server stores minimal information or none at all. This dynamic parameter adjustment reduces overall device complexity while preserving routing efficiency when needed.
Data Source
AI summary
A routing device of a telecommunications network can receive an initiation request of a communication session. The initiation request can include a destination identifier associated with a terminal. The routing device can query a responder for terminal-associated serving-network information. The routing device can then forward the initiation request to a serving network identified by the serving-network information. In some examples, the responder can query a registry for network-attachment information indicating a current media path associated with the terminal. The responder can provide the serving-network information based at least in part on the network-attachment information. In some examples, the destination identifier can include a global name, and the serving-network information can include an associated local name In some examples, the routing device can include an S-CSCF or ISBC, the responder can include an ENUM server, or the registry can include an HSS.