US 7,266,704 B2Grant
User-friendly rights management systems and methods
Issue Date:2007-09-04
•21 Claims
•6 Drawing Sheets
Abstract
This application describes methods and systems of performing digital asset management. In one implementation a method of determining whether content should be encrypted when the content is found in an unencrypted form is provided. The unencrypted form of the content includes a digital watermark embedded therein including a message. The method recites: decoding the digital watermark from the encrypted form of the content to obtain the message; based at least in part on the message, determining whether the unencrypted form of the content should be encrypted; and if so decided by the determination, encrypting the unencrypted form of the content. Other implementations and embodiments are provided as well.
Metadata
Assignee
- Digimarc Corporation
Inventor
- Kenneth L. Levy
Application Information
Application Number:US 10/126,921
Filing Date:2002-04-18
Priority Date:2000-12-18
Art Unit:2134
Classifications
IPC:
G06F11/30
Patent Drawings (6 sheets)
Description
Related Application Data
[0001] The present application is a continuation in part of U.S. patent application Ser. No. 10/017,679, filed Dec. 13, 2001 (published as US 2003-0056103 A1) now abandoned. The 10/017,679 application claims the benefit of U.S. Provisional Application Nos. 60/256,628, filed Dec. 18, 2000 and 60/336,209, filed Oct. 30, 2001. The present application also claims the benefit of U.S. patent application Nos. 60/285,514, filed Apr. 20, 2001 and 60/315,569, filed Aug. 28, 2001. Each of the above-mentioned patent applications is herein incorporated by reference.
Technical Field
[0002] The present invention relates to integrating identified content with digital rights management systems. The present invention also relates to multimedia signal processing, such as steganographically encoding auxiliary information into media signals, and decoding the auxiliary information from the media signals.
Background and Summary of the Invention
[0003] As digital content continues to proliferate, management of digital assets becomes an increasingly difficult challenge. The term “content” is broadly defined herein and may include audio, video, images, electronic data, biometric information, graphics and designs, electronic documents, copyrighted materials, software, multimedia content, etc., etc. Sometimes we interchangeably use the term “media” instead of content in this document. Enhancements in computer networking and database technology allow companies to manage large content collections and to make the content available to third parties. While network communication provides a powerful tool to enable a database manager to share content with others, it makes it more difficult to control and track how the content is being used.
[0004] For example, some companies maintain extensive content databases to promote their products. Customers or service providers such as advertising and marketing firms can access this content remotely via an internet, extranet, web site, intranet, LAN, WAN, wireless network or file transfer transactions. Although computer networking telecommunication technology facilitates access, it makes it difficult to ensure that customers and services providers are getting the latest content, and that they are getting accurate and helpful information relating to the content.
[0005] There is a need to enable digital rights management systems to reliably link content with additional, related data—including related content. The terms “link” and “linking” are defined broadly herein to include associating, pointing to, facilitating the access of, linking, connecting or connecting to, revealing a storage address of, and/or facilitating database interrogation, etc. There is also a need for a digital rights management system to reliably link content with related usage billing information. One way to associate content with information about the content is to place the information in a file header or footer. This approach is not terribly attractive because the added information often does not survive file format changes, conversion to the analog domain, and is susceptible to being stripped away, etc. We believe that an improved approach to associate content with related data is to steganographically hide identifying information within the content. One example of steganography is digital watermarking.
[0006] Digital watermarking is the science of encoding physical and electronic objects with plural-bit digital data, in such a manner that the data is essentially hidden from human perception, yet can be recovered by computer analysis. Most commonly, digital watermarking is applied to media such as images, audio signals, and video signals. However, it may also be applied to other types of data, including documents (e.g., through line, word or character shifting), software, multi-dimensional graphics models, and surface textures of objects. In physical objects, the data may be encoded in the form of surface texturing, or printing. Such marking can be detected from optical scan data, e.g., from a scanner, optical reader, input device, digital camera, or web cam. In electronic media (e.g., digital audio or imagery—including video), the data may be encoded as slight variations in sample values. Or if the media is represented in a so-called orthogonal domain (also termed “non-perceptual,” e.g., MPEG, DCT, wavelet, etc.), the data may be encoded as slight variations in quantization values or levels. The assignee's U.S. Pat. Nos. 5,862,260 and 6,122,403, and U.S. application Ser. No. 09/503,881, filed Feb. 14, 2000 (now U.S. Pat. No. 6,614,914), are illustrative of certain digital watermarking technologies. Each of these U.S. patent documents is herein incorporated by reference. A great many other approaches are familiar to those skilled in the art. The artisan is presumed to be familiar with the full range of literature about steganography, data hiding and digital watermarking.
[0007] Digital watermarking systems typically have two primary components: an encoder that embeds the watermark in a host media signal, and a decoder that detects and reads the embedded watermark from a signal suspected of containing a watermark (e.g., a suspect signal). The encoder embeds a watermark by altering the host media signal. For example, the encoder (or embedder) component embeds a watermark by altering data samples of the media content in the spatial, temporal or some other transform domain (e.g., Fourier, Discrete Cosine, Wavelet Transform domains). The decoder component analyzes a suspect signal to detect whether a watermark is present. In applications where the watermark encodes information, the decoder extracts this information from the detected watermark.
[0008] The analysis of the detected data can be accomplished in various known ways. Presently, most steganographic decoding relies on general-purpose microprocessors that are programmed by suitable software instructions to perform the necessary analysis. Other arrangements, such as using dedicated hardware, reprogrammable gate arrays, or other techniques, can of course be used.
[0009] According to one aspect of our invention, a digital watermarking system includes (or communicates with) a secondary component—a database. Such a database preferably includes data related to content. The related data may include, e.g., content owner or copyright information, metadata, usage rights, enhanced or interactive content, and billing information, etc. This related data is preferably organized or linked according to respective content identifiers. For example, if the content includes a song and the related data includes usage rules, then the usage rules can be associated with the song via a content identifier that is unique to the song or to a class of related songs. The database can be stored locally, remotely, or both. The database can also be distributed, with different databases stored in different networks or locations, such as a complete central and mirrored database and local databases including only subsets of the related data on a local computer. Of course our usage of the term database throughout this document is broad enough to include software-based databases, data structures, data records, etc., etc.
[0010] User-friendly digital rights management systems are preferred in our evolving digital and connected world. Many digital rights management systems fail because they focus solely on the content owner's security desires and not on consumer usage. As such, these rights management systems are not acceptable to consumers. A historical example is taken from the software industry in the 1980's, when that industry abandoned copy protection. We have solved some of the failing associated with traditional digital rights management systems. Our inventive user-friendly digital rights management system provides transparent usage models to consumers while protecting the content. In one implementation, a user-friendly rights management system enables consumers to easily purchase content that they want to play or use, as opposed to stopping consumers from using the content. One benefit of our inventive system is that it is now easier for a mass market to purchase content, rather than use illegitimately obtained content.
[0011] In one embodiment of the present invention, a digital watermark embedded within a content item is used to convey a content identifier(s). In a second embodiment, file headers associated with a content item include a content identifier(s). In still another embodiment, both digital watermarks and file headers are used to carry content identifiers. Content identifiers can be linked to related data, such as “usage rights” (or “usage rules”) common in some digital rights management (DRM) systems. (The artisan is presumed familiar with the many DRM systems, a few of which are described in U.S. Pat. Nos. 5,765,152, 5,410,598, 5,943,422, 6,363,488 and 6,330,670. Of course there are many other DRM systems and containers that can be enhanced by the present invention.). These rules typically define the scope of permissible content use, e.g., such as regulating printing, viewing, copying, altering, distributing, selling, etc. Digital watermarks—including a content identifier—can be used for content tracking and data management. In another embodiment, digital watermarks are used in connection with DRM content containers. Another aspect of the invention is a method of performing digital asset management of media content. In even another embodiment the copy protection state (also known as copy control information including copy freely, copy no more, copy never, and/or copy once) can be overridden through linking the identifier to usage rules, if the usage rules allow copy protection information to be overridden, e.g., to enable the sale or distribution of the content. This enables the content owners to be properly paid, and users to share content, instead of merely prohibiting use of the content.
[0012] One aspect of the present invention provides content owners with copy protection security and royalty tracking, and end-users with an easy-to-use system that improves current content distribution methods, such as CD, DVD and VHS. A combination of watermarking and DRM techniques can be employed, where a watermark allows content to leave and be found outside an associated DRM package without harming the security of the system. The watermark identification can link the content to the usage rules, and, optionally, the usage rules can dictate whether the content should be re-packaged into the DRM package if found outside of it. This means that content found outside the DRM package can be purchased and used, as well as re-secured, as opposed to that content being considered illegal and perhaps destroyed. This inventive feature increases the revenue generated from the content. A DRM package is broadly defined and may include an encryption-based format, or a container in which content is securely maintained, etc. Artisans know many DRM packaging techniques, which may be suitably interchanged with the packaging aspect of the present invention. DRM systems help publishers or content owners prevent unauthorized copying, replication, usage or distribution of their software products, either via CD-ROM, via the Internet, transfer, etc. Other DRM systems incorporate encryption, digital signature and license manager technologies, and enable authentication from either a disc, online database, or from a PC hard drive. These technologies can be applied to secure CD-ROM or computer executable files, and to maintain desired control over the distribution of content during its life cycle. A DRM package that allows licensing and reporting provides an ideal rights management system for audio, video and images.
[0013] Still another aspect of the present invention is to provide an efficient distribution chain based on identified content, particularly when combined with our inventive techniques. Yet another aspect of the present invention is linking together databases that are stored and protected by a network of the database owner, and enabling those databases to function as one database via a central router and database.
[0014] Further features, advantages and benefits will become apparent with reference to the following detailed description and drawings.
Brief Description of the Drawings
[0015] FIG. 1 illustrates a flow diagram of a content management process according to one embodiment of the present invention.
[0016] FIG. 2 illustrates a system for enhancing digital content management by identifying content, and linking the content with usage rules or permissions.
[0017] FIG. 3 illustrates an inventive content distribution chain.
[0018] FIG. 4 illustrates a content identifier format.
[0019] FIG. 5 illustrates a database structure for the distribution chain illustrated in FIG. 3 .
[0020] FIG. 6 illustrates an intelligent content distribution system, including linking databases via a central router to enhance efficiency and privacy of metadata.
[0021] FIG. 7 illustrates a content distribution chain including a reporting system and a billing system.
[0022] FIG. 8 illustrates the structure of FIG. 5 , including billing information.
[0023] FIG. 9 demonstrates a distributed database exemplar system.
Detailed Description
Rights Management System
[0024] With reference to FIG. 1 , a rights management system preferably includes four steps. In step S1, content, whether within an encryption package or not, is identified before rendering. (“Rendering” here has its familiar meaning of presenting for visual and/or audible inspection, e.g., on a TV, audio player, etc. Our use of the term “rendering” is broad enough to include transferring, copying and distributing.). Content is preferably identified by steganographically encoding data within the content, such as in the form of a digital watermark. The digital watermark preferably includes a unique content identifier. Content can be alternatively identified via frame and/or segment headers.
[0025] Usage rights are determined in step S2 via linking the content identifier to external data (e.g., data defining the usage rules). In general, usage rules define the scope of permitted use for respective content. Examples of usage rules include the scope of permissible copying, rendering, transferring, altering, playing, viewing, printing, distributing, using, etc. Content identifiers can be used to organize a database that is maintained locally or remotely (e.g., a central usage system). Once extracted from content, an identifier can be then used to interrogate the database to retrieve the usage rules. Content usage is regulated based on its corresponding usage rules.
[0026] Content usage can be tracked via an identifier in step S3. This usage tracking can be used, e.g., for proper billing to the consumer and payment to content owners and providers. Tracking can be incremental or per content item. In one embodiment, each video frame or every nth frame (or audio segment) is uniquely or redundantly identified. Tracking identifiers per frame (or audio segment) allows for a “pay-as-you-go” system, in that a consumer can be billed for only the amount of content they view, access or listen to. In another embodiment, billing is based on a one-time access fee.
[0027] As a fourth and optional step (step S4), if content is found outside of its respective DRM, and it should be in the DRM package as dictated by related usage rules, the content identifier can help facilitate repackaging of the content in a DRM container. Initially, the identifier will help identify the content. The identifier can also identify or point to a specific package or packaging protocol, or the identifier can link to repackaging requirements. An identifier can also be linked to usage rules, which can regulate content usage, even for content outside of a package. Examples of content being located outside of a container include transferring the content to a different medium, or converting from a digital format to an analog format. Since the content identifier is content specific, e.g., it is associated with the content and not the container, it persists with the content, even when the content is found outside of a container.
[0028] The preceding second through fourth steps preferably proceed on the assumption that the content has been packaged in an encryption container (or other DRM format) and digitally watermarked (or otherwise identified) prior or during distribution. Content that is neither protected nor identified can be handled under default system rules, such as allowing unrestricted usage or view-only usage.
[0029] In a preferred implementation, the identifier is provided via a digital watermark, potentially combined with header data for additional access. An advantage of a digital watermark identifier is that the watermark will typically survive end-user recording of the content onto new media or into a new format. This new format may be desirable for end-users to use multiple rendering devices, or used to try to bypass the security system. However, identifying the content itself helps to enforce security features and continue to track content, even when the content is found outside of a DRM container.
[0030] Optionally, the embedded data (e.g., a digital watermark) can provide fine-grain usage and quality of content monitoring as well as copy protection. An example of fine grain usage is to monitor content subsets, such as an audio segment or set of video frames. A watermark can be redundantly embedded per frame or segment, or different watermarks can be embedded per each frame or segment, to allow counting or monitoring of the content subsets.
Home Network System
[0031] A home rights management system 10 is shown in FIG. 2 . System 10 includes a local home network (indicated by the dashed-line box labeled “Home”). The local home network includes a home content server 30 in continuous or intermittent communication with rendering devices 40–42. The operation of our inventive system 10 is preferably indifferent to how content stored on the home content server 30 is initially obtained, and indifferent to whether the content is packaged in an encryption or other DRM package. The system 10 architecture and system 10 operations are described below.
[0032] Home content server 30 can include a personal computer that has downloaded compressed content from a web site or peer-to-peer site via the internet. Alternatively, home content server 30 can be a set-top box (STB) with suitable computing functionality. Or home content server 30 can include a storage device with computing, database and communication functionality. Of course, home content server 30 need not be located in a home, but may be located in an office, building, garage, theater, mobile computer, handheld device, etc.
[0033] Returning to FIG. 2 , system 10 preferably includes and central database 20 and central billing agency 50. Central database 20 and central billing agency 50 can be associated or otherwise communicate (e.g., as shown by the dashed-line box labeled “Internet . . . ” in FIG. 2 ). Of course the invention is not so limited. Indeed, there need not be interaction between database 20 and agency 50. In addition, agency 50 may be contacted only monthly, when, e.g., the home content server 30 reports its monthly usage. Central database 20 can communicate with home center server 30, via a network such as the internet (e.g., via a cable modem, modem or DSL), dial-up network, dedicated network, LAN, WAN, etc. Central database 20 is preferably contacted whenever new content, which was not sent with its usage rules to be stored in a local database such as home content server 30, enters the home network. In another embodiment, central database 20 includes a plurality of distributed databases, which are synchronized or which include specific subsets of content (e.g., based on region, genre, content, etc.). In another embodiment, central database 20 includes a plurality of peer-to-peer nodes. Database management software can be used to help track and manage content, content identifiers, and related content.
[0034] Central database 20 preferably maintains a set of usage rules. The usage rules define use limits for related content. The usage rules can be communicated to various network locations, such as to home content server 30. Home content server 30 can query central database 20 to obtain or update usage rules, or updated rules can be pushed to home content server 30. Server 30 can also cache the usage rules locally, or can occasionally query database 20 to obtain updates, etc.
[0035] Preferably, each of rendering device PC 40, STB/TV (or VCR, PVR or DVD, etc.) 41 and portable player 42 communicates with home content server 30, either continuously or intermittently. In one embodiment, some or all of the rendering devices communicate over a wireless channel. Of course, the invention is not so limited. Indeed, the rendering devices can communicate through other channels as well (e.g., via USB, parallel ports, communication links, EEE 1394, firewires, modems, coaxial cable, twisted pair, etc., etc.). In some implementations server 30 streams content to the rendering devices for real time play. In other implementations server 30 downloads the entire content or subset of the content to the devices. Some rendering devices may be able to decrypt the content (if the content is encrypted or other DRM protected) and detect a content identifier, e.g., an embedded digital watermark. Other rendering devices may rely on the home content server 30 for decryption (if needed) and identifier detection.
[0036] When content playing is requested, a rendering device 40–42 or home content server 30 checks the content item and/or frame headers for an identifier. In one embodiment, checking for an identifier includes a watermark detection process. In another embodiment, checking the content item includes extracting data from a file header. In still another embodiment, checking for an identifier involves both checking header data and detecting an embedded watermark.
[0037] In the case of checking a file header, if an identifier is found, and it is not part of an authenticated encryption package, it is self-authenticated. (This is particularly so when dealing with digital signatures or encryption authentication, etc.). This self-authentication process helps to ensure that the identifier has not been modified, including that it has not been copied from other content.
[0038] If a header identifier is not available or trusted, the content can be searched for a watermark identifier. (Alternatively, in another embodiment, an initial search for a watermark identifier is made.). Watermarks are inherently trusted due to the secrecy of their embedding key and/or self-authentication features. In an alternative embodiment, a so-called fragile watermark is used to enhance the security of an identifier. A fragile watermark can be designed to be lost, or to degrade predictably, when the data set into which it is embedded is processed in some manner. Thus, for example, a fragile watermark may be designed so that if an image is JPEG compressed and then decompressed, the watermark is lost. Or if an image is printed, and subsequently scanned back into digital form, the watermark is corrupted in a foreseeable way. Similarly, if a video or audio signal is converted from digital to analog the fragile watermark is corrupted or altered. (Fragile watermark technology is disclosed, e.g., in commonly assigned application Ser. Nos. 09/234,780, 09/433,104, 09/498,223, 60/198,138, 09/562,516, 09/567,405, 09/625,577, 09/645,779, and No. 60/232,163.). By such arrangements it is possible to infer how a data set has been processed by the attributes of a fragile watermark embedded in the original data set.
[0039] If the content is not identified, the home content server 30 (or rendering device) can handle the content according to a default usage rule or otherwise in a predetermined manner. For example, the server may allow unrestricted usage, or may permit a onetime play with copy restrictions. Alternatively, the home content server 30 may query central database 20 to receive guidance.
[0040] Once the content is identified, however, and the central database 20 provides usage rules associated with the content identifier, the home content server 30 or rendering device 40–42 determines whether, and/or to what extent, the content can be rendered according to the usage rules. The rendering device 40–42 may enforce these rules, or the home content server 30 may enforce them by withholding content from a rendering device 40–42 and 45 that it is not authorized to render the content. Since content is identified by content identifiers (e.g., digital watermark data), content can be tracked, managed, and rendered, even if it has left an encryption package. Indeed, linking an identifier to usage rules helps to ensure that the content can be controlled, even with out an encryption package.
[0041] In another embodiment, embedded data (e.g., watermark data) is extracted and used to determine if the content is even allowed outside an encryption package, and cause any open format content to be encrypted before it is played.
[0042] The identifier can also allow usage (e.g., playing, recoding, transferring, etc.) of the content to be tracked. In one embodiment, the tracking monitors each time that a content item is accessed. In another embodiment, the tracking determines how much of the content item is actually played. For example, if an identifier is continuously embedded throughout the content, either as metadata in frames or as digital watermarks, the identifier can be used to track how much of the content is played (e.g., a digital watermark counter). Further discussion regarding these and other techniques are found in assignee's U.S. patent application Ser. No. 09/574,668, filed May 18, 2000 (now U.S. Pat. No. 6,522,769). Otherwise, frame-counting (or group of frames-counting) techniques can monitor the amount of content usage.
[0043] System 10 can optionally save watermark “bookmarks,” so users can begin playing where they left off. In this case, a watermark identifier can be used to uniquely identify a location, chapter or segment within the content item. An identifier can then be used to index back into the content, much like a conventional bookmark.
[0044] A watermark identifier can also be even used to track quality by checking for degradation of the embedded data, such as through bit errors.
[0045] The home content server 30 can use tracking information (e.g., amount of content played, which content is accessed, types of use, etc.) to interact with a central billing agency 50. Central billing agency 50 can communicate with home content server 30 via the internet or other communications channel.
[0046] Central billing agency 50 can help facilitate billing for content consumed and/or used. Central billing agency 50 can also help ensure that other system participants, including content owners and providers, are properly paid. Optionally, the billing agency can provide information to the consumer about current billing and pricing on content before playing the content.
[0047] If content is not allowed to be played on the local home system or its usage rights are not know, the home content server 30 can obtain rights from central database 20. This process can be facilitated via internet or other communications channel. Alternatively, central or local information linked to an identifier can be used to provide the end-user directions on how to obtain rights. Thus, if content is obtained elsewhere, possibly from a file-sharing network or directly from a friend, the usage rights can be easily obtained from identifier-provided information. (Additional disclosure regarding using embedded data with file sharing can be found in assignee's U.S. patent application Ser. No. 09/620,019, filed Jul. 20, 2000.).
[0048] While the content is being played, the content identifier can be optionally used to provide or link to other information via additional data and links maintained in a content server or central database 20. This information can include new releases by the same artist or director, similar movies or songs, and related merchandise, etc. (U.S. patent application Ser. Nos. 09/620,019 and 09/571,422, filed May 15, 2000, include disclosure regarding linking to other information and actions via embedded data.). In addition, this information may provide opportunities to purchase the described or related items. Additionally, the identifiers can be used to link to interactive content, such as found on a web site.
[0049] A watermark identifier can provide additional advantages, such as providing copy protection bits within the embedded data that can be used to restrict or prohibit distribution (e.g., copying, transferring, rendering, etc.). of content to a format or media that may allow illegal distribution, such as a recordable DVD or CD. For example, home content server 30 may prohibit transfer of content, based on the copy protection bits, to recording device 45. If copy protection bits require that the content cannot be copied, but a content identifier links to usage rights or to a copy permission (either of which indicates permission for re-using or copying the content), the subsequently obtained permission preferably overrides the copy protection bits. In this case, a billing or central router can communicate to the home content server a permission (or updated usage rule) to indicate that the content can be re-used or copied according to permission. Hence, the permission or updated usage rule trumps the copy protection bits. (Of course obtaining the permission can be conditioned on payment or other billing requirements.). For non-DVD video and non-DVD or SDMI audio content, the presence of a specific watermark protocol can identify the content as protected. A fragile watermark can also be added for copy-once (i.e. one generation) capabilities, if desirable. In another embodiment, the presence of the watermark is determined in hardware, without reading the payload bits, thus reducing the cost of the copy control hardware. Then, the watermark payload is decoded in software. (Further discussion regarding copy control bits can be found in assignee's U.S. patent application Ser. No. 09/620,019.).
[0050] Thus, our rights management system is transparent and easy-to-use for the end-user, and allows copyright owners to protect and robustly track their content.
Distribution Chain
[0051] Traditionally, content is sent in a distribution chain from a content owner to a distributor, and then on to a service provider (e.g., a VOD service provider) that may include either (or both) of a cable/satellite operator and online retailer. The content is then provided to a client (e.g., a home consumer). Our distribution chain, e.g., such as a video on demand (VOD) chain, is now described with respect to FIG. 3 .
[0052] The content is preferably uniquely identified. Content can be identified, e.g., by a digital watermark. In some cases the digital watermark includes a unique ID. The unique ID preferably includes at least a content identifier, and may also include a content owner ID, distributor ID, VOD service provider ID and/or a Retailer ID, as shown in FIG. 4 . Of course alternative or additional fields can be used for a unique ID.
[0053] The unique ID and usage rules (e.g., for each of the distributor, operator, retailer, and consumer) are preferably created by the content owner and entered into an ID system. In one embodiment, an owner creates a unique ID by querying an ID system (or database) to obtain a unique identifier. These usage rules (or “rights”) regulate the permissible use by the various distribution chain participants. The usage rules are indexed via the unique ID. The ID system preferably includes a database to help manage the content owner's unique IDs and usage rules and to help ensure that any given ID is not redundantly assigned. Preferably, the unique ID can be read at various participant points in the FIG. 3 distribution chain. The unique ID can be used to determine the usage rules at these various participant points. For example, the Distributor can access the unique ID and query the ID system to retrieve distributor-related usage rules. The ID System may optionally include an authenticated method to identify the participant (e.g., distributor, service provided, consumer). There are many suitable authenticating methods known in the art, e.g., such as providing a user ID, account number, IP address, digital signatures, numeric identifiers, etc. Of course other authenticating methods may be suitably interchanged with this authentication aspect of the present invention. The ID system determines the proper usage rules for a requesting participant and then returns the usage rules to them. The ID system can also return other desired information or links (e.g., URL, IP address, e-mail list, etc.). For example, the ID system may return a link to access information regarding the actors in a subject movie and their new releases. Or the link may relate to a particular audio file or song that is being played by the consumer. If a proprietary player or plug-in to the player is provided by the last member of the chain before the consumer, such as the retailer, the retailer ID does not need to be embedded and can be obtained from the proprietary player. However, if this content is found unpackaged outside the authorized consumer environment, it is advantageous to have the retailer ID as part of the digital watermark unique ID so the retailer's rules can be applied and the retailer is properly paid for that content.
[0054] The ID system can include a master database or a plurality of databases. (Of course the ID system will typically include a computer or server, running database management software, to help manage the database.). Our preferred database format, shown in FIG. 5 , is used when a unique ID includes the ID of the requesting participant (e.g., Distributor ID, retailer ID, etc.) and its related usage rules. With this format, the unique ID identifies the requesting participant. So during a database interogation no additional information, besides the Unique ID, needs to be communicated to the database. The participant verification can be enhanced by using authenticated IDs including encryption and digital signatures, as well as different watermark algorithms (or payload structures) for each participant, where only that participant knows the algorithm. The secret part of the algorithm may vary a pseudo-random (PN) sequence for each participant. This process is also known as secret key watermarking.
[0055] The ID system may be maintained on one or many distributed central servers, as well as being “intelligently” distributed, as shown in FIG. 6 . Intelligent distribution includes storing various unique IDs and usage rules (and optionally related content, e.g., URLs, IP addresses, etc.) on local databases within each participant site of the distribtuion chain shown in FIG. 3 (e.g., in the Distributor Database or the Retailer Database, etc.). Preferably, the locally stored data is relevant only to the local participant. For example, the VOD Operator Database preferably includes only those usage rules that are relevant to the VOD operator. Or the Consumer database includes only those usage rules and related content that are relative to the subject video (or audio) content.
[0056] A content owner creates (for his/her content) unique IDs and usage rules (and optionally related content) for each of the distribution chain participants. In one implementation, a content owner creates a unique ID by query central rounter database to obtain a suitable ID. Of course many content owners (A–C) may create unique IDs and usage rules as shown in FIG. 6 . A central router and database are used to route the usage rules and any related data to a correct distribution chain participant. The central router database preferably only includes content owner IDs and content owner database addresses. In addition, the unique ID and database content is pushed from a content owner database to each other participant, including the consumer for content that she has licensed, through the central router. The database content can include the original content (videos, audio, etc.), usage rules and any related content (e.g., URLs, IP addresses, web pages, etc.). The pushed database content preferably includes only that information which is relevant to a particular participant. The distributor, VOD operator, retailer and consumer databases preferably only include the usage rules for that distributor, VOD operator, retailer and consumer, respectively. Local databases (e.g., the consumer and distributor databases) can be automatcically updated such as hourly, daily, weekly, etc., to remain fresh and up-to-date information. No one database or router needs to include all the content's usage rules, which helps to ensure security for the content. Participants also benefit since they rarely need to request usage rules from the central server because the usage rules for their content are regularly pushed to them. The usage rules can be periodically updated. In the example structure shown in FIG. 5 , the database entries which include that participant's ID and related information are stored in that participant's network and database.
Billing System
[0057] The FIG. 4 unique ID can be used to maintain usage reporting and royalty billing, as shown in FIG. 7 . FIG. 7 shows a centralized Reporting System and a centralized Billing System. Of course these systems can include computers and/or servers, tracking and accounting software executing on the servers and computers, and communications hardware/software, etc. The various participants (e.g., distributor, service provider, consumer, etc.) can be accurately billed for their access and/or handling of content based and tracked according to the unique ID. Of course the various participants can establish accounts with the billing system, to facilitated billing, automatic billing, etc. (In the case of a permission overriding copy protection bits, described above, a consumer can establish an account so that when she requests permission to distribute copy-protected content, the account is automatically billed when the permission to distribute is sent to the consumer.). Usage is preferably reported to the reporting system according to the unique identifiers. Of course, the Reporting Systems and Billing Systems shown in FIG. 7 can be distributed so that each participant keeps track of their own billing similar to the FIG. 6 distributed system.
[0058] Some of the above-mentioned databases are described as including usage rights. These databases can be expanded to include billing information, as shown in FIG. 8 . When the modified data structures are accessed, usage information can be optionally stored in the consumer's home system and updated to central systems to help track usage reporting and royalty billing, as shown in FIG. 7 . The billing and reporting systems do not usually need to receive updates as often as the content usage rules. For example, the billing and reporting systems may be updated from the home system every two weeks or every month or so.
Example
[0059] A distribution chain including a content owner A, VOD operator B, consumer C, and a video D is presented by way of example to illustrate one aspect of the present invention. Related, intelligently distributed databases are show in FIG. 9 , where the central router database is located in mirrored locations for the central router, the content owner A database is located in mirrored locations within the content owner A's network, and the VOD operator B database is located in mirrored locations within the VOD operator B's network.
[0060] For this example we assume that video D includes a digital watermark embedded therein. The digital watermark preferably includes a unique ID that at least uniquely identifies the video as video D. When consumer C wants to watch video D, the consumer's player (or plug-in to the player, or central home server, etc.) decodes the digital watermark to extract the unique ID. The extracted unique ID is communicated to the central database. The central database uses the unique ID to identify a VOD operator B identifier, which is used to locate the VOD operator B's database (or database IP address). The unique ID is also used to locate an owner A identifier (ID), which is used to locate a content owner A's database (or database IP address). (We note that an alternative implementation involves communicating a unique ID, like the one shown in FIG. 4 , which also includes the content owner ID and VOD provider ID. The central database uses the content owner ID and VOD ID to find the appropriate owner and VOD database IP address.). Once found, the content owner A's database provides usage rights for consumer C's usage, and the VOD operator B's database provides the consumer's pricing. Then, consumer C is informed of their rights for viewing and the price of, oh say $4.00 per view, by the player. The consumer can signal acceptance via the player, or viewing the video D can be deemed acceptance of the terms.
[0061] For example, let's now suppose that the consumer C watches the video D one and a half times. The amount of viewing is locally tracked in the player by counting or detecting digital watermarks that are embedded in video frames throughout the video D, e.g., embedded to correspond with 1 second intervals. The player reports the usage (along with the unique ID) to the central router database (or alternatively to the VOD operator B database). The amount owed for this usage, $6.00, can be recorded in the VOD operator billing information. (Of course, we expected that traditional billing methods, e.g., pre-authorization of a credit card or monthly billing, etc., can be used to collect or manage the amount due and can be stored locally until updated, such as to the VOD operator's billing system.). Based upon the unique ID, usage amount, and billing information provided to the content owner A via the VOD operator B, the content owner A is paid its share of the amount owned, e.g., perhaps 50% of the $6.00 (or $3.00).
[0062] Alternatively, a third party or clearinghouse is used for billing and reporting. In this case the player can report the unique ID and usage amount to the third party. Of course it would be beneficial to allow the content owner A access to the third party reporting to understand the amount and type of their content that is used.
Concluding Remarks
[0063] Having described and illustrated the principles of the technology with reference to specific implementations, it will be recognized that the technology can be implemented in many other, different, forms. To provide a comprehensive disclosure without unduly lengthening the specification, applicants herein incorporate by reference the patents and patent applications referenced above.
[0064] The various section headings in this document are provided for the reader's convenience and provide no substantive limitations. Of course, the subject matter under one section can be readily combined with the subject matter under another section.
[0065] The methods, processes, and systems described above may be implemented in hardware, software or a combination of hardware and software. For example, the watermark data encoding processes may be implemented in a programmable computer or a special purpose digital circuit. Similarly, watermark data decoding may be implemented in software, firmware, hardware, or combinations of software, firmware and hardware. The methods and processes described above may be implemented in programs executed from a system's memory (a computer readable medium, such as an electronic, optical or magnetic storage device). Finally, a content owner and content ID can be combined into one content ID which is desirable in situations, such as for audio and video content, where content owners, such as record labels and movie studios, are sold and traded between content groups.
[0066] The particular combinations of elements and features in the above-detailed embodiments are exemplary only; the interchanging and substitution of these teachings with other teachings in this and the incorporated-by-reference patents/applications are also contemplated.
Claims
We claim:
1. A method of repackaging content into an encryption container or digital rights management (DRM) container when the content is found outside of a container, the content comprising a digital watermark embedded therein, the digital watermark including a content identifier, said method comprising:
decoding the digital watermark from the content to obtain the content identifier, the content identifier identifying the content;
providing the content identifier to a database, the database including usage rules associated with the content identifier, the usage rules comprising at least one rule regarding repackaging;
based on the repackaging rule, determining whether the content should be repackaged in at least one of an encryption container and DRM container; and, if indicated by the determination,
packaging the content in at least one of an encryption container and DRM container.
2. A method comprising:
analyzing a content item to determine whether a digital watermark is steganographically embedded therein; and if the digital watermark is detected in the content,
abiding by a usage rule including at least one of an instruction to encrypt and an encryption protocol; and
encrypting the content item according to the usage rule.
3. The method of claim 2 wherein the usage rule is predetermined and a decision to encrypt the content item is dependent on both of the usage rule and an output channel through which the content item will be communicated.
4. The method of claim 3, wherein the output channel comprises a consumer device capable of copying or distributing the content item.
5. The method of claim 4, wherein the device comprises at least one of a compact disc player and digital video disc recorder.
6. The method of claim 2, wherein the instruction to encrypt is dependent on an output channel through which the content item will be communicated.
7. The method of claim 6, wherein the output channel comprises a consumer device capable of copying or distributing the content item.
8. A method comprising:
analyzing a file header associated with a content item to determine whether the header includes an indicator; and if the indicator is detected in the header,
abiding by a usage rule including at least one of an instruction to encrypt and an encryption protocol; and
encrypting the content item according to the usage rule.
9. The method of claim 8 wherein a decision to encrypt the content item is dependent on the usage rule and dependent on an output channel through which the content item will be communicated.
10. The method of claim 9, wherein the output channel comprises a consumer device capable of copying or distributing the content item.
11. The method of claim 8, wherein the instruction to encrypt is dependent on an output channel through which the content item will be communicated.
12. The method of claim 11, wherein the output channel comprises a consumer device capable of copying or distributing the content item.
13. A system for managing a content item comprising:
a system memory; and
electronic processing circuitry in communication with said memory via a communications bus,
wherein said memory includes computer executable software instructions stored therein for execution by said electronic processing circuitry, the software instructions including instructions to:
i) determine whether the content item includes a steganographic identifier embedded therein; and if the content does not include the steganographic identifier,
ii) abide by a default usage rule including at least one of an instruction to encrypt and an encryption protocol; and
iii) encrypt the content item according to the usage rule.
14. The system of claim 13 wherein the steganographic identifier is embedded in the content item in the form of a digital watermark.
15. A method of determining whether content should be encrypted when the content is found in an unencrypted form, wherein the unencrypted form of the content comprises a digital watermark embedded therein, the digital watermark including a message, said method comprising:
decoding the digital watermark from the unencrypted form of the content to obtain the message;
based at least in part on the message, determining whether the unencrypted form of the content should be encrypted, if so decided by the determination,
encrypting the unencrypted form of the content.
16. The method of claim 15, wherein said determining comprises providing at least a portion of the message to a data structure, wherein the data structure includes usage rules with at least one of the usage rules regarding encryption, wherein the at least a portion of the message is used to locate an encryption rule.
17. The method of claim 16, further comprising:
receiving from the data structure the encryption rule, and wherein said encrypting comprises encrypting the unencrypted form of the content according to the encryption rule.
18. The method of claim 15, wherein the message provides an indication of at least one of how the unencrypted from of the content is to be encrypted and an encryption protocol.
19. The method of claim 15, wherein said method is carried out prior to rendering.
20. The method of claim 15, further comprising:
if so decided by the determination that encryption is not warranted,
rendering the unencrypted form of the content.
21. The method of claim 15, wherein the unencrypted form of the content comprises two or more digital watermarks embedded therein.
Patent Citations (157)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US4218738(A) | 1980-08-01 | Matyas et al. | Applicant |
| US4528588(A) | 1985-07-01 | Lofberg | Applicant |
| US4528643(A) | 1985-07-01 | Freeny | Applicant |
| US4807031(A) | 1989-02-01 | Broughton et al. | Applicant |
| US4827508(A) | 1989-05-01 | Shear | Applicant |
| US4888798(A) | 1989-12-01 | Earnest | Applicant |
| US4941175(A) | 1990-07-01 | Enescu et al. | Applicant |
| US4972471(A) | 1990-11-01 | Gross et al. | Applicant |
| US4977594(A) | 1990-12-01 | Shear | Applicant |
| US4999806(A) | 1991-03-01 | Chernow et al. | Applicant |
| US5023907(A) | 1991-06-01 | Johnson et al. | Applicant |
| US5050213(A) | 1991-09-01 | Shear | Applicant |
| US5103476(A) | 1992-04-01 | Waite | Applicant |
| US5113518(A) | 1992-05-01 | Durst et al. | Applicant |
| US5138712(A) | 1992-08-01 | Corbin | Applicant |
| US5182770(A) | 1993-01-01 | Medveczky et al. | Applicant |
| US5319705(A) | 1994-06-01 | Halter | Applicant |
| US5321841(A) | 1994-06-01 | East | Applicant |
| US5410598(A) | 1995-04-01 | Shear | Applicant |
| US5428606(A) | 1995-06-01 | Moskowitz | Applicant |
| US5428731(A) | 1995-06-01 | Powers, III | Applicant |
| US5464997(A) | 1995-11-01 | Watanabe | Applicant |
| US5473692(A) | 1995-12-01 | Davis | Applicant |
| US5495411(A) | 1996-02-01 | Ananda | Applicant |
| US5519778(A) | 1996-05-01 | Leighton | Applicant |
| US5548645(A) | 1996-08-01 | Ananda | Applicant |
| US5553143(A) | 1996-09-01 | Ross et al. | Applicant |
| US5579479(A) | 1996-11-01 | Plum | Applicant |
| US5613004(A) | 1997-03-01 | Cooperman | Applicant |
| US5617119(A) | 1997-04-01 | Briggs et al. | Applicant |
| US5629980(A) | 1997-05-01 | Stefik et al. | Applicant |
| US5634012(A) | 1997-05-01 | Stefik et al. | Applicant |
| US5636276(A) | 1997-06-01 | Brugger | Applicant |
| US5638443(A) | 1997-06-01 | Stefik et al. | Applicant |
| US5646997(A) | 1997-07-01 | Barton | Applicant |
| US5646999(A) | 1997-07-01 | Saito | Applicant |
| US5652714(A) | 1997-07-01 | Peterson et al. | Applicant |
| US5657462(A) | 1997-08-01 | Brouwer et al. | Applicant |
| US5699526(A) | 1997-12-01 | Siefert | Applicant |
| US5715403(A) | 1998-02-01 | Stefik | Applicant |
| US5734119(A) | 1998-03-01 | France et al. | Applicant |
| US5734719(A) | 1998-03-01 | Tseydos | Applicant |
| US5745569(A) | 1998-04-01 | Moskowitz et al. | Applicant |
| US5748956(A) | 1998-05-01 | Lafer | Applicant |
| US5765152(A) | 1998-06-01 | Erickson | Applicant |
| US5765176(A) | 1998-06-01 | Bloomberg et al. | Applicant |
| US5801687(A) | 1998-09-01 | Peterson et al. | Applicant |
| US5822432(A) | 1998-10-01 | Moskowitz et al. | Applicant |
| US5828485(A) | 1998-10-01 | Hewlett | Applicant |
| US5841978(A) | 1998-11-01 | Rhoads | Applicant |
| US5845281(A) | 1998-12-01 | Benson | Applicant |
| US5848424(A) | 1998-12-01 | Scheinkman et al. | Applicant |
| US5850481(A) | 1998-12-01 | Rhoads | Applicant |
| US5852673(A) | 1998-12-01 | Young | Applicant |
| US5862260(A) | 1999-01-01 | Rhoads | Applicant |
| US5892900(A) | 1999-04-01 | Ginter et al. | Applicant |
| US5893218(A) | 1999-04-01 | Hunter et al. | Applicant |
| US5915019(A) | 1999-06-01 | Ginter | Applicant |
| US5917912(A) | 1999-06-01 | Ginter et al. | Applicant |
| US5920861(A) | 1999-07-01 | Hall et al. | Applicant |
| US5920878(A) | 1999-07-01 | DeMont | Applicant |
| US5926822(A) | 1999-07-01 | Garman | Applicant |
| US5940504(A) | 1999-08-01 | Griswold | Applicant |
| US5943422(A) | 1999-08-01 | Van Wie | Applicant |
| US5956716(A) | 1999-09-01 | Kenner et al. | Applicant |
| US5974141(A) | 1999-10-01 | Saito | Applicant |
| US5983218(A) | 1999-11-01 | Syeda-Mahmood | Applicant |
| US5991876(A) | 1999-11-01 | Johnson et al. | Applicant |
| US5995625(A) | 1999-11-01 | Sudia | Applicant |
| US6005858(A) | 1999-12-01 | Fallon et al. | Examiner |
| US6006332(A) | 1999-12-01 | Rabne et al. | Examiner |
| US6122403(A) | 2000-09-01 | Rhoads | Applicant |
| US6141753(A) | 2000-10-01 | Zhao et al. | Examiner |
| US6157721(A) | 2000-12-01 | Shear et al. | Applicant |
| US6185683(B1) | 2001-02-01 | Ginter | Applicant |
| US6226618(B1) | 2001-05-01 | Downs et al. | Applicant |
| US6233684(B1) | 2001-05-01 | Stefik | Applicant |
| US6236971(B1) | 2001-05-01 | Stefik | Applicant |
| US6285776(B1) | 2001-09-01 | Rhoads | Applicant |
| US6301660(B1) | 2001-10-01 | Benson | Applicant |
| US6330670(B1) | 2001-12-01 | England | Applicant |
| US6363488(B1) | 2002-03-01 | Ginter | Applicant |
| US6398245(B1) | 2002-06-01 | Gruse | Applicant |
| US6449367(B2) | 2002-09-01 | Van Wie et al. | Applicant |
| US6519352(B2) | 2003-02-01 | Rhoads | Applicant |
| US6522769(B1) | 2003-02-01 | Rhoads | Applicant |
| US6542927(B2) | 2003-04-01 | Rhoads | Applicant |
| US6574609(B1) | 2003-06-01 | Downs et al. | Applicant |
| US6614914(B1) | 2003-09-01 | Rhoads | Applicant |
| US6618484(B1) | 2003-09-01 | Van Wie et al. | Applicant |
| US6664976(B2) | 2003-12-01 | Lofgren et al. | Applicant |
| US6768808(B2) | 2004-07-01 | Rhoads | Applicant |
| US6785815(B1) | 2004-08-01 | Serret-Avila et al. | Applicant |
| US6786397(B2) | 2004-09-01 | Silverbrook | Applicant |
| US6807534(B1) | 2004-10-01 | Erickson | Applicant |
| US6829368(B2) | 2004-12-01 | Meyer et al. | Applicant |
| US6850252(B1) | 2005-02-01 | Hoffberg | Applicant |
| US6856977(B1) | 2005-02-01 | Adelsbach et al. | Applicant |
| US6898706(B1) | 2005-05-01 | Venkatesan et al. | Applicant |
| US6968455(B2) | 2005-11-01 | Okayasu | Applicant |
| US7035427(B2) | 2006-04-01 | Rhoads | Applicant |
| US7047241(B1) | 2006-05-01 | Erickson | Applicant |
| US7058697(B2) | 2006-06-01 | Rhoads | Applicant |
| US2001/0004736(A1) | 2001-06-01 | Hirano | Applicant |
| US2001/0008557(A1) | 2001-07-01 | Stefik | Applicant |
| US2001/0021144(A1) | 2001-09-01 | Oshima et al. | Applicant |
| US2001/0026618(A1) | 2001-10-01 | Van Wie et al. | Applicant |
| US2001/0032312(A1) | 2001-10-01 | Runje | Applicant |
| US2001/0037378(A1) | 2001-11-01 | Hirayama | Applicant |
| US2001/0042043(A1) | 2001-11-01 | Shear | Applicant |
| US2002/0002468(A1) | 2002-01-01 | Spagna | Applicant |
| US2002/0007456(A1) | 2002-01-01 | Peinado | Applicant |
| US2002/0013772(A1) | 2002-01-01 | Peinado | Applicant |
| US2002/0019814(A1) | 2002-02-01 | Ganesan | Applicant |
| US2002/0019946(A1) | 2002-02-01 | Iwamura | Applicant |
| US2002/0026362(A1) | 2002-02-01 | Tanaka | Applicant |
| US2002/0048369(A1) | 2002-04-01 | Ginter | Applicant |
| US2002/0059238(A1) | 2002-05-01 | Saito | Applicant |
| US2002/0062252(A1) | 2002-05-01 | Van Zoest | Applicant |
| US2002/0064759(A1) | 2002-05-01 | Durbin et al. | Applicant |
| US2002/0065780(A1) | 2002-05-01 | Barritz | Applicant |
| US2002/0069218(A1) | 2002-06-01 | Sull et al. | Applicant |
| US2002/0080969(A1) | 2002-06-01 | Giobbi | Applicant |
| US2002/0082922(A1) | 2002-06-01 | Van Zoest | Applicant |
| US2002/0083005(A1) | 2002-06-01 | Lowenstein | Applicant |
| US2002/0095601(A1) | 2002-07-01 | Hind et al. | Applicant |
| US2002/0106082(A1) | 2002-08-01 | Kori et al. | Applicant |
| US2002/0107803(A1) | 2002-08-01 | Lisanke et al. | Applicant |
| US2002/0108050(A1) | 2002-08-01 | Raley et al. | Applicant |
| US2002/0111878(A1) | 2002-08-01 | Namba | Applicant |
| US2002/0112163(A1) | 2002-08-01 | Ireton | Applicant |
| US2002/0112171(A1) | 2002-08-01 | Ginter | Applicant |
| US2002/0114458(A1) | 2002-08-01 | Belenko | Applicant |
| US2002/0114466(A1) | 2002-08-01 | Tanaka | Applicant |
| US2002/0120515(A1) | 2002-08-01 | Morimoto | Applicant |
| US2002/0124050(A1) | 2002-09-01 | Middeljans | Applicant |
| US2002/0136405(A1) | 2002-09-01 | Hori | Applicant |
| US2002/0141582(A1) | 2002-10-01 | Kocher | Applicant |
| US2002/0141584(A1) | 2002-10-01 | Razdan | Applicant |
| US2002/0144130(A1) | 2002-10-01 | Rosner | Applicant |
| US2002/0164047(A1) | 2002-11-01 | Yuval | Applicant |
| US2002/0194492(A1) | 2002-12-01 | Choi et al. | Applicant |
| US2003/0026421(A1) | 2003-02-01 | Morlet | Applicant |
| US2003/0056103(A1) | 2003-03-01 | Levy et al. | Applicant |
| US2003/0069852(A1) | 2003-04-01 | Bryant | Applicant |
| US2003/0076955(A1) | 2003-04-01 | Alve et al. | Applicant |
| US2003/0077065(A1) | 2003-04-01 | Scholten | Applicant |
| US2003/0078889(A1) | 2003-04-01 | Lee | Applicant |
| US2004/0005093(A1) | 2004-01-01 | Rhoads | Applicant |
| US2004/0148408(A1) | 2004-07-01 | Nadarajah | Applicant |
| US2005/0018873(A1) | 2005-01-01 | Rhoads | Applicant |
| US2005/0065890(A1) | 2005-03-01 | Benaloh | Applicant |
| US2005/0066187(A1) | 2005-03-01 | Peinado | Applicant |
| US2006/0062426(A1) | 2006-03-01 | Levy et al. | Applicant |
| WO2/19589 | 2002-03-01 | Applicant | |
| WO2/37489 | 2002-05-01 | Applicant | |
| WO2/086803 | 2002-10-01 | Applicant |
Non-Patent Literature (24)
- http://www.digimarc.com/media/release.asp?home=news&newsID=521.Examiner
- U.S. Appl. No. 60/256,628, filed Dec. 18, 2000, Levy.Applicant
- U.S. Appl. No. 60/285,514, filed Apr. 20, 2001, Rhoads.Applicant
- U.S. Appl. No. 60/315,569, filed Aug. 28, 2001, Levy.Applicant
- U.S. Appl. No. 60/336,209, filed Dec. 30, 2001, Levy.Applicant
- U.S. Appl. No. 09/571,422, filed May 15, 2000, Rhoads.Applicant
- U.S. Appl. No. 09/620,019, filed Jul 2, 2000, Levy.Applicant
- Choudhury et al., “Copyright Protection for Electronic Publishing Over Computer Networks,” 8302 IEEE Network 9, No. 3 (1995).Applicant
- “Multimedia Mixed Object Envelopes Supporting a Graduated Fee Scheme via Encryption,” IBM Technical Disclosure Bulletin vol. 37, No. 03, pp. 413-417, Mar. 1994.Applicant
- Sibert et al., “DigiBox: A Self-Protecting Container for Information Commerce,” Electronic Publishing Recourses, Inc., originall published in the Proceeding of the First USENIX Workshop on Electronic Commerce, Jul. 1995.Applicant
- Griswold, “A Method of Protecting Copyrights on Networks,” Proc. Technological Strategies for Protecting Intellectual Property in the Networked Multimedia Environment, 1994.Applicant
- Perritt, “Permission Headers and Contract Law,” Proc. Technological Strategies for Protecting Intellectual Property in the Networked Multimedia Environment, 1994.Applicant
- Upthegrove, “Intellectual Property Header Descriptors: A Dynamic Approach,” Proc. Technological Strategies for Protecting Intellectual Property in the Networked Multimedia Environment, 1994.Applicant
- PCT/US01/49395, Notification of Transmittal of International Preliminary Examination Report, dated Nov. 27, 2002.Applicant
- PCT/US01/49395, Notification of Transmittal of The International Search Report or the Declaration and International Search Report, dated May 31, 2002.Applicant
- PCT/US02/12171, Notification of Transmittal of International Preliminary Examination Report, dated Jan. 7, 2004.Applicant
- Program and System Information Protocol for Terrestrial Broadcast and Cable (Revision A) and Amendment No. 1, Advanced Television Systems Committee, Rev. A-May 31, 2000, 135 pages.Applicant
- Amendment No. 3 to Revision A of ATSC Standard: Program and System Information Protocol for Terrestrial Broadcast and Cable, Doc. A/65-(May 31, 2000) (Draft Amendment), Oct. 15, 2001, 4 pages.Applicant
- Perry et al., Progress Report of the Co-Chairs of the Broadcast Protection Discussion Subgroup of the Copy Protection Technical Working Group, Apr. 8, 2002, 6 pages.Applicant
- Protecting Against Unauthorized Redistribution of Digital Broadcast Content, Presentation to the CPTWG Intel, Hitachi, Matsushita, Sony and Toshiba, Nov. 28, 2001, 9 pages.Applicant
- Requirements for the Protection of Unencrypted Digital Terrestrial Broadcast Content Against Unauthorized Redistribution, Discussion Draft, Apr. 14, 2002, 13 pages.Applicant
- Requirements for the Protection of Unencrypted Digital Terrestrial Broadcast Content Against Unauthorized Redistribution, Discussion Draft, Redline version, Apr. 14, 2002, 13 pages.Applicant
- PCT/US01/49395, Written Opinion, dated Aug. 18, 2003 (6 pages).Applicant
- PCT/US02/12171, Written Opinion, dated Aug. 18, 2003 (6 pages).Applicant