WO2001022606A1

WO2001022606A1 - Automatic device synchronization apparatus and method using battery pack for data exchange

Info

Publication number: WO2001022606A1
Application number: PCT/US2000/024624
Authority: WO
Inventors: William Y. Son; Elbert A. Mclaren; Seung B. Yi
Original assignee: Neopoint, Inc.
Priority date: 1999-09-20
Filing date: 2000-09-07
Publication date: 2001-03-29
Also published as: WO2001022606A9; AU7357900A

Abstract

A system for interfacing a wireless handset (100) with a host computer (126). The system includes an interface docking station (124) having a transmit and receive path for data exchange between the handset and computer. A removable battery pack is attached to the handset. A first electrical contact extends through the pack and connects the transmit path of the interface with the handset processor to permit transmission of data from the handset to the computer. A second electrical contact extends through the pack and connects the receive path of the interface with the handset processor to permit reception of data by the electronic device from the host computer. The docking station has electrical contacts configured to mate with the electrical contacts of the battery pack. The handset processor is configured to automatically synchronize the handset with the host computer without user intervention via the first and second electrical contacts of the battery pack.

Description

AUTOMATIC DEVICE SYNCHRONIZATION APPARATUS AND METHOD USING BATTERY PACK FOR DATA EXCHANGE

RELATED APPLICATIONS

This is a continuation-in-part of U.S. patent application serial no. 09/245,823, which was filed on February 5, 1999.

BACKGROUND OF THE INVENTION 1. Field of the Invention

The present invention relates generally to wireless communication devices and more specifically to an automatic device synchronization apparatus and method that uses the existing metal contacts of a device battery pack for data exchange.

2. Related Art

The advent of wireless personal communications devices has revolutionized the telecommunications industry. Cellular, PCS and other services provide wireless personal communications to businesses and individuals at home, in the office, on the road, and virtually anywhere the wireless network reaches. Wireless telephone subscribers no longer have to stop at pay telephones along the road, or wait until they return home or to the office to check messages and return important business calls. Instead, wireless subscribers carry out their day to day business from their cars, from the jobsite, while walking along the airport concourse, and just about anywhere their signals are accessible.

Thus, it is no surprise that since the introduction of the cellular telephone service, the number of wireless telephone subscribers has increased steadily. Today, the number of wireless telephone subscribers is staggering and still growing rapidly. In fact, many households have multiple wireless telephones in addition to their conventional land-line services.

With a market of this size, there is fierce competition among hardware manufacturers and service providers. In an attempt to lure customers, most providers offer handsets with desirable features or attributes such as small size, light weight, longer battery life, speed dial, and so forth. Many recent additions to the marketplace include multi-functional handsets that even provide pocket-organizer functions integrated into the wireless handset. Most manufacturers, however, are still scrambling to add new features to their communication devices to snare a portion of this booming market.

SUMMARY OF THE INVENTION

The present invention is directed toward a system and method for providing automatic synchronization of a portable electronic device with a host computer. More specifically, in one implementation of the invention, the invention provides a system for interfacing a portable electronic device with a host computer. The system includes an interface comprising a transmit and receive path to permit exchange of data between the electronic device and host computer. A processor is provided within the portable electronic device for directing the overall operation of the device and has a receive pin for receiving data and a transmit pin for transmitting data. A removable battery pack is attached to the portable electronic device for providing power to the device. A first electrical contact extends through the pack and connects the transmit path of the interface with the processor transmit pin to permit transmission of data from the electronic device to the host computer. A second electrical contact extends through the pack and connects the receive path of the interface with the processor receive pin to permit reception of data by the electronic device from the host computer.

In one implementation, the portable electronics device is a wireless communication handset and the interface is a docking station having electrical contacts configured to mate with the electrical contacts of the battery pack. In a further implementation, the handset comprises computer program code logic configured to automatically synchronize the handset with the host computer without user intervention via the first and second electrical contacts of the battery pack.

In other embodiment of the present invention, a removable battery pack for powering a wireless communication handset is provided. A first electrical contact extends completely through the pack for transmitting data from the central processing unit of the handset to an external communications device. A second electrical contact extends completely through the pack for receiving data from the external communications device and providing it to the central processing unit. In a further implementation, a third electrical contact extends completely through the pack for connection of a battery within the pack to an external power source for recharging. Additional contacts may be provided extending partially through the pack for other purposes.

BRIEF DESCRIPTION OF THE DRAWINGS

Figure 1 is a block diagram illustrating an example wireless communication handset.

Figure 2 is a block diagram illustrating a wireless communication handset interfaced to a host computer by a direct cable or a docking station according to one embodiment of the invention.

Figure 3 is a diagram illustrating an example configuration for implementing automatic synchronization according to one embodiment of the invention.

Figure 4 is an operational flow diagram illustrating a process for carrying out automatic synchronization according to one embodiment of the invention. Figure 5 is a diagram illustrating an example processor-based system according to one embodiment of the invention.

Figure 6 is a perspective view of a wireless communication handset illustrating removal of a battery pack.

Figure 7 is a perspective view of the handset of Figure 6 with the battery pack installed.

Figure 8 is a block diagram of the battery pack of Figure 1 illustrating use of the pack's metal contacts for data transfer purposes.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS 1. Example Environment (Figure 1)

Before describing the invention in detail, an example environment in which the invention can be implemented will be described. One such example environment is a portable electronic device having personal data organizer functionality, or other data gathering capability in which it is desirable to exchange or share data with a host computer. One particular application of such a device is a wireless communication device such as, for example, a cellular, GSM, PCS, radio, or other wireless communication handset. Such handsets or communication devices provide wireless communication services and often include a keypad for control and data entry of the device, as well as a display to provide information to the user regarding the communication or regarding information entered by the user on the keypad. Wireless communication handsets or devices such as those that would benefit from the various features and aspects of the present invention, can be implemented in a number of different configurations with a number of different architectures. In fact, as will become apparent to one of ordinary skill in the art after reading this description, implementation of the features of the present invention is not dependent on a particular or specific architecture of the electronic device or communication device. However, to provide a backdrop for the description of the features, an example wireless communication device is described with reference to Figure 1.

Referring now to Figure 1, wireless communication device 100 includes a processor 104, a speaker 106, a display 108, a keypad 110, a transceiver 122, a memory 114, a microphone 116, a power source 118, a data port 122 and an antenna 120. Device 100 can be a handheld handset, integrated vehicle phone or other wireless communication device configured to communicate with other communications devices such as, for example, a base station 112 or other communication device. Contemporary communication handsets typically include one or more processors 104 to control the operation and the features of the handset. Processor 104 typically has associated therewith computer program code running on the processor to carry out the functionality of the device.

Memory 114 such as RAM, ROM, or other memory, can be included and interfaced with the processor to store the program code and to provide other storage space for data or other information useful in executing the program code as well as in carrying out functions of the handset. In fact, the features and functionality of the present invention can be implemented using hardware, software, or a combination thereof, and such software can run on a processor such as processor 104.

Handset 100 also includes a transceiver 122. Transceiver 122 provides a transmitter to transmit voice and data information via antenna 120 to a recipient communication device such as base station 112. Transceiver 122 typically also includes a receiver to receive voice and data communication from another communication device (e.g., base station 112) and to provide the received voice and data information to the user or to facilitate internal functionality of the handset.

User interface portions of the typical wireless communication handset 100 include a speaker 106, a display 108, a keypad 110, and a microphone 116. Microphone 116 accepts voice or other audio information from the user, converts this information to electrical signals such that they can be transmitted by the transceiver to a recipient. Likewise, speaker 106 converts electrical signals received by transceiver 122 into audio information that can be heard by a user of the wireless communication device 100.

Display 108 can be used to display information to the user such as, for example, call information, keypad entry display, signal presence and signal strength display, battery life display, or any other information useful to the user. Display 108 can include any type of display, but is preferably a liquid crystal display (LCD) due to the LCD's low power consumption characteristics. Display 108 can also include other visual displays such as, for example, light emitting diode (LED) indicators or other visual indicators. Keypad 110 can be implemented using a numeric or an alphanumeric keypad and can also include special function keys. In one embodiment, keypad 110 includes back lighting such that information on the keys can be viewed by the user in low light or dark conditions. Many electronic devices including wireless communication devices include a flip panel (not illustrated) that can be closed to conceal some or all of the keys on the keypad. Power source 118 is used to provide power to one or more of the components of the wireless communication handset 100. Power source 118 can be implemented, for example, using rechargeable batteries such as NiCad or NiMH rechargeable batteries. Other power sources can be included in addition to or in place of batteries. As will be discussed in connection with Figures 6-8 below, power source 118 may be implemented in handset 100 as a rechargeable battery in an easily removable and exchangeable battery pack 200.

Data port 125 can be used to exchange or share data with a host computer or other device. For example, where the functionality of the device includes personal organizer functionality, a user may wish to upload collected contact information to his or her laptop or desktop computer. Data port 125 can be a hard- wired or wireless data port and can use any of a number of different communication standards. One such example communication standard prominent in PC interfaces is RS-232. As will be discussed in connection with Figure 6-8 below, data port 125 may optionally be implemented in handset 100 using the existing metal contacts 202-212 of battery pack 200.

The invention is described herein in terms of this example application in this example environment. Description in these terms is provided for ease of discussion only. Those of ordinary skill in the art will understand that the present invention can be implemented in a number of different electronic devices or architectures, where it is desirable to share or exchange information with another device, such as for example, a host computer.

2. Automatic Synchronization and Data Transfer (Figures 2-5)

The present invention is directed toward a system and method for providing enhanced synchronization of electronic devices. It is more specifically directed toward automatic synchronization and data transfer between a portable electronic device and a host computer.

The automatic synchronization is described herein in terms of the example application of the wireless communication handset 100. As will be apparent to those of ordinary skill in the art, the features of the present invention could be implemented in alternative electronic devices and in alternative applications.

Figure 2 is a block diagram illustrating connection of a wireless communication handset 100 to a docking station 124. Handset 100 is insertable into the docking station 124.

Docking station 124 may include a power interface to recharge the power source 118 of handset 100 and a data interface to permit between exchange of data between handset 100 and host computer 126. The data and power interfaces may be implemented as electrical contacts in docking station 124 (not shown) that mate with corresponding contacts on handset 100.

These contacts provide data connections for exchange of data as well as power connections for battery charging. As will be described below in reference to Figure 6-8, the data and power interfaces in handset 100 may be implemented using the metal contacts of a battery pack 200.

A data cable 128 connects docking station 124 and host computer 126. Although other connection means are possible, such as direct bus plug-ins, a cable is preferable so that docking station 124 can be maintained separately from host computer 126. Additionally, cable 128 can be implemented as a wireless communication interface such as, for example, an infrared communication interface. Also illustrated in Figure 2 is a direct communication interface 132 between handset 100 and computer 126. As this illustrates, wireless handset 100 can be interfaced with host computer 126 directly without the need to interface via docking station 124.

Host computer 126 can be implemented as, for example, a user's personal computer. In applications where handset 100 includes organizer or PDA functions, for example, the user may wish to synchronize information such as contact and calendar entries that is stored in handset 100 with corresponding information stored on computer 126. As such, the present invention allows automatic synchronization and exchange of data between applications on handset 100 and host computer 126. Computer 126 may have application programs such as, for example, Microsoft Outlook^® or Lotus Notes^®, or other application programs that permit sharing and synchronization of data with a remote data collection source such as handset 100.

In operation, a user may use handset 100 to gather information. A business traveler, for example, may use the organizer contained in handset 100 for entry of business or contact information, for entry of appointment information, for entry of tasks or notes, or for other data entry purposes. Upon returning to his or her home or office, the user may wish to synchronize or update their personal computer database with the new information stored in the portable organizer.

In one scenario, the user may insert handset 100 into docking station 124. Advantageously, circuitry within handset 100 senses that handset 100 is now coupled to host computer 126. As such, the data synchronization or updating can occur automatically without additional user intervention. Additionally, where docking station 124 includes battery charger functionality, the batteries of handset 100 can be simultaneously charged. Thus, when the user returns to his or her home or office, the user simply inserts the device into docking station 124 and can go about his or her business without performing additional steps to synchronize the data between the device 100 and host computer 126. Similarly, the synchronization process can be initiated by plugging an interface cable 132 into electronic device 100.

Figure 3 is a block diagram illustrating an example configuration according to one embodiment of the invention. The embodiment illustrated in Figure 3 shows an electronic device, such as wireless communication handset 100, connected to a computer, such as host computer 126, via an interface 140. More particularly, interface 140 provides a data connection between a communications port 142 in host computer 126, and data port 125 of handset 100. As illustrated in Figure 2, interface 140 may be implemented utilizing a docking station 124 and cable 128. Interface 140 includes a transmit path 182, a receive path 184, and a ground 186. Interface 140 also includes a power line 188, which provides power to circuitry included with interface 140 from wireless communication handset 100. As will be described below in reference to Figure 6, transmit path 182, receive path

184, ground 186 and power line 188 may be implemented in docking station 124 as metal electrical contacts. Data port 125 and the power connections are implemented as the preexisting, mating metal contacts 202-212 in removable handset battery pack 200.

Circuitry in interface 140 includes a transmit buffer 154A and a receive buffer 154B. Buffers 154 receive their power via power line 188 from electronic wireless communication handset 100. Thus, until connector 140 is connected to data port 125, buffers 154 are not enabled or powered on. In the configuration illustrated in Figure 3, the input of transmit buffer 154A is pulled to a low level by pull-down resistor Rl connected to ground GND. Because transmit buffer 154 A is implemented as an inverter, when interface 140 is connected to data port 125 and transmit buffer 154A is powered on by power line 188, a high level is presented at the transmit pin 162 of data port 125. This signal is inverted by inverting buffer 172 and provided to a status input pin 176 of CPU 104. Thus, when interface 140 is connected to data port 125, a logic high level is presented at status input pin 176. Status pin 176 can be pulled low with a pull-down resistor (not illustrated) to ensure that it is not at a logic high level unless interface 140 is connected to data port 125.

CPU 104 periodically polls status pin 176, looking for a logic high level. When a logic high level is detected at pin 176, CPU 104 interprets this as indicating that interface 140 is connected to data port 125. In one embodiment, to avoid ambiguities that may be caused by ground bounce, pin 176 is polled in at least two clock cycles (preferably successive cycles). This, in turn, indicates to CPU 104 that handset 100 is connected to the host computer 126.

As such, CPU 104 can initiate the synchronization process. Hence, synchronization can take place without user keystrokes, simply by placing handset 100 in docking station. The synchronization occurs automatically as a result of transmit buffer 154A being supplied power by handset 100. An additional inverting buffer 174 may be provided to re-invert data before it is provided to CPU 104. After reading the above description, it will become apparent to one of ordinary skill in the art how to implement the invention utilizing other hardware configurations or other combinations of hardware and software to implement the invention. Additionally, it will be apparent to those of ordinary skill in the art how to implement the invention where status signal 176 is true at a logic low level as opposed to a logic high level. Of course, the choice of inverters for logic components is provided for illustration and description purposes only. The functionality could be implemented using alternative components or circuitry.

As stated, implementation of the invention is not limited to implementation in a wireless communication handset 100. The invention can be implemented in any electronic device that is interfaced with another processing system for synchronization or update of data.

In one implementation, the device may include a user-selectable option for turning on or off the automatic synchronization function. Where handset 100 is utilized, this option may be implemented as a menu-driven interface via display 108 and keypad 110. In this implementation, the user can page through or scroll down various menu options, one of which allows the user to enable or disable the automatic synchronization ("autosync") function. If the autosync function is disabled, connection of handset 100 to interface 140 will not automatically trigger synchronization. Manual intervention will be required. Conversely, if the autosync function is enabled, placing handset 100 in docking station 124 will automatically begin the synchronization process. The electronic device (handset 100) may also include other uni- or bi-directional communication features across data port 125. If such features are included, it may not be desirable to begin automatic synchronization as soon as a logic high level or other true level signal is presented at status pin 176. For example, data port 125 may be used to enable communication on the Internet, other network communications, or communication port 125 may be used as a diagnostic port allowing interface with a diagnostic computer system. In these modes, it may not be desirable to automatically begin synchronization upon detection of an activity or a particular logic level at status pin 176. Thus, software masking or disabling may be used to inhibit automatic synchronization for other data modes.

Figure 4 is an operational flow diagram illustrating a process for implementing automatic synchronization according to one embodiment of the invention. In a step 232, the system checks to determine whether autosync is enabled. That is, in embodiments where the autosync feature can be turned on or off at the discretion of the user, the system first checks to determine whether the user desires automatic synchronization to occur upon the connection of interface 140 at data port 125. If in step 232 it is determined that autosync is enabled, CPU 104 polls status line 176 periodically to determine whether status line 176 transitions to its true state. If it is true at the polling interval, the synchronization process begins. This is illustrated by steps 234, 236 and 240.

If status line 176 is not true at the polling interval, processor 104 continues polling until the autosync feature is either cancelled or otherwise disabled. This is illustrated by flow line 262. If, during the synchronization process the user cancels the autosync mode (either before or after synchronization actually begins), the status check is masked and the synchronization process aborted. This is illustrated by steps 238 and 112. Similarly, if autosync is disabled, status signal 176 is masked as well. This is illustrated by steps 232 and 242. Of course, the technique chosen to mask status signal 176 is simply a design choice to be made upon implementation of the invention. As stated above, there may be applications where other data is transferred via data port

125. In such cases, it may be desirable to disable the autosync process when data port 125 is used to handle communications for these other data modes. As such, the process illustrated in Figure 4 illustrates the step of checking to determine whether the handset or electronic device is currently configured for another data mode and, if so, the status signal 176 is masked to avoid automatic synchronization in other data modes.

Also illustrated in Figure 4 is a process for returning to the autosync mode after the device has been disconnected and reconnected to interface 140. This is illustrated by step 246 and flow line 264. This step can be provided for the purpose of allowing the status of autosync to be checked each time the device is connected to interface 140 and to begin the autosync process as illustrated by step 232 each time the device is connected or reconnected to interface 140.

In one or more of the embodiments described above, it is useful to check whether the electronic device has been disconnected from interface 140 and reconnected in determining whether to begin the autosync process. Particularly, in the embodiment described above, this step removes the mask provided to status line 176, allowing the synchronization process to take place even if the electronic device was previously in another data mode during the previous connection. There are several techniques that can be implemented to check to determine whether an electronic device has been disconnected and reconnected to interface 140. One such technique is to check for a high-impedance condition at the input of transmit pin 162. If the high impedance condition occurs, this indicates that the electronic device is disconnected from interface 140. Another technique is to require that the status signal 176 be true over a plurality of sequential clock-cycles. This condition would indicate that data from another data mode is no longer present or being transferred on transmit line at transmit pin 162. Similarly, a false status signal 176 for a given number of clock-cycles may also be used to sense a disconnect of interface 140. The various embodiments and features of the invention described above may be implemented using hardware, software or a combination thereof and may be implemented using a computing system having one or more processors. In fact, in one embodiment, these elements are implemented using a processor-based system capable of carrying out the functionality described with respect thereto. An example processor-based system 302 is shown in Figure 5. The computer system 302 includes one or more processors, such as processor 304. The processor 304 is connected to a communication bus 306. Various software embodiments are described in terms of this example computer system. After reading this description, it will become apparent to a person skilled in the relevant art how to implement the invention using other computer or processor systems and/or architectures. The functionality of the invention as described above is not dependent on a particular computer or processor architecture.

Processor-based system 302 can include a main memory 308, preferably random access memory (RAM), and can also include a secondary memory 310. The secondary memory 310 can include, for example, a hard disk drive 312 and/or a removable storage drive 314, representing a floppy disk drive, a magnetic tape drive, an optical disk drive, etc. The removable storage drive 314 reads from and/or writes to a removable storage medium 318 in a well-known manner. Removable storage media 318, represents a floppy disk, magnetic tape, optical disk, etc. which is read by and written to by removable storage drive 314. As will be appreciated, the removable storage media 318 includes a computer usable storage medium having stored therein computer software and/or data. In alternative embodiments, secondary memory 310 may include other similar means for allowing computer programs or other instructions to be loaded into computer system 302.

Such means can include, for example, a removable storage unit 322 and an interface 320.

Examples of such can include a program cartridge and cartridge interface (such as that found in video game devices), a removable memory chip (such as an EPROM, or PROM) and associated socket, and othei removable storage units 322 and interfaces 320 which allow software and data to be transferred from the removable storage unit 322 to computer system

302.

Computer system 302 can also include a communications interface 324. Communications interface 324 allows software and data to be transferred between computer system 302 and external devices. Examples of communications interface 324 can include a modem, a network interface (such as, for example, an Ethernet card), a communications port, a PCMCIA slot and card, etc. Software and data transferred via communications interface 324 are in the form of signals which can be electronic, electromagnetic, optical or other signals capable of being received by communications interface 324. These signals are provided to communications interface via a channel 328. This channel 328 carries signals and can be implemented using a wireless medium, wire or cable, fiber optics, or other communications medium. Some examples of a channel can include a phone line, a cellular phone link, an RF link, a network interface, and other communications channels. In this document, the terms "computer program medium" and "computer usable medium" are used to generally refer to media such as removable storage device 318, a disk capable of installation in disk drive 312, and signals on channel 328. These computer program products are means for providing software or program instructions to computer system 302. Computer programs (also called computer control logic) are stored in main memory and/or secondary memory 310. Computer programs can also be received via communications interface 324. Such computer programs, when executed, enable the computer system 302 to perform the features of the present invention as discussed herein. In particular, the computer programs, when executed, enable the processor 304 to perform the features of the present invention. Accordingly, such computer programs represent controllers of the computer system 302. In an embodiment where the elements are implemented using software, the software may be stored in, or transmitted via, a computer program product and loaded into computer system 302 using removable storage drive 314, hard drive 312 or communications interface

324. The control logic (software), when executed by the processor 304, causes the processor 304 to perform the functions of the invention as described herein.

In another embodiment, the elements are implemented primarily in hardware using, for example, hardware components such as PALs, application specific integrated circuits (ASICs) or other hardware components. Implementation of a hardware state machine so as to perform the functions described herein will be apparent to persons skilled in the relevant art(s). In yet another embodiment, elements are implemented using a combination of both hardware and software.

4. Data and Power Interfaces Implemented in Handset Battery Pack (Figures

6-8)

As illustrated in Figures 6 and 7, power source 118 may be implemented in handset 100 as a removable battery pack 200. In one implementation, battery pack 200 includes a rechargeable lithium ion battery. To insert battery pack 200 into handset 100, a user 199 aligns the battery alignment slots and inserts the top of battery pack 200 into the top of battery slot 198 at a slight angle (Figure 6). Once the top of the battery pack 200 is inserted, the user lays pack 200 flat in slot 198 and pushes pack 200 forward to click and lock it into place within slot 198 (Figure 7).

As is evident in Figure 7, battery pack 200 includes metal contact areas 201 and 207 at the bottom portion of the pack. Contact areas 201 and 207 are illustrated in more detail in

Figure 8, which is an enlarged block diagram of battery pack 200. When used in conjunction with a docking station such as docking station 124 of Figure 2, metal contact areas 201 and 207 will connect to mating electrical contacts in the docking station.

Figure 8 is just one feasible implementation of batter pack 200 and contact areas 201 and 207. In this implementation, contact area 201 contains two contact pins 202 and 204 which extend completely through battery pack 200, and one contact pin 206 that extends partially through pack 200. Similarly, contact area 207 includes two contact pins 210 and 212 that extend completely through pack 200, and one contact pin 208 that extends partially through pack 200. Alternate pin arrangements and contact areas will be apparent to those of ordinary skill in the art and are within the ambit of the present invention.

In Figure 8, outermost pins 202 and 212 are used, respectively, as a ground (GND) contact and a power (+V) contact. Referring to Figure 3 and the associated discussion above, if data port 125 and power line 188 were implemented in the battery pack of Figure 8, the

GND pin 202 would be connected to ground line 186 of interface 140 (i.e., a docking station

124). The +V pin 212 would be connected to line 188.

As noted above, pack 200 includes innermost pins 206 and 208 that extend only partially through pack 200. These pins have no equivalent that is shown in Figure 3, but in one implementation, pin 206 is used for temperature sensing purposes and pin 208 is available for any other appropriate use.

Middle pins 204 and 210 also extend completely through pack 200. These pins are provided in order to provide increased flexibility of use for battery pack 200. This increased flexibility lends itself to the present application, where middle pin 204 is used as a transmit (Tx) pin and middle pin 210 is used as a receive (Rx) pin. In Figure 3, Tx pin 204 would be connected to transmit path 182 of interface (docking station) 140, and Rx pin 210 would be connected to receive path 184 of the docking station.

Using battery pack 200 in conjunction with the interface configuration of Figure 3 permits use of battery pack 200 for transfer of serial data between handset 100 and computer 126. Data can be transferred from handset 100 through pack 200 via Tx pin 204, and through the transmit line 182 of a docking station to computer 126. Similarly, data can be transferred from computer 126 through the docking station via receive path 184, and through battery pack

Rx pin 204. In the same motion as placing handset 100 in a docking station for recharge of battery pack 200, automatic exchange of data and synchronization as described above can take place through battery pack 200 with no further action or selections of the user being required.

While various embodiments of the present invention have been described above, it should be understood that they have been presented by way of example only, and not limitation. Thus, the breadth and scope of the present invention should not be limited by any of the above-described exemplary embodiments, but should be defined only in accordance with the following claims and their equivalents.

Claims

WE CLAIM:

1. A system for interfacing a portable electronic device with a host computer comprising: an interface comprising a transmit and receive path to permit exchange of data between the electronic device and host computer; a processor within the portable electronic device for directing the overall operation of the device, the processor having a receive pin for receiving data and a transmit pin for transmitting data; a removable battery pack attached to the portable electronic device for providing power to the device, the battery pack having a first electrical contact extending through the pack and connecting the transmit path of the interface with the processor transmit pin to permit transmission of data from the electronic device to the host computer; and a second electrical contact extending through the pack and connecting the receive path of the interface with the processor receive pin to permit reception of data by the electronic device from the host computer.

2. The system of claim 1, wherein the electronic device and interface each further comprise a power supply line and a ground, and wherein the battery pack has a third electrical contact extending through the pack to connect the interface and device power supply lines, and a fourth electrical contact extending through the pack to connect the interface and device grounds.

3. The system of claim 2, wherein the portable electronic device is a wireless communication handset, and wherein the interface is a docking station having electrical contacts configured to mate with the electrical contacts of the battery pack.

4. The system of claim 3, wherein the handset further comprises computer program code logic configured to automatically synchronize the handset with the host computer without user intervention via the first and second electrical contacts of the battery pack.

5. In a wireless communications handset having a central processing unit configured to transmit and receive data to and from an external communications device, a removable battery pack for powering the handset, the removable battery pack comprising:. a first electrical contact extending completely through the battery pack for transmitting data from the central processing unit to the external communications device; and a second electrical contact extending completely through the battery pack for reception of data from the external communications device to the central processing unit.

6. The battery pack of claim 5, and further comprising a third electrical contact extending completely through the pack for connection of a battery within the pack to an external power source for recharging.

7. The battery pack of claim 7, and further comprising a fourth electrical contact extending completely through the pack for connection of a ground within the handset to an external ground.

8. The battery pack of claim 7, and further comprising fifth and sixth electrical contacts extending partially through the pack.