Internet telephony call pricing center

• US 6,205,211 B1
• Filed: 08/04/1999
• Issued: 03/20/2001
• Est. Priority Date: 08/04/1998
• Status: Expired due to Term

• Current Assignee: Transnexus Incorporated
• Original Assignee: Transnexus Incorporated
• Inventors: Dalton, James P.G. Jr., Thomas, Stephen Anthony, Bloomberg, Jason
• Primary Examiner(s): Kuntz, Curtis A.
• Assistant Examiner(s): TIEU, BINH KIEN
• Application Number:
  US09/366,984
• Time in Patent Office: 594 Days
• Field of Search: 379/111, 379/112, 379/114, 379/121, 379/125, 379/127, 379/128, 399/207, 399/219, 399/220, 399/221
• US Class Current: 379/114.06
• CPC Class Codes: H04M 15/00 Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
• CPC Class Codes: H04M 15/46 Real-time negotiation between users and providers or operators
• CPC Class Codes: H04M 15/49 Connection to several service providers
• CPC Class Codes: H04M 15/51 for resellers, retailers or service providers
• CPC Class Codes: H04M 15/56 for VoIP communications
• CPC Class Codes: H04M 15/8044 Least cost routing
• CPC Class Codes: H04M 2215/202 VoIP; Packet switched telephony
• CPC Class Codes: H04M 2215/42 Least cost routing, i.e. provision for selecting the lowest cost tariff
• CPC Class Codes: H04M 2215/46 Connection to several service providers
• CPC Class Codes: H04M 2215/54 Resellers-retail or service providers billing, e.g. agreements with telephone service operator, activation, charging/recharging of accounts
• CPC Class Codes: H04M 2215/56 On line or real-time flexible agreements between service providers and telecoms operators
• CPC Class Codes: H04M 2215/745 Least cost routing, e.g. Automatic or manual, call by call or by preselection

Abstract

The present invention discloses a call pricing center that assists gateway operators in defining preferences, including call prices for terminating an IP telephony call. A centralized routing engine associated with a clearinghouse uses the preferences to assist gateways in making routing decisions. The call pricing center provides IP network operators and retail IP telephony gateway operators with significant flexibility by allowing them to designate preferences and preference criteria. Preference criteria define circumstances in which preferences are to be applied. A source gateway operator may set preferences such as the maximum price that it is willing to paid for a call, the maximum delay that will be tolerated and the maximum autonomous system hop count that will be tolerated. A destination gateway operator may also set preferences relating to the prices it will charge for terminating calls. Using preference criteria, a gateway operator may specify particular times call prices are to be effective and to what called number ranges they are to be applied. Based on such preferences and preference criteria, the routing engine is able to locate destination gateways that are eligible to terminate a voice over telephony IP call. The routing engine provides a prioritized list of eligible destination gateways to the source gateway. The source gateway then works through the prioritized list and attempts to set up the voice over IP telephony call with each eligible destination gateway, until the call is established.

Claims

1. A method for defining call pricing information to be used by a call routing engine for the purpose of determining a preferred route for routing telephony calls from a originating gateway to a destination gateway via an IP network, comprising the computer-implemented steps of:

creating a time period schedule comprising at least one time period to which a selected rate for terminating a call is to be applied;

creating a called number map comprising at least one called number range to which a selected rate plan instance is to be applied, the called number range comprising at least one called number;

creating the rate plan instance by associating a rate with each time period included within the time period schedule;

creating a rate plan assignment instance by associating at least one device with the called number map; and

associating a rate plan instance with each called number range included in the called number map.

2. The method of claim 1, wherein the time period schedule corresponds to a pre-determined unit of time comprising at least one range of time;

and

wherein the step of creating the time period schedule comprises associating with each time period at least one selected range of time.

3. The method of claim 2, further comprising the step of assigning a name to each time period included in the time period schedule.

4. The method of claim 1, wherein the time period schedule comprises a weekly schedule corresponding to a week comprising at least one range of hours;

and

wherein the step of creating the time period schedule comprises associating with each time period at least one selected range of hours of the week.

5. The method of claim 1, wherein the time period schedule comprises a first time period and a second time period;

and

wherein defining a rate plan instance comprises associating a first rate with the first time period associating a second rate with the second time period.

6. The method claim 1, wherein the step of creating a called number map comprises the step of selecting the at least one called number from a list of all possible called numbers.

7. The method of claim 1, wherein the step of creating the rate plan assignment instance comprises:

associating a first device with a first called number map; and

associating a second device with a second called number map.

8. The method of claim 1, wherein the device is a source gateway.

9. The method of claim 8 further comprising the step of defining at least one preference to be associated with the called number range.

10. The method of claim 9, wherein the preference comprises a delay tolerance.

11. The method of claim 9, wherein the preference comprises a routing priority.

12. The method of claim 9, wherein the preference relates to a determination of autonomous system matching.

13. The method of claim 9, wherein the preference relates to a determination of domain matching.

14. The method of claim 9, wherein the preference relates to a determination of specified platform system matching.

15. The method of claim 9, wherein the preference relates to a maximum autonomous system hop count.

16. The method of claim 8, further comprising the steps of:

defining a plurality of preferences to be associated with the called number range;

defining at least one preference criteria; and

wherein a determination is made from the preference criteria as to which of the preferences apply to the device.

17. The method of claim 16, wherein the preference criteria comprises a date on which a selected preference is to be applied.

18. The method of claim 1, wherein the device is a destination gateway.

19. The method of claim 1, further comprising the step of defining a date for the rate plan instance to become effective.

20. The method of claim 1, further comprising the step of defining a date for the rate plan assignment instance to become effective.