METHODS, SYSTEMS, AND COMPUTER READABLE MEDIA FOR DIAMETER APPLICATION LOOP PREVENTION

• US 20110202614A1
• Filed: 02/11/2011
• Published: 08/18/2011
• Est. Priority Date: 02/12/2010
• Status: Active Grant

• Current Assignee: Tekelec
• Original Assignee: Tekelec
• Inventors: Graig, Jeffrey Alan, Wallace, Donald E, Kanode, Mark Edward, McCann, Thomas M.
• Granted Patent: US 8,504,630 B2
• Time in Patent Office: Days
• US Class Current: 709/206
• CPC Class Codes: H04L 43/0805 by checking availability
• CPC Class Codes: H04L 45/028 Dynamic adaptation of the update intervals, e.g. event-triggered updates
• CPC Class Codes: H04L 45/28 using route fault recovery
• CPC Class Codes: H04L 45/304 Route determination for signalling traffic
• CPC Class Codes: H04L 45/34 Source routing
• CPC Class Codes: H04L 45/60 Router architectures
• CPC Class Codes: H04L 63/0892 by using authentication-authorization-accounting [AAA] servers or protocols
• CPC Class Codes: H04L 69/08 Protocols for interworking; Protocol conversion

Abstract

According to one aspect, the subject matter described herein includes a method for providing Diameter application loop prevention. The method includes steps occurring at a first Diameter node. The method further includes receiving a first Diameter message that is to be sent to a destination. The method also includes determining whether the first Diameter message requires processing by a Diameter application. The method includes, in response to determining that the first Diameter message requires processing by the Diameter application, determining whether the first Diameter message has been processed by the Diameter application. The method further includes, in response to determining that the first Diameter message has been processed by the Diameter application, preventing the first Diameter message from being sent to the Diameter application for processing.

Claims

1. A method for providing Diameter application loop prevention, the method comprising:

at a first Diameter node;

receiving a first Diameter message that is to be sent to a destination;

determining whether the first Diameter message requires processing by a Diameter application;

in response to determining that the first Diameter message requires processing by the Diameter application, determining whether the first Diameter message has been processed by the Diameter application; and

in response to determining that the first Diameter message has been processed by the Diameter application, preventing the first Diameter message from being sent to the Diameter application for processing.

2. The method of claim 1 comprising:

determining whether the first Diameter message requires processing by a second Diameter application;

in response to determining that the first Diameter message requires processing by the second Diameter application, determining whether the first Diameter message has been processed by the second Diameter application; and

in response to determining that the first Diameter message has been processed by the second Diameter application, preventing the first Diameter message from being sent to the second Diameter application for processing.

3. The method of claim 1 comprising:

routing the first Diameter message to the destination.

4. The method of claim 1 wherein the first Diameter node is a Diameter signaling router (DSR) and wherein the DSR includes multiple processors for performing Diameter application loop prevention.

5. The method of claim 1 wherein determining whether the first Diameter message has been processed by the Diameter application includes determining whether the first Diameter message contains application status information.

6. The method of claim 5 wherein the application status information includes information for indicating that a Diameter message has been processed by a Diameter application.

7. The method of claim 5 wherein the application status information includes a Diameter attribute value pair (AVP) and wherein the Diameter AVP includes a unique identifier for identifying the Diameter application.

8. The method of claim 7 wherein the Diameter AVP is a Diameter Route Record AVP and the unique identifier is a fully qualified domain name (FQDN).

9. The method of claim 7 wherein the Diameter AVP is a vendor specific AVP.

10. The method of claim 5 comprising, in response to determining that the first Diameter message does not contain the application status information, providing a second Diameter message to the application.

11. The method of claim 10 wherein the second Diameter message comprises a copy of the first Diameter message, the first Diameter message, a modified first Diameter message, the first Diameter message modified to include the application status information, a new Diameter message, a new Diameter message including information contained in the first Diameter message, or a new Diameter message including information contained in the first Diameter message and the application status information.

12. The method of claim 10 comprising:

at a second Diameter node executing the Diameter application;

receiving the second Diameter message; and

processing, by the Diameter application, the second Diameter message.

13. The method of claim 12 comprising, in response to processing the second Diameter message, sending a third Diameter message to the destination, a third Diameter node, or the first Diameter node.

14. The method of claim 13 wherein the third Diameter message comprises a copy of the second Diameter message, the second Diameter message, a modified second Diameter message, the second Diameter message modified to include application information, the second Diameter message modified to include application information and the application status information, the second Diameter message modified to include application information and lack the application status information, a new Diameter message, a new Diameter message including information contained in the second Diameter message, a new Diameter message including information contained in the second Diameter message and application information, a new Diameter message including information contained in the second Diameter message, application information, and the application status information, or a new Diameter message including information contained in the second Diameter message, application information, and lacking the application status information.

15. The method of claim 13 wherein the first, second, and third Diameter nodes and the destination each comprises a Diameter signaling router (DSR), a Diameter relay agent, a Diameter redirect agent, a Diameter translation agent, a Diameter proxy agent, a mobility management entity (MME), a home subscriber server (HSS) and/or authentication, authorization, and accounting (AAA) server, a Bearer Binding and Event Reporting Function (BBERF), a serving gateway (SGW), a packet data network gateway (PDN GW), a policy charging enforcement function (PCEF), a policy charging and rules function (PCRF), a subscriber profile repository (SPR), a Diameter agent, a network node, a policy engine, a policy server, an application function (AF), an application server, a Diameter signaling agent, a long term evolution (LTE) node, an Internet protocol (IP) multimedia subsystem (IMS) network node, a server, a node, a database, or a computing platform.

16. The method of claim 14 wherein the application status information and the application information each include attribute value pair (AVP) information, parameter information, value information, message header information, or message payload information.

17. A system for providing Diameter application loop prevention, the system comprising:

a first Diameter node including;

a communications interface for receiving a first Diameter message that is to be sent to a destination; and

a screening module for determining whether the first Diameter message requires processing by a Diameter application, for, in response to determining that the first Diameter message requires processing by the Diameter application, determining whether the first Diameter message has been processed by the Diameter application, and for, in response to determining that the first Diameter message has been processed by the Diameter application, preventing the first Diameter message from being sent to the Diameter application for processing.

18. The system of claim 17 wherein the first screening module is further configured for determining whether the first Diameter message requires processing by a second Diameter application, for, in response to determining that the first Diameter message requires processing by the second Diameter application, determining whether the first Diameter message has been processed by the second Diameter application, and for, in response to determining that the first Diameter message has been processed by the second Diameter application, preventing the first Diameter message from being sent to the second Diameter application for processing.

19. The system of claim 17 wherein the first Diameter node is a Diameter signaling router (DSR) and wherein the DSR includes multiple processors for performing Diameter application loop prevention.

20. The system of claim 17 wherein the first Diameter node is configured for sending the first Diameter message to the destination.

21. The system of claim 17 wherein determining whether the first Diameter message has been processed by the Diameter application includes determining whether the first Diameter message contains application status information.

22. The system of claim 21 wherein application status information includes information for indicating whether a Diameter message has been processed by a Diameter application.

23. The system of claim 21 wherein the application status information includes a Diameter attribute value pair (AVP) and wherein the Diameter AVP includes a unique identifier for identifying the Diameter application.

24. The system of claim 23 wherein the Diameter AVP is a Diameter Route Record AVP and the unique identifier is a fully qualified domain name (FQDN).

25. The system of claim 23 wherein the Diameter AVP is a vendor specific AVP.

26. The system of claim 21 wherein the screening module is configured for, in response to determining that the first Diameter message does not contain the application status information, providing a second Diameter message to the application.

27. The system of claim 26 wherein the second Diameter message comprises a copy of the first Diameter message, the first Diameter message, a modified first Diameter message, the first Diameter message modified to include the application status information, a new Diameter message, a new Diameter message including information contained in the first Diameter message, or a new Diameter message including information contained in the first Diameter message and the application status information.

28. The system of claim 26 comprising:

a second Diameter node, the second Diameter node comprising;

a communications interface for receiving the second Diameter message; and

the Diameter application for processing the second Diameter message.

29. The system of claim 28 wherein processing the second Diameter message includes sending a third Diameter message to the destination, a third Diameter node, or the first Diameter node.

30. The system of claim 29 wherein the third Diameter message comprises a copy of the second Diameter message, the second Diameter message, a modified second Diameter message, the second Diameter message modified to include application information, the second Diameter message modified to include application information and the application status information, the second Diameter message modified to include application information and lack the application status information, a new Diameter message, a new Diameter message including information contained in the second Diameter message, a new Diameter message including information contained in the second Diameter message and application information, a new Diameter message including information contained in the second Diameter message, application information, and the application status information, or a new Diameter message including information contained in the second Diameter message, application information, and lacking the application status information.

31. The system of claim 29 wherein the first, second, and third Diameter nodes and the destination each comprises a Diameter signaling router (DSR), a Diameter relay agent, a Diameter redirect agent, a Diameter translation agent, a Diameter proxy agent, a mobility management entity (MME), a home subscriber server (HSS) and/or authentication, authorization, and accounting (AAA) server, a Bearer Binding and Event Reporting Function (BBERF), a serving gateway (SGW), a packet data network gateway (PDN GW), a policy charging enforcement function (PCEF), a policy charging and rules function (PCRF), a subscriber profile repository (SPR), a Diameter agent, a network node, a policy engine, a policy server, an application function (AF), an application server, a Diameter signaling agent, a long term evolution (LTE) node, an Internet protocol (IP) multimedia subsystem (IMS) network node, a server, a node, a database, or a computing platform.

32. The system of claim 30 wherein the application status information and the application information each includes attribute value pair (AVP) information, parameter information, value information, message header information, or message payload information.

33. 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 first Diameter node;

receiving a first Diameter message that is to be sent to a destination;

determining whether the first Diameter message requires processing by a Diameter application;

in response to determining that the first Diameter message requires processing by the Diameter application, determining whether the first Diameter message has been processed by the Diameter application; and

in response to determining that the first Diameter message has been processed by the Diameter application, preventing the first Diameter message from being sent to the Diameter application for processing.