SS7 Subsystem Number Routing for SIP Node Scalability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for routing messages from the SS7 domain to SIP nodes in the IP domain are inflexible and require maintaining a database of directory numbers, leading to scalability issues and the need for frequent updates when directory number provisioning changes.
Innovation Solution
Utilizing SS7 subsystem numbers to identify and route messages to SIP nodes, allowing SSGs to service multiple SIP nodes without a directory number database and enabling flexible routing without tying specific SIP nodes to SSGs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If an SSG maintains a directory number database to identify SIP nodes, then message routing can be performed, but the system requires frequent updates and has low scalability when directory number provisioning changes
Solution Approach 1:
The patent extracts the directory number database from the SSG, eliminating the need for the SSG to maintain local provisioning information. Instead, the SSG relies on SS7 network infrastructure (STP and GTT) to perform global title translation and route messages based on subsystem numbers, thereby removing the scalability bottleneck while maintaining routing accuracy
Solution Approach 2:
The patent introduces SS7 network intermediaries (Signal Transfer Points and Global Title Translation functions) as mediators between the SSG and SIP nodes. These intermediaries handle the complex task of directory number to SIP node mapping, allowing the SSG to remain simple and scalable while maintaining reliable message routing through the intermediary translation services
2Ease of operation
If an SSG has a one-to-one mapping with a SIP node, then message routing is straightforward, but the system has low flexibility and scalability
Solution Approach 1:
The patent enables SSGs to serve multiple SIP nodes simultaneously by using subsystem numbers as universal identifiers. Instead of dedicating one SSG to one SIP node, the SS7 network's global title translation capability allows any SSG to route messages to any SIP node based on the subsystem number in the message, providing multi-functionality and flexibility
Solution Approach 2:
The patent changes the routing parameter from directory numbers (which require database lookups) to subsystem numbers (which are directly routable through SS7 network infrastructure). This parameter change simplifies the routing operation while enabling flexible mapping between multiple SSGs and SIP nodes through the SS7 network's inherent translation capabilities
3Reliability
If directory number provisioning changes occur, then service updates are needed, but frequent updates increase system complexity and maintenance burden
Solution Approach 1:
The patent extracts the provisioning database from the SSG and places it in the SS7 network infrastructure (at the STP or as a separate GTT database). This extraction means that provisioning changes are managed by the SS7 network operators rather than requiring updates to each SSG, significantly reducing system maintenance complexity while maintaining provisioning accuracy
Solution Approach 2:
The patent enables the SS7 network infrastructure to automatically handle provisioning changes through its existing global title translation mechanisms. When directory number provisioning changes occur, the SS7 network self-updates its translation tables, and subsequent messages are automatically routed to the correct SIP nodes without requiring manual configuration changes at the SSG level
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Methods, systems, and computer program products for using signaling system 7 (SS7) subsystem numbers to route message to session initiation protocol (SIP) nodes. According to one method, an SS7 message can be received. A SIP message can be generated based on the SS7 message. A subsystem number associated with the SS7 message can be identified. A destination SIP node for the SIP message can be identified based on the subsystem number. Further, the SIP message can be forwarded to the SIP node.