Media content proof of play over optical medium

Information

  • Patent Grant
  • 11057685
  • Patent Number
    11,057,685
  • Date Filed
    Thursday, March 29, 2018
    6 years ago
  • Date Issued
    Tuesday, July 6, 2021
    2 years ago
Abstract
Methods and a System are provided for proving media content was played on a display through capturing of audit information presented in watermarks when the content is played on the display. In a method, content watermarks are generated for content that is to be rendered on a display of a display device. An image sensor that is externally affixed to a corner of the display captures the watermarks as the content is rendered on the display, the image sensor captures the watermarks being played with the content from the area associated the corner where the image sensor is affixed. The image sensor captures the watermarks as images and streams the images back to the display device for storage. The stored watermarks are processed to verify that the corresponding content associated with the watermarks was played by the display device (visually rendered on the display of the display device).
Description
BACKGROUND

In the absence of being physically present to verify playback of media content, it is difficult if not impossible for a vendor to provide proof that the media content was actually displayed on a display device, digital signage, television, etc.


Verification can be needed by a content provider for a variety of reasons, such as: licensing, advertising revenue, government regulations (when consumers are required to view an informational notice), etc.


At present, mechanisms that provide the audit information is typically a processing log or history for the processing device where the content is processed for display. However, even if a processing log or history provides evidence that content was played on a device, the actual display may malfunction from time to time or because of an undetected software/hardware issue where in a given situation the content may not actually display on a display device. In fact, there is no existing reliable way to provide a true verification from existing processing logs or histories. This presents a number of issues for the content vendors and for the enterprises that are tasked with displaying the content on display devices for contractual and/or governmental compliance reasons.


For example, if the content was critical to a customer and the customer repudiates that the content was displayed for viewing, the processing log when presented may not be enough to rebut the customer's repudiation because display devices can malfunction and a undetectable bug in the software, associated with rendering the content on a display, may only occur in situations that cannot be readily reproduced or that are unable to be discovered in a reasonable time frame during which the dispute needs resolved. As a result, even if a customer was dishonest in the repudiation, the customer may be able to avoid paying for the content even when the content was actually displayed, which is a less than ideal situation for content vendors responsible for displaying the content.


SUMMARY

In various embodiments, methods and a system for content proof of play are presented.


According to an embodiment, a method for content proof of play is presented. More particularly, images of encoded information are received from an imaging sensor affixed to an external corner of a display while content is rendered on the display. The encoded information as is decoded as decoded information. The content is verified as having been rendered on the display based on the decoded information.





BRIEF DESCRIPTION OF THE DRAWINGS


FIG. 1 is a diagram of a system for content proof of play over an optical media, according to an example embodiment.



FIG. 2 is a diagram of a method for content proof of play, according to an example embodiment.



FIG. 3 is a diagram of another method for content proof of play, according to an example embodiment.



FIG. 4 is a diagram of another system for content proof of play, according to an example embodiment.





DETAILED DESCRIPTION


FIG. 1 is a diagram of a system 100 for content proof of play processing, according to an example embodiment. The various components are illustrated and the arrangement of the components is presented for purposes of illustration only. It is to be noted that other arrangements with more or less components are possible without departing from the content proof of play teachings presented herein and below.


The techniques, methods, and system presented herein and below for content proof of play can be implemented in whole or in part in one, all, or some combination of the components shown with the system 100. The techniques and methods are programmed as executable instructions in memory and/or non-transitory computer-readable storage media and processed on one or more processors associated with the various components.


As used herein the terms “customer,” “consumer,” and “user” may be used synonymously and interchangeably.


As used herein the phrase and term “media content” and “content” may be used synonymously and interchangeably. The phrase and term refer to digital information being rendered on a display device and can include: video, images, animation, graphics, text, or a combination of video, images, animation, graphics, and text.


A “display device” as used herein refers to a device that includes a processor, memory, storage, software that executes on the processor, and at least one interfaced hardware display to which the content is visually rendered in one or more display screens within the display.


In an embodiment, the display device is: a digital sign, a television, or a processor-enabled display monitor.


The system 100 includes: a display device 110 having at least one hardware processor, memory, and non-transitory computer-readable storage. The processor of the device 110 executes executable instructions for software representing a watermark generator, a watermark verifier, and a media player 113. The display device 110 also includes a media player port 114.


The system 100 also includes an image sensor 120 interfaced to the display device 110 through a wired connection 130 to the port 114.


Furthermore, the system 100 includes an external server 140 having at least one hardware processor, memory, and non-transitory computer-readable storage. The processor of the server 140 executes executable instruction for software representing a content manager 141.


Initial configuration of the system 100, includes physically locating a field-of-view for a lens of the image sensor 120 in a predefined location external to a display surface of a display for the display device 110 and connecting the image sensor 120 to the display device 110 through the wired connection to the media player port 114. The image sensor's lens is directed to a specific small area of the display surface of the display.


The watermark generator 111 is configured to integrate into the processing flow of content display plans for content that is to be rendered on the display of the display device 110. When the content plans are installed the watermark generator 111 generates watermarks as visually displayable encoded codes, such as barcodes or Quick-Response (QR) codes. The encoded codes are intended to represent the content that is to be rendered on the display of the display device 110 in an encoded and compact code. When the watermarks are decoded, the watermarks represent the content that is to be rendered on the display. So, the watermark generator 111 generates the watermarks for the content of a content plan before the content is actually rendered in accordance with that plan on the display of the display device 110.


In an embodiment, the watermarks are integrated into the content as a portion of the content (modifying the original content with the watermarks).


In an embodiment, the watermarks are time sequenced with the content as a separate stream of data and a separate file from the content file associated with the content and the content plan.


The watermark generator 111 also ensures that the watermarks are either integrated into the content or streamed simultaneously with the content such that the watermarks play with the content when the content is rendered on the display of the display device 110 in a small area of the display to which the field-of-view of the image sensor 120 is directed.


When the media player 113 is invoked by a corresponding content plan with the content, the watermarks appear in a screen or overlaid screen such that the watermarks a visually captured by the image sensor 120 as images being played simultaneously with the content.


The image sensor 120 sends or streams the captured images of the watermarks during content play of the content to the watermark verifier 112 over the wired connection 130. The watermark verifier 112 can buffer or store the images in storage on the display device 110 with time and data stamps and a content plan identifier associated with the content plan of the content.


The watermark verifier 112 is configured to process the streamed watermarks by decoding the watermarks to verify the actual content that was rendered in screens of the display by the media player 113 by comparing the decoded watermarks to the content plan. Any missing watermarks are noted by the verifier 112 if present. If the decoded watermarks corresponding directly with the content of the content play, such is noted as well.


The watermark verifier 112 can be configured to verify the watermarks with the content of a given content plan: dynamically as the content is rendered on the display, at predefined intervals of time, at a concluding of content play for a given content plan, and/or on demand when a request for verification to a given content play is made over a network connection by the content manager 141.


In an embodiment, the watermark verifier 112 does not verify the watermarks to the content of a given content plan; rather: 1) dynamically in real time, 2) at predefined intervals of time, 3) at the conclusion of content play for a given content play, and/or 4) on demand when a request is made by the content manager 141, the watermark verifier 112 provides a content plan identifier, the time and date stamps, and the watermarks to the content manager 141 over the network connection for remote verification of the content being played on the display of the display device 110.


In an embodiment, the verifier 112 can independently verify that the content was played (visually rendered on screens of the display for the display device 110), provide results associated with verification to the content manager 141 over the network connection, and provide the watermarks, time and date stamps, and associated content plan identifier for the content plan to the content manager 141 over the network connection. In this way, the content manager 141 can receive results and also independently verify the accuracy of the verifier's verification processing.


In an embodiment, the verifier 112 sends just results from the content proof of play verification to the manager 141 and provides the recorded watermarks used for the verification to the manager 141 if requested (on demand) by the manager 141 thereafter.


In an embodiment, the results include a content plan identifier, a date and time stamp, and an indication of success when the verifier 112 performed the content proof of play verification and when the verification was successful.


In an embodiment, the results include a content plan identifier, content segment identifiers for specific content segments, and time and date stamps where the content segment identifiers identify specific segments or portions of the content in the content plan where the verifier 112 was unable to verify that those portions of the content were actually played (rendered within one or more screens of the display for the display device 110).


The results also include a display device identifier for the display device 110 so that the manager 141 can specifically identify the display device 110 and associated establishment (location and entity) where the display device 110 is located. This is used because a the manager 141 may be responsible for providing proof of content play for a plurality of display devices 110 of a same entity or a plurality of display devices 110 associated with a plurality of different entities.


In an embodiment, the content plan may logically divide the display of the display device 110 into panels, each panel including different content rendered by the media player 113 within different screens being rendered on the display. The watermarks being streamed in the predefined area of the display representing the content for each of the panels, such that the verifier 112 or the manager 141 can verify that all content for all panels were played by the media player 113.


In an embodiment, the media player port is a 3.5 mm audio jack to the media player 113.


In an embodiment, the display device 110 is a digital sign.


In an embodiment, the display device 110 is a television.


In an embodiment, the image sensor 120 is attached to one bottom or top corner of the display device 110 on the exterior housing of the display for the display device 110. In an embodiment, the image sensor 120 is attached with tape or glue. In an embodiment, the image sensor 120 is attached by a clip mechanism.


These embodiments and other embodiments are now discussed with reference to the FIGS. 2-4.



FIG. 2 is a diagram of a method 200 for content proof of play processing, according to an example embodiment. The software module(s) that implements the method 200 is referred to as a “proof of play verifier.” The proof of play verifier is implemented as executable instructions programmed and residing within memory and/or a non-transitory computer-readable (processor-readable) storage medium and executed by one or more processors of a device. The processor(s) of the device that executes the proof of play verifier are specifically configured and programmed to process the proof of play verifier. The proof of play verifier has access to one or more networks during its processing. The networks can be wired, wireless, or a combination of wired and wireless.


In an embodiment, the proof of play verifier is both of, one of, or a combination of 111 and/or 112.


In an embodiment, the device that executes the proof of play verifier is the display device 110. In an embodiment, the display device 110 is a digital sign. In an embodiment, the display device 110 is a television.


At 210, the proof of play verifier receives images of encoded information from an image sensor affixed to an external corner of a display while content is rendered or played on the display. In an embodiment, the image sensor is the image sensor 120.


According to an embodiment, at 211, the proof of play verifier generates and integrates the encoded information with the content prior to the content being played or rendered on the display.


In an embodiment of 211 and at 212, the proof of play verifier provides the encoded information with a modified version of the content that includes the encoded information.


In an embodiment of 211 and at 213, the proof of play verifier synchronizes each portion of the encoded information with the content as a separate stream of content that is overlaid on the content when the content is rendered or played on the display.


In an embodiment of 211 and at 214, the proof of play verifier produces the encoded information as barcodes or QR codes that map to each portion of the content.


In an embodiment, at 215, the proof of play verifier stores or buffers the images in storage or memory of a display device as images are received from the image sensor.


At 220, the proof of play verifier decodes the encoded information from the images as decoded information.


In an embodiment, at 221, the proof of play verifier produces each portion of the decoded information as data that describes or corresponds to a specific portion of the content. For example, the decoded information may indicate that segment one of length 10 seconds for a given content plan played at a specific time and date.


At 230, the proof of play verifier verifiers that the content was rendered on the display based on the decoded information.


In an embodiment of 221 and 230, at 231, the proof of play verifier notes or records any expected portion of the decoded information that failed to be present for a known portion of the content.


In an embodiment, at 232, the proof of play verifier sends the decoded information and a content identifier for the content to a content manager for performing the verification processing at 230.


In an embodiment, at 233, the proof of play verifier processes the verification processing at 230 once the content has stopped being rendered or played on the display. This may be triggered by a notification sent from or a state obtained for the media player that is playing the content indicating that the content is done being played by the media player.


In an embodiment, at 234, the proof of play verifier processes the verification processing at 230 at a predefined interval of elapsed time has passed after the content has stopped being rendered or played on the display. For example, every 30 seconds or minute after the media player has stopped playing the content.


In an embodiment, at 235, the proof of play verifier process the verification processing at 230 upon an on-demand request for verification of the content that is received from a content manager. In an embodiment, the content manager is the content manager 141 or the method 300 described below.



FIG. 3 is a diagram of another method 300 for proof of play processing, according to an example embodiment. The software module(s) that implement the method 300 is referred to herein as a “content manager.” The content manager is implemented as executable instructions and programmed within memory and/or a non-transitory computer-readable (processor-readable) storage medium that executes on one or more processors of a device. The processors of the device are specifically configured to execute the content manager. The content manager has access one or more networks; the networks can be wired, wireless, or a combination of wired and wireless.


In an embodiment, the content manager is the content manager 141.


In an embodiment, the device that executes the content manager is the server 140.


In an embodiment, the device that executes the content manager is a cloud processing environment.


At 310, the content manager interacts with a verifier that executes on a display device to receive images of encoded information that corresponds to or describes content that was played on a display of the display device. In an embodiment, the verifier is the verifier 112 or the method 200.


In an embodiment, at 311, the content manager receives the images at predefined intervals of time from the verifier. For example, 30 seconds or a minute after the content has stopped being played by a media player of the display device.


In an embodiment, at 312, the content manager receives the images from the verifier upon conclusion of the content being played on the display by a media player of the display device.


In an embodiment, at 313, the content manager receives the images from the verifier after first sending an on-demand request for the images with a content identifier for the content to the verifier.


At 320, the content manager decodes the encoded information from the images as decoded information.


At 330, the content manager verifies that the decoded information corresponds to or describes all portions of the content that was played on the display of the display device.


In an embodiment, at 331, the content manager records any expected decoded information that was expected for the content but was missing from the decoded information. This indicates that some portions of the content did not properly display when played on the display of the display device.


According to an embodiment, at 340, the content manager produces an audit trail and non-repudiated proof of play of the content with the verification processing of 330 when all portions of the content were verified through the decoded information as having been played to the display of the display device.



FIG. 4 is a diagram of another system 400 for proof of play processing, according to an example embodiment. The components of the system 400 are programmed and reside within memory and/or a non-transitory computer-readable medium and execute on one or more processors of the devices of the system 400. The system 400 also has access and can communicate over one or more networks; and the networks can be wired, wireless, or a combination of wired and wireless.


The system 400 is configured and programmed to perform the processing discussed above with the FIGS. 1-3.


The system 400 includes a server 401, a content manager 402, an image sensor 403, a display device 404, and a verifier 405.


In an embodiment, the display device 404 is the display device 110. In an embodiment, the display device 110 is a digital sign. In an embodiment, the display device 110 is a television.


In an embodiment, the verifier 405 is all or some combination of: the watermark generator 111, the watermark verifier 112, and/or the method 200.


In an embodiment, the external image sensor 403 is the image sensor 120.


In an embodiment, the server 401 is the server 140.


In an embodiment, the server 401 is part of a cloud processing environment.


In an embodiment, the content manager 402 is all of or some combination of: the content manager 141 and/or the method 300.


The image sensor 403 is affixed to an external surface of a display of the display device 404. The image sensor 403 is configured to capture images of watermarks being rendered in a predefined area of the display when content is played or rendered within the display.


The verifier 405 executes on at least one hardware processor of the display device 404 and is configured to: (i) receive images of the watermarks from the image sensor 403 when the content is played or rendered on the display, (ii) store the images in storage of the display device 404, and (iii) facilitate verification with the content manager 402 that all of the content was played or rendered on the display based on the images of the watermarks.


The content manager 402 executes on at least one hardware processor of the server 401 and is configured to: (i) interact with the verifier 405 to determine whether any portion of the content was not played or not rendered on the display and (ii) establish an audit trail as non-repudiated proof of playing or rendering of the content based on the interactions with the verifier 405 and the images of the watermarks.


In an embodiment, the verifier 405 processes the images to determine whether all portions of the content was played or rendered on the display of the display device 404.


In an embodiment, the content manager 402 processes the images to determine whether all portions of the content was played or rendered on the display of the display device 404.


In an embodiment, both the verifier 405 and the content manager 402 both independently process the images to independently determine whether all portions of the content was played or rendered on the display of the display device 404.


It should be appreciated that where software is described in a particular form (such as a component or module) this is merely to aid understanding and is not intended to limit how software that implements those functions may be architected or structured. For example, modules may be illustrated as separate modules, but may be implemented as homogenous code, as individual components, some, but not all of these modules may be combined, or the functions may be implemented in software structured in any other convenient manner.


Furthermore, although the software modules are illustrated as executing on one piece of hardware, the software may be distributed over multiple processors of a single device, or in any other convenient manner.


The above description is illustrative, and not restrictive. Many other embodiments will be apparent to those of skill in the art upon reviewing the above description. The scope of embodiments should therefore be determined with reference to the appended claims, along with the full scope of equivalents to which such claims are entitled.


In the foregoing description of the embodiments, various features are grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting that the claimed embodiments have more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed embodiment. Thus the following claims are hereby incorporated into the Description of the Embodiments, with each claim standing on its own as a separate exemplary embodiment.

Claims
  • 1. A method, comprising: generating encoded information for content;synchronizing each portion of the encoded information with content portions of the content and providing synchronized encoded information as a separate stream of information that is synchronized to the content portions, wherein the separated stream is overlaid on the content when the content is rendered on a display;receiving images of encoded information from an imaging sensor affixed to an external corner of the display while content is rendered on the display based on presentation of the encoded information in the images as overlaid on the content and being played with the separate stream of the information with the content on the display and captured and provided by the imaging sensor;decoding the encoded information from the images as decoded information; andverifying that the content was rendered on the display based on the decoded information, wherein verifying further includes verifying that each piece of the content was properly rendered within a specific screen of several screens rendered on the display from the decoded information.
  • 2. The method of claim 1, wherein generating further includes generating the encoded information as barcodes or Quick Response (QR) codes that map to each content portion of the content.
  • 3. The method of claim 1, wherein receiving further includes storing or buffering the images in storage or memory of a display device as the images are received from the sensor.
  • 4. The method of claim 1, wherein decoding further includes producing each portion of the decoded information as data that describes or corresponds to a specific portion of the content.
  • 5. The method of claim 4, wherein verifying further includes noting any expected portion of the decoded information that failed to be present for a known portion of the content.
  • 6. The method of claim 1, wherein verifying further includes sending the decoded information and a content identifier for the content to a content manager for performing the verifying.
  • 7. The method of claim 1, wherein verifying further includes processing the verifying once the content has stopped being rendered on the display.
  • 8. The method of claim 1, wherein verifying further includes processing the verifying at a predefined interval of elapsed time has passed after the content has stopped being rendered on the display.
  • 9. The method of claim 8, wherein verifying further includes processing the verifying upon a request for verification of the content that is received from a content manager.
  • 10. A method, comprising: interacting with a verifier that executes on a display device to receive images of encoded information that corresponds to content that was played on a display of the display device, wherein the encoded information is a separate stream of information that is synchronized with content portions of the content and the separate stream of information is overlaid on to the content and synchronized with the content while the content is played on the display;decoding the encoded information from the images as decoded information; andverifying that the decoded information corresponds to all portions of the content, wherein verifying further includes verifying that each piece of the content was properly rendered within a specific screen of several screens rendered on the display device from the decoded information.
  • 11. The method of claim 10, wherein interacting further includes receiving the images at predefined intervals of time from the verifier.
  • 12. The method of claim 10, wherein interacting further includes receiving the images from the verifier upon conclusion of the content being played on the display by a media player of the display device.
  • 13. The method of claim 10, wherein interacting further includes receiving the images from the verifier after sending an on-demand request for the images with a content identifier for the content to the verifier.
  • 14. The method of claim 10, wherein verifying further includes recording any expected decoded information that was expected for the content but was missing from the decoded information.
  • 15. The method of claim 10 further comprising, producing an audit trail for proof of play of the content with the verifying.
  • 16. A system, comprising: a server configured to execute a content manager;a display device configured to execute a verifier; andan image sensor affixed to an external surface of a display of the display device, wherein the image sensor configured to capture images of watermarks being rendered in a predefined area of the display when content is played or rendered within the display, wherein the watermarks are provided in a separate stream of information from the content and the watermarks are synchronized with content portions of the content; the separate stream of information is rendered over the content on this display as the content plays on the display;wherein the verifier is configured to: (i) receive images of the watermarks from the image sensor when the content is played or rendered on the display, (ii) store the images in storage of the display device, and (iii) facilitate verification with the content manager that all of the content was played or rendered on the display based on the images of the watermarks and verify that each piece of the content was properly rendered within a specific screen of several screens rendered on the display device from the decoded information;wherein the content manager is configured to: (i) interact with the verifier to determine whether any portion of the content was not played or not rendered on the display and (ii) establish an audit trail of playing or rendering of the content based on the interactions with the verifier and the images of the watermarks.
  • 17. The system of claim 16, wherein one or more of: the verifier is configured to process the images in order to determine whether all portions of the content was played or rendered on the display, and the content manager is configured to process the images in order to determine whether all portions of the content was played or rendered on the display.
US Referenced Citations (224)
Number Name Date Kind
6411725 Rhoads Jun 2002 B1
6580806 Sato Jun 2003 B1
6771794 Osaka Aug 2004 B1
6785399 Fujihara Aug 2004 B2
6829368 Meyer Dec 2004 B2
6944771 Epstein Sep 2005 B2
6947571 Rhoads Sep 2005 B1
6950519 Rhoads Sep 2005 B2
6961444 Levy Nov 2005 B2
6965697 Kondo Nov 2005 B1
6993152 Patterson Jan 2006 B2
6993154 Brunk Jan 2006 B2
7003131 Watson Feb 2006 B2
7006661 Miller Feb 2006 B2
7020349 Brunk Mar 2006 B2
7042470 Rhoads May 2006 B2
7050603 Rhoads May 2006 B2
7061510 Rhoads Jun 2006 B2
7098931 Patterson Aug 2006 B2
7099491 Takaku Aug 2006 B2
7099492 Rhoads Aug 2006 B2
7181044 Watson Feb 2007 B2
7181625 Peled Feb 2007 B2
7184572 Rhoads Feb 2007 B2
7197160 Rhoads Mar 2007 B2
7197164 Levy Mar 2007 B2
7224819 Levy May 2007 B2
7248715 Levy Jul 2007 B2
7248717 Rhoads Jul 2007 B2
7254249 Rhoads Aug 2007 B2
7286685 Brunk Oct 2007 B2
7333957 Levy Feb 2008 B2
7349552 Levy Mar 2008 B2
7373513 Levy May 2008 B2
7436976 Levy Oct 2008 B2
7444392 Rhoads Oct 2008 B2
7454035 Miller Nov 2008 B2
7460726 Levy Dec 2008 B2
7499566 Rhoads Mar 2009 B2
7502489 Rhoads Mar 2009 B2
7502490 Rhoads Mar 2009 B2
7505605 Rhoads Mar 2009 B2
7564992 Rhoads Jul 2009 B2
7577273 Rhoads Aug 2009 B2
7577841 Celik Aug 2009 B2
7587601 Levy Sep 2009 B2
7590259 Levy Sep 2009 B2
7593576 Meyer Sep 2009 B2
7602977 Rhoads Oct 2009 B2
7602978 Levy Oct 2009 B2
7620253 Miller Nov 2009 B2
7643649 Davis Jan 2010 B2
7650008 Rhoads Jan 2010 B2
7650010 Levy Jan 2010 B2
7693965 Rhoads Apr 2010 B2
7738711 Kondo Jun 2010 B2
7742618 Srinivasan Jun 2010 B2
7848540 Srinivasan Dec 2010 B2
7856116 Rodriguez Dec 2010 B2
7861276 Moroo Dec 2010 B2
7949147 Rhoads May 2011 B2
7949149 Rhoads May 2011 B2
7961949 Levy Jun 2011 B2
7970167 Rhoads Jun 2011 B2
7978874 Levy Jul 2011 B2
7986806 Rhoads Jul 2011 B2
7986845 Miller Jul 2011 B2
8000495 Levy Aug 2011 B2
8010632 Rhoads Aug 2011 B2
8023691 Rodriguez Sep 2011 B2
8023694 Rhoads Sep 2011 B2
8027506 Rhoads Sep 2011 B2
8027520 Rhoads Sep 2011 B2
8036418 Meyer Oct 2011 B2
8036420 Evans Oct 2011 B2
8045749 Rhoads Oct 2011 B2
8055899 Levy Nov 2011 B2
8073933 Rhoads Dec 2011 B2
8085976 Rhoads Dec 2011 B2
8087583 Hawes Jan 2012 B2
8094949 Rhoads Jan 2012 B1
8099403 Levy Jan 2012 B2
8103879 Levy Jan 2012 B2
8107674 Davis Jan 2012 B2
8108484 Rhoads Jan 2012 B2
8116516 Rhoads Feb 2012 B2
8135166 Rhoads Mar 2012 B2
8150032 Rhoads Apr 2012 B2
8151113 Rhoads Apr 2012 B2
8165341 Rhoads Apr 2012 B2
8189854 Watson May 2012 B2
8194919 Rodriguez Jun 2012 B2
8224022 Levy Jul 2012 B2
8230226 Srinivasan Jul 2012 B2
8243980 Rhoads Aug 2012 B2
8302143 Meuninck Oct 2012 B2
8315554 Levy Nov 2012 B2
8346567 Petrovic Jan 2013 B2
8358703 Zou Jan 2013 B2
8374383 Long Feb 2013 B2
8392827 Challenger Mar 2013 B2
8407752 Levy Mar 2013 B2
8442264 Rhoads May 2013 B2
8447064 Rhoads May 2013 B2
8462982 Colaitis Jun 2013 B2
8483426 Rhoads Jul 2013 B2
8542868 Ballocca Sep 2013 B2
8543661 Rhoads Sep 2013 B2
8548810 Rodriguez Oct 2013 B2
8549307 Winograd Oct 2013 B2
8588459 Bloom Nov 2013 B2
8607354 Levy Dec 2013 B2
8626666 Lofgren Jan 2014 B2
8681978 Petriovic Mar 2014 B2
8683537 Meuninck Mar 2014 B2
8726304 Petrovic May 2014 B2
8745403 Petrovic Jun 2014 B2
8745404 Petrovic Jun 2014 B2
8781967 Tehranchi Jul 2014 B2
8799659 Srinivasan Aug 2014 B2
8805689 Ramaswamy Aug 2014 B2
8806517 Petrovic Aug 2014 B2
8825518 Levy Sep 2014 B2
8838979 Srinivasan Sep 2014 B2
8863165 Gordon Oct 2014 B2
8869222 Winograd Oct 2014 B2
8879780 Sartor Nov 2014 B2
8959352 Levy Feb 2015 B2
8976998 Rodriguez Mar 2015 B2
8983116 Srinivasan Mar 2015 B1
8984574 Meuninck Mar 2015 B2
9009482 Winograd Apr 2015 B2
9042598 Ramaswamy May 2015 B2
9065683 Wolosewicz Jun 2015 B2
9106964 Zhao Aug 2015 B2
9117270 Wong Aug 2015 B2
9210208 Ramaswamy Dec 2015 B2
9262794 Zhao Feb 2016 B2
9282366 Nielsen Mar 2016 B2
9292894 MacIntosh Mar 2016 B2
9299120 Zou Mar 2016 B2
9380356 McMillan Jun 2016 B2
9412386 Rodriguez Aug 2016 B2
9437201 Srinivasan Sep 2016 B2
9460560 Rodriguez Oct 2016 B2
9471950 Park Oct 2016 B2
9497341 Rhoads Nov 2016 B2
9514503 Ramaswamy Dec 2016 B2
9515904 Besehanic Dec 2016 B2
9524584 Rodriguez Dec 2016 B2
9578289 Roberts Feb 2017 B2
9578360 Weidenfeller Feb 2017 B2
9589296 Li Mar 2017 B1
9596521 Winograd Mar 2017 B2
9648282 Petrovic May 2017 B2
9661397 Kim May 2017 B2
9681204 McMillan Jun 2017 B2
9718296 Rodriguez Aug 2017 B2
9788043 Davis Oct 2017 B2
9792661 Rodriguez Oct 2017 B2
9838281 Besehanic Dec 2017 B2
9854331 Winograd Dec 2017 B2
9854332 Winograd Dec 2017 B2
9860611 Kim Jan 2018 B2
9942602 Petrovic Apr 2018 B2
9967600 Bause May 2018 B2
9986282 MacIntosh May 2018 B2
10009663 Hoffman Jun 2018 B1
10074149 Meuninck Sep 2018 B2
10110971 Winograd Oct 2018 B2
10158926 Hoffman Dec 2018 B1
10178443 Petrovic Jan 2019 B2
10277959 Winograd Apr 2019 B2
10325337 Meuninck Jun 2019 B2
10334285 Hohl Jun 2019 B2
10341734 Gordon Jul 2019 B2
10354354 Zhao Jul 2019 B2
10445848 Petrovic Oct 2019 B2
10499120 Winograd Dec 2019 B2
10504200 Winograd Dec 2019 B2
10506291 Gordon Dec 2019 B2
10543711 Rodriguez Jan 2020 B2
10575068 Hazan Feb 2020 B2
20020021601 Chornenky Feb 2002 A1
20020090114 Rhoads Jul 2002 A1
20030138127 Miller Jul 2003 A1
20040218782 Brunk Nov 2004 A1
20040258273 Brunk Dec 2004 A1
20050008190 Levy Jan 2005 A1
20050210526 Levy Sep 2005 A1
20050251683 Levy Nov 2005 A1
20060133645 Rhoads Jun 2006 A1
20060210108 Brunk Sep 2006 A1
20070053549 Miller Mar 2007 A1
20070174624 Wolosewicz Jul 2007 A1
20070192872 Rhoads Aug 2007 A1
20080025561 Rhoads Jan 2008 A1
20080279536 Levy Nov 2008 A1
20090074241 Miller Mar 2009 A1
20090129627 Levy May 2009 A1
20090158318 Levy Jun 2009 A1
20090262975 Rhoads Oct 2009 A1
20100067737 Miller Mar 2010 A1
20100226525 Levy Sep 2010 A1
20110194730 Rhoads Aug 2011 A1
20120030041 Wolosewicz Feb 2012 A1
20120117584 Gordon May 2012 A1
20130081077 Mauduit Mar 2013 A1
20130297727 Levy Nov 2013 A1
20140152786 Nicholson Jun 2014 A1
20140201094 Herrington Jul 2014 A1
20150089526 Gordon Mar 2015 A1
20150127340 Epshteyn May 2015 A1
20150161587 Khan Jun 2015 A1
20160338120 Boyle Nov 2016 A1
20170094351 Gordon Mar 2017 A1
20180302672 Gordon Oct 2018 A1
20180302673 Gordon Oct 2018 A1
20180310058 Gordon Oct 2018 A1
20200068256 Gordon Feb 2020 A1
20200068257 Gordon Feb 2020 A1
20200068258 Gordon Feb 2020 A1
20200068259 Gordon Feb 2020 A1
20200068260 Gordon Feb 2020 A1
Related Publications (1)
Number Date Country
20190306588 A1 Oct 2019 US