Source: http://www.google.com/patents/US20020032042?dq=5,646,839
Timestamp: 2016-05-26 05:44:08
Document Index: 205246148

Matched Legal Cases: ['ART) 402', 'ART 402', 'ART 338', 'ART 338', 'ART 338', 'ART 402', 'ART 402', 'ART 404', 'ART 404', 'ART 510', 'ART 338', 'ART 338', 'ART 402']

Patent US20020032042 - Exporting controls to an external device connected to a portable phone system - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inPatentsWireless communications relative to a vehicle using a wireless communications device, a pocket for holding the wireless communication device and a docking station in communication with the pocket are provided. The pocket can include a processor for translating communications between the wireless communications...http://www.google.com/patents/US20020032042?utm_source=gb-gplus-sharePatent US20020032042 - Exporting controls to an external device connected to a portable phone systemAdvanced Patent SearchPublication numberUS20020032042 A1Publication typeApplicationApplication numberUS 09/952,958Publication dateMar 14, 2002Filing dateSep 14, 2001Priority dateFeb 18, 2000Publication number09952958, 952958, US 2002/0032042 A1, US 2002/032042 A1, US 20020032042 A1, US 20020032042A1, US 2002032042 A1, US 2002032042A1, US-A1-20020032042, US-A1-2002032042, US2002/0032042A1, US2002/032042A1, US20020032042 A1, US20020032042A1, US2002032042 A1, US2002032042A1InventorsRalph Poplawsky, Michael Durian, Daniel SerafinOriginal AssigneePoplawsky Ralph C., Durian Michael B., Daniel SerafinExport CitationBiBTeX, EndNote, RefManPatent Citations (11), Referenced by (159), Classifications (26), Legal Events (3) External Links: USPTO, USPTO Assignment, EspacenetExporting controls to an external device connected to a portable phone system
DETAILED DESCRIPTION [0048] With reference to FIG. 1A, an embodiment of a system 100 for providing wireless communications in a vehicle is depicted. The system 100 generally includes any communications device capable of wireless communications (e.g. a wireless telephone) 102, a first holding assembly or pocket 104, also referred to herein as adaptor 104, and a docking station or an interface module (IM) 106. For purposes of the present disclosure, the terms holding assembly, pocket and adaptor shall be treated as synonymous. The telephone 102 may have, or be compatible or otherwise operatively associated with, any current or future wireless technology, including, but not limited to, analog technologies such as the Advanced Mobile Phone System (AMPS), or digital systems such as a code division multiple access (CDMA) system, a time division multiple access (TDMA) system such as the Global System for Mobile Communications (GSM), a third generation (3G) system, such as wide band CDMA (W-CDMA), multicarrier CDMA, Time Division Duplex CDMA, or 3G EDGE (Enhanced Data Rates for GSM Evolution), or a combination of these and other air link technologies, such as the Bluetooth standard. In addition, the telephone 102 can be a wireless communications device other than a wireless telephone, such as a satellite telephone, a radio, a software defined radio, a personal digital assistant, with or without wireless telephone capability or other service. In general, the telephone 102 is designed by its manufacturer to operate on batteries 107 and to be small in size to allow for easy portability. In addition, the telephone 102 generally features a built-in speaker 108 and microphone 110 to provide for the input and output respectively of audio signals when the telephone 102 is held to the head of the user. [0049] The telephone 102 includes a keypad 112 to allow the user to dial numbers and to access the internal capabilities of the telephone 102, such as stored directories of telephone numbers, voice mail, paging or other features that may be provided by the telephone 102. User-defined functions such as directories of the telephone numbers may be stored in internal memory provided in the telephone 102. In addition, a typical telephone 102 includes a visual display 114 for displaying the number to be called or other information, such as the contents of a memory location or the number from which an incoming call originates. The telephone 102 will generally include baseband frequency amplifiers associated with the speaker 108 and the microphone 110. The telephone 102 also includes a radio frequency section for transmitting and receiving signals at the telephone's 102 operating frequencies. An electrical connector 116 is generally provided to allow the telephone 102 to be electrically connected to external devices. For example, the telephone 102 may be connected to an external power supply through the electrical connector 116. In addition, the connector 116 generally includes contacts for the transmission of control and data signals to the telephone 102. In some telephones 102, provision may also be made for the interconnection of a coaxial radio frequency cable to a radio frequency port 118, allowing the telephone 102 to utilize an external antenna. [0050] The pocket 104 generally includes a recess 120 shaped to receive the exterior of the telephone 102. The recess 120 may include surface features 122, such as friction pads or protrusions shaped to mate with receiving features on the telephone 102, to mechanically interconnect the telephone 102 and the pocket 104. The pocket 104 is also provided with an electrical connector 124 that mates with the electrical connector 116 of the telephone 102 when the telephone 102 is properly positioned within the recess 120 of the pocket 104. The pocket 104 may also be provided with a coaxial connector 126 for interconnection with a coaxial connector 118 on the telephone 102. Therefore, the pocket 104 is electrically connected to the telephone 102 through the electrical connections 116 and 124 and the coaxial connectors 118 and 126. The pocket 104 may also be provided with componentry to establish a wireless link with the telephone 102. [0051] The docking station 106 includes locating protuberances 128 for receiving locating apertures 130 located on the back side of the pocket 104 (see FIG. 2). The locating protuberances 128, together with latch tabs 132 cooperate with the locating apertures 130 to mechanically interconnect the pocket 104 to the docking station 106. The docking station 106 also features an electrical connector 134 that mates with an electrical connector 136 located on the back of the pocket 104 (see FIG. 2). The docking station 106 additionally includes a coaxial connector 138 for connection to a cooperating coaxial connector 140 located on the back of the pocket 104 (see FIG. 2). The docking station 106 may also be provided with componentry to establish a wireless link with the telephone 102 on the pocket 104. [0052] In the system of the present invention, the telephone 102 generally serves to transmit and receive radio frequency signals, and to demodulate and modulate those signals to and from the baseband frequencies (e.g., the audible frequencies or digital data communication frequencies). The telephone 102 then provides the baseband frequencies to the pocket 104 through the mating of the electrical connectors 116 and 124. Alternatively, the telephone 102 may provide the base band frequencies to the pocket 104 over a wireless link. The pocket 104 also holds the telephone 102 securely in place. The electrical connector 136 and/or wireless link, in cooperation with the electrical connector 134 on the docking station 106 and/or a wireless link provided by the docking station 106, or the pocket 104, completes the electrical interconnection of the telephone 102 to the docking station 106, and in turn to the vehicle. The docking station 106 also serves to mechanically interconnect the pocket 104, and in turn the telephone 102, to the vehicle, as the docking station 106 is generally rigidly affixed to the vehicle. The radio frequency connectors 118, 126, 138, and 140 also cooperate to carry radio frequency signals from the telephone 102 to an antenna mounted on the exterior of the vehicle. Therefore, in summary, the pocket 104 generally serves to mechanically and electrically interconnect the telephone 102 to the docking station 106 and in turn to the vehicle. [0053] Referring now to FIG. 1B, an alternative embodiment of the pocket 104 of the present invention is illustrated. According to the embodiment of the pocket 104 illustrated in FIG. 1B, a plurality of control buttons 142 are provided. The control buttons 142 allow the user to access certain advanced features of the pocket 104 provided with select embodiments of the system 100 and in particular of the pocket 104. These advanced functions will be discussed in detail below. [0054] Referring now to FIG. 3, the major internal components of the telephone 102, the pocket 104, and the docking station 106, as well as relevant components integral to the automobile or vehicle 302 are illustrated. As described generally above, the telephone 102 may provide various electronic signal paths. Therefore, the telephone 102 may accept power from an external source through a power supply line 303. The transmission of analog audio signals from the telephone 102 to the pocket 104 may be made through the analog audio output line 304, and analog audio signals may be transmitted from the pocket 104 to the telephone 102 through the analog audio input signal line 306. The telephone 102 may also be provided with one or more signal lines 308 for receiving and transmitting digital data or digital audio signals. Other signal lines that may be provided include a clock signal line 310, a frame synch signal line 312, and telephone control signal bus 314. Telephone control signals passed over the telephone control signal bus 314 may include signals to turn the telephone 102 on or off; to indicate that data is ready to be sent from the telephone, or that the telephone is ready to receive data; to request power or a change in power; to lock and unlock the telephone; to mute the telephone; to indicate an incoming call; to change the telephone language; to auto answer; to convey or request call timer information, current call status, call restriction data, telephone display data, calling number data, serial message data, cellular system information, or telephone system information; to request or control the telephone volume; to recall or write telephone numbers or other information from the telephone's memory; to simulate a telephone keypress; to dial a number; caller identification data; and to initiate the send command or the end command. All of the various electrical lines 303, 304, 306, 308, 310, 312 and 314 may be a part of the electrical connector 116 on the exterior of the telephone 102. The telephone 102 may also be provided with a radio frequency signal line 316 in the form of the coaxial connector 118. [0055] As described above, the pocket 104 is provided with an electrical connector 124 for electrically interconnecting the pocket 104 to the telephone 102. Some of the electrical signals passing through the connector 124 are simply carried through the pocket 104 to the electrical connector 136, and thereby are passed on to the docking station 106 directly. Other of the signals are manipulated or processed within the pocket 104. For example, the analog audio output signal 304 is amplified in the pocket 104 by an analog audio amplifier 318. In addition, a microprocessor 320 processes telephone control signals on the telephone control signal bus 314 that are passed between the telephone 102 and the pocket 104, and communication on the pocket-docking station bus 322 passed between the pocket 104 and the docking station 106. Pocket memory 324 may be associated with the microprocessor 320. The pocket memory 324 may be any addressable storage space, such as ROM, RAM, EEPROM, flash memory, or a combination of memory types. All or a portion of the memory 324 may be removable from the pocket 104. The pocket 104 also includes a ground signal 326 for signaling to the docking station 106 through electrical connectors 134 and 136 the presence or absence of the pocket 104. [0056] The docking station 106 includes processing hardware and software including at least one microprocessor and/or a digital signal processor 328, a programmable power supply 330, a DC to DC power converter 332, a near-end coder/decoder (CODEC) 334, a far-end CODEC 336, one or more universal asynchronous receivers/transmitters 338 (UART), and docking station memory 340. The docking station memory 340 may be any addressable storage space, such as ROM, RAM, EEPROM, flash memory or a combination of memory types. All or a portion of the memory 340 may be removable from the docking station 106. The docking station 106 also includes a multiplexer 342, an analog audio amplifier 344, and ground lines 326 and 346 for establishing a common ground between the pocket 104 and the docking station 106. The docking station 106 may additionally include an interface 348 for interconnecting the docking station 106 to various external subsystems or devices 378. The interface 348 may be integral to the docking station 106. Alternatively, the interface 348 may conveniently be mounted to a daughter board 380, also referred to herein as data daughter board (DDB) 380, to facilitate expanding the capabilities of the docking station 106. The daughter board 380 may also have a microprocessor including server capabilities. According to a further embodiment, instead of such a daughter board 380, all of the interface's 348 capabilities and the docking station components and their functionalities could be integrated on a single chip. The daughter board 380 may be interconnected to the processor 328 by a serial or parallel communications channel. In general, the provision of the interface 348 allows the docking station 106 to serve as a communications hub for various external subsystems 378. These external subsystems 378 may include personal computers, auto PCs, Global Positioning System (GPS) units, Personal Digital Assistants (PDA); devices for the storage of digital audio for playback through the automobile's stereo, such as devices storing music in the MP3 format; devices for monitoring various operational parameters of a vehicle, including the status of vehicle components and the geographic position of the vehicle, and that may also be used to transmit information between a driver of the vehicle and a centrally located dispatcher or base station; the data network or communications bus of vehicles, such as a controller area network (CAN), other data network or communications busses, visual displays; devices using the Bluetooth communications protocol or some other communications protocol; or other electronic systems. In connection with possible implementation of Bluetooth technology, such may be integrated with the docking station 106, as well as being incorporated with the pocket 104. In such a case, the Bluetooth technology need not be part of the wireless telephone 102 or other wireless communication device. According to this embodiment, the pocket 104 and the docking station 106 could cooperatively function to provide services for associated Bluetooth devices. In this configuration, the number of signal conducting wires is substantially reduced. However, one or more wires may be necessary or appropriate for providing charging functions and/or providing an external antenna connection. [0057] With respect to facilitating communications with the vehicle 302 having the wireless communications device 102, particularly communications to vehicle subsystems 378 using the Internet, the vehicle subsystems 378 can be configured to be separately accessible. These individualized communications are achieved, preferably not by assigning separate Internet protocol (IP) addresses to each of the vehicle subsystems 378, but by incorporating an address-related mapping technique. In accordance with the preferred embodiment, the particular vehicle 302 has only one IP address, or at least the number of IP addresses associated with the vehicle 302 and vehicle subsystems 378 is less than the total number of vehicle subsystems 378. In the case in which the vehicle 302 has only one IP address, it is necessary to be able to direct the received communication to the desired vehicle subsystem 378. This can be accomplished by assigning or correlating ports or other identifiers to each of the vehicle subsystems 378 for which there is interest in allowing such communication. When a communication is received for a designated vehicle subsystem 378, the docking station 106 and/or associated daughter board 380 functions to map the contents of the received communication to the port or other identifier associated with a particular vehicle subsystem 378 that is to be the recipient of this communication. In a preferred embodiment in which it is desirable to communicate with a number or a fleet of vehicles 302 from a common site outside the vehicle 302, each of the vehicles 302 in the fleet would be assigned a separate IP address. However, the identifiers or ports associated with each of the vehicle subsystems 378 in this fleet would have the same or corresponding port or other identifier. For example, vehicle subsystem 1 in vehicle 1 would have the same port number or other identifier as vehicle subsystem 1 in vehicle 2, although the IP addresses of vehicle 1 and vehicle 2 would be different. This configuration is highly beneficial in managing fleet vehicles 302, particularly sending/receiving information relative to each of a number of vehicle subsystems 378 in a large number of vehicles. Relatedly, such configuration makes it easier to identify and locate each of the vehicle subsystems 378 in a fleet since the same vehicle subsystem 378 in one vehicle has the same identifier as an identical vehicle subsystem 378 in another vehicle in the fleet. [0058] With regard to sending a first communication to a first external subsystem 378 located in a first vehicle 302, a communication can be prepared at a site remote from the vehicle 302. The communication packet includes an IP address for the first vehicle. The communication packet also includes address-related (e.g. port) information or other identifying information associated with the first external subsystem 378 that is to receive this first communication packet. The first communication packet is transmitted over the Internet to the first vehicle having the IP address in the communication packet. This communication packet is then received by the wireless telephone or other wireless communication device 102. Subsequently, a determination is made regarding the ultimate location or external subsystem 378 recipient of the first communication packet. This determination might be made by processing hardware and software in the docking station 106 and/or other processing hardware/software including possibly a server on the daughter board 380. The docking station 106 may be provided with a network interface, such as an Ethernet Network interface, for providing data packets to recipient external subsystems or devices 378 and applications running on those devices 378. The network interface may conveniently be provided as part of a data daughter board 380. The docking station 106 may also be provided with some other standard or proprietary interface 348. For instance, the docking station 106 may include an RS232 serial port or ports as part of the interface 348. As part of the processing or determination procedures, mapping or other correlation can be provided between the information in the first communication packet related to identifying the particular external subsystem 378 that is to receive the communication packet and a port or other identifier associated with this external subsystem 378. After the mapping is completed, the communication packet can be directed to the determined first external subsystem 378, which was designated as the recipient of this communication. As can be appreciated, in the case in which the same communication is to be sent to the same vehicle subsystem 378 located in a number of vehicles 302 in a fleet, only the IP address for each vehicle 302 need be changed to its dedicated vehicle IP address. As can be further appreciated, when it is desirable to send a communication to a second vehicle subsystem 378 located in the first vehicle 302, either at the same time or at different times, the same IP address associated with that first vehicle 302 can be utilized, while the mapping function to enable the communication to be received by the second vehicle subsystem 378 can be handled within the vehicle 302. [0059] Similarly, in communicating from the vehicle 302 to a site outside the vehicle, such as a common site associated with sending/receiving communications to/from a fleet of vehicles 302, and involving the transmission of data or other information from one or more vehicle subsystems 378 in the vehicle, the network address translation (NAT) can also be accomplished. In particular, the server or other processing hardware/software conducts an address translation by which the vehicle IP address is provided before the communication is sent over the Internet. Such a communication could also include identifying information that identifies the accompanying data as emanating from the particular vehicle subsystem. Consequently, the communication to the site outside the vehicle is accomplished using a single IP address, regardless of which vehicle subsystem might be providing data to the site over the Internet. [0060] Additionally, the docking station 106 is provided with various signal paths for interconnecting the docking station 106 to the pocket 104 and the vehicle or automobile 302. Signal paths between the pocket 104 and the docking station 106 include the analog audio input signal path 306 and the amplified analog audio output signal path 350. Digital data signal paths 308 and clock 310 and frame synch 312 signal paths may also be provided between the pocket 104 and the docking station 106. The pocket-docking station communications bus 322 also runs between the pocket 104 and the docking station 106. The bus 322 may be a serial bus or any other appropriate bus. Various power lines may also run between the pocket 104 and the docking station 106, such as the telephone power supply line 303 and the pocket power line 352. The docking station power enable line 354 connects the microprocessor 320 of the pocket 104 to the DC to DC power convertor 332 in the docking station 106. The ground 326 and pocket sense 346 lines also pass between the pocket 104 and the docking station 106. Radio frequency signals are passed through the docking station 106 from the pocket 104 to an antenna 356 mounted on the automobile 302 over the radio frequency signal line 316. Additionally, a signal indicating the position of the automobile's 302 ignition switch 358 is passed through the docking station 106 to the microprocessor 320 of the pocket through the ignition signal line 360. [0061] Signal paths between the docking station 106 and the automobile 302 include the radio frequency signal line 316, which passes from the telephone 102, through pocket 104 and the docking station 106 to the antenna 356 on the automobile 302. In addition, near-end audio input 370 and audio output 372 lines connect the near-end CODEC 334 to the microphone 368 and the speaker 366, respectively. The audio output line 372 passes through an analog audio amplifier 344 before continuing on to the speaker 366. The mute line 362 connects the docking station microprocessor 328 to the entertainment system 373 of the automobile 302. The main power line 374 connects the DC to DC power convertor 332 of the docking station 106 to the electrical power supply 364 of the automobile 302. The ignition signal line 360 passes through the docking station 106, between the microprocessor 303 of the pocket 104 and the ignition switch 358 of the automobile 302. Additionally, one or more custom interface signal lines 376 may connect the interface 348 of the docking station 106 to various other subsystems 378 located in the automobile 302. [0062] As a result of the above-mentioned signal paths, in addition to being mechanically interconnected to the automobile 302, the docking station 106 is electrically connected to certain of the automobile's 302 components. Therefore, the docking station 106 may be interconnected to an antenna 356 provided on an exterior of the automobile 302. Also, the docking station 106 is interconnected to the electrical power supply 364 of the automobile 302, and may also be connected to the ignition switch 358 of the automobile 302 to signal operation of the system 100 when the automobile 302 is running. Speakers 366 located within the automobile 302 may conveniently be utilized by the system 100 to provide an audible signal from the telephone 102. The speakers 366 may or may not be a part of the automobile's 302 audio entertainment system 373. Also, the speakers 366 may be part of a headset worn by the user. For receiving audible signals (e.g. the voice of a user), a microphone 368 may be located within the interior of the automobile 302, and that signal processed by the docking station 106 and provided to the telephone 102 via the pocket 104. The docking station 106 of the system 100 may also be interconnected to the audio system 373 of the automobile 302 to mute signals other than those transmitted from the telephone 102 to the speakers 366. [0063] Preferably, the system 100 is provided in a variety of models offering differing capabilities to suit the needs and budgets of individual users. These differing capabilities are provided by varying the functionality supported by the pocket 104 and/or the docking station 106. Referring now to FIGS. 4A and 4B, embodiments of the system 100 having differing capabilities are illustrated schematically. [0064] With reference now to FIG. 4A, a telephone 102, pocket 104, docking station 106, and automobile 302 of an embodiment of the system 100 are illustrated schematically. With respect to the telephone 102, the radio frequency 316, power 303, audio 304 and 306, control 314, and digital data signal lines 308 are illustrated. It is noted that, while the digital data path 308 is shown at the telephone 102, it is not passed through the pocket 104 to the docking station 106. This is because the embodiment of the pocket 104 illustrated in FIG. 4A does not support digital data signals 308, and thus does not provide a digital data line. [0065] The pocket 104 of the embodiment illustrated in FIG. 4A includes signal paths for the radio frequency 316 and power 303 signals. For at least the incoming analog audio signal, an amplifier 318 is provided. Telephone control data line 314 is interconnected to the microprocessor 320 located in the pocket 104. Therefore, it can be seen that, in the embodiment shown in FIG. 4A, the pocket 104 provides interconnections to all of the telephone's 102 electrical inputs and outputs, except for those outputs for digital data or digital audio. [0066] The pocket 104 of the embodiment shown in FIG. 4A amplifies audio signals provided from the telephone 102, and includes a microprocessor 320 for providing an interface for control data 314 passed between the telephone 102 and the docking station 106. As illustrated in FIG. 4A, a universal asynchronous receiver transmitter (UART) 402 may be associated with the microprocessor 320 for aiding the transmission of flow control data between the telephone 102 and the pocket 104. In one embodiment, a single UART 402, which is part of the microprocessor 320, is provided on the pocket 104 side of the telephone control signal path established between the pocket 104 and the docking station 106. Because a UART 338 is provided in the docking station 106, no additional UART is necessary. By eliminating an additional UART, the cost of the pocket 104, and in particular the cost of the microprocessor 320, can be kept to a minimum. However, in certain applications, such as those in which the docking station 106 is located at a distance from the pocket 104, it may be necessary to provide an additional line driver in the pocket 104. [0067] The docking station's 106 major components are shown in FIG. 4A as the docking station microprocessor 328, the power supply 330, the near-end 334 and far-end 336 CODECs, the UART 338, and the docking station memory 340. The docking station 106 is also illustrated as providing a signal path for the radio frequency signal 316. The docking station microprocessor 328 provides a variety of advanced functions that will be described in greater detail below. The power supply 330 provides a constant voltage or a constant current, according to the requirements of the particular telephone 102, for powering the telephone 102 and charging the telephone's 102 battery 107. The CODECs 334 and 336 provide for the conversion of analog audio signals to digital signals that can be processed by the docking station microprocessor 328, and likewise convert digital audio signals emanating from the docking station microprocessor 328 into analog signals usable by the analog audio inputs of the telephone 102 or the speakers 366 of the automobile 302. As described above with respect to the pocket 104, the UART 338 of the docking station 106 facilitates the communication of telephone 102 control data between the pocket 104 and the docking station 106 across the pocket-docking station bus 322. The docking station memory 340 allows voice memos or other data to be stored in digital form. In addition, the docking station memory 340 may be used to store word models and voice prompts used to support voice recognition features. As an additional function, the docking station memory 340 may be used to correct errors in the code resident in the docking station microprocessor 328. [0068] The automobile 302 is, in the embodiment illustrated in FIG. 4A, shown as being connected to the radio frequency 316, power 374, audio 370 and 372 and control 362 line. However, the data line 308 is not shown as being interconnected to the data line 308 of the telephone 102. This is because the pocket 104 of the embodiment makes no provision for transmitting such data 308 to or from the telephone 102. [0069] Referring now to FIG. 4B, a telephone 102, pocket 104, docking station 106, and automobile 302 of yet another embodiment of the system 100 are illustrated schematically. The system 100 illustrated in FIG. 4B includes all of the various signal lines and structures described above with respect to the embodiment illustrated in FIG. 4A. However, in addition, the embodiment illustrated in FIG. 4B includes a digital data line 308 from the telephone 102 through the pocket 104 to a second UART 402 located in the docking station 106. The second UART 402 of the docking station 106 is connected to a third UART 404 in the docking station 106. The interface signal line 376 runs between the third UART 404 of the docking station 106 and the automobile 302. Thus, the embodiment of the system 100 illustrated in FIG. 4B provides a direct path for digital data or audio from the telephone 102 to the docking station 106, including the docking station microprocessor 328, and from the docking station 106 to the automobile 302. The provision of these digital data lines 308 and 376 allows the system 100 to support additional features, as will be described in greater detail below. [0070] Referring now to FIG. 5, an embodiment of the pocket 104 of the present invention is illustrated schematically. As shown in FIG. 5, the pocket 104 generally includes an electrical connector 124 for providing electrical connectivity between the pocket 104 and the telephone 102. Additionally, a radio frequency connector 126 may be provided for the transmission of radio frequency signals across the pocket 104 to the docking station 106. The radio frequency signal line 316 thus travels between the radio frequency connector 126 at the interface of the telephone 102 and the pocket 104, and the radio frequency connector 140 at the interface of the pocket 104 and the docking station 106. An electrical connector 136 provides other electrical connections between the pocket 104 and the docking station 106. As discussed above, digital data lines 308 can be provided in the pocket 104 to pass digital data or digital audio signals directly from the telephone 102 to the docking station 106, without manipulation by componentry within the pocket 104. Other signal lines that are provided for transmission of signals across the pocket 104 without manipulation by the pocket 104 are the clock signal line 310 and the frame synch signal line 312. Also, one or more power supply lines 303 transmit power from the docking station 106 directly to the telephone 102. [0071] As discussed above, an analog audio amplifier 318 receives analog audio signals from the telephone 102 over the analog audio analog output line 304. The analog signals received at the amplifier 318 are then amplified a selected amount and passed to the docking station 106 over the amplified analog output line 350. Also shown in FIG. 5 is an analog audio input amplifier 502 which may be provided to selectively amplify analog audio signals from the docking station 106 before they are passed to the telephone 102 over analog audio input line 306. [0072] A voltage regulator 504 may be provided in the pocket 104 for providing the correct voltage level to power the microprocessor 320. For example, the voltage regulator 504 may take a 5 volt signal supplied by the DC to DC power convertor 332 in the docking station 106 over power line 352, and produce a 3 volt output. The 3 volt output may then be supplied to the microprocessor 320 over regulated power supply line 506. [0073] The signals provided from the docking station 106 through the electrical connector 136 to the pocket 104 include communication signals transmitted over the pocket-docking station communication bus 322. The communication bus 322 terminates in the microprocessor 320 at serial input/output pins 508. As will be described in greater detail below, the communication signals received at the serial I/O pins 508 are decoded before being sent to the microprocessor UART 510 for transmission to the telephone 102 over the telephone control lines 314. Other signal lines passing between the docking station 106 and the pocket 104 include a plurality of in-circuit programming signal lines 512, which may be used to program or re-program the pocket microprocessor 320. The ignition signal line 360 and mute line 362 are also provided. Additional I/O signal lines 514 may be provided between the microprocessor 320 and the telephone 102. A pocket detect ground 326 for interconnection to the docking station 106 is also provided. Additionally, memory 324 may be provided in the pocket 104 for use in association with the microprocessor 320. According to one embodiment of the pocket 104, the microprocessor 320 includes inputs for receiving signals from buttons 142 (see FIG. 1B) on the exterior of the pocket 104. [0074] As mentioned above, the telephone 102 may generally be used to transmit and receive voice and data signals over an air link to a base station, such as a cell in a cellular phone system. Additionally, the telephone 102 will typically allow for the storage of indexed lists of telephone numbers to provide the user with a customized list or directory of telephone numbers. The telephone 102 is also provided with a speaker 108 and microphone 110 to allow the user to engage in conversations over the telephone 102 when the telephone 102 is held to the face of the user. A keypad 112 is typically used to enter numbers and initiate dialing, answer incoming calls, and to enter telephone directory information. A visual display 114 is also typically provided for displaying the number to be called, memory location entries, or other information. The telephone 102 may be powered by a battery 107 so that the telephone 102 is easily portable. [0075] However, the telephone 102 is typically not provided with features allowing for easy hand held use in an automobile. For instance, placing a call typically requires the user to enter the number using the keypad 112, or again using the keypad 112, to select from an entry in a user-defined directory. Using the keypad requires that the user remove his or her eyes from the road to view the keypad 112 and the display 114, and to remove a hand from the automobile's 302 controls to enter the number or select the desired option. This is, of course, disadvantageous where the user is driving the automobile 302. Although some telephones 102 are available with built-in voice recognition features, they are “near talk” systems, and are not well suited for use in vehicle or other “far talk” environments. Therefore, it is desirable to provide a system to allow the reliable hands-free operation of the telephone 102. [0076] As can be appreciated, the telephone 102 may be produced by any one of a number of manufacturers, who each may produce a variety of different models. Accordingly, the physical shape of the telephone 102, as well as the physical configuration of the electrical connector 116 and the particular signal lines provided by the electrical connector 116 may vary greatly. Additionally, the communications protocol recognized by the telephone 102 is generally proprietary to the manufacturer of the telephone 102 and may vary among telephone 102 models produced by a single manufacturer. [0077] In order to accommodate the variety of physical, electrical, and communications protocol variations among telephones 102, the present invention provides a plurality of different pocket 104 configurations. Thus, a pocket 104 may be provided to mate with the various physical configurations of different telephones 102. Accordingly, the recess 120 and surface features 122 are generally determined by the physical characteristics of the telephone 102 meant to be accommodated by the particular pocket 104. In addition, the electrical connector 124 is physically configured to mate with the electrical connector 116 on the telephone 102. Where the telephone 102 provides a coaxial connector 118 for a radio frequency signal line, the pocket 104 may provide a mating coaxial connector 126. In this way, a particular telephone 102 may mechanically mate with the corresponding pocket 104. [0078] As mentioned above, the particular electrical signal lines provided by telephone 102 and the communications protocol used by the telephone 102 may vary between manufacturers, and even among the various models of telephones 102 produced by a particular manufacturer. Therefore, in order to electrically connect the telephone 102 to the pocket 104 and the docking station 106 and in turn the automobile 302, provisions must be made to accommodate these differences. Accordingly, the pocket 104 may be designed to accommodate the particular configuration and type of electrical signal lines provided by the telephone 102. In a physical sense, this is done by connecting the provided signal lines (e.g. 304, 306, 308, 310, 312, 314, 303 and 316) to the corresponding contacts, if so provided, in the electrical connector 116 and 118 of the telephone 102. [0079] Additionally, the pocket 104 is provided with a microprocessor 320 and associated pocket memory 324 for interfacing with the provided telephone control signals 314 of the telephone 102. In this way, the electrical and communications protocols of the telephone 102 can be accommodated by the particular pocket 104 designed for use with the particular telephone 102. Specifically, the memory 324 of the pocket 104 contains code that allows the pocket 104 to translate between commands formatted in the API of the system 100 and the proprietary communications interface of the telephone 102. Although the pocket 104 is physically and electrically configured for use with a particular telephone or telephones 102, it is desirable that the docking station 106 be capable of operating with any of the provided pockets 104 and associated telephones 102. Providing a common docking station 106 may reduce the cost of the system 100, as only the pocket 104 need be varied to accommodate the wide variety of telephones 102 available in the marketplace. To further increase the advantages gained by using a common docking station 106, many of the components necessary to provide the functions of the system 100 are located in the docking station 106. Conversely, the number and cost of components necessary for the pocket 104 to provide the desired functions are kept to a minimum. In addition, although the docking station 106 may be capable of carrying out a certain number of functions, all of these functions may not be available to a user who has a pocket 104 that allows access to only a limited number of the potentially available functions. Also, the functions supported by a particular pocket 104 may be varied according to the operational functions available using the particular telephone 102 or according to the functions supported by the particular pocket 104. [0080] With reference now to FIG. 6, a plurality of pockets 104 a, 104 b, 104 c, 104 d, 104 e, 104 f, 104 g and 104 h are shown, each having differing physical and/or functional compatibilities, but that are all physically and functionally compatible with a common docking station 106. The pockets A1 104 a, A2 104 b, A3 104 c, and A4 104 d may, for instance, be compatible with the physical characteristics of telephones A1 102 a, A2 102 b, and A3 102 c produced by a single manufacturer A. Pockets B1 104 e, B2 104 f, B3 104 g and B4 104 h may be physically compatible with telephones B1 102 d, B2 102 e, B3 102 f and B4 102 g produced by manufacturer B, or alternatively produced by manufacturer A, but having different physical characteristics from telephone 102 a, 102 b and 102 c. Although in the example the pockets 104 a-d are physically compatible with the telephones 102 a-c, and the pockets 104 e-h are physically compatible with telephones 102 d-g, all the various functionalities of telephones 102 a-c may not all be supported by the pockets 104 a-d and all the various functionalities of the telephones 102 d-g may not all be supported by the pockets 104 e-h. Similarly, the functional or other capabilities of the pockets 104 a-h may not all be supported by all of the telephones 102 a-g. In FIG. 6, the functional compatibilities between the individual pockets 104 a-h and the individual telephones 102 a-g are illustrated by arrows. A solid arrow from a pocket 104 to a telephone 102 indicates that all of the functions of the particular telephone 102 are supported by the particular pocket 104, while solid arrows from a telephone 102 to a pocket 104 indicate that all of the particular pocket's 104 capabilities are supported by the particular telephone 102. A dotted line from a telephone 102 to a pocket 104 indicates that only a subset of the pocket's 104 capabilities are supported by the particular telephone 102, while a dotted line from a pocket 104 to a telephone 102 indicates that only a subset of the particular telephone's 102 capabilities are supported by the particular pocket 104. [0081] As an example, telephones A1 102 a, A2 102 b, and A3 102 c may share common physical attributes, allowing any of those telephones to be mechanically interconnected to any of the pockets A1 104 a, A2 104 b, A3 104 c, and A4 104 d. However, the telephones A1 102 a, A2 102 b, and A3 102 c may have differing functional capabilities. Likewise the pockets A1 104 a, A2 104 b, A3 104 c, and A4 104 d may support different functions. For instance, pockets A1 104 a, A2 104 b, and A3 104 c may support all of the functional capabilities of telephones A1 102 a and A2 102 b, but only a subset of telephone A3's 102 c capabilities while pocket A4 104 d may support all of the functional capabilities of telephones A1 102 a, A2 102 b and A3 102 c. Telephones A1 102 a and A2 102 b may support all of the functional capabilities of pockets A1 104 a, A2 104 b, and A3 104 c, but only a subset of the functional capabilities of pocket A4 104 d, while telephone A3 102 c may support all of the functional capabilities of pockets A1 104 a, A2 104 b, A3 104 c and A4 104 d. Examples of the interaction between pockets 104 having differing functional capabilities and telephones 102 having differing functional capabilities will now be explained in the context of various examples. [0082] The pocket A1 104 a may be a level one pocket supporting only the most basic functions provided by the system 100. Thus, the pocket A1 104 a may provide basic speaker phone functions when interconnecting telephones A1 102 a, A2 102 b or A3 102 c to the docking station 106. The basic speaker phone functions may comprise the provision of a speaker 366 and microphone 368, to allow the user to carry on a conversation transmitted over a wireless link by the telephone 102 without having to hold the telephone 102 to his or her face. Thus, with reference now to FIG. 3, the pocket A1 104 a may provide analog audio signal lines 304 and 306 to support analog audio signals from and to the telephone 102, where the telephone, e.g. telephone A1 102 a, provides an analog audio input and output. The pocket A1 104 a may also provide analog audio amplifiers 318 and 502 (see FIG. 5) to allow for the gain of the analog audio signals to be adjusted. The pocket A1 104 a then provides connections for the analog audio signals to the docking station 106. Where the telephone A1 102 provides a digital input or output, for example, telephone A2 102 b, the pocket A1's 104 a digital audio signal lines 308 pass the digital audio signal directly to the docking station 106. In general, the capabilities and specifications of the telephone 102 are communicated to the docking station 106 by the pocket 104 via the pocket-docking station communications bus when the pocket 104 is initially interconnected to the docking station 106. [0083] The pocket A1 104 a also may provide a power line 303 for charging the battery 107 of the telephone 102 and/or providing electrical power to operate the telephone 102. [0084] The pocket A1 104 a additionally includes telephone control signal lines 314 between the telephone 102 and the microprocessor 320. Finally, the pocket A1 104 a may provide a radio frequency signal line 316, where a radio frequency output connector 118 is provided by the telephone 102. [0085] According to the embodiment of the system 100 having a level one pocket A1 104 a, the telephone 102 is physically held in position in the automobile 302, and is provided with speaker phone functionality. Thus, where a telephone call is placed from a remote site to the telephone 102, the user must generally press a button on the keypad 112 of the telephone 102 to enable communications with the telephone at the remote site. The establishment of the communications link with the remote site is signaled to the pocket 104 by the telephone 102 over the telephone control signal lines 314. The form of the signal given by the telephone 102 is generally proprietary to the manufacturer of the telephone 102. Accordingly, it may consist of a serial digital message, or simply by a change in the voltage at an electrical contact on the telephone 102. The pocket 104, and in particular the microprocessor 320, is programmed to recognize the particular message sent from the telephone 102 to indicate that a call is in progress. The microprocessor 320 then converts the message from the telephone 102 into one complying with the application programming interface (API) of the system 100. This message may be transmitted from a serial I/O port provided on the microprocessor 320 over the pocket-docking station communication bus 322 to the far-end UART 338 and from there to a parallel input/output port provided on the docking station microprocessor 328 of the docking station 106. The docking station microprocessor 328 reviews the call-in-progress message that originated in the telephone 102 and that was translated into the API of the system 100, and generally configures the system 100 so that it is ready to handle the call. In particular, the docking station microprocessor 328 activates the mute signal line 362 to mute any output from the automobile's 302 audio system 373. When the telephone provides an analog audio input 306 and an analog audio output 304, the docking station microprocessor 328 may also activate the analog audio output amplifier 318. Thus, where the telephone 102 provides an analog audio signal, that signal may be amplified by the analog audio amplifier 318 and passed to the docking station 106 wherein the analog signal is digitized by the far-end CODEC 336. The now digital audio signal is then passed to the multiplexer 342 and on to the docking station microprocessor 328 at a serial I/O port. The docking station microprocessor 328 then may perform a variety of signal processing functions on the audio signal. These functions may include acoustic echo cancellation, line echo cancellation, noise reduction, and frequency equalization. The docking station processor 328 may also provide partial full duplex operation, and automatic volume control functions. The processed digital audio signal is then passed from a serial I/O port of the docking station processor 328 to the near-end CODEC 334 where the digital audio signal is converted back into an analog signal. The analog signal may then be amplified to line level and conditioned in the analog audio amplifier 344 before being amplified by the audio system 373 or by a power amplifier associated with the speaker 366 and output by the speaker 366. [0086] Voice signals from the user in the automobile 302 are picked up at the microphone 368, which may feature built-in noise reduction capabilities, and digitized by the near-end CODEC 344, before being passed to the serial I/O port of the docking station microprocessor 328. Again, various signal processing functions may be carried out in the docking station microprocessor 328, before the digital audio signal is passed to the multiplexer 342 and on to the far-end CODEC 336. The far-end CODEC 336 transforms the digital audio signal into an analog signal that is passed to the telephone 102 for transmission over the air link to the remote site. [0087] Where the telephone 102 provides digital audio inputs and outputs, for example, telephones A2 102 b and A3 102 c, the transmission of signals through the system 100 is generally as described above, except that the digital audio signals may be passed between the telephone 102 and the docking station microprocessor 328 via the multiplexer 342, without any intervening digital to analog or digital to digital conversion, and without passing through the far end CODEC 336. [0088] The level one pocket A1 104 a may also provide the telephone 102 with power for charging the battery 107 and operating the telephone 102 over power line 303. In general, the microprocessor 320 of the pocket 104 will have been programmed to request the proper voltage or current from the programmable power supply 330 of the docking station 106. Of course, the power needs of the telephone 102 may vary according to the operational state of the telephone 102 or the charge of the battery 107. Therefore, the telephone 102 may request, for example, that power be supplied at a first voltage when the telephone 102 is in an idle state, and at a second voltage when the telephone 102 is in an active state. The signal requesting differing voltages may be passed from the telephone 102 over the telephone control signal lines 314 to the microprocessor 320 where the request is translated to the API of the system 100. The docking station microprocessor 328 may then control the programmable power supply 330 to provide the requested power. The pocket may also include a current limiter or voltage regulator as required. [0089] Because the pocket 104 is designed to provide a predetermined set of functionalities and to be used with a predetermined telephone or set of telephones 102, the microprocessor 320 and in particular the memory 324 associated with the microprocessor 320 will have been programmed to translate the particular signals of the telephone 102 into commands included in the API of the system 100. In addition, the pocket 104 will have been programmed with the power requirements of the telephone 102. This information regarding the functions supported and requirements of the telephone 102 may be communicated over the pocket-docking station communications bus 322 to the docking station microprocessor 328 when the pocket 104 is plugged into the docking station 106. The pocket 104 also communicates information regarding the functions supported by the pocket 104 to the docking station 106. In general, the docking station 106 is activated when the pocket 104 is plugged into the docking station 106 and the pocket sense ground 326 is established between the pocket 104 and the docking station 106. [0090] A second pocket 104 b, known as a level two pocket, may provide additional functionalities. For example, the pocket 104 b may support audible prompts, voice commands and voice memorandum recording. As illustrated in FIG. 6, the functionalities of pocket A2 104 b are fully supported by telephones A1 102 a, A2 102 b and A3 102 c, even though it provides this additional functionality. Also, the docking station 106 may be identical to the one described with reference to pocket A1 104 a. With respect to the basic speaker phone functions provided by the system 100 in connection with pocket A2 104 b, the functions and interconnections are as described above with respect to the pocket A1 104 a. [0091] In order to support voice commands, the pocket A2 104 b must be programmed to convey appropriate messages between the telephone 102 b and the docking station 106. For instance, the pocket A2 104 b must be capable of providing the telephone 102 with a telephone control signal directing the telephone 102 to pick up an incoming call. This is in contrast to the example given above with respect to pocket A1 104 b in which the user must press a button on the keypad 112 of the telephone 102 to pick up an incoming call. In addition, the microprocessor 320 of the pocket 104 b must include API commands for functions such as answering an incoming call. Apart from enabling additional functionalities such as voice recognition and voice memorandum recording, the pocket A2 104 b is, according to one embodiment of the present invention, the same as pocket A1 104 a. [0092] Audible voice prompts are, according to an embodiment of the system 100 of the present invention, provided to guide a user operating the system 100. Audible prompts are particularly advantageous when used in connection with voice recognition functions because they facilitate operation of the system 100 without requiring that the user look at the system 100 itself. For example, the system 100 may acknowledge commands given by the user, or provide the user with information concerning the status of the system 100. The audible prompts may be pre-recorded and stored in the pocket memory 324 and/or the docking station memory 340, with or without compression. Alternatively or in addition, the audible prompts may be generated from text stored in memory 324 or 340 using a text to speech functionality (described below). According to one embodiment, the voice prompts are stored in easily changed memory 324 or 340 cartridges, to allow the existing system 100 to be upgraded, or to accommodate a different or an additional language. [0093] The docking station 106 may include speech recognition functions to enable the system 100 to recognize voice commands. The docking station used in connection with pocket A2 104 b may be identical to the docking station 106 used in connection with pocket A1 104 a. Alternately, the docking station 106 used in connection with pocket A2 104 b may be enhanced to provide voice recognition functions. Even if the docking station 106 is provided in various models offering differing capabilities, any docking station 106 is preferably compatible, at least in part, with any pocket 104. In general, speech models are stored in the docking station memory 340 or the pocket memory 324 to enable the system 100 to recognize universal commands such as “answer call” or “place call.” Different memory 324 or 340 cartridges may be provided to conveniently upgrade the speech models or change them to a different language. In addition, provision may be made in the docking station 106 for storing user defined commands, such as “call home” or “call Mary.” According to one embodiment of the present invention, the user defined commands and voice memoranda may be stored in removable memory 324 or 340 to facilitate their use in other systems 100 or in compatible devices, to archive memoranda, or to allow the use of different command sets. The removable memory 324 or 340 may comprise a RAM memory card. The pocket A2 104 b may be provided with buttons 142 (see FIG. 1B) to enable the user to signal the system 100 to enter a voice command mode or voice memo record mode. [0094] The operation of the system 100 in processing a voice command will now be explained in the context of an example. Where a telephone call is not in progress (i.e. the telephone 102 is on-hook), a user may command that a general voice recognition mode be entered by uttering a special initiator word (e.g., “CellPort”). The system 100 may also be provided with a “barge-in” capability to allow voice recognition mode to be entered even while a telephone call is in progress (i.e. the telephone 102 is off-hook). Alternatively, the user may press a button 142 a provided on the exterior of the pocket 104 b to place the system 100 in voice recognition mode. Upon receiving the signal to enter voice recognition mode, the processor 320 sends a message across the pocket-docking station communication bus 322 to the docking station microprocessor 328 via the UART 338. The message sent by the microprocessor 320 is formatted according to the API of the system 100. Upon receiving the message to enter voice recognition mode, the docking station microprocessor 328 activates or otherwise communicates with the microphone 368. When a voice command is used, the docking station microprocessor 328 will cause the system 100 to enter a general voice recognition mode after a prescribed voice command has been issued by the user [0095] Voice commands issued by the user are converted into analog electrical signals by the microphone 368 and passed through the near-end CODEC 334, where the analog signals are digitized. The digitized voice commands are then compared in the docking station microprocessor 328 to the standard and customized speech models stored in the flash memory 340. If, for example, the user issues the command “call home,” the docking station microprocessor 328 will attempt to match those words to the stored word models. Upon finding a match, the docking station microprocessor 328 will initiate action according to the command. Thus, when the command “call home” is received, a signal to initiate a telephone call will be formatted in the API of the system 100, and passed to the microprocessor 320 of the pocket A2 104 b, where the API command is translated into a signal understood by the telephone 102. Where the telephone number associated with “home” is stored in memory 324 or 340, the command to the telephone 102 may consist of the digits of the telephone number and the send command. Alternatively, where the telephone 102 allows access to telephone directories stored in its internal memory, the command from the docking station microprocessor 328 may be in the form of a command to retrieve a number from a specified memory location in the telephone 102 and to initiate the send function. [0096] The functions provided by the level two pocket A2 104 b may also include provisions for voice memo recording. Thus, by pressing the associated buttons 142 b, or by issuing the appropriate voice command, such as “take a memo”, the system 100 may be configured to record a voice message. Such a capability is useful, for instance where a user wishes to give him or herself a reminder to do something without having to write the reminder down with pencil and paper. The voice memorandum capability is also useful for recording directions or a telephone number given by the person at the other end of the communications link. In voice memo recording mode, the voice message is converted to an analog electrical signal by the microphone 368 and transmitted to the near-end CODEC 334 where the signal is digitized. The digital voice memo is then processed and compressed by the docking station microprocessor 328 and stored in memory 340. When the user wishes to retrieve the voice memo, the user may press a button 142 c on the pocket A2 104 b causing a command to be sent from the microprocessor 320 across the pocket-docking station communication bus 322 to the docking station microprocessor 328, in the API of the system. The docking station microprocessor 328 then retrieves the message from memory 340, decompresses the message, performs signal processing functions, and provides a digital output of the message to the near-end CODEC 334, which converts the memo to an analog signal that is then amplified by the amplifier 344 and output at the speaker or headset 366. Where the command to replay a previously recorded voice memo is in the form of a voice command, the recognition of the voice command by the docking station microprocessor 328 initiates the retrieval of the voice message from memory 340 for playback through the speaker 366. In addition or as an alternative to playback through the speaker 366, the memorandum may be transmitted to another device for playback. For example, the memorandum could be transmitted by the telephone 102 to a remote telephone or device, or it could be transmitted to a computer or other external subsystem 378 for playback. [0097] A next level of functionality may be provided by the system 100 in connection with a pocket A3 104 c. The additional functions provided by the pocket 104 c may include storage for voice memos, directories and customized voice commands in the pocket 104. As illustrated in FIG. 6, the functionalities of pocket A3 104 c are fully supported by telephones A1 102 a, A2 102 b and A3 102 c. The docking station 106 may be identical to the docking station used in connection with any of the pockets A1-A4 104 a-c and B1-B4 104 e-h. The functionalities pocket A3 104 c shares with pockets A1 104 a and A2 104 b may be executed in the same manner as described above. [0098] The pocket A3 104 c is provided with memory 324 sufficient to allow the recordation of voice memos and for the storage of voice commands and directories programmed by the user in the pocket A2 104 c. In addition, a UART may be provided in the pocket A3 104 c to synchronize the transfer of voice memos and voice command data between the docking station 106 and the pocket 104. In general, the voice memo recording function using the pocket A3 104 c is identical to the function when carried out by pocket A2 104 b. However, the provision of additional memory 324 in the pocket A3 104 c allows for voice memos to be stored in the pocket A3 104 c. According to one embodiment of the present invention, voice memoranda may be stored in the pocket memory 324 as each memorandum is recorded. Alternatively, voice memoranda may be stored initially in the docking station memory 340, and later transferred to the pocket memory 324 automatically when the system 100 has the resources available to complete such a transfer. As yet another alternative, the user may initiate a transfer of voice memoranda data to the memory 324 in the pocket A3 104 c by, for example, pressing a button provided on the pocket A3 104 c or by issuing an appropriate voice command. Control logic provided in the pocket microprocessor 320 and/or the docking station microprocessor 328 may be provided to control whether data already written to the memory 324 is overwritten by new data. For example, the user may be notified when the memory 324 is full, and given a choice as to whether old data should be overwritten. After the voice memoranda has been transferred to the pocket memory 324, the pocket A3 104 c, which is easily disconnected from the docking station 106, can then be taken to, for example, the user's office. The pocket A3 104 c may then be interconnected to a device in the office having a microprocessor and associated speaker, similar to the docking station 106, for playback of stored messages. The UART 402 in the pocket A3 104 c allows the memo data to be transmitted over a dedicated line for storage in the pocket A3 104 c. [0099] The ability to store customized directories and voice commands in the pocket A3 104 c allows a user to use those customized features in any car equipped with a suitable docking station 106. Therefore, by moving the telephone 102 and the pocket A3 104 c different users may share an automobile, while retaining access to their own directories and commands. This feature is also useful where a user rents an automobile provided with an docking station 106, as all of the user's personalized information can be carried in the pocket A3 104 c. [0100] A further level of functionality may be provided by the system 100 in connection with pocket A4 104 d. As illustrated in FIG. 6, the functionalities of pocket A4 104 d are fully supported by telephone A3 102 c, but only partially supported by telephone A1 102 a and telephone A2 102 b. Pocket A4 104 d fully supports the functionalities of telephones A1-A3, 102 a-c. The additional functionalities provided or enabled by pocket A4 104 d may include text to speech capability. The text to speech function allows the system 100 to convert information received in the form of written text to audible speech. However, the text to speech function generally requires a telephone 102 capable of receiving textual information. According to the example illustrated in FIG. 6, telephone A3 102 c is the only telephone from manufacturer A having e-mail or Internet browsing capabilities. In the example of FIG. 6, telephones A1 102 a and A2 102 b lack the capability to receive information in the form of text and therefore cannot fully support the text to speech function. However, it should be noted that some text to speech capability may be possible in connection with telephones A1 102 a and A2 102 b, for example where information in the display 114 of the telephone 102 a or 102 b, such as caller ID information, is provided at the electrical connector 116 of the telephone 102 a or 102 b, in which case the information can be presented to the user as audible speech. In addition, the text to speech function may service other subsystems 378 capable of providing textual output. Generally, the pocket 104 d provides all of the functions described above with respect to pockets A1-A3, 104 a-c. [0101] The pocket A4 104 d is provided with commands in the microprocessor 320 to support the receipt of textual information from the telephone 102 c. The information received by the telephone 102 c is formatted into the API of the system 100 by the microprocessor 320 and transmitted to the docking station 106 over the digital data signal line 308 or the pocket-docking station communication bus 322. According to one embodiment of the present invention, the docking station 106 for use in connection with the pocket A4 104 d includes an additional processor at the custom interface 348, which may be conveniently mounted on a daughter board 380, for performing the text to speech function. Generally, the processor at the custom interface 348 transforms the received text into digitized speech, which can then be passed to the docking station microprocessor 328, and from there to the near-end CODEC 334 for conversion to an analog audio signal. The analog audio signal is then output through the speakers 366. The use of an additional processor at the custom interface 348, which can be added to the normal docking station 106, is desirable in that it allows for the use of a specialized processor for handling the relatively complex text to speech translation function. Additionally, it allows docking stations 106 not intended for use with a text to speech enabled pocket 104 and telephone 102 to be produced at a lower cost. As alternatives, the docking station microprocessor 328 may be sufficiently powerful or robust to perform the text to speech function, or an enhanced docking station 109, having a text to speech enabled docking station microprocessor 328 may be offered in addition to the normal docking station 106. As a further alternative, an enhanced microprocessor 320 in the pocket, or an additional microprocessor, may be provided in the pocket A3 102 c to handle the text to speech function. Apart from enabling additional and/or different functionalities, such as text to speech, the pocket A3 104 c is generally the same as pocket A1 104 a and A2 102 b. [0102] In connection with the above description of pockets A1-A4 104 a-d and their functional capabilities, a user may generally choose the capabilities of the system 100 according to the user's needs and desires by choosing the appropriate pocket A1-A4 104 a-d. Thus, a user owning any of telephones A1-A3 102 a-c can choose a system 100 having basic hands-free capabilities by purchasing pocket A1 104 a and docking station 106. By purchasing pocket A2 104 b and an docking station 106, a user may obtain voice command and voice recording capabilities. The use of pocket A3 104 c in connection with a docking station 106 provides the user with a system 100 that allows voice memos and programmed voice command information to be stored in the easily transported pocket A3 104 c. Accordingly, it is the pocket A1 104 a, A2 104 b, or A3 104 c that determines what capabilities the system 100 provides when used in connection with either a telephone A1 or A2 102 a or 102 b. Also, when purchasing a new pocket 104 in order to obtain advanced features or to accommodate a different telephone 102, the user need not replace the docking station 106. Furthermore, the same docking station 106 may be used in connection with pockets A1-A3 104 a-c. [0103] A system 100 providing text to speech capabilities may be obtained by using a docking station 106 with an additional or an enhanced processor or an enhanced docking station 109, pocket A4 104 d, and telephone A3 102 c. Although the docking station 106 or 107 used in connection with pocket A4 104 d in this example provides enhanced capabilities, it should be noted that, except for the text to speech function, pocket A4 104 d is fully supported and fully compatible with the general docking station 106. Similarly, pocket A4 104 d can be used with telephones A1 or A2 102 a or 102 b. [0104] With continued reference to FIG. 6, the relationship between telephones B1-B4 102 d-g, pockets B1-B-4 104 e-h, and docking station 106 are illustrated. In general, pockets B1-B4 104 e-h provide the four levels of functionality described above with respect to pockets A1-A4 104 a-d, but are designed to physically and electrically interconnect with telephones B1-B4 102 d-g produced by manufacturer B. However, the pockets B1-B-4 104 e-h are designed to work with the same docking station 106 as pockets A1-A4 104 a-d. [0105] As shown in FIG. 6, pockets B1 and B2 104 e and 104 f are fully compatible with telephones B1 and B2 102 d and 102 e, but only partially compatible with telephones B3 and B4 102 f and 102 g. Additionally, pockets B3 and B4 104 g and 104 h fully support the functional capabilities of telephones B3 and B4 102 f and 102 g, but are only partially compatible with telephones B1 and B2 102 d and 102 e. This situation may occur, for instance, where telephones B1 and B2 102 d and 102 e feature an older interface used by manufacturer B, while telephones B3 and B4 102 f and 102 g use a newer interface. Therefore, even though the telephones B1-B4 102 d-g may have the same physical characteristics, changes to the interface used to control and send data to and from the telephones 102 d-g will affect their compatibility with the pockets 104 e-h. According to an embodiment of the system 100, where a user has upgraded their telephone 102, but wishes to use a pocket having an interface adapted for an earlier model of the telephone 102, provided that the telephone 102 and pocket 104 are still physically compatible, the pocket 104 can be upgraded by modifying the memory 324 of the pocket 104 to enable the pocket 104 to properly interact with the telephone 102. [0106] Modifications to the memory 324 may be made by transmitting the upgrade to the memory 324 through a physical connection to a component of the system 100. For example, the pocket 104 may be connected to a personal computer that has been used to download a programming upgrade from an Internet website, or to read new programming code distributed on a floppy disk, CD ROM, or other storage medium. Alternatively, the docking station 106 could be connected to a personal computer, and new programming code loaded onto the memory 340 of the docking station 106. Regardless of whether the pocket 104 or the docking station 106 is used to initially receive the updated programming code, the programming code resident in the pocket memory 324, the docking station memory 340 or both can be modified using the above-described methods. [0107] Where a telephone 102 capable of downloading information from the Internet is available, that telephone 102 may be used to download new programming code to upgrade the pocket 104 and/or the docking station 106. Another method of upgrading the programming code of the system 100 is for the user to purchase an upgraded pocket 104 that contains new programming code for upgrading the code stored in the docking station memory 340. Similarly, a docking station 106 containing the necessary code may be used to upgrade the code resident in the pocket memory 324. As yet another method of upgrading the code resident in the memory 324 or 340, all or portions of the memory 324 or 340 may be augmented or replaced by memory 324 or 340 having upgraded programming code. [0108] However, modifying the memory 324 to properly translate between a new telephone interface and the API of the system 100 will not be sufficient where the manufacturer has made changes to the physical configuration of the telephone 102. Also, changes to the memory 324 alone will not be sufficient where the user has, for instance, purchased a new telephone from a different manufacturer having a different physical configuration. In these instances, compatibility with the system 100 may be regained by obtaining a new pocket 104 that is compatible with the user's new telephone 102. When purchasing a pocket, the purchase cost of a pocket 104 is less than the purchase cost of both a pocket 104 and a docking station 106, as the docking station 106 originally purchased by the user may be used with the new pocket 104. [0109] The multiple-processor multiple-bus configuration of the system 100 allows the system 100 to be designed using modular units. In particular, the system 100 provides a pocket 104 for at least every combination of physical and electrical characteristics found in supported telephones 102. The system 100 allows the use of a common docking station 106 by converting the unique physical and electrical characteristics of supported telephones 102 to a common electrical and physical interface at the pocket 104. Therefore, common system components can be placed within the docking station 106, while particular attributes required by particular telephones 102 can be accommodated by the pocket 104. In this way, the cost of the system 100 can be reduced and the flexibility increased. [0110] The application programming interface (API) of the system 100 is the common language used to communicate commands and information between the pocket 104 and the docking station 106. Translation between the interface of the telephone 102 and the API of the system 100 is performed in the pocket 104, and in particular in the microprocessor 320. After translation in the microprocessor 320, commands and information originating at the telephone 102 can be transmitted using the API to the docking station 106 over the pocket-docking station communication bus 322. Commands and data originating at the docking station 106 and at the system 100 follow the reverse course, with commands and data formatted in the API of the system 100 being translated into the telephone's 102 unique interface at the microprocessor 320 of the pocket 104. [0111] Where the system 100 is to be interconnected with subsystems 378 in addition to the telephone 102, an additional processor or custom interface 348 may be provided to perform translation between the API of the system 100 and the interface of the subsystem 378 to which the system 100 is interconnected. Preferably, the custom interface 348 may be provided in the form of an add-on or daughter board 380 that can be interconnected to the docking station microprocessor 328 using provided electrical contacts. Thus, connectivity to various other subsystems 378 may be achieved without requiring changes to the docking station's 106 main components or to the pocket 104 presently in use. Alternatively, or in addition, the subsystem 378 can communicate using the API of the system 100, without requiring any translation. For example, the interface required to communicate with an external subsystem 378 may be resident in the docking station 106. The custom interface 348 and daughter board 380 may simply provide a mechanical connection, or may not be provided at all where the external subsystem 378 interface is resident in the docking station 106. [0112] As mentioned above, the external subsystem 378 may comprise a variety of electronic devices. The subsystem 378 may include protocol based units and close-ended devices. The protocol based units can include networks and busses having associated components or peripheral devices that are interconnected. The close-ended devices are referred to herein as devices that do not have International Standards Organization (ISO) network layering and typically constitute a terminating communication node in the context of data flow ending or originating from such device, and not typically acting as a link or pass-through device for information or data transfers. An example of such a close-ended device might be a global positioning system (GPS) that is useful in providing vehicle location information, or a hardware device, such as a vehicle sensor, from which data can be obtained for a particular vehicle component to which the sensor is operably connected. [0113] In addition to the GPS, the external subsystem 378 may include an Internet Protocol (IP) stack comprised of a number of network layers that are commonly involved in transfers using the Internet. The external subsystem 378 can also include an intelligent transportation system data bus (IDB) and/or an on-board diagnostics (OBD) system that are involved with monitoring and providing information related to vehicle components. [0114] The external subsystem 378 may also include computing devices, such as laptop or notebook computers, PDA's, or other devices. The external subsystem 378 may also include applications running on such devices. In particular, the external subsystem may include Internet aware applications or other applications capable of passing data to or from another application over a communications link. [0115] Other external devices or subsystems 378 may include devices that monitor the operating status of a vehicle 302. In general, such devices record information such as engine oil pressure, fuel consumption, the operating temperature of the engine, vehicle acceleration and deceleration, vehicle speed, distance traveled, engine RPM, tire pressure, etc. Such an external device 378 may also include a system for determining the geographical location of the vehicle 302, such as a global positioning system (GPS) receiver. The information collected may be transmitted from the vehicle 302 to a base station over a wireless communications channel established by the wireless communications device or telephone 102. In addition, the external device 378 may be capable of receiving voice or text messages from a base station or external devices 378 located in other vehicles 302 and displaying or playing those messages to the driver of the vehicle 302. Likewise, voice or text messages may be sent from the driver of the vehicle 302 to the base station or to external devices 378 located in other vehicles 302 through the external subsystem 378 and the wireless communications device 102. [0116] The external subsystem 378 may also include a controller area network (CAN) found in at least some vehicles and which includes a bus along which a number of vehicle elements communicate for supplying information concerning such elements. The CAN is operatively connected to each of a plurality of vehicle devices that transmit, receive, or both transmit and receive desired data. For example, the vehicle devices include transducers or other physical devices that detect and provide information useful to applications software for processing to obtain information that is then transmitted for storing in memory for later transmission, or even for immediate transmission without processing, upon receipt of the proper request or command. Other available networks could be utilized, instead of CAN, such as Arcnet, which has a protocol similar to CAN. Where the external subsystem 378 includes one of a plurality of vehicle busses, the hardware supplied for interconnecting the external subsystem to the docking station 106, such as the daughter board 380, may include provisions for signaling to the docking station microprocessor 328 the format of the output required by the particular external subsystem 378. For example, the daughter board 380 may comprise cabling, and the presence or absence of a resistor between two signal paths may be used to indicate to the microprocessor 328 the proper voltage at which signals are to be transferred to and from the external subsystem 378. For further information regarding obtaining information or data from vehicle devices, see U.S. Pat. No. 5,732,074, filed on Jan. 16,1996 and assigned to the assignee of the present invention. The external subsystem 378 may also comprise an analog/digital converter (ADC), a standard serial bus, a universal serial bus (USB), an RS232 connection, a user datagram packet/Internet protocol stack, as well as one or more other custom proprietary devices. [0117] Other devices that may comprise the external subsystem 378 may include a PCMCIA (Personal Computer Memory Card Interface Association) unit, which may include a storage device for storing desired information or data. The external subsystem 378 may also include a device capable of communication using the Bluetooth protocol, which provides a standard protocol for the wireless communication of information between disparate devices. [0118] The protocol used for communications between the pocket 104 and the docking station 106, according to an embodiment of the present invention, is half duplex. Accordingly, there can only be one message in the pocket-docking station bus 322 at any one time. Normally, messages are responded to with either an ACK, acknowledging correct receipt of the message, or a NACK, indicating a problem. A response may be suppressed by issuing a “do not acknowledge” command with the message. In general, the combined message-response pair must be completed before another message can be placed on the bus. A time out period for failed messages may be established, and messages not receiving an acknowledgment within a selected period of time (e.g., 1 second), will be retransmitted up to a selected number of times (e.g., 8 times). [0119] According to an embodiment of the present invention, the pocket 104 acts as the bus master, and the docking station 106 acts as the slave. As master, the pocket 104 may issue API commands to the docking station 106 at any time. Periodically, the pocket 104 issues a bus grant message to the docking station 106 after which the docking station 106 may send a command to the pocket 104. After receiving the bus grant message, the docking station 106 can either send a pending message or reply with a bus release message. According to an embodiment of the present invention, the bus grant message is sent once every second, and the docking station 106 has 500 ms to issue a pending message or a bus release message. [0120] With reference now to FIG. 7, the pocket communications state machine in accordance with another embodiment of the present invention is illustrated. Generally, as noted above, the pocket 104 and the docking station 106 are in a master and slave relationship. As shown in FIG. 7, at state 702, the pocket 104, and in particular the microprocessor 320, awaits a message from the telephone 102. Upon receiving a telephone message, the pocket 104 enters state 704 in which the telephone request is handled. After handling the telephone request, the pocket 104 then enters state 706 in which the telephone request is sent to the docking station 106. Next, the pocket 104 awaits a message from the docking station 106 in state 708. If no message is received from the docking station 106, the pocket 104 then returns to state 702. A system 100 also includes the timer that operates in cooperation with determining whether or not a message is received. During normal operation, when no response is received from the docking station 106, another pulse or heartbeat is sent at predetermined times. However, if there is no response within a time interval associated with the timer timing out, a hardware reset line is enabled to reset the docking station 106. Where a docking station 106 message is received, the pocket handles the message in state 710, following which it returns to state 702. Where no telephone message is received, the pocket 104 periodically polls the docking station 106 at state 712. According to an embodiment of the present invention, the pocket 104 polls the docking station 106 every 72 milliseconds (i.e., the pocket 104 heartbeat rate is 72 milliseconds). After polling the docking station 106 in state 712, the pocket 104 enters state 708 in which it awaits a message from the docking station 106. If no message from the docking station 106 is received within 10 milliseconds of polling the docking station 106, the pocket 104 returns to state 702, in which it awaits a telephone 102 message. According to one embodiment of the present invention, communications between the pocket 104 and the docking station 106 occur at 19,200 baud, using eight data bits, one parity bit, and no stop bit. According to another embodiment of the present invention, the data between the pocket 104 and the docking station 106 is transmitted at 115200 bps, using 8 data bits, no parity, and one stop bit. However, other communication rates can be used, and may even be varied. [0121] Referring now to FIG. 8, the architecture of the docking station 106 software showing the relationships among the various software objects, is illustrated. In general, the top level loop is the processor (or digital signal processor) object 802. Thus, the power supply control 804, audio control 806, flash file system 808, user interface 810, voice memo recording 812, voice recognition 814, and pocket communications 816 objects can all be entered from the main loop 802 directly. Other software objects or modules are addressed in response to interrupts. Accordingly, communications between the pocket 104 and the docking station 106 generate an interrupt causing the software to enter the UART object 818. Activity concerning the near-end CODEC 334 is handled at object 820 across the interrupt boundary from the voice memo recording 812 and voice recognition 814 objects. Sound processing 822 and far-end CODEC 824 objects are associated with the near-end CODEC 820 object. [0122] The progression of typical communications scenarios are illustrated in FIG. 9. In FIG. 9, message A is shown originating in the pocket 104. An acknowledgment of message A originates in the docking station 106, and is transmitted to the pocket 104. A second message, message B, originates at the pocket 104, and is passed to the docking station 106 . After a one second time out, during which no message is received at the pocket 104, message B is retransmitted. Next in the diagram, the pocket 104 issues a bus grant message. In response to the bus grant, the docking station 106 issues a pending message, message C. In response to message C, the pocket 104 issues an acknowledgment. The pocket 104 next issues another bus grant. In response, the docking station issues a bus release message, as the docking station has no pending message. After one second, the pocket 104 again issues a bus grant message. Receiving no reply, after a 0.5 second time out, the pocket 104 issues a second bus grant message. Again receiving no reply, the pocket 104 issues yet an other bus grant message. The above-described typical scenarios serve as examples, and it will be appreciated that additional alternative scenarios are possible. [0123] With reference now to FIG. 10, a pocket 104 worst case scenario is illustrated. In FIG. 10, message A, is shown queued in the docking station 106. Message A is released after synch 2 to the pocket 104. At the time Message A is released, Message b is received from the telephone 102. In response to this situation, the pocket can immediately pass Message A to the telephone and return Response A to the docking station, while delaying handling of Message B from the telephone, or the pocket can communication Message B to the docking station as Message B while delaying the handling of Message A. [0124] With reference now to FIG. 11, a docking station 106 worst case scenario is illustrated. In FIG. 11, Message C is shown queued in the docking station 106. Shortly after Message C is queued, Message a is received at the telephone 102 and is communicated through the pocket 104 and to the docking station 106 as Message A. Then while Message C continues to be queued, Response A is communicated to the telephone 102 as Response a. Message B is then received at the telephone 102 and is communicated to the docking station 106 through the pocket 104 as Message B. The docking station 106 then sends Response B through the pocket 104 into the telephone 102 as Response b. Following the receipt of Response b at the telephone 102, a synchronization signal, labeled Synch 2, is sent from the pocket 104 to the docking station 106, causing the release of the queued message. Message C is then delivered to the pocket 104, and Response C delivered from the pocket 104 to the docking station. Therefore, in this worst case scenario, Message C could not be handled until Messages A and B had been dealt with, and the synchronization signal received. [0125] According to one embodiment of the system 100 of the present invention, the docking station 106 is provided with programming instructions necessary for communicating with the telephone 102. According to this embodiment, the pocket 104 need not be provided with a microprocessor 320 or memory 324. Instead, the pocket 104 may simply provide a physical interconnection to the telephone 102, and for the transfer of signals from the telephone 102 directly to the docking station 106. Where the docking station 106 is not intended to interconnect to telephones 102 having a variety of physical characteristics, the pocket 104 need not be a component that is separate and distinct from the docking station 106. According to one embodiment, the docking station 106 may be provided with programming code enabling it to interface with a variety of telephones 102. Thus, the pocket 104 may provide a signal to the docking station 106, for example, by providing differing voltage levels at input pins associated with the docking station 106 microprocessor 328 to indicate the type and capabilities of the telephone 102. The docking station 106 may use this information to select the appropriate command set for communicating with the telephone 102. The docking station 106 may be upgraded to provide advanced capabilities, or to communicate with additional telephones 102 through upgrades to the programming code generally stored in the docking station memory 340. The upgrades may be provided to the docking station 106 by interconnecting the docking station 106 to a personal computer that has read or downloaded the code upgrade, or by downloading the upgrade through an Internet-enabled telephone 102 directly to the docking station 106. [0126] The text to speech functionality described above with respect to certain embodiments of the present invention may be augmented by the ability to visually display textual information. Accordingly, textual information may be displayed, for example, on a screen associated with an external subsystem 378. Thus, textual information may be displayed on the screen of a personal digital assistant (PDA), a personal computer, or a display screen provided by the automobile 302. The system 100, upon receipt of textual information, may in a default mode provide a visual output of text where a visual display is interconnected to the system, and an audible output. The user may also select whether textual information is to be provided audibly or visually. For example, a user may command the system 100 to “read e-mail.” Alternatively, the user may command the system 100 to “display e-mail.” [0127] The system 100, particularly in connection with an automobile 302, may provide a variety of useful, automated functions. For example, the docking station 106 may be provided with a custom interface 348 that includes a telematics module to monitor activity occurring on an external subsystem 378. For instance, where a first external subsystem 378 is a vehicle bus, a message indicating a low fuel status transmitted over the bus may be decoded by the custom interface 348. The custom interface 348 may then cause a query to be transmitted over the wireless link provided by the telephone 102 to a central station interconnected to the Internet. The query, which may be transmitted from the telephone 102 according to the Internet protocol, may request the location and prices of fuel available in the area. The response to the query may be provided to the user of the system 100 through a visual display provided as, for example, a second external subsystem 378, or may be provided audibly to the user through the text to speech capabilities of the system 100. According to one embodiment, the query includes information concerning the location of the automobile 302. Such information may be provided automatically, for example, from a GPS receiver interconnected to the system 100 as a third external subsystem 378. Alternatively, location information may be provided by a telephone 102 capable of receiving GPS data. [0128] With reference now to FIG. 12, a system 100 in accordance with an embodiment of the present invention is illustrated. The system 100 shown in FIG. 12 interconnects a telephone 102 to a plurality of applications 1200 a, 1200 b, and 1200 c running on external subsystems 378 a, 378 b and 378 c. As shown in FIG. 12, the docking station 106 of the illustrated embodiment includes a custom interface 348, which may be included as part of a data daughter board (DDB) 380, for providing an interface between the docking station 106 and the external subsystems 378 a-c. Although the following discussion will generally describe a custom interface 348 that is provided as part of a data daughter board 380, the custom interface may be provided as part of the docking station 106 itself. For example, the custom interface 348 or any other interface, may be provided as part of a main circuit board of the docking station 106. Alternatively, at least some of the components or functions of the interface 348 may be provided as part of a cable interconnecting the external subsystem to the docking station 106. [0129] The custom interface 348 may include a local network interface 1204 for providing ports 1208 a-b to interconnect subsystems 378 a and 378 b, and the associated applications 1200 a and 1200 b, to the docking station 106 over signal lines 376 a and 376 b. For example, the local network interface 1204 may comprise an interface for TCP/IP formatted data, such as an Ethernet network card. Although only two applications 1200 a and 1200 b are illustrated as being interconnected to the docking station 106 over signal lines 376 a and 376 b, it can be appreciated that the number of applications 1200 that can be so interconnected is limited only by the capacity of the local network. As will be understood by those of skill in the art, the network interface 1204 may comprise a network hub alone or in combination with a network interface card. As will also be understood by those of skill in the art, more than one application 1200 may be running on a single external subsystem 378. [0130] The custom interface 380 may, in addition or as an alternative to a local network interface 1204 for use with wired signal lines 376 a, comprise a local wireless network interface 1212. In an embodiment in which a local wireless network interface 1212 is provided, a wireless line or lines of communication 376 c serve to transmit information between the local wireless network interface 1212 and the application 1200 c running on the external subsystem 378 c. As shown in FIG. 12, the local wireless network interface 1212 may be interconnected to the docking station 106 via a connection to a port 1208 c on the network interface 1204. Alternatively, the wireless interface 1212 may be directly interconnected to the docking station 106. Although only one application 1200 c is shown in communication with the docking station 106 over the wireless signal line 376 c, it can be appreciated that the number of applications so interconnected depends only on the capacity of the local wireless network. Furthermore, it will be appreciated that more than one application 1200 may be running on a single external subsystem 378 interconnected to the docking station by the wireless signal line 376 c. [0131] In general, the interface or interfaces provided by the custom interface 348 allow information to be passed between the docking station 106 and the interconnected external subsystems 378 as digital packet data. For instance, data may be passed between the interface 348 and the external subsystems 378 as packets of data formatted according to a data transmission protocol, such as the TCP/IP protocol. By providing a standard interface (i.e., the custom interface 348), the data daughter board 380 allows the docking station 106 to interface with any application 1200 running on an external subsystem 378 that is capable of communicating over a network using such a data transmission protocol. Therefore, the applications 1200 may include applications running on an external subsystem 378 comprising a computer equipped with a network interface that is compatible with the interface 348. Suitable computers include laptop and notebook computers. In addition, an application 1200 may be executed on a personal digital assistant (PDA) or other device having an appropriate network connection. In general, any external subsystem 378 and associated application or applications 1200 capable of communicating with the provided interface 348 may be interconnected to the docking station 106 by the data daughter board 380. Accordingly, it can be appreciated that the interface 348 of the docking station 106 provides a physical communications layer between the external subsystem 378 and the docking station 106. The docking station 106, in cooperation with the adaptor 104, also provides translation between the API of the system 100, and the command set needed to operate the telephone 102. Accordingly, it should be appreciated that due to the physical and logical interface provided by the docking station 106 and the adaptor 104, neither the external subsystem 378 nor the application 1200 is required to provide the particular physical and logical interface required by the particular telephone 102 used to establish a communications channel 1220. [0132] Communications received from the applications 1200 are passed from the docking station 106 to the adaptor 104 by either the digital data path signal lines 308 or the pocket-docking station bus 322. Communications passed over the pocket-docking station bus 322 generally comprise wireless communications device control commands, as will be described in greater detail below. Data passed along the digital data path signal lines 308 generally include data for transmission by the telephone 102. Accordingly, data passed along the digital data path 308 is, according to one embodiment of the present invention, not altered by the adaptor 104 before it is transmitted to a base station or server 1216 by the telephone 102 across wireless communications channel 1220. According to another embodiment of the present invention, the data passed along the digital data path 308 is reformatted, such as from a serial bit stream format used along signal lines 376 to a parallel bit format used by the telephone 102. The reformatting of the data, where necessary, may be performed by the adaptor 104. Communications passed across the pocket-docking station bus 322 are generally translated by the adaptor 104 into the format required by the telephone 102 before being passed to the telephone 102 over the telephone control signal bus 314. For instance, communication channel control commands expressed in the API of the system 100 will be translated into corresponding wireless communications device control commands that can understood by the telephone 102, and the commands will be formatted according to the protocol required by the telephone 102. [0133] With reference now to FIG. 13, details of a data daughter board 380 comprising the interface 348 in accordance with one embodiment of the present invention are illustrated. As seen in FIG. 13, the local network interface 1204 is interconnected to a processor 1300 by an internal bus 1304. In the embodiment illustrated in FIG. 13, a local wireless network interface 1212 is interconnected to the processor 1300 via the local network interface 1204 and internal bus 1304. Accordingly, in this embodiment of the data daughter board 380, the local wireless interface 1212 acts as a device or network hub interconnected to the local network interface 1204. As noted above, the interface 348 may be implemented entirely or in part as an integral part of the docking station 106, as an alternative to being part of a data daughter board 380. In addition, in another embodiment of the present invention the interface 348 does not include a processor 1300. [0134] The processor 1300 may include a microprocessor or a digital signal processor. In general, the processor 1300 examines data packets received from the local network interface 1204 to determine whether they contain control commands directed to the operation of the telephone 102, or data for transmission across the wireless communications channel 1220. According to one embodiment of the present invention, control commands have a unique address to indicate to the processor 1300 that a communications channel control command is contained in the packet of data. For instance, control commands may be addressed to a virtual control data port established by the interface 348. Communications channel control commands are provided to the adaptor 104 over the pocket-docking station bus 322 by serial ports 1308, while data received from the applications 1200 for transmission is placed on the digital data signal lines 308 by the serial ports 1308. Where the telephone 102 supports, for example, an Internet Protocol (IP) data stream, the data may simply be bridged by the interface 348 between the signal lines 376 and the data signal lines 308. According to an embodiment of the present invention, the applications 1200 are configured to point to the interface 348 as their gateway. According to a further embodiment of the present invention, packets of data for transmission are addressed to a virtual data transmission data port and are thus recognized as containing data for transmission over the wireless communications channel 1220. [0135] According to an embodiment of the present invention, a telephone 102 that does not provide IP framed data may be used in connection with applications 1200 that communicate using a TCP/IP protocol. For instance, the telephone 102 may be capable of sending and receiving data using a wireless application protocol (WAP) or other protocol. Such a telephone 102 may be capable of accessing certain web pages on the Internet that are formatted so that the information contained on the pages can be displayed by the display 114 of the telephone 102. Furthermore, the displayed information may not be available as IP data from the electrical connector 116 provided on the telephone 102. However, signals representing the characters displayed by the telephone 102 may be available. In such instances, the interface 348 may packetize the data regarding the displayed characters and provide that data to an application 1200. The reverse of this operation may also be performed to send information from an application to a server 1216. Accordingly, the interface 348 may present a TCP/IP interface to an application 1200 even when the system 100 is used in connection with telephones 102 that provide a non-standard data stream. [0136] With reference now to FIGS. 3 and 13, communications channel control commands are passed between the docking station 106 to the microprocessor 320 of the adaptor 104 by the pocket-docking station bus 322. As will be described in greater detail below, the microprocessor 320 reformats the communications channel control command as required. In particular, the microprocessor 320 translates the command between the API of the system and the set of commands used by the telephone 102. For example, the microprocessor 320 may receive a communications channel control command that has been formatted according to the API of the system 100 and translate that command into a corresponding wireless communications device control command selected from the set of wireless communication device control commands used by the telephone 102. In this way, the adaptor 104 allows communications channel control commands formatted according to a general standard, such as the API of the system 100, to be reformatted so that they can be acted upon by a particular telephone 102. Therefore, the translation function provided by the adaptor 104 removes the need for the applications 1200 to issue commands using the command set of the telephone 102 in order to control the operation of the telephone 102. [0137] With reference now to FIG. 14, the operation of a system 100 in accordance with an embodiment of the present invention is illustrated. In particular, FIG. 14 illustrates the operation of an embodiment of the system 100 in connection with the receipt of data from an application 1200. [0138] Initially, at step 1400, a data packet is received from an application 1200 at the docking station 106. The data packet is received by the local network interface 1204 and passed to the processor 1300. The processor 1300 determines whether the received data packet is addressed to the virtual control data port or whether it contains data for transmission (step 1404). If the data packet contains a communications channel control command, it is addressed to the logical or virtual control data port, and is directed to the microprocessor 320 of the adaptor 104 over the pocket-docking station control bus 322 (step 1408). The microprocessor 320 receives the control command, which is formatted according to the API of the system 100, and generates a wireless communications device control command that is formatted according to the requirements of the telephone 102 (step 1412). The telephone-specific command is then passed to the telephone 102 over telephone control signal bus 314 (step 1416). [0139] If the data packet contains data for transmission, and if the telephone 102 can send and receive TCP/IP formatted data, the data is passed to the telephone 102 directly. In particular, data for transmission is communicated to the telephone 102 over the digital data path signal lines 308, without alteration by the microprocessor 320. Accordingly, in connection with data for transmission, the function of the adaptor 104 is to provide a physical interconnection between the telephone 102 and the digital data path signal lines 308. According to a further embodiment of the present invention, the data for transmission may be reformatted as a parallel bit stream before it is passed to the telephone 102, for those telephones 102 that provided and receive a parallel bit stream at the electrical connector 116. [0140] With reference now to FIG. 15, the operation of the system 100 in accordance with an embodiment of the present invention in response to a request by an application 1200 for a communications channel 1220 is illustrated. Initially, at step 1500, a local communications channel is established between the application 1200 and the docking station 106. For example, the user of a laptop computer may establish a signal line 376 a by using a cable to interconnect the docking station 106 and the laptop computer 378, thereby providing a physical channel for data to be passed between the application 1200 and the docking station 106. Next, at step 1504, the application 1200 requests a wireless communications channel 1220. According to the present example, the application 1200 may involve any Internet-aware application. For example, the application 1200 may be an Internet browser. The request is made using a command selected from the commands comprising the API of the system. Because the data packet contains a communications channel control command, it will be addressed to the data control port of the data daughter board 380. The docking station 106 recognizes that the data packet contains a communications channel control command because it is addressed to the control data port of the interface 348. Accordingly, the docking station 106 passes the command to the adaptor 104 over the pocket-docking station communications bus 322 (step 1508). [0141] The adaptor 104 receives the request formatted according to the system protocol (e.g., the API of the system 100), and reformats the request as required by the telephone 102 (step 1512). For example, the command to access or establish a communications channel 1220 may comprise a command to dial a specified number. In response to such a command, the adaptor 104 must provide the telephone 102 with electrical signals at the correct pins of the electrical connector 116 and in the correct sequence in order to simulate entry of the number using the keypad 112 of the telephone 102. The reformatted request is provided to the telephone 102 over the telephone control signal bus 314 (step 1516). Accordingly, the adaptor 104 provides the request using commands selected from the set of wireless communications device control commands understood by the telephone 102 and in the format required by the telephone 102, and provides the electrical connector required to provide the request to the telephone 102. [0142] The telephone 102, in response to the request, establishes a communications channel 1220 with the base station or server 1216 (step 1520). How the telephone 102 establishes the communications channel 1220 depends on the particular telephone 102. For example, a telephone 102 having a dedicated data transmission channel may simply perform the steps necessary to activate that channel. Alternatively, the telephone 102 may be directed to a server or base station 1216 specified by the application 1200. For example, the request to establish a communications channel 1220 may include a direction to the telephone 102 to dial a specified telephone number and ready itself for data transmission. It should be appreciated that the request to establish a communications channel 1220 may be communicated by providing the telephone 102 with a series of data packets. For example, the telephone 102 may be provided with each digit of a telephone number serially, followed by a command to dial. [0143] As a further example, the command to access or establish a communications channel 1220 may contain no specific information regarding the gateway or server 1216 with which the channel 1220 is to be established. In such instances, the adaptor 104 or the docking station 106 may provide a previously stored telephone number to be dialed. If the telephone 102 is capable of establishing a communication channel 1220 for transmitting data without using a dial up connection, the command that is provided to the telephone 102 need only comprise an instruction to establish the communications channel 1220. If a request for a communications channel 1220 is received from a second application 1200 b after the communication channel 1220 has already been established by, for example, a first application 1200 a, the request does not need to be provided to the telephone 102. Instead, the docking station 106 may recognize that a channel 1220 has already been established and may provide a signal to the application 1200 b indicating that the channel 1220 is available. [0144] In general, the telephone 102 will provide a signal indicating that the communications channel 1220 has been established and is ready to transmit data. The telephone 102 issues this signal using the protocol determined by the manufacturer of the particular telephone 102. Accordingly, the confirmation of channel availability may be provided as a serial or parallel bit stream that encodes information regarding the available channel 1220. Alternatively, the availability of a channel 1224 may be signaled by changing the voltage at a single contact of the electrical connector 116. Regardless of how the telephone 102 signals the availability of the channel 1220, the signal is received by the adaptor 104 is translated and reformatted to comply with the API of the system 100 (step 1524). The translated and reformatted signal is then passed to the docking station 106 and, according to the present example, formatted as a TCP/IP data packet by the interface 348 and passed to the application 1200. [0145] After the availability of the channel has been communicated to the application 1200, data may be passed from the application 1200 to the wireless communications device 102 via the docking station 106 and adaptor 104 for transmission to the server or base station 1216 (step 1528). The data that is passed between the server 1216 and the application 1200 is generally not reformatted by the adaptor 104. Instead, the data for transmission, which is formatted according to a universal protocol, such as TCP/IP, is supplied directly to the telephone 102 from the application 1200 as a serial bit stream. However, when required by the telephone 102, the serial TCP/IP data stream from the application 1200 is reformatted. For instance, the data may be presented to the telephone 102 as a parallel bit stream. [0146] With reference now to FIG. 16, the operation of a system 100 in accordance with an embodiment of the present invention is illustrated in the context of an example. For purposes of this example, it will be assumed that the system 100 is installed in an automobile 302. According to this example, the external subsystem 378 a includes a laptop computer, external subsystem 378 c includes a PDA, application 1 1200 a includes an Internet browser, and application 1200 c includes an e-mail program. Initially, at step 1600, user 1 attaches her laptop computer 378 a to a local network interface 1204 port 1208 a on the docking station 106 using a cable, thereby establishing a signal line 376 a. For purposes of the present example, the local network interface 1204 can be assumed to be an Ethernet network card, and it will be assumed that the laptop computer 378 a is also equipped with an Ethernet network card. The cable 376 a connecting the Ethernet port of the local network interface 1204 to the Ethernet port of the laptop computer 378 a is an Ethernet cable having connectors for interfacing with mating connectors on the network cards. [0147] After completing the hardware connection with the docking station 106, user 1 activates an Internet browser application 1200 a on her laptop computer 378 a, which results in a TCP/IP protocol request, formatted according to the API of the system 100, for an Internet connection. This request is sent from the laptop 378 a to the docking station 106 (step 1604) over the cable 376 a. [0148] The interface 348 of the docking station 106 recognizes that the request is addressed to the virtual control data port of the interface 348. Accordingly, the docking station 106 extracts the request for an Internet connection from the TCP/IP formatted packets, and passes the request over the pocket-docking station communications bus 322 to the adaptor 104 (step 1608). The adaptor 104 reformats the request as required by the particular telephone 102 to which the adaptor is interconnected (step 1612). Accordingly, the adaptor 104 operates the telephone 102 to establish a wireless communications channel 1220 to the Internet server 1216. According to this example, no phone number is provided by the browser 1200 a or any other application remaining on the laptop computer 378 a. Instead, the telephone 102 is provided with a telephone number to dial that has previously been stored in the adaptor 104. The telephone number may be a telephone number for a dial up Internet account maintained for the automobile 302. Once the communications channel 1220 has been established, the telephone 102 signals that an Internet connection is available (step 1616). The adaptor 104 receives the signal, which is formatted according to the command protocol of the telephone 102, and translates and reformats the signal to correspond to the system API (step 1620). The adaptor 104 then passes the translated and reformatted signal to the docking station 106. [0149] The docking station 106 formats the API command as a TCP/IP data packet addressed to the Internet browser 1200 a running on the laptop computer 378 a (step 1624). The Internet browser 1200 a is then free to pass information between itself and the Internet server 1216. This data is transferred between the server 1216 and the laptop computer 378 a as TCP/IP data packets, without conversion by the adaptor 104 (step 1628). [0150] At step 1632, user 2 establishes a Bluetooth wireless network connection between a personal digital assistant (PDA) 378 c and the docking station 106. User 2 then activates an e-mail program 1200 c running on the PDA 378 c to retrieve correspondence from an email account. The Bluetooth formatted request for data from the e-mail account is sent from the PDA 378 c of the local wireless interface 1212 (step 1636). The Bluetooth formatted request is reformatted as a TCP/IP formatted request by the local wireless network interface 1212. The request itself at this point is expressed in the API of the system. [0151] In response to the request, the docking station 106 signals the PDA 378 c that an Internet connection is available over the communications channel 1220 originally established by user 1 (step 1640). Data may then be passed between the PDA 378 c and the Internet server 1216. As with the laptop computer 378 a of user 1, the application 1200 c running on the PDA 378 c is only required to know how to request a connection to the Internet using the API of the system 100. The application 1208 is not required to know what commands are required by the wireless telephone 102, or how those commands must be formatted. Because user 2 has established a connection using a Bluetooth wireless interface, the request must be encoded according to the Bluetooth standard for transmission between the PDA 378 c and the local wireless interface 1212 of the docking station 106. Otherwise, the operation is the same as with the connection established using a cable. [0152] From the above example, it can be appreciated that multiple devices may share a communications channel 1220 established by the system 100. In particular, data packets addressed to different devices and servers may be transmitted across the communications channel 1220 at substantially the same time. [0153] Although the examples set forth above are in the context of communications initiated by external devices 378, it should be appreciated that communications can also be initiated by devices or applications that are at the server 1216 side of the channel 1220. In such instances, data addressed to a particular device 378 or application may be routed from the telephone 102 to the receiving device 378 or application 1200. Of course, any required translation of the data format, such as from a parallel bit stream to a serial bit stream, may be performed in the adaptor 104. [0154] With reference now to FIG. 17, another embodiment of a system 100, in accordance with the present invention is illustrated. In the embodiment illustrated in FIG. 17, the docking station 106 includes an interface 348 having a control data port 1700 and a phone data port 1704. The ports 1700 and 1704 may utilize any communication protocol, and thus may include a universal serial bus, FIREWIRE, or controller area network interface. As a further example, the ports 1700 and 1704 may be RS232 serial data ports, in which case the ports 1700 and 1704 serve to interconnect the docking station 106 to an external device 378 over RS232signal lines 1708 a and 1708 b. According to one embodiment of the invention, the ports 1700 and 1704 are provided as part of a data daughter board or plug-in module 380. Alternatively, the interface 348 may be embedded in or included as part of the docking station 106, or be included as part of a cable physically interconnecting the docking station 106 to an external device 378. The following discussion will refer to an external device 378 without reference to an application 1200, however it should be understood that the external device 378 may be associated with one or more applications 1200. [0155] In general, control data, such as commands concerning the operation of the external device 378, are transmitted from the control data port 1700 of the docking station 106 over a first signal line 1708 a to the external device 378. Information concerning the status of the external device 378 may also be provided to the docking station 106 at the control data port 1700 over the first signal line 1708 a. The phone data port 1704 is generally used to transmit data other than control signals between the docking station 106 and the external device 378. For example, the external device 378 may collect information from various sensors or other devices located in a vehicle 302 associated with the system 100, and periodically transmit that data to a central location or base station, such as server 1216. The data is transmitted over a wireless communications channel 1220 established using the wireless communications device 102 as described more filly above. [0156] The commands provided to the external device 378 by the docking station 106 may, according to an embodiment of the present invention, be received by the docking station 106 as voice commands. With reference now to FIG. 18, the relationship between the docking station 106 and the external device 378 in connection with voice recognition functions of the system 100 is illustrated. In general, a voice command 1800 is issued by a user and received by the docking station 106. As described above, the docking station digitizes the voice command 1800. The digitized voice command is then compared to speech models stored in the docking station 106 and/or the adaptor 104. The speech models may be customized by the user, or may be provided as part of the system 100. Upon finding a match between the digitized voice command and at least one of the word models, a command signal 1804 that corresponds to the voice command is issued by the docking station 106. According to one embodiment of the present invention, the command signal 1804 is passed to the external device 378 over the first signal line 1708 a between the control port 1700 of the docking station 106 and the external device 378. [0157] With reference now to FIG. 19, the operation of an embodiment of the present invention in connection with the provision of commands to an external device 378 from voice commands issued by a user is illustrated. Initially, at step 1900, the system 100 is directed to enter voice recognition mode. As mentioned above, the voice recognition mode may be entered by pressing a button or by speaking a particular word. In response to the command to enter the voice recognition mode, the system 100 activates a voice recognition menu (step 1904). The voice recognition menu may allow the user to specify commands for operating the external device 378 using corresponding voice commands. Sub-menus containing commands for particular devices or operations may also be provided. According to one embodiment of the present invention, the system 100 issues an audible acknowledgment of the activation of the voice recognition mode and of each menu or sub-menu selection. The acknowledgment may be in the form of audible speech generated by the docking station 106 and provided to the user by the speaker 366. [0158] After the voice recognition mode has been entered and the proper menu has been selected, the user may issue a voice command to the external device 378. The voice command is received by the docking station 106 and is digitized. In particular, the user command is received by the microphone 368 and digitized by the near-end CODEC 334 of the docking station 106. The digitized voice command is correlated to word models for commands associated with the operation of the external device 378 (step 1912). The comparison between the digitized voice command and the recognized commands may be carried out in the processor 328 of the docking station 106. Generally, word models for an entire set of commands to be used to operate the external device 378 may be maintained by the docking station 106. Alternatively or in addition, word models may be stored in the adaptor 104. The selected command is then provided to the external device 378 as an electronic signal (step 1916). For instance, where the docking station 106 is in communication with an external device 378 over a digital interface, such as an RS232 serial interface, the command is provided to the external device 378 in the form of a binary code word. [0159] According to one embodiment of the present invention, the external device 378 issues an acknowledgment of its receipt of the command (step 1920). The docking station 106 may then indicate to the user that the command has been passed to the external device 378. Notification to the user may be delivered audibly, for instance by speech (step 1924). [0160] The system 100 of the present invention may, according to one embodiment, also provide a text to speech function in connection with an external device 378. For instance, the external device 378 may be capable of receiving text messages from a base station. For example, a dispatcher may send textual messages to a driver for display by the external device 378. These textual messages, in addition to being displayed by the external device 378, may be processed by the docking station 106 and provided to the driver as speech, as with the other text to speech functions provided by the docking station 106 and described above. [0161] As can be appreciated from the foregoing description, the present invention allows for various external devices 378 to be interconnected to a wireless communications device 102. The docking station 106 and adaptor 104 remove the requirement that an external device 378 be capable of operating or interacting with a wireless communications device 102 using the command protocol of the wireless communications device 102. Furthermore, the system 100 allows voice recognition and text to speech functions that may be provided by the docking station 106 to be used in connection with an external device 378. Although the use of voice commands in connection with an external device 378 have been described in the context of an external device 378 for monitoring various aspects of a vehicle, the invention is not so limited. In general, the system 100 of the present invention may be used to provide voice recognition and/or text to speech capabilities in connection with any external device 378, the functions of which may be at least in part controlled using signals provided to that device. [0162] In accordance with the present invention, a method and apparatus for wireless communications are provided. The invention in its broader aspects relates to an economical method and apparatus for providing various levels of hands-free functionality in combination with wireless communications devices. In particular, the present invention provides a method and apparatus allowing for a wide variety of telephones and pockets to be used with a common docking station, and in connection with multiple external devices. Furthermore, the present invention relates to providing voice recognition capabilities to wireless communications devices and external devices using a common docking station. [0163] The foregoing discussion of the invention has been presented for purposes of illustration and description. Further, the description is not intended to limit the invention to the form disclosed herein. Consequently, variations and modifications commensurate with the above teachings, within the skill and knowledge of the relevant art, are within the scope of the present invention. The embodiments described hereinabove are further intended to explain the best mode presently known of practicing the invention and to enable others skilled in the art to utilize the invention in such or in other embodiments and with various modifications required by their particular application or use of the invention. It is intended that the appended claims be construed to include alternative embodiments to the extent permitted by the prior art. Patent CitationsCited PatentFiling datePublication dateApplicantTitleUS5479479 *Apr 20, 1993Dec 26, 1995Cell Port Labs, Inc.Method and apparatus for transmission of and receiving signals having digital information using an air linkUS5513107 *Dec 17, 1992Apr 30, 1996Ford Motor CompanyMethods and apparatus for controlling operating subsystems of a motor vehicleUS5535274 *Apr 19, 1994Jul 9, 1996Cellport Labs, Inc.Universal connection for cellular telephone interfaceUS5732074 *Jan 16, 1996Mar 24, 1998Cellport Labs, Inc.Mobile portable wireless communication systemUS5822427 *Apr 4, 1996Oct 13, 1998Cell Port Labs, Inc.Battery charging for a plurality of different cellular telephoneUS5825283 *Jul 3, 1996Oct 20, 1998Camhi; ElieSystem for the security and auditing of persons and propertyUS5844473 *Apr 12, 1995Dec 1, 1998Products Research, Inc.Method and apparatus for remotely collecting operational information of a mobile vehicleUS5903850 *Nov 24, 1995May 11, 1999Nokia Mobile Phones Ltd.Mobile phone and interface configuration in a mobile phoneUS6198947 *Mar 9, 1996Mar 6, 2001Oki Telecom, Inc.External control unit with reduced keypad integrated in voice activated vehicular telephone system with call-in-process voice-to-tones and voice to-memory conversion facilitiesUS6377825 *Feb 18, 2000Apr 23, 2002Cellport Systems, Inc.Hands-free wireless communication in a vehicleUS6647270 *Sep 11, 2000Nov 11, 2003Richard B. HimmelsteinVehicletalk* Cited by examinerReferenced byCiting PatentFiling datePublication dateApplicantTitleUS6636749Dec 31, 2001Oct 21, 2003At&T Wireless Services, Inc.Method and apparatus for providing power and wireless protocol capability to a wireless device, such as a wireless phoneUS6778824Jun 11, 2003Aug 17, 2004Telular Corp.Apparatus for wirelessly-coupling a bluetooth-wireless cellular mobile handset to a docking station for connecting a standard telephone set to the cellular networkUS6889065Dec 31, 2001May 3, 2005Cingular Wireless Ii, LlcSystem and method for providing an adapter moduleUS6891420Dec 21, 2001May 10, 2005Motorola, Inc.Method and apparatus for digital frequency synthesisUS6892051Dec 31, 2001May 10, 2005Cingular Wireless Ii, LlcSystem and method for providing an adapter moduleUS7006851Jul 29, 2003Feb 28, 2006Cingular Wireless, Ii, LlcMethod and apparatus for providing power and wireless protocol capability to a wireless device, such as a wireless phoneUS7043588May 24, 2002May 9, 2006Dell Products L.P.Information handling system featuring multi-processor capability with processor located in docking stationUS7050467Aug 7, 2000May 23, 2006Motorola, Inc.Digital-to-phase-converterUS7069006Jul 19, 2004Jun 27, 2006Telular Corp.Apparatus for wirelessly-coupling a Bluetooth-wireless cellular mobile handset to a docking station for connecting a standard telephone set to the cellular networkUS7149805 *Oct 31, 2001Dec 12, 2006Hewlett-Packard Development, L.P.Wireless trusted point of access to a computer networkUS7154978Nov 2, 2001Dec 26, 2006Motorola, Inc.Cascaded delay locked loop circuitUS7162000Jan 16, 2002Jan 9, 2007Motorola, Inc.Delay locked loop synthesizer with multiple outputs and digital modulationUS7190954Feb 6, 2006Mar 13, 2007Telular Corp.Apparatus for wirelessly-coupling a Bluetooth-wireless cellular mobile handset to a docking station for connecting a standard telephone set to the cellular networkUS7197541 *Jun 18, 2001Mar 27, 2007Palm, Inc.Method and apparatus for automated personality transfer for a wireless enabled handheld deviceUS7280802 *Jul 8, 2003Oct 9, 2007Netalog, Inc.FM transmitter and power supply/charging assembly for MP3 playerUS7336943 *Nov 19, 2003Feb 26, 2008General Motors CorporationEstablishing mobile terminated connections with dynamically assigned wireless IP terminals in automotive telematics applicationsUS7391718Dec 9, 2005Jun 24, 2008Palm, Inc.Swapping a nonoperational networked electronic system for an operational networked electronic systemUS7406340 *Dec 16, 2003Jul 29, 2008Siemens AktiengesellschaftArrangement and interface module for connecting different radio telephones to operator components in a motor vehicleUS7580255Aug 24, 2005Aug 25, 2009Apple Inc.Docking station for hand held electronic devicesUS7610016Oct 27, 2009At&T Mobility Ii LlcSystem and method for providing an adapter moduleUS7627343Dec 1, 2009Apple Inc.Media player systemUS7632114Dec 15, 2009Apple Inc.Interface connecter between media player and other electronic devicesUS7672225Mar 2, 2010Palm, Inc.Swapping an operational networked electronic system for a nonoperational networked electronic systemUS7675746Mar 9, 2010Apple Inc.Docking station for hand held electronic devicesUS7719830May 9, 2005May 18, 2010Apple Inc.Universal docking station for hand held electronic devicesUS7734247 *Jan 25, 2007Jun 8, 2010Sony Ericsson Mobile Communications AbConfigurable serial memory interfaceUS7747009 *Feb 23, 2004Jun 29, 2010Audioton Kabelwerk GmbhRetaining device for mobile user devicesUS7751853Apr 3, 2009Jul 6, 2010Apple Inc.Female receptacle data pin connectorUS7756550 *Jul 13, 2010Bury Sp.Z.O.O.Hands free device for a cellular phoneUS7783070Sep 25, 2008Aug 24, 2010Apple Inc.Cable adapter for a media player systemUS7801283 *Sep 21, 2010Lear CorporationMethod of operating vehicular, hands-free telephone systemUS7881744Feb 1, 2011Research In Motion LimitedMedia transfer and control systemUS7894861 *Dec 16, 2003Feb 22, 2011Continental Automotive Systems, Inc.Method of enabling a remote communications device with a telematics functionality moduleUS7933117Apr 26, 2011Apple Inc.Universal docking station for hand-held electronic devicesUS8001177Feb 28, 2007Aug 16, 2011Hewlett-Packard Development Company, L.P.Method and apparatus for automated personal information management data transfer for a wireless enabled handheldUS8010728Nov 7, 2006Aug 30, 2011Koninklijke Philips Electronics N.V.Multi-function docking assembly for portable digital media storage and playback deviceUS8015010Sep 6, 2011E-Lane Systems Inc.Vehicle communication system with news subscription serviceUS8050714Nov 1, 2011Apple Inc.Docking station for media player systemUS8068336Jan 25, 2010Nov 29, 2011Apple Inc.Docking station for hand held electronic devicesUS8078224Dec 13, 2011Apple Inc.Male plug connectorUS8078776Dec 14, 2010Dec 13, 2011Apple Inc.Electronic device having a dual key connectorUS8086278 *Dec 27, 2011Quanta Computer Inc.Holding apparatusUS8165634Apr 24, 2012Apple Inc.Female receptacle connectorUS8190205May 29, 2012Apple Inc.Male plug connectorUS8207906Jun 26, 2012Apple Inc.Antenna insertUS8244295Aug 14, 2012Research In Motion LimitedMedia transfer and control systemUS8265617Sep 11, 2012Research In Motion LimitedMedia transfer and control systemUS8271038Oct 19, 2007Sep 18, 2012Apple Inc.Wireless adapter for media player systemUS8271705Sep 18, 2012Apple Inc.Dual key electronic connectorUS8271713Sep 18, 2012Philips Electronics North America CorporationInterface systems for portable digital media storage and playback devicesUS8306193Nov 6, 2012Lear CorporationMethod of pairing a portable device with a communications module of a vehicular, hands-free telephone systemUS8340215 *Dec 25, 2012Motorola Mobility LlcRadio transceiver architectures and methodsUS8364486Jan 29, 2013Intelligent Mechatronic Systems Inc.Speech understanding method and systemUS8416705Dec 29, 2009Apr 9, 2013Hewlett-Packard Development Company, L.P.User profile or user account association with multiple computersUS8449336 *Dec 19, 2012May 28, 2013Apple Inc.Compliant mount for connectorUS8467829Jun 18, 2013Apple Inc.Wireless adapter for media player systemUS8521220Jul 24, 2012Aug 27, 2013Blackberry LimitedMedia transfer and control systemUS8535102 *Dec 19, 2012Sep 17, 2013Apple Inc.Compliant mount for connectorUS8577543May 28, 2010Nov 5, 2013Intelligent Mechatronic Systems Inc.Communication system with personal information management and remote vehicle monitoring and control featuresUS8721356Sep 11, 2012May 13, 2014Apple Inc.Dock with compliant connector mountUS8723047 *Mar 21, 2008May 13, 2014Huawei Technologies Co., Ltd.Printed circuit board, design method thereof and mainboard of terminal productUS8838075Jun 19, 2009Sep 16, 2014Intelligent Mechatronic Systems Inc.Communication system with voice mail access and call by spelling functionalityUS8856009Mar 25, 2009Oct 7, 2014Intelligent Mechatronic Systems Inc.Multi-participant, mixed-initiative voice interaction systemUS8892172 *Jan 12, 2011Nov 18, 2014Continental Automotive Systems, Inc.Method of enabling a remote communications device with a telematics functionality moduleUS8986029Mar 8, 2013Mar 24, 2015Apple Inc.Dock connector with compliance mechanismUS9037685Mar 2, 2007May 19, 2015Qualcomm IncorporatedIntelligent migration between devices having different hardware or software configurationUS9160124Sep 7, 2012Oct 13, 2015Apple Inc.Compliant mount for connectorUS9229487 *Apr 11, 2014Jan 5, 2016Apple Inc.Dock with compliant connector mountUS9261919 *Apr 11, 2014Feb 16, 2016Apple Inc.Dock with compliant connector mountUS20030083062 *Oct 31, 2001May 1, 2003Emiliano BartolomeWireless trusted point of access to a computer networkUS20030099321 *Nov 2, 2001May 29, 2003Jui-Kuo JuanCascaded delay locked loop circuitUS20030119465 *Dec 21, 2001Jun 26, 2003Martin Frederick L.Method and apparatus for digital frequency synthesisUS20030152181 *Jan 16, 2002Aug 14, 2003Stengel Robert E.Delay locked loop synthesizer with multiple outputs and digital modulationUS20030221036 *May 24, 2002Nov 27, 2003Dell Products, L.P.Information handling system featuring multi-processor capability with processor located in docking stationUS20030227900 *Jan 15, 2003Dec 11, 2003Fujitsu LimitedPortable terminal supporting apparatus, data synchronizing method, and portable terminal apparatusUS20040017847 *Jul 26, 2002Jan 29, 2004William AlberthRadio transceiver architectures and methodsUS20040058649 *Jul 8, 2003Mar 25, 2004Jeff GradyFM transmitter and power supply/charging assembly for MP3 playerUS20040097272 *Jan 26, 2002May 20, 2004Guido SchuffertHands-free device for operating mobile telephones in motor vehiclesUS20040121819 *Jan 26, 2002Jun 24, 2004Frank VogelHands-free device for operating mobile telephones in motor vehiclesUS20040224638 *Apr 25, 2003Nov 11, 2004Apple Computer, Inc.Media player systemUS20040264430 *Jul 19, 2004Dec 30, 2004Wonak Daniel C.Apparatus for wirelessly-coupling a bluetooth-wireless cellular mobile handset to a docking station for connecting a standard telephone set to the cellular networkUS20050105509 *Nov 19, 2003May 19, 2005General Motors CorporationEstablishing mobile terminated connections with dynamically assigned wireless IP terminals in automotive telematics applicationsUS20050124380 *Dec 5, 2003Jun 9, 2005Rokusek Daniel S.Method of controling a communications sessionUS20050130723 *Dec 16, 2003Jun 16, 2005Grivas Nick J.Method of enabling a remote communications device with a telematics functionality moduleUS20050135573 *Dec 22, 2003Jun 23, 2005Lear CorporationMethod of operating vehicular, hands-free telephone systemUS20050176369 *Jul 29, 2003Aug 11, 2005James Holmes David W.Method and apparatus for providing power and wireless protocol capability to a wireless device, such as a wireless phoneUS20050197168 *Feb 14, 2005Sep 8, 2005Holmes David W.J.System and method for providing an adapter moduleUS20050202853 *Feb 4, 2005Sep 15, 2005Schmitt Edward D.System and method for providing an adapter moduleUS20060058070 *Sep 30, 2004Mar 16, 2006Chang Ta SUniversal device with means of holding a portable electronic device and communicating therewithUS20060067339 *Dec 9, 2005Mar 30, 2006Palm, Inc.Swapping a nonoperational networked electronic system for an operational networked electronic systemUS20060148420 *Feb 6, 2006Jul 6, 2006Wonak Daniel CApparatus for wirelessly-coupling a Bluetooth-wireless cellular mobile handset to a docking station for connecting a standard telephone set to the cellular networkUS20060161312 *Dec 16, 2003Jul 20, 2006Lars JuenglingArrangement and interface module for connecting different radio telephones to operator components in a motor vehicleUS20060250764 *May 9, 2005Nov 9, 2006Apple Computer, Inc.Universal docking station for hand held electronic devicesUS20060264246 *May 22, 2006Nov 23, 2006Roman PiekarzHands free device for a cellular phoneUS20070086724 *Oct 13, 2006Apr 19, 2007Jeff GradyInterface systems for portable digital media storage and playback devicesUS20070140108 *Dec 5, 2006Jun 21, 2007Palm, Inc.Swapping an operational networked electronic system for a nonoperational networked electronic systemUS20070214231 *Feb 28, 2007Sep 13, 2007Palm, Inc.Method and apparatus for automated personality transfer for a wireless enabled handheldUS20070228095 *Feb 23, 2004Oct 4, 2007Audioton Kabelwerk Gmbh Zweigniederlassung ScheinfeldRetaining device for mobile user devicesUS20070232098 *Mar 30, 2006Oct 4, 2007Apple Computer, Inc.Interface connector between media player and computerUS20070294710 *Jun 19, 2006Dec 20, 2007Alps Automotive Inc.Simple bluetooth software development kitUS20080027643 *Jul 30, 2007Jan 31, 2008Basir Otman AVehicle communication system with navigationUS20080089658 *Oct 13, 2006Apr 17, 2008Jeff GradyInterface systems for portable digital media storage and playback devicesUS20080089667 *Oct 13, 2006Apr 17, 2008Jeff GradyInterface systems for portable digital media storage and playback devicesUS20080092200 *Oct 13, 2006Apr 17, 2008Jeff GradyInterface systems for portable digital media storage and playback devicesUS20080114830 *Mar 2, 2007May 15, 2008Palm, Inc.Intelligent Migration Between Devices Having Different Hardware or Software ConfigurationUS20080123285 *Oct 19, 2007May 29, 2008Apple, Inc.Media player systemUS20080125031 *Oct 19, 2007May 29, 2008Apple Inc.Media Player SystemUS20080138028 *Oct 13, 2006Jun 12, 2008Jeff GradyInterface systems for portable digital media storage and playback devicesUS20080140408 *Nov 5, 2007Jun 12, 2008Basir Otman AVehicle communication system with news subscription serviceUS20080165066 *Jan 7, 2008Jul 10, 2008Apple Inc.Antenna insertUS20080182618 *Jan 25, 2007Jul 31, 2008Sony Ericsson Mobile Communications AbConfigurable serial memory interfaceUS20080227493 *Mar 4, 2008Sep 18, 2008Sony CorporationElectronic device system, electronic device, and processing methodUS20080230258 *Mar 21, 2008Sep 25, 2008Huawei Technologies Co., Ltd.Printed circuit board, design method thereof and mainboard of terminal productUS20080254785 *Apr 10, 2007Oct 16, 2008Mihal LazaridisMedia transfer and control systemUS20080313050 *Jun 5, 2008Dec 18, 2008Basir Otman AMedia exchange systemUS20090009957 *Aug 31, 2008Jan 8, 2009Apple Inc.Docking station for hand held electronic devicesUS20090164110 *Dec 10, 2008Jun 25, 2009Basir Otman AVehicle communication system with destination selection for navigationUS20090191732 *Apr 3, 2009Jul 30, 2009Apple Inc.Female receptacle data pin connectorUS20090234651 *Mar 12, 2009Sep 17, 2009Basir Otman ASpeech understanding method and systemUS20090248420 *Mar 25, 2009Oct 1, 2009Basir Otman AMulti-participant, mixed-initiative voice interaction systemUS20090318119 *Jun 19, 2009Dec 24, 2009Basir Otman ACommunication system with voice mail access and call by spelling functionalityUS20100023204 *Jul 24, 2009Jan 28, 2010Basir Otman APower management systemUS20100087099 *Apr 8, 2010Apple Inc.Male plug connectorUS20100118485 *Jan 25, 2010May 13, 2010Apple Inc.Docking station for hand held electronic devicesUS20100137037 *Feb 8, 2010Jun 3, 2010Basir Otman AVehicle immersive communication systemUS20100188808 *Apr 1, 2010Jul 29, 2010Apple Inc.Universal docking station for hand-held electronic devicesUS20100199331 *Dec 29, 2009Aug 5, 2010Palm, Inc.User profile or user account association with multiple computersUS20100206999 *Aug 19, 2010Quanta Computer, Inc.Holding ApparatusUS20100279612 *Jul 16, 2010Nov 4, 2010Lear CorporationMethod of Pairing a Portable Device with a Communications Module of a Vehicular, Hands-Free Telephone SystemUS20100323657 *Jul 22, 2008Dec 23, 2010Russell Brett Barnardcommunication devicesUS20100330975 *Jun 28, 2010Dec 30, 2010Basir Otman AVehicle internet radio interfaceUS20110086551 *Apr 14, 2011Apple Inc.Electronic device and connectorUS20110105198 *May 5, 2011Continental Automotive Systems, Inc.Method of Enabling A Remote Communications Device with A Telematics Functionality ModuleUS20110117864 *May 19, 2011Research In Motion LimitedMedia transfer and control systemUS20110121991 *Nov 24, 2010May 26, 2011Basir Otman AVehicle to vehicle chatting and communication systemUS20110151724 *Jun 23, 2011Apple Inc.Female receptacle connectorUS20110151725 *Jun 23, 2011Apple Inc.Male plug connectorUS20130325479 *May 29, 2012Dec 5, 2013Apple Inc.Smart dock for activating a voice recognition mode of a portable electronic deviceUS20140172228 *Dec 9, 2013Jun 19, 2014Cellassist, LlcAutomotive ecu mobile phone interfaceUS20140307383 *Apr 11, 2014Oct 16, 2014Apple Inc.Dock with compliant connector mountUS20150271858 *Nov 8, 2013Sep 24, 2015Shenzhen Seg Scientific Navigations Co., Ltd.Bluetooth-based system for automatically matching vehicle-mounted device with mobile phone terminalUSRE43577Aug 14, 2012Hewlett-Packard Development Company, L.P.Swapping a nonoperational networked electronic system for an operational networked electronic systemCN103522956A *Oct 12, 2013Jan 22, 2014中国电子科技集团公司第七研究所Handheld radio docking station and application structure thereofEP1369791A2 *Jan 2, 2003Dec 10, 2003Fujitsu LimitedPortable terminal supporting apparatus, data synchronizing method, and portable terminal apparatusEP1618675A1 *Mar 18, 2004Jan 25, 2006Apple Computer, Inc.Media player systemEP1783003A2 *Oct 20, 2006May 9, 2007Delphi Technologies, Inc.Communication interface module for vehicleEP1891848A1 *Jun 13, 2006Feb 27, 2008E-Lane Systems Inc.Vehicle immersive communication systemEP2023546A2 *Mar 13, 2008Feb 11, 2009Sony CorporationElectronic device system, electronic device, and processing methodEP2026546A2 *Mar 18, 2004Feb 18, 2009Apple Inc.Media player systemWO2003001342A2 *Jun 24, 2002Jan 3, 2003At & T Wireless Services, Inc.System and method for providing an adapter moduleWO2003001342A3 *Jun 24, 2002Feb 20, 2003At & T Wireless Services IncSystem and method for providing an adapter moduleWO2004012343A2 *Jul 22, 2003Feb 5, 2004Motorola, Inc., A Corporation Of The State Of DelawareRadio transceiver architectures and methodsWO2004012343A3 *Jul 22, 2003May 6, 2004Motorola IncRadio transceiver architectures and methodsWO2004080042A1 *Dec 16, 2003Sep 16, 2004Siemens AktiengesellschaftArrangement and interface module for connecting different radio telephones to operator components in a motor vehicleWO2005029822A1 *Sep 8, 2004Mar 31, 2005Audioton Kabelwerk GmbhConnection system, base part and adapter part for connecting mobile radio terminalsWO2007149440A2 *Jun 19, 2007Dec 27, 2007Alps Automotive Inc.Simple bluetooth software development kitWO2009145922A1 *Jun 1, 2009Dec 3, 2009Williams Stanley FHandheld cellular telephone conversion system for home telephone network compatibilityWO2010091312A1 *Feb 5, 2010Aug 12, 2010Social Gaming NetworkApparatuses, methods and systems for an enhanced device feature cradleWO2015191908A1 *Jun 11, 2015Dec 17, 2015Deratany Timothy AllenAutomobile adaptor system, apparatus and methodology* Cited by examinerClassifications U.S. Classification455/564, 455/569.2International ClassificationH04M1/60, H04M1/725, B60R11/00, H04B1/38, H04M1/27, H04M1/253, H04M1/04, B60R11/02Cooperative ClassificationH04M1/7255, H04M1/72525, H04M1/7253, B60R2011/0075, H04M2250/74, H04M1/6091, H04B1/3877, H04M1/271, H04M2250/02, H04M1/72561, B60R2011/0078, B60R2011/0071, B60R11/0241European ClassificationH04B1/38P6, H04M1/60T2C2A, B60R11/02GLegal EventsDateCodeEventDescriptionSep 14, 2001ASAssignmentOwner name: CELLPORT SYSTEMS, INC., COLORADOFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:POPLAWSKY, RALPH C.;DURIAN, MICHAEL B.;SERAFIN JR., DANIEL;REEL/FRAME:012175/0411;SIGNING DATES FROM 20010904 TO 20010906Apr 30, 2004ASAssignmentOwner name: ANDREW W. QUARTNER, MARYLANDFree format text: SECURITY INTEREST;ASSIGNOR:CELLPORT SYSTEMS, INC.;REEL/FRAME:014580/0663Effective date: 20040330Apr 11, 2007ASAssignmentOwner name: CELLPORT SYSTEMS, INC., COLORADOFree format text: RELEASE OF SECURITY INTEREST;ASSIGNOR:QUARTNER, ANDREW A.;REEL/FRAME:019181/0519Effective date: 20060306RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services