Pricing center for internet protocol routed transactions

• US 6,487,283 B2
• Filed: 12/11/2000
• Issued: 11/26/2002
• Est. Priority Date: 08/04/1998
• Status: Expired due to Term

• Current Assignee: Transnexus Incorporated
• Original Assignee: Transnexus Incorporated
• Inventors: Thomas, Stephen Anthony, Bloomberg, Jason, Dalton, James P. G. Jr.
• Primary Examiner(s): TIEU, BINH KIEN
• Application Number:
  US09/734,362
• Publication Number:
  US 20010001000A1
• Time in Patent Office: 715 Days
• Field of Search: 379/111, 379/112, 379/114, 379/121, 379/125, 379/127, 379/128, 379/207, 379/219, 379/220, 379/221, 370/351, 370/353, 370/354, 370/355, 370/356, 370/357
• US Class Current: 379/112.01
• 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

A call pricing center that assists Internet Protocol (IP)-compatible devices in defining preferences, including prices, for completing an IP routed transaction. A centralized routing engine associated with a clearinghouse uses the preferences to assist IP devices in making routing decisions. The pricing center provides IP network operators and retail IP telephony gateway operators with significant flexibility by allowing them to designate preferences and preference criteria. 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 IP telephony call with each eligible destination gateway, until the call is established.

Claims

1. A computer-implemented method for defining pricing information to be used by a routing engine for determining a preferred route for routing an Internet Protocol (IP) transaction via an IP network, comprising the steps of:

creating a time period schedule comprising at least one time period to which a selected rate for routing an IP transaction is to be applied;

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

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 of the IP network with the map; and

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

2. The method of claim 1, wherein the time period schedule corresponds to a predetermined 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 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 and associating a second rate with the second time period.

4. The method of claim 1 further comprising the step of defining at least one preference to be associated with the range.

5. The method of claim 4, wherein the preference comprises a certain preference selected from a group comprising a delay tolerance, a routing priority, a determination of autonomous system matching, a determination of domain matching, a determination of specified platform system matching, and a maximum autonomous system hop count.

6. The method of claim 1 further comprising the steps of:

defining a plurality of preferences to be associated with the 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 one of the devices of the IP network.

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

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

9. The method of claim 1, wherein the IP transaction comprises a telephony call to be routed via the IP network and the number comprises a called number associated with the telephony call.

12. The method of claim 1 further comprising the step of defining at least one preference to be associated with the range.

13. The method of claim 12, wherein the preference comprises a delay tolerance.

14. The method of claim 12, wherein the preference comprises a routing priority.

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

16. The method of claim 12, wherein the preference relates to a determination of domain matching.

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

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

10. A method for defining pricing information to be used by a routing engine for determining a preferred route for routing an Internet Protocol (IP) transaction 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 routing an IP transaction is to be applied;

creating a map comprising at least one IP transaction range to which a selected rate plan instance is to be applied, the range comprising at least one identifier for the IP transaction;

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 of the IP network with the map; and

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

11. The method of claim 10 wherein the time period schedule corresponds to a predetermined 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.

19. The method of claim 10, further comprising the steps of:

defining a plurality of preferences to be associated with the 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 each device of the IP network.

20. A computer-implemented method for defining pricing information to be used by a routing engine for determining a preferred route for routing an Internet Protocol (IP) transaction via an IP network, comprising the steps of:

creating a time period schedule comprising at least one time period to which a selected rate for routing an IP transaction is to be applied;

creating a map comprising at least one IP transaction range to which a selected rate plan instance is to be applied, the range comprising at least one identifier for the IP transaction;

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

creating a rate plan assignment instance by associating at least one device of the IP network with the map.