Patent application number | Description | Published |
20130326001 | 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: 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. | 12-05-2013 |
20130326085 | CUSTOM DIAMETER ATTRIBUTE IMPLEMENTERS - 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 includes an attribute-value pair (AVP) having a first value represented according to a first data type; establishing a context object in response to receiving the Diameter message; establishing, within the context object, a custom attribute object that corresponds to the AVP and provides access to at least a portion of the first value represented according to a second data type, wherein the second data type is different from the first data type; evaluating a rule that includes a context object reference, wherein the evaluation includes accessing the custom attribute object based on the context object reference; and transmitting a message based on the evaluation of the rule. | 12-05-2013 |
20150063130 | CUSTOMIZED DIAMETER PERFORMANCE METRICS - Various exemplary embodiments relate to a method performed by a Diameter node, the method including: receiving a Diameter message at the Diameter node; evaluating a custom metric rule to identify a metric to be collected; and collecting the metric related to the received Diameter message based upon the evaluation of the custom metric rule. | 03-05-2015 |
Patent application number | Description | Published |
20110302458 | FRAMEWORK FOR MANAGING FAILURES IN OUTBOUND MESSAGES - Various exemplary embodiments relate to a method and related network node including one or more of the following: receiving, at a policy and charging rules node (PCRN), a request from a requesting node for an establishment of a first service data flow (SDF); generating a first rule set for implementing the first SDF in response to the request; transmitting a first rule of the rule set to a first node for installation of the first rule; waiting for a period of time for a response from the first node; determining from the response whether installation of the first rule at the first node failed or succeeded; and if installation of the first rule succeeded, transmitting a second rule of the first rule set to a second node for installation of the second rule. | 12-08-2011 |
20120324297 | FRAMEWORK FOR MANAGING FAILURES IN OUTBOUND MESSAGES - Various exemplary embodiments relate to a method and related network node including one or more of the following: receiving, at a policy and charging rules node (PCRN), a request from a requesting node for an establishment of a first service data flow (SDF); generating a first rule set for implementing the first SDF in response to the request; transmitting a first rule of the rule set to a first node for installation of the first rule; waiting for a period of time for a response from the first node; determining from the response whether installation of the first rule at the first node failed or succeeded; and if installation of the first rule succeeded, transmitting a second rule of the first rule set to a second node for installation of the second rule. | 12-20-2012 |
20130237232 | HANDLING OF EVENT TRIGGER REGISTRATIONS ON BBERF DURING HAND-OVER - Various exemplary embodiments relate to a method performed by a policy and charging rules node of provisioning event triggers. The method may include: receiving, from a requesting node, a request to provision a set of event triggers on a primary gateway; forwarding, to the primary gateway, the set of event triggers; storing the set of event triggers in association with a session; detecting a handover of the session; determining a new primary gateway; and forwarding, to the new primary gateway, the set of event triggers. The method may further include: receiving a message; determining whether the message includes the same set of event triggers; if the message includes the same set of event triggers, refraining from sending the set of event triggers to the primary gateway; and if the message includes a different set of event triggers, forwarding the different set of event triggers to the primary gateway. | 09-12-2013 |
20130246602 | FRAMEWORK FOR MANAGING FAILURES IN OUTBOUND MESSAGES - Various exemplary embodiments relate to a method and related network node including one or more of the following: receiving, at a policy and charging rules node (PCRN), a request from a requesting node for an establishment of a first service data flow (SDF); generating a first rule set for implementing the first SDF in response to the request; transmitting a first rule of the rule set to a first node for installation of the first rule; waiting for a period of time for a response from the first node; determining from the response whether installation of the first rule at the first node failed or succeeded; and if installation of the first rule succeeded, transmitting a second rule of the first rule set to a second node for installation of the second rule. | 09-19-2013 |
20130322230 | AUTOMATIC CONNECTION RECOVERY - Various exemplary embodiments relate to a method and related network node including one or more of the following: selecting a connection of a plurality of connections; testing the selected connection to determine whether the selected connection is usable; and based on a determination that the selected connection is not usable: closing the selected connection and at least one additional connection of the plurality of connections, and reestablishing the selected connection and the at least one additional connection. | 12-05-2013 |