METHODS, SYSTEMS, AND COMPUTER READABLE MEDIA FOR PROVIDING DYNAMIC ORIGINATION-BASED ROUTING KEY REGISTRATION IN A DIAMETER NETWORK

• US 20110314178A1
• Filed: 06/15/2011
• Published: 12/22/2011
• Est. Priority Date: 06/15/2010
• Status: Active Grant

• Current Assignee: Tekelec
• Original Assignee: Tekelec
• Inventors: Kanode, Mark Edward, Marsico, Peter J.
• Granted Patent: US 8,566,474 B2
• Time in Patent Office: Days
• US Class Current: 709/238
• CPC Class Codes: H04L 45/54 Organization of routing tables
• CPC Class Codes: H04L 63/0892 by using authentication-authorization-accounting [AAA] servers or protocols

Abstract

Methods, systems, and computer readable media for providing dynamic origination-based routing key registration in a DIAMETER network are disclosed. According to one method, origin-based routing information is received, at a first DIAMETER node, from a second DIAMETER node. The origin-based routing information specifies one or more sources such that traffic originating from one of the one or more sources should be routed to the second DIAMETER node. A routing rule is automatically generated, at he first DIAMETER node, based on the received origin-based routing information.

Claims

1. A method for providing dynamic origination-based routing key registration in a diameter network, the method comprising:

at a first DIAMETER node;

receiving, from a second DIAMETER node, origin-based routing information, wherein the origin-based routing information specifies one or more sources such that traffic originating from one of the one or more sources should be routed to the second DIAMETER node; and

automatically generating a routing rule based on the received origin-based routing information.

2. The method of claim 1 comprising automatically populating a routing table on the first DIAMETER node with the routing rule.

3. The method of claim 1 comprising routing traffic originating from the one or more sources to the second DIAMETER node using the routing rule.

4. The method of claim 1 wherein the originating source information includes at least one of an originating realm identifier, an originating host identifier, and an application identifier.

5. The method of claim 1 wherein the origin-based routing information is included in dedicated message type.

6. The method of claim 1 wherein the origin-based routing information is included in one of a modified DIAMETER capabilities exchange request (CER) message and a modified DIAMETER capabilities exchange answer (CEA) message.

7. The method of claim 6 wherein the one of the modified DIAMETER CER message and the modified DIAMETER CEA message includes a routing key indicating the presence of origin-based routing information.

8. The method of claim 1 wherein the first DIAMETER node includes a DIAMETER signaling router.

9. The method of claim 1 wherein automatically generating a routing rule includes automatically generating a primary routing rule and a default routing rule.

10. The method of claim 9 comprising distinguishing the primary routing rule and the default routing rule using one of priority values and different weight values.

11. The method of claim 1 comprising authenticating the received origin-based routing information.

12. The method of claim 1 wherein the first DIAMETER node and the second DIAMETER node belong to the same realm.

13. The method of claim 1 wherein the first DIAMETER node belongs to a first realm and the second DIAMETER node belongs to a second realm.

14. A DIAMETER node for providing dynamic origination-based routing key registration in a diameter network, the system comprising:

a communications module for receiving, from a second DIAMETER node, origin-based routing information, wherein the origin-based routing information specifies one or more sources such that traffic originating from one of the one or more sources should be routed to the second DIAMETER node; and

a rule generation module for automatically generating a routing rule based on the received origin-based routing information.

15. The DIAMETER node of claim 14 comprising a peer routing table populated with the routing rule.

16. The DIAMETER node of claim 14 comprising a routing module for routing traffic originating from the one or more sources to the second DIAMETER node using the routing rule.

17. The DIAMETER node of claim 14 wherein the communications module receives originating source information including at least one of an originating realm identifier, an originating host identifier, and an application identifier.

18. The DIAMETER node of claim 14 wherein the origin-based routing information is included in dedicated message type.

19. The DIAMETER node of claim 14 wherein the communications module receives origin-based routing information included in one of a modified DIAMETER capabilities exchange request (CER) message and a modified DIAMETER capabilities exchange answer (CEA) message.

20. The DIAMETER node of claim 19 wherein the one of the modified DIAMETER CER message and the modified DIAMETER CEA message includes a routing key indicating the presence of origin-based routing information.

21. The DIAMETER node of claim 14 wherein the DIAMETER node includes a DIAMETER signaling router.

22. The DIAMETER node of claim 14 wherein the routing rule generation module automatically generates a primary routing rule and a default routing rule.

23. The DIAMETER node of claim 14 wherein the routing rule generation module assigns one of a priority value and a weight value to the routing rule.

24. The DIAMETER node of claim 14 comprising an authentication module for authenticating the received origin-based routing information.

25. The DIAMETER node of claim 14 wherein the DIAMETER node and the second DIAMETER node belong to the same realm.

26. The DIAMETER node of claim 14 wherein the DIAMETER node belongs to a first realm and the second DIAMETER node belongs to a second realm.

27. A computer readable medium comprising computer executable instructions embodied in a non-transitory computer readable medium and when executed by a processor of a computer performs steps comprising:

at a first DIAMETER node;

receiving, from a second DIAMETER node, origin-based routing information, wherein the origin-based routing information specifies one or more sources such that traffic originating from one of the one or more sources should be routed to the second DIAMETER node; and

automatically generating a routing rule based on the received origin-based routing information