The subject matter described herein relates to routing Diameter messages. More particularly, the subject matter described herein relates to methods, systems, and computer readable media for configurable Diameter address resolution.
In Diameter networks, it may be desirable to for network operators to direct Diameter signaling messages for specific subscribers or subscriber groups to nodes assigned to the subscribers or subscriber groups. For example, a network operator may have more than one home subscriber server (HSS), policy and charging rules function (PCRF), or online charging system (OCS). The network operator may desire to define end to end routing from one or more mobility management entities (MMEs), serving GPRS support nodes (SGSNs), or other nodes to the HSSs, PCRFs, or OCSs, such that messages pertaining to specific subscribers or subscriber groups are directed to specific nodes. Conventional Diameter routing that requires the message originator to specify the final destination host or realm for a message may not be scalable. In addition, different Diameter signaling messages may include different parameters that identify subscribers or subscriber devices and that are located in different attribute value pairs of the Diameter signaling messages. It may be desirable to use some of these parameters for routing or routing address resolution. Accordingly, there exists a need for configurable Diameter address resolution.
Methods, systems, and computer readable media for configurable Diameter address resolution are disclosed. One method includes, at a Diameter signaling router (DSR), sending Diameter signaling messages to and receiving Diameter signaling messages from Diameter signaling entities in a network. The method further includes providing for configuration of a plurality of routing entity identities and an order for preferentially using the routing entity identities in Diameter address resolution. The method further includes routing Diameter signaling messages using Diameter address information determined in the Diameter routing address resolution.
As used herein, the term “routing entity identity” refers to an identifier in a Diameter signaling message that identifies a subscriber, a subscriber device, or other entity that can be resolved into Diameter address information, such as a destination host, a destination realm, or both.
The subject matter described herein may be implemented using non-transitory computer readable medium having stored thereon executable instructions that when executed by the processor of a computer control the computer to perform steps. In one implementation, the subject matter described herein may be implemented in software embodied in a computer readable medium and executable by a processor. Exemplary computer readable media suitable use with the subject matter described herein include 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 plural devices or computing platforms.
Preferred embodiments of the subject matter described herein will now be explained with reference to the accompanied drawing of which:
The subject matter described herein includes methods, systems, and computer readable media for configurable Diameter address resolution. In one exemplary implementation, Diameter address resolution may be provisioned on a DSR.
According to an aspect of the subject matter described herein, Diameter address resolution module 104 may provide for configuration of routing entity identities used to search received Diameter signaling messages and, if located, to be used in Diameter address resolution. For example, Diameter address resolution module 104 may include a configuration interface accessible via a terminal local to DSR 100 and/or over a network that allows a user, such as a manufacturer or network operator, to populate data structures with routing entity identifiers, message command codes, preferences among routing entity identity identifiers, attribute value pairs to search for the routing entity identifiers, routing exception rules, and other parameters associated with Diameter address resolution. Exemplary data structures that may be populated by the user will be described in detail below.
In the network illustrated in
A DSR that supports Diameter address resolution may simultaneously support the roles of a Diameter proxy agent and a Diameter redirect agent on the same DSR.
Diameter address resolution that may be implemented by DSR 100 preferably resolves message parameters into a destination address. The network operator may be able to configure at least one of the following parameters for each destination address:
Other types of user identities may be used by DSR 100 in performing Diameter address resolution are IP multimedia domain user identities as specified in 3GPP TS 23.008 Section 3. Examples of IMS user identities are as follows:
Table 1 shown below illustrates an example of user identities that may be used by DSR 100 in performing Diameter address resolution.
According to an aspect of the subject matter described herein, DSR 100 and more specifically, Diameter address resolution module 104, may implement a routing entity identity preference list where messages are searched for specific routing entity identities and routing rules are applied according to preferences among the routing entity identities. As illustrated in Table 1, Diameter messages may have one or more routing entity identities. The user identities may be conditional and optional, which means that sometimes a message has an IMSI only, sometimes an IMPU only, sometimes an MSISDN only, and sometimes combinations of these parameters. Diameter address resolution module 104 may provide a generic framework that allows the operator to determine, through user configuration, which routing entity identity types in each message to use for an address resolution. Routing entity identity preferences may be supported by the routing entity identity preference list implemented in DSR100 and that is configurable by the network operator. The routing entity identity preference list may include multiple identities ordered according to a network operator's preference for each application ID, command code ordered pair. The routing entity identity preference list may define routing entity identities that can be used for address resolution and the order in which address resolution should look for the user identities in a message. For example, for the Cx interface in Table 1, the routing entity identity preference list for the ordered pair (Cx interface (16777216), *) may be:
1. IMPU—look for an IMPU first; and
2. IMSI—if a valid IMPU is not found, then look for an IMSI
Each type of routing entity identity may be carried in a finite set of message attribute value pairs (AVPs). In the 3GPP applications listed in Table 1, the routing entity identities that address resolution may support can be located in the AVPs specified in Table 2 below.
Table 2 lists combinations of routing entity identities and AVPs that may be present in Diameter signaling messages and used by address resolution module 104. However, the subject matter described herein is not limited to the examples in Table 2. Using any routing entity identity and AVP combination to search received Diameter signaling messages and perform address resolution is intended to be within the scope of the subject matter described herein.
One implementation, to provide a generic framework to support any Diameter application, Diameter address resolution module 104 will look for a routing entity identity type in the set of AVPs shown in Table 2 regardless of the application ID or command code in the received message. Address resolution module 104 will initially search the message looking for the AVP's that may contain the highest priority routing entity identity type that the operator has defined. As shown in Table 2, a routing entity identity type may be located in more than one AVP. This will be described in more detail below. Routing entity identities may also be embedded in AVPs of type “grouped”.
When address resolution module 104 encounters an AVP which may contain the desired routing entity identity type for which it is searching, Diameter address resolution module 104 may perform the following:
Determine whether the routing entity identity type is actually in the AVP (This mainly applies to grouped AVPs); and
If the desired routing entity identity type is found, than the address content may be verified (e.g., doesn't contain any invalid address characters). Address normalization may be performed to eliminate such characters. Address normalization will be described in more detail below.
If the desired routing entity identity is not found in the candidate AVP or the AVP contains the desired routing entity identity but its content is not supported by address resolution module 104, then address resolution module 104 may continue searching the message for another candidate AVP. Because multiple instances of AVPs may exist in the same message, address resolution module 104 may search through all AVPs and AVPs instances in the message that may contain the desired routing entity identity until a valid address is found.
If a valid routing entity identity is not found for the highest priority routing entity identity preference, and a next highest routing entity identity preference has been defined, then an address resolution module 104 will repeat the above procedure by searching the message for the next highest priority routing entity identity that has been defined. The procedure may be repeated until a valid routing entity identity is found or the preference list is exhausted. If no routing entity identity is found, then routing exception handling may be performed. Routing exception handling will be described in more detail below. If a valid address is found, then routing entity identity searching is complete. Address resolution module 104 may take the address digits and search a data structure referred to as a digit range table (DRT) associated with the application ID, command code, and routing entity identity type, looking for a match. If the DRT search fails (no matches), then routing fails and no further address resolution processing of the ingress message will occur. Routing exception handling with then be performed. If the DRT search is successful, then the destination address associated with the matching entry is used for routing the message. Individual address override may also be performed, as will be described in more detail below.
In the preceding paragraph, it is indicated that address resolution module 104 serially searches a received message until a valid routing entity identity is found. However, the subject matter described herein is not limited to such an embodiment. In an alternate embodiment, address resolution module 104 may search a received message for all possible routing entities and then perform the DRT lookup on the entities in the priority order configured by the user until a lookup is successful. A DRT is a set of addresses for a user or routing entity identity type which are serviced by server type (e.g., IMS-HSS, LTE-HSS, PCRF, OCS, OFCS). Each entry in the DRT may be a continuous block or range of addresses which are serviced by one of the servers (e.g., LTE-HSS1). A DRT may be associated with a destination address, which is typically a specific Diameter node assigned a FQDN.
Once the address is resolved using the hierarchy illustrated in
Once the final address is resolved, the message is forwarded to the Diameter routing layer where the message is routed from the ingress Diameter message processing module to the egress Diameter processing module associated with the destination.
According to another aspect of the subject matter described herein, address resolution module 104 may perform routing exception processing if it is unable to find a Diameter destination address for a message. Routing exception processing may be configurable, and may be performed as follows:
As set forth in
Many characters present in an AVP may not be part of the user identity that is used to search the range tables illustrated in
As set forth above, address resolution module 104 may perform address resolution based on any one or more of the following AVPs that contain user identity address information.
The user identity AVP contains either the IMPU or the MSISDN. The IMPU is embedded in a public identity value pair. The MSISDN is embedded in a MSISDN AVP.
The public identity AVP contains an IMPU. The IMPU may be a type UTF-8 string and may be in the form of SIP URI or a tel URI.
The MSISDN AVP contains the MSISDN in international format. The MSISDN may be encoded as a TBCD string with two digits per octet. The MSISDN AVP contains the IMPI or the IMSI. The user identity address will be stored in the user name portion of the NAI. An example of an IMSI that may be encoded in the NAI is IMSI@ims.mnc<MNC>.mcc<MCC>.3gppnetwork.org. An example of an IMPI that may be encoded in the NAI is 9194441212@vzw.com.
The subscription ID AVP may contain one of five user identity types as defined by the embedded subscription ID type AVP. The types that may be included are end user E.164 number, end user IMSI, end user SIP URI, end user NAI, or end user private address.
The service information AVP may contain one or more subscription ID AVPs. The subscription ID AVPs and the service information AVP may contain the identities described above. The framed IP address AVP may contain an IPv4 address of the subscriber. Similarly, the framed IPv6 prefix AVP may contain the IPv6 prefix of the subscriber's IPv6 address. The prefix is the routable portion of the IPv6 address.
Public identity and subscription ID AVPs may include SIP and/or tel URIs. SIP and tel URIs contain the IMPU of an IMS user. Because SIP and tel URIs have a canonical form, address resolution module 104 may extract the appropriate data, such as the E.164 number used to perform the address resolution.
In the example illustrated in
At each province DSR 100B, 100C, or 100D, the operator may want the flexibility to transparently move subscribers (i.e., without forcing subscribers to change their phone numbers or subscriber identities). In this example, gateway DSR 100A will perform HSS address resolution to either province DSR 100B, 100C, or 100D. When gateway DSR 100A forwards a message to province DSR 100B, province DSR 100B may perform address resolution a second time to determine the final destination address. However, some of the subscribers in province 1 may have been moved to province 2. After the address resolution on province 100B successfully resolves to a destination address, province DSR 100B may review an individual override table associated with the DRT in province DSR 100B to see if the user identity address has been moved. If the user identity address is found, IOT resolution takes precedence over DRT resolution.
For each DRT that address resolution overriding is supported, a separate IOT will be required. An IOT may be configured with the following attributes:
According to another aspect of the subject matter described herein, a DSR provisioned with address resolution as described herein may include the capability to prevent multiple identical address resolutions to be performed on the same message. This problem may occur if more than one DSR with overlapping address resolution data is deployed in a customer's network, as illustrated in
If in step 702 it is determined that Diameter address resolution does not apply, control proceeds to step 704 where an operator configurable routing exception processing in action is performed. For example, DSR 100 may be configured to route the message unchanged, route the message to a default destination, or send an answer with a user configurable result code or experimental result code value.
Returning to step 702, if it is determined that Diameter address resolution applies, control proceeds to step 706 with a message is searched for an operator configurable preferred routing entity identity. As set forth above, the network operator may provision a list of preferred routing entity identities and attribute value pairs where the identities are located to be used in searching a received message. In step 708, if the preferred identity is determined to be present in the message, control proceeds to step 710 where one or more Diameter address resolution lookups are performed using the preferred identity. The lookup may be performed in a data structure, such as that illustrated in
In step 712, it is determined whether the lookup was successful. If the lookup was successful in locating a matching entry, control proceeds to step 714 where operator configurable replacement or insertion of Diameter routing parameters and final routing are performed. As set forth above, if the received message is being routed, operator configurable replacement of parameters in the received message, such as the destination realm and/or the destination host, may be performed. The message may then be routed. If a new message, such as an answer to a received Diameter request, is being formed, the Diameter routing parameters located in the lookup may be inserted in the answer message and the message may be sent to the originator of the Diameter request.
Returning to step 708, if the preferred routing entity identity is determined not to be present in the received message, control proceeds to step 716 where it is determined whether the identity is the last identity in the preferred identity list. If the identity is the last identity, control proceeds to step 704 where operator configurable routing exception processing is performed as set forth above. If the identity is not the last identity in the preferred identity list, control proceeds to step 718 where the next identity is retrieved and then to step 706 where the message is searched for the next identity. Similarly, in step 712, if the Diameter address resolution lookup is not successful, control proceeds to step 716 where it is determined whether the identity for which the Diameter address resolution lookup was performed is the last identity in the preferred identity list. If the identity is the last identity, control proceeds to step 704 where operator configurable routing exception processing is performed. If in step 716, the identity is not the last identity, the next identity is extracted from the message in step 718 and control returns to step 706 where the message is searched for the next operator configurable preferred routing entity identity. The process may continue until the address resolution is performed or a routing exception occurs. The process may be repeated for each received Diameter signaling message.
It will be understood that various details of the presently disclosed subject matter may be changed without departing from the scope of the presently disclosed subject matter. Furthermore, the foregoing description is for the purpose of illustration only, and not for the purpose of limitation.
This application claims the benefit of U.S. Provisional Patent Application Ser. No. 61/454,462, filed Mar. 18, 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-Sichanni 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 |
6434144 | Romanov | Aug 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 |
6795701 | Baker et al. | Sep 2004 | B1 |
6836477 | West, Jr. et al. | Dec 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 |
7027433 | Touhino et al. | Apr 2006 | B2 |
7027582 | Khello et al. | Apr 2006 | B2 |
7039037 | Wang et al. | May 2006 | B2 |
7054652 | Luis | May 2006 | B2 |
7079524 | Bantukul et al. | Jul 2006 | B2 |
7079853 | Rathnasabapathy et al. | Jul 2006 | B2 |
7085260 | Karaul et al. | Aug 2006 | B2 |
7170982 | Li et al. | Jan 2007 | B2 |
7221952 | Cho et al. | May 2007 | B2 |
7286839 | McCann et al. | Oct 2007 | B2 |
7366530 | McCann et al. | Apr 2008 | B2 |
7397773 | Qu et al. | Jul 2008 | B2 |
7551608 | Roy | Jun 2009 | B1 |
7660287 | Axelsson et al. | Feb 2010 | B2 |
7715367 | Nishida et al. | May 2010 | B2 |
7751386 | Kobayashi et al. | Jul 2010 | B2 |
7756518 | Xu et al. | Jul 2010 | B2 |
7787445 | Marsico | Aug 2010 | B2 |
7889716 | Tejani et al. | Feb 2011 | B2 |
7996541 | Marathe et al. | Aug 2011 | B2 |
8254551 | Heinze et al. | Aug 2012 | B2 |
8452325 | McCann | May 2013 | B2 |
20010030957 | McCann et al. | Oct 2001 | A1 |
20010040957 | McCann et al. | Nov 2001 | A1 |
20020147845 | Sanchez-Herrero et al. | Oct 2002 | A1 |
20020173320 | Aitken et al. | Nov 2002 | A1 |
20020176382 | Madour et al. | Nov 2002 | A1 |
20030007482 | Khello et al. | Jan 2003 | A1 |
20030013464 | Jean Henry-Labordere | Jan 2003 | A1 |
20030026289 | Mukherjee et al. | Feb 2003 | A1 |
20030065788 | Salomaki | Apr 2003 | A1 |
20030081754 | Esparza et al. | May 2003 | A1 |
20030109271 | Lewis et al. | Jun 2003 | A1 |
20030128693 | Segal | Jul 2003 | A1 |
20030181206 | Zhou et al. | Sep 2003 | A1 |
20030193967 | Fenton et al. | Oct 2003 | A1 |
20030220951 | Muthulingam et al. | Nov 2003 | A1 |
20030227899 | McCann | Dec 2003 | A1 |
20040003114 | Adamczyk | Jan 2004 | A1 |
20040034699 | Gotz et al. | Feb 2004 | A1 |
20040053604 | Ratilainen et al. | Mar 2004 | A1 |
20040053610 | Kim | Mar 2004 | A1 |
20040076126 | Qu et al. | Apr 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 |
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 |
20050143075 | Halsell | Jun 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 |
20060034256 | Addagatla et al. | Feb 2006 | A1 |
20060067338 | Hua et al. | Mar 2006 | A1 |
20060098621 | Plata et al. | May 2006 | A1 |
20060136557 | Schaedler et al. | Jun 2006 | A1 |
20060165068 | Dalton et al. | Jul 2006 | A1 |
20060293021 | Zhou | Dec 2006 | A1 |
20070019625 | Ramachandran et al. | Jan 2007 | A1 |
20070061397 | Gregorat et al. | Mar 2007 | A1 |
20070115934 | Dauster et al. | May 2007 | A1 |
20070116250 | Stafford | May 2007 | A1 |
20070121879 | McGary et al. | May 2007 | A1 |
20080037759 | Chin et al. | Feb 2008 | A1 |
20080051036 | Vaswani et al. | Feb 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 |
20080171544 | Li et al. | Jul 2008 | A1 |
20080247526 | Qiu et al. | Oct 2008 | A1 |
20080281975 | Qiu et al. | Nov 2008 | A1 |
20080311917 | Marathe et al. | Dec 2008 | A1 |
20090103707 | McGary et al. | Apr 2009 | A1 |
20090193498 | Agarwal et al. | Jul 2009 | A1 |
20100284336 | Rui et al. | Nov 2010 | A1 |
20100285800 | McCann | Nov 2010 | A1 |
20120302229 | Ronneke | Nov 2012 | A1 |
20120311102 | Stenfelt | Dec 2012 | A1 |
Number | Date | Country |
---|---|---|
1968267 | May 2007 | CN |
200680051295 | Mar 2013 | CN |
0 512 962 | Nov 1992 | EP |
0 936 825 | Aug 1999 | EP |
0 944 276 | Sep 1999 | EP |
1 558 004 | Jul 2005 | EP |
1 742 452 | Jan 2007 | EP |
1 958 399 | Feb 2012 | EP |
2003-0040291 | May 2003 | KR |
10-2004-0107271 | Dec 2004 | 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 03005664 | Jan 2003 | WO |
WO 2004006534 | Jan 2004 | WO |
WO 2004008786 | Jan 2004 | WO |
WO 2004075507 | Sep 2004 | WO |
WO 2006072473 | Jul 2005 | WO |
WO 2007045991 | Apr 2007 | WO |
WO 2007064943 | Jun 2007 | WO |
WO 2008011101 | Jan 2008 | WO |
WO 2008073226 | Jun 2008 | WO |
WO 2008157213 | Dec 2008 | WO |
Entry |
---|
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/029673 (Oct. 31, 2012). |
Notice of Granting Patent Right for Invention for Chinese Patent Application No. 200680051295.9 (Nov. 6, 2012). |
Decision of Rejection for Chinese Patent Application No. 200780034804.1 (Aug. 31, 2012). |
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Charging management; Diameter charging applications (Release 11),” 3GPP TS 32.299, V11.3.0, pp. 1-150 (Mar. 2012). |
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; IP multimedia call control protocol based on Session Initiation Protocol (SIP)and Session Description Protocol (SDP); Stage 3 (Release 11),” 3GPP TS 24.229, V11.3.0, pp. 1-728 (Mar. 2012). |
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Sh Interface based on the Diameter protocol; Protocol details (Release 11),” 3GPP TS 29.329, V11.1.0, pp. 1-22 (Dec. 2011). |
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; IP Multimedia (IM) Subsystem Sh interface; Signalling flows and message contents (Release 11),” 3GPP TS 29.328, V11.2.0, pp. 1-53 (Dec. 2011). |
“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 11),” 3GPP T.3. 29.272, V11.1.0 pp. 1-98 (Dec. 2011). |
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Cx and Dx interfaces based on the Diameter protocol; Protocol details (Release 11),” 3GPP TS 29.229, V11.2.0, pp. 1-37 (Dec. 2011). |
“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 11),” 3GPP TS 29.228, V11.2.0, pp. 1-71 (Dec. 2011). |
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Policy and Charging Control over Rx reference point (Release 11),” 3GPP TS 29.214, V11.3.0, pp. 1-51 (Dec. 2011). |
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Policy and Charging Control (PCC) over Gx/Sd reference point (Release 11),” 3GPP TS 29.212, V11.3.0, pp. 1-171 (Dec. 2011). |
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Mobile Application Part (MAP) specification (Release 11),” 3GPP TS 29.002, V11.1.0, pp. 1-954 (Dec. 2011). |
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Organization of subscriber data (Release 11),” 3GPP TS 23.008, V11.2.0, pp. 1-105 (Dec. 2011). |
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Numbering, addressing and identification (Release 11),” 3GPP TS 23.003, V11.0.0, pp. 1-81 (Dec. 2011). |
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Network architecture (Release 11),” 3GPP TS 23.002, V11.1.0, pp. 1-96 (Dec. 2011). |
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Charging management; Charging Data Record (CDR) transfer (Release 10),” 3GPP TS 32.295, V10.0.0, pp.1-32 (Mar. 2011). |
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Generic Authentication Architecture (GAA); Zh and Zn Interfaces based on the Diameter protocol; Stage 3 (Release 10),” 3GPP TS 29.109., V10.0.0, pp. 1-67 (Mar. 2011). |
“The international public telecommunication numbering plan,” ITU-T, E.164, pp. 1-32 (Nov. 2010). |
“The international identification plan for public networks and subscriptions,” ITU-T, E.212, pp. 1-28 (May 2008). |
“3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Charging rule provisioning over Gx interface (Release 6),” 3GPP TS 29.210, V6.7.0, pp.1-21 (Dec. 2006). |
“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, pp. 1-63 (Mar. 2006). |
Aboba et al., “The Network Access Identifier,” RFC 4282, pp. 1-17 (Dec. 2005). |
Hakala et al., “Diameter Credit-Control Application,” RFC 4006, pp. 1-115 (Aug. 2005). |
Calhoun et al., “Diameter Network Access Server Application,” RFC 4005, pp. 1-86 (Aug. 2005). |
Schulzrinne, “The tel URI for Telephone Numbers,” RFC 3966, pp. 1-18 (Dec. 2004). |
Rosenberg et al., “SIP: Session Initiation Protocol,” RFC 3261, pp. 1-270 (Jun. 2002). |
Berners-Lee et al., “Uniform Resource Identifiers (URI): Generic Syntax,” RFC 2396, pp. 1-41 (Aug. 1998). |
Non-Final Official Action for U.S. Appl. No. 12/777,853 (Aug. 29, 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). |
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 11/635,406 (Apr. 20, 2012). |
Third Office Action for Chinese Patent Application No. 200680051295.9 (Mar. 20, 2012). |
Advisory Action for U.S. Appl. No. 11/635,406 (Mar. 14, 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). |
Decision to Grant a European Patent Pursuant to Article 97(1) EPC for European Patent Application No. 06844747.3 (Jan. 19, 2012). |
Final Official Action for U.S. Appl. No. 11/635,406 (Nov. 30, 2011). |
Second Office Action for Chinese Patent Application No. 200680051295.9 (Oct. 9, 2011). |
Notice of Panel Decision from Pre-Appeal Brief Review for U.S. Appl. No. 11/635,406 (Oct. 3, 2011). |
Communication under Rule 71(3) EPC for European Application No. 06 844 747.3 (Jul. 19, 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). |
“Ericsson Unified Number Portability,” (Downloaded from the Internet on Jan. 24, 2011). |
Chinese Official Action for Chinese Patent Application No. 200680051295.9 (Dec. 24, 2010). |
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/034372 (Nov. 30, 2010). |
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 11/291,502 (Oct. 5, 2010). |
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). |
Tsou et al., “Realm-Based Redirection in Diameter,” draft-ietf-dime-realm-based-redirect-03, RFC 3588, pp. 1-6 (Jul. 12, 2010). |
Communication Pursuant to Article 94(3) EPC for European Application No. 06844747.3 (May 11, 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). |
Final Official Action for U.S. Appl. No. 11/291,502 (Feb. 4, 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). |
Supplementary European Search Report for European application No. 07810606.9 (Nov. 23, 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). |
Communication pursuant to Article 94(3) EPC for European Application No. 06844747.3 (Jul. 28, 2009). |
Notification Concerning Transmittal of International Preliminary Report on Patentability for International Application No. PCT/US2007/024418 (Jun. 18, 2009). |
Final Official Action for U.S. Appl. No. 11/879,737 (Jun. 9, 2009). |
Official Action for U.S. Appl. No. 11/291,502 (May 13, 2009). |
Supplementary European Search Report for European Application No. 06844747.3 (Apr. 24, 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). |
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 Concerning Transmittal of International Preliminary Report on Patentability for International Application No. PCT/US2006/046108 (Oct. 2, 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/US2006/046108 (Sep. 9, 2008). |
Communication of European publication number and information on the application of Article 67(3) EPC for Application No. 06844747.3 (Jul. 23, 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). |
“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). |
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). |
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). |
Cisco, “Quality of Service Networks,” Internetworking Technologies Handbook, Chapter 49, pp. 49-1-49-32 (Sep. 11, 2003). |
Calhoun et al., “Diameter Base Protocol,” RFC 3588, pp. 1-90 (Sep. 2003). |
Moodie, “Agilent acceSS7: White Paper,” Agilent Technologies, pp. 1-14 (Apr. 1, 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). |
Barry, “A Signal for Savings,” Packet, Cisco Systems Users Magazine, vol. 14, No. 4, pp. Cover; 19-21; and 81 (Fourth Quarter 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). |
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). |
Etsi, “Digital Cellular Telecommunications Systems (Phase 2+); Support of Mobile Number Portability (MNP); Technical Realisation; Stage 2,” Global System for Mobile Communications, p. 1-71, (1998). |
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 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). |
Neustar, “ENUM: Driving Convergence in the Internet Age,” pp. 1-5 (Publication Date Unknown). |
Second Office Action for Chinese Application No. 200880103119.4 (Mar. 19, 2013). |
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 12/777,853 (Feb. 7, 2013). |
First Examination Report for Indian Application No. 3231/CHENP/2008 (Jan. 2, 2013). |
Third Office Action for Chinese Application No. 200880103119.4 (Aug. 19, 2013). |
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). |
Communication of European publication number and information on the application of Aticle 67(3) EPC for Euopean Application No. 12760372.8 (Jan. 7, 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). |
Second Office Action for Indian Application No. 3231/CHENP/2008 (Aug. 8, 2013). |
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; IP Multimedia Subsystem (IMS); Stage 2 (Release 8),” 36PP TS 23.228, V8.1.0 (Jun. 2007). |
Number | Date | Country | |
---|---|---|---|
20120236871 A1 | Sep 2012 | US |
Number | Date | Country | |
---|---|---|---|
61454462 | Mar 2011 | US |