Signalling Gateway Routing Key Extraction for SS7 to IP Migration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In SS7-based networks migrating to IP networks, the signalling information field of a TCAP message is often too small to carry all elements defining a routing key, leading to challenges in directing messages to the correct Application Server without requiring the signalling gateway or Application Server to manage a context for the transaction.

Innovation Solution

A method and apparatus that act as a conduit for structured transactions between transaction peers, allowing the determination and inclusion of a routing key from continue messages, enabling the construction and sending of begin and end messages without requiring a context on the signalling gateway, and modifying the application context and point code in end messages to facilitate correct routing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Loss of information

If the signalling information field of a TCAP message is used to carry routing key information, then the routing capability is improved, but the message field size limitation causes information loss

Engineering Contradiction:
Improverouting key informationVSAvoidsignalling information field
Core Design Contradiction:
Loss of informationVSLength of moving object

Solution Approach 1:

The routing key information is segmented into two parts: the routing key itself is extracted from the continue message, and a default application context is used as a placeholder. This segmentation allows the gateway to route messages correctly without requiring the full routing key information to be present in the original TCAP message.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The signalling gateway acts as an intermediary that extracts routing key information from continue messages and uses it to determine the correct application context. The gateway mediates between the limited message field size and the need for comprehensive routing information by using default contexts as placeholders.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If a default Application Server context is used for routing, then the gateway operation is simplified, but the routing precision deteriorates

Engineering Contradiction:
Improvegateway operationVSAvoidrouting precision
Core Design Contradiction:
Ease of operationVSMeasurement precision

Solution Approach 1:

The system dynamically switches from using a default application context to using a specific application context based on the extracted routing key information. The gateway operates simply with a default context initially, then transitions to precise routing when routing key information is available in the continue message.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The gateway changes the application context parameter from a default value to a specific value derived from the routing key information in the continue message. This parameter change enables precise routing while maintaining simple initial operation with the default context.

Inventive Principle:
Principle #35Parameter changes

3Reliability

If the signalling gateway manages a context for the transaction, then the transaction reliability is improved, but the device complexity increases

Engineering Contradiction:
Improvetransaction reliabilityVSAvoidgateway complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The routing key information is extracted from the continue message rather than being managed as a context by the gateway. This extraction approach maintains transaction reliability by ensuring correct routing while avoiding the complexity of context management.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system uses the continue message itself to carry the routing key information, allowing the message to serve its own routing function without requiring the gateway to manage separate contexts. The message structure provides the necessary information for reliable routing autonomously.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS7519051B2Methods and related apparatus for operating a gateway to act as a conduit for a structured transaction
Publication Date: 2009.04.14 UBER TECHNOLOGIES INC
  • US7519051B2 patent drawing
  • US7519051B2 patent drawing
  • US7519051B2 patent drawing

AI summary

A method is described for operating a gateway to act as a conduit for a structured transaction between a first transaction peer and a second transaction peer, the structured transaction having at least a begin message for opening a logical communication path, a continue message for maintaining a logical communication path and an end message for closing a logical communication path. The method comprises the steps of: receiving a first begin message from the first transaction peer; receiving from the first transaction peer a continue message having a request element; determining a routing key identifying the second transaction peer from the continue message; constructing and sending a second begin message, including the component, to the second transaction peer; receiving a first end message including a response element from the second transaction peer; constructing and sending a second end message including the response element to the first transaction peer. In described embodiments, the gateway is a signalling gateway linking an SS7 network and an IP network and the structured transaction is a TCAP structured dialogue.