Method and apparatus for sharing TCAP traffic load
View Patent ↗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.
1. A Signaling System No. 7 (SS7) 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 in a SS7 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, said first and second nodes having the same point code;
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 SS7 node as recited in claim 1 , wherein said first subnet is a public or private network.
3. The SS7 node as recited in claim 1 , wherein said second subnet is a public or private network.
4. The SS7 node as recited in claim 1 , wherein said message broadcasted is a TCAP Begin message.
5. 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 TCAP message.
6. The SS7 node as recited in claim 1 , wherein said processor gives each of said first and second records an expiry time and a lifespan for said first and second records.
7. 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 SS7 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, said first and second nodes having the same point code;
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.
8. The method as recited in claim 7 , wherein said first subnet is a public or private network.
9. The method as recited in claim 7 , wherein said second subnet is a public or private network.
10. The method as recited in claim 7 , wherein said message broadcasted is a TCAP Begin message.
11. The method 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 TCAP message.
12. The method as recited in claim 7 , further comprising giving each of said first and second records an expiry time and a lifespan for said first and second records.
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 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, said first and second nodes having the same point code;
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.
14. The computer readable storage medium as recited in claim 13 , wherein said first subnet is a public or private network.
15. The computer readable storage medium as recited in claim 13 , wherein said second subnet is a public or private network.
16. The computer readable storage medium as recited in claim 13 , wherein said message broadcasted is a TCAP Begin message.
17. 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 TCAP message.
18. The computer readable storage medium as recited in claim 13 , wherein said process further includes giving each of said first and second records an expiry time and a lifespan for said first and second records.