US 7,079,810 B2Grant
System and method for communicating with a remote communication unit via the public switched telephone network (PSTN)
Issue Date:2006-07-18
•21 Claims
•12 Drawing Sheets
Abstract
The present invention is generally directed to a system and method for communicating between a personal data access device and a remote communication unit. In accordance with one aspect of the invention, a device, electrically connected for communication with a public switched telephone network (PSTN), is provided for facilitating communications between a personal data access device and a remote communication unit disposed in communication with the PSTN. The device includes a radio frequency (RF) transceiver configured for communication with a remote RF transceiver associated with the personal data access device, via an RF link, and a controller, responsive to communications received from the remote RF transceiver to maintain two-way communication between the personal data access device and the remote communication unit via the PSTN and the RF link.
Metadata
Assignee
- StatSignal IPC, LLC
Inventors
- Thomas D. Petite
- James Davis
Application Information
Application Number:US 10/657,398
Filing Date:2003-09-08
Priority Date:1997-02-14
Art Unit:2687
Classifications
IPC:
H04B7/00
Patent Drawings (12 sheets)
Description
Cross Reference to Related Applications
[0001] This application is a continuation-in-part of U.S. patent application Ser. No. 09/301,671, filed on Apr. 28, 1999, now U.S. Pat. No. 6,618,578, and entitled “System and Method for Communicating with a Remote Communication Unit Via the Public Switched Telephone Network (PSTN),” which is a continuation-in-part of U.S. patent application Ser. No. 08/895,720, filed on Jul. 17, 1997, and entitled “Transmitter for Accessing Pay-Type Telephones,” now U.S. Pat. No. 5,926,531, which, in turn, is a continuation-in-part of U.S. patent application Ser. No. 08/825,576, filed on Mar. 31, 1997, and entitled “Transmitter for Accessing Automated Financial Transaction Machines,” which claims the benefit of U.S. Provisional Patent Application Ser. No. 60/040,316, filed Feb. 14, 1997, and entitled “Card Replacement Transceiver For Use With Automatic Teller Machines,” each of which are hereby incorporated by reference.
Field of the Invention
[0002] The present invention generally relates to communication systems, and more particularly to a system and method for communicating with a remote communication unit via the public switched telephone network (PSTN).
Background of the Invention
[0003] In recent years, there has been tremendous growth in the telecommunications industry. This growth has been fueled, in large part, by the proliferation of the Internet. More particularly, one segment of the telecommunications industry relates to data communications. As is known, data communications relates to the communication of data (as opposed to voice) from one end point to another. Typically, some type of computer or computing device is located at each end point, each having a communication device (such as a modem) to carry out the necessary modulation and demodulation of the signal that is communicated between the two end points.
[0004] A typical system configuration includes two computers, or computing devices, remotely located, but configured to inter-communicate over the PSTN. As one example, such a system exists when communicating between a first computer located at a residential customer premises and a second computer located at, for example, a service provider. In a manner that is well known, the first computer may initiate the connection by instituting a dial-up procedure, whereby it establishes a connection across the PSTN to make a second computer located at, for example, a service provider location. Once the connection is established, data communications may be freely exchanged between the first computer and the second computer, over the PSTN.
[0005] Remote computing devices, such as laptop computers, electronic schedulers, palmcorders, and other similar devices (also referred to herein as personal access devices) can be similarly configured for communication with a remote computing device. In one configuration, a jack or I/O port may be provided on the personal access device to allow a direct electrical connection (via cable) between the personal access device and, for example, a RJ-11 phone jack. However, in many situations phone jacks are not readily available. Therefore, an alternative means for communicating between two remote computing devices is desired.
[0006] Cellular systems are known to provide one such configuration. Referring to FIG. 1 , the system 10, as is known in the prior art, illustrates the data communications connection between the laptop computer 12 and a remote communication unit 14. The communication path established between laptop computer 12 and a remote communication unit 14 includes a cellular link 16 and a PSTN link 18. As is known, electrical hookups may be provided to electrically connect the computer 12 to a cellular phone 20. This “hookup” in part includes a cellular modem (not shown) within the computer 12. This cellular modem may communicate with this cellular phone 20 via a direct electrical connection. The cellular phone 20, in turn, communicates via electromagnetic waves to a nearby cellular base station 22 (located within the cell 24). The cellular base station 22 then relays this information to a mobile telephone switching office (MTSO) 26. In a manner that is known, the MTSO 26 may be disposed for communication with other cellular base stations (not shown), as well as the PSTN 18. Therefore, information may be communicated from the laptop computer 12 to the remote computing device 14 by way of cellular telephone 20, cellular base station 22, MTSO 26, and the PSTN 18.
[0007] The communication system 10 illustrated in FIG. 1 provides one configuration for communicating data between a transitory computing device (laptop 12) and a remote communication unit 14. However, existing configurations have several drawbacks. First, the communication channel established in a cellular link is inherently noisy and, therefore, unreliable. As a result, many errors can occur, leading to retransmissions of data, which slow down the effective communication link. In addition, most cellular service providers charge a relatively substantial fee for cellular phone usage. Therefore, a person is generally billed for each minute that they are communicating across the cellular phone 20.
[0008] Accordingly, an alternative configuration is desired that overcomes the shortcomings noted above.
Summary of the Invention
[0009] Certain objects, advantages and novel features of the invention will be set forth in part in the description that follows and in part will become apparent to those skilled in the art upon examination of the following or may be learned with the practice of the invention. The objects and advantages of the invention may be realized and obtained by means of the instrumentalities and combinations particularly pointed out in the appended claims.
[0010] To achieve the advantages and novel features, the present invention is generally directed to a system and method for communicating between a personal data access device and a remote communication unit. In accordance with one aspect of the invention, a system for communicating with a remote communication unit via a public switched telephone network (PSTN) is provided for facilitating communications between a personal data access device and a remote communication unit. The personal access device executes a program that communicates with the remote communication unit via the PSTN. The system includes a radio frequency (RF) transceiver associated with the personal data access device and in communication with the program. The system also includes a public, pay-type telephone, electrically connected to communicate over the PSTN. The system includes a second RF transceiver interfaced with the telephone and configured for communication with the RF transceiver in the personal data access device. A controller interfaced with the telephone is responsive to communications received from the first RF transceiver. The controller is configured to seize a phone line, initiate, and establish a data communication link over the PSTN to the remote communication unit designated by the personal data access device. The controller is also configured to allow simultaneous voice and data communications over the PSTN. The controller and the program are also configured to maintain two-way communication between the personal data access device and the remote communication unit via the PSTN and the RF link. The controller is further configured to terminate the data communication link over the PSTN to the remote communication unit designated by the personal data access device upon receiving a termination communication from the first RF transceiver.
[0011] In accordance with another aspect of the present invention, a system for communicating with a remote communication unit via a public switched telephone network (PSTN) is provided for facilitating communications between a personal data access device and a remote communication unit. The personal access device executes a program that communicates with the remote communication unit via the PSTN. The system includes a radio frequency (RF) transceiver associated with the personal data access device and in communication with the program. The system also includes a communication device, electrically connected to communicate over the PSTN. The system includes a second RF transceiver interfaced with the communication device and configured for communication with the RF transceiver in the personal data access device. A controller interfaced with the communication device is responsive to communications received from the first RF transceiver. The controller is configured to seize a phone line, initiate, and establish a data communication link over the PSTN to the remote communication unit designated by the personal data access device. The controller is also configured to allow simultaneous voice and data communications over the PSTN. The controller and the program are also configured to maintain two-way communication between the personal data access device and the remote communication unit via the PSTN and the RF link. The controller is further configured to terminate the data communication link over the PSTN to the remote communication unit designated by the personal data access device upon receiving a termination communication from the first RF transceiver.
[0012] In accordance with another aspect of the present invention, a method for retrofitting a public-pay telephone to provide wireless data network services to totable computing devices via the public switched telephone network (PSTN) is provided. In accordance with this aspect of the invention, the method includes the steps of interfacing a low-power transceiver with a pay-type telephone, providing public access to the low-power wireless transceiver, and enabling a totable computing device to communicate with the PSTN interface via the low-power wireless transceiver. In accordance with another aspect of the present invention, a method for providing wireless data network services to a totable computing device via the public switched telephone network (PSTN) is provided. In accordance with this aspect of the invention, the method includes linking a low-power wireless transceiver to a PSTN interface, providing public access to the low-power wireless transceiver, and enabling the totable computing device to communicate with the PSTN interface via the low-power wireless transceiver.
Description of the Drawings
[0013] The accompanying drawings incorporated in and forming a part of the specification, illustrate several aspects of the present invention, and together with the description serve to explain the principles of the invention. In the drawings:
[0014] FIG. 1 is a diagram illustrating a prior art system in which a laptop computer is disposed for communication with a remote communication unit via a cellular link and a PSTN link;
[0015] FIG. 2 is a diagram illustrating a system constructed in accordance with the present invention, wherein a computer is disposed for communication with a remote communication unit via an RF link and a PSTN link;
[0016] FIG. 3 is a block diagram illustrating certain components within a communication device (e.g., a telephone), in accordance with one embodiment of the present invention;
[0017] FIG. 4 is a block diagram illustrating certain components within a personal data access device (e.g., a laptop computer), in accordance with one embodiment of the present invention;
[0018] FIG. 5 is a flowchart illustrating the top-level functional operation of a communicating device constructed in accordance with one embodiment of the present invention;
[0019] FIG. 6 is a flowchart illustrating the top-level functional operation of a personal data access device constructed in accordance with one embodiment of the present invention;
[0020] FIG. 7 is a diagram illustrating a system constructed in accordance with the present invention, wherein a handset is disposed for communication with a plurality of communication devices on a network;
[0021] FIG. 8 is a diagram illustrating a system constructed in accordance with the present invention, wherein the controller and transceiver associated with the communication device are physically located outside of the communication device;
[0022] FIG. 9 is a diagram illustrating a system constructed in accordance with the present invention, wherein the communication device is a node;
[0023] FIG. 10 is a block diagram illustrating a typical business environment for implementing the described systems; and
[0024] FIG. 11 is a flowchart illustrating the steps used to provide wireless data networking over a PSTN between a personal access device and a remote communications unit.
Detailed Description of the Preferred Embodiment
[0025] Having summarized the present invention above, reference will now be made in detail to the description of the invention as illustrated in the drawings. While the invention will be described in connection with these drawings, there is no intent to limit it to the embodiment or embodiments disclosed herein. On the contrary, the intent is to cover all alternatives, modifications and equivalents included within the spirit and scope of the invention as defined by the appended claims.
[0026] Reference is now made to FIG. 2 , which is a diagram that illustrates a communication system 100 constructed in accordance with the present invention. In short, the present invention provides an alternative system and method for communicating between a personal data access device, such as a laptop computer 112, and a remote communication unit 114. In accordance with the invention, a communication link between the remote communication unit 114 and the personal data access device 112 is substantially across the PSTN 118. However, to accommodate the flexibility and remote nature of the personal data access device 112, a short segment of the communication link is established through electromagnetic waves, preferably in the form of a radio frequency (RF) link 115. One can appreciate that other forms of wireless communication, such as an infrared link, could also be used. A communication device—a public pay-type telephone 120 in the illustrated embodiment—provides for the translation and intercommunication between the PSTN 118 and the RF link 115.
[0027] It should be appreciated from the discussion herein, that the communication device may be provided in forms other than a public telephone 120. Indeed, communication devices may be provided in “nodes” that are disposed for communication with the PSTN 118, and which are inaccessible (hidden from view) from the general public. Nevertheless, they may be configured so that they may receive electromagnetic waves transmitted from a nearby personal data access device, in order to establish and maintain communications with a remote communication unit 114, in accordance with the present invention.
[0028] Remote communication unit 114 may be a variety of devices for communicating with personal access device 112. In accordance with one embodiment, remove communication unit 114 may provide an interface between the PSTN 118 and access to a network such as a LAN, WAN, an Intranet, or the Internet. In this embodiment, the remote communication unit 114 is a gateway between personal access device 112 and other remote computers on the remote network. In another embodiment, remote communication unit 114 may itself be configured as a data server for communication with the personal access device.
[0029] It should be appreciated that the personal data access device 112 may be any of a wide variety of devices, including but not limited to a desktop computer, a laptop computer, a palm-corder, or any of a number of hand-held computing devices. As is known, there are many hand-held computing devices, like schedulers and organizers, that have communication capability. Additionally, smart cards or similar personal transmitting devices with two-way, stored-value capabilities may be used. Devices such as these may be modified to include an RF transceiver and other necessary components to operate in accordance with the present invention. Personal data access device 112 may communicate with remote devices allowing a user to communicate data of personal and public nature. For example, a user may use the personal access device to use a web browser to access public Internet web pages. Alternatively, personal access device 112 may communicate with a remote server to download private, personal information such as email or calendar entries.
[0030] In operation, a user of the personal data access device 112 may use the device 112 in accordance with its ordinary functionality (e.g., computing, scheduling, etc.). When, however, it. is desired to access and inter-communicate with a remote computing device 114, the personal data access device 112 may be readily configured to establish this communication. Indeed, in one embodiment, a personal data access device 112 may be configured, consistent with prior art devices, to establish communication with a remote communication unit 114 through a direct PSTN connection. In this regard, the device 112 will be connected to, for example, a phone jack via a direct cable connection.
[0031] If, however, a direct cable connection is not a viable option (i.e., the user of the personal data access device 112 is not near an accessible phone jack), then an alternative means of communication between the device 112 and the remote communication unit 114 may be established and maintained in accordance with the present invention. By way of illustration, consider a person waiting on a flight in an airport wishing to check his or her e-mail messages, by dialing into a server at his or her place of employment, or an Internet service provider. In accordance with the present invention, the person may simply use the device 112 to initiate a dialout procedure via an RF link 115 through a nearby communication device such as telephone 120. It is assumed, for purposes of this illustration, that the nearby communication device incorporates a transceiver and other circuitry (discussed in connection with FIG. 3 ) in accordance with the present invention. Thus, it will be appreciated that the telephone 120 of the present invention will include internal circuitry that is not presently a part of standard telephone circuitry. In this regard, reference is made to FIG. 3 , which is a block diagram illustrating the basic components of this circuitry inside telephone 120. In the illustrated preferred embodiment, the telephone 120 includes a RF transceiver 122, an interface circuit 124, telephone circuitry 126, a handset 128, and a controller 130. The block denoted as “telephone circuitry” 126 should be understood as comprising components that are contained within standard telephones. Specifically, a typical telephone 120 will include an interface circuit 124, telephone circuitry 126, and handset 128. The interface circuit 124 refers to the line driver and other interface circuitry that interfaces a telephone with the two wire pair of the local loop.
[0032] In accordance with the present invention, additional circuitry, including a transceiver 122 and a controller 130 are integrated within the telephone 120. It should be appreciated that, in accordance with concepts and teachings of the present invention, the transceiver 122 need not be a RF transceiver, but could employ other technologies as well, such as infrared, ultrasonic, etc. However, in accordance with the preferred embodiment a RF transceiver 122 was selected. Indeed, in accordance with the preferred embodiment of the present invention a 900 MHz RF transceiver 122 was selected. In recent years, many cordless telephones have begun using 900 MHz RF transmission, which has been found to deliver better noise immunity in short distance RF communication. The classification of 900 MHz is rather loosely used, as precise communication frequencies typically vary slightly. The specific RF transceiver of the preferred embodiment may be the TR1000, manufactured by RF Monolithics, Inc.
[0033] As is known, the TR1000 hybrid transceiver is well suited for short range, wireless data applications where robust operation, small size, low power consumption, and low-cost are desired. All critical RF functions are contained within the single hybrid chip, simplifying circuit design and accelerating the design-in process. The receiver section of the TR1000 is sensitive and stable. A wide dynamic range log detector, in combination with digital automatic gain control (AGC), provides robust performance in the presence of channel noise or interference. Two stages of surface acoustic wave (SAW) filtering provides excellent receiver out-of-band rejection. The transmitter includes provisions for both on-off keyed (OOK) and amplitude-shift key (ASK) modulation. The transmitter employs SAW filtering to suppress output harmonics, for compliance with FCC and other regulations.
[0034] Additional details of the TR1000 transceiver need not be described herein, because the present invention is not limited by the particular choice of transceiver. Indeed, numerous transceivers may be implemented in accordance with the teachings of the present invention. Such other transceivers may include other 900 MHz transceivers, as well as transceivers at other RF frequencies. In addition, infrared, ultrasonic, and other types of transceivers may be employed, consistent with the broad scope of the present invention. Further details of the TR1000 transceiver may be obtained through data sheets, application nodes, design guides (e.g., the “ASH Transceiver Designers Guide”), and other documentation which are published and known by persons in the art. One skilled in the art would appreciate that a wide range of acceptable transceivers and frequencies may be used within the scope and spirit of the invention. For example, transceivers manufactured by Chipcon and Texas Instruments could also be incorporated. The invention is also not limited by frequency, and thus transceivers operating in the 2.4 GHz and 5 Ghz spectrum are also within the scope of the invention. Furthermore, the transceivers may use a number of wireless methods such as single channel frequency hopping, multi-channel frequency hopping, or direct sequence spread spectrum.
[0035] In keeping with the description of FIG. 3 , the telephone 120 also includes a controller 130. The controller 130, as illustrated, is disposed for communication with the interface circuit 124 as well as the transceiver 122. The controller 130 may be provided in a variety of forms. For example, the controller may be provided through dedicated circuitry. Alternatively, the controller 130 may be implemented through more general-purpose circuitry, which may include a CPU (not shown) and a memory (not shown). In a manner that should be appreciated, the memory may store program code 132 that includes a series of instructions that may be executed by the CPU. In accordance with the inventive aspects, portions of the program code may include a first segment 134 that is configured to control communications between the telephone 120 and a remote communication unit 114 over the PSTN 118. A second segment 136 may be configured to control RF communication between the telephone 120 and personal data access device 112 over of the RF link 115.
[0036] It should be appreciated that persons having ordinary skill in the art (an electrical circuit designer) will readily appreciate how the controller 130 may be implemented, without requiring undue experimentation. Indeed, the specific implementation of the controller 130 will necessarily vary depending upon the specific transceiver 122 and the details of the interface circuit 124. What is significant for purposes of the present invention is that the controller 130 is designed to control the operation of the RF transceiver 122, so that the transceiver 122 effectively communicates with the personal data access device 112. Likewise, the controller 130 controls the interface circuit 124 so that the interface circuit may effectively communicate, via the PSTN 118, with a remote communication unit 114. Furthermore, it should be understood that the RF transceiver 122 may be able to handle simultaneous communication between multiple personal data access devices at a time. Under these circumstances, controller 122 may be required to facilitate the necessary handshaking to allow the simultaneous communications.
[0037] In accordance with the broader aspects of the present invention, various embodiments of the controller 130, and system 100, may be implemented. In one embodiment, the system 100 may be designed so that all communications between the telephone 120 and the remote communication unit 114, via the PSTN 118, take place within the POTS (plain old telephone system) frequency band, which extends between approximately 0–4 kHz. In such an embodiment, if a person is using the telephone 120 in its ordinary fashion (i.e., by talking over the handset), then the controller 130 will be configured to prevent another person from establishing a connection, via the RF link 115, with the PSTN 118. Likewise, if a person has established a connection with a remote communication unit 114 via the PSTN 118 and RF link 115, then the controller is configured to prevent a person from disrupting this communication link by lifting the handset 128 and attempting to dial out, or otherwise. In one embodiment, once a communication link between the remote communication unit 114 and personal data access device 112 has been established, a person lifting the handset 128 to place a telephone call will simply hear a “dead” line, indicating that telephone is unavailable for current use. In alternative embodiments, the controller 130 may be interfaced with the telephone circuitry 126 to provide, for example, a recording, so that the person lifting the handset may hear a recorded message that the line is currently in use, and that they should try again later. Such a configuration may be preferred, because such a recording would prevent a person from confusing a “dead” line as indicating that the telephone 120 is out of order.
[0038] In accordance with an alternative configuration of the present invention, the system 100 may be configured to allow simultaneous communication with multiple remote units. In one such configuration, the POTS frequency band may be dedicated for conventional voice communication between the handset 128 and a remote telephone 140. An alternative service, such as DSL (digital subscriber line), ISDN (integrated services digital network), T1 line, or other, may be implemented to handle data communications. As is known, and illustrated by reference 150, DSL communications occur in a frequency band that is above the POTS frequency band. Therefore, the controller 130 and interface circuit 124 may be configured to allow simultaneous voice and data communications over the same two wire pair local loop 145 to two separate remote destinations, without signal interference. In such an embodiment, data communicated between the personal data access device 112 and a remote communication unit 114 may be communicated over the PSTN between the central office (not shown) and a telephone 120 at a higher frequency range. As is known, the PSTN may include Therefore, the data communications may take place between the personal data access device 112 and a remote communication unit 114 at the same time that voice communications may take place between the handset 128 and the remote telephone 140, sharing the same local loop 145.
[0039] Reference is now made to FIG. 4 , which is a block diagram that illustrates the personal data access device 112 in accordance with one embodiment of the present invention. As previously described, the personal data access device 112 may be in the form of a personal computer, such as a laptop computer. As is known, a laptop computer includes a CPU 162, memory 164, as well as other circuitry or circuit cards that are utilized in the operation of the device 112. In accordance with the present invention, a transceiver 160 is also provided in order to establish and maintain communications with the transceiver 122 described in connection with FIG. 3 . A modem 166 may also be provided for modulating the signal before delivering the signal to the RF transceiver 160. In some implementations, however, the modem 166 may be integrated as a part of the transceiver 160. Accordingly, although a variety of transceiver technologies may be employed, it will be appreciated that transceiver 160 will be compatible with the transceiver 122. An interface circuit 167 may also be provided and configured to interface the CPU 160 with the RF transceiver 160. Of course, the specific implementation of the interface circuit 167 will necessarily depend upon the specific transceiver 160 and CPU 162 that are implemented. Program code (not shown) stored within the memory 164 may be used to instruct the CPU 162, so as to control the operation of the RF transceiver 160.
[0040] In another embodiment, a handset 168 (illustrated in dash line) may be provided and coupled to the modem 166. Implementing technology such as simultaneous voice data (SVD) technology, the device 112 may communicate both voice and data information with a remote communication unit 114, through the communication path provided by the inventive system 100.
[0041] Having described the principal hardware components of a system 100 constructed in accordance with the invention, reference is now made to FIGS. 5 and 6 , which are flowcharts that illustrate the top-level functional operation of a telephone 120 and a personal data access device 112, in accordance with one embodiment of the invention. Referring first to FIG. 5 , a flowchart 200 illustrates the operation of a telephone 120 (or other communication device), constructed in accordance with one aspect of the present invention. As mentioned above, a system constructed in accordance with the invention may be implemented in various configurations. One configuration may allow simultaneous communication between a personal data access device 112 with a remote communication unit 114, and the telephone handset 128 with a remote telephone 140. In alternative configuration, such simultaneous communication is prohibited. A flowchart 200 of FIG. 5 illustrates the top-level operation of a system constructed in accordance with the alternative (i.e., no simultaneous communication) configuration.
[0042] After a power up reset, for example, the system may evaluate whether the telephone handset 128 is on hook or off hook (step 202). If the handset is off hook, then the controller 130 dedicates communications over the PSTN line 145 to the handset 128 (step 220). In one implementation, the controller 130 may check to determine whether the transceiver 122, in response to a request from the personal data access device 112, has requested communication over the PSTN (step 222). If so, the controller may control a reply message via the RF link 115 to the personal data access device 112, and inform the personal data access device 112 that the line is busy, and therefore unavailable (step 224). Thereafter, the controller may loop back to step 202. So long as the handset 128 remains off hook, the PSTN communication link 145 will “belong” to the handset 128. Once, however, the handset 128 is replaced and the telephone is no longer off hook, then the controller may check to determine whether the transceiver 122 has requested the PSTN communication link 145 (step 204). If not, the controller may loop on steps 202 and 204, until either the handset 128 is taken off hook or the transceiver 122 has requested the PSTN communication link 145. Once the transceiver 122 has requested communication over the PSTN link 145, then the controller controls communications between the transceiver 122 in the personal data access device 112 to retrieve initialization and start-up informnation. For example, the personal data access device 112 may communicate to the controller 130 the telephone number that is to be dialed in order to establish a communication link with a remote communication unit 114. The signaling that takes place in order to establish this link need not be described herein, as it should be appreciated by persons skilled in the art.
[0043] The controller may verify (step 208) that the communication link has been properly established. If not, the controller may return to step 202, and proceed as described above. If, however, the communication link has been properly established, then the controller will control the operation of the telephone 120 to relay communications between the PSTN 118 and the remote transceiver 160 of the personal data access device 112. In an embodiment that prohibits simultaneous communication between the device 112 and remote communication unit 114, and the handset 128 and a remote telephone 140, the controller 130 may be configured to check (during data communications) to determine whether the handset 128 is lifted (step 212). If so, the controller 130 may be configured to control the playback over the handset 128 of a recorded message (step 214). Such a message may inform the person lifting handset that the line is temporarily in use and that the person should try back again later. Such a feature helps to prevent confusion by the person as to whether the line may be dead, or telephone malfunctioning.
[0044] As the controller 130 operates to relay communications between the PSTN 118 and the personal data access device 112, it may also check for a termination sequence (step 216). Specifically, the controller 130 may evaluate messages received from the personal data access device 112 for a particular sequence that would identify the desire on the part of the device 112 to terminate the connection with the remote communication unit 114. Of course, in the preferred embodiment, program code within the device 112 will communicate this desire to the remote communication unit 114 before issuing a termination sequence to the controller 130. Once such a termination sequence is received, the controller then controls the signaling to terminate the PSTN connection (step 218). Thereafter, the controller may return to step 202 and proceed as described above.
[0045] Reference is now made to FIG. 6 , which is a flowchart 300 illustrating the top-level functional operation of the control aspect of one embodiment of the personal data access device 112. At a first step (step 302) the device 112 may determine whether it wishes to request communication with a remote device over the PSTN. If not, the device 112 may continue to operate in its normal, functional fashion (step 304). If, however, the PSTN communication connection is desired, then the device 112 will transmit, via electromagnetic waves, a certain signaling sequence (step 306) to the transceiver 122 integrated within the telephone 120, or other communication device. The device 112 may then check for a responsive message (sent from the telephone 120) to determine whether the line is available (step 308). As illustrated in FIG. 5 , the controller 130 of the telephone 120 may send a reply message if the line is unavailable (step 224). If step 308 determines that the line is not available, or it receives no response at all (indicating that there is no nearby transceiver connected to the PSTN), then it may display an appropriate message to the user, and thereafter return to step 302. If, however, a line is available, then the device 112 relays or exchanges the necessary information, via electromagnetic waves, with the transceiver 122 of the telephone 120 (step 310), in order for the controller 130 to establish a communication link with remote communication unit 114. The device 112 may then check to determine whether a communication link with remote communication unit 114 was properly established (step 314). If not, it may display an appropriate message to the user (step 312) and returns to step 302. If, however, a proper communication link was established between the controller 130 and the remote communication unit 114, then the device 112 will proceed to communicate with the remote communication unit 114 via RF link 115 and the PSTN 118. This communication will continue until the device 112 seeks to terminate the connection. Therefore, the device 112 may evaluate whether it wishes to disconnect (step 318) the connection. If not, the flowchart 300 indicates that the device may simply loopback to step 316, where communication continues. If, however, the device 112 wishes to disconnect the communication link, then it communicates via electromagnetic waves appropriate disconnect signaling (step 320) to the controller 130 of the telephone 120. Thereafter, the device 112 may return to step 302, where it may proceed as previously described.
[0046] As explained above, RF transceiver 122 may be able to handle simultaneous communication between more than one personal data access device 112 at a time. In this situation, each device 112 may maintain a communication link with remote communication unit 114 at the same time according to flowchart 300.
[0047] Now looking to FIG. 7 , system 700 is depicted in which a portable handset 705 communicates with remote communication unit 114. As described above in relation to system 100, the personal access device 112 (FIG. 4 ) may be any one of a number of totable, or fixed, devices such as a desktop computer, laptop computer, or PDA. In accordance with system 700, personal data access device 112 of FIG. 4 is embodied as a portable handset 705. The portable handset 705 enables a user to communicate voice information to remote communications unit 114. The handset 705 includes a microphone to receive voice signals and a speaker to convert received communications into audible sound. Handset 705 may already be configured to use cellular technologies such as GSM, CDMA, or TDMA and may be implemented with analog or digital transmission signals.
[0048] The voice signals may be transmitted between remote communications device 114 and handset 705 in at least two ways. In a first embodiment, packeted voice signals are sent from portable handset 705 over RF link 115 to telephone 120. Telephone 120 converts the packeted data into analog voice signals which are then communicated across the POTS voice band of the PSTN. In a second embodiment, packeted voice signals are sent over RF link 115 and forwarded across the PSTN to remote communication unit 114 where they may be decoded into the analog signal. These processes will now be described in more detail.
[0049] The portable telephone 705 of the first embodiment of system 700 digitizes a user's analog voice signals into data packets. The digitization process is typically performed by a digital signal processor (DSP) embedded within the portable phone 705. The data packets are then delivered across RF link 115 from RF transceiver 160 (FIG. 4 ) to RF transceiver 122 in telephone 120. The data packets may be assembled using the well known internet protocol (IP) which provides error checking and addressing. Telephone 120 may also have an embedded DSP for decoding the data packets sent from the RF transceiver 160 back into analog voice signals. The voice signals are then circuit-switched as a normal telephone call to provide POTS band voice communication over the PSTN 118 to remote telephone 140. One will appreciate that according to this embodiment, because telephone 120 circuit switches the call between the telephone 120 and the remote telephone 140, telephone 120 is not be able to accommodate simultaneous communication using handset 128 (FIG. 3 ) on the same connection to the PSTN. Thus, the functional operation described by system 200 (FIG. 5 ) would be implemented to provide access to telephone 120 and control access to the handset 128 on telephone 120.
[0050] One will appreciate that communications in the opposite direction, from remote telephone 140 to portable telephone 705 operate in a reverse manner. Analog voice signals communicated from remote telephone 140 are digitized into packeted data by circuitry, such as a DSP, within telephone 120. The packeted data is then delivered to portable phone 705 which decodes the packeted data and a speaker converts the resulting signal into audible sound.
[0051] The user initiating a voice communication may indicate a call destination by dialing a telephone number of remote telephone 140 or other identification via the user interface of personal access device 112. This destination identification is sent along with the voice data to provide telephone 120 with the destination for a particular communication. For example, in the case of a typical telephone call, the user may dial a telephone number identifying the phone address of a desired call destination. Telephone 120 includes telephone circuitry 126 designed to decode this information and route the call to the provided destination over the POTS voice band. In effect, the first embodiment of system 700 provides the voice communication capabilities of telephone 120 remotely via the portable telephone 705.
[0052] In a second embodiment of system 700, as in the first embodiment, portable telephone 705 digitizes a user's analog voice signals into packeted data signals which are transmitted to telephone 120. However, in contrast to the first embodiment of system 700 described above, telephone 120 does not convert the packeted data into a POTS band voice signal. Rather, the packeted data signals may be relayed via packet switching over PSTN 118 to remote communication unit 114. Remote communication unit 114 may then provide the circuitry, such as a DSP, to decode the packeted data into an analog voice signal and then route the voice communication to remote telephone 140 via the POTS voice band. As in the first embodiment, the remote telephone 140 may be identified by a telephone number provided by a user of the handset 168.
[0053] As in the prior embodiment, one will appreciate that communications in the opposite direction, from remote telephone 140 to portable telephone 705 will be performed in a reverse manner. Analog voice signals communicated from remote telephone 140 are digitized into packeted data by circuitry, such as a DSP, within remote communication unit 11 4. The packeted data is then delivered across the PSTN to telephone 120. Telephone 120 relays the packeted data to portable phone 705 which decodes the packeted data and the speaker converts the resulting signal into audible sound.
[0054] One will appreciate that according to this second embodiment telephone 120 is able to accommodate simultaneous voice communication using handset 128 (FIG. 3 ) on the same connection to the PSTN as portable telephone 705. Thus, the functional operation described by system 300 (FIG. 6 ) would be implemented to control access to the telephone 120 by portable handset 705.
[0055] It will be appreciated that this embodiment enables physical placement of a remote communication unit 114 in a location that enables a user to make what is typically a long distance call with only charges related to the local access at telephone 120 and any other connection fees associated with accessing the remote communication unit 114. Thus, using software and computer techniques that are now well known, a voice call can be placed over the PSTN, utilizing the Internet, to a very distant remote telephone 140, whereby long distance telephone calling is effectively achieved without the associated long distance connection fees.
[0056] Further embodiments to system 700 may include a roaming feature enabling the RF transceiver 160 (FIG. 4 ) to communicate with a RF transceiver 122 (FIG. 3 ) providing the strongest signal link strength in a given physical location. As a user of handset 705 moves about a geographic area within a network 124 of telephone 120 locations, the circuitry associated with RF transceiver 160 monitors the signal link strength of the connection with the current RF transceiver 122, and the strength of another available RF transceiver 122 in the network. If the signal link of the current RF transceiver becomes weaker than the signal of another RF transceiver 122 on the network 124, the RF transceiver 160 may transfer the current communication to the alternate RF transceiver 122 with the strongest signal. It will be understood that this embodiment provides handset 705 with a system for periodically monitoring the signal strength of surrounding RF transceivers 122 associated with a telephone 120. Accordingly, the RF transceiver 122 with the strongest signal may be selected for communication in order to establish the most reliable link.
[0057] It will be appreciated that the embodiments of system 700 described above may provide an alternative to traditional wireless phone usage. For example, the use of traditional wireless phones may be severely limited in certain locations, such as when a user is underground or surrounded by tall buildings. Instead, a handset 705 only need be positioned within the range of a RF transceiver 122 located within a telephone 120 or communication device. Such applications find use in hotels, office buildings, factories, city streets, restaurants, malls, and shopping centers.
[0058] As described above in relation to systems 100 and 700, the RF transceiver 122 and controller 130 are preferably located within the housing of a telephone 120 in order to save space, reduce cost, and provide physical protection. However, as depicted by system 800 in FIG. 8 , it will be appreciated that the RF transceiver 122 and controller 130, associated with the telephone 120, may be located outside the physical confines of the telephone 120 for ease of installation, ease of service, or space restrictions. Additionally, placing the RF transceiver 122 in a location remote from the telephone 120 housing may increase reception and reduce RF interference. The RF transceiver 122 and controller 130, may be placed in a separate module 121, yet continue to share the same connection to the PSTN 118 as used by the telephone. By using the same connection between the telephone 120 and the PSTN 118, existing infrastructure may be utilized to provide communications with a remote communication unit 114 without running additional network cables. The separate module 121 may be located just outside the telephone 120 housing, or may be remotely located by several feet in order to decrease visibility, increase reception, or provide a decreased risk of theft. Despite the greater proximity from the telephone 120, the RF transceiver 122 and controller 130, now housed within separate module 121, may interface through interface 801 to the interface circuit 124. Interface 801 may be a wired or wireless connection using well known communication methods. Interface 801 may provide a communication channel between the RF transceiver 122 and controller 130 to circuit 124 or other circuitry located within the telephone.
[0059] As mentioned above, in addition to telephone 120, a communication device may comprise any type of communication “node” connected to the PSTN. Such a node may be a DSL modem 902 with an integrated RF transceiver 122 and controller 130 as shown in system 900 in FIG. 9 . DSL modem 902 uses an existing connection to the PSTN 118 to provide data communication. DSL modem 902 is publicly accessible by anyone within the proximity of the integrated low-power RF transceiver. Such “nodes” are often hidden out-of-site of a customer's view in a stationary object such as an electric sign or billboard. Alternatively the nodes can be displayed as an indication to a user that the wireless service is available. A “node” may also describe a public, pay-type telephone which has been disabled conventional voice-type telephone calls using the integrated handset 128, but is configured for remote access by a personal data access device 112 according to systems 100, 700, 800, or 900.
[0060] The systems and methods of the described systems 100, 700, 800, or 900 may be used to provide publicly accessible wireless access to personal data access devices wherever communication devices already exist. Because the wiring infrastructure to the PSTN is already in place, retrofitting existing communication devices to handle wireless data access can provide a new method of generating revenue from existing business assets. For example, the cellular phone boom has left pay-phone companies with decreasing revenues. Besides the convenience and low prices of cellular phones, current cellular phone plans include free long distance. Thus, the demand for voice calls on pay-phones has declined, leaving pay-phone companies with assets returning very little profit. While voice calls using pay phones are on the decline, the use of wireless data networking by consumers is on the rise. Thus, by retrofitting pay-type telephones with wireless access, new life is breathed into these assets.
[0061] Referring now to FIG. 10 , a typical business environment 1000 for implementing business models using the described systems 100, 700, 800, or 900 (“the systems”) include three principal parties: a customer, a wireless service provider, and an Internet/Intranet Service Provider (ISP) 1015.
[0062] First, an end user, patron, or customer 1005 possesses the personal data access device 112 such as laptop or portable handset 705 (FIG. 7 ). This personal access device has the ability to communicate with a communications device such as telephone 120 or node 705. Customer 1005 may be a patron to a restaurant, a traveler in an airport terminal, a commuter on a city street, or the temporary resident of a hotel.
[0063] Second, a wireless service provider 1010 provides the communication device, such as telephone 120 (FIG. 2 ) or node 902 (FIG. 9 ) which can wirelessly connect to the personal access device 112 through the means described in connection with the systems above. Wireless service provider 1010, for example, may be a restaurant, an airport, a pay telephone owner or operator, or a hotel. Wireless service provider 1010 supplies the hardware and the connection to the communication device, but may not necessarily provide the service to connect to the Internet or Intranet over the PSTN 118.
[0064] A third party, Internet/Intranet Service Provider (ISP) 1020 provides the service connecting the customer 1005 to the remote communications device 114. Ultimately, remote communications device 114 may provide user 1005 with access to the Internet. ISP 1020 may be a traditional dial-up ISP when personal data access device 112 connects to the network using system 200 (FIG. 5 ). In the alternative, ISP 1020 may provide broadband services according to system 300 (FIG. 6 ).
[0065] Of course, in some situations ISP 1020 and wireless service provider 1010 may be the same entity. For example, a pay telephone company may operate both pay telephones and an Internet/Intranet access service.
[0066] In one embodiment, wireless service provider 1010 may require appropriate identification from customer 1005 to access a communications device. For example, the customer 1005 may be required to enter billing and/or identifying information through a provided portal each time a user wishes to gain access to the communications device. In other situations, wireless service provider 1010 may be able to decode identifying information sent from a customer's 1005 personal data access device 112. The wireless service provider 1010 may charge for access, or simply use the access as a free service designed to attract customers. For instance, when wireless service provider 1010 is a hotel the telephones installed throughout the hotel may be freely accessed as part of a guest's included amenities. On the other hand, the hotel may charge a fixed fee for an allotted access window, or alternatively the hotel may charge a customer on the basis of actual time of access, or the amount of data transmitted.
[0067] In another embodiment, ISP 1020 controls the access of user 1005 to the Internet instead of wireless service provider 1010. In this situation wireless service provider 1010 may provide the physical means to access the remote communication unit 114, but the ISP 1020 restricts access based on well known payment or billing procedures such as those currently used by dial-up and DSL internet providers.
[0068] In yet another embodiment, wireless service provider 1010 may provide all compensation to ISP 1020 for a user's 1005 access to remote communication unit 114. In this situation, customer 1005 does not compensate other parties for access. Thus, instead of charging for access, wireless service providers may use this method to entice customers 1005 to remain within the physical proximity of a wireless service provider 1010 for a longer period of time. By retaining the customers 1005 for a longer period of time, the wireless service provider 1010 has the opportunity to sell the customer more goods or services. For example, a coffee shop wishing to entice their customers to stay for another cup of coffee may provide a freely accessed communication device, such as node 902. This enables the coffee shop's customers to surf the Internet at their leisure at no cost to the customer 1005.
[0069] While several specific business models have been discussed, one skilled in the art would recognize that many models of payment for access to the remote communication unit 114 and/or a communication device such as telephone 120 are well within the spirit and scope of the invention.
[0070] Business environment 1000 may be implemented by various industries to provide data and/or voice communications for patrons. The business model is typically more successful in any location where communication devices typically already exist and the potential for data transmissions are high.
[0071] For example, a wireless service provider 1010 may be a business providing pay-telephone service via a network of pay-type telephones. The business providing the pay-phone service may retrofit their pay-type telephones throughout a geographic area with any of the described systems. The existing base of pay-type telephones are designed to primarily handle voice-type telephone calls by using a provided handset 128 integrated with the telephone. By incorporating a controller 130, R.F. transceiver 122, and interface circuit 124 into the base of telephones throughout a geographic area, a customer 1005 is provided with a method of remotely communicating voice and/or data with a personal data access device 112 without using a cellular base station 22. While the preferred embodiment retains the function of providing the access to a pay-telephone for normal voice calls using the pay-phone's integrated handset 128, in some cases the pay-type telephone may be removed leaving only a wireless node. In this case, the interface circuit 124 continues to handle the function of providing an interface between the PSTN and controller 130 and RF transceiver 122, but the telephone circuitry 126 and handset 128 are no longer needed.
[0072] Similarly, wireless service providers 1010 may include airports, subways, bus stations, and other transportation hubs that could use the system in conjunction with the pay-type telephones 120 or other communication devices found throughout the terminals and waiting areas. By installing pay-phones 120 containing the required circuitry (for example, system 100), or by installing add-on circuitry in a separate module 121 associated with the pay-phones (for example, system 900) an airport is able to provide wireless Internet access to travelers without the inconvenience of installing new cabling throughout a terminal.
[0073] Instead of a pay-type telephone in a public area, the communication device may be a telephone 120 in a hotel room, a telephone in a conference room, or an office telephone. For example, a hotel may use the business environment 1000 as an efficient way of deploying wireless Internet throughout a hotel. By placing transceivers 122 in or near the telephones in guest rooms, lobbies, and meeting areas, the hotel is provided with a network capable of supporting wireless communications between a personal data access device 112 and a remote communication unit 114 throughout the hotel. Similarly, an office building can be completely outfitted with a data network by using an existing telephone communications infrastructure, without running additional cables throughout the building.
[0074] Restaurants and other retailers may wish to install wireless communication nodes according to the described business environment 1000 in order to attract and retain customers 1005. For example, a retailer that wishes to attract customers may provide a wireless node 902 during a customer 1005 visit. Customers may own their own RF transceiver, installed within their personal access device 112, or they may rent or borrow the transceiver from the restaurant in order to use the service during the visit. This transceiver may be integrated into a PCMCIA (Personal Computer Memory Card International Association) adapter card that fits into a corresponding slot of a laptop computer. The retailer may use the system as a way to retain patrons in the store, to provide additional advertising and information to the customers, and if the service is provided for a fee, additional revenue. Because most business locations already have a telephone connection for voice communications, the connection to the PSTN 118 typically already exists. Therefore, system 900 is easily installed and maintained.
[0075] FIG. 11 shows one example of how the systems and methods of the invention may be used by a wireless service provider 1010 to provide wireless data networking between a personal data access device 112 and a remote communication unit 114. An RF link to a communications device may be provided in high traffic areas where users frequently gather (step 1105). For example, cafes, restaurants, airports, bus stations, hotels, and bus stops are examples of such places that typically have an installed base of telephones 120. Because several networks 124 (FIG. 7 ) may be located within the same proximity of each other, a network identifier may be transmitted by a communication device in order to identify a particular collection of communication devices making up a network (step 1110). A network is simply defined as a collection of one or more communication devices designed to be accessed under the same service provider. The network identifier may be provided in the format of an access code used to connect to the proper network. Alternatively, the user may execute software on the personal access device 112 to “sniff” for available networks. If a list of available networks is found, the user may then select the appropriate network to join. Once the user has joined the network, a portal may be provided as an initial display to the user; typically the portal is displayed within an Internet browser in order to establish access privileges (step 1115). Initially, the portal may be the only accessible feature on the network. However, once access privileges are granted, the personal access device 112 may be granted access to some greater amount of features, such as access to the Internet, after providing requested information (step 1120). For instance, the portal may request billing information which may be in the form of a credit card number, hotel room number, subscription account number, gift card number, or other known payment methods in exchange for the additional access to the system. Alternatively, many businesses may not charge at all for the service, but may still require information used to identify the user. In either case, the business may use the portal to advertise or provide information to customers. In the case of free access, the provider may not use a portal at all. Access rights can be granted to a personal access device 112 as determined based on a restricted usage of time, a restricted data transfer quantity, or a predetermined number of accesses (step 1125). Once the personal access device 112 has acquired access to the system, the user may continue to use the additional features until the access rights expire (step 1130). When the access rights have expired, the system may restrict access to the additional features and provide the portal for purchasing additional access rights (step 1135).
[0076] While it is anticipated that many users may pay for access via the portal using an electronic registration form and a charge account, many other forms of payment are within the scope of the invention. For example, the user may purchase access to the system at the communications device itself. In particular, a pay-type telephone 120 may have a credit card reader and user interface for activating access. Alternatively, the pay-type telephone 120 may use voice activated prompts to guide a user through payment for the access to the service.
[0077] In another embodiment, a subscription service may be provided such that a user may pre-arrange access to the network. According to this embodiment, a personal access device 112 may be automatically identified based on unique identification such as an Ethernet address. Alternatively, a user may enter identifying information into the portal to identify the prearranged subscription. It is contemplated that other commonly known billing methods, such as providing registration to a user through an Internet web portal, or by calling a service provider could also be used.
[0078] The transceiver 160 and related circuitry in the personal data access device 112 may be usable with a communication device such as pay-type telephone 120 operated by many different wireless service providers 1010 such that an customer 1005 may access a plurality of communications devices without purchasing additional transceiver circuitry for each service. For example, the RF link 115 between the telephone 120 and the personal data access device 112 may be any number of commonly-used, standardized protocols known in the art. For example, systems using Bluetooth technology, or systems using the wireless-Ethernet IEEE 802.11 standards (e.g. 802.11(a), 802.11(b), and 802.11(g)), commonly known as “Wi-Fi,” are contemplated. The 802.11 specification is an over-the-air interface between a wireless client and a transceiver in a base station or between two wireless clients. The 802.11 standard generally applies to wireless LANs and provides 1 or 2 Mbps transmission in the 2.4 GHz band using either frequency hopping spread spectrum (FHSS) or direct sequence spread spectrum (DSSS). The 802.11(a) variation is an extension to 802.11 that applies to wireless LANs and provides up to 54 Mbps in the 5 GHz band. The 802.11(a) variation uses an orthogonal frequency division multiplexing encoding scheme rather than FHSS or DSSS. The 802.11(b) variation, is an extension to 802.11 that applies to wireless LANs and provides an 11 Mbps transmission with a fallback to 5.5, 2 and 1 Mbps in the 2.4 GHz band. 802.11(b) uses only DSSS. The 802.11g variation applies to wireless LANs and provides over 20 Mbps in the 2.4 GHz band. Because this type of network technology provides network circuitry capable of being used with multiple wireless service providers 1010, a customer 1005 will typically own all the circuitry needed to interact with a communications device 120. However, some wireless service providers 1010 may rent the required transceiver to a user 1005 for a personal access device 112, and any rental fees may be included in the total revenue for the system.
[0079] Accordingly, as described above, a system is provided for communicating with a remote communication unit via a public switched telephone network (PSTN). In one embodiment, the system includes a personal data access device executing a program that is to communicate with the remote communication unit via the PSTN, a data communication device associated with the personal data access device and in communication with the program, and a first radio frequency (RF) transceiver associated with the personal data access device and in communication with the data communication device. The system further includes a public, pay-type telephone, electrically connected for communication over the PSTN, a second RF transceiver associated with the telephone, the second RF transceiver configured for communication, via an RF link, with the first RF transceiver, and a controller associated with the telephone, responsive to communications received from the first RF transceiver to seize a phone line, initiate, and establish a communication link over the PSTN to a remote communication link designated by the personal data access device, the controller and the program being further configured to maintain two-way communication between the personal data access device and the remote communication device via the PSTN and the RF link.
[0080] The foregoing description has been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise forms disclosed. Obvious modifications or variations are possible in light of the above teachings. The embodiment or embodiments discussed were chosen and described to provide the best illustration of the principles of the invention and its practical application to thereby enable one of ordinary skill in the art to utilize the invention in various embodiments and with various modifications as are suited to the particular use contemplated. All such modifications and variations are within the scope of the invention as determined by the appended claims when interpreted in accordance with the breadth to which they are fairly and legally entitled.
Claims
What is claimed is:
1. A system for communicating with a remote communication unit via a public switched telephone network (PSTN), comprising:
a personal data access device executing a program that is to communicate with the remote communication unit via the PSTN;
a first radio frequency (RF) transceiver associated with the personal data access device and in communication with the program, wherein the first RF transceiver is controlled by the program;
a public, pay-type telephone, electrically connected for communication over the PSTN;
a second RF transceiver interfaced with the telephone, the second RF transceiver configured for communication, via an RF link, with the first RF transceiver; and
a controller interfaced with the telephone, responsive to communications received from the first RF transceiver to communicate over a data communication link via the PSTN to the remote communication unit designated by the personal data access device, the controller being configured to allow data communications over the PSTN, the controller and the program being further configured to maintain two-way communication between the personal data access device and the remote communication unit via the PSTN and the RF link, and the controller being further configured to terminate the data communication link over the PSTN to the remote communication unit designated by the personal data access device, wherein responsive to receiving from the first RF transceiver a termination communication that originated from the program, the controller terminates the data communication link.
2. The system as defined in claim 1, wherein the personal data access device is a device selected from the group consisting of: a desktop computer, a laptop computer, a hand-held computing device, a portable handset, and a palm-corder.
3. The system as defined in claim 2, wherein the portable handset digitizes an analog voice signal into data packets, and the public, pay-type telephone relays the data packets to the remote communication unit.
4. The system as defined in claim 1, further including:
a second public, pay-type telephone, electrically connected for communication over the PSTN;
a third RF transceiver interfaced with the second telephone, the third RF transceiver configured for communication, via an RF link, with the first RF transceiver; and
circuitry associated with the first RF transceiver to monitor a signal link strength of a current communication with the second RF transceiver and the signal link strength of the third RF transceiver;
wherein the first RF transceiver is configured to transfer the current communication to the third RF transceiver based on the signal link strength.
5. The system as defined in claim 1, wherein the controller and second RF transceiver are interfaced to the public, pay-type telephone through an interface selected from the group consisting of: a wired and a wireless connection.
6. The system as defined in claim 1, wherein the controller and second RF transceiver are located outside the pay-phone in a separate module.
7. The system as defined in claim 1, wherein the public, pay-type telephone includes a digital subscriber line (DSL) modem for communicating data between the PSTN and the second RF transceiver.
8. The system as defined in claim 1, wherein the controller is further configured to allow simultaneous voice and data communication over the PSTN.
9. A system for communicating with a remote communication unit via a public switched telephone network (PSTN), comprising:
a personal data access device having a first radio frequency (RF) transceiver;
a communication device for communication over the PSTN;
a second RF transceiver interfaced with the communication device, the second RF transceiver configured for communication with the first RF transceiver via an RF link; and
a controller associated with the communication device, responsive to communications received from the first RF transceiver to communicate over a phone line via the PSTN and maintain two-way communication between the personal data access device and the remote communication unit via the PSTN and the RF link, the controller being configured to allow data communications over the PSTN and being configured to terminate the communication between the personal data access device and the remote communication unit, wherein responsive to receiving from the first RF transceiver a termination message, the controller terminates the communication between the personal data access device and the remote communication unit.
10. The system of claim 9, wherein the remote communication unit provides access to a network, wherein the network is selected from the group consisting of: a wide area network (WAN), a local area network (LAN), an Intranet, and the Internet.
11. The system of claim 9, wherein the first and second RF transceiver communicate over the RF link using a protocol selected from the group consisting of: single channel frequency hopping, multi-channel frequency hopping, and direct sequence spread spectrum.
12. The system of claim 9, wherein the controller and second RF transceiver are located outside of the communications device in a separate module.
13. The system of claim 9, further including a second personal data access device having a fourth radio frequency (RF) transceiver;
wherein the second RF transceiver interfaced with the communication device is configured to maintain communications with the second RF transceiver and the fourth RF transceiver simultaneously.
14. The system of claim 9, wherein the first radio frequency (RF) transceiver is integrated into a Personal Computer Memory Card International Association (PCMCIA) card.
15. The system of claim 9, wherein the communications device is located inside a stationary device, wherein the stationary device selected from the group consisting of: an electric sign or a billboard.
16. The system as defined in claim 9, wherein the personal data access device is a portable handset configured to transmit digitized voice signals between to the first RF transceiver and the second RF transceiver.
17. The system as defined in claim 9, wherein the communications device includes a digital subscriber line (DSL) modem for communicating data between the PSTN and the second RF transceiver.
18. The system as defined in claim 9, wherein the controller is further configured to allow simultaneous voice and data communication over the PSTN.
19. A system for communicating with a remote communication unit via a public switched telephone network (PSTN), comprising:
a personal data access device executing a program that is to communicate with the remote communication unit via the PSTN;
a first radio frequency (RF) transceiver associated with the personal data access device and in communication with the program, wherein the first RF transceiver is controlled by the program;
a communications device electrically connected for communication over the PSTN;
a second RF transceiver interfaced with the communications device, the second RF transceiver configured for communication, via an RF link, with the first RF transceiver; and
a controller interfaced with the communications device, responsive to communications received from the first RF transceiver to communicate over a data communication link via the PSTN to the remote communication unit designated by the personal data access device, the controller being configured to allow data communications over the PSTN, the controller and the program being further configured to maintain two-way communication between the personal data access device and the remote communication unit via the PSTN and the RF link, and the controller being further configured to terminate the data communication link over the PSTN to the remote communication unit designated by the personal data access device, wherein responsive to receiving from the first RF transceiver a termination communication that originated from the program, the controller terminates the data communication link.
20. The system as defined in claim 19, wherein the communications device is a device selected from the group consisting of: a node, a public pay-type telephone, a telephone, and a DSL modem.
21. The system as defined in claim 19, wherein the controller is further configured to allow simultaneous voice and data communication over the PSTN.
Patent Citations (555)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US3665475(A) | 1972-05-01 | Gram | Applicant |
| US3705385(A) | 1972-12-01 | Batz | Applicant |
| US3723876(A) | 1973-03-01 | Seaborn, Jr. | Applicant |
| US3742142(A) | 1973-06-01 | Martin | Applicant |
| US3848231(A) | 1974-11-01 | Wooten | Applicant |
| US3892948(A) | 1975-07-01 | Constable | Applicant |
| US3906460(A) | 1975-09-01 | Halpern | Applicant |
| US3914692(A) | 1975-10-01 | Seaborn, Jr. | Applicant |
| US3922492(A) | 1975-11-01 | Lumsden | Applicant |
| US3925763(A) | 1975-12-01 | Wadwhani et al. | Applicant |
| US4025315(A) | 1977-05-01 | Mazelli | Applicant |
| US4056684(A) | 1977-11-01 | Lindstrom | Applicant |
| US4083003(A) | 1978-04-01 | Haemmig | Applicant |
| US4120452(A) | 1978-10-01 | Kimura et al. | Applicant |
| US4124839(A) | 1978-11-01 | Cohen | Applicant |
| US4135181(A) | 1979-01-01 | Bogacki et al. | Applicant |
| US4204195(A) | 1980-05-01 | Bogacki | Applicant |
| US4213119(A) | 1980-07-01 | Ward et al. | Applicant |
| US4277837(A) | 1981-07-01 | Stuckert | Applicant |
| US4354181(A) | 1982-10-01 | Spletzer | Applicant |
| US4396910(A) | 1983-08-01 | Enemark et al. | Applicant |
| US4396915(A) | 1983-08-01 | Farnsworth et al. | Applicant |
| US4417450(A) | 1983-11-01 | Morgan, Jr. et al. | Applicant |
| US4436957(A) | 1984-03-01 | Mazza | Applicant |
| US4446454(A) | 1984-05-01 | Pyle | Applicant |
| US4454414(A) | 1984-06-01 | Benton | Applicant |
| US4468656(A) | 1984-08-01 | Clifford et al. | Applicant |
| US4488152(A) | 1984-12-01 | Arnason et al. | Applicant |
| US4495496(A) | 1985-01-01 | Miller, III | Applicant |
| US4551719(A) | 1985-11-01 | Carlin et al. | Applicant |
| US4611198(A) | 1986-09-01 | Levinson et al. | Applicant |
| US4621263(A) | 1986-11-01 | Takenaka et al. | Applicant |
| US4630035(A) | 1986-12-01 | Stahl et al. | Applicant |
| US4631357(A) | 1986-12-01 | Grunig | Applicant |
| US4670739(A) | 1987-06-01 | Kelly, Jr. | Applicant |
| US4707852(A) | 1987-11-01 | Jahr et al. | Applicant |
| US4731810(A) | 1988-03-01 | Watkins | Applicant |
| US4742296(A) | 1988-05-01 | Petr et al. | Applicant |
| US4757185(A) | 1988-07-01 | Onishi | Applicant |
| US4800543(A) | 1989-01-01 | Lyndon-James et al. | Applicant |
| US4825457(A) | 1989-04-01 | Lebowitz | Applicant |
| US4829561(A) | 1989-05-01 | Matheny | Examiner |
| US4849815(A) | 1989-07-01 | Streck | Applicant |
| US4851654(A) | 1989-07-01 | Nitta | Applicant |
| US4856046(A) | 1989-08-01 | Streck et al. | Examiner |
| US4857912(A) | 1989-08-01 | Everett, Jr. et al. | Applicant |
| US4875231(A) | 1989-10-01 | Hara et al. | Applicant |
| US4884132(A) | 1989-11-01 | Morris et al. | Applicant |
| US4897644(A) | 1990-01-01 | Hirano | Applicant |
| US4906828(A) | 1990-03-01 | Halpern | Applicant |
| US4908769(A) | 1990-03-01 | Vaughan et al. | Applicant |
| US4918690(A) | 1990-04-01 | Markkula, Jr. et al. | Applicant |
| US4918995(A) | 1990-04-01 | Pearman et al. | Applicant |
| US4928299(A) | 1990-05-01 | Tansky et al. | Applicant |
| US4940976(A) | 1990-07-01 | Gastouniotis et al. | Applicant |
| US4949077(A) | 1990-08-01 | Mbuthia | Applicant |
| US4952928(A) | 1990-08-01 | Carroll et al. | Applicant |
| US4962496(A) | 1990-10-01 | Vercellotti et al. | Applicant |
| US4967366(A) | 1990-10-01 | Kaehler | Applicant |
| US4968970(A) | 1990-11-01 | LaPorte | Applicant |
| US4968978(A) | 1990-11-01 | Stolarczyk | Applicant |
| US4972504(A) | 1990-11-01 | Daniel, Jr. et al. | Applicant |
| US4973957(A) | 1990-11-01 | Shimizu et al. | Applicant |
| US4973970(A) | 1990-11-01 | Reeser | Applicant |
| US4977612(A) | 1990-12-01 | Wilson | Applicant |
| US4980907(A) | 1990-12-01 | Raith et al. | Applicant |
| US4989230(A) | 1991-01-01 | Gillig et al. | Applicant |
| US4991008(A) | 1991-02-01 | Nama | Applicant |
| US4998095(A) | 1991-03-01 | Shields | Applicant |
| US4999607(A) | 1991-03-01 | Evans | Applicant |
| US5032833(A) | 1991-07-01 | Laporte | Applicant |
| US5038372(A) | 1991-08-01 | Elms et al. | Applicant |
| US5055851(A) | 1991-10-01 | Sheffer | Applicant |
| US5057814(A) | 1991-10-01 | Onan et al. | Applicant |
| US5061997(A) | 1991-10-01 | Rea et al. | Applicant |
| US5086391(A) | 1992-02-01 | Chambers | Applicant |
| US5091713(A) | 1992-02-01 | Horne et al. | Applicant |
| US5111199(A) | 1992-05-01 | Tomoda et al. | Applicant |
| US5113183(A) | 1992-05-01 | Mizuno et al. | Applicant |
| US5113184(A) | 1992-05-01 | Katayama | Applicant |
| US5115224(A) | 1992-05-01 | Kostusiak et al. | Applicant |
| US5115433(A) | 1992-05-01 | Baran et al. | Applicant |
| US5124624(A) | 1992-06-01 | de Vries et al. | Applicant |
| US5128855(A) | 1992-07-01 | Hilber et al. | Applicant |
| US5130519(A) | 1992-07-01 | Bush et al. | Applicant |
| US5131038(A) | 1992-07-01 | Puhl et al. | Applicant |
| US5134650(A) | 1992-07-01 | Blackmon | Applicant |
| US5136285(A) | 1992-08-01 | Okuyama | Applicant |
| US5155481(A) | 1992-10-01 | Brennan, Jr. et al. | Applicant |
| US5159317(A) | 1992-10-01 | Brav | Applicant |
| US5162776(A) | 1992-11-01 | Bushnell et al. | Applicant |
| US5177342(A) | 1993-01-01 | Adams | Applicant |
| US5189287(A) | 1993-02-01 | Parienti | Applicant |
| US5191192(A) | 1993-03-01 | Takahira et al. | Applicant |
| US5191326(A) | 1993-03-01 | Montgomery | Applicant |
| US5193111(A) | 1993-03-01 | Matty et al. | Applicant |
| US5195018(A) | 1993-03-01 | Kwon et al. | Applicant |
| US5197095(A) | 1993-03-01 | Bonnet et al. | Applicant |
| US5200735(A) | 1993-04-01 | Hines | Applicant |
| US5204670(A) | 1993-04-01 | Stinton | Applicant |
| US5212645(A) | 1993-05-01 | Wildes et al. | Applicant |
| US5216502(A) | 1993-06-01 | Katz | Applicant |
| US5221838(A) | 1993-06-01 | Gutman et al. | Applicant |
| US5223844(A) | 1993-06-01 | Mansell et al. | Applicant |
| US5231658(A) | 1993-07-01 | Eftechiou | Applicant |
| US5235630(A) | 1993-08-01 | Moody et al. | Applicant |
| US5239575(A) | 1993-08-01 | White et al. | Applicant |
| US5241410(A) | 1993-08-01 | Streck et al. | Examiner |
| US5243338(A) | 1993-09-01 | Brennan, Jr. et al. | Applicant |
| US5245633(A) | 1993-09-01 | Schwartz et al. | Applicant |
| US5252967(A) | 1993-10-01 | Brennan et al. | Applicant |
| US5253167(A) | 1993-10-01 | Yoshida et al. | Applicant |
| US5265150(A) | 1993-11-01 | Heimkamp et al. | Applicant |
| US5265162(A) | 1993-11-01 | Bush et al. | Applicant |
| US5266782(A) | 1993-11-01 | Alanara et al. | Applicant |
| US5272747(A) | 1993-12-01 | Meads | Applicant |
| US5282204(A) | 1994-01-01 | Shpancer et al. | Applicant |
| US5282250(A) | 1994-01-01 | Dent et al. | Applicant |
| US5289165(A) | 1994-02-01 | Belin | Applicant |
| US5295154(A) | 1994-03-01 | Meier et al. | Applicant |
| US5305370(A) | 1994-04-01 | Kearns et al. | Applicant |
| US5315645(A) | 1994-05-01 | Matheny | Examiner |
| US5317309(A) | 1994-05-01 | Vercellotti et al. | Applicant |
| US5319364(A) | 1994-06-01 | Waraksa et al. | Applicant |
| US5319698(A) | 1994-06-01 | Glidwell et al. | Applicant |
| US5319711(A) | 1994-06-01 | Servi | Applicant |
| US5323384(A) | 1994-06-01 | Norwood et al. | Applicant |
| US5325429(A) | 1994-06-01 | Kurgan | Applicant |
| US5331318(A) | 1994-07-01 | Montgomery | Applicant |
| US5334974(A) | 1994-08-01 | Simms et al. | Applicant |
| US5343493(A) | 1994-08-01 | Karimullah | Applicant |
| US5345231(A) | 1994-09-01 | Koo et al. | Applicant |
| US5347263(A) | 1994-09-01 | Carroll et al. | Applicant |
| US5354974(A) | 1994-10-01 | Eisenberg | Applicant |
| US5355513(A) | 1994-10-01 | Clarke et al. | Applicant |
| US5365217(A) | 1994-11-01 | Toner | Applicant |
| US5371736(A) | 1994-12-01 | Evan | Applicant |
| US5382778(A) | 1995-01-01 | Takahira et al. | Applicant |
| US5383134(A) | 1995-01-01 | Wrzesinski | Applicant |
| US5406619(A) | 1995-04-01 | Akhteruzzman et al. | Applicant |
| US5412192(A) | 1995-05-01 | Hoss | Applicant |
| US5412760(A) | 1995-05-01 | Peitz | Applicant |
| US5416475(A) | 1995-05-01 | Tolbert et al. | Applicant |
| US5416725(A) | 1995-05-01 | Pacheco et al. | Applicant |
| US5418812(A) | 1995-05-01 | Reyes et al. | Applicant |
| US5424708(A) | 1995-06-01 | Ballestry et al. | Applicant |
| US5432507(A) | 1995-07-01 | Mussino et al. | Applicant |
| US5438329(A) | 1995-08-01 | Gastouniotis et al. | Applicant |
| US5439414(A) | 1995-08-01 | Jacob | Applicant |
| US5442553(A) | 1995-08-01 | Parrillo | Applicant |
| US5445287(A) | 1995-08-01 | Center et al. | Applicant |
| US5451929(A) | 1995-09-01 | Adelman et al. | Applicant |
| US5451938(A) | 1995-09-01 | Brennan, Jr. | Applicant |
| US5452344(A) | 1995-09-01 | Larson | Applicant |
| US5465401(A) | 1995-11-01 | Thompson | Applicant |
| US5467074(A) | 1995-11-01 | Pedtke | Applicant |
| US5467082(A) | 1995-11-01 | Sanderson | Applicant |
| US5467345(A) | 1995-11-01 | Cutler et al. | Applicant |
| US5468948(A) | 1995-11-01 | Koenck et al. | Applicant |
| US5471201(A) | 1995-11-01 | Cerami et al. | Applicant |
| US5473322(A) | 1995-12-01 | Carney | Applicant |
| US5475689(A) | 1995-12-01 | Kay et al. | Applicant |
| US5481259(A) | 1996-01-01 | Bane | Applicant |
| US5484997(A) | 1996-01-01 | Haynes | Applicant |
| US5493273(A) | 1996-02-01 | Smurlo et al. | Applicant |
| US5493287(A) | 1996-02-01 | Bane | Applicant |
| US5506837(A) | 1996-04-01 | Sollner et al. | Applicant |
| US5509073(A) | 1996-04-01 | Monnin | Applicant |
| US5513244(A) | 1996-04-01 | Joao et al. | Applicant |
| US5515419(A) | 1996-05-01 | Sheffer | Applicant |
| US5517188(A) | 1996-05-01 | Caroll et al. | Applicant |
| US5522089(A) | 1996-05-01 | Kikinis et al. | Applicant |
| US5528215(A) | 1996-06-01 | Siu et al. | Applicant |
| US5539825(A) | 1996-07-01 | Akiyama et al. | Applicant |
| US5541938(A) | 1996-07-01 | Di Zenzo et al. | Applicant |
| US5542100(A) | 1996-07-01 | Hatakeyama | Applicant |
| US5544036(A) | 1996-08-01 | Brown, Jr. et al. | Applicant |
| US5544784(A) | 1996-08-01 | Malaspina | Applicant |
| US5548632(A) | 1996-08-01 | Walsh et al. | Applicant |
| US5550358(A) | 1996-08-01 | Tait et al. | Applicant |
| US5550359(A) | 1996-08-01 | Bennett | Applicant |
| US5550535(A) | 1996-08-01 | Park | Applicant |
| US5553094(A) | 1996-09-01 | Johnson et al. | Applicant |
| US5555258(A) | 1996-09-01 | Snelling et al. | Applicant |
| US5555286(A) | 1996-09-01 | Tendler | Applicant |
| US5562537(A) | 1996-10-01 | Zver et al. | Applicant |
| US5565857(A) | 1996-10-01 | Lee | Applicant |
| US5572438(A) | 1996-11-01 | Ehlers et al. | Applicant |
| US5573181(A) | 1996-11-01 | Ahmed | Applicant |
| US5574111(A) | 1996-11-01 | Brichta et al. | Applicant |
| US5583850(A) | 1996-12-01 | Snodgrass et al. | Applicant |
| US5587705(A) | 1996-12-01 | Morris | Applicant |
| US5589878(A) | 1996-12-01 | Cortjens et al. | Applicant |
| US5590038(A) | 1996-12-01 | Pitroda | Applicant |
| US5590179(A) | 1996-12-01 | Shincovich et al. | Applicant |
| US5592491(A) | 1997-01-01 | Dinks | Applicant |
| US5594431(A) | 1997-01-01 | Sheppard et al. | Applicant |
| US5602843(A) | 1997-02-01 | Gray | Applicant |
| US5604414(A) | 1997-02-01 | Milligan et al. | Applicant |
| US5604869(A) | 1997-02-01 | Mincher et al. | Applicant |
| US5606361(A) | 1997-02-01 | Davidsohn et al. | Applicant |
| US5608786(A) | 1997-03-01 | Gordon | Applicant |
| US5613620(A) | 1997-03-01 | Center et al. | Applicant |
| US5615277(A) | 1997-03-01 | Hoffman | Applicant |
| US5619192(A) | 1997-04-01 | Ayala | Applicant |
| US5625410(A) | 1997-04-01 | Washino et al. | Applicant |
| US5628050(A) | 1997-05-01 | McGraw et al. | Applicant |
| US5629687(A) | 1997-05-01 | Sutton et al. | Applicant |
| US5629875(A) | 1997-05-01 | Adair, Jr. | Applicant |
| US5630209(A) | 1997-05-01 | Wizgall et al. | Applicant |
| US5631554(A) | 1997-05-01 | Briese et al. | Applicant |
| US5644294(A) | 1997-07-01 | Ness | Applicant |
| US5655219(A) | 1997-08-01 | Jusa et al. | Applicant |
| US5657389(A) | 1997-08-01 | Houvener | Applicant |
| US5659300(A) | 1997-08-01 | Dresselhuys et al. | Applicant |
| US5659303(A) | 1997-08-01 | Adair, Jr. | Applicant |
| US5668876(A) | 1997-09-01 | Falk et al. | Applicant |
| US5673252(A) | 1997-09-01 | Johnson et al. | Applicant |
| US5673304(A) | 1997-09-01 | Connor et al. | Applicant |
| US5673305(A) | 1997-09-01 | Ross | Applicant |
| US5682139(A) | 1997-10-01 | Pradeep et al. | Applicant |
| US5682476(A) | 1997-10-01 | Tapperson et al. | Applicant |
| US5689229(A) | 1997-11-01 | Chaco et al. | Applicant |
| US5699328(A) | 1997-12-01 | Ishizaki et al. | Applicant |
| US5701002(A) | 1997-12-01 | Oishi et al. | Applicant |
| US5704046(A) | 1997-12-01 | Hogan | Applicant |
| US5704517(A) | 1998-01-01 | Lancaster, Jr. | Applicant |
| US5706191(A) | 1998-01-01 | Bassett et al. | Applicant |
| US5706976(A) | 1998-01-01 | Purkey | Applicant |
| US5708223(A) | 1998-01-01 | Wyss | Applicant |
| US5708655(A) | 1998-01-01 | Toth | Applicant |
| US5712619(A) | 1998-01-01 | Simkin | Applicant |
| US5712980(A) | 1998-01-01 | Beeler et al. | Applicant |
| US5714931(A) | 1998-02-01 | Petite et al. | Applicant |
| US5717718(A) | 1998-02-01 | Roswell et al. | Applicant |
| US5726634(A) | 1998-03-01 | Hess et al. | Applicant |
| US5726984(A) | 1998-03-01 | Kubler et al. | Applicant |
| US5732074(A) | 1998-03-01 | Spaur et al. | Applicant |
| US5732078(A) | 1998-03-01 | Arango | Applicant |
| US5736965(A) | 1998-04-01 | Mosebrook et al. | Applicant |
| US5740232(A) | 1998-04-01 | Pailles et al. | Applicant |
| US5742509(A) | 1998-04-01 | Goldberg et al. | Applicant |
| US5745849(A) | 1998-04-01 | Britton | Applicant |
| US5748104(A) | 1998-05-01 | Argyroudis et al. | Applicant |
| US5748619(A) | 1998-05-01 | Meier | Applicant |
| US5754111(A) | 1998-05-01 | Garcia | Applicant |
| US5754227(A) | 1998-05-01 | Fukuoka | Applicant |
| US5757783(A) | 1998-05-01 | Eng et al. | Applicant |
| US5757788(A) | 1998-05-01 | Tatsumi et al. | Applicant |
| US5761083(A) | 1998-06-01 | Brown, Jr. et al. | Applicant |
| US5764742(A) | 1998-06-01 | Howard et al. | Applicant |
| US5771274(A) | 1998-06-01 | Harris | Applicant |
| US5774052(A) | 1998-06-01 | Hamm et al. | Applicant |
| US5781143(A) | 1998-07-01 | Rossin | Applicant |
| US5790644(A) | 1998-08-01 | Kikinis | Examiner |
| US5790662(A) | 1998-08-01 | Valerij et al. | Applicant |
| US5790938(A) | 1998-08-01 | Talarmo | Applicant |
| US5796727(A) | 1998-08-01 | Harrison et al. | Applicant |
| US5798964(A) | 1998-08-01 | Shimizu et al. | Applicant |
| US5801643(A) | 1998-09-01 | Williams et al. | Applicant |
| US5815505(A) | 1998-09-01 | Mills | Examiner |
| US5818822(A) | 1998-10-01 | Thomas et al. | Applicant |
| US5822273(A) | 1998-10-01 | Bary et al. | Applicant |
| US5822544(A) | 1998-10-01 | Chaco et al. | Applicant |
| US5826195(A) | 1998-10-01 | Westerlage et al. | Applicant |
| US5828044(A) | 1998-10-01 | Jun et al. | Applicant |
| US5832057(A) | 1998-11-01 | Furman | Applicant |
| US5838223(A) | 1998-11-01 | Gallant et al. | Applicant |
| US5838237(A) | 1998-11-01 | Revell et al. | Applicant |
| US5838812(A) | 1998-11-01 | Pare, Jr. et al. | Applicant |
| US5841118(A) | 1998-11-01 | East et al. | Applicant |
| US5841764(A) | 1998-11-01 | Roderique et al. | Applicant |
| US5842976(A) | 1998-12-01 | Williamson | Applicant |
| US5844808(A) | 1998-12-01 | Konsmo et al. | Applicant |
| US5845230(A) | 1998-12-01 | Lamberson | Applicant |
| US5852658(A) | 1998-12-01 | Knight et al. | Applicant |
| US5854994(A) | 1998-12-01 | Canada et al. | Applicant |
| US5862201(A) | 1999-01-01 | Sands | Applicant |
| US5864772(A) | 1999-01-01 | Alvarado et al. | Applicant |
| US5873043(A) | 1999-02-01 | Comer | Applicant |
| US5874903(A) | 1999-02-01 | Shuey et al. | Applicant |
| US5880677(A) | 1999-03-01 | Lestician | Applicant |
| US5884184(A) | 1999-03-01 | Sheffer | Applicant |
| US5884271(A) | 1999-03-01 | Pitroda | Applicant |
| US5886333(A) | 1999-03-01 | Miyake | Applicant |
| US5889468(A) | 1999-03-01 | Banga | Applicant |
| US5892690(A) | 1999-04-01 | Boatman et al. | Applicant |
| US5892758(A) | 1999-04-01 | Argyroudis | Applicant |
| US5892924(A) | 1999-04-01 | Lyon et al. | Applicant |
| US5896097(A) | 1999-04-01 | Cardozo | Applicant |
| US5897607(A) | 1999-04-01 | Jenney et al. | Applicant |
| US5898369(A) | 1999-04-01 | Godwin | Applicant |
| US5905438(A) | 1999-05-01 | Weiss et al. | Applicant |
| US5907291(A) | 1999-05-01 | Chen et al. | Applicant |
| US5907491(A) | 1999-05-01 | Canada et al. | Applicant |
| US5907540(A) | 1999-05-01 | Hayashi | Applicant |
| US5907807(A) | 1999-05-01 | Chavez, Jr. et al. | Applicant |
| US5914672(A) | 1999-06-01 | Glorioso et al. | Applicant |
| US5914673(A) | 1999-06-01 | Jennings et al. | Applicant |
| US5917405(A) | 1999-06-01 | Joao | Applicant |
| US5917629(A) | 1999-06-01 | Hortensius et al. | Applicant |
| US5923269(A) | 1999-07-01 | Shuey et al. | Applicant |
| US5926103(A) | 1999-07-01 | Petite | Applicant |
| US5926529(A) | 1999-07-01 | Hache et al. | Applicant |
| US5926531(A) | 1999-07-01 | Petite | Applicant |
| US5933073(A) | 1999-08-01 | Shuey | Applicant |
| US5941363(A) | 1999-08-01 | Partyka et al. | Applicant |
| US5948040(A) | 1999-09-01 | DeLorme et al. | Applicant |
| US5949779(A) | 1999-09-01 | Mostafa et al. | Applicant |
| US5949799(A) | 1999-09-01 | Grivna et al. | Applicant |
| US5953371(A) | 1999-09-01 | Roswell et al. | Applicant |
| US5955718(A) | 1999-09-01 | Levasseur et al. | Applicant |
| US5960074(A) | 1999-09-01 | Clark | Applicant |
| US5963146(A) | 1999-10-01 | Johnson et al. | Applicant |
| US5963452(A) | 1999-10-01 | Etoh et al. | Applicant |
| US5963650(A) | 1999-10-01 | Simionescu et al. | Applicant |
| US5969608(A) | 1999-10-01 | Sojdehei et al. | Applicant |
| US5973756(A) | 1999-10-01 | Erlin | Applicant |
| US5978364(A) | 1999-11-01 | Melnik | Applicant |
| US5978371(A) | 1999-11-01 | Mason, Jr. et al. | Applicant |
| US5986574(A) | 1999-11-01 | Colton | Applicant |
| US5987421(A) | 1999-11-01 | Chuang | Applicant |
| US5991639(A) | 1999-11-01 | Rautiola et al. | Applicant |
| US5994892(A) | 1999-11-01 | Turino et al. | Applicant |
| US5995592(A) | 1999-11-01 | Shirai et al. | Examiner |
| US5995593(A) | 1999-11-01 | Cho | Examiner |
| US5997170(A) | 1999-12-01 | Brodbeck | Applicant |
| US5999094(A) | 1999-12-01 | Nilssen | Applicant |
| US6005759(A) | 1999-12-01 | Hart et al. | Applicant |
| US6005963(A) | 1999-12-01 | Bolle et al. | Applicant |
| US6021664(A) | 2000-02-01 | Granato et al. | Applicant |
| US6023223(A) | 2000-02-01 | Baxter, Jr. | Applicant |
| US6028522(A) | 2000-02-01 | Petite | Applicant |
| US6028857(A) | 2000-02-01 | Poor | Applicant |
| US6031455(A) | 2000-02-01 | Grube et al. | Applicant |
| US6032197(A) | 2000-02-01 | Birdwell et al. | Applicant |
| US6035266(A) | 2000-03-01 | Williams et al. | Applicant |
| US6036086(A) | 2000-03-01 | Sizer, II et al. | Applicant |
| US6038491(A) | 2000-03-01 | McGarry et al. | Applicant |
| US6044062(A) | 2000-03-01 | Brownrigg et al. | Applicant |
| US6054920(A) | 2000-04-01 | Smith et al. | Applicant |
| US6060994(A) | 2000-05-01 | Chen | Applicant |
| US6061604(A) | 2000-05-01 | Russ et al. | Applicant |
| US6064318(A) | 2000-05-01 | Kirchner, III et al. | Applicant |
| US6067030(A) | 2000-05-01 | Burnett et al. | Applicant |
| US6069886(A) | 2000-05-01 | Ayerst et al. | Applicant |
| US6073169(A) | 2000-06-01 | Shuey et al. | Applicant |
| US6073266(A) | 2000-06-01 | Ahmed et al. | Applicant |
| US6073840(A) | 2000-06-01 | Marion | Applicant |
| US6075451(A) | 2000-06-01 | Lebowitz et al. | Applicant |
| US6087957(A) | 2000-07-01 | Gray | Applicant |
| US6088659(A) | 2000-07-01 | Kelley et al. | Applicant |
| US6094622(A) | 2000-07-01 | Hubbard et al. | Applicant |
| US6100817(A) | 2000-08-01 | Mason, Jr. et al. | Applicant |
| US6101427(A) | 2000-08-01 | Yang | Applicant |
| US6101445(A) | 2000-08-01 | Alvarado et al. | Applicant |
| US6112983(A) | 2000-09-01 | D'Anniballe et al. | Applicant |
| US6119076(A) | 2000-09-01 | Williams et al. | Applicant |
| US6121593(A) | 2000-09-01 | Mansbery et al. | Applicant |
| US6121885(A) | 2000-09-01 | Masone et al. | Applicant |
| US6124806(A) | 2000-09-01 | Cunningham et al. | Applicant |
| US6127917(A) | 2000-10-01 | Tuttle | Applicant |
| US6128551(A) | 2000-10-01 | Davis et al. | Applicant |
| US6130622(A) | 2000-10-01 | Hussey et al. | Applicant |
| US6133850(A) | 2000-10-01 | Moore | Applicant |
| US6137423(A) | 2000-10-01 | Glorioso et al. | Applicant |
| US6140975(A) | 2000-10-01 | Cohen | Applicant |
| US6141347(A) | 2000-10-01 | Shaughnessy et al. | Applicant |
| US6150936(A) | 2000-11-01 | Addy | Applicant |
| US6150955(A) | 2000-11-01 | Tracy et al. | Applicant |
| US6157464(A) | 2000-12-01 | Bloomfield et al. | Applicant |
| US6157824(A) | 2000-12-01 | Bailey | Applicant |
| US6163276(A) | 2000-12-01 | Irving et al. | Applicant |
| US6172616(B1) | 2001-01-01 | Johnson et al. | Applicant |
| US6174205(B1) | 2001-01-01 | Madsen et al. | Applicant |
| US6175922(B1) | 2001-01-01 | Wang | Applicant |
| US6177883(B1) | 2001-01-01 | Jennetti et al. | Applicant |
| US6181255(B1) | 2001-01-01 | Crimmins et al. | Applicant |
| US6181284(B1) | 2001-01-01 | Madsen et al. | Applicant |
| US6181981(B1) | 2001-01-01 | Varga et al. | Applicant |
| US6188354(B1) | 2001-02-01 | Soliman et al. | Applicant |
| US6192390(B1) | 2001-02-01 | Berger et al. | Applicant |
| US6198390(B1) | 2001-03-01 | Schlager et al. | Applicant |
| US6199068(B1) | 2001-03-01 | Carpenter | Applicant |
| US6208266(B1) | 2001-03-01 | Lyons et al. | Applicant |
| US6215404(B1) | 2001-04-01 | Morales | Applicant |
| US6218953(B1) | 2001-04-01 | Petite | Applicant |
| US6218983(B1) | 2001-04-01 | Kerry et al. | Applicant |
| US6219409(B1) | 2001-04-01 | Smith et al. | Applicant |
| US6229439(B1) | 2001-05-01 | Tice | Applicant |
| US6233327(B1) | 2001-05-01 | Petite | Applicant |
| US6234111(B1) | 2001-05-01 | Ulman et al. | Applicant |
| US6236332(B1) | 2001-05-01 | Conkright et al. | Applicant |
| US6243010(B1) | 2001-06-01 | Addy et al. | Applicant |
| US6246677(B1) | 2001-06-01 | Nap et al. | Applicant |
| US6249516(B1) | 2001-06-01 | Brownrigg et al. | Applicant |
| US6259369(B1) | 2001-07-01 | Monico | Applicant |
| US6286756(B1) | 2001-09-01 | Stinson et al. | Applicant |
| US6288634(B1) | 2001-09-01 | Weiss et al. | Applicant |
| US6288641(B1) | 2001-09-01 | Carsais | Applicant |
| US6295291(B1) | 2001-09-01 | Larkins | Applicant |
| US6301514(B1) | 2001-10-01 | Canada et al. | Applicant |
| US6305602(B1) | 2001-10-01 | Grabowski et al. | Applicant |
| US6308111(B1) | 2001-10-01 | Koga | Applicant |
| US6311167(B1) | 2001-10-01 | Davis et al. | Applicant |
| US6314169(B1) | 2001-11-01 | Schelberg, Jr. et al. | Applicant |
| US6317029(B1) | 2001-11-01 | Fleeter | Applicant |
| US6334117(B1) | 2001-12-01 | Covert et al. | Applicant |
| US6351223(B1) | 2002-02-01 | DeWeerd et al. | Applicant |
| US6356205(B1) | 2002-03-01 | Salvo et al. | Applicant |
| US6357034(B1) | 2002-03-01 | Muller et al. | Applicant |
| US6362745(B1) | 2002-03-01 | Davis | Applicant |
| US6363057(B1) | 2002-03-01 | Ardalan et al. | Applicant |
| US6366217(B1) | 2002-04-01 | Cunningham et al. | Applicant |
| US6369769(B1) | 2002-04-01 | Nap et al. | Applicant |
| US6370489(B1) | 2002-04-01 | Williams et al. | Applicant |
| US6373399(B1) | 2002-04-01 | Johnson et al. | Applicant |
| US6380851(B1) | 2002-04-01 | Gilbert et al. | Applicant |
| US6384722(B1) | 2002-05-01 | Williams | Applicant |
| US6393341(B1) | 2002-05-01 | Lawrence et al. | Applicant |
| US6393381(B1) | 2002-05-01 | Williams et al. | Applicant |
| US6393382(B1) | 2002-05-01 | Williams et al. | Applicant |
| US6396839(B1) | 2002-05-01 | Ardalan et al. | Applicant |
| US6400819(B1) | 2002-06-01 | Nakano et al. | Applicant |
| US6401081(B1) | 2002-06-01 | Montgomery et al. | Applicant |
| US6411889(B1) | 2002-06-01 | Mizunuma et al. | Applicant |
| US6415245(B1) | 2002-07-01 | Williams et al. | Applicant |
| US6422464(B1) | 2002-07-01 | Terranova | Applicant |
| US6424270(B1) | 2002-07-01 | Ali | Applicant |
| US6424931(B1) | 2002-07-01 | Sigmar et al. | Applicant |
| US6430268(B1) | 2002-08-01 | Petite | Applicant |
| US6431439(B1) | 2002-08-01 | Suer et al. | Applicant |
| US6437692(B1) | 2002-08-01 | Petite et al. | Applicant |
| US6438575(B1) | 2002-08-01 | Khan et al. | Applicant |
| US6445291(B1) | 2002-09-01 | Addy et al. | Applicant |
| US6456960(B1) | 2002-09-01 | Williams et al. | Applicant |
| US6457038(B1) | 2002-09-01 | Defosse | Applicant |
| US6462644(B1) | 2002-10-01 | Howell et al. | Applicant |
| US6462672(B1) | 2002-10-01 | Besson | Applicant |
| US6477558(B1) | 2002-11-01 | Irving et al. | Applicant |
| US6483290(B1) | 2002-11-01 | Hemminger et al. | Applicant |
| US6484939(B1) | 2002-11-01 | Blaeuer | Applicant |
| US6489884(B1) | 2002-12-01 | Lamberson et al. | Applicant |
| US6491828(B1) | 2002-12-01 | Sivavec et al. | Applicant |
| US6492910(B1) | 2002-12-01 | Ragle et al. | Applicant |
| US6504357(B1) | 2003-01-01 | Hemminger et al. | Applicant |
| US6507794(B1) | 2003-01-01 | Hubbard et al. | Applicant |
| US6509722(B1) | 2003-01-01 | Lopata | Applicant |
| US6519568(B1) | 2003-02-01 | Harvey et al. | Applicant |
| US6538577(B1) | 2003-03-01 | Ehrke et al. | Applicant |
| US6542076(B1) | 2003-04-01 | Joao | Applicant |
| US6542077(B1) | 2003-04-01 | Joao | Applicant |
| US6543690(B1) | 2003-04-01 | Leydier et al. | Applicant |
| US6560223(B1) | 2003-05-01 | Egan et al. | Applicant |
| US6574603(B1) | 2003-06-01 | Dickson et al. | Applicant |
| US6600726(B1) | 2003-07-01 | Nevo et al. | Applicant |
| US6608551(B1) | 2003-08-01 | Anderson et al. | Applicant |
| US6618709(B1) | 2003-09-01 | Sneeringer | Applicant |
| US6628764(B1) | 2003-09-01 | Petite | Applicant |
| US6628965(B1) | 2003-09-01 | LaRosa et al. | Applicant |
| US6653945(B1) | 2003-11-01 | Johnson et al. | Applicant |
| US6671586(B1) | 2003-12-01 | Davis et al. | Applicant |
| US6674403(B1) | 2004-01-01 | Gray et al. | Applicant |
| US6678255(B1) | 2004-01-01 | Kuriyan | Applicant |
| US6678285(B1) | 2004-01-01 | Garg | Applicant |
| US6731201(B1) | 2004-05-01 | Bailey et al. | Applicant |
| US6735630(B1) | 2004-05-01 | Gelvin et al. | Applicant |
| US6747557(B1) | 2004-06-01 | Petite et al. | Applicant |
| US6771981(B1) | 2004-08-01 | Zalewski et al. | Applicant |
| US6891838(B1) | 2005-05-01 | Petite | Applicant |
| US6914533(B1) | 2005-07-01 | Petite | Applicant |
| US6914893(B1) | 2005-07-01 | Petite | Applicant |
| US6959550(B1) | 2005-11-01 | Freeman et al. | Applicant |
| US2001/0002210(A1) | 2001-05-01 | Petite | Applicant |
| US2001/0003479(A1) | 2001-06-01 | Fujiwara | Applicant |
| US2001/0021646(A1) | 2001-09-01 | Antonucci et al. | Applicant |
| US2001/0024163(A1) | 2001-09-01 | Petite | Applicant |
| US2001/0034223(A1) | 2001-10-01 | Rieser et al. | Applicant |
| US2001/0038343(A1) | 2001-11-01 | Meyer et al. | Applicant |
| US2002/0002444(A1) | 2002-01-01 | Williams et al. | Applicant |
| US2002/0012323(A1) | 2002-01-01 | Petite | Applicant |
| US2002/0013679(A1) | 2002-01-01 | Petite | Applicant |
| US2002/0019725(A1) | 2002-02-01 | Petite | Applicant |
| US2002/0027504(A1) | 2002-03-01 | Petite | Applicant |
| US2002/0031101(A1) | 2002-03-01 | Petite | Applicant |
| US2002/0032746(A1) | 2002-03-01 | Lazaridis | Applicant |
| US2002/0072348(A1) | 2002-06-01 | Wheeler et al. | Applicant |
| US2002/0089428(A1) | 2002-07-01 | Walden et al. | Applicant |
| US2002/0095399(A1) | 2002-07-01 | Devine et al. | Applicant |
| US2002/0098858(A1) | 2002-07-01 | Struhsaker | Applicant |
| US2002/0109607(A1) | 2002-08-01 | Cumeralto et al. | Applicant |
| US2002/0158774(A1) | 2002-10-01 | Johnson et al. | Applicant |
| US2002/0163442(A1) | 2002-11-01 | Fischer | Applicant |
| US2002/0169643(A1) | 2002-11-01 | Petite | Applicant |
| US2002/0193144(A1) | 2002-12-01 | Belski et al. | Applicant |
| US2003/0001754(A1) | 2003-01-01 | Johnson et al. | Applicant |
| US2003/0028632(A1) | 2003-02-01 | Davis | Applicant |
| US2003/0030926(A1) | 2003-02-01 | Aguren et al. | Applicant |
| US2003/0034900(A1) | 2003-02-01 | Han | Applicant |
| US2003/0036822(A1) | 2003-02-01 | Davis et al. | Applicant |
| US2003/0046377(A1) | 2003-03-01 | Daum et al. | Applicant |
| US2003/0058818(A1) | 2003-03-01 | Wilkes et al. | Applicant |
| US2003/0069002(A1) | 2003-04-01 | Hunter et al. | Applicant |
| US2003/0078029(A1) | 2003-04-01 | Petite | Applicant |
| US2003/0093484(A1) | 2003-05-01 | Petite | Applicant |
| US2003/0133473(A1) | 2003-07-01 | Manis et al. | Applicant |
| US2003/0169710(A1) | 2003-09-01 | Fan et al. | Applicant |
| US2003/0185204(A1) | 2003-10-01 | Murdock | Examiner |
| US2003/0210638(A1) | 2003-11-01 | Yoo | Applicant |
| US2004/0183687(A1) | 2004-09-01 | Petite | Applicant |
| US2005/0190055(A1) | 2005-09-01 | Petite | Applicant |
| US2005/0195768(A1) | 2005-09-01 | Petite | Applicant |
| US2005/0195775(A1) | 2005-09-01 | Petite | Applicant |
| US2005/0201397(A1) | 2005-09-01 | Petite | Applicant |
| US2005/0243867(A1) | 2005-11-01 | Petite | Applicant |
| EP718954 | 1996-06-01 | Applicant | |
| EP7144 | 1998-02-01 | Applicant | |
| EP1096454 | 2001-05-01 | Applicant | |
| FR2817110 | 2002-05-01 | Applicant | |
| GB2229302 | 1990-09-01 | Applicant | |
| GB2247761 | 1992-03-01 | Applicant | |
| GB2262683 | 1993-06-01 | Applicant | |
| GB2297663 | 1996-08-01 | Applicant | |
| GB2310779 | 1997-09-01 | Applicant | |
| GB2326002 | 1998-12-01 | Applicant | |
| GB2336272 | 1999-10-01 | Applicant | |
| GB2352004 | 2001-01-01 | Applicant | |
| GB2352590 | 2001-01-01 | Applicant | |
| JP60261288 | 1985-12-01 | Applicant | |
| JP1255100 | 1989-10-01 | Applicant | |
| JP11353573 | 1999-12-01 | Applicant | |
| JP200113590 | 2000-04-01 | Applicant | |
| JP2001063425 | 2001-03-01 | Applicant | |
| JP2001088401 | 2001-04-01 | Applicant | |
| JP2001309069 | 2001-11-01 | Applicant | |
| JP2001319284 | 2001-11-01 | Applicant | |
| JP2001357483 | 2001-12-01 | Applicant | |
| JP2002007672 | 2002-01-01 | Applicant | |
| JP2002007826 | 2002-01-01 | Applicant | |
| JP2002085354 | 2002-03-01 | Applicant | |
| JP2002171354 | 2002-06-01 | Applicant | |
| KR2001025431 | 2001-04-01 | Applicant | |
| WO90/13197 | 1990-11-01 | Applicant | |
| WO98/00056 | 1998-01-01 | Applicant | |
| WO98/37528 | 1998-08-01 | Applicant | |
| WO99/13426 | 1999-03-01 | Applicant | |
| WO1/15114 | 2000-08-01 | Applicant | |
| WO1/24109 | 2001-04-01 | Applicant | |
| WO2/08725 | 2002-01-01 | Applicant | |
| WO2/08866 | 2002-01-01 | Applicant | |
| WO2/052521 | 2002-07-01 | Applicant | |
| WO2/052521 | 2002-07-01 | Applicant | |
| WO3/007264 | 2003-01-01 | Applicant | |
| WO3/007264 | 2003-01-01 | Applicant | |
| WO3/021877 | 2003-03-01 | Applicant |
Non-Patent Literature (30)
- Sutherland, Ed, Payphones: The Next Hotspot Wave?, Jan. 28, 2003, http://www.isp-planet.com/fixed—wireless/news/2003/bellcanada—030128.html (3 pages).Applicant
- Reuters, Verizon Launches Wi-Fi Hot Spots, May 13, 2003, http://www.wired.com/news/wireless/0,1382,58830,00.html (2 pages).Applicant
- Verizon, Verizon Broadband Anytime, Copyright 2003, no month listed, https://www33.verizon.com/wifi/login/locations/locations-remote.jsp (2 pages).Applicant
- inCode Telecom Transforming Payphones into Wi-Fi Hot Spots, Jan. 14, 2003, http://www.pocketpcmag.com/news/incode.asp (2 pages).Applicant
- Bergstein, Brian, US telco plans WiFi payphone, May 12, 2003 http://www.news.com.au/common/story—page/0,4057,6420676%5E15306,00.html (2 pages).Applicant
- Bell Canada launches public wireless Internet hotspot pilot, Dec. 10, 2002, http://www.bell.ca/en/about/press/release/2002/pr—20021210.asp (3 pages).Applicant
- Stern, Christopher, Verizon to Offer Wireless Web Link Via Pay Phones, May 10, 2003, http://www.washingtonpost.com/ac2/wp-dyn?pagename=article&node=&contentId=A367 . . . (3 pages).Applicant
- Rants and Ramblings, Go Wireless . . . At A Payphone, May 10, 2003, http://www.morethanthis.net/blog/archives/2003/05/10/000301.html (2 pages).Applicant
- Wayport's Value Proposition: To provide the industry's best high-speed Internet and business center experience for the airport passenger to stay productive, http://www.wayport.net/airportsoverview (visisted Jul. 29, 2003) (2 pages).Applicant
- Wireless Access List—ATL Admirals Club, http://www.ezgoal.com/hotspots/wireless/f.asp?fid=60346 (visited Jul. 29, 2003) (1 page).Applicant
- Wireless Access List—Atlanta Hartsfield International Airport, http://www.ezgoal.com/hotspots/wireless/f.asp?fid=63643 (visited Jul. 29, 2003) (1 page).Applicant
- Airpath Wireless, Inc., Hot Spot Hardware, Copyright 2003, http://www.airpath.com/programs/hardware/hardware.htm (visited Jul. 29, 2003) (2 pages).Applicant
- Phoneline / HPNA / HomePNA Networks, http://www.homenethelp.com/web/howto/HomeNet-HPNA.asp (visited Jul. 29, 2003) (3 pages).Applicant
- to Starbucks and beyond: 802.11 wireless Internet access takes off, CommunicationsSolutions.com, vol. 4, Issue 1, Q1 2003, pp. 8-9, no date listed.Applicant
- Kooser, Amanda and Campanelli, Melissa, Testing, 1-2-3, Entrepeneur Magazine, Sep. 2003, pp. 27 and 30.Applicant
- Hogan, Mike, Call of the Wi-Fi, Entrepeneur Magazine, Sep. 2003, pp. 39 and 42.Applicant
- Westcott, Jil et al., “A Distributed Routing Design For A Broadcast Environment”, IEEE 1982, pp. 10.4.0-10.4.5.Applicant
- Khan, Robert E. et al., “Advances in Packet Radion Technology”, IEEE Nov. 1978, vol. 66, No. 11, pp. 1468-1496.Applicant
- Frankel, Michael S., “Packet Radios Provide Link for Distributed, Survivable C3 in Post-Attack Scenarios”, MSN Jun. 1983.Applicant
- Lauer, Greg et al., “Survivable Protocols for Large Scale Packet Radio Networks”, IEEE 1984, pp. 15.1-1 to 15.1-4.Applicant
- Gower, Neil et al., “Congestion Control Using Pacing in a Packet Radio Network”, IEEE 1982, pp. 23.1-1 to 23.1-6.Applicant
- MacGregor, William et al., “Multiple Control Stations in Packet Radio Networks”, IEEE 1982, pp. 10.3-1 to 10.3-5.Applicant
- Shacham, Nachum et al., “Future Directions in Packet Radio Technology”, IEEE 1985, pp. 93-98.Applicant
- Jubin, John, “Current Packet Radio Network Protocols”, IEEE 1985, pp. 86-92.Applicant
- Westcott, Jill A., Issues in Distributed Routing for Mobile Packet Radio Network, IEEE 1982, pp. 233 238.Applicant
- Lynch, Clifford A. et al., Packet Radio Networks, “Architectures, Protocols, Technologies and Applications,”.Applicant
- Brownrigg, Edwin, “User Provided Access to the Internet,”, Open Access Solutions, http://web.simmons.edu/chen/nit/NIT'92/033-bro.htm, Jun. 8, 2005-Jun. 9, 2005.Applicant
- Khan, Robert E., “The Organization of Computer Resources into a Packet Radio Network,” IEEE, Jan. 1977, vol. Com-25 No. 1, pp. 169-178.Applicant
- Westcott, Jill A., “Issues in Distributed Routing for Mobile Packet Radio Network,” IEEE 1982, pp. 233-238.Applicant
- Khan, Robert E., “The Organization of Computer Resources into a Packet Radio Network,” IEEE Transactions on Communications, Jan. 1977, vol. Com-25 No. 1, pp. 169-178.Applicant