This invention relates to Peer to Peer connections of processing devices over a network. More particularly, this invention relates to the creation and distribution of decoy content to discourage unauthorized transfers of protected works. Still more particularly, this invention relates to a system where Peer to Peer software in a processing device detects a transfer of a protected work to the processing device and generates decoy data in the received data of the work for storage in the processing device.
There are many so called “Peer to Peer” (P2P) products available for connecting processing devices over a network to share data between the processing devices. The P2P products are typically software that are executed by the processing device to provide a connection between the processing devices. The products allow a user to designate a collection of files that are to be “shared.” That is, these files are made available for retrieval by other processing devices executing the P2P software. The P2P products also allow a user to locate files of interest on another processing system and to retrieve files from the other processing system. Typical P2P products run on top of vastly interconnected and loosely coupled networks. These networks run on top of typical networks like TCP, UDP, ATM, etc.
Intellectual property right holders of a work typically have a right to payment when the work is used. For purposes of the present discussion, a work is anything that is fixed in a tangible medium. Some examples of works include, but are not limited to, audio renderings, video renderings, images, video/audio renderings, and software. An example of an audio rendering include a song and/or other audio track. Examples of video renderings include an animation and/or a video sequence. Examples of an image include a photograph and/or paintings. Examples of audio/video renderings include movies, television shows, and cartoons. Examples of software include word processing programs and video games.
Most works have a property right, such as a copyright associated with a work. Thus, the owner of the property right is entitled to a royalty or other form of compensation for use of the work. For example, an owner of a song copyright, such as a songwriter, is entitled to a royalty for each copy of the recording produced.
Courts today have sometimes found that the transfer of a work over a network constitutes a use of that work and thus a license is required from the copyright holder and some form of payment is typically due.
The files that are transferred over Peer to Peer “P2P” networks often are the embodiment of intellectual property of a work i.e. a copyright protected work. The transfer of files containing protected works is often done without the permission of the owner of the right.
Some copyright holders have taken objection to P2P file transfers and have taken steps to disrupt these transfers. As one example, a right holder might become a peer in one of these networks. This peer will share what appears to be a copy of a desirable work. However, that copy will in fact be defective in some way. The copy might be damaged or might even contain other content that the right holder wishes to convey. Damaged or substitute content is called “decoy” content.
The right holders might take aggressive steps to introduce these damaged files into these P2P networks. The right holders might not act as just one peer on the network, but act as hundreds or thousands, or hundreds of thousands of peers, thus flooding the network with damaged files. This action is called “spoofing.” Their intent is to make the network unreliable for the transmission of their works. Their hope is that an unreliable network will discourage users from transferring these works.
However, as aggressive as this sounds, the approach is not effective. P2P products have become adept at sharing information between peers. When one peer finds that decoy content is being shared by a particular IP address, it alerts other peers and the other peers in turn alert others. The source IP address is quickly eliminated from the network and the spoofer becomes ineffective. Some networks are able to eliminate entire IP address ranges from their scope. Some P2P products use a hash code or other mechanism to verify that the downloaded content is not damaged and reject any work with damaged content.
Thus, there is a need in the art for a method of introducing decoy material into a P2P network that can defeat the detect of the spoofed material in order to allow propagation of the spoofed material through a P2P network to discourage unauthorized transfers over the network of a protected work.
The above and other problems are solved and an advance in the art is made by the decoy data generation and distribution system for a P2P network in accordance with this invention. The main advantage of this invention is that a system is provided in which decoy data is inserted into a file including valid data of a protected work. Thus, the decoy is distributed over the network with identification data of a valid copy of a protected work. This makes the detection and elimination of decoy data from a P2P network harder and encourages authorized transfers of a protected work.
In accordance with this invention, the decoy generation and decoy system may be included in the P2P software being executed by a processing device. The system may be included in the software operating on all processing devices in the P2P network or may be executed by certain processing systems in the network.
The decoy data generation and distribution system operates in the following manner in accordance with this invention. A processing device executing P2P software including the instructions for a system in accordance with this invention connects to a P2P network. The processing device then requests a work from a second processing device or peer on the network. The data for the work is then transferred from the second processing device to the processing device.
When the data is received, the instructions for the system are executed which identify the received work. The system then determines whether the received work is a protected work. This may done by comparing the identity to a list of protected works stored in the processing system or by transmitting the identity to another processing device for determination. If the work is determined to be a protected work, the system alters the data stored in the file of the work to generate decoy data. The file is then stored in memory by the processing system. All identification information for the transferred work is also stored and used for making the file with the decoy data available to other processing devices on the P2P network.
The above and other advantages and features of this invention are described in the detailed description given below and the following drawings:
This invention relates to a system for generating decoy data and distributing the decoy data over a Peer to Peer network. The following is a description of exemplary embodiments in accordance with this invention. Where appropriate, components shown on different figures are given the same reference numeral throughout the description.
Processing system 200 has a Central Processing Unit (CPU) 201. CPU 201 is a processor, microprocessor, or any combination of processors and/or microprocessors that execute instructions stored in memory to perform an application. CPU 201 is connected to a memory bus 203 and Input/Output (I/O) bus 204.
A non-volatile memory such as Read Only Memory (ROM) 211 is connected to CPU 201 via memory bus 203. ROM 211 stores instructions for initialization and other systems command of processing system 200. One skilled in the art will recognize that any memory that cannot be written to by CPU 201 may be used for the functions of ROM 211.
A volatile memory such as Random Access Memory (RAM) 212 is also connected to CPU 201 via memory bus 203. RAM 212 stores instructions for all processes being executed and data operated upon by the executed processes. One skilled in the art will recognize that other types of memories such as DRAM and SRAM may also be used as a volatile memory and that memory caches and other memory devices (not shown) may be connected to memory bus 204.
Peripheral devices including, but not limited to, memory 221, display 222, I/O device 223, and network connection device 224 that are connected to CPU 201 via I/O bus 204. I/O bus 204 carries data between the device and CPU 201. Memory 201 is a device for storing data unto a media. Some examples of memory 221 include read/write compact discs (CDs), and magnetic disk drives. Display 222 is a monitor or display and associated drivers that convert data to a display. I/O device 223 is a keyboard, a pointing device or other device that may be used by a user to input data. Network device 224 is a modem or Ethernet “card” that connects processing system 200 to a network.
This invention relates to a system that generates and distributes decoy data for a work over a Peer to Peer network. A Peer to Peer network is a group of loosely coupled processing systems that communicate with one another to exchange files. There are many different architectures or configurations for Peer to Peer networks. The exact architecture of a Peer to Peer network is not important to providing a system in accordance with this invention.
Process 300 begins in step 305 with the Peer to Peer software being initiated on a processing device. In step 310, the processing unit sends out a request for other processing units connected to the network and executing the Peer to Peer software to respond. In some embodiments, the processing system may transmit non-routable request over the network. In some other embodiments, the processing system may transmit a routable request over the network. In still other embodiments, the executed software includes an address on the network to contact when connecting to the Peer to Peer network. The address may be an IP (Internet Protocol) address, a URL, or other addressing protocol for transmitting data to another processing system connected to the network.
In step 315, a reply is received from a processing system connected to the network and executing the Peer to Peer software. The reply includes address information for other processing systems connected to the network and executing the peer to peer software. This address information may be an IP address, URL, or other resource location information.
In step 320, the processing system reads the list of address information and stores the list in memory. The address information may be used by the processing system to contact other processing systems in the Peer to Peer network. This list may then be sent be the processing system when another processing system in the Peer to Peer network contacts the processing system. This allows the processing system to immediately participate in the massive distribution of address information of active peers to allow all processing systems in the peer to peer network to locate and connect with other processing systems in the network. Furthermore, this allows the processing system to quickly rejoin the network the next time the processing system connects or if the processing system where to be disconnected from the network.
The processing system is now connected to the Peer to Peer network. In step 325, the processing system then compiles a list of content stored by the processing system that is available to other system on the network. In a typical network, only a descriptor of the content of a file available to share is used. However, the list may include content titles, artists, source, encoding method, genre, category, software manufacturer, right holder, and other information. In addition, this information may include a SHA-1 hash, MD5 hash, TorrentID, or other identifier that uniquely describes the content of a file available to share over the network. One skilled in the art will recognize that the exact information is left to a designer of the Peer to Peer network.
In step 330, the list is then transmitted to all processing system identified on the list of connected processing systems stored in memory. One skilled in the art will recognize that list may only be stored locally in some embodiments of peer to peer networks.
In step 335, the processing system receives lists of available contents from other processing systems in the Peer to Peer network. In step 340, the address information for the processing system from which the list was received is stored. After a list is received from a processing system, the list of contents is merged into a list of available content stored by the processing system in step 340. In step 345, the processing system may transmit the list of available content to another processing system in the network. This allows information about available content to be quickly spread to other system connected to the network.
In step 347, the processing system receives a request for content available over the network. The request may be an input from a user. The request may also be a result of an automated process that is searching for a certain content. In step 350, the processing system searches the list of available material to determine a processing system in the network that has the content available. One skilled in the art will recognize that in some systems more than one processing system storing the desired content may be contacted. However, only a second processing system is used in this example to better show the file transfer process.
In step 355, the processing system then establishes a connection with a second processing system providing the content over the network. After the connection is established, the processing system requests the content from the second processing system. One skilled in the art will recognize this request may include some authentication procedure in which the processing system requesting content must transmit authentication data to the second processing system.
In step 360, the processing system receives authorization to receive the content from the second processing system. In some systems, the second processing system may also send a denial of the transfer or an indication that the requested content is no longer available from the second processing system. In step 365, the processing system receives the requested content from the second processing system and process 300 ends.
One skilled in the art will recognize that since the list of systems on the system may change constantly that many methods may be needed to assure that a connection to a processing system providing the requested content and minimize network traffic. However, these are outside the scope of the current discussion and not important to understanding this invention.
This invention relates to the generation and distribution of decoy content for a work over a Peer to Peer network. Instead of introducing decoy content by pretending to be a peer processing system connected to the network, the decoy data for the content of the work is inserted into a file storing the content after the file has been transferred over the network. The insertion is performed by the Peer to Peer application that provides the connection to the network. The instruction for a system in accordance with this invention may be stored as software, firmware, hardware, or any other tangible medium readable by a processing system to execute the instruction to perform processes.
Process 400 illustrated in
Once the identity is ascertained, the processing system compares the identity of the work to a list of known protected works in step 420. If the work is found on the list of protected works, the processing system creates decoy content in the data in step 425. An exemplary embodiment of the processing system of creating the decoy content is described below in process 500, shown in
In step 435, the processing system stores identifiers of the undamaged data. Thus, when the processing system generates a list of available content, the identifiers for the undamaged data of the work is used. This allows the decoy content for the work to be available for transfer with the information of the undamaged copy. This allows the decoy version to defeat some processes for detecting decoy material in Peer to Peer networks.
In step 440, the processing system generates a new set of identifiers for the data including the decoy content and stores the new set of identifiers in step 445. This allows the processing system to make the decoy available under a new identifier to try to prevent detection of the decoy material. The generating of identifiers may include generating a new title, a new hash code, and/or other identifiers used to identify the content of the data.
In step 450, the processing system then makes the stored decoy data in the received file available to other processing systems connected to the Peer to Peer network and process 400 ends. When another processing system connected to the Peer to Peer network searches for a work, that processing system might locate the damaged copy of the work being shared by the processing system. The searching processing system might transfer this decoy content from the processing system to itself. Upon receiving the decoy content, the searching processing system may note the damage and discard the content in which case the P2P network has become less useful. However, upon receiving the decoy content, the searching processing system may fail to notice the damage and keep the decoy in which case the searching processing system will, in turn, share this decoy content back into the network.
The decoy data inserted into the received data may be created by a variety of techniques as commonly known in the art. In the case of an audio work, the work might have a voiceover inserted imploring the listener to “please purchase a legitimate copy”. In the case of an image, the work might have a light overlay of lettering dominating the image. In the case of video, the work might be damaged by having both bold lettering inserted in the center of each frame and an imploring voiceover. In the case of software, the work might have a few key bits flipped to prevent reliable operation or bits inserted that cause the software to display a “please buy me” message when it is executed. In the case of a document, some of the content might be scrambled. The part of the content that is modified is not important. What is important is that the particular copy of the work is rendered less valuable in a way that satisfies the owner of the copyright of the work.
Process 500 begins in step 505 with the data for the work being read. In step 510, the content of the audio work is converted into a Pulse Code Modulation (PCM) format. In step 515, the data is altered. The re-encoding may include reducing the volume of the content by 70% and/or inserting a voice over. Another method of re-encoding may include replacing audio frames directly. The replacement causes an abrupt transition from the work to the inserted data. After the audio data is altered, the PCM data is re-encoded in a form suitable for storage in step 520 and process 500 ends.
In this way each peer on the network becomes a source of decoy content. There is no need for a copyright holder to employ massive spoofing technology to flood the network. As peers naturally migrate to different IP addresses through the normal mechanisms well known in the art, it will be difficult for the P2P network to excise the peer or the content from the network. Essentially the network will become unable to trade undamaged content unless the copyright owner allows it.
One skilled in the art will recognize that the above is a description of exemplary embodiments of this invention. It is envisioned that those skilled in the can and will derive alternative designs that infringe this invention as set forth in the claims below either literally or through the Doctrine of Equivalents.
This application claims priority to U.S. Provisional Patent Application No. 60/592,232, filed Jul. 28, 2004, which is hereby incorporated by reference as if set forth herein.
Number | Name | Date | Kind |
---|---|---|---|
3919479 | Moon et al. | Nov 1975 | A |
4230990 | Lert, Jr. et al. | Oct 1980 | A |
4449249 | Price | May 1984 | A |
4450531 | Kenyon et al. | May 1984 | A |
4454594 | Heffron et al. | Jun 1984 | A |
4677455 | Okajima | Jun 1987 | A |
4677466 | Lert, Jr. et al. | Jun 1987 | A |
4739398 | Thomas et al. | Apr 1988 | A |
4843562 | Kenyon et al. | Jun 1989 | A |
4918730 | Schulze | Apr 1990 | A |
5210820 | Kenyon | May 1993 | A |
5247688 | Ishigami | Sep 1993 | A |
5283819 | Glick et al. | Feb 1994 | A |
5327521 | Savic et al. | Jul 1994 | A |
5437050 | Lamb et al. | Jul 1995 | A |
5442645 | Ugon et al. | Aug 1995 | A |
5504518 | Ellis et al. | Apr 1996 | A |
5581658 | O Hagan et al. | Dec 1996 | A |
5588119 | Vincent | Dec 1996 | A |
5612729 | Ellis et al. | Mar 1997 | A |
5612974 | Astrachan | Mar 1997 | A |
5613004 | Cooperman et al. | Mar 1997 | A |
5638443 | Stefik et al. | Jun 1997 | A |
5692213 | Goldberg et al. | Nov 1997 | A |
5701452 | Siefert | Dec 1997 | A |
5710916 | Barbara et al. | Jan 1998 | A |
5724605 | Wissner | Mar 1998 | A |
5732193 | Aberson | Mar 1998 | A |
5850388 | Anderson et al. | Dec 1998 | A |
5881182 | Fiete et al. | Mar 1999 | A |
5918223 | Blum et al. | Jun 1999 | A |
5924071 | Morgan et al. | Jul 1999 | A |
5930369 | Cox et al. | Jul 1999 | A |
5943422 | Van Wie et al. | Aug 1999 | A |
5949885 | Leighton | Sep 1999 | A |
5959659 | Dokic | Sep 1999 | A |
5983176 | Hoffert et al. | Nov 1999 | A |
6006183 | Lai et al. | Dec 1999 | A |
6006256 | Zdepski et al. | Dec 1999 | A |
6011758 | Dockes et al. | Jan 2000 | A |
6026439 | Chowdhury et al. | Feb 2000 | A |
6044402 | Jacobson et al. | Mar 2000 | A |
6067369 | Kamei | May 2000 | A |
6088455 | Logan et al. | Jul 2000 | A |
6092040 | Voran | Jul 2000 | A |
6096961 | Bruti et al. | Aug 2000 | A |
6118450 | Proehl et al. | Sep 2000 | A |
6192340 | Abecassis | Feb 2001 | B1 |
6195693 | Berry et al. | Feb 2001 | B1 |
6229922 | Sasakawa et al. | May 2001 | B1 |
6243615 | Neway et al. | Jun 2001 | B1 |
6243725 | Hempleman et al. | Jun 2001 | B1 |
6253193 | Ginter et al. | Jun 2001 | B1 |
6253337 | Maloney et al. | Jun 2001 | B1 |
6279010 | Anderson | Aug 2001 | B1 |
6279124 | Brouwer et al. | Aug 2001 | B1 |
6285596 | Miura et al. | Sep 2001 | B1 |
6330593 | Roberts et al. | Dec 2001 | B1 |
6345256 | Milsted et al. | Feb 2002 | B1 |
6374260 | Hoffert et al. | Apr 2002 | B1 |
6385596 | Wiser et al. | May 2002 | B1 |
6418421 | Hurtado et al. | Jul 2002 | B1 |
6422061 | Sunshine et al. | Jul 2002 | B1 |
6438556 | Malik et al. | Aug 2002 | B1 |
6449226 | Kumagai | Sep 2002 | B1 |
6452874 | Otsuka et al. | Sep 2002 | B1 |
6453252 | Laroche | Sep 2002 | B1 |
6460050 | Pace et al. | Oct 2002 | B1 |
6463508 | Wolf et al. | Oct 2002 | B1 |
6477704 | Cremia | Nov 2002 | B1 |
6487641 | Cusson et al. | Nov 2002 | B1 |
6490279 | Chen et al. | Dec 2002 | B1 |
6496802 | van Zoest et al. | Dec 2002 | B1 |
6526411 | Ward | Feb 2003 | B1 |
6542869 | Foote | Apr 2003 | B1 |
6550001 | Corwin et al. | Apr 2003 | B1 |
6550011 | Sims, III | Apr 2003 | B1 |
6552254 | Hasegawa et al. | Apr 2003 | B2 |
6591245 | Klug | Jul 2003 | B1 |
6609093 | Gopinath et al. | Aug 2003 | B1 |
6609105 | Van Zoest et al. | Aug 2003 | B2 |
6628737 | Timus | Sep 2003 | B1 |
6636965 | Beyda et al. | Oct 2003 | B1 |
6654757 | Stern | Nov 2003 | B1 |
6732180 | Hale et al. | May 2004 | B1 |
6771316 | Iggulden | Aug 2004 | B1 |
6771885 | Agnihotri et al. | Aug 2004 | B1 |
6834308 | Ikezoye et al. | Dec 2004 | B1 |
6947909 | Hoke, Jr. | Sep 2005 | B1 |
6968337 | Wold | Nov 2005 | B2 |
7043536 | Philyaw et al. | May 2006 | B1 |
7047241 | Erickson et al. | May 2006 | B1 |
7058223 | Cox et al. | Jun 2006 | B2 |
7181398 | Thong et al. | Feb 2007 | B2 |
7266645 | Garg et al. | Sep 2007 | B2 |
7269556 | Kiss et al. | Sep 2007 | B2 |
7281272 | Rubin et al. | Oct 2007 | B1 |
7289643 | Brunk et al. | Oct 2007 | B2 |
7349552 | Levy et al. | Mar 2008 | B2 |
7363278 | Schmelzer et al. | Apr 2008 | B2 |
7500007 | Ikezoye et al. | Mar 2009 | B2 |
7529659 | Wold | May 2009 | B2 |
7562012 | Wold | Jul 2009 | B1 |
7565327 | Schmelzer | Jul 2009 | B2 |
7593576 | Meyer et al. | Sep 2009 | B2 |
20010013061 | DeMartin et al. | Aug 2001 | A1 |
20010027522 | Saito | Oct 2001 | A1 |
20010034219 | Hewitt et al. | Oct 2001 | A1 |
20010037304 | Paiz | Nov 2001 | A1 |
20010056430 | Yankowski | Dec 2001 | A1 |
20020049760 | Scott et al. | Apr 2002 | A1 |
20020064149 | Elliott et al. | May 2002 | A1 |
20020082999 | Lee et al. | Jun 2002 | A1 |
20020087885 | Peled et al. | Jul 2002 | A1 |
20020120577 | Hans et al. | Aug 2002 | A1 |
20020123990 | Abe et al. | Sep 2002 | A1 |
20020129140 | Peled et al. | Sep 2002 | A1 |
20020133494 | Goedken | Sep 2002 | A1 |
20020152261 | Arkin et al. | Oct 2002 | A1 |
20020152262 | Arkin et al. | Oct 2002 | A1 |
20020156737 | Kahn et al. | Oct 2002 | A1 |
20020158737 | Yokoyama | Oct 2002 | A1 |
20020186887 | Rhoads | Dec 2002 | A1 |
20020198789 | Waldman | Dec 2002 | A1 |
20030014530 | Bodin et al. | Jan 2003 | A1 |
20030018709 | Schrempp et al. | Jan 2003 | A1 |
20030023852 | Wold | Jan 2003 | A1 |
20030033321 | Schrempp et al. | Feb 2003 | A1 |
20030037010 | Schmelzer et al. | Feb 2003 | A1 |
20030051100 | Patel | Mar 2003 | A1 |
20030061352 | Bohrer et al. | Mar 2003 | A1 |
20030061490 | Abajian | Mar 2003 | A1 |
20030095660 | Lee et al. | May 2003 | A1 |
20030135623 | Schrempp et al. | Jul 2003 | A1 |
20030191719 | Ginter et al. | Oct 2003 | A1 |
20030195852 | Campbell et al. | Oct 2003 | A1 |
20040008864 | Watson et al. | Jan 2004 | A1 |
20040010495 | Kramer et al. | Jan 2004 | A1 |
20040053654 | Kokumai et al. | Mar 2004 | A1 |
20040073513 | Stefik et al. | Apr 2004 | A1 |
20040089142 | Georges et al. | May 2004 | A1 |
20040133797 | Arnold | Jul 2004 | A1 |
20040148191 | Hoke, Jr. | Jul 2004 | A1 |
20040163106 | Schrempp et al. | Aug 2004 | A1 |
20040167858 | Erickson | Aug 2004 | A1 |
20040201784 | Dagtas et al. | Oct 2004 | A9 |
20050021783 | Ishii | Jan 2005 | A1 |
20050039000 | Erickson | Feb 2005 | A1 |
20050044189 | Ikezoye et al. | Feb 2005 | A1 |
20050097059 | Shuster | May 2005 | A1 |
20050154678 | Schmelzer | Jul 2005 | A1 |
20050154680 | Schmelzer | Jul 2005 | A1 |
20050154681 | Schmelzer | Jul 2005 | A1 |
20050216433 | Bland et al. | Sep 2005 | A1 |
20050267945 | Cohen et al. | Dec 2005 | A1 |
20050289065 | Weare | Dec 2005 | A1 |
20060062426 | Levy et al. | Mar 2006 | A1 |
20070074147 | Wold | Mar 2007 | A1 |
20070078769 | Way | Apr 2007 | A1 |
20080008173 | Kanevsky et al. | Jan 2008 | A1 |
20080133415 | Ginter et al. | Jun 2008 | A1 |
20080141379 | Schmelzer | Jun 2008 | A1 |
20080154730 | Schmelzer et al. | Jun 2008 | A1 |
20080155116 | Schmelzer | Jun 2008 | A1 |
20090030651 | Wold | Jan 2009 | A1 |
20090031326 | Wold | Jan 2009 | A1 |
20090043870 | Ikezoye et al. | Feb 2009 | A1 |
20090077673 | Schmelzer | Mar 2009 | A1 |
20090089586 | Brunk | Apr 2009 | A1 |
20090192640 | Wold | Jul 2009 | A1 |
20090240361 | Wold et al. | Sep 2009 | A1 |
20090328236 | Schmelzer | Dec 2009 | A1 |
Number | Date | Country |
---|---|---|
0349106 | Jan 1990 | EP |
0 402 210 | Jun 1990 | EP |
0 459 046 | Apr 1991 | EP |
0 517 405 | May 1992 | EP |
0689316 | Dec 1995 | EP |
0 731 446 | Sep 1996 | EP |
0 859 503 | Aug 1998 | EP |
1 354 276 | Oct 2003 | EP |
1 449 103 | Aug 2004 | EP |
1 485 815 | Dec 2004 | EP |
1 593 018 | Nov 2005 | EP |
1485815 | Oct 2009 | EP |
9636163 | Nov 1996 | WO |
9820672 | May 1998 | WO |
0005650 | Feb 2000 | WO |
0039954 | Jul 2000 | WO |
WO 0063800 | Oct 2000 | WO |
WO 0123981 | Apr 2001 | WO |
WO 0147179 | Jun 2001 | WO |
WO 0152540 | Jul 2001 | WO |
WO 0162004 | Aug 2001 | WO |
WO 0203203 | Jan 2002 | WO |
WO 0215035 | Feb 2002 | WO |
WO 0237316 | May 2002 | WO |
WO 0237316 | May 2002 | WO |
WO 02082271 | Oct 2002 | WO |
WO 03007235 | Jan 2003 | WO |
WO 03009149 | Jan 2003 | WO |
WO 03036496 | May 2003 | WO |
WO 03067459 | May 2003 | WO |
WO 03091990 | Nov 2003 | WO |
WO 2004044820 | May 2004 | WO |
WO 2004070558 | Aug 2004 | WO |
WO 2009017710 | Feb 2009 | WO |
Number | Date | Country | |
---|---|---|---|
20060034177 A1 | Feb 2006 | US |
Number | Date | Country | |
---|---|---|---|
60592232 | Jul 2004 | US |