Methods, systems, and computer program products for providing quality of service using E.164 number mapping (ENUM) data in a communications network

• US 8,254,551 B2
• Filed: 12/07/2006
• Issued: 08/28/2012
• Est. Priority Date: 12/07/2006
• Status: Active Grant

• Current Assignee: Tekelec, Inc. (Oracle Corporation)
• Original Assignee: Tekelec, Inc. (Oracle Corporation)
• Inventors: Heinze, Christopher R., Marathe, Rohini, Wiatrowski, Maria A., Marsico, Peter J.
• Primary Examiner(s): Nguyen, Joseph J
• Application Number:
  US11/635,406
• Publication Number:
  US 20080137832A1
• Time in Patent Office: 2,091 Days
• Field of Search: 379/201.01, 379/220.01, 370/352, 370/338, 707/100, 707/102
• US Class Current: 379/220.01
• CPC Class Codes: H04L 61/4557 Directories for hybrid networks, e.g. including telephone numbers
• CPC Class Codes: H04L 65/80 Responding to QoS
• CPC Class Codes: H04M 7/128 Details of addressing, directories or routing tables

Abstract

Methods, systems, and computer program products for providing a quality of service (QoS) using E.164 number mapping (ENUM) data in a communications network. According to one method, a query message including an E.164 number can be received. Next, at least one uniform resource identifier (URI) associated with the E.164 number can be located. Afterwards, QoS data corresponding to the at least one URI is subsequently obtained. Further, the query message can be responded to with the URI and the corresponding QoS data.

Claims

1. A method for providing a quality of service (QoS) using E.164 number mapping (ENUM) data in a communications network, the method comprising steps of:

(a) receiving a query message including an E.164 number;

(b) locating at least two uniform resource identifiers (URIs) associated with the E.164 number using an ENUM database;

(c) obtaining corresponding QoS data for the at least two URIs; and

(d) responding to the query message with a response message that includes both the at least two URIs and the corresponding QoS data.

2. The method according to claim 1 wherein receiving a query message includes receiving an ENUM query message.

3. The method according to claim 1 wherein the E.164 number comprises a called party number.

4. The method according to claim 1 wherein the E.164 number is associated with a subscriber.

5. The method according to claim 1 wherein the at least two URIs include at least one of a SIP URI, an instant messaging (IM) identifier, an e-mail address identifier, an Internet chat session identifier, and an IP address.

6. The method according to claim 1 wherein the locating the at least two URIs comprises searching a database of naming authority pointer (NAPTR) records containing the at least two URIs associated with the E.164 number.

7. The method according to claim 1 further comprising:

acquiring corresponding presence information from a presence server for the at least two URIs.

8. The method according to claim 7 wherein obtaining the QoS data includes obtaining the QoS data for the URIs that have an available presence status.

9. The method according to claim 8 wherein responding to the query message comprises responding to the query message with the at least two URIs and indicating a presence status of each of the at least two URIs.

10. The method according to claim 1 wherein the query message includes a request for the corresponding QoS data.

11. The method according to claim 1 wherein the corresponding QoS data obtained for the at least two URIs comprises an abstract QoS indicator value.

12. The method according to claim 1 wherein the corresponding QoS data obtained for the at least two URIs comprises a protocol specific QoS indicator.

13. The method according to claim 1 wherein the corresponding QoS data is incorporated into the body of the at least two URIs.

14. The method according to claim 1 wherein the corresponding QoS data is incorporated in an additional section of an ENUM response.

15. The method according to claim 1 wherein obtaining the corresponding QoS data comprises obtaining the corresponding QoS data from the ENUM database.

16. The method according to claim 1 wherein obtaining the corresponding QoS data comprises obtaining the corresponding QoS data from the ENUM database.

17. The method according to claim 1 further comprising:

(a) comparing a QoS level associated with a calling party and the corresponding QoS data to determine a highest available QoS level; and

(b) providing service for a communication session between the calling party and a called party at the highest available QoS level.

18. The method according to claim 17 wherein the corresponding QoS data is obtained using a phone number of the calling party.

19. A system for providing quality of service (QoS) using E.164 number mapping (ENUM) data in a communications network, the system comprising:

(a) an ENUM database for storing mappings between E.164-formatted numbers and uniform resource indicators (URIs); and

(b) means for receiving a message containing an E.164-formatted number, for obtaining at least two URIs corresponding to the E.164-formatted number from the ENUM database, for obtaining QoS data corresponding to the E.164-formatted number and the at least two URIs, and for providing a second message containing both the QoS data and the at least two URIs.

20. The system according to claim 19 wherein the message comprises an ENUM query message.

21. The system according to claim 19 wherein the E.164-formatted number comprises a called party number.

22. The system according to claim 19 wherein the E.164-formatted number is associated with a subscriber.

23. The system according to claim 19 wherein the at least two URIs include at least one of a SIP URI, an instant messaging (IM) identifier, an e-mail address identifier, an Internet chat session identifier, and an IP address.

24. The system according to claim 19 wherein the means for receiving and for obtaining includes an ENUM application adapted to search the ENUM database for naming authority pointer (NAPTR) records containing the at least two URIs associated with the E.164-formatted number.

25. The system according to claim 24 wherein the ENUM application is adapted to acquire corresponding presence status data from a presence server for the at least two URIs.

26. The system according to claim 24 wherein the ENUM application is adapted to obtain the QoS data for URIs that have an available presence status.

27. The system according to claim 26 wherein the ENUM application is adapted to respond to the message with the at least two URIs and indicating a presence status of each of the at least two URIs.

28. The system according to claim 19 wherein the message includes a request for the corresponding QoS data.

29. The system according to claim 19 wherein the corresponding QoS data obtained for the at least two URIs comprises an abstract QoS indicator value.

30. The system according to claim 19 wherein the corresponding QoS data obtained for the at least two URIs comprises a protocol specific QoS indicator.

31. The system according to claim 19 wherein the corresponding QoS data is incorporated into the body of the at least two URIs.

32. The system according to claim 19 wherein the corresponding QoS data is incorporated in an additional section of an ENUM response.

33. The system according to claim 19 wherein the means for receiving and for obtaining includes querying a QoS database separate from the ENUM database.

34. The system according to claim 19 wherein the means for receiving and for obtaining includes means for obtaining the corresponding QoS data from the ENUM database.

35. The system according to claim 24 wherein the ENUM application is further adapted to compare a QoS level associated with a calling party and the corresponding QoS data to determine a highest available QoS level, and to provide service for a communication session between the calling party and a called party at the highest available QoS level.

36. The system according to claim 35 wherein the corresponding QoS data associated with a calling party is obtained using a phone number of the calling party.

37. A non-transitory computer readable medium having stored thereon computer executable instructions that when executed by a processor of a computer perform steps comprising:

(a) receiving a query message including an E.164 number;

(b) locating at least two uniform resource identifiers (URIs) associated with the E.164 number using an E.164 number mapping (ENUM) database;

(c) obtaining corresponding QoS data for the at least two URIs; and

(d) responding to the query message with a response message that includes both the at least two URIs and the corresponding QoS data.

38. An E.164 flexible numbering (E-Flex) node, comprising:

(a) a communication interface for receiving an E.164 number mapping (ENUM) response message originating from an ENUM server and containing at least two uniform resource identifiers (URIs); and

(b) an E-Flex processor for receiving the ENUM response message from the communication interface, for buffering the ENUM response message, for obtaining QoS data for the at least two URIs, and for communicating the ENUM response message that includes both the QoS data and the at least two URIs to a requesting node.

39. A non-transitory computer-readable medium having stored thereon an E.164 number mapping (ENUM) database, the database comprising:

(a) a plurality of first data fields containing directory numbers of subscribers of an E.164 number mapping service;

(b) a plurality of second data fields respectively corresponding to the first data fields containing at least two uniform resource identifiers (URIs) for each of the directory numbers; and

(c) a plurality of third data fields respectively corresponding to the second data fields containing quality of service (QoS) data for each of the at least two URIs.