Class 1 SCCP Load Sharing Using Composite Routing Keys
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for load sharing Class 1 SCCP messages in SS7 networks fail to achieve balanced distribution among database nodes, leading to uneven traffic loads and inefficient routing of messages belonging to the same transaction.
Innovation Solution
A method and system that generate a Message Signal Unit (MSU) load sharing key using a combination of MTP and SCCP parameters, specifically the Called Party Global Title (CdGT), Originating Point Code (OPC), and Signaling Link Selector (SLS), to ensure that messages belonging to the same transaction are routed to the same destination node, using pseudorandomly generated arrays for lookup.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the SCCP called party address is used as the load sharing key, then messages with the same called party address are routed to the same database node, but this results in one database node being overloaded while other nodes are underutilized
Solution Approach 1:
The patent combines multiple parameters (SCCP called party address, MTP originating point code, and MTP signaling link selector) into a single composite load sharing key. This merging of parameters creates a more distributed key space that routes messages more evenly across database nodes while still maintaining consistency for messages belonging to the same transaction.
Solution Approach 2:
The patent changes the load sharing key from a single parameter (SCCP called party address) to a composite key formed by combining multiple parameters (SCCP called party address, MTP originating point code, and MTP signaling link selector). This parameter transformation expands the key space and enables better load distribution across database nodes.
2Device complexity
If the TCAP transaction ID is used to load share class 1 SCCP messages, then routing may be simplified, but some class 1 SCCP messages such as TCAP END messages will not have the TCAP originator transaction ID, resulting in messages being routed to different database nodes
Solution Approach 1:
The patent performs global title translation to select a load sharing group before generating the final load sharing key. This preliminary action ensures that messages are routed to the correct group of database nodes that can handle the transaction, and then the composite key ensures consistent routing within that group, even for messages without TCAP transaction IDs.
Solution Approach 2:
The patent introduces an intermediate load sharing group selection step based on global title translation. This intermediary mechanism bridges the gap between simplified routing and transaction consistency by first routing to an appropriate group and then ensuring consistent distribution within the group using the composite key.
3Productivity
If the MTP OPC and signaling link selector are used to load share class 1 SCCP messages, then load sharing can be implemented, but there must be variation in the OPC and SLS values, and when a large number of messages originate from the same mobile switching center with the same OPC, messages are routed to the same destination node, resulting in uneven load balancing
Solution Approach 1:
The patent merges the SCCP called party address with MTP originating point code and MTP signaling link selector to create a composite load sharing key. This combination ensures that even when OPC and SLS values are identical (messages from the same mobile switching center), the variation in called party addresses creates sufficient diversity in the composite key to achieve uniform load distribution.
Solution Approach 2:
The patent creates a composite load sharing key by combining multiple parameters (SCCP called party address, MTP originating point code, and MTP signaling link selector) similar to creating a composite material. This composite key leverages the diversity across different parameter types to achieve uniform load distribution even when individual parameters lack sufficient variation.
Data Source
Figure 1
Figure 2
Figure 3A~3B
AI summary
A method for load sharing class 1 SCCP messages includes receiving a class 1 SCCP message requiring global title translation (GTT). The method includes performing GTT for the message to select a load sharing group for the message. The method further includes generating a message signal unit (MSU) load sharing key using parameters from a combination of message transfer part (MTP) layer parameters and signaling connection control part (SCCP) layer parameters. The method further includes using the MSU load sharing key to select a destination address from the load sharing group for the message. The method further includes inserting the destination address into the message. The method further includes routing the message to a destination corresponding to the destination address.