Venue based digital rights using capture device with digital watermarking capability

Description

FIELD OF THE INVENTION

Aspects of the presently disclosed technology generally pertain to the control of digital rights management (DRM) for captured digital media, including video, photo, and audio content. More particularly, features and steps are provided to enable a controlling entity such as a venue, performer, rights manager, etc. to control rights to digital media that was captured in conjunction with an event by one or more third parties, such as event attendees.

BACKGROUND OF THE INVENTION

Copyright laws protect original expressions including performances captured in audio and visual form. The proliferation of digital technology, such as computers and the internet, has introduced a myriad of challenges to rights holders, since the use of digital technology allows for exact copies of media to be made without degradation. For instance, an image obtained using a capture device such as a digital still camera or digital video camera may be copied an infinite number of times by a theoretically infinite number of persons. If any such copying is unauthorized, rights holders may have legal recourse, but may face tremendous difficulty in tracing and proving the extent of such unauthorized copying.

The proliferation of digital technology also affects rights holders with respect to live performances. For instance, the ever-increasing ubiquity of digital cameras creates a point of conflict for rights holders, such as performers or venue management authorities. Specifically, concert goers are accustomed to taking digital photographs of themselves and their surroundings using digital cameras and the like. However, in a concert setting, such cameras could be used to capture content which is owned by, e.g., the performer. Therefore, generally speaking, most venues and performers prohibit attendees at a performance from even bringing a content capture device such as a digital camera into the venue. Even if the venue or performer wished to grant the attendee a limited right to use his capture device, due to the innate nature of digital content, the venue or performer would have no guarantee that the attendees would honor any such limits.

In response to the challenges posed by the proliferation of digital content capture and management devices, various digital rights management (DRM) schemes and techniques have been developed. For example, different DRM implementations include, but are not limited to, Microsoft Windows Media DRM, Open Mobile Alliance DRM, Open MG (Sony), Fair Play (i.e. Apple iTunes), and the MPEG 21 rights expression language and rights data dictionary. These and other DRM implementations may be used to render content in a DRM-compatible format. However, rendering content in a DRM-compatible form may require additional steps and coordination that content owners may wish to avoid in certain circumstances.

Another known technique used in the field of content protection is watermarking. Watermarking comprises placing additional data in the same bits comprising content data. Various watermarking schemes have been proposed in which the watermark does not noticeably degrade the quality of the content when present. Furthermore, such watermarking schemes may be implemented in a manner that the quality of the content is severely degraded if the watermark is removed.

The use of watermarks in the context of identifying digital rights has been disclosed. For example, U.S. Patent Application Publication No. 2005/0286736 (Rhoads) includes discussion of the use of a database registry from which the identity of a rights holder for a copyrighted work may be ascertained by decoding information placed in the content by the rights holder. For instance, at a concert, audio may be identification coded before it drives concert hall speakers with the result that unauthorized recordings of the concert can be traced to a particular place and time.

It would be desirable for a venue or other rights holder to be able to implement a DRM policy or DRM policies with regard to content that is captured by third parties unaffiliated with the rights holder, such as concert attendees, without the need for the rights holder to resort to watermarking or otherwise including data in the content. Furthermore, it would be desirable to track content to a particular source in the event of a violation of DRM policies, or for other purposes.

SUMMARY OF THE INVENTION

A method of ensuring compliance with a DRM policy can comprise registering at least one capture device prior to presenting protectable content. Registering can include obtaining identification data associated with the device, such as a device ID. The method can further include storing time interval data identifying the time that the content was provided. A publicly-accessible copyright policy database may be made available, including copyright and/or rights policies for particular events, associated with time interval data and device identification identifying specific devices. The capture device or devices may be configured to embed identification data and time of capture data and all content captured by the devices. For instance, the device may include its ID number and the time that the content was captured. Registering can include verifying that the person registering the capture device agrees with a copyright policy and storing a record of such agreement. Registering can also include verifying the integrity of the device after content has been captured by the device. For example, the date and time accuracy of the device may be checked, as well as the integrity of the device's watermarking configuration. Data may be embedded into content in a variety of ways, including by watermarking the content files. If content is provided at a venue, information identifying the device may be obtained prior to allowing the device to enter the venue.

In some embodiments, the exemplary method above may further comprise a step of verifying the integrity of the device prior to allowing the device to enter the venue, including ensuring the device is capable of embedding data into content at the time of capture and ensuring that the date and time of the device are accurate within acceptable tolerances. Device identification data may be obtained during the process of providing a ticket to a venue attendee. The database may be configured to provide copyright status data, including accessing a copyright policy in response to a query identifying a device and at least a time interval. The method may include providing a DRM implementation application, the application including computer readable instructions that direct a computing device to access data embedded in content, such as by reading a watermark, the data including a unique identifier identifying the device that captured the content and capture time data that identifies when the content was captured. The DRM implementation application may further include instructions to direct a computing device to access a copyright policy database by sending a query including data identifying the device that captured the content and data indicating when the content was captured. The implementation application may then provide an indication of the copyright status of the content.

An exemplary method of ensuring the protection of digital content can include accessing data associated with at least one file that includes digital content, based upon the access data, determining the identity of the device that captured the content and when the content was captured, and querying a copyright policy database, including sending data identifying the device and the time when the content was captured.

An exemplary method of device registration in a DRM compliance system can comprise obtaining data from a capture device, the data including information uniquely identifying the device and the device's internal date and time. The device may be verified to ensure that it is compliant in accordance with DRM system requirements. Verification may include determining if the device is capable of embedding data into content at the time the content is captured and determining if the internal date and time of the device is accurate within acceptable tolerances. Registering can further include adding information identifying the device to a copyright policy database, including associating the added information with data identifying at least one time interval and at least one copyright policy. Prior to adding information identifying the device to the database, a copy of the copyright policy may be provided in human-readable form, for acknowledgement by a device user. The acknowledgement may be stored and associated with the identification information. Verifying that the device is compliant may include accessing device attributes directly or indirectly by checking a manufacturer's database.

An exemplary system for ensuring third-party compliance with DRM policies can comprise at least one capture device, with each capture device having a unique identifier and each device being capable of embedding data into content at the time of capture. The system may include at least one copyright policy database, the database associating at least one device, at least one time interval, and at least one copyright policy with one another. The system may include a rights compliance computer application, with the computer application configured to obtain data associated with digital content, the data including identification data and time data identifying a device that captured the content and the time the content was captured. The application may access the copyright policy database by providing the device identifier and time data. The devices may be configured to embed data by watermarking content, with each watermark including a unique identifier for the capturing device and the time that the content was captured.

An exemplary computer software product for use in a DRM compliance system can include instructions rendered in a computer-readable medium to direct a computing device to access data associated with at least one content file, and determine, based on the data, data identifying the device that captured the content in the file and the time at which the content was captured by the device. The instructions can further direct a computing device to query a rights management database using the identification and capture time data, and to receive copyright policy data associated with the content. Based on the copyright policy data, the application may determine the copyright status of the content.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

A full and enabling disclosure, including the best mode of practicing the appended claims, directed to one of ordinary skill in the art, is set forth more particularly in the remainder of the specification, which makes reference to the appended figures, in which:

FIG. 1 illustrates an exemplary system for copyright compliance documentation;

FIG. 2 is a block diagram generally illustrating various components and functional capabilities of an exemplary digital content capture device;

FIG. 3 provides an exemplary flowchart showing steps in a venue security check scenario for situations in which a device is not pre-registered;

FIG. 4 shows an exemplary flowchart of a pre-registration process for a content capture device;

FIG. 5 provides an exemplary illustration of a venue pre-performance security check for a content capture device; and

FIG. 6 provides an exemplary flowchart showing a venue security check for a content capture device that is intended to generally occur after an event.

Use of like reference numerals in different features is intended to illustrate like or analogous components.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

Reference will now be made in detail to various and alternative exemplary embodiments and to the accompanying drawings, with like numerals representing substantially identical structural elements. Each example is provided by way of explanation, and not as a limitation. In fact, it will be apparent to those skilled in the art that modifications and variations can be made without departing from the scope or spirit of the disclosure and claims. For instance, features illustrated or described as part of one embodiment may be used on another embodiment to yield a still further embodiment. Thus, it is intended that the instant disclosure includes modifications and variations as come within the scope of the appended claims and their equivalents

The technology discussed herein makes reference to servers, databases, software applications, and other computer-based systems, as well as actions taken and information sent to and from such systems. One of ordinary skill in the art will recognize the inherent flexibility of computer-based systems allows for a great variety of possible configurations, combinations, and divisions of tasks and functionality between and among components. For instance, server processes discussed herein may be implemented using a single server or multiple servers working in combination. Databases and applications may be implemented on a single system or distributed across multiple systems. Distributed components may operate sequentially or in parallel. When data is obtained or accessed between a first and second computer system or component thereof, the actual data may travel between the systems directly or indirectly. For example, if a first computer accesses a file from a second computer, the access may involve one or more intermediary computers, proxies, and the like. The actual file may move between the computers, or one computer may provide a pointer or metafile that the second computer uses to access the actual data from a computer other than the first computer.

The various computer systems discussed herein are not limited to any particular hardware architecture or configuration. Any suitable programming, scripting, or other type of language or combinations of languages may be used to implement the teachings contained herein.

FIG. 1 illustrates an exemplary system for copyright compliance documentation. User 10 utilizes content capture device 12 to capture content C₀. Content C₁ is denoted with the subscript to indicate content in an unprotected form, as opposed to content in a protected form, which is denoted as C₁. Content capture device 12 may comprise any suitable device capable of capturing audio and/or visual information, such as a digital camera or digital video camera. The system requires that the content capture device be capable of embedding data into content generated using the device in a way such the data cannot be removed without severely degrading or altering the content. For example, the content capture device 12 may be configured to include a digital watermark in images captured by the device.

Any suitable watermarking technology may be used. Capture device 12 is discussed in examples herein as being a still or video camera. However, one of ordinary skill in the art will appreciate that capture device 12 may encompass any suitable device capable of fixing content in a tangible medium. The content can include visual, audio, spatial, and any other physical phenomena that may be sensed and digitally recorded.

The systems and methods disclosed herein are not dependent upon the particular hardware, software, or other implementations of capture device features, so long as the capture device: (1) is capable of watermarking or otherwise encoding data into content at the time of capture, the data including an identifier of the device and the time of capture of the content; (2) maintains data which can be used to differentiate content captured by the device; and (3) maintains data uniquely identifying the device in a manner that such identification data may be accessed. It should be appreciated that although content is described herein as being differentiated on the basis of time of capture and/or a content counter maintained by the device, other ways of uniquely identifying content may be utilized.

Referring still to FIG. 1, when the attendee enters the venue or other location from which content will be recorded, the venue records information identifying the device, such as at a security check 24, and stores the information, such as in venue event database 22. The device identification may be associated with a rights policy, such as the illustrated event DRM policy, and copyright policy records may be thereby created, each record linking one or more particular devices to a time range and a copyright policy. The records may be stored in one or more databases 20, for example a publicly accessible copyright policy distributed database. For example, one database may store records including device IDs, one or more time intervals, and a copyright policy identifier, with a second database storing copyright policies accessible by identifiers.

User 10 may store the protected content C₁ in any suitable storage medium, indicated as a computer at 14 (and including memory or disk space as associated with such computer), from which the user may access and share the content, generally denoted as 16. Remote or distributed storage, such as via a network server or on a portable player may be used in addition to or instead of a local PC or other computer.

Parties who have received the content may verify or otherwise obtain information about the copyright status of the content by accessing the database 20. For instance, a publication that receives an image that the publication wishes to use may access the device ID and the time of capture by decoding the watermark, and then access the copyright policy database. If the publication discovers that the distribution of the content is restricted, the publication may thereby avoid liability for copyright infringement by declining to publicize the picture. Alternatively, if a rights holder obtains a copy of content from an unauthorized source, the rights holder may have documentation of the user's agreement not to redistribute the content. If, however, the user has redistributed the content, the rights holder may be able to bring action against the user not only for copyright violations, but for breach of contract, which may, under certain circumstances, be an easier way for the rights holders to recover.

FIG. 2 is a block diagram illustrating the watermarking or other data encoding capabilities of the content capture device 12. As raw image data is captured, digital watermarks are added prior to compression, storage, and other manipulation on the device. For instance, content captured by charge-coupled device (CCD) sensors 30 is compressed and watermarked by compression and watermarking circuitry and/or routine 31. The device may maintain a number of publicly-accessible data tags, such as tags 38A, 38B, and 38C, which denote the device's real time clock, device ID, and an incremental content ID, respectively. The device may be configured to include the device ID and clock data in each image or other content file generated and stored by storage capability 34. Device 12 may further include circuits and routines to allow for compressed and watermarked images to be downloaded, such as is indicated at 36, to content storage area 14.

Watermarking may be a native feature of the capture device. However, the systems and methods disclosed herein are suitable for use with devices that are modified to include watermarking of content with a unique identifier. For instance, a camera or other device that normally captures content in a non-watermarked form may be upgraded through addition of hardware and/or software modules so that it can capture content and watermark the content at the time of capture.

As a further example, a camera or other capture device may use storage media, with the watermarking, tagging, and other capabilities being implemented at least in part by processing and logic features of the storage media. The storage media could implement the security features (watermarking, unique ID, PINs, etc) discussed in conjunction with capture device 12, which could allow for use of pre-existing capture devices including those initially provided without the presently desired comprehensive security features. In such cases, the “device ID” would be unique to the storage media, and the actual capture device would preferably be configured to interface with the storage media so as to act as a conduit to relay the storage media ID during the registration process. Alternatively, the storage media could be accessed directly during the registration process.

The digital imaging device may further include an interface 32. Interface 32 may comprise any suitable type of port, or a combination of ports. For instance, interface 32 may provide for connectivity when the device is plugged into an IP appliance or other specialized hardware. Alternatively, the interface may support a standard connection, for example, a USB or IEEE 1394 port. The interface may support wireless connectivity, for example, by connections based on IEEE Standard 802.11, Bluetooth, infrared, or other suitable connection methodology. Interface 32 may comprise an RFID tag or interface which allows access to memory on device 14 via an RFID reader.

FIG. 2 also illustrates an exemplary compressed image format where raw (unprotected) content C₀ is interlaced with watermarks including date and time stamp, device ID, and content ID counter to create protected image C₁. Other information that may be maintained by device 12 and may be included in images include data identifying the manufacturer, model number, serial number, date of manufacture, location of manufacturer, firmware revision, and date of last firmware or feature revision for the capture device.

FIG. 3 provides an exemplary flowchart showing steps in a venue security check scenario for situations in which a device is not pre-registered. At step 102, a content capture device is entered into a security check prior to entering the venue or other area at which content will be provided. At step 104, the security checkpoint electronically reads the device ID and current date and time, as well as any other additional information. This information may be accessed from the device via any suitable interface, including the wired and wireless interfaces discussed in conjunction with interface 32 of FIG. 2. At step 106, the device is verified to determine if the device is compliant with the rights protection system. For instance, the watermarking capability of the device may be evaluated, for example, by accessing a device database maintained by the device manufacturer or another group. At step 108, the internal date and time of the device are checked against an external standard to determine if the date and time are within an acceptable margin. If either the encoding of the device or the date and time are insufficient, at step 116 the device is prohibited from entering the venue. If not, at step 110, the device owner is given a copy of the copyright policy for the event. Furthermore, the registration process may include obtaining an acknowledgement from the device owner that he will comply with the copyright policy. A record of that acknowledgement may be stored and maintained along with information identifying the device. At step 112, the device is allowed to enter the venue, and at step 114, the device ID and date and time range for the copyright policy are registered in one or more databases.

FIG. 4 shows an exemplary flowchart of a pre-registration process as part of an online ticket purchase. At step 200, a user initiates the electronic online ticket purchase. However, one of ordinary skill in the art will note that the pre-registration steps are equally applicable to a separate pre-registration process. At step 202, the user is given the option to pre-register the device and if the user selects “yes”, the user is presented at step 206 with the copyright policy applicable to the event. If the user agrees with the copyright policy, his agreement may be noted, and the pre-registration process obtains the device ID and current date and time at step 208. Other information, such as the present content ID count may also be obtained. Such data may be obtained directly from the capture device through use of a computing device, such as a separate IP appliance, or by interfacing the capture device and the computer through which the user is pre-registering. For instance, any technology suitable for device access via interface 32 may be used, including a wired or wireless interface, such as USB, Bluetooth, IEEE 802.11, IEEE 1344, USB, infrared, and the like. Based on data obtained from the device, at step 210, the pre-registration process determines whether the device meets encoding standards, and whether the date and time of the device is accurate at step 212. If both conditions are met, at 214 the device registration is completed, and in the ticket purchase context, the device is added to the electronic ticket. If any of the conditions are not met, the device is not pre-registered, as shown at step 213.

FIG. 5 provides an exemplary illustration of a security check at a venue. At step 302, the device enters the security check area, such as before entering the venue. At the security check, the venue or rights management personnel electronically obtain the device ID and current date and time, as well as other information, such as the content ID, as indicated at step 304. If the security check is part of the entrance process, the security check may also record the electronic ticket at step 306. At step 308, the registration status of the device is ascertained, and if the device has been pre-registered, the date and time accuracy of the device is verified at step 310. Assuming the device is accurate, it is allowed to enter at step 312, and at step 314 the device ID and content ID are recorded for inclusion in the copyright database. If the device has not been pre-registered the user is asked at step 316 if he wishes to register the device, and if so, at step 318, the pre-registration process is carried out. If the user does not wish to register the device, or if the device does not meet date and time accuracy requirements, step 313 indicates that the device is not allowed in the venue.

FIG. 6 provides an exemplary flowchart showing a venue security check after an event. At step 400, the device is entered into the venue and at step 402 records images inside the venue, and then at step 404 enters the post-performance security check. At step 406, the venue security check electronically obtains the device ID and current date and time, as well as information, such as the unique content ID, of the device. At step 408, the security check determines whether the device ID was recorded during entry, and at step 410 the security checks determines whether the date and time are still accurate within acceptable tolerances. If the device ID was not recorded and/or the time is not accurate, the device enters manual arbitration and verification at step 418, which may include a more detailed examination of the device to ensure that it has not malfunctioned or been subject to tampering. However, if the ID and time pass steps 408 and 410, the security check electronically updates the database at step 412 to indicate how much content was captured, for instance, by using the difference in content ID counts between the time of entry and time of exit. At step 414 the device exits the security check, and at step 416, the venue registers the device ID and content capture data in the copyright database.

Capture devices disclosed herein may support synchronization to a manufacturer server or other entity. For instance, if the manufacturer has implemented different, more effective, watermarking methodology, the device firmware/software could be updated to watermark content using the new methodology. The synchronization process may be achieved by an application running on a computer interfaced to the content capture device. Alternatively, the synchronization process may run on the device itself, provided that the device itself is network-capable. The device could be configured to access a remote computer over the network to supervise the device update process. For example, the device could contact an update server maintained by the manufacturer for periodic firmware updates, in a manner similar to live update services implemented for computer software and cell phone firmware updates. As part of the pre-registration, pre-performance security check, and/or post-performance security check, the device's update status could be verified, for instance, through reference to tags maintained by the device indicating the date/time of last update, and/or by consulting the manufacturer for the last time a device matching the unique ID for the device in question was updated.

Example

The following scenario is set forth for purposes of illustration and example only. In this scenario, a concert event is planned, with opening act performer P₁ and main act performer P₂ performing in succession at venue V, a large arena. Further assume that among the concert attendees are two users U₁ and U₂.

As part of the concert arrangements, P₁ and P₂ arrange for the use of venue V. As part of the arrangement, the performers contract with a Venue DRM compliance provider CP. In this scenario, the VDRM compliance provider CP maintains a distributed copyright policy server. Compliance provider CP may add two events to a venue event database, Event01 corresponding to P₁'s performance, and Event02 corresponding to P₂'s performance. CP may furthermore store the performers' respective preferred copyright policies and use restrictions and associate them with the event identifiers.

Users U₁ and U₂ may both obtain tickets to the event, either from the venue directly or via a ticketing management authority. Compliance provider CP may work with the ticketing authority to coordinate ticketing data, or may handle the ticketing. For example, during the ticketing process, assume both U₁ and U₂ indicate that they wish to bring their respective capture devices C₁ and C₂ to the concert. For this example, assume U₁ wishes to bring digital still camera C₁, while U₂ wishes to bring a video-capable cellular phone C₂. The ticketing authority's web site may direct the users to a site maintained by CP for pre-registering devices.

As part of the registration process, U₁ plugs his camera into an IP appliance (or directly into his PC). The pre-registration server accesses the camera's unique ID, and then consults a manufacturer's database to obtain a read-enable PIN and device-specific PIN. Using such PINs, the pre-registration server may access C₁ to ensure that the firmware is up-to-date and the time is within an acceptable tolerance. Assuming all is well, the C₁'s unique ID is provided to the ticketing authority to be included with U₁'s ticket. U₁ also reads a copyright policy presented to him in a window and clicks that he agrees not to redistribute any images taken during the concert for commercial purposes. The acknowledgement and unique ID are also stored by CP and associated with both Event01 and Event02.

Assume U₂ is at a public internet terminal, and thus has no access to an IP appliance or other connection for the pre-registration process to access C₂. Furthermore, assume that U₂ is indoors, and therefore cannot take advantage of C₂'s cellular connectivity (or assume that CP does not support pre-registration via direct connection to devices). In any event, pre-registration for C₂ fails, and U₂ obtains a “plain” ticket.

U₁ and U₂ then proceed to venue V to attend the concert. Both proceed to a checkpoint for attendees who wish to bring digital capture devices into the performance. U₁, who has pre-registered, provides C₁ for verification. Personnel of venue V or compliance provider CP access C₁ though, for example, C₁'s 802.11(b) capability, and verify that the device ID matches U₁'s ticket and that the device time and configuration are still in compliance. For example, if a firmware update has issued between U₁'s ticket purchase and his attendance at the event, he may be sent to manual arbitration and required to obtain the firmware update before entrance.

U₂, since he has not pre-registered, must complete the pre-registration process at venue V. Fortunately for U₂, the registration terminal and C₂ both have Bluetooth capability, and so he is able to register C₂. Furthermore, C₂ is up-to-date and within date tolerances. U₂ also agrees to the copyright policy, including a provision stating that videos taken during the performance may not be redistributed.

U₁ and U₂ enter the venue. CP updates stored data associated with the device IDs for C₁ and C₂ to note that C₁ and C₂ entered the venue.

Assume that P₁'s performance begins on time. During the performance, U₁ takes pictures of P₁, while U₂ videos portions of the act. Both C₁ and C₂ watermark (or otherwise encode) captured content with data indicating their respective device IDs, as well as with the time of capture.

CP notes the start and end times of the performance for Event01. At this point, CP may be able to publish a copyright policy record for Event01. The record will specify device IDs and the times of performance, plus data indicating the applicable copyright policy (such as permitted and prohibited use and other restrictions). Alternatively, for instance, the policy may specify IDs and simply Event01, with an event database accessible to provide the times and applicable policies.

Assume that there is a significant gap between P₁ and P₂'s performance, since P₂ was late arriving at venue V due to traffic. During the break, U₁ and U₂ take pictures and video of each other with their friends at the arena while waiting. Such pictures and video would also be watermarked. Finally, during P₂'s performance, both users capture stills and videos of P₂. CP notes the actual, not the planned, start time of P₂'s act for Event02. A copyright policy record is again generated, this time for Event02 and associated with device IDs and data defining Event02.

Assume, for this example, that venue V has another event planned for that evening, and so CP does not perform a post-performance security check. U₁ and U₂ go to their respective homes. U₁ connects C₁ to a PC to access the still photos from the concert. The images are downloaded to the PC, for example, under the supervision of a manufacturer-provided download application or operating system capability. U₁ sends a picture of P₁ on stage to his favorite music news website, which offers users a significant bounty for high-quality images of popular performers.

After the concert, U₂ takes advantage of C₂'s cellular connectivity by sending videos taken during the break to several friends who were unable to attend the concert. Eventually, a particularly interesting discussion amongst the friends is widely distributed across the Internet, for example, by e-mail forwarding, due to U₂'s expert cinematography and on-the-fly editing of the discussion.

Some time later, P₁'s representatives discover images of P₁ performing on-stage at the music news website, which promptly shuts down without providing any information as to where the image came from. However, P₁'s representatives are able to download a copy of the image prior to the shutdown, or afterwards from a cached copy of the site. Using a computer software application, P₁'s representatives decode the watermark data included in the image, which turns out to be an image captured by U₁ using C₁. P₁'s representatives (or other rights holder) can thus take legal action, and may use the watermarked data to establish the source of the image, and furthermore may use the record of U₁'s acknowledgement agreeing not to distribute the images.

In variation of the scenario, assume the music news website was more observant of potential copyright issues. Accordingly, the music news website could check the image provided by U₁ for use restrictions by decoding the data watermarked in the image before paying for/reproducing the image. For instance, a search for copyright policies matching the time stamp(s) and device ID associated with the image received from U₁ could lead the music news site to information about the copyright restrictions for the image, and the music news website could avoid liability by not accepting the image.

As for U₂'s popular video, an interested viewer could consult the copyright policy database to determine if any use restrictions are applicable. Since the video falls outside the timeframe of Event01 and Event02, neither P₁'s nor P₂'s restrictions apply. U₂ could conceivably register his own policy for protecting the content he created. Alternatively, a promoter who received the video and became interested in U₂'s apparent videography talent could access the database to track down U₂.

It is appreciated by persons skilled in the art that what has been particularly shown and described above is not meant to be limiting, but instead serves to show and teach various exemplary implementations of the present subject matter. As set forth in the attached claims, the scope of the present invention includes both combinations and sub-combinations of various features discussed herein, along with such variations and modifications as would occur to a person of skill in the art.