Patent Description:
This disclosure relates generally to monitoring media using media signatures and, more particularly, to methods and apparatus to synthesize reference media signatures based on constituent media signatures generated by metered media devices.

In recent years, methods of accessing media have evolved. For example, in the past, media was primarily accessed via televisions coupled to set-top boxes. Recently, media services deployed via Over-The-Top (OTT) devices or internet streaming capable devices, such as an Amazon Kindle Fire™, an Apple TV®, a Roku® media player, etc., have been introduced that allow users to request and present media on the OTT devices. Such OTT devices, as well as other media presentation platforms, such as desktop, laptop, and handheld mobile devices (e.g., smartphones, tablets, etc.) enable consumption of media from a variety of content providers and content publishers. <CIT> relates to an architecture for the collection and storage of fingerprints derived from media devices. <CIT> describes a method to create a media measurement reference database from a plurality of distributed sources. <CIT> relates to using a hierarchical, distributed approach to content identification.

The figures are not to scale. In general, the same reference numbers will be used throughout the drawing(s) and accompanying written description to refer to the same or like parts. Connecting lines and/or connectors shown in the figures are intended to represent example functional relationships and/or physical or logical couplings between the various elements.

The scope of this invention is defined by the claims. Any "embodiment" or "example" which is disclosed in the description but is not covered by the claims should be considered as presented for illustrative purpose only.

Many entities have an interest in understanding how users are exposed to media on the Internet. For example, an audience measurement entity (AME) desires knowledge of how users interact with media devices, such as smartphones, tablets, laptops, smart televisions, etc., and/or media presented thereon. For example, an AME may want to monitor media presentations made at the media devices to, among other things, monitor exposure to advertisements, determine advertisement effectiveness, determine user behavior, identify purchasing behavior associated with various demographics, etc..

AMEs coordinate with advertisers to obtain knowledge regarding an audience of media. For example, advertisers are interested in knowing the composition, engagement, size, etc., of an audience for media. For example, media (e.g., audio and/or video media) may be distributed by a media distributor to media consumers. Content distributors, advertisers, content producers, etc. have an interest in knowing the size of an audience for media by the media distributor, the extent to which an audience consumes the media, whether the audience pauses, rewinds, fast-forwards the media, etc. In some examples, the term "content" includes programs, advertisements, clips, shows, etc., In some examples, the term "media" includes any type of audio and/or visual content and/or advertisement delivered via any type of distribution medium. Thus, media includes television programming and/or advertisements, radio programming and/or advertisements, movies, web sites, streaming media, etc. Unless context clearly dictates otherwise, for ease of explanation, "media" refers to a piece of media (e.g., movie, TV show, etc.) in its entirety.

In some instances, AMEs identify media by extracting media identifiers such as fingerprints, signatures, and/or media-identifying metadata, such as codes, watermarks, etc., and comparing them to reference media identifiers. For example, fingerprint or signature-based media monitoring techniques generally use one or more inherent characteristics of the monitored media during a monitoring time interval to generate a substantially unique proxy for the media. Such a proxy is referred to as a signature or fingerprint, and can take any form (e.g., a series of digital values, a waveform, etc.) representative of any aspect(s) of the media signal(s) (e.g., the audio and/or video signals forming the media presentation being monitored). A reference media signature may be a series of constituent media signatures collected in series over a time interval. A good signature is repeatable when processing the same media presentation, but is unique relative to other (e.g., different) presentations of other (e.g., different) media. Accordingly, the terms "fingerprint" and "signature" are used interchangeably herein and are defined herein to mean any proxy for identifying media that is generated from one or more inherent characteristics of the media.

Signature-based media monitoring generally involves determining (e.g., generating or otherwise collecting) signature(s) representative of a media signal (e.g., an audio signal and/or a video signal) output by a monitored media device and comparing the collected signature(s) to one or more references signatures corresponding to known (e.g., reference) media sources. Various comparison criteria, such as a cross-correlation value, a Hamming distance, etc., can be evaluated to determine whether a collected signature matches a particular reference media signature. When a match between the collected signature and one of the reference media signatures is found, the monitored media can be identified as corresponding to the particular reference media represented by the reference media signature that matched the collected signature. Because attributes, such as an identifier of the media, a presentation time, a broadcast channel, etc., associated with the reference media signature are collected, these attributes may then be associated with the monitored media whose collected signature matched the reference media signature. Example systems for identifying media based on codes and/or signatures are long known and were first disclosed in<CIT>.

Example methods, apparatus, and articles of manufacture disclosed herein monitor media presentations at media devices. Such media devices may include, for example, Internet-enabled televisions, personal computers (e.g., desktop computers, laptop computers, etc.), Internet-enabled mobile handsets (e.g., a smartphone), video game consoles (e.g., Xbox®, PlayStation®), tablet computers (e.g., an iPad®), digital media players (e.g., an Apple TV®, an Amazon Kindle Fire™, a Roku® media player, a Slingbox®, etc.), etc..

In examples disclosed herein, a media device asset manager (MDAM) obtains a media device asset including one or more constituent media signatures from a metered media device and one or more corresponding media identifiers (e.g., metadata). As used herein, the term "media device asset" refers to any type of information extracted from media presented at a media device, such as, one or more signatures and/or other media-identifying metadata, such as one or more codes, one or more watermarks, etc. As used herein, the term "media identifier" refers to any type of media identification information, such as a source identifier, a stream identifier, a passive audio signature (PAS) timestamp, a duration of media, etc., and/or a combination thereof.

In some disclosed examples, the MDAM obtains from a device other than a media device (e.g., a metering device) a media asset including one or more signatures and one or more corresponding media identifiers. In some examples, the term "media asset" refers to any type of information extracted from media such as one or more signatures and/or other media-identifying metadata, such as one or more codes, one or more watermarks, etc..

In some disclosed examples, a media device asset is a collection of two or more signatures from a media device that individually and/or collectively identify media from which the signatures were obtained. For example, the media device asset may be a sequence of two or more signatures obtained from a meter operating on an Over-The-Top (OTT) device monitoring a presentation of the Home Box Office (HBO) content "Game of Thrones" on the OTT device. In another example, the meter may be operating externally to the OTT device. In such an example, the media device asset may be a sequence of two or more signatures obtained from a media meter, a people meter, etc., monitoring a presentation of the media.

In some disclosed examples, media is presented at a media device and a meter monitoring the media device uses signature-generation software to generate media device assets based on the presented media. In such disclosed examples, the media device asset may include unidentifiable data or unmatchable data (e.g., unidentifiable signatures, etc.) due to environmental elements such as audible noise emanating from the media device (e.g., a noise from a message alert on a smartphone, a noise from an email alert on a tablet, etc.). In some disclosed examples, a qualification process can be applied to the unidentifiable signatures to determine whether they can be stored in a reference media signature database. In some disclosed examples, the meter operates on the media device (e.g., a signature-generation application executing machine-readable instructions on a laptop, etc.). In other disclosed examples, the meter operates externally to the media device (e.g., a standalone metering device, etc.).

In some disclosed examples, the MDAM determines that a media device asset obtained from a media device has already been stored in a database (e.g., a media device asset database, etc.). For example, the MDAM may identify the media device asset as a duplicate syndicated media device asset. In such an example, the MDAM may (<NUM>) identify the media device asset based on an extracted media identifier, (<NUM>) determine that the media device asset has previously been stored in the database, and (<NUM>) determine that the previously stored media device asset is not a proprietary media asset. In such an example, the MDAM may store a log indicating that the media device asset is a duplicate syndicated media device asset. Additionally, and/or alternatively, the example MDAM may increment a duplicate syndicated media device asset counter corresponding to a number of times the media device asset is obtained and/or determined to be a duplicate syndicated media device asset. In some examples, after storing the log and/or incrementing the duplicate syndicated media device asset counter, the MDAM may discard the media device asset.

In some disclosed examples, the MDAM identifies a media device asset obtained from a media device as a syndicated duplicate of a proprietary media asset. In such an example, the MDAM may (<NUM>) identify the media device asset based on an extracted media identifier, (<NUM>) determine that the media device asset has previously been stored in the database, and (<NUM>) determine that the previously stored media device asset is a proprietary media asset. In such an example, the MDAM may store a log corresponding to determining that the media device asset is a syndicated duplicate of a proprietary media asset. Additionally, and/or alternatively, the example MDAM may replace the previously stored proprietary media asset with the media device asset.

In some disclosed examples, the MDAM determines that a media device asset obtained from a media device has not been previously stored in a database (e.g., a media device asset database, etc.). In such disclosed examples, the MDAM identifies the media device asset as a database candidate. For example, a database candidate may correspond to media where there are no reference media signatures stored in the database. As a result, a qualification process can be applied to one or more database candidates to determine a best one of the one or more database candidates to be stored in the database as a reference media signature, a reference media device asset, etc..

<FIG> is a block diagram of an example environment <NUM> constructed in accordance with teachings of this disclosure to synthesize reference media signatures based on constituent media signatures collected (e.g., generated, formed, computed, created, etc.) by metered media devices, three of which are designated at reference numerals <NUM>, <NUM> and <NUM>. In the illustrated example of <FIG>, the metered media devices <NUM>, <NUM>, <NUM> are devices that obtain (e.g., receive) media <NUM> and present the media <NUM>. In the illustrated example, the media <NUM> is a video that includes audio. However, any other type of media may be processed by examples disclosed herein. In some examples, the metered media devices <NUM>, <NUM>, <NUM> are capable of directly presenting media (e.g., via a display) while, in some other examples, the media devices <NUM>, <NUM>, <NUM> present the media on separate media presentation equipment (e.g., speakers, a display, etc.). For example, the metered media device <NUM> of the illustrated example is an Internet-enabled television capable of presenting media (e.g., via an integrated display and speakers, etc.) streaming from an OTT device. However, the metered media device <NUM> may be any other type of media device. Further, while in the illustrated example three media devices <NUM>, <NUM>, <NUM> are shown, any number and/or type(s) of media devices may be used.

In the illustrated example of <FIG>, each of the metered media devices <NUM>, <NUM>, <NUM> includes a respective meter <NUM>. In the illustrated example, the meters <NUM> are a software applications operating on the respective media device(s) <NUM>, <NUM>, <NUM> and including computer-readable instructions executable to generate media device assets. Additionally, and/or alternatively, one or more of the meter(s) <NUM> may operate externally to the respective media device <NUM>, <NUM>, <NUM> (e.g., a standalone device including a processor executing machine-readable instructions, etc.). In the illustrated example, the meters <NUM> generate media device assets <NUM> based on the media <NUM>. In the illustrated example, the media device assets <NUM> generated by a given meter <NUM> include signatures <NUM> computed or generated by an example generator 110A of the meter <NUM> from audio output and/or to be output by the media device <NUM>, <NUM>, <NUM>, and one or more media player metadata <NUM> collected by an example metadata collector 110B of the meter <NUM>, which may be implemented as a software meter monitoring a media player and/or other application (e.g., a web browser) capable of presenting media <NUM>. In the illustrated example, the signatures <NUM> include one or more audio-based signatures. Additionally, and/or alternatively, the signatures <NUM> may include one or more video-based signatures and/or any other type of signatures based on media identification information (e.g., media-identifying metadata, etc.). In the illustrated example, the media player metadata <NUM> includes media-identifying metadata corresponding to the media <NUM>, as well as metadata describing operation of the media player used to play the media <NUM>.

In the illustrated example of <FIG>, the example meters <NUM> transmit their respective media device assets <NUM> to an example MDAM <NUM> via an example network <NUM>. In the illustrated example of <FIG>, the network <NUM> is the Internet. However, the example network <NUM> may be implemented using any suitable wired and/or wireless network(s) including, for example, one or more data buses, one or more local area networks (LANs), one or more wireless LANs (WLANs), one or more cellular networks, one or more coaxial cable networks, one or more satellite networks, one or more private networks, one or more public networks, etc. The example network <NUM> enables the metered media devices <NUM>, <NUM>, <NUM>, the meters <NUM>, etc. to be in communication with the MDAM <NUM>. As used herein, the phrase "in communication," including variances (e.g., secure or non-secure communications, compressed or non-compressed communications, etc.) thereof, encompasses direct communication and/or indirect communication through one or more intermediary components and does not require direct physical (e.g., wired) communication and/or constant communication, but rather includes selective communication at periodic or aperiodic intervals, as well as one-time events.

In the illustrated example of <FIG>, the MDAM <NUM> coordinates an identification, a selection, etc., of a media device asset (e.g., a sequence of constituent media signatures <NUM>) to be stored in a database (e.g., an example datastore <NUM> in <FIG>). The MDAM <NUM> may use constituent media signatures <NUM> of a media device asset <NUM> to synthesize a reference media signature <NUM>.

In the illustrated example of <FIG>, an example report generator <NUM> generates and/or prepares reports using information stored in the media device asset database. In the illustrated example, the report generator <NUM> prepares media measurement reports indicative of the exposure of the media <NUM> on the media devices <NUM>, <NUM>, <NUM>. In some examples, the report generator <NUM> generates a report identifying demographics associated with the media <NUM> based on identifying one or more media device assets including the media device assets <NUM>. For example, a panelist at a media exposure measurement location may have provided the panelist's demographics to an AME. The report generator <NUM> may prepare a report associating the obtained panelist demographics with the media <NUM>.

<FIG> is a block diagram of an example implementation of the example MDAM <NUM> of <FIG> according to teachings of this disclosure. The example MDAM <NUM> of <FIG> manages a constituent media signatures datastore <NUM>, based on identifying media device assets (e.g., generated constituent media signatures <NUM>, collected media player metadata <NUM>, etc.) obtained (e.g., collected, received, etc.) from media devices (e.g., the example media devices <NUM>, <NUM>, and <NUM> of <FIG>) for use in subsequent measuring and/or monitoring by an AME. In the illustrated example of <FIG>, the example MDAM <NUM> includes an example network interface <NUM>, an example asset collector <NUM>, an example constituent media signatures datastore <NUM>, an example synthesizer <NUM>, and the example constituent media signatures datastore <NUM>.

In the illustrated example of <FIG>, the MDAM <NUM> includes the example network interface <NUM> and the example asset collector <NUM> to obtain information from and/or transmit information to the network <NUM> of <FIG>. In some examples, the example asset collector <NUM> implements a web server <NUM> that receives the media device assets <NUM> from the media device <NUM> and/or the meter <NUM>. In some such examples, the information included in the media device asset <NUM> is formatted as an HTTP message. However, any other message format and/or protocol may additionally, and/or alternatively, be used, such as, for example, a file transfer protocol (FTP), a simple message transfer protocol (SMTP), an HTTP secure (HTTPS) protocol, etc. In some examples, the asset collector <NUM> determines whether to continue monitoring a media device <NUM>, <NUM>, <NUM>. For example, the asset collector <NUM> may determine that one or more of the metered media devices <NUM>, <NUM>, <NUM> of <FIG> are not presenting the media <NUM> of <FIG>, are not powered on, etc. In the example of <FIG>, the media device assets <NUM> (e.g., as constituent media signatures <NUM> and media player metadata <NUM>) are stored in the example constituent media signatures datastore <NUM>.

To generate reference media signatures <NUM> that can be used to perform audience measurement, the example MDAM <NUM> includes the example synthesizer <NUM>. The example synthesizer <NUM> of <FIG> combines constituent media signatures <NUM> generated (e.g., computed, formed, etc.) by one or more of the example generators 110A of the one or more example meters <NUM> with media player metadata <NUM> collected by one or more of the collectors 110B of one or more of the example meters <NUM> to form reference media signatures <NUM>. The constituent media signatures <NUM> and the media player metadata <NUM> are collected in the constituent media signatures datastore <NUM> by the example asset collector <NUM>.

To synthesize reference media signatures <NUM> using the constituent media signatures <NUM> being collected by metered media devices (e.g., by the example meters <NUM> of the media devices <NUM>, <NUM>, <NUM>), the example MDAM <NUM> includes the example synthesizer <NUM>. The example synthesizer <NUM> of <FIG> processes the constituent media signatures <NUM> and the media player metadata <NUM> through a process of considering constituent media signatures <NUM>, qualifying them, and then creating reference media signatures <NUM> from the qualified constituent media signatures <NUM>. In some examples, a reference media signature <NUM> represents a complete piece of media <NUM> from its start to its end.

In some examples, the synthesizer <NUM> of <FIG> uses the media player metadata <NUM> to qualify constituent media signatures <NUM> by associating the constituent media signatures <NUM> with specific portions of the media <NUM> so they can then be combined to represent larger segments and/or all of a complete piece of the media <NUM>. The example synthesizer <NUM> of <FIG> combines constituent media signatures <NUM> to synthesize (e.g., form, generate, create, etc.) a set of reference media signatures <NUM> (a. a reference asset), which in some examples, is a complete sequence of media signatures from start to end of the media <NUM>, and its corresponding metadata (e.g., title, description, duration, episode, season, artist, owner, provider, etc.), which can be used by a crediting system to identify monitored media content by matching meter signatures (e.g., audio signatures) with reference media signatures <NUM>.

As media <NUM> is presented there may be usage behavior(s), such as fast-forward event, a rewind event, a pause event, a skip event, a stop/resume later event, etc., and/or browser/player behavior (e.g., buffering, etc.) that cause incomplete, duplicate, overlapping, irregular, non-contiguous, etc. constituent media signatures <NUM>. In some examples, the constituent media signatures <NUM> are harvested and presented to the qualification process as viable constituent media signatures <NUM>. Because, the metadata collector 110B can obtain and provide media player metadata <NUM> (e.g., such as position within content, pause, fast-forward, etc.), the synthesizer <NUM> can associate constituent media signatures <NUM> with locations within the media, rendering the constituent media signatures <NUM> viable, and useable to synthesize a reference media signature <NUM>.

While an example manner of implementing the MDAM <NUM> of <FIG> is illustrated in <FIG>, one or more of the elements, processes and/or devices illustrated in <FIG> may be combined, divided, re-arranged, omitted, eliminated and/or implemented in any other way. Further, the example constituent media signatures datastore <NUM>, the example network interface <NUM>, the example asset collector <NUM>, the example reference media signatures datastore <NUM>, the example synthesizer <NUM> and/or, more generally the example MDAM <NUM> of <FIG> may be implemented by hardware, software, firmware and/or any combination of hardware, software and/or firmware. Thus, for example, any of the example constituent media signatures datastore <NUM>, the example network interface <NUM>, the example asset collector <NUM>, the example reference media signatures datastore <NUM>, the example synthesizer <NUM> and/or, more generally the example MDAM <NUM> could be implemented by one or more analog or digital circuit(s), logic circuits, programmable processor(s), programmable controller(s), graphics processing unit(s) (GPU(s)), digital signal processor(s) (DSP(s)), application specific integrated circuit(s) (ASIC(s)), programmable logic device(s) (PLD(s)) and/or field programmable logic device(s) (FPLD(s)). When reading any of the apparatus or system claims of this patent to cover a purely software and/or firmware implementation, at least one of the example constituent media signatures datastore <NUM>, the example network interface <NUM>, the example asset collector <NUM>, the example reference media signatures datastore <NUM>, the example synthesizer <NUM> and/or, more generally the example MDAM <NUM> is/are hereby expressly defined to include a non-transitory machine-readable storage device or storage disk such as a memory, a digital versatile disk (DVD), a compact disc (CD), a Blu-ray disk, etc. including the software and/or firmware. Further still, the example MDAM <NUM> of <FIG> may include one or more elements, processes and/or devices in addition to, or instead of, those illustrated in <FIG>, and/or may include more than one of any or all the illustrated elements, processes and devices. As used herein, the phrase "in communication," including variations thereof, encompasses direct communication and/or indirect communication through one or more intermediary components, and does not require direct physical (e.g., wired) communication and/or constant communication, but rather additionally includes selective communication at periodic intervals, scheduled intervals, aperiodic intervals, and/or one-time events.

<FIG> is a block diagram of an example implementation of the example synthesizer <NUM> of <FIG>. To detect usage and/or browser, player, etc. events <NUM> (e.g., a pause, a rewind, a fast-forward, a skip, etc.) that may cause discrepancies between the media <NUM> being presented (e.g., watched, listened to, etc.) and the collected constituent media signatures <NUM>, the example synthesizer <NUM> includes an example event detector <NUM>. In some examples, the example event detector <NUM> of <FIG> detects events using any known and/or future methods, circuits, software, etc. including, but not limited to, an infrared receiver, a software utility logging use of a computer, etc. In some examples, events are detected at the MDAM <NUM>.

To modify a stream of constituent media signatures <NUM>, the example synthesizer <NUM> of <FIG> includes an example stream editor <NUM>. The example stream editor <NUM> of <FIG> maintains a stream <NUM> (e.g., collection) of constituent media signatures <NUM> that is being assembled to form a candidate set of reference media signature(s) <NUM> representing all of a piece of media <NUM>. The stream editor <NUM> can, among other things, add, remove and replace constituent media signatures <NUM> to and/or from the stream <NUM>.

To modify timestamps, the example synthesizer <NUM> of <FIG> includes an example timestamp editor <NUM>. The example timestamp editor <NUM> of <FIG> edits the timestamps of assembled constituent media signatures <NUM> of the stream <NUM> so their timestamps are contiguous to account, compensate, etc. for any events <NUM> detected by the event detector <NUM>.

To modify media times, the example synthesizer <NUM> of <FIG> includes an example media time editor <NUM>. The example media time editor <NUM> of <FIG> edits media times so they are contiguous and consistent with media signature timestamps.

While an example manner of implementing the synthesizer <NUM> of <FIG> is illustrated in <FIG>, one or more of the elements, processes and/or devices illustrated in <FIG> may be combined, divided, re-arranged, omitted, eliminated and/or implemented in any other way. Further, the example event detector <NUM>, the example stream editor <NUM>, the example timestamp editor <NUM>, the example media time editor <NUM> and/or, more generally the example synthesizer <NUM> of <FIG> may be implemented by hardware, software, firmware and/or any combination of hardware, software and/or firmware. Thus, for example, any of the example event detector <NUM>, the example stream editor <NUM>, the example timestamp editor <NUM>, the example media time editor <NUM> and/or, more generally the example synthesizer <NUM> could be implemented by one or more analog or digital circuit(s), logic circuits, programmable processor(s), programmable controller(s), GPU(s), DSP(s), ASIC(s), PLD(s) and/or FPLD(s). When reading any of the apparatus or system claims of this patent to cover a purely software and/or firmware implementation, at least one of the example event detector <NUM>, the example stream editor <NUM>, the example timestamp editor <NUM>, the example media time editor <NUM> and/or, more generally the example synthesizer <NUM> is/are hereby expressly defined to include a non-transitory machine-readable storage device or storage disk such as a memory, a DVD, a CD, a Blu-ray disk, etc. including the software and/or firmware. Further still, the example synthesizer <NUM> of <FIG> may include one or more elements, processes and/or devices in addition to, or instead of, those illustrated in <FIG>, and/or may include more than one of any or all the illustrated elements, processes and devices.

<FIG> is a block diagram representative of example hardware logic and/or machine-readable instructions <NUM> including machine-readable instructions <NUM>, <NUM>, <NUM>, <NUM> and <NUM> for implementing the synthesizer <NUM> of <FIG>. <FIG>, <FIG>, <FIG> and <FIG> are flowcharts representative of the example hardware logic and/or machine-readable instructions <NUM>, <NUM>, <NUM>, <NUM> and <NUM>, respectively, of <FIG>. The machine-readable instructions may be a program(s) or portion of a program(s) for execution by a processor such as the processor <NUM> shown in the example processor platform <NUM> discussed below in connection with <FIG>. The program(s) and/or portions thereof may be embodied in software stored on a non-transitory machine-readable storage medium such as a CD, a floppy disk, a hard drive, a DVD, a Blu-ray disk, or a memory associated with the processor <NUM>, but the entire program and/or parts thereof could alternatively be executed by a device other than the processor <NUM> and/or embodied in firmware or dedicated hardware. Further, although the example program is described with reference to the flowcharts illustrated in <FIG>, many other methods of implementing the example synthesizer <NUM> may alternatively be used. For example, the order of execution of the blocks may be changed, and/or some of the blocks described may be changed, eliminated, or combined. Additionally, and/or alternatively, any or all the blocks may be implemented by one or more hardware circuits (e.g., discrete and/or integrated analog and/or digital circuitry, an FPGA, a DSP, a GPU, a PLD, a FPLD, an ASIC, a comparator, an operational-amplifier (op-amp), a logic circuit, etc.) structured to perform the corresponding operation without executing software or firmware.

As mentioned above, the example processes of <FIG> may be implemented using executable instructions (e.g., computer and/or machine-readable instructions) stored on a non-transitory computer and/or machine-readable medium such as a hard disk drive, a flash memory, a read-only memory, a CD-ROM, a DVD, a cache, a random-access memory and/or any other storage device or storage disk in which information is stored for any duration (e.g., for extended time periods, permanently, for brief instances, for temporarily buffering, and/or for caching of the information). As used herein, the term non-transitory computer-readable medium is expressly defined to include any type of computer-readable storage device and/or storage disk and to exclude propagating signals and to exclude transmission media.

The term "and/or" when used, for example, in a form such as A, B, and/or C refers to any combination or subset of A, B, C such as (<NUM>) A alone, (<NUM>) B alone, (<NUM>) C alone, (<NUM>) A with B, (<NUM>) A with C, and (<NUM>) B with C.

The example program <NUM> of <FIG> begins with the example program <NUM> of <FIG>. The example program <NUM> of <FIG> processes the constituent media signatures <NUM> (between blocks <NUM> and <NUM>) collected from the meters <NUM> by the example asset collector <NUM> for a piece of media <NUM> to form a candidate set of reference media signature(s) <NUM>. In some examples, a constituent media signature <NUM> represents a portion of a piece of media <NUM>, and a set of reference media signature(s) 212is an ordered collection of constituent media signatures <NUM> that collectively represent the piece of media <NUM>. If the example event detector <NUM> of <FIG> detects a rewind event (block <NUM>), the synthesizer <NUM> removes (e.g., discards, deletes, etc.) the constituent media signatures <NUM> associated with the rewind event (example program <NUM>, see <FIG>). For example, the event detector <NUM> can determine a rewind event occurred by detecting the media time of a seek event (e.g., start, play, slow-play, etc.) (e.g., <NUM>:<NUM> minutes) is less than the media time associated with a pause event (e.g., <NUM>:<NUM> minutes). In some examples, the pause/stop and rewind events are reflected in the media player metadata <NUM>. In some examples, media time represents the location in media <NUM> expressed in time.

The example program <NUM> of <FIG> begins with the example stream editor <NUM> of <FIG> identifying and removing the constituent media signatures <NUM> associated with an extra (e.g., rewound) play of a section of media <NUM> from the set of reference media signature(s) <NUM> being formed to represent the media <NUM> (block <NUM>). For example, a duplicate set of constituent media signatures <NUM> associated with the media between <NUM>:<NUM> minutes and <NUM>:<NUM> minutes of the media <NUM> that was generated at a subsequent time the media <NUM> was played is ignored or discarded. Alternatively, prior constituent media signatures <NUM> are discarded. In some examples, the redundant, extra, etc. constituent media signatures <NUM> are also removed from the datastore <NUM>. The example timestamp editor <NUM> of <FIG> changes the timestamps of the constituent media signatures <NUM> in the set of reference media signature(s) <NUM> so the timestamps assigned to the constituent media signatures <NUM> are contiguous from before, through and after the rewind event (block <NUM>). The media time editor <NUM> adjusts media times, if needed, so media times are also contiguous and consistent with the timestamps (block <NUM>). By discarding the redundant (although possibly not identical) constituent media signatures <NUM> associated with the replay, and adjusting the signature timestamps and media times (e.g., the position in the media <NUM> expressed in second, minutes, etc.) to be contiguous, the reference media signature sequence <NUM> being created is as if the rewind event never occurred. In some examples, viewing duration is updated to include the replay event (block <NUM>). Control returns from the example program <NUM> of <FIG> to block <NUM> of <FIG>.

If the example event detector <NUM> of <FIG> detects a pause or stop event (block <NUM>), the synthesizer <NUM> removes the pause event (example program <NUM>, see <FIG>). For example, the event detector <NUM> can determine a pause event occurred by detecting use of a pause control aspect of a media device <NUM>, <NUM>, <NUM>. The example program <NUM> of <FIG> begins with the example stream editor <NUM> ignoring the constituent media signatures <NUM> that are inapplicable to the media <NUM> because they were generated during the pause event, e.g., while a pause control is active (e.g., as captured in the media player metadata <NUM>) (block <NUM>). The example timestamp editor <NUM> of <FIG> changes the timestamps of the constituent media signatures <NUM> in the set of reference media signature(s) <NUM> being formed to represent the media <NUM> so the timestamps assigned to the constituent media signatures <NUM> are contiguous from before, through and after the pause event (block <NUM>). The example media time editor <NUM> of <FIG> adjusts media times, if needed, so media times are also contiguous and consistent with the timestamps (block <NUM>). By discarding the inapplicable constituent media signatures <NUM> associated with the pause, and adjusting the signature timestamps and media times to be contiguous, the reference media signature sequence <NUM> being created is as if the pause event never occurred. In some examples, viewing duration is updated to include the pause event (block <NUM>). Control returns from the example program <NUM> of <FIG> to block <NUM> of <FIG>.

If the example event detector <NUM> of <FIG> detects a fast-forward, skip, etc. event (block <NUM>), the example synthesizer <NUM> removes the fast-forward event (example program <NUM>, see <FIG>). For example, the example event detector <NUM> can determine a fast-forward, skip, etc. event occurred by detecting use of a fast-forward, skip, etc. control aspect. The example program <NUM> of <FIG> begins with the example stream editor <NUM> filling all fast-forward sections of, for example, less than <NUM> seconds with silence starting at the media time when the fast-forward, skip, etc. started (block <NUM>). In some examples, the period of time can be filled is configurable. In some examples, other types of fill are used, base media signatures are left missing, etc. The example timestamp editor <NUM> of <FIG> changes the timestamps of the constituent media signatures <NUM> in the set of reference media signature(s) <NUM> so the timestamps assigned to the constituent media signatures <NUM> are contiguous from before, through and after the pause event (block <NUM>). The example media time editor <NUM> of <FIG> adjusts media times, if needed, so media times are also contiguous and consistent with the timestamps (block <NUM>). In some examples, viewing duration is updated to include the pause event (block <NUM>). Control returns from the example program <NUM> of <FIG> to block <NUM> of <FIG>.

If only a partial set of reference media signature(s) <NUM> can be formed from the constituent media signatures <NUM> of a particular meter <NUM> (block <NUM> of <FIG>), the example stream editor <NUM> of <FIG> combines the partial set of reference media signature(s) <NUM> generated using constituent media signatures <NUM> from two or more meters <NUM> (example program <NUM>, see <FIG>). The example program <NUM> of <FIG> begins with the example stream editor <NUM> of <FIG> using the media times associated with the constituent media signatures <NUM> of two or more meters <NUM> to combine (e.g., order, interlace, etc.) the constituent media signatures <NUM> together to form a combined reference media signature sequence <NUM> (block <NUM>), and any overlapping signatures are removed (block <NUM>). The example timestamp editor <NUM> of <FIG> changes the timestamps of the constituent media signatures <NUM> in the reference media signature <NUM> sequence so the timestamps assigned to the constituent media signatures <NUM> are contiguous from before, through and after the pause event (block <NUM>). The media time editor <NUM> of <FIG> adjusts media times, if needed, so media times are also contiguous and consistent with the timestamps (block <NUM>). In some examples, viewing duration is updated to include the pause event (block <NUM>).

In some examples, the example synthesizer <NUM> determines a credit skip point (CSP) for use in recording where a view skips to a next episode. In some examples, the synthesizer <NUM> averages the CSP point (e.g., point when a user can skip to next episode) of multiple viewers to determine what media time corresponds to the CSP point.

<FIG> is a block diagram of an example processor platform <NUM> structured to execute the instructions of <FIG> to implement the synthesizer <NUM> of <FIG>. The processor platform <NUM> can be, for example, a server, a personal computer, a mobile device (e.g., a cell phone, a smart phone, a tablet such as an iPad™), a personal digital assistant (PDA), an Internet appliance, a DVD player, a CD player, a digital video recorder, a Blu-ray player, a gaming console, a personal video recorder, a set top box, or any other type of computing device.

For example, the processor <NUM> can be implemented by one or more integrated circuits, logic circuits, microprocessors, GPUs, DSPs or controllers from any desired family or manufacturer. The hardware processor may be a semiconductor based (e.g., silicon based) device. In this example, the processor implements the example event detector <NUM>, the example stream editor <NUM>, the example timestamp editor <NUM>, the example media time editor <NUM>, the example synthesizer <NUM> and/or the MDAM <NUM>.

The volatile memory <NUM> may be implemented by Synchronous Dynamic Random-access Memory (SDRAM), Dynamic Random-access Memory (DRAM), RAMBUS® Dynamic Random-access Memory (RDRAM®) and/or any other type of random-access memory device. In this example, the non-volatile memory <NUM> implements the example constituent media signatures datastore <NUM>, and the example reference media signatures datastores <NUM>.

The interface circuit <NUM> may be implemented by any type of interface standard, such as an Ethernet interface, a universal serial bus (USB) interface, a Bluetooth®, a near field communication (NFC) interface, and/or a peripheral component interface (PCI) express interface.

The output devices <NUM> can be implemented, for example, by display devices (e.g., a light emitting diode (LED), an organic light emitting diode (OLED), a liquid crystal display, a cathode ray tube display (CRT), a touchscreen, etc.) a tactile output device, a printer, and/or speakers.

The interface circuit <NUM> of the illustrated example also includes a communication device such as a transmitter, a receiver, a transceiver, a modem and/or network interface card to facilitate exchange of data with external machines (e.g., computing devices of any kind) via a network <NUM> (e.g., an Ethernet connection, a digital subscriber line (DSL), a telephone line, a coaxial cable, a cellular telephone system, etc.).

Examples of such mass storage devices <NUM> include floppy disk drives, hard drive disks, CD drives, Blu-ray disk drives, redundant array of independent disks (RAID) systems, and DVD drives.

Coded instructions <NUM> including the coded instructions of <FIG> may be stored in the mass storage device <NUM>, in the volatile memory <NUM>, in the non-volatile memory <NUM>, and/or on a removable tangible machine-readable storage medium such as a CD or DVD.

Any references, including publications, patent applications, and patents, cited herein are hereby incorporated by reference to the same extent as if each reference were individually and specifically indicated to be incorporated by reference and were set forth in its entirety herein.

Further still example methods, apparatus, systems and articles of manufacture (e.g., physical storage media) to synthesize reference media signatures, determine media content based on metadata and media signatures, and implement the example meter <NUM> are provided in <CIT>.

From the foregoing, it will be appreciated that example methods, apparatus and articles of manufacture have been disclosed to synthesize reference media signatures based on constituent media signatures generated by metered media devices. Using teachings of this disclosure, reference media signatures can be generated without having to be aware of the media before it is presented. From the foregoing, it will be appreciated that methods, apparatus and articles of manufacture have been disclosed which enhance the operations of a computer by decreasing the time it takes to begin metering new media, and to enable the metering new media even if the new media is not watermarked before being presented. In some examples, computer operations can meter more media using teachings of this disclosure. Furthermore, example methods, apparatus, and/or articles of manufacture disclosed herein identify and overcome inability in the prior art to meter media before they are watermarked.

Example methods, apparatus, and articles of manufacture to synthesize reference media signatures based on constituent media signatures generated by metered media devices are disclosed herein. To better illustrate the method and apparatuses disclosed herein, a non-limiting list of examples is provided here:.

An example apparatus may include a collector to collect first constituent media signatures from a first media device that identify a first portion of media, a collector to collect second constituent media signatures from a second media device that identify a second portion of the media, and a synthesizer to combine the first constituent media signatures from the first media device and the second constituent media signatures from the second media device to form a reference media signature that represents the media, the reference media signature for comparison with third constituent media signatures collected from a third media device to detect consumption of the media at the third media device.

The example apparatus may further include an event detector to detect an event corresponding to at least one of a pause event, a stop event, a skip event, a fast-forward event, or a rewind event, and a stream editor to discard a portion of the first constituent media signatures corresponding to detected event.

The example apparatus may further include a timestamp editor to modify timestamps of the first constituent media signatures to compensate for discarding the portion of the first constituent media signatures.

The example apparatus may further include a media time editor to modify media times in the media associated with the first constituent media signatures to compensate for discarding the portion of the first constituent media signatures.

The example apparatus may further include a stream editor to delete a first constituent media signature when the first constituent media signature matches a second constituent media signature, and a timestamp editor to modify a timestamp of the second constituent media signature to be contiguous with a timestamp of a third constituent media signature preceding the first constituent media signature.

The first media device of the example apparatus may comprise the second media device.

An example method may include obtaining first constituent media signatures from a first media device that identify a first portion of media, obtaining second constituent media signatures from a second media device that identify a second portion of the media, and combining, by executing an instruction with a processor, the first constituent media signatures from the first media device and the second constituent media signatures from the second media device to form a reference media signature that identifies the media.

The example method may further include discarding a portion of the first constituent media signatures from the reference media signature.

The example method may further include collecting a third media signature from a third media device, comparing the third media signature with the reference media signature to identify presentation of the media at the third media device.

The example method may further include deleting a first constituent media signature when the first constituent media signature matches a second constituent media signature, and modifying a timestamp of the second constituent media signature to be contiguous with a timestamp of a third constituent media signature preceding the first constituent media signature.

The example method may further include discarding a first portion of the first constituent media signatures corresponding to at least one of a pause event, a stop event, a skip event, a fast-forward event, or a rewind event.

The example method may further include modifying timestamps of a second portion of the first constituent media signatures to compensate for discarding the first portion of the first constituent media signatures.

The example method may further include modifying media times in the media associated with the first constituent media signatures to compensate for discarding the portion of the first constituent media signatures.

The first media device of the example method may comprise the second media device.

An example non-transitory computer-readable storage medium may comprise instructions that, when executed, cause a machine to at least obtain first constituent media signatures from a first media device that identify a first portion of media, obtain second constituent media signatures from a second media device that identify a second portion of the media, and combine the first constituent media signatures from the first media device and the second constituent media signatures from the second media device to form a reference media signature that represents the media, the reference media signature for comparison with third constituent media signatures obtained from a third media device to detect consumption of the media at the third media device.

The example non-transitory computer-readable storage medium may include instructions that, when executed, cause the machine to discard a portion of the first constituent media signatures from the reference media signature.

The example non-transitory computer-readable storage medium may include instructions that, when executed, cause the machine to discard a portion of the first constituent media signatures corresponding to at least one of a pause event, a stop event, a skip event, a fast-forward event, or a rewind event.

The example non-transitory computer-readable storage medium may include instructions that, when executed, cause the machine to modify timestamps of the first constituent media signatures to compensate for discarding the portion of the first constituent media signatures.

The example non-transitory computer-readable storage medium may include instructions that, when executed, cause the machine to discard modify media times in the media associated with the first constituent media signatures to compensate for discarding the portion of the first constituent media signatures.

The example non-transitory computer-readable storage medium may include instructions that, when executed, cause the machine to delete a first constituent media signature when the first constituent media signature matches a second constituent media signature, and modify a timestamp of the second constituent media signature to be contiguous with a timestamp of a third constituent media signature preceding the first constituent media signature.

Claim 1:
An apparatus to synthesize reference signatures (<NUM>), the apparatus comprising:
memory; and
at least one processor to execute computer readable instructions to at least:
access a first sequence of media signatures (<NUM>) collected from a first device (<NUM>, <NUM>, <NUM>), the first sequence of media signatures representative of a first portion of first media (<NUM>), ones of the first sequence of media signatures having corresponding first timestamps;
identify and discard a first subset of the first sequence of media signatures (<NUM>) associated with an event (<NUM>) identified in metadata (<NUM>) associated with the first sequence of media signatures, the event corresponding to a usage behavior and/or browser/player behavior to cause a discrepancy between at least one reference media signature (<NUM>) representing the first media (<NUM>) and the first sequence of media signatures (<NUM>);
change the first timestamps of ones of a second subset of the first sequence of media signatures (<NUM>) that remain after the first subset is discarded to determine a modified first sequence of media signatures, so the timestamps assigned to the modified first sequence of media signatures are contiguous from before; and
combine the modified first sequence of media signatures with a second sequence of media signatures collected from a second device different from the first device to form a sequence of reference signatures (<NUM>) that represent the first media (<NUM>).