KENNETH ROZINSKY D (CA)
| US6473423B1 | 2002-10-29 | |||
| US20040160946A1 | 2004-08-19 | |||
| US20040062210A1 | 2004-04-01 | |||
| CA2334472A1 | 2001-08-08 | |||
| CA2268564C | 2005-07-12 |
I CLAIM:
1. A method of automatically initiating a call through a VOIP infrastructure to a destination from a mobile device, said method comprising:
(a) directly or indirectly contacting a central controller by sending at least an initial signal from said mobile device, said initial signal including a first device identification for said destination;
(b) said central controller automatically validating and processing a signal based on said initial signal by determining said first device identification for said call destination and a second device identification for said mobile device; and
(c) said central controller automatically using said first and second device identifications to connect said mobile device to said destination through said VOIP infrastructure.
2. A method as claimed in Claim 1 wherein said initial signal from said mobile device is sent to a service provider by a message to a messaging structure for said mobile device and said service provider sends a signal based on said initial signal to said central controller.
3. A method as claimed in Claim 1 including the steps of sending said initial signal from said mobile device to a messaging infrastructure of a carrier for said mobile device and said messaging infrastructure and sending a signal based on said initial signal from said messaging infrastructure to said central controller.
4. A method as claimed in Claim 3 wherein there is more than one destination and said central controller connects said mobile device with all of said destinations in a conference call.
5. A method as claimed in Claim 2 including the step of controlling the controller by software.
6. A method as claimed in Claim 1 including the step of making the call to a VOIP destination.
7. A method as claimed in Claim 2 including the step of sending said initial signal from said mobile device by one of text messaging or email service through said mobile carrier's infrastructure.
8. A method as claimed in Claim 7 including the step, where the initial signal is sent by email service, of sending said message to an appropriate SMTP server and, where said initial signal is sent by a SMS, of making the message available via the carrier's SMSC server.
9. A method as claimed in Claim 1 including the steps of processing said initial signal to extract identification information for said destination.
10. A method as claimed in Claim 9 including the step of extracting a number for said destination.
11. A method as claimed in Claim 1 including the steps of, after said call is initiated from said mobile device, said central controller calling said mobile device and calling said destination and connecting the mobile device to said destination if both of said calls are answered.
12. A method as claimed in Claim 1 including the step, after said call has been completed, of having the central controller send a message to said mobile device providing one or more of the number or numbers called, the duration of the call, and the cost of the call.
13. A method as claimed in Claim 1 including the steps, after said call is initiated by said mobile device, of disconnecting said mobile device and the central controller causes the mobile device to be called back.
14. A method as claimed in Claim 13 including the steps, after the central controller causes the mobile device to be called back, the destination is called by the central controller as soon as the mobile device answers the call back, said central controller connecting the mobile device with the destination when separate connections have been made to the destination and to the mobile device through the call back.
15. A method of automatically providing a VOIP connection between a mobile device and a destination, said method comprising having a central controller that is capable of receiving a remote signal directly or indirectly from said mobile device, said central controller automatically validating and processing each signal by determining a first device ID for the destination and a second device ID for the mobile device for each signal that is received by the central controller, the central controller separating the signals and processing each signal to connect the destination with the mobile device through a VOIP infrastructure,
16. A method of automatically providing a VOIP connection as claimed in Claim 7 including the steps of processing a plurality of calls, at least some of which occur simultaneously.
17. A system for automatically processing calls from mobile devices to destinations through a VOIP infrastructure, said system comprising a central controller, said central controller being capable of receiving an initial signal directly from a mobile device or directly from a messaging infrastructure of a carrier for said mobile device, said central controller being capable of identifying the mobile device and the destination sought by the mobile device, said central controller making a connection between the mobile device and the destination through said VOIP infrastructure until the mobile device or the destination disconnects.
18. A system as claimed in Claim 17 wherein said system is set up to make said connection by said controller calling said mobile device back and making said connection after said mobile device is answered.
19. A system as claimed in Claim 18 wherein said controller receives said initial signal by text messaging or email service through said messaging structure for said carrier. |
SYSTEM AND METHOD FOR INITIATING MOBILE DEVICE CALLS THROUGH A VOIP INFRASTRUCTURE
BACKGROUND OF THE INVENTION FIELD OF INVENTION
[0001] This invention relates to a method and system for completing calls from mobile devices to destinations through a VOIP infrastructure.
DESCRIPTION OF THE PRIOR ART
[0002] It is known to make calls to VOIP destinations through computers and to make calls to VOIP destinations through wired telephones. With the large increase in use of cell phones many long distance calls are made from mobile devices and those calls are relatively expensive compared to calls from wired telephones. Long distance calls from wired telephones to non-VOIP destinations are much more expensive than calls to VOIP destinations and the capability of making VOIP calls has resulted in a large reduction in the long distance charges by telephone companies.
[0003] The Bohacek et al U.S. Patent No. 6,982,985 issued on January 3, 2006 describes a communication system that includes a switching network and a wireless network. The system routes telephone calls to wireless subscribers and allows a VOIP VPN system to gain and maintain control of a call. If a called party does not answer a call, the caller may route a call to the called party's secretary, voicemail, pager or alternate destination. The system does not process calls from a wireless subscriber through a VOIP system and is intended to route calls to a wireless subscriber without going through the home service area of the subscriber when the subscriber is located outside of the home service area. SUMMARY OF THE INVENTION [0004] It is an object of the present invention to provide a system and method whereby calls can be made automatically through VOIP infrastructure to VOIP destinations or to other destinations from mobile devices.
[0005] It is a further object of the present invention to provide a system and method whereby long distance calls can be made from a mobile device to a destination through a VOIP infrastructure so that long distance charges on the call are at a significantly lower rate than the long distance charges for long distance calls from a cell phone that are not made through a VOIP infrastructure, except, perhaps, on the charges for the initial signal from the mobile device to
indicate that a call is desired to be made. VOIP rates are much less than non-VOIP rates, particularly for calls from a cell phone.
[0006] A method of automatically initiating a call through a VOIP infrastructure to a destination from a mobile device comprises directly or indirectly contacting a central controller by sending at least an initial signal from the mobile device, the initial signal including a first device identification for the destination. The central controller automatically validates and processes a signal based on the initiating signal by determining the first device identification for the call destination and a second device identification for the mobile device. The central controller automatically uses the first and second device identifications to connect the mobile device to the destination through the VOIP infrastructure and automatically terminates the call when one of the mobile device and the destination disconnects from the call. [0007] A system for automatically processing calls from mobile devices to destinations through a VOIP infrastructure comprises a central controller. The central controller is capable of receiving a signal directly from a mobile device or directly from a messaging infrastructure of a carrier for the mobile device. The central controller is capable of identifying the mobile device and the destination sought by the mobile device. The central controller makes a connection between the mobile device and the destination through the VOIP infrastructure until the mobile device or the destination disconnects. BRIEF DESCRIPTION OF THE DRAWINGS [0008] Figure 1 is a block diagram of a system and method for automatically making calls through VOIP infrastructure from a mobile device to destinations. DETAILED DESCRIPTION OF A PREFERRED EMBODIMENT
[0009] In Figure 1, the operator of the mobile device sends a message through the mobile carrier's messaging infrastructure or email service to a central controller. The message contains identification information for a destination that a mobile device user wishes to call or the message contains a request for information. The identification of the mobile device is usually automatically placed within the message and the central controller therefore identifies the mobile device and also identifies the destination that the user of the mobile device wishes to call. If the device identification for the mobile device is not automatically included, then the central controller indicates to the mobile device that that information is required.
[0010] The message is received by the mobile carrier and forwarded on for processing to the central controller. In cases where the message is being sent via email, the message will be
sent to the appropriate SMTP (Simple Mail Transfer Protocol) server. In cases where it is sent via a SMS (Short Message Service), then the message will be made available via the carrier's SMSC (Short Message Service Centre) server. As new messaging infrastructure and protocols become available, the message will be made available by whatever methods the protocol allows. [0011] The messages will be received, validated and processed to extract the identification of the destination or the information or service that the mobile device operator is requesting.
[0012] After a call is initiated from a mobile device to a destination, the central controller will call the mobile device and also call the destination. The call is initiated through the messaging structure of the service provider for the mobile device. For example, the call can be initiated by text messaging through the messaging service or email service of the service provider. The service provider sends a signal to the central controller. The central controller calls the mobile device and calls the destination. If the call to the destination is answered, the two calls are then connected to provide a call to a destination from a mobile device through the VOIP infrastructure. After the call has been completed, if desired, the central controller can send a message to the mobile device stating the number or numbers called, the duration of the call and the cost of the call.
[0013] When the mobile device sends a message through the mobile carrier's messaging infrastructure or email service, the message will contain either the number or device identification for the mobile device as well as the device identification for the destination.
[0014] The system is capable of handling a call from a mobile device to more than one destination simultaneously and the system will set up a conference call in those circumstances. [0015] The destination can be a VOIP destination or can be to a non-VOIP destination, as long as the call is always directed through a VOIP infrastructure. By having the controller make the call through a VOIP infrastructure, the mobile device user incurs VOIP rates for the long distance call. Charges can be incurred with the initial signal depending on how it is made. In any event, the duration of the call relating to the initial signal is very short. After the call is initiated, the mobile caller disconnects and the controller causes the mobile device to be called back in approximately 10 to 15 seconds. [0016] When the central controller causes the mobile device to be called back, the destination is called by the central controller as soon as the mobile device answers the call back.
When connections have been made to the destination and to the mobile device through the call back, the central controller connects the mobile device with the destination.
[0017] While the system and method have been described for one call, the system and method of the present invention can be used to process a plurality of calls.
[0018] The method and system of the present invention can also connect more than one destination with the mobile device in a conference call. The central controller is controlled by computer software.