NETWORK ROUTING

• US 20070071221A1
• Filed: 07/28/2006
• Published: 03/29/2007
• Est. Priority Date: 07/29/2005
• Status: Active Grant

• Current Assignee: Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Original Assignee: MCI Incorporated (Verizon Communications Inc.)
• Inventors: Gregorat, Mariafranca, Welch, Gregory, Tai, Yung-Hwa, Verlare, James, McClain, Richard, Lass, Steven, Raps, Yaron, Paiement, Sandra, Crable, Phillip, Dwight, Timothy, Allen, Curtis
• Granted Patent: US 8,798,253 B2
• Time in Patent Office: Days
• US Class Current: 379/265.10
• CPC Class Codes: H04L 41/06 Management of faults, events, alarms or notifications
• CPC Class Codes: H04L 41/0893 Assignment of logical groups to network elements
• CPC Class Codes: H04L 41/0894 Policy-based network configuration management
• CPC Class Codes: H04L 41/5003 Managing SLA; Interaction between SLA and QoS
• CPC Class Codes: H04L 41/509 wherein the managed service relates to media content delivery, e.g. audio, video or TV
• CPC Class Codes: H04L 41/5096 wherein the managed service relates to distributed or central networked applications
• CPC Class Codes: H04L 43/0817 by checking functioning
• CPC Class Codes: H04L 61/4557 Directories for hybrid networks, e.g. including telephone numbers
• CPC Class Codes: H04L 63/102 Entity profiles
• CPC Class Codes: H04L 65/1016 IP multimedia subsystem [IMS]
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04L 65/1096 Supplementary features, e.g. call forwarding or call holding systems providing special services or facilities to telephony subscribers H04M3/42
• CPC Class Codes: H04L 65/401 wherein the services involve a main real-time session and one or more additional parallel real-time or time sensitive sessions, e.g. white board sharing or spawning of a subconference
• CPC Class Codes: H04M 7/123 where the packet-switched network is an Internet Protocol Multimedia System-type network
• CPC Class Codes: H04M 7/128 Details of addressing, directories or routing tables
• CPC Class Codes: H04Q 3/0025 Provisions for signalling
• CPC Class Codes: H04Q 3/0045 involving hybrid, i.e. a mixture of public and private, or multi-vendor systems

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

1. A system comprising:

at least one device configured 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, and

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

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

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

3. The system of claim 1 wherein when determining whether the calling party or the called party is served by the IMS core, the at least one device is configured 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 wherein the information relating to the calling party and the information relating to the called party include telephone numbers.

5. The system of claim 1 wherein when determining whether the calling party or the called party is served by the IMS core, the at least one device is configured 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 wherein the database includes a telephone number mapping database.

7. The system of claim 1 wherein the at least one device is further configured 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 wherein the at least one device is further configured 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 a breakout gateway control function bypasses the IMS core.

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

a computer readable medium containing instructions for causing the at least one device to perform at least one of the determining or the routing.

10. A method comprising:

receiving a call from a first party for a second party;

determining, in response to receiving the call, whether the first party or the second party is served by an Internet Protocol Multimedia Subsystem (IMS) core;

routing the call to the IMS core when the first party or the second party is served by the IMS core; and

routing 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.

11. The method of claim 10 wherein the determining includes:

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

querying the database using information relating to the second party.

12. The method of claim 10 wherein the determining includes:

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

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

13. The method of claim 10 wherein the determining includes:

determining whether the first party invokes an IMS application.

14. The method of claim 13 wherein the determining further includes:

determining 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 configured to;

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

route the call request to an Internet Protocol Multimedia Subsystem (IMS) core when a first condition is met, and

bypass the IMS core when a second condition is met.

16. The system of claim 15 wherein the first condition represents whether the calling party or the called party is served by the IMS core.

17. The system of claim 15 wherein the second condition represents whether the calling party and the called party are not served by the IMS core.

18. The system of claim 15 wherein the first condition represents whether the calling party invokes an IMS application, the called party invokes an IMS application, or the called party is an IMS subscriber.

19. The system of claim 15 wherein the second condition represents whether the calling party does not invoke an IMS application, the called party does not invoke an IMS application, and the called party is not an IMS subscriber.

20. The system of claim 15 wherein the at least one device is further configured to:

determine whether the call request is an emergency call request, and

bypass the IMS core when the call request is determined to be an emergency call request.