Monitoring streaming media content

FIELD OF THE DISCLOSURE

0001This disclosure relates generally to content monitoring and, more particularly, to monitoring streaming media content.

BACKGROUND

0002Streaming enables media content to be delivered to and presented by a wide variety of content presentation devices, such as desktop computers, laptop computers, tablet computers, personal digital assistants, smartphones, etc. Because a significant portion of media content is presented via streaming to such devices, monitoring of streaming media content, like the monitoring of broadcasted media content, can provide valuable information to advertisers, content providers, and the like.

0003<patcit id="pcit0001" dnum="US20010044899A1"><text>US 2001/0044899 A1</text></patcit> pertains to transmarking a watermarked media signal to adapt the watermark to the robustness and perceptibility constraints of a new environment. <nplcit id="ncit0001" npl-type="s"><text>Pantos et al, "HTTP Live Streaming draft-pantos-http-live-streaming-06", IETF, March 31, 2011</text></nplcit>, describes a protocol for transferring unbounded streams of multimedia data. <patcit id="pcit0002" dnum="US20060242325A1"><text>US 2006/0242325 A1</text></patcit> describes transcoding of metadata to enable sharing and consumption of media content at dissimilar devices that are coupled to a home network. <patcit id="pcit0003" dnum="EP1760612A1"><text>EP 1 760 612 A1</text></patcit> pertains to processing content data supplied in a format that has at least a metadata region in which metadata of a content is stored.

BRIEF DESCRIPTION OF THE DRAWINGS

0004<ul id="ul0001" list-style="none"><li><figref idref="f0001">FIG. 1</figref> is block diagram of a first example system for monitoring streaming media content.</li><li><figref idref="f0002">FIG. 2</figref> is a block diagram of a first example server meter, which may be used to implement the example system of <figref idref="f0001">FIG. 1</figref>.</li><li><figref idref="f0002">FIG. 3</figref> is a block diagram of a first example device meter, which may be used to implement the example system of <figref idref="f0001">FIG. 1</figref>.</li><li><figref idref="f0002">FIG. 4</figref> is a block diagram of a first example media monitoring facility, which may be used to implement the example system of <figref idref="f0001">FIG. 1</figref>.</li><li><figref idref="f0003">FIG. 5</figref> is block diagram of a second example system for monitoring streaming media content.</li><li><figref idref="f0004">FIG. 6</figref> is a block diagram of a second example server meter, which may be used to implement the example system of <figref idref="f0003">FIG. 5</figref>.</li><li><figref idref="f0004">FIG. 7</figref> is a block diagram of a second example device meter, which may be used to implement the example system of <figref idref="f0003">FIG. 5</figref>.</li><li><figref idref="f0004">FIG. 8</figref> is a block diagram of a second example media monitoring facility, which may be used to implement the example system of <figref idref="f0003">FIG. 5</figref>.</li><li><figref idref="f0005">FIG. 9</figref> is block diagram of a third example system for monitoring streaming media content.</li><li><figref idref="f0006">FIG. 10</figref> is a block diagram of a third example server meter, which may be used to implement the example system of <figref idref="f0005">FIG. 9</figref>.</li><li><figref idref="f0006">FIG. 11</figref> is a block diagram of a third example media monitoring facility, which may be used to implement the example system of <figref idref="f0003">FIG. 5</figref>.</li><li><figref idref="f0007">FIG. 12</figref> is block diagram of a fourth example system for monitoring streaming media content.</li><li><figref idref="f0008">FIG. 13</figref> is a flowchart representative of example machine readable instructions that may be executed to implement the first example server meter of <figref idref="f0002">FIG. 2</figref>.</li><li><figref idref="f0009">FIG. 14</figref> is a flowchart representative of example machine readable instructions that may be executed to implement the first example device meter of <figref idref="f0002">FIG. 3</figref>.</li><li><figref idref="f0009">FIG. 15</figref> is a flowchart representative of example machine readable instructions that may be executed to implement the first example media monitoring facility of <figref idref="f0002">FIG. 4</figref>.</li><li><figref idref="f0010">FIG. 16</figref> is a flowchart representative of example machine readable instructions that may be executed to implement the second example server meter of <figref idref="f0004">FIG. 6</figref>.</li><li><figref idref="f0011">FIG. 17</figref> is a flowchart representative of example machine readable instructions that may be executed to implement the second example device meter of <figref idref="f0004">FIG. 7</figref>.</li><li><figref idref="f0011">FIG. 18</figref> is a flowchart representative of example machine readable instructions that may be executed to implement the second example media monitoring facility of <figref idref="f0004">FIG. 8</figref>.</li><li><figref idref="f0012">FIG. 19</figref> is a flowchart representative of example machine readable instructions that may be executed to implement the third example server meter of <figref idref="f0006">FIG. 10</figref>.</li><li><figref idref="f0012">FIG. 20</figref> is a flowchart representative of example machine readable instructions that may be executed to implement the third example media monitoring facility of <figref idref="f0006">FIG. 11</figref>.</li><li><figref idref="f0013">FIG. 21</figref> is a flowchart representative of example machine readable instructions that may be executed to implement the example metadata inserter included in the example system of <figref idref="f0007">FIG. 12</figref>.</li><li><figref idref="f0013">FIG. 22</figref> is a flowchart representative of example machine readable instructions that may be executed to implement the example transcoder included in the example system of <figref idref="f0007">FIG. 12</figref>.</li><li><figref idref="f0014">FIG. 23</figref> is a block diagram of an example system to combine metering data descriptive of streaming media content.</li><li><figref idref="f0015">FIG. 24</figref> is a block diagram of a fourth example server meter that may be used to implement the example system of <figref idref="f0014">FIG. 23</figref>.</li><li><figref idref="f0016">FIG. 25</figref> is a flowchart representative of example machine readable instructions that may be executed to implement the fourth example server meter of <figref idref="f0015">FIG. 24</figref>.</li><li><figref idref="f0017">FIG. 26</figref> illustrates example metadata that may be produced by the server meter of <figref idref="f0015">FIG. 24</figref>.</li><li><figref idref="f0017">FIG. 27</figref> illustrates second example metadata that may be produced by the server meter of <figref idref="f0015">FIG. 24</figref>.</li><li><figref idref="f0018">FIG. 28</figref> is block diagram of a fifth example system for monitoring streaming media content.</li><li><figref idref="f0019">FIG. 29</figref> is a flowchart representative of example machine readable instructions that may be executed to implement the example media monitoring facility included in the example system of <figref idref="f0018">FIG. 28</figref>.</li><li><figref idref="f0020">FIG. 30</figref> is a flowchart representative of example machine readable instructions that may be executed to implement the example device meter and secondary content presenter of <figref idref="f0018">FIG. 28</figref>.</li><li><figref idref="f0021">FIG. 31</figref> is a block diagram of an example processing system that may execute the example machine readable instructions of <figref idref="f0008 f0009 f0010 f0011 f0012 f0013">FIGS. 13-22</figref>, <figref idref="f0016">25</figref>, <figref idref="f0019">29</figref> and/or 30 to implement one or more of the example systems of <figref idref="f0001">FIGS. 1</figref>, <figref idref="f0003">5</figref>,<figref idref="f0005">9</figref>,<figref idref="f0007">12</figref>,<figref idref="f0014">23</figref> and/or 28, one or more of the example server meters of <figref idref="f0002">FIGS. 2</figref>, <figref idref="f0004">6</figref>,<figref idref="f0006">10</figref> and/or 24, one or more of the example device meters of <figref idref="f0002">FIGS. 3</figref> and/or 7, and/or one or more of the example media monitoring facilities of <figref idref="f0002">FIGS. 4</figref>, <figref idref="f0004">8</figref> and/or 11.</li></ul>

DETAILED DESCRIPTION

0005The invention is defined by the independent claims.

0006Methods, apparatus and articles of manufacture to monitor streaming media content are disclosed herein. An example method disclosed herein to monitor streaming media content includes decoding a transport stream carrying media content being streamed to a content presentation device to obtain the media content. The example method also includes extracting metering data having a first format from the media content, the metering data identifying at least one of the media content or a source of the media content. The example method further includes transcoding the extracted metering data to form metering data (e.g., metering metadata) having a second format decodable by a meter executed by the content presentation device.

0007In some examples, the method additionally includes combining extracted metering data or otherwise collected metering data that is dependent on (e.g., that accompanies) the streaming media content (e.g., metering data from a provider of the media content) with metering data to be associated with the streaming media content, but provided independently of the streaming media content (e.g. metering data from an independent metering data source). In some such examples, the extracted metering data is combined with metering data from an independent metering data source, which is then transcoded to form the metering metadata. In some examples, the independent metering data source determines a timestamp from a clock source and determines an identifier for the streaming media content from a data source communicatively coupled to the independent metering data source (e.g., a configuration file). In some examples, the metering data from the independent metering data source and the extracted metering data are redundant, are identical, or are similar. In some examples, the method includes inserting, by the independent metering data source, a tag or other identifying mark within the extracted metering data to identify the independently provided metering data. In some examples, a delimiter (e.g., a text character, such as a "|" character, or some other sign or indicator) is inserted between the extracted metering data and the metering data from the independent metering data source.

0008In some examples, the method additionally includes encoding the transcoded metering data (e.g., the extracted metering data or the combined metering data after transcoding) into a metadata channel associated with (e.g., that accompanies or flows with) the transport stream, and sending the transport stream and the metadata channel to the content presentation device. In some examples, the method then includes receiving the transport stream and the metadata channel at the content presentation device, detecting the metering data in the metadata channel using the meter executed by the content presentation device, and reporting the metering data to a media monitoring facility.

0009In some examples, the metadata channel corresponds to at least one of an external metadata channel external to the transport stream carrying the media content, or an internal metadata channel comprising one or more data fields of the transport stream carrying the media content. An example of an external metadata channel includes an M3U file or other data file encoded to contain the metering metadata, and which is associated with the transport stream that is to be sent to the content presentation device.

0010In some examples, the transport stream corresponds to a Moving Picture Experts Group (MPEG) 2 transport stream sent according to a hypertext transfer protocol (HTTP) live streaming protocol. In some examples, the metering data having the first format (which is extracted from the media content decoded from the transport stream) can include an audio watermark that is embedded in an audio portion of the media content. Additionally or alternatively, the metering data having the first format (which is extracted from the media content decoded from the transport stream) can include a video (e.g., image) watermark that is embedded in a video portion of the media content. In some examples, the metering metadata having the second format into which the extracted metering data is transcoded corresponds to metadata represented in a text format, such as a text format for inclusion in an M3U file.

0011Another example method disclosed herein to monitor streaming media content includes decoding a transport stream carrying media content being streamed to a content presentation device to obtain the media content. The example method also includes extracting metering data from the media content and/or receiving metering data from an independent metering data source, the metering data identifying at least one of the media content or a source of the media content. Additionally, the example method further includes decoding content identifying metadata (e.g., such as electronic guide data, playlist data, etc.) already accompanying the transport stream carrying the media content. The example method further includes verifying the content identifying metadata using the metering data extracted from the media content.

0012In some examples, the method additionally includes reporting the results of verifying the content identifying metadata using the metering data extracted from the media content to a media monitoring facility to enable validation of content identifying metadata reported separately by a meter executed by the content presentation device. For example, the meter executed by the content presentation device can also detect the content identifying metadata accompanying the transport stream providing the streaming media content to the content presentation device. The meter can then report this content identifying metadata to the media monitoring facility, which validates the accuracy of the content identifying metadata based on the reported results of previously verifying the content identifying metadata using the metering data extracted from the media content. As noted above, in some examples, the metering data that is extracted from the media content decoded from the transport stream can include an audio watermark that is embedded in an audio portion of the media content. Additionally or alternatively, the metering data that is extracted from the media content decoded from the transport stream can include a video (e.g., image) watermark that is embedded in a video portion of the media content. Additionally or alternatively, the method can include reporting metering data received from an independent metering data source.

0013Yet another example method disclosed herein to monitor streaming media content includes storing media content (which is to be streamed to a content presentation device) in a temporary storage prior to streaming the media content to the content presentation device. The example method also includes retrieving the media content from the temporary storage, and extracting metering data from the media content (e.g., such as audio/video watermark(s) embedded in the media content), the metering data identifying at least one of the media content or a source of the media content. The method can also include combining the extracted metering data with metering data from an independent metering data source. The example method further includes reporting the metering data to a media monitoring facility.

0014Prior techniques for monitoring broadcast media content can involve extracting metering data, such as audio and/or video watermarks, from a monitored media content presentation. In the context of streaming media content, digital rights management may prevent access to the streamed media content by applications, such as a device meter, other than the media content player(s) employed by the content presentation device. Monitoring of streaming media content in accordance with examples described herein enables a device meter executed by the content presentation device to detect metering metadata identifying the streaming media content that was transcoded from a first format not decodable by the device meter (e.g., such as a first format corresponding to an audio watermark or a video watermark embedded in the media content, which is inaccessible to the device meter due to digital rights management) to a second format that is decodable by the device meter (e.g., such as a second format corresponding to a text format included in an file sent via a metadata channel accompanying the streaming media content.) Additionally or alternatively, monitoring of streaming media content in accordance with examples described herein enables content identifying metadata already accompanying the streaming media content, and decodable by the device meter without transcoding, to be validated using metering data (e.g., such as audio and/or video watermarks) extracted from the media content. While examples disclosed herein are described in the context of monitoring streaming media content, example methods and apparatus disclosed herein may be applied to monitoring non-streaming media content.

0015Turning to the figures, a block diagram of a first example system 100 for monitoring streaming media content is illustrated in <figref idref="f0001">FIG. 1</figref>. The example system 100 includes a first example server meter 105, a first example device meter 110 and a first example media monitoring facility 115 to monitor media content that is streamed to an example content presentation device 120. In the illustrated example, the system 100 includes example compression gear 130, an example segmenter and packager 135, an example digital rights manager 140 and an example content streamer 145 to provide the streaming media content, which is provided by example content provider(s) 125, to the content presentation device 120. The example system 100 further includes an example network 150 via which media content can be streamed by the content streamer 145 to the content presentation device 120, and via which the device meter 110 can report metering data to the media monitoring facility 115.

0016The content provider(s) 125 of the illustrated example correspond to any one or more content providers capable of providing media content for streaming to the content presentation device 120. The media content provided by the content provider(s) 125 can be any type of media content, such as audio content, video content, multimedia content, etc. Additionally, the media content can correspond to live (e.g., broadcast) media content, stored media content (e.g., on-demand content), etc.

0017The compression gear 130 employs any appropriate technique(s) to compress and/or otherwise process the received media content into a form suitable for streaming. For example, the compression gear 130 may compress the media content in accordance with MPEG 4 audio/video compression. The segmenter and packager 135 employs any appropriate technique(s) to segment and package the compressed media content into a form suitable for streaming. For example, the segmenter and packager 135 can segment and package the compressed media content into one or more MPEG 2 transport streams for streaming to the content presentation device 120 via the network 150 using HTTP live streaming (HLS) or any other past, present and/or future, streaming protocol. The digital rights manager 140 encrypts and/or otherwise protects, in accordance with any appropriate digital rights management technique and/or protocol, the media content to be streamed. The content streamer 145 employs any appropriate technique(s) to select and stream the media content to a requesting device, such as the content presentation device 120. For example, the content streamer 145 can select media content that has been MPEG 4 compressed, segmented and packaged into one or more MPEG 2 transport streams, and encrypted for digital rights management, and then stream the content to the content presentation device 120 via the network 150 using HLS or any other streaming protocol.

0018In some examples, the compression gear 130, the segmenter and packager 135 and/or the digital rights manager 140 prepare content for streaming regardless of whether (e.g., prior to) a request is received from the content presentation device 120. In such an example, the content streamer 145 prepares a transport stream for streaming the already-prepared content to the content presentation device 120 when a request is received from the content presentation device 120. In other examples, the compression gear 130, the segmenter and packager 135 and/or the digital rights manager 140 prepare the content for streaming in response to a request received from the content presentation device 120.

0019The content presentation device 120 of the illustrated example is a computing device that is capable of presenting streaming media content provided by the content streamer 145 via the network 150. The content presentation device 120 may be, for example, a desktop computer, a laptop computer, a mobile computing device, a television, a smart phone, a mobile phone, an Apple^® iPad^®, an Apple^® iPhone^®, an Apple^® iPod^®, an AndroidTM powered computing device, a Palm^® webOS^® computing device, etc. In some examples, the content presentation device 120 includes one or more executable media players to present the streaming media content provided by the content streamer 145. For examples, the media player(s) available to the content presentation device 120 may be implemented in Adobe^® Flash^® (e.g., provided in a SWF file), may be implemented in hypertext markup language (HTML) version 5 (HTML5), may be implemented in Google^® Chromium^®, may be implemented according to the Open Source Media Framework (OSMF), may be implemented according to a device or operating system provider's media player application programming interface (API), may be implemented on a device or operating system provider's media player framework (e.g., the Apple^® iOS^® MPMoviePlayer software), etc., or any combination thereof. While a single content presentation device 120 is illustrated, any number and/or type(s) of content presentation devices may be included in the system 100.

0020The network 150 of the illustrated example is the Internet. Additionally or alternatively, any other network(s) linking the content streamer 145, the content presentation device 120, the device meter 110 and/or the media monitoring facility 115 may be used. The network 150 may comprise any number of public and/or private networks using any type(s) of networking protocol(s).

0021As noted above, media content provided by the content provider(s) 125 may include metering data, such as embedded audio and/or video watermarks, that identifies and/or is otherwise associated with the media content. However, such metering data may not be accessible by and, thus, may not be decodable by a device meter at the content presentation device 120. For example, the media content and, by extension, the audio and/or video watermarks embedded therein may be accessible only to an appropriate media player, and not a device meter or other application, due to the digital rights management techniques employed by the digital rights manager 140. To enable the device meter 120 to have access to and be able to decode metering data identifying and/or otherwise associated with streaming media content provided to the content presentation device 120, the system 100 of the illustrated example includes the server meter 105. In some examples, the server meter 105 is implemented as a plug-in or other application/device associated with or executed by one or more of the compression gear 130, the segmenter and packager 135, the digital rights manager 140 and/or the content streamer 145. In some examples, the server meter 105 is implemented by an apparatus separate from the compression gear 130, the segmenter and packager 135, the digital rights manager 140 and the content streamer 145.

0022In the illustrated example, the server meter 105 obtains, from the media content, metering data that is in a first format. In some examples the server meter 105 may also collect metering data from one or more independent metering data sources. The metering data from the independent metering data sources may be in the first format or any other format(s). The server meter 105 then transcodes the obtained metering data (e.g., the extracted metering data and/or the metering data from the independent metering data source) to form metering metadata that is in a second format accessible and decodable by the device meter 110. The metering data identifies the media content, identifies a source of the media content, and/or otherwise describes and/or is associated with the media content. For example, the server meter 105 can obtain embedded audio/video watermarks that correspond to metering data having a first format and/or the server meter 105 can obtain metering data from an independent metering data source. Then, the server meter 105 transcodes this metering data into text data, binary data, etc., that corresponds to metering metadata in a second format. The server meter 105 then encodes the transcoded metering metadata (which is in the second format that is decodable by the device meter 110 executed by or otherwise associated with the content presentation device 120) into a metadata channel associated with the transport stream(s) that is(are) to carry the streaming media content to the presentation device 120. In some examples, the server meter 105 is implemented as a plug-in based on a software development kit (SDK) provided by the entity that embedded the audio/video watermarks in the media content. In such examples, the server meter 105 can employ functionality provided by the SDK to extract and decode audio/video watermark(s) embedded in the media content to obtain the payload data carried by the watermark(s). In some examples, in accordance with one or more versions of the ID3 tagging standards, the server meter 105 then inserts the payload data obtained from the watermark(s) as ID3 tag metadata and/or other metadata in the transport stream(s) that is (are) to stream the media content in accordance with the HLS or other appropriate streaming protocol. Another example implementation of the server meter 105 is illustrated in <figref idref="f0002">FIG. 2</figref>, which is described in greater detail below.

0023The server meter 105 can also employ functionality provided by the SDK to collect metering data from an independent metering data source (e.g. such as by receiving data from an internal clock, receiving content identification information from a user input, receiving content identification information from a file, or another source that is independent of the provider of the media content). An example implementation of the server meter 105 that includes an independent metering data source is described in conjunction with <figref idref="f0015">FIG. 24</figref>.

0024The system 100 also includes the device meter 110 to monitor streaming media content provided to and/or presented by the content presentation device 120. In the illustrated example, the device meter 110 is executed by the content presentation device 120. In some examples, the device meter 110 may be implemented as a plug-in that is connected to a plug-in interface of a media player executed by the content presentation device 120. In some examples, the device meter 110 may be implemented as one or more instructions that are incorporated in a media player executed by the content presentation device 120. In some examples, the device meter 110 may be implemented as an executable application that is downloaded to the content presentation device 120 (e.g., downloaded as an App from the Apple^® App Store.) In some examples, the device meter 110 is implemented by an apparatus separate from the content presentation device 120, but that is able to access metadata (e.g., via one or more digital interfaces, data ports, etc., of the content presentation device 120) associated with streaming media content received by the content presentation device 120.

0025The device meter 110 of the illustrated example decodes metering metadata included in a metadata channel (or channels) associated with (e.g., provided prior to or accompanying and flowing with) the transport channel(s) providing the streaming media content to the content presentation device 120. For example, a metadata channel decoded by the device meter 110 can correspond to an external metadata channel external to the transport stream carrying the media content, or an internal metadata channel comprising one or more data fields of the transport stream carrying the media content. An example external metadata channel includes an M3U file or other text file associated with a transport stream carrying the streaming media content and containing metering metadata transcoded by the server meter 105 into a text or other appropriate data format. In some examples, such as an example employing the HLS protocol, the device meter 110 extracts and decodes ID3 tag(s) that contain the metering metadata. The device meter 110 of the illustrated example stores the decoded metering metadata (as well as any other metering information captured by the device meter, timestamps added by the device meter 110 to the decoded metering metadata and/or the other metering information, etc.) for reporting to the media monitoring facility 115. In the illustrated example, the device meter 110 reports its stored metering metadata (as well as any other metering information, timestamps, etc.) using an HTTP request sent to an HTTP interface of the media monitoring facility 115. An example implementation of the device meter 110 is illustrated in <figref idref="f0002">FIG. 3</figref>, which is described in greater detail below.

0026The media monitoring facility 115 includes an interface to receive reported metering information (e.g., metering metadata) received from the device meter 110 via the network 150. In the illustrated example, the media monitoring facility 115 includes an HTTP interface to receive HTTP requests that include metering information. Alternatively, any other method(s) to receive metering information may be used. In the illustrated example, the media monitoring facility 115 stores and analyzes metering information received from a plurality of different content presentation devices 120. For example, the media monitoring facility 115 may group metering information by content provider 125 (e.g., group all metering data associated with a particular content provider 125). The media monitoring facility 115 may also analyze the metering information to eliminate erroneous information. For example, the media monitoring facility 115 may compare two types of identifying information received for the same media content (e.g., by comparing content identifying metadata already accompanying the streaming media content with metering data and/or metadata determined by the device meter 110 and/or server meter 105) to identify discrepancies, may eliminate metering information containing discrepancies, and/or may mark certain identifying information as erroneous to be excluded from metering information received at a later time. Any other processing of metering information may additionally or alternatively be performed.

0027In some examples, the reported metering information includes metering data that was obtained by a dependent metering data source and an independent metering data source. Dependent metering data sources include, for example, sources of metering data obtained from, associated with or otherwise dependent on the media content and/or transport stream(s) providing the media content. For example, a dependent metering data source can include metering data extracted from a watermark payload of the streaming media content. In contrast, independent metering data sources include, for example, sources of metering data obtained independently from the media content and/or transport stream(s) providing the media content, but which can nevertheless be descriptive of the media content. For example, an independent metering data source can include redundant metering data, such as metering data that is the same as the metering data obtained from the dependent metering data source, metering data that is similar to the metering data obtained from the dependent metering data source, etc., but that was obtained by an independent metering data source (e.g., such as a source identifier that is stored in a configuration file at the server meter 105). In such examples, the media monitoring facility 115 may utilize the redundant metering data to verify the metering data from the dependent metering data source. Example metadata with redundant metering data obtained from an independent metering data source is described in conjunction with <figref idref="f0017">FIG. 26</figref>. In some examples, the media monitoring facility 115 may store and analyze both the redundant metering data and the metering data from the dependent metering data source. In some examples, the media monitoring facility 115 can store and/or analyze the redundant metering data when the metering data from the dependent metering data source is unreadable by the media monitoring facility 115. For example, the metering data from the dependent metering data source may fail an error check, be blank, or be null when an audio/video watermark is not able to be extracted from the streaming media content by the server meter 105 (e.g., an audio watermark may be unavailable during a silent portion of the streaming media content). Example metadata with unreadable metering data from a dependent metering data source is described in conjunction with <figref idref="f0017">FIG. 27</figref>.

0028The media monitoring facility 115 of the illustrated example also analyzes the received metering information reported by the content presentation device(s) 120 to generate reports concerning the presentation of media content. For example, the media monitoring facility 115 may generate reports indicating the number of times that media content was accessed, demographics for users that accessed the media content, interactions of users with the media content (e.g., fast-forwarding, pausing, etc.), the duration of accesses of the media content, etc. The media monitoring facility 115 may, for example, provide a webpage interface through which interested parties can generate custom reports or otherwise access the metering information (e.g., for a fee or part of a subscription service). For example, the media monitoring facility 115 may generate reports for a particular content provider 125, for advertisers that distribute advertisements via the content provider(s) 125, for competitors of the content provider(s) 125, etc. An example implementation of the media monitoring facility 115 is illustrated in <figref idref="f0002">FIG. 4</figref>, which is described in greater detail below.

0029A block diagram of an example implementation of the example server meter 105 of <figref idref="f0001">FIG. 1</figref> is illustrated in <figref idref="f0002">FIG. 2</figref>. The example server meter 105 of <figref idref="f0002">FIG. 2</figref> includes an example transport stream decoder 205 to decode transport stream(s) carrying streaming media content to obtain the media content being streamed to the content presentation device 120. For example, the transport stream decoder 205 can decode an MPEG 2 transport 2 encapsulating MPEG 4 compressed media content to obtain the encapsulated MPEG 4 content, and then perform MPEG 4 decompression to obtain the uncompressed audio/video content.

0030The example server meter 105 of <figref idref="f0002">FIG. 2</figref> also includes an example metering data extractor 210 to extract metering data having a first format from the uncompressed media content obtained from the transport stream decoder 205. For example, the metering data extractor 210 can implement functionality provided by an SDK to extract one or more audio watermarks, one or more video (e.g., image) watermarks, etc., embedded in the uncompressed audio/video content obtained from the transport stream decoder 205. (For example, the uncompressed audio/video content may correspond to uncompressed pulse code modulation (PCM) audio data or other types of audio data, uncompressed video/image data, etc.) To transcode the metering data in the first format obtained from the metering data extractor 210 to a second format decodable by the device meter 110, the example server meter 105 of <figref idref="f0002">FIG. 2</figref> further includes an example metering data transcoder 215. For example, the metering data transcoder 215 can determine (e.g., decode) the metering information (e.g., the watermark payload data, such as content identifying information, source identifying information, etc.) carried by a watermark extracted by the metering data extractor 210 and convert this metering information (also referred to as watermark payload data) into a text or binary format for inclusion in an M3U8 file or other data (e.g., text, binary, etc.) file for transmission as metadata (e.g., such as with a playlist or electronic program guide) accompanying the streaming media content. Additionally or alternatively, the metering data transcoder 215 can convert the extracted metering information (i.e., watermark payload data) into a binary or other appropriate format for inclusion in one or more data fields capable of carrying metadata in the transport stream(s) providing the streaming media content to the content presentation device 120. For example, the metering data transcoder 215 can convert watermark payload data corresponding to the metering information to ID3 tag metadata for insertion in the transport stream(s) that is (are) to stream the media content in accordance with the HLS or other appropriate streaming protocol. Other additional or alternative examples of transcoding that can be employed by the metering data transcoder 215 to transcode metering data into a format decodable by the device meter 110 are described in, for example, <patcit id="pcit0004" dnum="US7827312B"><text>U.S. Patent No. 7,827,312 ("METHODS AND APPARATUS FOR TRANSCODING METADATA" to Ramaswamy et al.), which issued on November 2, 2010</text></patcit>, and <patcit id="pcit0005" dnum="US61442758" dnum-type="L"><text>U.S. Provisional Application Serial No. 61/442,758 ("METHODS AND APPARATUS TO MONITOR MEDIA CONTENT AT A CONTENT DISPLAY SITE" to Deliyannis et al.), which was filed on February 14, 2011</text></patcit>. <patcit id="pcit0006" dnum="US7827312B"><text>U.S. Patent No. 7,827,312</text></patcit> and <patcit id="pcit0007" dnum="US61442758" dnum-type="L"><text>U.S. Provisional Application Serial No. 61/442,758</text></patcit>. In some examples, the metering data extractor 210 may be replaced by or include one or more of the elements of <figref idref="f0015">FIG. 24</figref>, which enables the server meter 505 to operate in accordance with the system described in conjunction with <figref idref="f0014">FIG. 23</figref>.

0031Additionally, in some examples, the server meter 105 of <figref idref="f0002">FIG. 2</figref> includes an example metering metadata encryptor 220 that employs any appropriate encryption to encrypt the metering metadata determined by the metering data transcoder 215. For example, the metering metadata encryptor 220 can encrypt the metering metadata using public or private key encryption such that the decryption key(s) are known and protected by the media monitoring facility 115. Inclusion of the metering metadata encryptor 220 can prevent unauthorized eavesdroppers from accessing the transcoded metering metadata identifying or otherwise associated with the streaming media content, thereby securing the privacy of users consuming the streaming media content.

0032In the illustrated example of <figref idref="f0002">FIG. 2</figref>, the server meter 105 includes an example transport stream encoder 225 to re-encode the transport stream(s) carrying the streaming media content to include the metering metadata determined by the metering data transcoder 215 (and encrypted by the metering metadata encryptor 220, as appropriate). For example, the transport stream encoder 225 can encode the metering metadata into an external metadata channel, such as by encoding an M3U8 or other data file to contain the metering metadata and to be associated with (e.g., included in, appended to, sent prior to, etc.) the transport stream(s) that are to provide the streaming media content to the content presentation device 120. Additionally or alternatively, the transport stream encoder 225 can encode the metering metadata into an internal metadata channel, such as by encoding metering metadata that is in a binary or other appropriate data format into one or more data fields of the transport stream(s) that is(are) capable of carrying metadata. For example, the transport stream encoder 225 can insert ID3 tag metadata corresponding to the metering metadata into the transport stream(s) that is (are) to stream the media content in accordance with the HLS or other appropriate streaming protocol.

0033A block diagram of an example implementation of the example device meter 110 of <figref idref="f0001">FIG. 1</figref> is illustrated in <figref idref="f0002">FIG. 3</figref>. The example device meter 110 of <figref idref="f0002">FIG. 3</figref> includes an example metering metadata extractor 305 to extract metering metadata from external and/or internal metadata channels associated with transport stream(s) providing streaming media content to the content presentation device 120. For example, the metering metadata extractor 305 can extract metering metadata from an external metadata channel (or more than one external metadata channel), such as by decoding an M3U8 or other data file that contains metering metadata and that is associated with (e.g., included in, appended to, sent prior to, etc.) the transport stream(s) providing the streaming media content to the content presentation device 120. Additionally or alternatively, the metering metadata extractor 305 can extract metering metadata from an internal metadata channel (or more than one internal metadata channel), such as by decoding metering metadata from one or more data fields of the transport stream(s) that is(are) capable of carrying metadata. In some examples, such as an example employing the HLS protocol, the metering metadata extractor 305 extracts and decodes ID3 tag(s) that contain the metering metadata.

0034The example device meter 110 of <figref idref="f0002">FIG. 3</figref> also includes an example metering metadata reporter 310 to report the metering metadata obtained by the metering metadata extractor 305 to the media monitoring facility 115. For example, the metering metadata reporter 310 may generate a GET or POST request including the metering metadata as a parameter of the request. Alternatively, any other method of transmitting the metering metadata to the media monitoring facility 115 may be used. The metering metadata may be transmitted at any interval. For example, the metering metadata may be transmitted as it is collected (e.g., streamed), may be transmitted when a certain amount of metering metadata is collected, when an available memory space is filled or reaches a threshold capacity (e.g., 90% or some other percentage being full), when a particular event is detected (e.g., when presentation of the media content ends, when new media content is presented, etc.), whenever new metering metadata is obtained, etc. The metadata reporter 310 may transmit metering metadata once for each media content or may transmit metering metadata multiple times (e.g., every time an event occurs, every time identifying information changes (e.g., when the media content includes metering data that change throughout the media content, etc.).

0035In some examples, the device meter 110 may determine metering information in addition to the metering metadata extracted by the metering metadata extractor 305. For example, the device meter 110 may collect other metadata (e.g., such as other content identifying metadata) already accompanying the transport stream(s) providing the streaming media content. Additionally or alternatively, in some examples, the device meter 110 may collect information describing usage of the media player presenting the media content, other usage of the content presentation device 120 while the media content is being presented, etc., or any combination thereof. In such examples, the metering metadata reporter 310 can use one or more of the example mechanisms described above to report this additional metering information to the media monitoring facility 115 along with, or separate from, the metering metadata extracted by the metering metadata extractor 305.

0036A block diagram of an example implementation of the example media monitoring facility 115 of <figref idref="f0001">FIG. 1</figref> is illustrated in <figref idref="f0002">FIG. 4</figref>. The example media monitoring facility 115 of <figref idref="f0002">FIG. 2</figref> includes an example metering metadata collector 405 to collect the metering metadata (and other metering information) reported by the device meter 110. As described above, the metering metadata collector 405 of the illustrated example includes an HTTP interface to receive HTTP requests that include metering information. Additionally or alternatively, any other method(s) to receive metering information may be used. The metering metadata collector 405 also stores (e.g., collects) and analyzes the received metering information, as described above in connection with <figref idref="f0001">FIG. 1</figref>. The example media monitoring facility 115 of <figref idref="f0002">FIG. 2</figref> also includes an example report generator 410 to generate reports based on the reported metering information, as described above in connection with <figref idref="f0001">FIG. 1</figref>.

0037A block diagram of a second example system 500 for monitoring streaming media content is illustrated in <figref idref="f0003">FIG. 5</figref>. The second example system 500 includes many elements in common with the first example system 100 of <figref idref="f0001">FIG. 1</figref>. As such, like elements in <figref idref="f0001">FIGS. 1</figref> and <figref idref="f0003">5</figref> are labeled with the same reference numerals. The detailed descriptions of these like elements are provided above in connection with the discussion of <figref idref="f0001">FIG. 1</figref> and, in the interest of brevity, are not repeated in the discussion of <figref idref="f0003">FIG. 5</figref>.

0038Turning to <figref idref="f0003">FIG. 5</figref>, the illustrated example system 500 includes the compression gear 130, the segmenter and packager 135, the digital rights manager 140 and the content streamer 145 to provide streaming media content to the content presentation device 120 via the network 150. To provide media content to the system 500, the illustrated example of <figref idref="f0003">FIG. 5</figref> includes the content provider(s) 125. To monitor media content that is streamed to the content presentation device 120, the system 500 of the illustrated examples also includes a second example server meter 505, a second example device meter 510 and a second example media monitoring facility 515. In some examples, the server meter 505 may be implemented as a plug-in or other application/device associated with or executed by one or more of the compression gear 130, the segmenter and packager 135, the digital rights manager 140 and/or the content streamer 145. In some examples, the server meter 505 may be implemented by an apparatus separate from the compression gear 130, the segmenter and packager 135, the digital rights manager 140 and the content streamer 145. In some examples, the device meter 510 may be implemented as a plug-in that is connected to a plug-in interface of a media player executed by the content presentation device 120. In some examples, the device meter 510 may be implemented as one or more instructions provided that are incorporated in a media player executed by the content presentation device 120. In some examples, the device meter 510 may be implemented as an executable application that is downloaded to the content presentation device 120 (e.g., downloaded as an App from the Apple^® App Store.) In some examples, the device meter 510 is implemented by an apparatus separate from the content presentation device 120, but that is able to access metadata (e.g., via one or more digital interfaces, data ports, etc., of the content presentation device 120) associated with streaming media content received by the content presentation device 120.

0039The server meter 505 of the illustrated example decodes transport stream(s) carrying media content to be streamed to the content presentation device 120, and extracts metering data from the decoded media content. The metering data identifies the media content, identifies a source of the media content, and/or otherwise describes and/or is associated with the media content. For example, the server meter 505 can extract audio and/or video watermarks embedded in the media content. Additionally, the server meter 505 decodes content identifying metadata (e.g., such as electronic guide data, playlist data, etc.) already accompanying the transport stream(s) carrying the media content to be streamed to the content presentation device 120. In some examples, the server meter 505 uses the metering data extracted from the media content to verify the content identifying metadata already accompanying the transport stream(s) carrying the media content. For example, electronic guide data, playlist data, etc., can have errors or be out-of-date. Using the metering data extracted from the media content to verify this content identifying metadata enables the media monitoring facility 515 to know whether the content identifying metadata already accompanying the transport stream(s) carrying the media content is accurate and, thus, can be used for media monitoring purposes. An example implementation of the server meter 505 is illustrated in <figref idref="f0004">FIG. 6</figref>, which is described in greater detail below.

0040The system 500 includes the device meter 510 to monitor streaming media content presented by the content presentation device 120. The device meter 510 of the illustrated example decodes content identifying metadata (e.g., such as electronic guide data, playlist data, etc.) already accompanying the transport stream(s) carrying the media content being streamed to the content presentation device 120. The device meter 510 stores the content identifying metadata (as well as any other metering information captured by the device meter) for reporting to the media monitoring facility 515. In the illustrated example, the device meter 510 reports its stored content identifying metadata (as well as any other metering information) using an HTTP request sent to an HTTP interface of the media monitoring facility 515. An example implementation of the device meter 510 is illustrated in <figref idref="f0004">FIG. 7</figref>, which is described in greater detail below.

0041The media monitoring facility 515 includes an interface to receive reported content identifying metadata received from the device meter 510 via the network 150. The media monitoring facility 515 also includes an interface to receive verification results from the server meter 505 indicating whether the content identifying metadata reported by the device meter 510 is valid (e.g., whether this content identifying metadata is accurate). Assuming the content identifying metadata is valid, the media monitoring facility 515 can store, analyze and generate reports based on the reported content identifying metadata using techniques similar to those employed by the media monitoring facility 115 to process the reported metering metadata. An example implementation of the media monitoring facility 515 is illustrated in <figref idref="f0004">FIG. 8</figref>, which is described in greater detail below.

0042A block diagram of an example implementation of the example server meter 505 of <figref idref="f0003">FIG. 5</figref> is illustrated in <figref idref="f0004">FIG. 6</figref>. Like the example server meter 105 of <figref idref="f0002">FIG. 2</figref>, the example server meter 505 of <figref idref="f0004">FIG. 6</figref> includes the transport stream decoder 205 to decode transport stream(s) carrying streaming media content to obtain the media content being streamed to the content presentation device 120. Like the example server meter 105 of <figref idref="f0002">FIG. 2</figref>, the example server meter 505 of <figref idref="f0004">FIG. 6</figref> also includes the metering data extractor 210 to extract metering data, such as one or more audio watermarks, one or more video (e.g., image) watermarks, etc., embedded in the media content obtained from the transport stream decoder 205. Further descriptions of these elements are provided above in connection with the discussion of <figref idref="f0002">FIG. 2</figref> and, in the interest of brevity, are not repeated in the discussion of <figref idref="f0004">FIG. 6</figref>.

0043The example server meter 505 of <figref idref="f0003">FIG. 5</figref> further includes an example content metadata extractor 605 to extract content identifying metadata (and/or other content descriptive information) already accompanying the transport stream(s) that carry the streaming media content. For example, the content metadata extractor 605 can extract content identifying metadata from a playlist, an electronic program guide, a data file, etc., already accompanying (e.g., already included in, appended to, sent prior to, etc.) the transport stream(s) that are to provide the streaming media content to the content presentation device 120. The example server meter 505 of <figref idref="f0003">FIG. 5</figref> additionally includes an example metadata verifier 610 to compare the content identifying metadata obtained by the content metadata extractor 605 with the metering data obtained from the metering data extractor 210 to determine whether the content identifying metadata is valid (e.g., is correct, accurate, up-to-date, etc.). The metadata verifier 610 also reports the verification results to the media monitoring facility 515 via the network 150 (e.g., using one or more HTTP requests).

0044A block diagram of an example implementation of the example device meter 510 of <figref idref="f0003">FIG. 5</figref> is illustrated in <figref idref="f0004">FIG. 7</figref>. The example device meter 510 of <figref idref="f0004">FIG. 7</figref> includes an example content metadata extractor 705 to extract content identifying metadata (and/or other content descriptive information) already accompanying the transport stream(s) providing the streaming media content to the content presentation device 130. For example, the content metadata extractor 705, like the content metadata extractor 605 of <figref idref="f0004">FIG. 6</figref>, can extract content identifying metadata from a playlist, an electronic program guide, a data file, etc., already accompanying (e.g., already included in, appended to, sent prior to, etc.) the transport stream(s) providing the streaming media content to the content presentation device 120.

0045The example device meter 510 of <figref idref="f0004">FIG. 7</figref> also includes an example content metadata reporter 710 to report the content identifying metadata obtained by the content metadata extractor 705 to the media monitoring facility 515. For example, the content metadata reporter 710 may generate a GET or POST request including the content identifying metadata as a parameter of the request. Alternatively, any other method of transmitting the content identifying metadata to the media monitoring facility 515 may be used. The content identifying metadata may be transmitted at any interval. For example, the content identifying metadata may be transmitted as it is collected (e.g., streamed), may be transmitted when a certain amount of content identifying metadata is collected, when an available memory space is filled or reaches a threshold capacity (e.g., 90% or some other percentage being full), when a particular event is detected (e.g., when presentation of the media content ends, when new media content is presented, etc.), whenever new content identifying metadata is obtained, etc. The content metadata reporter 710 may transmit content identifying metadata once for each media content or may transmit content identifying metadata multiple times (e.g., every time an event occurs, every time identifying information changes, etc.).

0046In some examples, the device meter 510 may determine metering information in addition to the content identifying metadata extracted by the content metadata extractor 705. For example, the device meter 510 may collect information describing usage of the media player presenting the media content, other usage of the content presentation device 120 while the media content is being presented, etc., or any combination thereof. In such examples, the content metadata reporter 710 can use one or more of the example mechanisms described above to report this additional metering information to the media monitoring facility 515 along with, or separate from, the content identifying metadata extracted by the content metadata extractor 705.

0047A block diagram of an example implementation of the example media monitoring facility 515 of <figref idref="f0003">FIG. 5</figref> is illustrated in <figref idref="f0004">FIG. 8</figref>. The example media monitoring facility 515 of <figref idref="f0004">FIG. 8</figref> includes an example content metadata collector 805 to collect the content identifying metadata (and other metering information) reported by the device meter 510. As described above, the content metadata collector 805 of the illustrated example includes an HTTP interface to receive HTTP requests that include metering information. Additionally or alternatively, any other method(s) to receive metering information may be used. The content metadata collector 805 also stores (e.g., collects) and analyzes the received metering information (e.g., based on verification results received from a content metadata validator 810), as described above in connection with <figref idref="f0003">FIG. 5</figref>.

0048The example media monitoring facility 515 of <figref idref="f0004">FIG. 8</figref> also includes an example content metadata validator 810 to receive verification results concerning the validity of the content identifying information that is to be received by the content metadata collector 805. For example, the content metadata validator 810 includes an HTTP interface to receive HTTP requests that include verification results reported by the server meter 505. The content metadata collector 805 can use the verification results received by the content metadata validator 810 to determine whether the content identifying metadata is valid (e.g., is correct, accurate, up-to-date, etc.). The example media monitoring facility 515 of <figref idref="f0004">FIG. 8</figref> further includes an example report generator 815 to generate reports based on the reported metering information, as described above in connection with <figref idref="f0003">FIG. 5</figref>.

0049A block diagram of a third example system 900 for monitoring streaming media content is illustrated in <figref idref="f0005">FIG. 9</figref>. The third example system 900 includes elements in common with the first example system 100 of <figref idref="f0001">FIG. 1</figref>. As such, like elements in <figref idref="f0001">FIGS. 1</figref> and <figref idref="f0005">9</figref> are labeled with the same reference numerals. The detailed descriptions of these like elements are provided above in connection with the discussion of <figref idref="f0001">FIG. 1</figref> and, in the interest of brevity, are not repeated in the discussion of <figref idref="f0005">FIG. 9</figref>.

0050Turning to <figref idref="f0005">FIG. 9</figref>, the illustrated example system 900 includes the compression gear 130, the segmenter and packager 135, the digital rights manager 140 and the content streamer 145 to provide streaming media content to the content presentation device 120 via the network 150. To provide media content to the system 900, the illustrated example of <figref idref="f0005">FIG. 9</figref> includes the content provider(s) 125. To monitor media content that is streamed to the content presentation device 120, the system 900 of the illustrated examples also includes a third example server meter 905 and a third example media monitoring facility 915. In some examples, the server meter 905 may be implemented as a plug-in or other application/device associated with or executed by one or more of the compression gear 130, the segmenter and packager 135, the digital rights manager 140 and/or the content streamer 145. In some examples, the server meter 905 may be implemented by an apparatus separate from the compression gear 130, the segmenter and packager 135, the digital rights manager 140 and the content streamer 145.

0051In the system 900 of the illustrated example, a copy of media content being streamed to the content presentation device 120 is stored in a temporary content storage 920 for subsequent processing. The temporary content storage 920 can be implemented by any memory or storage device or devices, such as one or more of the mass storage device 3130 and/or the volatile memory 3118 illustrated in <figref idref="f0021">FIG. 31</figref>, which is described in greater detail below. The media content can be stored in the temporary content storage 920 in any appropriate data format.

0052The server meter 905 of the illustrated example extracts metering data from the media content stored in the temporary content storage 920. The metering data identifies the media content, identifies a source of the media content, and/or otherwise describes and/or is associated with the media content. For example, the server meter 905 can extract audio and/or video watermarks embedded in the media content. In the illustrated example, the server meter 905 reports the extracted metering data (as well as any other metering information) using an HTTP request sent to an HTTP interface of the media monitoring facility 915. An example implementation of the server meter 905 is illustrated in <figref idref="f0006">FIG. 10</figref>, which is described in greater detail below.

0053The media monitoring facility 915 includes an interface to receive reported metering metadata received from the server meter 905 via the network 150. The media monitoring facility 515 can store, analyze and generate reports based on the reported metering data using techniques similar to those employed by the media monitoring facility 115 to process the reported metering metadata. An example implementation of the media monitoring facility 915 is illustrated in <figref idref="f0006">FIG. 11</figref>, which is described in greater detail below.

0054A block diagram of an example implementation of the example server meter 905 of <figref idref="f0005">FIG. 9</figref> is illustrated in <figref idref="f0006">FIG. 10</figref>. The example server meter 905 of <figref idref="f0006">FIG. 10</figref> includes a media content retriever 1005 to retrieve from the temporary content storage 920 a copy of media content that is to be streamed to the content presentation device 120. Like the example server meter 105 of <figref idref="f0002">FIG. 2</figref>, the example server meter 905 of <figref idref="f0006">FIG. 10</figref> also includes the metering data extractor 210 to extract metering data, such as one or more audio watermarks, one or more video (e.g., image) watermarks, etc., embedded in the media content obtained from the media content retriever 1005. Further description of the metering data extractor 210 is provided above in connection with the discussion of <figref idref="f0002">FIG. 2</figref> and, in the interest of brevity, is not repeated in the discussion of <figref idref="f0004">FIG. 6</figref>. In some examples, the metering data extractor 210 may be replaced by or include one or more of the elements of <figref idref="f0015">FIG. 24</figref>, which enables the server meter 905 to operate in accordance with the system described in conjunction with <figref idref="f0014">FIG. 23</figref>.

0055The example server meter 905 of <figref idref="f0006">FIG. 10</figref> further includes an example metering data reporter 1010 to report the metering data obtained by the metering data extractor 210 to the media monitoring facility 915. For example, the metering data reporter 1010 may generate a GET or POST request including the metering data as a parameter of the request. Alternatively, any other method of transmitting the metering data to the media monitoring facility 915 may be used. The metering data may be transmitted at any interval. For example, the metering data may be transmitted as it is collected (e.g., streamed), may be transmitted when a certain amount of metering data is collected, when an available memory space is filled or reaches a threshold capacity (e.g., 90% or some other percentage being full), when a particular event is detected (e.g., when presentation of the media content ends, when new media content is presented, etc.), whenever new metering data is obtained, etc. The metering data reporter 1010 may transmit metering data once for each media content or may transmit metering data multiple times (e.g., every time an event occurs, every time identifying information changes, etc.).

0056A block diagram of an example implementation of the example media monitoring facility 915 of <figref idref="f0005">FIG. 9</figref> is illustrated in <figref idref="f0006">FIG. 11</figref>. The example media monitoring facility 915 of <figref idref="f0005">FIG. 9</figref> includes an example metering data collector 1105 to collect the metering data reported by the server meter 905. As described above, the metering data collector 1105 of the illustrated example includes an HTTP interface to receive HTTP requests that include metering information. Additionally or alternatively, any other method(s) to receive metering information may be used. The metering data collector 1105 also stores (e.g., collects) and analyzes the received metering information, as described above in connection with <figref idref="f0005">FIG. 9</figref>. The example media monitoring facility 915 of <figref idref="f0006">FIG. 11</figref> also includes an example report generator 1110 to generate reports based on the reported metering information, as described above in connection with <figref idref="f0005">FIG. 9</figref>.

0057While example manners of implementing the server meters 105, 505 and 905, the device meters 110 and 510, and the media monitoring facilities 115, 515 and 915 of <figref idref="f0001">FIGS. 1</figref>, <figref idref="f0003">5</figref> and <figref idref="f0005">9</figref> have been illustrated in <figref idref="f0002">FIGS. 2-4</figref>, <figref idref="f0004">6-8</figref> and <figref idref="f0006">10-11</figref>, one or more of the elements, processes and/or devices illustrated in <figref idref="f0002">FIGS. 2-4</figref>, <figref idref="f0004">6-8</figref> and <figref idref="f0006">10-11</figref> may be combined, divided, re-arranged, omitted, eliminated and/or implemented in any other way. Further, the example transport stream decoder 205, the metering data extractor 210, the example metering data transcoder 215, the example metering metadata encryptor 220, the example transport stream encoder 225, the example metering metadata extractor 305, the example metering metadata reporter 310, the example metering metadata collector 405, the example report generator 410, the example content metadata extractor 605, the example metadata verifier 610, the example content metadata extractor 705, the example content metadata reporter 710, the example content metadata collector 805, the example content metadata validator 810, the example report generator 815, the example media content retriever 1005, the example metering data reporter 1010, the example metering data collector 1105, the example report generator 1110 and/or, more generally, one or more of the example server meters 105, 505 and/or 905, one or more of the example device meters 110 and/or 510, and/or one or more of the example media monitoring facilities 115, 515 and/or 915 of <figref idref="f0002">FIGS. 2-4</figref>, <figref idref="f0004">6-8</figref> and <figref idref="f0006">10-11</figref> may be implemented by hardware, software, firmware and/or any combination of hardware, software and/or firmware. Thus, for example, any of the example transport stream decoder 205, the metering data extractor 210, the example metering data transcoder 215, the example metering metadata encryptor 220, the example transport stream encoder 225, the example metering metadata extractor 305, the example metering metadata reporter 310, the example metering metadata collector 405, the example report generator 410, the example content metadata extractor 605, the example metadata verifier 610, the example content metadata extractor 705, the example content metadata reporter 710, the example content metadata collector 805, the example content metadata validator 810, the example report generator 815, the example media content retriever 1005, the example metering data reporter 1010, the example metering data collector 1105, the example report generator 1110 and/or, more generally, one or more of the example server meters 105, 505 and/or 905, one or more of the example device meters 110 and/or 510, and/or one or more of the example media monitoring facilities 115, 515 and/or 915 could be implemented by one or more circuit(s), programmable processor(s), application specific integrated circuit(s) (ASIC(s)), programmable logic device(s) (PLD(s)) and/or field programmable logic device(s) (FPLD(s)), etc. When any of the apparatus or system claims of this patent are read to cover a purely software and/or firmware implementation, at least one of the example server meters 105, 505 and/or 905, the example device meters 110 and/or 510, the example media monitoring facilities 115, 515 and/or 915, the example transport stream decoder 205, the metering data extractor 210, the example metering data transcoder 215, the example metering metadata encryptor 220, the example transport stream encoder 225, the example metering metadata extractor 305, the example metering metadata reporter 310, the example metering metadata collector 405, the example report generator 410, the example content metadata extractor 605, the example metadata verifier 610, the example content metadata extractor 705, the example content metadata reporter 710, the example content metadata collector 805, the example content metadata validator 810, the example report generator 815, the example media content retriever 1005, the example metering data reporter 1010, the example metering data collector 1105 and/or the example report generator 1110 are hereby expressly defined to include a tangible computer readable medium such as a memory, digital versatile disk (DVD), compact disk (CD), etc., storing such software and/or firmware. Further still, the example server meters 105, 505 and/or 905, the example device meters 110 and/or 510, the example media monitoring facilities 115, 515 and/or 915 of <figref idref="f0002">FIGS. 2-4</figref>, <figref idref="f0004">6-8</figref> and 10-11 may include one or more elements, processes and/or devices in addition to, or instead of, those illustrated in <figref idref="f0002">FIGS. 2-4</figref>, <figref idref="f0004">6-8</figref> and <figref idref="f0006">10-11</figref>, and/or may include more than one of any or all of the illustrated elements, processes and devices.

0058A block diagram of a fourth example system 1200 for monitoring streaming media content is illustrated in <figref idref="f0007">FIG. 12</figref>. The fourth example system 1200 includes many elements in common with the first example system 100 of <figref idref="f0001">FIG. 1</figref>. As such, like elements in <figref idref="f0001">FIGS. 1</figref> and <figref idref="f0007">12</figref> are labeled with the same reference numerals. The detailed descriptions of these like elements are provided above in connection with the discussion of <figref idref="f0001">FIG. 1</figref> and, in the interest of brevity, are not repeated in the discussion of <figref idref="f0007">FIG. 12</figref>.

0059Turning to <figref idref="f0007">FIG. 12</figref>, the system 1200 includes the content provider(s) 125 and an example content delivery network 1215 to provide streaming media content to the content presentation device 120 via the network 150. In the illustrated example, the content provider(s) 125 include an example television source 1205, which may correspond to, for example, any terrestrial, cable, satellite, Internet protocol, etc., broadcast and/or on-demand television source. The content provider(s) 125 of the illustrated example also include an example integrated receiver/decoder (IRD) 1210 to receive and decode a television signal provided by the television source 1205 to thereby obtain, for example, a television transport stream capable of being processed by the content delivery network 1215. Any type of IRD 1210 may be employed in the example system 1200. In the illustrated example, the content delivery network 1215 may include, for example, the compression gear 130, the segmenter and packager 135, the digital rights manager 140 and the content streamer 145 described above.

0060To enable monitoring of media content that is streamed to the content presentation device 120, the system 1200 of the illustrated examples also includes an example metadata inserter 1220 and one or more example transcoders 1225 and/or 1230, in addition to the previously described device meter 110 and media monitoring facility 115. The metadata inserter 1220 may be implemented, for example, as a separate device, or as a plug-in or other application/device associated with or executed by the IRD 210. The transcoders 1225 and/or 1230 may each be implemented, for example, as a separate device, or as a plug-in or other application/device associated with or executed by one or more elements of the content delivery network 1215 (e.g., such as one or more of the compression gear 130, the segmenter and packager 135, the digital rights manager 140 and/or the content streamer 145). In some examples, the metadata inserter 1220 and one or more of the transcoders 1225 and/or 1230 may be integrated into a single device or plug-in, whereas in other examples the metadata inserter 1220 is separate from the transcoders 1225 and 1230.

0061In the illustrated example, the metadata inserter 1220 is coupled to an interface of the IRD 1210 (e.g., such as a serial digital interface (SDI) or Internet protocol (IP) interface) and decodes of the television transport stream provided by the IRD 1210. The metadata inserter 1220 then extracts audio watermark(s) from the audio portion(s) of the television transport stream and decodes the audio watermark(s) to obtain audio watermark payload data, which in the illustrated example provides the metering information. Additionally or alternatively, in some examples the metadata inserter 1220 extracts video (e.g., image) watermark(s) from the video portion(s) of the television transport stream and decodes the video (e.g., image) watermark(s) to obtain video watermark payload data corresponding to the metering information. In some examples the metadata inserter 1220 may additionally or alternatively obtain metering data from an independent metering data source, such as the independent metering data source described in conjunction with <figref idref="f0014">FIGS. 23</figref> and <figref idref="f0015">24</figref>. The metadata inserter 1220 then inserts the watermark payload data corresponding to the metering information into one or more existing portions of the television transport stream capable of carrying metadata. For example, the metadata inserter 1220 can insert the watermark payload data corresponding to the metering information (and/or metering data obtained from an independent source) as vertical blanking interval (VBI) data in accordance with Society of Cable Telecommunications Engineers (SCTE) American National Standard ANSI/SCTE 127, or as one or more Advanced Television Systems Committee (ATSC) private information descriptors of the transport stream, etc. In some examples, operation of the metadata inserter 1220 results in little to no change in the program clock reference and/or audio/video timing of the television transport stream.

0062In the illustrated example, the system 1200 includes one or more of the transcoder 1225 or the transcoder 1230. The transcoders 1225 and 1230 each can take metering metadata inserted by the metadata inserter 1220 into the television transport stream and convert this metadata into a format compatible with streaming by the content delivery network 1215. The transcoders 1225 and 1230 each can then insert this reformatted metadata into certain portion(s) of the streaming content transport stream(s) that are capable of carrying metadata. For example, the transcoders 1225/1230 can decode metering metadata inserted as VBI payload data or as ATSC private information descriptor(s) and convert this metering metadata into ID3 tag metadata for insertion in the transport stream(s) that is (are) to stream the media content in accordance with the HLS or other appropriate streaming protocol. In some examples, the transcoders 1225/1230 encrypt the transcoded metering metadata prior to insertion in the transport stream(s) that is (are) to stream the media content (e.g., to protect privacy). Such encryption can prevent the metering metadata from being observable by applications at the content presentation device 120 other than the device meter 110. Additionally or alternatively, such encryption can be used to prevent the device meter 110 from extracting and/or decoding the metering metadata unless the device meter 110 has been provisioned (e.g., enabled) by the media monitoring facility 115.

0063In the illustrated example, the difference between the transcoder 1225 and the transcoder 1230 concerns the location and integration into the system 1200. For example, the transcoder 1225 performs its transcoding functions on the input to the content delivery network 1215 and, thus, may be implemented as a device separate from the CDN 1215 and/or may be integrated with or separate from the metadata inserter 1220. In contrast, the transcoder 1230 operates on transport stream(s) within the CDN 1215 (e.g., similar to the server meter 105) and, thus, may be implemented as a plug-in and/or application/device associated with or executed by one or more of the elements included in the CDN 1215.

0064A potential advantage of the example system 1200 is that different vendors can provide metadata inserters 1220 and transcoders 1225/1230, with their interfaces being specified by established industry standards (e.g., such as established SCTE or ATSC standards).

0065While an example manner of implementing the system 1200 has been illustrated in <figref idref="f0007">FIG. 12</figref>, one or more of the elements, processes and/or devices illustrated in <figref idref="f0007">FIG. 12</figref> may be combined, divided, re-arranged, omitted, eliminated and/or implemented in any other way. Further, the example television source 1205, the example IRD 1210, the example content delivery network 1215, the example metadata inserter 1220, the example transcoders 1225 and/or 1230 and/or, more generally, the example system 1200 of <figref idref="f0007">FIG. 12</figref> may be implemented by hardware, software, firmware and/or any combination of hardware, software and/or firmware. Thus, for example, any of the example television source 1205, the example IRD 1210, the example content delivery network 1215, the example metadata inserter 1220, the example transcoders 1225 and/or 1230 and/or, more generally, the example system 1200 could be implemented by one or more circuit(s), programmable processor(s), ASIC(s), PLD(s) and/or FPLD(s), etc. When any of the apparatus or system claims of this patent are read to cover a purely software and/or firmware implementation at least one of the example system 1200, the example television source 1205, the example IRD 1210, the example content delivery network 1215, the example metadata inserter 1220 and/or the example transcoders 1225 and/or 1230 are hereby expressly defined to include a tangible computer readable medium such as a memory, DVD, CD, etc., storing such software and/or firmware. Further still, the example system 1200 of <figref idref="f0007">FIG. 12</figref> may include one or more elements, processes and/or devices in addition to, or instead of, those illustrated in <figref idref="f0007">FIG. 12</figref>, and/or may include more than one of any or all of the illustrated elements, processes and devices.

0066Flowcharts representative of example machine readable instructions that may be executed to implement the example systems 100, 500, 900, 1200, 2300 and/or 2800, the example server meters 105, 505 and/or 905, the example device meters 110 and/or 510, the example media monitoring facilities 115, 515, 915 and/or 2815, the example transport stream decoder 205, the metering data extractor 210, the example metering data transcoder 215, the example metering metadata encryptor 220, the example transport stream encoder 225, the example metering metadata extractor 305, the example metering metadata reporter 310, the example metering metadata collector 405, the example report generator 410, the example content metadata extractor 605, the example metadata verifier 610, the example content metadata extractor 705, the example content metadata reporter 710, the example content metadata collector 805, the example content metadata validator 810, the example report generator 815, the example media content retriever 1005, the example metering data reporter 1010, the example metering data collector 1105 the example report generator 1110, the example metadata inserter 1220, the example transcoders 1225 and/1230, the example independent metering data source 2320, the example combiner 2330, the example clock 2410, the example data source(s) 2420, and/or the secondary content presenter 2825 are shown in <figref idref="f0008 f0009 f0010 f0011 f0012 f0013">FIGS. 13-22</figref>, <figref idref="f0016 f0017 f0018 f0019">25, 29</figref>, and/or 30. In these examples, the machine readable instructions represented by each flowchart may comprise one or more programs for execution by a processor, such as the processor 3112 shown in the example processing system 3100 discussed below in connection with <figref idref="f0021">FIG. 31</figref>. Alternatively, the entire program or programs and/or portions thereof implementing one or more of the processes represented by the flowcharts of <figref idref="f0008 f0009 f0010 f0011 f0012 f0013">FIGS. 13-22</figref>, <figref idref="f0016 f0019">25, 29</figref>, and/or 30 could be executed by a device other than the processor 3112 (e.g., such as a controller and/or any other suitable device) and/or embodied in firmware or dedicated hardware (e.g., implemented by an ASIC, a PLD, an FPLD, discrete logic, etc.). Also, one or more of the machine readable instructions represented by the flowchart of <figref idref="f0008 f0009 f0010 f0011 f0012 f0013">FIGS. 13-22</figref>, <figref idref="f0016 f0017 f0018 f0019">25, 29</figref>, and/or 30 may be implemented manually. Further, although the example machine readable instructions are described with reference to the flowcharts illustrated in <figref idref="f0008 f0009 f0010 f0011 f0012 f0013">FIGS. 13-22</figref>, <figref idref="f0016">25</figref>, <figref idref="f0019">29</figref>, and/or 30, many other techniques for implementing the example methods and apparatus described herein may alternatively be used. For example, with reference to the flowcharts illustrated in <figref idref="f0008 f0009 f0010 f0011 f0012 f0013">FIGS. 13-22</figref>, <figref idref="f0016">25</figref>, <figref idref="f0019">29</figref>, and/or 30, the order of execution of the blocks may be changed, and/or some of the blocks described may be changed, eliminated, combined and/or subdivided into multiple blocks.

0067As mentioned above, the example processes of <figref idref="f0008 f0009 f0010 f0011 f0012 f0013">FIGS. 13-22</figref>, <figref idref="f0016">25</figref>, <figref idref="f0019">29</figref>, and/or 30 may be implemented using coded instructions (e.g., computer readable instructions) stored on a tangible computer readable medium such as a hard disk drive, a flash memory, a read-only memory (ROM), a CD, a DVD, a cache, a random-access memory (RAM) and/or any other storage media in which information is stored for any duration (e.g., for extended time periods, permanently, brief instances, for temporarily buffering, and/or for caching of the information). As used herein, the term tangible computer readable medium is expressly defined to include any type of computer readable storage and to exclude propagating signals. Additionally or alternatively, the example processes of <figref idref="f0008 f0009 f0010 f0011 f0012 f0013">FIGS. 13-22</figref>, <figref idref="f0016">25</figref>, <figref idref="f0019">29</figref>, and/or 30 may be implemented using coded instructions (e.g., computer readable instructions) stored on a non-transitory computer readable medium, such as a flash memory, a ROM, a CD, a DVD, a cache, a random-access memory (RAM) and/or any other storage media in which information is stored for any duration (e.g., for extended time periods, permanently, 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 medium and to exclude propagating signals. Also, as used herein, the terms "computer readable" and "machine readable" are considered equivalent unless indicated otherwise. Furthermore, as used herein, when the phrase "at least" is used as the transition term in a preamble of a claim, it is open-ended in the same manner as the term "comprising" is open ended. Thus, a claim using "at least" as the transition term in its preamble may include elements in addition to those expressly recited in the claim.

0068Example machine readable instructions 1300 that may be executed to implement the first example server meter 105 of <figref idref="f0001 f0002">FIGS. 1-2</figref> are illustrated in <figref idref="f0008">FIG. 13</figref>. With reference to the preceding figures, the example machine readable instructions 1300 of <figref idref="f0008">FIG. 13</figref> begin execution at block 1305 at which the server meter 105 receives a transport stream carrying media content to be streamed to the content presentation device 120. At block 1310, the transport stream decoder 205 of the server meter 105 decodes the transport stream to obtain the (e.g., uncompressed) media content being streamed to the content presentation device 120. At block 1315, the metering data extractor 210 of the server meter 105 extracts metering data having a first format (e.g., such as one or more embedded audio/video watermarks) from the decoded (e.g., uncompressed) media content obtained at block 1310. At block 1320, the metering data transcoder 215 of the server meter 105 transcodes the metering data in the first format obtained at block 1315 to form metering metadata having a second format (e.g., a text, binary or other data format) that is decodable by the device meter 110. At block 1325, the transport stream encoder 225 of the server meter 105 re-encodes the transport stream that is to carry the streaming media content to include the metering metadata in a metadata channel to be associated with the transport stream. At block 1330, the server meter 105 sends the re-encoded transport stream (and the metadata channel carrying the transcoded metering metadata) to any other downstream processing elements for streaming to the content presentation device 120. Execution of the example machine readable instructions 1300 then ends.

0069In some examples, block 1315 may be modified and/or replaced with one or more blocks to utilize metering data from an independent metering data source, as described below in conjunction with <figref idref="f0016">FIG. 25</figref>.

0070Example machine readable instructions 1400 that may be executed to implement the first example device meter 110 of <figref idref="f0001">FIGS. 1</figref> and <figref idref="f0002">3</figref> are illustrated in <figref idref="f0009">FIG. 14</figref>. With reference to the preceding figures, the example machine readable instructions 1400 of <figref idref="f0009">FIG. 14</figref> begin execution at block 1405 at which the metering metadata extractor 305 of the device meter 110 detects metering metadata (e.g., metadata derived from metering data included in an audio/video watermark, metadata derived from metering data obtained from an independent metering data source, etc.) included in a metadata channel accompanying a transport stream providing streaming media content to the content presentation device 120. At block 1410, the metering metadata extractor 305 stores the metering metadata for subsequent reporting. At block 1415, the metering metadata reporter 310 of the device meter 110 reports the metering metadata to the media monitoring facility 115. Execution of the example machine readable instructions 1400 then ends.

0071Example machine readable instructions 1500 that may be executed to implement the first example media monitoring facility 115 of <figref idref="f0001">FIGS. 1</figref> and <figref idref="f0002">4</figref> are illustrated in <figref idref="f0009">FIG. 15</figref>. With reference to the preceding figures, the example machine readable instructions 1500 of <figref idref="f0009">FIG. 15</figref> begin execution at block 1505 at which the metering metadata collector 405 of the media monitoring facility 115 collects metering metadata (e.g., metadata derived from metering data included in an audio/video watermark, metadata derived from metering data obtained from an independent metering data source, etc.) and other metering information reported by the device meter 110. At block 1510, the report generator 410 of the media monitoring facility 115 generates one or more reports based on the reported metering information. Execution of the example machine readable instructions 1500 then ends.

0072Example machine readable instructions 1600 that may be executed to implement the second example server meter 505 of <figref idref="f0003 f0004">FIGS. 5-6</figref> are illustrated in <figref idref="f0010">FIG. 16</figref>. With reference to the preceding figures, the example machine readable instructions 1600 of <figref idref="f0010">FIG. 16</figref> begin execution at block 1605 at which the server meter 505 receives a transport stream carrying media content to be streamed to the content presentation device 120. At block 1610, the transport stream decoder 205 of the server meter 505 decodes the transport stream to obtain the (e.g., uncompressed) media content being streamed to the content presentation device 120. At block 1615, the metering data extractor 210 of the server meter 505 extracts metering data (e.g., such as one or more embedded audio/video watermarks) from the decoded (e.g., uncompressed) media content obtained at block 1610. At block 1620, the content metadata extractor 605 extracts content identifying metadata (such as playlist data, electronic programming guide data, etc.) already accompanying the transport stream that is carrying the streaming media content. At block 1625, the metadata verifier 610 of the server meter 505 compares the metering data extracted at block 1615 and the content identifying metadata extracted at block 1620 to verify the content identifying metadata. At block 1630, the metadata verifier 610 reports the verification results to the media monitoring facility 515. Execution of the example machine readable instructions 1600 then ends.

0073In some examples, block 1615 may be modified and/or replaced with one or more blocks to utilize metering data from an independent metering data source, as described below in conjunction with <figref idref="f0016">FIG. 25</figref>.

0074Example machine readable instructions 1700 that may be executed to implement the second example device meter 510 of <figref idref="f0003">FIGS. 5</figref> and <figref idref="f0004">7</figref> are illustrated in <figref idref="f0011">FIG. 17</figref>. With reference to the preceding figures, the example machine readable instructions 1700 of <figref idref="f0011">FIG. 17</figref> begin execution at block 1705 at which the content metadata extractor 705 of the device meter 510 extracts content identifying metadata (such as playlist data, electronic programming guide data, etc.) already accompanying the transport stream providing the streaming media content to the content presentation device 120. At block 1710, the content metadata extractor 705 stores the content identifying metadata for subsequent reporting. At block 1715, the content metadata reporter 710 of the device meter 510 reports the metering metadata to the media monitoring facility 515. Execution of the example machine readable instructions 1700 then ends.

0075Example machine readable instructions 1800 that may be executed to implement the second example media monitoring facility 515 of <figref idref="f0003">FIGS. 5</figref> and <figref idref="f0004">8</figref> are illustrated in <figref idref="f0011">FIG. 18</figref>. With reference to the preceding figures, the example machine readable instructions 1800 of <figref idref="f0011">FIG. 18</figref> begin execution at block 1805 at which the content metadata collector 805 of the media monitoring facility 515 collects content identifying metadata (e.g., metadata accompanying the transport stream, metadata derived from metering data included in an audio/video watermark, metadata derived from metering data obtained from an independent metering data source, etc.) and/or other metering information reported by the device meter 510. At block 1810, the content metadata validator 810 of the media monitoring facility 515 receives verification results concerning the validity of the content identifying information received at block 1805. At block 1815, the content metadata collector 805 validates the collected content identifying metadata using the verification results received at block 1810. Additionally, at block 1815 the report generator 815 of the media monitoring facility 515 generates one or more reports based on the reported metering information. Execution of the example machine readable instructions 1800 then ends.

0076Example machine readable instructions 1900 that may be executed to implement the third example server meter 905 of <figref idref="f0005 f0006">FIGS. 9-10</figref> are illustrated in <figref idref="f0012">FIG. 19</figref>. With reference to the preceding figures, the example machine readable instructions 1900 of <figref idref="f0012">FIG. 19</figref> begin execution at block 1905 at which media content retriever 1005 of the server meter 905 retrieves from the temporary content storage 920 a copy of media content being streamed to the content presentation device 120. At block 1910, the media content retriever 1005 decodes (e.g., unpacks, combines, uncompresses, etc.) the retrieved media content retrieved at block 1905, as appropriate. At block 1915, the metering data extractor 210 of the server meter 905 extracts metering data (e.g., such as one or more embedded audio/video watermarks) from the (e.g., uncompressed) media content obtained at block 1910. At block 1920, the metering data reporter 1010 of the server meter 905 reports the metering data obtained at block 1915 to the media monitoring facility 915. Execution of the example machine readable instructions 1900 then ends.

0077In some examples, block 1915 may be modified and/or replaced with one or more blocks to utilize metering data from an independent metering data source, as described below in conjunction with <figref idref="f0016">FIG. 25</figref>.

0078Example machine readable instructions 2000 that may be executed to implement the third example media monitoring facility 915 of <figref idref="f0005">FIGS. 9</figref> and <figref idref="f0006">11</figref> are illustrated in <figref idref="f0012">FIG. 20</figref>. With reference to the preceding figures, the example machine readable instructions 2000 of <figref idref="f0012">FIG. 20</figref> begin execution at block 2005 at which the metering data collector 1105 of the media monitoring facility 915 collects metering data (e.g., metadata already accompanying the transport stream, metadata derived from metering data included in an audio/video watermark, metadata derived from metering data obtained from an independent metering data source, etc.) reported by the server meter 905. At block 2010, the report generator 1110 of the media monitoring facility 915 generates one or more reports based on the reported metering information. Execution of the example machine readable instructions 2000 then ends

0079Example machine readable instructions 2100 that may be executed to implement the example metadata inserter 1220 of <figref idref="f0007">FIG. 12</figref> are illustrated in <figref idref="f0013">FIG. 21</figref>. With reference to the preceding figures, the example machine readable instructions 2100 of <figref idref="f0013">FIG. 21</figref> begin execution at block 2105 at which the metadata inserter 1220 obtains the decoded media content signal (e.g., the decoded television transport stream) from the IRD 1210. At block 2110, the metadata inserter 1220 extracts watermark(s) (e.g., audio and/or video watermark(s)) from the media content signal). At block 2115, the metadata inserter 1220 decodes the watermark(s) to obtain the watermark payload data and, thus, the metering information provided by the watermark payload data. At block 2120, the metadata inserter 1220 inserts the watermark payload data into existing portions of the media content signal capable of carrying metadata. For example, at block 2120 the metadata inserter 1220 can insert the watermark payload data as VBI data in accordance with the SCTE 127 standard, or as one or more ATSC private information descriptors of the television transport stream, etc. Execution of the example machine readable instructions 2100 then ends.

0080In some examples, block 2115 may be modified and/or replaced with one or more blocks to utilize metering data from an independent metering data source. Such an example is described in conjunction with <figref idref="f0016">FIG. 25</figref>.

0081Example machine readable instructions 2200 that may be executed to implement the example transcoders 1225 and/or 1230 of <figref idref="f0007">FIG. 12</figref> are illustrated in <figref idref="f0013">FIG. 22</figref>. For convenience, and without loss of generality, the machine readable instructions 2200 are described from the perspective of execution by the transcoder 1225. With reference to the preceding figures, the example machine readable instructions 2200 of <figref idref="f0013">FIG. 22</figref> begin execution at block 2205 at which the transcoder 1225 extracts payload data inserted in the metadata carrying portion(s) of the media content signal by the metadata inserter 1220. For example, at block 2205 the transcoder 1225 can extract the payload data as VBI data, as one or more ATSC private information descriptors, etc. At block 2210, the transcoder 1225 transcodes the payload metadata obtained at block 2205, and which corresponds to the metering information, to a format compatible with media streaming. For example, at block 2210 the transcoder 1225 can transcode the payload metadata into ID3 tag metadata. At block 2215, the transcoder 1225 inserts the transcoded metadata into portion(s) of the streaming content transport stream(s) that are capable of carrying metadata. For example, at block 2215 the transcoder 1225 can insert the ID3 tag metadata corresponding to the metering metadata into the appropriate portions of the transport stream(s) that is (are) to stream the media content in accordance with the HLS or other appropriate streaming protocol. Execution of the example machine readable instructions 2200 then ends.

0082<figref idref="f0014">FIG. 23</figref> is a block diagram of an example system 2300 that obtains metering data for streaming media content. The example system 2300 includes a dependent metering data source 2310, an independent metering data source 2320, and a combiner 2330 to generate the output metering data 2340.

0083The dependent metering data source 2310 of the illustrated example receives media content and extracts metering data from the media content. In other words, the metering data collected by the metering data source 2310 is provided by, associated with or otherwise dependent on the media content itself. For example, the dependent metering data source 2310 may extract metering data from an audio and/or video watermark included in the media content, may obtain metering data from a signature generated from the media content, etc.

0084The example independent metering data source 2320 obtains metering data from sources independent of the content of the media content. For example, the independent metering data source 2320 may obtain a timestamp from a clock, identifying information provided by a user input, identifying information stored in a file, etc. In some examples, the metering data obtained by the independent metering data source 2320 may be redundant, similar or identical in content and/or data type to the data extracted from the dependent metering data source 2310. For example, the metering data from the dependent metering data source 2310 and the metering data from the independent metering data source 2320 may include the same source identifier.

0085The combiner 2330 of the illustrated example receives first metering data from the dependent metering data source 2310 and second metering data from the independent metering data source 2320 and combines the first and second metering data to generate the combined metering data 2340. In some examples, the combined metering data 2340 contains redundant or partially redundant information as described in conjunction with <figref idref="f0017">FIG. 26</figref>. In some examples, the metering data extracted by the dependent metering data source 2310 is unavailable and, thus, only the metering data provided by the independent metering data source 2320 is included in the combined metering data 2340 as described in conjunction with <figref idref="f0017">FIG. 27</figref>.

0086A block diagram of an example server meter 2405 that is implemented in accordance with the system 2300 of <figref idref="f0014">FIG. 23</figref> is illustrated in <figref idref="f0015">FIG. 24</figref>. The server meter 2405 of <figref idref="f0015">FIG. 24</figref> includes the dependent metering data source 2310, the independent metering data source 2320, a clock 2410, data source(s) 2420, the combiner 2330, the metering data transcoder 215, the metering metadata encryptor 220, and the transport stream encoder 225, which are described in detail above. The server meter 2405 of the illustrated example can be used to implement any of the server meters 105, 505 and/or 905 described above.

0087The example dependent metering data source 2310 of <figref idref="f0015">FIG. 24</figref> is implemented by the transport stream decoder 205 and the metering data extractor 210 described in conjunction with <figref idref="f0002">FIG. 2</figref>. The metering data extractor 210 of the example dependent metering data source 2310 extracts metering data having a first format from media content obtained from the transport stream decoder 205. Additionally or alternatively, the dependent metering data source 2310 may be implemented by any other components to obtain metering data dependent on the content of the media content in any other manner.

0088The independent metering data source 2320 of the illustrated example obtains metering data from the clock 2410 and the data source(s) 2420. Additionally or alternatively, the independent metering data source 2320 may obtain metering data from any other internal or external sources of metering data that are independent (e.g., separate from) the media content and/or the transport stream(s) providing the media content.

0089The clock 2410 of the illustrated example is an internal system clock of the server meter 2405 that provides one or more timestamps to the independent metering data source 2320, when requested. The clock 2410 may alternatively be any type of internal clock, external clock, etc. For example, the clock 2410 may be a clock at a content provider and/or the clock 2410 may be an internal clock that is synchronized with a clock of a content provider.

0090The data source(s) 2420 of the illustrated example provide metering data to the independent metering data source 2320. The data source(s) 2420 provide metering data that is independent of the media content (e.g., is not extracted from the content of the media content). According to the illustrated example, the data source(s) 2420 include a configuration file storing information identifying the source (e.g., the content provider) of the streaming media content. The configuration file is created during setup of the server meter 2405. Additionally or alternatively, the data source(s) 2420 may include any one or more of locally stored data, externally stored data, data available via a network connection, data input by a user of the server meter 2405, etc.

0091In some examples, the independent metering data source 2320 inserts a tag or other form of identification into the obtained metering data to signify that the metering data was collected by the independent metering data source 2420. For example, the independent metering data source 2320 of <figref idref="f0015">FIG. 24</figref> identifies the collected metering data as "Non-Audio" to signify that the metering data was not extracted from the audio of the streaming media content. Additionally or alternatively, one or more other tags or identification information may be added.

0092The combiner 2330 of the illustrated example combines the metering data from the dependent metering data source 2310 with the metering data from the independent data provider 2320. For example, the combiner 2330 concatenates the metering data extracted by the dependent metering data source 2310 with the metering data obtained by the independent metering data source 2320 to produce one data string. The combiner inserts a delimiter (e.g. a "l") or any other character or indicator between the metering data extracted by the dependent metering data source 2310 and the metering data obtained by the independent metering data source 2320. Additionally or alternatively, the combiner 2330 may combine the metering data in any other manner.

0093To transcode the combined metering data obtained from the dependent metering data source 2310 and the independent metering data source 2320 from a first format to a second format decodable by a device meter, the example server meter 2405 of <figref idref="f0015">FIG. 24</figref> further includes the metering data transcoder 215. Additionally, the server meter 2405 of <figref idref="f0015">FIG. 24</figref> includes the metering metadata encryptor 220 that employs any appropriate encryption to encrypt the transcoded metering metadata determined by the metering data transcoder 215. In the illustrated example of <figref idref="f0015">FIG. 24</figref>, the server meter 2405 includes the transport stream encoder 225 to re-encode the transport stream(s) carrying the streaming media content to include the transcoded metering metadata determined by the metering data transcoder 215 (and encrypted by the metering metadata encryptor 220, as appropriate). Examples of the resulting metering data output by the server meter 2405, as detailed in <figref idref="f0015">FIG. 24</figref>, are disclosed in conjunction with <figref idref="f0017">FIG. 26 and FIG. 27</figref>.

0094While example manners of implementing the system 2300 are described in conjunction with <figref idref="f0014">FIG. 23</figref> and <figref idref="f0015">FIG. 24</figref>, one or more of the elements, processes and/or devices illustrated in <figref idref="f0014">FIG. 23</figref> and <figref idref="f0015">FIG. 24</figref> may be combined, divided, re-arranged, omitted, eliminated and/or implemented in any other way. Further, one or more of the dependent metering data source 2310, the independent metering data source 2320, and the combiner 2330 of <figref idref="f0014">FIG. 23</figref> and the server meter 2405, the transport stream decoder 205, the metering data extractor 210, the independent metering data extractor 2320, the combiner 2330, the clock 2410, the data sources 2420, the metering data transcoder 215, the metering data encryptor 220, and the transport stream encoder 225 of <figref idref="f0015">FIG. 24</figref> may be implemented by hardware, software, firmware and/or any combination of hardware, software and/or firmware. Thus, for example, one or more of the dependent metering data source 2310, the independent metering data source 2320, and the combiner 2330 of <figref idref="f0014">FIG. 23</figref> and the server meter 2405, the transport stream decoder 205, the metering data extractor 210, the independent metering data extractor 2320, the combiner 2330, the clock 2410, the data sources 2420, the metering data transcoder 215, the metering data encryptor 220, and the transport stream encoder 225 of <figref idref="f0015">FIG. 24</figref> could be implemented by one or more circuit(s), programmable processor(s), application specific integrated circuit(s) (ASIC(s)), programmable logic device(s) (PLD(s)) and/or field programmable logic device(s) (FPLD(s)), etc. When any of the apparatus or system claims of this patent are read to cover a purely software and/or firmware implementation, at least one of the dependent metering data source 2310, the independent metering data source 2320, and the combiner 2330 of <figref idref="f0014">FIG. 23</figref> and the server meter 2405, the transport stream decoder 205, the metering data extractor 210, the independent metering data extractor 2320, the combiner 2330, the clock 2410, the data sources 2420, the metering data transcoder 215, the metering data encryptor 220, and the transport stream encoder 225 of <figref idref="f0015">FIG. 24</figref> are hereby expressly defined to include a tangible computer readable medium such as a memory, digital versatile disk (DVD), compact disk (CD), etc., storing such software and/or firmware. Further still, the system 2300 of <figref idref="f0014">FIG. 23</figref> and the server meter 105 of <figref idref="f0015">FIG. 24</figref> may include one or more elements, processes and/or devices in addition to, or instead of, those illustrated in <figref idref="f0014">FIG. 23</figref> and <figref idref="f0015">FIG. 24</figref>, and/or may include more than one of any or all of the illustrated elements, processes and devices.

0095Example machine readable instructions 2500 that may be executed to implement the example server meter 2405 of <figref idref="f0015">FIG. 24</figref> are illustrated in <figref idref="f0016">FIG. 25</figref>. With reference to <figref idref="f0014">FIGS. 23</figref> and <figref idref="f0015">24</figref>, the example machine readable instructions 2500 of <figref idref="f0016">FIG. 25</figref> begin execution at block 2505 at which the server meter 2405 receives a transport stream carrying media content to be streamed to the content presentation device 120 (block 2505). The transport stream decoder 205 of the dependent metering data source 2310 decodes the transport stream to obtain the media content being streamed to the content presentation device 120 (block 2510). The metering data extractor 210 of the dependent metering data source 2310 extracts metering data having a first format (e.g., such as one or more embedded audio/video watermarks) from the decoded (e.g., uncompressed) media content obtained at block 2510 (block 2515). The independent metering data source 2320 collects metering data, which may have the first format or a second format, from sources independent of the content of the media content (block 2520). The combiner 2330 then combines the metering data collected by the metering data extractor 210 with the metering data collected by the independent metering data source 2320 (block 2525).

0096The metering data transcoder 215 of the server meter 2405 transcodes the metering data in the first and/or second format(s) obtained at blocks 2515 and 2520 and combined at block 2525 to form transcoded metering metadata having a third format (e.g., a text, binary or other data format) that is decodable by the device meter 110 (block 2530). The transport stream encoder 225 of the server meter 105 re-encodes the transport stream that is to carry the streaming media content to include the transcoded metering metadata in a metadata channel to be associated with the transport stream (block 2535). The server meter 2405 sends the re-encoded transport stream (and the metadata channel carrying the transcoded metering metadata) to any other downstream processing elements for streaming to the content presentation device 120 (block 2540). Execution of the example machine readable instructions 2500 then ends.

0097<figref idref="f0017">FIG. 26</figref> illustrates example metadata 2600, derived from the combined metering data 2340, after being extracted, obtained, combined, and transcoded by the server meter 2405 as detailed in <figref idref="f0015">FIG. 24</figref>. Metadata 2600 includes block 2610, which is the portion of the metadata 2600 that was extracted from the media content by metering data extractor 210. Timestamp 2612 is timestamp data extracted from the media content by the metering data extractor 210. Source identification 2614 is source identification data extracted by the metering data extractor 210 from the media content. Metadata 2600 also includes block 2620, which is the portion of the metadata 2600 collected by the independent metering data source 2320. Timestamp 2622 is timestamp data obtained by the independent metering data source 2320 from the clock 2410. Source identification 2624 is source identification data obtained by the independent metering data source 2320 from the data source(s) 2420. Tag 2626 is a tag on metadata 2620 that identifies metadata 2620 as obtained by the independent metering data source 2320. The metadata 2340, exemplified in <figref idref="f0017">FIG. 26</figref>, is an example in which the metadata 2610 was readable and the metadata 2620 serves as redundant, or similar, metadata.

0098<figref idref="f0017">FIG. 27</figref> illustrates example metadata 2700, derived from metering data 2340, after being extracted, obtained, combined, and transcoded by the server meter 105 as detailed in <figref idref="f0016">FIG. 25</figref>. Metadata 2700 illustrates an example where a portion of metadata 2700, block 2710, was unreadable or otherwise unavailable and a portion of the metadata 2700, block 2720, associated with an independent metering data source serves as a backup source of metadata that may be used to replace the unreadable or otherwise unavailable metadata. Block 2710 is the portion of the metadata 2700 that was extracted from the metering data extractor 210. Block 2720 is the portion of metadata 2700 obtained by the independent metering data source 2320. Timestamp 2722 is the timestamp data obtained by the independent metering data source 2320 from the clock 2410. Source identification 2724 is the source identification data obtained by the independent metering data source 2320 from the data source(s) 2420. Tag 2726 is a tag on metadata 2720 that identifies metadata 2720 as obtained by the independent metering data source 2320.

0099A block diagram of a fifth example system 2800 for monitoring streaming media content is illustrated in <figref idref="f0018">FIG. 28</figref>. The fifth example system 2800 includes many elements in common with the first example system 100 of <figref idref="f0001">FIG. 1</figref>. As such, like elements in <figref idref="f0001">FIGS. 1</figref> and <figref idref="f0018">28</figref> are labeled with the same reference numerals. The detailed descriptions of these like elements are provided above in connection with the discussion of <figref idref="f0001">FIG. 1</figref> and, in the interest of brevity, are not repeated in the discussion of <figref idref="f0018">FIG. 28</figref>.

0100Turning to <figref idref="f0018">FIG. 28</figref>, the illustrated example system 2800 includes the compression gear 130, the segmenter and packager 135, the digital rights manager 140 and the content streamer 145 to provide streaming media content to a second example content presentation device 2820 via the network 150. To provide media content to the system 2800, the illustrated example of <figref idref="f0018">FIG. 28</figref> includes the content provider(s) 125. To monitor media content that is streamed to the content presentation device 2820 and optionally provide secondary content based on the results of the media monitoring, the system 2800 of the illustrated examples also includes the server meter 105, the device meter 110, a fourth example media monitoring facility 2815, and an example secondary content presenter 2825.

0101The media monitoring facility 2815 includes an interface to receive reported metering information (e.g., metering metadata) received from the device meter 110 via the network 150. In the illustrated example, the media monitoring facility 2815 includes an HTTP interface to receive HTTP requests that include metering information. Additionally or alternatively, any other method(s) to receive metering information may be used. In the illustrated example, the media monitoring facility 2815 receives metering information from the device meter 110, selects secondary content using the received metering information, and sends the selected secondary content to the secondary content presenter 2825. In some examples, the media monitoring facility may select the secondary content from an internal content database. In some examples, the media monitoring facility 2815 may select the secondary content from one/or more external database(s) and/or third party database(s). In such examples, the media monitoring facility 2815 may access the external and/or third party database(s) via a network (e.g. the Internet, a local area network (LAN), a wide area network (WAN), etc.). Other additional or alternative examples of providing secondary media content associated with primary media content that may be employed by the media monitoring facility 2815 are described in, for example, <patcit id="pcit0008" dnum="US20100280641"><text>U.S. Patent Application Publication No. 2010/0280641 ("METHODS, APPARATUS AND ARTICLES OF MANUFACTURE TO PROVIDE SECONDARY CONTENT IN ASSOCIATION WITH PRIMARY BROADCAST MEDIA CONTENT" to Harkness et al.), which was filed on April 30, 2010</text></patcit>.

0102The content presentation device 2820 of the illustrated example is a computing device that is capable of presenting streaming media content provided by the content streamer 145 via the network 150. The content presentation device 2820 may be, for example, a desktop computer, a laptop computer, a mobile computing device, a television, a smart phone, a mobile phone, an Apple^® iPad^®, an Apple^® iPhone^®, an Apple^® iPod^®, an AndroidTM powered computing device, Palm^® webOS^® computing device, etc. In some examples, the content presentation device 2820 includes one or more executable media players to present the streaming media content provided by the content streamer 145. For examples, the media player(s) available to the content presentation device 120 may be implemented in Adobe^® Flash^® (e.g., provided in a SWF file), may be implemented in hypertext markup language (HTML) version 5 (HTML5), may be implemented in Google^® Chromium^®, may be implemented according to the Open Source Media Framework (OSMF), may be implemented according to a device or operating system provider's media player application programming interface (API), may be implemented on a device or operating system provider's media player framework (e.g., the Apple^® iOS^® MPMoviePlayer software), etc., or any combination thereof. While a single content presentation device 120 is illustrated, any number and/or type(s) of content presentation devices may be included in the system 100.

0103In the illustrated example, the content presentation device 2820 implements the secondary content presenter 2825. The secondary content presenter 2820 may be as an executable media presenter stored on a computing device that is capable of presenting secondary content provided by the media monitoring facility 2815 via the network 150. In some examples, the secondary content presenter 2825 may be implemented as a plug-in that is connected to a plug-in interface of a media player executed by the content presentation device 2820. In some examples, the secondary content presenter 2825 may be implemented as instructions provided that are incorporated in a media player executed by the content presentation device 2820. In some examples, the secondary content presenter 2825 may be implemented as an executable application that is downloaded to the content presentation device 2820 (e.g., downloaded as an App from the Apple^® App Store). For example, the secondary content presenter 2825 may be implemented in Adobe^® Flash^® (e.g., provided in a SWF file), may be implemented in hypertext markup language (HTML) version 5 (HTML5), may be implemented in Google^® Chromium^®, may be implemented according to the Open Source Media Framework (OSMF), may be implemented according to a device or operating system provider's media player application programming interface (API), may be implemented on a device or operating system provider's media player framework (e.g., the Apple^® iOS^® MPMoviePlayer software), etc., or any combination thereof. While a single secondary content presenter 2825 is illustrated, any number and/or type(s) of secondary content presenters associated with the content presentation device 2820 may be included in the system 2800.

0104Example machine readable instructions 2900 that may be executed to implement the second example media monitoring facility 2815 of <figref idref="f0018">FIG. 28</figref> are illustrated in <figref idref="f0019">FIG. 29</figref>. With reference to the preceding figures, the example machine readable instructions 2900 of <figref idref="f0019">FIG. 29</figref> begin execution at block 2905 at which the media monitoring facility 2815 collects metering metadata (e.g., metadata derived from metering data included in an audio/video watermark, metadata derived from metering data obtained from an independent metering data source, etc.) and/or other metering information reported by the device meter 110 (block 2905). Then, the media monitoring facility 2915 selects secondary content using the metering metadata received at block 2905 (block 2910). Then, the media monitoring facility 2815 sends the secondary content selected at block 2910 to the secondary content presenter 2825 (block 2915). Execution of the example machine readable instructions 2900 then ends.

0105Example machine readable instructions 3000 that may be executed to implement the device meter 110 and secondary content presenter within the content presentation device 2820 of <figref idref="f0018">FIG. 28</figref> are illustrated in <figref idref="f0020">FIG. 30</figref>. With reference to the preceding figures, the example machine readable instructions 3000 of <figref idref="f0020">FIG. 30</figref> begin execution at block 3005 at which the device meter 110 detects and reports metering metadata to the media monitoring facility 2815 (block 3005). Then, the secondary content presenter 2825 receives secondary content associated with the metering metadata reported to the media monitoring facility 2815 at block 3005 (block 3010). Then, the secondary content presenter 2825 presents the secondary content received at block 3010 (block 3015). Execution of the example machine readable instructions 3000 then ends.

0106<figref idref="f0021">FIG. 31</figref> is a block diagram of an example processing system 3100 capable of implementing the apparatus and methods disclosed herein. The processing system 3100 can be, for example, a tablet computer, a notebook/laptop computer, a personal computer, a personal digital assistant (PDA), a server, an Internet appliance, a DVD player, a CD player, a digital video recorder, a personal video recorder, a set top box, or any other type of computing device.

0107The system 3100 of the instant example includes a processor 3112 such as a general purpose programmable processor. The processor 3112 includes a local memory 3114, and executes coded instructions 3116 present in the local memory 3114 and/or in another memory device. The processor 3112 may execute, among other things, the machine readable instructions represented in <figref idref="f0008 f0009 f0010 f0011 f0012 f0013">FIGS. 13-22</figref>, <figref idref="f0016">25</figref>, <figref idref="f0019">29</figref> and/or 30. The processor 3112 may be any type of processing unit, such as one or more Intel^® microprocessors from the Pentium^® family, the Itanium^® family and/or the XScale^® family, one or more processing cores, such as one or more of the ARM^® families of processing cores, one or more microcontrollers, such as one or more of the PIC^® families of microcontrollers, etc. Of course, other processors from other families are also appropriate.

0108The processor 3112 is in communication with a main memory including a volatile memory 3118 and a non-volatile memory 3120 via a bus 3122. The volatile memory 3118 may be implemented by Static Random Access Memory (SRAM), 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. The non-volatile memory 3120 may be implemented by flash memory and/or any other desired type of memory device. Access to the main memory 3118, 3120 is typically controlled by a memory controller (not shown).

0109The processing system 3100 also includes an interface circuit 3124. The interface circuit 3124 may be implemented by any type of interface standard, such as an Ethernet interface, a universal serial bus (USB), and/or a third generation input/output (3GIO) interface.

0110One or more input devices 3126 are connected to the interface circuit 3124. The input device(s) 3126 permit a user to enter data and commands into the processor 3112. The input device(s) can be implemented by, for example, a keyboard, a mouse, a touchscreen, a track-pad, a trackball, an isopoint and/or a voice recognition system.

0111One or more output devices 3128 are also connected to the interface circuit 3124. The output devices 3128 can be implemented, for example, by display devices (e.g., a liquid crystal display, a cathode ray tube display (CRT)), by a printer and/or by speakers. The interface circuit 3124, thus, typically includes a graphics driver card.

0112The interface circuit 3124 also includes a communication device such as a modem or network interface card to facilitate exchange of data with external computers via a network (e.g., an Ethernet connection, a digital subscriber line (DSL), a telephone line, coaxial cable, a cellular telephone system, etc.).

0113The processing system 3100 also includes one or more mass storage devices 3130 for storing machine readable instructions and data. Examples of such mass storage devices 3130 include floppy disk drives, hard drive disks, compact disk drives and digital versatile disk (DVD) drives. In some examples, the mass storage device 3130 may implement the temporary content storage 920. Additionally or alternatively, in some examples the volatile memory 3118 may implement the temporary content storage 920.

0114The coded instructions 3132 of <figref idref="f0008 f0009 f0010 f0011 f0012 f0013">FIGS. 13-22</figref>, <figref idref="f0016">25</figref>, <figref idref="f0019">29</figref> and <figref idref="f0020">30</figref> may be stored in the mass storage device 3130, in the volatile memory 3118, in the non-volatile memory 3120, in the local memory 3114 and/or on a removable storage medium, such as a CD or DVD 3132.

0115As an alternative to implementing the methods and/or apparatus described herein in a system such as the processing system of <figref idref="f0021">FIG. 31</figref>, the methods and or apparatus described herein may be embedded in a structure such as a processor and/or an ASIC (application specific integrated circuit).