IP Library Granted Patent US 8,411,832
Granted Patent B2
US 8,411,832 · App. 13/233,865 · Granted Apr 2, 2013

Wireless call routing in a communication peering grid

Inventor: Steven D. Samuels (Denver, CO)
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,411,832
App. No.
13/233,865
Granted
Apr 2, 2013
Kind
B2
Abstract

A peering grid component operates to facilitate connections of call traffic in a peering grid comprised of customers interconnected with peering partners. A switch is configured to receive call traffic from a customer, and a routing engine is configured to analyze parameters of the call traffic to classify the call traffic as wireless or wire-line traffic. The classification of the call traffic is achieved through the provision of updated wireless routing information accessed by the routing engine. With the classification, the switch, for wireless traffic, accepts and transmits the call traffic at a wireless rate to a peering partner via a connection to the peering partner; and, for wire-line traffic, either transmits the call traffic back to the customer or accepts the call traffic for transmission at a wire-line rate. The wire-line rate is different than the wireless rate, and the associated rates are charged to the customer.

Claims (42)

1. A method for routing calls in a peering grid, the peering grid comprising a plurality of customers interconnected with one or more of a plurality of peering partners via a peering infrastructure, comprising:

receiving, at the peering infrastructure, call traffic from a customer;

analyzing parameters of the call traffic to classify the call traffic as wireless or wire-line traffic;

for wireless traffic, accepting the call traffic and transmitting the call traffic at a wireless rate to a peering partner via a connection to the peering partner, the call traffic destined for a phone number registered by the peering partner of the peering grid;

for wire-line traffic, performing an action comprising (i) transmitting the call traffic back to the customer or (ii) accepting the call traffic and transmitting the call traffic at a wire-line rate;

wherein the wire-line rate is different than the wireless rate, and wherein the wireless rate or the wire-line rate is charged to the customer; and

wherein each of the receiving, analyzing, accepting, and transmitting steps are implemented by a processing device at the peering infrastructure, wherein the processing device accesses instructions from a memory device, the instructions, when executed, causing each of the receiving, analyzing, accepting, and transmitting steps to be implemented.

2. The method of claim 1 , wherein performing an action for wire-line traffic is based upon pre-established terms with the customer generating the call traffic.

3. The method of claim 1 , wherein the connection to the peering partner comprises a dedicated Session Initiation Protocol (SIP) trunk line or a time-division multiplexed (TDM) connection.

4. The method of claim 1 , wherein transmitting the call traffic at a wire-line rate comprises transmitting the call traffic via a connection with a trunk group associated with the customer and charging the customer an associated wire-line rate.

5. The method of claim 1 , further comprising:

receiving updated information related to wireless phone numbers, the updated information comprising wireless routing information, the wireless routing information indicating the peering partners to which the wireless phone numbers are registered.

6. The method of claim 5 , wherein analyzing parameters of the call traffic to classify the call traffic as wireless or wire-line traffic comprises:

analyzing destination routing information associated with the call traffic;

determining if a match exists between the destination routing information and the updated information related to wireless phone numbers;

if a match exists, classifying the call traffic as wireless traffic; and

if a match does not exist, classifying the call traffic as wire-line traffic.

7. The method of claim 6 , wherein the call traffic includes signaling information, the signaling information comprising the destination routing information.

8. The method of claim 5 , wherein the updated information is provided by a Local Exchange Routing Guide (LERG), and wherein the wireless routing information comprises Numbering Plan Area Code Central Office (exchange) Code (NPANXX) numbers.

9. The method of claim 5 , further comprising:

storing the updated information related to wireless phone numbers, the stored, updated information for use in analyzing the parameters of the call traffic to classify the call traffic as wireless or wire-line traffic.

10. A peering infrastructure for routing calls in a peering grid, the peering grid comprising a plurality of customers interconnected with one or more of a plurality of peering partners for communicating call traffic therebetween, comprising:

a switch configured to receive call traffic from a customer;

a routing engine configured to analyze parameters of the call traffic to classify the call traffic as wireless or wire-line traffic;

the switch further configured to:

for wireless traffic, accept the call traffic and transmit the call traffic at a wireless rate to a peering partner via a connection to the peering partner, the call traffic destined for a phone number registered by the peering partner of the peering grid;

for wire-line traffic, perform an action comprising (i) transmit the call traffic back to the customer or (ii) accept the call traffic and transmit the call traffic at a wire-line rate;

wherein the wire-line rate is different than the wireless rate, and wherein the wireless rate or the wire-line rate is charged to the customer.

11. The peering infrastructure of claim 10 , wherein the switch configured to perform an action for wire-line traffic is based upon pre-established terms with the customer generating the call traffic.

12. The peering infrastructure of claim 10 , wherein the connection to the peering partner comprises a dedicated Session Initiation Protocol (SIP) trunk line or a time-division multiplexed (TDM) connection.

13. The peering infrastructure of claim 10 , wherein the switch configured to transmit the call traffic at a wire-line rate comprises the switch transmitting the call traffic via a connection with a trunk group associated with the customer and charging the customer an associated wire-line rate.

14. The peering infrastructure of claim 10 , further comprising:

a communication interface configured to receive updated information related to wireless phone numbers, the updated information comprising wireless routing information, the wireless routing information indicating the peering partners to which the wireless phone numbers are registered.

15. The peering infrastructure of claim 14 , wherein the routing engine configured to analyze parameters of the call traffic to classify the call traffic as wireless or wire-line traffic comprises the routing engine:

analyzing destination routing information associated with the call traffic;

determining if a match exists between the destination routing information and the updated information related to wireless phone numbers;

if a match exists, classifying the call traffic as wireless traffic; and

if a match does not exist, classifying the call traffic as wire-line traffic.

16. The peering infrastructure of claim 15 , wherein the call traffic includes signaling information, the signaling information comprising the destination routing information.

17. The peering infrastructure of claim 14 , wherein the updated information is provided by a Local Exchange Routing Guide (LERG), and wherein the wireless routing information comprises Numbering Plan Area Code Central Office (exchange) Code (NPANXX) numbers.

18. The peering infrastructure of claim 14 , further comprising:

storage configured to store the updated information related to wireless phone numbers, the stored, updated information for use in the routing engine analyzing the parameters of the call traffic to classify the call traffic as wireless or wire-line traffic.

Assignments (20)
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 →
SECURITY INTEREST Recorded Jul 22, 2024
From: INTELEPEER CLOUD COMMUNICATIONS LLC
To: ACQUIOM AGENCY SERVICES LLC
Reel/Frame 068039/0384 →
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: HORIZON TECHNOLOGY FINANCE CORPORATION
To: INTELEPEER CLOUD COMMUNICATIONS LLC
Reel/Frame 051153/0958 →
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 →
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 22, 2012
From: INTELEPEER, INC.
To: COMERICA BANK, A TEXAS BANKING ASSOCIATION
Reel/Frame 028247/0740 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 15, 2011
From: SAMUELS, STEVEN D.
To: INTELEPEER, INC.
Reel/Frame 026914/0407 →
Continuity (2)
Provisional Application 61408366 · Oct 29, 2010
Related Publication 20120106721A1 · May 3, 2012