Methods, systems, and computer readable media for configurable diameter address resolution

• US 8,831,016 B2
• Filed: 03/19/2012
• Issued: 09/09/2014
• Est. Priority Date: 03/18/2011
• Status: Active Grant

• Current Assignee: Tekelec
• Original Assignee: Tekelec
• Inventors: Wallace, Donald E., Kanode, Mark E., McCann, Thomas M., Karuturi, Sridhar, Karmarkar, Kedar K.
• Primary Examiner(s): MURPHY, RHONDA L
• Application Number:
  US13/424,001
• Publication Number:
  US 20120236871A1
• Time in Patent Office: 904 Days
• Field of Search: None
• US Class Current: 370/401
• CPC Class Codes: H04L 2101/395 Internet protocol multimedia private identity [IMPI]; Internet protocol multimedia public identity [IMPU]
• CPC Class Codes: H04L 2101/65 Telephone numbers
• CPC Class Codes: H04L 2101/654 International mobile subscriber identity [IMSI] numbers
• CPC Class Codes: H04L 61/10 of different types
• CPC Class Codes: H04L 63/0892 by using authentication-authorization-accounting [AAA] servers or protocols

Abstract

Methods, systems, and computer readable media for configurable Diameter address resolution are disclosed. One method includes, at a Diameter signaling router (DSR), sending Diameter signaling messages to and receiving Diameter signaling messages from Diameter signaling entities in a network. The method further includes providing for configuration of a plurality of routing entity identities and an order for preferentially using the routing entity identities in performing Diameter address resolution. The method further includes routing Diameter signaling messages using Diameter address information determined in the Diameter routing address resolution.

Claims

1. A Diameter signaling router (DSR) including:

a network interface for sending Diameter signaling messages to and receiving Diameter signaling messages from Diameter signaling entities in a network;

a Diameter address resolution module configured to provide for configuration of a plurality of routing entity identities and an order of preference for using the plurality of routing entity identities in performing Diameter address resolution, wherein the Diameter address resolution module searches attribute value pairs within a received Diameter signaling message for specific routing entity identities by searching a received Diameter signaling message for a most preferred routing entity identity specified by the order, and, in response to failing to locate the most preferred routing entity identity, searching for a next most preferred routing entity identity, and, if located, using the next most preferred network routing entity identity in performing the routing address resolution, determines which routing entity identity to use for the message based on the configured order of preference by using, in the order, routing entity identities located in the message to perform the routing address resolution until an instance of the routing address resolution is successful, and uses the determined routing entity identity to look up Diameter address information; and

a Diameter routing module configured to route the Diameter signaling message using the Diameter address information determined by the Diameter routing address resolution module, wherein the routing entity identity comprises an identifier in a Diameter signaling message that identifies an entity and that is resolved into Diameter address information.

2. The system of claim 1 wherein the Diameter address resolution module provides for configuration of specific attribute value pairs to be searched for the routing entity identities.

3. The system of claim 1 wherein the Diameter address resolution module is configured to provide for configuration of routing exceptions for Diameter signaling messages for which the Diameter routing address resolution fails.

4. The system of claim 3 wherein the routing exceptions include forwarding received Diameter messages, routing received Diameter messages to a default destination, or formulating a Diameter answer message with a configurable error code.

5. The system of claim 1 wherein the Diameter address resolution module is configured to replace Diameter address information in received Diameter signaling messages to be routed or to insert the Diameter address information determined in the Diameter address resolution into Diameter response messages generated in response to received Diameter request messages.

6. The system in claim 1 wherein the DSR is configured to function as a Diameter proxy agent and as a Diameter redirect agent.

7. The system in claim 1 wherein the Diameter address resolution module is configured to perform an individual address override lookup for a routing entity identity and, if successful, to bypass a range based Diameter routing address resolution lookup.

8. The system of claim 7 wherein the individual override lookup allows records for individual subscribers to be moved among Diameter service nodes.

9. The system of claim 1 wherein the Diameter address resolution module is configured to prevent multiple invocations of the same Diameter address resolution by marking a Diameter signaling message for which a Diameter routing address resolution is performed.

10. A method for configurable Diameter address resolution, the method comprising:

in a Diameter signaling router (DSR);

sending Diameter signaling messages to and receiving Diameter signaling messages from Diameter signaling entities in a network;

providing for configuration of a plurality of routing entity identities and an order of preference for using the plurality of routing entity identities in performing Diameter address resolution; and

receiving a Diameter signaling message, searching attribute value pairs within the received message for specific routing entity identities by searching a received Diameter signaling message for a most preferred routing entity identity specified by the order, and, in response to failing to locate the most preferred routing entity identity, searching for a next most preferred routing entity identity, and, if located, using the next most preferred network routing entity identity in performing the routing address resolution, determining which routing entity identity to use for the message based on the configured order of preference by using, in the order, routing entity identities located in the message to perform the routing address resolution until an instance of the routing address resolution is successful, using the determined routing entity identity to look up Diameter address information, and routing the received message using the Diameter address information, wherein the routing entity identity comprises an identifier in a Diameter signaling message that identifies an entity and that is resolved into Diameter address information.

11. The method of claim 10 comprising providing for configuration of specific attribute value pairs in which the DSR is configured to search for the routing entity identities.

12. The method of claim 10 comprising providing for configuration of routing exceptions for Diameter signaling messages for which the Diameter routing address resolution fails.

13. The method of claim 12 wherein the routing exceptions include routing the messages, routing the messages to a default destination, and generating an answer message with an error code.

14. The method of claim 10 comprising replacing Diameter destination parameters in received messages to be routed or inserting Diameter address information determined in the Diameter address resolution in Diameter response messages to be transmitted in response to Diameter request messages.

15. The method of claim 10 comprising, at the DSR, functioning as both a Diameter proxy agent and a Diameter redirect agent.

16. The method of claim 10 wherein performing the Diameter address resolution comprises performing a lookup in an individual address override table followed by a lookup in a range-based table if the lookup in the individual address override table fails.

17. The method of claim 16 wherein the individual override table is provisioned with routing entity identities corresponding to subscribers whose records have been moved among Diameter service nodes.

18. The method of claim 10 comprising marking egress Diameter signaling messages for which address resolution is successful to prevent multiple invocations of the same Diameter address resolution.

19. A non-transitory readable medium having stored thereon executable instructions that, when executed by a processor of a computer, control the computer to perform steps comprising:

in a network node for sending Diameter signaling messages to and receiving Diameter signaling messages from Diameter signaling entities in a network;

providing for configuration of a plurality of routing entity identities and an order of preference for using the plurality of routing entity identities in performing Diameter address resolution; and

receiving a Diameter signaling message, searching attribute value pairs within the received message for specific routing entity identities by searching a received Diameter signaling message for a most preferred routing entity identity specified by the order, and, in response to failing to locate the most preferred routing entity identity, searching for a next most preferred routing entity identity, and, if located, using the next most preferred network routing entity identity in performing the routing address resolution, determining which routing entity identity to use for the message based on the configured order of preference by using, in the order, routing entity identities located in the message to perform the routing address resolution until an instance of the routing address resolution is successful, using the determined routing entity identity to look up Diameter address information, and routing the received message using the Diameter address information, wherein the routing entity identity comprises an identifier in a Diameter signaling message that identifies an entity and that is resolved into Diameter address information.