WO2020257493A1 - Improved image watermarking - Google Patents
Improved image watermarking Download PDFInfo
- Publication number
- WO2020257493A1 WO2020257493A1 PCT/US2020/038489 US2020038489W WO2020257493A1 WO 2020257493 A1 WO2020257493 A1 WO 2020257493A1 US 2020038489 W US2020038489 W US 2020038489W WO 2020257493 A1 WO2020257493 A1 WO 2020257493A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- image
- screenshot
- string
- metadata associated
- timestamp
- Prior art date
Links
Classifications
-
- 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
-
- 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
- G06T1/005—Robust watermarking, e.g. average attack or collusion attack resistant
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06T—IMAGE DATA PROCESSING OR GENERATION, IN GENERAL
- G06T9/00—Image coding
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N19/00—Methods or arrangements for coding, decoding, compressing or decompressing digital video signals
- H04N19/44—Decoders specially adapted therefor, e.g. video decoders which are asymmetric with respect to the encoder
-
- 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, manipulating MPEG-4 scene graphs
- H04N21/23418—Processing of video elementary streams, e.g. splicing of video streams, manipulating MPEG-4 scene graphs involving operations for analysing video streams, e.g. detecting features or characteristics
-
- 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/238—Interfacing the downstream path of the transmission network, e.g. adapting the transmission rate of a video stream to network bandwidth; Processing of multiplex streams
- H04N21/2389—Multiplex stream processing, e.g. multiplex stream encrypting
- H04N21/23892—Multiplex stream processing, e.g. multiplex stream encrypting involving embedding information at multiplex stream level, e.g. embedding a watermark at packet level
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06T—IMAGE DATA PROCESSING OR GENERATION, IN GENERAL
- G06T2201/00—General purpose image data processing
- G06T2201/005—Image watermarking
- G06T2201/0051—Embedding of the watermark in the spatial domain
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06T—IMAGE DATA PROCESSING OR GENERATION, IN GENERAL
- G06T2201/00—General purpose image data processing
- G06T2201/005—Image watermarking
- G06T2201/0065—Extraction of an embedded watermark; Reliable detection
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06T—IMAGE DATA PROCESSING OR GENERATION, IN GENERAL
- G06T2201/00—General purpose image data processing
- G06T2201/005—Image watermarking
- G06T2201/0083—Image watermarking whereby only watermarked image required at decoder, e.g. source-based, blind, oblivious
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06T—IMAGE DATA PROCESSING OR GENERATION, IN GENERAL
- G06T2201/00—General purpose image data processing
- G06T2201/005—Image watermarking
- G06T2201/0202—Image watermarking whereby the quality of watermarked images is measured; Measuring quality or performance of watermarking methods; Balancing between quality and robustness
Definitions
- Image watermarking is a technique that embeds visually imperceptible data or messages into an image, and may be categorized as non-blind or blind, dependent respectively on whether the original image is necessary for watermark extraction. Blind watermarking is particularly useful in that the embedded data may be recovered without having access to the original pre-embedded image.
- blind image watermarking may have issues with perceptibility (e.g. whether distortion introduced by embedding the watermarking message may be detectable by a viewer), robustness (e.g. the rate of success in a decoder decoding the embedded message), and capacity (e.g. the amount of data or rate that data may be embedded in the image). In many implementations, increasing one of these may result in drastic degradations in the others.
- the systems and methods discussed herein allow for a higher decoding success rate, at the same distortion level and message rate; or a higher message rate, at the same distortion level and decoding success rate.
- Implementations of these systems utilize a side chain (or side channel) of additional information, available only to the decoder and not the encoder, to achieve asymptotically lossless data compression, allowing the same message to be transmitted more robustly or in fewer bits.
- the present disclosure is directed to a system for
- the system includes a decoder of a device.
- the decoder is configured to receive a capture of an image comprising at least one embedded watermark; determine a timestamp of the capture; decode a binary string from the embedded watermark; using a portion of the timestamp of the capture, decode an identifier from the binary string comprising a timestamp of the image; and output the decoded identifier.
- the timestamp of the capture is identified in metadata of the capture.
- the decoder is configured to extract the timestamp of the capture from a header of a packet comprising the capture.
- the binary string of the embedded watermark comprises a subset of the timestamp of the image.
- the decoder is configured to decode the identifier from the binary string by concatenating the portion of the timestamp of the capture with the subset of the timestamp of the image.
- the binary string of the embedded watermark comprises a number of error correction bits greater than a difference between a length of the timestamp of the image and a length of the subset of the timestamp of the image.
- the decoder is configured to decode the identifier from the binary string by combining the portion of the timestamp of the capture with a predetermined offset. In a further implementation, the decoder is configured to decode the identifier from the binary string by iteratively combining the portion of the timestamp of the capture with a multiple of the predetermined offset until successfully decoding the identifier.
- the binary string comprises an address of a content server that generated the image comprising the at least one embedded watermark.
- the binary string comprises an identifier of a process of the content server that generated the image comprising the at least one embedded watermark.
- the present disclosure is directed to a method for improved watermarking.
- the method includes receiving, by a decoder of a device from a client device, a capture of an image comprising at least one embedded watermark.
- the method also includes determining, by the decoder, a timestamp of the capture.
- the method also includes decoding, by the decoder, a binary string from the embedded watermark.
- the method also includes using a portion of the timestamp of the capture, decoding, by the decoder, an identifier from the binary string comprising a timestamp of the image.
- the method also includes outputting, by the decoder, the decoded identifier.
- the timestamp of the capture is identified in metadata of the capture.
- the method includes extracting, by the decoder, the timestamp of the capture from a header of a packet comprising the capture.
- the binary string of the embedded watermark comprises a subset of the timestamp of the image.
- the method includes concatenating the portion of the timestamp of the capture with the subset of the timestamp of the image.
- the binary string of the embedded watermark comprises a number of error correction bits greater than a difference between a length of the timestamp of the image and a length of the subset of the timestamp of the image.
- the method includes combining the portion of the timestamp of the capture with a predetermined offset. In a further implementation, the method includes iteratively combining the portion of the timestamp of the capture with a multiple of the predetermined offset until successfully decoding the identifier.
- the binary string comprises an address of a content server that generated the image comprising the at least one embedded watennark.
- the binary string comprises an identifier of a process of the content server that generated the image comprising the at least one embedded watermark.
- the present disclosure is directed to a watermarking system.
- the system includes an encoder of a device configured to: receive an image and metadata associated with the image; generate a binary string from a subset of the metadata associated with the image; encode a watermark from the binary string; and embed the watermark in the image.
- a decoder of the device or a second device recovers the metadata associated with the image from the subset of the metadata associated with the image encoded in the embedded watermark and additional metadata associated with a capture of a display of the image at a third device.
- the metadata associated with the image comprises a timestamp of the image
- the additional metadata comprises a timestamp of the capture of the display of the image at the third device.
- the encoder of the device is configured to generate the binary string from a predetermined number of least significant bits of the metadata associated with the image.
- the present disclosure is directed to a method for watermarking.
- the method includes receiving, by an encoder of a device, an image and metadata associated with the image.
- the method also includes generating, by the encoder, a binary string from a subset of the metadata associated with the image.
- the method also includes encoding, by the encoder, a watermark from the binary string.
- the method also includes embedding, by the encoder, the watermark in the image.
- a decoder of the device or a second device recovers the metadata associated with the image from the subset of the metadata associated with the image encoded in the embedded watermark and additional metadata associated with a capture of a display of the image at a third device.
- the metadata associated with the image comprises a timestamp of the image
- the additional metadata comprises a timestamp of the capture of the display of the image at the third device.
- the method includes generating the binary string from a predetermined number of least significant bits of the metadata associated with the image.
- the present disclosure also provides a computer program comprising instructions that, when executed by a computing device, cause the computing device to perform any of the methods disclosed herein.
- the present disclosure also provides a computer-readable medium comprising instructions that, when executed by a computing device, cause the computing device to perform any of the methods disclosed herein.
- FIG. 1 A is an illustration of an example implementation of image watermarking
- FIG. IB is an illustration of a data format for image watermarking, according to one implementation
- FIG. 1C is an illustration of a data format for image watermarking, according to another implementation.
- FIG. 2A is a block diagram of a system for image watermarking, according to one implementation
- FIG. 2B is a block diagram of a system for image watermarking, according to another implementation
- FIG. 3 is a block diagram of a system for image watermarking
- FIG. 4 is a flow chart of a method for image watermarking, according to some implementations.
- Image watermarking is a technique that embeds visually imperceptible data or messages into an image, and may be categorized as non-blind or blind, dependent respectively on whether the original image is necessary for watermark extraction. Blind watermarking is particularly useful in that the embedded data may be recovered without having access to the original pre-embedded image.
- a small watermark code 102 may comprise an array of pixels of a size and placed within an image 100 such that they are not visible to viewers. As shown, watermark codes 102 may be duplicated throughout the image, to provide resistance against cropping, regional artifacts due to compression or other impairment, or other such distortions. Although shown with just a few pixels for clarity, in many
- a watermark code may comprise a region with 64 pixels, 128 pixels, or any other such amount. Adjustments to the pixels to define values of the encoding may be relatively imperceptible, as opposed to simply black and white pixels. For example, in many implementations, the pixels that make up the encoded region may have colors matching or similar to the surrounding pixels, but with adjusted alpha (transparency) values. For example, the encoding may change a pixel with an alpha value of 0 to an alpha value of 10, 50, 100, 255, or any other such value. In some implementations, the code may be detected by identifying pixels with alpha values that widely vary from surrounding alpha values. In some implementations, differential encoding may be applied with an overlay encoding each bit, with changes to alpha values of pixels within the overlay to encode a different value.
- Any sort of data may be encoded within the watermarks 102.
- the illustrated data format comprises 128 bits, with a 64 bit timestamp 152 (e.g. based on an epoch time), an IP address 154, and a process identifier 156.
- Data in the data format 150 may be referred to herein as a query ID.
- Many implementations also include error correction bits (not illustrated) to improve decoding of the watermark.
- the code may be encoded as a QR code with Reed-Solomon error correction codes included within the mark.
- the data may be encoded by a content server into an image prior to providing the image to a client device, with an IP address of the content server and a process identifier of the process that generated the image.
- a monitoring process on the client device may capture a screenshot of the image and provide the screenshot to the content server or a monitoring server.
- the monitoring process on the client device may not be able to access the image itself (e.g. the image may be stored in a location in the memory of the client device to which the monitoring process does not have access), but can capture a screenshot of the image (e.g. by reading image data from a frame buffer, or by capturing the image with a camera).
- the server may decode the watermark to identify the original generating process and server, as well as the time at which the image was generated or marked, and may compare the screenshotted image to the original image. This may allow a system to automatically identify distortion or image corruption caused by rendering or encoding processes for the image, as well as identifying other aspects of the image. In implementations in which the content server and monitoring server are different, this may particularly allow the monitoring server to identify a particular content server of a plurality of content servers that provided the image to the client device. This may be useful for logging, tracking, and analysis, and may be significantly easier than attempting to retrieve HTTP logs or similar logs from the client device (to which the monitoring server may not have access).
- FIG. 2A is a block diagram of a system 200 for image watermarking, according to one implementation.
- the system may comprise an encoder 202 and decoder 204, which may be on the same or different computing devices (e.g. a content server and a monitoring server).
- An image“S” 206 may be encoded by an encoder 202 with a message“X” 208 to create a watermarked image“S’” 210 comprising S+X.
- the encoded or watermarked image S’ may be transmitted over a communication channel 212, such as to a client device.
- a corresponding watermarked image (e.g. from a screenshot, as discussed above), may be provided to the decoder 204.
- the client device may send the watermarked image to the decoder 204 via the communication channel 212.
- the communication channel may thus comprise any combination of networks and devices between the encoder and decoder, which may potentially introduce any sort of additional distortion.
- the channel may be lossy as a result of either intentional or unintentional attacks or impairments.
- unintentional impairments include rotation of the image, scaling, and format conversion.
- intentional impairments include noise injection (e.g. adding information), and attempts to remove watermarking codes (e.g. subtracting information).
- the decoder 204 may detect and decode the watermark from the
- the encoder may encode a message, such as the
- the factors that impact decoding success rate are distortion introduced to the image by the encoder (D e ) and distortion between the captured screenshot and the watermarked image at the encoder output (D c ).
- watermarking as measured in decoding success rate is controlled by D e : for the same D c , if D e is increased, the higher the decoding success rate can be achieved. However, for most purposes, the watermarks must be visually imperceptible in the watermarked image. Such a requirement imposes an upper bound on D e. This constraint on D e essentially implies an upper bound of decoding success rate for any given channel. In some extreme cases where D c introduced by the channel is large, the decoding success rate can drop to near zero, and thus limits the applicability of such implementations of watermarking.
- the systems and methods discussed herein provide for improved image watermarking to improve robustness and capacity, without degrading perceptibility. Specifically, the systems and methods discussed herein allow for a higher decoding success rate, at the same distortion level and message rate; or a higher message rate, at the same distortion level and decoding success rate.
- Implementations of these systems utilize a side chain of additional information, available only to the decoder and not the encoder, to achieve asymptotically lossless data compression, allowing the same message to be transmitted in fewer bits.
- the systems discussed herein focus on the tradeoff between the decoding success rate and the message rate. Specifically, the system circumvents the above mentioned lower-bound of the message rate without compromising the usefulness of the watermarking message. Consequently, it allows for greater flexibility in finding the right tradeoff between robustness and capacity that was not possible in prior implementations. Specifically, side information, available only at the decoder, may be used to achieve asymptotically lossless compression.
- FIG. 2B is a block diagram of a system 200’ for image watermarking, according to one such implementation.
- an encoder 202 encodes an image 206 with a message 208 to generate a watermarked image 210, which may be provided via a communications channel 212 to a decoder 204.
- the decoder uses additional side information“Y” 214, unavailable to the encoder. This obviates any requirement of separate communication between the encoder and decoder, which may be particularly advantageous in implementations in which the content server and monitoring server are not the same device (and may not be controlled by the same entity).
- the system may leverage side information Y at the decoder to improve robustness.
- the encoder in FIG. 2B embeds a watermarking message into an image as follows: 1. Convert the watermarking message X to a K-bit binary string, where K is determined by H(X
- the decoder of FIG. 2B decodes the watermarking message X from a screenshot of the watermarked image as follows:
- steps 6-7 may be combined into a single step for better performance.
- a QR codeword includes patterns for detection and an error correction code in a 2D layout.
- a ID error correction codeword along with ID patterns for detection may be used in place of a QR codeword for better performance/flexibility in generating a watermarking image.
- ID error correction codes include Reed-Solomon codes, Turbo codes, LDPC (low-density parity-check) codes, and other general linear block codes.
- step 1 in the encoding process above in order to determine
- Y) a priori H(X
- side information Y for which a priori knowledge of H(X
- the query ID discussed in FIG. IB above is a 128-bit binary string consisting of a timestamp (64bit), an IP address (32bit), and a process id (32 bit) (not including any additional error coding bits).
- the screenshot timestamp T s is strongly correlated with the timestamp T q in the query ID such that Tq ⁇ T s ; and there exists a non-negative integer D such that T s - T q ⁇
- the timestamp for 2019-01-01 in epoch time is: 1546300800, and its binary is:
- the timestamp for 2018-01-01 is 1514764800, and its binary version is: ObOlOl 0110 0001 1010 1011 1010 1001 1101 0010 1000 0000 0000 0000
- the top 18 bits in their 64-bit representations are the same. The closer the two timestamps are, the more of the top significant bits are the same. In typical implementations, the image timestamp and screenshot timestamp may typically be significantly closer, such as within a day, a week, or a month, and thus have a greater number of bits the same.
- FIG. 1C is an illustration of a data format 150’ for image watermarking, according to one such implementation. As shown, while the IP address 154 and process ID 156 are the same as in the implementation of FIG. IB, the timestamp is reduced to a portion of the least significant bits 158, and additional data 160 may be added, without reducing the size of the data.
- the timestamp LSB 158 may identify the index of the bin containing the correct timestamp Tq.
- the decoder may combine the first log2(A) bits of T s and the (64-log2(A))-bit bin index to obtain T’ q .
- log2(A) is not an integer
- T q must be among the following list of size m:
- a 21x21 QR code can store up to 152 bits of information as listed in the following table:
- the system can utilize a higher Error Correction Code (ECC) level or a smaller QR code to improve decoding success rate (e.g. changing from medium to quartile).
- ECC Error Correction Code
- the encoder of FIG. 2B may embed a
- the decoder of FIG. 2B may decode the
- these implementations essentially provide additional K-bit messaging capability for free, i.e., with the same decoding success rate and the same distortion level. These additional K bits may be used to provide better tracking capability and/or user experience in terms of ease of use.
- a client device 300 which may comprise a desktop computer, laptop computer, tablet computer, wearable computer, smartphone, embedded computer, smart car, or any other type and form of computing device, may communicate via a network 312 with one or more servers 314.
- a client device 300 may include a processor
- the memory device 306 may store machine instructions that, when executed by the processor cause the processor to perform one or more of the operations described herein.
- the processor 302 may include a microprocessor, ASIC, FPGA, etc., or combinations thereof. In many
- a processor may be a multi-core processor or an array of processors.
- a memory device 306 may include, but is not limited to, electronic, optical, magnetic, or any other storage devices capable of providing a processor with program instructions.
- a memory device may include a floppy disk, CD- ROM, DVD, magnetic disk, memory chip, ROM, RAM, EEPROM, EPROM, flash memory, optical media, or any other suitable memory from which a processor can read instructions.
- the instructions may include code from any suitable computer programming language such as, but not limited to, C, C++, C#, Java, JavaScript, Perl, HTML, XML, Python and Visual Basic.
- a client device 300 may include one or more network interfaces 304.
- a network interface 304 may include any type and form of interface, including Ethernet including 10 Base T, 100 Base T, or 1000 Base T (“Gigabit”); any of the varieties of 802.11 wireless, such as 802.11a, 802.11b, 802. l lg, 802.11h, or 802.1 lac; cellular, including CDMA, LTE, 3G, or 4G cellular; Bluetooth or other short range wireless connections; or any combination of these or other interfaces for communicating with a network.
- a client device 300 may include a plurality of network interfaces 304 of different types, allowing for connections to a variety of networks 312.
- network 312 may comprise a local area network (LAN), wide area network (WAN) such as the Intemet, cellular network, broadband network, Bluetooth network, 802.11 (WiFi) network, satellite network, or any combination of these or other networks, and may include one or more additional devices (e.g. routers, switches, firewalls, hubs, network accelerators, caches, etc.).
- LAN local area network
- WAN wide area network
- additional devices e.g. routers, switches, firewalls, hubs, network accelerators, caches, etc.
- a client device may include one or more user interface devices.
- a user interface device may be any electronic device that conveys data to a user by generating sensory information (e.g., a visualization on a display, one or more sounds, tactile feedback, etc.) and/or converts received sensory information from a user into electronic signals (e.g., a keyboard, a mouse, a pointing device, a touch screen display, a microphone, etc.).
- the one or more user interface devices may be internal to the housing of a client device, such as a built-in display, touch screen, microphone, etc., or external to the housing of a client device, such as a monitor connected to a client device, a speaker connected to a client device, etc., according to various implementations.
- Memory 306 may comprise an application 308 for execution by
- Application 308 may comprise any type and form of application, such as a media application, web browser, productivity application, or any other such application.
- Application 308 may receive images from a content server, including watermarks embedded within the images, and may display them via a user interface for a user of the client device.
- Memory 306 may also comprise a capture engine 310, which may be part of application 308 (e.g. a plug-in or extension of a browser) and/or part of an operating system of the device.
- Capture engine 310 may comprise an application, server, service, daemon, routine, or other executable logic for capturing screenshots of rendered images including watermarks.
- Capture engine 310 may be configured to capture a screenshot of every image or some images. For example, in some implementations, capture engine 310 may be triggered to take a screenshot of an image responsive to metadata of the image, or responsive to a script executed by application 308 (e.g. responsive to a script embedded in a web page displayed by a browser for example).
- Capture engine 310 may, in some implementations, take a screenshot of just an image, or may take a screenshot of an entire display or screen. In a further implementation, capture engine may crop a captured image to just the desired image. This may be done for example based on coordinates of display of the image within the display. Capture engine 310 may add metadata to the screenshot, such as a capture time (e.g. in epoch time) as discussed above. Capture engine 310 may also transmit the screenshot to a monitoring server via network interface 304. In some implementations, capture engine 310 may comprise a script embedded in a web page and executed by an application 308 while rendering the web page; such web pages may also include an embedded image or a link to an image for the capture engine to capture a screenshot of.
- Server 314 may include a content server and/or monitoring server, which may be the same or different devices.
- Server(s) 314 may include one or more processors 302, network interfaces 304, and memory devices 306.
- a content server 314 may comprise one or more content items 316 in storage, such as images to be watermarked, as well as other content (e.g. web pages, other media, etc.).
- Content server 314 may also comprise an encoder 202 as discussed above in connection with FIGs. 2A and 2B.
- Encoder 202 may comprise software, hardware, or a combination of hardware and software.
- encoder 202 may comprise an ASIC, FPGA, or other dedicated hardware for embedding watermarks into images.
- a monitoring server may comprise a decoder 204, as discussed above in connection with FIG. 2B.
- Decoder 204 may comprise software, hardware, or a combination of hardware and software.
- decoder 204 may comprise an ASIC, FPGA, or other dedicated hardware for identifying and decoding watermarks from images.
- decoder 204 may receive side information to aid in decoding the watermark, such as a screenshot time from metadata of a screenshot received from a capture engine 310.
- FIG. 4 is a flow chart of a method for image watermarking, according to some implementations.
- a client device may request a content item. The request may be triggered during rendering of a web page by a browser or other application (e.g.
- a content server 314 may select a content item.
- the content item may be selected via any means, and may be based on the client device type, a user account or device identifier, contextual items within a web page or other application, or any other such information.
- the content server 314 may generate a watermark
- the content item may be encoded with the watermark.
- encoding the content item may comprise generating an overlay with an alpha channel having pixels modified from a default value or pattern representing altered bits of the encoded watermark (e.g. a QR code or similar code).
- the watermarks may be repeated at predetermined intervals or spacing across the image.
- the overlay may then be blended or combined with the image to generate the encoded content item.
- the encoded content item may be transmitted by the content server to the client device.
- content items may be pre-encoded (e.g. before step 402), and the content server may select a pre-encoded content item for delivery.
- pre-encoding may be performed within a predetermined time frame prior to the request.
- content items may be encoded with a given timestamp and utilized for a predetermined time period (e.g. two weeks), and then replaced or re-encoded with a new timestamp. This may allow the content server to perform encoding processing during less busy times, while still ensuring that the content and timestamp are relatively fresh.
- the shorter the window during which pre-encoded content items may be used the more data may be encoded in the watermark and/or the watermark made more robust; however, even in the example described above, windows of a year or more may be used while still significantly reducing the data required.
- the client device may render the content item, e.g. within an application such as a web browser, media player, game, or other application.
- an application such as a web browser, media player, game, or other application.
- a capture engine of the client device may capture a screenshot of the content item.
- the screenshot may be cropped or limited to the content item, or may be of the full screen or a portion of the screen.
- the screenshot may be identified via metadata with a capture timestamp, and may include other identifiers (e.g. device identifiers, context identifiers of the application and/or web page, etc.).
- the capture timestamp may be provided via other means. For example, in some implementations, given that the capture time and time of transmission of the screenshot to a server are likely very close (e.g. within a few seconds), a packet transmission time (e.g. identified or extracted from a header of the packet, such as a timestamp option field of a transport layer header) or receipt time may be utilized as the capture timestamp.
- the client device may transmit the screenshot to a monitoring server.
- a monitoring server which may be a content server or a different device, may receive the screenshot and, in some implementations, may extract the timestamp from metadata of the screenshot or may identify a transmission or receipt time of the screenshot. The timestamp may be provided to a decoder of the monitoring server as side information.
- the decoder may scan the screenshot and extract any
- the decoder may compare the identified watermarks and select or generate a watermark with the least distortion (e.g. a watermark that matches the highest number of other watermarks in the image, a watermark that is an average of the other identified watermarks, etc.).
- the decoder may convert the watermark to a string.
- the decoder may generate a timestamp from a portion of the extracted timestamp from step 418 (e.g. a predetermined number of the least significant bits) and may test decoding of the string using the generated timestamp (e.g. applying error correction algorithms to the decoded string with the generated timestamp). If the string decodes correctly according to the error correction bits, then at step 426, the monitoring server may process the screenshot image or data related to the content item (e.g. identifying the content server via the IP address and process identifier, comparing the screenshot to the original content item to detect rendering distortion or corruption, tracking delivery of the content item, etc.).
- a timestamp from a portion of the extracted timestamp from step 418 (e.g. a predetermined number of the least significant bits) and may test decoding of the string using the generated timestamp (e.g. applying error correction algorithms to the decoded string with the generated timestamp). If the string decodes correctly according to the error correction bits, then at step 426, the monitoring server
- the decoder may advance the generated timestamp according to the value D from the binning scheme, and may retest the decode at step 424. This may be repeated iteratively until either decoding is successful, or all of the bin index values have been tested (suggesting that the watermark was corrupted or improperly extracted, or that a content item from prior to usage time window discussed above was utilized). If all bin index values have been tested and decoding is unsuccessful, then at step 428, the decoder may report an error to an administrator or user of the system.
- the systems and methods discussed herein provide for improved image watermarking to improve robustness and capacity, without degrading perceptibility.
- the systems and methods discussed herein allow for a higher decoding success rate, at the same distortion level and message rate; or a higher message rate, at the same distortion level and decoding success rate. Implementations of these systems utilize a side chain of additional information, available only to the decoder and not the encoder, to achieve asymptotically lossless data compression, allowing the same message to be transmitted in fewer bits.
- a computer storage medium can be, or be included in, a computer-readable storage device, a computer-readable storage substrate, a random or serial access memory array or device, or a combination of one or more of them.
- a computer storage medium is not a propagated signal
- a computer storage medium can be a source or destination of computer program instructions encoded in an artificially-generated propagated signal.
- the computer storage medium can also be, or be included in, one or more separate components or media (e.g., multiple CDs, disks, or other storage devices). Accordingly, the computer storage medium may be tangible.
- client or“server” include all kinds of apparatus, devices, and machines for processing data, such as a programmable processor, a computer, a system on a chip, or multiple ones, or combinations, of the foregoing.
- the apparatus can include special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit).
- the apparatus can also include, in addition to hardware, code that creates an execution environment for the computer program in question, e.g., code that constitutes processor firmware, a protocol stack, a database management system, an operating system, a cross-platform runtime environment, a virtual machine, or a combination of one or more of them.
- code that creates an execution environment for the computer program in question e.g., code that constitutes processor firmware, a protocol stack, a database management system, an operating system, a cross-platform runtime environment, a virtual machine, or a combination of one or more of them.
- the apparatus and execution environment can realize various different computing model infrastructures, such as web services, distributed computing and grid computing infrastructures.
- a computer program (also known as a program, software, software application, script, or code) can be written in any form of programming language, including compiled or interpreted languages, declarative or procedural languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, object, or other unit suitable for use in a computing environment.
- a computer program may, but need not, correspond to a file in a file system.
- a program can be stored in a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub-programs, or portions of code).
- a computer program can be deployed to be executed on one computer or on multiple computers that are located at one site or distributed across multiple sites and interconnected by a communication network.
- Processors suitable for the execution of a computer program include both general and special purpose microprocessors, and any one or more processors of any kind of digital computer. Generally, a processor will receive instructions and data from a read-only memory or a random access memory or both.
- the essential elements of a computer are a processor for performing actions in accordance with instructions and one or more memory devices for storing instructions and data.
- a computer will also include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto-optical disks, or optical disks.
- mass storage devices for storing data, e.g., magnetic, magneto-optical disks, or optical disks.
- a computer need not have such devices.
- a computer can be embedded in another device, e.g., a mobile telephone, a personal digital assistant (PDA), a mobile audio or video player, a game console, a Global Positioning System (GPS) receiver, or a portable storage device (e.g., a universal serial bus (USB) flash drive), to name just a few.
- PDA personal digital assistant
- GPS Global Positioning System
- USB universal serial bus
- Non-volatile memory media and memory devices, including semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks.
- semiconductor memory devices e.g., EPROM, EEPROM, and flash memory devices
- magnetic disks e.g., internal hard disks or removable disks
- magneto-optical disks and CD-ROM and DVD-ROM disks.
- the processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.
- implementations of the subject matter described in this specification can be implemented on a computer having a display device, e.g., a CRT (cathode ray tube), LCD (liquid crystal display),
- a display device e.g., a CRT (cathode ray tube), LCD (liquid crystal display),
- OLED organic light emitting diode
- TFT thin-film transistor
- plasma other flexible configuration, or any other monitor for displaying information to the user and a keyboard, a pointing device, e.g., a mouse, trackball, etc., or a touch screen, touch pad, etc., by which the user can provide input to the computer.
- Other kinds of devices can be used to provide for interaction with a user as well; feedback provided to the user can be any form of sensory feedback, e.g., visual feedback, auditory feedback, or tactile feedback; and input from the user can be received in any form, including acoustic, speech, or tactile input.
- a computer can interact with a user by sending documents to and receiving documents from a device that is used by the user; by sending webpages to a web browser on a user’s client device in response to requests received from the web browser.
- Implementations of the subject matter described in this specification can be implemented in a computing system that includes a back-end component, e.g., as a data server, or that includes a middleware component, e.g., an
- application server or that includes a front-end component, e.g., a client computer having a graphical user interface or a Web browser through which a user can interact with an implementation of the subject matter described in this
- Communication networks may include a local area network (“LAN”) and a wide area network (“WAN”), an inter-network (e.g., the Internet), and peer- to-peer networks (e.g., ad hoc peer-to-peer networks).
- LAN local area network
- WAN wide area network
- Internet inter-network
- peer- to-peer networks e.g., ad hoc peer-to-peer networks
- the users may be provided with an opportunity to control whether programs or features that may collect personal information (e.g., information about a user's social network, social actions or activities, a user's preferences, or a user's location), or to control whether or how to receive content from a content server or other data processing system that may be more relevant to the user.
- personal information e.g., information about a user's social network, social actions or activities, a user's preferences, or a user's location
- certain data may be anonymized in one or more ways before it is stored or used, so that personally identifiable information is removed when generating parameters.
- a user's identity may be anonymized so that no personally identifiable information can be determined for the user, or a user's geographic location may be generalized where location information is obtained (such as to a city, postal code, or state level), so that a particular location of a user cannot be determined.
- location information such as to a city, postal code, or state level
- the user may have control over how information is collected about him or her and used by the content server.
Abstract
Description
Claims
Priority Applications (6)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202080006695.8A CN113168666B (en) | 2019-06-19 | 2020-06-18 | Improved image watermarking |
GB2107910.8A GB2593638B (en) | 2019-06-19 | 2020-06-18 | Improved image watermarking |
US17/298,012 US20220092721A1 (en) | 2019-06-19 | 2020-06-18 | Improved image watermarking |
KR1020217016131A KR102578027B1 (en) | 2019-06-19 | 2020-06-18 | Improved image watermarking |
DE112020000150.4T DE112020000150T5 (en) | 2019-06-19 | 2020-06-18 | IMPROVED IMAGE WATERMARKS |
JP2021531779A JP7225403B2 (en) | 2019-06-19 | 2020-06-18 | Improved image watermarking |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/US2019/037959 WO2020256718A1 (en) | 2019-06-19 | 2019-06-19 | Improved image watermarking |
USPCT/US2019/037959 | 2019-06-19 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2020257493A1 true WO2020257493A1 (en) | 2020-12-24 |
Family
ID=67138214
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2019/037959 WO2020256718A1 (en) | 2019-06-19 | 2019-06-19 | Improved image watermarking |
PCT/US2020/038489 WO2020257493A1 (en) | 2019-06-19 | 2020-06-18 | Improved image watermarking |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2019/037959 WO2020256718A1 (en) | 2019-06-19 | 2019-06-19 | Improved image watermarking |
Country Status (4)
Country | Link |
---|---|
JP (1) | JP7225403B2 (en) |
KR (1) | KR102578027B1 (en) |
DE (1) | DE112020000150T5 (en) |
WO (2) | WO2020256718A1 (en) |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN113542767B (en) * | 2021-07-14 | 2022-06-10 | 广东工业大学 | Information hidden image processing model construction method, device, terminal and medium |
CN116957893B (en) * | 2023-06-26 | 2024-04-16 | 海易科技(北京)有限公司 | Watermark generation method, watermark generation device, electronic device and computer readable medium |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1190548A1 (en) * | 1999-06-18 | 2002-03-27 | Telefonaktiebolaget LM Ericsson (publ) | Estimation of time stamps in real-time packet communications |
US20160309238A1 (en) * | 2013-12-03 | 2016-10-20 | Lg Electronics Inc. | Apparatus for transmitting broadcast signals, apparatus for receiving broadcast signals, method for transmitting broadcast signals and method for receiving broadcast signals |
US20160360288A1 (en) * | 2015-06-08 | 2016-12-08 | Qualcomm Incorporated | Broadcast content redistribution and ad insertion |
Family Cites Families (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2014014252A1 (en) | 2012-07-16 | 2014-01-23 | Lg Electronics Inc. | Method and apparatus for processing digital service signals |
EP3661381B1 (en) | 2017-08-04 | 2023-08-30 | NIKE Innovate C.V. | Article of footwear having a knitted component with a forefoot portion and a heel portion |
-
2019
- 2019-06-19 WO PCT/US2019/037959 patent/WO2020256718A1/en active Application Filing
-
2020
- 2020-06-18 JP JP2021531779A patent/JP7225403B2/en active Active
- 2020-06-18 WO PCT/US2020/038489 patent/WO2020257493A1/en active Application Filing
- 2020-06-18 DE DE112020000150.4T patent/DE112020000150T5/en active Pending
- 2020-06-18 KR KR1020217016131A patent/KR102578027B1/en active IP Right Grant
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP1190548A1 (en) * | 1999-06-18 | 2002-03-27 | Telefonaktiebolaget LM Ericsson (publ) | Estimation of time stamps in real-time packet communications |
US20160309238A1 (en) * | 2013-12-03 | 2016-10-20 | Lg Electronics Inc. | Apparatus for transmitting broadcast signals, apparatus for receiving broadcast signals, method for transmitting broadcast signals and method for receiving broadcast signals |
US20160360288A1 (en) * | 2015-06-08 | 2016-12-08 | Qualcomm Incorporated | Broadcast content redistribution and ad insertion |
Also Published As
Publication number | Publication date |
---|---|
DE112020000150T5 (en) | 2021-08-26 |
JP2022532814A (en) | 2022-07-20 |
KR20210079362A (en) | 2021-06-29 |
WO2020256718A1 (en) | 2020-12-24 |
KR102578027B1 (en) | 2023-09-13 |
JP7225403B2 (en) | 2023-02-20 |
CN113168666A (en) | 2021-07-23 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20120076346A1 (en) | Message Encoding | |
Zhu et al. | Robust steganography by modifying sign of DCT coefficients | |
CN108064395B (en) | System and method for embedding two-dimensional code in video image | |
WO2020257493A1 (en) | Improved image watermarking | |
US20230111326A1 (en) | Image watermarking | |
Zhang et al. | Enhancing reliability and efficiency for real-time robust adaptive steganography using cyclic redundancy check codes | |
US10706488B2 (en) | Embedding debugging information via watermarks | |
Bao et al. | A robust image steganography on resisting JPEG compression with no side information | |
US20220092721A1 (en) | Improved image watermarking | |
Fang et al. | An optimization model for aesthetic two-dimensional barcodes | |
Zhang et al. | Semantic image compression based on data hiding | |
CN113168666B (en) | Improved image watermarking | |
JPWO2017130333A1 (en) | Image processing apparatus, image processing method, and program | |
US20230325959A1 (en) | Zoom agnostic watermark extraction | |
US20230325961A1 (en) | Zoom agnostic watermark extraction | |
CN114626968A (en) | Watermark embedding method, watermark extracting method and device | |
JP2013058965A (en) | Digital data information embedding apparatus and embedded information detection apparatus | |
Rodrigues et al. | Reversible image steganography using cyclic codes and dynamic cover pixel selection | |
Preetha et al. | Adaptive image steganography based on Syndrome-Trellis codes | |
Nakamura et al. | A fast and robust digital watermark detection scheme for cellular phones | |
Pan et al. | Domain Transformation of Distortion Costs for Efficient JPEG Steganography with Symmetric Embedding | |
Liu et al. | Matrix embedding in multicast steganography: analysis in privacy, security and immediacy | |
Jouhari et al. | A new steganographic scheme based on first order reed muller codes-A new steganographic scheme | |
Kireev et al. | Transform-Aware Content Adaptive Stegosystem for Social Networks | |
Qiao et al. | Robust steganography in practical communication: a comparative study |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 20735257 Country of ref document: EP Kind code of ref document: A1 |
|
DPE1 | Request for preliminary examination filed after expiration of 19th month from priority date (pct application filed from 20040101) | ||
ENP | Entry into the national phase |
Ref document number: 20217016131 Country of ref document: KR Kind code of ref document: A |
|
ENP | Entry into the national phase |
Ref document number: 2021531779 Country of ref document: JP Kind code of ref document: A |
|
ENP | Entry into the national phase |
Ref document number: 202107910 Country of ref document: GB Kind code of ref document: A Free format text: PCT FILING DATE = 20200618 |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 20735257 Country of ref document: EP Kind code of ref document: A1 |