The invention relates to multimedia signal processing, and in particular relates to hiding auxiliary information in media signals like audio, video and image signals.
Digital watermarking is a process for modifying physical or electronic media to embed a machine-readable code into the media. The media may be modified such that the embedded code is imperceptible or nearly imperceptible to the user, yet may be detected through an automated detection process. Most commonly, digital watermarking is applied to media signals such as images, audio signals, and video signals. However, it may also be applied to other types of media objects, including documents (e.g., through line, word or character shifting), software, multi-dimensional graphics models, and surface textures of objects.
Digital watermarking systems typically have two primary components: an encoder that embeds the watermark in a host media signal, and a decoder that detects and reads the embedded watermark from a signal suspected of containing a watermark (a suspect signal). The encoder embeds a watermark by altering the host media signal. The reading component analyzes a suspect signal to detect whether a watermark is present. In applications where the watermark encodes information, the reader extracts this information from the detected watermark.
Several particular watermarking techniques have been developed. The reader is presumed to be familiar with the literature in this field. Particular techniques for embedding and detecting imperceptible watermarks in media signals are detailed in the assignee's co-pending application Ser. No. 09/503,881 and U.S. Pat. No. 5,862,260, which are hereby incorporated by reference.
The invention provides methods and systems for associating watermark enabled objects with machine behaviors. In this context, machine behaviors refer to actions by devices or systems in response to a triggering event. Examples of these behaviors include fetching a web page, opening an email client to send an email to a specific person, initiating a phone or video conference call, etc. In the detailed description to follow, a watermark system enables users to associate machine behaviors with objects through a watermark embedded in the objects. The decoding of the watermark initiates a process for triggering the machine behaviors associated with the watermarked object. While the detailed description focuses on an implementation for stickers as a class of watermark enabled objects, the system and related methods apply to other forms of watermark enabled objects.
Further features will become apparent with reference to the following detailed description and accompanying drawings.
The following description details a system and related methods for associating watermark enabled objects with machine behaviors. To illustrate the system, the description focuses on an example of watermark enabled stickers. As noted, the system applies more broadly to watermarking both physical and electronic objects. In particular, aspects of the system may be used for watermarking media signals like images, video and audio, as well as applying watermarks to physical objects. Watermarks may be applied to physical objects by placing a watermarked image on a physical object, by modulating the surface topology of the object, etc. See U.S. Pat. No. 5,862,260, for more information about watermark embedding of and decoding from physical and electronic objects.
Stickers in all their varieties have found an enduring place in our society. From the workplace (Post-It® brand message notes), to kids in a classroom, stickers have an inherent value associated with them, whether it be functional (seals, labels, etc.) or just to identify yourself with a particular affinity group (bumper stickers on cars). By placing a watermark on stickers they can be used in novel ways. By encoding a set of stickers with a watermark during production, specific machine behaviors can be assigned to them. These behaviors can be associated or even possibly changed by anyone from the manufacturer through the distributor, all the way to the end-user. In addition, the users can create their own watermark enabled stickers by creating an image, embedding a watermark in it, and associating the watermark with one or more machine behaviors.
These behaviors may include, but are not limited to the following:
In each of the above applications, the watermark carries information that links the watermarked object (e.g., sticker) with a machine behavior. To trigger this behavior, a watermark decoder application captures an image or images of the watermarked sticker, extracts the watermark, and uses information embedded in the watermark to determine the associated machine behavior. The watermark decoder then takes action to initiate the machine behavior associated with the watermark.
For some applications, it is useful to enable the user to control the behavior associated with a watermarked object. This type of management may be handled by creating accounts for users and providing access to the accounts via some authentication method (email, passwords, etc.). For a number of reasons, these access methods can be problematic (losing passwords, asking kids for their email addresses, etc.). As an alternative, watermarks may be used to manage the process of associating behaviors with a watermarked object.
For example, in the scenario where a user wants to assign behaviors to a set of watermarked stickers they have received, they can hold up the first sticker (or its packaging), and be taken to a registration application to activate the stickers in the pack.
The system architecture shown in
The registration system maintains a registration database including records of the registration identifiers and corresponding watermark identifiers. The registration identifiers are serialized numbers corresponding to the watermarked stickers or packages of them. The watermark identifiers are a form of object identifiers that are encoded into the watermarks on the corresponding stickers. The registration system maintains a registration database 110 of data records indicating the watermark identifiers associated with each registration identifier. When a user selects a behavior to be associated with a watermarked object via the registration system, the registration system sends an update 112 to a behavior database 114 specifying the behavior to be associated with a corresponding watermark identifier. In response, the database management system 108 updates its database to include a record that indicates the behavior associated with a particular watermark identifier.
The database management system 108 is also responsible for supporting machine behavior associated with a watermarked sticker in response to detection of the watermark on the sticker. It has a network interface for communicating with other computers over the Internet. In particular, it receives requests in the form of an XML packet from a watermark decoding computer, extracts a watermark identifier from the packet and looks up the associated behavior or behaviors in the behavior database. It then initiates the associated behavior. The details of how this behavior is carried out depend on the application and type of behavior.
In a typical registration process, the user accesses the registration system via a registration web site, which presents an HTML interface to the users' computers. The user may fetch the HTML pages of this interface using an Internet browser or application program, like the watermark decoder application executing on the computer 100. This interface enables the user to enter a registration identifier to start a process of associating behaviors with watermark identifiers embedded in watermarked stickers. In response to a registration identifier, the registration system returns a page that enables the user to specify the behavior. In the case where the behavior is linking a watermarked sticker to a web site, the user specifies the network address of the web site, such as a URL or IP address. In the case where the behavior is linking a watermarked sticker to an email message, the user specifies the email address of the email recipient.
As noted above, there are many other types of watermark enabled behaviors. They can be classified as providing information to the watermark decoding computer, launching some software program or machine action, or a combination of both. Table 1 below gives some examples of behaviors, and the related information and actions.
For a given application, the registration system provides information to the user to enable the user to select the behavior and provide pertinent information, such as URL, IP address, phone number, email address, content file (e.g., audio, image or video file), etc. The registration system formulates a description of the behavior, associates it with the watermark identifier specified by the user, and creates an update 112 to the behavior database.
The user then uses the stickers or shares them with friends. To trigger the behavior of a sticker, a user captures an image of the sticker with an image capture device 102 using a watermark decoder application 104 executing on the computer 100. The watermark decoder extracts the watermark identifier from a watermark embedded in the image on the sticker. It then sends the watermark identifier to the database management system 108 via the Internet, which in turn, looks up the associated behavior. The database management system then triggers the associated behavior by sending information, or instructions back to the decoding computer. The decoding computer renders the information, and launches a software or other machine action associated with the instructions returned from the database. The database need not be implemented in a remote computer. For example, the database may be implemented in the watermark decoding computer or device.
As an enhancement to the registration process, objects may carry watermarks that automatically link the user to the registration web site. For example, one side of the sticker 116 or its packaging 118 may contain a watermark with the network address or an index to a network address of the registration web site. The user shows this part of the sticker or packaging to the image capture device. The watermark decoder extracts the watermark and looks up the network address in the behavior database, and launches a browser to fetch the registration web site. The watermark may also carry the registration identifier. In this case, the registration web site can tailor the web page returned to the user to be specific to the watermarked object. If the user or someone else previously associated a behavior with the sticker, the registration web site returns the current status associated with the registration identifier and the behaviors associated with the watermarked objects linked to that registration identifier. To get detailed information about particular watermarked objects during the registration process, the user can show the watermarked object to a camera, and use a watermark decoder to extract the watermark identifier and supply it to the registration system. In response, the registration system takes the watermark identifier, queries the behavior database via the database management system, and returns a description of the associated behaviors. This approach provides a simple and automated process of activating watermark enabled objects.
For more information about an object identifier registration system and system for linking objects with machine behaviors, see U.S. patent application Ser. No. 09/571,422, which is hereby incorporated by reference.
In some applications, the user may wish to create his or her own watermarked objects.
The process begins when an embedder 120 creates a registration request. In the system shown in
Next, the embedder connects, via a network connection, to the registration system 106. In particular, it connects to a registration web site via an Internet connection. This web site requests the embedder's username and password to authenticate it.
The user enters his username and password via a user interface displayed on the PC 100 and submits them to the web site for authentication.
Upon authentication, the registration website 106 returns an HTML page presenting the embedder with a user interface screen that allows the user to locate the embedder's registration request file for uploading to the web site. The user then enters a command to instruct the embedder to upload the selected request file.
The embedder provides the information required to locate the file on the embedder's computer and submits it for upload.
The registration request file is uploaded into a registration loader program 122.
The registration loader 122 performs a quick scan of the uploaded registration request file and reports back to the embedder any errors in format that it detects. If there are errors, the file is not processed.
If the registration request file is properly formatted, the embedder receives a confirmation from the registration website 106 that the request file has been successfully uploaded and will be submitted for processing by the registration loader 122.
The embedder may now either submit a new registration request file or logoff of the registration web site 106.
The registration loader 122 uses the information contained in the embedder's uploaded registration request file to automatically allocate (register) watermark identifiers in a registration database 110. The identifiers are in the form of serial numbers. Once this process is completed, the registration loader 122 initiates a request to a registration extractor 124 for these new registration entries.
Upon receipt of a request, the registration extractor 124 accesses the registration database 110 and creates embedder control files for each of these new registered watermark identifiers (e.g., serial numbers).
Upon completion of this process, the registration extractor 124 process sends the embedder control file(s) back to the embedder via Internet e-mail. In the event that the embedder is server based, the extractor sends the control file(s) (or a pointer to them) to the embedder server 126, which may be integrated with the registration system or implemented at a different Internet site. The extractor 124 also sends an update 128 to the behavior database 114 to create database records associating each of the watermark identifier with a behavior.
Once the embedder 120 has received the embedder control file(s), it uses these file(s), along with the media file(s) (in this case, image files) and a set of embedding instructions to the embedder 120 to instruct the embedder to automatically embed the list of watermark serial numbers included in the embedder control file(s) into the listed media files, producing a set of watermark-embedded media files. In the case where the embedder is server based, the client executing on the PC 100 uploads the media files to be embedded to the embedder server, either directly or as part of the registration process (e.g., as part of the request file). The embedder server then returns the watermarked files to the computer 100 via e-mail or other network file transfer protocol.
For detailed disclosure describing how to embed watermarks in media signals, including images, audio, and video, see U.S. Pat. No. 5,862,260, and co-pending application Ser. No. 09/503,881, filed Feb. 14, 2000, incorporated above.
The embedder may create watermarked objects by printing watermarked images on objects, such as stickers, documents, etc. The embedder sends the watermarked image to a printer 128, which in turn, prints the image on an object.
The above system provides a mechanism for linking objects to machine behaviors. As noted previously, this mechanism applies to both physical objects, like stickers and packaging, and electronic objects, like image, audio and video signals. It also applies to other forms of machine readable signal carriers that can be applied to such objects, including bar codes, magnetic stripes, Radio Frequency tags, integrated circuit chips, organic transistors, etc. These machine readable carriers can be used in the same way that watermarks are used in the example of watermarked enabled stickers above.
While these technologies provide a mechanism for linking objects to machine behaviors, there is a need for a tool that explicitly facilitates the creative coordination between the object and the behavior linked to it. The linking process results in a potentially complex database structure which not only embodies the fundamental object to behavior link, but also might include a hierarchy of delivered responses as a function of user implicit or explicit requests. Or, said in a quite different way, the creative process of linking an object to complex data-driven responses is itself a creative endeavor all to itself, involving thinking through the various different reactions that users will want and expect when using an object as a portal. The artist who is tasked with creating the choreography between an object and a simple or complex machine behavior will need explicit assistance from well designed tools, resulting in a database record which memorializes that creativity as an active element within a connectivity system described in this document and U.S. patent application Ser. No. 09/571,422. The immediate creative output is a database structure. The long term creative output is the active use of that structure as a stimulus-response hub.
Whether a link design tool be web-server based, or whether it be a stand-alone application similar in kind to an Adobe Photoshop or a Quark Express, it is possible to offer visual metaphors to a creative designer which literally presents that designer with an image of the to-be-linked object along with explicit visual links to one or more data responses.
One embodiment of this tool for linking printed objects to web pages is a local computer application which presents an image of a printed object on the left side of an application's window pane and the image of a web page on the right side of the application pane. The images of the printed objects may be stored locally or fetched from a remote device (e.g., a content database) and rendered to the left side of the screen. Similarly, the web pages may be stored locally or downloaded from web sites on the Internet or some other network. The user interface of the application displays a control such as a button, labeled, “Connect”, “Link” or some other active word representing the process of associating an object with a corresponding machine behavior. The user, having browsed through a series of objects to be linked, and browsed through a series of potential web site destinations, finding the best “matched-pair”, pushes the button and off this relational link goes into a queue waiting to “go live”, or, in other words, a temporary record is stored for a candidate link to be sent to the behavior database of the linking system described previously. A user can perform multiple links per session, queueing them up as they go, reviewing the queue at some point in time, then directing the links to become active at the behavioral database, as described previously and in the referenced documents.
An extension begins by generalizing the single printed item to be an icon or visual analogy to a related set of printed material. Graphical user interface methods can be employed to move, manipulate, view and otherwise process this icon in a fashion familiar to creative professionals. Likewise, surrounding this generalized icon representing the object(s) to be printed can be a whole series of icons representing a variety of potential data-delivered responses that are possible links. Existing web pages, placeholders for web pages to be designed, streaming media icons, Java application icons, “links to links” icons wherein a given response may explicitly point to a menu of actions presented to the end user. (end user=consumer doing the linking). This list of possible responses is incomplete but nevertheless representative of graphically displaying the possible relationships between printed material and data responses.
As in the baseline case, various relationships can be created between objects and responses, ultimately stored into a queue. The actual functionality and quality assurance of the links could be tested in the process. Once the creative artist is satisfied with their link or set of links, the queue can be sent to go live at the behavior database and further double checks on quality performed.
Having described and illustrated the principles of the technology with reference to specific implementations, it will be recognized that the technology can be implemented in many other, different, forms. To provide a comprehensive disclosure without unduly lengthening the specification, applicants incorporate by reference the patents and patent applications referenced above.
While the invention is illustrated with reference to watermarked stickers, aspects of the invention apply to other object types including media signals like audio and video. There are number of different watermark embedding and decoding methods that may be used. The watermark embedding process may modulate features of a signal in the time, frequency, spatial or some other transform domain of the signal to be watermarked.
In addition to an object identifier, the watermark may be used to convey other information, such as an index to related metadata, rendering control instructions, etc. For example, the watermark can carry a network address or index to a network address to link the watermarked signal to a network resource such as a related web site.
Other machine readable codes may be embedded in an object and used to link the object to a machine behavior. Some examples include bar codes, magnetic stripes, RF tags, etc. The devices and methods used to extract an identifier from the machine readable code differ, yet the process for registering identifiers and associating behavior with objects may be similar.
The methods, processes, and systems described above may be implemented in hardware, software or a combination of hardware and software. For example, the auxiliary data encoding processes may be implemented in a programmable computer or a special purpose digital circuit. Similarly, auxiliary data decoding may be implemented in software, firmware, hardware, or combinations of software, firmware and hardware. The methods and processes described above may be implemented in programs executed from a system's memory (a computer readable medium, such as an electronic, optical or magnetic storage device).
The particular combinations of elements and features in the above-detailed embodiments are exemplary only; the interchanging and substitution of these teachings with other teachings in this and the incorporated-by-reference patents/applications are also contemplated.
This patent application is a continuation in part of U.S. patent application Ser. No. 09/633,587, filed Aug. 7, 2000, which is a continuation in part of U.S. patent application Ser. No. 09/343,104, filed Jun. 29, 1999. U.S. patent application Ser. No. 09/343,104 claims priority from U.S. Provisional Application No. 60/134,782, filed May 19, 1999. This patent application is also a continuation in part of U.S. patent application Ser. No. 09/571,422, filed May 15, 2000, which claims priority to U.S. Provisional Application No. 60/134,782, filed May 19, 1999. These patent applications are hereby incorporated by reference. This patent application is also a continuation in part of U.S. patent application Ser. No. 09/560,976, filed Apr. 28, 2000 (Now U.S. Pat. No. 6,553,129), which is a continuation of U.S. application Ser. No. 08/746,613, filed Nov. 12, 1996 (now U.S. Pat. No. 6,122,403), which is a continuation in part of U.S. application Ser. No. 08/649,419, filed May 16, 1996 (now U.S. Pat. No. 5,862,260), PCT Application No. PCT/US96/06618, filed May 7, 1996 (Published as WO96/36163), and U.S. application Ser. No. 08/508,083, filed Jul. 27, 1995 (now U.S. Pat. No. 5,841,978). This patent application is also a continuation in part of U.S. patent application Ser. No. 09/314,648, filed May 19, 1999 (Now U.S. Pat. No. 6,681,028). The subject matter of the present application is related to that disclosed in U.S. Pat. No. 5,862,260, and in application Ser. No. 09/503,881, filed Feb. 14, 2000 (now U.S. Pat. No. 6,614,914), which are hereby incorporated by reference.
Number | Name | Date | Kind |
---|---|---|---|
4659919 | Price | Apr 1987 | A |
4807031 | Broughton et al. | Feb 1989 | A |
4846693 | Baer | Jul 1989 | A |
4953080 | Dysart et al. | Aug 1990 | A |
5013047 | Schwab | May 1991 | A |
5026058 | Bromley | Jun 1991 | A |
5314336 | Diamond et al. | May 1994 | A |
5331547 | Laszlo | Jul 1994 | A |
5385371 | Izawa | Jan 1995 | A |
5411259 | Pearson et al. | May 1995 | A |
5450490 | Jensen et al. | Sep 1995 | A |
5463209 | Figh et al. | Oct 1995 | A |
5495581 | Tsai | Feb 1996 | A |
5517336 | Molee | May 1996 | A |
5533124 | Smith et al. | Jul 1996 | A |
5575659 | King et al. | Nov 1996 | A |
5606609 | Houser et al. | Feb 1997 | A |
5612943 | Moses et al. | Mar 1997 | A |
5617119 | Briggs et al. | Apr 1997 | A |
5621864 | Benade et al. | Apr 1997 | A |
5638513 | Ananda | Jun 1997 | A |
5640193 | Wellner | Jun 1997 | A |
5640647 | Hube | Jun 1997 | A |
5644711 | Murphy | Jul 1997 | A |
5673316 | Auerbach et al. | Sep 1997 | A |
5680619 | Gudmundson et al. | Oct 1997 | A |
5689561 | Pace | Nov 1997 | A |
5689626 | Conley | Nov 1997 | A |
5742845 | Wagner | Apr 1998 | A |
5743801 | Welander | Apr 1998 | A |
5748731 | Shepherd | May 1998 | A |
5754981 | Veeneman et al. | May 1998 | A |
5765152 | Erickson | Jun 1998 | A |
5765176 | Bloomberg | Jun 1998 | A |
5768426 | Rhoads | Jun 1998 | A |
5778102 | Sandford et al. | Jul 1998 | A |
5795213 | Goodwin | Aug 1998 | A |
5804803 | Cragun et al. | Sep 1998 | A |
5810666 | Mero et al. | Sep 1998 | A |
5825892 | Braudaway et al. | Oct 1998 | A |
5841978 | Rhoads | Nov 1998 | A |
5848413 | Wolff | Dec 1998 | A |
5853327 | Gilboa | Dec 1998 | A |
5855483 | Collins | Jan 1999 | A |
5892900 | Ginter et al. | Apr 1999 | A |
5899700 | Williams et al. | May 1999 | A |
5900608 | Iida | May 1999 | A |
5902353 | Reber et al. | May 1999 | A |
5903729 | Reber et al. | May 1999 | A |
5905248 | Russell et al. | May 1999 | A |
5905800 | Moskowitz et al. | May 1999 | A |
5906369 | Brennan | May 1999 | A |
5915027 | Cox et al. | Jun 1999 | A |
5915115 | Talati | Jun 1999 | A |
5932863 | Rathus et al. | Aug 1999 | A |
5933798 | Linnartz | Aug 1999 | A |
5938726 | Reber et al. | Aug 1999 | A |
5940595 | Reber et al. | Aug 1999 | A |
5954332 | Mero et al. | Sep 1999 | A |
5954515 | Iggulden | Sep 1999 | A |
5956877 | Raasch et al. | Sep 1999 | A |
5959281 | Domiteaux | Sep 1999 | A |
5974548 | Adams | Oct 1999 | A |
5978773 | Hudetz et al. | Nov 1999 | A |
5982736 | Pierson | Nov 1999 | A |
5995105 | Reber et al. | Nov 1999 | A |
6052486 | Knowlton et al. | Apr 2000 | A |
6081827 | Reber et al. | Jun 2000 | A |
6082774 | Schlauch | Jul 2000 | A |
6084528 | Beach et al. | Jul 2000 | A |
6122403 | Rhoads | Sep 2000 | A |
6138151 | Reber et al. | Oct 2000 | A |
6160540 | Fishkin et al. | Dec 2000 | A |
6164534 | Rathus et al. | Dec 2000 | A |
6190174 | Lam | Feb 2001 | B1 |
6199048 | Hudetz et al. | Mar 2001 | B1 |
6200216 | Peppel | Mar 2001 | B1 |
6256398 | Chang | Jul 2001 | B1 |
6309690 | Brogger et al. | Oct 2001 | B1 |
6311214 | Rhoads | Oct 2001 | B1 |
6314457 | Schena et al. | Nov 2001 | B1 |
6324573 | Rhoads | Nov 2001 | B1 |
6332031 | Rhoads et al. | Dec 2001 | B1 |
6345256 | Milsted et al. | Feb 2002 | B1 |
6434561 | Durst, Jr. et al. | Aug 2002 | B1 |
6448979 | Schena et al. | Sep 2002 | B1 |
6449377 | Rhoads | Sep 2002 | B1 |
6456725 | Cox et al. | Sep 2002 | B1 |
6470096 | Davies et al. | Oct 2002 | B1 |
6505160 | Levy et al. | Jan 2003 | B1 |
6510234 | Cox et al. | Jan 2003 | B1 |
6526449 | Philyaw et al. | Feb 2003 | B1 |
6535614 | Kimura et al. | Mar 2003 | B1 |
6542933 | Durst, Jr. et al. | Apr 2003 | B1 |
6553129 | Rhoads | Apr 2003 | B1 |
6591252 | Young | Jul 2003 | B1 |
6614914 | Rhoads | Sep 2003 | B1 |
6681028 | Rodriguez et al. | Jan 2004 | B1 |
6735324 | McKinley et al. | May 2004 | B1 |
20010001854 | Schena et al. | May 2001 | A1 |
20020006212 | Rhoads et al. | Jan 2002 | A1 |
20020012446 | Tanaka | Jan 2002 | A1 |
20020023148 | Ritz et al. | Feb 2002 | A1 |
20020049967 | Haseltine et al. | Apr 2002 | A1 |
20020059162 | Shinoda et al. | May 2002 | A1 |
20020062382 | Rhoads et al. | May 2002 | A1 |
20020073214 | Iinuma | Jun 2002 | A1 |
20020075298 | Schena et al. | Jun 2002 | A1 |
20020080271 | Eveleens et al. | Jun 2002 | A1 |
20020080396 | Silverbrook et al. | Jun 2002 | A1 |
20020085759 | Davies et al. | Jul 2002 | A1 |
20020102966 | Lev et al. | Aug 2002 | A1 |
20020153661 | Brooks et al. | Oct 2002 | A1 |
20020155893 | Swanberg et al. | Oct 2002 | A1 |
Number | Date | Country |
---|---|---|
493091 | Jul 1992 | EP |
975147 | Jan 2000 | EP |
1001605 | May 2000 | EP |
7115474 | May 1995 | JP |
WO9743736 | Nov 1997 | WO |
WO9803923 | Jan 1998 | WO |
WO0007356 | Feb 2000 | WO |
WO0026749 | May 2000 | WO |
WO0115021 | Mar 2001 | WO |
WO0161987 | Aug 2001 | WO |
WO0173586 | Oct 2001 | WO |
WO0184438 | Nov 2001 | WO |
WO0203328 | Jan 2002 | WO |
Number | Date | Country | |
---|---|---|---|
60134782 | May 1999 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 08746613 | Nov 1996 | US |
Child | 09343104 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 09633587 | Aug 2000 | US |
Child | 09690773 | US | |
Parent | 09571422 | May 2000 | US |
Child | 09633587 | US | |
Parent | 09560976 | Apr 2000 | US |
Child | 09571422 | US | |
Parent | 09314648 | May 1999 | US |
Child | 09560976 | US | |
Parent | 09343104 | Jun 1999 | US |
Child | 09314648 | US | |
Parent | 08649419 | May 1996 | US |
Child | 08746613 | US | |
Parent | PCT/US96/06618 | May 1996 | US |
Child | 08649419 | US | |
Parent | 08508083 | Jul 1995 | US |
Child | PCT/US96/06618 | US |