Message handling extension using context artifacts

• US 8,923,204 B2
• Filed: 08/23/2012
• Issued: 12/30/2014
• Est. Priority Date: 05/29/2012
• Status: Active Grant

• Current Assignee: Alcatel-Lucent SA (Nokia Corporation)
• Original Assignee: Alcatel-Lucent SA (Nokia Corporation)
• Inventors: Jorgensen, Peter K., Mann, Robert A.
• Primary Examiner(s): Kizou, Hassan
• Assistant Examiner(s): DAYA, TEJIS A
• Application Number:
  US13/593,087
• Publication Number:
  US 20140056214A1
• Time in Patent Office: 859 Days
• Field of Search: None
• US Class Current: 370/328
• CPC Class Codes: H04L 45/30 Routing of multiclass traffic
• CPC Class Codes: H04L 45/304 Route determination for signalling traffic
• CPC Class Codes: H04L 45/306 Route determination based on the nature of the carried application
• CPC Class Codes: H04L 45/308 Route determination based on user's profile, e.g. premium users
• CPC Class Codes: H04L 47/2475 for supporting traffic characterised by the type of applications
• CPC Class Codes: H04L 51/226 Delivery according to priorities
• CPC Class Codes: H04L 67/63 Routing a service request depending on the request content or context

Abstract

Various exemplary embodiments relate to a method and related network node including one or more of the following: identifying a context artifact, wherein the context artifact defines a context object type for use by the DRA; receiving a Diameter message at the DRA from an origin device; establishing a context object of the context object type defined by the context artifact; evaluating a rule that includes a context object reference, wherein the evaluation includes accessing the context object based on the context object reference; and transmitting a message based on the evaluation of the rule.

Claims

1. A method performed by a Diameter Routing Agent (DRA) for processing a Diameter message, the method comprising:

identifying a context artifact, wherein the context artifact defines a context object type for use by the DRA;

receiving a Diameter message at the DRA from an origin device;

establishing a context object of the context object type defined by the context artifact;

evaluating a rule that includes a context object reference, wherein the evaluation includes accessing the context object based on the context object reference; and

transmitting a message based on the evaluation of the rule.

2. The method of claim 1, wherein the context artifact is a runtime library that defines a class of the context object.

3. The method of claim 1, wherein accessing the context object comprises retrieving an attribute defined by the context artifact.

4. The method of claim 1, wherein accessing the context object comprises invoking an action defined by the context artifact.

5. The method of claim 1, further comprising, prior to identifying the context artifact, receiving the context artifact via a user interface of the DRA.

6. The method of claim 1, further comprising:

locating an annotation in the context artifact; and

generating a component name for the context object type based on the annotation, wherein the component name refers to at least one of an attribute and an action of the context object type.

7. The method of claim 6, further comprising:

receiving, via the user interface, a rule definition that corresponds to the rule, wherein the rule definition includes a reference to the component name, and the reference to the component name corresponds to the context object reference.

8. A Diameter Routing Agent (DRA) for processing a Diameter message, the DRA comprising:

a context artifact storage configured to store a context artifact that defines a context object type;

a rule storage configured to store a rule that includes a context object reference;

a Diameter stack configured to receive a Diameter message from an origin device;

a context creator configured to establish a context object of the context object type defined by the context artifact;

a rule engine configured to evaluate the rule, wherein the evaluation includes accessing the context object based on the context object reference; and

a message handler configured to transmit, via the Diameter stack, a message based on the evaluation of the rule.

9. The DRA of claim 8, wherein the context artifact is a runtime library that defines a class of the context object.

10. The DRA of claim 8, wherein, in accessing the context object, the rule engine is configured to retrieve an attribute defined by the context artifact.

11. The DRA of claim 8, wherein, in accessing the context object, the rule engine is configured to invoke an action defined by the context artifact.

12. The DRA of claim 8, further comprising a user interface configured to:

receive the context artifact from a user; and

store the context artifact in the context artifact storage.

13. The DRA of claim 8, wherein the context creator is further configured to:

locate an annotation in the context artifact; and

generate a component name for the context object type based on the annotation, wherein the component name refers to at least one of an attribute and an action of the context object type.

14. The DRA of claim 13, further comprising a user interface configured to receive a rule definition that corresponds to the rule, wherein the rule definition includes a reference to the component name, and the reference to the component name corresponds to the context object reference.

15. A non-transitory machine-readable storage medium encoded with instructions for execution by a Diameter Routing Agent (DRA) for processing a Diameter message, the medium comprising:

instructions for identifying a context artifact, wherein the context artifact defines a context object type for use by the DRA;

instructions for receiving a Diameter message at the DRA from an origin device;

instructions for establishing a context object of the context object type defined by the context artifact;

instructions for evaluating a rule that includes a context object reference, including instructions for accessing the context object based on the context object reference; and

instructions for transmitting a message based on the evaluation of the rule.

16. The non-transitory machine-readable storage medium of claim 15, wherein the context artifact is a runtime library that defines a class of the context object.

17. The non-transitory machine-readable storage medium of claim 15, wherein the instructions for accessing the context object comprise instructions for invoking an action defined by the context artifact.

18. The non-transitory machine-readable storage medium of claim 15, further comprising instructions for, prior to identifying the context artifact, receiving the context artifact via a user interface of the DRA.

19. The non-transitory machine-readable storage medium of claim 15, further comprising:

instructions for locating an annotation in the context artifact; and

instructions for generating a component name for the context object type based on the annotation, wherein the component name refers to at least one of an attribute and an action of the context object type.

20. The non-transitory machine-readable storage medium of claim 19, further comprising:

instructions for receiving, via the user interface, a rule definition that corresponds to the rule, wherein the rule definition includes a reference to the component name, and the reference to the component name corresponds to the context object reference.