US 7,609,848 B2Grant

Multi-stage watermarking process and system

Issue Date:2009-10-27

•18 Claims

•13 Drawing Sheets

Abstract

A multi-stage watermarking system and process that creates a watermark specification which describes how to generate a watermark, generates a template specification which describes how to merge the watermark into a target document, generates the watermark based on the watermark specification, and merges the watermark into the target document based on the template specification to provide a watermarked document.

Metadata

Assignee

ContentGuard Holdings, Inc.

Inventors

Xin Wang
Steve Atsushi Okamoto
Russell Robert Lear
Nancy Lynn Ishigo

Application Information

Application Number:US 11/209,647

Filing Date:2005-08-24

Priority Date:2000-12-29

Art Unit:2624

Classifications

IPC:

G06K9/00H04L9/32

Patent Drawings (13 sheets)

Description

Cross Reference to Related Applications

[0001] This application is a Continuation Application of application Ser. No. 11/142,256 filed on Jun. 2, 2005, which is a Continuation Application of application Ser. No. 09/749,895 filed Dec. 29, 2000.

Background of the Invention

[0002] 1. Field of the Invention

[0003] The present invention is directed to the field of digital rights management. More specifically, the present invention is directed to digital watermarking processes and systems.

[0004] 2. Description of the Related Art

[0005] In the field of documents and publishing, a work created by an author is usually provided to a publisher which formats, duplicates and/or prints numerous copies of the document. A “document”, as the term is used herein, is any unit of information subject to distribution or transfer, including but not limited to correspondence, books, magazines, journals, newspapers, other papers, software, photographs and other images, audio and video clips, and other multimedia presentations or products. A document may be embodied in printed form on paper, as digital data on a storage medium, or in any other known manner on a variety of media. The copies of the document are then sent by a distributor to bookstores or other retail outlets, from which the copies are purchased by end users. With the advent of current computing and communications systems such as personal computers, workstations, and other devices connected over communications networks such as local area networks (LANs), intranets, and the Internet, publishers and authors are increasingly publishing their documents electronically to minimize cost and delays. Presently, audio and video recordings, software, books, journals and multimedia works, are all being electronically published.

[0006] A fundamental issue facing the publishing and other information industries as they consider electronic publishing, is how to prevent the unauthorized and unaccounted distribution or usage of electronically published documents. Electronically published documents are typically distributed in digital form and recreated on a computer based system having the capability to recreate the published document. The ease in which electronically published documents can be accurately reproduced and distributed is a major concern. Because publishers, authors, as well as other parties in these industries receive royalties for each published document that is delivered (i.e. sold), any unaccounted distribution of the document such as by copying or distribution to another digital medium results in unpaid royalties. Moreover, whereas the low quality of copying and the high cost of distributing printed material have served as deterrents to unauthorized copying in the past, it is far too easy to copy, modify, and redistribute unprotected digital documents. Accordingly, some method of protecting digital documents is necessary to make it more difficult to copy such documents without authorization. Efforts to resolve this problem have been termed “Intellectual Property Rights Management” (“IPRM”), “Digital Property Rights Management” (“DPRM”), “Intellectual Property Management” (“IPM”), “Rights Management” (“RM”), and “Electronic Copyright Management” (“ECM”), collectively referred to as “Digital rights management (DRM)” herein. There are a number of issues in digital rights management: authentication, authorization, accounting, payment and financial clearing, rights specification, rights verification, rights enforcement, and document protection, for example.

[0007] Two basic schemes have been employed to attempt to solve the document protection problem. The first approach is the use of subscription based services in which the user is granted access to the document (or information to generate the document) only after paying a subscription fee. Existing digital rights management systems such as IBM's Cryptolopes utilizes encryption technology to encrypt documents which are then decrypted by users who have paid for the documents or have been otherwise authorized to have access to the documents. However, once these documents are distributed and have been decrypted by an end user system, little protection is available to prevent copying or distributing the decrypted document. In addition, there is no effective way to trace back such copies of the document to the original source and the intended user. The second approach is to utilize proprietary formats wherein the document can only be generated by a select application that is obligated to enforce the publisher's rights. Of course, this approach requires the use of a single proprietary format and thus, one loses the ability to combine popular formats and the richness of content associated therewith. In addition, this approach requires the user to use a previously unknown application and requires development of the select application in order for each format to be created in a secure manner. Furthermore, the documents must be generated or converted using non-standard tools.

[0008] To deter “pirating”, i.e. unauthorized copying, use, or distribution of the documents, “watermarks” are frequently used to identify the copyright owners, authorized users, and/or distributors. Such watermarking also aids in the identification of the source of the document thereby allowing enforcement of the rights of the publisher and/or the author. With respect to the digitally published documents, current digital watermarking technology digitally marks the document with details such as information provided by the copyright owner, the authorized user, or the distributor. Typically, a watermark is used to identify the source or originator of a document. If the watermark is used to identify the user to whom the document is delivered, it is typically referred to as a “fingerprint”. The technologies utilized for both watermarking, and fingerprinting, are typically the same. Thus, the term “watermarking” is used herein to refer to both watermarking and fingerprinting, and the terms “watermark” and “mark” are also used herein to refer to both watermarks and fingerprints.

[0009] Presently, most existing watermarking products or tool kits generate marked documents via document editors or special tools. For instance, Adobe Photo Shop® is a widely used software tool for image creation and publishing on the Internet. DigiMarc Corporation has provided a plug-in to Photo Shop 4.0® which allows a user to embed into an image, a digital ID (which is issued by DigiMarc) as well as some attributes such as the type of use and content. IBM® has also introduced digital watermarking technology through a plug-in for Photo Shop® to identify and preserve the rights of digital content owners. In addition, watermarking of audio clips such as a music file has also been attained by converting the music file into a frequency domain utilizing Fourier transforms, embedding a watermarking signal at a desired frequency range, and reconverting the music file. In this regard, efforts have been taken to standardize DRM of digital music as evidenced by the Secure Digital Music Initiative which may be found in the Internet address www.sdmi.org.

[0010] Despite the utility that the above-described plug-ins and watermarking techniques provide, these watermarking products have several key limitations. More specifically, the present applicants have found that the current processes and systems “bind” or affix the content information into the watermark at early stages of the document life cycle thereby limiting the type of content information which can be stored in the watermark to “static” information which is known or already determined. Another limitation arise from the fact that watermarks are frequently placed into documents manually through the use of WYSIWYG (what you see is what you get) editors or other tools. Tools exist for merging watermarks into multiple same objects (such as images) of a target document automatically. However, such tools do not facilitate insertion of various watermarks into target documents that have multiple differing objects. Moreover, the use of existing processes and systems for inserting watermarks are limited to a single watermarking technology and thus, are limited to utilizing one predetermined application. Consequently, the existing systems and methods do not allow selection of different or multiple technologies nor support use of such different technologies.

[0011] Therefore, there exists an unfulfilled need for a watermarking process and system which will provide a solution to the above noted limitations to thereby allow efficient creation and use of watermarks to identify and preserve the rights of digital content owners.

Brief Summary of the Invention

[0012] In view of the foregoing, it is an object of the present invention to provide an improved process and system that will allow efficient creation and use of watermarks to identify and preserve the rights of digital content owners.

[0013] A second object of the present invention is to provide an improved process and system that will allow early and late binding of content information into the watermark.

[0014] A third object of the present invention is to provide an improved process and system that will support the use of multiple watermarking and merging technologies.

[0015] Another object of the present invention is to provide an improved process and system that will allow automatic or manual merging of watermarks into the document.

[0016] A fifth object of the present invention is to provide an improved process and system that will create a watermark specification and render the watermark at different stages of the watermarking process.

[0017] Still another object of the present invention is to provide such an improved process and system that generates a template specification and merges the watermark into the document at different stages of the watermarking process.

[0018] Yet another object of the present invention is to provide such an improved process and system that allows generation and merging of the watermark into the document at different stages of the watermarking process.

[0019] These objects are obtained by a multi-stage watermarking system and process in accordance with embodiments of the present invention which perform the steps of creating a watermark specification which describes how to generate a watermark, generating a template specification which describes how to merge the watermark into a target document, generating the watermark based on the watermark specification, and merging the watermark into the target document based on the template specification to provide a watermarked document.

[0020] The watermark specification created may include content information which describes content to be in the watermark and the watermark may have a plurality of content information associated therewith. The content of each of the content information may be application specific and specify at least one of static information and dynamic information. The watermark specification created may also include mark technology specification which describes a specific watermarking technology to be used in the step of generating the watermark. The mark technology specification may include parameters needed by the specific watermarking technology during the step of generating the watermark. The watermark specification created may also include a target object specification which describes at least one of a target object and a characteristic of the target object into which the watermark is generated, the target object specification specifying at least one of a shape, color, font and resolution of an image. The target object specification may include a pointer pointing to a content information which describes the content to be inserted in the watermark. In this regard, the watermark specification created may described using a watermark specification language that has grammar elements that: identifies the watermark specification, identifies a specific watermarking technology to be used, and identifies a target object in which the watermark is generated. Optionally, the watermark specification language may have grammar elements that at least one of: identifies version of the watermark specification language, identifies a name of the watermark specification, and specifies technology of content information of the watermark specification.

[0021] In accordance with one embodiment of the present invention, the template specification generated may include a merge map associated with the watermark specification which describes where the watermark is to be merged into the target document. A plurality of merge maps may be associated with the watermark specification. The template specification generated may include a merge technology specification which describes a specific merging technology to be used in the step of merging the watermark into the target document. The template specification generated may also include merge target specification which describes at least one of the target document and a characteristic of the target document into which the watermark is merged. In addition, the template specification generated may be described using a watermark specification language having grammar elements that: identifies version of the watermark specification language, provides a list of a plurality of watermark specifications to be used, and provides a mapped list of how a plurality of watermarks associated with the plurality of watermarks is to be merged with the target document. In this regard, the watermark specification language may optionally have grammar elements that at least one of: identifies the template specification, identifies a name of the template specification, provides a description of the template specification, identifies owner authorized to change the template specification, and provides comments regarding the template specification.

[0022] In accordance with another embodiment of the present invention, the step of generating the watermark in the multi-stage watermarking system and process may include the step of binding dynamic information in the watermark. In addition, the step of generating the watermark may also include the step of receiving and interpreting information from the watermark specification. The step of generating the watermark may also include the step of parsing the watermark specification to thereby obtain the information required to generate the watermark. The step of generating the watermark may further include the step of encoding the content that is to be in the watermark. In this regard, the specific watermarking technology may be used to place the encoded content in a target object to be merged into the target document.

[0023] In accordance with yet another embodiment of the present invention, the step of merging the watermark may include the step of receiving and interpreting information from the template specification. The step of merging the watermark may also include the step of parsing the template specification to thereby obtain the information required to merge the watermark into the target document. In addition, the step of merging the watermark may also include the step of merging the watermarks into the target document to thereby provide the marked document. Moreover, the step of merging the watermark may also include the step of merging the generated watermark in a target object which is then merged into the target document to thereby provide the watermarked document.

[0024] Optionally, in accordance with another embodiment, the multi-stage watermarking system and process of the present invention may also include the step of recovering the content information from the watermarked document. The content information may be recovered based on at least one of the watermark specification and the template specification.

[0025] The above objects are also attained by a system for specifying, generating, and merging digital watermarks into a document at different stages of the document's life cycle in accordance with the present invention including a content information means for describing application-specific content to be in watermarks, the application-specific content being generated by multiple applications and including application identification that is used during watermarks recovery; a static information means for specifying static content that is already determined for binding into the watermarks; and a dynamic information means for specifying dynamic content that is to be determined for binding into the watermarks by the time of at least one of generating the watermarked, and creating the watermarked document.

[0026] In accordance with another embodiment, the system may also include a mark technology specification means for describing a specific watermarking technology to be used in creating the watermarks, where the mark technology specification means further includes parameters needed by the specific watermarking technology. The system may also include a target object specification means for providing the target object information that describes the target object into which the watermarks are generated.

[0027] The system may also include a target object specification means for providing the target object information that describes the target object into which the watermarks are generated. The data capacity of the watermarks may be determined based on at least one of the content information and the target object information. If the data capacity of the watermark is insufficient, then the content may be truncated or a pointer to the content information may be generated.

[0028] The system preferably binds the static content to the watermarks prior to the binding of dynamic content to the watermarks and the watermark is merged into the document by at least one of manually by a user and automatically by the system. The system may further include a mark specification interpreter which supports multiple marking technologies.

[0029] The above noted objects may be further attained by a system for specifying, generating, and merging digital watermarks into a documents at different stages of the document's life cycle in accordance with the present invention including a content information means for generating application-specific content information to be in the watermark, the application-specific content information being generated by multiple applications and including application identification that is used during watermark recovery; a watermark specification means for generating a watermark specification having information regarding the watermark based on the content information; a template specification means for generating a template specification having at least one merge map that describes how each watermark is to be merged into a target document; and a watermark generation means for generating the watermark in a target object based on at least one of a watermark specification, a target object information, and dynamic content information.

[0030] In accordance with one embodiment, the content information may also include at least one of digital rights information, text content information, and reference to a workflow processing application. The watermark specification means may include a watermark specification interpreter with a parser that parses the watermark specification, the watermark specification interpreter adapted to obtain the application-specific content information from the watermark specification and to invoke appropriate encoders to encode the content information that is to be in the watermark. In this regard, the watermark specification interpreter may support multiple marking technologies.

[0031] The system may further include a static information means for specifying static content that is already determined for binding into the watermarks and a dynamic information means for specifying dynamic content that is to be determined for binding into the watermarks by the time of at least one of generating the watermark, and creating the watermarked document. The static content is preferably bound to the watermarks prior to the binding of dynamic content to the watermarks.

[0032] In accordance with yet another embodiment, the system may further include a mark technology specification means for describing a specific watermarking technology to be used in creating the watermarks. The mark technology specification means may include parameters needed by the specific watermarking technology. The system may also include a target object specification means for providing the target object information that describes a target object into which the watermarks are to be generated. The data capacity of the watermarks are preferably determined based on at least one of the content and the target object information.

[0033] In accordance with still another embodiment of the present invention, the template specification may also include a merge technology specification that describes the specific merging technology to be use in merging the watermarks into the target document. The template specification may include a merge target specification that describes the target document into which the watermarks are to be merged.

[0034] Preferably, the watermark is merged into the document by at least one of manually by a user and automatically by the system. In addition, the template specification is preferably generated based on the watermark specification and may include a template specification interpreter that utilizes a parser to parse the template specification.

[0035] These and other objects, features and advantages of the present invention will become more apparent from the following detailed description of the preferred embodiments of the present invention when viewed in conjunction with the accompanying drawings.

Brief Description of the Drawings

[0036] FIG. 1 is a schematic illustration of a multi-stage watermarking process in accordance with one embodiment of the present invention.

[0037] FIG. 2 is a schematic illustration of a watermark specification creation stage in accordance with one embodiment of the present invention.

[0038] FIG. 3 is a schematic illustration of a template specification generation stage in accordance with one embodiment of the present invention.

[0039] FIG. 4A is a schematic illustration of a watermark generation stage in accordance with one embodiment of the present invention.

[0040] FIG. 4B is an detailed schematic illustration of a watermark generation stage of FIG. 4A.

[0041] FIG. 5A is a schematic illustration of a watermark merging stage in accordance with one embodiment of the present invention.

[0042] FIG. 5B is an detailed schematic illustration of a watermark merging stage of FIG. 5A.

[0043] FIG. 6 is a schematic illustration of a watermark recovery stage in accordance with one embodiment of the present invention.

[0044] FIG. 7 is an object model illustration of a multi-stage watermarking process in accordance with one embodiment of the present invention.

[0045] FIG. 8 is an object model illustration of a content information class in accordance with one embodiment of the present invention.

[0046] FIG. 9 is an object model illustration of a mark technology spec class in accordance with one embodiment of the present invention.

[0047] FIG. 10 is an object model illustration of a mark technology class in accordance with one embodiment of the present invention.

[0048] FIG. 11 is an object model illustration of a merge technology spec class in accordance with one embodiment of the present invention.

[0049] FIG. 12 is an object model illustration of a merge technology class in accordance with one embodiment of the present invention.

[0050] FIG. 13 is one example of a document with watermarks that were generated using the multi-state watermarking process of the present invention.

[0051] FIG. 14 is a schematic illustration of one application where the present invention may be effectively used.

[0052] FIG. 15 is a schematic illustration of another application where the present invention may be effectively used.

Detailed Description of the Invention

[0053] As will be evident by the discussions provided hereinbelow, the preferred embodiment of the multi-stage watermarking process and system in accordance with the present invention allows efficient creation and use of watermarks to identify and preserve the rights of digital content owners. Initially, it is noted that U.S. patent application Ser. No. 08/948,893 which is incorporated herein by reference, discloses the use of watermarks in identifying and preserving the rights of digital content owners. Moreover, as previously noted, it should be kept in mind that the term “watermarking” as used herein below refers to both watermarking and fingerprinting, and that the terms “watermark” and “mark” also used herein refer to both watermarks and fingerprints.

[0054] FIG. 1 shows a schematic illustration of a multi-stage watermarking process 2 in accordance with one embodiment of the present invention which will attain the above noted objectives. As can be seen, the multi-stage watermarking process 2 in the illustrated embodiment includes various steps or “stages” including a watermark specification creation 10 stage, a template specification generation 20 stage, a watermark generation 30 stage, and watermark merging 40 stage. Moreover, the illustrated embodiment also includes an optional watermark recovery 50 stage. These stages of the multi-stage watermarking process 2 may be executed by a system such as a computer system (not shown) or the like to thereby provide a process and system which avoids the limitations of the prior art processes and systems. In this regard, it should be initially clarified that the present invention may be practiced using a computer system (including distributed and/or networked systems) and may be embodied as a software program to be executed in such systems. In such an embodiment, the various stages may be embodied or otherwise executed as modules of the software program. These modules may be separate from one another or be integrated together, as long as the modules perform the various desired steps or functions as described in the claims appended hereto.

[0055] The multi-stage water marking process 2 and a system of the present invention allows the creation of a watermark specification which describes the watermark, and the actual rendering or generation of the watermark, to occur at different stages of the watermarking process. For instance, the present invention allows the specification of the watermark to be created in a first system, whereas the generation of the watermark occurs subsequently on a second system, so long as the second system has access to the watermark specification created by the first. In addition, the multi-stage watermarking process 2 of the present invention also allows the generation of a template specification which describes how to merge the watermark into a target document, and the actual merging of the watermark into the document, to occur in different stages within the watermarking process. Moreover, the multi-stage watermarking process 2 further allows the generation of the watermark and the merging of the watermark into the document to occur at different stages in the watermarking process. As will be explained in further detail below, this enables mixing of watermarking technologies within a given document, support for various merging technologies, and also allows these stages to occur at different times and on different systems.

[0056] Importantly, as will be evident to one of ordinary skill in the art in view of the discussions below, these provisions of the multi-stage watermarking process 2 allow early and late binding of content information of the watermark. In particular, the process in accordance with the present invention allows one to have both early binding of static information, and late binding of dynamic information in the watermark. Thus, the present invention allows late binding of dynamic information so that it is possible to incorporate content information into the watermarks which are only available or determined at later stages of the document life cycle. For instance, the name of the system or device that creates the watermarked document or the time at which the watermarked document is created can only be determined at the time of their occurrence. Furthermore, the present invention allows automatic (as well as manual) merging of watermarks into a document. In this regard, the present invention allows marking of multiple documents with a single watermark specification, as well as marking a single document with multiple watermark specifications. Such a feature would be very useful to those who desire to mark a large collection of documents using the same set of watermarks. For instance, one can create a template specification for merging multiple watermarks (as defined by watermark specifications) into multiple target documents. Moreover, as will be explained in further detail below, by providing a multi-stage watermarking process 2, the present invention allows multiple watermarking and merging technologies to be used within a document.

[0057] The discussion hereinbelow describes in further detail the embodiment of the multi-stage watermarking process 2 in accordance with the present invention as shown in FIG. 1. However, for clarity and to facilitate understanding, the discussion hereinbelow sets forth the various stages of the watermarking process 2 of FIG. 1 noted above as well as other aspects of the present invention under separate sub-headings.

Watermark Specification Creation

[0058] As can be seen, one stage of the multi-stage watermarking process 2 in accordance with the illustrated embodiment of the present invention is the watermark specification creation 10 stage. FIG. 2 illustrates the watermark specification creation 10 stage in accordance with one embodiment of the present invention in further detail. As can be seen, the main output of this stage is a watermark specification 12 that describes how the watermark is to be generated, what information is to be in the watermark, and what technology is to be used in generating the watermark. As will be described in further detail below, the watermark may be generated and directly merged into the target document or may optionally generated within a specified target object which is then merged into the target document. In applications where the document is textual, the target object may be an area or region in which the watermark is to be placed. In applications where the document is an audio clip, a video clip, or other multimedia product, the target object may be a video segment or a frequency range or other portion of the multimedia product. It should also be noted that various different computer languages can be used to create the watermark specification 12. However, a preferred embodiment of a watermark specification language is described below. As can be seen, the watermark specification creation 10 stage utilizes various components to create the watermark specification 12. These various components include content information 14, mark technology specification 16, and target object specification 18.

[0059] The content information 14 describes the application-specific content that is to be inserted into the watermark. It is noted that the content is application-specific which means that multiple different applications may be used to provide multiple, different content information 14 as shown in FIG. 2. Correspondingly, it should be appreciated that one can have multiple content information 14 (i.e. from multiple applications) within a single watermark as long as there is enough data capacity in the watermark. Each of the content information 14 also includes the application identification that will be used later in the multi-stage watermarking process as will be discussed below. In addition, the content information 14 may include a pointer which points to the target object where the watermark is generated if applicable. The content information 14 may further specify the “static” information and the “dynamic” information. In particular, the static information is the data/information relative to the watermark or the document that is already determined or presently known such as the publisher's identity and initial publication date, etc. On the other hand, the dynamic information is the data/information relative to the watermark or the document that is not determined or presently known but is to be resolved at a later time, such as when the watermarked document is created. Such dynamic information may include the identity of the authorized distributor or the intended end user who has proper access to the digital document, which in digital publishing, may not be readily known until the document is received, generated and/or printed by the distributor or the intended end user.

[0060] The mark technology specification 16 which is also a component of the watermark specification 12 describes a specific watermarking technology to be used in generating the watermark. For instance, the mark technology specification 16 may specify either DataGlyph® or DigiMarc®, for example, both of these watermarking technologies being commercially available. Other technologies include Verance®'s Electronic DNA®, Alpha Tech®'s EIKONAmark®, Audiomark® and Videomark®, Blue Spike®, and IBM® applications, etc. The mark technology specification 16 may also include various parameters needed by the specific watermarking technology, such as specific parameters specifically required by DataGlyph® or DigiMarc®.

[0061] The target object specification 18 which is an optional component of the watermark specification 12 describes the target object into which the watermark may be generated in one embodiment of the present invention. As previously noted, the target object refers to an area, region or a portion in which the watermark may be generated. For instance, the target object specification 18 for a DataGlyph® watermark may specify at least one of a shape, color, font and resolution of an image into which a DataGlyph® watermark is to be generated, the target area then being merged into the target document as described below. For watermarking technologies that embed watermarks into images, the target object specification 18 may specify that the target object is an image. Again, as previously noted, in applications where the document is an audio clip, a video clip, or other multimedia product, the target object may be a video segment or a frequency range or other portion of the multimedia product. It should further be noted that the target object specification 18 may describe a specific target object, or a characteristic of the target object, in which case the generation of the watermark may optionally occur at a later stage described hereinbelow. It is again noted that the generation of the watermark in a target object and merging of the target object into the target document is optional and in other embodiments, the watermark may be directly merged into the target document.

[0062] In the above described manner, the watermark specification creation 10 stage of the present process utilizes content information 14, mark technology specification 16, and optionally, target object specification 18 to thereby create the watermark specification 12. Thus, the watermark specification 12 describes how the watermark is to be generated, what information is to be in the watermark, and what technology is to be used in generating the watermark. It is also noted that as part of the process of generating the watermark specification 12 (or as part of watermark generation described hereinbelow), the size of the content information 14 is preferably checked against the data capacity of the watermark itself. The capacity of the watermark may be determined based on the mark technology specification 16 and the target object specification 18, if applicable. If there is insufficient data capacity in the watermark, various methods may be utilized to address the insufficiency. For example, the watermark may be truncated, or a pointer may be provided in the watermark to point to the content information 14 rather than putting the actual content in the watermark.

Template Specification Generation

[0063] The multi-stage watermarking process 2 in accordance with preferred embodiment of the present invention as shown in FIG. 1 also includes a template specification generation 20 stage which is shown in further detail in FIG. 3. The primary output of the template specification generation 20 stage is template specification 22 which describes how to merge one or more watermarks directly into the target document, or by merging a target object with the watermark as described previously. For instance, the template specification 22 may indicate which pages a specific watermark should appear if the document is a textual product such as a correspondence or a book. In applications where the document is an audio clip, a video clip or some other multimedia product, the template specification 22 may indicate the audio/visual segments into which the watermarks are merged. The template specification 22 may also include a pointer that points to the target document. In a similar manner to the watermark specification 12 described above, different languages can be developed and/or used for generating the template specification 22. However, as noted previously, an example of a watermark specification language is described in a later section below. As can be clearly seen in FIG. 3, the template specification 22 is generated during the template specification generation 20 stage utilizing merge maps 24 that correspond to each watermark specification 12 as described below. In addition, optional components such as a merge technology specification 26, and a merge target specification 28 may also be utilized in generating the template specification 22.

[0064] More specifically, the merge maps 24 describe where each watermark or watermark in a target object, as represented by watermark specification 12 of FIG. 2, is to be merged into the target document. Preferably, there is one watermark specification 12 associated with each merge map 24 since each watermark should be merged into the target document in at least one location. Otherwise, there is no need for a watermark specification for a watermark which is not used. However, it should be noted that the watermark specification 12 may be associated with multiple merge maps 24 since the same watermark may be merged into the target document at various locations.

[0065] As noted above, the merge technology specification 26 shown in FIG. 3 is an optional component which may be used to generate the template specification 22 during the template specification generation 20 stage. The merge technology specification 26 describes the specific merging technology to be used in merging the watermarks into the target document. For example, the merge technology specification 26 may indicate PostScript® forms, Document Object Model, XML, MS Office®, etc. which are all different technologies. As can be appreciated by one of ordinary skill in the art, this description of the specific merging technology is desirable if the merge technology to be used requires specific parameters to be defined.

[0066] As previously noted, the merge target specification 28 shown in FIG. 3 is also an optional element which may be used to generate the template specification 22 during the template specification generation 20 stage. The merge target specification 28 describes the target document into which the watermarks are to be merged. For instance, the merge target specification 28 may indicate that the target document is a correspondence, book, magazine, journal, newspaper, other paper, software, photograph, image, audio and video clips, or a multimedia presentation or product. In this regard, it should be noted that merge target specification 28 may describe a specific target document or a characteristic of the target document, in which case binding of the watermark may occur at later stages as described hereinbelow.

Watermark Generation

[0067] The multi-stage watermarking process 2 in accordance with one embodiment of the present invention as shown in FIG. 1 also includes a watermark generation 30 stage as shown in FIG. 4A. As can be seen, in the illustrated embodiment, the watermark generation 30 stage generates a watermark in a target object to thereby provide a marked object 32 as its output based on the watermark specification 12 described previously relative to FIG. 2. Thus, in this embodiment, the marked object 32 is a watermarked target object (i.e. the marked object 32) which may later be merged with the target document. Such use of target objects is especially useful in textual documents where sizing and positioning of the watermark may be required and in HTML applications where a specific watermark may only be associated with a specific hyperlink or a specific web page. Of course, as previously explained, the present invention may also be practiced without the use of such target objects by generating the watermark and directly merging the watermark into the target document. However, with respect to the illustrated embodiment where target objects are used, the various components used in the watermark generation 30 stage of the multi-stage watermarking process 2 may be the watermark specification 12 (of FIG. 2), the target object 34 to which the watermark specification 12 points to, and dynamic content information 36, if dynamic information is to be bound or affixed into the watermark.

[0068] The details of one embodiment of the watermark generation 30 stage is more clearly shown in FIG. 4B. As can be seen, the watermark generation 30 stage includes a mark specification interpreter 31 which utilizes a watermark specification language (WSL) parser 33 to parse the watermark specification 12 to thereby obtain the information required to generate the marked object. Such information may include information from the mark technology specification 16 and/or the mark technology specification 16 discussed relative to FIG. 2. The mark specification interpreter 31 also invokes the appropriate content information encoder 35 to encode the content that is to be inserted into the watermark. The watermark technology 37 then places the content into the target object in the form of watermarks. It should also be noted that in accordance with the embodiment of the present invention, different watermark technologies 37 can be used to generate the watermark. For instance, the watermark technology can be DataGlyph®, or any other suitable technology.

[0069] By providing a multi-stage water marking process 2 with a watermark specification creation 10 stage and a separate watermark generation 30 stage, the present invention allows the creation of a watermark specification 12, and the actual generation or rendering of the watermark to occur at different stages of the watermarking process 2. Thus, the present invention allows the specification of the watermark to be created in one system, whereas the generation or rendering of the watermark may occur subsequently on a different rendering device.

Watermark Merging

[0070] The multi-stage watermarking process in accordance with one embodiment of present invention also includes watermark merging 40 stage in which the watermark generated during the watermark generation 30 stage is merged into the target document. As previously explained, the watermark may be directly merged into the target document. However, if the watermark was generated in a target object to thereby provide a marked object 32, the target object with the watermark therein (i.e. the marked object 32) may be merged into the target document. As shown in FIG. 5A, a watermarked document 42 is outputted by merging the watermark or the marked object into the target document 44. It should be noted that whereas in the present illustrated embodiment, the target document 44 (and thus the resulting watermarked document 42) is an actual document, in other embodiments, the target document 44 may alternatively be another object so that the watermarked document 42 is another watermarked object that can later be merged into a document. Thus, the term “document” should be construed broadly to mean actual documents or objects. As can be also seen in FIG. 5A, the watermarked document 42 is provided in the watermark merging stage 40 based on various components including the previously described template specification 22 of FIG. 3, and a target document 44 to which the template specification 22 points to.

[0071] The specific details of one embodiment of the watermark merging 40 stage is more clearly illustrated in FIG. 5B. As can be seen, the watermark merging 40 stage includes a template specification interpreter 41 which utilizes the watermark specification language parser 43 to parse the template specification 22 of FIG. 3 to thereby obtain the watermark specification 12 and the mapping requirements as provided by the merge maps 24. The template specification interpreter 41 then invokes the merge technology 45 to merge the watermarks or the target objects with the watermarks therein (i.e. marked objects 32) into the target document to thereby provide the watermarked document 42. It should also be noted that different merging technologies can be used to generate the watermarked document 42, depending on the format and the requirements of the watermarked document 42. For instance, there may be specific merge technologies for PostScript (via forms) or for MS Office, etc.

[0072] In the manner described above, the multi-stage watermarking process 2 of the present invention thus allows the creation of template specification 22 and the actual merging of the watermark into the document to occur in different stages within the watermarking process 2. Moreover, the multi-stage watermarking process 2 further allows the generation and merging of the watermark into the document at different stages in the watermarking process. This enables mixing of watermarking technologies within a given document and also allows these stages to occur at different times and on different systems. As can now be appreciated by one of ordinary skill in the art, these provisions of the multi-stage watermarking process 2 allows early binding of static information and late binding of the dynamic information in the watermark. The present invention also allows automatic (as well as manual) watermarking of multiple documents with a single watermark specification, as well as watermarking a single document with multiple watermark specifications. Moreover, the multi-stage watermarking process 2 of the present invention provides support for various watermarking and merging technologies.

Watermark Recovery

[0073] The multi-stage watermarking process 2 in accordance with the embodiment of the present invention as illustrated in FIG. 1 also includes an optional watermark recovery 50 stage which is more clearly shown in FIG. 6. In the watermark recovery 50 stage, the content information 14 (FIG. 2) which was previously put into the watermark of the watermarked document 42 in the manner described above, is now recovered from the watermarked document 42. This may attained by utilizing an object character recognition (OCR) system known in the art to thereby obtain desirable information regarding the watermarked document. For instance, the recovery of the watermark may be desired to recognize the type of document, determine the document's authenticity, the document's source, or other relevant information. The template specification 22 and the watermark specification 12 which were also described previously relative to the other stages of the multi-stage watermarking process 2, may also be utilized to effectively recover the content information 14.

Object Model

[0074] To further describe the multi-stage watermarking process 2 in accordance with the illustrated embodiment of the present invention of FIG. 1, the discussion hereinbelow sets forth the present invention utilizing an object model syntax. In particular, FIG. 7 describes an embodiment of the present invention utilizing the Unified Modeling Language (UML) which is a general purpose notational language used by those skilled in the art to specify and visualize complex software. As can be seen in FIG. 7, the relevant outputs of the stages and the classes corresponding to the components thereof are illustrated in FIGS. 1-6 and have been recreated as an object model using the UML syntax. Correspondingly, the relevant outputs of the stages and the classes have been enumerated in FIG. 7 utilizing numerals of FIGS. 1-6 which have been increased by 100. It should also be noted that due to the length of the text in the object models, the term “watermark” is merely referred to as “mark” which as previously noted, refer to both watermarks and fingerprints. In addition, the term “specification” is merely referred to as “spec” whereas “technology” is sometimes referred to as “tech”.

[0075] Accordingly, in FIG. 7, the watermark specification is represented by mark spec 112 while the template specification is represented as template spec 122. The mark spec 112 and template spec 122 represent the data and the actions that can be performed on the previously described watermark specification 12 and template specification 22 respectively. As can be seen, the mark spec 112 includes the classes content information 114, mark technology spec 116, and target object spec 118. In the illustrated embodiment, the mark spec 112 may utilize the mark technology 137 to generate the watermark. As can also be seen, the template spec 122 includes classes merge map 124, merge technology spec 126, and merge target spec 128. In the illustrated embodiment, the template spec 122 may utilize the merge technology 145 to properly merge the watermark into the target document to thereby provide a watermarked document. Thus, FIG. 7 clearly shows a representative relationship between the mark spec 112, the template spec 122, and the various classes thereof.

[0076] As shown in FIG. 8, the content information 114 may be subclassed into application specific objects. In the illustrated example, the content information 114 may include rights info 202, the text content info 204, and workflow applet 206 (i.e. a workflow processing application). The rights info 202 is content information that may include digital property rights information. The text content info 204 is an application that inserts straight text information into the watermark. The workflow applet 206 may represent the various applets that will be invoked during different stages of the document workflow. It should again be noted that the content information 114 is a representation of various application-specific content information 14 described previously and thus, it may vary depending on the specific application.

[0077] The mark technology spec 116, as shown in FIG. 9, and the mark technology 137, as shown in FIG. 10, represent various technologies that can be used in generating the watermark in accordance with the multi-stage watermarking process of the present invention. As can be seen in FIG. 9, the mark technology spec 116 may include the DataGlyph® tech spec 208 or the DigiMarc® tech spec 210 which correspond to Xerox® DataGlyph® and DigiMarc® technologies respectively that may be utilized to create the watermark specification 12 shown in FIG. 2. Similarly, as shown in FIG. 10, the mark technology 137 may utilize the DataGlyph® mark tech 209 or the DigiMarc® tech 211 to generate the desired watermarked object 32 shown in FIGS. 4A and 4B. Thus, with respect to FIGS. 9 and 10, two different watermark technologies are represented under the watermark specification creation 10 stage and the watermark generation 30 stage described previously of the multi-stage watermarking process in accordance with one embodiment of the present invention. It should also be noted that other watermark technologies may also be used in other embodiments of the present invention. As previously noted, such other technologies include Verance®'s Electronic DNA®, Alpha Tech®'s EIKONAmark®, Audiomark® and Videomark®, Blue Spike®, and IBM® applications, etc.

[0078] In a similar manner, the merge technology spec 126, and the merge technology 145 of FIGS. 11 and 12 represent the various merging technologies that can be used into merge the watermark into the target document in accordance with the present invention. In particular, as can be seen in FIG. 11, the merge technology spec 126 may include PostScript® PS forms tech spec 212, document object model (DOM) tech spec 214, or MS Office® tech spec 216 that may be used in the template specification generation 20 stage to generate the template specification 22 as shown in FIG. 3. In addition, as shown in FIG. 12, the merge technology 145 may include the PostScript® PS forms merge tech 213, document object model DOM merge tech 215, or MS Office® merge tech 217 that may be used in the watermark merging 40 stage in the manner shown in FIGS. 5A and 5B to thereby generate the watermarked document 42. Thus, with respect to FIGS. 11 and 12, two different merging technologies are represented for the template specification generation 20 stage and the watermark merging 40 stage described previously of the multi-stage watermarking process in accordance with one embodiment of the present invention. Of course, it should also be noted that other merging technology may be used instead of the ones discussed above.

[0079] It can be readily appreciated by one of ordinary skill in the art, the above described multi-stage watermarking process in accordance with the present invention attains the previously noted objectives by allowing digital watermarks to be specified, generated, and merged, into documents at different stages of the document life cycle. Thus, the present invention enables mixing of watermarking technologies within a given document, and enables support for various merging technologies, and also allows these stages to occur at different times and on different systems. The present invention also allows early binding of static information and late binding of dynamic information. The present invention further allows automatic watermarking of multiple documents with a single watermark specification, as well as watermarking a single document with multiple watermark specifications.

Example Applications

[0080] FIG. 13 illustrates a watermark template 302 having various watermarks 304 generated in the manner described above which may be utilized in various applications, two of such applications being described in further detail hereinbelow which are made possible by the multi-stage watermarking process of the present invention. FIG. 14 illustrates one application for the multi-stage watermarking process in accordance with the present invention. In this application, a publisher utilizes a template creation system 402 described in further detail hereinbelow to sell digital documents that are to be printed by users at their local commercial print shops that utilize print system 404. To deter and/or detect illegal copying, the publisher desires to put standard watermarks for all of their documents printed at the commercial print shops. The publishing company creates a watermark template 302 of FIG. 13 or any other watermark template that includes a template specification described previously. The watermark template may specify several watermarked objects that are to appear on each printed document. For instance, the publisher may specify borders for its standard header and footer using DataGlyph watermarks. Of course, different sets of watermarks could be specified for the front cover and/or a dynamic information may be put into the watermarks in order to identify the various print shops. These templates can then be distributed to print shops that are authorized to print the publisher's documents. When the print shop prints the publisher's document, the print system 404 will follow the watermark template to render the correct watermarks on the specified pages.

[0081] More specifically, as can be seen in FIG. 14, the template creation system 402 used by the publisher includes a mark specification tool 410 and a template tool 420. The mark specification tool 410 enables the users to create watermark specification described previously, and stores it into the watermark specification repository 411. The publisher interacts with the template tool 420 to thereby create templates having template specifications described previously by using the watermark specification stored in the mark specification repository 411. The templates are then stored in the publisher template repository 421. These templates are subsequently stored in the printer template repository 441 of an authorized print shop. Any method can be used to transfer the templates from the publisher's template creation system 402 to the print shop's print system 440 including via a network such as the Internet, a secure network, or by physically transferring an information storage media such as an optical or magnetic disc with the templates thereon. The templates stored within the printer template repository 441 of the print system 440 may then be retrieved as needed by the print system 440. Of course, in other applications, the templates may also be provided together with the document to be printed.

[0082] When a publisher's document 460 is submitted to the print shop, the print system 440 spools the publisher's document 460 into the printer document spool 445. The print system 440 then searches the printer template repository 441 for the appropriate template to use. During rendering, the printer's rendering module 447 performs the watermark generation and watermark merging function described previously by generating the watermark, reading the template, and merging the watermark into the target document to thereby provide a watermarked document 461. The document may then be and printed by the printer marking module 449 and a hard copy may be outputted by the print system 440. Any dynamic content info 446 may be provided to the printer rendering module 447 so that such dynamic content info 446 can be placed into the watermark of the watermarked document 461 by the printer marking module 449. As previously explained, such dynamic content info 446 may be any information which was not readily available, for instance, the identity of the print shop or the identity of the person for whom the watermarked document 461 is provided.

[0083] FIG. 15 illustrates yet another application of the multi-stage watermarking process in accordance with the present invention. In this illustrated embodiment, the scan service 502 utilizes the multi-stage watermarking process to process various forms in the manner described below. The scan service 502 may be, for example, an insurance company which processes various types of claim forms or documents that are sent into the company via surface mail or fax. The scan service 502 scans in each form or document for record keeping purposes and inserts watermarks into the scanned image of each claim form or document in order to record various types of information such as the receipt date of the form and the status of the claim. Other information can of course, be provided in the watermark to facilitate workflow processing of the claim form. The scan service 502 may design different watermark templates for each type of claim form 560, each template being defined using a watermark specification to record the information in the appropriate format (for example, DataGlyph®), and a template specification in the manner described previously. For instance, the template specification may include a watermark to record the status of the claim as a text image in the background of the claim form image. This may be desirable to allow claims adjusters to process the claim forms manually.

[0084] Referring again to FIG. 15, when the claim form 560 is initially scanned in by the scan service 502, the scan service 502 performs the watermark recovery function corresponding to the watermark recovery 50 stage and looks for the form type which has been recorded in the DataGlyph format. The image processing system 547 then brings up the corresponding watermark template from the template repository 521 and puts the desired additional watermarks into the image. Moreover, dynamic content information 546 such as information regarding the current status of the claims may also be incorporated into the watermark. The image processing system 547 then performs the watermark generation and watermark merge functions described previously to render the watermarks into the image and output the watermarked image 562 which may then be sent to an appropriate repository for subsequent processing.

Watermark Specification Language

[0085] As previously noted, the present invention provides a multi-stage watermarking process 2 and a system such as a computer based system for executing such a process. In this regard, one embodiment of a watermark specification language (hereinafter “WSL” or “language”) that may be used for defining the watermark specification 12 and template specification 22 discussed above is proposed herein below in detail. This embodiment of the watermark specification language is modeled from the Digital Property Rights Language (DPRL) developed by Mark Stefik et al. as fully described in detail in U.S. Pat. Nos. 5,629,980, and 5,715,403 which are incorporated herein by reference, as well as application Ser. No. 08/948,893 which was previously incorporated herein by reference. As such, the language grammar and grammar rules given below relative to the watermark specification language generally correspond to DPRL but the keywords and the syntax of the WSL differ from DPRL. It should also be noted that DPRL itself includes information which may be a component of the watermark specification. In particular, DPRL specifies the requirement for watermark from the rights perspective. For example, the publishers can specify what information is to be in the watermark. The WSL in accordance with the present invention also allows specification of how the watermark should be put into the document. In this sense, WSL enhances DPRL and may be used in conjunction with DPRL to define the watermark specification 12, or be used by itself. This is attained since the WSL also allows defining of the template specification 22 in accordance with the present invention as described previously. Of course, other languages may be utilized in practicing the present invention and the details set forth hereinbelow should be understood as merely showing one example. For example, the present invention may be practiced by utilizing a watermark specification language in the XML format or other derivations thereof.

[0086] Initially, it is noted that terms of the WSL in italics are expanded into other terms in the actual WSL specification, the specification referring to the watermark specification 12 and/or the template specification 22 in the present embodiment. Italicized terms that are to be expanded into other terms in the actual WSL statements are referred to as non-terminals, and terms that appear in actual WSL statements are referred to as terminals. The right arrow “→” indicates a grammar expansion rule. Thus, as an example, the rule:

- [0087] a-spec→b: b-spec
  means that the non-terminal a-spec is expanded to “b:” followed by an expansion of b-spec. The subscript “opt” indicates that a specification is optional. Vertical bars “|” are used to indicate alternative expressions. For example, the rule
- [0088] b-spec→a|
  - [0089] x (Goodies: b-list)_opt|
  - [0090] c: c-spec
    means that a b-spec is expanded into either an “a” or an “x” followed optionally by a parenthetical expression starting with “Goodies:” and followed by the expansion of b-list, or a “c:” followed by an expansion of c-spec.

[0091] In the embodiment below, the white space in the language such as spaces and tabs, is used merely to separate the grammar of the language and has no other meaning except inside quoted strings. The case of terms such as capitalization is also not meaningful. Thus, a “Template:” keyword can be written as “Template:” or “template:” or even “tEmPlaTe:”. However, capitalizing the first letter is preferred for readability. Preferably, programs that print specifications out from objects utilize the preferential capitalization.

[0092] Some of the design goals for the grammar include:

- [0093] Simple parsing. To arrange statements in uniform format to thereby simplify parsing.
- [0094] Extensive defaulting. To provide a language with well-defined defaults when a particular parameter is not specifically given, especially since many parameters are optional.
- [0095] Extensiblity. To establish a language style in which it is easy to add new features unambiguously without substantially modifying the language or rewriting old specifications.
  To this end, the grammar elements have the form:
- [0096] (keyword: parameter₁parameter ₂)
  that is, a keyword is followed by a colon, followed by a set of optional parameters. The language has many optional parameters and few position-sensitive parameters. The parameters themselves are recursively represented as further elements. This leads to sentences of the form:
- [0097] (keyword₁:(keyword₂: parameter₁)
  - [0098] (keyword₃: (keyword₄: parameter₂) (keyword₅: parameters₃)))
    with short parenthesized elements whose meaning is easy to recognize. At the bottom, there are keyword-value pairs that describe particular parameter values.

[0099] In the examples below, the preferred order for key-word phrases is the order shown in the grammar. In many cases, this order is thought to be clearest in meaning. However, except as noted in the text, compilers and interpreters of the language preferably accept the phrases in other orders as well. Programs that generate statements in the language are expected to print out phrases in the preferred order.

Template Specification

[0100] The highest level grouping in the Watermark Specification Language (WSL) is template specification 22 (FIG. 3) which as been described previously above and may have the following grammar with the grammar elements:

- [0101] watermark-template→
  - [0102] (WMTemplate:
  - [0103] (WSL-Version: version-id)
  - [0104] (Template-ID: template-id)_opt
  - [0105] (Name: text-description)_opt
  - [0106] (Description: text-description)_opt
  - [0107] (Owner: certificate-spec)_opt
  - [0108] (Comment: comment-str)_opt
  - [0109] watermark-list-spec
  - [0110] map-list-spec)

[0111] The WSL-Version includes a grammar element which is a machine-readable identifier version-id that identifies the version of the watermark specification language used. The identification of the version of the WSL used facilitates backwards compatibility to works in which the template specification were written in an older version of the language.

[0112] As indicated by the subscript “opt”, the grammar element template-id is an optional identification tag which can be used to identify the particular template. In this regard, the template-id may identify a digital certificate signed by a trusted registration authority that assigns a unique identification number to the template. It also may include information for locally detecting any changes or tampering with the template. In addition, the template-id may also include address information for locating a reference copy of the template.

[0113] The template specification 22 may also include optional grammar elements for a name and a description of the template. The format and scope of the information in the name and the description are not specified so that different parties can put various types of information here, depending on the application.

[0114] The template specification 22 may further include an optional grammar element for owner specification, which may indicate who is authorized to change any part of the template-specification, including adding or deleting watermarks and its associated parameters. The owner specification may also indicate what digital license is required to make the changes. If no owner specification is specified, then anyone (or no one) would be able to make changes to the watermarks in a digital work.

[0115] The template specification 22 may also include an optional grammar element for comments. Comments in WSL may be intended for documentation purposes and may be used by people creating and updating template specifications. Comments are not interpreted for meaning by watermarking systems but their provision and use is important in the WSL. More specifically, since WSL statements can be compiled into objects and subsequently printed out again to make new source statements, it is important that comments be preserved throughout the edit-compile-reprint cycle for specifying rights. In the WSL herein described, the comments have fixed and specific locations in the syntax (“structured comments”) corresponding to structured locations for object storage to thereby ensure that the comments be stored in the compiled watermark objects. In this regard, there is preferably only one comment in a template specification at each level.

[0116] The watermark-list-spec in the template specification 22 preferably lists all of the watermark specifications that are used in the template and have the following grammar:

- [0117] watermark-list-spec→(Watermark-List: watermark-list)
- [0118] watermark-list→wm-spec watermark-list_opt
  A fuller description for the watermark-spec is provided in a later section hereinbelow.

[0119] The map-list-spec in the template specification 22 lists the descriptions of how each watermark should be merged within the document and have the following grammar:

- [0120] map-list-spec→(Map-List: map-list)
- [0121] map-list→map-spec map-list_opt
  A fuller description for the map-spec is also provided in a later section hereinbelow.

[0122] An example template specification 22 is given below:

[0123]


(WMTemplate:
	(WSL-Version: 1.01)
	(Template-ID: “Journal-Press-Registry-kjru89902)
	(Name: “standard-journal-page”)
	(Description: “Template for page for standard journal cover page”)
	(Owner: (Certificate:
	(Authority: “Journal Publishers Association”)
	(ID: “Journal Press Publishing”)))
	(Comment: “To be included in all journal cover sheet”)
	(Watermark-List:
	(WMSpec: (
	(Name: “DataGlyph 1X6”)
	(WMSpec-ID: “JPP-1278”
	(WMContentInfo.RightsContentInfo:
	(Label-ID: JPA223049-01))
	(WMTechInfo.XDGTechInfo:...)
	(WMTargetInfo:...))
	(WMSpec: (
	(Name: “Copyright Notice”)
	(WMSpec-ID: “JPP-748922”
	(WMContentInfo.NullContentInfo: )))
	)
	(Map-List:
	(WMMap: (
	(WMSpec-ID: “JPP-1278”)
	(WMPosition.PageCoord: 1 50 125)))
	(WMMap: (
	(WMSpec-ID: “JPP-748922”)
	(WMPosition.PageCoord: 2, 350 250)))
	)
)

Watermark Specification

[0124] Watermark specification 12 (FIG. 2) defines how the watermark is to be generated, what information is to be in the watermark, and what technology is to be used in generating the watermark. It contains information on the content (such as content information 14), the technology to use (such as mark technology specification 16), and the target object (target object specification 18) into which the watermark is to be placed. It should be noted that the watermark specification 12 can exist independent of the template specification 22 described previously and has the following grammar with the grammar elements:

- [0125] wm-spec→
  - [0126] (WMSpec:
  - [0127] (WSL-Version: version-id)_opt
  - [0128] (Name: name-str)_opt
  - [0129] (WMSpec-ID: wm-spec-id)
  - [0130] content-info-list_opt
  - [0131] tech-info-spec
  - [0132] target-info-spec

[0133] The WSL-Version includes a grammar element which is a machine-readable identifier version-id that identifies the version of the watermark specification language used. The identification of the version of the WSL used facilitates backwards compatibility to works in which the watermark specification were written in an older version of the language. The provision of the version-id is optional for the watermark specification 12 if the watermark specification 12 is actually a part of the template specification 22, and if the version of the language happens to be the same. Each watermark specification 12 may have an optional grammar element for a name:

- [0134] Name: name-str

[0135] The watermark specification 12 also includes a grammar element wm-spec-id which is an identification tag used to identify the watermark specification 12. This is preferably provided since each watermark map-spec appearing in the template specification 22 refers to a watermark specification 12 using the wm-spec-id.

[0136] As previously noted, there are preferably three main components to the watermark specification 12: the content information 14, the mark technology specification 16, and the target object specification 18 which are shown in FIG. 2. As previously described, the content information 14 indicates what information should be in the watermark. In many cases, the content information 14 is application specific. For example, a rights management application may specify rights-related information to be in the watermark whereas a workflow application may specify other types of information to be in the watermark. Therefore, the parameters for the content information 14 is preferably specific to the application and in the present embodiment, has the following grammar:

- [0137] content-info-list→content-info-spec content-info-list_opt
- [0138] content-info-spec→(WMContentInfo.content-info-qualifier:
  - [0139] application-id-spec_opt
  - [0140] content-info-parameters)
- [0141] application-id-spec→Appl-ID: application-id
  The grammar element content-info-qualifier specifies the particular application and thus, the content-info-spec, for example, may be:
- [0142] (WMContentInfo.RightsContentInfo: (Label-ID: 25.457/12546))
  where the RightsContentInfo is the application and the Label-ID is the parameter specific to the application.

[0143] The grammar element application-id is an optional identification tag in the watermark to help identify the particular application associated with the content so as to aid in associating the application with the content when the watermark is recovered.

[0144] The mark technology specification 16 describes a specific watermarking technology, with associated parameters, to use in creating or interpreting the watermark. Thus, the specification is closely related to the specific technology selected. For example, an application involving DataGlyphs® may require error correction parameters, whereas one involving DigiMarc® may us some other particular information. Because of this specificity, the technology information parameters in the language may depend on the technology actually being used.

- [0145] tech-info-spec→
  - [0146] (WMTechInfo.technology-info-qualifier: technology-info-parameters)
    Here the grammar element technology-info-qualifier identifies the specific technology involved and the technology-info-parameters provide the necessary parameters for that technology. For example, the tech-info for DataGlyphs may be:
- [0147] (WMTechInfo.XDGTechInfo: (Error-correction: 20) (Write-white: false))

[0148] The target object specification 18 describes the target object into which the watermark is to be placed and may have the grammar:

- [0149] target-info→(WMTargetInfo.target-info-qualifier.target-info-parameters)
  This specification is loosely related to the watermarking technology and the content information. For instance, it isn't meaningful to specify a JPEG image as the target object if the technology is specified as DataGlyphs®. In the above noted grammar, the target-info-qualifier is specific to the type of the target. For example, if the technology selected is DataGlyphs®, the target-info may be:
- [0150] (WMTargetInfo.XDGTargetInfo:
  - [0151] (XDGWidth: 16)
  - [0152] (XDGHeight: 16)
  - [0153] XDGFileType: BMP))

[0154] Lastly, referring again to the map-spec previously noted relative to the template specification 22 discussed above, the map-spec defines how the watermark is to be merged into the document and may have the grammar with the grammar elements:

- [0155] map-spec→
  - [0156] (WMMap:
  - [0157] (WMSpec-ID: wm-spec-id)
  - [0158] wm-pos-spec)
    The grammar element wm-spec-id is an identification tag which may be used to identify the corresponding watermark specification 12 and is assumed to be in the template specification itself, or otherwise be available to the application that processes the template specification. The map-spec and the positional information therein, indicates the specifics of where the watermark should appear in the target document. In many cases, the positional information is specific to a target object. For example, if the target object is a document formatted for printing, the positional information may be in terms of pages and the x/y coordinates within a page. Positional information may also point to some object in the document. If the target object is a video or audio clip, the positional information could be quite different (e.g., with time element). In any case, the grammar element wm-pos-spec may be:
- [0159] wm-pos-spec→(WMPosition.position-qualifier: position-vector)
- [0160] position-vector→position-element position-element-vector_opt
  The position specification is preferably in a form of a vector representing the hierarchy of positional elements, with each successive element defining the position in more detail. For example, position specification for a document might have section, chapter, page and x/y position in the vector, in that order. The position-qualifier specifies the particular type of position specification. For example, the wm-pos-spec may be:
- [0161] (WMPosition.PageCoord: 1 546 785)

[0162] The type and the order of individual elements in the position-vector are specific to the type of the position specification as indicated by the position-qualifier. In the example above, the PageCoord qualifier identifies the page number and the x/y coordinates within the specified page. There may be other page based qualifiers that describe in different forms, the page designation (e.g., first page, last page, etc.). Each position-element itself could also be of the “(a: param)” form, depending on the type of the position element that the position vector requires.

[0163] It should be evident from the above detailed discussions that by providing a multi-stage water marking process, the present invention allows the creation of a watermark specification, and the actual generation of the watermark, to occur at different stages of the watermarking process. It should also be evident how the present invention allows the generation and merging of the watermark into the document to occur at different stages in the watermarking process. It is further evident how the present invention allows the creation of template specification and the actual merging of the watermark into the document to occur in different stages within the watermarking process. As explained above, these provisions allow early binding of static information and late binding of dynamic information. The present invention further allows automatic watermarking of multiple documents with a single watermark specification, as well as watermarking a single document with multiple watermark specifications. Moreover, it should also be evident how the present invention allows the support of multiple watermarking and merging technologies so that it will allow various watermarking technologies to be used within a document.

[0164] It should also be noted that the present invention can be embodied as software, hardware, or combination thereof. For instance, the present invention may be implemented utilizing any type of hardware or combination thereof such as various “clients” and “servers”. Accordingly, the terms “client” and “server” as used herein, can refer to any type of computing device or data terminal, such as personal computer, a portable computer, a dumb terminal, a thin client, a hand held device, a wireless phone, or any combination of such devices. The various clients and servers can be a single computer at a single location or multiple computers at single or multiple locations. For example, a server may be comprised of a plurality of redundant computers disposed in co-location facilities or at various locations to facilitate scalability. There can be any number of clients and any number of servers and the client can also be physically located on the same hardware as the server.

[0165] Moreover, the present invention can be implemented over any type of communications network, such as the Internet, a local area network (LAN), a wide area network (WAN), direct computer connections, or the like using any type of communications hardware and protocol. Communication can be accomplished over electric cable, fiber optic cable, or any other cable, or in a wireless manner using radio frequency, infrared, or other technologies. As previously noted, documents can be of any type and contain any type of content such as text, audio information, video information, or any combinations thereof.

[0166] It should also be noted that whereas the multi-stage watermarking process in accordance with the present invention is described as having multiple stages, it should be appreciated that these stages need not be embodied in separate software or hardware but may be provided in a single software or hardware. Moreover, it should also be apparent that the various stages of the present embodiment as discussed above can be subdivided into small stages and other stages may be added as well. In this regard, if the present invention is implemented in software, the various steps can be merely separate portions of the same software code, different files, interspersed lines of code, etc.

[0167] While various embodiments in accordance with the present invention have been shown and described, it is understood that the invention is not limited thereto. The present invention may be changed, modified and further applied by those skilled in the art. Therefore, this invention is not limited to the detail shown and described previously, but also includes all such changes and modifications which are encompassed by the claims.

Claims

Certificate of Correction present

The claims shown below may not include correction changes. Use the corrected PDF for authoritative text.

The invention claimed is:

1. A method of recovering content information from a watermark in a target digital document to be carried out by a computer adapted to perform the steps of:

locating the watermark in the target document based on a pre-determined template specification that describes a manner in which the watermark was merged into the target document, the template specification identifying at least one watermark specification and providing a mapping list indicating a manner in which at least one watermark associated with the at least one watermark specification is merged into a document; and

obtaining the content information from the located watermark according to a watermark specification identified by the template specification, the watermark specification identifying a specific watermarking technology and a target object into which the watermark was placed.

2. The method of claim 1, wherein the at least one watermark specification is described using a watermark specification language including grammar elements.

3. The method of claim 1, wherein the obtained content information includes dynamic information pertaining to different stages of the life cycle of the target document.

4. The method of claim 1, wherein the content information indicates at least one of document type, document-associated application, document authenticity and document source.

5. The method of claim 1, wherein the predetermined template specification is identified by comparing a plurality of template specifications to the target document and selecting a match.

6. The method of claim 1, wherein obtaining the content information further comprises

selecting a watermark specification identified by the pre-determined template specification;

comparing the located watermark to the selected watermark specification to identify if the selected watermark specification is a matched watermark specification; and decoding the located watermark into the content information according to the matched watermark specification if the located watermark matches the selected watermark specification.

7. The method of claim 1, wherein the target document comprises audio or video content.

8. A watermark recovery system comprising:

a watermarked document including a watermark with encoded content information;

a watermark specification for identifying a specific watermarking technology and identifying a target object in which the watermark is placed;

a template specification identifying at least one watermark specification and providing a mapping list indicating a manner in which at least one watermark associated with the at least one watermark specification is merged into a document;

a watermark scanning module for scanning the watermarked document to locate a watermark according to the template specification, the watermark scanning module including a repository for storing at least one of the template specification and a watermark specification; and

a watermark recovery module for recovering the content information from the located watermark according to a watermark specification identified by the template specification.

9. The system of claim 8, wherein the template specification describes the manner in which the watermark was merged into the target document.

10. The system of claim 8, wherein the content information indicates at least one of document type, document-associated application, document authenticity and document source.

11. The system of claim 8, wherein the watermarked document comprises audio or video content.

12. A method for creating a watermark in a target digital document at different stages of the target document life cycle to be carried out by a computer adapted to perform the steps of:

scanning the target document containing a target watermark;

recovering the target watermark from the target document, the recovered target watermark indicating a template specification that describes how the target watermark was merged into the target document;

generating an additional watermark according to a watermark specification;

updating the template specification by adding the watermark specification and associating the additional watermark with the watermark specification in the template specification; and

merging the generated additional watermark with the scanned target document.

13. The method of claim 12, wherein the template specification identifies at least one watermark specification and provides a mapping list of how the target watermark associated with the at least one watermark specification is merged, the at least one watermark specification identifying a specific watermarking technology and a target object in which the additional watermark is placed.

14. The method of claim 12, wherein the additional watermark includes dynamic information pertaining to different stages of the life cycle of the target document.

15. The method of claim 12, wherein the target watermark has a dataglyph format indicating a form type associated with the template specification.

16. The method of claim 12, wherein the target document comprises audio or video content.

17. The method of claim 1, wherein the target watermark has a dataglyph format indicating a form type associated with the template specification.

18. The system of claim 8, wherein the target watermark has a dataglyph format indicating a form type associated with the template specification.

Patent Citations (334)

Patent	Date	Inventor	Cited By
US3263158(A)	1966-07-01	Janis	Applicant
US3609697(A)	1971-09-01	Blevins et al.	Applicant
US3790700(A)	1974-02-01	Callais et al.	Applicant
US3798605(A)	1974-03-01	Feistel	Applicant
US4159468(A)	1979-06-01	Barnes et al.	Applicant
US4200700(A)	1980-04-01	Mäder	Applicant
US4220991(A)	1980-09-01	Hamano et al.	Applicant
US4278837(A)	1981-07-01	Best	Applicant
US4323921(A)	1982-04-01	Guillou	Applicant
US4361851(A)	1982-11-01	Asip et al.	Applicant
US4423287(A)	1983-12-01	Zeidler	Applicant
US4429385(A)	1984-01-01	Cichelli et al.	Applicant
US4442486(A)	1984-04-01	Mayer	Applicant
US4529870(A)	1985-07-01	Chaum	Applicant
US4558176(A)	1985-12-01	Arnold et al.	Applicant
US4593376(A)	1986-06-01	Volk	Applicant
US4614861(A)	1986-09-01	Pavlov et al.	Applicant
US4621321(A)	1986-11-01	Boebert et al.	Applicant
US4644493(A)	1987-02-01	Chandra et al.	Applicant
US4658093(A)	1987-04-01	Hellman	Applicant
US4713753(A)	1987-12-01	Beobert et al.	Applicant
US4736422(A)	1988-04-01	Mason	Applicant
US4740890(A)	1988-04-01	William	Applicant
US4796220(A)	1989-01-01	Wolfe	Applicant
US4816655(A)	1989-03-01	Musyck et al.	Applicant
US4817140(A)	1989-03-01	Chandra et al.	Applicant
US4827508(A)	1989-05-01	Shear	Applicant
US4868376(A)	1989-09-01	Lessin et al.	Applicant
US4888638(A)	1989-12-01	Bohn	Applicant
US4891838(A)	1990-01-01	Faber	Applicant
US4924378(A)	1990-05-01	Hershey et al.	Applicant
US4932054(A)	1990-06-01	Chou et al.	Applicant
US4937863(A)	1990-06-01	Robert et al.	Applicant
US4949187(A)	1990-08-01	Cohen	Applicant
US4953209(A)	1990-08-01	Ryder et al.	Applicant
US4961142(A)	1990-10-01	Elliott et al.	Applicant
US4975647(A)	1990-12-01	Downer et al.	Applicant
US4977594(A)	1990-12-01	Shear	Applicant
US4999806(A)	1991-03-01	Chernow et al.	Applicant
US5010571(A)	1991-04-01	Katznelson	Applicant
US5014234(A)	1991-05-01	Edwards	Applicant
US5023907(A)	1991-06-01	Johnson et al.	Applicant
US5047928(A)	1991-09-01	Wiedemer	Applicant
US5050213(A)	1991-09-01	Shear	Applicant
US5052040(A)	1991-09-01	Preston et al.	Applicant
US5058164(A)	1991-10-01	Elmer et al.	Applicant
US5103476(A)	1992-04-01	Waite et al.	Applicant
US5113519(A)	1992-05-01	Johnson et al.	Applicant
US5129083(A)	1992-07-01	Cutler et al.	Applicant
US5136643(A)	1992-08-01	Fischer	Applicant
US5138712(A)	1992-08-01	Corbin	Applicant
US5146499(A)	1992-09-01	Geffrotin	Applicant
US5148481(A)	1992-09-01	Abraham et al.	Applicant
US5159182(A)	1992-10-01	Eisele	Applicant
US5174641(A)	1992-12-01	Lim	Applicant
US5183404(A)	1993-02-01	Aldous et al.	Applicant
US5191193(A)	1993-03-01	Le Roux	Applicant
US5204897(A)	1993-04-01	Wyman	Applicant
US5222134(A)	1993-06-01	Waite et al.	Applicant
US5235642(A)	1993-08-01	Wobber et al.	Applicant
US5247575(A)	1993-09-01	Sprague et al.	Applicant
US5255106(A)	1993-10-01	Castro	Applicant
US5260999(A)	1993-11-01	Wyman	Applicant
US5263157(A)	1993-11-01	Janis	Applicant
US5263158(A)	1993-11-01	Janis	Applicant
US5276444(A)	1994-01-01	McNair	Applicant
US5276735(A)	1994-01-01	Boebert et al.	Applicant
US5287408(A)	1994-02-01	Samson	Applicant
US5291596(A)	1994-03-01	Mita	Applicant
US5293422(A)	1994-03-01	Loiacono	Applicant
US5301231(A)	1994-04-01	Abraham et al.	Applicant
US5311591(A)	1994-05-01	Fischer	Applicant
US5319705(A)	1994-06-01	Halter et al.	Applicant
US5335275(A)	1994-08-01	Millar et al.	Applicant
US5337357(A)	1994-08-01	Chou et al.	Applicant
US5339091(A)	1994-08-01	Yamazaki et al.	Applicant
US5341429(A)	1994-08-01	Stringer et al.	Applicant
US5347579(A)	1994-09-01	Blandford	Applicant
US5381526(A)	1995-01-01	Ellson	Applicant
US5386369(A)	1995-01-01	Christiano	Applicant
US5390297(A)	1995-02-01	Barber et al.	Applicant
US5394469(A)	1995-02-01	Nagel et al.	Applicant
US5410598(A)	1995-04-01	Shear	Applicant
US5412717(A)	1995-05-01	Fischer	Applicant
US5414852(A)	1995-05-01	Kramer et al.	Applicant
US5428606(A)	1995-06-01	Moskowitz	Applicant
US5432849(A)	1995-07-01	Johnson et al.	Applicant
US5438508(A)	1995-08-01	Wyman	Applicant
US5444779(A)	1995-08-01	Daniele	Applicant
US5453601(A)	1995-09-01	Rosen	Applicant
US5455953(A)	1995-10-01	Russell	Applicant
US5457746(A)	1995-10-01	Dolphin	Applicant
US5473687(A)	1995-12-01	Lipscomb et al.	Applicant
US5473692(A)	1995-12-01	Davis	Applicant
US5485577(A)	1996-01-01	Eyer et al.	Applicant
US5499298(A)	1996-03-01	Narasimhalu et al.	Applicant
US5502766(A)	1996-03-01	Boebert et al.	Applicant
US5504814(A)	1996-04-01	Miyahara	Applicant
US5504816(A)	1996-04-01	Hamilton et al.	Applicant
US5504818(A)	1996-04-01	Okano	Applicant
US5504837(A)	1996-04-01	Griffeth et al.	Applicant
US5509070(A)	1996-04-01	Schull	Applicant
US5530235(A)	1996-06-01	Stefik et al.	Applicant
US5532920(A)	1996-07-01	Hartrick et al.	Applicant
US5534975(A)	1996-07-01	Stefik et al.	Applicant
US5535276(A)	1996-07-01	Ganesan	Applicant
US5539735(A)	1996-07-01	Moskowitz	Applicant
US5553143(A)	1996-09-01	Ross et al.	Applicant
US5557678(A)	1996-09-01	Ganesan	Applicant
US5563946(A)	1996-10-01	Cooper et al.	Applicant
US5564038(A)	1996-10-01	Grantz et al.	Applicant
US5568552(A)	1996-10-01	Davis	Applicant
US5619570(A)	1997-04-01	Tsutsui	Applicant
US5621797(A)	1997-04-01	Rosen	Applicant
US5625690(A)	1997-04-01	Michel et al.	Applicant
US5629980(A)	1997-05-01	Stefik et al.	Examiner
US5633932(A)	1997-05-01	Davis et al.	Applicant
US5634012(A)	1997-05-01	Stefik et al.	Applicant
US5636346(A)	1997-06-01	Saxe	Applicant
US5638443(A)	1997-06-01	Stefik et al.	Applicant
US5638513(A)	1997-06-01	Ananda	Applicant
US5649013(A)	1997-07-01	Stuckey et al.	Applicant
US5655077(A)	1997-08-01	Jones et al.	Applicant
US5708709(A)	1998-01-01	Rose	Applicant
US5708717(A)	1998-01-01	Alasia	Applicant
US5715403(A)	1998-02-01	Stefik	Applicant
US5734823(A)	1998-03-01	Saigh et al.	Applicant
US5734891(A)	1998-03-01	Saigh	Applicant
US5737413(A)	1998-04-01	Akiyama et al.	Applicant
US5737416(A)	1998-04-01	Cooper et al.	Applicant
US5745569(A)	1998-04-01	Moskowitz et al.	Applicant
US5745879(A)	1998-04-01	Wyman	Applicant
US5748783(A)	1998-05-01	Rhoads	Applicant
US5757907(A)	1998-05-01	Cooper et al.	Applicant
US5761686(A)	1998-06-01	Bloomberg	Applicant
US5764807(A)	1998-06-01	Pearlman et al.	Applicant
US5765152(A)	1998-06-01	Erickson	Applicant
US5768426(A)	1998-06-01	Rhoads	Applicant
US5787172(A)	1998-07-01	Arnold	Applicant
US5790677(A)	1998-08-01	Fox et al.	Applicant
US5812664(A)	1998-09-01	Bernobich et al.	Applicant
US5825876(A)	1998-10-01	Peterson	Applicant
US5825879(A)	1998-10-01	Davis	Applicant
US5825892(A)	1998-10-01	Braudaway et al.	Applicant
US5838792(A)	1998-11-01	Ganesan	Applicant
US5848154(A)	1998-12-01	Nishio et al.	Applicant
US5848378(A)	1998-12-01	Shelton et al.	Applicant
US5850443(A)	1998-12-01	Van Oorschot et al.	Applicant
US5892900(A)	1999-04-01	Ginter et al.	Applicant
US5910987(A)	1999-06-01	Ginter et al.	Applicant
US5915019(A)	1999-06-01	Ginter et al.	Applicant
US5917912(A)	1999-06-01	Ginter et al.	Applicant
US5920861(A)	1999-07-01	Hall et al.	Applicant
US5933498(A)	1999-08-01	Schneck et al.	Applicant
US5940504(A)	1999-08-01	Griswold	Applicant
US5943422(A)	1999-08-01	Van Wie et al.	Applicant
US5949876(A)	1999-09-01	Ginter et al.	Applicant
US5982891(A)	1999-11-01	Ginter et al.	Examiner
US5987134(A)	1999-11-01	Shin et al.	Applicant
US5999624(A)	1999-12-01	Hopkins	Applicant
US5999949(A)	1999-12-01	Crandall	Applicant
US6006332(A)	1999-12-01	Rabne et al.	Applicant
US6020882(A)	2000-02-01	Kinghorn et al.	Applicant
US6047067(A)	2000-04-01	Rosen	Applicant
US6073234(A)	2000-06-01	Kigo et al.	Applicant
US6091777(A)	2000-07-01	Guetz et al.	Applicant
US6112181(A)	2000-08-01	Shear et al.	Applicant
US6112239(A)	2000-08-01	Kenner et al.	Applicant
US6115471(A)	2000-09-01	Oki et al.	Applicant
US6135646(A)	2000-10-01	Kahn et al.	Applicant
US6138119(A)	2000-10-01	Hall et al.	Applicant
US6141754(A)	2000-10-01	Choy	Applicant
US6157719(A)	2000-12-01	Wasilewski et al.	Applicant
US6157721(A)	2000-12-01	Shear et al.	Applicant
US6169976(B1)	2001-01-01	Colosso	Applicant
US6185683(B1)	2001-02-01	Ginter et al.	Applicant
US6189037(B1)	2001-02-01	Adams et al.	Applicant
US6189146(B1)	2001-02-01	Misra et al.	Applicant
US6209092(B1)	2001-03-01	Linnartz	Applicant
US6216112(B1)	2001-04-01	Fuller et al.	Applicant
US6219652(B1)	2001-04-01	Carter et al.	Applicant
US6226618(B1)	2001-05-01	Downs et al.	Examiner
US6233684(B1)	2001-05-01	Stefik et al.	Examiner
US6236971(B1)	2001-05-01	Stefik et al.	Applicant
US6237786(B1)	2001-05-01	Ginter et al.	Applicant
US6240185(B1)	2001-05-01	Van Wie et al.	Applicant
US6253193(B1)	2001-06-01	Ginter et al.	Applicant
US6278781(B1)	2001-08-01	Rhoads	Examiner
US6292569(B1)	2001-09-01	Shear et al.	Applicant
US6301660(B1)	2001-10-01	Benson	Applicant
US6307939(B1)	2001-10-01	Vigarie	Applicant
US6327652(B1)	2001-12-01	England et al.	Applicant
US6330670(B1)	2001-12-01	England et al.	Applicant
US6345256(B1)	2002-02-01	Milsted et al.	Applicant
US6353888(B1)	2002-03-01	Kakehi et al.	Applicant
US6363488(B1)	2002-03-01	Ginter et al.	Applicant
US6389151(B1)	2002-05-01	Carr et al.	Examiner
US6389402(B1)	2002-05-01	Ginter et al.	Applicant
US6397333(B1)	2002-05-01	Söhne et al.	Applicant
US6401211(B1)	2002-06-01	Brezak, Jr. et al.	Applicant
US6405369(B1)	2002-06-01	Tsuria	Applicant
US6424717(B1)	2002-07-01	Pinder et al.	Applicant
US6424947(B1)	2002-07-01	Tsuria et al.	Applicant
US6487659(B1)	2002-11-01	Kigo et al.	Applicant
US6516052(B2)	2003-02-01	Voudouris	Applicant
US6516413(B1)	2003-02-01	Aratani et al.	Applicant
US6519571(B1)	2003-02-01	Guheen et al.	Examiner
US6523745(B1)	2003-02-01	Tamori	Applicant
US6611607(B1)	2003-08-01	Davis et al.	Examiner
US6614914(B1)	2003-09-01	Rhoads et al.	Examiner
US6625780(B1)	2003-09-01	Charbon et al.	Examiner
US6796555(B1)	2004-09-01	Blahut	Applicant
US2001/0009026(A1)	2001-07-01	Terao et al.	Applicant
US2001/0011276(A1)	2001-08-01	Durst, Jr. et al.	Applicant
US2001/0014206(A1)	2001-08-01	Artigalas et al.	Applicant
US2001/0037467(A1)	2001-11-01	O'Toole, Jr. et al.	Applicant
US2001/0039659(A1)	2001-11-01	Simmons et al.	Applicant
US2002/0001387(A1)	2002-01-01	Dillon	Applicant
US2002/0035618(A1)	2002-03-01	Mendez et al.	Applicant
US2002/0044658(A1)	2002-04-01	Wasilewski et al.	Applicant
US2002/0056118(A1)	2002-05-01	Hunter et al.	Applicant
US2002/0069282(A1)	2002-06-01	Reisman	Applicant
US2002/0099948(A1)	2002-07-01	Kocher et al.	Applicant
US2002/0127423(A1)	2002-09-01	Kayanakis	Applicant
US2003/0097567(A1)	2003-05-01	Terao et al.	Applicant
US2004/0052370(A1)	2004-03-01	Katznelson	Applicant
US2004/0172552(A1)	2004-09-01	Boyles et al.	Applicant
BR9810967(A)	2001-10-01		Applicant
EP67556(B1)	1982-12-01		Applicant
EP84441	1983-07-01		Applicant
EP180460	1986-05-01		Applicant
EP257585(A2)	1988-03-01		Applicant
EP262025(A2)	1988-03-01		Applicant
EP332304(A2)	1989-09-01		Applicant
EP332707	1989-09-01		Applicant
EP393806(A2)	1990-10-01		Applicant
EP450841(A2)	1991-10-01		Applicant
EP529261(A2)	1993-03-01		Applicant
EP613073(A1)	1994-08-01		Applicant
EP651554	1995-05-01		Applicant
EP668695	1995-08-01		Applicant
EP678836(A1)	1995-10-01		Applicant
EP679977(A1)	1995-11-01		Applicant
EP715243(A1)	1996-06-01		Applicant
EP715244(A1)	1996-06-01		Applicant
EP715245(A1)	1996-06-01		Applicant
EP725376	1996-08-01		Applicant
EP731404(A1)	1996-09-01		Applicant
EP763936(A2)	1997-03-01		Applicant
EP818748(A2)	1998-01-01		Applicant
EP840194(A2)	1998-05-01		Applicant
EP862318(A2)	1998-09-01		Applicant
EP892521(A2)	1999-01-01		Applicant
EP934765(A1)	1999-08-01		Applicant
EP946022(A2)	1999-09-01		Applicant
EP964572(A1)	1999-12-01		Applicant
EP1103922(A2)	2001-05-01		Applicant
GB1483282	1977-08-01		Applicant
GB2022969(A)	1979-12-01		Applicant
GB2136175	1984-09-01		Applicant
GB2236604	1991-04-01		Applicant
GB2236604(A)	1991-04-01		Applicant
GB2309364(A)	1997-07-01		Applicant
GB2316503(A)	1998-02-01		Applicant
GB2354102(A)	2001-03-01		Applicant
JP62-241061	1987-10-01		Applicant
JP64-068835	1989-03-01		Applicant
JP3063717(A)	1991-03-01		Applicant
JP4-369068	1992-12-01		Applicant
JP5-100939	1993-04-01		Applicant
JP5168039(A2)	1993-07-01		Applicant
JP5-268415	1993-10-01		Applicant
JP6131371(A)	1994-05-01		Applicant
JP6-175794	1994-06-01		Applicant
JP6-215010	1994-08-01		Applicant
JP7-36768	1995-02-01		Applicant
JP7-084852	1995-03-01		Applicant
JP7-200317	1995-08-01		Applicant
JP7-244639	1995-09-01		Applicant
JP715241	1996-06-01		Applicant
JP11031130(A2)	1999-02-01		Applicant
JP11032037(A2)	1999-02-01		Applicant
JP11205306(A2)	1999-07-01		Applicant
JP11215121(A2)	1999-08-01		Applicant
JP2000215165(A2)	2000-08-01		Applicant
JP2005218143(A2)	2005-08-01		Applicant
JP2005253109(A2)	2005-09-01		Applicant
JP2006180562(A2)	2006-07-01		Applicant
WO83/04461(A1)	1983-12-01		Applicant
WO92/20022	1992-11-01		Applicant
WO92/20022(A1)	1992-11-01		Applicant
WO93/01550	1993-01-01		Applicant
WO93/01550(A1)	1993-01-01		Applicant
WO93/11480(A1)	1993-06-01		Applicant
WO94/01821	1994-01-01		Applicant
WO94/03003(A1)	1994-02-01		Applicant
WO96/13814(A1)	1996-05-01		Applicant
WO96/24092	1996-08-01		Applicant
WO96/24092(A2)	1996-08-01		Applicant
WO96/27155(A2)	1996-09-01		Applicant
WO97/25800(A1)	1997-07-01		Applicant
WO97/37492(A1)	1997-10-01		Applicant
WO97/41661(A2)	1997-11-01		Applicant
WO97/43761(A2)	1997-11-01		Applicant
WO97/48203	1997-12-01		Applicant
WO98/09209(A1)	1998-03-01		Applicant
WO98/10561(A1)	1998-03-01		Applicant
WO98/11690	1998-03-01		Applicant
WO98/11690(A1)	1998-03-01		Applicant
WO98/19431(A1)	1998-05-01		Applicant
WO98/42098	1998-09-01		Applicant
WO98/43426(A1)	1998-10-01		Applicant
WO98/45768(A1)	1998-10-01		Applicant
WO99/24928(A2)	1999-05-01		Applicant
WO99/34553(A1)	1999-07-01		Applicant
WO99/35782(A1)	1999-07-01		Applicant
WO99/36876	1999-07-01		Applicant
WO99/48296(A1)	1999-09-01		Applicant
WO99/49615	1999-09-01		Applicant
WO99/60461(A1)	1999-11-01		Applicant
WO99/60750(A2)	1999-11-01		Applicant
WO/04727(A2)	2000-01-01		Applicant
WO/05898(A2)	2000-02-01		Applicant
WO/46994(A1)	2000-08-01		Applicant
WO/59152	2000-10-01		Applicant
WO/59152(A2)	2000-10-01		Applicant
WO/62260(A1)	2000-10-01		Applicant
WO/72118(A1)	2000-11-01		Applicant
WO/73922(A2)	2000-12-01		Applicant
WO1/03044(A1)	2001-01-01		Applicant
WO1/37209(A1)	2001-05-01		Applicant
WO1/63528	2001-08-01		Applicant
WO2004/034223(A2)	2004-04-01		Applicant
WO2004/103843	2004-12-01		Applicant

Non-Patent Literature (71)

Blaze et al, “Divertible Protocols and Atomic Proxy Cryptography” 1998 Advances in Cryptography—Euro Crypt International Conference on the Theory and Application of Crypto Techniques, Springer Verlag, DE.Applicant
Blaze et al, “Atomic Proxy Cryptography” Draft (Online) (Nov. 2, 1997) XP002239619 Retrieved from the Internet.Applicant
No Author, “Capability- and Object-Based Systems Concepts,” Capability-Based Computer Systems, pp. 1-19 (no date).Applicant
Cox, “Superdistribution” Wired Magazine (Sep. 1994) XP002233405 URL:http://www.wired.com/wired/archive/2.09/superdis—pr.html&gt.Applicant
Dunlop et al, Telecommunications Engineering, pp. 346-352 (1984).Applicant
Elgamal, “A Public Key Cryptosystem and a Signature Scheme Based on Discrete Logarithms,” IEEE Transactions on Information Theory IT-31(4):469-472 (Jul. 1985).Applicant
Gheorghiu et al., “Authorization for Metacomputing Applications” (no date).Applicant
Iannella, ed., Open Digital Rights Language (ODRL), pp. 1-31 (Nov. 21, 2000).Applicant
Kahle, wais.concepts.txt, Wide Area Information Server Concepts, Thinking Machines Version 4, Draft, pp. 1-18 (Nov. 3, 1989).Applicant
Kahn, “Deposit, Registration and Recordation in an Electronic Copyright Management System,” Technical Report, Corporation for National Research Initiatives, Reston, Virginia (Aug. 1992) URL:http://www.cni.org/docs/ima.ip-workshop/kahn.html.Applicant
Kahn et al, “The Digital Library Project, vol. 1: The World of Knowbots (Draft), An Open Architecture for a Digital Library System and a Plan for its Development,” Corporation for National Research Initiatives, pp. 1-48 (Mar. 1988).Applicant
Kohl et al, Network Working Group Request for Comments: 1510, pp. 1-112 (Sep. 1993).Applicant
Lee et al, CDMA Systems Engineering Handbook (1998) [excerpts but not all pages numbered].Applicant
Mambo et al, “Protection of Data and Delegated Keys in Digital Distribution,” Information Security and Privacy. Second Australian Conference, ACISP '97 Proceedings, pp. 271-282 (Sydney, NSW, Australia, Jul. 7-9, 1997, 1997 Berlin, Germany, Springer-Verlag, Germany), XP008016393 ISBN: 3-540-63232-8.Applicant
Mambo et al, “Proxy Cryptosystems: Delegation of the Power to Decrypt Ciphertexts,”, IEICE Trans. Fundamentals vol. E80-A, No. 1:54-63 (Jan. 1997) XP00742245 ISSN: 0916-8508.Applicant
Microsoft Word, Users Guide, Version 6.0, pp. 487-489, 549-555, 560-564, 572-575, 599-613, 616-631 (1993).Applicant
Ojanperä and Prasad, eds., Wideband CDMA for Third Generation Mobile Communications (1998) [excerpts but not all pages numbered].Applicant
Perritt, “Knowbots, Permissions Headers and Contract Law,” Paper for the Conference on Technological Strategies for Protecting Intellectual Property in the Networked Multimedia Environment, pp. 1-22 (Apr. 2-3, 1993 with revisions of Apr. 30, 1993).Applicant
Raggett, (Hewlett Packard), “HTML+(Hypertext markup language),” pp. 1-31 (Jul. 12, 1993) URL:http://citeseer.ist.psu.edu/correct/340709.Applicant
Samuelson et al, “Intellectual Property Rights for Digital Library and Hypertext Publishing Systems: An Analysis of Xanadu,” Hypertext '91 Proceedings, pp. 39-50 (Dec. 1991).Applicant
No Author, “Softlock Services Introduces . . . Softlock Services” Press Release (Jan. 28, 1994).Applicant
No Author, “Appendix III—Compatibility with HTML,” No Title, pp. 30-31 (no date).Applicant
No Editor, No Title, Dictionary pages, pp. 469-472, 593-594 (no date).Applicant
Benoit, Digital Television MPEG-1, MPEG-2 and Principles of the DVB System, pp. 75-80, 116-121 (no date).Applicant
Benoit, Digital Television MPEG-1, MPEG-2 and Principles of the DVB System, 2nd edition, pp. 74-80 (no date).Applicant
AH Digital Audio and Video Series, “DTV Receivers and Measurements,” Understanding Digital Terrestrial Broadcasting, pp. 159-164 (no date).Applicant
O'Driscoll, The Essential Guide to Digital Set-Top Boxes and Interactive TV, pp. 6-24 (no date).Applicant
Ius Mentis, “The ElGamal Public Key System,” pp. 1-2 (Oct. 1, 2005) online at http://www.iusmentis.com/technology/encryption/elgamal/.Applicant
Schneier, “Crypto Bibliography,” Index of Crypto Papers Available Online, pp. 1-2 (online) (no date).Applicant
No Author, No Title, pp. 344-355 (no date).Applicant
No Author, “Part Four Networks,” No Title, pp. 639-714 (no date).Applicant
Microsoft Word User's Guide, pp. 773-774, 315-316, 487-489, 561-564, 744, 624-633 (1993).Applicant
No Author, “What is the ElGamal Cryptosystem,” p. 1 (Nov. 27, 2006) online at http://www.x5.net/faqs/crypto/q29.html.Applicant
Johnson et al., “A Secure Distributed Capability Based System,” ACM, pp. 392-402 (1985).Applicant
Wikipedia, “El Gamal Encyption,” pp. 1-3 (last modified Nov. 2, 2006) online at http://en.wikipedia.org/wiki/ElGamal—encryption.Applicant
Blaze, “Atomic Proxy Cryptography,” p. 1 Abstract (Oct. 20, 1998).Applicant
Blaze, “Matt Blaze's Technical Papers,” pp. 1-6 (last updated Aug. 6, 2006).Applicant
Online Search Results for “inverted file”, “inverted index” from www.techweb.com, www.cryer.co.uk, computing-dictionary.thefreedictionary.com, www.nist.gov, en.wikipedia.org, www.cni.org, www.tiscali.co.uk (Jul. 15-16, 2006).Applicant
Corporation for National Research Initiatives, “Digital Object Architecture Project,” http://www.nnri.reston.va.us/doa.html (updated Nov. 28, 2006).Applicant
Stefik, Summary and Analysis of A13 (Kahn, Robert E and Vinton G Cerf, “The Digital Library Project, vol. 1: The World of Knowbots (Draft), An Open Architecture for a Digital Library System and a Plan for its Development,” Corporation for National Research Initiatives (Mar. 1988)), pp. 1-25 (May 30, 2007).Applicant
Johnson et al., “A Secure Distributed Capability Based System,” Proceedings of the 1985 ACM Annual Conference on the Range of Computing: Mid-80's Perspective: Mid-80's Perspective Association for Computing Machinery pp. 392-402 (1985).Applicant
European Search Report Dated Dec. 22, 2003.Applicant
“National Semiconductor and EPR Partner for Information Metering/Data Security Cards” Mar. 4, 1994, Press Release from Electronic Publishing Resources, Inc.Applicant
Weber, R., “Digital Rights Management Technology” Oct. 1995.Applicant
Flasche, U. et al., “Decentralized Processing of Documents”, pp. 119-131, 1986, Comput. & Graphics, vol. 10, No. 2.Applicant
Mori, R. et al., “Superdistribution: The Concept and the Architecture”, pp. 1133-1146, 1990, The Transactions of.Applicant
Weber, R., “Metering Technologies for Digital Intellectual Property”, pp. 1-29, Oct. 1994, A Report to the International Federation of Reproduction Rights Organizations.Applicant
Clark, P.C. et al., “Bits: A Smartcard protected Operating System”, pp. 66-70 and 94, Nov. 1994, Communications of the ACM, vol. 37, No. 11.Applicant
Ross, P.E., “Data Guard”, pp. 101, Jun. 6, 1994, Forbes.Applicant
Saigh, W.K., “Knowledge is Sacred”, 1992, Video Pocket/Page Reader Systems, Ltd.Applicant
Kahn, R.E., “Deposit, Registration and Recordation in an Electronic Copyright Management System”, pp. 1-19, Aug. 1992, Corporation for National Research Initiatives, Virginia.Applicant
Hilts, P. et al., “Books While U Wait”, pp. 48-50, Jan. 3, 1994, Publishers Weekly.Applicant
Strattner, A, “Cash Register on a Chip may Revolutionize Software Pricing and Distribution; Wave Systems Corp.”, pp. 62, Apr. 1994, Computer Shopper, vol. 14, No. 4, ISSN 0886-0556.Applicant
O'Conner, M., “New Distribution Option for Electronic Publishers; iOpener Data Encryption and Metering System for CD-ROM use; Column”, pp. 134, Mar. 1994, CD-ROM Professional, vol. 7, No. 2, ISSN: 1409-0833.Applicant
Willett, S., “Metered PCs: Is Your System Watching You? Wave System beta tests new technology”, pp. 84, May 2, 1994, InfoWorld.Applicant
Linn, R., “Copyright and Information Services in the Context of the National Research and Education Network”, pp. 9-20, Jan. 1994, IMA Intellectual Property Project Proceedings, vol. 1, Issue 1.Applicant
Perrit, Jr., H., “Permission Headers and Contract Law”, pp. 27-48, Jan. 1994, IMA Intellectual Property Project Proceedings, vol. 1, Issue 1.Applicant
Upthegrove, L., “Intellectual Property Header Descriptors: A Dynamic Approach”, pp. 63-66, Jan. 1994, IMA Intellectual Property Proceedings, vol. 1, Issue 1.Applicant
Sirbu, M., “Internet Billing Service Design and prototype Implementation”, pp. 67-80, Jan. 1994, IMA Intellectual Property Project Proceedings, vol. 1, Issue 1.Applicant
Simmel, S. et al., “Metering and Licensing of Resources: Kala's General Purpose Approach”, pp. 81-110, Jan. 1994, IMA Intellectual Property Project Proceedings, vol. 1, Issue 1.Applicant
Kahn, R., “Deposit, Registration and Recordation in an Electronic Copyright Management System”, pp. 111-120, Jan. 1994, IMA Intellectual Property Project Proceedings, vol. 1, Issue 1.Applicant
Tygar, J. et al., “Dyad: A System for Using Physically Secure Coprocessors”, pp. 121-152, Jan. 1994, IMA Intellectual Property Project Proceedings, vol. 1, Issue 1.Applicant
Griswold, G., “A Method for Protecting Copyright on Networks”, pp. 169-178, Jan. 1994, IMA Intellectual Property Project Proceedings, vol. 1, Issue 1.Applicant
Nelson, T., “A Publishing and Royalty Model for Networked Documents”, pp. 257-259, Jan. 1994, IMA Intellectual Property Project Proceedings, vol. 1, Issue 1.Applicant
Robinson, E., “Redefining Mobile Computing”, pp. 238-240, 247-248 and 252, Jul. 1993, PC Computing.Applicant
Abadi, M. et al., “Authentication and Delegation with Smart-cards”, 1990, Research Report DEC Systems Research Center.Applicant
Mark Stefik, “Letting Loose the Light: Igniting Commerce in Electronic Publication”, pp. 219-253, 1996, Internet Dreams: Archetypes, Myths, and Metaphors, IDSN 0-262-19373-6.Applicant
Mark Stefik, “Letting Loose the Light: Igniting Commerce in Electronic Publication”, pp. 2-35, Feb. 8, 1995, Internet Dreams: Archetypes, Myths and Metaphors.Applicant
Henry H. Perritt, Jr., “Technological Strategies for Protecting Intellectual Property in the Networked Multmedia Enviroment”, Apr. 2-3, 1993, Knowbots, Permissions Headers & Contract Law.Applicant
Delaigle, “Digital Watermarking,” Spie Conference in Optical Security and Counterfeit Deterrence Techniques, San Jose, CA (Feb. 1996).Applicant
Perritt, “Technologies Strategies for Protecting Intellectual Property in the Networked Multimedia Environment,” Knowbots, Permissions Headers and Contract Law (Apr. 2-3, 1993).Applicant

Abstract