System and method for speeding call originations to a variety of devices using intelligent predictive techniques for half-call routing

• US 7,974,618 B2
• Filed: 10/26/2006
• Issued: 07/05/2011
• Est. Priority Date: 03/02/2006
• Status: Active Grant

• Current Assignee: Tango Networks Incorporated
• Original Assignee: Tango Networks Incorporated
• Inventors: Silver, Andrew
• Primary Examiner(s): Eng; George
• Assistant Examiner(s): SIVJI, NIZAR N
• Application Number:
  US11/588,078
• Publication Number:
  US 20070206573A1
• Time in Patent Office: 1,713 Days
• Field of Search: 370/252, 370/352, 370/338, 455/445, 455/554.1, 455/439, 455/432.1, 455/437, 455/426.1, 455/464, 455/428, 455/416, 379/221, 379/220.01, 379/221.05, 379/221.14
• US Class Current: 455/426.1
• CPC Class Codes: H04L 12/4633 Interconnection of networks using encapsulation techniques, e.g. tunneling
• CPC Class Codes: H04L 12/64 Hybrid switching systems
• CPC Class Codes: H04L 63/107 wherein the security policies are location-dependent, e.g. entities privileges depend on current location or allowing specific operations only from locally connected terminals
• CPC Class Codes: H04L 65/1016 IP multimedia subsystem [IMS]
• CPC Class Codes: H04L 65/103 in the network
• CPC Class Codes: H04L 65/104 in the network
• CPC Class Codes: H04Q 2213/1307 Call setup
• CPC Class Codes: H04Q 2213/13091 CLI, identification of calling line
• CPC Class Codes: H04Q 2213/13098 Mobile subscriber
• CPC Class Codes: H04Q 2213/13103 Memory
• CPC Class Codes: H04Q 2213/13109 Initializing, personal profile
• CPC Class Codes: H04Q 2213/13141 Hunting for free outlet, circuit or channel
• CPC Class Codes: H04Q 2213/13152 Callback
• CPC Class Codes: H04Q 2213/13176 Common channel signaling, CCS7
• CPC Class Codes: H04Q 2213/1318 Ringing
• CPC Class Codes: H04Q 2213/13196 Connection circuit/link/trunk/junction, bridge, router, gateway
• CPC Class Codes: H04Q 2213/13206 User-to-user signaling, UUS
• CPC Class Codes: H04Q 2213/1322 PBX
• CPC Class Codes: H04Q 2213/13336 Store & forward, messaging systems email H04Q2213/13375
• CPC Class Codes: H04W 12/08 Access security
• CPC Class Codes: H04W 12/61 : Time-dependent
• CPC Class Codes: H04W 40/02 : Communication route or path selection, e.g. power-based or shortest path routing
• CPC Class Codes: H04W 76/12 : Setup of transport tunnels
• CPC Class Codes: H04W 8/04 : Registration at HLR or HSS [Home Subscriber Server]
• CPC Class Codes: H04W 8/18 : Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data

Abstract

A system configured to originate telecommunications services is provided. The system includes a cellular gateway server (GS-C) communicating with a network gateway server (GS-E) located in an enterprise network via a signaling connection. The GS-C is configured to prepare the GS-E for an upcoming communication. The GS-E is configured to receive originator and destination data from the GS-C and is further configured to initiate a route based on the destination data prior to completion of a route from the originator through the GS-C.

Claims

1. A system configured to originate telecommunications services comprising:

a carrier gateway server located in a public cellular network, the carrier gateway server communicates with a mobile switching network, the carrier gateway server configured to receive dialed digits from a mobile device located in the public cellular network;

an enterprise gateway server, located in an enterprise network, that communicates with the carrier gateway server, wherein signaling information only is transmitted between the carrier gateway server and the enterprise gateway server;

the carrier gateway server configured to send data to the enterprise gateway server for an upcoming communication associated with the dialed digits;

the enterprise gateway server configured to;

receive the data including a destination, from the carrier gateway server;

originate a second call leg to the destination associated with the dialed digits, wherein the connection of the second call leg may be delayed for a first time interval based on historical data of a length of time required to establish a voice path to the destination and based on historical data of a length of time required to establish a voice path from the carrier gateway server to the enterprise gateway server so as to minimize an overall time for connecting the call from the mobile device to the destination;

connect the second call leg to the destination with a first call leg from the carrier gateway server; and

wherein the carrier gateway server further comprises an origination route delay system receiving historical destination routing time data based on the data of the destination from the enterprise gateway server, wherein the carrier gateway server is configured to use the historical destination routing time data to complete the first call leg from the carrier gateway server to the enterprise gateway server.

2. The system of claim 1 wherein the enterprise gateway server further comprises a destination route system storing historical destination routing time data based on destination data, wherein the enterprise gateway server is configured to use the historical destination routing time data to initiate the second call leg.

3. The system of claim 1 wherein the enterprise gateway server further comprises a route history system storing historical route timing data based on route data, wherein the enterprise gateway server is configured to use the historical route timing data to initiate the second call leg.

4. The system of claim 1 wherein the enterprise gateway server further comprises a device route system storing historical device routing data based on mobile device data associated with the data of the destination data, wherein the enterprise gateway server is configured to use the historical device routing data to initiate the second call leg.

5. A method for executing originating services comprising:

receiving, by a carrier gateway server located in a public cellular network, dialed digits from a mobile device located in the public cellular network, the carrier gateway server communicates with a mobile switching network;

transmitting originator and destination data associated with the dialed digits, from the carrier gateway server, located in a cellular network, to an enterprise gateway server, located in an enterprise network, wherein signaling information only is transmitted between the carrier gateway server and the enterprise gateway server;

connecting a second call leg, by the enterprise gateway server, to a destination based on the historical call routing data including length of time data, wherein the connection of the second call leg may be delayed for a first time interval based on historical data of a length of time required to establish a voice path to the destination and based on historical data of a length of time required to establish a voice path from the carrier gateway server to the enterprise gateway server, wherein the second call leg is connected prior to the completion of the establishment of a first call leg;

receiving historical destination routing time data based on the data of the destination from the enterprise gateway server, wherein the carrier gateway server uses the historical destination routing time data to complete of the first call leg from the carrier gateway server to the enterprise gateway server; and

connecting the first call leg to the second call leg.

6. The method of claim 5 comprising retrieving historical call routing data at the enterprise gateway server including retrieving historical call route time data associated with one or more prior time intervals required to establish the second call leg over a predetermined route.

7. The method of claim 5 comprising retrieving historical call routing data at the enterprise gateway server including retrieving historical destination route time data associated with one or more prior time intervals required to establish the second call leg to a predetermined destination.

8. The method of claim 5 comprising retrieving historical call routing data at the enterprise gateway server including retrieving historical device route time data associated with one or more prior time intervals required to establish the second call leg to a predetermined class of mobile device.

9. The method of claim 5 further comprising completing a route from the carrier gateway server to the enterprise gateway server based on the historical data.

10. The method of claim 5 further comprising storing call routing time data at the enterprise gateway server based on a time required to complete the second call leg from the enterprise gateway server to the destination.

11. The method of claim 5 further comprising storing call routing time data at the enterprise gateway server based on a time required to complete the second call leg from the enterprise gateway server to the destination as a function of the destination.

12. The method of claim 5 further comprising storing call routing time data at the enterprise gateway server based on a time required to complete the second call leg from the enterprise gateway server to the destination as a function of the second call leg.

13. The method of claim 5 further comprising storing call routing time data at the enterprise gateway server based on a time required to complete the second call leg from the enterprise gateway server to the destination as a function of a type of mobile device being served.