This application is related to: (i) U.S. patent application Ser. No. 11/245,937, filed Oct. 7, 2005, and entitled “TECHNIQUES FOR PAIRING REMOTE CONTROLLERS WITH HOST DEVICES”, which is hereby incorporated by reference herein; and (i) U.S. patent application Ser. No. 11/513,692, filed concurrently, and entitled “PAIRING OF WIRELESS DEVICES USING A WIRED MEDIUM”.
1. Field of the Invention
The present invention relates to wireless devices and, more particularly, to pairing wireless devices for authorized data exchange.
2. Description of the Related Art
Traditionally, headphones or earphones are connected to an audio output device, such as a mobile phone, through a wired connection. The wired connection can, however, in many cases be cumbersome or annoying to the user. Hence, in recent times, wireless headsets or earphones have been developed. Typically, these wireless devices utilize Bluetooth technology in order to wirelessly transmit data between the headset or earphone and the mobile phone. As a result, there is no need for a wired connection between the headset or earphones and the media player.
Unfortunately, however, before the wireless headset or earphone can operate in a wireless manner with a mobile phone, the wireless headset or earphone must be paired to operate with the mobile phone. Pairing is a process that is used to associate a headset or earphone with a particular mobile phone, and vice versa. The pairing provides for secure data transfer between the devices, typically through use of encryption. Thus, the pairing helps ensure that the data being transferred is not only secured but also transferred to the appropriate recipient device. Pairing, however, requires that a pin code be entered in order to pair a mobile phone with a headset or earphone. Entering of a pin code is sometimes problematic for a user. For example, often mobile audio devices are small handheld devices and the entering of a pin code can be cumbersome given the small scale of mobile audio devices (e.g., mobile phones, portable music players, etc.). The mobile audio devices may also not offer a user interface that supports ease of entry of a pin code. Still further, users often do not know the appropriate pin code to be utilized.
Moreover, given that a mobile audio device can wirelessly pair with headsets or earphones associated with a large range of different manufacturers, a mobile audio device manufacturer has no control over the type of headset or earphones that a user might desire to pair with their mobile audio device. In limited cases, such as when the manufacturer of the mobile audio device is the same as the manufacturer of the headset or earphones, it is possible that a user need not enter a pin code because a proprietary exchange of information can facilitate pairing.
Thus, there is a need for improved techniques to facilitate pairing of wireless headsets or earphones with mobile audio devices.
The invention pertains to improved techniques that facilitate pairing of wireless accessory devices with wireless host devices. Advantageously, the improved techniques permit pairing of wireless devices without requiring user entry of pin codes.
In one embodiment, a wireless accessory device is a headset or earphone and a wireless host device is an audio output device, such as a mobile phone or media player. The media player can be a portable media player, a docking station for a portable media player, a dedicated media appliance, or a computer having media playback capabilities.
The invention can be implemented in numerous ways, including as a method, system, device, apparatus, or computer readable medium. Several embodiments of the invention are discussed below.
As a method for pairing a wireless electronic accessory device with a wireless host device, one embodiment of the invention includes at least the acts of: receiving a request to initiate pairing of the wireless host device with the wireless electronic accessory device, where the manufacturer of the wireless host device is different than the manufacturer of the wireless electronic accessory device; obtaining a potential pin code for the wireless accessory device from an electronic data storage device within the wireless host device; attempting to pair the wireless host device with the wireless electronic accessory device using the potential pin code; and completing the pairing of the wireless host device with the wireless electronic accessory device when the potential pin code matches the pin code required by the wireless electronic accessory device.
As a method for pairing a wireless electronic accessory device with a wireless host device, another embodiment of the invention includes at least the acts of: receiving a request to initiate pairing of the wireless host device with the wireless electronic accessory device; obtaining a set of potential pin codes for the wireless accessory device from an electronic data storage device; attempting to pair the wireless host device with the wireless electronic accessory device using one of the potential pin codes; repeating the attempting using another one of the potential pin codes when the one of the potential pin codes being used does not match the pin code required by the wireless electronic accessory device; and completing the pairing of the wireless host device with the wireless electronic accessory device when the one of the potential pin codes being used matches the pin code required by the wireless electronic accessory device.
As a computer readable medium including computer program code for pairing a wireless electronic accessory device with a wireless host device, one embodiment of the invention includes at least: computer program code for receiving a request to initiate pairing of the wireless host device with the wireless electronic accessory device; computer program code for obtaining a set of potential pin codes for the wireless accessory device from an electronic data storage device; computer program code for attempting to pair the wireless host device with the wireless electronic accessory device using one of the potential pin codes and repeating the attempting using another one of the potential pin codes when the one of the potential pin codes being used does not match the pin code expected by the wireless electronic accessory device; and computer program code for completing the pairing of the wireless host device with the wireless electronic accessory device when the one of the potential pin codes being used matches the pin code expected by the wireless electronic accessory device.
As a portable electronic device, one embodiment of the invention includes at least: a memory for storing data and executable computing code; a controller for operating the portable electronic device including executing the executable computing code; and a pin code database storing a plurality of potential pin codes for wireless companion devices of a plurality of different manufacturers. The executable computing code can perform pairing operations as well as other operations.
Other aspects and advantages of the invention will become apparent from the following detailed description taken in conjunction with the accompanying drawings which illustrate, by way of example, the principles of the invention.
The invention will be readily understood by the following detailed description in conjunction with the accompanying drawings, wherein like reference numerals designate like structural elements, and in which:
The invention pertains to improved techniques that facilitate pairing of wireless accessory devices with wireless host devices. Advantageously, the improved techniques permit pairing of wireless devices without requiring user entry of pin codes.
In one embodiment, a wireless accessory device is a headset or earphone and a wireless host device is an audio output device, such as a mobile phone or media player. The media player can be a portable media player, a docking station for a portable media player, a dedicated media appliance, or a computer having media playback capabilities.
Embodiments of this aspect of the invention are discussed below with reference to
In order for the wireless host device 102 to be able to transmit or receive data to or from the wireless accessory device 104, the wireless accessory device 104 needs to be paired with the wireless host device 102. Pairing is a process that is used to associate the wireless accessory device 104 with the wireless host device 102. The pairing ensures that the data being transferred is not only secured but also transferred to the appropriate recipient device.
In general, the pairing of these devices can be performed in a substantially automated manner. As discussed in greater detail below, the wireless host device 102 will receive information about the wireless accessory device 104. Then, in order to pair the devices together, the wireless host device 102 can determine one or more potential (i.e., likely) pin codes associated with the wireless accessory device 104. Then, the wireless host device 102 can attempt to pair itself with the wireless accessory device 104 using the one or more potential pin codes. Assuming that one of the potential pin codes is the actual pin code required by the wireless accessory device 104, the pairing process is able to be completed without requiring the user of the wireless host device 102 to enter a pin code. In the event that none of the potential pin codes attempted is the required pin code for the wireless accessory device 104, the user of the wireless host device 102 can still thereafter be prompted to enter the required pin code. Once the pairing has been established, the wireless host device 102 and the wireless accessory device 104 are able to exchange data in a substantially secure manner.
In one embodiment, the pin code is used to establish a link key that is utilized by both the wireless host device 102 and the wireless accessory device 104 when encrypting data to be exchanged between these devices. Each of the devices is also able to decrypt any received encrypted data.
The inter-device communication system 200 also includes a client computing device 208. The client computing device is, for example, a personal computer. The client computing device can connect to the wireless host device 202 over a cable 210. The cable 210 is, for example, a USB cable or a Firewire cable. Alternatively, the client computing device 208 can wirelessly connect to the wireless host device 202 through the local wireless network 206. The client computing device 208 can also couple to a data network 212. The data network 212 can be a local area network, a wide area network, or a global network, such as the Internet. A remote server 214 can also couple to the data network 212.
The wireless host device 202 can receive data pertaining to potential pin codes from the client computing device 208, either via the cable 210 or via the local wireless network 206. The client computing device 208 can, in turn, receive data regarding potential pin codes from the remote server 214 via the data network 212. As such, the remote server 214 can provide potential pin codes to a wide range of client computing devices 208 via the data network 212. These various client computing devices 208 can then provide the potential pin codes to wireless host devices 202 that are associated with the client computing devices 208. In this manner, wireless host devices 202 are able to receive updated pin codes from the remote server 214, which can be useful to support future wireless accessory devices.
The accessory device 302 is a low power device and thus can be powered by a battery 306. The accessory device 302 also includes at least a controller 308, a user input device 310 and a memory 312. The controller 308 controls the overall operation of the accessory device 302. The user input device 310 enables a user to interact with the accessory device 302. As an example, the user input device 310 can include a button that enables a user to place the accessory device 302 into a pairing mode. The memory 312 provides persistent data storage for various elements, including program code, identifier(s), data structures, etc. Still further, the accessory device 302 includes a transceiver 314. In one embodiment, the transceiver 314 is a radio-frequency (RF) transceiver. The transceiver 314 can output a wireless transmission 316. Typically, the wireless transmission 316 is directed toward the host device 304.
The host device 304 includes a receiver 318 for the wireless transmission 316. The host device 304 includes at least a controller 320, a memory 322, an operating system 324, application program(s) 326, an output device 328 and a user input device 330. The controller 320 controls the overall operation of the host device 304. The memory 322 can be used to store persistent data, including program code (e.g., for the operating system 324 and the application program(s) 326), identifier(s), data structures, etc. The operating system 324 together with the controller 320 enables the host device 304 to not only wirelessly receive transmissions from the accessory device 302, but to also support and operate one or more application programs 326 as well as to utilize the output device 328 and the user input device 330. The host device 304 can also include a pin code database 332. The pin code database 332 can store a plurality of pin codes associated with different manufacturers, device types, and etc. During pairing, the host device can attempt to pair using one or more of the pin codes stored in the pin code database 332. Although the pin code database 332 is shown as a separate component, it should be noted that the pin code database 332 can be stored in the memory 332.
The accessory device 302 can communicate with the host device 304 over a wireless link 316. As a result of such communication, the operation of the host device 304 can be manipulated by a user of the accessory device 302. In this embodiment, the communication is uni-directional—from accessory device 302 to the host device 304. However, in other embodiments, the communication could be bi-directional.
According to one aspect of the invention, the accessory device 302 can be paired with the host device 304. When paired, the accessory device 302 is responsive to only the host device 304. Hence, if there are other host devices in the vicinity of the accessory device 302, the accessory device 302 understands to ignore wireless communications from such other host devices. In contrast, when unpaired, the accessory device 302 can be responsive to any compatible host devices in the vicinity. The host device 304 can also be paired with more than one accessory device.
Additional details are discussed below for the operations associated with pairing accessory devices to host devices. When paired, a user of the accessory device 302 can interact with the one or more application programs 326 operating on the host device 304. For example, one type of application program 326 is a media player program capable of playing digital media assets stored in the memory 322 or some other memory accessible by the host device 304. Hence, the user of the accessory device 302 can interact with the user input device 310 of the remote controller 302 to manipulate media playback controls, such as volume changes, next track, previous track, and play and pause operations associated with the media player program. For other types of application programs 326 available at the host device 304, the particular controls or commands being provided by the accessory device 302 to the host device 304 can vary widely depending upon the application.
The pin code database 332 can also be updated through user entry of pin codes or data transmission(s) to the host device 304. Through such updates to the pin code database 332, the ability to successfully pair devices can become more robust and efficient. Moreover, the automatic pairing aspects of the invention can also support newly released accessory devices that may utilize different pin codes.
The pairing initiation process 400 initially places 402 a wireless device to be paired in a pairing mode. For example, a wireless accessory device can be placed in a pairing mode by physical action with respect to the wireless accessory device. In one example, a button can be pressed on the wireless accessory device to cause the wireless accessory device to enter a pairing mode. Next, a user interface (UI) of the wireless host device is navigated 404 so as to request pairing with another wireless device (e.g., the wireless accessory device). In one embodiment, the navigation 404 involves one or more selections from a graphical user interface so that the user of the wireless host device can request that pairing be performed. Once pairing has been requested, available wireless devices in the vicinity of the wireless host device are discovered 406. The discovered available wireless devices are then displayed 408 on the user interface. In one embodiment, as each of the available wireless devices is discovered, the user interface is updated as each of the available devices is discovered. Typically, the discovered available wireless devices are displayed 408 such that the user of the wireless host device can select one of the available wireless devices to be paired with. Hence, a decision 410 determines whether a user selection of one of the discovered available wireless devices has been made. When the decision 410 determines that a user selection of one of the discovered available wireless devices has not yet been made, the pairing initiation process 400 awaits such a selection.
On the other hand, when the decision 410 determines that a user has selected one of the discovered available wireless devices, the wireless host device is paired 412 with the selected wireless device. Here, in order to pair the wireless host device with the selected wireless device, a pairing processing is performed. The pairing processing is, for example, described in
The device pairing process 500 begins with a pairing request 502. When the decision 502 determines that a pairing request has not been made, the device pairing process 500 awaits such a request. On the other hand, when the decision 502 determines that a pairing request has been received, the device pairing process 500 continues. In other words, the device pairing process 500 can be deemed invoked once pairing is to be performed between a wireless host device and a wireless accessory device. As an example, the block 410 illustrated in
Once the decision 502 determines that a pairing request has been received, a set of potential pin codes for the wireless accessory device is obtained 504. A potential pin code is then selected 506 from the set of potential pin codes. Then, a pairing request is sent 508 from the wireless host device to the wireless accessory device. A decision 510 then determines whether pairing between the wireless host device and the wireless accessory device has been successful. When the pairing has not been successful, a decision 512 determines whether there are more potential pin codes to be attempted. When the decision 512 determines that there are more potential pin codes to be attempted, the device pairing process 500 returns to repeat blocks 506-510 so that a next potential pin code can be selected and attempted. On the other hand, when the decision 510 determines that pairing has been successful, a link key for use with the wireless accessory device is stored 514. The link key is a cryptographic key that is utilized in data communication or data transfer with the wireless accessory device. The link key results from the pairing operation and facilitates the secure data transfer between the wireless host device and the wireless accessory device that are now paired. Following the block 514, the device pairing process 500 is complete and ends with the pairing being successful.
Alternatively, when the decision 512 determines that there are no more potential pin codes, then the pairing process has not been able to successfully complete using any of the potential pin codes from the set of potential pin codes. Hence, additional processing is performed to facilitate pairing. Namely, a user of the wireless host device is prompted 516 to enter a pin code. For example, the user could be prompted by a graphical user interface to enter a pin code using a alphanumeric keypad. A decision 518 then determines whether a pin code has been entered. When the decision 518 determines that a pin code has not yet been entered, the device pairing process 500 awaits entry of a pin code.
When the decision 518 determines that a pin code has been entered, a pairing request is sent 520 from the wireless host device to the accessory device. Next, a decision 522 determines whether pairing has been successful. When the decision 522 determines that pairing has not been successful, a decision 524 determines whether reentry is permitted. Here, the device pairing process 500 can limit the number of pin code entry attempts that are permitted. The decision 524 can thus determine whether additional pin code entry is permitted. When the decision 524 determines that a retry is permitted, then the device pairing process 500 returns to repeat the block 516 and subsequent blocks so that the user can attempt to pair the devices using yet another pin code that is entered. Alternatively, when the decision 524 determines that a retry is not permitted, then the device pairing process 500 ends with the devices not having been paired.
On the other hand, when the decision 522 determines that pairing has been successful following user entry of a pin code, the device pairing process 500 performs the block 514 where a link key is stored 514 for use with data exchanges between the wireless host device and the wireless accessory device that are now paired. Following the block 514, the device pairing process 500 ends with pairing being successful, albeit in this case due to a user-entered pin code.
In another embodiment of the device pairing process, in addition to storing 514 the link key at block 514, the device pairing process can store the pin code that led to the successful pairing (from either a potential pin code or a manually entered pin code). Hence, the host device can store the link key and/or the pin code for use with the wireless accessory device. The storage of these keys or codes can be done in association with network addresses, identifiers, and/or manufacturers to facilitate subsequent retrieval of the appropriate codes and/or keys. Indeed, since a host device can support more than one wireless accessory device, the host device can store link keys and/or pin codes for various accessory devices. In the event that the pairing of the host device and the wireless accessory device is lost, the pairing process can proceed (i.e., re-pair) on an automatic basis using a stored pin code (e.g., blocks 504-508).
In still another embodiment of the device pairing process, the set of potential pin codes being obtained 504 in the device pairing process 500 can be limited. In particular, when a wireless accessory device limits the number of successive attempts to enter a correct pin code, the set of potential pin codes to be attempted can be limited to not exceed the limit. More particularly, the number of potential pin codes to be attempted can be one less than the maximum number of attempts being permitted. Since many different wireless accessory device manufacturers have different limits, in one implementation, a database can store the maximum number of permitted attempts for various devices and/or manufacturers, and then the appropriate maximum number can be retrieved and utilized to limit the number of pairing requests using the pin code from the set of potential pin codes to be automatically attempted. The database can be part of or separate from the pin code database 332.
Assuming that pairing has been successful between a wireless host device and a wireless accessory device, thereafter, data transfer can be performed between the wireless host device and the wireless accessory device in a secured and controlled manner through use of the link key that was established during the pairing operation.
The wireless data transfer process 600 begins with a decision 602 that determines whether a connection to the wireless accessory device is desired. When the decision 602 determines that a connection from the wireless host device to the wireless accessory device is not desired, then the wireless data transfer process 600 is effectively not invoked. Alternatively, when the decision 602 determines that a connection between the wireless host device and the wireless accessory device is desired, the wireless data transfer process 600 is effectively invoked. In such case, a decision 602 determines whether the wireless host device has a link key for use with the wireless accessory device. When the wireless host device does not have such a link key, the desired connection is not available 606. Typically, in this case, the wireless host device has not been successfully paired with the wireless accessory device and thus does not have a link key that facilitates data transfer with the wireless accessory device. On the other hand, when the decision 604 determines that the wireless host device does have an appropriate link key for use with the wireless accessory device, the wireless host device connects 608 to the wireless accessory device using the known link key. With the connection being established, data can then be transmitted over a wireless link provided by the connection between the wireless host device and the wireless accessory device. Next, a decision 612 determines whether the connection is to be closed. When the decision 612 determines that the connection is not to be closed, data transfer over a wireless link can continue to be transferred 610. As an example, the wireless accessory device can be a headset and the wireless host device can be a media player or cellular phone. In either case, the user can use the headset to interact with the media player or cellular phone in a wireless manner. Alternatively, when the decision 612 determines that the connection should be closed, the connection is then closed 614. Following the block 614, as well as following the block 606, the wireless data transfer process 600 ends.
The various aspects, embodiments, implementations or features of the invention can be used separately or in any combination.
The invention can be implemented by software, hardware or a combination of hardware and software. The invention can also be embodied as computer readable code on a computer readable medium. The computer readable medium is any data storage device that can store data which can thereafter be read by a computer system. Examples of the computer readable medium include read-only memory, random-access memory, CD-ROMs, DVDs, magnetic tape, optical data storage devices. The computer readable medium can also be distributed over network-coupled computer systems so that the computer readable code is stored and executed in a distributed fashion.
The advantages of the invention are numerous. Different aspects, embodiments or implementations may yield one or more of the following advantages. One advantage of the invention is that wireless device can be paired without any need for a user enter a pin code that is often not readily available to the user. In other words, pairing of wireless devices can be achieved in a substantially automated manner. Another advantage of the invention is that a wireless host device can provide a data storage with potential pin codes that can be intelligently selected and attempted for pairing other wireless devices, such as wireless accessory devices. Still another advantage of the invention is that potential pin codes' storage in the data storage of the wireless host device can be updated by a remote server which can provide additional potential codes.
The many features and advantages of the present invention are apparent from the written description. Further, since numerous modifications and changes will readily occur to those skilled in the art, the invention should not be limited to the exact construction and operation as illustrated and described. Hence, all suitable modifications and equivalents may be resorted to as falling within the scope of the invention.
Number | Name | Date | Kind |
---|---|---|---|
3612265 | Dickerson | Oct 1971 | A |
3807388 | Orr et al. | Apr 1974 | A |
3918058 | Noyori et al. | Nov 1975 | A |
3958459 | Shimomura | May 1976 | A |
3978725 | Haditke | Sep 1976 | A |
4089057 | Eriksson | May 1978 | A |
4090216 | Constable | May 1978 | A |
4101873 | Anderson et al. | Jul 1978 | A |
4114450 | Shulman et al. | Sep 1978 | A |
4195642 | Price et al. | Apr 1980 | A |
4210024 | Ishiwatari et al. | Jul 1980 | A |
4223211 | Allsen et al. | Sep 1980 | A |
4248244 | Charnitski et al. | Feb 1981 | A |
4317126 | Gragg, Jr. | Feb 1982 | A |
4371188 | Hull | Feb 1983 | A |
4371945 | Karr et al. | Feb 1983 | A |
4375674 | Thornton | Mar 1983 | A |
4386345 | Narveson et al. | May 1983 | A |
4423630 | Morrison | Jan 1984 | A |
4434801 | Jiminez et al. | Mar 1984 | A |
4451849 | Fuhrer | May 1984 | A |
4516110 | Overmyer | May 1985 | A |
4516865 | Hideo | May 1985 | A |
4578769 | Frederick | Mar 1986 | A |
4589022 | Prince et al. | May 1986 | A |
4625733 | Saynajakangas | Dec 1986 | A |
4694694 | Vlakancic et al. | Sep 1987 | A |
4699379 | Chateau et al. | Oct 1987 | A |
4703445 | Dassler | Oct 1987 | A |
4720093 | Del Mar | Jan 1988 | A |
4722222 | Purdy et al. | Feb 1988 | A |
4736312 | Dassler et al. | Apr 1988 | A |
4745564 | Tennes et al. | May 1988 | A |
4757453 | Nasiff | Jul 1988 | A |
4757714 | Purdy et al. | Jul 1988 | A |
4759219 | Cobb et al. | Jul 1988 | A |
4763275 | Carlin | Aug 1988 | A |
4763284 | Carlin | Aug 1988 | A |
4763287 | Gerhaeuser et al. | Aug 1988 | A |
4771394 | Cavanagh | Sep 1988 | A |
4774679 | Carlin | Sep 1988 | A |
4775948 | Dial et al. | Oct 1988 | A |
4780837 | Namekawa | Oct 1988 | A |
4821218 | Potsch | Apr 1989 | A |
4822042 | Landsman | Apr 1989 | A |
4824107 | French | Apr 1989 | A |
4829812 | Parks et al. | May 1989 | A |
4830021 | Thornton | May 1989 | A |
4862394 | Thompson et al. | Aug 1989 | A |
4862395 | Fey et al. | Aug 1989 | A |
4873867 | McPherson et al. | Oct 1989 | A |
4876500 | Wu | Oct 1989 | A |
4883271 | French | Nov 1989 | A |
4903212 | Yokouchi et al. | Feb 1990 | A |
4908523 | Snowden et al. | Mar 1990 | A |
4928307 | Lynn | May 1990 | A |
4935887 | Abdalah et al. | Jun 1990 | A |
4951171 | Tran et al. | Aug 1990 | A |
4955980 | Masuo | Sep 1990 | A |
5033013 | Kato et al. | Jul 1991 | A |
5036467 | Blackburn et al. | Jul 1991 | A |
5056783 | Matcovich et al. | Oct 1991 | A |
5067081 | Person | Nov 1991 | A |
5088836 | Yamada et al. | Feb 1992 | A |
5117444 | Sutton et al. | May 1992 | A |
5144226 | Rapp | Sep 1992 | A |
5148002 | Kuo et al. | Sep 1992 | A |
5150310 | Greenspun et al. | Sep 1992 | A |
5162828 | Furness et al. | Nov 1992 | A |
5181181 | Glynn | Jan 1993 | A |
5200827 | Hanson et al. | Apr 1993 | A |
5243993 | Alexander et al. | Sep 1993 | A |
5258927 | Havriluk et al. | Nov 1993 | A |
5295085 | Hoffacker | Mar 1994 | A |
5316249 | Anderson | May 1994 | A |
5324038 | Sasser | Jun 1994 | A |
5335664 | Nagashima | Aug 1994 | A |
5339699 | Carignan | Aug 1994 | A |
5343445 | Cherdak | Aug 1994 | A |
5348519 | Prince et al. | Sep 1994 | A |
5382972 | Kannes | Jan 1995 | A |
5396429 | Hanchett | Mar 1995 | A |
5406305 | Shimomura et al. | Apr 1995 | A |
5420828 | Geiger | May 1995 | A |
5426595 | Picard | Jun 1995 | A |
5436838 | Miyamori | Jul 1995 | A |
5446775 | Wright et al. | Aug 1995 | A |
5450329 | Tanner | Sep 1995 | A |
5452269 | Cherdak | Sep 1995 | A |
5471405 | Marsh | Nov 1995 | A |
5475725 | Nakamura | Dec 1995 | A |
5476427 | Fujima | Dec 1995 | A |
5485402 | Smith et al. | Jan 1996 | A |
5486815 | Wagner | Jan 1996 | A |
5487006 | Kakizaki et al. | Jan 1996 | A |
5509082 | Toyama et al. | Apr 1996 | A |
5513854 | Daver | May 1996 | A |
5524637 | Erickson | Jun 1996 | A |
5526326 | Fekete et al. | Jun 1996 | A |
5528228 | Wilk | Jun 1996 | A |
5539336 | Nguyen et al. | Jul 1996 | A |
5541604 | Meier | Jul 1996 | A |
5546307 | Mazur et al. | Aug 1996 | A |
5546974 | Bireley | Aug 1996 | A |
5559945 | Beaudet et al. | Sep 1996 | A |
5564698 | Honey et al. | Oct 1996 | A |
5574669 | Marshall | Nov 1996 | A |
5583776 | Levi et al. | Dec 1996 | A |
5583993 | Foster et al. | Dec 1996 | A |
5590908 | Carr | Jan 1997 | A |
5592401 | Kramer | Jan 1997 | A |
5605336 | Gaoiran et al. | Feb 1997 | A |
5608698 | Yamanoi et al. | Mar 1997 | A |
5615132 | Horton et al. | Mar 1997 | A |
5616876 | Cluts | Apr 1997 | A |
5617084 | Sears | Apr 1997 | A |
5617386 | Choi | Apr 1997 | A |
5618995 | Otto et al. | Apr 1997 | A |
5627548 | Woo et al. | May 1997 | A |
5629131 | De Keyzer et al. | May 1997 | A |
5633070 | Murayama et al. | May 1997 | A |
5636146 | Flentov et al. | Jun 1997 | A |
5646857 | McBurney et al. | Jul 1997 | A |
5670985 | Cappels, Sr. et al. | Sep 1997 | A |
5671010 | Shimbo et al. | Sep 1997 | A |
5671162 | Werbin | Sep 1997 | A |
5673691 | Abrams et al. | Oct 1997 | A |
5680102 | Xydis | Oct 1997 | A |
5684513 | Decker | Nov 1997 | A |
5688183 | Sabatino et al. | Nov 1997 | A |
5690119 | Rytky et al. | Nov 1997 | A |
5690591 | Kenmochi et al. | Nov 1997 | A |
5690773 | Fidalgo et al. | Nov 1997 | A |
5694340 | Kim | Dec 1997 | A |
5701257 | Miura et al. | Dec 1997 | A |
5710922 | Alley et al. | Jan 1998 | A |
5712638 | Issa | Jan 1998 | A |
5712949 | Kato et al. | Jan 1998 | A |
5720200 | Anderson et al. | Feb 1998 | A |
5721539 | Goetzi | Feb 1998 | A |
5721949 | Smith et al. | Feb 1998 | A |
5723786 | Klapman | Mar 1998 | A |
5724265 | Hutchings | Mar 1998 | A |
5726672 | Hernandez et al. | Mar 1998 | A |
5734337 | Kupersmit | Mar 1998 | A |
5738104 | Lo et al. | Apr 1998 | A |
5739451 | Winksy et al. | Apr 1998 | A |
5740143 | Suetomi | Apr 1998 | A |
5743269 | Okigami et al. | Apr 1998 | A |
5745037 | Guthrie et al. | Apr 1998 | A |
5749615 | Itson | May 1998 | A |
5761096 | Zakutin | Jun 1998 | A |
5771485 | Echigo | Jun 1998 | A |
5779576 | Smith, III et al. | Jul 1998 | A |
5781155 | Woo et al. | Jul 1998 | A |
5790477 | Hauke | Aug 1998 | A |
5807284 | Foxlin | Sep 1998 | A |
5812056 | Law | Sep 1998 | A |
5815225 | Nelson | Sep 1998 | A |
5822288 | Shinada | Oct 1998 | A |
5835721 | Donahue et al. | Nov 1998 | A |
5835732 | Kikinis et al. | Nov 1998 | A |
5862803 | Besson et al. | Jan 1999 | A |
5864868 | Contois | Jan 1999 | A |
5870710 | Ozawa et al. | Feb 1999 | A |
5886739 | Winningstad | Mar 1999 | A |
5891042 | Sham et al. | Apr 1999 | A |
5895073 | Moore | Apr 1999 | A |
5897457 | Mackovjak | Apr 1999 | A |
5899963 | Hutchings | May 1999 | A |
5901303 | Chew | May 1999 | A |
5905460 | Odagiri et al. | May 1999 | A |
5918281 | Nabulsi | Jun 1999 | A |
5918303 | Yamaura et al. | Jun 1999 | A |
5920728 | Hallowell et al. | Jul 1999 | A |
5923757 | Hocker et al. | Jul 1999 | A |
5925001 | Hoyt et al. | Jul 1999 | A |
5929335 | Carter | Jul 1999 | A |
5930741 | Kramer | Jul 1999 | A |
5936523 | West | Aug 1999 | A |
5946643 | Zakutin | Aug 1999 | A |
5947917 | Carte et al. | Sep 1999 | A |
5952992 | Helms | Sep 1999 | A |
5955667 | Fyfe | Sep 1999 | A |
5959568 | Woolley | Sep 1999 | A |
5960380 | Flentov et al. | Sep 1999 | A |
5963523 | Kayama et al. | Oct 1999 | A |
5963891 | Walker et al. | Oct 1999 | A |
5976083 | Richardson et al. | Nov 1999 | A |
5977877 | McCulloch et al. | Nov 1999 | A |
5978972 | Stewart et al. | Nov 1999 | A |
5984842 | Chu | Nov 1999 | A |
6002982 | Fry | Dec 1999 | A |
6006274 | Hawkins et al. | Dec 1999 | A |
6009237 | Hirabayashi et al. | Dec 1999 | A |
6009629 | Gnepf et al. | Jan 2000 | A |
6011491 | Goetzl | Jan 2000 | A |
6011585 | Anderson | Jan 2000 | A |
6013007 | Root et al. | Jan 2000 | A |
6018677 | Vidrine et al. | Jan 2000 | A |
6018705 | Gaudet et al. | Jan 2000 | A |
6020851 | Busack | Feb 2000 | A |
6028625 | Cannon | Feb 2000 | A |
6028627 | Helmsderfer | Feb 2000 | A |
6032084 | Anderson et al. | Feb 2000 | A |
6032108 | Seiple et al. | Feb 2000 | A |
6032530 | Hock | Mar 2000 | A |
6041023 | Lakhansingh | Mar 2000 | A |
6043747 | Altenhofen | Mar 2000 | A |
6045364 | Dugan et al. | Apr 2000 | A |
6052654 | Gaudet et al. | Apr 2000 | A |
6057756 | Engellenner | May 2000 | A |
6059576 | Brann | May 2000 | A |
6073086 | Marinelli | Jun 2000 | A |
6074271 | Derrah | Jun 2000 | A |
6075443 | Schepps et al. | Jun 2000 | A |
6091342 | Janesch et al. | Jul 2000 | A |
6108426 | Stortz | Aug 2000 | A |
6111541 | Karmel | Aug 2000 | A |
6111571 | Summers | Aug 2000 | A |
6122340 | Darley et al. | Sep 2000 | A |
6122959 | Hoshal et al. | Sep 2000 | A |
6122960 | Hutchings et al. | Sep 2000 | A |
6125686 | Haan et al. | Oct 2000 | A |
6127931 | Mohr | Oct 2000 | A |
6145389 | Ebeling et al. | Nov 2000 | A |
6148271 | Marinelli | Nov 2000 | A |
6151647 | Sarat | Nov 2000 | A |
6157898 | Marinelli | Dec 2000 | A |
6160254 | Zimmerman et al. | Dec 2000 | A |
6161944 | Leman | Dec 2000 | A |
6163021 | Mickelson | Dec 2000 | A |
6167356 | Squadron et al. | Dec 2000 | A |
6172948 | Keller et al. | Jan 2001 | B1 |
6179432 | Zhang et al. | Jan 2001 | B1 |
6183425 | Whalen et al. | Feb 2001 | B1 |
6191939 | Burnett | Feb 2001 | B1 |
6196932 | Marsh et al. | Mar 2001 | B1 |
6204813 | Wadell et al. | Mar 2001 | B1 |
6208044 | Viswanadham et al. | Mar 2001 | B1 |
6216131 | Liu et al. | Apr 2001 | B1 |
6217183 | Shipman | Apr 2001 | B1 |
6226622 | Dabbiere | May 2001 | B1 |
6238338 | DeLuca et al. | May 2001 | B1 |
6245002 | Belikov | Jun 2001 | B1 |
6248946 | Dwek | Jun 2001 | B1 |
6249487 | Yano et al. | Jun 2001 | B1 |
6254513 | Takenaka et al. | Jul 2001 | B1 |
6263279 | Bianco et al. | Jul 2001 | B1 |
6266623 | Vock et al. | Jul 2001 | B1 |
6295541 | Bodnar et al. | Sep 2001 | B1 |
6298314 | Blackadar et al. | Oct 2001 | B1 |
6305221 | Hutchings | Oct 2001 | B1 |
6332175 | Birrell et al. | Dec 2001 | B1 |
6336365 | Blackadar et al. | Jan 2002 | B1 |
6336727 | Kim | Jan 2002 | B1 |
6341316 | Kloba et al. | Jan 2002 | B1 |
6356856 | Damen et al. | Mar 2002 | B1 |
6357147 | Darley et al. | Mar 2002 | B1 |
6360597 | Hubbard, Jr. | Mar 2002 | B1 |
6377530 | Burrows | Apr 2002 | B1 |
6380597 | Gudesen et al. | Apr 2002 | B1 |
6385473 | Haines et al. | May 2002 | B1 |
6436052 | Nikolic et al. | Aug 2002 | B1 |
6441747 | Khair et al. | Aug 2002 | B1 |
6452610 | Reinhardt et al. | Sep 2002 | B1 |
6456261 | Zhang | Sep 2002 | B1 |
6459881 | Hoder et al. | Oct 2002 | B1 |
6467924 | Shipman | Oct 2002 | B2 |
6493652 | Ohlenbusch et al. | Dec 2002 | B1 |
6498994 | Vock et al. | Dec 2002 | B2 |
6501393 | Richards et al. | Dec 2002 | B1 |
6504483 | Richards et al. | Jan 2003 | B1 |
6516284 | Flentov et al. | Feb 2003 | B2 |
6527711 | Stivoric | Mar 2003 | B1 |
6529131 | Wentworth | Mar 2003 | B2 |
6531982 | White et al. | Mar 2003 | B1 |
6536139 | Darley et al. | Mar 2003 | B2 |
6539336 | Vock et al. | Mar 2003 | B1 |
6549497 | Miyamoto et al. | Apr 2003 | B2 |
6560903 | Darley | May 2003 | B1 |
6563417 | Shaw | May 2003 | B1 |
6570526 | Noller et al. | May 2003 | B1 |
6587403 | Keller et al. | Jul 2003 | B1 |
6587404 | Keller et al. | Jul 2003 | B1 |
6595929 | Stivoric | Jul 2003 | B2 |
6600418 | Francis et al. | Jul 2003 | B2 |
6605038 | Teller | Aug 2003 | B1 |
6611782 | Wooster | Aug 2003 | B1 |
6611789 | Darley | Aug 2003 | B1 |
6617962 | Horwitz et al. | Sep 2003 | B1 |
6619835 | Kita | Sep 2003 | B2 |
6621768 | Keller et al. | Sep 2003 | B1 |
6623427 | Mandigo | Sep 2003 | B2 |
6633743 | Berlinsky | Oct 2003 | B1 |
6643608 | Hershey et al. | Nov 2003 | B1 |
6714121 | Moore | Mar 2004 | B1 |
6731312 | Robbin | May 2004 | B2 |
6735630 | Gelvin et al. | May 2004 | B1 |
6748902 | Boesch et al. | Jun 2004 | B1 |
6760536 | Amir et al. | Jul 2004 | B1 |
6762741 | Weindorf | Jul 2004 | B2 |
6772331 | Hind et al. | Aug 2004 | B1 |
6794566 | Pachet | Sep 2004 | B2 |
6799226 | Robbin et al. | Sep 2004 | B1 |
6801964 | Mahdavi | Oct 2004 | B1 |
6813586 | Vock et al. | Nov 2004 | B1 |
6825777 | Vock et al. | Nov 2004 | B2 |
6837827 | Lee et al. | Jan 2005 | B1 |
6856934 | Vock et al. | Feb 2005 | B2 |
6870529 | Davis | Mar 2005 | B1 |
6871063 | Schiffer | Mar 2005 | B1 |
6876947 | Darley et al. | Apr 2005 | B1 |
6882955 | Ohlenbusch et al. | Apr 2005 | B1 |
6883694 | Abelow | Apr 2005 | B2 |
6885971 | Vock et al. | Apr 2005 | B2 |
6898550 | Blackadar et al. | May 2005 | B1 |
6900732 | Richards | May 2005 | B2 |
6911971 | Suzuki et al. | Jun 2005 | B2 |
6914551 | Vidal | Jul 2005 | B2 |
6918677 | Shipman | Jul 2005 | B2 |
6934812 | Robbin et al. | Aug 2005 | B1 |
6950087 | Knox et al. | Sep 2005 | B2 |
6959259 | Vock et al. | Oct 2005 | B2 |
7009517 | Wood | Mar 2006 | B2 |
7042360 | Light et al. | May 2006 | B2 |
7046230 | Zadesky | May 2006 | B2 |
7054784 | Flentov et al. | May 2006 | B2 |
7062225 | White | Jun 2006 | B2 |
7064669 | Light et al. | Jun 2006 | B2 |
7072789 | Vock et al. | Jul 2006 | B2 |
7084856 | Huppi | Aug 2006 | B2 |
7084921 | Ogawa | Aug 2006 | B1 |
7092846 | Vock et al. | Aug 2006 | B2 |
7146437 | Robbin et al. | Dec 2006 | B2 |
7174130 | Kurisko et al. | Feb 2007 | B2 |
7174277 | Vock et al. | Feb 2007 | B2 |
7234026 | Robbin et al. | Jun 2007 | B2 |
7254516 | Case et al. | Aug 2007 | B2 |
7559877 | Parks et al. | Jul 2009 | B2 |
20010022828 | Pyles | Sep 2001 | A1 |
20010033244 | Harris et al. | Oct 2001 | A1 |
20010041021 | Boyle et al. | Nov 2001 | A1 |
20010042107 | Palm | Nov 2001 | A1 |
20010049890 | Hirsch et al. | Dec 2001 | A1 |
20020002413 | Tokue | Jan 2002 | A1 |
20020013784 | Swanson | Jan 2002 | A1 |
20020022551 | Watterson et al. | Feb 2002 | A1 |
20020045961 | Gibbs et al. | Apr 2002 | A1 |
20020046315 | Miller et al. | Apr 2002 | A1 |
20020055934 | Lipscomb et al. | May 2002 | A1 |
20020090912 | Cannon et al. | Jul 2002 | A1 |
20020116082 | Gudorf | Aug 2002 | A1 |
20020152045 | Dowling et al. | Oct 2002 | A1 |
20020161865 | Nguyen | Oct 2002 | A1 |
20020173273 | Spurgat et al. | Nov 2002 | A1 |
20020189426 | Hirade et al. | Dec 2002 | A1 |
20030016844 | Numaoka | Jan 2003 | A1 |
20030037254 | Fischer et al. | Feb 2003 | A1 |
20030046434 | Flanagin et al. | Mar 2003 | A1 |
20030065805 | Barnes | Apr 2003 | A1 |
20030074457 | Kluth | Apr 2003 | A1 |
20030076301 | Tsuk et al. | Apr 2003 | A1 |
20030079038 | Robbin et al. | Apr 2003 | A1 |
20030095096 | Robbin et al. | May 2003 | A1 |
20030097379 | Ireton | May 2003 | A1 |
20030133694 | Yeo | Jul 2003 | A1 |
20030163287 | Vock et al. | Aug 2003 | A1 |
20030167318 | Robbin et al. | Sep 2003 | A1 |
20030229490 | Etter | Dec 2003 | A1 |
20040001395 | Keller et al. | Jan 2004 | A1 |
20040001396 | Keller et al. | Jan 2004 | A1 |
20040012556 | Yong et al. | Jan 2004 | A1 |
20040055446 | Robbin et al. | Mar 2004 | A1 |
20040069122 | Wilson | Apr 2004 | A1 |
20040076086 | Keller et al. | Apr 2004 | A1 |
20040086120 | Akins, III et al. | May 2004 | A1 |
20040094018 | Ueshima et al. | May 2004 | A1 |
20040104845 | McCarthy | Jun 2004 | A1 |
20040198436 | Alden | Oct 2004 | A1 |
20040224638 | Fadell et al. | Nov 2004 | A1 |
20040267825 | Novak et al. | Dec 2004 | A1 |
20050015254 | Beaman | Jan 2005 | A1 |
20050027910 | Barrett et al. | Feb 2005 | A1 |
20050080566 | Vock et al. | Apr 2005 | A1 |
20050088275 | Valoteau et al. | Apr 2005 | A1 |
20050152294 | Yu et al. | Jul 2005 | A1 |
20050166153 | Eytchison et al. | Jul 2005 | A1 |
20050177929 | Greenwald et al. | Aug 2005 | A1 |
20050245839 | Stivoric et al. | Nov 2005 | A1 |
20050266798 | Moloney et al. | Dec 2005 | A1 |
20050266961 | Shum et al. | Dec 2005 | A1 |
20060013414 | Shih | Jan 2006 | A1 |
20060068760 | Hameed et al. | Mar 2006 | A1 |
20060097847 | Bervoets et al. | May 2006 | A1 |
20060152377 | Beebe et al. | Jul 2006 | A1 |
20060190577 | Yamada | Aug 2006 | A1 |
20060221788 | Lindahl et al. | Oct 2006 | A1 |
20060265503 | Jones et al. | Nov 2006 | A1 |
20070011919 | Case, Jr. | Jan 2007 | A1 |
20070021269 | Shum | Jan 2007 | A1 |
20070028009 | Robbin et al. | Feb 2007 | A1 |
20070032195 | Kurisko et al. | Feb 2007 | A1 |
20070124679 | Jeong et al. | May 2007 | A1 |
20080125288 | Case | May 2008 | A1 |
Number | Date | Country |
---|---|---|
43 34 773 | Apr 1994 | DE |
44 45 023 | Jun 1996 | DE |
10325805 | Jan 2005 | DE |
0 127 139 | May 1984 | EP |
0336782 | Oct 1989 | EP |
0578604 | Jan 1994 | EP |
0 757 437 | Feb 1997 | EP |
0 863 469 | Sep 1998 | EP |
0 917 077 | May 1999 | EP |
0917893 | May 1999 | EP |
0 982 732 | Mar 2000 | EP |
1 028 425 | Aug 2000 | EP |
1028426 | Aug 2000 | EP |
1 076 302 | Feb 2001 | EP |
1 289 197 | Mar 2003 | EP |
1 455 477 | Sep 2004 | EP |
1536612 | Jun 2005 | EP |
1566948 | Aug 2005 | EP |
1567238 | May 1980 | GB |
2137363 | Oct 1984 | GB |
2384399 | Jul 2003 | GB |
59-023610 | Feb 1984 | JP |
03-152469 | Jun 1991 | JP |
2000122044 | Apr 2000 | JP |
2000-224099 | Aug 2000 | JP |
2000-299834 | Oct 2000 | JP |
2001-312338 | Nov 2001 | JP |
2001321202 | Nov 2001 | JP |
2002-076977 | Mar 2002 | JP |
2002101908 | Apr 2002 | JP |
WO 0133569 | Jun 1995 | WO |
WO 9516950 | Jun 1995 | WO |
9817032 | Apr 1998 | WO |
WO 9806466 | Dec 1998 | WO |
WO 9854581 | Dec 1998 | WO |
WO 0022820 | Apr 2000 | WO |
WO 0051259 | Aug 2000 | WO |
WO 0078170 | Dec 2000 | WO |
WO 0101706 | Apr 2001 | WO |
WO 0165413 | Sep 2001 | WO |
WO 0167753 | Sep 2001 | WO |
WO 0225610 | Mar 2002 | WO |
WO 03023786 | Mar 2003 | WO |
WO 03067202 | Aug 2003 | WO |
2004061850 | Jul 2004 | WO |
WO 2004055637 | Jul 2004 | WO |
WO 2004084413 | Sep 2004 | WO |
WO 2005031737 | Apr 2005 | WO |
2005048644 | May 2005 | WO |
WO 2005048644 | May 2005 | WO |
WO 2005008505 | Jul 2005 | WO |
2005109781 | Nov 2005 | WO |
2006071364 | Jun 2006 | WO |
WO 2006094380 | Sep 2006 | WO |
WO 2007022421 | Feb 2007 | WO |
Number | Date | Country | |
---|---|---|---|
20080057890 A1 | Mar 2008 | US |