IP Library Granted Patent US 8,089,952
Granted Patent B2
US 8,089,952 · App. 11/849,044 · Granted Jan 3, 2012

Intelligent call routing

Assignee: IntelePeer, Inc.
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 8,089,952
App. No.
11/849,044
Granted
Jan 3, 2012
Kind
B2
Abstract

A call routing decision for connecting a call between source and target devices is based on the traffic type (e.g., facsimile, modem, voice). In some implementations, the traffic type is determined and stored (e.g., in a billing record). The traffic type can be used to connect, block or reroute subsequent calls of the same traffic type.

Claims (92)

1. A method comprising:

receiving traffic from a first device for transmission to a second device at least partially through a packet-switched data network, wherein the traffic comprises a communication session between the first device and the second device;

determining a traffic type at least partially based on traffic previously transmitted by the first device for prior transmissions, wherein the traffic type comprises characteristics related to the traffic that establish handling of the traffic to the second device;

determining at least one or more routes to the second device based on the determined traffic type, each determined route comprising a single path between the first device and the second device that is able to support the communication session between the first device and the second device;

ordering the determined routes according to a desired criteria to establish the communication session;

setting a counter equal to the number of determined routes to the second device;

transmitting the traffic to the second device based on the route to establish the communication session; and

decrementing the counter if the traffic was not successfully transmitted.

2. The method of claim 1 , wherein traffic is a facsimile transmission.

3. The method of claim 1 , wherein the first or second device is a computer or facsimile machine.

4. The method of claim 1 , where the packet-switched data network is the Internet.

5. The method of claim 1 , where determining a traffic type further comprises:

determining a traffic type using an in band or out-of-band signal.

6. The method of claim 1 , where determining a traffic type further comprises:

obtaining the traffic type from a storage device.

7. The method of claim 6 , where the traffic type is stored in a billing or call detail record.

8. The method of claim 1 further comprising:

determining if the transmission was completed using the route; and

if the transmission was not completed, attempting to transmit the traffic using a different route or blocking the traffic.

9. The method of claim 1 , further comprising monitoring the traffic to determine if the traffic was successful transmitted.

10. A method comprising:

receiving a call from a source device, wherein the call comprises a communication session from the source device to a target device;

determining if the call is a first call, wherein the first call comprises a first communication from the source device;

if the call is a first call, determining a traffic type from the first call, wherein the traffic type comprises characteristics related to the call that establish handling of the call to the target device;

storing the traffic type for use with subsequent calls after the first call;

determining one or more routes based on the traffic type, wherein the one or more routes each comprise a single path between the source device and the target device that is able to support the communication session between the source device and the target device;

attempting to connect the call to the target device using the one or more routes;

ordering the determined routes according to a desired criteria to establish the communication session;

setting a counter equal to the number of determined routes to the second device; and

decrementing the counter if the traffic was not successfully transmitted.

11. The method of claim 10 , further comprising:

determining if the call was completed using the route; and

if the call was not completed, attempting to connect the call to the target device using a different route.

12. A system comprising:

an interface configurable for obtaining traffic from a first device for transmission to a second device at least partially through a packet-switched data network, wherein the traffic comprises a communication session between the first device and the second device; and

a signaling control module coupled to the interface and configurable for determining a traffic type at least partially based on traffic previously transmitted by the first device for prior transmissions, wherein the traffic type comprises characteristics related to the traffic that establish handling of the traffic to the second device, and for determining at least one or more routes to the second device based on the traffic determined type, each determined route comprising a single path between the first device and the second device that is able to support the communication session between the first device and the second device;

ordering the determined routes according to a desired criteria to establish the communication session;

setting a counter equal to the number of determined routes to the second device; and

decrementing the counter if the traffic was not successfully transmitted.

13. The system of claim 12 , wherein traffic is a facsimile transmission.

14. The system of claim 12 , wherein the first or second device is a computer or facsimile machine.

15. The system of claim 12 , where the packet-switched data network is the Internet.

16. The system of claim 12 , where determining a traffic type further comprises:

determining a traffic type using an in band or out-of-band signal.

17. The system of claim 12 , where determining a traffic type further comprises:

obtaining the traffic type from a storage device.

18. The system of claim 17 , where the traffic type is stored in a billing or call detail record.

19. A non-transitory computer-readable medium having instructions stored thereon, which, when executed by a processor, causes the processor to perform operations comprising:

receiving traffic from a first device for transmission to a second device at least partially through a packet-switched data network, wherein the traffic comprises a communication session between the first device and the second device;

determining a traffic type at least partially based on traffic previously transmitted by the first device for prior transmissions, wherein the traffic type comprises characteristics related to the traffic that establish handling of the traffic to the second device;

determining at least one or more routes to the second device based on the determined traffic type, each determined route comprising a single path between the first device and the second device that is able to support the communication session between the first device and the second device;

transmitting the traffic to the second device based on the route to establish the communication session;

ordering the determined routes according to a desired criteria to establish the communication session;

setting a counter equal to the number of determined routes to the second device; and

decrementing the counter if the traffic was not successfully transmitted.

20. A system comprising:

means for receiving traffic from a first device for transmission to a second device at least partially through a packet-switched data network, wherein the traffic comprises a communication session between the first device and the second device;

means for determining a traffic type at least partially based on traffic previously transmitted by the first device for prior transmissions, wherein the traffic type comprises characteristics related to the traffic that establish handling of the traffic to the second device;

means for determining at least one route to the second device based on the determined traffic type, each determined route comprising a single path between the first device and the second device that is able to support the communication session between the first device and the second device;

means for transmitting the traffic to the second device based on the route to establish the communication session;

means for ordering the determined routes according to a desired criteria to establish the communication session;

means for setting a counter equal to the number of determined routes to the second device;

decrementing the counter if the traffic was not successfully transmitted.

21. A method for routing traffic between a first device and a second device, the method comprising:

receiving traffic from the first device for transmission to the second device at least partially through a packet-switched data network, wherein the traffic comprises a communication session between the first device and the second device;

determining a traffic type, wherein the traffic type comprises characteristics related to the traffic that establish handling of the traffic to the second device;

determining routes to the second device based on the determined traffic type, wherein each of the routes comprises a single path between the first device and the second device that is able to support the communication session between the first device and the second device;

ordering the determined routes according to desired criteria to establish the communication session;

setting a counter equal to the number of determined routes to the second device;

transmitting the traffic to the second device via the most preferable determined route;

monitoring the traffic to determine if the traffic was successfully transmitted; and

decrementing the counter if the traffic was not successfully transmitted.

22. The method of claim 21 , further comprising:

transmitting the traffic to the second device via the next preferable determined route if the traffic was not successfully transmitted; and

decrementing the counter if the traffic was not successfully transmitted.

23. The method of claim 22 , further comprising:

if the counter reaches zero, blocking the traffic and/or providing a user of the first device with information relating to the transmission.

24. The method of claim 21 , wherein the desired criteria comprises one or more of quality and cost.

25. A method for routing traffic between a first device and a second device, the method comprising:

receiving traffic from the first device for transmission to the second device, wherein the first device is part of a Voice over Internet Protocol (VoIP) network and the second device is not part of the VoIP network, wherein the first device and the second device are coupled to respective gateways to enable interfacing between the VoIP network and the network of the second device, wherein the traffic comprises a communication session between the first device and the second device;

determining a traffic type, wherein the traffic type comprises characteristics related to the traffic that establish handling of the traffic to the second device;

storing the traffic type in a registry associated with the first device;

determining routes to the second device based on the determined traffic type, wherein each of the routes comprises a single path between the first device and the second device that is able to support the communication session between the first device and the second device;

transmitting the traffic to the second device via static routing to enable transmission outside of the VoIP network between the first device gateway and the second device gateway to establish the communication session;

ordering the determined routes according to desired criteria to establish the communication session;

setting a counter equal to the number of determined routes to the second device; and

decrementing the counter if the traffic was not successfully transmitted.

26. The method of claim 25 , further comprising:

performing a load balancing operation among the first device gateway and the second device gateway.

27. The method of claim 25 , further comprising:

storing routing information relating to the second device; and

providing access to the second device routing information among other devices in the VoIP network for subsequent transmissions to the second device outside of the VoIP network.

Assignments (23)
SECURITY INTEREST Recorded Jul 22, 2024
From: INTELEPEER CLOUD COMMUNICATIONS LLC
To: ACQUIOM AGENCY SERVICES LLC
Reel/Frame 068039/0384 →
RELEASE OF SECURITY INTEREST Recorded Jul 22, 2024
From: TC LENDING, LLC
To: INTELEPEER CLOUD COMMUNICATIONS LLC
Reel/Frame 068041/0472 →
RELEASE OF SECURITY INTEREST Recorded Jul 22, 2024
From: TC LENDING, LLC
To: INTELEPEER CLOUD COMMUNICATIONS LLC
Reel/Frame 068041/0748 →
GRANT OF A SECURITY INTEREST -- PATENTS Recorded May 12, 2021
From: INTELEPEER CLOUD COMMUNICATIONS LLC
To: TC LENDING, LLC, AS AGENT
Reel/Frame 056224/0344 →
RELEASE OF SECURITY INTEREST Recorded Jan 6, 2020
From: COMERICA BANK
To: INTELEPEER HOLDINGS, INC.
Reel/Frame 051427/0263 →
RELEASE OF SECURITY INTEREST Recorded Dec 2, 2019
From: SILICON VALLEY BANK
To: INTELEPEER HOLDINGS, INC.; INTELEPEER CLOUD COMMUNICATIONS LLC; ADVANTONE FLORIDA INC.; ADVANTONE, INC.
Reel/Frame 051153/0825 →
RELEASE OF SECURITY INTEREST Recorded Dec 2, 2019
From: HORIZON TECHNOLOGY FINANCE CORPORATION
To: INTELEPEER CLOUD COMMUNICATIONS LLC
Reel/Frame 051153/0958 →
GRANT OF A SECURITY INTEREST -- PATENTS Recorded Dec 2, 2019
From: INTELEPEER CLOUD COMMUNICATIONS LLC
To: TC LENDING, LLC, AS COLLATERAL AGENT
Reel/Frame 051159/0500 →
RELEASE OF SECURITY INTEREST Recorded Nov 22, 2019
From: COMERICA BANK
To: INTELEPEER INC.
Reel/Frame 051097/0970 →
RELEASE OF SECURITY INTEREST Recorded Nov 21, 2019
From: PARTNERS FOR GROWTH IV, L.P.
To: INTELEPEER CLOUD COMMUNICATIONS, LLC
Reel/Frame 051080/0521 →
AMENDED AND RESTATED INTELLECTUAL PROPERTY SECURITY AGREEMENT Recorded May 9, 2019
From: INTELEPEER CLOUD COMMUNICATIONS, LLC
To: SILICON VALLEY BANK
Reel/Frame 049124/0464 →
SECURITY INTEREST Recorded Apr 10, 2019
From: INTELEPEER CLOUD COMMUNICATIONS LLC
To: FINANCE, HORIZON T, FINA
Reel/Frame 048843/0719 →
SECURITY INTEREST Recorded Jan 7, 2018
From: INTELEPEER CLOUD COMMUNICATIONS LLC
To: HORIZON TECHNOLOGY FINANCE CORPORATION
Reel/Frame 044553/0319 →
RELEASE OF SECURITY INTEREST Recorded Aug 1, 2016
From: EAST WEST BANK
To: INTELEPEER CLOUD COMMUNICATIONS LLC
Reel/Frame 039695/0931 →
SECURITY INTEREST Recorded Jul 21, 2016
From: INTELEPEER CLOUD COMMUNICATIONS LLC
To: SILICON VALLEY BANK
Reel/Frame 039213/0749 →
SECURITY INTEREST Recorded Mar 31, 2016
From: INTELEPEER CLOUD COMMUNICATIONS, LLC
To: PARTNERS FOR GROWTH IV, L.P.
Reel/Frame 038163/0001 →
SECURITY AGREEMENT Recorded May 15, 2014
From: INTELEPEER CLOUD COMMUNICATIONS LLC
To: EAST WEST BANK
Reel/Frame 032918/0693 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 18, 2013
From: INTELEPEER, INC.
To: INTELEPEER CLOUD COMMUNICATIONS LLC
Reel/Frame 031619/0873 →
SECURITY AGREEMENT Recorded May 24, 2012
From: HERCULES TECHNOLOGY II, L.P.
To: INTELEPEER, INC.
Reel/Frame 028274/0596 →
SECURITY AGREEMENT Recorded May 22, 2012
From: INTELEPEER, INC.
To: COMERICA BANK, A TEXAS BANKING ASSOCIATION
Reel/Frame 028247/0740 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 14, 2010
From: VOEX, INC.
To: INTELEPEER, INC.
Reel/Frame 024385/0178 →
SECURITY AGREEMENT Recorded May 7, 2010
From: INTELEPEER, INC.,
To: HERCULES TECHNOLOGY II, L.P., A DELAWARE LIMITED PARTNERSHIP; COMERICA BANK
Reel/Frame 024355/0978 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 6, 2007
From: SPADE, JOHN; HABA, HAYDAR; RAMAN, SAM
To: VOEX, INC.
Reel/Frame 019793/0145 →
Continuity (1)
Related Publication 20090059918A1 · Mar 5, 2009