IP Library Granted Patent US 9,154,319
Granted Patent B2
US 9,154,319 · App. 14/202,535 · Granted Oct 6, 2015

Method and apparatus for sharing TCAP traffic load

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 9,154,319
App. No.
14/202,535
Granted
Oct 6, 2015
Kind
B2
Abstract

The present invention relates to a point code emulation apparatus and method for dividing a Common Channel Signaling System No. 7 (or SS7) signaling network into two or more networks. The point code emulator is adapted to receive TCAP messages from two or more subnets and converts, for the messages crossing over the subnets, the information of the TCAP messages, including originating point code, destination point code, and transaction identifier, (and optionally, calling party number and called party number), and forwards to the other one of the two or more subnets. Correspondence among the two or more subnets may be provisioned by an authorized user of the system, may be learned automatically by the system based on ISUP message correspondences or previous TCAP transactions, or may be automatically discovered by the system broadcasting messages to nodes in the destined one of the two or more subnets.

Claims (54)

1. A Signaling System No. 7 (SS7 ) node for routing transaction capabilities application part (TCAP) messages from a first subnet to a second subnet by discovering a destination node from a plurality of nodes in the second subnet, comprising:

a) a first interface for the first subnet;

b) a second interface for the second subnet;

c) a processor in communication with the first and second interfaces and one or more structured database storages, the processor configured to:

i) receive a first TCAP message from the first subnet through the first interface;

ii) extract originating point code (OPC), destination point code (DPC) and transaction identifier (TID) of said first TCAP message;

iii) broadcast a message to all or a part of said plurality of the nodes in the second subnet through the second interface;

iv) receive one or more responses to the message from one or more of said plurality of the nodes in the second subnet;

v) determine the destination node and a corresponding OPC, DPC and TID based on a most successful one of the one or more responses;

vi)route the most successful one of one or more responses to the first subnet through the first interface;

vii) receive a second TCAP message from the first subnet through the first interface subsequent to determining the destination node and a corresponding OPC, DPC and TID based on said most successful one of the one or more responses;

viii) extract originating point code (OPC), destination point code (DPC) and transaction identifier (TID) of said second TCAP message

ix) look up and retrieve, from said one or more structured database storages, said corresponding OPC, said corresponding DPC and said corresponding TID for said destination node in said second subnet partially or combinedly based on said extracted OPC, DPC and TID of said second received TCAP message;

x) replace said extracted OPC, DPC and TID of said second TCAP message with said retrieved corresponding OPC, DPC and TID; and

xi) forward said second TCAP message with said corresponding OPC, DPC, and TID through said second interface to the second subnet.

2. The SS7 node as recited in claim 1 , wherein said broadcast message is a TCAP Begin message.

3. The SS7 node as recited in claim 2 , wherein said first TCAP message is a TCAP Begin message.

4. The SS7 node as recited in claim 1 , wherein said look up and retrieval of said corresponding OPC, said corresponding DPC and said corresponding TID is based on said DPC of said received second TCAP message.

5. The SS7 node as recited in claim 1 , wherein said first subnet is a public SS7 network and said second subnet is a private SS7 network.

6. The SS7 node as recited in claim 1 , wherein said most successful response from said plurality of nodes in said second subnet is a first successful response.

7. A method of routing transaction capabilities application part (TCAP) messages from a first subnet to a second subnet by discovering a destination node from a plurality of nodes in the second subnet, comprising the steps of:

a) at a node, receiving a first TCAP message from the first subnet;

b) at the node, extracting an originating point code (OPC), a destination point code (DPC) and a transaction identifier (TID) of said first TCAP message;

c) from the node, broadcasting a message to all or a part of said plurality of nodes in the second subnet;

d) at the node, receiving one or more responses to the message from one or more of said plurality of the nodes in the second subnet;

e) determining the destination node and a corresponding OPC, DPC and TID based on a most successful one of the one or more responses;

f) routing the most successful one of one or more responses to the first subnet;

g) at the node, receiving a second TCAP message from the first subnet subsequent to determining the destination node and a corresponding OPC, DPC, and TID based on said most successful one of the one or more responses;

h) at the node, extracting an originating point code (OPC), a destination point code (DPC) and a transaction identifier (TID) of said second TCAP message;

i) look up and retrieve, from one or more structured database stores, said corresponding OPC, said corresponding DPC and said corresponding TID for said extracted OPC, DPC and TID for said destination node in said second subnet partially or combinedly based on said extracted OPC, DPC and TID of said second received TCAP message;

j) replace said extracted OPC, DPC and TID of said second TCAP message with said retrieved corresponding OPC, DPC and TID; and

k) forward said second TCAP message with said corresponding OPC, DPC, and TID to the second subnet.

8. The method as recited in claim 7 , wherein said broadcast message is a TCAP Begin message.

9. The method as recited in claim 8 , wherein said first TCAP message is a TCAP Begin message.

10. The method as recited in claim 7 , wherein said look up and retrieval of said corresponding OPC, said corresponding DPC and said corresponding TID is based on said DPC of said received second TCAP message.

11. The method as recited in claim 7 , wherein said first subnet is a public SS7 network and said second subnet is a private SS7 network.

12. The method as recited in claim 7 , wherein said most successful response from said plurality of nodes in said second subnet is a first successful response.

13. A non-transitory computer readable storage medium storing executable computer program instructions which, when executed at a node, causes the node to perform a process of routing transaction capabilities application part (TCAP) messages from a first subnet to a second subnet by discovering a destination node from a plurality of nodes in the second subnet, comprising the steps of:

a) at the node, receiving a first TCAP message from the first subnet;

b) at the node, extracting an originating point code (OPC), a destination point code (DPC) and a transaction identifier (TID) of said first TCAP message;

c) from the node, broadcasting a message to all or a part of said plurality of nodes in the second subnet;

d) at the node, receiving one or more responses to the message from one or more of said plurality of the nodes in the second subnet; e) determining the

destination node and a corresponding OPC, DPC and TID based on a most successful one of the one or more responses;

f) routing the most successful one of one or more responses to the first subnet;

g) at the node, receiving a second TCAP message from the first subnet subsequent to determining the destination node and a corresponding OPC, DPC, and TID based on said most successful one of the one or more responses;

h) at the node, extracting an originating point code (OPC), a destination point code (DPC) and a transaction identifier (TID) of said second TCAP message;

i) look up and retrieve, from one or more structured database stores, said corresponding OPC, said corresponding DPC and said corresponding TID for said extracted OPC, DPC and TID for said destination node in said second subnet partially or combinedly based on said extracted OPC, DPC and TID of said second received TCAP message;

j) replace said extracted OPC, DPC and TID of said second TCAP message with said retrieved corresponding OPC, DPC and TID; and

k) forward said second TCAP message with said corresponding OPC, DPC, and TID to the second subnet.

14. The computer readable storage medium as recited in claim 13 , wherein said broadcast message is a TCAP Begin message.

15. The computer readable storage medium as recited in claim 14 , wherein said first TCAP message is a TCAP Begin message.

16. The computer readable storage medium as recited in claim 13 , wherein said look up and retrieval of said corresponding OPC, said corresponding DPC and said corresponding TID is based on said DPC of said received second TCAP message.

17. The computer readable storage medium as recited in claim 13 , wherein said first subnet is a public SS7 network and said second subnet is a private SS7 network.

18. The computer readable storage medium as recited in claim 13 , wherein said most successful response from said plurality of nodes in said second subnet is a first successful response.

Assignments (12)
RELEASE OF SECURITY INTEREST Recorded Jun 24, 2024
From: CITIZENS BANK, N.A.
To: RIBBON COMMUNICATIONS OPERATING COMPANY, INC. (F/K/A GENBAND US LLC AND SONUS NETWORKS, INC.)
Reel/Frame 067822/0433 →
RELEASE OF SECURITY INTEREST Recorded May 16, 2023
From: PNC BANK, NATIONAL ASSOCIATION
To: INVACARE CORPORATION; FREEDOM DESIGNS, INC.; GARDEN CITY MEDICAL INC.; THE AFTERMARKET GROUP, INC.; DYNAMIC MEDICAL SYSTEMS, LLC; INVACARE CONTINUING CARE, INC.; MEDBLOC, INC.; ADAPTIVE SWITCH LABORATORIES, INC.; CENTRALIZED MEDICAL EQUIPMENT LLC; THE HELIXX GROUP, INC.; INVACARE CANADIAN FINANCE, LLC; INVACARE CANDIAN HOLDINGS, INC.; INVACARE CREDIT CORPORATION; INVACARE FLORIDA CORPORATION; INVACARE FLORIDA HOLDINGS, LLC; INVACARE HOLDINGS, LLC; INVACARE INTERNATIONAL CORPORATION; INVAMEX HOLDINGS LLC; INVACARE OUTCOMES MANAGEMENT LLC
Reel/Frame 063668/0639 →
TERMINATION AND RELEASE OF PATENT SECURITY AGREEMENT AT R/F 044978/0801 Recorded Dec 6, 2021
From: SILICON VALLEY BANK, AS ADMINISTRATIVE AGENT
To: RIBBON COMMUNICATIONS OPERATING COMPANY, INC. (F/K/A GENBAND US LLC AND SONUS NETWORKS, INC.)
Reel/Frame 058949/0497 →
SECURITY INTEREST Recorded Mar 3, 2020
From: RIBBON COMMUNICATIONS OPERATING COMPANY, INC.
To: CITIZENS BANK, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 052076/0905 →
CHANGE OF NAME Recorded Jan 16, 2019
From: SONUS NETWORKS, INC.
To: RIBBON COMMUNICATIONS OPERATING COMPANY, INC.
Reel/Frame 048078/0036 →
SECURITY INTEREST Recorded Jan 2, 2018
From: GENBAND US LLC; SONUS NETWORKS, INC.
To: SILICON VALLEY BANK, AS ADMINISTRATIVE AGENT
Reel/Frame 044978/0801 →
MERGER AND CHANGE OF NAME Recorded Dec 24, 2017
From: SOLSTICE SAPPHIRE, INC.; SONUS NETWORKS, INC.; SONUS NETWORKS, INC.
To: SONUS, INC.
Reel/Frame 044957/0243 →
CHANGE OF NAME Recorded Dec 24, 2017
From: SONUS, INC.
To: SONUS NETWORKS, INC.
Reel/Frame 044957/0213 →
CORRECTIVE ASSIGNMENT TO CORRECT THE APPLICATION NUMBER 13/847,302 PREVIOUSLY RECORDED AT REEL: 034574 FRAME: 0711. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Jan 21, 2015
From: PERFORMANCE TECHNOLOGIES, INC.
To: SONUS NETWORKS, INC.
Reel/Frame 034783/0641 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 23, 2014
From: PERFORMANCE TECHNOLOGIES, INC.
To: SONUS NETWORKS, INC.
Reel/Frame 034574/0711 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 10, 2014
From: GLAUDE, NORMAND; WESLEY-JAMES, CHARLES; AUBRY, CHRISTINE
To: PERFORMANCE TECHNOLOGIES INC.
Reel/Frame 032395/0269 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 10, 2014
From: LAPORTE, PIERRE
To: PERFORMANCE TECHNOLOGIES INC.
Reel/Frame 032395/0396 →