US 7,787,445 B2Grant
Methods, systems, and computer program products for routing and processing ENUM queries
Issue Date:2010-08-31
•20 Claims
•6 Drawing Sheets
Abstract
The subject matter described herein includes methods, systems, and computer program products for routing ENUM queries to an ENUM database. According to one aspect, the subject matter described herein includes a method for routing ENUM queries to an ENUM database. The method includes receiving an ENUM query including a subscriber identifier. An ENUM database is identified among a plurality of non-identically provisioned ENUM databases based on the subscriber identifier. The ENUM query is routed to the identified ENUM database.
Metadata
Assignee
- Tekelec
Inventor
- Peter J. Marsico
Application Information
Application Number:US 11/879,737
Filing Date:2007-07-18
Priority Date:2006-07-20
Art Unit:2614
Classifications
IPC:
H04L12/66H04L12/28H04L12/56
Patent Drawings (6 sheets)
Description
Related Applications
[0001] This application claims the benefit of U.S. Provisional Patent Application Ser. No. 60/832,084 filed Jul. 20, 2006; the disclosure of which is incorporated herein by reference in its entirety.
Technical Field
[0002] The subject matter described herein relates to ENUM queries. More specifically, the subject matter relates to methods, systems, and computer program products for routing and processing ENUM queries.
Background
[0003] E.164 number mapping (ENUM) refers to the translation of E.164-formatted telephone numbers into uniform resource indicators (URIs) resolvable by a domain name system (DNS) server into Internet protocol (IP) addresses. ENUM has been extensively deployed worldwide in order to provide integration between IP networks, such as the Internet, and the public switched telephone network (PSTN). In one proposal, as described in RFC 2916, the telephone number format used in ENUM translation is the E.164 number format. According to ITU-T standards, an E.164 telephone number may include up to 15 digits and include a leading + symbol indicating that the number is globally unique. For example, a valid E.164 telephone number may include +420-123456789. ENUM translation of an E.164 number into an IP network identifier may include formulating an ENUM query including the E.164 number and querying an ENUM database containing one or more naming authority pointer (NAPTR) records that associate individual E.164 numbers with one or more IP network identifiers. A NAPTR record is a type of DNS record that supports regular-expression-based rewriting, where each network identifier within the NAPTR record may differentiated based on a variety of parameters. Thus, a NAPTR record may contain multiple URIs associated with a single telephone number, where each URI may be differentiated based on an order, a preference, and a service. For example, the E.164 telephone number +420-123456789 may be associated with SIP URI [email protected], H.323 URI [email protected], and email URI [email protected] within a NAPTR record located in an ENUM database.
[0004] Upon receiving an ENUM query, the ENUM database may locate and return the NAPTR record associated with the telephone number included in the query. Additional translations may be required in order to select a particular network identifier from within the provided NAPTR record to first attempt to connect to. Typically, ENUM queries are processed by an ENUM database located near the query originator in order to reduce the response time for an ENUM response. Therefore, conventionally, multiple identically provisioned ENUM databases may be distributed throughout a particular geographic area such that each database is capable of responding to an ENUM query associated with any subscriber within the network.
[0005] One problem with some conventional ENUM systems is that all ENUM databases contain a complete set of ENUM data associated with all subscribers in the network. Yet as more subscribers and services are added to existing networks, including text and multimedia messaging services, voice over IP (VoIP), and other Internet multimedia subsystem (IMS) services, the volume of ENUM data stored in each of these ENUM databases increases correspondingly. As the volume of ENUM data increases, it becomes increasingly difficult to maintain all ENUM data within a single ENUM database.
[0006] In ENUM database systems where multiple identically provisioned databases serve a network, routing is simple because queries can be sent to any of the databases for translations. For example, queries may be load shared among identically provisioned ENUM databases.
[0007] In some instances, ENUM databases that serve a network may not be identically provisioned. For example, when an operator's existing ENUM database becomes maximally utilized, the operator may desire to bring a new ENUM database into service and move a portion of the subscriber data from the old ENUM database to the new ENUM database. As a result of moving the portion of the subscriber data to the new ENUM database, the new and old ENUM databases do not contain identical sets of subscribers ENUM data. Consequently, switches that formulate ENUM queries must be provisioned with location information that identifies the ENUM database that holds a particular subscriber's data. Requiring switches to be reprovisioned with ENUM database location information for each subscriber is labor intensive, especially in networks with a large number of existing switches. Such reprovisioning can be required any time the service provider desires to move subscriber ENUM data among ENUM databases. As a result, there exists a need for improved methods, systems, and computer program products for routing and processing ENUM queries.
Summary
[0008] The subject matter described herein includes methods, systems, and computer program products for routing ENUM queries to an ENUM database. According to one aspect, the subject matter described herein includes a method for routing ENUM queries to an ENUM database. The method includes receiving an ENUM query including a subscriber identifier. An ENUM database is identified among a plurality of non-identically provisioned ENUM databases based on the subscriber identifier. The ENUM query is routed to the identified ENUM database.
[0009] According to another aspect, the subject matter described herein includes a flexible ENUM routing node for routing ENUM queries to an ENUM database. The flexible ENUM routing node includes a communications module for receiving an ENUM query including a subscriber identifier and an E.164-to-ENUM database identifier mapping data structure for associating one or more subscriber identifiers with one or more ENUM database identifiers. The flexible ENUM routing node further includes an ENUM database identifier function for identifying, based on the subscriber identifier and using the E.164-to-ENUM database identifier mapping data structure, an ENUM database from a plurality of non-identically provisioned ENUM databases, and for routing the ENUM query to the identified ENUM database.
[0010] The subject matter described herein may be implemented using a computer program product comprising computer executable instructions embodied in a computer readable medium. Exemplary computer readable media suitable for implementing the subject matter described herein include chip memory devices, disc memory devices, application specific integrated circuits, and programmable logic devices. In addition, a computer program product that implements a subject matter described herein may reside on a single device or computing platform or maybe distributed across multiple devices or computing platforms.
Brief Description of the Drawings
[0011] The subject matter described herein will now be explained with reference to the accompanying drawings of which:
[0012] FIG. 1 is a network diagram of an exemplary system for routing ENUM queries to an ENUM database including a range-based E.164-to-ENUM database identifier mapping data structure according to an embodiment of the subject matter described herein;
[0013] FIG. 2 is a network diagram of an exemplary system for routing ENUM queries to an ENUM database including a combination range-based and exception-based E.164-to-ENUM database identifier mapping data structure according to an embodiment of the subject matter described herein;
[0014] FIG. 3 is a flow chart of an exemplary process for routing ENUM queries to an ENUM database according to an embodiment of the subject matter described herein;
[0015] FIG. 4 is a block diagram of an exemplary internal architecture of a flexible ENUM routing node for routing ENUM queries to an ENUM database according to an embodiment of the subject matter described herein; and
[0016] FIG. 5 is a network diagram of an exemplary system for routing ENUM queries to an ENUM database.
Detailed Description
[0017] The subject matter described herein includes methods, systems, and computer program products for routing and processing ENUM queries. FIG. 1 is a network diagram of an exemplary system for routing ENUM queries to an ENUM database. In FIG. 1 , the system includes a range-based E.164-to-ENUM database identifier mapping data structure. Referring to FIG. 1 , network 100 may include a signaling point (SP) 102, a flexible ENUM routing node 104, and ENUM databases 106, 108 and 110. SP 102 may be connected to flexible ENUM routing node 104 via a communications link, such as a signaling system number 7 (SS7) communications link, an IP communications link, or an SS7-over-IP communications link, for communicating signaling messages, such as ENUM query and response messages, with flexible ENUM routing node 104. Similarly, flexible ENUM routing node 104 may be connected to ENUM databases 106-110 via one or more suitable communications links for sending and receiving ENUM query messages and ENUM response messages with ENUM databases 106-110.
[0018] SP 102 may be any suitable network element for generating and/or transmitting ENUM queries within network 100 according to the subject matter described herein. For example, SP 102 may include be a mobile switching center (MSC), a media gateway controller (MGC), a session initiation protocol (SIP) proxy server, an H.323 gatekeeper, an IP multimedia subsystem (IMS) node, or other suitable node for generating ENUM queries.
[0019] ENUM data may be distributed across ENUM databases 106-110, where, in one example, each ENUM database 106-110 may contain a subset of the ENUM data associated with subscribers within network 100. For example, ENUM database 106 may contain ENUM data associated with a first set of subscribers, ENUM database 108 may contain ENUM data associated with a second set of subscribers, and ENUM database 110 may contain ENUM data associated with a third set of subscribers. Therefore, collectively, ENUM databases 106-110 contain a complete set of ENUM data associated with subscribers in network 100. In another example, ENUM databases 106-110 may include some overlapping data.
[0020] Within network 100, ENUM databases 106-110 may be identified by one or more network identifiers. In the embodiment illustrated in FIG. 1 , ENUM databases 106-110 may be identified by network identifiers including a uniform resource indicator and a combination of an IP address and a port number. For example, ENUM database 106 may be identified within network 100 by [email protected] and 100.98.10.0/port x, where port x indicates any suitable port value selected from all available ports and conforming to conventional port numbering rules so as not to conflict with other services operating on ENUM database 106. ENUM databases 108 and 110 may be similarly identified by URIs [email protected] and [email protected] and IP addresses/port numbers 100.98.10.1/port x and 100.98.10.2/port x, respectively. It is appreciated that in addition to the network identifiers described above, other identifiers may be used for identifying ENUM databases 106-110 within network 100 without departing from the scope of the subject matter described herein.
[0021] In FIG. 1 , ENUM queries including a subscriber identifier, such as an E.164 number, may be generated by SP 102 and transmitted to flexible ENUM routing node 104. ENUM queries may be received by flexible ENUM routing node 104 and a lookup may be performed to determine the appropriate ENUM database from among ENUM databases 106-110 to process the query. For example, flexible ENUM routing node 104 may include E.164-to-ENUM database identifier mapping data structure 112 for associating ranges of E.164 telephone numbers with ENUM database URIs and IP address/port combinations. Referring to table 112, E.164 numbers 1-234-234-2000 through 1-234-234-2999 are associated with [email protected] and 100.98.10.0/port x, and E.164 numbers 1-234-234-3000 through 1-234-234-3999 are associated with [email protected] and 100.98.10.1/port x. A lookup may be performed using table 112 based on a received E.164 address by locating a row in table 112 where the searched number may be located between the values of the E.164 numbers located in the first and second columns. In addition to the data structure illustrated in FIG. 1 , it is appreciated that E.164-to-ENUM database identifier mapping data structure 112 may include other data structures, including a database, a flat file, a list, an array, and a binary tree, without departing from the scope of the subject matter described herein. Table 112 may be located in computer readable medium, such as random access memory (RAM), or any other suitable means according to the subject matter described herein.
[0022] In the example illustrated in FIG. 1 , ENUM query 114 may be received by flexible ENUM routing node 104, where ENUM query 114 includes the address 1.4.3.2.4.3.2.4.3.2.1.e164.arpa corresponding to E.164 telephone number 1-234-234-2341. It is appreciated that in other embodiments, ENUM query 114 may be addressed to flexible ENUM routing node 104 or may be addressed to one of ENUM databases 106-110. Therefore, flexible ENUM routing node 104 may be configured to receive ENUM queries addressed to it directly, or may intercept ENUM queries addressed to one of ENUM databases 106-110.
[0023] Upon receiving ENUM query 114, flexible ENUM routing node 104 may perform a lookup in E.164-to-ENUM database identifier mapping data structure 112 as described above to locate a URI or an IP address/port number associated with one of ENUM databases 106-110. In this example, a lookup performed may result in determining that 1-234-234-2341 is within the range indicated by the first row of table 112, and therefore, network address information corresponding to ENUM database 106 is returned. For example, flexible ENUM routing node 104 may locate URI [email protected] and IP address/port number 100.98.10.0/port x and modify ENUM query 118 to include the determined ENUM database address.
[0024] In one embodiment, flexible ENUM routing node 104 may modify ENUM query 114 to include the ENUM database address determined in the lookup and route the query to the determined ENUM database, as indicated by modified ENUM query 116 illustrated in FIG. 1 . Modified ENUM query 116 may be delivered to ENUM database 106 for processing. In another embodiment, flexible ENUM routing node 104 may forward unmodified ENUM query 114 to one of ENUM databases 106-110 identified in the lookup in table 112. It is appreciated that an intermediate DNS query may be generated by flexible ENUM routing node 104 to obtain an IP address and port number for modifying and delivering ENUM query 114 to ENUM database 106 as described above if, for example, a URI is returned as the result of a lookup in E.164-to-ENUM database identifier mapping data structure.
[0025] Upon receiving modified ENUM query 116, ENUM database 106 may locate a NAPTR record associated with the subscriber identifier included in query 114 and generate ENUM response 118. ENUM response 118 may be sent directly to SP 102 in one embodiment or, alternately, may be routed to SP 102 via flexible ENUM routing node 104.
[0026] FIG. 2 is a network diagram of an exemplary system for routing ENUM queries to an ENUM database. In FIG. 2 , the system includes a range-based data structure and an exception-based data structure for identifying an ENUM database. In contrast to the embodiment shown in FIG. 1 , ENUM routing table 112 shown in FIG. 2 includes an exception-based data structure in addition to a range-based data structure. As used herein, a range-based data structure is a data structure in which entries are indexed by ranges of subscriber identifiers. For example, each entry in range based data structure 200 illustrated in FIG. 2 is indexed by a range of E.164 numbers. As used herein, an exception-based data structure is a data structure whose entries are indexed by individual subscriber identifiers that are exceptions to the ranges by which the entries in the range-based data structure are indexed. An exception may be a subscriber that is within one of the ranges in the range-based data structure but specifies a different ENUM server or an entry that is outside of all the ranges in the range-based data structure. For example, the entry in exception-based data structure 201 indexed by the individual E.164 number 1234-234-3342 is within the range corresponding to the second entry in range data structure 200. However, the entry in exception data structure 201 returns the ENUM server ENUM 1 while the range-based entry in data structure 202 returns the ENUM server ENUM 2. It may be desirable to provision an individual number that is an exception to a range of numbers, for example, when moving subscriber identifiers among ENUM databases for load balancing purposes or when new databases are brought into service. Because such numbers can be reallocated among the databases and the routing information needs only to be changed at flexible routing node 104, efficiency is achieved over implementations where each individual query originator, such as SP 102 needs to be modified with the new ENUM database information. Another example of an exception-based entry may occur when a subscriber is ported-in to a service provider's network. When the subscriber is ported in and maintains the same E.164 number, the subscriber's ENUM translation information may be assigned to one of the new service provider's ENUM databases, even though the E.164 number of the subscriber is outside of all the ranges of subscriber identifiers corresponding to the service provider's ENUM databases.
[0027] In the scenario illustrated in FIG. 2 , flexible ENUM routing node 104 may receive ENUM query 202 including 2.4.3.3.4.3.2.4.3.2.1.e164.arpa corresponding to E.164 number 1-234-234-3342. Upon receiving ENUM query 202, flexible ENUM routing node 104 may first perform a lookup in exception-based data structure 201 for an entry matching 1-234-234-3342. In this example, exception-based data structure 201 includes one entry matching queried address 1-234-234-3342. Accordingly, no further searching need be performed and network address information corresponding to ENUM database 106 may be returned for routing query 202 to ENUM database 106.
[0028] Alternately, if a lookup performed in exception-based data structure 201 fails to locate a match, a lookup may be performed in range-based data structure 200 in a manner like that described above with respect to FIG. 1 . For example, if ENUM query 202 had included telephone number 1-234-234-2000, then a lookup performed in exception-based data structure 201 would fail to locate a match, and an entry located in the first row of the range data structure would be returned including [email protected] and/or 100.98.10.0/port x. After determining the ENUM database identifier associated with the subscriber identifier extracted from ENUM query 202, flexible ENUM routing node 104 may modify and/or forward the ENUM query to ENUM database 106.
[0029] FIG. 3 is a flow chart of an exemplary process for distributing and accessing ENUM data located in multiple ENUM databases according to an embodiment of the subject matter described herein. In block 300, an ENUM query including a subscriber identifier is received. For example, as described above, signaling point 102 may generate ENUM query 114 including an E.164 telephone number and transmit the ENUM query to, or the ENUM query may be intercepted by, flexible ENUM routing node 104.
[0030] In block 302, an ENUM database is identified among a plurality of non-identically provisioned ENUM databases based on the subscriber identifier. For example, as illustrated in FIGS. 1 and 2 , network 100 may include multiple ENUM databases 106, 108, and 110 containing ENUM data associated with a first set of subscribers, a second set of subscribers, and a third set of subscribers, respectively. The ENUM data stored in databases 106, 108, and 110 may be non-overlapping or partially overlapping. The determination of an ENUM database identifier associated with the E.164 number included in a received ENUM query may be made by searching an E.164-to-ENUM database identifier mapping data structure associating one or more E.164 numbers with one or more ENUM database identifiers.
[0031] As described above, E.164-to-ENUM database identifier mapping data structure may include a range-based data structure, a combination of exception-based and range-based data structures, or any other suitable data structure indexed by E.164 numbers. Such a data structure may be implemented using any suitable construct, such as a table, a flat file, a list, an array, a tree, or a trie. As stated above, in FIGS. 1 and 2 , E.164-to-ENUM database identifier mapping data structures 112, 200, and 201 include a range-based table and a combination exception-based and range-based table, respectively. Because the E.164-to-ENUM database identifier mapping data structure may be indexed by individual E.164 numbers or by ranges of E.164 numbers, ENUM databases may be added or removed dynamically and ENUM data may be redistributed across ENUM databases so as to provide for more efficient usage of ENUM database storage resources. Moreover, by segmenting ENUM data and storing it across multiple ENUM databases, ENUM service providers may more easily scale with increases in ENUM data volume.
[0032] In block 304, the ENUM query is routed to the identified ENUM database. For example, based on ENUM database identifier 100.98.10.0/port x, flexible ENUM routing node 104 may route a received ENUM query to ENUM database 106. According to one embodiment, routing the ENUM query to the appropriate ENUM database may include modifying the ENUM query to include the ENUM database identifier determined in block 302. For example, flexible ENUM routing node 104 may generate modified ENUM query 116 including IP address 100.98.10.0 and port x for delivery to ENUM database 106. It is appreciated that in addition to the exemplary network components shown in FIGS. 1 and 2 , additional network components (not shown) may be located between flexible ENUM routing node 104 and one or more of ENUM databases 106-110, where additional network components (not shown) may route ENUM queries to ENUM databases 106-110 according to conventional methods.
[0033] FIG. 4 is a block diagram of an exemplary internal architecture of a flexible ENUM routing node 104 according to an embodiment of the subject matter described herein. Referring to FIG. 4 , exemplary flexible ENUM routing node 104 may include communication module 400 and flexible ENUM processing modules 402 and 404 connected via a bus 406. As illustrated in FIG. 4 , it is appreciated that one or more ENUM processing modules may be included in flexible ENUM routing node 104.
[0034] It is further appreciated that the components and/or the functionality of flexible ENUM routing node 104 may be implemented in a standalone network element, may be incorporated into an existing network element, or may be distributed across multiple network elements. For example, flexible ENUM routing according to the subject matter described herein may be provided by a signaling gateway node, a network router, an SS7-IP router, an IP router, a SIP server, an IMS node such as a CSCF, a softswitch, an application server, or any other communications network element.
[0035] Communication module 400 may include an SS7 or IP stack 408 and a distribution module 410. Stack 408 may be configured to send and receive messages, such as ENUM query and response messages, via a communications network. For example, stack 408 may be connected to an SS7 or IP network and configured to receive ENUM query 405 and send modified ENUM query 409. Distribution module 410 may receive messages from stack 408 and distribute them among ENUM processing modules 402. For example, distribution module 410 may receive ENUM query 405 from stack 408 and send the query to ENUM processing module 402 for processing. In one implementation, ENUM processing modules 402 and 404 may be identically provisioned. As a result, distributions module 410 may load share queries between ENUM processing modules 402 and 404.
[0036] ENUM processing module 402 may include an ENUM database identifier function 412, an E.164-to-ENUM database mapping data structure 414, and a routing function 416. ENUM database identifier function 412 may receive ENUM query messages from distribution function 410 via internal communications bus 406 and may extract an E.164 subscriber identifier used to query E.164-to-ENUM database identifier mapping data structure 414. Data structure 414 may be provisioned as a range-based data structure (see FIG. 1 ), as a combination of range-based and exception-based data structures (see FIG. 2 ), or as any other suitable data structure for providing access to ENUM database location information. If a matching entry in mapping data structure 414 is located, ENUM database identifier function 412 may modify ENUM query 405 to include the address of the determined ENUM database. The modified ENUM query may then be passed to routing function 416 for delivery to the appropriate ENUM database via stack 408 on communications module 400. For example, routing function 416 may determine on which outbound communication link, socket, SCTP association or other suitable connection the modified query is to be transmitted. ENUM query processing module 404 may be identically provisioned to module 404. However, a description of the corresponding components will not be repeated herein.
[0037] In the examples described above, flexible routing node 104 routes ENUM queries to ENUM databases. In alternate implementation, flexible routing node 104 may terminate ENUM queries, store state information relating to ENUM transactions, originate new ENUM queries, process responses, pair responses with queries using stored state information, and forward ENUM responses to query originators. Such an implementation is illustrated in FIG. 5 . In FIG. 5 , flexible routing node 104 receives an ENUM query from signaling point 102. The ENUM query may be addressed to flexible routing node 104. Flexible routing node 104 identifies the ENUM database to which the query should be routed using any of the methods described above. Rather than routing the original query to the database, flexible routing node 104 sends a new ENUM query to the ENUM database, which in this example is ENUM database 106. Flexible routing node 104 also stores state information indicating that the ENUM query that it sent to database 106 corresponds to a receipt received ENUM query from node 102. This information may be stored on the processing module 402 or 404 to which the original ENUM query was routed. In addition, distribution function 410 may store information that identifies the processing module that processes a particular ENUM query.
[0038] When ENUM database 106 responds to the ENUM query from routing node 104, the ENUM response is received by communication interface 400 illustrated in FIG. 4 . Distribution function 410 forwards the response to the processing module that originated the ENUM query. That processing module pairs the ENUM response data with the original query, formulates a new response, and routes the response to the query originator, which in this example is SP 102. Accordingly, a flexible ENUM routing node according to the subject matter described herein may have a stateful implementation. Such an implementation, simplifies processing by query originators because the query originators simply forward ENUM queries to flexible routing node 104 and flexible routing node 104 handles the processing with the ENUM databases to obtain the ENUM translation information.
[0039] It will be understood that various details of the subject matter described herein may be changed without departing from the scope of the subject matter described herein. Furthermore, the foregoing description is for the purpose of illustration only, and not for the purpose of limitation, as the subject matter described herein is defined by the claims as set forth hereinafter.
Claims
What is claimed is:
1. A method for routing E.164 number mapping (ENUM) queries to an ENUM database, the method comprising:
receiving an ENUM query including a subscriber identifier;
identifying an ENUM database among a plurality of non-identically provisioned ENUM databases belonging to the same service provider's network based on the subscriber identifier, wherein each of the ENUM databases contains ENUM data associated with subscribers belonging to the same service provider's network and wherein at least some of the ENUM databases contain ENUM data for different subscribers belonging to the same service provider's network, wherein receiving an ENUM query includes receiving an ENUM query including an E.164 telephone number and wherein identifying an ENUM database includes searching a range-based data structure using the subscriber identifier; and
routing the ENUM query to the identified ENUM database.
2. The method of claim 1 wherein receiving an ENUM query includes receiving an ENUM query generated by one of a service switching point (SSP), a mobile switching center (MSC), a media gateway controller (MGC), a session initiation protocol (SIP) proxy server, an H.323 gatekeeper, and an IP multimedia subsystem (IMS) node.
3. The method of claim 1 wherein receiving an ENUM query includes receiving an ENUM query at a flexible ENUM routing node where the query is addressed to the flexible ENUM routing node.
4. The method of claim 1 wherein receiving an ENUM query includes intercepting an ENUM query addressed to an ENUM database.
5. The method of claim 1 wherein identifying an ENUM database includes searching an exception-based data structure and, in response to failing to identify an ENUM database corresponding to the subscriber identifier in the exception-based data structure, searching the range-based data structure.
6. The method of claim 1 wherein identifying an ENUM database includes determining at least one of a uniform resource indicator (URI), an IP address, and a port number associated with the identified ENUM database.
7. The method of claim 1 wherein identifying an ENUM database includes determining a uniform resource indicator (URI) associated with the identified ENUM database.
8. The method of claim 1 wherein routing an ENUM query includes modifying the ENUM query to include the address of the identified ENUM database.
9. A method for processing an E.164 number mapping (ENUM) query, the method comprising:
receiving an ENUM query including a subscriber identifier;
utilizing the subscriber identifier to identify an ENUM database among a plurality of non-identically provisioned ENUM databases belonging to the same service provider's network, wherein each of the ENUM databases contains ENUM data associated with subscribers belonging to the same service provider's network and wherein at least some of the ENUM databases contain ENUM data for different subscribers belonging to the same service provider's network, wherein receiving an ENUM query including a subscriber identifier includes receiving an ENUM query that includes an E.164 telephone number and wherein utilizing the subscriber identifier to identify an ENUM database includes searching a range-based data structure utilizing the subscriber identifier; and
terminating the ENUM query, generating and forwarding a new ENUM query to the identified ENUM database.
10. The method of claim 9 comprising storing state information for an ENUM transaction associated with the ENUM queries.
11. The method of claim 10 comprising:
receiving an ENUM response;
associating the ENUM response with the ENUM transaction using the stored state information;
terminating the ENUM response, generating a new ENUM response, and forwarding the new ENUM response to an originator of the received ENUM query.
12. A flexible ENUM routing node for routing ENUM queries to an ENUM database, the node comprising:
a communications module for receiving an ENUM query including a subscriber identifier;
an E.164-to-ENUM database identifier mapping data structure for associating one or more subscriber identifiers with one or more ENUM database identifiers; and
an ENUM database identifier function for identifying, based on the subscriber identifier and using the E.164-to-ENUM database identifier mapping data structure, an ENUM database from a plurality of non-identically provisioned ENUM databases belonging to the same service provider's network, wherein each of the ENUM databases contains ENUM data associated with subscribers belonging to the same service provider's network and wherein at least some of the ENUM databases contain ENUM data for different subscribers belonging to the same service provider's network, wherein the E.164-to-ENUM database identifier mapping data structure includes a range-based data structure.
13. The flexible ENUM routing node of claim 12 wherein the communications module is configured to receive an ENUM query generated by one of a service switching point (SSP), a mobile switching center (MSC), a media gateway controller (MGC), a session initiation protocol (SIP) proxy server, an H.323 gatekeeper, and an IP multimedia subsystem (IMS) node.
14. The flexible ENUM routing node of claim 12 wherein the communications module is configured to receive an ENUM query addressed to the flexible ENUM routing node.
15. The flexible ENUM routing node of claim 12 wherein the communications module is configured to intercept an ENUM query addressed to one of the ENUM databases.
16. The flexible ENUM routing node of claim 12 wherein the E.164-to-ENUM database identifier mapping data structure includes an exception-based and the range-based data structure and wherein the ENUM database identifier function is adapted to search the exception-based data structure for an entry matching the subscriber identifier, and, in response to failing to locate a matching entry in the exception-based data structure, to search the range-based data structure for an entry matching the subscriber identifier.
17. The flexible ENUM routing node of claim 12 wherein the ENUM database identifier function is configured to determine at least one of a uniform resource indicator (URI), an IP address, and a port number associated with the identified ENUM database.
18. The flexible ENUM routing node of claim 12 wherein the ENUM database identifier function is configured to determine a uniform resource indicator (URI) associated with the identified ENUM database and to perform a domain name system (DNS) query to resolve the URI into an Internet protocol (IP) address.
19. The flexible ENUM routing node of claim 12 wherein the ENUM database identifier function is configured to modify the ENUM query to include an address of the identified ENUM database.
20. A non-transitory computer program product comprising computer executable instructions embodied in a computer readable medium for performing steps comprising:
receiving an ENUM query including a subscriber identifier;
identifying an ENUM database among a plurality of non-identically provisioned ENUM databases belonging to the same service provider's network based on the subscriber identifier, wherein each of the ENUM databases contains ENUM data associated with subscribers belonging to the same service provider's network and wherein at least some of the ENUM databases contain ENUM data for different subscribers belonging to the same service provider's network, wherein receiving an ENUM query including a subscriber identifier includes receiving an ENUM query that includes an E.164 telephone number and wherein identifying an ENUM database includes searching a range-based data structure utilizing the subscriber identifier; and
routing the ENUM query to the identified ENUM database.
Patent Citations (168)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US4310727(A) | 1982-01-01 | Lawser | Applicant |
| US4754479(A) | 1988-06-01 | Bicknell et al. | Applicant |
| US4819156(A) | 1989-04-01 | DeLorme et al. | Applicant |
| US5089954(A) | 1992-02-01 | Rago | Applicant |
| US5237604(A) | 1993-08-01 | Ryan | Applicant |
| US5247571(A) | 1993-09-01 | Kay et al. | Applicant |
| US5251248(A) | 1993-10-01 | Tokunaga et al. | Applicant |
| US5400390(A) | 1995-03-01 | Salin | Applicant |
| US5422941(A) | 1995-06-01 | Hasenauer et al. | Applicant |
| US5423068(A) | 1995-06-01 | Hecker | Applicant |
| US5430719(A) | 1995-07-01 | Weisser, Jr. | Applicant |
| US5442683(A) | 1995-08-01 | Hoogeveen | Applicant |
| US5455855(A) | 1995-10-01 | Hokari | Applicant |
| US5457736(A) | 1995-10-01 | Cain et al. | Applicant |
| US5481603(A) | 1996-01-01 | Gutierrez et al. | Applicant |
| US5502726(A) | 1996-03-01 | Fischer | Applicant |
| US5504804(A) | 1996-04-01 | Widmark et al. | Applicant |
| US5526400(A) | 1996-06-01 | Nguyen | Applicant |
| US5579372(A) | 1996-11-01 | Åström | Applicant |
| US5590398(A) | 1996-12-01 | Matthews | Applicant |
| US5594942(A) | 1997-01-01 | Antic et al. | Applicant |
| US5623532(A) | 1997-04-01 | Houde et al. | Applicant |
| US5689548(A) | 1997-11-01 | Maupin et al. | Applicant |
| US5706286(A) | 1998-01-01 | Reiman et al. | Applicant |
| US5711002(A) | 1998-01-01 | Foti | Applicant |
| US5819178(A) | 1998-10-01 | Cropper | Applicant |
| US5822694(A) | 1998-10-01 | Coombes et al. | Applicant |
| US5832382(A) | 1998-11-01 | Alperovich | Applicant |
| US5854982(A) | 1998-12-01 | Chambers et al. | Applicant |
| US5878347(A) | 1999-03-01 | Joensuu et al. | Applicant |
| US5890063(A) | 1999-03-01 | Mills | Applicant |
| US5953662(A) | 1999-09-01 | Lindquist et al. | Applicant |
| US5953663(A) | 1999-09-01 | Maupin et al. | Applicant |
| US5983217(A) | 1999-11-01 | Khosravi-Sichani et al. | Applicant |
| US6006098(A) | 1999-12-01 | Rathnasabapathy et al. | Applicant |
| US6011803(A) | 2000-01-01 | Bicknell et al. | Applicant |
| US6014557(A) | 2000-01-01 | Morton et al. | Applicant |
| US6018657(A) | 2000-01-01 | Kennedy, III et al. | Applicant |
| US6038456(A) | 2000-03-01 | Colby et al. | Applicant |
| US6049714(A) | 2000-04-01 | Patel | Applicant |
| US6097960(A) | 2000-08-01 | Rathnasabapathy et al. | Applicant |
| US6115463(A) | 2000-09-01 | Coulombe et al. | Applicant |
| USH1895(H) | 2000-10-01 | Hoffpauir et al. | Applicant |
| US6128377(A) | 2000-10-01 | Sonnenberg | Applicant |
| US6137806(A) | 2000-10-01 | Martinez | Applicant |
| US6138016(A) | 2000-10-01 | Kulkarni et al. | Applicant |
| US6138017(A) | 2000-10-01 | Price et al. | Applicant |
| US6138023(A) | 2000-10-01 | Agarwal et al. | Applicant |
| US6144857(A) | 2000-11-01 | Price et al. | Applicant |
| US6148204(A) | 2000-11-01 | Urs et al. | Applicant |
| US6192242(B1) | 2001-02-01 | Rollender | Applicant |
| US6205210(B1) | 2001-03-01 | Rainey et al. | Applicant |
| US6226517(B1) | 2001-05-01 | Britt et al. | Applicant |
| US6236365(B1) | 2001-05-01 | LeBlanc et al. | Applicant |
| US6263212(B1) | 2001-07-01 | Ross et al. | Applicant |
| US6308075(B1) | 2001-10-01 | Irten et al. | Applicant |
| US6327350(B1) | 2001-12-01 | Spangler et al. | Applicant |
| US6377674(B1) | 2002-04-01 | Chong et al. | Applicant |
| US6411632(B2) | 2002-06-01 | Lindgren et al. | Applicant |
| US6424832(B1) | 2002-07-01 | Britt et al. | Applicant |
| US6434144(B1) | 2002-08-01 | Romanov | Applicant |
| US6463055(B1) | 2002-10-01 | Lupien et al. | Applicant |
| US6505046(B1) | 2003-01-01 | Baker | Applicant |
| US6515997(B1) | 2003-02-01 | Feltner et al. | Applicant |
| US6535746(B1) | 2003-03-01 | Yu et al. | Applicant |
| US6539077(B1) | 2003-03-01 | Ranalli et al. | Applicant |
| US6560216(B1) | 2003-05-01 | McNiff et al. | Applicant |
| US6560456(B1) | 2003-05-01 | Lohtia et al. | Applicant |
| US6574481(B1) | 2003-06-01 | Rathnasabapathy et al. | Applicant |
| US6577723(B1) | 2003-06-01 | Mooney | Applicant |
| US6594258(B1) | 2003-07-01 | Larson et al. | Applicant |
| US6611516(B1) | 2003-08-01 | Pirkola et al. | Applicant |
| US6643511(B1) | 2003-11-01 | Rune et al. | Applicant |
| US6662017(B2) | 2003-12-01 | McCann et al. | Applicant |
| US6683881(B1) | 2004-01-01 | Mijares et al. | Applicant |
| US6684073(B1) | 2004-01-01 | Joss et al. | Applicant |
| US6731926(B1) | 2004-05-01 | Link, II et al. | Applicant |
| US6738636(B2) | 2004-05-01 | Lielbriedis | Applicant |
| US6748057(B2) | 2004-06-01 | Ranalli et al. | Applicant |
| US6775737(B1) | 2004-08-01 | Warkhede et al. | Applicant |
| US6795701(B1) | 2004-09-01 | Baker et al. | Applicant |
| US6836477(B1) | 2004-12-01 | West, Jr. et al. | Applicant |
| US6885872(B2) | 2005-04-01 | McCann et al. | Applicant |
| US6917612(B2) | 2005-07-01 | Foti et al. | Applicant |
| US6950441(B1) | 2005-09-01 | Kaczmarczyk et al. | Applicant |
| US6993038(B2) | 2006-01-01 | McCann | Applicant |
| US7035239(B2) | 2006-04-01 | McCann et al. | Applicant |
| US7079524(B2) | 2006-07-01 | Bantukul et al. | Applicant |
| US7079853(B2) | 2006-07-01 | Rathnasabapathy et al. | Applicant |
| US7085260(B2) | 2006-08-01 | Karaul et al. | Examiner |
| US7092505(B2) | 2006-08-01 | Allison et al. | Applicant |
| US7221952(B2) | 2007-05-01 | Cho et al. | Applicant |
| US7286839(B2) | 2007-10-01 | McCann et al. | Applicant |
| US7366530(B2) | 2008-04-01 | McCann et al. | Applicant |
| US2001/0008532(A1) | 2001-07-01 | Lee | Applicant |
| US2001/0029182(A1) | 2001-10-01 | McCann et al. | Applicant |
| US2001/0030957(A1) | 2001-10-01 | McCann et al. | Applicant |
| US2001/0040957(A1) | 2001-11-01 | McCann et al. | Applicant |
| US2002/0095421(A1) | 2002-07-01 | Koskas | Applicant |
| US2002/0147845(A1) | 2002-10-01 | Sanchez-Herrero et al. | Applicant |
| US2002/0173320(A1) | 2002-11-01 | Aitken et al. | Applicant |
| US2002/0176382(A1) | 2002-11-01 | Madour et al. | Applicant |
| US2003/0007482(A1) | 2003-01-01 | Khello et al. | Examiner |
| US2003/0026289(A1) | 2003-02-01 | Mukherjee et al. | Applicant |
| US2003/0054844(A1) | 2003-03-01 | Anvekar et al. | Applicant |
| US2003/0065788(A1) | 2003-04-01 | Salomaki | Applicant |
| US2003/0081754(A1) | 2003-05-01 | Esparza et al. | Applicant |
| US2003/0109271(A1) | 2003-06-01 | Lewis et al. | Applicant |
| US2003/0128693(A1) | 2003-07-01 | Segal | Examiner |
| US2003/0193967(A1) | 2003-10-01 | Fenton et al. | Applicant |
| US2003/0220951(A1) | 2003-11-01 | Muthulingam et al. | Applicant |
| US2003/0227899(A1) | 2003-12-01 | McCann | Applicant |
| US2004/0034699(A1) | 2004-02-01 | Gotz et al. | Applicant |
| US2004/0076126(A1) | 2004-04-01 | Qu et al. | Applicant |
| US2004/0081206(A1) | 2004-04-01 | Allison et al. | Applicant |
| US2004/0082332(A1) | 2004-04-01 | McCann et al. | Applicant |
| US2004/0087300(A1) | 2004-05-01 | Lewis | Applicant |
| US2004/0142707(A1) | 2004-07-01 | Midkiff et al. | Applicant |
| US2004/0198351(A1) | 2004-10-01 | Knotts | Applicant |
| US2004/0202187(A1) | 2004-10-01 | Kelly et al. | Applicant |
| US2004/0246965(A1) | 2004-12-01 | Westman et al. | Applicant |
| US2005/0003838(A1) | 2005-01-01 | McCann et al. | Applicant |
| US2005/0101297(A1) | 2005-05-01 | Delaney et al. | Applicant |
| US2005/0119017(A1) | 2005-06-01 | Lovell, Jr. et al. | Applicant |
| US2005/0251509(A1) | 2005-11-01 | Pontius | Applicant |
| US2005/0286531(A1) | 2005-12-01 | Tuohino et al. | Examiner |
| US2005/0286695(A1) | 2005-12-01 | Pershan et al. | Examiner |
| US2006/0067338(A1) | 2006-03-01 | Hua et al. | Applicant |
| US2006/0098621(A1) | 2006-05-01 | Plata et al. | Applicant |
| US2006/0136557(A1) | 2006-06-01 | Schaedler et al. | Applicant |
| US2007/0061397(A1) | 2007-03-01 | Gregorat et al. | Applicant |
| US2007/0121879(A1) | 2007-05-01 | McGary et al. | Examiner |
| US2007/0133574(A1) | 2007-06-01 | Tejani et al. | Applicant |
| US2007/0203909(A1) | 2007-08-01 | Marathe et al. | Applicant |
| US2007/0286379(A1) | 2007-12-01 | Wiatrowski et al. | Applicant |
| US2008/0130856(A1) | 2008-06-01 | Ku et al. | Examiner |
| US2008/0311917(A1) | 2008-12-01 | Marathe et al. | Applicant |
| US2009/0103707(A1) | 2009-04-01 | McGary et al. | Examiner |
| US2009/0227276(A1) | 2009-09-01 | Agarwal et al. | Applicant |
| EP512962(A2) | 1992-11-01 | Applicant | |
| EP936825(A3) | 1999-08-01 | Applicant | |
| EP944276(A1) | 1999-09-01 | Applicant | |
| EP1527536 | 2003-12-01 | Applicant | |
| EP1558004(A) | 2005-07-01 | Applicant | |
| WO95/12292(A1) | 1995-05-01 | Applicant | |
| WO96/11557 | 1996-04-01 | Applicant | |
| WO97/33441(A1) | 1997-09-01 | Applicant | |
| WO98/56195 | 1998-12-01 | Applicant | |
| WO99/11087(A2) | 1999-03-01 | Applicant | |
| WO99/57926 | 1999-11-01 | Applicant | |
| WO/16583(A1) | 2000-03-01 | Applicant | |
| WO/60821 | 2000-10-01 | Applicant | |
| WO1/47297(A2) | 2001-06-01 | Applicant | |
| WO1/48981(A1) | 2001-07-01 | Applicant | |
| WO1/54444(A1) | 2001-07-01 | Applicant | |
| WO3/005664(A2) | 2003-01-01 | Applicant | |
| WO3/021982(A1) | 2003-03-01 | Applicant | |
| WO3/105382(A1) | 2003-12-01 | Applicant | |
| WO2004/006534 | 2004-01-01 | Applicant | |
| WO2004/087686(A) | 2004-01-01 | Applicant | |
| WO2004/075507 | 2004-09-01 | Applicant | |
| WO2004/102345(A2) | 2004-11-01 | Applicant | |
| WO2005/013538(A3) | 2005-02-01 | Applicant | |
| WO2007/045991(A1) | 2007-04-01 | Applicant | |
| WO2007/064943(A2) | 2007-06-01 | Applicant | |
| WO2007/092205(A2) | 2007-08-01 | Applicant | |
| WO2007/146257(A2) | 2007-12-01 | Applicant | |
| WO2008/157213(A2) | 2008-12-01 | Applicant |
Non-Patent Literature (110)
- Commonly-assigned, co-pending U.S. Appl. No. 11/605,837 for “Methods, Systems and Computer Program Products for Accessing Number Portability (NP) and E.164 Number (ENUM) Data Using a Common NP/Enum Data Locator Structure,” (Unpublished, filed Nov. 29, 2006).Applicant
- 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).Applicant
- Notification Concerning Transmittal of International Preliminary Report on Patentability for Internation Application No. PCT/US2007/002520 (Aug. 21, 2008).Applicant
- Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration for Internation Application No. PCT/US07/02520 (Mar. 3, 2008).Applicant
- 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).Applicant
- Official Action for U.S. Appl. No. 11/364,759 (Mar. 30, 2009).Applicant
- Final Official Action for U.S. Appl. No. 11/291,502 (Feb. 4, 2010).Applicant
- Final Official Action for U.S. Appl. No. 11/364,759 (Jan. 21, 2010).Applicant
- Supplementary European Search Report for European application No. 07810606.9 (Nov. 23, 2009).Applicant
- Supplementary European Search Report for European Patent No. 1676386 (Oct. 30, 2009).Applicant
- 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).Applicant
- Supplementary European Search Report for European application No. 04751843.6 (Aug. 7, 2009).Applicant
- Communication pursuant to Article 94(3) EPC for European application No. 06844747.3 (Jul. 28, 2009).Applicant
- Official Action for U.S. Appl. No. 11/291,502 (May 13, 2009).Applicant
- Supplementary European Search Report for European Application No. 06844747.3 (Apr. 24, 2009).Applicant
- 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/072641 (Feb. 24, 2009).Applicant
- 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).Applicant
- Notification Concerning Transmittal of International Preliminary Report on Patentability for International Application No. PCT/US2006/046108 (Oct. 2, 2008).Applicant
- 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).Applicant
- Communication of European publication number and information on the application of Article 67(3) EPC for Application No. 06844747.3 (Jul. 23, 2008).Applicant
- Notice of Allowance and Fee(s) Due for U.S. Appl. No. 11/112,126 (Mar. 28, 2008).Applicant
- Notice of Allowance and Fee(s) Due for U.S. Appl. No. 11/112,126 (Dec. 17, 2007).Applicant
- Notice of Allowance for U.S. Appl. No. 10/729,519 (Jul. 30, 2007).Applicant
- Official Action for U.S. Appl. No. 11/112,126 (Jun. 15, 2007).Applicant
- “IP Multimedia Subsystem,” printout from wikipedia.org, Wikimedia Foundation, Inc. (May 29, 2007).Applicant
- Official Action for U.S. Appl. No. 10/729,519 (Nov. 28, 2006).Applicant
- Notification Concerning Transmittal of International Preliminary Report on Patentability for International Application No. PCT/US2004/024328 (Jul. 20, 2006).Applicant
- “HP OperCall Home Subscriber Server Software—Data Sheet”, 4AA0-3360ENW Rev. 2, Hewlett-Packard Development Company, L.P. (Jul. 2006).Applicant
- Notice of Allowance for U.S. Appl. No. 10/631,586 (May 25, 2006).Applicant
- Notification of Transmittal of the International Search Report, or the Declaration and Written Opinion of the International Searching Authority for International Application No. PCT/US2004/024328 (Apr. 25, 2006).Applicant
- Supplemental Notice of Allowance for U.S. Appl. No. 09/747,070 (Feb. 10, 2006).Applicant
- Communication pursuant to Rules 109 and 110 EPC for European Application No. 04751843.6 (Dec. 16, 2005).Applicant
- Notice of Allowance for U.S. Appl. No. 09/747,070 (Dec. 2, 2005).Applicant
- Interview Summary for U.S. Appl. No. 09/747,070 (Dec. 2, 2005).Applicant
- Notification Concerning Transmittal of International Preliminary Report on Patentability (Chapter I of the Patent Cooperation Treaty) in International Application No. PCT/US2004/014645 (Nov. 24, 2005).Applicant
- Advisory Action for U.S. Appl. No. 09/747,070 (Nov. 1, 2005).Applicant
- Official Action for U.S. Appl. No. 10/631,586 (Oct. 26, 2005).Applicant
- Notice of Allowance for U.S. Appl. No. 10/166,968 (Sep. 20, 2005).Applicant
- Supplemental Notice of Allowance and Fee(s) Due for U.S. Appl. No. 10/842,394 (Feb. 9, 2005).Applicant
- 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/US2004/014645 (Dec. 16, 2004).Applicant
- Notice of Allowance and Fee(s) Due for U.S. Appl. No. 10/842,394 (Dec. 15, 2004).Applicant
- 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/US04/06247 (Nov. 10, 2004).Applicant
- Notice of Allowance for U.S. Appl. No. 09/471,946 (Oct. 15, 2004).Applicant
- Final Official Action for U.S. Appl. No. 09/747,070 (May 11, 2005).Applicant
- Official Action for U.S. Appl. No. 09/747,070 (Jun. 30, 2004).Applicant
- Supplemental Notice of Allowability for U.S. Appl. No. 09/471,946 (May 24, 2004).Applicant
- “Cisco IP Transfer Point as the Signaling Gateway for the Cisco BTS 10200 Softswitch,” Cisco Systems, Inc., pp. 1-10 (Summer 2004).Applicant
- “Cisco IP Transfer Point as the Signaling Gateway for the Cisco PGW 2200 Softswitch,” Cisco Systems, Inc., pp. 1-11 (Summer 2004).Applicant
- “Next-Generation Signaling Transports Cisco IP Transfer Point,” Cisco Systems, Inc., pp. 1-27 (Summer 2004).Applicant
- “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).Applicant
- Notice of Allowance and Fee(s) Due for U.S. Appl. No. 09/471,946 (Feb. 6, 2004).Applicant
- 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).Applicant
- “Cisco IPT Multilayer Routing (MLR) SMS MO Routing Requirements,” Cisco Systems, Inc., p. 1 (Copyright 2004).Applicant
- “Cisco Signaling, Gateway Manager Release 3.2 For Cisco IP Transfer Point,” Cisco Systems, Inc., pp. 1-9 (Copyright 1992-2004).Applicant
- “Solutions for Mobile Network Operators,” Cisco Systems, Inc., pp. 1-8 (Copyright 1992-2004).Applicant
- Official Action from European Patent Office in courterpart European Patent Application (Dec. 11, 2003).Applicant
- Interview Summary for U.S. Appl. No. 09/471,946 (Dec. 9, 2003).Applicant
- Communication pursuant to Article 96(2) EPC for European Application No. 00988270.5 (Nov. 12, 2003).Applicant
- Notification of Transmittal of the International Search Report or the Declaration for International Application No. PCT/US2003/018266 (Oct. 31, 2003).Applicant
- Office Communication for U.S. Appl. No. 09/759,743 (Oct. 20, 2003).Applicant
- Official Action for U.S. Appl. No. 09/471,946 (Jul. 9, 2003).Applicant
- Moodie, “Agilent acceSS7: White Paper,” Agilent Technologies, pp. 1-14 (Apr. 1, 2003).Applicant
- Notice of Allowance and Fee(s) Due for U.S. Appl. No. 09/759,743 (Mar. 10, 2003).Applicant
- Interview Summary for U.S. Appl. No. 09/759,743 (Feb. 27, 2003).Applicant
- “Cisco IP Transfer Point,” Cisco Systems, Inc., pp. 1-10 (Copyright 1992-2003).Applicant
- “Cisco IP Transfer Point Multilayer Short Message Serivce Routing Solution,” Cisco Systems, Inc., pp. 1-6 (Copyright 1992-2003).Applicant
- “Cisco ITP MAP Gateway for Public WLAN Slm Authentication and Authorization,” Ciso Systems, Inc., pp. 1-13 (Copyright 1992-2003).Applicant
- Final Official Action for U.S. Appl. No. 09/759,743 (Dec. 2, 2002).Applicant
- Barry, “A Signal for Savings,” Packet, Cisco Systems Users Magazine, vol. 14, No. 4, pp. Cover; 19-21; and 81 (Fourth Quarter 2002).Applicant
- Interview Summary for U.S. Appl. No. 09/759,743 (Sep. 13, 2002).Applicant
- Official Action for U.S. Appl. No. 09/759,743 (May 23, 2002).Applicant
- Interview Summary for U.S. Appl. No. 09/759,743 (Mar. 6, 2002).Applicant
- “Agilent Tchnologies 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).Applicant
- “Cisco IP Transfer Point: MTP3 User Adaptation (M3UA) and SCCP User Adaptation (SUA) Signaling Gateway,” Cisco Systems, Inc., pp. 1-14 (Copyright 2002).Applicant
- “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).Applicant
- “Next-Generation SS7 Networks with the Cisco IP Transfer Point,” Cisco Systems, Inc., pp. 1-14 (Copyright 1992-2002).Applicant
- Notification of Transmittal of International Preliminary Examination Report for International Application No. PCT/US1999/030861 (Dec. 28, 2001).Applicant
- Official Action for U.S. Appl. No. 09/759,743 (Dec. 3, 2001).Applicant
- International Preliminary Examination Report for International Application No. PCT/US01/01052 (Nov. 7, 2001).Applicant
- 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.Applicant
- “Agilent acceSS7 Business intelligence,” Agilent Technologies, pp. 1-6 (Copyright 2001-Printed in the UK Nov. 30, 2001).Applicant
- International Search Report for International Application No. PCT/US00/34924 (May 16, 2001).Applicant
- “Cisco IP Transfer Point (ITP) Network Management Product Presentation,” Cisco Systems, Inc., pp. 1-20 (Copyright 2001).Applicant
- “Networkers,” Cisco Systems, Inc., pp. 1-60 (Copyright 2001).Applicant
- “Cisco SS7 Signaling Offload,” Cisco Systems, Inc., pp. 1-33 (Copyright 1992-2001).Applicant
- Rockhold, “Or,” Wireless Review, p. 22, 23, 26, 28, 30, 32, (Aug. 15, 2000).Applicant
- Notification of Transmittal of the International Search Report or the Declaration for International Application No. PCT/US1999/030861 (Mar. 17, 2000).Applicant
- “Topsail Beach-SS7 Over IP-” Cisco Systems, Inc., pp. 1-16 (Copyright 1999).Applicant
- 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).Applicant
- Smith, “Number Portability Pileup,” Telephony, p. 22, 24, 26, (Jan. 6, 1997).Applicant
- 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).Applicant
- Heinmiller, “Generic Requrements for SCP Application and GTT Function for Number Portability,” Illinois Number Portability Workshop, p. 1-50, (Sep. 4, 1996).Applicant
- International Telecommunication Union, “Series Q: Switching and Signalling: Specifications of Signalling Systems No. 7-Signalling Connection Control Part,” p. 11-16, (Jul. 1996).Applicant
- Rice, “SS7 Networks in a PCS World,” Telephony, pp. 138, 140 142, 144, 146, (Jun. 24, 1996).Applicant
- Tekelec, “Eagle STP Planning Guide”, Eagle Network Switching Division, (No. 3), p. i-vii, 1-64, A1-A2, B1-2, (May 1996).Applicant
- Anonymous, “Generic Switching and Signaling Requirements for Number Portability,” AT&T Network Systems, No. 1, p. 1-75, (Feb. 2, 1996).Applicant
- ETSI, Digital Cellular Telecommunications System (Phase 2+); Milbe Application Part (MAP) Specification, Global System for Mobile Communications, pp. 112-114 (1996).Applicant
- Jain, et al., “A Hashing Scheme for Phone Number Portability in PCS Systems with ATM Backbones,” Bell Communications Research, p. 593-597, (1996).Applicant
- Bishop, “Freeing the Network for Competition,” Telecommunications, p. 75-80, (Apr. 1995).Applicant
- Anonymous, “Zeichengabesystem-Eine, neue Generation für ISDN und intelligente Netze,” Zeichengabesystem, Medien-Institut Bremen, p. iz-xi; 170-176, (Feb. 17, 1995).Applicant
- Giordano et al., “PCS Number Portability,” IEEE, p. 1146-1150, (Sep. 1994).Applicant
- Bellcore, “Signaling Transfer Point (STP) Generic Requirements,” Bell Communications Research, No. 1, p. ii-xxii, 4-84-J14, (Jun. 1994).Applicant
- Telcordia Technologies, “CCS Network interface Specification (CCSNIS) Supporting SCCP and TCAP,”Bell Communications Research, p. ii-xii, 1-1-C-22, (Mar. 1994).Applicant
- Buckles, “Very High Capacity Signaling Trnsfer Point for Intelligent Network Servcies,” DSC Communciations Corporation, p. 1308-1311, (1988).Applicant
- “Diameter Overview,” referenced from www.ulticom.com/html/products/signalware-diameter-reference-guide.asp (Publication date unknown), Submitted on Apr. 16, 2010.Applicant
- “Chapter 1: Overview,” SS7 Port Adapter Installation and Configuration, pp. 1-1-1-8 (Publication Date Unknown), Submitted on Apr. 16, 2010.Applicant
- “Configuring ITP Basic Functionally,” IP Transfer Point, Cisco IOS Release 12.2(4)MB12, pp. 31-50 (Publication Date Unknown), Submitted on Apr. 16, 2010.Applicant
- “Configuring ITP Optional Features,” IP Transfer Point, Cisco IOS Release 12.294)MB12, pp. 65-136 (Publication Date Unknown), Submitted on Apr. 16, 2010.Applicant
- “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), Submitted on Apr. 16, 2010.Applicant
- “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), Submitted on Apr. 16, 2010.Applicant