Alcatel Lucent

Provenance Asset Group LLC

Peter K Jorgensen

Robert Alexander Mann

Darryl Jaakkola

Mike Vihtari

Stephen Edgar Ellis

Mikael Vihtari

Robert A Mann

Various exemplary embodiments relate to a Diameter network device which may include a storage configured to store one or more global variables, a memory; and a processor. The processor may be configured to: establish an object within the memory representative of a global variable; configure the object to access fields of the global variable including a property of the network device which was modified; and access via the object an attribute for the global variable.

Using global variables to data-drive rule engine evaluation

Various exemplary embodiments relate to a method, network node, and machine-readable medium including one or more of the following: instructions for processing a received Diameter message according to a plurality of proxylets; and instructions for defining a plug-in framework as a proxylet of the plurality of proxylets, including: instructions for retrieving a plug-in chain identifying a sequence of plug-ins; instructions for determining a current plug-in based on the plug-in chain; and instructions for evaluating plug-in instructions associated with a current plug-in.

Diameter routing agent application plug-in framework

Various exemplary embodiments relate to a method of routing Diameter requests. The method includes: receiving an initial request from a client, the initial request including a session identifier, an initial destination realm, and request content; determining a Diameter route for the initial request based on the destination realm and the request content; forwarding the initial request according to the Diameter route; receiving a response to the initial request; extracting an origin realm or host from the response; and storing the origin realm or host in association with the session identifier. Various exemplary embodiments relate a Diameter Routing Agent (DRA) configured to perform the above method. Various exemplary embodiments relate to a non-transitory machine-readable storage medium encoded with instructions for performing the method.

DRA destination mapping based on diameter answer message

Various exemplary embodiments relate to a method and related network node including one or more of the following: receiving a first Diameter message at the DRA; evaluating a first rule, including accessing data from a generic binding context object including: locating a record associated with a key specified by the first rule, and retrieving the data from the record; and transmitting a message based on the evaluation of the first rule. Various embodiments additionally relate to receiving a second Diameter message at the DRA; and evaluating a second rule, including accessing the generic binding context object, including storing the data in the record associated with the key.

Generic persistence in a diameter routing agent

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.

Message handling extension using context artifacts

Various exemplary embodiments relate to a method and related network node including one or more of the following: receiving a Diameter message at the DRA from an origin device, wherein the Diameter message is associated with a subscriber; establishing a subscriber record context object in response to receiving the Diameter message, wherein the subscriber record context object is associated with a subscriber record of the subscriber; evaluating a rule that includes a context object reference, wherein the evaluation includes accessing the subscriber record context object based on the context object reference; and transmitting a message based on the evaluation of the rule.

Subscriber record context objects

Various exemplary embodiments relate to a method and related network node including one or more of the following: receiving a Diameter message at the DRA from an origin device; establishing a context object in response to receiving the Diameter message; 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.

Rule engine evaluation of context objects

Various exemplary embodiments relate to a method and related network node including one or more of the following: receiving, via a user interface of the DRA, a request to define a rule; retrieving metadata associated with a context object; determining that a component specified by the metadata is an enumerated type component; presenting, via the user interface, a first displayed component for the enumerated type component, wherein the first displayed component is associated with a numeric value; presenting, via the user interface, a second displayed component for the enumerated type component, wherein the second displayed component is associated with an alphanumeric value; and receiving, via the user interface, a rule definition, wherein receiving the rule definition comprises receiving a selection of at least one of the first displayed component and the second displayed component.

Multiple form enumerated attributes

Various exemplary embodiments relate to a method and related network node including one or more of the following: receiving a Diameter message at the DRA from an origin device; determining a received message type of the received Diameter message; determining an inverse message type based on the received message type; establishing an inverse message context object based on the inverse message type, wherein the inverse message context object provides access to a related Diameter message of the received Diameter message; processing the received Diameter message, wherein processing includes accessing the inverse message context object; and transmitting a message based on the processing.

Inverse message context objects

Various exemplary embodiments relate to a method and related network node including one or more of the following: receiving a Diameter message at the DRA from an origin device; establishing a routing decision context object in response to receiving the Diameter message, wherein the routing decision context object is associated with a destination device chosen to receive a previous message; evaluating a rule that includes a context object reference, wherein the evaluation includes accessing the routing decision context object based on the context object reference; and transmitting a message based on the evaluation of the rule.

Growing community of inventors

Nepean, Canada

Peter K Jorgensen