Methods, systems, and computer readable media for performing diameter overload control

• US 9,699,045 B2
• Filed: 04/15/2013
• Issued: 07/04/2017
• Est. Priority Date: 04/13/2012
• Status: Active Grant

• Current Assignee: Tekelec, Inc. (Oracle Corporation)
• Original Assignee: Tekelec, Inc. (Oracle Corporation)
• Inventors: Roach, Adam Boyd, Campbell, Ben Allen, McMurry, Sam Eric
• Primary Examiner(s): ZHANG, SHIRLEY X
• Application Number:
  US13/863,351
• Publication Number:
  US 20130275583A1
• Time in Patent Office: 1,541 Days
• Field of Search: 709224
• CPC Class Codes: H04L 43/08 Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
• CPC Class Codes: H04L 43/0882 Utilisation of link capacity
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32

Abstract

According to one aspect, the subject matter described herein includes a system for performing Diameter overload control. The system occurs at a Diameter routing node. The system includes a network interface for receiving a Diameter message. The system also includes a Diameter overload control unit configured to detect an overload condition for a Diameter session associated with the Diameter message and to communicate an indication of the overload condition to a second Diameter node using a Diameter message defined for a purpose other than overload control.

Claims

1. A system for performing Diameter overload control, the system comprising:

a Diameter server configured to, prior to detecting an overload condition, assign Diameter sessions to overload groups and to communicate the assignments to a Diameter routing node using Diameter messages containing Diameter overload control information, wherein the Diameter overload control information indicates that a first plurality of Diameter sessions are assigned to a first overload group and that a second plurality of Diameter sessions are assigned to a second overload group; and

the Diameter routing node including;

at least one network interface for receiving a second Diameter message related to one of the plurality of Diameter sessions, and

a Diameter overload control unit configured to detect an overload condition associated with the second Diameter message and to communicate an indication of the overload condition to a plurality of Diameter nodes that originate the first plurality of Diameter sessions assigned to the first overload group using at least a third Diameter message defined for a purpose other than overload control.

2. The system of claim 1 wherein indication of the overload condition includes a Diameter overload scope.

3. The system of claim 2 wherein the Diameter overload scope includes one of a node, a realm, an application, a host, a group, a session, and a connection.

4. The system of claim 1 wherein the Diameter routing node comprises a Diameter agent, wherein the second Diameter message comprises a session establishment request originating from a Diameter client, wherein the Diameter agent detects the overload condition from the Diameter server providing service to the Diameter client.

5. The system of claim 1 wherein the Diameter routing node utilizes the overload groups assigned by the Diameter server in communicating the indication of the overload condition.

6. The system of claim 1 wherein the Diameter routing node assigns the sessions to overload groups that are different from the overload groups assigned by the Diameter server and uses the overload groups assigned by the Diameter routing node in communicating the indication of the overload condition.

7. The system of claim 1 wherein the Diameter agent assigns the sessions to overload groups.