Dual key electronic connector

Information

  • Patent Grant
  • 8271705
  • Patent Number
    8,271,705
  • Date Filed
    Thursday, November 3, 2011
    12 years ago
  • Date Issued
    Tuesday, September 18, 2012
    11 years ago
Abstract
A connector interface system for a communication device is disclosed. The interface includes a docking connector. The docking connector includes first make/last break contacts that minimize internal damage to the internal electronics. The docking connector also includes specific keying arrangement to prevent noncompliant connectors from being plugged in, and thereby minimizes potential damage to the multi-communication device. The connector interface system also includes a remote connector which provides for the ability to output audio, input audio, provides I/O serial protocol, and to provide an output video. Embodiments of the present invention allow for a standard headphone cable to be plugged in but also for special remote control cables, microphone cables, video cables could be utilized in such a system. The connector interface system also includes a serial protocol to control device features. These controls help a user sort and search for data more efficiently within the device.
Description
FIELD OF THE INVENTION

The present invention relates generally to multi-communication devices and more particularly to a connector interface system for such devices.


BACKGROUND OF THE INVENTION

Multi-communication devices are utilized in a variety of environments. What is meant by a multi-communication device is a device such as MP3 player, or other type of device that receives video, audio, and a variety of other digital data and can provide an output of the data. As these devices proliferate, a connector interface specification becomes more important, and also insuring that a particular multi-communications device interfaces appropriately with the appropriate external devices becomes more important.


In a typical connector interface, there is a docking connector that allows for the docking of the multi-communications device to a docking station for another type of communication for the device. A multi-communication device also typically includes a remote connector with the ability to output audio. As more multi-media content becomes available (i.e., digital video graphics, etc.) it is desirable to have a multi-media device which can effectively input and output such data.


Finally, such an interface typically has some sort of protocol to control device features from an external device and it also is desirable for the protocol to help the user sort and search for data faster and in an efficient manner. Heretofore, there is no device that includes features that overcome many of the above-stated problems. What is desired is a connector interface system which is utilized in such a device to address all the above-identified issues. The present invention addresses such a need.


SUMMARY OF THE INVENTION

A connector interface system for a communication device is disclosed. The interface includes a docking connector. The docking connector includes first make/last break contacts that minimize internal damage to the internal electronics. The docking connector also includes specific keying arrangement to prevent noncompliant connectors from being plugged in, and thereby minimizes potential damage to the multi-communication device. The connector interface system also includes a remote connector which provides for the ability to output audio, input audio, and output video using an I/O serial protocol. Heretofore, all these features have not been implemented in a connector. Therefore, this would allow for a standard headphone cable to be plugged in but also for special remote control cables, microphone cables, video cables to be utilized in such a system. The connector interface system also includes a serial protocol to control device features. These controls help a user sort and search for data more efficiently within the device.





BRIEF DESCRIPTION OF THE DRAWINGS


FIGS. 1A and 1B illustrate a docking connector in accordance with the present invention.



FIGS. 2A-2C illustrate the remote connector in accordance with the present invention.



FIG. 3A illustrates the connection pin designations for the docking connector.



FIG. 3B illustrates the connection pin designations for the remote connector.



FIG. 4A illustrates the Firewire connector interface.



FIG. 4B illustrates the USB connector interface.



FIG. 4C illustrates a reference schematic diagram for accessory detect and identify system for detecting and identifying accessories for the docking connector.



FIG. 4D is a reference schematic of an electret microphone that is within the remote connector.





DETAILED DESCRIPTION

The present invention relates generally to multi-communication devices and more particularly to a connector interface system for such devices. The following description is presented to enable one of ordinary skill in the art to make and use the invention and is provided in the context of a patent application and its requirements. Various modifications to the preferred embodiment and the generic principles and features described herein will be readily apparent to those skilled in the art. Thus, the present invention is not intended to be limited to the embodiment shown but is to be accorded the widest scope consistent with the principles and features described herein.


Connector System Overview


To describe the features of the connector system in accordance with the present invention in more detail, refer now to the following description in conjunction with the accompanying drawings.


Docking Connector



FIGS. 1A and 1B illustrate a docking connector 100 in accordance with the present invention. Referring first to FIG. 1A, the keying features 102 are of a custom length 104. In addition, a specific key arrangement where one set of keys are separated by one length are at the bottom and another set of keys are separated by another length at the top of the connector is used. The use of this key arrangement prevents noncompliant connectors from being plugged in and causing potential damage to the device. The connector for power utilizes a Firewire specification for power. The connector includes a first make/last break contact to implement this scheme. FIG. 1B illustrates the first make/last break contact 202 and also illustrates a ground pin and a power pin related to providing an appropriate first mate/last break contact. In this example, the ground pin 204 is longer than the power pin 206. Therefore, the ground pin 204 would contact its mating pin in the docking accessory before the power pin 206. Therefore internal electrical damage of the electronics of the device is minimized.


In addition, a connector interface system in accordance with the present invention uses both USB and Firewire interfaces as part of the same docking connector alignment, thereby making the design more compatible with different types of interfaces, as will be discussed in detail hereinafter. In so doing, more remote systems and devices can interface with the multi-communication device.


Remote Connector


The connection interface system also includes a remote connector which provides for the ability to output audio, input audio, and output video using an I/O serial protocol. FIG. 2A is a front and top view of a remote connector 200 in accordance with the present invention. As is seen, the remote connector 200 includes a top headphone receptacle 202, as well as, a second receptacle 204 for remote devices. FIG. 2B illustrates a plug 300 to be utilized in the remote connector. The plug 300 allows the features to be provided via the remote connector. FIG. 2C illustrates the plug 300 inserted into the remote connector 200. Heretofore, all these features have not been implemented in a remote connector. Therefore, a standard headphone cable can be plugged in but also special remote control cables, microphone cables, video cables could be utilized with the remote connector.


Serial Protocol


The connector interface system also includes a serial protocol. The protocol is utilized to allow external devices to control the multi-communication device. These controls help a user sort and display for data more efficiently utilizing the device. A representation list of controls includes, but are not limited to:


Next album


Previous album


Next chapter


Previous chapter


Next play list


Previous play list


Shuffle setting advance


Repeat setting advance


Backlight for 30 seconds


Begin fast forward


Begin rewind


To describe the features of the connector interface system in more detail, please find below a functional description of the docking connector, remote connector and a serial protocol in accordance with the present invention.


Docking and Remote Connector Specifications


For an example of the connector pin designations for both the docking connector and for the remote connector for a multi-communication device such as an iPod device by Apple Inc., refer now to FIGS. 3A and 3B. FIG. 3A illustrates the connector pin designations for the docking connector. FIG. 3B illustrates the connection pin designations for the remote connector.


Docking Connector Specifications



FIG. 4A illustrates a typical FireWire connector interface for the docking connector:


FireWire Power:


a) 8V-30V DC IN


b) 10 W Max


FireWire:


a) Designed to IEEE 1394 A Spec (400 Mb/s)



FIG. 4B illustrates the USB connector interface.


USB 2.0:


a) Designed to USB 2.0 High Speed Spec


b) The USB Power (pin 8 on the 30-pin connector) is not used for powering device; only used to detect a USB host connection.



FIG. 4C illustrates a reference schematic diagram for accessory detect and identify system for detecting and identifying accessories for the docking connector. The system comprises:


a) A simple resistor to ground allows the device to determine what has been plugged into docking connector. There is an internal pullup on Accessory Identify.


b) Two pins required (Accessory Identify & Accessory Detect)


Serial Protocol Communication:


a) Two pins are used to communicate to and from device (Rx & Tx)


b) Input & Output (0V=Low; 3.3V=High)


c) A device with an identity resistor (ID #13) is a serial dock accessory.


A device coupled to the docking connector allows for a standard serial protocol to be utilized. Attaching a serial dock accessory makes any top-attached (remote connector) accessories inactive.


Line Level Input (Left & Right):


a) Stereo audio input b) Input Level 1V RMS (max)


a) Chassis ground is tied to specified pins


b) Digital ground should not be tied to Audio Return


Remote Connector Specifications


Audio Out:


a) Stereo Output per channel volume controlled by device


Mono Mic In:


a) Mono mic in through Left channel


b) Filtered electret power supplied by internal device



FIG. 4D is a reference schematic of an electret microphone that is within the remote connector.


Serial Protocol Communication:


a) Two pins used to communicate to and from device (Rx & Tx)


b) Input & Output (0V=Low, 3.3V=High)


Serial Protocol


Protocol Generalities


As previously mentioned, another feature of the present invention is the use of a serial protocol for allowing features to be implemented for remote devices. In a preferred embodiment, the protocol builds upon a signaling protocol, such as the RS-232 serial specification. However, the signaling levels are nonstandard. In true RS-232, a mark is −7V and a space is 7V. In this protocol, a mark is 3.3V and a space is 0V. The signaling rate for this protocol is 19,200 bps. All signaling is at 8 bits data, no parity and one stop bit (8-N-1).


This protocol is to be used in both directions of a link. Every device is encouraged to implement both sending and receiving capabilities. It is be possible to determine the direction (host to device or device to host) of a packet from its contents only. This means that no packet is valid for sending from both the host and device.


All devices must be able to handle variable-length packets. For example, even though an identify packet currently has no defined data, a device must be able to understand an identify packet with data and should respond to the best of its ability. It must at least not lose sync to the packet signaling.


Lingo Specifications
















Lingo
ID









General
0x00



Microphone
0x01



Simple Remote
0x02



Display Remote
0x03



RF transmitter
0x05










The general lingo is shared for housekeeping commands across all devices. The microphone lingo is used by the remote connector on the multi-communication device. The simple remote lingo is used by a standard in-line remote control. The display remote lingo is reserved for a device with similar functionality to the standard remote but with a display for status.


General Lingo Specification

















Command
ID
Data Length









Request identify
0x00
0x00 



Identify
0x01
0x01+










The host may send a request identify to the device to ask the device to reidentify itself.


The device sends an identify packet to identify itself. At this time multifunction (combo) devices are not supported. The identify data payload is thus the command ID 0x01 followed by a single byte of the same value as the lingo specification of the functionality the device implements unless specified otherwise. The identify packet returned in response to a request identify packet does not need to have the extra sync bytes and delays used during the startup process.


Simple Remote Lingo Specification

















Command
ID
Data Length









Buttons status
0x00
0x00+










A simple remote device sends a buttons status command to indicate an updated status of which buttons are held down. The data of the packet is a number of bytes indicating which buttons are currently held down. The bytes are made up by ORing the masks of the buttons together. The device will send a 0x00 in data (or no data) to indicate all buttons are released. While any buttons are held down the device should repeat this packet on a predetermined interval. If no packet of this sort is received by the host for 200 ms the host may assume a packet was lost and go to “all buttons up” mode.


A representative simple remote button map is shown below:


Simple Remote Button Map

















Button
Number
Byte No, Mask




















Play/Pause
0
0, 0x01



Volume Up
1
0, 0x02



Volume Down
2
0, 0x04



Next Track
3
0, 0x08



Previous Track
4
0, 0x10



Next Album
5
0, 0x20



Previous Album
6
0, 0x40



Stop
7
0, 0x80



Play/Resume
8
1, 0x01



Pause
9
1, 0x02



Mute toggle
10
1, 0x04



Next Chapter
11
1, 0x08



Previous Chapter
12
1, 0x10



Next Playlist
13
1, 0x20



Previous Playlist
14
1, 0x40



Shuffle setting advance
15
1, 0x80



Repeat setting advance
16
2, 0x01



Power On
17
2, 0x02



Power Off
18
2, 0x04



Backlight for 30 seconds
19
2, 0x08



Begin FF
20
2, 0x10



Begin REW
22
2, 0x20










The use of the button remote map allows for features that heretofore have not been utilized in multi-communication devices such as an iPod device manufactured by Apple Inc.


A connector interface system for a communication device is disclosed. The interface includes a docking connector. The docking connector includes first make/last break contacts that minimize internal damage to the internal electronics. The docking connector also includes specific keying arrangement to prevent noncompliant connectors from being plugged in, and thereby minimizes potential damage to the multi-communication device. The remote connector provides for the ability to output audio, input audio, and output video using an I/O serial protocol. The connector interface also includes a serial protocol to control device features. These controls help a user sort and search for data more efficiently within the device.


Although the present invention has been described in accordance with the embodiments shown, one of ordinary skill in the art will readily recognize that there could be variations to the embodiments and those variations would be within the spirit and scope of the present invention. Accordingly, many modifications may be made by one of ordinary skill in the art without departing from the spirit and scope of the appended claims.

Claims
  • 1. An electronic connector comprising: a connector housing designed to accommodate at least 30 contacts spaced apart in sequentially numbered contact locations including: (i) ground contact locations 1, 15 and 30 designated for ground, (ii) a plurality of digital contact locations including first and second USB data contact locations 4 and 6 designated for USB data signals and contact locations 3, 5 and 7 interleaved around the first and second USB data contact locations and designated for digital signals other than USB data signals, (iii) analog contact locations 27 and 28 designated for left and right audio signals, (iv) a plurality of contacts designated for power including contact location 13 designated for accessory power and contact location 8; anda keying arrangement including first and second sets of keys, wherein the first set of keys is formed on a first side of the housing and is spaced apart by a first length and the second set of keys is formed on a second side of the housing, opposite the first side, and is spaced apart by a second length different than the first length.
  • 2. The electronic connector set forth in claim 1 wherein the sequentially numbered contact locations further include ground contact locations 2, 16 and 29 designated for ground.
  • 3. The electronic connector set forth in claim 1 wherein the sequentially numbered contact locations further include an accessory detect contact location at location 20 designated for an accessory detect signal.
  • 4. The electronic connector set forth in claim 1 wherein the sequentially numbered contact locations further include an accessory identify contact at location 10 designated for an accessory identify signal.
  • 5. The electronic connector set forth in claim 1 wherein the sequentially numbered contact locations further include serial communication contact locations 17 and 18 designated for transmitting and receiving digital signals using a serial protocol.
  • 6. The electronic connector set forth in claim 1 wherein the contact locations designated for USB data signals are designated for a USB D+ signal and a second USB D− signal.
  • 7. The electronic connector set forth in claim 1 wherein the sequentially numbered contact locations consists of thirty contact locations arranged in a single row.
  • 8. The electronic connector of claim 1 wherein the plurality of contacts designated for power further includes contact locations 11 and 12 designated for charger input power.
  • 9. The electronic connector set forth in claim 4 wherein contact locations 3, 5 and 7 are designated for Firewire signals.
  • 10. The electronic connector of claim 8 wherein contact location 13 is designated to carry power at a first power level and contact locations 11 and 12 are designated to carry power at a second power level that is higher than the first power level.
  • 11. The electronic connector of claim 10 wherein the first power level is 3.3 volts.
  • 12. The electronic connector of claim 11 wherein the second power level is between 8-30 volts.
  • 13. An electronic connector comprising: a connector housing designed to accommodate at least 30 contacts spaced apart in a single row of sequentially numbered contact locations including: (i) ground contact locations 1, 15 and 30 designated for ground, (ii) a plurality of digital contact locations including first and second USB data contact locations 4 and 6 designated for USB data signals and contact locations 3, 5 and 7 interleaved around the first and second USB data contact locations designated for digital signals other than USB data signals, (iii) analog contact locations 27 and 28 designated for left and right audio signals, (iv) a plurality of contacts designated for power including contact location 13 designated for accessory power and contact location 8, (v) an accessory identify contact at location 10 designated for an accessory identify signal, (vi) an accessory detect contact location at location 20 designated for an accessory detect signal, and (vii) serial communication contact locations 17 and 18 designated for transmitting and receiving digital signals using a serial protocol; anda keying arrangement including first and second sets of keys, wherein the first set of keys is formed on a first side of the housing and is spaced apart by a first length and the second set of keys is formed on a second side of the housing, opposite the first side, and is spaced apart by a second length different than the first length.
  • 14. The electronic connector set forth in claim 13 wherein the sequentially numbered contact locations further include ground contact locations 2, 16 and 29 designated for ground.
  • 15. The electronic connector set forth in claim 13 wherein contact locations 3, 5 and 7 are designated for Firewire signals.
  • 16. The electronic connector set forth in claim 13 wherein the sequentially numbered contact locations consists of thirty contact locations.
  • 17. The electronic connector of claim 16 wherein the plurality of contacts designated for power further includes contact locations 11 and 12 designated for charger input power.
  • 18. The electronic connector of claim 17 wherein contact location 13 is designated to carry power at a first power level and contact locations 11 and 12 are designated to carry power at a second power level that is higher than the first power level.
  • 19. The electronic connector of claim 18 wherein the first power level is 3.3 volts.
  • 20. The electronic connector of claim 19 wherein the second power level is between 8-30 volts.
CROSS-REFERENCES TO RELATED APPLICATIONS

This application is continuation of U.S. patent application Ser. No. 12/967,859, filed Dec. 14, 2010; which claims priority from and is a continuation of U.S. Non-Provisional application Ser. No. 12/210,022, Sep. 12, 2008; which is a continuation of U.S. Non-Provisional application Ser. No. 10/833,689, Apr. 27, 2004. The entire contents of each are incorporated herein by reference for all purposes. The contents of the following related applications are herein incorporated by reference in their entirety for all purposes: (1) U.S. application Ser. No. 12/209,962, now U.S. Pat. No. 7,660,929, issued Feb. 9, 2010, entitled “CONNECTOR INTERFACE SYSTEM FOR A MULTI-COMMUNICATION DEVICE” and filed concurrently with the present application; (2) U.S. application Ser. No. 12/209,970, now U.S. Pat. No. 7,587,540, issued Sep. 8, 2009, entitled “TECHNIQUES FOR TRANSFERRING STATUS INFORMATION BETWEEN AN ACCESSORY AND A MULTI-COMMUNICATION DEVICE” and filed concurrently with the present application; and (3) U.S. application Ser. No. 12/209,993, now U.S. Pat. No. 7,702,833, issued Apr. 20, 2010, entitled “TECHNIQUES FOR TRANSFERRING INFORMATION BETWEEN AN ACCESSORY AND A MULTI-COMMUNICATION DEVICE” and filed concurrently with the present application.

US Referenced Citations (142)
Number Name Date Kind
4850899 Maynard Jul 1989 A
4874316 Kamon et al. Oct 1989 A
4972470 Farago Nov 1990 A
5055069 Townsend et al. Oct 1991 A
5077552 Abbate Dec 1991 A
5080603 Mouissie Jan 1992 A
5104243 Harding Apr 1992 A
5108313 Adams Apr 1992 A
D333460 Huang Feb 1993 S
5186646 Pederson Feb 1993 A
5277624 Champion Jan 1994 A
5357608 Bartow et al. Oct 1994 A
5379057 Clough et al. Jan 1995 A
5438678 Smith Aug 1995 A
5457784 Wells et al. Oct 1995 A
5568525 de Nijs et al. Oct 1996 A
5574947 Massa Nov 1996 A
5586893 Mosquera Dec 1996 A
5618045 Kagan et al. Apr 1997 A
5660558 Osanai et al. Aug 1997 A
5675362 Clough et al. Oct 1997 A
5737364 Cohen et al. Apr 1998 A
5830001 Kinoshita Nov 1998 A
5832244 Jolley Nov 1998 A
5901049 Schmidt et al. May 1999 A
5941963 Charles et al. Aug 1999 A
5975957 Noda et al. Nov 1999 A
5983073 Ditzik Nov 1999 A
6030229 Tsutsui Feb 2000 A
6053773 Wu Apr 2000 A
6073201 Jolley et al. Jun 2000 A
6139373 Ward et al. Oct 2000 A
6154798 Lin et al. Nov 2000 A
6183302 Daikuhara et al. Feb 2001 B1
6203345 Roque et al. Mar 2001 B1
6206480 Thompson Mar 2001 B1
6267623 Hisamatsu Jul 2001 B1
6304764 Pan Oct 2001 B1
6314479 Frederick et al. Nov 2001 B1
6319061 Chen et al. Nov 2001 B1
6322396 Kuan Nov 2001 B1
6344727 Desai et al. Feb 2002 B1
6353169 Juszkiewicz et al. Mar 2002 B1
6354713 Leifer et al. Mar 2002 B1
6431915 Ko Aug 2002 B1
6454592 Takagi Sep 2002 B2
6461173 Mizuno et al. Oct 2002 B1
6464542 Lee Oct 2002 B1
6468110 Fujino et al. Oct 2002 B2
6478603 Wu Nov 2002 B1
6480378 Chang Nov 2002 B2
6485328 Wu Nov 2002 B1
6523124 Lunsford Feb 2003 B1
6524119 Kato et al. Feb 2003 B2
6549401 Lin et al. Apr 2003 B2
6552567 Boles et al. Apr 2003 B1
6561815 Schmidt May 2003 B1
6570756 Alfonso et al. May 2003 B2
6577877 Charlier et al. Jun 2003 B1
6589076 Davis et al. Jul 2003 B1
6591085 Grady Jul 2003 B1
6608264 Fouladpour Aug 2003 B1
6616473 Kamata et al. Sep 2003 B2
6631098 Chang et al. Oct 2003 B2
6633932 Bork et al. Oct 2003 B1
6653813 Khatri Nov 2003 B2
6658516 Yao Dec 2003 B2
6663420 Xiao Dec 2003 B1
6674995 Meyers et al. Jan 2004 B1
6728546 Peterson et al. Apr 2004 B1
6733310 Fujikura et al. May 2004 B2
6754468 Sieben et al. Jun 2004 B1
6766175 Uchiyama Jul 2004 B2
6776626 Huang et al. Aug 2004 B2
6776665 Huang Aug 2004 B2
6777660 Lee Aug 2004 B1
6782239 Johnson et al. Aug 2004 B2
6798647 Dickie Sep 2004 B2
6799226 Robbin et al. Sep 2004 B1
6813528 Yang Nov 2004 B1
6816376 Bright et al. Nov 2004 B2
6856506 Doherty et al. Feb 2005 B2
6859854 Kwong Feb 2005 B2
6959205 Yambe Oct 2005 B2
6973516 Athanas et al. Dec 2005 B1
6973658 Nguyen Dec 2005 B2
6988897 Belongia et al. Jan 2006 B2
6991483 Milan et al. Jan 2006 B1
7004787 Milan Feb 2006 B2
7054963 Betts-LaCroix et al. May 2006 B2
7054965 Bell et al. May 2006 B2
7056153 Watanabe et al. Jun 2006 B2
7107296 Novak et al. Sep 2006 B2
7110755 Shibasaki et al. Sep 2006 B2
7114988 Sato et al. Oct 2006 B2
7149475 Kawamura Dec 2006 B2
7187948 Alden et al. Mar 2007 B2
7284036 Ramaswamy Oct 2007 B2
7293122 Schubert et al. Nov 2007 B1
7298765 Ganton et al. Nov 2007 B2
7390197 Merz Jun 2008 B2
7441062 Novotney et al. Oct 2008 B2
7627343 Fadell et al. Dec 2009 B2
RE41224 Kubota et al. Apr 2010 E
7751853 Fadell et al. Jul 2010 B2
7783070 Fadell et al. Aug 2010 B2
8078776 Novotney et al. Dec 2011 B2
20020002035 Sim et al. Jan 2002 A1
20020006748 Tolmie et al. Jan 2002 A1
20020010759 Hitson et al. Jan 2002 A1
20020032042 Poplawsky et al. Mar 2002 A1
20020065074 Cohn et al. May 2002 A1
20020068610 Anvekar et al. Jun 2002 A1
20020103008 Rahn et al. Aug 2002 A1
20020105861 Leapman Aug 2002 A1
20020115480 Huang Aug 2002 A1
20020132651 Jinnouchi Sep 2002 A1
20020151327 Levitt Oct 2002 A1
20020163780 Christopher Nov 2002 A1
20020173273 Spurgat et al. Nov 2002 A1
20020180803 Kaplan et al. Dec 2002 A1
20030017746 Lee Jan 2003 A1
20030028664 Tan et al. Feb 2003 A1
20030056220 Thornton et al. Mar 2003 A1
20030059022 Nebiker et al. Mar 2003 A1
20030073432 Meade Apr 2003 A1
20030079038 Robbin et al. Apr 2003 A1
20030097379 Ireton May 2003 A1
20030172209 Lui et al. Sep 2003 A1
20030198015 Vogt Oct 2003 A1
20030218445 Behar Nov 2003 A1
20040039860 Mills et al. Feb 2004 A1
20040090998 Chen May 2004 A1
20040151327 Marlow Aug 2004 A1
20040162029 Grady Aug 2004 A1
20050014536 Grady Jan 2005 A1
20060154530 Novotney et al. Jul 2006 A1
20060264114 Novotney et al. Nov 2006 A1
20070161262 Lloyd Jul 2007 A1
20070232098 Danner et al. Oct 2007 A1
20080123285 Fadell et al. May 2008 A1
20080125031 Fadell et al. May 2008 A1
Foreign Referenced Citations (51)
Number Date Country
101 31 299 Jan 2003 DE
1 104 150 May 2001 EP
1104968 Jun 2001 EP
1 168 770 Jan 2002 EP
1 176 783 Jan 2002 EP
2 362 237 Nov 2001 GB
H06-051881 Feb 1994 JP
H07-176351 Jul 1995 JP
H09-311993 Feb 1997 JP
H10-098512 Apr 1998 JP
H10-321302 Dec 1998 JP
H10-334993 Dec 1998 JP
H11-288420 Oct 1999 JP
2000-068006 Mar 2000 JP
2000-214953 Aug 2000 JP
2000-223215 Aug 2000 JP
2000-223216 Aug 2000 JP
2000-223218 Aug 2000 JP
2001-035603 Feb 2001 JP
2001-196133 Jul 2001 JP
2001-230021 Aug 2001 JP
2001-265360 Sep 2001 JP
2001-306114 Nov 2001 JP
2001-332350 Nov 2001 JP
2002-025720 Jan 2002 JP
2002-170643 Jun 2002 JP
2002-203641 Jul 2002 JP
2002-245719 Aug 2002 JP
2002-252566 Sep 2002 JP
2002-342659 Nov 2002 JP
2002-374447 Dec 2002 JP
3090747 Dec 2002 JP
2003-015616 Jan 2003 JP
2003-017165 Jan 2003 JP
2003-031319 Jan 2003 JP
2003-032351 Jan 2003 JP
2003-092638 Mar 2003 JP
2003-274386 Sep 2003 JP
2004-531916 Oct 2004 JP
2002-0015579 Feb 2002 KR
WO 0060450 Oct 2000 WO
WO 0113204 Feb 2001 WO
WO 0117262 Mar 2001 WO
WO 0162004 Aug 2001 WO
WO 0243359 May 2002 WO
WO 0249314 Jun 2002 WO
WO 02075517 Sep 2002 WO
WO 02087205 Oct 2002 WO
WO 02103545 Dec 2002 WO
WO 2004084413 Sep 2004 WO
WO 2004098079 Nov 2004 WO
Related Publications (1)
Number Date Country
20120052745 A1 Mar 2012 US
Continuations (3)
Number Date Country
Parent 12967859 Dec 2010 US
Child 13288876 US
Parent 12210022 Sep 2008 US
Child 12967859 US
Parent 10833689 Apr 2004 US
Child 12210022 US