Methods, systems, and computer readable media for negotiating diameter capabilities

• US 9,888,001 B2
• Filed: 01/28/2014
• Issued: 02/06/2018
• Est. Priority Date: 01/28/2014
• Status: Expired due to Fees

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Donovan, Steven Robert
• Primary Examiner(s): Srivastava, Vivek
• Assistant Examiner(s): McBeth, William C
• Application Number:
  US14/166,772
• Publication Number:
  US 20150215167A1
• Time in Patent Office: 1,470 Days
• Field of Search: 709223, 709230
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/0892 by using authentication-authorization-accounting [AAA] servers or protocols
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources
• CPC Class Codes: H04L 63/20 for managing network security; network security policies in general filtering policies H04L63/0227
• CPC Class Codes: H04L 63/205 involving negotiation or determination of the one or more network security mechanisms to be used, e.g. by negotiation between the client and the server or between peers or by selection according to the capabilities of the entities involved negotiation of communication capabilities H04L69/24
• CPC Class Codes: H04W 12/06 Authentication
• CPC Class Codes: H04W 12/088 using filters or firewalls

Abstract

According to one method, the method occurs at a Diameter relay agent including at least one processor and a memory. The method includes receiving first Diameter capabilities information associated with a first Diameter node. The method also includes sending, to at least a second Diameter node, the first Diameter capabilities information.

Claims

1. A method for negotiating Diameter capabilities, the method comprising:

at a Diameter relay agent implemented using at least one hardware processor and a non-transitory computer readable medium having stored thereon executable instructions that are configured to be executed by the at least one hardware processor;

receiving, from a requesting node, a capabilities negotiation request (CNR) message for requesting Diameter capabilities information associated with at least one first Diameter node that is separate from the Diameter relay agent;

in response to receiving the CNR message, determining the at least one first Diameter node for which the Diameter capabilities information is requested based on node identifying information received in a prior CNR message and determining that the Diameter capabilities information associated with the at least one first Diameter node is stored and accessible by the Diameter relay agent; and

in response to determining that the Diameter capabilities information is stored and accessible by the Diameter relay agent, sending, by the Diameter relay agent, the Diameter capabilities information on behalf of the at least one first Diameter node without sending the CNR message to the at least one first Diameter node.

2. The method of claim 1 comprising:

in response to determining that the Diameter capabilities information is not stored or is inaccessible by the Diameter relay agent, sending the CNR message to the at least one first Diameter node;

receiving, from the at least one first Diameter node, the Diameter capabilities information associated with the at least one first Diameter node; and

sending, to the requesting node, the Diameter capabilities information associated with the at least one first Diameter node.

3. The method of claim 2 wherein receiving, from the at least one first Diameter node, the Diameter capabilities information associated with the at least one first Diameter node includes receiving, from a plurality of nodes, Diameter capabilities information associated with the plurality of nodes.

4. The method of claim 1 comprising:

sending the Diameter capabilities information to a plurality of nodes, wherein the plurality of nodes is determined using a subscription method, a location-based method, a network-based method, or preconfigured information.

5. The method of claim 1 wherein the Diameter capabilities information is sent from a second Diameter relay agent or the at least one first Diameter node.

6. The method of claim 1 wherein the Diameter capabilities information includes information about a Diameter protocol version, a Diameter application, a Diameter extension, or a security protocol.

7. The method of claim 1 wherein the at least one first Diameter node includes a Diameter client, a Diameter server, a Diameter routing agent, a Diameter proxy agent, a Diameter signaling router, or a Diameter peer node.

8. The method of claim 1 wherein sending the Diameter capabilities information includes sending a capabilities report message.

9. The method of claim 8 wherein the capabilities report message includes Diameter capabilities information associated with one or more nodes.

10. A system for routing a Diameter message, the system comprising:

a Diameter relay agent, the Diameter relay agent comprising;

at least one hardware processor;

a non-transitory computer readable medium; and

a Diameter capabilities negotiation relay (DCNR) module implemented using the at least one hardware processor and a non-transitory computer readable medium having stored thereon executable instructions that are configured to be executed by the at least one hardware processor, wherein the DCNR module is configured to receive, from a requesting node, a capabilities negotiation request (CNR) message for requesting Diameter capabilities information associated with at least one first Diameter node that is separate from the Diameter relay agent, in response to receiving the CNR message, to determine the at least one first Diameter node for which the Diameter capabilities information is requested based on node identifying information received in a prior CNR message and determine that the Diameter capabilities information associated with the at least one first Diameter node is stored and accessible by the Diameter relay agent, and in response to determining that the Diameter capabilities information is stored and accessible by the Diameter relay agent, to send, by the Diameter relay agent, the Diameter capabilities information on behalf of the at least one first Diameter node without sending the CNR message to the at least one first Diameter node.

11. The system of claim 10 wherein the DCNR module is configured to in response to determining that the Diameter capabilities information is not stored or is inaccessible by the Diameter relay agent, to send the CNR message to the at least one first Diameter node, to receive, from the at least one first Diameter node, the Diameter capabilities information associated with the at least one first Diameter node and to send, to requesting node, the Diameter capabilities information associated with the at least one first Diameter node.

12. The system of claim 11 wherein receiving, from the at least one first Diameter node, the Diameter capabilities information associated with the at least one first Diameter node includes receiving, from a plurality of nodes, Diameter capabilities information associated with the plurality of nodes.

13. The system of claim 10 wherein the DCNR module is configured to send the Diameter capabilities information to a plurality of nodes, wherein the plurality of nodes is determined using a subscription method, a location-based method, a network-based method, or preconfigured information.

14. The system of claim 10 wherein the Diameter capabilities information is sent from a second Diameter relay agent or the at least one first Diameter node.

15. The system of claim 10 wherein the Diameter capabilities information includes information about a Diameter protocol version, a Diameter application, a Diameter extension, or a security protocol.

16. The system of claim 10 wherein the at least one first Diameter node includes a Diameter client, a Diameter server, a Diameter routing agent, a Diameter proxy agent, a Diameter signaling router, or a Diameter peer node.

17. The system of claim 10 wherein the DCNR module is configured to send a capabilities report message.

18. The system of claim 17 wherein the capabilities report message includes Diameter capabilities information associated with one or more nodes.

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

at a Diameter relay agent implemented using at least one hardware processor and a non-transitory computer readable medium having stored thereon executable instructions that are configured to be executed by the at least one hardware processor;

receiving, from a requesting node, a capabilities negotiation request (CNR) message for requesting Diameter capabilities information associated with at least one first Diameter node that is separate from the Diameter relay agent;

in response to receiving the CNR message, determining the at least one first Diameter node for which the Diameter capabilities information is requested based on node identifying information received in a prior CNR message and determining that the Diameter capabilities information associated with the at least one first Diameter node is stored and accessible by the Diameter relay agent; and

in response to determining that the Diameter capabilities information is stored and accessible by the Diameter relay agent, sending, by the Diameter relay agent, the Diameter capabilities information on behalf of the at least one first Diameter node without sending the CNR message to the at least one first Diameter node.