Source: http://www.google.nl/patents/US9106769
Timestamp: 2018-01-17 07:16:14
Document Index: 62810167

Matched Legal Cases: ['art 2013', 'art 2013', 'art 2014', 'art 2014', 'art 2012', 'art 2006', 'art 2008', 'art 2009', 'art 2009', 'art 2009', 'art 2011', 'art 2011', 'art 2011', 'art 2011', 'art 2012', 'art 2011', 'art 2011', 'art 2013', 'Application No. 13776083', 'Application No. 10841576', 'Application No. 10841576', 'Application No. 201080064945', 'art 1', 'art 1', 'art 2', 'art 2017']

Patent US9106769 - Methods, systems, and computer readable media for congestion management in a ... - Google Patenten
According to one aspect, the subject matter described herein includes a method for congestion management in a Diameter signaling network. The method occurs a Diameter routing node. The method includes determining, using a metric associated with Diameter message processing, that a first Diameter message...http://www.google.nl/patents/US9106769?utm_source=gb-gplus-sharePatent US9106769 - Methods, systems, and computer readable media for congestion management in a diameter signaling network
Publicatienummer US9106769 B2
Aanvraagnummer US 13/572,156
Publicatiedatum 11 aug 2015
Prioriteitsdatum 10 aug 2011
Ook gepubliceerd als US20130039176, US20130041994
Publicatienummer 13572156, 572156, US 9106769 B2, US 9106769B2, US-B2-9106769, US9106769 B2, US9106769B2
Uitvinders Mark Edward Kanode, Seetharaman Khadri, Peter J. Marsico
Patentcitaties (138), Niet-patentcitaties (81), Verwijzingen naar dit patent (11), Classificaties (13), Juridische gebeurtenissen (1)
US 9106769 B2
1. A method for managing congestion in a Diameter signaling network, the method comprising:
processing and routing a plurality of received Diameter messages;
determining, using a metric associated with Diameter message processing, that a first Diameter message processing metric threshold has been exceeded;
in response to determining that the first Diameter message processing metric threshold has been exceeded, performing a first congestion mitigation action, wherein performing the first congestion mitigation action includes:
analyzing subsequent Diameter messages to determine one or more common attributes of the subsequent Diameter messages, wherein analyzing the subsequent Diameter messages to determine the one or more common attributes of the subsequent Diameter messages includes determining that the subsequent Diameter messages include a same value for one or more Diameter attribute-values pairs (AVPs);
in response to determining the one or more common attributes of the subsequent Diameter messages, performing a second congestion mitigation action for Diameter messages having the one or more common attributes, wherein the second congestion mitigation action mitigates congestion associated with the Diameter messages having the one or more common attributes by discarding at least some of the Diameter messages having the one or more common attributes and transmitting messages to originating nodes of the discarded messages;
determining whether the metric associated with Diameter message processing has fallen below a second Diameter message processing metric threshold, wherein the second Diameter message processing metric threshold has a different value than the first Diameter message processing metric threshold; and
in response to determining that the metric associated with Diameter message processing has fallen below the second Diameter message processing metric threshold, ceasing the second congestion mitigation action.
2. The method of claim 1 wherein the metric associated with Diameter message processing includes an ingress rate of Diameter signaling messages to the Diameter routing node, an egress rate of Diameter signaling messages from the Diameter routing node, a message processing queue depth associated with the Diameter routing node, a processor utilization metric associated with the Diameter routing node, a failed transaction volume metric associated with the Diameter routing node, or a rate of communication of Diameter messages.
3. The method of claim 1 wherein discarding at least some of the Diameter messages having the one or more common attributes includes discarding Diameter Request messages having the one or more common attributes, wherein sending messages to the originators of the discarded messages includes sending Diameter Answer messages associated with the discarded Diameter Request messages.
4. The method of claim 1 wherein performing the second congestion mitigation action includes performing the second congestion mitigation action using a white list or black list.
6. The method of claim 5 wherein discarding at least some of the Diameter messages includes discarding the messages based on predefined Diameter message criteria.
7. The method of claim 6 wherein the predefined Diameter message criteria include a Diameter AVP value.
8. A system for managing congestion in a Diameter signaling network, the system comprising:
a Diameter signaling node, the Diameter signaling node comprising:
at least one memory, wherein the at least one processor is configured to, by executing instructions stored in the at least one memory:
process and route a plurality of Diameter messages;
determine, using a metric associated with Diameter message processing, that a first Diameter message processing metric threshold has been exceeded;
perform a first congestion mitigation action in response to determining that the first Diameter message processing metric threshold has been exceeded, wherein performing the first congestion mitigation includes analyzing subsequent Diameter messages to determine one or more common attributes of the subsequent Diameter messages, wherein analyzing the subsequent Diameter messages to determine the one or more common attributes of the subsequent Diameter messages includes determining that the subsequent Diameter messages include a same value for one or more Diameter attribute-values pairs (AVPs), and in response to determining the one or more common attributes of the subsequent Diameter messages, performing a second congestion mitigation action for Diameter messages having the one or more common attributes, wherein the second congestion mitigation action mitigates congestion associated with the Diameter messages having the one or more common attributes by discarding at least some of the Diameter messages having the one or more common attributes and transmitting messages to originating nodes of the discarded messages;
determine whether the metric associated with Diameter message processing has fallen below a second Diameter message processing metric threshold, wherein the second Diameter message processing metric threshold has a different value than the first Diameter message processing metric threshold; and
in response to determining that the metric associated with Diameter message processing has fallen below the second Diameter message processing metric threshold, cease the second congestion mitigation action.
9. The system of claim 8 wherein the metric associated with Diameter message processing includes an ingress rate of Diameter signaling messages to the Diameter routing node, an egress rate of Diameter signaling messages from the Diameter routing node, a message processing queue depth associated with the Diameter routing node, a processor utilization metric associated with the Diameter routing node, a failed transaction volume metric associated with the Diameter routing node, or a rate of communication of Diameter messages.
10. The system of claim 8 wherein discarding at least some of the Diameter messages having the one or more common attributes includes discarding Diameter Request messages having the one or more common attributes, wherein sending messages to the originators of the discarded messages includes sending Diameter Answer messages associated with the discarded Diameter Request messages.
11. The system of claim 10 wherein discarding at least some of the Diameter messages includes discarding the messages based on predefined Diameter message criteria.
12. The system of claim 11 wherein the predefined Diameter message criteria include a Diameter AVP value.
13. The system of claim 8 wherein the congestion management module is configured to perform the second congestion mitigation action using a white list or black list.
14. The system of claim 8 wherein the Diameter routing node comprises a Diameter signaling router (DSR).
15. The system of claim 14 wherein the at least one processor includes a plurality of message processors for routing Diameter signaling messages, wherein the determining, using the metric associated with Diameter message processing, that a first Diameter message processing metric threshold has been exceeded is implemented on each of the message processors.
16. The system of claim 15 wherein first and second congestion mitigation actions are implemented on each of the message processors.
Referring to FIG. 1, DSR 100 may include functionality for processing and/or routing various messages and may include various communications interfaces for communication with Diameter nodes, e.g., 3rd Generation Partnership Project (3GPP) LTE communications interfaces and other (e.g., non-LTE) communications interfaces. DSR 100 may include functionality for correlating and/or monitoring Diameter messages associated with one or more communications interfaces. In some embodiments, correlating and/or monitoring functionality may be included in one or more modules. For example, DSR 100 may include or have access to one or more screening modules 102 and one or more congestion management modules (CMMs) 104 for monitoring Diameter signaling messages and managing congestion associated with multiple different Diameter signaling interfaces, e.g., S9, S6a, Cx, and Dx.
Exemplary monitored metrics may include an ingress rate of Diameter signaling messages to DSR 100, an egress rate of Diameter signaling messages from DSR 100, a message processing queue depth associated with DSR 100, a processor utilization metric associated with DSR 100, a failed transaction volume metric associated with DSR 100, a rate of communication of Diameter messages, or a pending transaction volume metric. Screening modules may be aware of various metric thresholds that correspond to a monitored metric. For example, an ingress message per second (MPS) rate for Diameter request messages directed to DSR 100 could be monitored and a threshold for the metric may be 800 MPS. If a metric threshold is exceeded, screening module 102 may be configured to mark, identify, and/or initiate another module to perform a congestion mitigation action.
In some embodiments, Diameter traffic profiling may be applied to ingress Diameter message traffic, egress Diameter traffic, or all Diameter traffic. Traffic profiling statistics may be generated for a predetermined period of time, a predetermined number of Diameter messages, or based on another factor (e.g., until another threshold is exceeded).
After a Diameter traffic profile is generated, CMM 104 or another module may analyze the Diameter traffic profile. In some embodiments, the analysis seeks to identify attributes (e.g., attribute value pairs (AVPs)) that are common to some or all of the Diameter messages associated with the traffic profile. If common attributes are identified, CMM 104 may perform one or more congestion mitigation actions for zero or more (e.g., 50%) of all related Diameter messages (e.g., messages having the identified common attributes).
In some embodiments, a screening module 102 and a CMM 104 may be integrated at a single node or may each be located at distinct nodes. For example, a screening module 102 and a CMM 104 may be located at DSR 100. In another example, a screening module 102 may be located at DSR 100 and a CMM 104 may be located at a distinct computing platform. In yet example, a screening module 102 may be located at a link probe and a CMM 104 may be located at a distinct computing platform and/or node. In some embodiments, a screening module 102 and CMM 104 may be integrated into a single module or function. For example, CMM 104 may screen Diameter messages and manage congestion of a Diameter signaling network and may be located at numerous message processors of DSR 100.
In the embodiment illustrated in FIG. 1, DSR 100 may communicate with equipment identity register (EIR) 106 via a Diameter S13 interface 116. DSR 100 may also communicate with HSS 108 via a Diameter S6a interface, a Diameter S6d interface, a Diameter Cx interface, or a Diameter Dh interface (collectively referred to herein as an HSS interface 118). DSR 100 may communicate with serving gateway (SGW) 110 via a Diameter S8 interface 120. DSR 100 may communicate with MME 112 via an S11 interface 122. DSR 100 may communicate with PCRF 114 via a Diameter Gx, Rx, or S9 interface 124. DSR 100 may also interface with a packet gateway, such as a GGSN or PDN Gateway, via Gy, Gz, Ro, or Rf interfaces (not shown).
In some embodiments, DSR 100 may receive Diameter messages via other Diameter interfaces. For example, DSR 100 may receive Diameter message via an LTE interface, an IMS interface, an IETF specification interface, a 3GPP specification interface, a Third Generation Partnership Project 2 (3GPP2) specification interface, a European Telecommunications Standards Institute (ETSI) specification interface, an International Telecommunications Union (ITU) specification interface, a PacketCable specification interface, a MultiService Forum (MSF) specification interface, an Sh interface, a Dx interface, a Ro interface, a Rf interface, an Sp interface, a Gx interface, a Rx interface, a Gz interface, a Gy interface, a Gq interface, a Zh interface, a Dz interface, a Zn interface, a Ty interface, a Tx interface, a Dw interface, a Wa interface, a Wd interface, a Wx interface, a Wm interface, a Wg interface, a Pr interface, a Gr interface, a Gr+ interface, a Gi interface, a Wo interface, a Wf interface, a Re interface, an S6 interface, an S2 interface, an SW interface, an Sta interface, an S7 interface, an H2 interface, an E2 interface, an E4 interface, an E5 interface, a A3 interface, a A4 interface, a Rr interface, a Gq′ interface, a TC-6 interface, a TC-7 interface, a TC-8 interface, a TC-9 interface, a TC-10 interface, a TC-11 interface, a DB-0 interface, a DB-2 interface, a BI-1 interface, a LOC-1 interface, an Rw interface, a Pkt-mm-2 interface, a P-CSCF-PAM interface, a Pkt-laes-2 interface, an MM10 interface, an MZ interface, a Gmb interface, or a Zn′ interface.
Screening modules 102 may include functionality for processing and/or copying signaling messages. In some embodiments, screening modules 102 may be adapted to screen Diameter messages based on one or more screening rules. Exemplary screening rules may be used to copy, correlate, and/or monitor Diameter messages, or portions thereof, based on various factors. For example, screening modules 102, using one or more screening rules, may copy messages, or portions thereof, that include a particular Visited-PLMN-ID value or a particular User-Name value. In another example, screening modules 102, using screening rules, may copy messages, or portions thereof, associated with a particular Diameter interface.
In some embodiments, screening rule criteria may include a message type (e.g., a ULR message command code and Location Information Request (LIR) message command code, Credit Control Request (CCR) message command code, Re-Authorization Request message command code, etc.), time of day, a network condition, a network operator, a subscriber tier, a subscriber, an associated interface, an origination node, an origination network, a destination node, a destination network, a particular AVP code, and/or AVP information (e.g., a Visited-PLMN-ID, SGSN-Number, and User-Name).
In some embodiments, screened messages (e.g., Diameter messages, or portions thereof, that traverse MPs 202 and/or copies of such Diameter messages or portions) may be sent from DSR 100 to an external application or node for reporting and/or further processing. For example, copies of screened messages may be provided (e.g., as raw message copy output) to a node that is external to DSR 100.
MAM rules storage 216 may include any entity (e.g., a database, cache, or other memory device) for maintaining or storing MAM rules. DSR 100, including components and modules therein, may access MAM rules storage 216 for obtaining MAM rules and/or related information. In some embodiments, MAM rules storage 216 may be integrated with DSR 100. In some embodiments, MAM rules storage 216 may be distinct from and/or external to DSR 100.
MAM storage 218 may include any entity for maintaining or storing MAM records, or portions thereof. DSR 100, including components and modules therein, may access MAM storage 218 for determining congestion mitigation actions performed. In some embodiments, message storage 218 may be integrated with DSR 100. In some embodiments, message storage 218 may be distinct from and/or external to DSR 100.
In the architecture described above with respect to FIG. 2, screening modules 102 associated with message processors 202 copy Diameter signaling messages and send the messages to TPCM 206 for correlation. In an alternate implementation, because Diameter is a hop-by-hop protocol, message processors 202 may maintain a pending transaction list for every Diameter request message that traverses a message processor. Upon receiving an answer message, message processors 202 may correlate the answer with a pending request using the transaction list.
Table 400 may represent a data structure containing routing information and associated MPS thresholds. Table 400 may include information stored in multiple fields or columns, such as an origination host field, an origination realm field, a destination host field, a destination realm field, an application identifier field, a direction (e.g., ingress or egress) field, an MPS threshold field, and a congestion mitigation action field. Using the exemplary data of table 400, DSR 100 or a module therein may determine whether to apply a congestion mitigation action based on one or more characteristics of a Diameter message. For example, if a Diameter message has characteristics matching the first six fields of row 1 in Table 400 and if a threshold of 500 MPS has been exceeded, then a post-threshold action identified as “Apply Mediation Rule X” may occur.
Table 402 may represent a data structure containing congestion mitigation rules. Table 402 may include information stored in multiple fields or columns, such as a post-threshold mediation rule identifier field, a rule description field, a parameter or AVP identifier field, a parameter or AVP value field, and a congestion mitigation action field. Using the exemplary data of table 402, DSR 100 or a module therein may determine which congestion mitigation action is to be performed. For example, “Mediation Rule X” is a parameter specific discrimination rule for discarding a Diameter request message and sending a Diameter answer message to the Diameter request message originator.
FIG. 5 is a diagram illustrating exemplary connection and congestion management data according to an embodiment of the subject matter described herein. In some embodiments, the exemplary data may be stored in DSR 100, MP 202, or modules (e.g., rule storage 208, 210, or 216) therein.
As depicted, table 500 may represent a data structure containing peer connection information and associated MPS thresholds. Table 500 may include information stored in multiple fields or columns, such as a transport connection identifier field, an MPS threshold field, and a post-threshold action field. Using the exemplary data of table 500, DSR 100 or a module therein may determine whether to apply a congestion mitigation action based on the transport connection identifier. For example, if a Diameter message is part of a session associated with transport identifier “3333333” and if a threshold of 800 MPS has been exceeded, then a post-threshold action identified as “Apply Mediation Rule Y” may occur.
Table 502 may represent a data structure containing congestion mitigation rules. Table 502 may include information stored in multiple fields or columns, such as a post-threshold mediation rule identifier field, a rule description field, a parameter or AVP identifier field, a parameter or AVP value field, and a congestion mitigation action field. Using the exemplary data of table 502, DSR 100 or a module therein may determine which congestion mitigation action is to be performed. For example, “Mediation Rule Y” is an apply traffic profiling rule for building and reporting a thirty second traffic profile.
FIG. 6 is a diagram illustrating exemplary message and congestion management data according to an embodiment of the subject matter described herein. In some embodiments, the exemplary data may be stored in DSR 100, MP 202, or modules (e.g., rules storage 208, 210, or 216) therein.
As depicted, table 600 may represent a data structure containing message attribute information and associated MPS thresholds. Table 600 may include information stored in multiple fields or columns, such as a transport connection identifier field, an MPS threshold field, and a post-threshold action field. Using the exemplary data of table 600, DSR 100 or a module therein may determine whether to apply a congestion mitigation action based on a command code and flags associated with a Diameter message. For example, if a Diameter message includes command code “316” and a request (R) flag is “0” and if a threshold of 800 MPS has been exceeded, then a post-threshold action identified as “Apply Mediation Rule Y” may occur.
Table 602 may represent a data structure containing congestion mitigation rules. Table 602 may include information stored in multiple fields or columns, such as a post-threshold mediation rule identifier field, a rule description field, a parameter or AVP identifier field, a parameter or AVP value field, and a congestion mitigation action field. Using the exemplary data of table 602, DSR 100 or a module therein may determine which congestion mitigation action is to be performed. For example, “Mediation Rule Y” may be a parameter specific discrimination rule for changing a Visited-PLMN-ID AVP and discarding the Diameter message.
In some embodiments, DSR 100 or a module therein may determine, using the metric associated with Diameter message processing, that a second Diameter message processing metric threshold has been exceeded. In response to determining that the second Diameter message processing metric threshold has been exceeded, DSR 100 or a module therein may cease a congestion mitigation action. Continuing with the example stated above, a second metric threshold of 500 MPS may be associated with the ingress rate of new registration request messages to HSS. If the second metric threshold is exceeded (e.g., if the current ingress rate of new registration request messages to HSS goes below 500 MPS), DSR 100 or a module therein may stop throttling new registration request messages to HSS 108.
It will be appreciated that the above examples are illustrative and that the functionality described herein may be implemented for use with or applicable for various signaling messages, various signaling interfaces and various signaling nodes, including messages, interfaces, and nodes not explicitly described above, without departing from the scope of the subject matter described herein.
US8305922 18 feb 2010 6 nov 2012 Alcatel Lucent Method for PCRF to autonomously respond to cell capacity shortage
US8326263 1 dec 2008 4 dec 2012 Zte Corporation Method for selecting policy and charging rules function
US8331229 15 dec 2006 11 dec 2012 At&T Mobility Ii Llc Policy-enabled dynamic deep packet inspection for telecommunications networks
US8335220 5 jan 2010 18 dec 2012 Huawei Technologies Co., Ltd. Method and network element for obtaining IP-can session policy control information
US8353000 20 mei 2009 8 jan 2013 Huawei Technologies Co., Ltd. System and charging control method of network convergence policy and charging control architecture
US8400916 28 juni 2010 19 maart 2013 Alcatel Lucent Method of authorizing AF sessions using external subscriber database
US8406137 28 juni 2010 26 maart 2013 Alcatel Lucent Method and system for generating PCC rules based on service requests
US8438290 24 dec 2008 7 mei 2013 Zte Corporation Method for selecting a policy and charging rules function entity in the non-roaming scenario
US8543118 12 april 2007 24 sept 2013 Sprint Communications Company L.P. Multidomain, intercarrier network-to-network interface
US8605583 18 feb 2010 10 dec 2013 Alcatel Lucent PCC/QOS rule creation
US8630925 9 mei 2011 14 jan 2014 Telefonaktiebolaget L M Ericsson (Publ) Method and apparatus for controlling service traffic in a communication network
US8675487 28 juni 2010 18 maart 2014 Alcatel Lucent System and method for generating and updating PCC rules based on service requests
US8683544 14 mei 2008 25 maart 2014 Bridgewater Systems Corp. System and method for providing access to a network using flexible session rights
US8818327 27 maart 2012 26 aug 2014 Verizon Patent And Licensing Inc. Communicating a subscriber's status using an interface
US20030200277 29 jan 2003 23 okt 2003 Bong-Cheol Kim Method for controlling flow of radius protocol
US20040116117 26 sept 2003 17 juni 2004 Kati Ahvonen Enhanced QoS control
US20050105464 17 nov 2003 19 mei 2005 International Business Machines Corporation Differentiated handling of SIP messages for VoIP call control
US20050176438 16 sept 2004 11 aug 2005 Nokia Corporation Communication system
US20050195743 22 sept 2004 8 sept 2005 P-Cube Ltd. Real time charging of pre-paid accounts
US20060069776 15 sept 2004 30 maart 2006 Shim Choon B System and method for load balancing a communications network
US20060090004 27 okt 2004 27 april 2006 Microsoft Corporation Throttling service connections based on network paths
US20070083927 11 okt 2005 12 april 2007 Intel Corporation Method and system for managing denial of services (DoS) attacks
US20070121596 9 aug 2006 31 mei 2007 Sipera Systems, Inc. System and method for providing network level and nodal level vulnerability protection in VoIP networks
US20070153995 * 29 dec 2005 5 juli 2007 Qian Fang Method of converting between radius message and diameter messages
US20070232301 2 april 2007 4 okt 2007 Fujitsu Limited Roaming in wireless networks
US20080142599 28 feb 2007 19 juni 2008 Michael Benillouche Methods and systems to meter point-of-purchase conduct with a wireless communication device equipped with a camera
US20080170497 5 okt 2007 17 juli 2008 Moo Ryong Jeong Proactive Per-Class Load Management
US20080250156 9 april 2007 9 okt 2008 Lucent Technologies Inc. Method and apparatus for overload control and audit in a resource control and management system
US20080253387 28 maart 2008 16 okt 2008 International Business Machines Corporation Method and apparatus for improving SIP server performance
US20090061855 4 sept 2007 5 maart 2009 Janardan Sethi Dynamic ggsn relocation in a gprs network
US20090092131 9 okt 2007 9 april 2009 International Business Machines Corporation Method and Device for Rejecting Redundantly Retransmitted SIP Messages
US20090185494 * 31 maart 2009 23 juli 2009 Li Jijun Redirector, relay, system for configuring route information and method for updating route information
US20090207730 14 feb 2008 20 aug 2009 Qualcomm Incorporated Scheduling policy-based traffic management
US20090219946 10 april 2009 3 sept 2009 Huawei Technologies Co., Ltd. System and method for resource admission and control
US20090228956 20 mei 2009 10 sept 2009 Huawei Technologies Co., Ltd. System and charging control method of network convergence policy and charging control architecture
US20090270099 28 april 2009 29 okt 2009 Gallagher Michael D Method and Apparatus for Network Controller Selection in a Voice over Long Term Evolution via Generic Access System
US20100121960 5 juni 2009 13 mei 2010 Camiant, Inc. Method and system for providing mobility management in network
US20100190497 11 dec 2009 29 juli 2010 Christopher David Pudney Telecommunications network access rejection
US20100192170 2 maart 2009 29 juli 2010 Gregory G. Raleigh Device assisted service profile management with user preference, adaptive policy, network neutrality, and user privacy
US20100287121 30 juli 2010 11 nov 2010 Huawei Technologies Co., Ltd. Method, Apparatus, and System for Implementing Policy and Charging Control
US20110035495 10 jan 2006 10 feb 2011 Ekstroem Hannes Method and devices for filtering data packets in a transmission
US20110040845 1 mei 2008 17 feb 2011 Yigang Cai Message restriction for diameter servers
US20110061061 15 mei 2008 10 maart 2011 Alcatel Lucent Method and network elements of end-to-end overload control for diameter applications
US20110067085 10 sept 2010 17 maart 2011 Alcatel-Lucent Method for delivering dynamic policy rules to an end user, according on his/her account balance and service subscription level, in a telecommunication network
US20110076985 14 sept 2010 31 maart 2011 Youssef Chami Data management in telecommunication networks
US20110122886 20 jan 2011 26 mei 2011 Per Willars Method and devices for installing packet filters in a data transmission
US20110138066 18 aug 2009 9 juni 2011 Dirk Kopplin Handling of aggregate maximum bit rate by policy and charge control
US20110165901 21 dec 2010 7 juli 2011 Uri Baniel Methods, systems, and computer readable media for policy charging and rules function (pcrf) node selection
US20110171958 * 11 jan 2010 14 juli 2011 Suzann Hua Mobile device usage management via home subscriber server operation and profile
US20110188457 29 jan 2010 4 aug 2011 Hua Shu Method and apparatus for managing mobile resource usage
US20110199903 18 feb 2010 18 aug 2011 Alcatel-Lucent Canada Inc. Method for pcrf to autonomously respond to cell capacity shortage
US20110225306 15 maart 2011 15 sept 2011 Mark Delsesto Methods, systems, and computer readable media for triggering a service node to initiate a session with a policy charging and rules function
US20110299395 * 19 feb 2009 8 dec 2011 Telefonaktiebolaget Lm Ericsson (Publ) Traffic Control for Roaming Subscribers
US20110307790 14 juni 2010 15 dec 2011 Alcatel-Lucent Canada, Inc. Extending revalidation-time of diameter sessions
US20110317557 28 juni 2010 29 dec 2011 Alcatel-Lucent Canada, Inc. System and method for generating and updating pcc rules based on service requests
US20120014332 13 juli 2011 19 jan 2012 Rivada Networks Llc Methods and Systems for Dynamic Spectrum Arbitrage
US20120028626 31 juli 2010 2 feb 2012 Motorola, Inc. Policy determination for user equipment providng mutual aid in a visited enterprise operating area of a long term evolution system
US20120044867 * 18 aug 2011 23 feb 2012 Stefano Faccin Methods and apparatus to maintain call continuity
US20120052866 27 aug 2010 1 maart 2012 Tektronix, Inc. System and Method for Managing Subscriber Bandwidth Based on Cell Congestion Analysis
US20120087368 * 7 okt 2010 12 april 2012 Pulse Networks System and method for best value routing
US20120099715 20 okt 2011 26 april 2012 Venkataramaiah Ravishankar Methods, systems, and computer readable media for diameter routing agent (dra) based credit status triggered policy control
US20120115478 13 jan 2012 10 mei 2012 Research In Motion Limited Data-Capable Network Prioritization With Reduced Delays In Data Service
US20120131165 * 2 sept 2011 24 mei 2012 Uri Baniel Method and system for providing mobility management in network
US20120140632 13 juli 2010 7 juni 2012 Nederlandse Organisatie Voor Toegepast- Natuurwetenschappelijk Onderzoek Tno Congestion Control in a Telecommunications Network
US20120155389 * 1 dec 2011 21 juni 2012 Openet Telecom Ltd. Methods, systems and devices for dynamic context-based routing
US20120176894 17 aug 2009 12 juli 2012 Telefonaktiebolaget L M Ericsson (Publ) Method and Apparatus for Adapting Policy Control
US20120203781 * 20 april 2012 9 aug 2012 Apertio Limited Variant entries in network data repositories
US20120213072 18 feb 2011 23 aug 2012 Verizon Patent And Licensing Inc. Data rate aware scheduling in advanced wireless networks
US20120221445 * 28 feb 2011 30 aug 2012 Alcatel-Lucent Usa Inc. Method and apparatus for detecting duplicate accounting records in distributed network
US20120221693 * 25 feb 2011 30 aug 2012 Alcatlel-Lucent Canada Inc. Temporary restrictions and rollback
US20120250573 31 maart 2011 4 okt 2012 Alcatel-Lucent Canada Inc. Rules system versions
US20120250613 31 maart 2011 4 okt 2012 Alcatel-Lucent Canada Inc. Rules system version cloning
US20120303796 * 27 mei 2011 29 nov 2012 Alcate-Lucent Canada Inc. Mapping accounting avps to monitoring keys for wireline subscriber management
US20130079006 17 juni 2011 28 maart 2013 Samsung Electronics Co. Ltd. Wireless communication system and method for establishing a connection between user equipment and a mobility management entity thereof
US20130114404 2 nov 2012 9 mei 2013 Telefonaktiebolaget L M Ericsson (Publ) Node and method for the handling of serving gateway partial failure
US20130160058 19 dec 2011 20 juni 2013 Nokia Siemens Networks Oy Video EPOCH Coordination And Modification
US20130163429 * 25 juni 2012 27 juni 2013 Adam Dunstan System and method of adaptive congestion management
US20130177146 28 feb 2013 11 juli 2013 At&T Intellectual Property L, L.P. Methods and apparatus for authorization and/or routing of outdial communication services
US20130265911 6 juni 2013 10 okt 2013 Alcatel-Lucent Rules system versions
US20130275583 15 april 2013 17 okt 2013 Tekelec, Inc. Methods, systems, and computer readable media for performing diameter overload control
US20140018067 15 juli 2013 16 jan 2014 Tekelec, Inc. Methods, systems, and computer readable media for policy-based local breakout (lbo)
US20140022897 15 juli 2013 23 jan 2014 Tekelec, Inc. Methods, systems, and computer readable media for dynamically controlling congestion in a radio access network
US20140031029 22 juli 2013 30 jan 2014 Tekelec, Inc. Methods, systems and computer readable media for distributing policy rules to the mobile edge
US20140040975 21 juli 2013 6 feb 2014 Headwater Partners I Llc Virtualized Policy & Charging System
US20140376380 24 juni 2014 25 dec 2014 Oracle International Corporation Methods, systems and computer readable media for collecting and distributing diameter overload control information to non-adjacent nodes
US20150011182 29 sept 2014 8 jan 2015 Alla Goldner System, device, and method of cellular traffic monitoring
US20150036486 31 juli 2013 5 feb 2015 Oracle International Corporation Methods, systems, and computer readable media for destination-host defined overload scope
US20150036504 31 juli 2013 5 feb 2015 Oracle International Corporation Methods, systems and computer readable media for predicting overload conditions using load information
US20150036505 31 juli 2013 5 feb 2015 Oracle International Corporation Methods, systems, and computer readable media for mitigating traffic storms
EP0857399B1 21 okt 1996 12 mei 2004 Telefonaktiebolaget LM Ericsson (publ) Packet switched radio channel congestion control
JP2006100873A Titel niet beschikbaar
KR20090029348A Titel niet beschikbaar
WO2009070179A1 1 dec 2007 4 juni 2009 Lucent Technologies, Inc. Ims diameter router with load balancing
WO2009129487A2 17 april 2009 22 okt 2009 Tekelec Methods, systems, and computer readable media for session initiation protocol (sip) overload control
WO2009149341A2 5 juni 2009 10 dec 2009 Camiant, Inc. Method and system for providing mobility management in network
WO2011161575A1 6 juni 2011 29 dec 2011 Telefonaktiebolaget L M Ericsson (Publ) Notifying a controller of a change to a packet forwarding configuration of a network element over a communication channel
WO2012130264A1 6 sept 2011 4 okt 2012 Nec Europe Ltd. User traffic accountability under congestion in flow-based multi-layer switches
WO2013155535A1 15 april 2013 17 okt 2013 Tekelec, Inc. Methods, systems, and computer readable media for performing diameter overload control
WO2014014829A1 15 juli 2013 23 jan 2014 Tekelec, Inc. Methods, systems, and computer readable media for dynamically controlling congestion in a radio access network
WO2014015331A1 22 juli 2013 23 jan 2014 Tekelec, Inc. Methods, systems and computer readable media for distributing policy rules to the mobile edge
WO2015017422A1 29 juli 2014 5 feb 2015 Oracle International Corporation Methods, systems, and computer readable media for mitigating traffic storms
1 "3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Access to the 3GPP Evolved Packet Core (EPC) via non-3GPP access networks; Stage 3 (Release 12)," 3GPP TS 24.302, V12.1.0, pp. 1-68 (Jun. 2013).
2 "3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Study on Diameter overload control mechanisms (Release 12)," 3GPP TR 29.809 V0.3.0, pp. 1-51 (Jun. 2013).
3 "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Policy and charging control architecture (3GPP TS 23.203 version 8.14.0 Release 8)," ETSI TS 123 203, pp. 1-118 (Jul. 2012).
5 "Signaling Flows for the IP Multimedia Call control Based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP)," 3GPP TS 24.228 V1.1.0, p. 1-653 (Jul. 3-6, 2001).
6 "Smart Cards; Card Application Toolkit (CAT) (Release 9)," ETSI TS 102 223 V9.2.0, pp. 1-209 (Oct. 2010).
7 "Universal Mobile Telecommunications System (UMTS); LTE; Policy and Charging Control over Gx Reference Point (3GPP TS 29.212 version 9.2.0 Release 9)," ETSI TS 129 212 V9.2.0, pp. 1-115 (Apr. 2010).
8 3GPP, "3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) Functions Related to Mobile Station (MS) in Idle Mode (Release 10)," 3GPP TS 23.122 v10.0.0, pp. 1-41 (Jun. 2010).
9 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.2.0, pp. 1-111 (Mar. 2010).
10 3GPP, "3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; UICC-terminal Interface; Physical and Logical Characteristics (Release 9)," 3GPP TS 31.101, V9.1.0, pp. 1-35 (Jun. 2010).
11 3GPP, "3rd Generation Partnership Project; Technical Specification Group GSM/EDGE Radio Access Network; Mobile Radio Interface Layer 3 Specification; Radio Resource Control (RRC) Protocol (Release 10)," 3GPP TS 44.018 V10.0.0, pp. 1-429 (Sep. 2010).
12 3GPP, "3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol Specification (Release 9)," 3GPP TS 36.331 V94.0, pp. 1-252 (Sep. 2010).
13 3GPP, "3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Radio Resource Control (RRC); Protocol Specification (Release 9)," 3GPP TS 25.331, V9.4.0, pp. 1-1789 (Sep. 2010).
14 3GPP, "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Network Identity and Timezone (NITZ); Service Description, Stage 1 (Release 9)," 3GPP TS 22.042, V9.0.0, pp. 1-8 (Dec. 2009).
15 3GPP, "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Charging management; Diameter charging applications (Release 9)," 3GPP TS 32.299 V9.4.0, pp. 1-149 (Jun. 2010).
16 3GPP, "3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Universal Geographical Area Description (GAD) (Release 10)," 3GPP TS 23.032 V10.0.0, pp. 1-29 (Mar. 2011).
17 3GPP, "Digital Cellular Telecommunications System (Phase 2+); Universal Mobile Telecommunications System (UMTS); Universal Subscriber Identity Module (USIM) Application Toolkit (USAT) (3GPP TS 31.111 version 8.3.0 Release 8)," ETSI TS 131 111 V8.3.0, pp. 1-102 (Oct. 2008).
18 3GPP, "Universal Mobile Telecommunications System (UMTS); LTE; 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control Plane (GTPv2-C); Stage 3 (3GPP TS 29.274 version 9.3.0 Release 9)," ETSI TS 129 274 V9.3.0, pp. 1-162 (Jun. 2010).
19 Advisory Action and Examiner-Initiated Interview Summary for U.S. Appl. No. 13/040,020 (Dec. 5, 2014).
20 Advisory Action for U.S. Appl. No. 13/251,784 (Sep. 6, 2013).
21 Applicant-Initiated Interview Summary for U.S. Appl. No. 13/040,020 (Mar. 20, 2014).
22 Calhoun et al., "Diameter Base Protocol," RFC 3588, pp. 1-147 (Sep. 2003).
23 Campbell, "Diameter Overload Control Solution Issues," draft-campbell-dime-overload-issues-00, pp. 1-16 (Jun. 2013).
24 Commonly-assigned, co-pending International Application No. PCT/US14/48651 for "Methods, Systems, and Computer Readable Media for Diameter Load and Overload Information and Virtualization," (Unpublished, filed Jul. 29, 2014).
25 Commonly-assigned, co-pending International Application No. PCT/US14/66240 for "Methods, Systems, and Computer Readable Media for Diameter Routing Using Software Defined Network (SDN) Functionality," (Unpublished, filed Nov. 18, 2014).
26 Commonly-assigned, co-pending U.S. Appl. No. 13/572,132 for "Methods, Systems, and Computer Readable Media for Policy Event Record Generation," (Unpublished, filed Aug. 10, 2012).
27 Commonly-assigned, co-pending U.S. Appl. No. 14/034,478 for "Methods, Systems, and Computer Readable Media for Diameter Load and Overload Information and Virtualization," (Unpublished, filed Sep. 23, 2013).
28 Communication of European publication number and information on the application of Article 67(3) EPC for European Application No. 13776083.1 (Jan. 21, 2015).
29 Communication of European Publication Number and Information on the Application of Article 67(3) EPC for European Patent Application No. 10841576.1 (Oct. 10, 2012).
30 Communication of extended European Search Report for European Patent Application No. 10841576.1 (May 9, 2014).
31 Donovan et al., "Session Timers in the Session Initiation Protocol (SIP)," Network Working Group, RFC 4028 (Apr. 2005).
33 Final Office Action for U.S. Appl. No. 12/425,998 (Jun. 8, 2011).
34 Final Office Action for U.S. Appl. No. 12/973,228 (Jun. 21, 2013).
35 Final Office Action for U.S. Appl. No. 13/040,020 (Dec. 13, 2013).
36 Final Office Action for U.S. Appl. No. 13/040,020 (Sep. 19, 2014).
37 Final Office Action for U.S. Appl. No. 13/251,784 (Jun. 26, 2013).
38 Final Office Action for U.S. Appl. No. 13/572,132 (Mar. 11, 2015).
39 First Office Action for Chinese Application No. 201080064945.X (Sep. 17, 2014).
40 Grossglauser et al., "On the Relevance of Long-Range Dependence in Network Traffic," IEEE/ACM Transactions on Networking, vol. 7, No. 5, p. 629-640 (Oct. 1999).
41 Hilt et al., "Session Initiation Protocol (SIP) Overload Control," IETF, draft-hilt-sipping-overload-02, p. 1-28 (Jul. 8, 2007).
42 International Standard, "Maritime Navigation and Radiocommunication Equipment and Systems-Digital Interfaces-Part 1: Single Talker and Multiple Listeners," IEC 61162-1, Second edition, pp. 1-86 (Jul. 2000).
43 Interview Summary for U.S. Appl. No. 12/425,998 (Mar. 1, 2011).
44 Interview Summary for U.S. Appl. No. 12/425,998 (Sep. 14, 2011).
45 Korhonen et al., "The Diameter Overload Control Application (DOCA)," draft-korhonen-dime-ovl-01.txt, Diameter Maintenance and Extensions (DIME), pp. 1-18 (Feb. 25, 2013).
46 Kuthan et al., "Denial of Service Attacks Targeting a SIP VoIP Infrastructure: Attack Scenarios and Prevention mechanisms," IEEE Networks Magazine, vol. 20, No. 5 (Sep. 2006).
47 McMurry et al., "Diameter Overload Control Requirements," draft-ietf-dime-overload-reqs-00, pp. 1-25 (Sep. 21, 2012).
48 Nahum et al., "Evaluating SIP Server Performance," IBM T.J. Watson Research Center, RC24183 (Feb. 2007).
49 Non-Final Office Action for U.S. Appl. No. 12/425,998 (Nov. 29, 2010).
50 Non-Final Office Action for U.S. Appl. No. 12/973,228 (Feb. 1, 2013).
51 Non-Final Office Action for U.S. Appl. No. 12/973,228 (Oct. 25, 2013).
52 Non-Final Office Action for U.S. Appl. No. 13/040,020 (Apr. 21, 2014).
53 Non-Final Office Action for U.S. Appl. No. 13/040,020 (Jan. 29, 2015).
54 Non-Final Office Action for U.S. Appl. No. 13/040,020 (Jul. 18, 2013).
55 Non-Final Office Action for U.S. Appl. No. 13/251,784 (Dec. 19, 2012).
56 Non-Final Office Action for U.S. Appl. No. 13/251,784 (Oct. 10, 2013).
57 Non-Final Office Action for U.S. Appl. No. 13/276,916 (Apr. 11, 2013).
58 Non-Final Office Action for U.S. Appl. No. 13/572,132 (Aug. 11, 2014).
59 Non-Final Office Action for U.S. Appl. No. 13/942,323 (Feb. 25, 2015).
60 Non-Final Office Action for U.S. Appl. No. 13/947,314 (Jan. 16, 2015).
61 Notice of Allowance and Fee(s) Due for U.S. Appl. No. 12/973,228 (Mar. 20, 2014).
62 Notice of Allowance and Fee(s) Due for U.S. Appl. No. 13/251,784 (Feb. 12, 2014).
63 Notice of Allowance and Fee(s) Due for U.S. Appl. No. 13/276,916 (Sep. 3, 2013).
64 Notice of Allowance and Fee(s) Due for U.S. Appl. No. 13/330,086 (Nov. 6, 2013).
68 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/US2013/050512 (Dec. 2, 2013).
69 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/US2013/051447 (Oct. 28, 2013).
70 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/US2014/048644 (Oct. 17, 2014).
71 Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration for International Patent Application No. PCT/US2010/061586 (Sep. 26, 2011).
72 Ohta, "Overload Protection in a SIP Signaling Network," in International conference on Internet Surveillance and Protection (ICISP), p. 1-6 (2006).
73 Ohta, "Simulation Study of SIP Signaling in an Overload Condition," International Conference for Communications, Internet, and Information Technology, IASTED/ACTA Press, pp. 321-326 (Nov. 22-24, 2004).
74 Roach et al., "A Mechanism for Diameter Overload Control," draft-roach-dime-overload-ctrl-03, DIME, pp. 1-49 (May 17, 2013).
75 Rosenberg et al., "SIP: Session Initiation Protocol," Network Working Group, RFC 3261, http://www.ietf.org/rfc/rfc3261.txt, p. 1-252 (Jun. 2002).
76 Rosenberg, "Requirements for Management of Overload in the Session Initiation Protocol," IETF, draft-rosenbergy-sipping-overload-reqs-02, p. 1-22 (Oct. 2006).
77 Schulzrinne et al., "SIPstone-Benchmarking SIP Server Performance," (Apr. 2002).
78 Tschofenig, "Diameter Overload Architecture and Information Model," draft-tschofenig-dime-overload-arch-00.txt, DIME, pp. 1-9 (Jul. 16, 2013).
79 Zhang et al., "Denial of Service Attack and Prevention on SIP VoIP Infrastructures Using DNS Flooding," in Principles, Systems, and Applications of IP Telecummunications (IPTCOMM) (Jul. 2007).
80 Znaty, "Diameter, GPRS, (LTE+ePC=EPS), IMS, PCC and SDM," Effort, pp. 1-229 (Part 1 of 2) (May 2010).
81 Znaty, "Diameter, GPRS, (LTE+ePC=EPS), IMS, PCC and SDM," EFORT pp. 230-461 (Part 2 of 2) (May 2010).
US9369386 31 juli 2013 14 juni 2016 Oracle International Corporation Methods, systems, and computer readable media for destination-host defined overload scope
US9391897 31 juli 2013 12 juli 2016 Oracle International Corporation Methods, systems, and computer readable media for mitigating traffic storms
US9450872 24 juni 2014 20 sept 2016 Oracle International Corporation Methods, systems and computer readable media for collecting and distributing diameter overload control information to non-adjacent nodes
US9537775 23 sept 2013 3 jan 2017 Oracle International Corporation Methods, systems, and computer readable media for diameter load and overload information and virtualization
US9674046 * 21 okt 2014 6 juni 2017 At&T Intellectual Property I, L.P. Automatic detection and prevention of network overload conditions using SDN
US9680965 * 1 april 2015 13 juni 2017 Alcatel-Lucent Usa Inc. Software upgrades for offline charging systems within a network
US9699045 15 april 2013 4 juli 2017 Tekelec, Inc. Methods, systems, and computer readable media for performing diameter overload control
US20160112275 * 21 okt 2014 21 april 2016 At&T Intellectual Property I, L.P. Automatic detection and prevention of network overload conditions using sdn
WO2017050128A1 * 7 sept 2016 30 maart 2017 中兴通讯股份有限公司 Overload control method and apparatus for accounting request
Internationale classificatie H04L12/14, H04L12/801, G06F11/00, H04L12/26, H04L12/24, H04L29/06, H04M15/00
Coöperatieve classificatie H04L12/1403, H04L41/5074, H04M15/8027, H04L47/19, H04L43/16, H04L63/0892
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:KANODE, MARK EDWARD;KHADRI, SEETHARAMAN;MARSICO, PETER J.;SIGNING DATES FROM 20121017 TO 20121024;REEL/FRAME:029437/0152