IP Library Granted Patent US 8,798,253
Granted Patent B2
US 8,798,253 · App. 11/460,750 · Granted Aug 5, 2014

Network routing

Inventors: Curtis E. Allen (Colorado Springs, CO); Phillip D. Crable (Falcon, CO); Mariafranca Gregorat (Dallas, TX); Steven L. Lass (Allen, TX); Richard L. McClain (Frisco, TX); Sandra A. Paiement (Colorado Springs, CO); Timothy Dwight (Richardson, TX); James L. Verlare (Colorado Springs, CO); Yung-Hwa Tai (Holmdel, NJ); Gregory Welch (Somerset, NJ); Yaron Raps (Brooklyn, NY)
Assignee: Verizon Patent and Licensing 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,798,253
App. No.
11/460,750
Granted
Aug 5, 2014
Kind
B2
Abstract

At least one device receives a call request from a calling party to a called party. The device routes the call request to an Internet Protocol Multimedia Subsystem (IMS) core when a first condition is met and bypasses the IMS core when a second condition is met.

Claims (61)

1. A system comprising:

at least one device to:

receive a call request from a calling party to a called party,

determine whether the calling party or the called party is served by an Internet Protocol Multimedia Subsystem (IMS) core,

route the call request toward the called party, and bypassing the IMS core when the calling party and the called party are not served by the IMS core, and

route the call request to the IMS core when the calling party is not served by the IMS core and the called party is served by the IMS core.

2. The system of claim 1 , where the at least one device is further to:

route the call request to the IMS core when the calling party is served by the IMS core.

3. The system of claim 1 , where, when determining whether the calling party or the called party is served by the IMS core, the at least one device is to:

query a database using information relating to the calling party, and

query the database using information relating to the called party.

4. The system of claim 3 , where the information relating to the calling party and the information relating to the called party include telephone numbers.

5. The system of claim 1 where, when determining whether the calling party or the called party is served by the IMS core, the at least one device is to:

send a first domain name service (DNS) query to a database using information relating to the calling party, and

send a second DNS query to the database using information relating to the called party.

6. The system of claim 5 , where the database includes a telephone number mapping database.

7. The system of claim 1 , where the at least one device is further to:

store a list of originating hosts,

determine whether the call request was received from an originating host in the list of originating hosts, and

reject the call request when the call was not received from an originating host in the list of originating hosts.

8. The system of claim 1 , where the at least one device is further to:

store a list of emergency numbers,

determine whether the call request is an emergency call request using the list of emergency numbers, and

route the call request to a breakout gateway control function when the call request is an emergency call request, the routing the call request to the breakout gateway control function bypasses the IMS core.

9. The system of claim 1 , where the at least one device comprises:

a computer readable memory device containing instructions for causing the at least one device to perform at least one of the determining or the routing the call request to the IMS core.

10. A method performed by a network device, the method comprising:

receiving, by a communication interface of the network device, a call from a first party for a second party;

determining, by a processor of the network device and based on receiving the call, whether the first party is served by an Internet Protocol Multimedia Subsystem (IMS) core;

determining, by the processor of the network device and based on receiving the call, whether the second party is served by the IMS core;

routing, by the communication interface, the call toward the second party and bypassing the IMS core when the first party and the second party are not served by the IMS core; and

routing, by the communication interface, the call request to the IMS core when the first party is not served by the IMS core and the second party is served by the IMS core.

11. The method of claim 10 ,

where determining whether the first party is served by the IMS core includes:

querying a database using information relating to the first party, and

where determining whether the second party is served by the IMS core includes:

querying the database using information relating to the second party.

12. The method of claim 10 ,

where determining whether the first party is served by the IMS core includes:

sending a first domain name service (DNS) query to a database using information relating to the first party, and

where determining whether the second party is served by the IMS core includes:

sending a second DNS query to the database using information relating to the second party.

13. The method of claim 10 , where determining whether the first party is served by the IMS core includes:

determining whether the first party invokes an IMS application.

14. The method of claim 10 , where determining whether the first party is served by the IMS core includes:

determining at least one of whether the second party invokes an IMS application or whether the second party is an IMS subscriber.

15. A system comprising:

at least one device to:

receive a call request from a calling party to a called party,

neither the calling party nor the called party being an Internet Protocol Multimedia Subsystem (IMS) user,

evaluate whether the calling party has invoked an IMS application,

evaluate whether the called party has invoked an IMS application,

route the call request to the IMS core when at least one of the calling party or the called party has invoked the IMS application,

bypass the IMS core when the calling party and the called party have not invoked the IMS application,

receive another call request,

determine that the other call request is an emergency call request, and

bypass an IMS core based on the other call request being the emergency call request.

16. The system of claim 15 , where the at least one device is further to:

store a list of originating hosts,

determine whether the call request was received from an originating host in the list of originating hosts, and

reject the call request when the call was not received from an originating host in the list of originating hosts.

Assignments (5)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 27, 2014
From: ALLEN, CURTIS E.; CRABLE, PHILLIP D.; GREGORAT, MARIAFRANCA; PAIEMENT, SANDRA A.; DWIGHT, TIMOTHY; VERLARE, JAMES L.; TAI, YUNG-HWA; WELCH, GREGORY; RAPS, YARON
To: MCI, LLC
Reel/Frame 033197/0681 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 2, 2009
From: VERIZON BUSINESS GLOBAL LLC
To: VERIZON PATENT AND LICENSING INC.
Reel/Frame 023455/0210 →
CHANGE OF NAME Recorded Mar 21, 2007
From: MCI, LLC
To: VERIZON BUSINESS GLOBAL LLC
Reel/Frame 019041/0052 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 12, 2006
From: LASS, STEVEN L.; MCCLAIN, RICHARD L.
To: MCI, LLC
Reel/Frame 018620/0235 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 20, 2006
From: MCCLAIN, RICHARD LEE
To: MCI COMMUNICATIONS CORPORATION
Reel/Frame 018538/0378 →
Continuity (3)
Provisional Application 60703812 · Jul 29, 2005
Provisional Application 60764748 · Feb 3, 2006
Related Publication 20070071221A1 · Mar 29, 2007