Methods, systems, and computer readable media for congestion management in a diameter signaling network
According to one aspect, the subject matter described herein includes a method for congestion management in a Diameter signaling network. The method occurs a Diameter routing node. The method includes determining, using a metric associated with Diameter message processing, that a first Diameter message processing metric threshold has been exceeded. The method also includes in response to determining that the first Diameter message processing metric threshold has been exceeded, performing a first congestion mitigation action, where performing the first congestion mitigation action includes analyzing subsequent Diameter messages to determine one or more common attributes of the subsequent Diameter messages and in response to determining the one or more common attributes of the subsequent Diameter messages, performing a second congestion mitigation action for Diameter messages having the one or more common attributes.
1. A method for managing congestion in a Diameter signaling network, the method comprising:
at a Diameter routing node:
processing and routing a plurality of received Diameter messages;
determining, using a metric associated with Diameter message processing, that a first Diameter message processing metric threshold has been exceeded;
in response to determining that the first Diameter message processing metric threshold has been exceeded, performing a first congestion mitigation action, wherein performing the first congestion mitigation action includes:
analyzing subsequent Diameter messages to determine one or more common attributes of the subsequent Diameter messages, wherein analyzing the subsequent Diameter messages to determine the one or more common attributes of the subsequent Diameter messages includes determining that the subsequent Diameter messages include a same value for one or more Diameter attribute-values pairs (AVPs);
in response to determining the one or more common attributes of the subsequent Diameter messages, performing a second congestion mitigation action for Diameter messages having the one or more common attributes, wherein the second congestion mitigation action mitigates congestion associated with the Diameter messages having the one or more common attributes by discarding at least some of the Diameter messages having the one or more common attributes and transmitting messages to originating nodes of the discarded messages;
determining whether the metric associated with Diameter message processing has fallen below a second Diameter message processing metric threshold, wherein the second Diameter message processing metric threshold has a different value than the first Diameter message processing metric threshold; and
in response to determining that the metric associated with Diameter message processing has fallen below the second Diameter message processing metric threshold, ceasing the second congestion mitigation action.
2. The method of claim 1 wherein the metric associated with Diameter message processing includes an ingress rate of Diameter signaling messages to the Diameter routing node, an egress rate of Diameter signaling messages from the Diameter routing node, a message processing queue depth associated with the Diameter routing node, a processor utilization metric associated with the Diameter routing node, a failed transaction volume metric associated with the Diameter routing node, or a rate of communication of Diameter messages.
3. The method of claim 1 wherein discarding at least some of the Diameter messages having the one or more common attributes includes discarding Diameter Request messages having the one or more common attributes, wherein sending messages to the originators of the discarded messages includes sending Diameter Answer messages associated with the discarded Diameter Request messages.
4. The method of claim 1 wherein performing the second congestion mitigation action includes performing the second congestion mitigation action using a white list or black list.
5. The method of claim 1 wherein the Diameter routing node comprises a Diameter signaling router (DSR).
6. The method of claim 5 wherein discarding at least some of the Diameter messages includes discarding the messages based on predefined Diameter message criteria.
7. The method of claim 6 wherein the predefined Diameter message criteria include a Diameter AVP value.
8. A system for managing congestion in a Diameter signaling network, the system comprising:
a Diameter signaling node, the Diameter signaling node comprising:
at least one processor; and
at least one memory, wherein the at least one processor is configured to, by executing instructions stored in the at least one memory:
process and route a plurality of Diameter messages;
determine, using a metric associated with Diameter message processing, that a first Diameter message processing metric threshold has been exceeded;
perform a first congestion mitigation action in response to determining that the first Diameter message processing metric threshold has been exceeded, wherein performing the first congestion mitigation includes analyzing subsequent Diameter messages to determine one or more common attributes of the subsequent Diameter messages, wherein analyzing the subsequent Diameter messages to determine the one or more common attributes of the subsequent Diameter messages includes determining that the subsequent Diameter messages include a same value for one or more Diameter attribute-values pairs (AVPs), and in response to determining the one or more common attributes of the subsequent Diameter messages, performing a second congestion mitigation action for Diameter messages having the one or more common attributes, wherein the second congestion mitigation action mitigates congestion associated with the Diameter messages having the one or more common attributes by discarding at least some of the Diameter messages having the one or more common attributes and transmitting messages to originating nodes of the discarded messages;
determine whether the metric associated with Diameter message processing has fallen below a second Diameter message processing metric threshold, wherein the second Diameter message processing metric threshold has a different value than the first Diameter message processing metric threshold; and
in response to determining that the metric associated with Diameter message processing has fallen below the second Diameter message processing metric threshold, cease the second congestion mitigation action.
9. The system of claim 8 wherein the metric associated with Diameter message processing includes an ingress rate of Diameter signaling messages to the Diameter routing node, an egress rate of Diameter signaling messages from the Diameter routing node, a message processing queue depth associated with the Diameter routing node, a processor utilization metric associated with the Diameter routing node, a failed transaction volume metric associated with the Diameter routing node, or a rate of communication of Diameter messages.
10. The system of claim 8 wherein discarding at least some of the Diameter messages having the one or more common attributes includes discarding Diameter Request messages having the one or more common attributes, wherein sending messages to the originators of the discarded messages includes sending Diameter Answer messages associated with the discarded Diameter Request messages.
11. The system of claim 10 wherein discarding at least some of the Diameter messages includes discarding the messages based on predefined Diameter message criteria.
12. The system of claim 11 wherein the predefined Diameter message criteria include a Diameter AVP value.
13. The system of claim 8 wherein the congestion management module is configured to perform the second congestion mitigation action using a white list or black list.
14. The system of claim 8 wherein the Diameter routing node comprises a Diameter signaling router (DSR).
15. The system of claim 14 wherein the at least one processor includes a plurality of message processors for routing Diameter signaling messages, wherein the determining, using the metric associated with Diameter message processing, that a first Diameter message processing metric threshold has been exceeded is implemented on each of the message processors.
16. The system of claim 15 wherein first and second congestion mitigation actions are implemented on each of the message processors.
17. A non-transitory computer readable medium having stored thereon executable instructions that when executed by the processor of a computer control the computer to perform steps comprising:
at a Diameter routing node:
processing and routing a plurality of received Diameter messages;
determining, using a metric associated with Diameter message processing, that a first Diameter message processing metric threshold has been exceeded;
in response to determining that the first Diameter message processing metric threshold has been exceeded, performing a first congestion mitigation action, wherein performing the first congestion mitigation action includes:
analyzing subsequent Diameter messages to determine one or more common attributes of the subsequent Diameter messages, wherein analyzing the subsequent Diameter messages to determine the one or more common attributes of the subsequent Diameter messages includes determining that the subsequent Diameter messages include a same value for one or more Diameter attribute-values pairs (AVPs);
in response to determining the one or more common attributes of the subsequent Diameter messages, performing a second congestion mitigation action for Diameter messages having the one or more common attributes, wherein the second congestion mitigation action mitigates congestion associated with the Diameter messages having the one or more common attributes by discarding at least some of the Diameter messages having the one or more common attributes and transmitting messages to originating nodes of the discarded messages;
determining whether the metric associated with Diameter message processing has fallen below a second Diameter message processing metric threshold, wherein the second Diameter message processing metric threshold has a different value than the first Diameter message processing metric threshold; and
in response to determining that the metric associated with Diameter message processing has fallen below the second Diameter message processing metric threshold, ceasing the second congestion mitigation action.