Patent Grant
9635526
The subject matter described herein relates to the communication and routing of short message service (SMS) messages and Diameter agents used in an evolved packet system (EPS). More particularly, the subject matter described herein relates to systems, methods, and computer readable media for utilizing a Diameter proxy agent to communicate SMS messages.
In telecommunications networks that support mobile subscribers, there is a need to know or determine the current location of mobile subscribers so that communications, such a short message service (SMS) messages, may be directed to those mobile subscribers. In mobile telephone networks, there are network entities that are responsible for storing and managing the mobile subscriber location information. In third-generation (3G) and long term evolution (LTE) telecommunications networks, the home subscriber server (HSS) is responsible for managing this type of information. The HSS may also be configured to receive queries for the current location information of a particular mobile subscriber and reply to the queries with the last known location of the mobile subscriber. The location may be provided in the form of the network address or identifier of network entity, such as a mobile switching center (MSC) or mobility management entity (MME), that is currently serving the mobile subscriber.
On occasion, an SMS message may be communicated to a mobile subscriber via an LTE access network and an evolved packet system (EPS). In such instances, standards such as 3GPP TS 23.272 and 3GPP TS 29.338 define Diameter based protocols that may be used by SMS-capable MMEs that handle the communication of an SMS. However, these existing standards currently do not define the manner in which an LTE network may route an SMS message if a recipient mobile subscriber has ported out of network. Specifically, there is no definable means described in the standards to properly forward a mobile subscriber location information request message to the correct HSS if the recipient mobile subscriber has been ported to a foreign network.
Accordingly, in light of these potential disadvantages, there exists a need for methods, systems, and computer readable media for utilizing a Diameter proxy agent to communicate SMS messages.
Methods, systems, and computer readable media for utilizing a Diameter proxy agent to communicate SMS messages in a Diameter network are disclosed. According to one aspect, a method includes receiving, from an SMS service center via a Diameter interface, a mobile subscriber location information request message directed to a home subscriber server (HSS) in the first network, wherein the mobile subscriber location information request message is associated with a recipient mobile subscriber. The method further includes querying a number portability (NP) database to determine whether the recipient mobile subscriber has been ported to a foreign network and forwarding the mobile subscriber location information request message toward a gateway associated with the foreign network. In response to determining the recipient mobile subscriber has been ported to the foreign network. The method also includes, in response to determining the recipient mobile subscriber has not been ported to the foreign network, forwarding the request message to the HSS in the first network.
According to yet another aspect, the subject matter described herein comprises a method including, at a Diameter proxy agent located in a home network, receiving, from a mobility management entity (MME) via a Diameter interface, a mobile originated-forward short message (MO-FSM) message directed to a short message service (SMS) service center located in the home network, wherein the MO-FSM message is originated from a sending mobile subscriber. The method further includes querying a local database to determine if the SMS service center is located in the home network and querying a number portability (NP) database to determine whether the sending mobile subscriber is not a subscriber to the home network if the SMS service center is located in the home network. In response to determining the sending mobile subscriber is not a subscriber to the home network, the method includes sending an error message to the sending mobile subscriber. In response to determining the sending mobile subscriber is a subscriber to the home network, the method includes forwarding the MO-FSM message to the SMS service center associated with the home network.
The subject matter described herein may be implemented in hardware, software, firmware, or any combination thereof. As such, the terms “function”, “node” or “module” as used herein refer to hardware, which may also include software and/or firmware components, for implementing the feature being described. 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:
The subject matter described herein relates to methods, systems, and computer readable medium for utilizing a Diameter proxy agent to communicate SMS messages in an evolved packet system (EPS) or evolved packet core (EPC).
Referring to
In one embodiment, SMS service center 108 may receive the MO-FSM message which includes a destination address or mobile subscriber identifier associated with a recipient mobile subscriber (or with a network element that is servicing the recipient mobile subscriber). In response to receiving the MO-FSM message, SMS service center 108 may be configured to generate a mobile subscriber location information request message, such as a Send Routing Information for short message (SRI-SM) message that includes the mobile subscriber identifier or address associated with the destination, i.e., the receiving mobile subscriber. Exemplary mobile subscriber location information request messages may include a Send Routing Information (SRI) message, a SRI for short message (SRI-SM) message, a SRI for general packet radio service (SRI-GPRS) message, a SRI for location services (SRI-LCS) message, and a Diameter location information request (LIR) message.
In some embodiments, the mobile subscriber identifier may include an MSISDN, an Internet protocol (IP) address, a destination-host identifier and/or a destination-realm identifier associated with the mobile subscriber, a network entity (e.g., HSS) that is currently serving the subscriber associated with a mobile subscriber. SMS service center 108 may be further configured to send the SRI-SM message toward an HSS (e.g., one of HSS 120-124) in home network 100 that includes location information associated with the receiving mobile subscriber. For example, the location information may include information that identifies a switch, host, or other network entity (e.g., an S-CSCF) that is currently servicing the receiving mobile subscriber.
In some embodiments, a Diameter proxy agent 110 may receive and/or intercept the SRI-SM message sent by SMS service center 108. The SRI-SM message may be sent and received via a Diameter S6c interface. Diameter proxy agent 110 may include any router, server, or computing device configured to receive, process, and send Diameter based messages. Upon receiving the SRI-SM message, Diameter proxy agent 110 may be configured to extract the receiving mobile subscriber identifier (or address) and query a number portability (NP) database 112 that is configured to store number portability information associated with mobile subscribers. For example, NP database 112 may include entries of identifiers/addresses associated with mobile device subscribers that have ported out of home network 100 as well as ported into home network 100. The entries of NP database 112 may also include an identifier/address associated with the foreign network or a network element in the foreign network the mobile subscriber has ported to (e.g., a location routing number (LRN)). Although number portability database 112 is depicted as a database stored locally on Diameter proxy agent 110, an external NP database accessible by Diameter proxy agent 110 may be utilized without departing from the scope of the present subject matter. In one embodiment, Diameter proxy agent 110 may cross-reference and compare the mobile subscriber identifier associated with the receiving mobile subscriber with entries of NP database 112. If a matching entry is found, then Diameter proxy agent 110 may determine that the receiving mobile subscriber has ported out of home network 100 and ported to a foreign network identified in NP database 112. In one embodiment, Diameter proxy agent 110 may utilize NP database 112 determine that the recipient mobile subscriber is owned by the foreign network. Similarly, Diameter proxy agent 110 may also determine whether the receiving mobile subscriber has ported into home network 100. Notably, the number portability check conducted by Diameter proxy agent 110 may serve as a function to avoid the communication problems associated with forwarding a SRI-SM message intended for a mobile subscriber that has ported out of home network 100. Thus, in instances where Diameter proxy agent 110 determines that the receiving mobile subscriber is ported from home network 100, Diameter proxy agent 110 may forward the SRI-SM message to the foreign network hosting the recipient mobile subscriber via home network gateway 114 (or a switch). Alternatively, if Diameter proxy agent 110 determines that the receiving mobile subscriber is not included in NP database 112, Diameter proxy agent 110 may forward the SRI-SM message to the HSS the message was originally sent and the SMS delivery process continues as normal.
In an alternate embodiment, if Diameter proxy agent 110 determines that the receiving mobile subscriber is not included in NP database 112, Diameter proxy agent 110 may utilize subscriber locator function 111 to determine the HSS containing the location information associated with the receiving mobile subscriber. Subscriber locator function 111 may include a database that maps mobile subscriber identifiers with the respective HSS host identifiers. Accordingly, Diameter proxy agent 110 is able to ascertain the correct HSS that contains the location information of the receiving mobile subscriber in instances where the receiving mobile subscriber is an original subscriber or a ported in subscriber to home network 100. To obtain the location information of the receiving mobile subscriber, Diameter proxy agent may send a Diameter location information request to the identified HSS. The HSS will subsequently respond to Diameter proxy agent 110 with a Diameter location information answer (LIA) message. From the Diameter location information answer, Diameter proxy agent 110 may instructed to forward the SRI-SM message to a switch in the recipient network. Specifically, the location information provided by the HSS may include the address or other identifier, such as a location routing number (LRN), a point code address, a uniform resource identifier (URI), and/or an Internet protocol address of a node in the network that is currently serving the recipient mobile subscriber. The mobile subscriber location request (e.g., SRI-SM message) may then include the provided location information for the purpose of delivery of an SMS message to the recipient mobile subscriber.
In step 204, the destination address in the received mobile subscriber location information request message is used to query a number portability database. In one embodiment, the Diameter proxy agent may extract a mobile subscriber identifier from the received SRI-SM message and use the extracted identifier to query a local number portability database.
In step 206, a determination is made as to whether the destination address has been ported out of the home network to a foreign network. In one embodiment, the Diameter proxy agent may compare the mobile subscriber identifier from the received mobile subscriber location information request message with entries in a number portability database. In some embodiments, the Diameter proxy agent may also be configured to use the number portability database and/or another database to determine if the recipient mobile subscriber is owned by the foreign network. If a matching entry is found in the number portability database, then the Diameter proxy agent determines that the recipient mobile subscriber has been ported to a foreign network (i.e., a network that is separate and distinct from the home network) or is owned by the foreign network and method 200 continues to step 208. If a matching entry is not found in the number portability database, then the recipient mobile subscriber has not been ported from the home network and method 200 proceeds to step 210. In some embodiments, method 200 may proceed to step 210 in the event the Diameter proxy agent determines that the recipient mobile subscriber has ported into the home network.
In step 208, the mobile subscriber location information request message is routed to the foreign network via a home network gateway or switch. In one embodiment, the Diameter proxy agent routes mobile subscriber location information request message to the ported to address contained in the number portability database. For example, Diameter proxy agent may forward the mobile subscriber location information request message to a gateway or switch in the home network, which in turn may direct the mobile subscriber location information request message to the foreign network that hosts the ported to recipient mobile subscriber.
In step 210, the SRI-SM message is routed to the correct HSS. If it is determined that the recipient mobile subscriber has not been ported out of the home network (in step 206), then the Diameter proxy agent may ascertain the specific HSS that contains location information associated with the recipient mobile subscriber. In one embodiment, the Diameter proxy agent may forward the SRI-SM message to the HSS the message was originally addressed. In another embodiment, the Diameter proxy agent may query a database to determine which HSS (from among a plurality of HSSs) in the home network (i.e., the first) contains the location information associated with the recipient mobile subscriber. Alternatively, the HSS may be located in another network that is not the home network or the foreign network. The Diameter proxy agent may then utilize the obtained location information to proceed with the delivery of the SMS message.
Referring to
In one embodiment, E-UTRAM 304 sends the MO-FSM message to MME 306 for delivery to SMS service center 308. MME 306 forwards the MO-FSM message, which is subsequently received and/or intercepted by Diameter proxy agent 310. The MO-FSM message may be sent and received via a Diameter SGd interface. In some embodiments, Diameter proxy agent 310 includes a local service center database 312 which contains a list of entries that includes valid SMS service center addresses or identifiers associated with home network 300 (e.g., located in or hosted by home network 300). Diameter proxy agent 310 may also be configured to use the SMS service center address contained in the received MO-FSM message for querying the entries of database 312. If a matching entry is found, then Diameter proxy agent 310 may validate the SMS service center address. Otherwise, Diameter proxy agent 310 may send an error message to UE 302 if no matching entry is found in database 312.
After validating of the SMS service center address in the MO-FSM message, Diameter proxy agent 310 may be configured to use the sending mobile subscriber identifier in the MO-FSM message to query entries of a number portability (NP) database 314. If the sending mobile subscriber identifier matches an entry in NP database 314, then Diameter proxy agent 310 may determine that the sending mobile subscriber has been ported out of home network 300 and is improperly (e.g., inadvertently, fraudulently, etc.) using home network 300 for sending SMS messages. In such a scenario, Diameter proxy agent 310 may discard the MO-FSM message and send an error message to UE 302.
Alternatively, if the sending mobile subscriber identifier does not match an entry in NP database 314, then Diameter proxy agent 310 may determine that the sending mobile subscriber has not been ported out of home network 100. In such a scenario, Diameter proxy agent 310 may send the MO-FSM message to SMS service center 308 for further SMS delivery processing.
In an alternative embodiment, the number portability information contained in database 314 and the service center address information contained in 314 may be present in a common database that is accessible by Diameter proxy agent 110. Thus, Diameter proxy agent 110 may obtain the number portability information and the service center address information in a single lookup.
In step 404, the validity of the SMS service center address in the received message is checked. In one embodiment, the Diameter proxy agent uses the SMS service center address or identifier to query a database containing valid SMS service center addresses in the home network.
In step 406, a determination is made as to whether the SMS service center address is valid. In one embodiment, the Diameter proxy agent may determine that the SMS service center address is valid by finding a matching entry in the queried service center database. In such a scenario, method 400 continues to step 408. If the Diameter proxy agent determines that the SMS service center is invalid (e.g., not finding a matching entry in the service center database), then method 400 proceeds to block 412 where an error message is sent (e.g., to the sending mobile subscriber).
In step 408, the sending mobile subscriber identifier in the message is used to query a number portability database to determine if the sender is a subscriber to the home network. In one embodiment, the Diameter proxy agent may extract a origin-host identifier and/or origin-realm identifier from the received MO-FSM message and use the extracted identifier(s) to query a number portability database.
In step 410, a determination is made as to whether the sending mobile subscriber identifier (e.g., originating address) has been ported out of the home network. In one embodiment, the Diameter proxy agent may compare the mobile subscriber identifier (e.g., origin-host identifier and/or the origin-realm identifier) from the received MO-FSM message with entries in a number portability database. If a matching entry is found, then the sending mobile subscriber has been ported to a foreign network (i.e., a network that is separate and distinct from the home network) and method 400 continues to step 412 where an error message is sent (e.g., to the sending mobile subscriber). If a matching entry is not found, then the sending mobile subscriber has not been ported from the home network and method 200 proceeds to step 414.
In step 414, the MO-FSM message is routed to the SMS service center. In one embodiment, after determining that the sending mobile subscriber has not been ported to a foreign network, the Diameter proxy node may then route the message to the SMS service center the message was originally addressed. In another embodiment, the Diameter proxy agent may use a selection function to query a database to determine which SMS service center (from among a plurality of SMS service centers in the home network) should continue the delivery process of the received MO-FSM message.
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.
| 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 | Aströ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-Sichanie 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 |
| 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 |
| 6594258 | Larson et al. | Jul 2003 | B1 |
| 6611516 | Pirkola et al. | Aug 2003 | B1 |
| 6643511 | Rune et al. | Nov 2003 | B1 |
| 6662017 | McCann et al. | Dec 2003 | B2 |
| 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 |
| 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 |
| 7010002 | Chow et al. | Mar 2006 | B2 |
| 7027582 | Khello et al. | Apr 2006 | B2 |
| 7079524 | Bantukul et al. | Jul 2006 | B2 |
| 7079853 | Rathnasabapathy et al. | Jul 2006 | B2 |
| 7085260 | Karaul et al. | Aug 2006 | B2 |
| 7221952 | Cho et al. | May 2007 | B2 |
| 7457283 | Dalton, Jr. et al. | Nov 2008 | B2 |
| 7627108 | Enzmann et al. | Dec 2009 | B1 |
| 7693135 | Pershan | Apr 2010 | B2 |
| 7715367 | Nishida et al. | May 2010 | B2 |
| 7746864 | Asawa et al. | Jun 2010 | B1 |
| 7751386 | Kobayashi et al. | Jul 2010 | B2 |
| 7787445 | Marsico | Aug 2010 | B2 |
| 7996541 | Marathe et al. | Aug 2011 | B2 |
| 8131266 | Cai et al. | Mar 2012 | B2 |
| 8184798 | Waitrowski et al. | May 2012 | B2 |
| 8254551 | Heinze et al. | Aug 2012 | B2 |
| 8594679 | Agarwal et al. | Nov 2013 | B2 |
| 20010030957 | McCann et al. | Oct 2001 | A1 |
| 20010040957 | McCann et al. | Nov 2001 | A1 |
| 20020054674 | Chang et al. | May 2002 | A1 |
| 20020114440 | Madour et al. | Aug 2002 | A1 |
| 20020147845 | Sanchez-Herrero et al. | Oct 2002 | A1 |
| 20020173320 | Aitken et al. | Nov 2002 | A1 |
| 20020176562 | Hao | Nov 2002 | A1 |
| 20030007482 | Khello et al. | Jan 2003 | A1 |
| 20030026289 | Mukherjee et al. | Feb 2003 | A1 |
| 20030054844 | Anvekar et al. | Mar 2003 | A1 |
| 20030081754 | Esparza et al. | May 2003 | A1 |
| 20030109271 | Lewis et al. | Jun 2003 | A1 |
| 20030128693 | Segal | Jul 2003 | A1 |
| 20030193967 | Fenton et al. | Oct 2003 | A1 |
| 20030227899 | McCann | Dec 2003 | A1 |
| 20040003114 | Adamczyk | Jan 2004 | A1 |
| 20040081206 | Allison et al. | Apr 2004 | A1 |
| 20040082332 | McCann et al. | Apr 2004 | A1 |
| 20040087300 | Lewis | May 2004 | A1 |
| 20040141488 | Kim et al. | Jul 2004 | A1 |
| 20040142707 | Midkiff et al. | Jul 2004 | A1 |
| 20040196858 | Tsai et al. | Oct 2004 | A1 |
| 20040198351 | Knotts | Oct 2004 | A1 |
| 20040202187 | Kelly et al. | Oct 2004 | A1 |
| 20040243596 | Lillqvist et al. | Dec 2004 | A1 |
| 20040246965 | Westman et al. | Dec 2004 | A1 |
| 20050002407 | Shaheen | Jan 2005 | A1 |
| 20050003838 | McCann et al. | Jan 2005 | A1 |
| 20050119017 | Lovell et al. | Jun 2005 | A1 |
| 20050176448 | Klockner | Aug 2005 | A1 |
| 20050182781 | Bouvet | Aug 2005 | A1 |
| 20050286531 | Tuohino et al. | Dec 2005 | A1 |
| 20060002308 | Na et al. | Jan 2006 | A1 |
| 20060002400 | Kenyon et al. | Jan 2006 | A1 |
| 20060067338 | Hua et al. | Mar 2006 | A1 |
| 20060068762 | Baldwin et al. | Mar 2006 | A1 |
| 20060136557 | Schaedler et al. | Jun 2006 | A1 |
| 20060165068 | Dalton et al. | Jul 2006 | A1 |
| 20060245573 | Sheth et al. | Nov 2006 | A1 |
| 20070061397 | Gregorat et al. | Mar 2007 | A1 |
| 20070104184 | Ku et al. | May 2007 | A1 |
| 20070115934 | Dauster et al. | May 2007 | A1 |
| 20070116250 | Stafford | May 2007 | A1 |
| 20070121879 | McGary et al. | May 2007 | A1 |
| 20070191003 | Smith et al. | Aug 2007 | A1 |
| 20070238465 | Han et al. | Oct 2007 | A1 |
| 20070243876 | Duan | Oct 2007 | A1 |
| 20070286379 | Wiatrowski et al. | Dec 2007 | A1 |
| 20080068762 | Kobayashi et al. | Mar 2008 | A1 |
| 20080109532 | Denoual et al. | May 2008 | A1 |
| 20080112399 | Cohen et al. | May 2008 | A1 |
| 20080130856 | Ku et al. | Jun 2008 | A1 |
| 20080137832 | Heinze et al. | Jun 2008 | A1 |
| 20080247526 | Qiu et al. | Oct 2008 | A1 |
| 20080281975 | Qiu et al. | Nov 2008 | A1 |
| 20090103707 | McGary et al. | Apr 2009 | A1 |
| 20090181671 | Preiss | Jul 2009 | A1 |
| 20090227276 | Agarwal | Sep 2009 | A1 |
| 20100278122 | Singh | Nov 2010 | A1 |
| 20110038287 | Agarwal | Feb 2011 | A1 |
| 20110098049 | Gosnell et al. | Apr 2011 | A1 |
| 20120184307 | van Velsen | Jul 2012 | A1 |
| 20130079009 | Aumann | Mar 2013 | A1 |
| 20130115983 | Ronneke | May 2013 | A1 |
| 20140206403 | Buckley | Jul 2014 | A1 |
| Number | Date | Country |
|---|---|---|
| 1968267 | May 2007 | CN |
| ZL 200780034804.1 | Sep 2015 | CN |
| 0 512 962 | Nov 1992 | EP |
| 0 936 825 | Aug 1999 | EP |
| 0 944 276 | Sep 1999 | EP |
| 2 047 667 | May 2014 | EP |
| 2 033 431 | Aug 2014 | EP |
| 2 165 557 | May 2015 | EP |
| 274670 | Aug 2016 | IN |
| 275525 | Aug 2016 | IN |
| 2003-0040291 | May 2003 | KR |
| WO 9512292 | May 1995 | WO |
| WO 9611557 | Apr 1996 | WO |
| WO 9733441 | Sep 1997 | WO |
| WO 9856195 | Dec 1998 | WO |
| WO 9911087 | Mar 1999 | WO |
| WO 9957926 | Nov 1999 | WO |
| WO 0016583 | Mar 2000 | WO |
| WO 0154444 | Jul 2001 | WO |
| WO 02096147 | Nov 2002 | WO |
| WO 03005664 | Jan 2003 | WO |
| WO 2004006534 | Jan 2004 | WO |
| WO 2004075507 | Sep 2004 | WO |
| WO 2007045991 | Apr 2007 | WO |
| WO 2007146257 | Dec 2007 | WO |
| WO 2008011101 | Jan 2008 | WO |
| WO 2008073226 | Jun 2008 | WO |
| WO 2008157213 | Dec 2008 | WO |
| WO 2012119147 | Sep 2012 | WO |
| WO 2014116700 | Jul 2014 | WO |
| Entry |
|---|
| Third Office Action for Chinese Application No. 200880103119.4 (Aug. 19, 2013). |
| Notice of Allowance and Fee(s) Due for U.S. Appl. No. 12/400,576 (Jul. 19, 2013). |
| Second Office Action for Chinese Application No. 200880103119.4 (Mar. 19, 2013). |
| 3rd Generation Partnership Project, “Technical Specification Group Core Network and Terminals; Diameter based protocols to support Short Message Service (SMS) capable Mobile Management Entities (MMEs),” 3GPP TS 29.338, V12.0.0, pp. 1-40 (Mar. 2013). |
| 3rd Generation Partnership Project, “Technical Specification Group Services and System Aspects; Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2,” 3GPP TS 23.272, V10.10.0, pp. 1-84 (Mar. 2013). |
| Decision of Rejection for Chinese Patent Application No. 200780034804.1 (Aug. 31, 2012). |
| Notice of Loss of Rights Pursuant to Rule 112(1) EPC for European Patent Application No. 07867566.7 (Jul. 31, 2012). |
| First Official Action for Chinese Patent Application No. 200880103119.4 (Jul. 4, 2012). |
| Advisory Action for U.S. Appl. No. 12/400,576 (Jun. 26, 2012). |
| Notice of Allowance and Fee(s) Due for U.S. Appl. No. 11/635,406 (Apr. 20, 2012). |
| Advisory Action for U.S. Appl. No. 11/635,406 (Mar. 14, 2012). |
| Final Official Action for U.S. Appl. No. 12/400,576 (Mar. 9, 2012). |
| Interview Summary for U.S. Appl. No. 11/635,406 (Mar. 7, 2012). |
| Second Office Action for Chinese Patent Application No. 200780034804.1 (Feb. 21, 2012). |
| Notice of Allowance and Fee(s) Due for U.S. Appl. No. 11/605,837 (Jan. 20, 2012). |
| Final Official Action for U.S. Appl. No. 11/635,406 (Nov. 30, 2011). |
| Notice of Panel Decision from Pre-Appeal Brief Review for U.S. Appl. No. 11/635,406 (Oct. 3, 2011). |
| Non-Final Official Action for U.S. Appl. No. 12/400,576 (Aug. 24, 2011). |
| Notice of Publication of Abstract for Indian Patent Application No. 6406/CHENP/2010 A (Jun. 17, 2011). |
| Interview Summary for U.S. Appl. No. 11/605,837 (May 24, 2011). |
| First Office Action for Chinese Patent Application No. 200780034804.1 (May 19, 2011). |
| Final Official Action for U.S. Appl. No. 11/635,406 (Apr. 5, 2011). |
| Notice of Allowance and Fee(s) Due for U.S. Appl. No. 11/888,907 (Apr. 1, 2011). |
| Non-Final Official Action for U.S. Appl. No. 11/605,837 (Feb. 1, 2011). |
| Chinese Official Action for Chinese Patent Application No. 200780030069.7 (Jan. 31, 2011). |
| “Ericsson Unified Number Portability,” (Downloaded from the Internet on Jan. 24, 2011). |
| Official Action for U.S. Appl. No. 11/888,907 (Sep. 16, 2010). |
| Communication pursuant to Article 94(3) EPC for European application No. 07810606.9 (Aug. 26, 2010). |
| Official Action for U.S. Appl. No. 11/635,406 (Aug. 26, 2010). |
| Official Action for U.S. Appl. No. 11/605,837 (Jul. 20, 2010). |
| Tsou et al., “Realm-Based Redirection in Diameter,” draft-ietf-dime-realm-based-redirect-03, RFC 3588, pp. 1-6 (Jul. 12, 2010). |
| Notice of Allowance and Fee(s) Due for U.S. Appl. No. 11/879,737 (Apr. 22, 2010). |
| Communication pursuant to Article 94(3) EPC for European application No. 07810606.9 (Feb. 12, 2010). |
| Korhonen at al., “Clarifications on the Routing of Diameter Requests Based on the Username and the Realm,” RFC 5729, pp. 1-9 (Dec. 2009). |
| Supplementary European Search Report for European application No. 07810606.9 (Nov. 23, 2009). |
| 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/US2009/036538 (Sep. 30, 2009). |
| Non-Final Official Action for U.S. Appl. No. 11/879,737 (Sep. 30, 2009). |
| Communication of European publication number and information on the application of Article 67(3) EPC for European application No. 07867566.7 (Aug. 12, 2009). |
| Final Official Action for U.S. Appl. No. 11/879,737 (Jun. 9, 2009). |
| Communication of European publication number and information on the application of Article 67(3) EPC for European Application No. 07810606.9 (Mar. 18, 2009). |
| Communication of European publication number and information on the application of Article 67(3) EPC for European Application No. 07809476.0 (Feb. 11, 2009). |
| 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/US2008/066675 (Dec. 9, 2008). |
| 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/US07/16370 (Sep. 15, 2008). |
| Official Action for U.S. Appl. No. 11/879,737 (Sep. 15, 2008). |
| 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/US07/24418 (May 1, 2008). |
| “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). |
| Notification of Transmittal of the International Search Report and Writtent Opinion of the International Searching Authority, or the Declaration for International Application No. PCT/US07/13732 (Jan. 29, 2008). |
| Notice of Allowance for U.S. Appl. No. 10/729,519 (Jul. 30, 2007). |
| “IP Multimedia Subsystem,” printout from wikipedia.org, Wikimedia Foundation, Inc. (May 29, 2007). |
| Official Action for U.S. Appl. No. 10/729,519 (Nov. 28, 2006). |
| “HP OpenCall Home Subscriber Server Software—Data Sheet”, 4AA0-3360ENW Rev. 2, Hewlett-Packard Development Company, L.P. (Jul. 2006). |
| Lucent Technologies, “ENUM Use and Management for the Successful Deployment of ENUM-Enabled Services; Understand ENUM and its Deployment to Insure Success of your VoIP and Other ENUM-enabled Services,” White Paper, pp. 1-12 (Jul. 2006). |
| Stiemerling et al., “NAT/Firewall NSIS Signaling Layer Protocol (NSLP),” draft-ietf-nsis-nslp-natfw-06, pp. 1-70 (May 16, 2005). |
| Schwarz, “ENUM Trial to Link Phone, Internet Addresses,” (Mar. 22, 2005). |
| Peterson, “Telephone Number Mapping (ENUM) Service Registration for Presence Services,” Network Working Group, RFC 3953 (Jan. 2005). |
| Jones, “The Definitive Guide to Scaling Out SQL Server,” http://www.snip.gob.ni/Xdc/SQL/DGSOSSFinal.pdf (Retrieved on Aug. 16, 2010) (2005). |
| 3GPP, “3rd Generation Partnership Project; Technical Specification Group Core Network; Support of Mobile Number Portability (MNP); Technical Realization; Stage 2 (Release 6),” 3GPP TS 23.066, V6.0.0, pp. 1-83 (Dec. 2004). |
| Peterson et al., “Using E.164 Numbers With the Session Initiation Protocol (SIP),” Network Working Group, RFC 3824, pp. 1-14 (Jun. 2004). |
| “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). |
| Office Communication for U.S. Appl. No. 09/759,743 (Oct. 20, 2003). |
| Cisco, “Quality of Service Networks,” Internetworking Technologies Handbook, Chapter 49, pp. 49-1-49-32 (Sep. 11, 2003). |
| Moodie, “Agilent acceSS7: White Paper,” Agilent Technologies, pp. 1-14 (Apr. 1, 2003). |
| Notice of Allowance and Fee(s) Due for U.S. Appl. No. 09/759,743 (Mar. 10, 2003). |
| Interview Summary for U.S. Appl. No. 09/759,743 (Feb. 27, 2003). |
| Foster et al., “Number Portability in the Global Switched Telephone Network (GSTN): An Overview,” Network Working Group, RFC 3482 (Feb. 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). |
| Final Official Action for U.S. Appl. No. 09/759,743 (Dec. 2, 2002). |
| Barry, “A Signal for Savings,” Packet, Cisco Systems Users Magazine, vol. 14, No. 4, pp. Cover; 19-21; and 81 (Fourth Quarter 2002). |
| Interview Summary for U.S. Appl. No. 09/759,743 (Sep. 13, 2002). |
| Official Action for U.S. Appl. No. 09/759,743 (May 23, 2002). |
| Interview Summary for U.S. Appl. No. 09/759,743 (Mar. 6, 2002). |
| “Global Implementation of ENUM: A Tutorial Paper,” International Telecommunication Union, Telecommunication Standardization Union, Study Group 2, (Feb. 8, 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). |
| Official Action for U.S. Appl. No. 09/759,743 (Dec. 3, 2001). |
| International Preliminary Examination Report for International Application No. PCT/US01/01052 (Nov. 7, 2001). |
| 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). |
| Mealling, “The Naming Authority Pointer (NAPTR) DNS Resource Record,” Network Working Group, RFC 2915 (Sep. 2000). |
| 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 Number 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 and 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). |
| Communication under Rule 71(3) EPC for European Application No. 07 810 606.9 (Mar. 4, 2014). |
| First Examination Report for Indian Application No. 663/CHEN/2009 (Feb. 6, 2014). |
| Final Office Action for Chinese Application No. 200880103119.4 (Dec. 4, 2013). |
| Extended European Search Report for European Application No. 08770806.1 (Dec. 2, 2013). |
| Extended European Search Report for European Application No. 07809476.0 (Nov. 6, 2013). |
| “Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2,” ETSI TS 123 272, V11.3.0, pp. 1-93 (Jan. 2013). |
| “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; IP Multimedia Subsystem (IMS); Stage 2 (Release 8),” 3GPP TS 23.228, V8.1.0 (Jun. 2007). |
| “Infrastructure ENUM” 05TD143r4 Draft ETSI TR 102 055, V0.0.8 (2005). |
| Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration for PCT International Application No. PCT/US2014/017800 (Dec. 12, 2014). |
| Communication pursuant to Article 94(3) EPC for European Patent Application No. 08770806.1 (Oct. 10, 2014). |
| Notification of Reexamination for Chinese Patent Applcation No. 200780034804.1 (Sep. 15, 2014). |
| First Examiniation Report for Indian Patent Application No. 3929/CHENP/2009 (Aug. 20, 2014). |
| Communication pursuant to Article 94(3) EPC for European Patent Application No. 08770806.1 (Aug. 6, 2014). |
| Decision to Grant a European Patent Pursuant to Article 97(1) EPC for European Patent Application No. 07809476.0 (Jul. 31, 2014). |
| First Examination Report for Indian Patent Application No. 7234/CHENP/2008 (Jul. 18, 2014). |
| Communication under Rule 71(3) EPC for European Patent Application No. 07809476.0 (Jun. 23, 2014). |
| Notification of Reexamination for Chinese Patent Application No. 200780034804.1 (May 14, 2014). |
| Decision to grant a European patent pursuant to Article 97(1) EPC for European Patent Application No. 07810606.9 (Apr. 25, 2014). |
| Letter Regarding Granted Patent Information for Indian Patent Application No. 7234/CHENP/2008 (Sep. 14, 2015). |
| Letter Regarding Decision to Grant for Chinese Patent Application No. 200780034804.1 (Jul. 30, 2015). |
| First Examination Report for Indian Patent Application No. 185/CHENP/2010 (Jul. 28, 2015). |
| Second Examination Report for Indian Patent Application No. 7234/CHENP/2008 (May 14, 2015). |
| Decision to Grant a European Patent pursuant to Article 97(1) EPC for European Patent Application No. 08770806.1 (May 4, 2015). |
| Reexamination Decision for Chinese Patent Application No. 200780034804.1 (Mar. 27, 2015). |
| Letter Regarding Telephone Interview for Chinese Patent Application No. 200780034804.1 (Mar. 6, 2015). |
| Communication Under Rule 71(3) EPC for European Patent Application No. 08770806.1 (Mar. 3, 2015). |
| Communication of European publication number and information on the application of Article 67(3) EPC for European Application No. 14709831.3 (Dec. 23, 2015). |
| Notification of Reexamination for Chinese Application No. 200880103119.4 (Nov. 11, 2015). |
| Extended European Search Report for European Application No. 09717865.1 (Jul. 17, 2015). |
| “Address Resolution in MMS (Re: SerG LS E.164 Address Scheme)”, Liaison Statement, 3GPP TSG-T WG2-SWG3, http://www.3gpp.org/ftp/tsg—t/WG2—Capability/TSGT2—15—Cancun/Docs/, (Dec. 4, 2001). |
| Communication of the extended European search report for European Patent Application No. 14709831.3 (Aug. 5, 2016). |
| Partial Supplementary European Search Report for European Patent Application No. 14709831.3 (Jul. 8, 2016). |
| Hearing Notice for Indian Patent Application No. 663/CHENP/2009 (May 17, 2016). |
| Second Notification of Reexamination for Chinese Patent Application No. 200880103119.4 (Apr. 21, 2016). |
| “Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2,” 3GPP TS 23.272 version 11.4.0 Release 11, pp. 1-93 (Apr. 2013). |
| Tekelec, “Tekelec Eagle® 5,” Feature Manual—MO SMS, 910-6260-001 Revision A, pp. 1-148 (Jan. 2012). |
| Number | Date | Country | |
|---|---|---|---|
| 20140274170 A1 | Sep 2014 | US |
