Source: https://patents.google.com/patent/US8527598
Timestamp: 2018-03-22 08:21:58
Document Index: 790970917

Matched Legal Cases: ['Application No. 11742894', 'Application No. 11742901', 'Application No. 11742905', 'Application No. 11742906', 'Application No. 11742909', 'Application No. 11742912', 'Application No. 11742921', 'Application No. 11742923']

US8527598B2 - Methods, systems, and computer readable media for answer-based routing of diameter request messages - Google Patents
Methods, systems, and computer readable media for answer-based routing of diameter request messages Download PDF
US8527598B2
US8527598B2 US13026112 US201113026112A US8527598B2 US 8527598 B2 US8527598 B2 US 8527598B2 US 13026112 US13026112 US 13026112 US 201113026112 A US201113026112 A US 201113026112A US 8527598 B2 US8527598 B2 US 8527598B2
US13026112
US20110202613A1 (en )
Methods, systems, and computer readable media for answer-based routing of Diameter request messages are disclosed. According to one method, a Diameter request message is received from a first Diameter node at a. A copy of at least a portion of the Diameter request message is cached at the DSR and the Diameter request message is routed to a second Diameter node. The DSR determines whether a predetermined condition associated with an answer to the first Diameter request message exists. In response to determining that the predetermined condition exists, the cached portion of the Diameter request message is retrieved, a Diameter request that includes the cached portion of the Diameter request message is generated, and the generated Diameter request message is routed.
This application claims the benefit of U.S. Provisional Patent Application Ser. No. 61/304,310, filed Feb. 12, 2010; the disclosure of which is incorporated herein by reference in its entirety.
The disclosures of each of the following commonly-owned, co-pending U.S. Patent Applications filed on Feb. 11, 2011 are hereby incorporated herein by reference in their entireties:
“Methods, Systems, and Computer Readable Media for Inter-Diameter-Message Processor Routing, ” (Ser. No. 13/025,968) (pending);
“Methods, Systems, and Computer Readable Media for Source Peer Capacity-Based Diameter Load Sharing,” (Ser. No. 13/026,031) (pending);
“Methods, Systems, and Computer Readable Media for Inter-Message Processor Status Sharing,” (Ser. No. 13/026,105) (pending);
“Methods, Systems, and Computer Readable Media for Providing Priority Routing at a Diameter Node,” (Ser. No. 13/026,060) (pending);
“Methods, Systems, and Computer Readable Media for Providing Peer Routing at a Diameter Node,” (Ser. No. 13/026,076) (pending);
“Methods, Systems, and Computer Readable Media for Providing Origin Routing at a Diameter Node,” (Ser. No. 13/026,081) (pending);
“Methods, Systems, and Computer Readable Media for Providing Local Application Routing at a Diameter Node,” (Ser. No. 13/026,098) (pending);
“Methods, Systems, and Computer Readable Media for Performing Diameter Answer Message-Based Network Management at a Diameter Signaling Router (DSR),” (Ser. No. 13/026,125) (pending);
“Methods, Systems, and Computer Readable Media for Multi-Interface Monitoring and Correlation of Diameter Signaling Information,” (Ser. No. 13/026,133) (pending);
“Methods, Systems, and Computer Readable Media for Diameter Protocol Harmonization,” (Ser. No. 13/026,144) (pending);
“Methods, Systems, and Computer Readable Media for Diameter Network Management,” (Ser. No. 13/026,153) (pending); and
“Methods, Systems, and Computer Readable Media for Diameter Application Loop Prevention,” (Ser. No. 13/026,162) (allowed).
The subject matter described herein relates to routing of Diameter messages. More specifically, the subject matter relates to methods, systems, and computer readable media for answer-based routing of Diameter request messages.
Diameter is an authentication, authorization, and accounting (AAA) protocol for computer networks, and is a successor to RADIUS. The Diameter base protocol is defined in IETF RFC 3588, the disclosure of which is incorporated by reference herein in its entirety. Diameter communications may use a request-answer message exchange. Diameter routing involves routing of request messages in one direction and answer messages in the reverse direction. However, Diameter routing does not use information learned from received Diameter answer messages or from non-receipt of expected Diameter answer messages to route request messages.
Accordingly, there exists a need for methods, systems, and computer readable media for answer-based routing of Diameter request messages.
Methods, systems, and computer readable media for answer-based routing of Diameter request messages are disclosed. According to one method, a Diameter request message is received from a first Diameter node at a. A copy of at least a portion of the Diameter request message is cached at the DSR and the Diameter request message is routed to a second Diameter node. The DSR determines whether a predetermined condition associated with an answer to the first Diameter request message exists. In response to determining that the predetermined condition exists, the cached portion of the Diameter request message is retrieved, a Diameter request that includes the cached portion of the Diameter request message is generated, and the generated Diameter request message is routed. Determining whether the predetermined condition exists may include determining whether a received Diameter answer message that correlates with the request message sent to the second Diameter node includes non-protocol 3xxx error indicator information. Determining whether a predetermined condition associated with an answer message exists may also include determining whether the answer message or the request message is lost. Determining whether the answer or request message is lost may include initiating a timer when the request message is sent to the second Diameter node. If an answer to the request message is not received before the timer reaches a predetermined value, then the answer or the request (or both) is determined to be lost. Determining whether a predetermined condition associated with an answer to the request message exists may also include receiving an answer message, and determining whether additional service information is required before responding to the request originator.
According to another aspect of the subject matter described herein, a system for answer-based routing of Diameter request messages is provided. The system includes a DSR. The DSR includes a Diameter message processor for receiving a Diameter request message from a first Diameter node. The DSR further includes a caching module that caches a copy of at least a portion of the Diameter answer message. The DSR further includes an answer message-based request routing module that is configured to route the Diameter request message to a second Diameter node, to determine whether an error condition associated with an answer to the first Diameter request message exists, and, response to determining that the error condition exists, the answer message-based routing module retrieves the cached portion of the Diameter request message, generates a Diameter request message that includes the cached portion of the Diameter request message, and routes the generated Diameter request message.
FIG. 1A is a block diagram of an exemplary Diameter signaling router for performing answer-based routing of Diameter request messages according to an embodiment of the subject matter described herein;
FIG. 1B illustrates an exemplary Diameter signaling router with a distributed internal architecture and that performs answer-based routing of diameter signaling messages according to an embodiment of the subject matter described herein;
FIG. 2 is a flow chart illustrating exemplary steps for answer-based routing of Diameter request messages according to an embodiment of the subject matter described herein;
FIG. 3 is a message sequence diagram illustrating an exemplary conditional-on-response “error” condition scenario as part of performing answer-based routing of Diameter request messages according to an embodiment of the subject matter described herein;
FIG. 4 is a flow chart illustrating exemplary steps for answer-based routing of Diameter request messages according to an embodiment of the subject matter described herein;
FIG. 5 is a message sequence diagram illustrating an exemplary conditional-on-response “non-error” condition scenario as part of answer-based routing of Diameter request messages according to an embodiment of the subject matter described herein; and
FIG. 6 is a message sequence diagram illustrating an exemplary conditional-on-response “non-error” condition scenario as part of answer-based routing of Diameter request messages according to an embodiment of the subject matter described herein.
FIG. 1A is a block diagram of an exemplary Diameter signaling router (DSR) for performing Diameter answer message-based routing of Diameter request messages according to embodiments of the subject matter described herein. DSR 100 may perform a variety of Diameter message routing functions and, therefore, may include functionality including a Diameter routing agent, Diameter translation agent, Diameter proxy agent, Diameter relay agent, and/or Diameter redirect agent. However, for the sake of simplicity, the term DSR will be used throughout the description of the subject matter disclosed herein to refer to an entity that performs these functions. Referring to FIG. 1A, DSR 100 may include a Diameter connection layer (DCL), Diameter routing layer (DRL), one or more applications, and one or more routing tables. Exemplary DRL capabilities may include: routing request messages to peers or local applications based on message content, discarding or rejecting Diameter request messages based on message content rules, peer congestion control, allowing an operator to access only the features and capacities that are purchased, and easier configuration. DSR 100 may support Relay Agent Diameter message routing and a variety of value-add services/applications. In order to support both application processing and core Diameter routing functions, DSR 100 may support two message routing tables: an application routing table (ART) and a peer routing table (PRT). Additionally, the subject matter described herein for performing Diameter answer-based routing of Diameter request messages may be designed with the assumption that answer messages or routed request messages will be lost and, therefore, effectively handle lost answer or request messages in order to avoid wasting memory or other resources to maintain pending transaction records for transactions that are no longer pending.
Diameter application layer (DAL) 102 may include applications 104. Exemplary applications 104 may include, but are not limited to, a Diameter client, Diameter server, translation agent, proxy agent, redirect agent, integrated monitoring application, Diameter message screening and filtering application, Diameter firewall application, and a load generator. Diameter application layer 102 may also include timer 106 and application data 108. DAL 102 may interface with Diameter message encode/decode library 110 for encoding and decoding Diameter messages.
Diameter message processor (MP) 122 may further include Diameter routing layer (DRL) 124. DRL 124 may be responsible for the following functions. DRL 124 may perform ingress and egress message looping detection and prevention. DRL 124 may route ingress messages to one or more local DSR applications based upon user-define rules. DRL 124 may reroute messages upon failures. DRL 124 may perform message routing based upon route priorities and weights. DRL 124 may perform message routing based upon user-defined message content. DRL 124 may perform message routing to peers with multiple transport connections. DRL 124 may manage peer transport connections (TPS). DRL 124 may throttle ingress messages based upon local DSR congestion. DRL 124 may detect and avoid peer congestion. DRL 124 may load balance peer connection load to meet transaction per second (TPS) constraints of Diameter message processor 122.
DRL 124 may include answer-based request routing module 126, event processing module 128, DRL rerouting module 130, answer routing module 132, routing data 134, and DRL timer task 136. Answer-based request routing module 126 may perform the operations described herein for answer-based routing of Diameter request messages.
Diameter connection layer (DCL) 138 may perform the following functions. DCL 138 may implement Diameter connection state machine 140 for each Diameter peer. DCL 138 may establish transport connections with Diameter peers and process Diameter peer-to-peer messages and related functionality. This may include capabilities exchange request/answer (CER/CEA), Diameter Watchdog request/answer (DWR/DWA), and Disconnect Peer request/answer (DPR/DPA). DCL 138 may interface with the DRL 124 by sending Diameter messages received from peers to DRL 124 using one or more message-based APIs. DCL 138 may send Diameter messages received from URL 124 to the appropriate peer. DCL 138 may notify DRL of peer transport connection and congestion status changes. DCL 138 may process configuration and maintenance requests from DSR OAM for transport configuration objects. DCL 138 may update MEAL data for transport configuration objects. DCL 138 may perform transport layer capacity control.
DCL 138 may include Diameter message dispatch module 140. DCL listener/initiator module 142. DCL timer task 144, and connection data 145.
DCL 138 may also include one or more IP transport tasks. For example, DCL 138 may include IP transport task 146 and 148, where each IP transport task includes a receiving thread and a transmitting thread. For example, IP transport task 146 includes Rx thread 150 and Tx thread 152 and IP transport task 148 includes Rx thread 154 and Tx thread 156. IP transport tasks 146 and 148 may each communicate with SCTP/TCP sockets for interfacing with an operating system. For example, IP transport task 146 may communicate with SCTP/TCP socket 158 and IP transport task 148 may communicate with SCTP/TCP socket 160. SCTP/TCP sockets 158 and 160 may be associated with OS 162.
For simplicity, DSR 100 illustrated in FIG. 1A includes a single message processor 122. This is one possible configuration of DSR 100, where a single message processor routes all Diameter signaling messages. However, DSR 100 may include plural message processors, each configured as message processor 122 illustrated in FIG. 1A. FIG. 1B illustrates such an embodiment. In FIG. 1B, DSR 100 includes a plurality of message processors 122A-D, each of which sends Diameter signaling messages to and receives Diameter signaling messages from a Diameter network. Message processors 122A-D may be connected through an internal network 162. Although each message processor 122A-D may include all of the components of message processor 122 illustrated in FIG. 1A, for simplicity, only answer-based message routing module 126 and message cache 105 are shown.
In operation, when a Diameter message arrives at one of message processors 122A-D, the message is routed based on Diameter signaling information in the message from the ingress message processor to the egress message processor, and from the egress message processor to the Diameter network. As will be described in detail below, each Diameter message processor 122A-D may perform the steps described herein for answer-based routing of Diameter request messages, which may in some instances over-ride or supplement the routing of Diameter messages based on Diameter signaling information.
FIG. 2 is a flow chart illustrating exemplary steps for answer-based routing of Diameter request according to an embodiment of the subject matter described herein. It may be appreciated that the exemplary scenario described in FIG. 2 includes a determination as to whether Diameter answer messages contain non-protocol 3xxx error information. However, routing of Diameter request messages by DSR 100 is not intended to be limited to only a non-protocol 3xxx error determination and may include determining whether Diameter messages include any error indicator information (e.g., Diameter transient failure 4xxx, Diameter permanent failure 5xxx) without departing from the scope of the subject matter described herein. Referring to FIG. 2, in step 200, a Diameter request message may be received at a DSR from a first Diameter node. For example, a request message associated with service A may be received by DSR 100 from a source Diameter peer node.
In step 202, a copy of at least a portion of the Diameter request message is cached at the DSR. For example, a portion of (or the entirety of) a Diameter request message may be stored in message cache 105 on DSR 100.
In step 204, Diameter request message is routed to a second Diameter node. For example, the request message may be forwarded, by DSR 100, to Diameter node 1 for performing service A.
In step 206, a Diameter answer message associated with the Diameter request message from the second node is received at the DSR. For example, DSR 100 may receive a Diameter answer message corresponding to the Diameter request message for service A.
In addition, one embodiment of DSR 100 may include DCL 138 and DRL 124 being hosted on different computers and/or multiple interacting instances of DCL 138 and DRL 124 (i.e., scalable DSR). As such, an additional step (not shown) may be performed between steps 206 and 208 during which DCL 138 may determine the location of the DRL 124 having the cached copy of the corresponding request message and forward the answer message to that instance of DRL 124. However, for simplicity of illustration and description, unless otherwise noted, embodiments described herein assumed a single instance of DRL 124 co-located with DCL 138.
In step 208, it is determined by answer-based request routing module 126 whether the received Diameter answer message contains non-protocol 3xxx error information. A non-protocol error is one that occurs at the base protocol level and may require per hop attention. Exemplary 3xxx error codes and their corresponding descriptions are listed below.
DIAMETER_COMMAND_UNSUPPORTED 3001
The request contained a Command-Code that the receiver did not recognize or support. This is used when a Diameter node receives an experimental command that it does not understand.
DIAMETER_UNABLE_TO_DELIVER 3002
This error is given when Diameter cannot deliver the message to the destination, either because no host within the realm supporting the required application was available to process the request, or because Destination-Host AVP was given without the associated Destination-Realm AVP.
DIAMETER_REALM_NOT_SERVED 3003
DIAMETER_TOO_BUSY 3004
This error must is used when a specific server is requested and it cannot provide the requested service.
DIAMETER_LOOP_DETECTED 3005
An agent detected a loop while trying to get the message to the intended recipient.
DIAMETER_REDIRECT_INDICATION 3006
A redirect agent has determined that the request could not be satisfied locally.
DIAMETER_APPLICATION UNSUPPORTED 3007
DIAMETER_INVALID_HDR_BITS 3008
DIAMETER_INVALID_AVP_BITS 3009
DIAMETER_UNKNOWN_PEER 3010
Returning to FIG. 2, if the received Diameter answer message does not contain non-protocol 3xxx error information, control proceeds to step 210 where the answer message may be processed normally. For example, if DSR 100 receives an answer message with error cause ‘Diameter_Too_Busy’ and the Origin-Host of the answer message equals the Destination-Host of the original request, DSR 100 may process the answer message normally. Alternatively, if DSR 100 receives an answer message with error cause ‘Diameter_Too_Busy’ and the Origin-Host of the answer message does not equal the Destination-Host of the original request, then DSR 100 may discard the answer message and attempt to re-route the request message according to the routeset used to route the original message. Additionally, in the event that a peer node transport failure or timeout is detected, DSR 100 may apply alternate routing of any pending transactions (for which DSR 100 had sent a request, but not received an answer message yet) according to the routeset used to route the original message. If an alternate route is not available when re-routing is attempted, DSR 100 may process the answer message normally.
If the received Diameter answer message contains non-protocol 3xxx error information, then control proceeds to step 212 where the Diameter request message's copy associated with the Diameter answer message is retrieved from message cache 105 by answer-based request routing module 126.
In step 214, the Diameter message copy is routed by answer-based request routing module 126. The Diameter message may be routed to the second Diameter node and after a configurable number of failed delivery attempts, to a third Diameter node. Alternatively, the Diameter message copy may be sent to a third Diameter node after detecting the error condition associated with the answer message. For example, the request message for service A may be forwarded to Diameter node 2 for performing service A. DSR 100 may allow the user to define a set of cause values which, when received, may result in alternate routing being attempted. The set of cause values may be found, for example, in the result-code attribute value pair (AVP) of the message.
In one embodiment, upon receiving an answer message responsive to a message sent by DSR 100, DSR 100 may add the original Hop-by-Hop ID from the request message to an answer message, forward the answer message to the original peer from which DSR 100 received the corresponding request message, and purge the corresponding request message. It may be appreciated that the user/operator may specify whether to make a copy of an answer message and route it to a specified Diameter destination.
In another embodiment, upon receiving an answer message for which DSR 100 has no pending transaction, DSR 100 may discard the message and, according to one possible embodiment, generate a UIM.
FIG. 3 is a message sequence diagram illustrating an exemplary conditional-on-response “error” condition scenario as part of performing answer-based routing of Diameter request messages according to an embodiment of the subject matter described herein. Referring to FIG. 3, DSR 100 and associated answer-based request routing module 126 may communicate with client Diameter node 300, server Diameter node 302A and server Diameter node 304A. For example, client Diameter node 300 may send Diameter request message 306 for service A to DSR 100. DSR 100 may cache a copy of at least a portion of the Diameter request message and route Diameter request message 308 for service A to server Diameter node 302A. Server Diameter node 302A may return Diameter answer message 310 that includes error information. At step 312, DSR 100 may analyze Diameter answer message 310 to determine whether Diameter answer message 310 includes non-protocol 3xxx error information. In the scenario shown, Diameter answer message 310 may be determined to include non-protocol 3xxx error information and, therefore, DSR 100 may retrieve the Diameter request message copy from the cache 105 and route Diameter request message 314 to server Diameter node 304A. In response, server Diameter node 304A may return Diameter answer message 316 (e.g., Answer message (non-error to client Diameter node 300. At step 318, DSR 100 may analyze the answer message and, in step 320, DSR 100 may forward Diameter answer message (non-error) 316 to client Diameter node 300.
FIG. 4 is a flow chart illustrating exemplary steps for performing Diameter answer-based routing of request messages according to an embodiment of the subject matter described herein. In the example illustrated in FIG. 4, information from a first answer message is cached and used to generate and route a new request message, as described above. However, the first answer message may not indicate an error condition, but may indicate that further or additional service information is required before sending an answer to the request originator. Referring to FIG. 4, in step 400, a first Diameter request message is received from a first Diameter node at a DSR. For example, DSR 100 may receive a Diameter request message for service A from a client Diameter node.
In step 402, the first Diameter request message is routed to a second Diameter node. For example, the Diameter request message for service A may be forwarded, by DSR 100, to Diameter node 1, which may be a server.
In step 404, a first Diameter answer message associated with the first Diameter request message from the second Diameter node is received at the DSR. For example, DSR 100 may receive a Diameter answer message from the Diameter server corresponding to the request message for service A.
In step 406, information contained in the first Diameter answer message is analyzed to determine whether additional service information is needed before answering the request originator. For example, the first Diameter request message may be a request for subscriber information from an HSS, and the first answer message may be an indication that the subscriber is not provisioned in the HSS. Accordingly, step 406 may include analyzing the first answer message to determine that a second Diameter request message to a second HSS is needed.
If no additional service information is determined to be needed, control proceeds to step 407 where the DSR sends an answer message to the request originator. If, in step 406, it is determined that additional service information is needed, control proceeds to step 408 where a copy of at least a portion of the first Diameter answer message is cached at the DSR. For example, DSR 100 may cache the answer message in message cache 105. In an embodiment in which the DCL and DRL layers are implemented on different computers, the DCL may determine the location of the DRL having the cached copy of the corresponding request message and may forward the answer message to that instance of the DRL. The DRL may then cache the answer message along with the corresponding request in its message cache 105.
In step 410, a second Diameter request message is generated, and, in step 412, the second Diameter request message is routed to a third Diameter node. For example, Diameter message B may be generated and forwarded to Diameter node 2, which in this example may be a new HSS.
In step 414, a second Diameter answer message associated with the second Diameter request message is received from the third Diameter node. For example, DSR 100 may receive Diameter answer message B. Continuing with the example, answer message B may be an update location answer message from the new HSS and may include the requested subscriber information.
In step 416, information from the first Diameter answer message copy and the second Diameter answer message are combined. For example, information from the first Diameter answer message that indicates that the subscriber is not provisioned in the first queried HSS and information from the second answer message indicating that the subscriber is provisioned in the second queried HSS along with the requested subscription information may be combined.
In step 418, a Diameter answer message containing the combined information is sent to the first Diameter node. For example, a Diameter answer message containing the non-serving HSS, serving HSS, and subscription information may be forwarded to the source Diameter peer node that sent the original Diameter request message.
FIG. 5 is a message sequence diagram illustrating an exemplary conditional-on-response “non-error” condition scenario as part of performing answer-based routing of Diameter request messages according to an embodiment of the subject matter described herein. The message flow in FIG. 5 provides an example of the processing described above with respect to FIG. 4. Referring to FIG. 5, DSR 100 may include message cache 105 and answer-based Diameter request routing module 126 as described above. In FIG. 5, client Diameter node 300 may send Diameter request message 500 for service A to DSR 100. DSR 100 may cache in message cache 105 a copy of at least a portion of the Diameter request message and forward Diameter request message 502 for service A to server Diameter node 302A. Server Diameter node 302A may return Diameter answer message 504.
At step 506, DSR 100 may analyze the information contained in Diameter answer message 504 and trigger a new request B message. For example, DSR 100 may determine that additional service is required before answering client Diameter node 300. Examples of additional processing include the above-described HSS example or an example where multiple different service nodes providing the same or different services are required to be queried before responding to a Diameter request originator.
In the scenario shown, DSR 100 may generate Diameter request message 508 for service B, which may be the same or a different service from service A. In response, server Diameter node 304B may return Diameter answer message (e.g., answer message (non-error)) 510 for service B. At step 512, DSR 100 may analyze Diameter answer message 510 and combine information from Diameter answer messages 504 and 510. DSR 100 may then send Diameter answer message 514 containing the combined information from Diameter answer messages 504 and 510 to client Diameter node 300.
FIG. 6 is a message sequence diagram illustrating an exemplary conditional-on-response “non-error” condition scenario as part of performing Diameter answer message-based routing at a DSR according to an embodiment of the subject matter described herein. Referring to FIG. 6, client Diameter node 300 may send Diameter request message 600 for service A to DSR 100.
At step 602, DSR 100 may store a copy of Diameter request message 600. At step 604, request A message may be routed and a response timer may be started. DSR 100 may then send Diameter request message 606 for service A to server Diameter node 302A.
At step 608, it may be determined whether the timer has expired without receiving a Diameter answer message for Diameter request message 606. If the timer has expired, at step 610, DSR 100 may retrieve a copy of Diameter request message 606 and select an alternate route to server Diameter node 302A to which Diameter request message 606 should be sent and record an indication that delivery to server Diameter node 302A was attempted and failed to limit redelivery attempts to server node 302A. DSR 100 may then send Diameter request message 612 to server Diameter node 304A. In response, server Diameter node 304A may return Diameter answer (e.g., answer A message (non-error)) message 614 to DSR 100. At step 616, DSR 100 may analyze answer B message and, at step 618, DSR 100 may forward Diameter answer A+B message (non-error) to client Diameter node 300.
In addition to the scenario described above, it may be appreciated that the loss of a request message sent by DSR 100 may be indistinguishable (e.g., treated the same) from the loss of an answer message sent to DSR 100 by a peer node. In the event of a lost request message, it may be appreciated that the peer node would never send an answer message.
Lost Answer Messages
When answer messages are lost prior to their receipt by DSR 100, the “pending transactions” associated with the lost answer messages may either be aborted (answer message sent to peer) or re-routed. Since DSR 100 cannot “detect” a lost answer message, nor can it query the remote status of a forwarded request message, it may predict with high probability that one has been lost.
One method may be time-based. If an answer has not been received in “X” seconds, then the answer message may be assumed to most likely be lost. The larger the value of “X”, the higher the probability of loss. In one embodiment, a DRL “Lost answer Timer” may be supported and operator-configurable. An exemplary default value for X may be 30 seconds. It may be appreciated that the value of X may also be application dependent. For example, if the “Lost answer Timer” is application specific and DSR 100 supports multiple applications, the value may be per-application specific. It may also be appreciated that when the “Lost answer Timer” expires, DRL 124 may abort the transaction (default) and send an answer message to an originator of the request indicating an error condition. In another embodiment, DRL 124 may re-route the transaction. Additionally, it may be appreciated that if a connection fails at DSR 100, and it is the only connection between DSR 100 and a peer node, then all pending answer messages for that connection may be deemed, by DSR 100, to be lost.
Processing Answer Messages from Redirect Agents
As discussed previously, a forwarded request message may be routed to a Redirect Agent which sends an answer message containing an ordered list of hosts for routing the message. The base Diameter specification states that the recipient of a redirect response may re-route a pending request message using Redirect-Host AVPs, but does not require the recipient to do so. Therefore, in one embodiment, rather than re-routing the original request message using the redirect routing information received, DSR 100 may be configured to backwards-route the redirect response. However, because backwards routing may not be supported by a downstream peer in all customer networks, in another possible embodiment, the answer message may be re-routed using Redirect-Host AVPs. It may be appreciated that the process for redirecting an answer message may be a DRL-configurable option. As such, an operator may configure DRL 124 to use backward propagation as the default option.
Routing Answer Messages to Unavailable/Congested Peers
When DRL 124 receives an answer message and the message cannot be immediately delivered because the transport layer queue for the peer is full or the peer is congested, then DRL 124 has two options: delay delivery of the message within DRL 124 or immediately discard the answer message.
Delaying delivery of the message within DRL 124 may include buffering answer messages for a configurable time-period X1. If the peer's status changes before the timer expires, then the buffered answer messages may be forwarded. If the timer expires and the peer is available, then an attempt may be made to forward the buffered answer message until the buffer is flushed or another blocking condition occurs (e.g., transport queue full). In order to prevent an answer message from being queued indefinitely, a “maximum answer message queue delay” may be supported (i.e., message aging) where the answer message may be discarded when the above mentioned maximum delay is exceeded. It may be appreciated that if the transport connection is blocked for an inordinate period of time, preventing any answer messages from being sent, the transport layer may be disconnected in order to clear the condition and trigger the peer to re-forward the messages in the pending transaction queue(s).
It will be appreciated that in some or all of the embodiments described above, the DSR may be adapted to record or log each occurrence of a Diameter answer message error-driven routing event. The DSR may include in such log entries information associated with the related routing action taken by the DSR. The DSR may provide this information Diameter answer-based routing event log information to a network operations center or other network administration system.
1. A method for answer-based routing of Diameter request messages, the method comprising:
receiving a first Diameter request message from a first Diameter node;
caching, at the DSR, a copy of at least a portion of the first Diameter request message;
routing the first Diameter request message to a second Diameter node;
determining whether a predetermined condition associated with an answer to the first Diameter request message exists; and
in response to determining that the predetermined condition exists:
retrieving the cached portion of the first Diameter request message;
generating a second Diameter request message that includes the cached portion of the first Diameter request message; and
routing the generated second Diameter request.
2. The method of claim 1 wherein routing the generated second Diameter request message includes at least one of: attempting to deliver the generated second Diameter request to the second Diameter node and sending the generated second Diameter request message to a third Diameter node.
3. The method of claim 1 wherein determining whether the predetermined condition exists includes receiving a Diameter answer message, correlating the answer message with the received first Diameter request message, and determining whether the Diameter answer message includes one of non-protocol 3xxx error indicator information, transient 4xxx error indicator information, and permanent 5xxx error indicator information.
4. The method of claim 1 wherein determining whether the predetermined condition exists includes initiating a timer with the first Diameter request message is routed and detecting that the timer has reached a predetermined value without receipt of an answer message that correlates with the routed first Diameter request message.
5. The method of claim 1 wherein determining whether the predetermined condition exists includes determining whether an operational connection exists between the DSR and the second Diameter node.
6. The method of claim 1 comprising receiving a Diameter answer message and discarding the received Diameter answer message in response to determining that no pending transaction exists at the DSR corresponding to the Diameter answer message.
7. The method of claim 1 comprising storing, at the DSR, Diameter answer message-based routing event log information that includes information associated with at least one occurrence of a detected Diameter answer message-based error condition.
8. The method of claim 7 comprising storing, with the Diameter answer message-based routing event log information at the DSR, routing action information that includes information associated with a routing action taken by the DSR.
9. The method of claim 8 comprising providing, by the DSR, the Diameter answer-based routing event log information to one of a network operations center or network administration system.
10. The method of claim 1 wherein determining predetermined condition exists includes receiving, at the DSR, a first Diameter answer message associated with the first Diameter request message from the second Diameter node, analyzing information contained in the first Diameter answer message, to determine whether additional service information is required before answering the first Diameter node, and, in response to determining that additional service information is required:
caching at least a portion of the information contained in the first Diameter answer message:
generating a second Diameter request message; and
routing the second Diameter request message to a third Diameter node;
receiving, at the DSR, a second Diameter answer message associated with the second Diameter request message from the third Diameter node;
combining the cached information from the first Diameter answer message copy with information from the second Diameter answer message; and
sending a Diameter answer message containing the combined information to the first Diameter node.
11. A system for answer-based routing of Diameter request messages, the system comprising:
a Diameter message processor for receiving a first Diameter request message from a first Diameter node;
a message cache for caching a copy of at least a portion of the first Diameter request message; and
an answer message-based request routing module for:
generating a second Diameter request message that includes the cached portion of the second Diameter request message; and
routing the generated Diameter request message.
12. The system of claim 11 wherein the answer-based request routing module is configured to attempt to route the generated second Diameter request message to one of: the second Diameter node and a third Diameter node.
13. The system of claim 11 wherein the answer-based request routing module is configured to receive a Diameter answer message, correlate the answer message with the received first Diameter request message, and determine whether the received first Diameter answer message includes one of non-protocol 3xxx error indicator information, transient 4xxx error indicator information, and permanent 5xxx error indicator information.
14. The system of claim 11 wherein the answer-based request routing module is configured to determine whether the predetermined condition exists by initiating a timer when the first Diameter request message is routed and detecting that the timer has reached a predetermined value without receipt of an answer message that correlates with the routed first Diameter request message.
15. The system of claim 11 wherein the answer-based request routing module is configured to determine whether an operational connection exists between the DSR and the second Diameter node.
16. The system of claim 11 wherein the Diameter message processor is configured to determine whether no Diameter answer message responsive to the first Diameter request message has been received by the DSR.
17. The system of claim 11 wherein the answer based request routing module is configured to receive a Diameter answer message and discard the received Diameter answer message in response to determining that no pending transaction exists at the DSR corresponding to the Diameter answer message.
18. The system of claim 11 wherein the caching module is configured to store Diameter answer message-based routing event log information that includes information associated with at least one occurrence of a detected Diameter answer message-based error condition.
19. The system of claim 18 wherein the caching module is configured to store, with the Diameter answer message-based routing event log information at the DSR, routing action information that includes information associated with a routing action taken by the DSR.
20. The system of claim 18 wherein the answer-based request routing module is configured to provide the Diameter answer-based routing event log information to one of a network operations center or network administration system.
21. The system of claim 11 wherein, in determining whether the predetermined condition exists, the answer-based request routing module is configured to:
analyze information contained in the first Diameter answer message to determine whether additional service information is required before answering the first Diameter node;
in response to Determining that additional service information is required:
caching at least a portion of the information contained in the first Diameter answer message;
generate a second Diameter request message;
route the second Diameter request message to a third Diameter node; and
receiving a second Diameter answer message;
combining the cached information from the first Diameter answer message with information from the second Diameter answer message; and
generating and routing to the first Diameter node, a third Diameter message including the combined information.
22. A non-transitory computer readable medium comprising computer executable instructions embodied in a non-transitory computer readable medium and when executed by a processor of a computer performs steps comprising:
at a Diameter signaling router (DSR)
routing the Diameter request message to a second Diameter node;
retrieving the cached portion of the first Diameter request message; and
routing the generated second Diameter request message.
US13026112 2010-02-12 2011-02-11 Methods, systems, and computer readable media for answer-based routing of diameter request messages Active 2031-03-20 US8527598B2 (en)
US13026112 US8527598B2 (en) 2010-02-12 2011-02-11 Methods, systems, and computer readable media for answer-based routing of diameter request messages
US14016000 US8996636B2 (en) 2010-02-12 2013-08-30 Methods, systems, and computer readable media for answer-based routing of diameter request messages
US14016000 Continuation US8996636B2 (en) 2010-02-12 2013-08-30 Methods, systems, and computer readable media for answer-based routing of diameter request messages
US20110202613A1 true US20110202613A1 (en) 2011-08-18
US8527598B2 true US8527598B2 (en) 2013-09-03
US13025968 Active 2031-12-30 US8478828B2 (en) 2010-02-12 2011-02-11 Methods, systems, and computer readable media for inter-diameter-message processor routing
US13026060 Active 2031-04-18 US8644324B2 (en) 2010-02-12 2011-02-11 Methods, systems, and computer readable media for providing priority routing at a diameter node
US13026098 Active 2031-05-23 US8483233B2 (en) 2010-02-12 2011-02-11 Methods, systems, and computer readable media for providing local application routing at a diameter node
US13026105 Active US9088478B2 (en) 2010-02-12 2011-02-11 Methods, systems, and computer readable media for inter-message processor status sharing
US13026153 Active 2031-05-19 US8498202B2 (en) 2010-02-12 2011-02-11 Methods, systems, and computer readable media for diameter network management
US13026144 Active 2031-07-16 US8532110B2 (en) 2010-02-12 2011-02-11 Methods, systems, and computer readable media for diameter protocol harmonization
US13026112 Active 2031-03-20 US8527598B2 (en) 2010-02-12 2011-02-11 Methods, systems, and computer readable media for answer-based routing of diameter request messages
US13026081 Active 2031-04-15 US8554928B2 (en) 2010-02-12 2011-02-11 Methods, systems, and computer readable media for providing origin routing at a diameter node
US13026031 Active 2031-08-18 US8601073B2 (en) 2010-02-12 2011-02-11 Methods, systems, and computer readable media for source peer capacity-based diameter load sharing
US13026162 Active 2031-10-21 US8504630B2 (en) 2010-02-12 2011-02-11 Methods, systems, and computer readable media for diameter application loop prevention
US13026125 Active 2032-05-11 US8792329B2 (en) 2010-02-12 2011-02-11 Methods, systems, and computer readable media for performing diameter answer message-based network management at a diameter signaling router (DSR)
US13932608 Active US8799391B2 (en) 2010-02-12 2013-07-01 Methods, systems, and computer readable media for inter-diameter-message processor routing
US14016000 Active US8996636B2 (en) 2010-02-12 2013-08-30 Methods, systems, and computer readable media for answer-based routing of diameter request messages
US14185438 Active US8995256B2 (en) 2010-02-12 2014-02-20 Methods, systems, and computer readable media for performing diameter answer message-based network management at a diameter signaling router (DSR)
US20140233430A1 (en) * 2013-02-18 2014-08-21 Tekelec, Inc. Methods, systems, and computer readable media for providing targeted services to telecommunications network subscribers based on information extracted from network signaling and data traffic
US6304273B1 (en) 1997-05-23 2001-10-16 France Telecom Process for depicting paths within a graphical representation of a network
US20020049901A1 (en) 2000-09-21 2002-04-25 Avici Systems, Inc. System and method for implementing source based and egress based virtual networks in an interconnection network
US20020051427A1 (en) 2000-09-21 2002-05-02 Avici Systems, Inc. Switched interconnection network with increased bandwidth and port count
US20020087723A1 (en) 2001-01-03 2002-07-04 Robert Williams Method and apparatus for performing priority-based flow control
US20040037278A1 (en) 1998-02-13 2004-02-26 Broadcom Corporation Load balancing in link aggregation and trunking
US20040042485A1 (en) 2002-03-27 2004-03-04 Alcatel Canada Inc. Method and apparatus for redundant signaling links
US20040098612A1 (en) 2002-11-07 2004-05-20 Mednovus, Inc. Authentication, authorization and accounting (diameter) protocol-based accounting method using batch processing
EP1465385A1 (en) 2003-03-31 2004-10-06 Lucent Technologies Inc. Method for common authentication and authorization across disparate networks
US20050099964A1 (en) 2003-11-10 2005-05-12 Tekelec Methods and systems for automatically populating network route table
US20050232407A1 (en) 2004-03-18 2005-10-20 Tekelec Methods, systems, and computer program products for organizing, managing, and selectively distributing routing information in a signaling message routing node
US20050232236A1 (en) 2004-04-14 2005-10-20 Tekelec Methods and systems for mobile application part (MAP) screening in transit networks
US20050246545A1 (en) 2002-09-13 2005-11-03 Richard Reiner Screening for illegitimate requests to a computer application
US20060045249A1 (en) 2004-08-26 2006-03-02 Li Xiang Y Call authorization and billing message routing capability
US20060101159A1 (en) 2004-10-25 2006-05-11 Alcatel Internal load balancing in a data switch using distributed network processing
US20060104210A1 (en) 2004-11-03 2006-05-18 Telefonaktiebolaget Lm Ericsson (Publ) Dynamic network management
US20060177007A1 (en) 2005-02-07 2006-08-10 Shahriar Vaghar Caching message information in an integrated communication system
US20060200670A1 (en) 2005-03-01 2006-09-07 Kuffel Irene H Method and apparatus for securely disseminating security server contact information in a network
US20060253563A1 (en) 2005-05-06 2006-11-09 Won-Jong Yang Network management system and method
US20070153995A1 (en) 2005-12-29 2007-07-05 Qian Fang Method of converting between radius message and diameter messages
US20070168421A1 (en) 2006-01-09 2007-07-19 Tekelec Methods, systems, and computer program products for decentralized processing of signaling messages in a multi-application processing environment
US7257636B2 (en) 2001-11-15 2007-08-14 Electronics And Telecommunication Research Institute Inter-working method of wireless internet networks (gateways)
US20070280447A1 (en) 2006-05-31 2007-12-06 Yigang Cai Ims gateway systems and methods
US20080167035A1 (en) 2007-01-08 2008-07-10 Research In Motion Limited Apparatus, and associated method, for providing an instance indentifier to a network database node of a mobile network
WO2008087633A2 (en) 2007-01-17 2008-07-24 Traffix Communication Systems Ltd. Method for statistics based performance optimization of regenerated code
US20080301162A1 (en) 2007-05-31 2008-12-04 Bank Of America Corporation Data conversion environment
US20080317247A1 (en) 2005-10-14 2008-12-25 Postdata Co., Ltd Apparatus and Method for Processing Eap-Aka Authentication in the Non-Usim Terminal
WO2009058067A1 (en) 2007-11-01 2009-05-07 Lm Ericsson Telefonaktiebolaget (Publ) Method and system for correlating authentication, authorization and accounting sessions
US20090138619A1 (en) 2001-10-16 2009-05-28 Schnizlein John M Method and apparatus for assigning network addresses based on connection authentication
US7567796B2 (en) 2005-02-04 2009-07-28 Nokia Corporation System and method of registering subscription characteristics using user identities
US7583963B2 (en) 2004-08-03 2009-09-01 Nokia Corporation User registration in a communication system
WO2009134265A1 (en) 2008-05-01 2009-11-05 Lucent Technologies Inc Message restriction for diameter servers
US7792981B2 (en) 1999-02-16 2010-09-07 Taylor Rebecca S Generic communications protocol translator
US20100265948A1 (en) 2009-04-16 2010-10-21 Alcatel-Lucent Canada Inc. Handling of received implicit null packets
US7822023B2 (en) 2002-05-16 2010-10-26 Nokia Corporation Routing data packets through a wireless network
CA2716544A1 (en) 2010-10-08 2010-12-15 Traffix Communication Systems Ltd. Method and system for providing network services
US20110060830A1 (en) * 2008-05-13 2011-03-10 Huawei Technologies Co., Ltd. Method, system and device for device capabilities exchange
US20110188397A1 (en) 2009-10-16 2011-08-04 Mccann Thomas M Methods, systems, and computer readable media for multi-interface monitoring and correlation of diameter signaling information
US7996007B2 (en) 2007-01-18 2011-08-09 Tekelec Methods, systems, and computer program products for routing a call from a 2G network to a dual mode 2G/session initiation protocol (SIP) device
US20110200047A1 (en) 2010-02-12 2011-08-18 Mccann Thomas M Methods, systems, and computer readable media for diameter protocol harmonization
US8170035B2 (en) 2003-05-08 2012-05-01 Qualcomm Incorporated Data frame processing
EP1847076B1 (en) 2004-12-17 2012-02-15 Tekelec Methods, systems, and computer program products for supporting database access in an internet protocol multimedia subsystem (IMS) network environment
US7894353B2 (en) 2007-02-14 2011-02-22 Huawei Technologies Co., Ltd. Method, apparatus, and system for diagnosing route in network based on diameter protocol
WO2011100629A2 (en) 2010-02-12 2011-08-18 Tekelec Methods, systems, and computer readable media for diameter network management
US20110199895A1 (en) 2010-02-12 2011-08-18 Mark Edward Kanode Methods, systems, and computer readable media for diameter network management
WO2011100609A2 (en) 2010-02-12 2011-08-18 Tekelec Methods, systems, and computer readable media for inter-message processor status sharing
WO2011100630A2 (en) 2010-02-12 2011-08-18 Tekelec Methods, systems, and computer readable media for diameter application loop prevention
WO2011100600A2 (en) 2010-02-12 2011-08-18 Tekelec Methods, systems and computer readable media for providing priority routing at a diameter node
WO2011100615A2 (en) 2010-02-12 2011-08-18 Tekelec Methods, systems, and computer readable media for performing diameter answer message-based network management at a diameter signaling router (dsr)
US20110202677A1 (en) 2010-02-12 2011-08-18 Jeffrey Alan Craig Methods, systems, and computer readable media for inter-message processor status sharing
US20110202614A1 (en) 2010-02-12 2011-08-18 Jeffrey Alan Graig Methods, systems, and computer readable media for diameter application loop prevention
WO2011100621A2 (en) 2010-02-12 2011-08-18 Tekelec Methods, systems, and computer readable media for multi-interface monitoring and correlation of diameter signaling information
US20110202684A1 (en) 2010-02-12 2011-08-18 Jeffrey Alan Craig Methods, systems, and computer readable media for inter-diameter-message processor routing
US20110202604A1 (en) 2010-02-12 2011-08-18 Jeffrey Alan Craig Methods, systems, and computer readable media for source peer capacity-based diameter load sharing
WO2011100626A2 (en) 2010-02-12 2011-08-18 Tekelec Methods, systems, and computer readable media for diameter protocol harmonization
US20110200054A1 (en) 2010-02-12 2011-08-18 Jeffrey Alan Craig Methods, systems, and computer readable media for providing local application routing at a diameter node
US20110199906A1 (en) 2010-02-12 2011-08-18 Mark Edward Kanode Methods, systems, and computer readable media for performing diameter answer message-based network management at a diameter signaling router (dsr)
WO2011100587A2 (en) 2010-02-12 2011-08-18 Tekelec Methods, systems, and computer readable media for inter-diameter-message processor routing
WO2011100594A2 (en) 2010-02-12 2011-08-18 Tekelec Methods, systems, and computer readable media for source peer capacity-based diameter load sharing
"Diameter Overview," referenced from www.ulticom.com/html/products/signalware-diameter-reference-guide.asp. (Publication Date Unknown).
"Digital Cellular Telecommunications System (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; IP Multimedia (IM) Subsystem CX and DX Interfaces; Signalling Flows and Message Contents (3GPP TS 29.228 Version 8.7.0 Release 8)," ETSI TS 129 228 v8.7.0 (Jan. 2010).
"Mapping Diameter Interfaces to Functionality in 3GPP/3GPP2 IMS Architecture," Whitepaper by Traffix Systems, pp. 1-10 (Copyright 2010).
"Next Generation Networks Load Balancing-The Key to NGN Control, Management, and Growth," Whitepaper by Traffix Systems, pp. 1-7 (Publication Date Unknown) (Downloaded from the Internet on Feb. 8, 2010).
"Next Generation Networks Load Balancing—The Key to NGN Control, Management, and Growth," Whitepaper by Traffix Systems, pp. 1-7 (Publication Date Unknown) (Downloaded from the Internet on Feb. 8, 2010).
"Traffix Diameter Gateway; Instant Diameter Connection to any Network Element," Traffix Systems, pp. 1-4 (Publication Date Unknown) (Downloaded from the Internet on Feb. 8, 2010).
"Traffix Diameter Load Balancer; Scaling the Diameter Control Plane," Traffix Systems, pp. 1-4 (Publication Date Unknown) (Downloaded from the Internet on Feb. 8, 2010).
"Universal Mobile Telecommunications Systems (UMTS); LTE; InterWorking Function (IWF) Between MAP Based and Diameter Based Interfaces (3GPP TS 29.305 Version 9.0.0 Release 9)," ETSI TS 129 305 V9.0.0 (Jan. 2010).
3GPP, "3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; 3GPP System to Wireless Local Area Network (WLAN) Interworking; Stage 3 (Release 9)," 3GPP TS 29.234 V9.0.0 (Dec. 2009).
3GPP, "3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Cx and Dx Interfaces Based on the Diameter Protocol; Protocol Details (Release 9)," 3GPP TS 29.229 V9.0.0 (Dec. 2009).
3GPP, "3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Diameter-based Protocols Usage and Recommendations in 3GPP (Release 8)," 3GPP TR 29.909 V8.1.2 (Jan. 2009).
3GPP, "3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Diameter-based Protocols Usage and Recommendations in 3GPP (Release 9)," 3GPP TR 29.909 V9.0.0 (Dec. 2009).
3GPP, "3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Evolved Packet System (EPS); Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) Related Interfaces Based on Diameter Protocol (Release 8)," ETSI TS 129.272 V8.3.0 (Jun. 2009).
3GPP, "3rd Generation Partnership Project; Technical Specification Group core Network and Terminals; Generic Authentication Architecture (GAA); Zh and Zn Interfaces Based on the Diameter Protocol; Stage 3 (Release 8)," 3GPP TS 29.109 V8.3.0 (Sep. 2009).
3GPP, "3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; IP Multimedia (IM) Subsystem Cx and Dx Interfaces; Signalling Flows and Message Contents (Release 9)," 3GPP TS 29.228 V9.0.0 (Dec. 2009).
3GPP, "3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; IP Multimedia (IM) Subsystem Sh Interface; Signalling Flows and Message Contents (Release 9)," 3GPP TS 29.328 V9.0.0 (Dec. 2009).
3GPP, "3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Numbering, Addressing and Identification (Release 8)," 3GPP TS 23.003 V8.6.0 (Sep. 2009).
3GPP, "3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Policy and Charging Control over Gx Reference Point (Release 9)," 3GPP TS 29.212 V9.1.0 (Dec. 2009).
3GPP, "3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Policy and Charging Control Over Rx Reference Point (Release 9)," 3GPP TS 29.214 V9.2.0 (Dec. 2009).
3GPP, "3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Policy Control Over Go Interface (Release 6)," 3GPP TS 29.207 V6.5.0 (Sep. 2005).
3GPP, "3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Sh Interface Based on the Diameter Protocol; Protocol Details (Release 9)," 3GPP TS 29.329 V9.0.0 (Dec. 2009).
3GPP, "3rd Generation Partnership Project; Technical Specification Group Service and System Aspects; Telecommunication Management; Charging Management; Charging Data Description for the IP Multimedia Subsystem (IMS) (Release 5)," 3GPP TS 32.225 V5.11.0 (Mar. 2006).
3GPP, "3rd Generation Partnership Project; Technical Specification Group Service and System Aspects; Telecommunication Management; Charging Management; Diameter Charging Applications (Release 9)," 3GPP TS 32.299 V9.2.0 (Dec. 2009).
3GPP, "3rd Generation Partnership Project; Technical Specification Group Service and System Aspects; Telecommunication Management; Charging Management; Online Charging System (OCS): Applications and Interfaces (Release 9)," 3GPP TS 32.296 V9.1.0 (Dec. 2009).
3GPP, "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Generic Authentication Architecture (GAA); Generic Bootstrapping Architecture (Release 9)," 3GPP TS 33.220 V9.2.0 (Dec. 2009).
3GPP, "3rd Generation Partnership, Project; Technical Specification Group Services and System Aspects; Policy and Charging Control Architecture (Release 9)," 3GPP TS 23.203 V9.3.0 (Dec. 2009).
Aboba et al., "Authentication, Authorization and Accounting (AAA) Transport Profile," Network Working Group, RFC 3539, pp. 1-39 (Jun. 2003).
Aboba et al., "The Network Access Identifier," Network Working Group, RFC 4282, pp. 1-17 (Dec. 2005).
Bhardwaj, "Roaming Hubbing & LTE," GSMA London, pp. 1-11 (May 19, 2009).
Calhoun et al., "Diameter Base Protocol," Network Working Group, RFC 3588, pp. 1-148 (Sep. 2003).
Calhoun et al., "Diameter Mobile IPv4 Application," Network Working Group, RFC 4004, pp. 1-50 (Aug. 2005).
Carlberg et al., "Diameter Priority Attribute Value Pairs," Diameter Maintenance and Extensions (DIME) Internet-Draft , pp. 1-6 (Oct. 19, 2009).
Carlberg et al., "Diameter Priority Attribute Value Pairs," Diameter Maintenance and Extensions (DIME) Internet-Draft <draft-carlberg-dime-priority-avps-00.txt>, pp. 1-6 (Oct. 19, 2009).
Communication of European Publication Number and Information on the Application of Article 67(3) EPC for European Patent Application No. 11742894.6 (Nov. 21, 2012).
Communication of European Publication Number and Information on the Application of Article 67(3) EPC for European Patent Application No. 11742901.9 (Nov. 21, 2012).
Communication of European Publication Number and Information on the Application of Article 67(3) EPC for European Patent Application No. 11742905.0 (Nov. 21, 2012).
Communication of European Publication Number and Information on the Application of Article 67(3) EPC for European Patent Application No. 11742906.8 (Nov. 21, 2012).
Communication of European Publication Number and Information on the Application of Article 67(3) EPC for European Patent Application No. 11742909.2 (Nov. 21, 2012).
Communication of European Publication Number and Information on the Application of Article 67(3) EPC for European Patent Application No. 11742912.6 (Nov. 21, 2012).
Communication of European Publication Number and Information on the Application of Article 67(3) EPC for European Patent Application No. 11742921.7 (Sep. 12, 2012).
Communication of European Publication Number and Information on the Application of Article 67(3) EPC for European Patent Application No. 11742923.3 (Nov. 21, 2012).
Eronen et al., "Diameter Extensible Authentication Protocol (EAP) Application," Network Working Group, RFC 4072, pp. 1-31 (Aug. 2005).
Fajardo et al., "Diameter Base Protocol," DIME Internet-Draft, draft-ietf-dime-rfc3588bis-19.txt, pp. 1-160 (Sep. 2, 2009).
Final Official Action for U.S. Appl. No. 13/026,076 (Dec. 7, 2012).
Final Official Action for U.S. Appl. No. 13/026,105 (Nov. 26, 2012).
Greene et al., "Bi-Directional Session Setup Extension to Diameter," Internet Draft , pbs. 1-12 (Jul. 1998).
Greene et al., "Bi-Directional Session Setup Extension to Diameter," Internet Draft <draft-greene-diameter-ss7-session-00.txt>, pbs. 1-12 (Jul. 1998).
Hakala et al., "Diameter Credit-Control Application," Network Working Group RFC 4006, pp. 1-107 (Aug. 2005).
Huang et al., "The Diameter Precongestion Notification (PCN) Data Collection Applications," Network Working Group Internet-Draft , pp. 1-19 (Oct. 26, 2009).
Huang et al., "The Diameter Precongestion Notification (PCN) Data Collection Applications," Network Working Group Internet-Draft <draft-huang-dime-pcn-collection-02>, pp. 1-19 (Oct. 26, 2009).
Interview Summary for U.S. Appl. No. 13/026,144 (Mar. 4, 2013).
Jiao et al., "The Diameter Capabilities Update Application," Network Working Group Internet-Draft draft-ieft-dime-capabilities-update-01, pp. 1-8 (Dec. 1, 2009).
Jones et al., "Diameter Extended NAPTR," Individual Submission Internet-Draft, draft-ietf-dime-extended-naptr-00, pp. 1-9 (Dec. 29, 2009).
Jones et al., "Diameter Extended NAPTR," Internet-Draft, draft-jones-dime-extended-naptr-00, pp. 1-8 (Aug. 23, 2009).
Korhonen et al., "Diameter User-Name and Realm Based Request Routing Clarifications," Diameter Maintenance and Extensions (DIME) Internet-Draft, draft-ietf-dime-nai-routing-04.txt, pp. 1-13 (Oct. 6, 2009).
Korhonen et al., "Diameter User-Name and Realm Based Request Routing Clarifications," Internet-Draft, draft-ietf-dime-nai-routing-03.txt, pp. 1-11 (Aug. 19, 2009).
Liu et al., "Introduction to Diameter," Developer Works http://www.ibm.com/developerworks/library/wi-diameter/index.html (Downloaded from the Internet on Aug. 2, 2011), pp. 1-9 (Jan. 24, 2006).
Non-Final Official Action for U.S. Appl. No. 13/026,060 (Sep. 19, 2012).
Non-Final Official Action for U.S. Appl. No. 13/026,076 (Jun. 4, 2012).
Non-Final Official Action for U.S. Appl. No. 13/026,081 (Sep. 12, 2012).
Non-Final Official Action for U.S. Appl. No. 13/026,098 (Sep. 20, 2012).
Non-Final Official Action for U.S. Appl. No. 13/026,105 (May 16, 2012).
Non-Final Official Action for U.S. Appl. No. 13/026,144 (Oct. 16, 2012).
Non-Final Official Action for U.S. Appl. No. 13/026,153 (Nov. 6, 2012).
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 13/025,968 (Feb. 27, 2013).
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 13/026,031 (Jan. 30, 2013).
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 13/026,098 (Mar. 11. 2013).
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 13/026,162 (Dec. 19, 2012).
Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration for International Application No. PCT/US2011/024588 (Oct. 20, 2011).
Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration for International Application No. PCT/US2011/024601 (Oct. 20, 2011).
Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration for International Application No. PCT/US2011/024611 (Oct. 20, 2011).
Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration for International Application No. PCT/US2011/024614 (Oct. 31, 2011).
Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration for International Application No. PCT/US2011/024617 (Oct. 31, 2011).
Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration for International Application No. PCT/US2011/024621 (Oct. 28, 2011).
Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration for International Application No. PCT/US2011/024622 (Oct. 31, 2011).
Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration for International Application No. PCT/US2011/024625 (Oct. 25, 2011).
Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration for International Application No. PCT/US2011/024629 (Oct. 27, 2011).
Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration for International Application No. PCT/US2011/024637 (Oct. 27, 2011).
Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration for International Application No. PCT/US2011/024642 (Oct. 28, 2011).
Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration for International Application No. PCT/US2011/024645 (Oct. 28, 2011).
Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration for International Application No. PCT/US2011/024646 (Oct. 28, 2011).
Stewart et al., "Stream Control Transmission Protocol," Network Working Group RFC 2960, pp. 1-134 (Oct. 2000).
Supplemental Notice of Allowability for U.S. Appl. No. 13/026,162 (Feb. 27, 2013).
Supplemental Notice of Allowability for U.S. Appl. No. 13/026,162 (Feb. 7, 2013).
Supplemental Notice of Allowability for U.S. Appl. No. 13/026,162 (Jan. 24, 2013).
Traffix Systems, "Datasheet; Traffix Signaling Delivery Controller (SDC)," pp. 1-5 (May 2011).
Tsou et al., "Realm-Based Redirection in Diameter," Internet Engineering Task Force, draft-ietf-dime-realm-based-redirect-02, pp. 1-7 (Oct. 27, 2009).
Tsou et al., "Session-Spectific Explicit Diameter Request Routing," Network Working Group Internet-Draft, draft-tsou-diameter-explicit-routing-03, pp. 1-18 (Aug. 5, 2009).
Znaty, "Diameter, GPRS, (LTE+ePC=EPS), IMS, PCC and SDM," EFORT, pp. 1-460 (May 2010).
US20140226495A1 (en) * 2010-02-12 2014-08-14 Tekelec, Inc. Methods, systems, and computer readable media for performing diameter answer message-based network management at a diameter signaling router (dsr)
US8995256B2 (en) * 2010-02-12 2015-03-31 Tekelec, Inc. Methods, systems, and computer readable media for performing diameter answer message-based network management at a diameter signaling router (DSR)
US20070230482A1 (en) 2007-10-04 Method for on demand distributed hash table update
US20020184376A1 (en) 2002-12-05 Scalable, reliable session initiation protocol (SIP) signaling routing node
US20110255410A1 (en) 2011-10-20 Congestion control method and devices
US20070110079A1 (en) 2007-05-17 Method and network nodes for reporting at least one dropped-out connection path withing a communication network
US20060002385A1 (en) 2006-01-05 Switching method and apparatus for use in a communications network
US20100036956A1 (en) 2010-02-11 Load balancing system
US20070223372A1 (en) 2007-09-27 Method and apparatus for preventing congestion in load-balancing networks
US20080101224A1 (en) 2008-05-01 Priority call routing
US20030023877A1 (en) 2003-01-30 System and method of managing data transmission loads
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:CRAIG, JEFFREY ALAN;KANODE, MARK EDWARD;MCCANN, THOMAS MATTHEW;AND OTHERS;SIGNING DATES FROM 20110221 TO 20110415;REEL/FRAME:026179/0150
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:CRAIG, JEFFREY ALAN;KANODE, MARK EDWARD;MCCANN, THOMAS MATTHEW;AND OTHERS;SIGNING DATES FROM 20110626 TO 20110801;REEL/FRAME:026762/0821