US9270799B2 - Using indirect communication to provide a solution to use international dialing convention and incorporating phone numbers for non-phone devices - Google Patents

Abstract

An indirect communication system and a method of indirect communication include a mobile phone as either a calling device or receiving device. The mobile phone calls another device to set up a prospective communication, and then uses Voice over Internet Protocol (VoIP) to communicate with the other device over the Internet. The receiving device receives a generated signal notifying the receiving device of a proposed communication with the calling device. A server sets up a meeting point channel after the calling device has connected to the server. The server receives outgoing VoIP packets from the calling device and redirects the outgoing VoIP packets to the receiving device.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

The subject application is a continuation in part of U.S. application Ser. No. 11/808,753, filed Jun. 12, 2007, which claims priority to U.S. Provisional Application Ser. No. 60/840,005, filed Aug. 25, 2006, and this application is also based upon and claims the benefit of priority of the prior U.S. Provisional Patent Application No. 61/676,457, filed Jul. 27, 2012, and U.S. Provisional Patent Application No. 61/670,938, filed Jul. 12, 2012, the entire contents of all of which are incorporated herein by reference.

BACKGROUND

1. Field

The invention relates generally to a device and method of making and receiving relatively low cost, high quality phone calls using a mobile phone with wireless media and Voice over Internet Protocol (VoIP).

2. Description of the Related Art

A1. The International Dialing Convention (IDC)

The International Dialing Convention (IDC) is a method to identify every individual phone (mobile phone or landline phone) in the world uniquely regardless the country and region status. The format is

+(Country Code) (Area Code) (Local Number)

The plus sign “+”, is the international dialing prefix follow by the “Country Code” representing each country in the world. For example, “+1” represents “USA”, and “+44” is “United Kingdom”. The area code is usually used to identify the city of the country. Together with the local number, each phone can be identified uniquely such as:

+44 7927 176753—A mobile phone (12345678) in UK

+1 202 87654321—A phone (87654321) in Washington D.C., USA

SUMMARY

In one aspect a communication system includes a first transceiver having a first identifier, a second transceiver having a second identifier, a first sub-device having a first sub-identifier comprised of the first identifier and a first device code, a second sub-device having a second sub-identifier comprised of the second identifier and a second device code, a first communication channel between the first sub-device and the second sub-device, a second communication channel between the first sub-device and the second transceiver, a first transmission of information from the first sub-device on the first communication channel identified by the first sub-identifier, a second transmission of information from the second sub-device on the first communication channel identified by the second sub-identifier, a third transmission of information from the first sub-device on the second communication channel identified by the first identifier, and a fourth transmission of information from the second transceiver on the second communication channel identified by the second identifier.

The first and/or second identifiers may be an identification number of the first transceiver, a phone identifier, a series of digits, a GSM identifier, an International Dialing Convention identifier, a mobile phone identifier, or a land-line telephone identifier.

The first and/or second sub-identifiers may be an artificial device code, a sub-device identifier assigned to the first transceiver, or the first or the second identifiers.

The artificial device code and/or the sub-device identifier may be removed to call an outside line.

The first and/or second transceivers may be a handset, a phone, a gateway, a base station, a server, a cell tower, a transceiver, a computer, a palm top, a laptop, a tablet, or a personal digital assistant.

In one aspect a method of communication includes applying a first identifier to a first transceiver, applying a second identifier to a second transceiver, applying a first sub-identifier to a first sub-device comprised of the first identifier and a first device code, applying a second sub-identifier to a second sub-device comprised of the second identifier and a second device code, providing a first communication channel between the first sub-device and the second sub-device, providing a second communication channel between the first sub-device and the second transceiver, transmitting first information from the first sub-device on the first communication channel identified by the first sub-identifier, transmitting second information from the second sub-device on the first communication channel identified by the second sub-identifier, transmitting third information from the first sub-device on the second communication channel identified by the first identifier, and transmitting fourth information from the second transceiver on the second communication channel identified by the second identifier.

In one aspect a communication system includes a first transceiver having a first identifier, a second transceiver having a second identifier, a server having a third identifier, a first sub-device having a first sub-identifier comprised of the first identifier and a first device code, a second sub-device having a second sub-identifier comprised of the second identifier and a second device code, a first communication channel between the first sub-device and the second sub-device, a second communication channel between the first sub-device and the server, the second communication channel not concurrent with the first communication channel, a third communication channel between the second sub-device and the server, the third communication channel not concurrent with the first communication channel, a first transmission of information from the first sub-device on the first communication channel identified by the first sub-identifier, a second transmission of information from the first sub-device on the second communication channel identified by the first sub-identifier, the second transmission of information following the first transmission of information and being relayed by the server to the second sub-device, and a third transmission of information from the second sub-device on the third communication channel identified by the second sub-identifier, the third transmission of information following the first transmission of information and being relayed by the server to the first sub-device.

The server may be a computer, a base station, a handset, a Voice over Internet Protocol handset, a Voice over Internet Protocol controller, a switch box, or a dedicated black box device and peripherals.

An address of a meeting point on the server may be an identification identifier of the second transceiver and an Internet Protocol address or a Domain Name System name of the server.

If the second transceiver accepts the first transmission, the second transceiver connects to the meeting point.

If the second transceiver declines the first transmission, the second transceiver sends a decline message to the server and the server relays the decline message to the first transceiver.

If the second transceiver suggests an alternative meeting point, the second transceiver connects to the alternative meeting point.

The second and third communication channels may be comprised of packets formatted with a format selected from the group consisting of Voice over Internet Protocol, Internet Protocol, and User Datagram Protocol.

The packets may be redirected at the server by changing a sending address of each packet header from an address of the meeting point to an address of the second transceiver.

In one aspect a method of communication includes applying a first identifier to a first transceiver, applying a second identifier to a second transceiver, applying a third identifier to a server, providing a first sub-device having a first sub-identifier comprised of the first identifier and a first device code, providing a second sub-device having a second sub-identifier comprised of the second identifier and a second device code, providing a first communication channel between the first sub-device and the second sub-device, providing a second communication channel between the first sub-device and the server, the second communication channel not concurrent with the first communication channel, providing a third communication channel between the second sub-device and the server, the third communication channel not concurrent with the first communication channel, transmitting first information from the first sub-device on the first communication channel identified by the first sub-identifier, transmitting second information from the first sub-device on the second communication channel identified by the first sub-identifier, the second transmission of information following the first transmission of information, relaying the second transmission of information to the second sub-device by the server, transmitting third information from the second sub-device on the third communication channel identified by the second sub-identifier, the third transmission of information following the first transmission of information, and relaying the third transmission of information to the first sub-device by the server.

The above-described embodiments of the present invention are intended as examples, and all embodiments of the present invention are not limited to including the features described above.

The above and other features and advantages of the present invention, as well as the structure and operation of various embodiments of the present invention, are described in detail below with reference to the accompanying drawings.

Additional aspects and/or advantages of the invention will be set forth in part in the description which follows and, in part, will be obvious from the description, or may be learned by practice of the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated herein and form part of the specification, illustrate various embodiments of the present invention and, together with the description, further serve to explain the principles of the invention and to enable a person skilled in the pertinent art to make and use the invention. In the drawings, like reference numbers indicate identical or functionally similar elements. These and/or other aspects and advantages of the invention will become apparent and more readily appreciated from the following description of the embodiments, taken in conjunction with the accompanying drawing of which:

FIG. 1 is a schematic of an indirect communication system according to an embodiment;

FIG. 2 is schematic of a meeting point server for use with an embodiment;

FIG. 3A is schematic of an indirect communication system according to an embodiment;

FIG. 3B is schematic of an indirect communication system according to an embodiment;

FIG. 4 is a schematic of a meeting point server for use with an embodiment;

FIG. 5 is a schematic of a base station for use with an embodiment;

FIG. 6 is a schematic of a transceiver for use with an embodiment;

FIG. 7 is a schematic of a meeting point server for use with an embodiment;

FIG. 8 is a schematic of a notifying signal for use with an embodiment;

FIG. 9 is a schematic of a meeting point server for use with an embodiment;

FIG. 10 is a schematic of a meeting point server for use with an embodiment;

FIG. 11 is a schematic of a meeting point server for use with an embodiment;

FIG. 12 is a schematic of a meeting point server for use with an embodiment;

FIG. 13 is a schematic of a meeting point server for use with an embodiment;

FIG. 14 is a schematic of a meeting point server for use with an embodiment;

FIG. 15 is a schematic of a meeting point server for use with an embodiment;

FIG. 16 is a schematic of a meeting point server for use with an embodiment;

FIG. 17 is a schematic of a meeting point server for use with an embodiment;

FIG. 18 is a schematic of a meeting point server for use with an embodiment;

FIG. 19 is a process chart of an indirect communication method according to an embodiment;

FIG. 20 is a process chart of address generation for use with an embodiment;

FIG. 21 is a process chart of packet redirection for use with an embodiment;

FIG. 22 is a process chart of setting up a meeting point channel for use with an embodiment;

FIG. 23 is a process chart of setting up a telephone call for use with an embodiment;

FIG. 24 is a schematic of a meeting point server for use with an embodiment; and

FIG. 25 is a schematic of a meeting point server for use with an embodiment.

FIG. 26 shows a transceiver according to an embodiment;

FIG. 27 shows an indirect communication system according to an embodiment;

FIG. 28 shows a communication system using an artificial device code according to an embodiment;

FIG. 29 shows a transceiver according to an embodiment;

FIG. 30 shows a call from one sub-device to another according to an embodiment;

FIG. 31 shows a call from a sub-device to an outside line according to an embodiment;

FIG. 32 shows a call from one sub-device to another according to an embodiment;

FIG. 33 shows a communication system according to an embodiment;

FIG. 34 shows a method of communication according to an embodiment;

FIG. 35 shows a communication system according to an embodiment; and

FIG. 36 shows a method of communication according to an embodiment.

DEFINITIONS

The Internet: sometimes called the Transmission Control Protocol/Internet Protocol (TCP/IP) network, refers generally to a collection of interconnected networks that uses the TCP/IP protocol.

An Internet Protocol (IP) address refers generally to an address which is a unique number having four parts separated by dots, e.g., 165.113.223.2. Each part can have values from 0 to 255. For the TCP/IP network (or Internet), IP addresses can be used to uniquely identify a computer on the network. A newer version of IP addresses using six parts instead of four is called IPv6. A computer network in which each computer can be uniquely identified by its corresponding IP address is also called the IP network.

A Domain Name System (DNS) refers generally to an Internet service that translates domain names into IP addresses. the domain name system may be used on the Internet to translate a name such as www.pwt.com to an IP address, e.g. 165.113.223.2.

Broadband refers generally to a type of data transmission in which a single medium (wire or wireless) has the capacity to carry several channels at any one time. Also known as multiplexing. Computer network or communications between computers may be broadband, with speeds from, for example, 1 Mbps (mega bit per second) to 20 Mbps.

Session Initiation Protocol (SIP) is the Internet Engineering Task Force (IETF) protocol for VoIP and other text and multimedia sessions, like instant messaging, video, online games and other services.

A SIP Phone refers generally to a device, such as a phone, which is connected to Internet directly via a broadband modem or similar device for making and receiving calls without the involvement of a PC.

An IP Packet refers generally to packets used for Internet communication that are structured the same way to ensure compatibility in a global scale. An IP packet includes an IP header followed by a variable-length data field.

A PSTN Gateway refers generally to software installed on a machine with VoIP which allows the VoIP machine to make and receive calls from an ordinary phone (i.e. a PSTN phone).

A Base Station (BS) refers generally to a device, such as a gateway, WiFi router, GSM router, a computer or a server, with a connection to a transceiver, enabling communication with a mobile phone. The BS can also connect to the Internet for VoIP functionality.

The Global System for Mobile Communication (GSM) Network uses a series of radio transmitters, which may be Base Stations (BS), to connect mobile phones to the cellular network. The radio frequency of a Base Station, which is also called a cell, covers a certain range within a discrete area. Base Stations may be interconnected so that a mobile phone can move from one cell to another without dropping a call. A set of Base Stations is connected to a particular Base Station Controller (BSC). A set of Base Station Controllers is connected to a Mobile Switching Center (MSC). The Mobile Switching Center and its associated modules route incoming and outgoing calls, including the PSTN calls and calls to other networks.

Wireless Media or Frequency refers generally to the Radio Frequency used to communicate between a mobile phone and a Base Station.

GSM Wireless Media refers generally to the five radio frequency (RF) bands used by GSM mobile phones. The bands are:

GSM-900—using 890-915 MHz and from 1 to 124 RF channel number.

GSM-1800—using 1710-1785 MHz and 374 RF channels from 512 to 885 channel number.

GSM-850—using 824-849 MHz and from 128 to 251 channel number.

GSM-1900—using 1850-1910 MHz from 512 to 810 channel number.

GSM-400—using 890-915 MHz.

Both radio frequency and channel number are compatible with 1st generation (1 G) mobile phones.

Wireless Fidelity (Wi-Fi), also known as IEEE 802.11, operates within the spectrum near 2.4 GHz, except for 802.11a, which uses 5 GHz. Different countries may have different Wi-Fi settings due to the power output requirements. By using standardized channel numbers, Radio Frequency (RF) differences can be easily detected internationally. The standard coverage of Wi-Fi is short, under a few hundred meters.

Worldwide interoperability Microway Access (WiMAX), also known as IEEE 802.16, is a standard for specific wireless access using RF between 2 to 20 GHz. The transmitting and receiving range for WiMAX, often more than 20 kilometers, is greater than that of Wi-Fi.

DESCRIPTION OF EMBODIMENTS

It would be desirable to allow mobile phones to place and receive calls using the Internet (or a Voice over Internet Protocol network), at low cost and relatively high quality. It would further be desirable if a caller were able to let a receiving device know that someone is waiting to communicate at a meeting point on the Internet, without incurring excessive airtime charges. It would further be desirable for the receiving device to be able to connect to the meeting point as well and communicate with the calling device using Voice over Internet Protocol (VoIP), without incurring further air time charges. It would further be desirable if the caller were able to let the receiving device know that someone is waiting at a the meeting point by sending a short signal to the receiving device over the existing cellular network, to minimize expenditures for air time. It would further be desirable if the receiving device did not have to answer the short notification tone, or could hang up quickly, along with the calling device, so that airtime expenditures could be minimized, and conduct the actual communication with the calling device through the meeting point. Finally, it would be desirable if the location of the receiving device did not need to be known to the caller.

The Internet is a so-called packet-switched network. Packets are structured similarly to ensure compatibility on a global scale. An IP packet has a header followed by a variable-length data field. Among the header fields will be a Source IP, which is an address of the originating device, and a Destination IP, which is an address of the destination device. Although IP is used in this description, the invention is not limited to a particular packet format, or to IP in general. The examples herein, rather, are merely exemplary, and not meant to be limiting.

Another type of network is a circuit switched network, such as the Public Switched Telephone Network (PSTN), also known as the Plain Old Telephone System (POTS). A public switched telephone network refers generally to the national and international telephone system based on copper wires and carrying analog voice data. Telephone service carried by the public switched telephone network is often called “Plain Old Telephone Service” (POTS). Plain old telephone service is the standard telephone service that most homes use. In general, plain old telephone service is restricted to about 52 Kbps (52,000 bits per second).

A third type of network is a wireless, or radio frequency (RF), network. Wireless networks could be packet switched, like the internet, or circuit switched, like the public switched telephone network, or both.

A gateway is often used to convert packet switched data to circuit switched data, and vice versa. Thus, a gateway enables a VoIP device to make and receive calls from an ordinary phone, such as a public switched telephone network phone. A gateway refers generally to a device, either hardware or software, equipped to interface with another network that uses different protocols. A gateway may contain devices such as protocol or signal translators, for example, to provide system interoperability. A gateway may establish mutually acceptable procedures between two networks.

Voice over Internet Protocol (VoIP) refers generally to protocols, such as Session Initiation Protocol (SIP) and the International Telecommunication Union (ITU) H.323, used to carry voice signals over a packet-switched network, such as the Internet. VoIP can provide telephony capability to users on the Internet. A computer with a VoIP client (or VoIP software phone) can be used to make calls to another computer over the TCP/IP network (i.e. Internet). In general, the speaker, microphone, and the sound card of the computer can be used to talk and listen with the person at the other end. The keyboard of the computer can be used to type in the IP address or the domain name system of the receiving end so that communication can be established. The entire community using VoIP client over the TCP/IP network is generally referred to as the VoIP Network.

In a Voice over Internet Protocol communication, a voice signal received from a microphone is sampled and the samples are converted into packet payloads with a sound card by, for example, extracting the frequency content of the voice signal with a discrete Fourier transform, and forming packet payloads with the frequency data. The address of the receiver to which the packets will be addressed may be entered at a keyboard. The frequency data are converted back to voice signals at the receiver with an inverse Fourier transform using another sound card, and emitted by a speaker. Thus, VoIP can provide telephony capability to users on the Internet. The speaker and microphone could be embodied in a software phone.

Formats like Voice over Internet Protocol, which utilize the Internet to transfer information, offer the ability to communicate for a flat fee, paid to an internet service provider. A flat fee is often less expensive, given the duration or frequency of the communication, than the comparable cost of communication using a cellular phone. One drawback associated with communication over the Internet, however, is that the parties to the communication need to intend to communicate, and also participate in setting up the call by, at least, making their location known. Each party, for example, accesses the Internet separately, contacts the other party, and then commences the communication.

There is, in general, no Internet analogy to the notifying function provided by a cellular telephone service provider, in which one party dials a telephone number of the other party, and the cellular phone service provider locates the other party's phone and connects the call. The Internet, in particular, has none of the infrastructure provided by a cellular phone service provider dedicated to locating the cellular phone of the called party. It would be desirable, therefore, to be able to utilize the infrastructure possessed by the cellular phone service providers to set up a communication, by locating and notifying the called party, and then switch to, for example, communication over the Internet for the actual duration of the call.

InFIG. 1, there is shown an embodiment of an indirect communication system including acalling device100, which may have atransceiver104, and areceiving device102, which may also have atransceiver104. If a cellular network, such as a Global System for Mobile Communication (GSM) network, serves the callingdevice100 and the receivingdevice102, the callingdevice100 and the receivingdevice102 might be connected to the network by a series ofbase stations106. Thebase stations106 may be connected, in turn, to a mobile switching center (MSC), which is in turn connected to other networks.

Eachbase station106 serves an area called a cell, and thecalling device100 or the receivingdevice102, upon entering the cell, communicates with the network through thatbase station106. The callingdevice100 and the receivingdevice102, furthermore, may be handed off from onebase station106 to another as they move from cell to cell. Thebase station106 may be a personal computer (PC) with a public switched telephone network gateway, a modem, and/or switch box with the usual public switched telephone network.

The indirect communication system may also have ameeting point server108 for communicating with the callingdevice100 and the receivingdevice102, and a connection with ancommunication network114. Themeeting point server108 may be a server with a public switched telephone network gateway, a modem, and/or a switch box. Either the callingdevice100, the receivingdevice102, or both, may be a mobile phone. The roles of thecalling device100 and the receivingdevice102 may be reversed, without loss of generality.

The callingdevice100 is capable of transmitting and receiving asignal110 via thetransceiver104. The callingdevice100 is connected to thebase station106 throughtransceiver104. The callingdevice100 is also capable of connecting to themeeting point server108 via thetransceiver104 or thebase station106. For a minimum level of service, full Internet access between thebase station106 and thecalling device100 is not necessary. In fact, audio communication between thebase station106 and thecalling device100 is sufficient, so that the central processing unit (CPU) and/or computing power of thecalling device100 can be kept to a minimum.

As shown inFIG. 1, the callingdevice100 may call the receivingdevice102 by sending asignal110 to receivingdevice102. Thesignal110 may be a short (one or two tone) ringing tone. Thesignal110 alerts the receivingdevice102 of a prospective communication with the callingdevice102. In one embodiment, the callingdevice100 notifies the receivingdevice102 of an intention to communicate by sending thesignal110 to the receivingdevice102 and hangs up, incurring no further airtime charges. In one embodiment, the callingdevice100 hangs up by disconnecting from thebase station106.

There are a number of devices and methods that can be used to transmit thesignal110. The callingdevice100 can send thesignal110 to the receivingdevice102 over the GSM network in the traditional manner. Thesignal110 can also be generated or broadcast by thetransceiver104 of thecalling device100. In an alternative embodiment the, thebase station106 can send thesignal110 to the receivingdevice102. In an alternative embodiment, themeeting point server108 can send thesignal110 to the receivingdevice102.

Thesignal110 could be a discrete multi-tone (DMT) signal, such as a discrete multi-tone signal having one or two tones. In one embodiment, thesignal110 includes information for the receivingdevice102 identifying the location, such as the address, of themeeting point server108. In another embodiment, thesignal110 includes information for themeeting point server108 identifying the phone number or the address of thecalling device100 or the receivingdevice102. In another embodiment, thesignal110 may include no other information at all.

In several embodiments, thesignal110 could be any analog or digital signal suitable for connecting thecalling device100 to thebase station106 or themeeting point server108, such as a spread-spectrum signal, a time-, frequency-, or code division multiplexed signal, or a combination thereof. In one embodiment, thesignal110 is a GSM signal. Thesignal110 may be directed to the receivingdevice102 using the phone number assigned to the receivingdevice102. In this case, thesignal110 may be the aforementioned two-tone discrete multi-tone signal, a short signal to notify the receivingdevice102 of a prospective or prospective communication.

After sending thesignal110, the callingdevice100 may, in general, hang up so that no further phone or airtime charges accrue. In one embodiment, the callingdevice100 hangs up by disconnecting from thebase station106. The callingdevice100 may then connect to the home meeting point channel of the receivingdevice102 inside themeeting point server108, and await the response of the receivingdevice102. There is no need for the receivingdevice102 to be connected constantly to thebase station106 or the Internet.

In one embodiment, the receivingdevice102 is capable of sending and receiving asignal112. Thesignal112 could be a discrete multi-tone signal, such as a discrete multi-tone signal having two tones. In the case of direct communication between the callingdevice100 and the receivingdevice102, thesignal112 could be thesignal110, albeit displaced in time or space. In one embodiment, thesignal112 includes information for thecalling device100 identifying the location, such as the address, of themeeting point server108. In another embodiment, thesignal112 includes information for themeeting point server108 identifying the phone number or the address of thecalling device100 or the receivingdevice102.

In several embodiments, thesignal112 could be any analog or digital signal suitable for connectingbase station106 ormeeting point server108 to receivingdevice102, such as a spread-spectrum signal, a time-, frequency-, or code division multiplexed signal, or a combination thereof. Thesignal112 could also be used for connecting the receivingdevice102 to themeeting point server108 via thetransceiver104 or thebase station106. In one embodiment, thesignal112 is a GSM signal.

The receivingdevice102 may not answer the call, or it may answer the call and hang up, to minimize charges for using airtime. In one embodiment, hanging up means disconnecting from thebase station106. The callingdevice100 may also hang up immediately after sending the short notification signal to receivingdevice102, also to minimize charges. Thesignal110, in particular, may alert receivingdevice102 of the prospective communication, without necessarily carrying out the communication itself. Thesignal110 may also impart identifying information of themeeting point server108.

The receivingdevice102, upon receiving thesignal110 from the callingdevice100, may connect to a meeting point channel on themeeting point server108. In one embodiment, the receivingdevice102 connects to themeeting point server108 through thebase station106. In another embodiment, the receivingdevice102 may connect to the meeting point channel on themeeting point server108 directly, such as over the Internet, and commence communication with the callingdevice100. After both thecalling device100 and the receivingdevice102 have connected to themeeting point server108, communication can commence using VoIP.

Themeeting point server108 is capable of supporting a communication connection between the callingdevice100 and the receivingdevice102. The connection may include thesignal110 alerting the receivingdevice102 of the prospective communication with the callingdevice100. In this case, the receivingdevice102 may form a connection with themeeting point server108 after receiving thesignal110.

The receivingdevice102, however, may not need to answer the call represented by the short, two-tone signal. Instead, thesignal110 itself may impart sufficient information for the receivingdevice102 to recognize the prospect of communication with the callingdevice100 at themeeting point server108. In the alternative, the receivingdevice102 may answer the call, but hang up immediately, thus minimizing airtime charges.

In one embodiment, hanging up may mean disconnecting from thebase station106. Therefore, an advantage of this embodiment is that the indirect communication system allows any mobile device to communicate to another device throughmeeting point server108, such as by Voice over Internet Protocol (VoIP), while avoiding the use of airtime.

Themeeting point server108 is also capable of supporting a connection between the callingdevice100 and a plurality of receivingdevices102, such as during a conference call. In this case, themeeting point server108 would copy each packet received from the callingdevice100 and redirect the copies to theindividual receiving devices102. Each of the receivingdevices102 would have formed a connection with themeeting point server108 after receiving theirrespective signals110.

The receivingdevices102 may not, however, have answered the call, or else, if they did answer it, they may have hung up immediately. Thus, each of the receivingdevices102 would hear the callingdevice100, but without incurring further airtime charges. Therefore, an advantage of the embodiment is that the indirect communication system allows thecalling device100 to communicate with a plurality of receivingdevices102 throughmeeting point server108, such as by Voice over Internet Protocol (VoIP), while avoiding the use of airtime.

Themeeting point server108 may be connected to other servers using thecommunication network114. In one embodiment, thecommunication network114 may be an Internet communication network. In another embodiment, thecommunication network114 may be an Intranet communication network, such as a company's proprietary network.

Themeeting point server108 may have an identifier, such as an IP address on thecommunication network114. The address could be a unique number having four or six parts, separated by dots, e.g. 165.113.223.2. The address can be used to identifymeeting point server108 uniquely on thecommunication network114. Themeeting point server108 may also have a domain name, such as www.pwt.com. The domain name may be convertible into an IP address by a domain name system.

In one embodiment, such as VoIP applications, themeeting point server108 may simply be a personal computer with an IP address such as 165.113.223.2, or a domain name system name such as a web site address (e.g. www.voip_mobilephone.com or www.pwt.com). In one embodiment, thebase station106 connecting thecalling device100 and/or the receivingdevice102 can also be used as themeeting point server108. Many meeting points (locations or channels) can be set up inside themeeting point server108 for thecalling device100 and the receivingdevice102 to meet and talk.

In one embodiment, the callingdevice100 may have aphone number 1111. The callingdevice100 places a call to the receivingdevice102, which may have aphone number 2222. The callingdevice100 calls the receivingdevice102 by sending thesignal110 in the form of a short ringing tone, possibly including thephone number 2222 of the receivingdevice102, to the receivingdevice102.

After sending thesignal110, the callingdevice100 connects to themeeting point server108, which may have an IP address such as 165.113.223.2. The connection with themeeting point server108 may be via theappropriate base station106. Themeeting point server108 may set up a communication channel with the receivingdevice102 on themeeting point server108 and direct thecalling device100 to that channel.

In one embodiment, the only information held in common by the callingdevice100, themeeting point server108, and the receivingdevice102 is the phone number of the receivingdevice102. In this embodiment, the meeting point channel on themeeting point server108 may have an address formed by combining the phone number of the receivingdevice102, i.e. 2222, with the IP address of themeeting point server108, i.e. 165.113.223.2. Thus, the address of the meeting point channel might be of the form 2222@165.113.223.2. Thenumber 2222 is derived from the number of the receivingdevice102, while the IP address 165.113.223.2 is derived from the address of themeeting point server108.

In one embodiment, the meeting point channel has been prearranged, and both the receivingdevice102 and thecalling device100 are aware of the address of the meeting point channel on themeeting point server108. In this embodiment, when the receivingdevice102 withnumber 2222 receives the short ringing tone, the receivingdevice102 will go to the predetermined, or default, meeting location represented by 2222@165.113.223.2, to commence communication with the callingdevice100. In this embodiment, the receiving device withnumber 2222 may own the channel represented by 2222@165.113.223.2, and ownership of meeting point channel is established thereby.

In another embodiment, the receivingdevice102 may only be aware of the IP address of themeeting point server108 along with, of course, its own phone number. In this embodiment, there may be a prearranged protocol between the callingdevice100 and areceiving device102 in which it is understood that sending thesignal110 to the receivingdevice102 indicates that there is a meeting point channel waiting on themeeting point server108. It may further be understood that the address of the meeting point channel will be formed from the phone number of the receivingdevice102 and the IP address of themeeting point server108.

In this embodiment, when the receivingdevice102 with aphone number 2222 receives the short ringing tone, the receivingdevice102 will perform home calling. In this embodiment, the receivingdevice102 will go to themeeting point server108, where themeeting point server108 will transfer the receivingdevice102 to its home meeting point channel represented by 2222@165.113.223.2. The receivingdevice102 will then commence communication with the callingdevice100. Thus, the receivingdevice102 will be able decipher the address of the meeting point channel from its own phone number and an address of themeeting point server108.

In yet another embodiment, thesignal110 may include tones representative of the address of the meeting point channel on themeeting point server108. In this embodiment, the receivingdevice102 may be unaware of the address of themeeting point server108. In this embodiment, rather, the receivingdevice102 may be able to interpret the tones of thesignal110 to decipher the address of the meeting point channel on themeeting point server108.

It may be possible, furthermore, for the receivingdevice102 to decipher the address of the meeting point channel without answering the call represented by thesignal110. This may be the case if, for example, the receivingdevice102 has “caller ID,” or an analogous function in which the telephone number or other information of thecalling device100 are represented on a display of the receivingdevice102. In the alternative, the receivingdevice102 may answer thesignal110, and remain connected to thecalling device100 via thesignal110 long enough to receive the information representing the address of the meeting point channel on themeeting point server108, after which thereceiving device102 will hang up.

The callingdevice100 may need to know the number of the receivingdevice102, and both thecalling device100 and the receivingdevice102 may need to know the corresponding IP address of the gateway or themeeting point server108. The callingdevice100 can make the calls by a click of the “VoIP Call” button. For the receivingdevice102, a “VoIP Accept” button will be used to receive the call.

In one embodiment, the calling format used with a dedicated mobile phone handset, or a mobile phone with a built-in function to store the gateway (or MPS) IP address, is the number of the receiving device, such as 2222. In this embodiment, pressing, for example, a “VoIP Call” button calls the number of the receiving device. There is no need to type in the IP address explicitly since the IP address is stored inside the phone. The indirect meeting point channel (IMPC), such as 2222@165.113.223.2, can be established automatically after the short ringing tone. Therefore, only the receiving device number is needed to be known by the user.

In one embodiment, a calling format for a mobile phone without a built-in function to store the gateway IP address may be 2222@165.113.223.2. After pressing the “VoIP Call” button, the system will send a short ringing tone to the receivingdevice number 2222 and set up the indirect meeting point channel as 2222@165.113.223.2.

In one embodiment, the channel 2222@165.113.223.2 may be entered as two separate items. The number of the receivingdevice102, e.g. 2222, is entered in the number field. The IP address, such as 165.113.223.2, is entered in, e.g. the gateway field. This calling format can also be used when the gateway IP address is somewhere on the Internet, and is different from the default IP address, e.g. 165.113.223.2. In this case, a transfer function from the gateway IP to the default IP address may be provided.

Mobile phone calls can also be made when no default gateway or default IP address is available at all. Instead, thebase station106 or any PC with VoIP on the Internet can be used as themeeting point server108. In this case, the callingdevice100 should have the ability to send a short ringing tone and transmit the meeting point IP address to the receivingdevice102. This allows an indirect meeting point channel to be established without the involvement of a default gateway.

Note that by having a default gateway such as themeeting point server108, the short signal (or ringing tone) can be sent by the gateway promptly and uniquely. Without a default gateway, the callingdevice100 would need to send the meeting point information to the receivingdevice102, although the software inside the mobile phone can program this.

After thecalling device100 sends thesignal110 to the receivingdevice102 indicating that a meeting point channel has been established on themeeting point server108, the callingdevice100 connects to the meeting point channel as well.

In one embodiment, a meeting point channel and a gateway is dedicated on the server. In this embodiment, the callingdevice100 connects to the server and the server sends thesignal110 to the receivingdevice102 indicating that a meeting point channel has been established on themeeting point server108. In one embodiment, the callingdevice100 will be transferred to the meeting point channel address. The meeting point channel address may be in the form of the phone number of the receivingdevice102 and an address of themeeting point server108, as discussed above. In one embodiment, themeeting point server108 may provide music or other entertainment for attendees of the meeting while they wait for the other attendees to arrive.

After receiving thesignal110, the receivingdevice102 will connect with the meeting point channel at themeeting point server108 as well, in order to communicate with the callingdevice100. If the receivingdevice102 arrives at the meeting point channel before thecalling device100, the receivingdevice102 may wait for thecalling device100. In one embodiment, the meeting point channel will be “owned” by the receivingdevice102. This embodiment establishes ownership of the meeting point channel and may offer better control and avoid confusion.

In one embodiment, the callingdevice100 or the receivingdevice102 may set up the meeting point channel on themeeting point server108 by calling its own number. In this embodiment, themeeting point server108 will set up a meeting point channel with an address in the form of the phone number of thecalling device100 or the receivingdevice102 combined with an address of themeeting point server108 itself. Setting up a meeting point channel by calling its own phone number may be referred to as “home calling.” In one embodiment, the number dialed by the callingdevice100 or the receivingdevice102 includes a prefix and an extension.

In one embodiment, home calling is operable both nationally and internationally, thus circumventing barriers posed by incompatible methods of caller ID transmission. In one embodiment, home calling dispenses with the need for alternative notification methods, such as short message service (SMS) messages. In one embodiment home calling is operable for acalling device100 served by a communication network that is incompatible with that serving receivingdevice102. In this embodiment, for example, thesignal110 will indicate to the receivingdevice102 that someone is waiting to talk even if the receivingdevice102 is on a network that is incompatible with the callingdevice100.

In one embodiment, after sending thesignal110, the callingdevice100 and the receivingdevice102 agree on a fixed meeting point channel on themeeting point server108. An address of the fixed meeting point channel may have a specific format, such as a number at the IP address of themeeting point server108. In one embodiment, every prospective participant of the call must be aware of the address of the fixed meeting point channel.

In another embodiment, after sending thesignal110, themeeting point server108 may arrange for both thecalling device100 and areceiving device102 to connect to an unoccupied meeting point channel. In this embodiment, themeeting point server108 can transfer thecalling device102 to the unoccupied meeting point channel when the callingdevice102 contacts themeeting point server108. For this embodiment, the meeting point server may need to know an identification number of the receivingdevice102, such as the phone number of the receivingdevice102, so that themeeting point server108 can also transfer the receivingdevice102 to the correct meeting point channel where thecalling device100 is waiting.

In another embodiment, a substitution number is associated with each number registered to themeeting point server108. In this embodiment, after sending thesignal110, a meeting point channel is generated using the substitution number for the number of the receivingdevice102. After receiving thesignal110, the receivingdevice102 calls the substitution number to meet thecalling device100 and communicate. In this embodiment, each device will need to be aware of two numbers, the substitution number and its own phone number.

In one embodiment, the owner of the meeting point channel, i.e., the receivingdevice102, may have the right to close the meeting point channel at any time. In another embodiment, the owner of the meeting point channel, i.e. the receivingdevice102, may be allowed to ask all other devices connected to the meeting point channel to hang up.

In the alternative, the receivingdevice102 may decline the communication, in which case no further communication takes place between callingdevice100 and receivingdevice102. In a further alternative, receivingdevice102 could respond by counter-offering an alternate meeting point channel, connecting thereto and awaiting the response of callingdevice100. If callingdevice100 accepts the counter-offer, and connects to the alternate meeting point channel, communication commences with receivingdevice102 as well.

Thetransceiver104,base station106, ormeeting point server108 are all capable of transmitting thesignal110 received by receivingdevice102. Thesignal110 may be a ringing tone generated by a GSM network, or it may be generated by the base station to which thecalling device100 is currently tethered, a computer, a public switched telephone network gateway, a modem, or a switch box for use with the public switched telephone network.

If themeeting point server108 is used to generate the short signal ringing tone, the ringing tone can also be generated with a public switched telephone network gateway, a modem, or a switch box for use with the public switched telephone network. Finally, the short signal ringing tone can be generated by a transceiver or an antenna associated with the indirect communication system.

As shown inFIG. 2, themeeting point server206 included with the indirect communication system may include agenerator214, asender216, ameeting point creator218, ameeting point channel220, and aredirector222. Thegenerator214 generates asignal212 in response to an instruction from acalling device200. The generatedsignal212 is a two-ring ring tone or a short signal. Thesender216 is a notifier notifying a receivingdevice202, which may be a mobile phone, of a prospective communication in response to an instruction from acalling device200, which may also be a mobile phone. If thecalling device200 is a mobile phone, the callingdevice200 may reduce airtime charges by using a generated signal to alert thereceiving device202 of a prospective communication, but conducting the actual communication elsewhere.

Themeeting point creator218 generates themeeting point channel220 in response to the instruction from callingdevice200. Themeeting point channel220 may be created after thecalling device200 has established connection with the meeting point server208. The establishment ofmeeting point channel220 on the server enables signal210 from the callingdevice200 and signal212 from the receivingdevice202 to meet atmeeting point channel220 and form a communication path between the callingdevice200 and the receivingdevice202 through themeeting point channel220.

The communication, however, may not be directly from callingdevice200 to receivingdevice202. Callingdevice200 and receivingdevice202, rather, each communicate separately withmeeting point channel220, andmeeting point channel220 redirects their respective communications to the appropriate destinations. Therefore, airtime minutes may be reduced by communicating throughmeeting point channel220, such as over the Internet using VoIP, rather than over the air.

Themeeting point channel220 may include aredirector222. The redirector is capable of receiving converted Voice over Internet packets from the callingdevice200 and redirecting the Voice over Internet packets to the receivingdevice202, and vice versa. The Voice over Internet packets are sent directly to themeeting point channel220 from either thecalling device200 or the receivingdevice202. The VoIP packets are then redirected to the destination device by changing the destination address on packet to the address of either thecalling device200 or receivingdevice202, as appropriate. The roles of thecalling device200 and the receivingdevice202 may be reversed, without loss of generality.

In another embodiment, as shown inFIG. 3A, an indirect communication system may include ameeting point server308a, which is capable of receiving a communication from acalling device300aor areceiving device302aviabase stations306aand307a. Either the callingdevice300aor the receivingdevice302a, or both, may be a mobile phone.

The callingdevice300amay have aphone number 1111. The callingdevice300aplaces a call to the receivingdevice302a, which may have aphone number 2222. In one embodiment, the callingdevice300acalls the receivingdevice302aby sending thesignal312ain the form of a short ringing tone, thesignal312amay include no information or no instructions such as a caller ID of thecalling device300a.

After sending thesignal312a, the callingdevice300aconnects to themeeting point server308a, which may have an IP address such as 165.113.223.2. The connection with themeeting point server308amay be via theappropriate base station306a. In this embodiment, themeeting point server308amay set up a communication channel with the receivingdevice302adynamically and putting the calling device in that channel waiting for the receivingdevice302a. The meeting point channel may be 2222@165.113.223.2, where thefirst number 2222, in this case, may be used to identify the receiving device. In the case of no information available from thesignal312a, the number of the receiving device can be used to complete the connection.

After thereceiving device302awith aphone number 2222 receives the short ringing tone, the receivingdevice302amay make a call with its own number such as 2222@165.113.223.2. By direct dialing this call using the receiving device will connect the receiving device to themeeting point server308aand transfer to the meeting point channel 2222@165.113.223.2, to commence communication with the callingdevice300a. Dialing its own number is called home calling. In this embodiment, the receivingdevice302ais just like to go home and meeting someone.

In another embodiment, the callingdevice300amaking a call to the receiving device by a direct dialing 2222@165.113.223.2. This action connects the calling device to themeeting point server308aby identifying the IP address 165.113.223.2. Theserver308amay then send thesignal312ato the receivingdevice302awithnumber 2222. After sending the signal, theserver308agenerates the meeting point 2222@165.113.223.2 and put the receiving device into this channel waiting for the receiving device to make a home calling.

Alternatively and depending on the network of thebase station307a, the callingdevice300amay capture the voice data and converts it to an “Outgoing VoIP Packet”. In this embodiment, the job of thebase station307ais just passing the packet to the meeting point channel inside the meeting point server.

In another embodiment, when both calling and receiving device have themeeting point server308aIP address stored as parameter or built-in function, the operation of home calling is the same as dialing its own number on the device.

In another embodiment, thereceiving device 2222 may own the meeting point channel 2222@165.113.223.2 inside theserver308a. Establishing ownership of meeting point channel may allow the owner to perform administration work such as close the meeting point channel at any time forcing people inside the channel to hang up.

In another embodiment, as shown inFIG. 3B, an indirect communication system may include ameeting point server308, which is capable of receiving a communication from acalling device300 or areceiving device302 viabase stations306 and307. Either the callingdevice300 or the receivingdevice302, or both, may be a mobile phone.

Both thecalling device300 and areceiving device302 may connect to themeeting point server308 after asignal312 is sent by the callingdevice300 to the receivingdevice302. In this embodiment, thesignal312 may include information or instructions such as a caller ID of thecalling device300, an address of themeeting point server308 or an alternate meeting point, or a callback number.

After thecalling device300 and the receivingdevice302 are connected to themeeting point server308, the callingdevice300 and areceiving device302 may begin sending information meant for their opposite party to themeeting point server308. Themeeting point server308 may then redirect the communication to therespective calling device300 or receivingdevice302. Therefore, airtime minutes may be reduced by enabling both callingdevice300 and receivingdevice302 to communicate with each other using VoIP, throughmeeting point server308, thereby lowering the cost of communicating and increasing the quality of phone communication.

In one embodiment, redirection works as follows. The callingdevice300 sends a short ringing tone to the receivingdevice302, and connects to thebase station306. Thebase station306 and may have an IP address such as BS1_IP. The details of the address BS1_IP may be known by acalling device300 when the callingdevice300 connects to thebase station306. After receiving the short ringing tone, the receivingdevice302 connects to thebase station307. Thebase station307 may have an IP address such as BS2_IP.

Themeeting point server308 may be located on the Internet at an IP address such as 165.113.223.2. The IP address of themeeting point server308 may be known to thecalling device300, or thebase station306, or both. The callingdevice300 connects to thebase station306 with the IP address BS1_IP. Thebase station306 with the IP address BS1_IP captures the voice data from the callingdevice300 and converts it to an “Outgoing VoIP Packet”. The outgoing IP packet has a header, according to which the outgoing IP packet is being sent from thebase station306 at the IP address BS1_IP to the address of the meeting point server308 (i.e. 165.113.223.2). Thebase station306 at the IP address BS1_IP sends this packet to themeeting point server308.

When the outgoing packet from thebase station306 at the IP address BS1_IP arrives at themeeting point server308, themeeting point server308 changes the destination address in the header of the IP packet. Themeeting point server308 changes the destination address from 165.113.223.2, which is the address of themeeting point server308, to BS2_IP, which is the IP address of thebase station307 associated with receivingdevice302. Themeeting point server308 then sends the IP packet to thebase station307.

When thebase station307 with the address BS2_IP receives the packet, it will consider it to be an incoming VoIP packet and pass the voice content to the receivingdevice302. In this way, communication from the callingdevice300 to the receivingdevice302 is established. Similarly, communication can be established from the receivingdevice302 to thecalling device300, i.e. in the reverse direction, by changing the destination address of each IP packet from 165.113.223.2, the address of themeeting point server308, to BS1_IP, the IP address of thebase station306 associated with callingdevice300. The roles of thecalling device300 and the receivingdevice302 may be reversed, without loss of generality.

As shown inFIG. 4, themeeting point server408 included with the indirect communication system may include agenerator414, asender416, ameeting point creator418, ameeting point channel420, and aredirector422. Thegenerator414 generates a signal in response to an instruction from a calling device. The generated signal is a two-ring ring tone or a short signal. Thesender416 is a notifier notifying a receiving device of a prospective communication in response to an instruction from a calling device. Therefore, if the calling device is a mobile phone, then the calling device will reduce airtime charges by using a generated signal to alert the receiving device of a prospective communication.

Themeeting point creator418 generates themeeting point channel420 in response to the instruction from the calling device. Themeeting point channel420 may be created after the calling device has established connection with themeeting point server408. The establishment ofmeeting point channel420 on themeeting point server408 enables the calling device and the receiving device to meet at themeeting point channel420 and communicate with each other, without using further airtime.

InFIG. 5, there is shown abase station506 included in an indirect communication system that may also include acalling device500, which may be a mobile phone, and areceiving device502, which may also be a mobile phone, as well as other devices. Thebase station506 may be a computer with a transceiver, and a connection to either callingdevice500 or receivingdevice502, and is equipped with VoIP capability, a public switched telephone network gateway, a modem, and/or a switch box for connection to the public switched telephone network. Thebase station506 is capable of transmitting asignal512 upon receiving instructions from the callingdevice500. Thesignal512 is capable of notifying the receivingdevice502 of a prospective communication. The roles of thecalling device500 and the receivingdevice502 may be reversed, without loss of generality.

InFIG. 6, there is shown atransceiver604 included in an indirect communication system that may also include acalling device600, which may be a mobile phone, and areceiving device602, which may also be a mobile phone, as well as, other devices. Thetransceiver604, represented by an antenna, is capable of transmitting asignal612 upon instructions from the callingdevice600. Thesignal612 is capable of notifying the receivingdevice602 of a prospective communication via broadcast. The roles of thecalling device600 and the receivingdevice602 may be reversed, without loss of generality.

InFIG. 7, there is shown ameeting point server708 included in an indirect communication system that may also include acalling device700, which may be a mobile phone, and areceiving device702, which may also be a mobile phone, as well as other devices. Themeeting point server708 is for example a computer on the Internet, having an address or a domain name, or a base station. The address may be fixed to avoid confusing it with an address of a base station. In the alternative, the domain name of themeeting point server708 could be kept constant, while the address is allowed to change.

Themeeting point server708 may also be equipped with a public switched telephone network gateway, a modem, and/or a switch box related to themeeting point server708. Themeeting point server708 is capable of transmitting thesignal712. Thesignal712 is capable of notifying the receivingdevice702 of a prospective communication. Themeeting point server708 re-directs packets sent to it from the callingdevice700 to the receivingdevice702, and vice versa. The roles of thecalling device700 and the receivingdevice702 may be reversed, without loss of generality.

InFIG. 8, there is shown acalling device800 included in an indirect communication system that may also include a receivingdevice802, which may be a mobile phone, as well as other devices. The callingdevice800 can generate asignal812. The generatedsignal812 is received via a Global Systems for Mobile Communication (GSM) network. Callingdevice800 could be provided with hardware or software for transmitting the short, two ring, signal, connecting to the Internet, and setting up a meeting point channel, either directly or through a base station or the public switched telephone network.

The software could be downloaded to thecalling device800 and areceiving device802, which may be also be a mobile phone, over the cellular network. In this case the callingdevice800 and the receivingdevice802 may be programmable and controllable by a third-party to download the software. The software may include a menu, an interface, radio boxes, check boxes, and option press buttons. The callingdevice800 and receivingdevice802 may also have a switch to switch to the meeting point channel after sending the short, two-tone signal over the cellular network.

The callingdevice800 and the receivingdevice802 may have a built-in function to store the address of the meeting point server, such as a default gateway. In that case there would be no need to type the address explicitly. Only the phone number of the receivingdevice802 would be necessary in order to form the address of the meeting point server. The roles of thecalling device800 and the receivingdevice802 may be reversed, without loss of generality.

As shown inFIG. 9, themeeting point server908 includes ameeting point channel920. A callingdevice900, which may be a mobile phone, calls themeeting point server908 to set up a call to a receiving device, which may also be a mobile phone. Themeeting point server908 may have a plurality ofmeeting point channels920 for multiple communications. Themeeting point channel920 is identified by an address of a receiving device and either an Internet Protocol address or a Domain Name System name. A typicalmeeting point channel920 identification channel may be in the form of an email address.

If the phone number of a receiving device is 22222 and either the Internet Protocol address is 165.113.223.2 or the Domain Name System name is www.mps_VoIP.com, then the channel location may be 22222@165.113.223.2 or 22222@www.mps_VoIP.com. Therefore, a receiving device would have the information necessary to connect to thechannel920 after connecting to themeeting point server908, which would then complete the call to thecalling device900.

InFIG. 10, there is shown ameeting point server1008 having ameeting point channel1020. Acalling device1000, which may be a mobile phone, and areceiving device1002, which may also be a mobile phone, meet in themeeting point channel1020, after themeeting point channel1020 is created in themeeting point server1008. The roles of thecalling device1000 and thereceiving device1002 may be reversed, without loss of generality.

InFIG. 11, there is shown a meeting point server1108 including a meeting point creator1118 and an alternate meeting point channel1120. The alternate meeting point channel1120 is created when a receiving device1102 selects “alternative meeting point location”. The meeting point creator1118 creates the alternate meeting point channel1120. Sometimes, the alternative meeting point channel1120 may be in another meeting point server somewhere on the Internet.

The alternative meeting point channel1120 receives a connection from a calling device1100, which may be a mobile phone, and a receiving device1102, which may also be a mobile phone. Therefore, an advantage of the alternative meeting point channel1120 is that a communication can be established at any channel in the meeting point server1108. The roles of the calling device1100 and the receiving device1102 may be reversed, without loss of generality.

In another embodiment, shown inFIG. 12, an indirect communication system includes a dedicatedmeeting point server1208. Themeeting point server1208 is capable of receiving an instruction from apersonal computer1200 with VoIP capability. The instructions received include the number of areceiving device1202, which may be a mobile phone, and an Internet Protocol address, for example 88.169.11.1, in a gateway field. By having a dedicatedmeeting point server1208, themeeting point server1208 is capable of transmitting a two-ring ring tone orshort signal1212.

Thecomputer1200 may then wait for thereceiving device1202 to connect to themeeting point channel1220 in themeeting point server1208. Themeeting point server1208 is also capable of receiving a connection from thereceiving device1202, via abase station1206. Thebase station1206 is a nearest base station to thereceiving device1202. Thecomputer1200 will thus be able to communicate with another mobile phone using VoIP, without actual knowledge of where the receiving device is located.

In another embodiment, shown inFIG. 13, an indirect communication system includes ameeting point server1308. Themeeting point server1308 is capable of receiving an instruction from thecalling device1300, which may be a mobile phone, via abase station1306 instructing themeeting point server1308 to connect to acomputer1302 with VoIP capability. The instruction includes an address of thecomputer1302, and an address ofmeeting point server1308. Themeeting point server1308 is capable of having ameeting point channel1320 identified by the address of thecomputer1302 and the address of themeeting point server1308.

If, for example, an address of thecomputer1302 is 66.168.100.2, and an address of themeeting point server1308 is 250.19.2.10, the address of the meeting point channel might be 66.168.100.2@250.19.2.10. In one embodiment, thecomputer1302 is capable of being a meeting point as well. In this case thecalling device1300 would enter an address of the receivingcomputer1302, allowing thecalling device1300 to directly connect, via a base station, to thecomputer1302.

A PC with broadband and VoIP may be called from thecalling device1300 as well. In the case of a direct VoIP call, the IP address of the receivingcomputer1302, such as 66.168.100.2, would be entered at thecalling device1300. In this case, the meeting point is on the receiving computer1302 (i.e. 66.168.100.2).

Alternatively, in the case of calling via themeeting point server1308, the IP address of the receivingcomputer1302, such as 66.168.100.2, or the IP address of themeeting point server1308, such as 165.113.223.2, could be entered. In another embodiment, the IP address of themeeting point server1308 can be a dedicated MPS or any other PC with VoIP. Also, from an application point of view, a PC with VoIP is equivalent to a SIP phone, so that the communication format in this section can also apply to an SIP phone.

In another embodiment, shown inFIG. 14, an indirect communication system uses ameeting point server1408 to establish a connection between the callingcomputer1400 withmodem1401 and areceiving device1402, which may be a mobile phone. Themeeting point server1408 receives an instruction from the callingcomputer1400, which has a modem, notifying thereceiving device1402 of a prospective communication. The instructions include the phone number of thereceiving device1402 and an address of themeeting point server1408.

Themeeting point server1408 transmits a generatedsignal1412 to thereceiving device1402. Themeeting point server1408 creates ameeting point channel1420 based upon the phone number of thereceiving device1402 and the address of themeeting point server1408. The callingcomputer1400 waits for thereceiving device1402 to connect to themeeting point server1408 after establishing connection to themeeting point server1408. Themeeting point server1408 is capable of receiving VoIP packets directed to themeeting point server1408 from the callingcomputer1400, and redirecting the VoIP packets to thereceiving device1402. Therefore, the system allows a mobile phone to communicate with another device over the Internet, while saving money and having quality phone calls.

In one embodiment, a mobile phone may be called from a PC, which may have broadband and VoIP. In this embodiment, the VoIP client (software) is activated, and the number of the receiving device, such as 2222, is entered, along with the IP address of the meeting point server (MPS), such as 88.192.168.11.1. Note that many VoIP software clients specified by the ITU H.323 standard should contain fields for the phone number and the gateway address. If the MPS is a dedicated MPS, the MPS can generate the short ringing tone and wait for connection from the receiving device.

In another embodiment, shown inFIG. 15, an indirect communication system includes ameeting point server1508 capable of transmitting asignal1512 and creating ameeting point channel1520. Thesignal1512 is generated when themeeting point server1508 receives an instruction from acalling device1500, which may be a mobile phone, via abase station1506. The instruction includes the phone number of the receivingcomputer1502, which has amodem1501, and the address of themeeting point server1508.

Themeeting point server1508 sends the generated signal to the receivingcomputer1502. Themeeting point channel1520, in themeeting point server1508, is capable of receiving VoIP packets from thebase station1506. Thebase station1506 converts voice data, received from thecalling device1500, into VoIP packets. Themeeting point server1508 is capable of redirecting the VoIP packets, which were directed to themeeting point server1508, to the receivingcomputer1502 withmodem1501.

In another embodiment, shown inFIG. 16, an indirect communication system includes ameeting point server1608 including aPSTN gateway1630. Themeeting point server1608 is capable of receiving a communication from a calling device, such as aphone1600 using a public switched telephone network line via thePSTN gateway1630. Themeeting point server1608 is also capable of receiving a communication from areceiving device1602, which may be a mobile phone, via abase station1608. Themeeting point server1608 is also capable of transmitting a signal to thereceiving device1602 from thephone1600 using the public switched telephone network line via thePSTN gateway1630, upon receiving instructions from thephone1600. The instruction includes a phone number of thereceiving device1602 and an address of themeeting point server1608.

Themeeting point server1608 creates ameeting point channel1620. The phone number of thereceiving device1602 and the address of themeeting point server1608 are combined to identify themeeting point channel1620. Themeeting point channel1620 is capable of receiving VoIP packets, which were previously converted at thePSTN gateway1630 when received from the calling device using a PSTN line1601. Themeeting point channel1620 is capable of redirecting the VoIP packets to thenearest base station1606, and from thebase station1606 to thereceiving device1602. Therefore, thephone1600 using a public switched telephone network line can call thereceiving device1602, thereby allowing the mobile phone to incur low cost of communication and receive a quality phone call.

In one embodiment, a personal computer (PC) connected to a public switched telephone network line (ordinary phone line) with, for example, a modem can be used to make Internet connections through a dial up network. In this embodiment, the PC will dial a number to an Internet Service Provider (ISP) through a modem. The ISP would provide Internet access to the PC via the public switched telephone network line. Once connected to the Internet, a VoIP software client can be used to make a call to a mobile phone. The process is the same as calling from a PC (with broadband and VoIP) to a mobile phone.

In another embodiment, a computer connected to a public switched telephone network line with dial up network may be called from a mobile phone. First, the mobile phone makes a calling format such as 123456@165.113.223.2, where 123456 is the public switched telephone network phone number. The MPS sends a short signal to the modem and hangs up. The modem together with a specific software will activate the PC to connect to the Internet and the MPS, making the VoIP conversation possible.

In another embodiment, a mobile phone may be called from a standalone public switched telephone network line, such as a public switched telephone network line with no direct Internet access. In this embodiment, a public switched telephone network gateway may be installed in the MPS. If, for example, the telephone number for the public switched telephone network gateway is 464530, and the mobile phone number e.g. 2222, the first number can be used to form the connection between the phone 123456 and the public switched telephone network gateway inside MPS (i.e. 464530). Once connected to the MPS, the MPS can generate a short signal to mobile phone and making the final connection with the mobile phone by creating the meeting point channel 2222@165.113.223.2.

In another embodiment, a standalone public switched telephone network line, without direct Internet, may be called from a mobile phone. In this embodiment, a public switched telephone network gateway may be installed in the MPS with number 464530. A mobile phone (no. 2222) can make a call to a standalone public switched telephone network phone 123456 through the MPS and the public switched telephone network gateway. First, the number of the standalone public switched telephone network e.g. 123456, is entered, and a “PSTN Call” button, or similar option, is pressed. The mobile phone will connect to the MPS and organize a meeting point channel such as 2222@165.113.223.2. By entering the number 123456 and pressing the “PSTN Call”, the mobile phone will instruct the MPS and the public switched telephone network gateway to dial out the number 123456.

In another embodiment, shown inFIG. 17, an indirect communication system includes ameeting point server1708 with a temporarymeeting point channel1720. Themeeting point server1708 is connected to aphone1702 over aPSTN gateway1730 and aPSTN line1712. Themeeting point server1708 is capable of supporting a connection between acalling device1700, which may be a mobile phone, via abase station1706, and thephone1702 using thePSTN line1712.

Themeeting point server1708 generates a signal to send to thephone1702, after receiving an instruction from thecalling device1700 via thebase station1706. The instruction includes an address of themeeting point channel1720 in the form of a combination of a phone number of thephone1702 and the address of themeeting point server1708. Themeeting point channel1720 is able to receive VoIP packets, which were previously converted from voice data at thebase station1706 when received from thecalling device1700. Themeeting point channel1720 is also capable of redirecting the VoIP packets to thePSTN gateway1730. ThePSTN gateway1730 uses VoIP software to convert the packets to voice data and transmit them to thephone1702.

In another embodiment, shown inFIG. 18, an indirect communication system includes ameeting point server1808 capable of receiving outgoing VoIP packets and redirecting the outgoing VoIP packets. The received outgoing VoIP packets are received from abase station1806 of acalling device1800, which may be a mobile phone. The receiving outgoing VoIP packets include an IP header. The IP header includes a delivery address and a source address. The delivery address is an address of themeeting point server1608. The source address is an address of thebase station1806 of thecalling device1800.

Themeeting point server1808 redirects the packets tobase station1807 of thereceiving device1802 by changing the delivery address from the address of themeeting point server1808 to the address of thebase station1807 of areceiving device1802, which may also be a mobile phone. Themeeting point server1808 also changes the source address from the address of thebase station1806 of thecalling device1800 to the address of themeeting point server1808. This embodiment allows a mobile phone to communicate with any device using the Internet. The roles of thecalling device1800 and thereceiving device1802 may be reversed, without loss of generality.

InFIG. 19, there is shown a process chart of an indirect communication method. Inoperation1900, the process begins. Inoperation1902, a signal is sent to a receiving device notifying the receiving device of a prospective. Inoperation1904, a calling device connects to a meeting point server. Inoperation1906, the meeting point server generates an indirect meeting point channel. Inoperation1908, a receiving device connects to the indirect meeting point server. Inoperation1910, packets received from the calling device are redirected to the receiving device at the meeting point channel. Inoperation1912, the process ends.

InFIG. 20, there is shown a process chart of address generation for use with an embodiment of the indirect communication method. Inoperation2000, the process begins. Inoperation2002, a public switched telephone network number of a meeting point server is entered. Inoperation2004, a number of a mobile device is entered. Inoperation2006, the meeting point server receives the number of the mobile device. Inoperation2008, the meeting point server generates a signal including a short, two-ring tone, an address of the server, and the number of the mobile phone. Inoperation2010, the mobile receiving device receives the signal. Inoperation2012, the mobile receiving device connects to the meeting point server. Inoperation2014, the meeting point server redirects packets received from the calling device to the receiving device. Inoperation2016, the process ends.

InFIG. 21, there is shown a process of packet redirection for use with an embodiment of the indirect communication method. Inoperation2100, the process begins. Inoperation2102, a meeting point server receives incoming packets from a calling device. Inoperation2104, the meeting point server converts the incoming packets to outgoing packets by replacing a delivery address with an address of a receiving device and replacing a source address with an address of the meeting point server. Inoperation2106, the meeting point server sends the outgoing packets received from the calling device to the receiving device. Inoperation2108, the process ends.

InFIG. 22, there is shown a process of setting up a meeting point channel for use with an embodiment of the indirect communication method. Inoperation2200, the process begins. Inoperation2202, a meeting point server receives a number of a receiving device and a VoIP call. Inoperation2204, the meeting point server sets up a meeting point channel. Inoperation2208, the meeting point server an address to the meeting point channel composed of the number of the receiving device and an address of the meeting point server. Inoperation2210, the process ends.

InFIG. 23, there is shown a process of setting up a telephone call for use with an embodiment of the indirect communication method. Inoperation2300, the process begins. Inoperation2302, a VoIP call button is pressed on a calling device. Inoperation2303, the calling device connects to a server. Inoperation2304, the calling device sends a signal to a receiving device. Inoperation2306, unless the receiving device is busy, the receiving device either declines the call, accepts the call, or counter-offers an alternate meeting point. Inoperation2308, the receiving device declines. Inoperation2310, the receiving device accepts, and connects to a meeting point server. Inoperation2312, the receiving device counter-offers an alternate meeting point, and connects to the alternate meeting point. Inoperation2314, the decline message ofoperation2308 is sent to the meeting point server. Inoperation2316, the process ends.

InFIG. 24, there is shown ameeting point server2408 capable of supporting a connection betweencalling device2400 and a plurality of receivingdevices2402, such as during a conference call. In this case, themeeting point server2408 would copy each packet received from callingdevice2400 inside ameeting point channel2420 and redirect the copies toindividual receiving devices2402 connected to themeeting point channel2420.

Each of the receivingdevices2402 would have formed a connection withmeeting point server2408 after receiving the short, two-tone signal, but without answering the call represented by the short, two-tone signal, or else hanging up immediately. Thus, each of the receivingdevices2402 would hear thecalling device2400. Mobile phones can join the conference call even when the conference call is already in progress. This can be done by making a connection with the meeting point channel or the hosting mobile phone. In a normal situation, when the meeting point channel is “2222@88.168.11.1,” the hosting mobile phone number is 2222. Therefore, an advantage of the embodiment is that the indirect communication system allows any mobile device to communicate to with a plurality of devices throughmeeting point server2408, such as by Voice over Internet Protocol (VoIP), while avoiding the use of airtime.

InFIG. 25, there is shown ameeting point server2508 capable of supporting a connection between a plurality of callingdevices2500 and a plurality of receivingdevices2502, such as during a conference call. In this case, themeeting point server2508 would copy each packet received from each of thecalling devices2500 inside ameeting point channel2520 and redirect the copies toindividual receiving devices2502 at themeeting point channels2520.Meeting point server2508 could further support a plurality ofmeeting point channels2520. Each of the plurality ofmeeting point channels2520 could support, in turn, a plurality of callingdevices2500 or receivingdevices2502. Callingdevices2500 and receivingdevices2502 may be similar functionally, differing only in the current direction of communication from or to themeeting point server2508.

Each of the receivingdevices2502 may have formed a connection withmeeting point server2508 after receiving the short, two-tone signal, but without answering the call represented by the short, two-tone signal, or else hanging up immediately. Thus, each of the receivingdevices2502 would hear each of thecalling devices2500. Therefore, an advantage of the embodiment is that the indirect communication system allows any mobile device to communicate with a plurality of devices throughmeeting point server2508, such as by Voice over Internet Protocol (VoIP), while avoiding the use of airtime.

In one embodiment, the indirect communication system is implemented by manufacturing dedicated hardware mobile phones. In this way, the following new functions can be added along with the existing mobile features: transmitting and receiving compatible RF with wireless media such as WiMAX and connecting to a base station; generating an indirect ringing tone to receiving devices (mobile phones); setting up the Meeting Point Channel on the Internet with VoIP (e.g. a meeting point server); and communicating with the receiving device with VoIP.

By developing the dedicated mobile phone, full access and control of menu, interfaces including options, radio boxes, check boxes, and push button can be obtained. In this embodiment, the mobile phone circuit design may contain the hardware, such as a chipset.

In another embodiment, the indirect communication system is implemented by downloading software to a mobile phone, such as via the wireless media. Such a mobile phone may be a programmable mobile phone, which is controllable by a third party. The downloadable software may include a menu, an interface, radio boxes, check boxes, and option press buttons. The mobile phone may have the ability to generate or switch to the compatible RF with the wireless media connecting to the BS in order to communicate with the BS. Software for the mobile phones may be upgraded with new features, and additional functions may be added. In one embodiment, the indirect communication system could be implemented purely by software. In other embodiments, in addition to the wireless download, the download mechanism to mobile phones can also be a CD via a PC, direct or indirect memory card and stick, Internet Web Site, and others.

In another embodiment, an add-on device may be added to existing mobile phones, i.e. a two-way or Walkie-Talkie style phone, to implement the indirect communication system. In order to reach a wider range of mobile phone users, an add-on (or plug-in) hardware to be added at the bottom of the mobile phone may be provided. For this implementation, the add-on device turns the existing mobile phone into a “Two-way Walkie-Talkie” type. That is, the add-on device captures the voice at the mobile phone and transmits the signal to the BS via the wireless media. In one embodiment, the communication between the add-on device and BS is similar to a Walkie-Talkie. In addition to the hardware add-on device, the software inside the add-on device can also be software downloadable so that an up-grade is easily available.

In another embodiment, referring again toFIG. 1, the callingdevice100 and the receivingdevice102 could be on different networks. In general, a voice over IP network can be considered to be an implementation of a particular “server” running on the Internet, and a particular piece of software (or hardware) known as a “client,” which is installed on a computer or other device for making the connection. In some instances, one voice over IP network will not be able to make calls directly to another voice over IP network. This may be the case if, for example, there is an incompatibility between the implementations of the server from which the call originates, and the destination server, such as different protocols, standards, and proprietary issues.

This may also be the case if there is an incompatibility between the implementations of the clients, which may also be due to different protocols or standards, as well as to different usernames and passwords. The callingdevice100 could be a GSM phone, for example, while the receivingdevice102 is a CDMA phone. In this case, the callingdevice100 does not need to know on what kind of network the receivingdevice102 is operating.

The callingdevice100, rather, sends an instruction about the network of thecalling device100, in addition to the short ringing tone, to the receivingdevice102 when commencing the call. The receivingdevice102, after receiving the details of the network of thecalling device100, can activate the appropriate client software to suit the network of thecalling device100, and connect to theInternet114 and the particularmeeting point server108.

For one voice over IP network, only one piece of client software needs to be installed on thecalling device100. The client software can be downloaded to thecalling device100, and activated only when needed. This arrangement can reduce airtime since the voice over IP network will not need to be active, online, or on air, at all times.

The Adoption of International Dialing Convention (IDC)

Due to a number of problems involving communication compatibility and identity (such as caller id) passing internationally, there is no straight-forward way to use IDC as phone number registration directly. This is one of the classic problems for all traditional telephone companies such as British Telecom (BT) or AT&T. This is also a problem for all Internet Phone companies such as Skype using the Internet as a communication tool.

In fact, this problem is due to the nature of direct communication and caller id passing. For our indirect communication method, we can provide a solution to solve this problem with our indirect communication method. That is, we can use IDC as registration number directly in our indirect system so that every existing phone number (old and new) of different countries can be under one single system to communicate freely.

The Incorporation of Non-Phone Devices into Global Telephone Number System

Most of the Non-Phone devices such as an iPad, TabletPC, PC, etc are not designed to be used as a phone and therefore there is no phone number (or SIM card) associated with them. Also, there is no existing effective method to assign phone numbers to these devices or for integrating them with the existing phone number systems in the world effectively.

In this document, we provide a method and a numbering system so that non-phone devices can also be integrated into the public phone network number system. In general, we regard any internet-capable device which is not designed as a phone as a “Non-phone Device”. Caller ID can also be transmitted legally for non-phone devices.

Implementation of IDC with Indirect Communication System: IDC Direct Registration

To register an IDC number to our indirect system is straight-forward. This is due to the fact that every registered number in our system will be represented by a virtual meeting point. All communication (or talk) will take place inside the meeting point.

We just consider IDC as a normal phone number and nothing special. We can simply put the IDC number into the registration field directly.

Suppose, we have two existing phones with numbers as shown below. One of the phone is in the UK and one is in the USA.

+44 7927 176753—A mobile phone (12345678) in UK

+1 202 87654321—A phone (87654321) in Washington D.C., USA

To register the UK phone, all we need is to activate the prototype (we have a prototype working on iPhone) and enter the IDC number into the “Reg. Tel. No.” field as illustrated below inFIG. 26. For the USA phone we do the same thing.

Later in this document, we will show a similar method to register “Non-devices” into the Indirect Communication System.

Implementation of IDC with Indirect Communication System: Call Initiation and Communication

As shown inFIG. 27, call initiation and communication in an indirect communication system proceeds as follows. In this case, thephone numbers 1111 and 2222 in the figure are replaced by “+44 7927 176753” and “+1 202 87654321” respectively, i.e.

1111-->+44 7927 176753

2222-->+1 202 87654321

When the phone “+447927176753” makes a call to the phone “+120287654321”, he/she just dials the number “+120287654321” directly.

The indirect system will activate the meeting point of the receiving phone, i.e.

“+120287654321@165.113.223.2”

Assuming the IP address of the indirect system is 165.113.223.2 as illustrated inFIG. 3A.

The indirect system will also put the caller “+44 792 7176753” into the meeting point as a visitor waiting for the receiving phone to go on-line to his/her home (i.e. meeting point), meet the visitor and begin talking.

Incorporating Non-Phone Devices into Global Phone Number SystemsAssigning Phone Numbers for Non-Phone Devices Problems

Most of the Non-Phone devices such as iPad, TabletPC, PC, etc are not designed to be used as phones and therefore there is no phone number (or SIM card) associated with them. Also, there is no existing method to assign phone numbers for these devices and integrate them with the existing phone number systems in the world effectively.

Since many of these non-phone devices have the capability to connect to Internet using wireless (such as Wi-Fi, 3G Internet) or wired (direct Internet cable) connections, they can be converted to a phone (e.g. an Internet Phone) easily using our Indirect method with a suitable App (or application).

To be able to assign phone number to non-phone devices effectively and integrate them into the existing phone system (phone number system) is essential for telecommunication.

Solution: Using Artificial Device Code (ADC)

With our indirect method, all these non-phone devices can also be assigned a compatible phone number using an “Artificial Device Code” (or ADC) together with one primary phone number. And Artificial Device Code (ADC) is similar to the country code used in the International Dialing Convention (IDC). To include Non-phone devices into the phone system, we simply need to create a new “country” code (which is non-existing). Consider the following example, shown inFIG. 28.

For example, if you have oneiPad2804, oneTabletPC2806, oneregular PC2808, and onemobile phone2802 with a real number such as “+44 7793 12345”, you can register youriPad2804,TabletPC2806, andregular PC2808 in the indirect system such as

iPad2804 phone number as +007 00 44 7793 12345

TabletPC2806 phone number as +007 01 44 7793 12345

regular PC2808 phone number as +007 99 44 7793 12345

where

+ is the International Dialing Prefix

007—is the Artificial Device Code (ADC)

00—the next two digits after the ADC is the sub-device number ranging from 00 to 99 (for example). In this case you can have 99 sub-devices.

44 7793 12345—after the sub-device number is the primary phone number associated with the non-phone device.

Remarks

1. The primary number such as +44 7793 12345 can be any land-line or any mobile phone in the world.

2. Each primary number can have up to 99 sub-devices (or associated device numbers) in our indirect system having prefix “+007xx” or ADC code plus device number (i.e. +ADCxx)

For example, the primary phone number +44 77933 12345 can have up to 99 associated sub-device numbers as follows:

$\begin{array}{cc}+00700& 447793312345\\ +00701& 447793312345\\ +00702& 447793312345\\ & ⋮\\ +00798& 447793312345\\ +00799& 447793312345\end{array}$

(Note: All numbers inFIG. 28 contains the International Dialing Prefix i.e. “+” sign)

3. The ADC code is not restricted to “007” and can be any digits and suitable format. Sometimes, a non-number string can also be used.

4. In order to identify non-phone devices and to avoid confusion, the ADC code should not be the same as any “Country Code” used today.

5. Sub-devices can be an “iPad”, “PC”, “tablet-PC” (e.g. Non-Phone devices).

6. Sub-devices can also be normal phone-devices such as another “iPhone” and/or “Android-Phone”.

7. Sub-devices can register to our indirect system server as shown inFIG. 27.

An implementation prototype using an iPad is shown inFIG. 29. This non-phone device (an iPad architecture) was registered in our prototype communication server (code name: Speekezy) as follows:

“+”	asInternational Dialing Prefix
007	as Artificial Device Code (ADC)
03	as Sub-device (i.e. the 3rd sub-device)
44 7717 791168	as Primary Number (a true number in UK)

Integrating with Existing Phone Number System and CallerID TransmissionI. When an Internet Call and Connection is Used

Consider when the Internet is used (such as Wi-Fi) to connect two devices. As shown inFIG. 30, a sub-device with number “+00 700 44 77933 12345” is making a call to another member of in the indirect system with number “+00 807 44 77933 54321”, both sub-devices will be considered as individual phones by the system. In this case, a full callerID such as “+00 700 44 77933 12345” will be transmitted to the recipient.

The recipient device can simply return the call to this full ID (i.e. +00 700 44 77933 12345), reaching the caller with the system.

(Note: All numbers inFIG. 30 contain the International Dialing Prefix i.e. “+” sign)

II. When GSM Call and Connection is Needed to Reach Outside Lines

Consider when GSM is used to call outside line. One typical example would be if sub-device “+00701 447793312345” is making a GSM call to an outside line “+441895222333” via the indirect system, as shown inFIG. 31. The indirect system will cut the ADC code and sub-device range out and transmit the remaining number (i.e. the primary number) as a callerID.

+00701 44 77933 12345 Calls +44 1895 222 333

with caller id as +44 77933 12345

In other words, the indirect system will only transmit the primary number “+44 77933 12345” as callerID to the recipient. Since the primary number is a true number in the global telephone system, this process will be fully compatible with the international dialing convention and requirement.

The recipient can simply return the call with the primary number reaching back to the caller. In this case, the primary phone of the caller will ring (Not the sub-device) in this case.

By “GSM” call is used, we mean the system needs to access the public telephone network via the PSTN or mobile phone via the cellular network reaching the recipient device. In this case, the Internet connection of the recipient device may not be available or not turned on.

Remarks

1. For this to work, all non-Phone devices such as iPad, PC or TabletPC will need to be registered as sub-device of a primary number.

2. If you have one Blackberry (BB), three iPhones, two iPads, five PCs, and four Android-Phones, you can register all of these non-Phone devices plus some phone devices as sub-devices of the BB phone.

When a sub-device is making a GSM call, the recipient will receive the callerID of the BB phone. When the call is returned using GSM, your BB phone will ring.

There is NO requirement for the BB phone to be registered with the system. We only need to associate all sub-devices with a true phone number.

3. When the GSM network is needed to make a call from a sub-device (+00701 44 77933 12345) to another sub-device (+00807 44 77933 54321), as shown inFIG. 32, that is also straight forward. The system will detect the ADC and sub-device range of both caller and callee. In this situation, the system will simply cut out the ADC and sub-device number of both caller and callee to make the GSM call. It is just like making a normal GSM call. In this case, the primary number of the callee will ring.

The Benefit of Incorporating Non-Phone Devices into Global Phone Number SystemEvery Single Existing (and New) Phones and Non-Phone Devices in the World are Included into ONE System

One obvious benefit of incorporating phone and non-phone devices is that every capable device, old or new, in the world regardless the country and region status are included in one phone number system.

All capable devices (mobiles, landline phones, PCs, iPads, Tablets) and communication are under one roof, one company, or one system.

You don't need to change to a new phone number. Your existing number can be used and registered to our system directly. Adding sub-devices is simple.

You don't need to change your phone contacts or your address book. You can use your phone contacts to make a call directly. Your friends and family can call you using phone contacts without changing anything no matter what countries they are in. This capability is also extended to non-phone devices.

Consistent CallerID Transmission

Non-Phone devices such as iPad, Tablet PC, PC, Mac, etc. . . . can have legal caller ID in the global phone number system. All caller ID transmission will be consistent with the international standard.

Different ADC can represent different non-phone devices (i.e. Different categories). Even in this situation, caller ID transmission is still legitimately represented by the same primary number.

For example, we can create the ADC (or Artificial Device Code) such as +007 to represent an iPad. It's just like creating a new “Country Code” for the iPad. Similarly, we can create a new country code for each new device type:

+007xx xxxxxxxxxxxx—Country code 007 to represent all iPad +004xx xxxxxxxxxxxx—Country code 004 to represent all PC.

When a GSM call is required, the primary phone number will be transmitted as callerID and be fully compliant with the international callerID transmission requirement.

Easy Adoption by Big Telephone Companies

For some big companies such as AT&T or BT, to adopt our system is easy. Since they already have millions of existing phone numbers, they can simply include all their numbers into our system. That will include all non-phone devices existing today and future. In this case, the world will have only ONE very big telephone company at the end.

In one embodiment, as shown inFIG. 33, a communication system3300 may have afirst transceiver3302 which has afirst identifier3304 and asecond transceiver3306 which has asecond identifier3308. Thefirst transceiver3302 may be a handset, a phone, a gateway, a base station, a server, a cell tower, a transceiver, a computer, a palm top, a laptop, a tablet, or a personal digital assistant. Thesecond transceiver3306 may be a handset, a phone, a gateway, a base station, a server3340, a cell tower, a transceiver, a computer, a palm top, a laptop, a tablet, or a personal digital assistant.

Thefirst identifier3304 may be an identification number of thefirst transceiver3302, a phone identifier, a series of digits, a GSM identifier, an International Dialing Convention identifier, a mobile phone identifier, or a land-line telephone identifier. Thesecond identifier3308 may be an identification number of thesecond transceiver3306, a phone identifier, a series of digits, a GSM identifier, an International Dialing Convention identifier, a mobile phone identifier, or a land-line telephone identifier.

Afirst sub-device3310 may have a first sub-identifier3312 comprised of thefirst identifier3304 and afirst device code3314. The first sub-identifier3312 may be an artificial device code, a sub-device identifier assigned to thefirst transceiver3302, or thefirst identifier3304. The artificial device code and the sub-device identifier may be removed to call an outside line.

Asecond sub-device3316 may have a second sub-identifier3318 comprised of thesecond identifier3308 and asecond device code3320. The second sub-identifier3318 may be an artificial device code, a sub-device identifier assigned to thesecond transceiver3306, or thesecond identifier3308.

Afirst communication channel3322 may exist between thefirst sub-device3310 and thesecond sub-device3316. A first transmission ofinformation3326 may emanate from thefirst sub-device3310 on thefirst communication channel3322 identified by thefirst sub-identifier3312.

Asecond communication channel3324 may exist between thefirst sub-device3310 and thesecond transceiver3306. A second transmission ofinformation3328 may emanate from thesecond sub-device3316 on thefirst communication channel3322 identified by thesecond sub-identifier3318.

A third transmission ofinformation3330 may emanate from thefirst sub-device3310 on thesecond communication channel3324 identified by thefirst identifier3304.

A fourth transmission ofinformation3332 may emanate from thesecond transceiver3306 on thesecond communication channel3324 identified by thesecond identifier3308.

In another embodiment, as shown inFIG. 34, a method of communication3400 may start by applying a first identifier to a first transceiver and applying a second identifier to a second transceiver, as shown inoperation3402.

The method of communication may continue by applying a first sub-identifier to a first sub-device comprised of the first identifier and a first device code, as shown inoperation3404.

The method of communication may continue by applying a second sub-identifier to a second sub-device comprised of the second identifier and a second device code, as shown inoperation3406.

The method of communication may continue by providing a first communication channel between the first sub-device and the second sub-device, as shown inoperation3408.

The method of communication may continue by providing a second communication channel between the first sub-device and the second transceiver, as shown inoperation3410.

The method of communication may continue by transmitting first information from the first sub-device on the first communication channel identified by the first sub-identifier, as shown inoperation3412.

The method of communication may continue by transmitting second information from the second sub-device on the first communication channel identified by the second sub-identifier, as shown inoperation3414.

The method of communication may continue by transmitting third information from the first sub-device on the second communication channel identified by the first identifier, as shown inoperation3416.

The method of communication may continue by transmitting fourth information from the second transceiver on the second communication channel identified by the second identifier, as shown inoperation3418.

In another embodiment, as shown inFIG. 35, a communication system3500 may have afirst transceiver3502 which has afirst identifier3504 and asecond transceiver3506 which has asecond identifier3508.

Aserver3540 may have athird identifier3538. Theserver3540 may be a computer, a base station, a handset, a Voice over Internet Protocol handset, a Voice over Internet Protocol controller, a switch box, or a dedicated black box device and peripherals. An address of a meeting point on theserver3540 may be an identification identifier of thesecond transceiver3506 and an Internet Protocol address or a Domain Name System name of theserver3540.

Afirst sub-device3510 may have a first sub-identifier3512 comprised of thefirst identifier3504 and afirst device code3514.

Asecond sub-device3516 may have a second sub-identifier3518 comprised of thesecond identifier3508 and asecond device code3520.

Afirst communication channel3522 may exist between thefirst sub-device3510 and thesecond sub-device3516.

Asecond communication channel3524 may exist between thefirst sub-device3510 and theserver3540, thesecond communication channel3524 not concurrent with thefirst communication channel3522. Thesecond communication channel3524 may be packets formatted with a format such as Voice over Internet Protocol, Internet Protocol, or User Datagram Protocol.

Athird communication channel3534 may exist between thesecond sub-device3516 and theserver3540, thethird communication channel3534 not concurrent with thefirst communication channel3522. Thethird communication channel3534 may be packets formatted with a format such as Voice over Internet Protocol, Internet Protocol, or User Datagram Protocol.

A first transmission ofinformation3526 may be transmitted from thefirst sub-device3510 on thefirst communication channel3522 identified by thefirst sub-identifier3512. If thesecond transceiver3506 accepts the first transmission, thesecond transceiver3506 connects to the meeting point.

A second transmission of information3528 from thefirst sub-device3510 may be transmitted on thesecond communication channel3524 identified by the first sub-identifier3512, the second transmission of information3528 following the first transmission ofinformation3526 and being relayed by theserver3540 to thesecond sub-device3516.

A third transmission ofinformation3530 may be transmitted from thesecond sub-device3516 on thethird communication channel3534 identified by thesecond sub-identifier3518. The third transmission ofinformation3530 following the first transmission ofinformation3526 and being relayed by theserver3540 to thefirst sub-device3510.

The packets may be redirected at theserver3540 by changing a sending address of each packet header from an address of the meeting point to an address of thesecond transceiver3506.

If thesecond transceiver3506 declines the first transmission, thesecond transceiver3506 sends a decline message to theserver3540 and theserver3540 relays the decline message to thefirst transceiver3502.

If thesecond transceiver3506 suggests an alternative meeting point in response to the first transmission, thesecond transceiver3506 connects to the alternative meeting point.

In another embodiment, as shown inFIG. 36, a method of communication3600 may start by applying a first identifier to a first transceiver, as shown inoperation3602.

The method of communication may continue by applying a second identifier to a second transceiver, as shown inoperation3604.

The method of communication may continue by applying a third identifier to a server, as shown inoperation3606.

The method of communication may continue by providing a first sub-device may have a first sub-identifier comprised of the first identifier and a first device code, as shown inoperation3608.

The method of communication may continue by providing a second sub-device may have a second sub-identifier comprised of the second identifier and a second device code, as shown inoperation3610.

The method of communication may continue by providing a first communication channel between the first sub-device and the second sub-device, as shown inoperation3612.

The method of communication may continue by providing a second communication channel between the first sub-device and the server, the second communication channel not concurrent with the first communication channel, as shown inoperation3614.

The method of communication may continue by providing a third communication channel between the second sub-device and the server, the third communication channel3634 not concurrent with the first communication channel, as shown inoperation3616.

The method of communication may continue by transmitting first information from the first sub-device on the first communication channel identified by the first sub-identifier, as shown inoperation3618.

The method of communication may continue by transmitting second information from the first sub-device on the second communication channel identified by the first sub-identifier, the second transmission of information following the first transmission of information, as shown inoperation3620.

The method of communication may continue by relaying the second transmission of information to the second sub-device by the server, as shown inoperation3622.

The method may continue by transmitting third information from the second sub-device on the third communication channel identified by the second sub-identifier, the third transmission of information following the first transmission of information, as shown inoperation3624.

The method of communication may continue by relaying the third transmission of information to the first sub-device by the server, as shown inoperation3626.

The foregoing has described the principles, embodiments, and modes of operation of the present invention. However, the invention should not be construed as being limited to the particular embodiments described above, as they should be regarded as being illustrative and not restrictive. It should be appreciated that variations may be made in those embodiments by those skilled in the art without departing from the scope of the present invention.

While a preferred embodiment of the present invention has been described above, it should be understood that it has been presented by way of example only, and not limitation. Thus, the breadth and scope of the present invention should not be limited by the above described exemplary embodiment.

Obviously, numerous modifications and variations of the present invention are possible in light of the above teachings. It is therefore to be understood that the invention may be practiced otherwise than as specifically described herein.

The many features and advantages of the invention are apparent from the detailed specification and, thus, it is intended by the appended claims to cover all such features and advantages of the embodiments that fall within the true spirit and scope thereof. Further, since numerous modifications and changes will readily occur to those skilled in the art, it is not desired to limit the inventive embodiments to the exact construction and operation shown and described, and accordingly all suitable modifications and equivalents may be resorted to, falling within the scope thereof.

Claims (18)

What is claimed is:

1. A communication system, comprising:

a first transceiver having a first identifier;

a second transceiver having a second identifier;

a first sub-device having a first sub-identifier comprised of the first identifier and a first device code;

a second sub-device having a second sub-identifier comprised of the second identifier and a second device code;

a first communication channel between the first sub-device and the second sub-device;

a second communication channel between the first sub-device and the second transceiver;

a first transmission of information from the first sub-device on the first communication channel identified by the first sub-identifier;

a second transmission of information from the second sub-device on the first communication channel identified by the second sub-identifier;

a third transmission of information from the first sub-device on the second communication channel identified by the first identifier; and

a fourth transmission of information from the second transceiver on the second communication channel identified by the second identifier,

wherein the first sub-identifier is comprised of an artificial device code, a sub-device identifier assigned to the first transceiver, and the first identifier, and

wherein the second sub-identifier is comprised of an artificial device code, a sub-device identifier assigned to the second transceiver, and the second identifier.

2. The communication system ofclaim 1, wherein the first identifier is selected from the group consisting of:

an identification number of the first transceiver;

a phone identifier,

a series of digits;

a GSM identifier;

an International Dialing Convention identifier,

a mobile phone identifier, and

a land-line telephone identifier.

3. The communication system ofclaim 1, wherein the second identifier is selected from the group consisting of:

an identification number of the second transceiver;

a phone identifier,

a series of digits;

a GSM identifier;

an International Dialing Convention identifier,

a mobile phone identifier, and

a land-line telephone identifier.

4. The communication system ofclaim 1, wherein the artificial device code and the sub-device identifier are removed to call an outside line.

5. The communication system ofclaim 1, wherein the first transceiver is a handset, a phone, a gateway, a base station, a server, a cell tower, a transceiver, a computer, a palm top, a laptop, a tablet, or a personal digital assistant.

6. The communication system ofclaim 1, wherein the second transceiver is a handset, a phone, a gateway, a base station, a server, a cell tower, a transceiver, a computer, a palm top, a laptop, a tablet, or a personal digital assistant.

7. A method of communication, comprising:

applying a first identifier to a first transceiver;

applying a second identifier to a second transceiver;

applying a first sub-identifier to a first sub-device comprised of the first identifier and a first device code;

applying a second sub-identifier to a second sub-device comprised of the second identifier and a second device code;

providing a first communication channel between the first sub-device and the second sub-device;

providing a second communication channel between the first sub-device and the second transceiver;

transmitting first information from the first sub-device on the first communication channel identified by the first sub-identifier;

transmitting second information from the second sub-device on the first communication channel identified by the second sub-identifier;

transmitting third information from the first sub-device on the second communication channel identified by the first identifier; and

transmitting fourth information from the second transceiver on the second communication channel identified by the second identifier,

wherein the first sub-identifier is comprised of an artificial device code, a sub-device identifier assigned to the first transceiver, and the first identifier, and

wherein the second sub-identifier is comprised of an artificial device code, a sub-device identifier assigned to the second transceiver, and the second identifier.

8. A communication system, comprising:

a first transceiver having a first identifier;

a second transceiver having a second identifier;

a server having a third identifier;

a first sub-device having a first sub-identifier comprised of the first identifier and a first device code;

a second sub-device having a second sub-identifier comprised of the second identifier and a second device code;

a first communication channel between the first sub-device and the second sub-device;

a second communication channel between the first sub-device and the server, the second communication channel not concurrent with the first communication channel;

a third communication channel between the second sub-device and the server, the third communication channel not concurrent with the first communication channel;

a first transmission of information from the first sub-device on the first communication channel identified by the first sub-identifier;

a second transmission of information from the first sub-device on the second communication channel identified by the first sub-identifier, the second transmission of information following the first transmission of information and being relayed by the server to the second sub-device; and

a third transmission of information from the second sub-device on the third communication channel identified by the second sub-identifier; the third transmission of information following the first transmission of information and being relayed by the server to the first sub-device,

wherein the first sub-identifier is comprised of an artificial device code, a sub-device identifier assigned to the first transceiver, and the first identifier, and

wherein the second sub-identifier is comprised of an artificial device code, a sub-device identifier assigned to the second transceiver, and the second identifier.

9. The communication system ofclaim 8, wherein the server is a computer, a base station, a handset, a Voice over Internet Protocol handset, a Voice over Internet Protocol controller, a switch box, or a dedicated black box device and peripherals.

10. The communication system ofclaim 8, wherein an address of a meeting point on the server comprises an identification identifier of the second transceiver and an Internet Protocol address or a Domain Name System name of the server.

11. The communication system ofclaim 8, wherein the second communication channel comprises packets formatted with a format selected from the group consisting of:

Voice over Internet Protocol,

Internet Protocol, and

User Datagram Protocol.

12. The communication system ofclaim 8, wherein the third communication channel comprises packets formatted with a format selected from the group consisting of:

Voice over Internet Protocol,

Internet Protocol, and

User Datagram Protocol.

13. The communication system ofclaim 10, wherein if the second transceiver accepts the first transmission, the second transceiver connects to the meeting point.

14. The communication system ofclaim 10, wherein if the second transceiver declines the first transmission, the second transceiver sends a decline message to the server and the server relays the decline message to the first transceiver.

15. The communication system ofclaim 10, wherein if the second transceiver suggests an alternative meeting point, the second transceiver connects to the alternative meeting point.

16. The communication system ofclaim 11, wherein the packets are redirected at the server by changing a sending address of each packet header from an address of the meeting point to an address of the second transceiver.

17. The communication system ofclaim 12, wherein the packets are redirected at the server by changing a sending address of each packet header from an address of the meeting point to an address of the second transceiver.

18. A method of communication, comprising:

applying a first identifier to a first transceiver;

applying a second identifier to a second transceiver;

applying a third identifier to a server;

providing a first sub-device having a first sub-identifier comprised of the first identifier and a first device code;

providing a second sub-device having a second sub-identifier comprised of the second identifier and a second device code;

providing a first communication channel between the first sub-device and the second sub-device;

providing a second communication channel between the first sub-device and the server, the second communication channel not concurrent with the first communication channel;

providing a third communication channel between the second sub-device and the server, the third communication channel not concurrent with the first communication channel;

transmitting first information from the first sub-device on the first communication channel identified by the first sub-identifier;

transmitting second information from the first sub-device on the second communication channel identified by the first sub-identifier, the second transmission of information following the first transmission of information;

relaying the second transmission of information to the second sub-device by the server; transmitting third information from the second sub-device on the third communication channel identified by the second sub-identifier, the third transmission of information following the first transmission of information; and

relaying the third transmission of information to the first sub-device by the server,

wherein the first sub-identifier is comprised of an artificial device code, a sub-device identifier assigned to the first transceiver, and the first identifier, and

wherein the second sub-identifier is comprised of an artificial device code, a sub-device identifier assigned to the second transceiver, and the second identifier.

Images