Methods, systems, and computer program products for routing and processing ENUM queries

• US 7,787,445 B2
• Filed: 07/18/2007
• Issued: 08/31/2010
• Est. Priority Date: 07/20/2006
• Status: Active Grant

• Current Assignee: Tekelec
• Original Assignee: Tekelec
• Inventors: Marsico, Peter J.
• Primary Examiner(s): ADDY, THJUAN KNOWLIN
• Application Number:
  US11/879,737
• Publication Number:
  US 20080019356A1
• Time in Patent Office: 1,140 Days
• Field of Search: 370/352, 370/395.2, 379/196, 379/265.01, 379/218.01, 379/201.01
• US Class Current: 370/352
• CPC Class Codes: H04L 61/4552 Lookup mechanisms between a plurality of directories; Synchronisation of directories, e.g. metadirectories
• CPC Class Codes: H04L 61/4557 Directories for hybrid networks, e.g. including telephone numbers
• CPC Class Codes: H04M 7/0075 Details of addressing, directories or routing tables
• CPC Class Codes: H04M 7/123 where the packet-switched network is an Internet Protocol Multimedia System-type network
• CPC Class Codes: H04Q 2213/13097 Numbering, addressing
• CPC Class Codes: H04Q 2213/13141 Hunting for free outlet, circuit or channel
• CPC Class Codes: H04Q 2213/13353 Routing table, map memory
• CPC Class Codes: H04Q 3/76 Translation from the called subscriber's number to the outgoing or incoming control information

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.

Claims

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.