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

• US 8,862,120 B2
• Filed: 02/12/2014
• Issued: 10/14/2014
• 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): SIVJI, NIZAR N
• Application Number:
  US14/179,022
• Publication Number:
  US 20140162634A1
• Time in Patent Office: 244 Days
• Field of Search: 370/252, 370/352, 370/338, 455/445, 455/554, 455/439, 455/432, 455/437, 455/426, 455/464, 455/416, 379/220, 379/221
• US Class Current: 455/426
• CPC Class Codes: H04L 12/66 Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
• CPC Class Codes: H04L 65/00 Network arrangements, protocols or services for supporting real-time applications in data packet communication real-time or near real-time messaging, e.g. instant messaging [IM] H04L51/04; selective video distribution H04N21/00
• CPC Class Codes: H04L 65/1016 IP multimedia subsystem [IMS]
• CPC Class Codes: H04L 65/102 Gateways arrangements for connecting between networks having differing types of switching systems, e.g. gateways, H04L12/66
• CPC Class Codes: H04L 65/1023 Media gateways
• CPC Class Codes: H04L 65/1033 Signalling gateways
• CPC Class Codes: H04L 65/104 in the network
• CPC Class Codes: H04L 65/1053 IP private branch exchange [PBX] functionality entities or arrangements circuit switched PBXs H04M3/00
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04L 65/1076 Screening of IP real time communications, e.g. spam over Internet telephony [SPIT]
• CPC Class Codes: H04L 65/1095 Inter-network session transfer or sharing
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• CPC Class Codes: H04L 65/1106 Call signalling protocols; H.323 and related
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04M 15/00 Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
• CPC Class Codes: H04M 15/57 for integrated multimedia messaging subsystem [IMS]
• CPC Class Codes: H04M 15/63 based on the content carried by the session initiation protocol [SIP] messages
• CPC Class Codes: H04M 15/8292 Charging for signaling or unsuccessful connection
• CPC Class Codes: H04M 2203/1091 Fixed mobile conversion
• CPC Class Codes: H04M 2215/208 : IMS, i.e. Integrated Multimedia messaging Subsystem
• CPC Class Codes: H04M 3/42042 : Notifying the called party of information on the calling party details within substation equipment H04M1/57, signalling details H04Q3/72
• CPC Class Codes: H04M 3/42068 : where the identifier is used to access a profile
• CPC Class Codes: H04M 3/42102 : Making use of the called party identifier
• CPC Class Codes: H04M 3/42314 : in private branch exchanges
• CPC Class Codes: H04M 7/006 : Networks other than PSTN/ISDN providing telephone service, e.g. Voice over Internet Protocol (VoIP) , including next generation networks with a packet-switched transport layer H04L65/00 takes precedence; aspects not specific to the type of network H04M3/00; special services in those networks H04M3/42
• CPC Class Codes: H04M 7/0075 : Details of addressing, directories or routing tables
• CPC Class Codes: H04M 7/009 : in systems involving PBX or KTS networks
• CPC Class Codes: H04Q 2213/13034 : A/D conversion, code compression/expansion
• 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/13109 : Initializing, personal profile
• 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/13204 : Protocols
• CPC Class Codes: H04Q 2213/1322 : PBX
• CPC Class Codes: H04Q 2213/13224 : Off-net subscriber, dial in to/out from network, teleworking
• CPC Class Codes: H04Q 2213/13296 : Packet switching, X.25, frame relay
• CPC Class Codes: H04Q 2213/13348 : Channel/line reservation
• CPC Class Codes: H04Q 2213/13384 : Inter-PBX traffic, PBX networks, e.g. corporate networks
• CPC Class Codes: H04Q 2213/13389 : LAN, internet
• CPC Class Codes: H04Q 2213/13405 : Dual frequency signaling, DTMF
• CPC Class Codes: H04Q 2213/13407 : Detection of data transmission mode
• 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
• CPC Class Codes: H04Q 3/62 : for connecting to private branch exchanges
• CPC Class Codes: H04Q 3/72 : Finding out and indicating number of calling subscriber
• CPC Class Codes: H04W 28/0289 : Congestion control load shedding arrangements in network planning H04W16/08; performing reselection for handling the traffic H04W36/22; wireless traffic scheduling H04W72/12
• CPC Class Codes: H04W 4/16 : Communication-related supplementary services, e.g. call-transfer or call-hold
• CPC Class Codes: H04W 4/20 : Services signaling; Auxiliary data signalling, i.e. transmitting data via a non-traffic channel
• CPC Class Codes: H04W 40/00 : Communication routing or communication path finding
• CPC Class Codes: H04W 40/02 : Communication route or path selection, e.g. power-based or shortest path routing
• CPC Class Codes: H04W 40/22 : using selective relaying for reaching a BTS [Base Transceiver Station] or an access point
• CPC Class Codes: H04W 40/30 : for proactive routing
• CPC Class Codes: H04W 76/10 : Connection setup
• CPC Class Codes: H04W 76/12 : Setup of transport tunnels
• CPC Class Codes: H04W 76/19 : Connection re-establishment
• CPC Class Codes: H04W 76/20 : Manipulation of established connections
• CPC Class Codes: H04W 76/22 : Manipulation of transport tunnels
• CPC Class Codes: H04W 76/28 : Discontinuous transmission [DTX]; Discontinuous reception [DRX]
• CPC Class Codes: H04W 76/30 : Connection release
• CPC Class Codes: H04W 8/12 : between location registers or mobility servers
• CPC Class Codes: H04W 8/26 : Network addressing or numbering for mobility support
• CPC Class Codes: H04W 80/00 : Wireless network protocols or protocol adaptations to wireless operation
• CPC Class Codes: H04W 84/16 : WPBX [Wireless Private Branch Exchange]
• CPC Class Codes: H04W 88/16 : Gateway arrangements
• CPC Class Codes: H04W 92/02 : Inter-networking arrangements
• CPC Class Codes: H04W 92/06 : between gateways and public network devices
• CPC Class Codes: H05K 999/99 : dummy group

Abstract

A mobile application gateway configured to interconnect mobile communication devices on a cellular network with an enterprise network is provided. The mobile application gateway includes a voice and data signaling gateway configured to provide routing functionalities, service functionalities and admission control. A gateway GPRS support node (GGSN) is configured to establish a secure data session between one or more of the mobile communication devices and the enterprise network by establishing a GPRS tunneling protocol (GTP) tunnel between a carrier-hosted serving GPRS support node (SGSN) and the GGSN.

Claims

1. A system, comprising:

a carrier gateway server configured to receive destination routing information from a mobile network; and

the carrier gateway server configured to send a destination to an enterprise gateway server for a communication associated with the destination routing information;

wherein the enterprise gateway server comprises an origination route delay system including access to historical destination routing time data; and

wherein the enterprise gateway server is configured to use the historical destination routing time data to decide when to route a second call leg towards the destination in advance of a first call leg having been routed to the enterprise gateway server.

2. The system of claim 1 wherein the enterprise gateway server 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 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 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. The system of claim 1 wherein the decision when to route the second call leg towards the destination in advance of the first call leg having been routed to the enterprise gateway is performed in order to minimize a time to connect to the destination.

6. A method, comprising:

receiving, by a carrier gateway server, destination routing information from a mobile network; and

transmitting a destination from the carrier gateway server to an enterprise gateway server;

wherein the enterprise gateway server comprises an origination route delay system including access to historical destination routing time data; and

wherein the enterprise gateway server is configured to use the historical destination routing time data to decide when to route a second call leg towards the destination in advance of a first call leg having been routed to the enterprise gateway.

7. The method of claim 6 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.

8. The method of claim 6 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.

9. The method of claim 6 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.

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

11. The method of claim 6 wherein the decision when to route the second call leg towards the destination in advance of the first call leg having been routed to the enterprise gateway is performed in order to minimize a time to connect to the destination.

12. The method of claim 6 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.

13. The method of claim 6 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.

14. The method of claim 6 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.

15. The method of claim 6 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.

16. A non-transitory computer readable medium comprising instructions for:

receiving, by a carrier gateway server, destination routing information from a mobile network; and

transmitting a destination from the carrier gateway server to an enterprise gateway server;

wherein the enterprise gateway server comprises an origination route delay system including access to historical destination routing time data; and

wherein the enterprise gateway server is configured to use the historical destination routing time data to decide when to route a second call leg towards the destination in advance of a first call leg having been routed to the enterprise gateway.

17. The non-transitory computer readable medium of claim 16 comprising instructions for retrieving historical call routing data at the enterprise gateway server including at least one of:

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;

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; and

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.

18. The non-transitory computer readable medium of claim 16 comprising instructions for completing a route from the carrier gateway server to the enterprise gateway server based on the historical data.

19. The non-transitory computer readable medium of claim 16 comprising instructions for wherein the decision when to route the second call leg towards the destination in advance of the first call leg having been routed to the enterprise gateway is performed in order to minimize a time to connect to the destination.

20. The non-transitory computer readable medium of claim 16 comprising instructions for 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 at least one of:

the destination;

the destination as a function of the destination;

the destination as a function of the second call leg; and

the destination as a function of a type of mobile device being served.