Methods and systems for message transfer part (MTP) load sharing using MTP load sharing groups

• US 8,817,627 B2
• Filed: 06/09/2010
• Issued: 08/26/2014
• Est. Priority Date: 11/20/2003
• Status: Active Grant

• Current Assignee: Tekelec Global, Inc. (Oracle Corporation)
• Original Assignee: Tekelec Global, Inc. (Oracle Corporation)
• Inventors: Delaney, Robert J., Eichler, Todd
• Primary Examiner(s): Pham, Chi
• Assistant Examiner(s): LOPATA, ROBERT J
• Application Number:
  US12/797,197
• Publication Number:
  US 20100246403A1
• Time in Patent Office: 1,539 Days
• Field of Search: 370/229, 370/235, 370/236, 370/465, 370/468, 709/204, 709/205, 379/219, 379/220.01, 379/221.01, 379/221.08, 379/229, 379/230
• US Class Current: 370/236
• CPC Class Codes: H04Q 3/0025 Provisions for signalling

Abstract

Methods and systems for load sharing signaling messages at the MTP level are disclosed. When a signaling message is received, it is determined whether the signaling message includes a routing indication indicating route-on-point-code-subsystem-number. If the routing indicator indicates route-on-point-code-subsystem-number, it is determined whether the signaling message belongs to an MTP level 3 load sharing group. If the signaling message belongs to an MTP level 3 load sharing group, the signaling message may be routed to any of the point codes in the MTP level 3 load sharing group. Routing the signaling message to a point code in the MTP level 3 load sharing group may include replacing the destination point code in the signaling message with the destination point code of the node to which the signaling message is to be routed. Once the point code has been replaced, the signaling message is routed to the destination associated with the point code.

Claims

1. A method for performing network management for a message transfer part (MTP) load sharing group, the method comprising:

(a) maintaining network management status for an MTP load sharing group wherein the MTP load sharing group is configured such that messages originating from the same network node will be load shared among different destination nodes, wherein the messages originating from the same network node are received by a network routing node as route-on-point-code-subsystem number (PC-SSN) messages addressed to a common capability point code (CPC) that is shared by the different destination nodes;

(b) detecting, by the network routing node, a network management event affecting status of a member of the MTP load sharing group, wherein detecting a network management event includes receiving a first transfer-prohibited (TFP) message or a first transfer-controlled (TFC) message from the member of the MTP load sharing group;

(c) determining, by the network routing node, whether a status for the MTP load sharing group has changed, wherein the status for the MTP load sharing group is changed in the event each of the different destination nodes of the MTP load sharing group is congested or prohibited; and

(d) in response to determining that a network management status for the MTP load sharing group has changed, performing, by the network routing node, a network management procedure for the MTP load sharing group, wherein performing the network management procedure includes sending a second TFP message or a second TFC message to the same network node.

2. The method of claim 1 wherein maintaining network management status for the MTP load sharing group includes maintaining network management status for the capability point code assigned to the MTP load sharing group.

3. The method of claim 1 wherein maintaining network management status for the MTP load sharing group includes maintaining network management status for an MTP load sharing group identifier assigned to the MTP load sharing group.

4. The method of claim 1 comprising, in response to detecting the network management event, updating the status for the MTP load sharing group member.

5. The method of claim 1 comprising, in response to determining that the network management status has not changed, inhibiting performance of the network management procedure for the MTP load sharing group.

6. The method of claim 1 wherein performing a network management procedure for the MTP load sharing group includes communicating network management status for the MTP load sharing group to an external node.

7. A network routing node for performing network management for a message transfer part (MTP) load sharing group, the network routing node comprising:

a message transfer part (MTP) load sharing group table located within a network routing node for maintaining network management status for an MTP load sharing group wherein the MTP load sharing group is configured such that messages originating from the same network node will be load shared among different destination nodes, wherein the messages originating from the same network node are received by a network routing node as and route-on-point-code-subsystem number (PC-SSN) messages addressed to a common capability point code (CPC) that is shared by the different destination nodes; and

a processor located within the network routing node for;

detecting a network management event affecting status of a member of the MTP load sharing group, wherein detecting a network management event includes receiving a first transfer-prohibited (TFP) message or a first transfer-controlled (TFC) message from the member of the MTP load sharing group;

determining whether a status for the MTP load sharing group has changed, wherein the status for the MTP load sharing group is changed in the event each of the different destination nodes of the MTP load sharing group is congested or prohibited; and

in response to determining that a network management status for the MTP load sharing group has changed, performing a network management procedure for the MTP load sharing group, wherein performing the network management procedure includes sending a second TFP message or a second TFC message to the same network node.