Methods, systems, and computer program products for specifying a particular ENUM service type in a communications network that utilizes a plurality of different ENUM service types

• US 8,400,947 B2
• Filed: 07/19/2007
• Issued: 03/19/2013
• Est. Priority Date: 07/20/2006
• Status: Active Grant

• Current Assignee: Tekelec
• Original Assignee: Tekelec
• Inventors: Heinze, Christopher R., Marsico, Peter J., Wiatrowski, Maria A.
• Primary Examiner(s): Phillips, Hassan
• Assistant Examiner(s): CATTUNGAL, AJAY P
• Application Number:
  US11/880,108
• Publication Number:
  US 20080025492A1
• Time in Patent Office: 2,070 Days
• Field of Search: 370/255, 370/259, 370/352, 370/389, 370/395.3, 370/401, 370/422, 379/88.17, 379/67.1, 379/88.13, 379/88.18, 379/201.01, 379/218.01, 379/265.09, 379/900
• US Class Current: 370/259
• CPC Class Codes: H04L 2101/65 Telephone numbers
• CPC Class Codes: H04L 61/106 across networks, e.g. mapping telephone numbers to data network addresses
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04L 61/4555 Directories for electronic mail or instant messaging
• CPC Class Codes: H04M 7/128 Details of addressing, directories or routing tables

Abstract

The subject matter described herein includes methods, systems, and computer program products for specifying an ENUM service type in a communications network that uses a plurality of different ENUM service types. According to one method, at least one ENUM service type is identified from a plurality of different ENUM service types. The identification is performed at a signaling point separate from an ENUM database. An ENUM query message corresponding to the at least one identified ENUM service type is generated. The ENUM query message is transmitted to an at least one ENUM server for providing the at least one identified ENUM service type.

Claims

1. A method for specifying an E.164 number mapping (ENUM) service type in a communications network that utilizes a plurality of different ENUM service types, the method comprising:

detecting, at a signaling point separate from an ENUM database, a communication origination event for establishing communication with a called party destination;

identifying, at the signaling point separate from the ENUM database, at least one ENUM service type from a plurality of different ENUM service types based on a media type associated with the called party destination;

generating at least one ENUM query message that includes at least one ENUM service type identifier that identifies the at least one identified ENUM service type; and

transmitting the at least one ENUM query message to at least one ENUM server that is configured to utilize the at least one ENUM service type identifier to locate at least one destination identifier for establishing the communication with the called party destination via the at least one identified ENUM service type.

2. The method of claim 1 wherein identifying at least one ENUM service type at a signaling point separate from an ENUM database includes determining an ENUM service type at one of a PSTN switching office, an IP multimedia subsystem (IMS) node, a media gateway controller (MGC), a session initiation protocol (SIP) proxy server, an H.323 gatekeeper, a softswitch, a next generation network (NGN) node, an application server, a service control point, a mobile switching center (MSC) server, a home location register (HLR), an IMS home subscriber server (HSS), and a presence server.

3. The method of claim 1 wherein transmitting the ENUM query message includes transmitting the ENUM query message to a single ENUM server having access to ENUM data for plural ENUM service types.

4. The method of claim 1 wherein:

identifying at least one ENUM service type includes identifying a plurality of ENUM service types;

generating at least one query message includes generating a plurality of ENUM query messages corresponding to the identified ENUM service types; and

transmitting the at least one query message includes transmitting each of the ENUM query messages to an ENUM server corresponding to the service type identified for each query message.

5. The method of claim 1 comprising inserting a service type identifier parameter in the at least one ENUM query message:

intercepting the at least one ENUM query message at a routing node between the signaling point and the at least one ENUM database;

removing the ENUM service type identifier from the at least one ENUM query message;

forwarding the at least one ENUM query message to the at least one ENUM server for providing the ENUM service;

receiving an ENUM response from the at least one ENUM server; and

forwarding the response to the signaling point.

6. The method of claim 1 comprising:

inserting a plurality of ENUM service types in the at least one ENUM query message;

receiving the at least one ENUM query message at a routing node between the signaling point and the at least one ENUM database;

at the routing node, formulating a plurality of service specific ENUM queries and transmitting the ENUM queries to ENUM databases corresponding to the specific service types;

receiving responses to the ENUM queries; and

combining ENUM data from the received responses into a single ENUM response and forwarding the response to the signaling point.

7. The method of claim 1 comprising:

receiving the transmitted ENUM query at a routing node between the signaling point and the at least one ENUM database, and at the routing node;

accessing a subscriber preferences database to identify subscriber preferences associated with at least one ENUM service type;

formulating a new ENUM query corresponding to an ENUM service type specified by a subscriber preference; and

forwarding the ENUM query to at least one ENUM database for providing the ENUM service type specified by the subscriber preferences.

8. The method of claim 1 comprising inserting a max URIs parameter in the at least one ENUM query message specifying a maximum number of URIs to be returned by an ENUM database.

9. A system for specifying an E.164 number mapping (ENUM) service type in a communications network that utilizes a plurality of different ENUM service types, the system comprising:

a signaling point for detecting a communication origination event for establishing communication with a called party destination, for identifying at least one ENUM service type from a plurality of different ENUM service types based on a media type associated with the called party destination, for generating at least one ENUM query message that includes at least one ENUM service type identifier that identifies to the at least one identified ENUM service type, and for transmitting the at least one ENUM query message; and

at least one ENUM server for receiving the at least one ENUM query message and that is configured to utilize the at least one ENUM service type identifier to locate at least one destination identifier for establishing the communication with the called party destination via the at least one identified ENUM service type.

10. The system of claim 9 wherein the signaling point comprises one of a PSTN switching office, an IP multimedia subsystem (IMS) node, a media gateway controller (MGC), a session initiation protocol (SIP) proxy server, a H.323 gatekeeper, a softswitch, a next generation network (NGN) node, an application server, a service control point, a mobile switching center (MSC) server, a home location register (HLR), an IMS home subscriber server (HSS), and a presence server.

11. The method of claim 9 wherein the at least one ENUM server comprises a single ENUM server having access to ENUM data for plural ENUM service types.

12. The system of claim 9 wherein the at least one ENUM server comprises a plurality of ENUM servers corresponding to different ENUM service types and wherein the signaling point is adapted to generate a plurality of ENUM query messages corresponding to a plurality of identified ENUM service types and transmit each query message to the ENUM server corresponding to the service type identified for each query message.

13. The system of claim 9 comprising a routing node for receiving the at least one ENUM query from the signaling point, for removing an ENUM service type parameter from the at least one query, for forwarding the at least one ENUM query to at least one ENUM server corresponding to the identified ENUM service type, for receiving an ENUM response from the ENUM server, and forwarding a response to the signaling point.

14. The system of claim 9 comprising a routing node for receiving the at least one ENUM query from the signaling point, for identifying a plurality of ENUM service types based on service type parameters in the query, for formulating a plurality of ENUM queries to ENUM database corresponding to a specific service types, for receiving ENUM responses from the ENUM servers, for combining ENUM data from the responses in to a single ENUM response and for forwarding the single ENUM response to the signaling point.

15. The system of claim 9 comprising a routing node for receiving the ENUM query from the signaling point, for accessing subscriber preferences to determine a subscriber preferred ENUM service type, for formulating an ENUM query to an ENUM server corresponding to the subscriber preferred service type.

16. The system of claim 9 wherein the signaling point is adapted to insert a max URIs parameter in the ENUM query specifying a maximum number of URIs to be returned to the signaling point.

17. A signaling point for identifying an E.164 number mapping (ENUM) service type and for formulating at least one ENUM query message according to the identified ENUM service type, the signaling point comprising:

an ENUM service type identifier for detecting a communication requiring ENUM service and for identifying at least one ENUM service type for the communication based on a media type associated with a called party destination of the communication; and

an ENUM query message generator for generating an ENUM query that includes at least one ENUM service type identifier that identifies the at least one identified ENUM service type and for transmitting the at least one ENUM query message to at least one ENUM server that is configured to utilize the at least one ENUM service type identifier to locate at least one destination identifier for establishing the communication with the called party destination via the at least one identified ENUM service type.

18. A computer program product comprising computer executable instructions embodied in a non-transitory computer readable medium for performing steps comprising:

detecting, at a signaling point separate from an ENUM database, a communication origination event for establishing communication with a called party destination;

identifying, at the signaling point separate from the ENUM database, at least one ENUM service type from a plurality of different ENUM service types based on a media type associated with the called party destination;

generating at least one ENUM query message that includes at least one ENUM service type identifier that identifies the at least one identified ENUM service type; and

transmitting the at least one ENUM query message to at least one ENUM server that is configured to utilize the at least one ENUM service type identifier to locate at least one destination identifier for establishing the communication with the called party destination via the at least one identified ENUM service type.