IP Library Granted Patent US 9,565,029
Granted Patent B2
US 9,565,029 · App. 14/840,592 · Granted Feb 7, 2017

Methods and apparatus for routing TCAP messages

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,565,029
App. No.
14/840,592
Granted
Feb 7, 2017
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 (50)

1. A communications node for routing a transaction capabilities application part (TCAP) message from a first node in a first subnet to a second node in a second subnet of a communications network, said node comprising:

a) a first interface for said first subnet;

b) a second interface for said second subnet;

c) a processor in communication with said first and second interfaces, and further in communication with a structured database, wherein said processor is configured to:

i) prepare a first record for said first node and a second record for said second node in said structured database,

ii) receive said TCAP message from said first node through said first interface;

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

iv) look up and retrieve, from said structured database, said second record for a corresponding OPC, a corresponding DPC and a corresponding TID partially or combinedly based on said OPC, said DPC and said TID of said received TCAP message; and

v) replace said OPC, said DPC and said TID of said received TCAP message with said corresponding OPC, said corresponding DPC, and said corresponding TID; and

vi) forward said TCAP message with said corresponding OPC, said corresponding DPC, and said corresponding TID through said second interface; and

vii) prior to looking up and retrieving said corresponding OPC, said corresponding DPC and said corresponding TID, said processor:

broadcasts a message to all or a part of the nodes in said second subnet; and

determines values of said corresponding OPC, said corresponding DPC and said corresponding TID by receiving a successful response from one of said all or part of said one or more nodes in said second subnet.

2. The communications node as recited in claim 1 , wherein said first subnet is a public or private network.

3. The communications node as recited in claim 1 , wherein said second subnet is a public or private network.

4. The communications node as recited in claim 1 , wherein said message broadcasted is a TCAP Begin message.

5. The communications 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 TCAP message.

6. The communications node of claim 1 , wherein said first and second records each have a lifespan value.

7. The communications node of claim 6 , wherein each lifespan value is individually assigned to each of said first and second records.

8. The communications node of claim 7 , wherein when said first record lifespan value is determined to be expired recycling the first record and any records in said structured database with a corresponding TID record.

9. The communications node of claim 7 , wherein when said second record lifespan value is determined to be expired recycling the second record and any records in said structured database with a corresponding TID.

10. A method of routing a transaction capabilities application part (TCAP) message from a first node in a first subnet to a second node in a second subnet in a communications network, comprising the steps of:

a) preparing a first record for said first node and a second record for said second node in a structured database

b) at a node, receiving said TCAP message from said first node in said first subnet through a first interface;

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

d) looking up and retrieving, from said structured database, said second record for a corresponding OPC, a corresponding DPC and a corresponding TID partially or combinedly based on said OPC, said DPC and said TID of said received TCAP message;

e) replacing said OPC, said DPC and said TID of said received TCAP message with said corresponding OPC, said corresponding DPC, and said corresponding TID;

f) from the node, forwarding said TCAP message with said corresponding OPC, said corresponding DPC, and said corresponding TID to said second node in said second subnet through a second interface; and

g) prior to looking up and retrieving said corresponding OPC, said corresponding DPC and said corresponding TID:

(i) broadcasting a message to all or a part of the nodes in said second subnet; and

(ii) determining values of said corresponding OPC, said corresponding DPC and said corresponding TID by receiving a successful response from one of said all or part of said one or more nodes in said second subnet.

11. The method as recited in claim 10 , wherein said first subnet is a public or private network.

12. The method as recited in claim 10 , wherein said second subnet is a public or private network.

13. The method as recited in claim 10 , wherein said message broadcasted is a TCAP Begin message.

14. The method recited in claim 10 , 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 TCAP message.

15. The method of claim 10 , wherein said first and second records each have a lifespan value.

16. The method of claim 15 , wherein each lifespan value is individually assigned to each of said first and second records.

17. The method of claim 16 , wherein said first record lifespan value is determined to be expired recycling the first record and any records in said structured database with a corresponding TID.

18. The method of claim 16 , wherein when said second record lifespan value is determined to be expired recycling the second record and any records in said structured database with a corresponding TID.

19. 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 a transaction capabilities application part (TCAP) message from a first node in a first subnet to a second node in a second subnet comprising the steps of:

a) preparing a first record for said first node and a second record for said second node in a structured database;

b) at the node, receiving said TCAP message from said first node in said first subnet through a first interface;

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

d) looking up and retrieving, from said structured database, said second record for a corresponding OPC, a corresponding DPC and a corresponding TID partially or combinedly based on said OPC, said DPC and said TID of said received TCAP message;

e) replacing said OPC, said DPC and said TID of said received TCAP message with said corresponding OPC, said corresponding DPC, and said corresponding TID;

f) from the node, forwarding said TCAP message with said corresponding OPC, said corresponding DPC, and said corresponding TID to said second node in said second subnet through a second interface; and

g) prior to looking up and retrieving said corresponding OPC, said corresponding DPC and said corresponding TID:

(i) broadcasting a message to all or a part of the nodes in said second subnet; and

(ii) determining values of said corresponding OPC, said corresponding DPC and said corresponding TID by receiving a successful response from one of said all or part of said one or more nodes in said second subnet.

20. The non-transitory computer readable storage medium as recited in claim 19 , wherein said process further includes recycling the first record and any records in said structured database with a corresponding TID upon determining that a lifespan assigned to said first record has expired.

Assignments (10)
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 →
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 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 23, 2016
From: GLAUDE, NORMAND; WESLEY-JAMES, CHARLES; AUBRY, CHRISTINE
To: PERFORMANCE TECHNOLOGIES INC.
Reel/Frame 040761/0272 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 23, 2016
From: LAPORTE, PIERRE
To: PERFORMANCE TECHNOLOGIES INC.
Reel/Frame 040761/0278 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 23, 2016
From: PERFORMANCE TECHNOLOGIES, INC.
To: SONUS NETWORKS, INC.
Reel/Frame 041187/0947 →