Patent Grant
9935922
The subject matter described herein relates to screening Diameter messages within a Diameter signaling router (DSR) having a distributed message processor architecture. More specifically, the subject matter relates to methods, systems, and computer readable media for screening Diameter messages within a DSR having a distributed message processor architecture.
The Diameter protocol is a next generation authentication, authorization, and accounting (AAA) protocol. The Diameter base protocol is defined in IETF RFC 3588, the disclosure of which is incorporated by reference herein in its entirety. Commonly used within the Internet multimedia subsystem (IMS) architecture, the Diameter protocol was derived from the remote authentication dial-in user service (RADIUS) protocol. Historically, the RADIUS protocol was employed by Internet service providers (ISPs) to provide a secure communication channel between an ISP's access server and a secure location where user credential information was stored, e.g., a lightweight directory access protocol (LDAP) server. While the RADIUS protocol provided a standardized AAA exchange protocol, the emergence of new technologies and applications necessitated the development of a protocol capable of meeting ever-changing demands. Diameter aims to extend the standardized approach of RADIUS while providing expanded functionality and remaining open to future development.
As the prevalence of the Diameter protocol increases within providers' telecommunication networks, many providers are turning to distributed architectures for processing and routing the accompanying increase in volume of Diameter message traffic. While a distributed architecture may offer a provider advantages such as load balancing and redundancy, it also presents various issues. One such issue is providing for the screening of Diameter messages within such a distributed architecture.
Accordingly, a need exists for methods, systems, and computer readable media for screening Diameter messages within a DSR having a distributed message processor architecture.
According to one aspect, the subject matter described herein includes a method for screening Diameter messages within a Diameter signaling router (DSR) having a distributed message processor architecture. The method includes steps occurring at a DSR comprising a plurality of Diameter message processors, each configured to perform at least one Diameter function. The steps include receiving, at an ingress Diameter message processor of the Diameter message processors, a Diameter message from a Diameter peer node. The steps also include identifying, at a Diameter application message processor of the Diameter message processors, a Diameter message screening rule associated with the received Diameter message. The steps further include performing, at the Diameter application message processor of the Diameter message processors, a screening function associated with the identified Diameter message screening rule on the received Diameter message.
According to another aspect, the subject matter described herein includes a system for screening Diameter messages within a DSR having a distributed message processor architecture. The system includes a DSR. The DSR includes an ingress Diameter message processor configured to receive a Diameter message from a Diameter peer node. The DSR also includes a Diameter application message processor configured to identify a Diameter message screening rule associated with the received Diameter message and perform a screening function associated with the identified Diameter message screening rule on the received Diameter message.
As used herein, the term “node” refers to a physical computing platform including one or more processors and memory.
The subject matter described herein can be implemented in software in combination with hardware and/or firmware. For example, the subject matter described herein may be implemented in software executed by one or more processors. In one exemplary implementation, the subject matter described herein may be implemented using a non-transitory computer readable medium having stored thereon computer executable instructions that when executed by the processor of a computer control the computer to perform steps. Exemplary computer readable media suitable for implementing the subject matter described herein include non-transitory computer readable media, such as disk memory devices, chip memory devices, programmable logic devices, and application specific integrated circuits. In addition, a computer readable medium that implements the subject matter described herein may be located on a single device or computing platform or may be distributed across multiple devices or computing platforms.
The subject matter described herein will now be explained with reference to the accompanying drawings of which:
Methods, systems, and computer readable media for screening Diameter messages within a DSR having a distributed message processor architecture are provided.
As indicated above, Diameter message processor 208 may be configured as a Diameter application message processor. In accordance with embodiments of the subject matter described herein, Diameter message processor 208 may be configured to screen Diameter messages within DSR node 108. For example, in an exemplary routing scenario, at step 1, DSR node 108 may receive, via a communication interface (not illustrated), an inbound Diameter message from Diameter peer node 200. The inbound Diameter message may be received via ingress Diameter message processor 204's DCL 210. At step 2, the Diameter message may be forwarded to ingress Diameter message processor 204's DRL 212 for any required inbound Diameter routing functions. At step 3, DRL 212 may forward the Diameter message to Diameter application message processor 208. Diameter application message processor 208 may be dedicated to performing one or more Diameter screening functions. As will be described in greater detail below, Diameter application message processor 208 may identify one or more Diameter message screening rules associated with the received Diameter message. In some embodiments, Diameter application message processor 208 may be configured to identify one or more screening rules associated with the received Diameter message based on one or more of a Diameter connection over which the received Diameter message was received, a Diameter session of which the received Diameter message is a part, an origin host associated with the received Diameter message, an origin realm associated with the received Diameter message, a source Internet protocol (IP) address associated with the received Diameter message, a destination host associated with the received Diameter message, a destination realm associated with the received Diameter message, a Diameter connection over which the received Diameter message will be sent, a destination IP address to which the received Diameter message will be sent, a Diameter application identifier associated with the received Diameter message, a Diameter message command code associated with the received Diameter message, an attribute value pair (AVP) code associated with the received Diameter message, and an AVP data value associated with the received Diameter message.
Having identified one or more screening rules associated with the received Diameter message, Diameter application message processor 208 may perform one or more screening functions associated with the one or more identified Diameter message screening rules on the received Diameter message. For example, Diameter application message processor 208 may discard the received Diameter message, may modify the received Diameter message, and/or may update one or more usage or measurement statistics associated with the received Diameter message. Having performed one or more Diameter screening functions on the received Diameter message, at step 4, Diameter application message processor 208 may forward the Diameter message back to ingress Diameter message processor 204's DRL 212. At step 5, ingress Diameter message processor 204's DRL 212 may forward the Diameter message to egress Diameter message processor 206's DRL 216 which may perform any required egress routing functions. At step 6, DRL 216 may forward the Diameter message to egress Diameter message processor 206's DCL 214 for communication, at step 7, to Diameter peer node 202.
As will be described in greater detail below, in some embodiments Diameter application message processor 208 may identify a Diameter message screening rule that specifies that one or more usage or measurement statistics associated with the identified Diameter message screening rule should be updated. For example, Diameter application message processor 208 may identify a Diameter message screening rule from Diameter message screening and validation rules database 300 that specifies that when a Diameter message associated with MME node 106 is received by DSR 108, a current receipt rate associated with the identified Diameter message screening rule should be updated to reflect receipt of the Diameter message. In some embodiments, the identified Diameter message screening rule may specify a maximum receipt rate for Diameter messages associated with the Diameter message screening rule. Such a Diameter message screening rule may further specify a screening function that should be performed when the current receipt rate exceeds the maximum receipt rate for the Diameter message screening rule. For example, a Diameter message screening rule may specify that when the current receipt rate exceeds the maximum receipt rate for the Diameter message screening rule, any Diameter messages associated with the Diameter message screening rule should be discarded. DSR node 108 may be operative to communicate with a usage and measurement statistics database 302 for storing usage and measurement statistics (e.g., current receipt rates) and/or maximum receipt rates.
Upon updating the current receipt rate associated with the identified Diameter message screening rule, Diameter application message processor 208 may determine that the current receipt rate associated with the identified Diameter message screening rule exceeds the maximum receipt rate specified by the identified Diameter message screening rule, and in response to making such a determination may perform the screening function(s) specified by the identified Diameter message screening rule. For example, at step 3, Diameter application message processor 208 may discard the ULR message received from MME node 106 rather than communicating it to HSS node 110. At step 4, Diameter application message processor 208 may generate a screening event notification message (e.g., a screening event notification message indicating that DSR node 108 has exceeded its maximum receipt rate for messages associated with the identified Diameter message screening rule) and communicate the screening event notification message to NOC node 112. At step 5, Diameter application message processor 208 may generate and communicate to MME node 106 a ULA message containing an error code (e.g., an error code indicating that the ULR message could not be communicated to HSS node 110).
Similarly, table 602 may specify one or more application level “blacklist” rules. That is, table 602 may include one or more Diameter message screening rules that specify Diameter applications for which associated Diameter messages should not be allowed and/or one or more screening functions that should be performed on the associated Diameter messages. For example, table 602 includes an entry specifying that Diameter messages having an origin host “MME_Visited”; an origin realm “Visited.net”; any destination host; a destination realm “Home.net”; and an application identifier “16777251”, should not be allowed and that such messages should be discarded. Table 602, also includes an entry specifying that Diameter messages having an origin host “MME_Visited”; an origin realm “Visited.net”; any destination host; a destination realm “Home.net”; and an application identifier “16777267”, should not be allowed and such messages should be routed and the network operator notified.
Similarly, table 702 may specify one or more message level “blacklist” rules. That is, table 702 may include one or more Diameter message screening rules that specify Diameter message codes for which associated Diameter messages should not be allowed and/or one or more screening functions that should be performed on the associated Diameter messages. For example, table 702 includes an entry specifying that Diameter messages having an origin host “MME_Visited”; an origin realm “Visited.net”; any destination host; a destination realm “Home.net”; an application identifier “16777251”; and a message code “317”, should not be allowed and that such messages should be discarded. Table 702, also includes an entry specifying that Diameter messages having an origin host “MME_Visited”; an origin realm “Visited.net”; any destination host; a destination realm “Home.net”; an application identifier “16777251”; and a message code “322”, should not be allowed and such messages should be routed and the network operator notified. Table 702, further includes an entry specifying that Diameter messages having an origin host “MME_Visited”; an origin realm “Visited.net”; any destination host; a destination realm “Home.net”; an application identifier “16777267”; and any message code, should not be allowed and a reply with error message should be generated and communicated in response to such messages.
Similarly, table 802 may specify one or more AVP level “blacklist” rules. That is, table 802 may include one or more Diameter message screening rules that specify Diameter message AVP codes for which associated Diameter messages should not be allowed and/or one or more screening functions that should be performed on the associated Diameter messages. For example, table 802 includes an entry specifying that Diameter messages having an origin host “MME1”; an origin realm “Visited.net”; any destination host; a destination realm “Home.net”; an application identifier “16777251”; a message code “316”; and an AVP code “1401”, should not be allowed and that such messages should be modified to remove the AVP code.
Similarly, table 902 may specify one or more AVP value level “blacklist” rules. That is, table 902 may include one or more Diameter message screening rules that specify Diameter message AVP values for which associated Diameter messages should not be allowed and/or one or more screening functions that should be performed on the associated Diameter messages. For example, table 902 includes an entry specifying that Diameter messages having an origin host “vMME”; an origin realm “Visited.net”; any destination host; a destination realm “Home.net”; an application identifier “16777251”; a message code “316”; an AVP code “1407”; and an AVP value “20801”, should not be allowed and that such messages should be modified to remove the AVP value. Table 902 also includes an entry specifying that Diameter messages having an origin host “vMME”; an origin realm “Visited.net”; any destination host; a destination realm “Home.net”; an application identifier “16777251”; a message code “316”; an AVP code “1032”; and an AVP value “E-UTRAN”, should not be allowed and that such messages should be routed and the network operator notified.
It will be understood that various details of the subject matter described herein may be changed without departing from the scope of the subject matter described herein. Furthermore, the foregoing description is for the purpose of illustration only, and not for the purpose of limitation, as the subject matter described herein is defined by the claims as set forth hereinafter.
This application claims the benefit of U.S. Provisional Patent Application Ser. No. 61/435,102, filed Jan. 21, 2011; the disclosure of which is incorporated herein by reference in its entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4310727 | Lawser | Jan 1982 | A |
| 4754479 | Bicknell et al. | Jun 1988 | A |
| 5089954 | Rago | Feb 1992 | A |
| 5237604 | Ryan | Aug 1993 | A |
| 5247571 | Kay et al. | Sep 1993 | A |
| 5251248 | Tokunaga et al. | Oct 1993 | A |
| 5400390 | Salin | Mar 1995 | A |
| 5422941 | Hasenauer et al. | Jun 1995 | A |
| 5423068 | Hecker | Jun 1995 | A |
| 5430719 | Weisser, Jr. | Jul 1995 | A |
| 5442683 | Hoogeveen | Aug 1995 | A |
| 5455855 | Hokari | Oct 1995 | A |
| 5457736 | Cain et al. | Oct 1995 | A |
| 5481603 | Gutierrez et al. | Jan 1996 | A |
| 5502726 | Fischer | Mar 1996 | A |
| 5504804 | Widmark et al. | Apr 1996 | A |
| 5526400 | Nguyen | Jun 1996 | A |
| 5579372 | Åström | Nov 1996 | A |
| 5590398 | Matthews | Dec 1996 | A |
| 5594942 | Antic et al. | Jan 1997 | A |
| 5623532 | Houde et al. | Apr 1997 | A |
| 5689548 | Maupin et al. | Nov 1997 | A |
| 5706286 | Reiman et al. | Jan 1998 | A |
| 5711002 | Foti | Jan 1998 | A |
| 5819178 | Cropper | Oct 1998 | A |
| 5822694 | Coombes et al. | Oct 1998 | A |
| 5832382 | Alperovich | Nov 1998 | A |
| 5854982 | Chambers et al. | Dec 1998 | A |
| 5878347 | Joensuu et al. | Mar 1999 | A |
| 5878348 | Foti | Mar 1999 | A |
| 5890063 | Mills | Mar 1999 | A |
| 5953662 | Lindquist et al. | Sep 1999 | A |
| 5953663 | Maupin et al. | Sep 1999 | A |
| 5983217 | Khosravi-Sichannie et al. | Nov 1999 | A |
| 6006098 | Rathnasabapathy et al. | Dec 1999 | A |
| 6011803 | Bicknell et al. | Jan 2000 | A |
| 6014557 | Morton et al. | Jan 2000 | A |
| 6018657 | Kennedy, III et al. | Jan 2000 | A |
| 6038456 | Colby et al. | Mar 2000 | A |
| 6049714 | Patel | Apr 2000 | A |
| 6097960 | Rathnasabapathy et al. | Aug 2000 | A |
| 6115463 | Coulombe et al. | Sep 2000 | A |
| H1895 | Hoffpauir et al. | Oct 2000 | H |
| 6128377 | Sonnenberg | Oct 2000 | A |
| 6137806 | Martinez | Oct 2000 | A |
| 6138016 | Kulkarni et al. | Oct 2000 | A |
| 6138017 | Price et al. | Oct 2000 | A |
| 6138023 | Agarwal et al. | Oct 2000 | A |
| 6144857 | Price et al. | Nov 2000 | A |
| 6148204 | Urs et al. | Nov 2000 | A |
| 6192242 | Rollender | Feb 2001 | B1 |
| 6205210 | Rainey et al. | Mar 2001 | B1 |
| 6226517 | Britt et al. | May 2001 | B1 |
| 6236365 | LeBlanc et al. | May 2001 | B1 |
| 6263212 | Ross et al. | Jul 2001 | B1 |
| 6308075 | Irten et al. | Oct 2001 | B1 |
| 6327350 | Spangler et al. | Dec 2001 | B1 |
| 6377674 | Chong et al. | Apr 2002 | B1 |
| 6411632 | Lindgren et al. | Jun 2002 | B2 |
| 6424832 | Britt et al. | Jul 2002 | B1 |
| 6463055 | Lupien et al. | Oct 2002 | B1 |
| 6505046 | Baker | Jan 2003 | B1 |
| 6515997 | Feltner et al. | Feb 2003 | B1 |
| 6535746 | Yu et al. | Mar 2003 | B1 |
| 6539077 | Ranalli et al. | Mar 2003 | B1 |
| 6560216 | McNiff et al. | May 2003 | B1 |
| 6560456 | Lohtia et al. | May 2003 | B1 |
| 6574481 | Rathnasabapathy et al. | Jun 2003 | B1 |
| 6577723 | Mooney | Jun 2003 | B1 |
| 6594258 | Larson et al. | Jul 2003 | B1 |
| 6611516 | Pirkola et al. | Aug 2003 | B1 |
| 6643511 | Rune et al. | Nov 2003 | B1 |
| 6683881 | Mijares et al. | Jan 2004 | B1 |
| 6684073 | Joss et al. | Jan 2004 | B1 |
| 6731926 | Link, II et al. | May 2004 | B1 |
| 6738636 | Lielbriedis | May 2004 | B2 |
| 6748057 | Ranalli et al. | Jun 2004 | B2 |
| 6775737 | Warkhede et al. | Aug 2004 | B1 |
| 6795546 | Delaney et al. | Sep 2004 | B2 |
| 6795701 | Baker et al. | Sep 2004 | B1 |
| 6839421 | Ferraro Esparza et al. | Jan 2005 | B2 |
| 6871070 | Ejzak | Mar 2005 | B2 |
| 6917612 | Foti et al. | Jul 2005 | B2 |
| 6950441 | Kaczmarczyk et al. | Sep 2005 | B1 |
| 6967956 | Tinsley et al. | Nov 2005 | B1 |
| 7010002 | Chow et al. | Mar 2006 | B2 |
| 7027582 | Khello et al. | Apr 2006 | B2 |
| 7043000 | Delaney et al. | May 2006 | B2 |
| 7079524 | Bantukul et al. | Jul 2006 | B2 |
| 7079853 | Rathnasabapathy et al. | Jul 2006 | B2 |
| 7170982 | Li et al. | Jan 2007 | B2 |
| 7221952 | Cho et al. | May 2007 | B2 |
| 7286516 | Delaney et al. | Oct 2007 | B2 |
| 7286839 | McCann et al. | Oct 2007 | B2 |
| 7298725 | Rune | Nov 2007 | B2 |
| 7383298 | Palmer et al. | Jun 2008 | B2 |
| 7403537 | Allison et al. | Jul 2008 | B2 |
| 7466807 | McCann et al. | Dec 2008 | B2 |
| 7633872 | Pitcher et al. | Dec 2009 | B2 |
| 7633969 | Caugherty et al. | Dec 2009 | B2 |
| 7706343 | Delaney et al. | Apr 2010 | B2 |
| 7916685 | Schaedler et al. | Mar 2011 | B2 |
| 7961685 | Suh et al. | Jun 2011 | B2 |
| 7996007 | Bantukul | Aug 2011 | B2 |
| 7996541 | Marathe et al. | Aug 2011 | B2 |
| 8045983 | Bantukul | Oct 2011 | B2 |
| 8050391 | Andreasen et al. | Nov 2011 | B1 |
| 8219697 | Langen et al. | Jul 2012 | B2 |
| 8468267 | Yigang et al. | Jun 2013 | B2 |
| 8504630 | Craig et al. | Aug 2013 | B2 |
| 8613073 | McCann et al. | Dec 2013 | B2 |
| 8750126 | McCann et al. | Jun 2014 | B2 |
| 8958306 | McCann et al. | Feb 2015 | B2 |
| 9647986 | McCann et al. | May 2017 | B2 |
| 20010030957 | McCann et al. | Oct 2001 | A1 |
| 20010040957 | McCann et al. | Nov 2001 | A1 |
| 20010053694 | Igarashi et al. | Dec 2001 | A1 |
| 20020057669 | Joung | May 2002 | A1 |
| 20020147845 | Sanchez-Herrero et al. | Oct 2002 | A1 |
| 20020173320 | Aitken et al. | Nov 2002 | A1 |
| 20030007482 | Khello et al. | Jan 2003 | A1 |
| 20030026289 | Mukherjee et al. | Feb 2003 | A1 |
| 20030081754 | Esparza et al. | May 2003 | A1 |
| 20030109271 | Lewis et al. | Jun 2003 | A1 |
| 20030193967 | Fenton et al. | Oct 2003 | A1 |
| 20030227899 | McCann | Dec 2003 | A1 |
| 20040003114 | Adamczyk | Jan 2004 | A1 |
| 20040034699 | Gotz et al. | Feb 2004 | A1 |
| 20040081206 | Allison et al. | Apr 2004 | A1 |
| 20040082332 | McCann et al. | Apr 2004 | A1 |
| 20040087300 | Lewis | May 2004 | A1 |
| 20040142707 | Midkiff et al. | Jul 2004 | A1 |
| 20040198351 | Knotts | Oct 2004 | A1 |
| 20040202187 | Kelly et al. | Oct 2004 | A1 |
| 20040246965 | Westman et al. | Dec 2004 | A1 |
| 20060067338 | Hua et al. | Mar 2006 | A1 |
| 20060123477 | Raghavan et al. | Jun 2006 | A1 |
| 20060136557 | Schaedler et al. | Jun 2006 | A1 |
| 20060225128 | Aittola et al. | Oct 2006 | A1 |
| 20070067794 | Russell et al. | Mar 2007 | A1 |
| 20080025230 | Patel et al. | Jan 2008 | A1 |
| 20080160954 | Agarwal et al. | Jul 2008 | A1 |
| 20080165687 | Wang | Jul 2008 | A1 |
| 20080167035 | Buckley et al. | Jul 2008 | A1 |
| 20090080410 | Aoyagi et al. | Mar 2009 | A1 |
| 20090185494 | Li et al. | Jul 2009 | A1 |
| 20090193071 | Qiu et al. | Jul 2009 | A1 |
| 20090264096 | Cai et al. | Oct 2009 | A1 |
| 20100042525 | Cai et al. | Feb 2010 | A1 |
| 20100177780 | Ophir et al. | Jul 2010 | A1 |
| 20100202383 | Sugimoto et al. | Aug 2010 | A1 |
| 20100217877 | Willars et al. | Aug 2010 | A1 |
| 20100299451 | Yigang et al. | Nov 2010 | A1 |
| 20100304710 | Sharma et al. | Dec 2010 | A1 |
| 20110014939 | Ravishankar et al. | Jan 2011 | A1 |
| 20110038287 | Agarwal et al. | Feb 2011 | A1 |
| 20110116382 | McCann et al. | May 2011 | A1 |
| 20110126277 | McCann et al. | May 2011 | A1 |
| 20110188397 | McCann et al. | Aug 2011 | A1 |
| 20110202613 | Craig et al. | Aug 2011 | A1 |
| 20110225281 | Riley et al. | Sep 2011 | A1 |
| 20110289162 | Furlong | Nov 2011 | A1 |
| 20110295978 | Pazos et al. | Dec 2011 | A1 |
| 20110320622 | Cutler et al. | Dec 2011 | A1 |
| 20130039176 | Kanode et al. | Feb 2013 | A1 |
| 20130163424 | Goerke et al. | Jun 2013 | A1 |
| 20130163429 | Dunstan | Jun 2013 | A1 |
| 20140181952 | McCann et al. | Jun 2014 | A1 |
| 20150282242 | Merino Vazquez et al. | Oct 2015 | A1 |
| 20160014635 | Rasanen | Jan 2016 | A1 |
| 20160073282 | Speicher et al. | Mar 2016 | A1 |
| 20170013502 | Baniel et al. | Jan 2017 | A1 |
| Number | Date | Country |
|---|---|---|
| 2 716 544 | Dec 2010 | CA |
| 1964316 | May 2007 | CN |
| ZL 201080056996.8 | Apr 2015 | CN |
| 103460648 | Apr 2017 | CN |
| 0 512 962 | Nov 1992 | EP |
| 0 936 825 | Aug 1999 | EP |
| 0 944 276 | Sep 1999 | EP |
| 1 054 529 | Nov 2000 | EP |
| 1 314 324 | Aug 2008 | EP |
| 1 847 076 | Feb 2012 | EP |
| 2 819 455 | Dec 2014 | EP |
| 219214 | Oct 2015 | IL |
| 10-2004-0107271 | Dec 2004 | KR |
| WO 1995012292 | May 1995 | WO |
| WO 1996011557 | Apr 1996 | WO |
| WO 1997033441 | Sep 1997 | WO |
| WO 1998056195 | Dec 1998 | WO |
| WO 1999011087 | Mar 1999 | WO |
| WO 1999057926 | Nov 1999 | WO |
| WO 2000016583 | Mar 2000 | WO |
| WO 2004006534 | Jan 2004 | WO |
| WO 2004075507 | Sep 2004 | WO |
| WO 2007045991 | Apr 2007 | WO |
| WO 2008087633 | Jul 2008 | WO |
| WO 2009070179 | Jun 2009 | WO |
| WO 2011047382 | Apr 2011 | WO |
| WO 2011100621 | Aug 2011 | WO |
| WO 2014185987 | Nov 2014 | WO |
| Entry |
|---|
| Congdon, P., Sanchez, M., and B. Aboba, “RADIUS Filter Rule Attribute”, RFC 4849, DOI 10.17487/RFC4849, Apr. 2007, <https://www.rfc-editor.org/info/rfc4849>. |
| F. Eyermann, P. Racz, B. Stiller, C. Schaefer and T. Walter, “Diameter-based accounting management for wireless services,” IEEE Wireless Communications and Networking Conference, 2006. WCNC 2006., Las Vegas, NV, 2006, pp. |
| D. Tairov, I. Ganchev and M. O'Droma, “Signaling Messages and AVPs for 3P-AAA Framework,” 2011 Fifth International Conference on Next Generation Mobile Applications, Services and Technologies, Cardiff, 2011, pp. 180-184. |
| Ma Wenjing, Song Junde, Wu Jianqing and Song Mei, “A new type diameter-transmission mechanism based on distributed authorization signaling,” 2009 Joint Conferences on Pervasive Computing (JCPC), Tamsui, Taipei, 2009, pp. |
| P. J. Li and C. S. Zhi, “A Mobile IPv6 Firewall Traversal Scheme Integrating with AAA,” 2006 International Conference on Wireless Communications, Networking and Mobile Computing, Wuhan, 2006, pp. 1-6. |
| Non-Final Office Action for U.S. Appl. No. 12/906,998 (dated Jan. 2, 2013. |
| 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/US2012/021874 (dated Sep. 21, 2012). |
| Final Official Action for U.S. Appl. No. 12/906,998 (dated Mar. 29, 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/024637 (dated Oct. 27, 2011). |
| Non-Final Official Action for U.S. Appl. No. 12/906,998 (dated Sep. 21, 2011). |
| Traffix Systems, “Datasheet; Traffix Signaling Delivery Controller (SDC),” pp. 1-5 (May 2011). |
| “Ericsson Unified Number Portability,” (Downloaded from the Internet on Jan. 24, 2011). |
| Tsou et al., “Realm-Based Redirection in Diameter,” draft-ietf-dime-realm-based-redirect-03, RFC 3588, pp. 1-6 (Jul. 12, 2010). |
| Znaty, “Diameter, GPRS, (LTE ° ePC=EPS), IMS, PCC and SDM,” EFORT (May 2010). (Part 1 of 2, pp. 1-229). |
| Znaty, “Diameter, GPRS, (LTE + ePC=EPS), IMS, PCC and SDM,” EFORT (May 2010). (Part 2 of 2, pp. 230-460). |
| “3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Policy and Charging Control signalling flows and Quality of Service (QoS) parameter mapping (Release 9),” 3GPP TS 29.213, V9.2.0, pp. 1-129 (Mar. 2010). |
| “Mapping Diameter Interfaces to Functionality in 3GPP/3GPP2 IMS Architecture,” Whitepaper by Traffix Systems, pp. 1-10 (Copyright 2010). |
| Korhonen et al., “Clarifications on the Routing of Diameter Requests Based on the Username and the Realm,” RFC 5729, pp. 1-9 (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 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 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; 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 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; 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; 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; 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 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 Services and System Aspects; Policy and Charging Control Architecture (Release 9),” 3GPP TS 23.203 V9.3.0 (Dec. 2009). |
| 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). |
| “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 9),” 3GPP TS 29.272, V9.0.0, pp. 1-71 (Sep. 2009). |
| “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),” 3GPP TS 29.272, V8.4.0, pp. 1-71 (Sep. 2009). |
| “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Policy and charging control architecture (Release 8),” 3GPP TS 23.203, V8.1.1, pp. 1-87 (Mar. 2008). |
| “IP Multimedia Subsystem,” printout from wikipedia.org, Wikimedia Foundation, Inc. (May 29, 2007). |
| “HP OpenCall Home Subscriber Server Software—Data Sheet”, 4AA0-3360ENW Rev. 2, Hewlett-Packard Development Company, L.P. (Jul. 2006). |
| Tschofenig et al., “Securing the Next Steps in Signaling (NSIS) Protocol Suite,” International Journal of Internet Protocol Technology, vol. 1, pp. 1-14 (2006). |
| Stiemerling et al., “NAT/Firewall NSIS Signaling Layer Protocol (NSLP),” draft-ietf-nsis-nslp-natfw-06, pp. 1-70 (May 16, 2005). |
| 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 Core Network and Terminals; Policy Control Over Go Interface (Release 6),” 3GPP TS 29.207 V6.5.0 (Sep. 2005). |
| Hakala et al., “Diameter Credit-Control Application,” Network Working Group RFC 4006, pp. 1-107 (Aug. 2005). |
| “Cisco IP Transfer Point as the Signaling Gateway for the Cisco BTS 10200 Softswitch,” Cisco Systems, Inc., pp. 1-10 (Summer 2004). |
| “Cisco IP Transfer Point as the Signaling Gateway for the Cisco PGW 2200 Softswitch,” Cisco Systems, Inc., pp. 1-11 (Summer 2004). |
| “Next-Generation Signaling Transports Cisco IP Transfer Point,” Cisco Systems, Inc., pp. 1-27 (Summer 2004). |
| “A Study in Mobile Messaging: The Evolution of Messaging in Mobile Networks, and How to Efficiently and Effectively Manage the Growing Messaging Traffic,” White Paper, Cisco Systems, Inc., pp. 1-6 (Spring 2004). |
| Walker, “The IP Revolution in Mobile Messaging,” Packet, Cisco Systems Users Magazine, vol. 16, No. 1, pp. Cover, 73-74; and 89 (First Quarter 2004). |
| “Cisco ITP Multilayer Routing (MLR) SMS MO Routing Requirements,” Cisco Systems, Inc., p. 1 (Copyright 2004). |
| “Cisco Signaling Gateway Manager Release 3.2 for Cisco IP Transfer Point,” Cisco Systems, Inc., pp. 1-9 (Copyright 1992-2004). |
| “Solutions for Mobile Network Operators,” Cisco Systems, Inc., pp. 1-8 (Copyright 1992-2004). |
| Calhoun et al., “Diameter Base Protocol,” RFC 3588, pp. 1-147 (Sep. 2003). |
| Moodie, “Agilent acceSS7: White Paper,” Agilent Technologies, pp. 1-14 (Apr. 1, 2003). |
| “Cisco IP Transfer Point,” Cisco Systems, Inc., pp. 1-10 (Copyright 1992-2003). |
| “Cisco IP Transfer Point Multilayer Short Message Service Routing Solution,” Cisco Systems, Inc., pp. 1-6 (Copyright 1992-2003). |
| “Cisco ITP MAP Gateway for Public WLAN Slm Authentication and Authorization,” Cisco Systems, Inc., pp. 1-13 (Copyright 1992-2003). |
| Loshin, “19.4: Network Address Translation,” TCP/IP Clearly Explained, Fourth Edition, Morgan Kaufman Publishers, pp. 435-437 (2003). |
| Barry, “A Signal for Savings,” Packet, Cisco Systems Users Magazine, vol. 14, No. 4, pp. Cover; 19-21; and 81 (Fourth Quarter 2002). |
| “Agilent Technologies and Cisco Systems SS7 Over IP White Paper,” Cisco Systems, Inc. and Agilent and Technologies, pp. 1-6 (Copyright 2002—Printed in the UK Feb. 1, 2002). |
| “Cisco IP Transfer Point: MTP3 User Adaptation (M3UA) and SCCP User Adaptation (SUA) Signaling Gateway,” Cisco Systems, Inc., pp. 1-14 (Copyright 2002). |
| “Cisco SS7 Port Adapter for the Cisco 7500 Versatile Interface Processor and 7200 VXR Routers Provide High-Density SS7 Agrregation,” Cisco Systems, Inc., pp. 1-5 (Copyright 1992-2002). |
| “Next-Generation SS7 Networks with the Cisco IP Transfer Point,” Cisco Systems, Inc., pp. 1-14 (Copyright 1992-2002). |
| The attached email dated Oct. 20, 2001 and PowerPoint presentation dated Oct. 24, 2001 disclose an MSISDN-based auto-provisioning solution proposed by a customer of the assignee of the presend application. |
| “Agilent acceSS7 Business intelligence,” Agilent Technologies, pp. 1-6 (Copyright 2001—Printed in the UK Nov. 30, 2001). |
| “Cisco IP Transfer Point (ITP) Network Management Product Presentation,” Cisco Systems, Inc., pp. 1-20 (Copyright 2001). |
| “Networkers,” Cisco Systems, Inc., pp. 1-60 (Copyright 2001). |
| “Cisco SS7 Signaling Offload,” Cisco Systems, Inc., pp. 1-33 (Copyright 1992-2001). |
| Rockhold, “Or,” Wireless Review, p. 22, 23, 26, 28, 30, 32, (Aug. 15, 2000). |
| “Topsail Beach—SS7 Over IP-” Cisco Systems, Inc., pp. 1-16 (Copyright 1999). |
| Smith, “Number Portability Pileup,” Telephony, p. 22, 24, 26, (Jan. 6, 1997). |
| Jain et al., “Phone Nummer Portability for PCS Systems with ATM Backbones Using Distributed Dynamic Hashing,” IEEE, vol. 15 (No. 1), p. 96-105, (Jan. 1997). |
| Heinmiller, “Generic Requrements for SCP Application and GTT Function for Number Portability,” Illinois Number Portability Workshop, p. 1-50, (Sep. 4, 1996). |
| International Telecommunication Union, “Series Q: Switching and Signalling: Specifications of Signalling Systems No. 7—Signalling Connection Control Part,” p. 11-16, (Jul. 1996). |
| Rice, “SS7 Networks in a PCS World,” Telephony, pp. 138, 140 142, 144, 146, (Jun. 24, 1996). |
| Tekelec, “Eagle STP Planning Guide”, Eagle Network Switching Division, (No. 3), p. i-vii, 1-64, A1-A2, B1-2, (May 1996). |
| Anonymous, “Generic Switching and Signaling Requirements for Number Portability,” AT&T Network Systems, No. 1, p. 1-75, (Feb. 2, 1996). |
| ETSI, Digital Cellular Telecommunications System (Phase 2+); Milbe Application Part (MAP) Specification, Global System for Mobile Communications, pp. 112-114 (1996). |
| Jain, et al., “A Hashing Scheme for Phone Number Portability in PCS Systems with ATM Backbones,” Bell Communications Research, p. 593-597, (1996). |
| Bishop, “Freeing the Network for Competition,” Telecommunications, p. 75-80, (Apr. 1995). |
| Anonymous, “Zeichengabesysteme-Eine neue Generation für ISDN und intelligente Netze,” Zeichengabesystem, Medien-Institut Bremen, p. iz-xi; 170-176, (Feb. 17, 1995). |
| Giordano et al., “PCS Number Portability,” IEEE, p. 1146-1150, (Sep. 1994). |
| Bellcore, “Signaling Transfer Point (STP) Generic Requirements,” Bell Communications Research, No. 1, p. ii-xxii, 4-84-J14, (Jun. 1994). |
| Telcordia Technologies, “CCS Network Interface Specification (CCSNIS) Supporting SCCP and TCAP,” Bell Communications Research, p. ii-xii, 1-1—C-22, (Mar. 1994). |
| Buckles, “Very High Capacity Signaling Trnsfer Point for Intelligent Network Servcies,” DSC Communciations Corporation, p. 1308-1311, (1988). |
| “Diameter Overview,” referenced from www.ulticom.com/html/products/signalware-diameter-reference-guide.asp (Publication date unknown). |
| “Chapter 1: Overview,” SS7 Port Adapter Installation and Configuration, pp. 1-1-1-8 (Publication Date Unknown). |
| “Configuring ITP Basic Functionality,” IP Transfer Point, Cisco IOS Release 12.2(4)MB12, pp. 31-50 (Publication Date Unknown). |
| “Configuring ITP Optional Features,” IP Transfer Point, Cisco IOS Release 12.294)MB12, pp. 65-136 (Publication Date Unknown). |
| “Configuring M3UA and SUA SS7 Over IP Signaling Gateways,” IP Transfer Point, Cisco IOS Release 12.2(4)MB13, pp. 51-66 (Publication Date Unknown). |
| “Configuring M3UA and SUA SS7 Over IP Signaling Gateways,” IP Transfer Point, Cisco IOS Release 12.2(4)MB10, pp. 49-62 (Publication Date Unknown). |
| Notice of Allowance and Fee(s) Due for U.S. Appl. No. 13/026,133 (dated Feb. 3, 2014). |
| Communication of European Publication Number and Information on the Application of Article 67(3) EPC for European Patent Application No. 12737038.5 (dated Oct. 30, 2013). |
| Non-Final Office Action for U.S. Appl. No. 13/026,133 (dated Aug. 19, 2013). |
| Notice of Allowance and Fee(s) Due for U.S. Appl. No. 12/906,998 (dated Jul. 31, 2013). |
| Letter regarding Office Action for Japanese Patent Application No. 2013-550580 (dated Oct. 27, 2015). |
| Non-Final Office Action for U.S. Appl. No. 14/107,818 (dated Sep. 18, 2015). |
| Notification of the First Office Action for Chinese Application No. 201280009801.3 (dated Jul. 22, 2015). |
| Commonly assigned, co-pending U.S. Appl. No. 14/794,369 for, “Methods, Systems, and Computer Readable Media for Communicating Radio Access Network Congestion Status Information for Large Numbers of Users,” (Unpublished, filed Jul. 8, 2015). |
| 3GPP, “3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Nq and Nq′ Application Protocol (Nq-Ap); Stage 3 (Release 13),” 3GPP TS 29.405 V0.3.0 (Feb. 2015). |
| 3GPP, “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on system enhancements for user plane congestion management (Release 13),” 3GPP TR 23.705 V1.2.0 (Nov. 2014.). |
| 3GPP, “3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Policy and Charging Control over Np reference point (Release 13),” 3GPP TS 29.217 V1.0.0 (Nov. 2014). |
| Pre-Acceptance Notice for Israel Patent Application No. 219214 (dated Apr. 29, 2015). |
| Letter Regarding Notice of Grant for Chinese Patent Applcation No. ZL201080056996.8 (dated Feb. 12, 2015). |
| Corrected Notice of Allowability for U.S. Appl. No. 12/906,816 (dated Dec. 2, 2014). |
| Letter Regarding Notification of Non-Substantial Deficiencies for Israel Patent Application No. 219214 (dated Nov. 17, 2014). |
| Notice of Allowance and Fee(s) Due for U.S. Appl. No. 12/906,816 (dated Oct. 7, 2014). |
| Notification of the Second Office Action for Chinese Application No. 201080056996.8 (dated Sep. 3, 2014). |
| Office Action for Israel Patent Application No. 219214 (dated Jul. 2, 2014). |
| Non-Final Office Action for U.S. Appl. No. 12/906,816 (dated Jun. 19, 2014). |
| Applicant-Initiated Interview Summary for U.S. Appl. No. 12/906,816 (dated May 15, 2014). |
| First Office Action for Chinese Application No. 201080056996.8 (dated Apr. 4, 2014). |
| Final Office Action for U.S. Appl. No. 12/906,816 (dated Feb. 11, 2014). |
| Applicant-Initiated Interview Summary for U.S. Appl. No. 12/906,816 (dated Jan. 10, 2014). |
| Non-Final Office Action for U.S. Appl. No. 12/906,816 (dated Oct. 1, 2013). |
| Communication of European publication number and information on the application of Article 67(3) EPC for European Application No. 10824243.9 (dated Jul. 25, 2012). |
| Advisory Action for U.S. Appl. No. 12/906,816 (dated Jun. 5, 2012). |
| Applicant-Initiated Interview Summary for U.S. Appl. No. 12/906,816 (dated May 17, 2012). |
| Final Official Action for U.S. Appl. No. 12/906,816 (dated Feb. 21, 2012). |
| Applicant-Initiated Interview Summary for U.S. Appl. No. 12/906,816 (dated Jan. 27, 2012). |
| Non-Final Official Action for U.S. Appl. No. 12/906,816 (dated Oct. 5, 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/US2010/053062 (dated Jun. 28, 2011). |
| Jones et al., “Diameter Command Code Registration for the Third Generation Partnership Project (3GPP) Evolved Packet System (EPS),” Network Working Group, RFC 5516, pp. 1-5 (Apr. 2009). |
| Advisory Action Before the Filing of an Appeal Brief for U.S. Appl. No. 14/107,818 (dated May 26, 2016). |
| Applicant-Initiated Interview Summary for U.S. Appl. No. 14/107,818 (dated May 24, 2016). |
| Notification of the Second Office Action for Chinese Application No. 201280009801.3 (dated Apr. 5, 2016). |
| Letter Regarding Issued Patent for Japanese Patent Registration No. 5885757 (dated Mar. 15, 2016). |
| Final Office Action for U.S. Appl. No. 14/107,818 (dated Feb. 11, 2016). |
| Letter Regarding Notice of Grant for Japanese Patent Application No. 2013-556855 (dated Feb. 2, 2016). |
| Office action for U.S. Appl. No. 14/107,818 (dated Jul. 5, 2016). |
| Letter regarding Decision to Grant for Chinese Patent Application No. ZL201280009201.3 (dated Jan. 20, 2017). |
| Notice of Allowance and Fee(s) Due for U.S. Appl. No. 14/107,818 (dated Dec. 27, 2016). |
| Non-Final Office Action for U.S. Appl. No. 14/794,369 (dated Dec. 30, 2016). |
| Applicant Initated Interview Summary for U.S. Appl. No. 14/107,818 (dated Oct. 24, 2016). |
| Letter regarding Office Action for Chinese Patent Application No. 201280009801.3 (dated Sep. 19, 2016). |
| Eronen et al., “Diameter Extensible Authentication Protocol (EAP) Application,” https://www.ietf.org/rfc/rfc4072.txt, pp. 1-31 (Aug. 2005). |
| Fajardo, “Open Diameter Routing Architecture,” http://diameter.sourceforge.net/diameter-routing/, pp. 1-5 (Jun. 25, 2004). |
| Extended European Search Report for European Application No. 10824243.9 (dated Jun. 8, 2017). |
| Corrected Notice of Allowability for U.S. Appl. No. 14/107,818 (dated Apr. 11, 2017). |
| Extended European Search Report for European Application No. 12737038.5 (dated Mar. 16, 2017). |
| Advisory Action, Examiner-Initiated Interview Summary and AFCP 2.0 Decision for U.S. Appl. No. 14/794,369 (dated Sep. 29, 2017). |
| Final Office Action for U.S. Appl. No. 14/794,369 (dated Jul. 11, 2017). |
| Number | Date | Country | |
|---|---|---|---|
| 20120191847 A1 | Jul 2012 | US |
| Number | Date | Country | |
|---|---|---|---|
| 61435102 | Jan 2011 | US |
