Monitoring streaming media content
35 claims: 35 independent, 0 dependent
- 1ストリーミングメディ アを モニタリングするための方法であって、 第1の形式を有するメータリングデータを、トランスポートストリームによって メディア 提示デバイスに提供 される メディアからプロセッサを使用して抽出するステップであって、前記抽出されたメータリングデータが、前記メディ ア及び 前記メディ アの ソースの少なくとも一方を識別し、前記抽出されたメータリングデータが、前記 メディア 提示デバイスに関連するメータによって復号可能ではない、ステップと、 前記抽出されたメータリングデータを、前記プロセッサを使用してトランスコードして、前記 メディア 提示デバイスに関連する前記メータによって復号可能な第2の形式を有するトランスコードされたメータリングデータを形成するステップと、 前 記トランスコードされたメータリングデータを前記 メディア 提示デバイスに 提供 するため に、前記トランスコードされたメータリングデータを、前記メディア提示デバイスに送信されるファイルを含む外部 メタデータチャネル内に、前記プロセッサを使用して符号化するステップであって、 前記ファイルは、前記メディア提示デバイスへの前記トランスポートストリームの通信とは別に当該通信に先だって前記メディア提示デバイスに送信されるファイルであり、 前記 外部 メタデータチャネルが前記トランスポートストリームに関連する、ステップとを含む方法。
- 2ストリーミングメディアをモニタリングするための方法であって、 第1の形式を有するメータリングデータを、トランスポートストリームによってメディア提示デバイスに提供されるメディアからプロセッサを使用して抽出するステップであって、前記抽出されたメータリングデータが、前記メディア及び前記メディアのソースの少なくとも一方を識別し、前記抽出されたメータリングデータが、前記メディア提示デバイスに関連するメータによって復号可能ではない、ステップと、 前記抽出されたメータリングデータを、前記プロセッサを使用してトランスコードして、前記メディア提示デバイスに関連する前記メータによって復号可能な第2の形式を有するトランスコードされたメータリングデータを形成するステップと、 前記トランスコードされたメータリングデータを前記メディア提示デバイスに提供するために、前記トランスコードされたメータリングデータを、前記メディア提示デバイスに送信されるファイルを含む外部メタデータチャネル内に、前記プロセッサを使用して符号化するステップであって、前記ファイルが前記トランスポートストリームに関連する、ステップと、を含み、 前記ファイルが、M3Uファイルに対応し、前記抽出されたメータリングデータをトランスコードして、前記第2の形式を有する前記トランスコードされたメータリングデータを形成するステップが、前記抽出されたメータリングデータをトランスコードして、前記メータリングデータに対応するテキストデータを形成するサブステップを含み、前記トランスコードされたメータリングデータを前記 外部 メタデータチャネル 内 に符号化するステップが、前記テキストデータを前記外部メタデータチャネルを実施する前記M3Uファイルに挿入するサブステップを含む 、方 法。
- 3前記第1の形式を有する前記メータリングデータを前記メディアから抽出するステップが、透かしデータを前記メディアから抽出するサブステップを含み、前記抽出されたメータリングデータをトランスコードして、前記第2の形式を有する前記トランスコードされたメータリングデータを形成するステップが、前記抽出された透かしデータをトランスコードして、M3Uファイル内に含ませるためのテキストデータを形成するサブステップを含む、請求項 1に 記載の方法。
- 42次 メディア を前記 メディア 提示デバイスに送信するステップであって、前記2次 メディア が、前記 メディア 提示デバイスにおいてモニタリングされる前記トランスコードされたメータリングデータに基づいて選択される、ステップをさらに含む、請求項1 ~3のいずれか一項 に記載の方法。
- 5機械可読命令を記憶する有形な機械可読記憶媒体であって、前記機械可読命令は、実行されると、少なくとも、 第1の形式を有するメータリングデータを、トランスポートストリームによって メディア 提示デバイスに提供 される メディ アか ら抽出することであって、前記抽出されたメータリングデータが、前記メディ ア及び 前記メディ アの ソースの少なくとも一方を識別し、前記抽出されたメータリングデータが、前記 メディア 提示デバイスに関連するメータによって復号可能ではない、抽出することと、 前記抽出されたメータリングデータをトランスコードして、前記 メディア 提示デバイスに関連する前記メータによって復号可能な第2の形式を有するトランスコードされたメータリングデータを形成することと、 前 記トランスコードされたメータリングデータを前記 メディア 提示デバイスに 提供 するため に、前記トランスコードされたメータリングデータを、前記メディア提示デバイスに送信されるファイルを含む外部 メタデータチャネルに符号化することであって、 前記ファイルは、前記メディア提示デバイスへの前記トランスポートストリームの通信とは別に当該通信に先だって前記メディア提示デバイスに送信されるファイルであり、 前記 外部 メタデータチャネルが前記トランスポートストリームに関連する、符号化することとを機械に行わせる、記憶媒体。
- 6機械可読命令を記憶する有形な機械可読記憶媒体であって、前記機械可読命令は、実行されると、少なくとも、 第1の形式を有するメータリングデータを、トランスポートストリームによってメディア提示デバイスに提供されるメディアから抽出することであって、前記抽出されたメータリングデータが、前記メディア及び前記メディアのソースの少なくとも一方を識別し、前記抽出されたメータリングデータが、前記メディア提示デバイスに関連するメータによって復号可能ではない、抽出することと、 前記抽出されたメータリングデータをトランスコードして、前記メディア提示デバイスに関連する前記メータによって復号可能な第2の形式を有するトランスコードされたメータリングデータを形成することと、 前記トランスコードされたメータリングデータを前記メディア提示デバイスに提供するために、前記トランスコードされたメータリングデータを、前記メディア提示デバイスに送信されるファイルを含む外部メタデータチャネル内に符号化することであって、前記ファイルが前記トランスポートストリームに関連する、符号化することと を機械に行わせ、 前記ファイルが、M3Uファイルに対応し、前記抽出されたメータリングデータをトランスコードして、前記第2の形式を有する前記トランスコードされたメータリングデータを形成するために、前記機械可読命令は、実行されると、前記抽出されたメータリングデータをトランスコードして、前記メータリングデータに対応するテキストデータを形成することを前記機械に行わせ、前記トランスコードされたメータリングデータを前記 外部 メタデータチャネル 内 に符号化するために、前記機械可読命令は、実行されると 、前 記外部メタデータチャネルを実施する前記M3Uファイルに 前記テキストデータを 挿入することを前記機械に行わせる 、記 憶媒体。
- 7前記第1の形式を有する前記メータリングデータを前記メディアから抽出するために、前記機械可読命令は、実行されると、透かしデータを前記メディアから抽出することを前記機械に行わせ、前記抽出されたメータリングデータをトランスコードして、前記第2の形式を有する前記トランスコードされたメータリングデータを形成するために、前記機械可読命令は、実行されると、前記抽出された透かしデータをトランスコードして、M3Uファイル内に含ませるためのテキストデータを形成することを前記機械に行わせる、請求項 5に 記載の記憶媒体。
- 8前記機械可読命令は、実行されると、2次 メディア を前記 メディア 提示デバイスに送信することを前記機械にさらに行わせ、前記2次 メディア が、前記 メディア 提示デバイスにおいてモニタリングされる前記トランスコードされたメータリングデータに基づいて選択される、請求項 5~7のいずれか一項 に記載の記憶媒体。
- 9ストリーミング メディ アを モニタリングするためのメータであって、 第1の形式を有するメータリングデータを、トランスポートストリームによって メディア 提示デバイスに提供 される メディ アか ら抽出するための抽出器であって、前記抽出されたメータリングデータが、前記メディ ア及び 前記メディ アの ソースの少なくとも一方を識別し、前記抽出されたメータリングデータが、前記 メディア 提示デバイスに関連するメータによって復号可能ではない、抽出器と、 前記抽出されたメータリングデータを、トランスコードして、前記 メディア 提示デバイスに関連する前記メータによって復号可能な第2の形式を有するトランスコードされたメータリングデータを形成するためのトランスコーダと、 前 記トランスコードされたメータリングデータを前記 メディア 提示デバイスに 提供 するため に、前記トランスコードされたメータリングデータを、前記メディア提示デバイスに送信されるファイルを含む外部 メタデータチャネル 内 に符号化するための符号化器であって、 前記ファイルは、前記メディア提示デバイスへの前記トランスポートストリームの通信とは別に当該通信に先だって前記メディア提示デバイスに送信されるファイルであり、 前記 外部 メタデータチャネルが前記トランスポートストリームに関連する、符号化器とを備えるメータ。
- 10ストリーミングメディアをモニタリングするためのメータであって、 第1の形式を有するメータリングデータを、トランスポートストリームによってメディア提示デバイスに提供されるメディアから抽出するための抽出器であって、前記抽出されたメータリングデータが、前記メディア及び前記メディアのソースの少なくとも一方を識別し、前記抽出されたメータリングデータが、前記メディア提示デバイスに関連するメータによって復号可能ではない、抽出器と、 前記抽出されたメータリングデータを、トランスコードして、前記メディア提示デバイスに関連する前記メータによって復号可能な第2の形式を有するトランスコードされたメータリングデータを形成するためのトランスコーダと、 前記トランスコードされたメータリングデータを前記メディア提示デバイスに提供するために、前記トランスコードされたメータリングデータを、前記メディア提示デバイスに送信されるファイルを含む外部メタデータチャネル内に符号化するための符号化器であって、前記ファイルが前記トランスポートストリームに関連する、符号化器と、を備え、 前記ファイルが、M3Uファイルに対応し、前記トランスコーダが、前記抽出されたメータリングデータをトランスコードして、前記メータリングデータに対応するテキストデータを形成することによって、前記抽出されたメータリングデータをトランスコードして、前記第2の形式を有する前記トランスコードされたメータリングデータを形成し、前記符号化器が 、前 記外部メタデータチャネルを実施する前記M3Uファイルに 前記テキストデータを 挿入することによって、前記トランスコードされたメータリングデータを前記 外部 メタデータチャネルに符号化す るメ ータ。
- 11前記抽出器が、透かしデータを前記メディアから抽出することによって、前記第1の形式を有する前記メータリングデータを前記メディアから抽出し、前記トランスコーダが、前記抽出された透かしデータをトランスコードして、M3Uファイル内に含ませるためのテキストデータを形成することによって、前記抽出されたメータリングデータをトランスコードして、前記第2の形式を有する前記トランスコードされたメータリングデータを形成する、請求項 9に 記載のメータ。
- 12ストリーミングメディ アを モニタリングするための方法であって、 第1のメータリングデータを、トランスポートストリームによって メディア 提示デバイスに提供 される メディ ア からプロセッサを使用して抽出するステップであって、前記第1のメータリングデータが、前記メディ ア及び 前記メディ アの ソースの少なくとも一方を識別する、ステップと、 前記第1のメータリングデータを、前記メディ アと は独立に獲得された第2のメータリングデータと、前記プロセッサを使用して組み合わせるステップであって、前記組み合わされたメータリングデータが、前記 メディア 提示デバイスに関連するメータによって復号可能ではない、ステップと、 前記組み合わされたメータリングデータを、前記プロセッサを使用してトランスコードして、前記 メディア 提示デバイスに関連する前記メータによって復号可能な形式を有するトランスコードされたメータリングデータを形成するステップと 、 前記トランスコードされたメータリングデータを前記メディア提示デバイスに提供するために、前記トランスコードされたメータリングデータを、前記メディア提示デバイスに送信されるファイルを含む外部メタデータチャネル内に、前記プロセッサを使用して符号化するステップであって、前記ファイルは、前記メディア提示デバイスへの前記トランスポートストリームの通信とは別に当該通信に先だって前記メディア提示デバイスに送信されるファイルである、ステップと を含む方法。
- 13前記メディ アと は独立に獲得された前記第2のメータリングデータが、前記メディ アか ら抽出された前記第1のメータリングデータと実質的に類似する、請求項 12 に記載の方法。
- 14前記組み合わされたメータリングデータが、前記メディ アと は独立に獲得された前記第2のメータリングデータに対応する、前記組み合わされたメータリングデータの部分を識別するための、区切り文字を含む、請求項 12又は13 に記載の方法。
- 15前 記トランスポートストリーム及び前記 外部 メタデータチャネルを、前記 メディア 提示デバイスにストリーミングするステッ プを さらに含む、請求項 12~14のいずれか一項 に記載の方法。
- 162次 メディア を前記 メディア 提示デバイスにストリーミングするステップであって、前記2次 メディア が、前記 メディア 提示デバイスにおいてモニタリングされている前記組み合わされたメータリングデータに基づいて選択される、ステップをさらに含む、請求項 12~15のいずれか一項 に記載の方法。
- 17前記メディ アを 搬送する前記トランスポートストリームに関連する メディア 識別メタデータを復号するステップであって、前記 メディア 識別メタデータが、前記メディ アの プロバイダによって提供される、ステップと、 前記メディ アか ら抽出された前記第1のメータリングデータを使用して、前記 メディア 識別メタデータを検証するステップとをさらに含む、請求項 12~16のいずれか一項 に記載の方法。
- 18前記メディ アか ら抽出された前記第1のメータリングデータを使用して、前記 メディア 識別メタデータを検証した結果を、メディアモニタリング機関に報告して、前記 メディア 提示デバイスに関連する前記メータによって報告されたメータリング結果の妥当性確認を可能にするステップをさらに含む、請求項 17 に記載の方法。
- 19前記メディ アか ら抽出された前記第1のメータリングデータが、前記メディ ア内 に埋め込まれた透かしデータを含み、前記トランスコードされたメータリングデータが、テキスト形式で表され る、 請求項 12~18のいずれか一項 に記載の方法。
- 20機械可読命令を記憶する有形な機械可読記憶媒体であって、前記機械可読命令は、実行されると、少なくとも、 第1のメータリングデータを、トランスポートストリームによって メディア 提示デバイスに提供 される メディ アか ら抽出することであって、前記第1のメータリングデータが、前記メディ ア及び 前記メディ アの ソースの少なくとも一方を識別する、抽出することと、 前記第1のメータリングデータを、前記メディ アと は独立に獲得された第2のメータリングデータと組み合わせることであって、前記組み合わされたメータリングデータが、前記 メディア 提示デバイスに関連するメータによって復号可能ではない、組み合わせることと、 前記組み合わされたメータリングデータをトランスコードして、前記 メディア 提示デバイスに関連する前記メータによって復号可能な形式を有するトランスコードされたメータリングデータを形成することと 、 前記トランスコードされたメータリングデータを前記メディア提示デバイスに提供するために、前記トランスコードされたメータリングデータを、前記メディア提示デバイスに送信されるファイルを含む外部メタデータチャネル内に符号化することであって、前記ファイルは、前記メディア提示デバイスへの前記トランスポートストリームの通信とは別に当該通信に先だって前記メディア提示デバイスに送信されるファイルである、符号化することと を機械に行わせる、記憶媒体。
- 21前記メディ アと は独立に獲得された前記第2のメータリングデータが、前記メディ アか ら抽出された前記第1のメータリングデータと実質的に類似する、請求項 20 に記載の記憶媒体。
- 22前記組み合わされたメータリングデータが、前記メディ アと は独立に獲得された前記第2のメータリングデータに対応する、前記組み合わされたメータリングデータの部分を識別するための、区切り文字を含む、請求項 20又は21 に記載の記憶媒体。
- 23前記機械可読命令は、実行されると、 前 記トランスポートストリーム及び前記 外部 メタデータチャネルを、前記 メディア 提示デバイスにストリーミングするこ とを 前記機械にさらに行わせる、請求項 20~22のいずれか一項 に記載の記憶媒体。
- 24前記機械可読命令は、実行されると、2次 メディア を前記 メディア 提示デバイスにストリーミングすることであって、前記2次 メディア が、前記 メディア 提示デバイスにおいてモニタリングされている前記組み合わされたメータリングデータに基づいて選択される、ストリーミングすることを前記機械にさらに行わせる、請求項 20~23のいずれか一項 に記載の記憶媒体。
- 25前記機械可読命令は、実行されると、 前記メディ アを 搬送する前記トランスポートストリームに関連する メディア 識別メタデータを復号することであって、前記 メディア 識別メタデータが、前記メディ アの プロバイダによって提供される、復号することと、 前記メディ アか ら抽出された前記第1のメータリングデータを使用して、前記 メディア 識別メタデータを検証することとを前記機械にさらに行わせる、請求項 20~24のいずれか一項 に記載の記憶媒体。
- 26前記機械可読命令は、実行されると、前記メディ アか ら抽出された前記第1のメータリングデータを使用して、前記 メディア 識別メタデータを検証した結果を、メディアモニタリング機関に報告して、前記 メディア 提示デバイスに関連する前記メータによって報告されたメータリング結果の妥当性確認を可能にすることを前記機械に行わせる、請求項 25 に記載の記憶媒体。
- 27前記メディ アか ら抽出された前記第1のメータリングデータが、前記メディ ア内 に埋め込まれた透かしデータを含み、前記トランスコードされたメータリングデータが、テキスト形式で表され る、 請求項 20~26のいずれか一項 に記載の記憶媒体。
- 28ストリーミング メディ アを モニタリングするためのメータであって、 第1のメータリングデータを、トランスポートストリームによって メディア 提示デバイスに提供 される メディ アか ら抽出するための抽出器であって、前記第1のメータリングデータが、前記メディ ア及び 前記メディ アの ソースの少なくとも一方を識別する、抽出器と、 前記第1のメータリングデータを、前記メディ アと は独立に獲得された第2のメータリングデータと組み合わせるためのコンバイナであって、前記組み合わされたメータリングデータが、前記 メディア 提示デバイスに関連するメータによって復号可能ではない、コンバイナと、 前記組み合わされたメータリングデータをトランスコードして、前記 メディア 提示デバイスに関連する前記メータによって復号可能な形式を有するトランスコードされたメータリングデータを形成するためのトランスコーダと 、 前記トランスコードされたメータリングデータを前記メディア提示デバイスに提供するために、前記トランスコードされたメータリングデータを、前記メディア提示デバイスに送信されるファイルを含む外部メタデータチャネル内に符号化するための符号化器であって、前記ファイルは、前記メディア提示デバイスへの前記トランスポートストリームの通信とは別に当該通信に先だって前記メディア提示デバイスに送信されるファイルである、符号化器と を備えるメータ。
- 29前記メディ アと は独立に獲得された前記第2のメータリングデータが、前記メディ アか ら抽出された前記第1のメータリングデータと実質的に類似する、請求項 28 に記載のメータ。
- 30前記組み合わされたメータリングデータが、前記メディ アと は独立に獲得された前記第2のメータリングデータに対応する、前記組み合わされたメータリングデータの部分を識別するための、区切り文字を含む、請求項 28又は29 に記載のメータ。
- 31前 記トランスポートストリーム及び前記 外部 メタデータチャネルを、前記 メディア 提示デバイスにストリーミングするためのストリー マを さらに備える、請求項 28~30のいずれか一項 に記載のメータ。
- 322次 メディア を前記 メディア 提示デバイスにストリーミングするためのストリーマであって、前記2次 メディア が、前記 メディア 提示デバイスにおいてモニタリングされている前記組み合わされたメータリングデータに基づいて選択される、ストリーマをさらに備える、請求項 28~31のいずれか一項 に記載のメータ。
- 33前記メディ アを 搬送する前記トランスポートストリームに関連する メディア 識別メタデータを復号するための復号器であって、前記 メディア 識別メタデータが、前記メディ アの プロバイダによって提供される、復号器と、 前記メディ アか ら抽出された前記第1のメータリングデータを使用して、前記 メディア 識別メタデータを検証するための検証器とをさらに備える、請求項 28~32のいずれか一項 に記載のメータ。
- 34前記メディ アか ら抽出された前記第1のメータリングデータを使用して、前記 メディア 識別メタデータを検証した結果を、メディアモニタリング機関に報告して、前記 メディア 提示デバイスに関連する前記メータによって報告されたメータリング結果の妥当性確認を可能にするための報告器をさらに備える、請求項 33 に記載のメータ。
- 35前記メディ アか ら抽出された前記第1のメータリングデータが、前記メディ ア内 に埋め込まれた透かしデータを含み、前記トランスコードされたメータリングデータが、テキスト形式で表され る、 請求項 28~34のいずれか一項 に記載のメータ。
Independent claims35
149 paragraphs, as filed
Related application
0001[0001] This patent claims the priority of U.S. Patent Application No. 13/341646, entitled "Monitoring Streaming Media Content," filed December 30, 2011, which was filed on June 2011. US Patent Provisional Application No. 61/499520, entitled "Monitoring Streaming Media Content," filed on 21st March, and US Patent, entitled "Monitoring Streaming Media Content," filed on 8th December 2011. Claim the priority of provisional application No. 61/568631. This patent was filed on December 30, 2011, "Monitoring Streaming Media." It also claims the priority of U.S. Patent Application No. 13/341661 entitled "Content", which claims the priority of U.S. Patent Application No. 61/499520 and U.S. Patent Application No. 61/568631. To do. U.S. Patent Applications Nos. 13/341646 and 13/341661, and U.S. Patent Applications Provisional Applications 61/499520 and 61/568631, respectively, are incorporated herein by reference in their entirety.
Field of disclosure
0002[0002] The present disclosure is generally made.<u style="single">, Mo</u>For more information on knitting, see Streaming Medi<u style="single">A</u>Regarding monitoring.
background
0003[0003] Streaming is a wide variety of desktop computers, laptop computers, tablet computers, personal digital assistants, smartphones, etc.<u style="single">media</u>Medi to the presentation device<u style="single">A</u>Delivered and Medi by them<u style="single">A</u>Allows you to present. Medi<u style="single">A</u>A significant portion is presented to such devices by streaming, so broadcast media<u style="single">A</u>Streaming media such as monitoring<u style="single">A</u>Monitoring can provide valuable information to advertisers, content providers, and the like.
0004<figref num="1">Streaming Medi<u style="single">A</u>It is a block diagram of the first exemplary system for monitoring.</figref>
0005<figref num="2">FIG. 5 is a block diagram of a first exemplary server meter that can be used to implement the exemplary system of FIG.</figref>
0006<figref num="3">FIG. 5 is a block diagram of a first exemplary device meter that can be used to implement the exemplary system of FIG.</figref>
0007<figref num="4">FIG. 5 is a block diagram of a first exemplary media monitoring facility that can be used to implement the exemplary system of FIG.</figref>
0008<figref num="5">Streaming Medi<u style="single">A</u>It is a block diagram of a second exemplary system for monitoring.</figref>
0009<figref num="6">FIG. 5 is a block diagram of a second exemplary server meter that can be used to implement the exemplary system of FIG.</figref>
0010<figref num="7">FIG. 5 is a block diagram of a second exemplary device meter that can be used to implement the exemplary system of FIG.</figref>
0011<figref num="8">FIG. 5 is a block diagram of a second exemplary media monitoring agency that can be used to implement the exemplary system of FIG.</figref>
0012<figref num="9">Streaming Medi<u style="single">A</u>It is a block diagram of a third exemplary system for monitoring.</figref>
0013<figref num="10">FIG. 6 is a block diagram of a third exemplary server meter that can be used to implement the exemplary system of FIG.</figref>
0014<figref num="11">FIG. 5 is a block diagram of a third exemplary media monitoring agency that can be used to implement the exemplary system of FIG.</figref>
0015<figref num="12">Streaming Medi<u style="single">A</u>It is a block diagram of a fourth exemplary system for monitoring.</figref>
0016<figref num="13">FIG. 5 is a flow chart representing an exemplary machine-readable instruction that can be executed to implement the first exemplary server meter of FIG.</figref>
0017<figref num="14">FIG. 3 is a flow chart representing an exemplary machine-readable instruction that can be executed to implement the first exemplary device meter of FIG.</figref>
0018<figref num="15">FIG. 5 is a flow chart representing an exemplary machine-readable instruction that can be executed to implement the first exemplary media monitoring agency of FIG.</figref>
0019<figref num="16">FIG. 6 is a flow chart representing an exemplary machine-readable instruction that can be executed to implement the second exemplary server meter of FIG.</figref>
0020<figref num="17">FIG. 6 is a flow chart representing an exemplary machine-readable instruction that can be executed to implement the second exemplary device meter of FIG.</figref>
0021<figref num="18">FIG. 8 is a flow chart representing an exemplary machine-readable instruction that can be executed to implement the second exemplary media monitoring agency of FIG.</figref>
0022<figref num="19">FIG. 5 is a flow chart representing an exemplary machine-readable instruction that can be executed to implement the third exemplary server meter of FIG.</figref>
0023<figref num="20">FIG. 5 is a flow chart representing an exemplary machine-readable instruction that can be executed to implement the third exemplary media monitoring agency of FIG.</figref>
0024<figref num="21">FIG. 6 is a flow chart representing an exemplary machine-readable instruction that can be executed to implement an exemplary metadata inserter contained within the exemplary system of FIG.</figref>
0025<figref num="22">FIG. 5 is a flow chart representing an exemplary machine-readable instruction that can be executed to implement an exemplary transcoder included within the exemplary system of FIG.</figref>
0026<figref num="23">Streaming Medi<u style="single">A</u>FIG. 6 is a block diagram of an exemplary system for combining the metering data to be described.</figref>
0027<figref num="24">FIG. 6 is a block diagram of a fourth exemplary server meter that can be used to implement the exemplary system of FIG.</figref>
0028<figref num="25">FIG. 4 is a flowchart illustrating an exemplary machine-readable instruction that can be executed to implement the fourth exemplary server meter of FIG.</figref>
0029<figref num="26">FIG. 5 shows exemplary metadata that can be generated by the server meter of FIG.</figref>
0030<figref num="27">It is a figure which shows the 2nd exemplary metadata which can be generated by the server meter of FIG.</figref>
0031<figref num="28">Streaming Medi<u style="single">A</u>FIG. 5 is a block diagram of a fifth exemplary system for monitoring.</figref>
0032<figref num="29">FIG. 8 is a flow chart representing an exemplary machine-readable instruction that can be executed to implement an exemplary media monitoring agency included in the exemplary system of FIG. 28.</figref>
0033<figref num="30">Illustrative device meter and secondary in Figure 28<u style="single">media</u>FIG. 6 is a flow chart representing an exemplary machine-readable instruction that can be executed to implement a presenter.</figref>
0034<figref num="31">13-22, 25, 29, and / or the exemplary machine-readable instructions of FIG. 30, FIG. 1, FIG. 5, FIG. 9, FIG. 12, FIG. 23, and / or FIG. 28. One or more of the exemplary systems, one or more of the exemplary server meters of FIGS. 2, 6, 10, and / or 24, the exemplary device meters of FIGS. 3, and / or 7. It is a block diagram of an exemplary processing system capable of implementing one or more of, and / or one or more of the exemplary media monitoring institutions of FIGS. 4, 8, and / or 11.</figref>
Detailed explanation
0035[0035] Streaming Medi<u style="single">A</u>Methods, devices, and products for monitoring are disclosed herein. Streaming Medi<u style="single">A</u>An exemplary method disclosed herein for monitoring is<u style="single">media</u>Presentation debye<u style="single">To</u>Streaming Medi<u style="single">A</u>Decrypt the transport stream to carry and mediate<u style="single">A</u>Includes steps to acquire. An exemplary method is to mediate metering data having the first form.<u style="single">A?</u>It is a step to extract from, and the metering data is the media.<u style="single">A and</u>Medi<u style="single">A</u>It also includes a step that identifies at least one of the sources. An exemplary method is to transcode the extracted metering data.<u style="single">media</u>It further comprises the step of forming metering data (eg, metering metadata) having a second form that can be decoded by the meter performed by the presentation device.
0036[0036] In some examples, the method is extracted metering data, or streaming media.<u style="single">To a</u>Dependent (eg, incidental) separately collected metering data (eg, Medi)<u style="single">A</u>Metering data from the provider), streaming media<u style="single">To a</u>Related, but streaming media<u style="single">With a</u>Further includes steps to combine with independently provided metering data (eg, 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, and then the combined metering data is transcoded into metering metadata. To form. In some examples, an independent metering data source determines the time stamp from a clock source and streams media from a data source (eg, a configuration file) communicatively coupled to the independent metering data source.<u style="single">A</u>Determine the identifier for. In some examples, the metering data from an independent metering data source and the extracted metering data are duplicated, identical, or similar. In some examples, the method inserts a tag or other identification mark within the extracted metering data by an independent metering data source to identify the independently provided metering data. Including. In some examples, the delimiter (for example, a text character such as the "|" character, or some other sign or indicator) is the extracted metering data and the metering data from an independent metering data source. It is inserted in between.
0037[0037] In some examples, the method relates transcoded metering data (eg, extracted metering data, or metering data combined after transcoding) to a transport stream (eg,). For example, steps to encode into a metadata channel that accompanies or flows together, and transport streams and metadata channels.<u style="single">media</u>It further includes a step of sending to the presentation device. In some examples, the method then uses the transport stream and metadata channel.<u style="single">media</u>Steps to receive on the presentation device and<u style="single">media</u>It includes a step of detecting metering data in a metadata channel using a meter performed by a presentation device and a step of reporting the metering data to a media monitoring agency.
0038[0038] In some examples, the metadata channel is a media<u style="single">A</u>An external metadata channel or media outside the transport stream to carry<u style="single">A</u>Corresponds to at least one of the internal metadata channels containing one or more data fields of the transport stream being carried. An example of an external metadata channel includes an M3U file or other data file encoded to contain metering metadata, and the file is:<u style="single">media</u>Associated with the transport stream sent to the presentation device.
0039[0039] In some examples, transport streams are transmitted according to the hypertext transfer protocol (HTTP), the Moving Picture Experts Group (MPEG). Supports 2 transport streams. In some examples, (Medi decrypted from the transport stream<u style="single">A?</u>The metering data with the first form (extracted from) is Medi<u style="single">A</u>It can include an audio watermark embedded in the audio portion. In addition, or as an alternative, (Medi decrypted from the transport stream)<u style="single">A?</u>The metering data with the first form (extracted from) is Medi<u style="single">A</u>It can include a video watermark (eg, an image watermark) embedded in the video portion. In some examples, metering metadata with a second format in which the extracted metering data is transcoded into metadata represented in text format, such as text format for inclusion in an M3U file. Correspond.
0040[0040] Streaming Medi<u style="single">A</u>Another exemplary method disclosed herein is for monitoring.<u style="single">media</u>Medi-streamed to the presentation device<u style="single">A</u>Decrypt the transport stream to carry and mediate<u style="single">A</u>Includes steps to acquire. An exemplary method is to mediate metering data<u style="single">A?</u>Is the step of extracting and / or receiving metering data from an independent metering data source, where the metering data is the media.<u style="single">A and</u>Medi<u style="single">A</u>It also includes a step that identifies at least one of the sources. In addition, an exemplary method is Medi<u style="single">A</u>Already attached to the transport stream to be transported (for example, electronic guide data, playlist data, etc.)<u style="single">media</u>It further includes a step of decrypting the identification metadata. An exemplary method is Medi<u style="single">A?</u>Using the metering data extracted from<u style="single">media</u>It further includes a step to validate the identification metadata.
0041[0041] In some examples, the method is Medi<u style="single">A?</u>Using the metering data extracted from<u style="single">media</u>Report the results of verifying the identification metadata to the media monitoring agency,<u style="single">media</u>Reported separately by the meter performed by the presentation device<u style="single">media</u>It further includes steps that allow validation of the identification metadata. For example<u style="single">media</u>The meter performed by the presentation device is<u style="single">media</u>Streaming media to presentation device<u style="single">A</u>Accompanying the provided transport stream,<u style="single">media</u>Identification metadata can also be detected. Then the meter is this<u style="single">media</u>Identification metadata can be reported to media monitoring agencies, which media monitoring agencies<u style="single">A?</u>Using the metering data extracted from<u style="single">media</u>Based on the results reported by previously validating the identification metadata<u style="single">media</u>Validate the identification metadata. As mentioned above, in some examples, the media decrypted from the transport stream<u style="single">A?</u>The metering data extracted from the<u style="single">A</u>It can include an audio watermark embedded in the audio portion. In addition or as an alternative, the media decrypted from the transport stream<u style="single">A?</u>The metering data extracted from the<u style="single">A</u>A video (eg, image) watermark embedded in the video portion can be included. In addition, or as an alternative, the method can include reporting metering data received from an independent metering data source.
0042[0042] Streaming Medi<u style="single">A</u>Another exemplary method disclosed herein is for monitoring.<u style="single">media</u>Medi to the presentation device<u style="single">A</u>Before streaming,<u style="single">media</u>Medieval (streamed to the presentation device)<u style="single">A</u>Includes a step of storing in a temporary storage device. An exemplary method is from temporary storage to Medi<u style="single">A</u>Steps to search and (eg Medi<u style="single">In a</u>Medit metering data (such as audio / video watermarks (s) embedded in<u style="single">A?</u>It is a step to extract from, and the metering data is the media.<u style="single">A and</u>Medi<u style="single">A</u>It also includes a step that identifies at least one of the sources. The method can also include combining the extracted metering data with metering data from an independent metering data source. The exemplary method further includes the step of reporting the metering data to the media monitoring agency.
0043[0043] Broadcasted Medi<u style="single">A</u>Traditional techniques for monitoring are monitored presentation media.<u style="single">A?</u>Etc., it can include extracting metering data such as audio and / or video watermarks. Streaming Medi<u style="single">A</u>In the scene, digital rights management,<u style="single">media</u>Medis utilized by the presentation device<u style="single">Up</u>Streamed media by applications such as device meters other than layers<u style="single">To a</u>May interfere with access. Streaming media according to the examples described herein.<u style="single">A</u>Monitoring is<u style="single">media</u>The device meter performed by the presentation device is inaccessible from the device meter in the first form that is not decryptable by the device meter (eg, due to digital rights management, media).<u style="single">In a</u>A second format (eg, streaming media) that can be decoded by the device meter from the first format corresponding to the audio or video watermark embedded in<u style="single">To a</u>A streaming media transcoded into a second format that corresponds to the text format contained within the file sent over the accompanying metadata channel).<u style="single">A</u>Allows detection of identifying metering metadata. In addition, or as an alternative, streaming media according to the examples described herein.<u style="single">A</u>Monitoring is a streaming media<u style="single">To a</u>Already attached, decryptable by device meter without transcoding<u style="single">media</u>The validity of the identification metadata, Medi<u style="single">A?</u>It is possible to confirm using the metering data extracted from the above (for example, audio and / or video watermark). The examples disclosed herein are streaming media.<u style="single">A</u>Although described in connection with monitoring, exemplary methods and devices disclosed herein are non-streaming media.<u style="single">A</u>It can also be applied to monitoring.
0044[0044] See Figure, Streaming Medi<u style="single">A</u>A block diagram of the first exemplary system 100 for monitoring is shown in Figure 1. The exemplary system 100 includes a first exemplary server meter 105, a first exemplary device meter 110, and an exemplary system 100.<u style="single">media</u>Medi-streamed to presentation device 120<u style="single">A</u>Includes a first exemplary media monitoring agency 115 for monitoring. In the example shown, system 100 has an exemplary compression gear 130, an exemplary segmenter and packager 135, and an exemplary digital rights manager 140. And by the exemplary content provider (s) 125<u style="single">media</u>Streaming media provided to presentation device 120<u style="single">A</u>Illustrative to provide<u style="single">media</u>story<u style="single">Ma 1</u>Including 45 and. An exemplary system 100 media through it<u style="single">Media</u>By streamer 145<u style="single">media</u>It further includes an exemplary network 150 that can be streamed to the presentation device 120, through which the device meter 110 can report metering data to the media monitoring agency 115.
0045[0045] The example content provider (s) 125 shown is<u style="single">media</u>Medi for streaming to presentation device 120<u style="single">A</u>Corresponds to any one or more content providers available. Medis provided by Content Provider (s) 125<u style="single">A is</u>,voice<u style="single">media</u>, Video<u style="single">media</u>, Multimedical<u style="single">Ah</u>Any type of medi<u style="single">With a</u>can do. In addition, Medi<u style="single">A is</u>, Live (eg broadcast) Medi<u style="single">A,</u>Saved Medi<u style="single">A (</u>For example, on-demand content) can be supported.
0046[0046] The compression gear 130 uses any suitable technique (s) to receive the media.<u style="single">A</u>Compress to a format suitable for streaming and / or process separately. For example, compression gear 130 follows MPEG4 audio / video compression.<u style="single">A</u>Can be compressed. The segmenter and packager 135 are compressed media using any suitable technique (s).<u style="single">A</u>Segment and package into a format suitable for streaming. For example, the segmenter and packager 135 uses the HTTP live streaming (HLS) protocol, or any other streaming protocol in the past, present, and / or future, over network 150.<u style="single">media</u>Compressed media for streaming to presentation device 120<u style="single">A</u>Segment and package into one or more MPEG2 transport streams. Digital Rights Manager 140 is a media streamed according to any suitable digital rights management technique and / or protocol.<u style="single">A</u>Encrypt and / or protect separately.<u style="single">media</u>Streamer 145 uses any suitable technique (s) to mediate<u style="single">A</u>Selected,<u style="single">media</u>Stream to the requesting device, such as presentation device 120. For example<u style="single">media</u>Streamer 145 is an MPEG4 compressed, segmented, packaged MPEG2 transport stream, and encrypted for digital rights management.<u style="single">A</u>Select and then use HLS or any other streaming protocol over network 150<u style="single">media</u>To presentation device 120<u style="single">media</u>Stream.
0047[0047] In some examples, the compression gear 130, segmenter and packager 135, and / or digital rights manager 140 (eg, in advance).<u style="single">media</u>For streaming regardless of whether a request was received from the presentation device 120<u style="single">media</u>Prepare. In such an example,<u style="single">media</u>Streamer 145<u style="single">media</u>Already prepared when the request was received from the presentation device 120<u style="single">media</u>To<u style="single">media</u>Prepare the transport stream for streaming to the presentation device 120. In another example, the compression gear 130, segmenter and packager 135, and / or digital rights manager 140<u style="single">media</u>To stream in response to a request received from the presentation device 120<u style="single">media</u>Prepare.
0048[0048] In the example shown<u style="single">media</u>The presentation device 120 is over the network 150.<u style="single">media</u>Streaming media provided by Streamer 145<u style="single">A</u>It is a computing device that can be presented.<u style="single">media</u>Presentation device 120 includes, for example, desktop computers, laptop computers, mobile computing devices, televisions, smartphones, mobile phones, Apple® iPad®, Apple® iPhone®. ), Apple (registered trademark) iPod (registered trademark), Android (trademark) equipped computer device, Palm (registered trademark) webOS (registered trademark) computing device, etc. In some examples<u style="single">media</u>The presentation device 120<u style="single">media</u>Streaming media provided by Streamer 145<u style="single">A</u>Includes one or more executable media players for presentation. For example<u style="single">media</u>The media player (s) available on the presentation device 120 can be implemented in Adobe (registered trademark) Flash (registered trademark) (provided, for example, in a SWF file) and hypertext. It can be implemented in Markup Language (HTML) version 5 (HTML5), it can be implemented in Google® (registered trademark) Chromium (registered trademark), and it can be implemented in the Open Source Media Framework (OSMF: Open). Can be implemented according to the Source Media Framework), can be implemented according to the device or operating system provider's media player application programming interface (API), and can be implemented according to the device or operating system provider's media player framework (eg, Apple®). It can be implemented on iOS (registered trademark) MPMoviePlayer software, etc., or can be any combination thereof. single<u style="single">media</u>Presentation device 120 is shown, but system 100 is of any number and / or type.<u style="single">media</u>Presentation devices can be included.
0049The network 150 in the example shown is the Internet. In addition or as an alternative<u style="single">media</u>Streamer 145,<u style="single">media</u>Any other network (s) that connect the presentation device 120, device meter 110, and / or media monitoring agency 115 may also be used. The network 150 can include any number of public and / or private networks that use any type (s) of networking protocols (s).
0050[0050] As mentioned above, the media provided by Content Provider (s) 125.<u style="single">A is</u>, Medi<u style="single">A</u>Identify and / or separate media<u style="single">To a</u>It can include related metering data such as embedded audio and / or video watermarks. However, such metering data is<u style="single">media</u>It may not be accessible by the device meter of the presentation device 120 and therefore may not be decryptable. For example, Medi<u style="single">A,</u>As a result, the audio and / or video watermark embedded in it is only accessible by a suitable media player due to the digital rights management techniques utilized by Digital Rights Manager 140, and by some device meters or other applications. It may not be accessible. Device meter 120<u style="single">media</u>Streaming media provided to presentation device 120<u style="single">A</u>The example system 100 shown includes a server meter 105 to allow access to and / or decryption of metering data associated with it. In some examples, the server meter 105 has a compression gear 130, a segmenter and packager 135, a digital rights manager 140, and / or<u style="single">media</u>Implemented as a plug-in or other application / device associated with or executed by one or more of the streamers 145. In some examples, the server meter 105 has a compression gear 130, a segmenter and packager 135, a digital rights manager 140, and<u style="single">media</u>It is carried out by a device different from the streamer 145.
0051[0051] In the example shown, the server meter 105 is a media.<u style="single">A?</u>To obtain metering data in the first form. In some examples, the server meter 105 can also collect metering data from one or more independent metering data sources. Metering data from an independent metering data source can take the first form or any other form (s). The server meter 105 then transcodes the acquired metering data (eg, extracted metering data and / or metering data from an independent metering data source) and is accessible by the device meter 110. It forms metering metadata that takes the second form, which is and is decodable. Metering data is Medi<u style="single">A</u>Identify and Medi<u style="single">A</u>Identify the source and / or separate media<u style="single">A</u>Describe and / or related to it. For example, the server meter 105 can acquire an embedded audio / video watermark corresponding to the metering data having the first form, and / or the server meter 105 is metering from an independent metering data source. Data can be acquired. The server meter 105 then transcodes this metering data into text data, binary data, etc. corresponding to the second form of metering metadata. After that, the server meter 105,<u style="single">media</u>Transcoded metering metadata (which takes the second form, which is performed by the presenting device 120 or is separately decodable by the device meter 110 associated therewith).<u style="single">media</u>Streaming media to presentation device 120<u style="single">A</u>Encode to the metadata channel associated with the transport stream (s) to carry. In some examples, the server meter 105 mediates audio / video watermarks.<u style="single">In a</u>It is implemented as a plug-in based on the software development kit (SDK) provided by the entity embedded in. In such an example, the server meter 105 takes advantage of the features provided by the SDK.<u style="single">In a</u>It is possible to extract the audio / video watermark (s) embedded in the watermark, decode it, and acquire the payload data carried by the watermark (s). In some examples, according to one or more versions of the ID3 tagging standards, the server meter 105 then pulls the payload data obtained from the watermark (s) into the ID3 tag metadata (ID3 tag). metadata) and / or other metadata according to HLS or other suitable streaming protocol<u style="single">A</u>Insert in the transport stream (s) to be streamed. Another exemplary implementation of the server meter 105 is shown in FIG. 2, which is described in more detail below.
0052[0052] The server meter 105 takes advantage of the features provided by the SDK (eg, receiving data from the internal clock, from user input).<u style="single">media</u>Receive identification information, from a file, or media<u style="single">A</u>From another source independent of the provider<u style="single">media</u>Metering data can also be collected from an independent metering data source (for example, by receiving identification information). An exemplary implementation of the server meter 105, including an independent metering data source, is illustrated in connection with FIG. 24.
0053[0053] System 100<u style="single">media</u>Provided to presentation device 120 and / or<u style="single">media</u>Streaming media presented by presentation device 120<u style="single">A</u>A device meter 110 for monitoring can also be included. In the example shown, the device meter 110<u style="single">media</u>Performed by the presentation device 120. In some examples, the device meter 110<u style="single">media</u>It can be implemented as a plug-in connected to the plug-in interface of the media player performed by the presentation device 120. In some examples, the device meter 110<u style="single">media</u>It can be implemented as one or more instructions contained within the media player executed by the presentation device 120. In some examples, the device meter 110<u style="single">media</u>It can be implemented as an executable application that is downloaded to the presentation device 120 (eg, downloaded as an App from the Apple® App Store). In some examples, the device meter 110<u style="single">media</u>Apart from the presentation device 120,<u style="single">media</u>Streaming media received by presentation device 120<u style="single">To a</u>To relevant metadata (eg<u style="single">media</u>Performed by a device that is accessible (via one or more digital interfaces, data ports, etc.) of the presentation device 120.
0054[0054] The example device meter 110 shown is<u style="single">media</u>Streaming media to presentation device 120<u style="single">A</u>Decrypts metering metadata contained within a metadata channel (s) associated with the transport channel (s) provided (eg, previously provided, incidental, and flowing together). For example, the metadata channel decoded by the device meter 110 is a media<u style="single">A</u>An external metadata channel or media outside the transport stream to carry<u style="single">A</u>It can accommodate an internal metadata channel that contains one or more data fields of the transport stream to carry. An exemplary external metadata channel is a streaming media<u style="single">A</u>Includes M3U files or other text files that relate to the transport stream to be transported and contain metering metadata transcoded to text or other suitable data format by the server meter 105. In some examples, such as one using the HLS protocol, the device meter 110 extracts and decodes ID3 tags (s) containing metering metadata. The device meter 110 in the example shown is the decoded metering metadata (as well as any other metering information captured by the device meter, the decoded metering meta) for reporting to the media monitoring agency 115. The data stores the time stamp added by the device meter 110 and / or other metering information, etc.). In the example shown, the device meter 110 uses HTTP requests sent to the HTTP interface of the media monitoring agency 115 to capture stored metering metadata (and any other metering information, time stamps, etc.). Report. An exemplary implementation of the device meter 110 is shown in FIG. 3, which is described in more detail below.
0055[0055] The media monitoring agency 115 includes an interface for receiving reported metering information (eg, metering metadata) received from the device meter 110 over the network 150. In the example shown, the media monitoring agency 115 includes an HTTP interface for receiving HTTP requests containing metering information. Alternatively, any other method (s) for receiving metering information can be used. In the example shown, the media monitoring agency 115 has several different<u style="single">media</u>The metering information received from the presentation device 120 is stored and analyzed. For example, the media monitoring agency 115 may group metering information by content provider 125 (eg, group all metering data associated with a particular content provider 125). The media monitoring agency 115 can also analyze the metering information to eliminate erroneous information. For example, the media monitoring agency 115 (eg, streaming media)<u style="single">To a</u>Already attached<u style="single">media</u>Same media (by comparing the identification metadata with the metering data and / or metadata determined by the device meter 110 and / or the server meter 105)<u style="single">To a</u>The two types of identification information received can be compared to identify the difference, the metering information containing the difference can be excluded, and / or excluded from the metering information received later. Can be marked to indicate that certain identification information is incorrect. In addition, or as an alternative, any other processing of metering information can be performed.
0056[0056] In some examples, the reported metering information can include metering data acquired by a dependent metering data source and an independent metering data source. Dependent metering data sources are, for example, Medi<u style="single">A and</u>And / or Medi<u style="single">A</u>Includes sources of metering data obtained from the provided transport streams (s), related to them, or separately dependent on them. For example, a dependent metering data source is a streaming media<u style="single">A</u>It can contain metering data extracted from the watermark payload. In contrast, independent metering data sources are, for example, Medi<u style="single">A and</u>And / or Medi<u style="single">A</u>Obtained independently of the transport stream provided (s), but nevertheless Medi<u style="single">A</u>Includes sources of metering data that can be described. For example, an independent metering data source may be metering data that is the same as metering data obtained from a dependent metering data source, metering data that is similar to metering data obtained from a dependent metering data source, and so on. It can contain redundant metering data acquired by an independent metering data source (eg, source identifier stored in the configuration file of server meter 105). In such an example, the media monitoring agency 115 can utilize redundant metering data to validate metering data from dependent metering data sources. Illustrative metadata with redundant metering data obtained from an independent metering data source is illustrated in connection with FIG. 26. In some examples, the media monitoring agency 115 can store and analyze both redundant metering data and metering data from dependent metering data sources. In some examples, the media monitoring agency 115 may store and / or analyze redundant metering data if the metering data from the dependent metering data source cannot be read by the media monitoring agency 115. it can. For example, metering data from a dependent metering data source is streamed by the server meter 105.<u style="single">A?</u>If the audio / video watermark cannot be extracted (for example, streaming media)<u style="single">A</u>Audio watermarks may not be available during silence), error checking may fail, may be blank, or may be null. Illustrative metadata with unreadable metering data from dependent metering data sources is illustrated in connection with FIG. 27.
0057[0057] The media monitoring agency 115 in the example shown is<u style="single">media</u>Analyzing the received metering information reported by the presentation device (s) 120, Medi<u style="single">A</u>You can also generate a report on the presentation. For example, media monitoring agency 115<u style="single">A</u>Number of accesses, Medi<u style="single">To a</u>Demographics of visiting users, users and media<u style="single">With a</u>Dialogue (eg fast forward, pause, etc.), Medi<u style="single">A</u>You can generate a report that shows the duration of access and so on. The media monitoring agency 115 provides, for example, a web page interface through which stakeholders can generate custom reports or access metering information separately (eg, for part of a fee or subscription service). be able to. For example, the media monitoring agency 115 reports for a particular content provider 125, for advertisers serving ads through the content provider (s) 125, for competitors in the content provider (s) 125, and so on. Can be generated. Another exemplary practice of Media Monitoring Agency 115 is shown in Figure 4, which is described in more detail below.
0058A block diagram of an exemplary implementation of the exemplary server meter 105 of FIG. 1 is shown in FIG. The exemplary server meter 105 in Figure 2 is a streaming media.<u style="single">A</u>Decrypt the transport stream (s) to carry and<u style="single">media</u>Medi-streamed to presentation device 120<u style="single">A</u>Includes an exemplary transport stream decoder 205 for acquisition. For example, the Transport Stream Decoder 205 is an MPEG4 compression media.<u style="single">A</u>Decoding the encapsulated MPEG2 transport 2 to encapsulate the MPEG4<u style="single">media</u>And then run MPEG4 decompression to uncompressed audio / video<u style="single">media</u>Can be earned.
0059The exemplary server meter 105 of FIG. 2 is an uncompressed media obtained from the transport stream decoder 205.<u style="single">A?</u>Also included is an exemplary metering data extractor 210 for extracting metering data having the first form of these. For example, the metering data extractor 210 performs the functions provided by the SDK and uncompressed audio / video obtained from the transport stream decoder 205.<u style="single">media</u>It is possible to extract one or more audio watermarks, one or more video (eg, image) watermarks embedded within. (For example, uncompressed audio / video<u style="single">media</u>Can accommodate uncompressed pulse code modulation (PCM) audio data or other types of audio data, uncompressed video / image data, etc.). The exemplary server meter 105 in FIG. 2 is exemplary in order to transcode the first form of metering data obtained from the metering data extractor 210 into a second form that can be decoded by the device meter 110. Also includes a metering data transcoder 215. For example, the metering data transcoder 215 may include metering information (eg, eg) carried by a watermark extracted by the metering data extractor 210.<u style="single">media</u>Watermark payload data such as identification information, source identification information, etc. can be determined (for example, decrypted), and this metering information (also called watermark payload data) can be streamed to the streaming media.<u style="single">To a</u>In text or binary format for inclusion in M3U8 files or other data (eg text, binary, etc.) files for transmission as accompanying metadata (eg with playlists or electronic program guides, etc.) Can be converted. In addition, or as an alternative, the metering data transcoder 215 transfers the extracted metering information (ie, watermark payload data).<u style="single">media</u>Streaming media to presentation device 120<u style="single">A</u>The provided transport stream (s) may be converted to binary or other suitable format for inclusion in one or more data fields capable of carrying metadata. For example, the metering data transcoder 215 mediates the watermark payload data corresponding to the metering information according to HLS or other suitable streaming protocol.<u style="single">A</u>It can be converted to ID3 tag metadata for insertion into the transport stream (s) to be streamed. Other additional or alternative examples of transcoding available by the metering data transcoder 215 to transcode metering data into a format that can be decoded by the device meter 110, eg, November 2010 2 US Patent No. 7827312 (Ramaswamy et al., "METHODS AND APPARATUS FOR TRANSCODING METADATA") issued on February 14, 2011, and US Patent Provisional Application No. 61/442758 (Deliyannis et al., "METHODS" filed on February 14, 2011. AND APPARATUS TO MONITOR MEDIA CONTENT AT A CONTENT DISPLAY SITE "). U.S. Pat. No. 7827312 and U.S. Patent Provisional Application No. 61/442758, respectively, are incorporated herein by reference in their entirety. In some examples, the metering data extractor 210 is replaced by one or more of the elements of FIG. 24 that allow the server meter 505 to operate according to the system described in connection with FIG. 23. , Or they can be included.
0060[0060] In addition, in some examples, the server meter 105 in FIG. 2 utilizes any suitable encryption to encrypt the metering metadata determined by the metering data transcoder 215. Includes an exemplary metering metadata encoder 220. For example, the metering metadata encrypter 220 encrypts metering metadata using public or private key encryption, where the decryption key (s) is known and protected by the media monitoring agency 115. Can be transformed into. Including the metering metadata encryptor 220 allows unauthorized eavesdroppers to stream media<u style="single">A</u>It can prevent access to transcoded metering metadata that is identified or otherwise associated with it, thereby streaming media.<u style="single">A</u>Protect the privacy of consuming users.
0061[0061] In the example shown in FIG. 2, the server meter 105 is a metering meta determined by the metering data transcoder 215 (encrypted by the metering metadata encoder 220, if appropriate). Streaming media to include data<u style="single">A</u>Includes an exemplary transport stream encoder 225 for recoding the transport stream (s). For example, the transport stream encoder 225 contains metering metadata and<u style="single">media</u>Streaming media to presentation device 120<u style="single">A</u>External metadata for metering metadata, such as by encoding M3U8 or other data files related to the transport stream (s) provided (eg, included, added, sent ahead, etc.) It can be coded into a data channel. In addition, or as an alternative, the transport stream encoder 225 can carry metering metadata in binary or other suitable data format, one of the transport streams (s) capable of carrying the metadata. Metering metadata can be encoded in the internal metadata channel, such as by encoding into one or more data fields. For example, the transport stream encoder 225 mediates the ID3 tag metadata corresponding to the metering metadata according to HLS or other suitable streaming protocol.<u style="single">A</u>Can be inserted within the transport stream (s) to be streamed.
0062An exemplary implementation block diagram of the exemplary device meter 110 of FIG. 1 is shown in FIG. The exemplary device meter 110 in Figure 3<u style="single">media</u>Streaming media to presentation device 120<u style="single">A</u>Includes an exemplary metering metadata extractor 305 for extracting metering metadata from external and / or internal metadata channels associated with the provided transport stream (s). For example, metering metadata extractor 305 contains metering metadata and contains<u style="single">media</u>Streaming media to presentation device 120<u style="single">A</u>External metadata channels (or two), such as by decrypting M3U8 or other data files related to the transport stream (s) provided (eg, included, added, sent in advance, etc.) Metering metadata can be extracted from the above external metadata channels). In addition, or as an alternative, the metering metadata extractor 305 can decode metering metadata from one or more data fields of a transport stream (s) capable of carrying metadata, etc. Allows you to extract metering metadata from an internal metadata channel (or two or more internal metadata channels). In some examples, such as one using the HLS protocol, the metering metadata extractor 305 extracts and decodes ID3 tags (s) containing metering metadata.
0063[0063] The exemplary device meter 110 of FIG. 3 is an exemplary metering metadata reporter 310 for reporting the metering metadata acquired by the metering metadata extractor 305 to the media monitoring agency 115. Also includes. For example, the metering metadata reporter 310 can generate a GET or POST request that includes metering metadata as a parameter of the request. Alternatively, any other method of transmitting metering metadata to the media monitoring agency 115 can be used. Metering metadata can be transmitted at arbitrary intervals. For example, metering metadata can be sent when it is collected (eg, streamed), and when a certain amount of metering metadata is collected, the available memory space is full. Or when a threshold capacity is reached (eg, 90% or some other percentage is met), or when a particular event is detected (eg, Medi)<u style="single">A</u>When the presentation is finished, a new media<u style="single">A</u>It can be sent at any time, such as when presented) or when new metering metadata is acquired. Metering metadata reporter 310 is for each media<u style="single">To a</u>You can send metering metadata only once, or (eg, every time an event occurs (eg, Medi).<u style="single">A</u>Medi<u style="single">A</u>The metering metadata can be transmitted multiple times (for example, each time the identification information changes when it contains metering data that changes during continuation).
0064[0064] In some examples, the device meter 110 can determine metering information in addition to the metering metadata extracted by the metering metadata extractor 305. For example, the device meter 110 is a streaming media.<u style="single">A</u>Already attached to the transport stream (s) provided (eg, other<u style="single">media</u>Other metadata (such as identification metadata) can be collected. In addition, or as an alternative, in some examples, the device meter 110 is a Medi<u style="single">A</u>Use of media player to present, media<u style="single">A</u>While being presented<u style="single">media</u>Information can be collected that represents other uses of the presentation device 120, etc., or any combination thereof. In such an example, the metering metadata reporter 310 uses one or more of the exemplary mechanisms described above, along with the metering metadata extracted by the metering metadata extractor 305. , Or separately, this additional metering information may be reported to the media monitoring agency 115.
0065A block diagram of an exemplary implementation of the exemplary media monitoring agency 115 of FIG. 1 is shown in FIG. The exemplary media monitoring agency 115 of FIG. 2 includes an exemplary metering metadata collector 405 for collecting metering metadata (and other metering information) reported by the device meter 110. As described above, the metering metadata collector 405 in the example shown includes an HTTP interface for receiving HTTP requests containing metering information. In addition, or as an alternative, any other method (s) for receiving metering information can also be used. The metering metadata collector 405 also stores (eg, collects) and analyzes the received metering information, as described above in connection with FIG. The exemplary media monitoring agency 115 in FIG. 2 also includes an exemplary report generator 410 for generating reports based on the reported metering information, as described above in connection with FIG. ..
0066[0066] Streaming Medi<u style="single">A</u>A block diagram of a second exemplary system 500 for monitoring is shown in Figure 5. The second exemplary system 500 contains many elements in common with the first exemplary system 100 of FIG. Therefore, similar elements in FIGS. 1 and 5 are given the same reference numbers. A detailed description of these similar elements is provided above in connection with the description of FIG. 1 and is not repeated in the description of FIG. 5 for brevity.
0067[0067] With reference to FIG. 5, the illustrated system 500 is via a compression gear 130, a segmenter and packager 135, a digital rights manager 140, and a network 150.<u style="single">media</u>Streaming media to presentation device 120<u style="single">A</u>To provide<u style="single">media</u>Includes streamer 145 and. Medi to System 500<u style="single">A</u>To provide, the example shown in FIG. 5 includes a content provider (s) 125.<u style="single">media</u>Medi-streamed to presentation device 120<u style="single">A</u>For monitoring, the system 500 of the example shown also includes a second exemplary server meter 505, a second exemplary device meter 510, and a second exemplary media monitoring agency 515. In some examples, the server meter 505 is a compression gear 130, a segmenter and packager 135, a digital rights manager 140, and / or<u style="single">media</u>It can be implemented as a plug-in or other application / device associated with or executed by one or more of the streamers 145. In some examples, the server meter 505 has a compression gear 130, a segmenter and packager 135, a digital rights manager 140, and<u style="single">media</u>It can be carried out by a device different from the streamer 145. In some examples, the device meter 510<u style="single">media</u>It can be implemented as a plug-in connected to the plug-in interface of the media player performed by the presentation device 120. In some examples, the device meter 510<u style="single">media</u>It can be implemented as one or more instructions provided within the media player executed by the presentation device 120. In some examples, the device meter 510<u style="single">media</u>It can be implemented as an executable application that is downloaded to the presentation device 120 (eg, downloaded as an App from the Apple® App Store). In some examples, the device meter 510<u style="single">media</u>Apart from the presentation device 120,<u style="single">media</u>Streaming media received by presentation device 120<u style="single">To a</u>To relevant metadata (eg<u style="single">media</u>Performed by a device that is accessible (via one or more digital interfaces, data ports, etc.) of the presentation device 120.
0068[0068] The example server meter 505 shown is<u style="single">media</u>Medi-streamed to presentation device 120<u style="single">A</u>Decrypts the transport stream (s) to be carried, and the decrypted media<u style="single">A?</u>Extract metering data from. Metering data is Medi<u style="single">A</u>Identify and Medi<u style="single">A</u>Identify the source and / or separate media<u style="single">A</u>Describe and / or related to it. For example, the server meter 505 is a Medi<u style="single">In a</u>Audio and / or video watermarks embedded in can be extracted. In addition, the server meter 505<u style="single">media</u>Medi-streamed to presentation device 120<u style="single">A</u>Already attached to the transport stream (s) to be transported (for example, electronic guide data, playlist data, etc.)<u style="single">media</u>Decrypt the identification metadata. In some examples, the server meter 505 is a Medi<u style="single">A?</u>Using the metering data extracted from<u style="single">A</u>Already attached to the transport stream (s) to be carried<u style="single">media</u>Validate the identification metadata. For example, electronic guide data, playlist data, etc. may have errors or may not be up to date. Medi<u style="single">A?</u>Using the metering data extracted from<u style="single">media</u>By validating the identification metadata, media monitoring agency 515<u style="single">A</u>Already attached to the transport stream (s) to be carried<u style="single">media</u>It is possible to know if the identification metadata is accurate and therefore can be used for media monitoring purposes. An exemplary implementation of the server meter 505 is shown in FIG. 6, which is described in more detail below.
0069[0069] System 500<u style="single">media</u>Streaming media presented by presentation device 120<u style="single">A</u>Includes device meter 510 for monitoring. The device meter 510 in the example shown is<u style="single">media</u>Medi-streamed to presentation device 120<u style="single">A</u>Already attached to the transport stream (s) to be transported (for example, electronic guide data, playlist data, etc.)<u style="single">media</u>Decrypt the identification metadata. The device meter 510 is used to report to the media monitoring agency 115.<u style="single">media</u>Stores identification metadata (and any other metering information captured by the device meter). In the example shown, device meter 510 stored using an HTTP request sent to the HTTP interface of media monitoring agency 515.<u style="single">media</u>Report identification metadata (and any other metering information). An exemplary implementation of the device meter 510 is shown in FIG. 7, which is described in more detail below.
0070[0070] Media monitoring agency 515 reported receiving from device meter 510 over network 150<u style="single">media</u>Includes an interface for receiving identification metadata. Media monitoring agency 515 reported by device meter 510<u style="single">media</u>Whether the identification metadata is valid (eg this<u style="single">media</u>It also includes an interface for receiving verification results from the server meter 505 that indicate (whether the identification metadata is accurate).<u style="single">media</u>Assuming that the identification metadata is valid, the media monitoring agency 515 was reported using a technique similar to the technique utilized by the media monitoring agency 115 for processing the reported metering metadata.<u style="single">media</u>Storage, analysis, and report generation can be performed based on the identification metadata. An exemplary implementation of Media Monitoring Agency 515 is shown in Figure 8, which is described in more detail below.
0071A block diagram of an exemplary implementation of the exemplary server meter 505 of FIG. 5 is shown in FIG. Similar to the exemplary server meter 105 in FIG. 2, the server meter 505 in FIG. 6 is a streaming media.<u style="single">A</u>Decrypt the transport stream (s) to carry and<u style="single">media</u>Medi-streamed to presentation device 120<u style="single">A</u>Includes transport stream decoder 205 for acquisition. Similar to the exemplary server meter 105 in FIG. 2, the exemplary server meter 505 in FIG. 6 is a media obtained from the transport stream decoder 205.<u style="single">In a</u>Also included is a metering data extractor 210 for extracting metering data, such as one or more audio watermarks, one or more video watermarks, embedded in. Further discussion of these elements is provided above in connection with the description of FIG. 2 and is not repeated in the description of FIG. 6 for brevity.
0072The exemplary server meter 505 of FIG. 5 is a streaming media.<u style="single">A</u>Already attached to the transport stream (s) to be carried<u style="single">media</u>Identification metadata (and / or other<u style="single">media</u>Illustrative for extracting descriptive information)<u style="single">media</u>Further includes a metadata extractor 605. For example<u style="single">media</u>Metadata extractor 605<u style="single">media</u>Streaming media to presentation device 120<u style="single">A</u>From playlists, electronic program guides, data files, etc. that are already attached to the provided transport stream (s) (for example, already included, added, previously sent, etc.)<u style="single">media</u>Identification metadata can be extracted. The exemplary server meter 505 of FIG. 5 is<u style="single">media</u>Acquired by Metadata Extractor 605<u style="single">media</u>Comparing the identification metadata with the metering data obtained from the metering data extractor 210,<u style="single">media</u>It also includes an exemplary metadata verifier 610 for determining whether the identifying metadata is valid (eg, correct, accurate, up-to-date, etc.). The metadata verifier 610 also reports the validation results to the media monitoring agency 515 over the network 150 (eg, using one or more HTTP requests).
0073A block diagram of an exemplary implementation of the exemplary device meter 510 of FIG. 5 is shown in FIG. The exemplary device meter 510 in FIG. 7 is<u style="single">media</u>Streaming media to presentation device 130<u style="single">A</u>Already attached to the transport stream (s) provided<u style="single">media</u>Identification metadata (and / or other<u style="single">media</u>Illustrative for extracting descriptive information)<u style="single">media</u>Includes metadata extractor 705. For example<u style="single">media</u>The metadata extractor 705 is shown in Figure 6.<u style="single">media</u>Similar to Metadata Extractor 605<u style="single">media</u>Streaming media to presentation device 120<u style="single">A</u>From playlists, electronic program guides, data files, etc. that are already attached to the provided transport stream (s) (for example, already included, added, previously sent, etc.)<u style="single">media</u>Identification metadata can be extracted.
0074[0074] The device meter 510 in FIG. 7 is<u style="single">media</u>Acquired by Metadata Extractor 705<u style="single">media</u>Illustrative for reporting identification metadata to media monitoring agency 515<u style="single">media</u>Also includes the metadata reporter 710. For example<u style="single">media</u>Metadata reporter 710 as a request parameter<u style="single">media</u>A GET or POST request containing identification metadata can be generated. As an alternative<u style="single">media</u>Any other method of transmitting the identification metadata to the media monitoring agency 515 can also be used.<u style="single">media</u>The identification metadata can be transmitted at any interval. For example<u style="single">media</u>Identification metadata can be sent when it is collected (eg, streamed) and in a certain amount<u style="single">media</u>Certain events were detected when the discriminative metadata was collected, when the available memory space was full, or when the threshold capacity was reached (eg, 90% or some other percentage was filled). When (for example, Medi<u style="single">A</u>When the presentation is finished, a new media<u style="single">A</u>Always new (such as when presented)<u style="single">media</u>It can be transmitted when the identification metadata is acquired.<u style="single">media</u>Metadata reporter 710 is a media<u style="single">To a</u>Once with<u style="single">media</u>Identification metadata can be sent, or multiple times (eg, every time an event occurs, every time the identification information changes, etc.)<u style="single">media</u>Identification metadata can be sent.
0075[0075] In some examples, the device meter 510<u style="single">media</u>Extracted by metadata extractor 705<u style="single">media</u>In addition to the identification metadata, metering information can also be determined. For example, the device meter 510 is a Medi<u style="single">A</u>Use of media player to present, media<u style="single">A</u>While being presented<u style="single">media</u>Information can be collected that represents other uses of the presentation device 120, etc., or any combination thereof. In such an example,<u style="single">media</u>The Metadata Reporter 710 uses one or more of the exemplary mechanisms described above.<u style="single">media</u>Extracted by metadata extractor 705<u style="single">media</u>This additional metering information may be reported to the media monitoring agency 515 with or separately from the identification metadata.
0076[0076] A block diagram of an exemplary implementation of the exemplary media monitoring agency 515 of FIG. 5 is shown in FIG. The exemplary media monitoring agency 515 in Figure 8 was reported by the device meter 510.<u style="single">media</u>Illustrative for collecting identification metadata (and other metering information)<u style="single">media</u>Includes metadata collector 805. As explained above, in the example shown<u style="single">media</u>The metadata collector 805 includes an HTTP interface for receiving HTTP requests containing metering information. In addition, or as an alternative, any other method (s) for receiving metering information can also be used.<u style="single">media</u>The metadata collector 805 is described above in connection with FIG. 5 (eg, for example.<u style="single">media</u>It also stores (eg, collects) and analyzes the metering information received (based on the verification results received from the metadata validator 810).
0077[0077] An exemplary media monitoring agency 515 in Figure 8<u style="single">media</u>Received by metadata collector 805<u style="single">media</u>Illustrative for receiving validation results regarding the validity of the identification information<u style="single">media</u>Also includes the metadata validator 810. For example<u style="single">media</u>The metadata validator 810 includes an HTTP interface for receiving HTTP requests containing validation results reported by the server meter 505.<u style="single">media</u>Metadata collector 805<u style="single">media</u>Using the validation results received by the metadata validator 810,<u style="single">media</u>Determine if the identification metadata is valid (eg, correct, accurate, up-to-date, etc.). The exemplary media monitoring agency 515 of FIG. 8 further provides an exemplary report generator 815 for generating reports based on the reported metering information, as described above in connection with FIG. Including.
0078[0078] Streaming Medi<u style="single">A</u>A block diagram of a third exemplary system 900 for monitoring is shown in Figure 9. The third exemplary system 900 includes elements in common with the first exemplary system 100 of FIG. Therefore, similar elements in FIGS. 1 and 9 are given the same reference numbers. A detailed description of these similar elements is provided above in connection with the description of FIG. 1 and is not repeated in the description of FIG. 9 for brevity.
0079[0079] With reference to FIG. 9, the illustrated system 900 is via a compression gear 130, a segmenter and packager 135, a digital rights manager 140, and a network 150.<u style="single">media</u>Streaming media to presentation device 120<u style="single">A</u>To provide<u style="single">media</u>Includes streamer 145 and. Medi to System 900<u style="single">A</u>To provide, the example shown in FIG. 9 includes a content provider (s) 125.<u style="single">media</u>Medi-streamed to presentation device 120<u style="single">A</u>For monitoring, the system 900 of the example shown also includes a third exemplary server meter 905 and a third exemplary media monitoring agency 915. In some examples, the server meter 905 has a compression gear 130, a segmenter and packager 135, a digital rights manager 140, and / or<u style="single">media</u>It can be implemented as a plug-in or other application / device associated with or executed by one or more of the streamers 145. In some examples, the server meter 905 has a compression gear 130, a segmenter and packager 135, a digital rights manager 140, and<u style="single">media</u>It can be carried out by a device different from the streamer 145.
0080[0080] In system 900 in the example shown,<u style="single">media</u>Medi-streamed to presentation device 120<u style="single">A</u>The copy is temporary for later processing<u style="single">media</u>It is stored in the storage device 920. Temporary<u style="single">media</u>The storage device 920 is provided by any memory or one or more storage devices, such as one or more of the mass storage device 3130 and / or the volatile memory 3118, as shown in FIG. 31, which is described in more detail below. Can be carried out. Medi<u style="single">A is</u>, Temporarily in any suitable data format<u style="single">media</u>It can be stored in the storage device 920.
0081[0081] The example server meter 905 shown is temporary.<u style="single">media</u>Medi stored in storage device 920<u style="single">A?</u>Extract metering data from. Metering data is Medi<u style="single">A</u>Identify and Medi<u style="single">A</u>Identify the source and / or separate media<u style="single">A</u>Describe and / or related to it. For example, the server meter 905 is a Medi<u style="single">In a</u>Audio and / or video watermarks embedded in can be extracted. In the example shown, the server meter 905 reports the extracted metering data (and any other metering information) using an HTTP request sent to the HTTP interface of the media monitoring agency 915. An exemplary implementation of the server meter 905 is shown in FIG. 10, which is described in more detail below.
0082[0082] Media monitoring agency 915 includes an interface for receiving reported metering metadata received from server meter 905 over network 150. The media monitoring agency 515 stores, analyzes, and stores, analyzes, based on the reported metering data, using techniques similar to those used by the media monitoring agency 115 to process the reported metering metadata. And can generate reports. An exemplary implementation of Media Monitoring Agency 915 is shown in Figure 11, which is described in more detail below.
0083A block diagram of an exemplary implementation of the exemplary server meter 905 of FIG. 9 is shown in FIG. The exemplary server meter 905 in Figure 10 is<u style="single">media</u>Medi-streamed to presentation device 120<u style="single">A</u>Temporarily copy<u style="single">media</u>Medi for searching from storage 920<u style="single">A inspection</u>Includes cord 1005. Similar to the exemplary server meter 105 in FIG. 2, the exemplary server meter 905 in FIG. 10 is a media.<u style="single">A inspection</u>Medis obtained from the cord device 1005<u style="single">In a</u>Also included is a metering data extractor 210 for extracting metering data, such as one or more audio watermarks, one or more video (eg, image) watermarks embedded in. Further description of the metering data extractor 210 is provided above in connection with the description of FIG. 2 and is not repeated in the description of FIG. 6 for brevity. In some examples, the metering data extractor 210 is replaced by one or more of the elements of FIG. 24 that allow the server meter 905 to operate according to the system described in connection with FIG. 23. , Or they can be included.
0084[0084] The exemplary server meter 905 of FIG. 10 further includes an exemplary metering data reporter 1010 for reporting the metering data acquired by the metering data extractor 210 to the media monitoring agency 915. .. For example, the metering data reporter 1010 can generate a GET or POST request that includes metering data as a parameter of the request. Alternatively, any other method of transmitting metering data to the media monitoring agency 915 can be used. Metering data can be transmitted at arbitrary intervals. For example, metering data can be sent when it is collected (eg, streamed), and when a certain amount of metering data is collected, the available memory space is full. Or when the threshold capacity is reached (eg, 90% or some other percentage is met), when a particular event is detected (eg, Medi)<u style="single">A</u>When the presentation is finished, a new media<u style="single">A</u>It can be sent at any time, such as when presented) or when new metering data is acquired. Metering data reporter 1010 is for each media<u style="single">To a</u>The metering data can be transmitted once, or multiple times (for example, each time an event occurs, each time the identification information changes, etc.).
0085[0085] A block diagram of an exemplary implementation of the exemplary media monitoring agency 915 of FIG. 9 is shown in FIG. The exemplary media monitoring agency 915 of FIG. 9 includes an exemplary metering data collector 1105 for collecting the metering data reported by the server meter 905. As described above, the metering data collector 1105 in the example shown includes an HTTP interface for receiving HTTP requests containing metering information. In addition, or as an alternative, any other method (s) for receiving metering information can also be used. The metering data collector 1105 also stores (eg, collects) and analyzes the received metering information, as described above in connection with FIG. The exemplary media monitoring agency 915 of FIG. 11 also includes an exemplary report generator 1110 for generating reports based on the reported metering information, as described above in connection with FIG. ..
0086[0086] Illustrative methods of implementing the server meters 105, 505, 905, device meters 110, 510, and media monitoring agencies 115, 515, 915 of FIGS. 1, 5, and 9 are shown in FIGS. 2-4. , 6-8, and 10-11, but of the elements, processes, and / or devices shown in 2-4, 6-8, and 10-11. One or more may be combined, split, rearranged, omitted, removed, and / or implemented in any other way. In addition, an exemplary transport stream decoder 205, an exemplary metering data extractor 210, and an exemplary metering data transcoder 215 in FIGS. 2-4, 6-8, and 10-11. , An exemplary metering metadata encoder 220, an exemplary transport stream encoder 225, an exemplary metering metadata extractor 305, an exemplary metering metadata reporter 310, an exemplary meter. Ring metadata collector 405, exemplary report generator 410, exemplary<u style="single">media</u>Metadata extractor 605, exemplary metadata verifier 610, exemplary<u style="single">media</u>Metadata extractor 705, exemplary<u style="single">media</u>Metadata reporter 710, exemplary<u style="single">media</u>Metadata collector 805, exemplary<u style="single">media</u>Metadata Validator 810, Illustrative Report Generator 815, Illustrative Medi<u style="single">A inspection</u>Cable 1005, exemplary metering data reporter 1010, exemplary metering data collector 1105, exemplary report generator 1110, and / or more generally, exemplary server meters 105, 505, And / or one or more of 905, one or more of the exemplary device meters 110, and / or 510, and / or one or more of the exemplary media monitoring agencies 115, 515, and / or 915. , Hardware, software, firmware, and / or any combination of hardware, software, and / or firmware. Thus, for example, an exemplary transport stream decoder 205, an exemplary metering data extractor 210, an exemplary metering data transcoder 215, an exemplary metering metadata encoder 220, an exemplary transformer. Port stream encoder 225, exemplary metering metadata extractor 305, exemplary metering metadata reporter 310, exemplary metering metadata collector 405, exemplary report generator 410, exemplary Nana<u style="single">media</u>Metadata extractor 605, exemplary metadata verifier 610, exemplary<u style="single">media</u>Metadata extractor 705, exemplary<u style="single">media</u>Metadata reporter 710, exemplary<u style="single">media</u>Metadata collector 805, exemplary<u style="single">media</u>Metadata Validator 810, Illustrative Report Generator 815, Illustrative Medi<u style="single">A inspection</u>Cable 1005, exemplary metering data reporter 1010, exemplary metering data collector 1105, exemplary report generator 1110, and / or more generally, exemplary server meters 105, 505, And / or one or more of 905, one or more of the exemplary device meters 110, and / or 510, and / or one or more of the exemplary media monitoring agencies 115, 515, and / or 915. All are one or more circuits (s), programmable processors (s), application specific integrated circuits (ASICs) (ASICs (s)), programmable logic devices (s) (PLD (s)). )), And / or field programmable logic devices (s) (FPLD (s)) and the like. If either the device or system claims of this patent are read to include pure software and / or firmware implementation, the exemplary server meters 105, 505, and / or 905, the exemplary device meter 110, and / Or 510, exemplary media monitoring agencies 115, 515, and / or 915, exemplary transport stream decoder 205, exemplary metering data extractor 210, exemplary metering data transcoder 215, exemplary. Metric metering metadata encoder 220, exemplary transport stream encoder 225, exemplary metering metadata extractor 305, exemplary metering metadata reporter 310, exemplary metering meta Data collector 405, exemplary report generator 410, exemplary<u style="single">media</u>Metadata extractor 605, exemplary metadata verifier 610, exemplary<u style="single">media</u>Metadata extractor 705, exemplary<u style="single">media</u>Metadata reporter 710, exemplary<u style="single">media</u>Metadata collector 805, exemplary<u style="single">media</u>Metadata Validator 810, Illustrative Report Generator 815, Illustrative Medi<u style="single">A inspection</u>At least one of the cord 1005, the exemplary metering data reporter 1010, the exemplary metering data collector 1105, and / or the exemplary report generator 1110 stores such software and / or firmware. The text clearly stipulates that it includes tangible computer-readable media such as memory, digital versatile discs (DVDs), and compact discs (CDs). Furthermore, the exemplary server meters 105, 505, and / or 905 of FIGS. 2-4, 6-8, and 10-11, the exemplary device meters 110 and / or 510, exemplary. Media monitoring agencies 115, 515, and / or 915 add to or replace the elements, processes, and / or devices shown in FIGS. 2-4, 6-8, and 10-11. Can include one or more elements, processes, and / or devices, and / or include any two or more or all of the indicated elements, processes, and devices.
0087[0087] Streaming Medi<u style="single">A</u>A block diagram of a fourth exemplary system 1200 for monitoring is shown in FIG. The fourth exemplary system 1200 contains many elements in common with the first exemplary system 100 of FIG. Therefore, similar elements in FIGS. 1 and 12 are given the same reference numbers. A detailed description of these similar elements is provided above in connection with the description of FIG. 1 and is not repeated in the description of FIG. 12 for brevity.
0088[0088] With reference to FIG. 12, the system 1200 is via the content provider (s) 125 and the network 150.<u style="single">media</u>Streaming media to presentation device 120<u style="single">A</u>Illustrative to provide<u style="single">media</u>Includes distribution network 1215. In the example shown, the content provider (s) 125 is an exemplary television source that may support broadcasting and / or on-demand television sources, for example by any terrestrial, cable, satellite, internet protocol, etc. Including 1205. The content provider (s) 125 in the example shown receives and decodes the television signal provided by television source 1205, thereby, for example, eg.<u style="single">media</u>It also includes an exemplary Integrated Receiver / Decoder (IRD) 1210 for acquiring television transport streams that can be processed by the distribution network 1215. In the exemplary system 1200, any type of IRD1210 can be utilized. In the example shown<u style="single">media</u>The distribution network 1215 includes, for example, the compression gear 130, the segmenter and packager 135, the digital rights manager 140, and the digital rights manager 140 described above.<u style="single">media</u>Streamer 145 can be included.
0089[0089]<u style="single"> media</u>Medi-streamed to presentation device 120<u style="single">A</u>To enable monitoring, the system 1200 of the example shown is an exemplary metadata inserter 1220 and one or more exemplary, in addition to the device meter 110 and media monitoring agency 115 described above. Also includes transcoders 1225 and / or 1230. The metadata inserter 1220 can be implemented, for example, as a separate device, or as a plug-in or other application / device associated with or executed by the IRD210. The transcoders 1225 and / or 1230, respectively, as separate devices or (eg, compression gear 130, segmenter and packager 135, digital rights manager 140, and / or<u style="single">media</u>(One or more of Streamer 145, etc.)<u style="single">media</u>It can be implemented as a plug-in or other application / device associated with or executed by one or more elements of the distribution network 1215. In some examples, the metadata inserter 1220 and one or more of the transcoders 1225 and / or 1230 can be integrated into a single device or plug-in, while in other examples the metadata. The inserter 1220 is separated from the transcoders 1225, 1230.
0090[0090] In the example shown, the metadata inserter 1220 is coupled to an interface of the IRD1210 (eg, such as a serial digital interface (SDI) or Internet Protocol (IP) interface) and is a television transformer provided by the IRD1210. Decrypt the port stream. The metadata inserter 1220 then extracts the audio watermark (s) from the audio portion (s) of the television transport stream, decodes the audio watermark (s), and metering in the example shown. Acquires audio watermark payload data that provides information. In addition, or as an alternative, in some examples, the metadata inserter 1220 extracts a video (eg, image) watermark (s) from the video portion (s) of the television transport stream and extracts the video (s). For example, the image) watermark (s) are decoded to obtain the video watermark payload data corresponding to the metering information. In addition, or as an alternative, in some examples, the metadata inserter 1220 has metering data from an independent metering data source, such as the independent metering data source described in connection with FIGS. 23 and 24. Can be earned. The metadata inserter 1220 then inserts the watermark payload data corresponding to the metering information into one or more existing parts of the television transport stream capable of carrying the metadata. For example, the metadata inserter 1220 provides watermark payload data corresponding to metering information (and / or metering data obtained from an independent source) to the American National Standards Institute (SCTE) of the Society of Cable Telecommunications Engineers (SCTE). Vertical return elimination section (VBI:) conforming to the standard ANSI / SCTE127 It can be inserted as vertical blanking interval) data, or as one or more Advanced Television Systems Committee (ATSC) private information descriptors for transport streams. In some examples, the operation of the metadata inserter 1220 causes, or does not result in, slight changes in the program clock reference and / or audio / video timing of the television transport stream.
0091[0091] In the example shown, system 1200 comprises one or more of transcoders 1225 or transcoders 1230. The transcoders 1225 and 1230, respectively, acquire the metering metadata inserted into the television transport stream by the metadata inserter 1220 and use this metadata.<u style="single">media</u>It can be converted to a format suitable for streaming by the distribution network 1215. After that, the transcoders 1225 and 1230 each stream this format-converted metadata so that it can carry the metadata.<u style="single">media</u>It can be inserted into a part (s) of a transport stream (s). For example, transcoder 1225/1230 decodes metering metadata inserted as VBI payload data or ATSC private information descriptors (s) and mediates this metering metadata according to HLS or other suitable streaming protocol.<u style="single">A</u>It can be converted to ID3 tag metadata for insertion into the transport stream (s) to be streamed. In some examples, the transcoder 1225/1230 is a Medi<u style="single">A</u>Encrypt transcoded metering metadata (for example, to protect privacy) before inserting it into the transport stream (s) to be streamed. Such encryption is provided by metering metadata,<u style="single">media</u>It is possible to prevent the presentation device 120 from becoming observable by an application other than the device meter 110. In addition, or as an alternative, if the device meter 110 is not prepared (eg, enabled) by the media monitoring agency 115, then using such encryption, the device meter 110 will be metered. It is possible to prevent the ring metadata from being extracted and / or decrypted.
0092[0092] In the example shown, the differences between transcoder 1225 and transcoder 1230 relate to location and integration into system 1200. For example, the transcoder 1225 has its transcoding capabilities.<u style="single">media</u>It can be performed at the input to the distribution network 1215 and thus can be implemented as a device separate from the CDN 1215 and / or integrated with or separate from the metadata inserter 1220. In contrast, the transcoder 1230 processes the transport stream (s) within the CDN1215 (eg, like the server meter 105) and is therefore associated with one or more of the elements contained in the CDN1215. Or it can be implemented as a plug-in or other application / device executed by them.
0093[0093] A potential advantage of the exemplary system 1200 is the metadata inserter 1220 and transcoder, using interfaces specified by established industry standards (eg, enacted SCTE or ATSC standards). It is possible for different vendors to offer 1225/1230.
0094An exemplary method of implementing the system 1200 has been described in FIG. 12, but one or more of the elements, processes, and / or devices shown in FIG. 12 may be combined, divided, and combined. It can be rearranged, omitted, removed, and / or implemented in any other way. In addition, the exemplary television source 1205, exemplary IRD1210, exemplary in Figure 12.<u style="single">media</u>The delivery network 1215, the exemplary metadata inserter 1220, the exemplary transcoders 1225 and / or 1230, and / or more generally, the exemplary system 1200 of FIG. 12 are hardware, software, firmware, And / or any combination of hardware, software, and / or firmware. So, for example, an exemplary television source 1205, an exemplary IRD1210, an exemplary.<u style="single">media</u>Distribution network 1215, exemplary metadata inserter 1220, exemplary transcoders 1225 and / or 1230, and / or, more generally, exemplary system 1200, any one or more circuits. It can be implemented by (possible), programmable processor (s), ASIC (s), PLD (s), and / or FPLD (s). If any of the device or system claims of this patent are read to include pure software and / or firmware implementation, an exemplary system 1200, an exemplary television source 1205, an exemplary IRD1210, an exemplary IRD1210.<u style="single">media</u>At least one of the distribution network 1215, the exemplary metadata inserter 1220, and / or the exemplary transcoders 1225 and / or 1230 stores such software and / or firmware, memory, DVDs, CDs, etc. The inclusion of tangible computer-readable media is explicitly stated in the text. Furthermore, the exemplary system 1200 of FIG. 12 includes one or more elements, processes, and / or devices in addition to or in place of the elements, processes, and / or devices shown in FIG. It can and / or include any two or more of the indicated elements, processes, and devices.
0095[0095] FIGS. 13-22, 25, 29, and / or 30 show exemplary systems 100, 500, 900, 1200, 2300, and / or 2800, exemplary server meters 105, 505. , And / or 905, exemplary device meters 110 and / or 510, exemplary media monitoring agencies 115, 515, 915, and / or 2815, exemplary transport stream decoder 205, metering data extractor. 210, exemplary metering data transcoder 215, exemplary metering metadata encoder 220, exemplary transport stream encoder 225, exemplary metering metadata extractor 305, exemplary meter Ring metadata reporter 310, exemplary metering metadata collector 405, exemplary report generator 410, exemplary<u style="single">media</u>Metadata extractor 605, exemplary metadata verifier 610, exemplary<u style="single">media</u>Metadata extractor 705, exemplary<u style="single">media</u>Metadata reporter 710, exemplary<u style="single">media</u>Metadata collector 805, exemplary<u style="single">media</u>Metadata Validator 810, Illustrative Report Generator 815, Illustrative Medi<u style="single">A inspection</u>Cable 1005, exemplary metering data reporter 1010, exemplary metering data collector 1105, exemplary report generator 1110, exemplary metadata inserter 1220, exemplary transcoder 1225 and / or 1230, exemplary independent metering data source 2320, exemplary combiner 2330, exemplary clock 2410, exemplary data source (s) 2420, and / or secondary<u style="single">media</u>A flowchart showing an exemplary machine-readable instruction that can be executed to implement the presenter 2825 is shown. In these examples, the machine-readable instructions represented by each flowchart are one for execution by a processor, such as the processor 3112 shown in the exemplary processing system 3100 described below in connection with FIG. Alternatively, it can include a plurality of programs. Alternatively, the entire program and / or parts thereof that implement one or more of the processes represented by the flowcharts of FIGS. 13-22, 25, 29, and / or 30. Can be run by devices other than processor 3112 (eg, controllers and / or any other suitable device), and / or by firmware, or (eg, ASIC, PLD, FPD, individual logic, etc.) It can be embodied in dedicated hardware (implemented). In addition, one or more machine-readable instructions represented by the flowcharts of FIGS. 13 to 22, 25, 29, and / or 30 can also be manually executed. Further, exemplary machine-readable instructions are described with reference to the flowcharts shown in FIGS. 13-22, 25, 29, and / or 30, but as an alternative, they are described herein. Many other techniques for carrying out exemplary methods and devices can be used. For example, referring to the flowcharts shown in FIGS. 13-22, 25, 29, and / or 30, the order of execution of blocks can be changed and / or some of the blocks described. Can be modified, removed, combined, and / or divided into multiple blocks.
0096[0096] As mentioned above, the exemplary process of FIGS. 13-22, 25, 29, and / or 30 can be carried out over any period of time (eg, over a long period of time, permanently, for a short period of time). Hard disk drive, flash memory, read-only memory (ROM), CD, DVD, cache, random, where information is stored (only during temporary buffering and / or while caching information) It can be performed using encoded instructions (eg, computer-readable instructions) stored on tangible computer-readable media, such as access memory (RAM) and / or any other storage medium. .. As used herein, the term tangible computer-readable medium is expressly defined as including any type of computer-readable memory and excluding propagating signals. In addition, or as an alternative, the exemplary process of FIGS. 13-22, 25, 29, and / or 30 is temporary for any period of time (eg, for a long period of time, permanently, for a short period of time). Flash memory, ROM, CD, DVD, cache, RAM, and / or any other storage medium in which information is stored (while buffering and / or caching information), etc. It can be performed using coded instructions (eg, computer-readable instructions) stored on a non-temporary computer-readable medium. As used herein, the term non-transitory computer-readable medium is expressly defined as including any type of computer-readable memory and excluding propagating signals. Also, as used herein, the terms "computer readable" and "machine readable" are considered equivalent unless otherwise noted. In addition, as used herein, "at least (at) When the phrase "least" is used as a transition word in a claim preamble, it is as non-limiting as the term "comprising" is open-ended. Therefore, a claim that uses "at least" as a transition word in the preamble can include elements in addition to the elements explicitly listed in the claim.
0097An exemplary machine-readable instruction 1300 that can be executed to implement the first exemplary server meter 105 of FIGS. 1-2 is shown in FIG. Also referring to the preceding figure, the exemplary machine-readable instruction 1300 of FIG. 13 begins execution at block 1305, and the server meter 105<u style="single">media</u>Medi-streamed to presentation device 120<u style="single">A</u>Receives the transport stream to carry. At block 1310, the transport stream decoder 205 of the server meter 105 decodes the transport stream and<u style="single">media</u>Medi-streamed (eg, uncompressed) to presentation device 120<u style="single">A</u>Acquire. At block 1315, the metering data extractor 210 of the server meter 105 has the decoded (eg, uncompressed) media acquired at block 1310.<u style="single">A?</u>To extract metering data having a first format (eg, one or more embedded audio / video watermarks). At block 1320, the metering data transcoder 215 of the server meter 105 transcodes the metering data of the first format acquired at block 1315 and can be decoded by the device meter 110 in a second format (eg, for example. Form metering metadata with text, binary, or other data format). At block 1325, the transport stream encoder 225 of the server meter 105 contains the metering metadata in the metadata channel associated with the transport stream.<u style="single">A</u>Recode the transport stream to carry. At block 1330, the server meter 105 connects the recoded transport stream (and the metadata channel that carries the transcoded metering metadata).<u style="single">media</u>Send to any other downstream processing element for streaming to the presentation device 120. Execution of the exemplary machine-readable instruction 1300 is then terminated.
0098[0098] In some examples, block 1315 is modified to utilize metering data from an independent metering data source and / or as described below in connection with FIG. 25. Can be replaced with one or more blocks.
0099An exemplary machine-readable instruction 1400 that can be executed to implement the first exemplary device meter 110 of FIGS. 1 and 3 is shown in FIG. Also referring to the preceding figure, the exemplary machine-readable instruction 1400 of FIG. 14 begins executing at block 1405, and the metering metadata extractor 305 of the device meter 110<u style="single">media</u>Streaming media to presentation device 120<u style="single">A</u>Metering metadata contained within the metadata channel associated with the provided transport stream (eg, metadata derived from the metering data contained within the audio / video watermark, obtained from an independent metering data source. Detect metadata derived from metering data, etc.). At block 1410, metering metadata extractor 305 stores metering metadata for later reporting. At block 1415, the metering metadata reporter 310 of the device meter 110 reports the metering metadata to the media monitoring agency 115. Execution of the exemplary machine-readable instruction 1400 is then terminated.
0100[0100] An exemplary machine-readable instruction 1500 that can be executed to carry out the first exemplary media monitoring agency 115 of FIGS. 1 and 4 is shown in FIG. Also referring to the preceding figure, the exemplary machine-readable instruction 1500 of FIG. 15 started executing at block 1505, and the metering metadata collector 405 of the media monitoring agency 115 was reported by the device meter 110. Metering metadata (eg, metadata derived from metering data contained within audio / video watermarks, metadata derived from metering data obtained from an independent metering data source, etc.), and others. Collect metering information. At block 1510, the report generator 410 of the media monitoring agency 115 generates one or more reports based on the reported metering information. Execution of the exemplary machine-readable instruction 1500 is then terminated.
0101An exemplary machine-readable instruction 1600 that can be executed to implement the second exemplary server meter 505 of FIGS. 5-6 is shown in FIG. Also referring to the preceding figure, the exemplary machine-readable instruction 1600 of FIG. 16 begins execution at block 1605, and the server meter 505<u style="single">media</u>Medi-streamed to presentation device 120<u style="single">A</u>Receives the transport stream to carry. At block 1610, the transport stream decoder 205 of the server meter 505 decodes the transport stream and<u style="single">media</u>Medi-streamed (eg, uncompressed) to presentation device 120<u style="single">A</u>Acquire. At block 1615, the metering data extractor 210 of the server meter 505 is the decoded (eg, uncompressed) media acquired at block 1610.<u style="single">A?</u>To extract metering data (eg, one or more embedded audio / video watermarks). In block 1620<u style="single">media</u>Metadata Extractor 605 is a streaming media<u style="single">A</u>Already attached to the transport stream being transported (playlist data, electronic program guide data, etc.)<u style="single">media</u>Extract identification metadata. At block 1625, the metadata verifier 610 of server meter 505 extracted the metering data extracted at block 1615 and the metering data extracted at block 1620.<u style="single">media</u>Compare the identification metadata,<u style="single">media</u>Validate the identification metadata. At block 1630, the metadata verifier 610 reports the verification results to the media monitoring agency 515. Execution of the exemplary machine-readable instruction 1600 is then terminated.
0102[0102] In some examples, block 1615 is modified to utilize metering data from an independent metering data source and / or as described below in connection with FIG. 25. Can be replaced with one or more blocks.
0103An exemplary machine-readable instruction 1700 that can be executed to implement the second exemplary device meter 510 of FIGS. 5 and 7 is shown in FIG. Also referring to the preceding figure, the exemplary machine-readable instruction 1700 of FIG. 17 begins execution at block 1705 of the device meter 510.<u style="single">media</u>Metadata extractor 705<u style="single">media</u>Streaming media to presentation device 120<u style="single">A</u>Already attached to the provided transport stream (playlist data, electronic program guide data, etc.)<u style="single">media</u>Extract identification metadata. In block 1710<u style="single">media</u>Metadata extractor 705, for later reporting,<u style="single">media</u>Store identification metadata. In block 1715, on the device meter 510<u style="single">media</u>The metadata reporter 710 reports the metering metadata to the media monitoring agency 515. Execution of the exemplary machine-readable instruction 1700 is then terminated.
0104An exemplary machine-readable instruction 1800 that can be executed to implement the second exemplary media monitoring agency 515 of FIGS. 5 and 8 is shown in FIG. Also referring to the preceding figure, the exemplary machine-readable instruction 1800 of FIG. 18 begins execution at block 1805 and of the media monitoring agency 515.<u style="single">media</u>Metadata collector 805 was reported by device meter 510,<u style="single">media</u>Distinguished metadata (eg, metadata that accompanies the transport stream, metadata that is derived from the metering data contained within the audio / video watermark, and metering data that is obtained from an independent metering data source. Collect metadata etc.) and / or other metering information. In block 1810, media monitoring agency 515<u style="single">media</u>Metadata validation device 810 received in block 1805<u style="single">media</u>Receive the verification result regarding the validity of the identification information. In block 1815<u style="single">media</u>Metadata collector 805 was collected<u style="single">media</u>Validate the identification metadata using the validation results received in block 1810. In addition, at block 1815, the report generator 815 of the media monitoring agency 515 generates one or more reports based on the reported metering information. Execution of the exemplary machine-readable instruction 1800 is then terminated.
0105An exemplary machine-readable instruction 1900 that can be executed to implement the third exemplary server meter 905 of FIGS. 9-10 is shown in FIG. Also referring to the preceding figure, the exemplary machine-readable instruction 1900 of FIG. 19 begins execution at block 1905 and mediates the server meter 905.<u style="single">A inspection</u>The cord device 1005 is<u style="single">media</u>Medi-streamed to presentation device 120<u style="single">A</u>Copy, temporarily<u style="single">media</u>Search from storage device 920. In block 1910, Medi<u style="single">A inspection</u>The probe 1005, where appropriate, was found in block 1905.<u style="single">A</u>Decrypt (eg, unzip, combine, unpack, etc.). At block 1915, the metering data extractor 210 of the server meter 905 acquired (eg, uncompressed) media at block 1910.<u style="single">A?</u>To extract metering data (eg, one or more embedded audio / video watermarks). At block 1920, the metering data reporter 1010 on the server meter 905 reports the metering data acquired at block 1915 to the media monitoring agency 915. Execution of the exemplary machine-readable instruction 1900 is then terminated.
0106[0106] In some examples, block 1915 is modified to utilize metering data from an independent metering data source and / or as described below in connection with FIG. 25. Can be replaced with one or more blocks.
0107An exemplary machine-readable instruction 2000 that can be executed to implement the third exemplary media monitoring agency 915 of FIGS. 9 and 11 is shown in FIG. Also referring to the preceding figure, the exemplary machine-readable instruction 2000 of FIG. 20 began executing at block 2005, and the metering data collector 1105 of the media monitoring agency 915 was reported by the server meter 905, the meter. Derived from ring data (for example, metadata already associated with the transport stream, metadata derived from metering data contained within audio / video watermarks, metering data obtained from an independent metering data source) Collect metadata, etc.). In block 2010, media monitoring agency 915 report generator 1110 generates one or more reports based on the reported metering information. Execution of the exemplary machine-readable instruction 2000 is then terminated.
0108An exemplary machine-readable instruction 2100 that can be executed to implement the exemplary metadata inserter 1220 of FIG. 12 is shown in FIG. Also referring to the preceding figure, the exemplary machine-readable instruction 2100 of FIG. 21 begins execution at block 2105 and the metadata inserter 1220 is a decoded media.<u style="single">Ashin</u>Obtain the issue (eg, the decrypted television transport stream) from the IRD1210. In block 2110, the metadata inserter 1220 is a Medi<u style="single">Ashin</u>(No.) to extract the watermark (s) (for example, audio and / or video watermark (s)). At block 2115, the metadata inserter 1220 decodes the watermark (s) to acquire the watermark payload data and thus the metering information provided by the watermark payload data. At block 2120, the metadata inserter 1220 is capable of carrying metadata.<u style="single">Ashin</u>Insert watermark payload data in the existing part of the issue. For example, in block 2120, the metadata inserter 1220 can insert watermark payload data as a VBI compliant with the SCTE127 standard, or as one or more ATSC private information descriptors for television transport streams. Execution of the exemplary machine-readable instruction 2100 is then terminated.
0109[0109] In some examples, block 2115 can be modified to utilize metering data from an independent metering data source and / or replaced with one or more blocks. Such an example is described in connection with FIG.
0110An exemplary machine-readable instruction 2200 that can be executed to implement the exemplary transcoder 1225 and / or 1230 of FIG. 12 is shown in FIG. For convenience, without loss of generality, the machine-readable instruction 2200 is described in terms of execution by the transcoder 1225. Also referring to the preceding figure, the exemplary machine-readable instruction 2200 of FIG. 22 begins execution at block 2205, and the transcoder 1225 is medied by the metadata inserter 1220.<u style="single">Ashin</u>Extract the payload data inserted in the metadata transport part (s) of the issue. For example, in block 2205, the transcoder 1225 can extract payload data as VBI data, one or more ATSC private information descriptors, and so on. At block 2210, transcoder 1225 transcodes the payload metadata corresponding to the metering information acquired at block 2205 into a format suitable for media streaming. For example, at block 2210, transcoder 1225 can transcode payload metadata to ID3 tag metadata. At block 2215, transcoder 1225 is capable of carrying metadata Streaming<u style="single">media</u>Insert transcoded metadata into a part (s) of a transport stream (s). For example, in block 2215, the transcoder 1225 mediates the ID3 tag metadata corresponding to the metering metadata according to HLS or other suitable streaming protocol.<u style="single">A</u>It can be inserted in the appropriate part of the transport stream (s) to be streamed. Execution of the exemplary machine-readable instruction 2200 is then terminated.
0111[0111] Figure 23 shows the streaming media.<u style="single">To a</u>It is a block diagram of an exemplary system 2300 that acquires metering data about it. An exemplary system 2300 includes a dependent metering data source 2310, an independent metering data source 2320, and a combiner 2330 for generating output metering data 2340.
0112[0112] The dependent metering data source 2310 in the example shown is Medi<u style="single">A</u>Receive, Medi<u style="single">A?</u>Extract metering data from. In other words, the metering data collected by the dependent metering data source 2310 is Medi<u style="single">A self</u>Provided by the body, Medi<u style="single">A self</u>Body related or Medi<u style="single">A self</u>It depends on the body. For example, the dependent metering data source 2310 is Medi<u style="single">In a</u>Extracting metering data from audio and / or video watermarks contained in<u style="single">A?</u>It is possible to acquire metering data from the signatures generated from the above.
0113[0113] An exemplary independent metering data source 2320 is a Medi<u style="single">A</u>Obtain metering data from a source independent of the content. For example, an independent metering data source 2320 can acquire a time stamp from a clock, acquire identification information provided by user input, acquire identification information stored in a file, and so on. In some examples, the metering data obtained by the independent metering data source 2320 is the data extracted from the dependent metering data source 2310, and<u style="single">media</u>And / or the data types may be duplicated, similar, or identical. For example, metering data from a dependent metering data source 2310 and metering data from an independent metering data source 2320 may contain the same source identifier.
0114[0114] The combiner 2330 in the example shown receives the first metering data from the dependent metering data source 2310 and the second metering data from the independent metering data source 2320, and the first and second metering data. The metering data of the above are combined to generate the combined metering data 2340. In some examples, the combined metering data 2340 contains duplicate or partially duplicated information, as described in connection with FIG. 26. In some examples, the metering data extracted by the dependent metering data source 2310 is not available and therefore by the independent metering data source 2320, as described in connection with FIG. 27. Only the metering data provided is included in the combined metering data 2340.
0115[0115] A block diagram of an exemplary server meter 2405 implemented according to system 2300 in FIG. 23 is shown in FIG. The server meter 2405 in FIG. 24 includes the dependent metering data source 2310, the independent metering data source 2320, the clock 2410, the data source (s) 2420, and the combiner 2330, as described in detail above. , Includes metering data transcoder 215, metering metadata encoder 220, and transport stream encoder 225. The server meter 2405 in the example shown can be used to implement any of the server meters 105, 505, and / or 905 described above.
0116The exemplary dependent metering data source 2310 of FIG. 24 is performed by the transport stream decoder 205 and metering data extractor 210 described in connection with FIG. The metering data extractor 210 of the exemplary subordinate metering data source 2310 is a media obtained from the transport stream decoder 205.<u style="single">A?</u>Then, the metering data having the first format is extracted. In addition, or as an alternative, the dependent metering data source 2310 may otherwise mediate.<u style="single">A</u>It can be done by any other component to obtain content-dependent metering data.
0117[0117] Independent metering data source 2320 in the example shown obtains metering data from clock 2410 and data source (s) 2420. In addition, or as an alternative, the independent metering data source 2320 is Medi<u style="single">A and</u>And / or Medi<u style="single">A</u>Metering data can be obtained from any other internal or external source of metering data that is independent (eg, separated) from the transport stream (s) provided.
0118[0118] The clock 2410 in the example shown is the internal system clock of the server meter 2405 that provides one or more time stamps to the independent metering data source 2320 when requested. Alternatively, the clock 2410 can be any type of internal clock, external clock, and so on. For example, the clock 2410 can be a clock at the content provider and / or the clock 2410 can be an internal clock synchronized with the content provider's clock.
0119[0119] The example data source (s) 2420 shown provides metering data to an independent metering data source 2320. Data source (s) 2420 is Medi<u style="single">With a</u>Is independent (eg Medi<u style="single">A</u>Provides metering data (not extracted from the content). According to the example shown, the data source (s) 2420 is a streaming media<u style="single">A</u>Contains a configuration file that stores information that identifies the source (eg, content provider). The configuration file is generated during the setup of Server Meter 2405. In addition, or as an alternative, the data source (s) 2420 may include locally stored data, externally stored data, data available over a network connection, or data entered by the user of Server Meter 2405. Any one or more such as may be included.
0120[0120] In some examples, the independent metering data source 2320 inserts a tag or other form of identification into the acquired metering data so that the metering data is by the independent metering data source 2420. Inform that it was collected. For example, the independent metering data source 2320 in Figure 24 identifies the collected metering data as "non-voice" and the metering data is streamed media.<u style="single">A</u>Notify that it is not extracted from voice. In addition, or as an alternative, one or more other tags or identification information may be added.
0121[0121] The combiner 2330 in the example shown combines the metering data from the dependent metering data source 2310 with the metering data from the independent data provider 2320. For example, combiner 2330 concatenates the metering data extracted by the dependent metering data source 2310 with the metering data acquired by the independent metering data source 2320 to generate a single data string. The combiner may use a delimiter (eg, "|") or any other optional delimiter between the metering data extracted by the dependent metering data source 2310 and the metering data acquired by the independent metering data source 2320. Insert the letter or indicator. In addition, or as an alternative, combiner 2330 can combine metering data in any other way.
0122[0122] To transcode the combined metering data obtained from the dependent metering data source 2310 and the independent metering data source 2320 from the first format to a second format that can be decoded by the device meter. The exemplary server meter 2405 of FIG. 24 further includes a metering data transcoder 215. In addition, or as an alternative, the server meter 2405 in FIG. 24 utilizes any suitable encryption to encrypt the transcoded metering metadata determined by the metering data transcoder 215. Includes ring metadata encryptor 220. In the example shown in FIG. 24, the server meter 2405 is a transcoded metering determined by the metering data transcoder 215 (encrypted by the metering metadata encoder 220, where appropriate). Streaming media to include metadata<u style="single">A</u>Includes a transport stream encoder 225 for recoding the transport stream (s) to be carried. An example of the resulting metering data output by the server meter 2405, detailed in FIG. 24, is disclosed in connection with FIGS. 26 and 27.
0123An exemplary method of implementing system 2300 has been described in connection with FIGS. 23 and 24, but one or more of the elements, processes, and / or devices shown in FIGS. 23 and 24. Can be combined, split, rearranged, omitted, removed, and / or implemented in any other way. In addition, the dependent metering data source 2310 in FIG. 23, the independent metering data source 2320, and the combiner 2330, and the server meter 2405, transport stream decoder 205, metering data extractor 210, independent meter in FIG. 24. One or more of the Ring Data Extractor 2320, Combiner 2330, Clock 2410, Data Source 2420, Metering Data Transcoder 215, Metering Data Encoder 220, and Transport Stream Encoder 225, hardware, software , And / or any combination of hardware, software, and / or firmware. Thus, for example, the dependent metering data source 2310 in FIG. 23, the independent metering data source 2320, and the combiner 2330, and the server meter 2405, transport stream decoder 205, metering data extractor 210 in FIG. 24, independent. Metering Data Extractor 2320, Combiner 2330, Clock 2410, Data Source 2420, Metering Data Transcoder 215, Metering Data Encoder 220, and Transport Stream Encoder 225, One or More Or multiple circuits (s), programmable processors (s), application-specific integrated circuits (s) (ASICs (s)), programmable logic devices (s) (PLD (s)), and / Alternatively, it can be implemented by a field programmable logical device (s) (FPLD (s)) or the like. Device or system claims of this patent If any of the above is read to include pure software and / or firmware implementation, then the dependent metering data source 2310 in Figure 23, the independent metering data source 2320, and the combiner 2330, and the server meter 2405 in Figure 24. , Transport Stream Decoder 205, Metering Data Extractor 210, Independent Metering Data Extractor 2320, Combiner 2330, Clock 2410, Data Source 2420, Metering Data Transcoder 215, Metering Data Encryptor 220, and At least one of the transport stream encoders 225 includes tangible computer readable media such as memory, digital versatile discs (DVDs), compact discs (CDs) that store such software and / or firmware. That is clearly defined by the text. Furthermore, the system 2300 of FIG. 23 and the server meter 105 of FIG. 24 are in addition to or in place of the elements, processes, and / or devices shown in FIGS. 23 and 24, one or more elements, processes. , And / or devices, and / or any two or more or all of the indicated elements, processes, and devices. The text clearly stipulates that it includes tangible computer-readable media such as D) and compact discs (CDs). Furthermore, the system 2300 of FIG. 23 and the server meter 105 of FIG. 24 are in addition to or in place of the elements, processes, and / or devices shown in FIGS. 23 and 24, one or more elements, processes. , And / or devices, and / or any two or more or all of the indicated elements, processes, and devices. The text clearly stipulates that it includes tangible computer-readable media such as D) and compact discs (CDs). Furthermore, the system 2300 of FIG. 23 and the server meter 105 of FIG. 24 are in addition to or in place of the elements, processes, and / or devices shown in FIGS. 23 and 24, one or more elements, processes. , And / or devices, and / or any two or more or all of the indicated elements, processes, and devices.
0124An exemplary machine-readable instruction 2500 that can be executed to implement the exemplary server meter 2405 of FIG. 24 is shown in FIG. 25. Also with reference to FIGS. 23 and 24, the exemplary machine-readable instruction 2500 of FIG. 25 begins execution at block 2505, and the server meter 2405<u style="single">media</u>Medi-streamed to presentation device 120<u style="single">A</u>Receives the transport stream to carry (block 2505). The transport stream decoder 205 of the dependent metering data source 2310 decodes the transport stream and<u style="single">media</u>Medi-streamed to presentation device 120<u style="single">A</u>Acquire (block 2510). The metering data extractor 210 of the dependent metering data source 2310 has the decoded (eg, uncompressed) media acquired in block 2510.<u style="single">A?</u>To extract metering data having a first format (eg, one or more embedded audio / video watermarks) (block 2515). Independent metering data source 2320 is Medi<u style="single">A</u>Collect metering data that can have a first form or a second form from a content-independent source (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).
0125[0125] The metering data transcoder 215 of the server meter 2405 transcodes the first and / or second form (s) of metering data acquired in blocks 2515 and 2520 and combined in block 2525. Code to form transcoded metering metadata with a third format (eg, text, binary, or other data format) that can be decoded by the device meter 110 (block 2530). The transport stream encoder 225 of the server meter 105 contains streaming media to include transcoded metering metadata within the metadata channel associated with the transport stream.<u style="single">A</u>Recode the transport stream to carry (block 2535). The server meter 2405 delivers a recoded transport stream (and a metadata channel that carries transcoded metering metadata).<u style="single">media</u>Send to any other downstream processing element for streaming to presentation device 120 (block 2540). Execution of the exemplary machine-readable instruction 2500 is then terminated.
0126[0126] FIG. 26 is an exemplary meta derived from the combined metering data 2340 after being extracted, acquired, combined, and transcoded by the server meter 2405, as detailed in FIG. 24. Data 2600 is shown. Metadata 2600 is medied by metering data extractor 210<u style="single">A?</u>Contains block 2610, which is part of the metadata 2600 extracted from. Timestamp 2612 is medied by metering data extractor 210<u style="single">A?</u>It is the time stamp data extracted from. Source identification 2614 is medied by metering data extractor 210<u style="single">A?</u>It is the source identification data extracted from the above. Metadata 2600 includes block 2620, which is part of metadata 2600 collected by an independent metering data source 2320. Timestamp 2622 is the time stamp data obtained from clock 2410 by an independent metering data source 2320. Source identification 2624 is source identification data obtained from the data source (s) 2420 by an independent metering data source 2320. Tag 2626 is a tag on metadata 2620 that identifies metadata 2620 as being acquired by an independent metering data source 2320. The metadata 2340 illustrated in FIG. 26 is an example in which the metadata 2610 is readable and the metadata 2620 serves as duplicate or similar metadata.
0127[0127] FIG. 27 provides exemplary metadata 2700 derived from metering data 2340 after being extracted, acquired, combined, and transcoded by the server meter 105, as detailed in FIG. 25. Shown. Metadata 2700 is a block 2720 that is part of the metadata 2700 that is unreadable or separately unavailable and is associated with an independent metering data source. It provides an example that serves as a source of metadata backup that can be used to replace unreadable or separately unavailable metadata. Block 2710 is part of the metadata 2700 extracted from the metering data extractor 210. Block 2720 is part of the metadata 2700 acquired by an independent metering data source 2320. Timestamp 2722 is the time stamp data obtained from clock 2410 by an independent metering data source 2320. Source identification 2724 is source identification data obtained from the data source (s) 2420 by an independent metering data source 2320. Tag 2726 is a tag on metadata 2720 that identifies metadata 2720 as being acquired by an independent metering data source 2320.
0128[0128] Streaming Medi<u style="single">A</u>A block diagram of a fifth exemplary system 2800 for monitoring is shown in Figure 28. The fifth exemplary system 2800 contains many elements in common with the first exemplary system 100 of FIG. Therefore, similar elements in FIGS. 1 and 28 are given the same reference numbers. A detailed description of these similar elements is provided above in connection with the description of FIG. 1 and is not repeated in the description of FIG. 28 for brevity.
0129[0129] With reference to FIG. 28, the illustrated system 2800 is a second via compression gear 130, segmenter and packager 135, digital rights manager 140, and network 150.<u style="single">media</u>Streaming media to presentation device 2820<u style="single">A</u>To provide<u style="single">media</u>Includes streamer 145 and. Medi to system 2800<u style="single">A</u>To provide, the example shown in FIG. 28 includes a content provider (s) 125.<u style="single">media</u>Medistreamed to presentation device 2820<u style="single">A</u>Monitor and optionally secondary based on media monitoring results<u style="single">media</u>To provide, the example system 2800 shown is a server meter 105, a device meter 110, a fourth exemplary media monitoring agency 2815, and an exemplary secondary.<u style="single">media</u>Also includes presenter 2825.
0130[0130] The media monitoring agency 2815 includes an interface for receiving reported metering information (eg, metering metadata) received from the device meter 110 over network 150. In the example shown, the media monitoring agency 2815 includes an HTTP interface for receiving HTTP requests containing metering information. In addition, or as an alternative, any other method (s) for receiving metering information may be used. In the example shown, the media monitoring agency 2815 receives metering information from the device meter 110 and uses the received metering information to secondary.<u style="single">media</u>Select and select secondary<u style="single">media</u>Secondary<u style="single">media</u>Send to presenter 2825. In some cases, the media monitoring agency is internal<u style="single">media</u>From the database, secondary<u style="single">media</u>Can be selected. In some examples, the media monitoring agency 2815 is secondary from one or more external databases (s) and / or third-party databases (s).<u style="single">media</u>Can be selected. In such an example, the media monitoring agency 2815 accesses the external and / or third-party database (s) over a network (eg, the Internet, local area network (LAN), wide area network (WAN), etc.). can do. Secondary media related to primary metering data available by media monitoring agency 2815<u style="single">A</u>Other additional or alternative examples provided are, for example, filed April 30, 2010, which is incorporated herein by reference in its entirety, U.S. Patent Application Publication No. 2010/0280641 (Harkness). In addition, it is explained in "METHODS, APPARATUS AND ARTICLES OF MANUFACTURE TO PROVIDE SECONDARY CONTENT IN ASSOCIATION WITH PRIMARY BROADCAST MEDIA CONTENT").
0131[0131] In the example shown<u style="single">media</u>Presentation device 2820 over network 150<u style="single">media</u>Streaming media provided by Streamer 145<u style="single">A</u>It is a computing device that can be presented.<u style="single">media</u>Presentation device 2820 includes, for example, desktop computers, laptop computers, mobile computing devices, televisions, smartphones, mobile phones, Apple® iPad®, Apple® iPhone®, Apple. It can be a (registered trademark) iPod (registered trademark), a computing device equipped with an android (trademark), a palm (registered trademark) webOS (registered trademark) computing device, or the like. In some examples<u style="single">media</u>Presentation device 2820<u style="single">media</u>Streaming media provided by Streamer 145<u style="single">A</u>Includes one or more executable media players for presentation. For example<u style="single">media</u>The media player (s) available on the presentation device 120 can be implemented in Adobe® Flash® (eg, provided in a SWF file) and Hypertext Markup Language (HTML). It can be implemented in version 5 (HTML5), it can be implemented in Google® Chromium®, it can be implemented in accordance with the Open Source Media Framework (OSMF), and it can be implemented by the device or operating system provider. It can be implemented according to a media player application programming interface (API), such as on a device or operating system provider's media player framework (eg, Apple® iOS® MPMoviePlayer software). Or it can be any combination thereof. single<u style="single">media</u>Presentation device 120 is shown, but system 100 is of any number and / or type (s).<u style="single">media</u>Presentation devices can be included.
0132[0132] In the example shown<u style="single">media</u>Presentation device 2820 is secondary<u style="single">media</u>Implement the presenter 2825. Secondary<u style="single">media</u>The presenter 2820 is a secondary provided by the media monitoring agency 2815 over network 150.<u style="single">media</u>Can be stored on a computing device as a viable media presenter capable of presenting. In some examples, secondary<u style="single">media</u>Presenter 2825<u style="single">media</u>It can be implemented as a plug-in connected to the plug-in interface of the media player run by the presentation device 2820. In some examples, secondary<u style="single">media</u>Presenter 2825<u style="single">media</u>It can be implemented as a provided instruction contained within the media player executed by the presentation device 2820. In some examples, secondary<u style="single">media</u>Presenter 2825<u style="single">media</u>It can be implemented as an executable application that is downloaded to the presentation device 2820 (eg, downloaded as an App from the Apple® App Store). For example, secondary<u style="single">media</u>Presenter 2825 can be implemented in Adobe® Flash® (eg, provided in SWF files) and can be implemented in Hypertext Markup Language (HTML) Version 5 (HTML5). Can be implemented according to Google® Chromium®, can be implemented according to the Open Source Media Framework (OSMF), and can be implemented according to the device or operating system provider's media player application programming interface (API). It can be implemented on a device or operating system provider's media player framework (eg, Apple® iOS® MPMoviePlayer software), or any combination thereof. it can. Single secondary<u style="single">media</u>The presenter 2825 is shown, but the system 2800 has<u style="single">media</u>Secondary of any number and / or type (s) associated with the presentation device 2820<u style="single">media</u>A presenter can be included.
0133[0133] An exemplary machine-readable instruction 2900 that can be executed to implement the second exemplary media monitoring agency 2815 of FIG. 28 is shown in FIG. 29. Also referring to the preceding figure, the exemplary machine-readable instruction 2900 of FIG. 29 begins execution at block 2905, and the media monitoring agency 2815 reports metering metadata (eg, audio) reported by device meter 110. / Collect metadata derived from metering data contained within the video watermark, metadata derived from metering data obtained from an independent metering data source, and other metering information (block). 2905). The media monitoring agency 2915 then uses the metering metadata received in block 2905 to secondary.<u style="single">media</u>Select (block 2910). The media monitoring agency 2815 then selected the secondary in block 2910.<u style="single">media</u>, Secondary<u style="single">media</u>Send to presenter 2825 (block 2915). Execution of the exemplary machine-readable instruction 2900 is then terminated.
0134[0134] Device meter 110 and FIG. 28<u style="single">media</u>Secondary in presentation device 2820<u style="single">media</u>An exemplary machine-readable instruction 3000 that can be executed to implement the presenter is shown in FIG. Also referring to the preceding figure, the exemplary machine-readable instruction 3000 of FIG. 30 begins execution at block 3005, and the device meter 110 detects metering metadata and reports it to the media monitoring agency 2815. (Block 3005). Then secondary<u style="single">media</u>The presenter 2825 is a secondary related to the metering metadata reported to the media monitoring agency 2815 in block 3005.<u style="single">media</u>Is received (block 3010). Then secondary<u style="single">media</u>The presenter 2825 received the secondary received at block 3010.<u style="single">media</u>Present (block 3015). Execution of the exemplary machine-readable instruction 3000 is then terminated.
0135[0135] FIG. 31 is a block diagram of an exemplary processing system 3100 capable of implementing the devices and methods disclosed herein. The processing system 3100 includes, for example, tablet computers, notebook / laptop computers, personal computers, personal digital assistants (PDAs), servers, internet devices, DVD players, CD players, digital video recorders, personal video recorders, set-top boxes, etc. Or it can be any other type of computing device.
0136[0136] The processing system 3100 in this example includes a processor 3112, such as a general purpose programmable processor. Processor 3112 executes a coded instruction 3116 that includes local memory 3114 and resides in local memory 3114 and / or in another memory device. Processor 3112 is capable of, among other things, executing the machine-readable instructions shown in FIGS. 13-22, 25, 29, and / or 30. Processor 3112 is one or more Intel® Micros that belong to the Pentium® family, the Itanium® family, and / or the XScale® family. One or more microcontrollers, such as one or more of the ARM® family of processors, processing cores, one or more of the PIC® family of microcontrollers, etc. Can be any type of processing unit. Of course, other processors belonging to other families are also suitable.
0137[0137] Processor 3112 communicates with main memory, including volatile memory 3118 and non-volatile memory 3120, via bus 3122. Volatile memory 3118 includes 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. It can be implemented by the access memory device. The non-volatile memory 3120 can be implemented with flash memory and / or any other desired type of memory device. Access to the main memories 3118 and 3120 is generally controlled by a memory controller (not shown).
0138[0138] The processing system 3100 also includes an interface circuit 3124. The interface circuit 3124 can 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.
0139[0139] One or more input devices 3126 are connected to interface circuit 3124. The input device (s) 3126 allows the user to enter data and commands into the processor 3112. The input device (s) can be implemented, for example, by a keyboard, mouse, touch screen, trackpad, trackball, isopoint, and / or speech recognition system.
0140[0140] One or more output devices 3128 are also connected to interface circuit 3124. The output device 3128 can be implemented, for example, by a display device (eg, a liquid crystal display, a cathode ray tube display (CRT)), by a printer, and / or by a speaker. Therefore, the interface circuit 3124 generally includes a graphics driver card.
0141[0141] Interface circuit 3124 facilitates the exchange of data with an external computer over a network (eg, Ethernet connection, Digital Subscriber Line (DSL), telephone line, coaxial cable, cellular telephone system, etc.). Also includes communication devices such as modems or network interface cards.
0142[0142] The 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 disc drives, hard drive discs, compact disc drives, and digital versatile disc (DVD) drives. In some examples, the mass storage device 3130 is temporary<u style="single">media</u>Storage device 920 can be implemented. In addition, or as an alternative, in some cases, volatile memory 3118 is temporary.<u style="single">media</u>Storage device 920 can also be implemented.
0143[0143] The encoded instructions 3132 of FIGS. 13 to 22, 25, 29, and 30 are local in the mass storage device 3130, in the volatile memory 3118, in the non-volatile memory 3120. It can be stored in memory 3114 and / or on a removable storage medium 3132 such as a CD or DVD.
0144[0144] Instead of implementing the methods and / or devices described herein in a system such as the processing system of FIG. 31, the methods and / or devices described herein are processors and / or ASICs. It can be embedded in a structure such as (integrated circuit for specific applications).
0145[0145] Finally, some exemplary methods, devices, and products have been described herein, but the scope of this patent is not limited to them. On the contrary, this patent covers all methods, devices, and products that are fairly included within the scope of this disclosure, literally or under the doctrine of equivalents.
31 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8 Sheet 9 Sheet 10 Sheet 11 Sheet 12 Sheet 13 Sheet 14 Sheet 15 Sheet 16 Sheet 17 Sheet 18 Sheet 19 Sheet 20 Sheet 21 Sheet 22 Sheet 23 Sheet 24 Sheet 25 Sheet 26 Sheet 27 Sheet 28 Sheet 29 Sheet 30 Sheet 31
Every citation, both ways
| Document | Relation | Office |
|---|---|---|
| JP2003524199A | Cites | Japan |
| JP2004320752A | Cites | Japan |
| WO2010095320A1 | Cites | World Intellectual Property Organization (WIPO) |
| US20060242325A1 | Cites | United States of America |
79 members in 10 offices
Priority claims9
| Document | Office | Kind | Date |
|---|---|---|---|
| 61499520 | United States of America | – | |
| 201161499520 | United States of America | P | |
| 61568631 | United States of America | – | |
| 201161568631 | United States of America | P | |
| 13341646 | United States of America | – | |
| 13341661 | United States of America | – | |
| 201113341646 | United States of America | A | |
| 201113341661 | United States of America | A | |
| 2012043535 | United States of America | W |
Members79
| Document | Office | Kind | |
|---|---|---|---|
| CA2840092A1 | Canada | A1 | |
| CA2840094A1 | Canada | A1 | |
| WO2012177866A2 | World Intellectual Property Organization (WIPO) | A2 | |
| WO2012177870A2 | World Intellectual Property Organization (WIPO) | A2 | |
| WO2012177872A2 | World Intellectual Property Organization (WIPO) | A2 | |
| WO2012177874A2 | World Intellectual Property Organization (WIPO) | A2 | |
| US2013007298A1 | United States of America | A1 | |
| US2013007794A1 | United States of America | A1 | |
| WO2012177874A3 | World Intellectual Property Organization (WIPO) | A3 | |
| WO2012177870A3 | World Intellectual Property Organization (WIPO) | A3 | |
| WO2012177872A3 | World Intellectual Property Organization (WIPO) | A3 | |
| AU2012272868A1 | Australia | A1 | |
| AU2012272872A1 | Australia | A1 | |
| AU2012272874A1 | Australia | A1 | |
| AU2012272876A1 | Australia | A1 | |
| WO2012177866A3 | World Intellectual Property Organization (WIPO) | A3 | |
| US2013268623A1 | United States of America | A1 | |
| US2013268630A1 | United States of America | A1 | |
| US2013290508A1 | United States of America | A1 | |
| US2013291001A1 | United States of America | A1 | |
| US2013311776A1 | United States of America | A1 | |
| US2013311780A1 | United States of America | A1 | |
| KR20140044837A | Republic of Korea | A | |
| CN103733629A | China | A | |
| CN103733630A | China | A | |
| CN103748825A | China | A | |
| CN103748894A | China | A | |
| EP2724547A2 | European Patent Office (EPO) | A2 | |
| MX2013015025A | Mexico | A | |
| MX2014000281A | Mexico | A | |
| EP2735116A2 | European Patent Office (EPO) | A2 | |
| MX2014000280A | Mexico | A | |
| EP2756683A2 | European Patent Office (EPO) | A2 | |
| EP2756684A2 | European Patent Office (EPO) | A2 | |
| JP2014526158A | Japan | A | |
| EP2735116A4 | European Patent Office (EPO) | A4 | |
| EP2724547A4 | European Patent Office (EPO) | A4 | |
| EP2756683A4 | European Patent Office (EPO) | A4 | |
| EP2756684A4 | European Patent Office (EPO) | A4 | |
| AU2012272868B2 | Australia | B2 | |
| AU2012272872B2 | Australia | B2 | |
| KR101554997B1 | Republic of Korea | B1 | |
| AU2012272874B2 | Australia | B2 | |
| AU2015252031A1 | Australia | A1 | |
| US9197421B2 | United States of America | B2 | |
| US9209978B2 | United States of America | B2 | |
| US9210208B2 | United States of America | B2 | |
| AU2012272872A8 | Australia | A8 | |
| US2016043916A1 | United States of America | A1 | |
| AU2012272876B2 | Australia | B2 | |
| JP5963373B2This record | Japan | B2 | |
| CN103748825B | China | B | |
| CA2840094C | Canada | C | |
| CA2840092C | Canada | C | |
| US9515904B2 | United States of America | B2 | |
| US2017041204A1 | United States of America | A1 | |
| AU2015252031B2 | Australia | B2 | |
| EP2735116B1 | European Patent Office (EPO) | B1 | |
| CN103748894B | China | B | |
| US9838281B2 | United States of America | B2 | |
| CN107682352A | China | A | |
| EP2724547B1 | European Patent Office (EPO) | B1 | |
| EP3404920A1 | European Patent Office (EPO) | A1 | |
| HK1250436A | Hong Kong, China | A | |
| HK1250436A1 | Hong Kong, China | A1 | |
| EP3404920B1 | European Patent Office (EPO) | B1 | |
| EP3661114A1 | European Patent Office (EPO) | A1 | |
| US2020177480A1 | United States of America | A1 | |
| US10791042B2 | United States of America | B2 | |
| CN107682352B | China | B | |
| US2021014140A1 | United States of America | A1 | |
| US11252062B2 | United States of America | B2 | |
| US11296962B2 | United States of America | B2 | |
| US2022124016A1 | United States of America | A1 | |
| EP3661114B1 | European Patent Office (EPO) | B1 | |
| US11784898B2 | United States of America | B2 | |
| US2024039810A1 | United States of America | A1 | |
| US12155546B2 | United States of America | B2 | |
| US2025055775A1 | United States of America | A1 |
17 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Cancellation because of no payment of annual feesLAPS | LAPS | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Certificate of patent or registration of utility modelJAPANESE INTERMEDIATE CODE: R150R150 | R150 | |
| First payment of annual fees (during grant procedure)JAPANESE INTERMEDIATE CODE: A61A61 | A61 | |
| Written decision to grant a patent or to grant a registration (utility model)JAPANESE INTERMEDIATE CODE: A01A01 | A01 | |
| Decision of grant or rejection writtenTRDD | TRDD | |
| Request for written amendment filedJAPANESE INTERMEDIATE CODE: A523A521 | A521 | |
| Notification of reasons for refusalJAPANESE INTERMEDIATE CODE: A131A131 | A131 | |
| Request for written amendment filedJAPANESE INTERMEDIATE CODE: A523A521 | A521 | |
| Written submission of copy of amendment under article 19 pctJAPANESE INTERMEDIATE CODE: A524A524 | A524 | |
| Written request for extension of timeJAPANESE INTERMEDIATE CODE: A601A601 | A601 | |
| Written request for extension of timeJAPANESE INTERMEDIATE CODE: A601A601 | A601 | |
| Notification of reasons for refusalJAPANESE INTERMEDIATE CODE: A131A131 | A131 | |
| Report on retrievalJAPANESE INTERMEDIATE CODE: A971007A977 | A977 |
Numbers
- Publication
- 5963373
- Application
- 2014517158
Titles2
- Japanese
- ストリーミングメディアのモニタリング
- English
- Streaming media monitoring
Classification
- CPC, 10
- H04N21/8358
- H04L65/70
- H04L43/06
- H04L65/80
- H04N21/6582
- H04N21/8126
- H04N19/46
- H04N1/32101
- H04N21/2353
- H04L65/61
- IPC, 2
- H04N21 235
- H04N21 435
