RECEIVED MESSAGE CONTEXT OBJECTS

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

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

determining a message type of the Diameter message;

establishing a message context object based on the message type, wherein the message context object provides access to the Diameter message;

processing the Diameter message, wherein processing includes accessing the message context object; and

transmitting a message based on the processing.

2 . The method of claim 1 , wherein the determining the message type comprises extracting an identification of an application and an identification of a command from the Diameter message.

3 . The method of claim 1 , wherein establishing the message context object based on the message type comprises:

locating a message definition for the message type;

establishing the message context object based on the message definition; and

associating the message context object with the Diameter message.

4 . The method of claim 3 , further comprising, before establishing the message context object receiving, via a user interface, the message definition, wherein the message definition specifies a structure of Diameter messages having the message type.

5 . The method of claim 3 , wherein:

establishing the message context object based on the message type further comprises locating an extension definition associated with the message definition, and

establishing the message context object based on the message definition comprises establishing the message context object based on the message definition and the extension definition.

6 . The method of claim 5 , wherein the Diameter message is associated with an identification of a vendor and the extension definition is associated with the identification of the vendor.

7 . The method of claim 1 , wherein:

processing the Diameter message comprises accessing an action of the message context object, wherein the action modifies the Diameter message, and

transmitting a message based on the processing comprises transmitting the Diameter message to another device.

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

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

a message handler configured to determine a message type of the Diameter message;

a context creator configured to establish a message context object based on the message type, wherein the message context object provides access to the Diameter message; and

a processing engine configured to process the Diameter message, wherein processing includes accessing the message context object,

wherein the message handler is further configured to transmit a message based on the processing.

9 . The DRA of claim 8 , wherein, in determining the message type, the message handler is configured to extract an identification of an application and an identification of a command from the Diameter message.

10 . The DRA of claim 8 , further comprising a message dictionary storage configured to store a message definition for the message type, wherein, in establishing the message context object based on the message type, the context creator is configured to:

locate the message definition;

establish the message context object based on the message definition; and

associate the message context object with the Diameter message.

11 . The DRA of claim 10 , wherein the message dictionary storage is a user-defined dictionary storage, the DRA further comprising a user interface configured to, before the context creator establishes the message context object:

receive the message definition, wherein the message definition specifies a structure of Diameter messages having the message type; and

store the message definition in the user-defined dictionary.

12 . The DRA of claim 8 , further comprising an extension dictionary storage configured to store an extension definition associated with the message definition, wherein:

in establishing the message context object based on the message type, the context creator is further configured to locate the extension definition; and

in establishing the message context object based on the message definition, the context creator is configured to establish the message context object based on the message definition and the extension definition.

13 . The DRA of claim 12 , wherein the Diameter message is associated with an identification of a vendor and the extension definition is associated with the identification of the vendor.

14 . The DRA of claim 8 , wherein:

in processing the Diameter message, the engine is configured to access an action of the message context object, wherein the action modifies the Diameter message, and

in transmitting a message based on the processing, the message handler is configured to transmit the Diameter message to another device.

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 receiving a Diameter message at the DRA from an origin device;

instructions for determining a message type of the Diameter message;

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

instructions for determining a message type of the Diameter message;

instructions for establishing a message context object based on the message type, wherein the message context object provides access to the Diameter message;

instructions for processing the Diameter message, wherein processing includes accessing the message context object; and

instructions for transmitting a message based on the processing.

16 . The non-transitory machine-readable storage medium of claim 15 , wherein the instructions for determining the message type comprise instructions for extracting an identification of an application and an identification of a command from the Diameter message.

17 . The non-transitory machine-readable storage medium of claim 15 , wherein the instructions for establishing the message context object based on the message type comprise:

instructions for locating a message definition for the message type;

instructions for establishing the message context object based on the message definition; and

instructions for associating the message context object with the Diameter message.

18 . The non-transitory machine-readable storage medium of claim 17 , further comprising instructions for, before establishing the message context object receiving, via a user interface, the message definition, wherein the message definition specifies a structure of Diameter messages having the message type.

19 . The non-transitory machine-readable storage medium of claim 17 , wherein:

the instructions for establishing the message context object based on the message type further comprise instructions for locating an extension definition associated with the message definition, and

the instructions for establishing the message context object based on the message definition comprise instructions for establishing the message context object based on the message definition and the extension definition.

20 . The non-transitory machine-readable storage medium of claim 15 , wherein:

the instructions for processing the Diameter message comprise instructions for accessing an action of the message context object, wherein the action modifies the Diameter message, and

the instructions for transmitting a message based on the processing comprise instructions for transmitting the Diameter message to another device.