The present invention relates to VoIP communications, and more particularly to integrating cell phone technology with computer systems equipped with VoIP functionality.
A system, method and computer program product are provided. Included is a cellular phone capable of communicating via a long-range cellular network protocol and a short-range protocol. Further included is a computer system capable of communicating via a long-range hard-line network protocol and the short-range protocol. Thus, when the cellular phone is in the proximity of the computer system, the cellular phone communicates with the computer system utilizing the short-range protocol, so that the cellular phone is used to communicate via the long-range hard-line communication network protocol.
Coupled to the networks 102 are data server computers 104 which are capable of communicating over the networks 102. Also coupled to the networks 102 and the data server computers 104 is a plurality of end user computers 106. In order to facilitate communication among the networks 102, at least one gateway or router 108 is optionally coupled therebetween.
The workstation shown in
The workstation may have resident thereon any desired operating system. It will be appreciated that an embodiment may also be implemented on platforms and operating systems other than those mentioned. One embodiment may be written using JAVA, C, and/or C++ language, or other programming languages, along with an object oriented programming methodology. Object oriented programming (OOP) has become increasingly used to develop complex applications.
Further included is a cellular phone (not numbered) that communicates with the computer as well as a cellular network.
Our course, the various embodiments set forth herein may be implemented utilizing hardware, software, or any desired combination thereof. For that matter, any type of logic may be utilized which is capable of implementing the various functionality set forth herein.
Included is a cellular phone capable of communicating via a long-range cellular network protocol and a short-range protocol. Further included is a computer system capable of communicating via a long-range hard-line network protocol and the short-range protocol. Note, for example, the illustrative architecture of
In one embodiment, the long-range cellular network protocol includes a Global System for Mobile (GSM) protocol, the short-range protocol includes Bluetooth or 802.11 protocol, and the long-range hard-line network protocol includes voice over Internet Protocol (VoIP).
Thus, when the cellular phone is in the proximity of the computer system, the cellular phone communicates with the computer system utilizing the short-range protocol, so that the cellular phone is used to communicate via the long-range hard-line communication network protocol.
As an option, the cellular phone and the computer system may automatically detect each other, and communicate via the short-range protocol upon said detection.
In use, a single phone number may be used in association with the computer system, such that calls are received via the computer system. If the cellular phone and the computer system detect each other via the short-range protocol, the cellular phone ring is initiated via the short-range protocol so that the cellular phone is used to communicate via the long-range hard-line communication network protocol. Note operation 302. If, however, the cellular phone and the computer system do not detect each other via the short-range protocol, the calls are routed to the cellular phone via the long-range cellular network protocol. See operation 304.
Still yet, if the cellular phone and the computer system detect each other via the short-range protocol, the cellular phone call is initiated via the short-range protocol so that the cellular phone is used to communicate via the long-range hard-line communication network protocol by way of the computer system. See operation 306. Finally, if the cellular phone and the computer system do not detect each other via the short-range protocol, the calls are routed via the long-range cellular network protocol. Note operation 308.
As a further option, the computer system may include an interface that is displayed upon said detection. Such interface may indicate details regarding the communication long-range hard-line network protocol.
As yet another option, a cellular phone component such as a cellular phone headset (which is capable of communicating with the cellular phone via the short-range protocol) may further be capable of communicating directly with the computer system via the short-range protocol, to carry out the functionality set forth herein. Of course the various control logic necessary to carry out such functionality may be positioned either in the cellular phone and/or component thereof.
Thus, a speaker or a microphone of the cellular phone may used for communicating using the long-range hard-line network protocol via the computer system, thus obviating the need for a separate speaker or microphone on the computer system. Similarly, a dial pad of the cellular phone may be used for initiating the communications using the long-range hard-line network protocol via the computer system.
To this end, the long-range hard-line network protocol may be used in lieu of long-range cellular network protocol for cost savings, security, and increasing the integrity of the communications.
While various embodiments have been described above, it should be understood that they have been presented by way of example only, and not limitation. For example, any of the network elements may employ any of the desired functionality set forth hereinabove. Thus, the breadth and scope of a preferred embodiment should not be limited by any of the above-described exemplary embodiments, but should be defined only in accordance with the following claims and their equivalents.
The present application claims priority from a provisional application filed Jul. 12, 2004 under application Ser. No. 60/587,343, which is incorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
5771355 | Kuzma | Jun 1998 | A |
6396513 | Helfman et al. | May 2002 | B1 |
6629129 | Bookspan et al. | Sep 2003 | B1 |
7472351 | Zilka | Dec 2008 | B1 |
7702728 | Zaner et al. | Apr 2010 | B2 |
20020111140 | Kim | Aug 2002 | A1 |
20030162544 | Austin et al. | Aug 2003 | A1 |
20040078448 | Malik et al. | Apr 2004 | A1 |
20040116120 | Gallagher et al. | Jun 2004 | A1 |
20040131078 | Gupta et al. | Jul 2004 | A1 |
20040137967 | Bodley | Jul 2004 | A1 |
20040146021 | Fors et al. | Jul 2004 | A1 |
20040266404 | Nasu et al. | Dec 2004 | A1 |
20040267871 | Pratley et al. | Dec 2004 | A1 |
20050086309 | Galli et al. | Apr 2005 | A1 |
20050108338 | Simske et al. | May 2005 | A1 |
20050131900 | Palliyll et al. | Jun 2005 | A1 |
20050271020 | Thermond | Dec 2005 | A1 |
20060062400 | Chia-Chun | Mar 2006 | A1 |
20060101119 | Qureshi et al. | May 2006 | A1 |
Number | Date | Country |
---|---|---|
WO 0201823 | Jan 2002 | WO |
WO 02073886 | Sep 2002 | WO |
Entry |
---|
Office Action Summary from U.S. Appl. No. 11/828,012 mailed on Apr. 30, 2009. |
Lotus white paper “real-time collaboration with lotus sometime” (Jan. 2001). |
Microsoft Word 2003, “How to track and manage changes in a word 2002 and a word 2003 document”, 2003, pp. 1-5. |
Examiner's Answer from U.S. Appl. No. 12/413,676 dated Jan. 30, 2012. |
Office Action from U.S. Appl. No. 11/119,461 dated Apr. 10, 2008. |
Office Action from U.S. Appl. No. 11/119,461 dated Jul. 17, 2008. |
Office Action from U.S. Appl. No. 11/119,461 dated Sep. 18, 2007. |
Office Action from U.S. Appl. No. 11/119,461 dated Nov. 26, 2008. |
Office Action from U.S. Appl. No. 11/828,003 dated Apr. 27, 2009. |
Office Action from U.S. Appl. No. 11/828,003 dated May 1, 2008. |
Office Action from U.S. Appl. No. 11/828,003 dated Oct. 2, 2008. |
Office Action from U.S. Appl. No. 11/828,012 dated Apr. 30, 2009. |
Office Action from U.S. Appl. No. 11/828,012 dated May 1, 2008. |
Office Action from U.S. Appl. No. 11/828,012 dated Oct. 2, 2008. |
Office Action from U.S. Appl. No. 12/413,676 dated May 6, 2011. |
Office Action from U.S. Appl. No. 12/413,676 dated Dec. 1, 2010. |
U.S. Appl. No. 11/119,461, filed Apr. 29, 2005. |
U.S. Appl. No. 11/828,003, filed Jul. 25, 2007. |
U.S. Appl. No. 11/828,012 Jul. 25, 2007. |
U.S. Appl. No. 12/413,676, filed Mar. 30, 2009. |
Number | Date | Country | |
---|---|---|---|
60587343 | Jul 2004 | US |