WO2002050760A1 - Structure fonctionnelle pour application de commerce audio/video - Google Patents

Structure fonctionnelle pour application de commerce audio/video Download PDF

Info

Publication number
WO2002050760A1
WO2002050760A1 PCT/US2001/049395 US0149395W WO0250760A1 WO 2002050760 A1 WO2002050760 A1 WO 2002050760A1 US 0149395 W US0149395 W US 0149395W WO 0250760 A1 WO0250760 A1 WO 0250760A1
Authority
WO
WIPO (PCT)
Prior art keywords
content
identifier
watermark
message
payload
Prior art date
Application number
PCT/US2001/049395
Other languages
English (en)
Inventor
Kenneth L. Levy
R. Stephen Hiatt
Geoffrey B. Rhoads
Original Assignee
Digimarc Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US10/017,679 external-priority patent/US20030056103A1/en
Application filed by Digimarc Corporation filed Critical Digimarc Corporation
Priority to AU2002235231A priority Critical patent/AU2002235231A1/en
Publication of WO2002050760A1 publication Critical patent/WO2002050760A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N7/00—Television systems
    • H04N7/16—Analogue secrecy systems; Analogue subscription systems
    • H04N7/173—Analogue secrecy systems; Analogue subscription systems with two-way working, e.g. subscriber sending a programme selection signal
    • H04N7/17309—Transmission or handling of upstream communications
    • H04N7/17318—Direct or substantially direct transmission and handling of requests
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/10—Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM]
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06T—IMAGE DATA PROCESSING OR GENERATION, IN GENERAL
    • G06T1/00—General purpose image data processing
    • G06T1/0021—Image watermarking
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
    • H04N21/234—Processing of video elementary streams, e.g. splicing of video streams or manipulating encoded video stream scene graphs
    • H04N21/2343—Processing of video elementary streams, e.g. splicing of video streams or manipulating encoded video stream scene graphs involving reformatting operations of video signals for distribution or compliance with end-user requests or end-user device requirements
    • H04N21/234327—Processing of video elementary streams, e.g. splicing of video streams or manipulating encoded video stream scene graphs involving reformatting operations of video signals for distribution or compliance with end-user requests or end-user device requirements by decomposing into layers, e.g. base layer and one or more enhancement layers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/25—Management operations performed by the server for facilitating the content distribution or administrating data related to end-users or client devices, e.g. end-user or client device authentication, learning user preferences for recommending movies
    • H04N21/254—Management at additional data server, e.g. shopping server, rights management server
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/25—Management operations performed by the server for facilitating the content distribution or administrating data related to end-users or client devices, e.g. end-user or client device authentication, learning user preferences for recommending movies
    • H04N21/254—Management at additional data server, e.g. shopping server, rights management server
    • H04N21/2541—Rights Management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/43—Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
    • H04N21/442—Monitoring of processes or resources, e.g. detecting the failure of a recording device, monitoring the downstream bandwidth, the number of times a movie has been viewed, the storage space available from the internal hard disk
    • H04N21/44204—Monitoring of content usage, e.g. the number of times a movie has been viewed, copied or the amount which has been watched
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client 
    • H04N21/63—Control signaling related to video distribution between client, server and network components; Network processes for video distribution between server and clients or between remote clients, e.g. transmitting basic layer and enhancement layers over different transmission paths, setting up a peer-to-peer communication via Internet between remote STB's; Communication protocols; Addressing
    • H04N21/633—Control signals issued by server directed to the network components or client
    • H04N21/6332—Control signals issued by server directed to the network components or client directed to client
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client 
    • H04N21/65—Transmission of management data between client and server
    • H04N21/658—Transmission by the client directed to the server
    • H04N21/6582—Data stored in the client, e.g. viewing habits, hardware capabilities, credit card number
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/80—Generation or processing of content or additional data by content creator independently of the distribution process; Content per se
    • H04N21/83—Generation or processing of protective or descriptive data associated with content; Content structuring
    • H04N21/835—Generation of protective data, e.g. certificates
    • H04N21/8352—Generation of protective data, e.g. certificates involving content or source identification data, e.g. Unique Material Identifier [UMID]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/80—Generation or processing of content or additional data by content creator independently of the distribution process; Content per se
    • H04N21/83—Generation or processing of protective or descriptive data associated with content; Content structuring
    • H04N21/835—Generation of protective data, e.g. certificates
    • H04N21/8358—Generation of protective data, e.g. certificates involving watermark
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/80—Generation or processing of content or additional data by content creator independently of the distribution process; Content per se
    • H04N21/85—Assembly of content; Generation of multimedia applications
    • H04N21/854—Content authoring
    • H04N21/8543—Content authoring using a description language, e.g. Multimedia and Hypermedia information coding Expert Group [MHEG], eXtensible Markup Language [XML]
    • G—PHYSICS
    • G11—INFORMATION STORAGE
    • G11B—INFORMATION STORAGE BASED ON RELATIVE MOVEMENT BETWEEN RECORD CARRIER AND TRANSDUCER
    • G11B20/00—Signal processing not specific to the method of recording or reproducing; Circuits therefor
    • G11B20/00086—Circuits for prevention of unauthorised reproduction or copying, e.g. piracy
    • G—PHYSICS
    • G11—INFORMATION STORAGE
    • G11B—INFORMATION STORAGE BASED ON RELATIVE MOVEMENT BETWEEN RECORD CARRIER AND TRANSDUCER
    • G11B20/00—Signal processing not specific to the method of recording or reproducing; Circuits therefor
    • G11B20/00086—Circuits for prevention of unauthorised reproduction or copying, e.g. piracy
    • G11B20/00884—Circuits for prevention of unauthorised reproduction or copying, e.g. piracy involving a watermark, i.e. a barely perceptible transformation of the original data which can nevertheless be recognised by an algorithm

Definitions

  • AudioNideo Commerce Application Architectural Framework is an exemplary foundation for a variety of audio and video watermarking applications. These applications may be conceptualized as falling into three classes:
  • Audio/Video commerce applications can further be categorized into one of two categories - Local or Connected. These categories are overlapping because some applications may include aspects of both categories.
  • Local applications such as copy/play control, need to locally interpret a watermark and apply the desired action (e.g., "Do Not Copy”).
  • Connected applications such as broadcast monitoring, copyright communication, forensic tracking, content monitoring, asset management, and connected e-commerce, need to connect to a remote entity, e.g., a Central Server and Database, to understand how to fully respond.
  • This framework does not rely on a particular watermarking technology. Indeed, it is contemplated that different types of watermarks may be applied to different objects.
  • object identification may be conveyed by means other than watermark, e.g., header data or separately represented meta data. Standardization of certain ofthe data thereby conveyed, however, allow the architecture to support a wide variety of systems.
  • the reader may ask, why not embed the link directly as a watermark or metadata?
  • the answer is that it is more flexible to embed an ID, and use a secondary database to link that ID to some external information, such as a URL.
  • the secondary database can easily allow links to be updated and dynamically changed depending on the situation. For example, different links may be provided depending on whether the consumer is using a PC or PDA, or if they are linking from an image on their desktop or within an image editor, such as Adobe Photoshop.
  • the secondary database can allow information to be displayed without an associated link.
  • This ID configuration also greatly reduces the number of bits being used. This is critical for watermarks because watermarking is a tradeoff of embedded bit capacity, computational performance, imperceptibility, reliability and robustness. When using non-compliant editors, watermarks stick to the content during format changes or operations, such as open and save, with non-compliant editors. Thus, they are more robust than metadata, and can be used to provide content protection.
  • the Local Application can be enhanced when the system is connected.
  • the Local Application may only know that the content is adult content, but after connecting to a Central Server with a content ID, the server can provide a complete rating scheme.
  • Fig. 1 is a block diagram showing a connected application's system overview.
  • Fig. 2 is a block diagram showing a connected application's linking stage.
  • Fig. 3 illustrates standard interfaces for the linking stage.
  • Fig. 4 illustrates a standard interfaces information relationship.
  • Fig. 5 illustrates potential usage models for audio/video commerce.
  • Fig. 6 is a diagram illustrating various watermark tradeoffs.
  • Fig. 7 illustrates the standard interfaces with a connected-content response highlighted.
  • Fig. 8 illustrates the standard interfaces with a connected-content message highlighted.
  • Fig. 9 illustrates the standard interfaces with an application message highlighted.
  • Fig. 10 illustrates the standard interfaces with a watermark payload highlighted.
  • Fig. 11 illustrates the standard interfaces with a watermark protocol highlighted.
  • Digimarc has two Connected Applications products on the market, Digimarc MediaBridge and Image Commerce.
  • Digimarc's two Connected Applications use Digimarc's central system, sometimes called Digimarc Grand Central.
  • Digimarc Grand Central Most importantly, this central system is designed to be open, such that other vendors can use the system to link their embedded IDs via their proprietary Product Handlers.
  • the central Internet server has one location, it can include linked and globally located central systems. (As such, the term “the Central Servers” is used to refer to all ofthe linked central Internet servers, and the term “a Central Server” is used to refer to one of these central Internet servers.
  • the terms Product Handler, Central Router, and Central Database are used similarly.
  • Digimarc MediaBridge currently enables content-providers and owners to embed watermarks into printed media, such as ads, editorial images and packaging.
  • This process enables the consumer to connect directly to the content owner's web page by showing the ad, editorial image or packaging to a standard PC video camera.
  • This web page can be deep inside the content owner's web site. The user can go directly to a specific web page without having to remember a long URL that is printed on the image.
  • the consumer can be presented with a choice of places to go, including places for unbiased information or to purchase an item.
  • the framework should take into account that content can change format. For example, CD or DND- Audio can be ripped into MP3 or AAC. A movie sound track can also be converted to MP3. Similarly, a video freeze frame can be saved as a still image. • Applicable to universal watermark readers
  • the watermark should survive the following format changes for audio, as shown in Table 5:
  • FIG. 7 A connected content response is illustrated in Fig. 7.
  • the Connected-Content Response is the interface that defines the response of a Central Server to the watermark reader or separate application.
  • the Connected-Content Response interface is simple. It includes a success code and URL or error code and associated text.
  • An example is in Appendix A: Connected-Content Response
  • the multiple links are presented to the consumer for his/her choice after the Connected-Content Message is processed.
  • the list of links could include a link for unbiased information, a link to purchase the product at the users preferred online stores, and a link to the owner's web page.
  • the Central Servers use an open interface to receive request packets and to send response to the originating user.
  • the XML header is a simple structure that includes the:
  • Primary and Secondary information may change by request code, but in general conform to the definitions below.
  • the Request Code instructs the Product Handler to take a specified action. It is mandatory within the Product Information.
  • the Primary Information portion contains the data required to properly service the request. The Primary Information varies based on the Request Code.
  • the Secondary Information is intended for aggregate usage monitoring and reporting, engineering analysis.
  • Personal data about the user may be used for detailed usage monitoring and to obtain user specific connected-content responses. Because Secondary Information may contain private information, the tags and data are only sent if allowed by the consumer. If consumers allow personal data to be gathered, they should receive a benefit for providing this information.
  • the Primary Information needed currently includes:
  • Aggregate usage monitoring is an auto response system. Aggregate usage monitoring does not actually require the sending of personal information. It only requires connected-content messages to be sent without the user's input. As such, aggregate usage monitoring may be an option presented to the consumer, separate from secondary information. Once again, the consumer should receive benefits for allowing this action, and be informed that no personal information is being transmitted. Once again, if this approach is taken, the secondary tags should not even be sent, thus reducing any chance of raising privacy issues.
  • Secondary Information includes:
  • a Central Server may determine some ofthe following:
  • the Application Message is the interface that defines the message sent from the watermark reader to the rendering application, if one exists, and/or included within the Connected-Content Message. It includes the information from the Watermark Payload and additional related information available from the watermark reader. It is only one component ofthe Connected-Content Message.
  • Application Message fields are shells for the Watermark Payload, and all ofthe bits in the Application Message field are not embedded!
  • This format provides maximum flexibility and extensibilities.
  • Third party vendors can register new Application Message type with the Central Servers and Databases and produce proprietary format as long as the format includes an initial 16-bit message type. However, it is optimal if their format can fit into existing types, preferably type 4. Application message types' 128 to 255 are reserved for future uses.
  • Examples of type 2 applications are: Broadcast Monitoring, Copyright Communication, Copy/Play Control, File Verification, Content Monitoring, Asset Management, Forensic Tracking and Connected e-Commerce.
  • Examples of type 3 applications are for Distributors using Broadcast Monitoring, Copyright Communication, Copy/Play Control, File Verification, Content Monitoring, Asset Management, Forensic Tracking and Connected e-Commerce.
  • This interface is defined to enable all current audio/video commerce watermarking applications and possibly future applications. It also enables potential streaming applications by providing the number of information bits following the message type.
  • IDs equal to 0 mean the field is not being used, i.e. not valid.
  • the CMC bits are designed to indicate whether the bits are used, possibly with a value of 0, or not used.
  • Application Message type 4 is the preferred type since it can accommodate all watermarking applications and clients.
  • Type 4 applications include all AudioNideo Commerce Watermarking Applications.
  • This interface is compliant with the proposed European Broadcast Union (EBU) system. It demonstrates how easy this framework adapts to other systems. This is one example of a message type that is compliant, and many others could easily be designed and registered, or this message type can be changed if the EBU changes its format. Refer to Section 6.6 for a detailed demonstration.
  • EBU European Broadcast Union
  • All Application Message types include CMC bits for local copy control as well as connected copyright issues. Although it is expected that local copy control issues will be handled by a special copy control watermark, these CMC bits are optional and extend beyond DVD CPTWG or SDMI copy control. The adult bit is used to identify, and filter (if desired) adult content. Finally, copy protection and connected applications may merge in the future; thus, we have defined types to enable this merger.
  • a C language implementation is shown in Appendix C: Example Application Message C-Class.
  • Content-Owner IDs and Distributor IDs are globally unique. Third party vendors may be required to use these IDs; thus, they will be unique across third party vendors.
  • the object IDs are not globally unique, but unique to each client ID (i.e. Content-Owner ID or Distributor ID).
  • This usage model is advantageous because fewer bits have to be embedded than needed if object IDs were globally unique.
  • This model also enables the central servers to forward the information to client servers, which can interpret the object IDs, with only the registration ofthe client ID.
  • the disadvantage is that content is uniquely identified by a pair of IDs rather than with one ID. As long as applications are aware and respect this fact, this disadvantage is minimal.
  • this framework enables the choice of re-using object IDs or not when a new Watermark Payload version is implemented.
  • a new Watermark Payload version probably means that a new Watermark Protocol has been developed.
  • This Watermark Protocol is more robust with higher embedded bit capacities. At that time, the choice between re-using object IDs or not can be made depending on how much the new bit capacities have increased.
  • third party vendors should use global Content-Owner IDs and Distributor IDs. As such, the system will make sure that content owners only have one ID across all vendors. This means that if the vendor is using a proprietary registration handler, the Central Systems will have to handle the Content-Owner ID registrations.
  • Object IDs can identify the content, the content and its format, and/or a transaction, such as a sale of to the content.
  • These object IDs can be inte ⁇ reted by a Central Server (a.k.a. public) or a client server (a.k.a. private).
  • a private object ID does not mean that the ID cannot be read, but that the central or public system does not know how to interpret the ID, and should forward it to one ofthe client's servers.
  • Fig. 10 illustrates standard interfaces for a watermark payload.
  • the first layer ofthe EBU system requires 64 embedded bits and locks the system to 32k local agencies.
  • the framework detailed herein defines a different lower level Watermark Payload and Protocol that can handle all ofthe requirements ofthe EBU with the advantage of allowing 1 million client systems to be linked and only requires 51 bits to be embedded.
  • Our payload structure can be used in both a public key and private key system (defined below).
  • the inventive payload structure and/or layering is used with a centralized router and database, e.g., to facilitate video/audio watermark ID registration and reporting.
  • a content ID is a number or identifier that uniquely identifies an item of content.
  • Content items include audio and video, although the concepts in this section can be extended to images and other data.
  • the content owner's name is maintained in a related database under, e.g., a Content ID database entry.
  • Database Links content ID to content owner and distributor ID to content aggregator (including Networks) or service provider for broadcast video, as well as distributor or retailer for recorded media.
  • Content owner or distributor can track use of their content over the Internet
  • Database Links content ID to content owner
  • Watermark Payload Content ED, and possibly Distributor ED
  • Watermark Payload Content ED, and possibly Distributor ED
  • a preferable environment for our payload is an architecture that includes unique content IDs, such that a central router knows a content owner's name (or other identifier, such as an account) and/or knows an EP address to link to a database (e.g., a central or distributed database) to retrieve the content owner's name or other information.
  • This architecture allows content owners to exchange content with minimal changes to the system and no changes to the watermark payload.
  • Our payload works well with an architecture based upon unique content identifiers (e.g., a "Content ID”) such that a central router knows the content owner's name and/or IP address to link to a distributed private database.
  • This architecture allows content owners to buy and sell content with minimal changes to the system and no changes to the watermark payload.
  • a watermark system In a time-independent mode, a watermark system typically embeds a watermark with a payload in the range of 2 - 256 range. Most preferably, the payload is in a range of 16 - 72 bits. (We note that the WaterCast system currently envisions multi-sized payloads, such as 36 and 72-bit payloads.). Choosing, for example, a 36-bit payload allows layering multiple watermarks (or watermark messages) in the same video frame (or audio segment). Layering multiple watermarks as such in a broadcast monitoring environment allows different broadcasters to watermark their content, even if the content has been previously watermarked, without compromising the quality ofthe content. Similarly, distributors can watermark content that they receive from content owners.
  • the time dependent mode is useful for applications where a date/timestamp (DTS) sufficiently identifies content, along with minimal identifiers such as an embedder identifier or a distribution channel ID.
  • DTS date/timestamp
  • the DTS is automatically updated at a predetermined time interval (e.g., every 1 second, etc.) by the embedder once the embedding process starts.).
  • An example payload structure e.g., for a 36-bit time dependent mode, uses a 12-bit DTS field and a 24-bit identifier field.
  • the bit-size can be varied according to different payload capacity and/or to accommodate other payload fields, etc.
  • a layer refers to a watermarking protocol or format (discussed below).
  • the term “layer” may alternatively refer to an embedding session, process, or payload structure.
  • a "message type” (discussed below) is used as a layer or as a layer component.
  • a message type 0 may be embedded by a content owner as layer 0 to identify the content
  • a message type 1 can be embedded by a content distributor as layer 1 to identify the distributor.
  • Layer 1 is typically embedded at a later time, and perhaps with a different protocol, than layer 0.
  • the number of public keys used with an item of content preferably corresponds to the number of layers embedded in the content. For example, in a four-layer example, there are preferably four corresponding public keys. Preferably, the four keys are unique and standardized as layers 1, 2, 3 and 4. An adult key (or bits) can be added to a layer for additional screening and content control. For example, consider the following:
  • the privacy aspect of a private key system can be accomplished with this public key system via a "Privacy Code.”
  • the system's watermark detector will only output the payload for this layer if it has been enabled with the Privacy Code, found in message types 8 to 12 below (section 6.8.6+). If the detector is not enabled to read the watermark, the output of the detector gives no indication that a watermark was found.
  • the related database that acts on the payload can be designed to require authentication before acting upon the payload.
  • Encryption is not used since it would change the payload to a different, but identical, payload each time.
  • a method to overcome this limitation is to use a time-based encryption scheme. The scheme can be rather expensive to implement.
  • a payload message is assumed to include between one (1) and four (4), 36-bit packets. (It should be appreciated, however, that the number of bits, packets, etc. could vary without deviating from the scope ofthe present invention. Hence, the following discussion is given by way of example.).
  • Each payload message is identified as one of many different message types. Each unique message type includes different information, based on the requirements of individual applications. For example, if there is a requirement that an identifier be detected each and every second, message type 0 can be used to carry this identifier. But if a content ED and a distributor ED are needed, for example, then a message type 2 can be used.
  • the number of message types can vary according to the watermark system. Preferably, a system includes enough message types to provide system flexibility and versatility.
  • each packet includes 36-bits.
  • the first packet segment e.g., the first 6-bits, forms the message type and sequence number ofthe packet.
  • the remaining number of bits forms the message (or data) payload.
  • the number of bits per segment is varied in other embodiments.
  • a packet may include 16, 48, 72, 144 or 256 bits, etc., where the respective number of bits is variously allocated to the message type, sequence number and data payload.
  • a generic format for a 36-bit packet is:
  • the detector can know the format ofthe data payload after its first second of detection. As such, if a message type has 3 packets, the detector can detect it in, e.g., 3 seconds (e.g., in the WaterCast system) as opposed to having to wait until the first packet is identified and start from there - which would have taken, on average, 4.5 seconds, if used.
  • 3 seconds e.g., in the WaterCast system
  • Message Type 0 is used in those instances where an ID needs to be detected at given intervals, e.g., once every .5, 1, 3, 5, etc. seconds, and where the content needs to be uniquely identified independent of a broadcaster, distributor, content owner or service provider.
  • watermark message detection/decoding takes a finite amount of processing time. For example, a message may take a minimum of .025 seconds, .5 seconds or 1 second, etc. (In the Watercast system, for example, we understand that detection of this watermark message type should take about 1 second.).
  • the detection interval should be set to allow sufficient detection time.
  • Message Type 1 is preferably used to uniquely identify a distributor content, but when the distributor ED cannot be added at the same time or location as the Content ED.
  • the Distributor ED can refer to the content aggregator (including Networks) or service provider for broadcast video, as well as distributor and retailer for recorded media.
  • This message type can be added as an additional layer and, optionally, in conjunction with Message Type 0. (In the WaterCast system, for example, we understand that detection of this watermark message type should take about 1 second.).
  • Message Type 2 is used when the distributor needs to be identified and an ID registered by the content owner is used to identify the content, but where time is not necessarily of the essence and utilizing the watermarking layers for future use may be required. Both Content and Distributor ID can be embedded at the same time and location. Message Type 2 requires additional processing time due to the dual sequence processing. (We understand that the detection time needed by the WaterCast system for this message should be about 2 seconds.).
  • Message Type 3 is used for broadcast monitoring where a Distributor ID is not needed. Message Type 3 should be used when there is a need for minimizing the use of layers for later watermarking activates. (We understand that the detection time needed by the WaterCast system for this message should be about 2 seconds.). This message type must be created by an embedding platform application since it cannot be used with WaterCast in the time dependent mode. In addition, one-second accuracy can be obtained by checking that a content ID is read in between each DTS payload.
  • Message Type 4 is preferably used for broadcast monitoring where the Content ED is not needed. This message type should be used when there is a need for minimizing the use of layers for later watermarking activates. This watermark requires a minimum of 2 seconds for detection.
  • the embedding platform application can create this message type. (In the WaterCast system, this message type is preferably not used the time dependent mode. In addition, one-second accuracy can be obtained by checking that a content ID is read in between each DTS payload.).
  • the message type can be used in the case where a broadcaster has several outbound feeds that require a DTS associated with each feed.
  • the Distributor ID can be the unique identifier for that feed.
  • Message Type 5 is used for broadcast monitoring where, not only is the Content ED needed, but also the out-bound feed, e.g., distributor ID, ofthe content is needed.
  • This message type should be used when there is a need for minimizing the use of layers for later watermarking activates. (We understand that for use in the WaterCast system, this watermark message type requires about 3 seconds for detection.
  • This message type is preferably created by the embedding platform application since it cannot be used with WaterCast in the time dependent mode. In addition, one-second accuracy can be obtained by checking that a content ID is read in between each DTS payload.).
  • Message Type 6 is used to represent two distributors, one who is sending the content and another who is receiving the content.
  • the first distributor can be the content aggregator and the second distributor could be a service provider.
  • Message Type 6 requires about 2 seconds to detect, but only uses one layer as opposed to using two layers of message type 1.).
  • Message Type 13 is used to uniquely, e.g., forensically, identify the content's rendering equipment or a user account for the content so that illegal used content can be traced via this forensic ID.
  • This message type would be added as an additional layer and in conjunction with Message Type 0. (In a WaterCast environment, this watermark message type takes about 2 seconds to detect, but may be randomly placed throughout the content to increase robustness to collusion attack. Thus, the WaterCast detector may need much more than 1 second of content to find the Forensic ID.).
  • the Forensic Owner ID refers to the owner ofthe private forensic database.
  • the Forensic ID refers to the identification ofthe user. For video systems, this is could be a 32 bit smart-card ID.
  • message types can be variously combined to adequately identify the content, distribution, and usage and/or to convey additional information.
  • message type in this example includes 4 bits, a total of 16 message types can be used. (Of course increasing the message type bit field can expand the total allowable number of message types.).
  • an advertisement is preferably digitally watermarked to include a payload message type 5, defined above, where the distributor ED includes a broadcasting network ID (or broadcaster ID) that broadcasts the advertisement.
  • a watermark detector uses the content ID to obtain the content title and content owner via a central router and database. Of course the database can be local with respect to the detector, or can be centralized or distributed. The watermark detector extracts the distributor ED. The database is interrogated with the distributor ED to determine the broadcaster. Extracting a content ED and distributor ID from the Message Type 5 enhances accuracy. These IDs can be used to interrogate the database to retrieve confirming information.
  • the time stamp (DTS) marks an interval of time (e.g., every three seconds of absolute time), and is used by the watermark detector to ensure the correct section or segment ofthe advertisement is played. (A private key functionality can be obtained using message type 12 as described above.).
  • an advertisement can use message type 3 to publicly monitor broadcasts, or message type 10 to privately monitor broadcasts.
  • the system is similar to the message types described above, except that a tuner/receiver that receives the broadcast signal (e.g., a TV signal), and then communicates the signal to a watermark detector, determines the broadcast network ED (e.g., the outbound channel ID) since the tuner knows which station is being monitored.
  • This context data is sent with the content ED and time information to a router for database storage.
  • Another alternative method uses message type 0 and message type 4 as two separate layers for a public system, message type 0 and message type 11 for a public content ID and private DTS and watermark embedder code, or message type 7 and message type 11 for a private broadcast monitoring system. This system is similar to the above alternative, except that a time stamp can be used to confirm accuracy.
  • the system could also use only message type 0 and count each payload for timing information.
  • message type 0 and message type 1 can be combined for a public system or message type 8 for a private system could be used in two layers, and each payload retrieved is counted for timing information.
  • a news segment preferably includes a content ID as a message type 0, e.g., in layer 3.
  • the message type 0 is redundantly embedded throughout a news story to represent the news source such as CNN.
  • a sub-segment of the news story may have a content ID as a message type 0, e.g., in layer 1, to represent a section ofthe news story that is attributable to Reuters.
  • Another, sub-segment ofthe final content may have a content ID as a message type 0, e.g., in layer 2, to represent a section ofthe story attributable to ABC news.
  • a watermark detector working with a central router and database can detect and decode these content IDs and log the usage ofthe news stories such that the correct royalties can be paid. If royalties are based upon amount of usage, the number of content EDs can be counted to determine the time.
  • a message type 3 with DTS can be used to determine or confirm accuracy.
  • a service operator is uniquely identified such that correct information is provided for that service operator based upon its carriage agreements.
  • a message type 0 preferably carries the content ED such that interactive information or a web link to information can be retrieved from a local database residing in (or communicating with) the service provider's head-end.
  • a message type 2 is used and a central router sends the detected watermark payload (or ID) to a remote database that provides corresponding interactive information or Internet.
  • message type 0 could be used in layer 1 to identify the content
  • message type 1 could be used in layer 2 to identify the service provider.
  • This alternative configuration can also be used with a message type 0.
  • the watermark detector possibly located in the head-end or consumer's set-top box, determines the service provider. This context information is sent to the central router and/or related database along with the watermark payload.
  • the EBU has a watermarking infrastructure where: Wl is a 64-bit watermark that identifies content ownership; W2 is a 64-bit watermark that identifies sending and receiving broadcasters; and W3 is a 64-bit watermark that identifies a receiving device.
  • Our inventive payload structure can provide this information with three or four layers of 36 bits (108 bits/sec for 3 layers or 144 bits/sec for 4 layers, respectively) as opposed to three 64-bit as required by EBU (192 bits for 3 layers).
  • our inventive architecture relies upon a central router and ID registration system, whereas the EBU allows for multiple registration authorities. Note that private and secure remote databases can be supported with the central router.
  • Watermark Wl can be represented by a content ID embedded using message type 0 in layer 1.
  • Watermark W2 can be represented with a distributor ED for the content provider embedded in message type 1 in layer 2, and a distributor ID for the content provider embedded in message type 1 in layer 3.
  • both distributor IDs can be embedded in layer 2 via message type 6.
  • Watermark W3 can represented with a Forensic ID embedded in a message type 13 in layer 3 or 4, depending which distributor message type is used.
  • a central router and related database links the Content ED to the content owner, Distributor EDs to content providers and service providers, appropriately, and a Device ED to a consumer.
  • message type 2 that contains the Content ED and Distributor ID in one layer could be used for layer 1 to satisfy many EBU requirements, while reducing the number of layers to embed to two layers at 72 bps.
  • the other layer would be the Forensic ID as message type 2 in layer 2.
  • any or all ofthe private message types could be substituted for the corresponding public message type for a semi- or completely- private system.
  • this public payload architecture enables EBU functionality with many fewer watermarked bits.
  • the privacy code allows the watermark payload to be read, but the privacy code may block the detector from sending the payload to the wrong party.
  • a pirate detector where the pirate has obtained the secret watermarking key and algorithm, could obtain the payload.
  • sequence number is randomized for a private Content ID. This is acceptible since the whole payload needs to be read before being decrypted, and, as such, sequence information will not speed the detection.
  • the signature ofthe content ID helps guarantee that the correct encryption key is used as well as scramble the content ID with more bits. Note that the message type is not encrypted so the system can read the message type and decrypte the content ED and signature.
  • a random packet could be added to each paylaod.
  • Fig. 11 illustrates a standard interface with emphasis on the watermark protocol.
  • the Watermark Protocol is the interface that defines the format ofthe embedded bits after being processed by the watermark algorithm.
  • the watermarking algorithm is the method in which the Watermark Payload is embedded in the content. Some watermarks employ a pseudo-random spreading key and error correction bits.
  • the Watermark Protocol is commonly dependent on the content type, such as audio or video, and its psychophysical characteristics.
  • the Watermark Protocol should, in general, be computationally efficient, robust and imperceptible enough, as defined above. Most importantly, preliminary calculations show that a sample watermark decoder (e.g., the Philips' Watercast system) can read a 32-bit payload using, at most, 24% ofthe Trimedia TM32, and that amount of processing power remains is available in common set top boxes.
  • a sample watermark decoder e.g., the Philips' Watercast system
  • the Watermark Payload types can be combined into one large protocol, or consist of several protocol layers. It appears that embedding and reading two or three watermarks is similar to one larger watermark. If this is true, the layer approach should be used since it has the advantages of allowing more watermark data to be added over time. If a layered approach is not used, content owner usage model C and distributor usage model H are impossible, and the overall system is limited (see Fig. 5).
  • the layers may be added as a transaction occurs (usage model C or H).
  • the Class 1 watermarking applications only require content-owner layers. Then, at a later time, when the technology has evolved such that the distributor layers can be added, the distributor layers can be made available for Class 2 and 3 watermarking applications. This approach is identified in Section 6.5.
  • a Central Server and Database become more useful as more content is registered, assuming it is using standard client IDs and high-level interfaces.
  • the systems should be as open as possible and as easy to use as possible such that other vendors can be licensed to use the system.
  • Vendors may include international organizations, such as EBU or cIDf, or other companies. Such vendors will have rights to use Digimarc's IP and the existing Central Server.
  • the vendor may create and maintain a proprietary Product Handler, use an existing Product Handler, have Digimarc create and maintain an additional Product Handler, or any alternative combination.
  • the third party need only comply with the higher-level framework, including the Connected-Content Response, Connected-Content Message, and Application Message interfaces, preferably using pre-defined types. If the vendor defines a new interface type, they should register it with the Central Servers and Central Databases. In other words, it is not advantageous to leverage the existing system and IP to force other vendors to use a standard Watermark Payload and protocol.
  • the vendor is expected to conform to Digimarc's ID registration specifications and use Digimarc's Central Databases of unique Content-Owner IDs.
  • the vendor is required to conform to the following:
  • UID User 's ID
  • the Connected-Content Response is XML and is formatted as follows.
  • Successful replies include a return code of 1 and the related URL Errors return a code that is less than zero with the error message.
  • the Central Routers support the http protocol.

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Theoretical Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Software Systems (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • Technology Law (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)
  • Editing Of Facsimile Originals (AREA)

Abstract

L'invention concerne une structure fonctionnelle destinée à des applications de commerce audio/vidéo. Dans une réalisation, des types de message sont utilisés dans des applications différentes. Ces applications peuvent conceptuellement être classées en trois catégories: 1) surveillance de diffusion, communication de copyright, commande de copie/lecture, vérification de fichier, et commerce électronique par connexion avec un ordinateur personnel, 2) suivi de procédure, surveillance de contenu, et gestion d'actifs, et 3) commerce électronique par connexion à un décodeur.
PCT/US2001/049395 2000-12-18 2001-12-17 Structure fonctionnelle pour application de commerce audio/video WO2002050760A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU2002235231A AU2002235231A1 (en) 2000-12-18 2001-12-17 Audio/video commerce application architectural framework

Applications Claiming Priority (6)

Application Number Priority Date Filing Date Title
US25662800P 2000-12-18 2000-12-18
US60/256,628 2000-12-18
US33620901P 2001-10-30 2001-10-30
US60/336,209 2001-10-30
US10/017,679 2001-12-13
US10/017,679 US20030056103A1 (en) 2000-12-18 2001-12-13 Audio/video commerce application architectural framework

Publications (1)

Publication Number Publication Date
WO2002050760A1 true WO2002050760A1 (fr) 2002-06-27

Family

ID=27360856

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2001/049395 WO2002050760A1 (fr) 2000-12-18 2001-12-17 Structure fonctionnelle pour application de commerce audio/video

Country Status (2)

Country Link
AU (1) AU2002235231A1 (fr)
WO (1) WO2002050760A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2004097827A2 (fr) * 2003-04-25 2004-11-11 Thomson Licensing S.A. Appareil et procede permettant le marquage judiciaire de supports copies
US10885543B1 (en) 2006-12-29 2021-01-05 The Nielsen Company (Us), Llc Systems and methods to pre-scale media content to facilitate audience measurement

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5956716A (en) * 1995-06-07 1999-09-21 Intervu, Inc. System and method for delivery of video data over a computer network
US6285776B1 (en) * 1994-10-21 2001-09-04 Digimarc Corporation Methods for identifying equipment used in counterfeiting

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6285776B1 (en) * 1994-10-21 2001-09-04 Digimarc Corporation Methods for identifying equipment used in counterfeiting
US5956716A (en) * 1995-06-07 1999-09-21 Intervu, Inc. System and method for delivery of video data over a computer network

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2004097827A2 (fr) * 2003-04-25 2004-11-11 Thomson Licensing S.A. Appareil et procede permettant le marquage judiciaire de supports copies
WO2004097827A3 (fr) * 2003-04-25 2005-02-24 Thomson Licensing Sa Appareil et procede permettant le marquage judiciaire de supports copies
US10885543B1 (en) 2006-12-29 2021-01-05 The Nielsen Company (Us), Llc Systems and methods to pre-scale media content to facilitate audience measurement
US11568439B2 (en) 2006-12-29 2023-01-31 The Nielsen Company (Us), Llc Systems and methods to pre-scale media content to facilitate audience measurement
US11928707B2 (en) 2006-12-29 2024-03-12 The Nielsen Company (Us), Llc Systems and methods to pre-scale media content to facilitate audience measurement

Also Published As

Publication number Publication date
AU2002235231A1 (en) 2002-07-01

Similar Documents

Publication Publication Date Title
US7587601B2 (en) Digital watermarking methods and apparatus for use with audio and video content
US8055899B2 (en) Systems and methods using digital watermarking and identifier extraction to provide promotional opportunities
US8650128B2 (en) Rights management system and methods
EP1515534B1 (fr) Système de filigrane électronique
US6829368B2 (en) Establishing and interacting with on-line media collections using identifiers in media signals
EP2135376A2 (fr) Systèmes et procédés de gestion des droits numériques et de mesure d'audience
US20090129627A1 (en) Digital watermarking systems and methods
AU2007240075A1 (en) Method and apparatus for delivering encoded content
AU5145700A (en) Methods and systems employing digital watermarking in music and other media
JP2004505496A (ja) ウォーターマーキングと信号の固有のシグネチャとを組み合わせることによるマルチメディアの監視
WO2006041233A1 (fr) Systeme et procede de localisation sur la base d'une empreinte digitale de contenus copies illegalement
KR20010097834A (ko) 암호화된 알고리즘을 이용하여 실시간으로디지털워터마킹을 하는 시스템 및 그 방법
US7058608B1 (en) Copyright information management system
Augot et al. Secure delivery of images over open networks
CN100571121C (zh) 无线数字版权管理系统中的盗版跟踪和识别方法
JP4987978B2 (ja) デジタルフィンガープリンティングを用いたデジタルコンテンツ供給システム
KR100773963B1 (ko) 핑거프린팅 관리 시스템 및 핑거프린트 코드 전달 방법
WO2002050760A1 (fr) Structure fonctionnelle pour application de commerce audio/video
JP2002297541A (ja) 不正利用通知方法、不正利用通知装置および不正利用通知プログラム
JP2004110277A (ja) コンテンツ配信管理方法、装置、およびプログラム
KR101808817B1 (ko) 디지털 콘텐츠 포렌식마킹 장치 및 그 방법
US20220046332A1 (en) System and method for automatic detection and reporting of group watermarking data
JP2007520098A (ja) 破損型デジタルコンテンツ生成及び修復装置及び方法
EP1071289A2 (fr) Géneration de filigrane dans des flux de données
WO2001013642A1 (fr) Filigranage de trains de donnees a des niveaux de distribution multiples

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ OM PH PL PT RO RU SD SE SG SI SK SL TJ TM TN TR TT TZ UA UG US UZ VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
121 Ep: the epo has been informed by wipo that ep was designated in this application
REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase

Ref country code: JP

WWW Wipo information: withdrawn in national office

Country of ref document: JP