Measuring video-asset viewing
11537971 · 2022-12-27
Assignee
Inventors
Cpc classification
H04N21/23424
ELECTRICITY
H04N21/4821
ELECTRICITY
H04N21/44204
ELECTRICITY
G06Q10/08
PHYSICS
H04N21/4532
ELECTRICITY
International classification
H04N21/234
ELECTRICITY
G06Q10/08
PHYSICS
H04N21/45
ELECTRICITY
H04N21/442
ELECTRICITY
H04N21/438
ELECTRICITY
Abstract
A computer-implemented method of using channel tuning data from a video asset viewing device connected to a network to measure video asset viewing at a second-by-second level during one or more user defined lead-in periods, and then correlating that with video asset viewing during a user defined target period, for the purpose of analyzing how viewing activity during the lead-in period(s) correlates with viewing activity during the target period, thus producing longitudinal viewing metrics; all while maintaining viewer anonymity. Additionally, viewing metrics can be categorized based on user defined demographic, geographic, and histogram groupings representing the percentage of video asset viewing with the result that the analyst is able to gain detailed insight into customer viewing behavior. The lead-in video asset may be any video asset or assets. The target may be any subsequent video asset. The metrics produced are useful to service providers, advertisers, and content producers.
Claims
1. A method comprising: receiving data indicating output of a plurality of media segments by a plurality of devices during a time range, wherein a first time period and a second time period later than the first time period are in the time range and separated by a time duration; determining, based on the data and for each interval of a plurality of intervals of the second time period, media segments, of the plurality of media segments, outputted by the plurality of devices; based on the determining of the media segments, determining that a first device, associated with a user, outputted a first media segment of the plurality of media segments during the first time period and a second device, associated with the user, outputted a second media segment of the plurality of media segments during the second time period; and based on the determining that the first device outputted the first media segment and the second device outputted the second media segment, incrementing a count associated with outputting both the first media segment and the second media segment.
2. The method of claim 1, wherein the second media segment comprises an advertisement associated with a provider, and wherein the first media segment comprises a different advertisement associated with the provider.
3. The method of claim 1, wherein the first media segment comprises an advertisement for the second media segment.
4. The method of claim 1, further comprising: determining, based at least in part on the data, a metric for one or more media segments of the plurality of media segments.
5. The method of claim 4, wherein the metric is indicative of an impact outputting the first media segment has on outputting the second media segment.
6. The method of claim 1, wherein the second media segment comprises a video program, and wherein the first media segment comprises an advertisement referencing the video program.
7. The method of claim 1, wherein the first media segment comprises an episode in a series of episodic video content, and wherein the second media segment comprises a subsequent episode in the series of episodic video content.
8. The method of claim 1, wherein the first media segment comprises content indicating the second media segment.
9. The method of claim 1, further comprising determining, based at least in part on the data, a source from which the first media segment was received by a device of the plurality of devices.
10. A system comprising: a computing device; and a second device; wherein the computing device comprises: one or more first processors; and first memory storing first instructions that, when executed by the one or more first processors, cause the computing device to: receive data indicating output of a plurality of media segments by a plurality of devices during a time range, wherein a first time period and a second time period later than the first time period are in the time range and separated by a time duration, wherein the plurality of devices comprises a first device and the second device, and wherein the first device and the second device are associated with a user; determine, based on the data and for each interval of a plurality of intervals of the second time period, media segments, of the plurality of media segments, outputted by the plurality of devices; based on the determining of the media segments, determine that the first device outputted a first media segment of the plurality of media segments during the first time period and the second device outputted a second media segment of the plurality of media segments during the second time period; and based on the determining that the first device outputted the first media segment and the second device outputted the second media segment, increment a count associated with outputting both the first media segment and the second media segment; and wherein the second device comprises: one or more second processors; and second memory storing second instructions that, when executed by the one or more second processors, cause the second device to send second data indicating one or more media segments outputted by the second device during the time range.
11. The system of claim 10, wherein the second media segment comprises an advertisement associated with a provider, and wherein the first media segment comprises a different advertisement associated with the provider.
12. The system of claim 10, wherein the first media segment comprises an advertisement for the second media segment.
13. The system of claim 10, wherein the first instructions, when executed by the one or more first processors, further cause the computing device to: determine, based at least in part on the data, a metric for one or more media segments of the plurality of media segments.
14. The system of claim 13, wherein the metric is indicative of an impact outputting the first media segment has on outputting the second media segment.
15. The system of claim 10, wherein the second media segment comprises a video program, and wherein the first media segment comprises an advertisement referencing the video program.
16. The system of claim 10, wherein the first media segment comprises an episode in a series of episodic video content, and wherein the second media segment comprises a subsequent episode in the series of episodic video content.
17. The system of claim 10, wherein the first media segment comprises content indicating the second media segment.
18. The system of claim 10, wherein the first instructions, when executed by the one or more first processors, further cause the computing device to determine, based at least in part on the data, a source from which the first media segment was received by a device of the plurality of devices.
19. A non-transitory computer-readable medium storing instructions that, when executed, cause a computing device to: receive data indicating output of a plurality of media segments by a plurality of devices during a time range, wherein a first time period and a second time period later than the first time period are in the time range and separated by a time duration; determine, based on the data and for each interval of a plurality of intervals of the second time period, media segments, of the plurality of media segments, outputted by the plurality of devices; based on the determining of the media segments, determine that a first device, associated with a user, outputted a first media segment of the plurality of media segments during the first time period and a second device, associated with the user, outputted a second media segment of the plurality of media segments during the second time period; and based on the determining that the first device outputted the first media segment and the second device outputted the second media segment, increment a count associated with outputting both the first media segment and the second media segment.
20. The computer-readable medium of claim 19, wherein the second media segment comprises an advertisement associated with a provider, and wherein the first media segment comprises a different advertisement associated with the provider.
21. The computer-readable medium of claim 19, wherein the first media segment comprises an advertisement for the second media segment.
22. The computer-readable medium of claim 19, wherein the instructions, when executed, further cause the computing device to: determine, based at least in part on the data, a metric for one or more media segments of the plurality of media segments.
23. The computer-readable medium of claim 22, wherein the metric is indicative of an impact outputting the first media segment has on outputting the second media segment.
24. The computer-readable medium of claim 19, wherein the second media segment comprises a video program, and wherein the first media segment comprises an advertisement referencing the video program.
25. The computer-readable medium of claim 19, wherein the first media segment comprises an episode in a series of episodic video content, and wherein the second media segment comprises a subsequent episode in the series of episodic video content.
26. The computer-readable medium of claim 19, wherein the first media segment comprises content indicating the second media segment.
27. The computer-readable medium of claim 19, wherein the instructions, when executed, further cause the computing device to determine, based at least in part on the data, a source from which the first media segment was received by a device of the plurality of devices.
28. An apparatus comprising: one or more processors; and memory storing instructions that, when executed by the one or more processors, cause the apparatus to: receive data indicating output of a plurality of media segments by a plurality of devices during a time range, wherein a first time period and a second time period later than the first time period are in the time range and separated by a time duration; determine, based on the data and for each interval of a plurality of intervals of the second time period, media segments, of the plurality of media segments, outputted by the plurality of devices; based on the determining of the media segments, determine that a first device, associated with a user, outputted a first media segment of the plurality of media segments during the first time period and a second device, associated with the user, outputted a second media segment of the plurality of media segments during the second time period; and based on the determining that the first device outputted the first media segment and the second device outputted the second media segment, increment a count associated with outputting both the first media segment and the second media segment.
29. The apparatus of claim 28, wherein the second media segment comprises an advertisement associated with a provider, and wherein the first media segment comprises a different advertisement associated with the provider.
30. The apparatus of claim 28, wherein the first media segment comprises an advertisement for the second media segment.
31. The apparatus of claim 28, wherein the instructions, when executed by the one or more processors, cause the apparatus to: determine, based at least in part on the data, a metric for one or more media segments of the plurality of media segments.
32. The apparatus of claim 31, wherein the metric is indicative of an impact outputting the first media segment has on outputting the second media segment.
33. The apparatus of claim 28, wherein the second media segment comprises a video program, and wherein the first media segment comprises an advertisement referencing the video program.
34. The apparatus of claim 28, wherein the first media segment comprises an episode in a series of episodic video content, and wherein the second media segment comprises a subsequent episode in the series of episodic video content.
35. The apparatus of claim 28, wherein the first media segment comprises content indicating the second media segment.
36. The apparatus of claim 28, wherein the instructions, when executed by the one or more processors, cause the apparatus to determine, based at least in part on the data, a source from which the first media segment was received by a device of the plurality of devices.
Description
BRIEF DESCRIPTION OF THE DRAWINGS
(1) In the drawings, closely related figures have the same number but different alphabetic suffixes.
(2)
(3)
(4)
(5)
(6)
(7)
(8)
(9)
(10)
(11)
(12)
(13)
(14)
(15)
(16)
(17)
(18)
(19)
(20)
(21)
(22)
(23)
(24)
(25)
(26)
(27)
(28)
(29)
(30)
(31)
(32)
(33)
(34)
(35)
(36)
(37)
(38)
(39)
DETAILED DESCRIPTION OF THE DRAWINGS
(40) When reading the information below, it can be appreciated that these are merely samples of table layouts, format and content, and many aspects of these tables may be varied or expanded within the scope of the embodiment. The table layouts, field formats and content, algorithms, and other aspects are what I presently contemplate for this embodiment, but other table layouts, field formats and content, algorithms, etc. can be used. The algorithms are samples and various aspects of the algorithms may be varied or expanded within the scope of the embodiment.
(41) Note on Claims reference in drawings—because of the large number of data fields and new concepts taught in this specification, and because a description in the drawings may not use the exact same words or spelling as the corresponding concept in the claims, the reader will note that in limited cases I have added text preceded by the words “Claims reference” to assist the reader in correlating information in the drawings or detailed description of the drawings with the corresponding information in the claims.
(42) For many of the metrics shown below, I have suggested what the metric indicates. This is not to limit the purpose of the metric to that one usage, but simply to indicate one of potentially many valuable uses for the metric.
(43) Note that the specification and drawings use certain terms interchangeably. The reader will note this most frequently with the terms set-top box and video asset viewing device. The reader will appreciate that a set-top box is merely a specific kind of video asset viewing device. A smart phone, a tablet device, a gaming console are all examples of video asset viewing device.
(44) Thus any discussion below that refers to a set-top box should be read to also include any kind of a video asset viewing device.
(45) In one embodiment the Lead-In Analytics Engine 200 can be implemented on processors provided by the INTEL® Corporation under the trademark Core™ i3-2120 using single or multiple processor configurations. The operating system offered by MICROSOFT® Corporation under the trademark WINDOWS 7 Professional can be used as the computer operating system. The Lead-In Analytics Engine 200 can be implemented in a number of programming languages, including but not limited to, COBOL, C and C++.
(46) I have implemented the Lead-In Analytics Engine 200 and supporting code in FUJITSU® NetCOBOL® for WINDOWS® version 10.1 developed by Fujitsu® and distributed by Alchemy Solutions Inc. This product is available at http://www.alchemysolutions.com or http://www.netcobol.com. The Lead-In Analytics Engine 200 and all of the supporting processes have been developed and run on a DELL® Vostro 260 with INTEL® Core™ i3-2120 CPU 3.30 GHz with 4.00 GB of RAM running MICROSOFT® WINDOWS 7 Professional Service Pack 1. The computer was purchased from Dell Computer Corporation. The operating system is from Microsoft.
(47) Although the embodiments described herein enable one of ordinary skill in the art to implement (i.e. build) the Lead-In Analytics Engine 200 and supporting software, it in no way restricts the method of implementation, the Lead-In Analytics Engine 200 and supporting software being capable of being implemented on a variety of hardware/software platforms using a variety of development languages, databases, communication protocols and frameworks as will be evident to those of ordinary skill in the art.
(48)
(49) As I described in my prior United States Patent Application having U.S. application Ser. No. 12/981,301 filed on Dec. 29, 2010, a cable television company may operate a Switched Digital Video system from a vendor which provides such a system. That system collects channel tuning data as part of its normal operation. Such data can be preprocessed using a computer program which reformats the SDV vendor's channel tuning data into a common format, performs data enrichments, and applies business rules as data quality checks all in preparation for creating an unsorted channel tune file in a common or standardized format.
(50) I also described in that prior Application how a cable television company or satellite television broadcasting company provides Set-top box application software for its customers to use to operate their set-top box. Such software may be developed in-house or by a third party. The STB software collects channel tuning data as part of the normal operation of said Set-top box application software system. STB Channel tuning data is then preprocessed using a computer program which reformats the STB Channel tuning data into a common format, performs data enrichments, and applies business rules as data quality checks all in preparation for creating an unsorted channel tune file in a common or standardized format.
(51) In addition to those methods for collecting channel tuning data, there are now set-top box applications available that are able to collect channel tuning data and other set-top box interactions. The company Fourth Wall Media provides such as application. See their web site at http://www.fourthwallmedia.tv/Products/.
(52) In the context of hand-held personal communication devices which play audio and video, the devices are able to capture video viewing information and make that information available to an analytics engine.
(53) Data from any of these sources and other potential sources are represented by the Channel Tuning Data Collector 100 which takes the raw channel tuning data from various sources, reformats it into a common format, performs data enrichments, and applies business rules as data quality checks, all in preparation for creating an unsorted channel tune file in a common or standardized format. Said Channel Tuning Data Collector 100 then sorts the unsorted channel tuning data to produce Channel Tune File 110 (see
(54) In
(55) In addition to providing the Channel Tuning Data as a file, this information could also be provided as the result set of a data base query or as XML messages.
(56) In a similar manner, an internet protocol television system can track the viewing activity related to each video asset and make that viewing activity available to the Lead-In Analytics Engine 200.
(57) Proceeding with the review of
(58) Proceeding with the review of
(59) Each study will have a Lead In Video Play Info File 130 with each record having fields similar to those described in
(60) The data in this file may be entered to a data base using a graphical user interface and then queried from there to provide the file, or it may be entered to a web application and provided as an XML file, or it may be keyed into a flat file directly. Those with ordinary skill in the art will have no difficulty using common software development tools to develop a process which provides a file or a database table like the one shown as input to the Lead-In Analytics Engine 200.
(61) Proceeding with the review of
(62) As non-limiting examples, I provide the following examples of how the Lead In Demographic Geographic Histogram may be configured: 1. The Analyst may define one Demographic Group and one Geographic Group with a variety of Histogram viewing buckets. 2. The Analyst may define Several Demographic Groups and one Geographic Group with a variety of Histogram viewing buckets. 3. The Analyst may define one Demographic Group and several Geographic Groups with one Histogram viewing bucket. 4. The Histogram viewing buckets may be defined from 1% to 100% with any number of breakdowns or only one bucket for the entire range if the intent is to focus only on demographic and/or geographic attributes of the viewers. 5. A Histogram viewing bucket may be defined as 0 to 0 which enables analysis based on set-top boxes which were not tuned during the lead-in video viewing periods.
(63) Each study will have a Lead In Demographic Geographic Histogram Definition File 140 with each record having fields similar to those described in
(64) The Lead In Analytic Engine presently supports up to 200 combinations of Demographic, Geographic, and Histogram categories, but this may be changed as needed.
(65) The data in this file may be entered to a data base using a graphical user interface and then queried from there to provide the file, or it may be entered to a web application and provided as an XML file, or it may be keyed into a flat file directly. Those with ordinary skill in the art will have no difficulty using common software development tools to develop a process which provides a file or a database table like the one shown as input to the Lead-In Analytics Engine 200.
(66) Note: The histogram aspect of this file is similar to the histogram for Result viewing but it has its own definition because the purpose is very different. This histogram is applicable only to analyzing Lead In viewing during the individual lead-in periods.
(67) Proceeding with the review of
(68) Each study will have one Analysis Period Target File record with fields similar to those described in
(69) Proceeding with the review of
(70) Each study may have an Analysis Period Definition File 160 with each record having fields similar to those described in
(71) The data in this file may be entered to a data base using a graphical user interface and then queried from there to provide the file, or it may be entered to a web application and provided as an XML file, or it may be keyed into a flat file directly. Those with ordinary skill in the art will have no difficulty using common software development tools to develop a process which provides a file or a database table like the one shown as input to the Lead-In Analytics Engine 200.
(72) Proceeding with the review of
(73) This Result Histogram information is used by the Lead-In Analytics Engine 200 as follows: For each set-top box, all of the lead-in viewing from all of the lead-in periods together is aggregated. That number is converted to a percentage of the total lead-in viewing that the set-top box was tuned to. That percentage is then compared to the Histogram percentages in the Result Demographic Geographic Histogram Definition File 170 in order to categorize the viewing of this set-top box with the viewing of set-top boxes that had a similar amount of aggregate lead-in viewing so that those similarly situated set-top boxes can then be tracked as to viewing during the Target period. This allows the Lead-In Analytics Engine 200 to compare Target viewing based on the amount of aggregate Lead-in viewing to determine whether the lead-in viewing had any impact on the Target viewing. As an example, the Analyst can compare Target viewing by those set-top boxes which viewed 1-10% of the lead-in video with those that viewed 80-100% of the lead-in video to measure what impact exposure to the lead-in viewing had on viewing of the Target.
(74) As non-limiting examples, I provide the following examples of how the Result Demographic Geographic Histogram may be configured: 1. The Analyst may define one Demographic Group and one Geographic Group with a variety of Histogram viewing buckets. 2. The Analyst may define Several Demographic Groups and one Geographic Group with a variety of Histogram viewing buckets. 3. The Analyst may define one Demographic Group and several Geographic Groups with one Histogram viewing bucket. 4. The Histogram viewing buckets may be defined from 1% to 100% with any number of breakdowns or only one bucket for the entire range if the intent is to focus only on demographic and/or geographic attributes of the viewers. 5. A Histogram viewing bucket may be defined as 0 to 0 which enables analysis based on set-top boxes which were not tuned during any of the lead-in video viewing periods.
(75) Each study will have a Result Demographic Geographic Histogram Definition File 170 with each record having fields similar to those described in
(76) The Lead In Analytic Engine presently supports up to 200 combinations of Demographic, Geographic, and Histogram categories, but this may be changed as needed.
(77) The data in this file may be entered to a data base using a graphical user interface and then queried from there to provide the file, or it may be entered to a web application and provided as an XML file, or it may be keyed into a flat file directly. Those with ordinary skill in the art will have no difficulty using common software development tools to develop a process which provides a file or a database table like the one shown as input to the Lead-In Analytics Engine 200.
(78) Note: The histogram aspect of this file similar to the histogram for Lead-in viewing but it has its own definition because the purpose is very different. We are using this file to group viewers for Target period analysis based on the aggregate amount of viewing during the Lead-in period.
(79) Proceeding with the review of
(80) The data in this file may be entered to a data base using a graphical user interface and then queried from there to provide the file, or it may be entered to a web application and provided as an XML file, or it may be keyed into a flat file directly. Those with ordinary skill in the art will have no difficulty using common software development tools to develop a process which provides a file or a database table like the one shown as input to the Lead-In Analytics Engine 200.
(81) Proceeding with the review of
(82) Recall that the Lead-in video can be used to promote viewing of a particular video asset and that this lead-in video asset may have aired on various dates. One non-limiting example of this may be a series of commercials that aired on various dates to promote an upcoming Target show. A second non-limiting example of this may be an episodic program where the Lead-In Analytics Engine 200 is tracking data for the last 7 weeks with the Target being the next episode. In either case, the Channel Tune File 110 may contain channel tuning activity that is not of interest for the study the analyst is doing. This file provides the analyst with a method to skip those Channel tuning records that he is not interested in and to focus on those tuning records that are likely to contain relevant channel tuning activity.
(83) The Tuning Data Dates File 190 is described in
(84) The data in this file may be entered to a data base using a graphical user interface and then queried from there to provide the file, or it may be entered to a web application and provided as an XML file, or it may be keyed into a flat file directly. Those with ordinary skill in the art will have no difficulty using common software development tools to develop a process which provides a file or a database table like the one shown as input to the Lead-In Analytics Engine 200.
(85) Proceeding with the review of
(86) An exemplary record layout for the Analysis Group File 210 which is created by the Lead-In Analytics Engine 200 is described in
(87) The data in this file may be loaded to a data base in support of further analytics. Those with ordinary skill in the art will have no difficulty using common software development tools to develop a process which loads a file like the one shown to a data base or data warehouse in support of additional reporting and analytics. Alternatively, the Lead-In Analytics Engine 200 could update a data base table which has a structure similar to file format shown in
(88) Proceeding with the review of
(89) An exemplary record layout for the Analysis Lead In Period File 220 which is created by the Lead-In Analytics Engine 200 is described in
(90) The data in this file may be loaded to a data base in support of further analytics. Those with ordinary skill in the art will have no difficulty using common software development tools to develop a process which loads a file like the one shown to a data base or data warehouse in support of additional reporting and analytics. Alternatively, the Lead-In Analytics Engine 200 could update a data base table which has a structure similar to file format shown in
(91) Proceeding with the review of
(92) An exemplary record layout for the Lead In Viewing Result File 230 which is created by the Lead-In Analytics Engine 200 is described in
(93) The data in this file may be loaded to a data base in support of further analytics. Those with ordinary skill in the art will have no difficulty using common software development tools to develop a process which loads a file like the one shown to a data base or data warehouse in support of additional reporting and analytics. Alternatively, the Lead-In Analytics Engine 200 could update a data base table which has a structure similar to file format shown in
(94) To recap the output files that are created related to Lead-in viewing, the Lead-In Analytics Engine 200 has created a summary Analysis Group File 210 which records overall information about the Analysis study that is being done. Then the Analysis Lead In Period File 220 records information about each Lead-in video asset along with the aggregate viewing information for all of the Demographic Geographic Histogram groupings that viewed this Lead In video asset. Finally the Lead In Viewing Result File 230 records statistics about the lead in viewing broken out by the audience segments defined in the Demographic Geographic Histogram Definition File. The end result is that the analyst has very detailed information regarding viewing activity for each lead-in video asset.
(95) A non-limiting example will help to illustrate: If the Lead-in was a series of commercials promoting a baseball game, the Analysis Group File 210 records information about the study such as that it is tracking lead-in viewing for a series of ads promoting a baseball game including potential viewing seconds if a set-top box tuned to all the ads, the number of possible exposures that a set-top box may have, and then actual viewing results measured in aggregate viewing seconds and aggregate exposures. Then the Analysis Lead In Period File 220 records the various details about the individual lead-in segments or commercials that were aired promoting the game including the channel each video played on and the date and time. It also records the aggregate viewing in seconds of that lead-in video across all of the demographic-geographic-histogram groupings. Finally, the Lead In Viewing Result File 230 records each of the viewership demographic and geographic breakouts along with the histogram buckets which break-out viewing by how much of that particular lead-in video the set-top box was tuned to.
(96) The end result for the lead-in viewing is that the analyst is able to get a very detailed breakdown of actual viewership for each lead-in segment. He can determine demographic coding of the viewers and their geographic location. He can determine whether or not the people he was targeting with the ad actually were tuned in when it aired and how much of it they viewed. He can see longitudinal activity across a series of ads that aired on the same day or on multiple days. He has new tools that were never available previously to measure the effectiveness of his ads.
(97) Proceeding with the review of
(98) An exemplary record layout for the Analysis Period Result Header File 240 which is created by the Lead-In Analytics Engine 200 is described in
(99) The data in this file may be loaded to a data base in support of further analytics. Those with ordinary skill in the art will have no difficulty using common software development tools to develop a process which loads a file like the one shown to a data base or data warehouse in support of additional reporting and analytics. Alternatively, the Lead-In Analytics Engine 200 could update a data base table which has a structure similar to file format shown in
(100) Proceeding with the review of
(101) An exemplary record layout for the Analysis Period Result Detail File 250 which is created by the Lead-In Analytics Engine 200 is described in
(102) The data in this file may be loaded to a data base in support of further analytics. Those with ordinary skill in the art will have no difficulty using common software development tools to develop a process which loads a file like the one shown to a data base or data warehouse in support of additional reporting and analytics. Alternatively, the Lead-In Analytics Engine 200 could update a data base table which has a structure similar to file format shown in
(103) Proceeding with the review of
(104) An exemplary record layout for the Analysis Period Result Demographic Geographic Histogram File 260 which is created by the Lead-In Analytics Engine 200 is described in
(105) The data in this file may be loaded to a data base in support of further analytics. Those with ordinary skill in the art will have no difficulty using common software development tools to develop a process which loads a file like the one shown to a data base or data warehouse in support of additional reporting and analytics. Alternatively, the Lead-In Analytics Engine 200 could update a data base table which has a structure similar to file format shown in
(106) Proceeding with the review of
(107) An exemplary record layout for the Analysis Period Result Channel Viewing Detail File 270 which is created by the Lead-In Analytics Engine 200 is described in
(108) The data in this file may be loaded to a data base in support of further analytics. Those with ordinary skill in the art will have no difficulty using common software development tools to develop a process which loads a file like the one shown to a data base or data warehouse in support of additional reporting and analytics. Alternatively, the Lead-In Analytics Engine 200 could update a data base table which has a structure similar to file format shown in
(109) To recap the output files related to Target viewing, the Lead-In Analytics Engine 200 has created a summary file for the Target (defined in Analysis Period Result Header File 240) which provided information on the Target as a whole along with a way to group together all of the detail data for the Target. It then created a individual segments (defined in Analysis Period Result Detail File 250) which allowed the analyst to break the Target down into one or more periods of interest for analysis. Each of these analysis period segments was then further broken down by various Demographic, Geographic, and Histogram characteristics (defined in Analysis Period Result Demographic Geographic Histogram File 260) so that the analyst could gain insight into the viewership of the Target segment. Finally, viewing at this fine level of granularity was captured for each channel through the list of channels viewed (defined in Analysis Period Result Channel Viewing Detail File 270).
(110) A non-limiting example will help to illustrate: The Lead-in was a series of commercials promoting a baseball game. The Target that the analyst wants to understand is viewing of the baseball game. The individual segments are the innings. The various Demographic, Geographic, and Histogram characteristics are the breakdowns of the viewing audience. The Demographic identifier of the viewer is identified in the channel tuning data. The Geographic location of the viewer is identified in the channel tuning data. The Histogram index (viewing percentage) is set based on the aggregate viewing of the lead-in commercials by this set-top box. The channel viewing result measures how much of the game the set-top box was tuned to, broken down by inning and by demographic-geographic-histogram. Finally, channel viewing result also tracks what the set-top box tuned to during each segment instead of the game, if anything.
(111) The end result is that the analyst now has a level of understanding of audience viewership never before possible. Nonlimiting examples include: he can compare viewing based on exposure to the lead-in to see if his lead-in had any effect on viewership; he can determine what the viewers watched instead of his Target; he can measure actual viewership of his Target.
(112)
(113) The process begins with Load Lead In Demo-Geo-Hist Array 300. The process then executes Read Lead In Demo-Geo-Hist file 310 which reads file Lead In Demographic Geographic Histogram Definition File 140 as input. The process checks for End of File 320. If it is the end of file, the process is Done 340. If End of File 320 does not detect an end of file condition, then the record that was read is loaded to the array using Load Lead In Demo-Geo-Hist Array 330.
(114) The end result of this process is that the Lead-In Analytics Engine 200 has loaded the Lead-in Demographic Geographic Histogram Definition data into an array in the memory of the computer running the engine.
(115) Additional detail on step Load Lead In Demo-Geo-Hist Array 330 follows:
(116) The Lead-In Analytics Engine 200 populates each of the fields as follows:
(117) LI-DEMOGRAPHIC-CODE 5810 is populated from LEAD-IN-DEMOGRAPHIC-CODE 1610 in input file 140.
(118) LI-DEMOGRAPHIC-DESC 5820 is populated from LEAD-IN-DEMOGRAPHIC-DESC 1620 in input file 140.
(119) LI-GEOGRAPHIC-CODE 5830 is populated from LEAD-IN-GEOGRAPHIC-CODE 1630 in input file 140.
(120) LI-GEOGRAPHIC-DESC 5840 is populated from LEAD-IN-GEOGRAPHIC-DESC 1640 in input file 140.
(121) LI-HISTOGRAM-INDEX 5850 is populated from LEAD-IN-HISTOGRAM-INDEX 1650 in input file 140.
(122) LI-HISTOGRAM-BUCKET-NAME 5860 is populated from LEAD-IN-HISTOGRAM-BUCKET-NAME 1660 in input file 140.
(123) LI-HISTOGRAM-BEG-PCT 5870 is populated from LEAD-IN-HISTOGRAM-BEG-PCT 1670 in input file 140.
(124) LI-HISTOGRAM-END-PCT 5880 is populated from LEAD-IN-HISTOGRAM-END-PCT 1680 in input file 140.
(125) The source code for this routine can be found in the accompanying source code file as routines C110-LOAD-LI-DEMO-GEO-HISTG-AR and C112-LOAD-DEMO-GEO-HISTG-DEF which is included herein by reference.
(126)
(127) The process begins with Load Result in Demo-Geo-Hist Array 350. The process then executes Read Result Demo-Geo-Hist file 360 which reads file Result Demographic Geographic Histogram Definition File 170 as input. The process checks for End of File 370. If it is the end of file, the process is Done 390. If End of File 370 does not detect an end of file condition, then the record that was read is loaded to the array using Load Result Demo-Geo-Hist Array 380.
(128) The end result of this process is that the Lead-In Analytics Engine 200 has loaded the Result Demographic Geographic Histogram Definition data into an array in the memory of the computer running the engine.
(129) Additional detail on step Load Result Demo-Geo-Hist Array 380 follows:
(130) The Lead-In Analytics Engine 200 populates each of the fields as follows:
(131) RE-DEMOGRAPHIC-CODE 5910 is populated from RESULT-DEMOGRAPHIC-CODE 2210 in input file 170.
(132) RE-DEMOGRAPHIC-DESC 5920 is populated from RESULT-DEMOGRAPHIC-DESC 2220 in input file 170.
(133) RE-GEOGRAPHIC-CODE 5930 is populated from RESULT-GEOGRAPHIC-CODE 2230 in input file 170.
(134) RE-GEOGRAPHIC-DESC 5940 is populated from RESULT-GEOGRAPHIC-DESC 2240 in input file 170.
(135) RE-HISTOGRAM-INDEX 5950 is populated from RESULT-HISTOGRAM-INDEX 2250 in input file 170.
(136) RE-HISTOGRAM-BUCKET-NAME 5960 is populated from RESULT-HISTOGRAM-BUCKET-NAME 2260 in input file 170.
(137) RE-HISTOGRAM-BEG-PCT 5970 is populated from RESULT-HISTOGRAM-BEG-PCT 2270 in input file 170.
(138) RE-HISTOGRAM-END-PCT 5980 is populated from RESULT-HISTOGRAM-END-PCT 2280 in input file 170.
(139) The source code for this routine can be found in the accompanying source code file as routines C115-LOAD-RE-DEMO-GEO-HISTG-AR and C117-LOAD-DEMO-GEO-HISTG-DEF which is included herein by reference.
(140)
(141) The end result of this process is that the Lead-In Analytics Engine 200 has loaded the Channels to Analyze data into an array in the memory of the computer running the engine.
(142) Additional detail on step Load Channels to Analyze Array 430 follows:
(143) The Lead-In Analytics Engine 200 populates each of the fields as follows:
(144) CHAN-TO-ANALYZE-CALL-SIGN 6010 is populated from CHANNEL-CALL-SIGN 2410 in input file 180.
(145) CHAN-TO-ANALYZE-CALL-SIGN-NAME 6020 is populated from CHANNEL-CALL-SIGN-NAME 2420 in input file 180.
(146) The source code for this routine can be found in the accompanying source code file as routines C120-CHANNELS-TO-ANALYZE and C122-CHANNELS-TO-ANALYZE which is included herein by reference.
(147)
(148) The process begins with Load Lead In Video Info Array 450. The process then executes Read Analysis Group Info file and Load to Array 460 which reads file Analysis Group Info File 120 as input and loads the Analysis Group record to the array. Note that there is only one record in this file.
(149) The process then proceeds to Read Lead In Video Info file 470 where it reads file Lead In Video Play Info File 130 as input. The process checks for End of File 475. If it is the end of file, the process is Done 495. If End of File 475 does not detect an end of file condition, then the record that was read is loaded to the array using Load Lead In Video Info Array 480. While still working with this Lead-in Period definition record, the process then executes Load Lead In Demo-Geo-Hist Info for Lead In Group 490 which copies the set of Lead-in Demographic-Geographic-Histogram definitions, that was loaded previously (reference
(150) The result is that each Lead-in Period definition ends up with the entire set of Lead-in Demographic-Geographic-Histogram definitions. Those Lead-in Demographic-Geographic-Histogram definitions will then be used later in the process by the Lead-In Analytics Engine 200 as it collects viewing data for each Lead-in period and groups it into the buckets defined by the Lead-in Demographic-Geographic-Histogram definitions. This allows the Lead-In Analytics Engine 200 to categorize the lead-in viewing based on the Demographic-Geographic characteristics of of the viewer. Additionally, the Histogram feature allows the Lead-In Analytics Engine 200 to categorize the lead-in viewing related to each Demographic-Geographic grouping based on the percentage of the individual Lead-in video that the set-top box was tuned to.
(151) Additional detail on step Read Analysis Group Info file and Load to Array 460 follows:
(152) The Lead-In Analytics Engine 200 populates each of the fields as follows:
(153) LEAD-IN-ANALYSIS-GROUP-ID 4810 is populated from AGI-ANALYSIS-GROUP-ID 1310 in input file 120.
(154) LEAD-IN-MARKET 4800 is populated from ANALYSIS-GROUP-MARKET 1320 in input file 120.
(155) LEAD-IN-ANALYSIS-GROUP-DESC 4820 is populated from ANALYSIS-GROUP-DESC 1330 in input file 120.
(156) LEAD-IN-POTENTIAL-VIEWING-SECS 4830 is populated from POTENTIAL-VIEWING-SECONDS 1340 in input file 120.
(157) LEAD-IN-POTENTIAL-EXPOSURES 4850 is populated from POTENTIAL-EXPOSURES 1350 in input file 120.
(158) Additional detail on step Load Lead In Video Info Array 480 follows:
(159) The Lead-In Analytics Engine 200 populates each of the fields as follows:
(160) LEAD-ANALYSIS-PERIOD-ID 4880 is populated from LEAD-ANALYSIS-PERIOD-ID 1420 in input file 130.
(161) LEAD-CHANNEL-CALL-SIGN 4890 is populated from LEAD-CHANNEL-CALL-SIGN 1430 in input file 130.
(162) LEAD-VIDEO-PLAY-DATE 4900 is populated from LEAD-VIDEO-PLAY-DATE 1440 in input file 130.
(163) LEAD-VIDEO-PLAY-BEG-TIME 4910 is populated from LEAD-VIDEO-PLAY-BEG-TIME 1450 in input file 130.
(164) LEAD-VIDEO-PLAY-BEG-SEC-OF-DAY 4920 is populated from LEAD-VIDEO-PLAY-BEG-SEC-OF-DAY 1460 in input file 130.
(165) LEAD-VIDEO-PLAY-END-TIME 4930 is populated from LEAD-VIDEO-PLAY-END-TIME 1470 in input file 130.
(166) LEAD-VIDEO-PLAY-END-SEC-OF-DAY 4940 is populated from LEAD-VIDEO-PLAY-END-SEC-OF-DAY 1480 in input file 130.
(167) LEAD-IN-INDUSTRY-PROGRAM-ID 4950 is populated from LEAD-INDUSTRY-PROGRAM-ID 1510 in input file 130.
(168) LEAD-IN-INDUSTRY-ASSET-ID 4960 is populated from LEAD-INDUSTRY-ASSET-ID 1520 in input file 130.
(169) LEAD-IN-VIDEO-DURATION-SECS 4970 is populated from LEAD-VIDEO-DURATION-SECS 1490 in input file 130.
(170) LEAD-IN-SECS-FOR-EXPOSURE 4975 is populated from LEAD-SECS-FOR-EXPOSURE 1500 in input file 130.
(171) LEAD-VIDEO-DESC 4980 is populated from LEAD-VIDEO-DESC 1530 in input file 130.
(172) Additional detail on step Load Lead In Demo-Geo-Hist Info for Lead In Group 490 follows:
(173) The Lead-In Analytics Engine 200 populates each of the fields as follows:
(174) LEAD-RESLT-DEMOGRAPHIC-CODE 5050 is populated from LI-DEMOGRAPHIC-CODE 5810 in array in
(175) LEAD-RESLT-GEOGRAPHIC-CODE 5060 is populated from LI-GEOGRAPHIC-CODE 5830 in array in
(176) LEAD-RESLT-HISTOGRAM-INDEX 5070 is populated from LI-HISTOGRAM-INDEX 5850 in array in
(177) LEAD-RESLT-HISTOGRAM-BEG-PCT 5080 is populated from LI-HISTOGRAM-BEG-PCT 5870 in array in
(178) LEAD-RESLT-HISTOGRAM-END-PCT 5090 is populated from LI-HISTOGRAM-END-PCT 5880 in array in
(179) The source code for this routine can be found in the accompanying source code file as routines C130-LEAD-IN-VIDEO-PLAY-INFO and C132-LOAD-LEAD-IN-VIDEO-INFO and C136-LOAD-DEMO-GEO-HISTG which is included herein by reference.
(180)
(181) The process begins with Load Analysis Period Def Info Array 500. The process then executes Read and Load Analysis Period Target file 510 which reads file Analysis Period Target File 150 as input and loads the Analysis Period Target record to the array. Note that there is only one record in this file.
(182) The process then proceeds to Read Analysis Period Def file 520 where it reads file Analysis Period Def File 160 as input. The process checks for End of File 530. If it is the end of file, the process is Done 535. If End of File 530 does not detect an end of file condition, then the record that was read is loaded to the array using Load Analysis Period Def Array 540. While still working with this Analysis Period Definition record, the process then executes Load Demo-Geo-Hist Info for Result Group 550 which copies the set of Result Demographic-Geographic-Histogram definitions, that was loaded previously (reference
(183) The result is that each Analysis Period Definition ends up with the entire set of Result Demographic-Geographic-Histogram definitions and each such definition then ends up with the entire set of Channels to Analyze. Those Result Demographic-Geographic-Histogram definitions and the accompanying Channels to Analyze definitions will then be used later in the process by the Lead-In Analytics Engine 200 as it collects viewing data for each Analysis Period and groups it into the buckets defined by the Result Demographic-Geographic-Histogram definitions and then further groups that viewing into the channels viewed. This allows the Lead-In Analytics Engine 200 to categorize the Analysis Period viewing based on the Demographic-Geographic characteristics of the viewer and the Histogram breakouts and then to add another level of detail by collecting channel viewing information for that combination of Demographic-Geographic-Histogram.
(184) As a non-limiting example, if the Target is a baseball game and the Analysis Periods are the innings, and the analyst is tracking viewership by various demographic groups in ad zone XYZ across multiple channels, then the Lead-In Analytics Engine 200 has now populated the arrays in preparation for collecting this viewership information.
(185) Additional detail on step Read and Load Analysis Period Target file 510 follows:
(186) The Lead-In Analytics Engine 200 populates each of the fields as follows:
(187) AP-TARGET-CHANNEL 5160 is populated from AP-TRG-CHANNEL 1820 in input file 150.
(188) AP-POTENTIAL-VIEWING-SECONDS 5170 is populated from AP-POTENTIAL-VIEWING-SECOND 1830 in input file 150.
(189) AP-POTENTIAL-EXPOSURES 5180 is populated from AP-POTENTIAL-EXPOSURES 1840 in input file 150.
(190) AP-TARGET-IND-VIDEO-PGM-ID 5190 is populated from AP-TARGET-INDUSTRY-VIDEO-PROGRAM-ID 1850 in input file 150.
(191) AP-TARGET-IND-VIDEO-ASSET-ID 5200 is populated from AP-TARGET-INDUSTRY-VIDEO-ASSET-ID 1860 in input file 150.
(192) AP-TARGET-AIRING-DATE 5210 is populated from AP-TRG-AIRING-DATE 1870 in input file 150.
(193) AP-TARGET-AIRING-BEG-TIME 5220 is populated from AP-TRG-AIRING-BEG-TIME 1880 in input file 150.
(194) AP-TARGET-AIRING-END-TIME 5230 is populated from AP-TRG-AIRING-END-TIME 1900 in input file 150.
(195) AP-TARGET-AIRNG-BEG-SEC-OF-DAY 5240 is populated from AP-TRG-AIRNG-BEG-SEC-OF-DAY 1890 in input file 150.
(196) AP-TARGET-AIRNG-END-SEC-OF-DAY 5250 is populated from AP-TRG-AIRNG-END-SEC-OF-DAY 1910 in input file 150.
(197) AP-TARGET-MIN-SECS-VW-AT-START 5260 is populated from AP-TRG-MIN-SECS-VW-AT-START 1920 in input file 150.
(198) Additional detail on step Load Analysis Period Def Array 540 follows:
(199) The Lead-In Analytics Engine 200 populates each of the fields as follows:
(200) AP-DEF-DATE 5300 is populated from AP-DEF-DATE 2020 in input file 160.
(201) AP-DEF-BEG-TIME-HH-MM-SS-PM 5310 is populated from AP-DEF-BEG-TIME-HH-MM-SS 2030 in input file 160.
(202) AP-DEF-BEG-TIME-SEC-OF-DAY 5320 is populated from AP-DEF-BEG-TIME-SEC-OF-DAY 2040 in input file 160.
(203) AP-DEF-END-TIME-HH-MM-SS-PM 5330 is populated from AP-DEF-END-TIME-HH-MM-SS 2050 in input file 160.
(204) AP-DEF-END-TIME-SEC-OF-DAY 5340 is populated from AP-DEF-END-TIME-SEC-OF-DAY 2060 in input file 160.
(205) AP-DEF-PERIOD-DURATION-SECS 5350 is calculated for each analysis period as AP-DEF-END-TIME-SEC-OF-DAY 2060−AP-DEF-BEG-TIME-SEC-OF-DAY 2040+1.
(206) Additional detail on step Load Demo-Geo-Hist Info for Result Group 550 follows:
(207) The Lead-In Analytics Engine 200 populates each of the fields as follows copying them from the one array to the other array:
(208) ANALYS-RESLT-DEMOGRAPHIC-CODE 5390 is populated from RE-DEMOGRAPHIC-CODE 5910 in array in
(209) ANALYS-RESLT-GEOGRAPHIC-CODE 5400 is populated from RE-GEOGRAPHIC-CODE 5930 in array in
(210) ANALYS-RESLT-HISTOGRAM-INDEX 5410 is populated from RE-HISTOGRAM-INDEX 5950 in array in
(211) ANALYS-RESLT-HISTOGRAM-BEG-PCT 5420 is populated from RE-HISTOGRAM-BEG-PCT 5970 in array in
(212) ANALYS-RESLT-HISTOGRAM-END-PCT 5430 is populated from RE-HISTOGRAM-END-PCT 5980 in array in
(213) Additional detail on step Load Channels for Result Group 560 follows:
(214) The Lead-In Analytics Engine 200 populates this field as follows copying it from the one array to the other array:
(215) ANALYS-RES-CHANNEL-CALL-SIGN 5500 is populated from CHAN-TO-ANALYZE-CALL-SIGN 6010 in array in
(216) The source code for this routine can be found in the accompanying source code file as routines C140-INIT-ANALYSIS-PERIOD-DEF and C142-INIT-ANALYSIS-PERIOD-DEF and C146-LOAD-DEMO-GEO-HISTG and C148-LOAD-CHANNELS which is included herein by reference.
(217)
(218) The end result of this process is that the Lead-In Analytics Engine 200 has loaded the Tuning Data Dates data into an array in the memory of the computer running the engine. The analyst uses the Tuning Data Dates file 190 to tell the Lead-In Analytics Engine 200 which tuning records in the Channel Tuning File have data that is of interest to the study. In the case where the Channel Tuning Data file has channel tune data from multiple dates, this allows the analyst to restrict the analysis to the data which the analyst deems significant.
(219) Additional detail on step Load Tuning Data Dates Array 590 follows:
(220) The Lead-In Analytics Engine 200 populates each of the fields as follows:
(221) CVIEW-VIEWING-DATE 4300 is populated from TUNING-DATA-DATE 2510 in file Tuning Data Dates File 190.
(222) The source code for this routine can be found in the accompanying source code file as routines C170-TUNING-DATA-DATES and C172-TUNING-DATA-DATES which is included herein by reference.
(223)
(224) The process begins with Process Channel Tuning File 600. The process then executes Read Channel Tuning File 610 which reads file Channel Tune File 110 as input. The process checks for End of File 620. If it is the end of file, the process is Done 625. If End of File 620 does not detect an end of file condition, then the Lead-In Analytics Engine 200 compares the set-top box id 630 to the id of the previous record to determine if the set-top box id has changed. When the set-top box id is the same, the Lead-In Analytics Engine 200 loads the channel tuning information represented in that record to an array in the memory of the computer as defined in Load Channel Tuning Data to Chan-Viewing-Detail Array 660. See
(225) The Lead-In Analytics Engine 200 then proceeds to read the next record in the file repeating the process. The result of this interim step is that all of the channel tuning data for this set-top box has been loaded to an array in the memory of the computer. See
(226) When the Lead-In Analytics Engine 200 detects that a different set-top box has been read (based on a change in the set-top box identifier), it begins the tabulation process. The Lead-In Analytics Engine 200 first executes step Tabulate Lead In Viewing 635 which tabulates all of the viewing by this set-top box for each of the lead-in periods that were defined for this Study. See
(227) After tabulating the Lead-in viewing, the Lead-In Analytics Engine 200 then sets the histogram index which categorizes this set-top box into a histogram bucket based on the aggregate viewing during all of the Lead-in periods combined. This is done by executing Set Histogram Index from Lead In Viewing 640. The purpose for this is to group Analysis Period viewing based on similar amounts of overall lead-in viewing.
(228) After identifying the proper histogram bucket, the Lead-In Analytics Engine 200 then tabulates the analysis period viewing by executing Tabulate Analysis Period Target Viewing 645. See
(229) At this point the Lead-In Analytics Engine 200 has completed tabulating all of the viewing for this set-top box. The next step is to initialize the channel tuning array in preparation for processing the data for the next set-top box (the one with the new id). This is done by executing Initialize Channel Tuning Array 650. Once the channel tuning array is initialized, the Lead-In Analytics Engine 200 can load the Channel Tuning Data for the new set-top box into the array, thus resuming the process.
(230)
(231) Each time the Lead-In Analytics Engine 200 detects a new set-top box id in routine If new set-top box id, load identifying fields to CHAN-VIEWING-DETAIL Array 665, it populates the identifying fields in the CHAN-VIEWING-DETAIL array as follows:
(232) CVIEW-MARKET 4200 is populated from MARKET 1010 in Channel Tune File 110.
(233) CVIEW-SET-TOP-BOX-ID 4210 is populated from SET-TOP-BOX-ID 1050 in Channel Tune File 110.
(234) CVIEW-DEMOGRAPHIC-CODE 4220 is populated from DEMOGRAPHIC-CODE 1220 in Channel Tune File 110.
(235) CVIEW-GEOGRAPHIC-CODE 4230 is populated from GEOGRAPHIC-CODE 1230 in Channel Tune File 110.
(236) The process then executes Loop Thru CHAN-VIEWING-DETAIL Array Dates to Find Match on Tuning Date 670. In this process the program is looping thru the dates that were loading to the CHAN-VIEWING-DETAIL array by the process described in
(237) If the Channel Tune Date (field Tune-in-date 1090) does not match any of the dates in the CHAN-VIEWING-DETAIL array, then this Channel Tuning record is ignored; reference procedure: Done (Tuning Record is Ignored) 685.
(238) If the Channel Tune Date (field Tune-in-date 1090) does match one of the dates in the CHAN-VIEWING-DETAIL array (field CVIEW-Viewing-date 4300), then the viewing activity represented in this Channel Tuning record is loaded to the array by process Loop from Tune In Second to Tune Out Second Setting Channel Viewed in CHAN-VIEWING-DETAIL array 690. Upon successful completion of loading the Channel Tuning Data to the CHAN-VIEWING-DETAIL array, Done 695, returns control to the main routine where the next channel tuning record is read.
(239) The end result of this process is that the Lead-In Analytics Engine 200 has loaded all of the required Channel Tuning Data for one set-top box into the CHAN-VIEWING-DETAIL array in the memory of the computer running the Lead-In Analytics Engine 200. The required data is that data where the Channel Tune Date matches a date that the analyst has defined for this study. The array structure provides one bucket for every second of the day with said bucket identifying the channel to which the set-top box was tuned; this array contains multiple days of tuning data thus allowing the Lead-In Analytics Engine 200 to analyze second-by-second level tuning activity for the set-top box over an extended period of time thus providing Longitudinal viewing analysis at a second-by-second level.
(240) Additional detail on step Loop Thru CHAN-VIEWING-DETAIL Array Dates to Find Match on Tuning Date 670 follows:
(241) The Lead-In Analytics Engine 200 identifies the correct date in the channel viewing array using a routine like this:
(242) TABLE-US-00004 PERFORM VARYING CVIEW-DATE-SUB FROM 1 BY 1 UNTIL TUNE-IN-DATE 1090 = CVIEW-VIEWING-DATE(CVIEW-DATE-SUB) 4300 Or no match is found END-PERFORM
(243) Additional detail on step Loop from Tune In Second to Tune Out Second Setting Channel Viewed in CHAN-VIEWING-DETAIL array 690 follows:
(244) The Lead-In Analytics Engine 200 populates the second-by-second viewing activity using a routine like this:
(245) TABLE-US-00005 PERFORM VARYING CVIEW-SEC-SUB FROM TUNE-IN-SECOND-OF-DAY 1120 BY 1 UNTIL CVIEW-SEC-SUB > TUNE-OUT-SECOND-OF-DAY 1160 MOVE CHANNEL-CALL-SIGN 1170 TO CVIEW-CHANNEL-CALL-SIGN (CVIEW-DATE-SUB, CVIEW-SEC-SUB) 4330 END-PERFORM
(246) The source code for this routine can be found in the accompanying source code file as routines D000-PREP-CHAN-TUNING-FILE and D100-PROCESS-CHAN-TUNING-FILE and the various routines called by D100-PROCESS-CHAN-TUNING-FILE, which is included herein by reference.
(247)
(248) The Lead-In and related data was loaded to the LEAD-IN-AND-TARGET-INFO array defined in
(249) The Channel Tuning Data was loaded to the CHAN-VIEWING-DETAIL array defined in
(250) The process begins with Tabulate Lead In Viewing 700. Prior to calling this routine, the Lead-In Analytics Engine 200 has already read all of the Channel Tuning records for a set-top box and loaded them to the CHAN-VIEWING-DETAIL Array as described in
(251) The process then executes Loop Thru Lead In Viewing Array Rows 710. In this process the program is looping thru the array rows that define the lead in periods. If there are no more rows, the program proceeds to Done 725. If there are more rows, then the program proceeds to Loop Thru Channel Tuning Array to Find Match on Channel Tuning Date in Channel Tuning Array and Lead In Date 730 where the Lead-In Analytics Engine 200 compares the date of the channel tuning activity (Viewing-date 4300) with the date of the Lead-in period (LEAD-VIDEO-PLAY-DATE 4900) to determine if there is a match.
(252) When Found Matching Date 740 is not true, the program proceeds to 710 to get the next lead-in period.
(253) When Found Matching Date 740 is true, the program proceeds to Loop Thru Channel Tuning Data from Lead In Beg to Lead In End Tallying Viewing Seconds 750 tallying the viewing seconds by the set-top box during this lead-in period.
(254) After tallying the viewing seconds, the program proceeds to Loop Thru Lead In Histogram to locate proper bucket for Lead In Viewing Seconds 760 where it loops through the Histogram definitions to find the proper histogram into which to categorize the set-top box's lead-in period viewing.
(255) Once the proper Histogram identifier is found, the program proceeds to Loop Thru Lead In Demo-Geo-Hist to locate proper Demo-Geo-Hist and add Lead In Viewing Seconds to that row 770 where the program loops through each of the Demographic-Geographic-Histogram groupings defined for this lead-in period with the objective of finding the proper bucket into which to tally this set-top box's lead-in viewing. The program is looking for the Demographic-Geographic-Histogram grouping where the set-top box Demographic identifier 4220 matches the lead-in period Demographic identifier 5050, and the set-top box Geographic identifier 4230 matches the lead-in period Geographic identifier 5060 and the Histogram bucket that was identified in 760 matches the one in the Lead-in period 5070.
(256) Once the proper row is found, the viewing seconds are tabulated as defined in the program. Reference procedure: E140-TALLY-LEAD-IN-VIEWING in the accompanying source code file which is included herein by reference.
(257) At this point the Lead-In Analytics Engine 200 is done tallying lead-in period viewing for this lead-in period for this set-top box. It will now proceed to the next lead-in period as described in Loop Thru Lead In Viewing Array Rows 710.
(258) Additional detail on step Loop Thru Channel Tuning Data from Lead In Beg to Lead In End Tallying Viewing Seconds 750 follows:
(259) The Lead-In Analytics Engine 200 tallies the lead in viewing using a routine like this:
(260) TABLE-US-00006 MOVE 0 TO LEAD-IN-SECONDS-VIEWED-COUNTER. MOVE 0 TO LEAD-IN-EXPOSURES-COUNTER. PERFORM VARYING CVIEW-SEC-SUB FROM LEAD-VIDEO-PLAY-BEG-SEC-OF-DAY(LI-SUB) 4920 BY 1 UNTIL CVIEW-SEC-SUB > LEAD-VIDEO-PLAY-END-SEC-OF-DAY(LI-SUB) 4940 IF CVIEW-CHANNEL-CALL-SIGN (CVIEW-DATE-SUB, CVIEW-SEC-SUB) 4330 = LEAD-CHANNEL-CALL-SIGN(LI-SUB) 4890 ADD 1 TO LEAD-IN-SECONDS-VIEWED-COUNTER ADD 1 TO AGGR-ALL-LEAD-IN-VIEW-SECS END-IF END-PERFORM.
(261) Calculate the number of set-top boxes tuned in at the beginning of the lead-in period.
(262) TABLE-US-00007 IF CVIEW-CHANNEL-CALL-SIGN 4330 (CVIEW-DATE-SUB, LEAD-VIDEO-PLAY-BEG-SEC-OF-DAY(LI-SUB) 4920) = LEAD-CHANNEL-CALL-SIGN(LI-SUB) 4890 ADD 1 TO LEAD-IN-STB-COUNT-AT-BEG(LI-SUB) 5020 END-IF
(263) Calculate the number of set-top boxes tuned in at the end of the lead-in period.
(264) TABLE-US-00008 IF CVIEW-CHANNEL-CALL-SIGN 4330 (CVIEW-DATE-SUB, LEAD-VIDEO-PLAY-END-SEC-OF-DAY(LI-SUB) 4940) = LEAD-CHANNEL-CALL-SIGN(LI-SUB) 4890 ADD 1 TO LEAD-IN-STB-COUNT-AT-END(LI-SUB) 5030 END-IF
(265) Calculate the number of set-top boxes tuned in for the entire lead-in period.
(266) TABLE-US-00009 IF LEAD-IN-SECONDS-VIEWED-COUNTER = LEAD-IN-VIDEO-DURATION-SECS (LI-SUB) 4970 ADD 1 TO LEAD-IN-STB-COUNT-VIEW-ALL(LI-SUB) 5040 END-IF. IF LEAD-IN-SECONDS-VIEWED-COUNTER > LEAD-IN-SECS-FOR-EXPOSURE (LI-SUB) 4975 MOVE 1 TO LEAD-IN-EXPOSURES-COUNTER END-IF.
(267) Additional detail on step Loop Thru Lead In Histogram to locate proper bucket for Lead In Viewing Seconds 760 follows:
(268) The Lead-In Analytics Engine 200 locates the proper histogram bucket for lead in viewing using a routine like shown below and then it tallies the lead-in viewing as shown:
(269) TABLE-US-00010 COMPUTE PCT-OF-LEAD-IN-VIEWING = (LEAD-IN-SECONDS-VIEWED-COUNTER / LEAD-IN-VIDEO-DURATION-SECS(LI-SUB)) 4970 * 100 PERFORM VARYING LEAD-RES-SUB FROM 1 BY 1 UNTIL FOUND-HISTOGRAM-MATCH = “Y” OR LEAD-RES-SUB > LI-DEMO-GEO-HISTG-ROWS-LOADED IF CVIEW-DEMOGRAPHIC-CODE 4220 = LEAD-RESLT-DEMOGRAPHIC-CODE (LI-SUB, LEAD-RES-SUB) 5050 AND CVIEW-GEOGRAPHIC-CODE 4230 = LEAD-RESLT-GEOGRAPHIC-CODE (LI-SUB, LEAD-RES-SUB) 5060 AND PCT-OF-LEAD-IN-VIEWING >= LEAD-RESLT-HISTOGRAM-BEG-PCT (LI-SUB, LEAD-RES-SUB) 5080 AND PCT-OF-LEAD-IN-VIEWING <= LEAD-RESLT-HISTOGRAM-END-PCT (LI-SUB, LEAD-RES-SUB) 5090 MOVE “Y” TO FOUND-HISTOGRAM-MATCH
(270) At this point, tally the lead in viewing using logic like this:
(271) TABLE-US-00011 COMPUTE LEAD-RESLT-STB-COUNT (LI-SUB, LEAD-RES-SUB) 5100 = LEAD-RESLT-STB-COUNT (LI-SUB, LEAD-RES-SUB) 5100 + 1 COMPUTE LEAD-RESLT-AGGR-VIEW-SECS (LI-SUB, LEAD-RES-SUB) 5110 = LEAD-RESLT-AGGR-VIEW-SECS (LI-SUB, LEAD-RES-SUB) 5110 + LEAD-IN-SECONDS-VIEWED-COUNTER COMPUTE LEAD-RESLT-EXPOSURES (LI-SUB, LEAD-RES-SUB) 5120 = LEAD-RESLT-EXPOSURES (LI-SUB, LEAD-RES-SUB) 5120 + LEAD-IN-EXPOSURES-COUNTER
(272) Calculate the number of set-top boxes tuned in at the beginning of the lead-in period for this demographic-geographic-histogram group.
(273) TABLE-US-00012 IF CVIEW-CHANNEL-CALL-SIGN 4330 (CVIEW-DATE-SUB, LEAD-VIDEO-PLAY-BEG-SEC-OF-DAY(LI-SUB) 4920) = LEAD-CHANNEL-CALL-SIGN(LI-SUB) 4890 ADD 1 TO LEAD-RES-STB-COUNT-AT-BEG (LI-SUB, LEAD-RES-SUB) 5130 END-IF
(274) Calculate the number of set-top boxes tuned in at the end of the lead-in period for this demographic-geographic-histogram group.
(275) TABLE-US-00013 IF CVIEW-CHANNEL-CALL-SIGN 4330 (CVIEW-DATE-SUB, LEAD-VIDEO-PLAY-END-SEC-OF-DAY(LI-SUB) 4940) = LEAD-CHANNEL-CALL-SIGN(LI-SUB) 4890 ADD 1 TO LEAD-RES-STB-COUNT-AT-END (LI-SUB, LEAD-RES-SUB) 5140 END-IF
(276) Calculate the number of set-top boxes tuned in for the entire lead-in period for this demographic-geographic-histogram group.
(277) TABLE-US-00014 IF LEAD-IN-SECONDS-VIEWED-COUNTER = LEAD-IN-VIDEO-DURATION-SECS (LI-SUB) 4970 ADD 1 TO LEAD-RES-STB-COUNT-VIEW-ALL (LI-SUB, LEAD-RES-SUB) 5150 END-IF. END-IF END-PERFORM
(278)
(279) The Analysis Period Result and related data was loaded to the LEAD-IN-AND-TARGET-INFO array defined in
(280) The Channel Tuning Data was loaded to the CHAN-VIEWING-DETAIL array defined in
(281) The process begins with Tabulate Analysis Period Target Viewing 800. It then proceeds to Set Result Histogram Index based on Aggregate Lead In Viewing Seconds 810 which sets the histogram index that will be used to group Analysis Period Result viewership. In this process the Lead-In Analytics Engine 200 is identifying the proper histogram bucket to use by comparing the aggregate lead-in period viewing with the histogram definitions that were defined for Result (Target) period viewing.
(282) Once the proper histogram index is identified, the program proceeds to Loop Thru Analysis Period Definition Array Rows 820 where it loops thru the Analysis Period definitions in the array. This is where the analyst has defined the individual analysis periods for which the system is to track viewing during the overall Target Analysis Period.
(283) The program then checks for More rows 824. When there are no more Analysis Period Definitions, the process is Done 828. When there are more rows, it proceeds to step Loop Thru Analysis Period Result (Result Demo-Geo-Hist) rows in Array to Find Match on Demo-Geo-Hist in Channel Tuning Data and Demo-geo-Hist in Result Array 830 where the program looks for a match on the Demographic-Geographic-Histogram values. The program is looking for the Demographic-Geographic-Histogram grouping where the set-top box Demographic identifier 4220 matches the Analysis period Demographic identifier 5390, and the set-top box Geographic identifier 4230 matches the Analysis period Geographic identifier 5400 and the Histogram bucket that was identified in 810 matches the one in the Analysis period 5410.
(284) When Found Matching Demo-Geo-Hist? 840 results in No, the program returns control to Loop Thru Analysis Period Definition Array Rows 820. When a match is found, control passes to Loop Thru Analysis Period Result Channels to Analyze 850 where the program loops thru each of the channels that the analyst has specified to be analyzed (this list was loaded by the process in
(285) Once the matching date is found, the Lead-In Analytics Engine 200 runs procedure Loop Thru Channel Tuning Data from Result Beg Sec to Result End Sec Tallying Viewing Seconds 870 where the Engine 200 tabulates viewing of that channel during the Analysis period by looping from the result beginning second to the result ending second tallying viewing seconds of where the channel in ANALYS-RES-CHANNEL-CALL-SIGN 5500 matches the channel in CVIEW-CHANNEL-CALL-SIGN 4330.
(286) When the program finishes tallying the viewing seconds, it returns control to Loop Thru Analysis Period Definition Array Rows 820.
(287) Additional detail on step Set Result Histogram Index based on Aggregate Lead In Viewing Seconds 810 follows:
(288) The Lead-In Analytics Engine 200 locates the proper histogram bucket for result viewing and then sets the desired values using a routine like shown below:
(289) TABLE-US-00015 COMPUTE PCT-OF-ALL-LEAD-IN-VIEWING = (CVIEW-1-LEAD-IN-AGGR-VIEW-SECS 4280 / LEAD-CALCULATED-POT-VIEW-SECS) 4840 * 100 PERFORM VARYING DGH-SUB FROM 1 BY 1 UNTIL FOUND-HISTOGRAM-MATCH = “Y” OR DGH-SUB > RE-DEMO-GEO-HISTG-ROWS-LOADED IF PCT-OF-ALL-LEAD-IN-VIEWING >= RE-HISTOGRAM-BEG-PCT(DGH-SUB) 5970 AND PCT-OF-ALL-LEAD-IN-VIEWING <= RE-HISTOGRAM-END-PCT(DGH-SUB) 5980 MOVE “Y” TO FOUND-HISTOGRAM-MATCH MOVE RE-HISTOGRAM-INDEX(DGH-SUB) 5950 TO CVIEW-HISTOGRAM-INDEX 4240 MOVE RE-HISTOGRAM-BUCKET-NAME(DGH-SUB) 5960 TO CVIEW-HISTOGRAM-DESC 4250 MOVE RE-HISTOGRAM-BEG-PCT(DGH-SUB) 5970 TO CVIEW-HISTOGRAM-BEG-PCT 4260 MOVE RE-HISTOGRAM-END-PCT(DGH-SUB) 5980 TO CVIEW-HISTOGRAM-END-PCT 4270 END-IF END-PERFORM.
(290) Claims Reference:
(291) In this process the Lead-In Analytics Engine 200 has identified the target histogram bucket for this video asset viewing device based on the aggregate lead-in viewing by this device across the various lead-in periods. This allows the Lead-In Analytics Engine 200 to correlate lead-in viewing activity for a video asset viewing device with target viewing activity for that device and to group the target viewing activity for the device with other video asset viewing devices that had a similar amount of aggregate viewing of the lead-in video assets.
(292) Additional detail on step Loop Thru Channel Tuning Array to Find Match on Channel Tuning Date in Channel Tuning Array and Result Date 860 follows:
(293) The Lead-In Analytics Engine 200 locates the proper date where the channel tuning data matches the result viewing data using a routine like shown below:
(294) TABLE-US-00016 PERFORM VARYING CVIEW-DATE-SUB FROM 1 BY 1 UNTIL AP-DEF-DATE(AP-DEF-SUB) 5300 = CVIEW-VIEWING-DATE(CVIEW-DATE-SUB) 4300 Or no more rows END-PERFORM
(295) Additional detail on step Loop Thru Channel Tuning Data from Result Beg Sec to Result End Sec Tallying Viewing Seconds 870 follows:
(296) The Lead-In Analytics Engine 200 tabulates the detail channel viewing during the analysis result period using a routine like shown below:
(297) TABLE-US-00017 MOVE 0 TO ANALYSIS-PERIOD-CHAN-VIEW-SECS PERFORM VARYING CVIEW-SEC-SUB FROM AP-DEF-BEG-TIME-SEC-OF-DAY(AP-DEF-SUB) 5320 BY 1 UNTIL CVIEW-SEC-SUB > AP-DEF-END-TIME-SEC-OF-DAY(AP-DEF-SUB) 5340 IF CVIEW-CHANNEL-CALL-SIGN(CVIEW-DATE-SUB, CVIEW-SEC-SUB) 4330 = ANALYS-RES-CHANNEL-CALL-SIGN (AP-DEF-SUB, AP-RES-SUB, CTA-SUB) 5500 COMPUTE ANALYS-RES-AGGR-CHAN-VIEW-SECS (AP-DEF-SUB, AP-RES-SUB, CTA-SUB) 5510 = ANALYS-RES-AGGR-CHAN-VIEW-SECS (AP-DEF-SUB, AP-RES-SUB, CTA-SUB) 5510 + 1 ADD 1 TO ANALYSIS-PERIOD-CHAN-VIEW-SECS ADD 1 TO AGGR-ALL-RES-HISTG-CHN-VW-SECS END-IF END-PERFORM. IF ANALYSIS-PERIOD-CHAN-VIEW-SECS > AP-TARGET-MIN-SECS-VW-AT-START 5260 COMPUTE ANALYS-RES-CHAN-EXPOSURES (AP-DEF-SUB, AP-RES-SUB, CTA-SUB) 5520 = ANALYS-RES-CHAN-EXPOSURES (AP-DEF-SUB, AP-RES-SUB, CTA-SUB) 5520 + 1 END-IF. IF ANALYSIS-PERIOD-CHAN-VIEW-SECS > 0 COMPUTE ANALYS-RES-STB-ANY-VIEWING (AP-DEF-SUB, AP-RES-SUB, CTA-SUB) 5530 = ANALYS-RES-STB-ANY-VIEWING (AP-DEF-SUB, AP-RES-SUB, CTA-SUB) 5530 + 1 END-IF.
(298) Claims Reference:
(299) Both
(300)
(301) The LEAD-IN-AND-TARGET-INFO array defined in
(302) The process begins with Calculate Result Viewing Rollups 900. In this process the Lead-In Analytics Engine 200 is performing various aggregations which will summarize the detail viewing data calculated at the Channel level to higher levels.
(303) The step Loop Thru Analysis Period Definition Array Rows 910 loops thru each of the Analysis Period definition rows in the array. The process performs More rows? 914 where it checks for more rows in the array. When there are no more rows, Done 918 is executed. When the are more rows, then control passes to Loop Thru Analysis Period Result (Result Demo-Geo-Hist) rows in Array doing Calculations 920 where the process loops thru each of the Result Demographic-Geographic-Histogram rows performing various calculations as defined in the source code which is included herein by reference.
(304) The next step is Loop Thru Analysis Period Result Channels to Analyze doing first pass Calculations 930 where the program loops thru the Analysis Period Result Channels doing a first pass of calculations as defined in the source code which is included herein by reference. The first pass is performing various aggregations.
(305) After the first pass calculations are completed, the program proceeds to Loop Thru Analysis Period Result Channels to Analyze doing second pass Calculations 940 where a second pass of calculations is completed as defined in the source code which is included herein by reference. The second pass is calculating percentage of viewing using the aggregated values calculated in the first pass.
(306) Additional detail on this step follows:
(307) The Lead-In Analytics Engine 200 tabulates various aggregations for the analysis result period using a routine like shown below:
(308) TABLE-US-00018 PERFORM loop thru Analysis Period Def Rows VARYING AP-DEF-SUB FROM 1 BY 1 UNTIL AP-DEF-SUB > ANALYSIS-PERIOD-ROWS-LOADED PERFORM loop thru Analysis Result Rows (Demo-Geo-Histg) VARYING AP-RES-SUB FROM 1 BY 1 UNTIL AP-RES-SUB > RE-DEMO-GEO-HISTG-ROWS-LOADED PERFORM loop thru Channels VARYING CTA-SUB FROM 1 BY 1 UNTIL CTA-SUB > CHAN-TO-ANALYZE-ROWS-LOADED calculate the totals (rollups) needed to calculate the percent of viewing that this channel got. COMPUTE ANALYS-RESLT-TOT-CHAN-VIEW-SEC (AP-DEF-SUB, AP-RES-SUB) 5440 = ANALYS-RESLT-TOT-CHAN-VIEW-SEC (AP-DEF-SUB, AP-RES-SUB) 5440 + ANALYS-RES-AGGR-CHAN-VIEW-SECS (AP-DEF-SUB, AP-RES-SUB, CTA-SUB) 5510 COMPUTE ANALYS-RESLT-TOT-CHAN-EXPOSURE (AP-DEF-SUB, AP-RES-SUB) 5450 = ANALYS-RESLT-TOT-CHAN-EXPOSURE (AP-DEF-SUB, AP-RES-SUB) 5450 + ANALYS-RES-CHAN-EXPOSURES (AP-DEF-SUB, AP-RES-SUB, CTA-SUB) 5520 COMPUTE ANALYS-RESLT-TOT-STB-ANY-VIEW (AP-DEF-SUB, AP-RES-SUB) 5460 = ANALYS-RESLT-TOT-STB-ANY-VIEW (AP-DEF-SUB, AP-RES-SUB) 5460 + ANALYS-RES-STB-ANY-VIEWING (AP-DEF-SUB, AP-RES-SUB, CTA-SUB) 5530 COMPUTE AP-DEF-TOT-CHAN-VIEW-SEC (AP-DEF-SUB) 5360 = AP-DEF-TOT-CHAN-VIEW-SEC (AP-DEF-SUB) 5360 + ANALYS-RES-AGGR-CHAN-VIEW-SECS (AP-DEF-SUB, AP-RES-SUB, CTA-SUB) 5510 COMPUTE AP-DEF-TOT-CHAN-EXPOSURE (AP-DEF-SUB) 5370 = AP-DEF-TOT-CHAN-EXPOSURE (AP-DEF-SUB) 5370 + ANALYS-RES-CHAN-EXPOSURES (AP-DEF-SUB, AP-RES-SUB, CTA-SUB) 5520 COMPUTE AP-DEF-TOT-STB-ANY-VIEW (AP-DEF-SUB) 5380 = AP-DEF-TOT-STB-ANY-VIEW (AP-DEF-SUB) 5380 + ANALYS-RES-STB-ANY-VIEWING (AP-DEF-SUB, AP-RES-SUB, CTA-SUB) 5530 Aggregate values for the entire Target viewing period. COMPUTE AP-TARGET-AGGR-ACTUAL-VIEW-SEC 5280 = AP-TARGET-AGGR-ACTUAL-VIEW-SEC 5280 + ANALYS-RES-AGGR-CHAN-VIEW-SECS (AP-DEF-SUB, AP-RES-SUB, CTA-SUB) 5510 COMPUTE AP-TARGET-AGGR-ACTUL-EXPOSURES 5290 = AP-TARGET-AGGR-ACTUL-EXPOSURES 5290 + ANALYS-RES-CHAN-EXPOSURES (AP-DEF-SUB, AP-RES-SUB, CTA-SUB) 5520 END-PERFORM end loop thru channels part 1 Now that we have calculated the total viewing seconds for this Demo-Geo-Histg, calculate the percent of viewing that this channel got from all the viewing for this Demo-Geo-Hist. PERFORM loop thru Channels VARYING CTA-SUB FROM 1 BY 1 UNTIL CTA-SUB > CHAN-TO-ANALYZE-ROWS-LOADED IF ANALYS-RESLT-TOT-CHAN-VIEW-SEC (AP-DEF-SUB, AP-RES-SUB) 5440 > 0 COMPUTE CHAN-PCT-SHARE-OF-VIEWING (AP-DEF-SUB, AP-RES-SUB, CTA-SUB) 5540 = ANALYS-RES-AGGR-CHAN-VIEW-SECS (AP-DEF-SUB, AP-RES-SUB, CTA-SUB) 5510 / ANALYS-RESLT-TOT-CHAN-VIEW-SEC (AP-DEF-SUB, AP-RES-SUB) 5440 * 100 ELSE MOVE 0 TO CHAN-PCT-SHARE-OF-VIEWING (AP-DEF-SUB, AP-RES-SUB, CTA-SUB) 5540 END-IF END-PERFORM end loop thru channels part 2 END-PERFORM end loop thru Analysis Result Rows (Demo-Geo-Histg) COMPUTE AP-TARGET-AGGR-EXPECT-VIEW-SEC 5270 = AP-TARGET-AGGR-EXPECT-VIEW-SEC 5270 + AP-DEF-TOT-CHAN-EXPOSURE (AP-DEF-SUB) 5370 * (AP-DEF-END-TIME-SEC-OF-DAY(AP-DEF-SUB) 5340 − .sup. AP-DEF-BEG-TIME-SEC-OF-DAY(AP-DEF-SUB) 5320 + 1) END-PERFORM. .sup. End loop thru Analysis Period Def Rows
(309)
(310) The LEAD-IN-AND-TARGET-INFO array defined in
(311) The process begins with Write Output Files 1000. The Lead-In Analytics Engine 200 will perform process Write Analysis Group File 1010 where it will write the Analysis Group information to file Analysis Group File 210 using data in the LEAD-IN-AND-TARGET-INFO array which was described in
(312) The field mapping is as follows:
(313) ANALYSIS-GROUP-ID 3010 is populated from LEAD-IN-ANALYSIS-GROUP-ID 4810 from array in
(314) ANALYSIS-GROUP-MARKET 3020 is populated from LEAD-IN-MARKET 4800 from array in
(315) ANALYSIS-GROUP-DESC 3030 is populated from LEAD-IN-ANALYSIS-GROUP-DESC 4820 from array in
(316) POTENTIAL-VIEWING-SECONDS 3040 is populated from LEAD-IN-POTENTIAL-VIEWING-SECS 4830 from array in
(317) POTENTIAL-EXPOSURES 3050 is populated from LEAD-IN-POTENTIAL-EXPOSURES 4850 from array in
(318) AGGREGATE-VIEWING-ALL-STB 3060 is populated from LEAD-IN-AGGR-VIEWING-ALL-STB 4860 from array in
(319) AGGREGATE-EXPOSURES-ALL-STB 3070 is populated from LEAD-IN-AGGR-EXPOSURES-ALL-STB 4870 from array in
(320) The Lead-In Analytics Engine 200 will then perform process Write Analysis Lead In Period Definition Result 1020 where will it will write the Analysis Lead In Period File 220 which contains the information about the Lead-In period(s) that were defined by the analyst for the study.
(321) The field mapping is as follows:
(322) ANALYSIS-GROUP-ID 3105 is populated from LEAD-IN-ANALYSIS-GROUP-ID 4810 from array in
(323) ANALYSIS-PERIOD-ID 3110 is populated from LEAD-ANALYSIS-PERIOD-ID 4880 from array in
(324) CHANNEL-CALL-SIGN 3115 is populated from LEAD-CHANNEL-CALL-SIGN 4890 from array in
(325) VIDEO-PLAY-DATE 3120 is populated from LEAD-VIDEO-PLAY-DATE 4900 from array in
(326) VIDEO-PLAY-BEG-TIME 3125 is populated from LEAD-VIDEO-PLAY-BEG-TIME 4910 from array in
(327) VIDEO-PLAY-BEG-SEC-OF-DAY 3130 is populated from LEAD-VIDEO-PLAY-BEG-SEC-OF-DAY 4920 from array in
(328) VIDEO-PLAY-END-TIME 3135 is populated from LEAD-VIDEO-PLAY-END-TIME 4930 from array in
(329) VIDEO-PLAY-END-SEC-OF-DAY 3140 is populated from LEAD-VIDEO-PLAY-END-SEC-OF-DAY 4940 from array in
(330) VIDEO-DURATION-SECS 3145 is populated from LEAD-IN-VIDEO-DURATION-SECS 4970 from array in
(331) LEAD-IN-SECS-FOR-EXPOSURE 3150 is populated from LEAD-IN-SECS-FOR-EXPOSURE 4975 from array in
(332) INDUSTRY-PROGRAM-ID 3155 is populated from LEAD-IN-INDUSTRY-PROGRAM-ID 4950 from array in
(333) INDUSTRY-ASSET-ID 3160 is populated from LEAD-IN-INDUSTRY-ASSET-ID 4960 from array in
(334) VIDEO-DESC 3165 is populated from LEAD-VIDEO-DESC 4980 from array in
(335) STB-COUNT 3170 is populated from LEAD-IN-STB-COUNT 4990 from array in
(336) AGGR-VIEW-SECS 3175 is populated from LEAD-IN-AGGR-VIEW-SECS 5000 from array in
(337) EXPOSURES 3180 is populated from LEAD-IN-EXPOSURES 5010 from array in
(338) STB-TUNED-AT-BEG-OF-LEAD-IN-CNT 3185 is populated from LEAD-IN-STB-COUNT-AT-BEG 5020 from array in
(339) STB-TUNED-AT-END-OF-LEAD-IN-CNT 3190 is populated from LEAD-IN-STB-COUNT-AT-END 5030 from array in
(340) STB-TUNE-FOR-ALL-OF-LEAD-IN-CNT 3195 is populated from LEAD-IN-STB-COUNT-VIEW-ALL 5040 from array in
(341) The Lead-In Analytics Engine 200 will then perform process Write Lead In Viewing Result File 1030 where it will write the Lead In Viewing Result File 230 which contains information about the viewing that occurred during the Lead-In period. This viewing is broken down into the Demographic-Geographic-Histogram segments that the Analysis defined for this study.
(342) The field mapping is as follows:
(343) ANALYSIS-GROUP-ID 3205 is populated from LEAD-IN-ANALYSIS-GROUP-ID 4810 from array in
(344) ANALYSIS-PERIOD-ID 3210 is populated from LEAD-ANALYSIS-PERIOD-ID 4880 from array in
(345) CHANNEL-CALL-SIGN 3215 is populated from LEAD-CHANNEL-CALL-SIGN 4890 from array in
(346) VIDEO-PLAY-DATE 3220 is populated from LEAD-VIDEO-PLAY-DATE 4900 from array in
(347) VIDEO-PLAY-BEG-TIME 3225 is populated from LEAD-VIDEO-PLAY-BEG-TIME 4910 from array in
(348) LEAD-IN-DEMOGRAPHIC-CODE 3230 is populated from LEAD-RESLT-DEMOGRAPHIC-CODE 5050 from array in
(349) LEAD-IN-GEOGRAPHIC-CODE 3235 is populated from LEAD-RESLT-GEOGRAPHIC-CODE 5060 from array in
(350) LEAD-IN-HISTOGRAM-INDEX 3240 is populated from LEAD-RESLT-HISTOGRAM-INDEX 5070 from array in
(351) LEAD-IN-HISTOGRAM-BEG-PCT 3245 is populated from LEAD-RESLT-HISTOGRAM-BEG-PCT 5080 from array in
(352) LEAD-IN-HISTOGRAM-END-PCT 3250 is populated from LEAD-RESLT-HISTOGRAM-END-PCT 5090 from array in
(353) STB-COUNT 3255 is populated from LEAD-RESLT-STB-COUNT 5100 from array in
(354) AGGR-VIEW-SECS 3260 is populated from LEAD-RESLT-AGGR-VIEW-SECS 5110 from array in
(355) EXPOSURES 3265 is populated from LEAD-RESLT-EXPOSURES 5120 from array in
(356) STB-TUNED-AT-BEG-OF-LEAD-IN-CNT 3270 is populated from LEAD-RES-STB-COUNT-AT-BEG 5130 from array in
(357) STB-TUNED-AT-END-OF-LEAD-IN-CNT 3275 is populated from LEAD-RES-STB-COUNT-AT-END 5140 from array in
(358) STB-TUNE-FOR-ALL-OF-LEAD-IN-CNT 3280 is populated from LEAD-RES-STB-COUNT-VIEW-ALL 5150 from array in
(359) The Lead-In Analytics Engine 200 will then perform process Write Analysis Period Result Header Result File 1040 where will it will write the Analysis Period Reslt Hdr File 240 which contains the information about the overall Analysis Period or Target for which viewing was being measured by this study.
(360) The field mapping is as follows:
(361) ANALYSIS-GROUP-ID 3405 is populated from LEAD-IN-ANALYSIS-GROUP-ID 4810 from array in
(362) TARGET-CHANNEL 3410 is populated from AP-TARGET-CHANNEL 5160 from array in
(363) POTENTIAL-VIEWING-SECOND 3415 is populated from AP-POTENTIAL-VIEWING-SECONDS 5170 from array in
(364) POTENTIAL-EXPOSURES 3420 is populated from AP-POTENTIAL-EXPOSURES 5180 from array in
(365) TARGET-INDUSTRY-VIDEO-PROGRAM-ID 3425 is populated from AP-TARGET-IND-VIDEO-PGM-ID 5190 from array in
(366) TARGET-INDUSTRY-VIDEO-ASSET-ID 3430 is populated from AP-TARGET-IND-VIDEO-ASSET-ID 5200 from array in
(367) TARGET-AIRING-DATE 3435 is populated from AP-TARGET-AIRING-DATE 5210 from array in
(368) TARGET-AIRING-BEG-TIME 3440 is populated from AP-TARGET-AIRING-BEG-TIME 5220 from array in
(369) TARGET-AIRNG-BEG-SEC-OF-DAY 3445 is populated from AP-TARGET-AIRNG-BEG-SEC-OF-DAY 5240 from array in
(370) TARGET-AIRING-END-TIME 3450 is populated from AP-TARGET-AIRING-END-TIME 5230 from array in
(371) TARGET-AIRNG-END-SEC-OF-DAY 3455 is populated from AP-TARGET-AIRNG-END-SEC-OF-DAY 5250 from array in
(372) TARGET-MIN-SECS-VW-AT-START 3460 is populated from AP-TARGET-MIN-SECS-VW-AT-START 5260 from array in
(373) AGGR-EXPECT-VIEW-SEC 3465 is populated from AP-TARGET-AGGR-EXPECT-VIEW-SEC 5270 from array in
(374) AGGR-ACTUAL-VIEW-SEC 3470 is populated from AP-TARGET-AGGR-ACTUAL-VIEW-SEC 5280 from array in
(375) AGGR-ACTUL-EXPOSURES 3475 is populated from AP-TARGET-AGGR-ACTUL-EXPOSURES 5290 from array in
(376) The Lead-In Analytics Engine 200 will then perform process Write Analysis Period Result Detail File 1050 where it will write the Analysis Period Reslt Dtl File 250 which contains the information about the individual Analysis Periods (segments of the Target) that are being analyzing to determine viewership. Recall that one Analysis Period Header may have many individual detail periods defined such as, for example, the innings of a baseball game.
(377) The field mapping is as follows:
(378) APD-DEF-ANALYSIS-GROUP-ID 3610 is populated from LEAD-IN-ANALYSIS-GROUP-ID 4810 from array in
(379) AP-DEF-DATE 3615 is populated from AP-DEF-DATE 5300 from array in
(380) AP-DEF-BEG-TIME-HH-MM-SS 3620 is populated from AP-DEF-BEG-TIME-HH-MM-SS-PM 5310 from array in
(381) AP-DEF-BEG-TIME-SEC-OF-DAY 3625 is populated from AP-DEF-BEG-TIME-SEC-OF-DAY 5320 from array in
(382) AP-DEF-END-TIME-HH-MM-SS 3630 is populated from AP-DEF-END-TIME-HH-MM-SS-PM 5330 from array in
(383) AP-DEF-END-TIME-SEC-OF-DAY 3635 is populated from AP-DEF-END-TIME-SEC-OF-DAY 5340 from array in
(384) AP-DEF-PERIOD-DURATION-SECS 3640 is populated from AP-DEF-PERIOD-DURATION-SECS 5350 from array in
(385) AP-DEF-TOT-CHAN-VIEW-SEC 3645 is populated from AP-DEF-TOT-CHAN-VIEW-SEC 5360 from array in
(386) AP-DEF-TOT-CHAN-EXPOSURE 3650 is populated from AP-DEF-TOT-CHAN-EXPOSURE 5370 from array in
(387) AP-DEF-TOT-STB-ANY-VIEW 3655 is populated from AP-DEF-TOT-STB-ANY-VIEW 5380 from array in
(388) The Lead-In Analytics Engine 200 will then perform process Write Analysis Period Result Demographic Geographic Histogram File 1060 where it will write the Analys Per Demo Geo Histg File 260 file which contains the information about the viewing that occurred during each individual Analysis Period. This viewing is broken down into the Demographic-Geographic-Histogram segments that the analyst defined for this study.
(389) The field mapping is as follows:
(390) APD-DEF-ANALYSIS-GROUP-ID 3810 is populated from LEAD-IN-ANALYSIS-GROUP-ID 4810 from array in
(391) AP-DEF-DATE 3820 is populated from AP-DEF-DATE 5300 from array in
(392) AP-DEF-BEG-TIME-HH-MM-SS 3830 is populated from AP-DEF-BEG-TIME-HH-MM-SS-PM 5310 from array in
(393) RESULT-DEMOGRAPHIC-CODE 3840 is populated from ANALYS-RESLT-DEMOGRAPHIC-CODE 5390 from array in
(394) RESULT-GEOGRAPHIC-CODE 3850 is populated from ANALYS-RESLT-GEOGRAPHIC-CODE 5400 from array in
(395) RESULT-HISTOGRAM-INDEX 3860 is populated from ANALYS-RESLT-HISTOGRAM-INDEX 5410 from array in
(396) RESULT-HISTOGRAM-BEG-PCT 3870 is populated from ANALYS-RESLT-HISTOGRAM-BEG-PCT 5420 from array in
(397) RESULT-HISTOGRAM-END-PCT 3880 is populated from ANALYS-RESLT-HISTOGRAM-END-PCT 5430 from array in
(398) RESULT-TOT-CHAN-VIEW-SEC 3890 is populated from ANALYS-RESLT-TOT-CHAN-VIEW-SEC 5440 from array in
(399) RESULT-TOT-CHAN-EXPOSURE 3900 is populated from ANALYS-RESLT-TOT-CHAN-EXPOSURE 5450 from array in
(400) RESLT-TOT-STB-ANY-VIEW 3910 is populated from ANALYS-RESLT-TOT-STB-ANY-VIEW 5460 from array in
(401) Finally, the Lead-In Analytics Engine 200 will then perform process Write Analysis Period Result Channel Viewing Detail File 1070 where it will write the Analys Res Chan View Dtl File 270 which contains the viewing information for each channel that was viewed by the Set-top boxes classified by the Demographic-Geographic-Histogram segments that the analyst defined for this study.
(402) The field mapping is as follows:
(403) APD-DEF-ANALYSIS-GROUP-ID 4010 is populated from LEAD-IN-ANALYSIS-GROUP-ID 4810 from array in
(404) AP-DEF-DATE 4020 is populated from AP-DEF-DATE 5300 from array in
(405) AP-DEF-BEG-TIME-HH-MM-SS 4030 is populated from AP-DEF-BEG-TIME-HH-MM-SS-PM 5310 from array in
(406) RESULT-DEMOGRAPHIC-CODE 4040 is populated from ANALYS-RESLT-DEMOGRAPHIC-CODE 5390 from array in
(407) RESULT-GEOGRAPHIC-CODE 4050 is populated from ANALYS-RESLT-GEOGRAPHIC-CODE 5400 from array in
(408) RESULT-HISTOGRAM-INDEX 4060 is populated from ANALYS-RESLT-HISTOGRAM-INDEX 5410 from array in
(409) RESULT-CHANNEL-CALL-SIGN 4070 is populated from ANALYS-RES-CHANNEL-CALL-SIGN 5500 from array in
(410) RESULT-AGGR-CHAN-VIEW-SECS 4080 is populated from ANALYS-RES-AGGR-CHAN-VIEW-SECS 5510 from array in
(411) RESULT-CHAN-EXPOSURES 4085 is populated from ANALYS-RES-CHAN-EXPOSURES 5520 from array in
(412) RESULT-STB-ANY-VIEWING 4090 is populated from ANALYS-RES-STB-ANY-VIEWING 5530 from array in
(413) At this point the process is Done 918.
(414) The result is that the Lead-In Analytics Engine 200 has created very detailed analytics and written them to flat files which can be loaded to a data base for further reporting. Alternatively, these analytics may be written directly to data base tables. In either event, the analyst now has very detailed information about video asset viewership for each Lead-in period with the various demographic, geographic, histogram breakouts, and for the Target period and its segments and the Demographic-Geographic-Histogram breakouts during each segment along with the channel viewing information.
(415) Each of the files described in
(416)
(417)
(418)
(419)
(420) The Channel Tuning data is collected, preprocessed, and prepared for the Lead-In Analytics Engine 200 by the Channel Tuning Data Collector 100. The Channel Tuning Data Collector 100 may receive data from a variety of sources including but not limited to Switched Digital Video systems, Set top box applications, Internet Protocol collection systems, or from other collection sources.
(421) The Channel Tuning Data Collector 100 delivers the Channel Tune File 110 containing channel tuning data ready to be analyzed to the Lead-In Analytics Engine 200.
(422) Another embodiment may deliver that channel tuning data as the output of a data base query or as XML messages or in any other suitable format.
(423) In my prior United States Patent Application having U.S. application Ser. No. 12/981,301 filed on Dec. 29, 2010, I reviewed switched digital video systems as one of several possible data sources. In that application I noted that switched digital video channel change data is readily available under current technology. I provided information about two vendors that supply switched digital video systems, namely Motorola and CISCO. I also described a process for preparing the channel tuning file created by a source system so that said file could be used by the Analytics Engine described in that specification.
(424) The Lead-In Analytics Engine described in this specification uses a Channel Tuning File similar to the one described in my prior Application. Therefore, in the present Application, I have simply described the layout of the Channel Tune File while making note that the Lead-In Analytics Engine 200 does not presently use all of the fields in this layout. Because they are part of the process described in said prior patent Application I have included them here.
(425)
(426)
(427)
(428)
(429)
(430) Lead In Video Play Information File records information about each of the Lead In video viewing periods. The analyst is allowed to define whatever Lead-In periods he wants to analyze. Nonlimiting examples include:
(431) In the case of an ad or a series of ads promoting an upcoming program, the analyst may use this to define each of the ads that will be presented to the viewer to encourage them to view the target video.
(432) In the case where the analyst is seeking to explore viewership of a particular program, the analyst may treat the entire program as a series of lead-in segment; in that case the analyst may define various segments of that program such as twelve (12) five (5) minute segments for a one hour program.
(433) In the case of an episodic program where the analyst is tracking viewing for the last 7 weeks with the Target being the 8.sup.th week, the analyst may define weekly lead-in's for each episode for the last 7 weeks.
(434) In the case of the nightly news where the analyst is tracking daily viewing for the last 7 days, the analyst may define daily lead-in periods for each day's news cast for the last week.
(435) In the case of a series of ads where the advertiser is trying to measure audience fatigue, the analyst may define each of the instances of an ad that ran during the last day or several days as the lead-in periods.
(436) In the case of prime time viewing, the analyst may define the first hour of broadcasting as the lead-in period which is then followed by a target hour.
(437) The analyst is allowed to define whatever Lead-In periods he wants to analyze. The Lead In Analytic Engine 200 presently supports up to 100 Lead In periods.
(438)
(439)
(440)
(441)
(442) The Lead In Demographic Geographic Histogram Definition File 140 is used to create a user defined Histogram of Demographic identifier, Geographic identifier, and Histogram Percentages by which to categorize Lead In viewing. The user may define one Demographic group and one Geographic group with a variety of Histogram viewing buckets, or Several Demographic groups and one Geographic group with a variety of Histogram viewing buckets, or one Demographic group and several Geographic groups, etc.
(443) The Lead In Analytic Engine presently supports up to 200 combinations of Demographic, Geographic, and Histogram categories.
(444) Note: This is similar to the histogram for Result viewing, except that this histogram is applicable only to analyzing Lead In viewing.
(445)
(446)
(447)
(448)
(449) The Analysis Period Target File 150 contains information about the Target video asset for which the system is tracking viewership to understand how effective the Lead-in video assets were in encouraging viewership of the Target.
(450) If the analyst only needs to analyze Lead-in viewing without regard to Target viewing, then this file is not required.
(451) The Lead In Analytic Engine 200 presently supports one Analysis Period Target. The Target can then be broken into segments as defined in
(452)
(453)
(454)
(455)
(456) The Analysis Period Definition File 160 allows the user to subdivide the Target video defined in Analysis Period Target into viewing segments for analysis. For example, a baseball game could be divided into 9 segments, one for each inning. A football game could be divided into 4 segments, one for each quarter; or into 6 segments for pre-game show, 2 quarters, half-time, and final 2 quarters. A movie could be divided into scenes. A newscast could be divided into segments for the various parts of the newscast (national news, local news, weather, sports). One could also define segments for each commercial.
(457) The analyst is allowed to use the Analysis Period Definition File 160 to define whatever Target segments he wants to analyze. The Lead In Analytics Engine 200 presently supports up to sixty (60) Analysis Period Definitions. This can be changed as needed.
(458)
(459)
(460)
(461)
(462) The Result Demographic Geographic Histogram Definition File 170 is used to create a user defined Histogram of Demographic identifier, Geographic identifier, and Histogram Percentages by which to categorize Result viewing. The histogram value is set based on the aggregate viewing during the lead-in period and then that value is used to assign the set-top box to the appropriate category for result viewing. The user may define one Demographic Group and one Geographic Group with a variety of Histogram viewing buckets, or Several Demographic Groups and one Geographic Group with a variety of Histogram viewing buckets, or one Demographic Group and several Geographic Groups, etc.
(463) The Lead In Analytics Engine 200 presently supports up to 200 combinations of Demographic, Geographic, and Histogram categories. This can be changed as needed.
(464) Note: This is similar to the histogram for Lead In viewing, except that this histogram is applicable only to analyzing Result viewing. Having the ability to create different definitions provides greater flexibility in the analysis.
(465)
(466)
(467)
(468)
(469) The Channels To Analyze File 180 provides a list of all the channels on which the Lead In Analytics Engine 200 will run analytics during the Target period (defined in Analysis Period Def) to gather viewing information on those channels. The analyst may define one, several, or many channels as desired.
(470) The Lead In Analytics Engine 200 presently supports up to 200 channels as presently configured, but this may be changed as needed.
(471)
(472)
(473)
(474)
(475) The Tuning Data Dates File 190 records the date or dates in the tuning data file for which the Lead In Analytics Engine will process the channel tuning data. Only channel tuning data that matches the dates in this file will be processed as part of the analysis study. If the Channel Tuning Data file contains multiples days of data, this allows the analyst to choose the days of interest for the study.
(476)
(477)
(478)
(479)
(480) The Analysis Group File 210 records overall information about the Analysis study that was done.
(481)
(482)
(483)
(484)
(485) The data in this file may be loaded to a data base in support of further analytics. Those with ordinary skill in the art will have no difficulty using common software development tools to develop a process which loads a file like the one shown to a data base or data warehouse in support of additional reporting and analytics. Alternatively, the Lead-In Analytics Engine 200 could update a data base table which has a structure similar to file format shown in
(486)
(487)
(488)
(489)
(490) The Lead In Viewing Result File 230 records statistics about the lead-in viewing broken out by the audience segments defined in the Demographic Geographic Histogram Definition File. Viewing during each Lead-in viewing period is broken out based on the criteria which the analyst defined in the Lead-In Demographic Geographic Histogram Definition File 140. Thus it is evident that the analyst has opportunity to define segmentation criteria that will reveal to him details about which demographic groups viewed each lead-in video, or which geographic groups viewed each lead-in video, or to categorize the viewers by the amount of lead-in viewing by using the histogram groups. Additionally, the analyst can combine any of these criteria to gain still greater insight to the viewers.
(491) The data in this file may be loaded to a data base in support of further analytics. Those with ordinary skill in the art will have no difficulty using common software development tools to develop a process which loads a file like the one shown to a data base or data warehouse in support of additional reporting and analytics. Alternatively, the Lead-In Analytics Engine 200 could update a data base table which has a structure similar to file format shown in
(492)
(493)
(494)
(495)
(496) The data in this file may be loaded to a data base in support of further analytics. Those with ordinary skill in the art will have no difficulty using common software development tools to develop a process which loads a file like the one shown to a data base or data warehouse in support of additional reporting and analytics. Alternatively, the Lead-In Analytics Engine 200 could update a data base table which has a structure similar to file format shown in
(497)
(498)
(499)
(500)
(501) The data in this file may be loaded to a data base in support of further analytics. Those with ordinary skill in the art will have no difficulty using common software development tools to develop a process which loads a file like the one shown to a data base or data warehouse in support of additional reporting and analytics. Alternatively, the Lead-In Analytics Engine 200 could update a data base table which has a structure similar to file format shown in
(502)
(503)
(504)
(505)
(506) The Analysis Period Result Demographic Geographic Histogram File 260 records for each start and end time of each video segment that was analyzed, the demographic grouping, the geographic grouping, and the histogram definitions along with viewing statistics for that combination within the Analysis Period Result Detail. It also has fields to link to the parent Analysis Period Result Detail.
(507) The data in this file may be loaded to a data base in support of further analytics. Those with ordinary skill in the art will have no difficulty using common software development tools to develop a process which loads a file like the one shown to a data base or data warehouse in support of additional reporting and analytics. Alternatively, the Lead-In Analytics Engine 200 could update a data base table which has a structure similar to file format shown in
(508)
(509)
(510)
(511)
(512) The Analysis Period Result Channel Viewing Detail File 270 records for each of the start and end times of each video segment that was analyzed with its histogram definitions, each Channel Call Sign that was viewed and the related viewing statistics. It also has fields to link to the parent Analysis Period Result Demographic Geographic Histogram.
(513) The data in this file may be loaded to a data base in support of further analytics. Those with ordinary skill in the art will have no difficulty using common software development tools to develop a process which loads a file like the one shown to a data base or data warehouse in support of additional reporting and analytics. Alternatively, the Lead-In Analytics Engine 200 could update a data base table which has a structure similar to file format shown in
(514)
(515)
(516)
(517)
(518) Claims Reference:
(519) In the Claims this CHAN-VIEWING-DETAIL array is referred to as a user activity data structure.
(520)
(521)
(522) Claims Reference:
(523) By defining a user activity data structure which contains both the identifying fields and the buckets for the second-by-second viewing activity, the Lead-In Analytics Engine 200 is able to correlate the identifying fields with the buckets representing individual seconds of time during a window of time of interest for analysis.
(524)
(525) Claims Reference:
(526) In the Claims this LEAD-IN-AND-TARGET-INFO array is referred to as a Lead-in viewing analysis data structure (for the fields related to lead-in viewing) and Target viewing analysis data structure (for the fields related to Target viewing). Those with ordinary skill in the art will readily recognize that these descriptive names have no bearing on the end result, but they do make it easier to read the specification and accompanying claims.
(527) Also, in the Claims the Demographic-geographic-histogram groupings in the LEAD-IN-AND-TARGET-INFO array are referred to as fields for tracking lead-in video asset viewing by various groupings.
(528) Also, in the Claims the ANALYSIS-PERIOD-DEFINITION fields within the LEAD-IN-AND-TARGET-INFO array are referred to as a target viewing analysis data structure.
(529) Also, in the Claims the ANALYSIS-PERIOD-DEF-ROW fields within the LEAD-IN-AND-TARGET-INFO array are referred to as a user defined target video asset segments.
(530) Also, in the Claims the ANALYSIS-PERIOD-RESULT-ROW fields within the LEAD-IN-AND-TARGET-INFO array are referred to as fields for tracking target video asset segment viewing by demographic geographic histogram groupings.
(531) Also, in the Claims the ANALYS-RESLT-CHANNELS-VIEWED fields within the LEAD-IN-AND-TARGET-INFO array are referred to as fields for tracking target video asset segment viewing by channel within said demographic geographic histogram groupings.
(532) By defining a LEAD-IN-AND-TARGET-INFO array which contains both all of the lead-in fields and all of the target fields, the Lead-In Analytics Engine 200 is able to correlate the lead-in viewing results with the target viewing results for a video asset viewing device.
(533) By defining a LEAD-IN-AND-TARGET-INFO array which contains both all of the lead-in fields and all of the target fields, the Lead-In Analytics Engine 200 is able to correlate the lead-in viewing results with the target viewing results for a computer system accessed through said network.
(534) By defining a LEAD-IN-AND-TARGET-INFO array which contains both all of the lead-in fields and all of the target fields, the Lead-In Analytics Engine 200 is able to correlate the lead-in viewing results with the target viewing results for an operator of a video asset viewing device.
(535) By defining a LEAD-IN-AND-TARGET-INFO array which contains both all of the lead-in fields and all of the target fields, the Lead-In Analytics Engine 200 is able to correlate the lead-in viewing results with the target viewing results for the video asset viewing devices associated with a household.
(536) By defining a LEAD-IN-AND-TARGET-INFO array which contains both all of the lead-in fields and all of the target fields, the Lead-In Analytics Engine 200 is able to correlate the lead-in viewing results with the target viewing results.
(537) Furthermore, by having the lead-in part of the array contain each lead-in period and then having each lead-in period contain the lead-in demographic codes, geographic codes, and histogram bucket definitions, the Lead-In Analytics Engine 200 is able to correlate the lead-in demographic, geographic, and histogram data with the lead-in period.
(538) Furthermore, by having the target part of the array contain the target period and then having the target period contain the target segments and then having each target segment contain the demographic codes, geographic codes, and histogram bucket definitions and then having each of those demographic codes, geographic codes, and histogram bucket definitions contain the channel viewing data, the Lead-In Analytics Engine 200 is able to correlate the target segments with the demographic, geographic, and histogram grouping with the channel viewing data for the target viewing period.
(539)
(540) The Lead In Analytics Engine 200 presently supports up to 200 combinations as presently configured, but this may be changed as needed.
(541) In the accompanying program, this array is named LI-DEMO-GEO-HISTG-ARRAY.
(542)
(543) The Lead In Analytics Engine 200 presently supports up to 200 combinations as presently configured, but this may be changed as needed.
(544) In the accompanying program, this array is named RE-DEMO-GEO-HISTG-ARRAY.
(545)
(546) The Lead In Analytics Engine 200 presently supports up to 300 combinations as presently configured, but this may be changed as needed.
(547) In the accompanying program, this array is named CHANNELS-TO-ANALYZE.
(548)
(549) In this nonlimiting example, the purpose is not to describe in detail the operations of a cellular network, but to simply show that the viewer 7800 is interacting with a video asset viewing device 8010 which is interacting with a computer system 8060 accessed through a network 8040.
(550) The video asset viewing device in this example may be a hand-held device which allows the viewer to view video content. A non-limiting example may be a smart phone or an electronic tablet device.
(551) To follow the chain of interactions in this nonlimiting example, the viewer 7800 is using a video asset viewing device 8010 such as a cell phone or a personal communication device or a personal video player or tablet or any similar electronic device. The video asset viewing device 8010 uses a radio wave or electronic signal 8020 to communicate with a cell tower or wireless network 8030 which then communicates via a network 8040 to reach a computer system such as a node or port 8050 which then communicates via a another network segment 8040 to access a computer system 8060 which uses another network segment 8040 to communicate with another computer system 8060 which may feed streaming video to the video asset viewing device 8010.
(552) The video asset viewing device 8010 is then able to capture the Video asset viewing device usage data caused by the viewer 7800 and feed this back to the central collection system which resides on a Computer system 8060.
(553) As described in
(554)
(555) In this nonlimiting example, the purpose is not to describe in detail the operations of an internet protocol network, but to simply show that the viewer 7800 is interacting with a video asset viewing device which in this example is an Internet Protocol Television device 8220 which is interacting with a computer system 8230 accessed through a network 8040.
(556) To follow the chain of interactions in this nonlimiting example, the viewer 7800 is using a video asset viewing device 8220 such as an internet protocol television or any similar video asset viewing device. The video asset viewing device 8220 uses a wireless or wired network 8040 to communicate with an Internet Protocol (IP) TV Delivery computer system 8230 which provides video to the IP TV. IP TV Delivery computer system 8230 itself also uses a network 8040 to communicate with an IP TV Video Server computer system 8250.
(557) The video asset viewing device 8220 is then able to capture the Video asset viewing device usage data caused by the viewer 7800 and feed this back to the central collection system which resides on an IP TV Delivery computer system 8230.
(558) As described in
(559)
(560) In these nonlimiting examples, the purpose is not to describe in detail the operations of a cable television network or a switched digital video system, but to simply show that the viewer 7800 or 7802 or 7804 is interacting with a set-top box 7810 or 7812 or 7814 which is interacting with a computer system 102 or 104 or 7870 accessed through a network 7830 or 7832 or 7834 and that the overall network includes various components such as SDV systems, Cable Video systems, STB systems, Service Groups, Hubs, and Headends which are all part of a Market in a cable television system.
(561) To follow the chain of interactions in this nonlimiting example, in the first Switched Digital Video part of this Figure, the viewer 7800 is using a set-top box 7810 or any similar video asset viewing device attached to a television 7820. The signal produced by the set-top box 7810 is viewed on a television 7820. The set-top box 7810 uses a HFC network segment 7830 to communicate with Switched Digital Video system from Vendor 1 102 which is accessed via a Service Group 7840 and a Hub 7850. The Hub 7850 is linked to a Headend 7890 via a transport ring 7900. Switched Digital Video system from Vendor 1 102 produces the file Vendor 1 SDV Channel Tune File 112 which can then be made available to the Channel Tuning Data Collector 100 for use by the Lead In Analytics Engine 200 (as described in
(562) To continue following the chain of interactions in this nonlimiting example, in the second Switched Digital Video part of this Figure, the viewer 7802 is using a set-top box 7812 or any similar video asset viewing device attached to a television 7822. The signal produced by the set-top box 7812 is viewed on a television 7822. The set-top box 7812 uses a HFC network segment 7832 to communicate with Switched Digital Video system from Vendor 2 104 which is accessed via a Service Group 7840 and a Hub 7850. The Hub 7850 is linked to a Headend 7890 via a transport ring 7900. Switched Digital Video system from Vendor 2 104 produces the file Vendor 2 SDV Channel Tune File 114 which can then be made available to the Channel Tuning Data Collector 100 for use by the Lead In Analytics Engine 200.
(563) To further continue following the chain of interactions in this nonlimiting example, in the non-Switched Digital Video part of this Figure, a different viewer 7804 is using a different set-top box 7814 or any similar video asset viewing device attached to a television. The signal produced by the set-top box 7814 is viewed on a different television 7824. The set-top box 7814 uses a different HFC network segment 7834 to communicate with a Cable Video Computer System 7870 which is accessed via a Service Group 7840 and a Hub 7850. The Hub 7850 is linked to a Headend 7890 via a transport ring 7900. Set-top box 7814 is running Set-top box application software from STB software vendor 106 and the software is collecting channel tuning data which is used to produce Set-top box Vendor Channel Tune File 116.
(564) The following details are not shown: The Set-top box Vendor Channel Tune File 116 from a plurality of set-top boxes is routed back through the HFC Network 7834 where the files are aggregated and can then be made available to the Channel Tuning Data Collector 100 for use by the Lead In Analytics Engine 200.
(565) To summarize these nonlimiting examples shown in
(566) As described in
(567) Channel tuning file formats for Switched Digital Video channel tuning data are further defined in Applicant's U.S. application Ser. No. 12/981,301 filed on Dec. 29, 2010 entitled “SYSTEM AND METHOD FOR ANALYZING HUMAN INTERACTION WITH ELECTRONIC DEVICES THAT ACCESS A COMPUTER SYSTEM THROUGH A NETWORK”. This application is incorporated in its entirety but is not admitted to be prior art.
(568) Channel tuning file formats for Set-top box channel tuning data are further defined in Applicant's U.S. application Ser. No. 12/981,301 filed on Dec. 29, 2010 entitled “SYSTEM AND METHOD FOR ANALYZING HUMAN INTERACTION WITH ELECTRONIC DEVICES THAT ACCESS A COMPUTER SYSTEM THROUGH A NETWORK”. This application is incorporated in its entirety but is not admitted to be prior art.
(569)
(570) In these nonlimiting examples, the purpose is not to describe in detail the operations of a satellite television network, but to simply show that the viewer 7806 is interacting with a set-top box 7816 which is interacting with computer systems 8004 and 8050 accessed through networks 8006 and 8040 and that the overall network includes various components such as a Computer that sends signals to a satellite 8004 and a computer that receives set-top box activity 8050, both being part of a satellite television system.
(571) To follow the chain of interactions in this nonlimiting example, the video or audio signal is sent by the Computer sending Signal to Satellite 8004 as a Signal to Satellite 8006. The Satellite 8010 receives the signal and beams it as a Signal from a Satellite 8020 to the Satellite receiver dish 8030 where it is then passed on to the Set-top box 7816. The viewer 7806 controls the Set-top box 7816 by interacting with it. The set-top box 7816 displays video on the Television 7824. The Set-top box application software from STB software vendor 106 captures the interactions of the viewer 7806 and packages them into a file Set-top box Vendor Channel Tune File 116 or other message which is then sent to the Satellite provider's STB Usage Data Collection Computer System 8050 using or across the Satellite providers network 8040.
(572) As described in
(573) The Satellite provider's STB Usage Data Collection Computer System 8050 may aggregate Set-top box Vendor Channel Tune File 116 from many individual set-top boxes into one large STB Channel Tuning File. This detail is not shown.
Alternative Embodiments
(574) Note that the specification and drawings use certain terms interchangeably. The reader will note this most frequently with the terms set-top box and video asset viewing device. The reader will appreciate that a set-top box is merely a specific kind of video asset viewing device. A smart phone, a tablet device, a gaming console are all examples of video asset viewing device. Thus any discussion below that refers to a set-top box should be read to also include any kind of a video asset viewing device.
(575) Although the description above contains much specificity, these should not be construed as limiting the scope of the embodiments but as merely providing illustrations of some of several embodiments. As a nonlimiting example, additional qualifiers may be added along with demographic and geographic codes. Histograms can be created based on quantity of viewing rather than percentage of viewing. Additional calculations can be done once the data is loaded to the various data structures.
(576) Scope of Channel Tuning Data Loaded
(577) I presently contemplate that the Lead-In Analytics Engine 200 will load up to seven days of channel tuning data to the CHAN-VIEWING-DETAIL array (user activity data structure in the claims) including all the seconds of the day for each day. Another embodiment may load only a subset of the daily channel tuning data but perhaps for more days. A non-limiting example of this would be to load viewing seconds for the 6:00 PM to 10:00 PM time slot for 30 days thus supporting longitudinal viewing analysis over a 30 day period.
(578) Tracking Trick Play Activity
(579) I presently contemplate that an additional field or fields may be added to the user activity data structure to allow the measurement of other types of viewing activity in addition to standard play mode. Such a field may be added at the one-second level such that for each second of the day there is a field to indicate play speed and direction. This then could be used in the various algorithms as part of the scoring when counting the number of viewing seconds earned by a video asset.
(580) Tracking Multiple Concurrent Activities
(581) As a second nonlimiting example, viewing activity or device usage data can reflect multiple concurrent activities such as a set-top box using multiple tuners simultaneously as in multiple pictures on a television screen or one picture on the television screen and one video stream being recorded by a digital video recorder. One can readily envision set-top box applications or personal computer applications or advanced television applications which show multiple windows such as a television program, a TV menu, a sports channel, a weather channel, a traffic cam, a twitter (© 2010 Twitter, Twitter, Inc.) session, an instant message session, a You Tube (© 2010 YouTube, LLC, www.youtube.com) video, an email session, a web browsing session, a Facebook (Facebook© 2010, www.facebook.com) session, etc.
(582) Usage data could be collected for each of these activities with perhaps weightings assigned to the activities based on business rules. In this case, one could tally the ad or program viewing time taking into account multiple activities occurring simultaneously and perhaps assigning partial values to those seconds. For example, enable viewing activity to be tracked for multiple, perhaps five, channels for each second of the day. Then if the viewing device has two channels visible at the same time, allocate the viewing based on the percentage of the viewing space attributable to each channel (data source) with perhaps extra credit given to the channel (data source) which is being actively viewed as determined by business rules. Additional business rules can be developed to properly allocate the percentage of viewing activity that should be allocated in other similar circumstances.
(583) As another nonlimiting example, set-top box viewing activity or video asset viewing device usage data can reflect use of trick plays such as fast forwarding through recorded content such as using the DVR to fast forwarding through commercials. In this case one could reduce the amount of viewing earned per second depending on how fast the DVR is moving with perhaps quad-speed earning less viewing credit than half-speed because the viewer will have reduced exposure to the content.
(584) Methods for Receiving Data
(585) I presently contemplate Channel Tuning data data being provided in flat files, but another embodiment may provide this data in any computer readable format including but not limited to data base tables, XML messages, or other messaging constructs.
(586) I presently contemplate Channel Tuning data data being being sorted as part of the Tuning Data Collector 100 processing, but another embodiment may sort this data as part of a data base query that is providing the data to the Lead-In Analytics Engine 200.
(587) I presently contemplate Lead-in Video Schedule data data being provided in flat files, but another embodiment may provide this data in any computer readable format including but not limited to data base tables, XML messages, or other messaging constructs.
(588) I presently contemplate Analysis Period Target data data being provided in flat files, but another embodiment may provide this data in any computer readable format including but not limited to data base tables, XML messages, or other messaging constructs.
(589) Identifiers for Data
(590) I presently contemplate using mnemonics for the various identifiers such as market, demographic code, geographic code, channel call sign, analysis group id, lead-in analysis period id, industry program id, industry asset id, and other similar fields, but another embodiment could use numeric values as identifiers with links to reference tables for the descriptions of the numeric identifiers.
(591) I presently contemplate using record identifiers with multipart keys. Another embodiment could provide simple numeric identifiers or other identifiers that accomplish a similar purpose.
(592) Run Size
(593) I presently contemplate processing the data within the context of a Market or a Headend in a service provider's network, but another embodiment could process the data within larger or small groupings, or within any suitable combination of identifiers.
(594) I presently contemplate allowing multiple, up to 100, lead-in viewing periods, but another embodiment may process only one lead-in viewing period per run or even more than 100 lead-in viewing periods per run.
(595) I presently contemplate that the lead-in analysis period is associated with a channel, but another embodiment may associate it with a web address or an IP address.
(596) I presently contemplate allowing multiple, up to 200, demographic-geographic-histogram combinations for each lead-in viewing period, but another embodiment may allow a different number of combinations.
(597) I presently contemplate allowing multiple, up to 60, segments for the analysis periods, but another embodiment may allow a different number of segments.
(598) I presently contemplate allowing multiple, up to 200, demographic-geographic-histogram combinations for each analysis period target segment, but another embodiment may allow a different number of such combinations.
(599) I presently contemplate allowing multiple, up to 300, channels for each demographic-geographic-histogram combination for each analysis period target segment, but another embodiment may allow a different number of channels.
(600) I presently contemplate analyzing channel viewing activity within each demographic-geographic-histogram combination, but another embodiment may analyze web sites or IP addresses.
(601) I presently contemplate executing the algorithms described herein separately in some sequence, but another embodiment could combine multiple simple algorithms into fewer complex algorithms.
(602) I presently contemplate processing up to seven days of channel tuning data at a time, but another embodiment may accept individual channel tuning events in near real time and then process them as they are received. Along with this, such an embodiment could also receive video asset schedule data or targeted content data in like manner so that the channel tuning events could be matched to such data.
(603) I presently contemplate processing up to seven days of channel tuning data at a time, but another embodiment may process more days of data or only a part of a day.
(604) Channel Tuning Data Non-Used Fields
(605) I presently contemplate not using the fields in the Channel Tuning Data file 110 that are identified as “Not presently used”; they are included in
(606) Receiving Date and Time Information
(607) I presently contemplate that the tune-in date and time and the tune-out date and time will be presented in YYYY-MM-DD HH:MM:SS AM/PM format to the Channel Tuning Data Collector 100 which will then prepare the data for the Lead In Analytics Engine 200. Another embodiment could provide these values in seconds from some historic date such as Epoch time (Jan. 1, 1970) and then subtract the proper number of seconds from the value so as to bring the value into the seconds of the current date. For example, Aug. 1, 2010 at 12:00:00 AM is Epoch time 1280646000. Subtracting this value from any tune-in date and time or tune-out date and time from Aug. 1, 2010, will result in the second of the day that can be used in populating the Viewing Detail Data Structure. A tune-in at Aug. 1, 2010 at 12:30:00 AM has Epoch time of 1280647800. Thus we see that 1280647800−1280646000=1800 seconds which would be 30 minutes after midnight. Either embodiment can be used as input to create the metrics.
(608) I presently contemplate that the Channel Tuning Data Collector 100 function will be provided with the tune-in date and time and the tune-out date and time presented in YYYY-MM-DD HH:MM:SS AM/PM format. Another embodiment could provide the tune-in date and time in this format and then provide the duration of the tuning activity in seconds instead of providing the tune-out date and time presented in YYYY-MM-DD HH:MM:SS AM/PM format. In this situation the Channel Tuning Data Collector 100 function would add the tuning duration in seconds to the tune-in time in seconds to arrive at the tune-out time.
(609) I presently contemplate that the Channel Tuning Data Collector 100 function will be provided with the tune-in date and time and the tune-out date and time presented in YYYY-MM-DD HH:MM:SS AM/PM format. Another embodiment could provide the tune-out date and time in this format and then provide the duration of the tuning activity in seconds instead of providing the tune-in date and time presented in YYYY-MM-DD HH:MM:SS AM/PM format. In this situation the Channel Tuning Data Collector 100 function would subtract the tuning duration in seconds from the tune-out time in seconds to arrive at the tune-in time.
(610) I presently contemplate that the Analysis Group Info File 120 will be provided as a flat file in the format shown. Another embodiment could provide similar information as the result of a data base query or other method.
(611) I presently contemplate that the Lead In Video Play Info File 130 will be provided as a flat file in the format shown. Another embodiment could provide similar information as the result of a data base query or other method.
(612) I presently contemplate that the Lead In Demographic Geographic Histogram Definition File 140 will be provided as a flat file in the format shown. Another embodiment could provide similar information as the result of a data base query or other method.
(613) I presently contemplate that the Analysis Period Target File 150 will be provided as a flat file in the format shown. Another embodiment could provide similar information as the result of a data base query or other method.
(614) I presently contemplate that the Analysis Period Definition File 160 will be provided as a flat file in the format shown. Another embodiment could provide similar information as the result of a data base query or other method.
(615) I presently contemplate that the Result Demographic Geographic Histogram Definition File 170 will be provided as a flat file in the format shown. Another embodiment could provide similar information as the result of a data base query or other method.
(616) I presently contemplate that the Channels to Analyze File 180 will be provided as a flat file in the format shown. Another embodiment could provide similar information as the result of a data base query or other method. Yet another embodiment may discover the channels to analyze as they appear in the channel tuning data.
(617) I presently contemplate that the Tuning Data Dates File 190 will be provided as a flat file in the format shown. Another embodiment could provide similar information as the result of a data base query or other method. Yet another embodiment may discover the tuning data dates as they appear in the channel tuning data.
(618) I presently contemplate that the data which is written to the Analysis Group File 210 will be written as a flat file. Another embodiment could insert to or update a data base table to record this information.
(619) I presently contemplate that the data which is written to the Analysis Lead In Period File 220 will be written as a flat file. Another embodiment could insert to or update a data base table to record this information.
(620) I presently contemplate that the data which is written to the Lead In Viewing Result File 230 will be written as a flat file. Another embodiment could insert to or update a data base table to record this information.
(621) I presently contemplate that the data which is written to the Analysis Period Result Header File 240 will be written as a flat file. Another embodiment could insert to or update a data base table to record this information.
(622) I presently contemplate that the data which is written to the Analysis Period Result Detail File 250 will be written as a flat file. Another embodiment could insert to or update a data base table to record this information.
(623) I presently contemplate that the data which is written to the Analysis Period Result Demographic Geographic Histogram Detail File 260 will be written as a flat file. Another embodiment could insert to or update a data base table to record this information.
(624) I presently contemplate that the data which is written to the Analysis Period Result Channel Viewing Detail File 270 will be written as a flat file. Another embodiment could insert to or update a data base table to record this information.
(625) I presently contemplate receiving all of the date and time values in local time, but another embodiment may provide these in Coordinated Universal Time (UTC time).
(626) Data Correlations
(627) I presently contemplate that the Analysis Group will contain a common key (Analysis Group Id) that serves as the identifier of an entire study thus linking the lead-in parts of the study with the result (target) parts of the study. Another embodiment could provide a similar study identifier using some other method.
(628) Yet another embodiment may provide this data in data base tables where a SQL query links the values together using a common key. Yet another embodiment may use multiple data base tables to store this information in a highly normalized format and link the various tables together using keys.
(629) Thus we see that data correlations can be accomplished in various ways within the spirit and scope of this embodiment.
(630) General Information
(631) I presently contemplate using variables having the data types and field sizes shown, but another embodiment may use variables with different data types and field sizes to accomplish a similar result.
(632) I presently contemplate tracking viewing activity at the granularity of one second, but another embodiment may track viewing activity at a finer granularity, perhaps half-second, or tenth-second, or millisecond. Yet another embodiment may receive data at a granularity finer than one second and round to the nearest second for use by the Lead-In Analytics Engine 200.
(633) I presently contemplate using data structures similar to those defined herein, but another embodiment may use a different data structure or data structures to accomplish a similar result.
(634) I presently contemplate using a LEAD-IN-AND-TARGET-INFO array structure similar to that defined herein, but another embodiment may use a different data structure(s) to accomplish a similar result. As a nonlimiting example, the LEAD-IN-AND-TARGET-INFO array structure could be stored in a relational data base table or tables or similar structure and still accomplish a similar result.
(635) Implementation Information
(636) I presently contemplate using the WINDOWS 7 Professional operating system from MICROSOFT Corporation, but another embodiment may use a different operating system.
(637) I presently contemplate using FUJITSU® NetCOBOL® for WINDOWS® version 10.1 developed by FUJITSU® and distributed by Alchemy Solutions Inc, but another embodiment may use a different programming language or a different version of COBOL.
(638) General Remarks
(639) It will be apparent to those of ordinary skill in the art that various changes and modifications may be made which clearly fall within the scope of the embodiments revealed herein. In describing an embodiment illustrated in the drawings, specific terminology has been used for the sake of clarity. However, the embodiments are not intended to be limited to the specific terms so selected, and it is to be understood that each specific term includes all technical equivalents which operate in a similar manner to accomplish a similar purpose.
(640) In general, it will be apparent to one of ordinary skill in the art that various embodiments described herein, or components or parts thereof, may be implemented in many different embodiments of software, firmware, and/or hardware, or modules thereof. The software code or specialized control hardware used to implement some of the present embodiments is not limiting of the present embodiment. For example, the embodiments described hereinabove may be implemented in computer software using any suitable computer software language type such as, for example, C, C #, or C++ using, for example, conventional or object-oriented techniques. Such software may be stored on any type of suitable computer-readable medium or media such as, for example, a magnetic or optical storage medium. Thus, the operation and behavior of the embodiments are described in COBOL style pseudocode purely as a matter of convenience. It is clearly understood that artisans of ordinary skill would be able to design software and control hardware to implement the embodiments presented in the language of their choice based on the description herein with only a reasonable effort and without undue experimentation.
(641) The processes associated with the present embodiments may be executed by programmable equipment, such as computers. Software or other sets of instructions that may be employed to cause programmable equipment to execute the processes may be stored in any storage device, such as, for example, a computer system (non-volatile) memory, a compact disk, an optical disk, magnetic tape, or magnetic disk. Furthermore, some of the processes may be programmed when the computer system is manufactured or via a computer-readable medium.
(642) It can also be appreciated that certain process aspects disclosed herein may be performed using instructions stored on a computer-readable memory medium or media that direct a computer or computer system to perform process steps. A computer-readable medium may include, for example, memory devices such as diskettes, compact discs of both read-only and read/write varieties, optical disk drives, memory sticks, and hard disk drives. A computer-readable medium may also include memory storage that may be physical, virtual, permanent, temporary, semi-permanent and/or semi-temporary.
(643) In various embodiments disclosed herein, a single component or algorithm may be replaced by multiple components or algorithms, and multiple components or algorithms may be replaced by a single component or algorithm, to perform a given function or functions. Except where such substitution would not be operative to implement the embodiments disclosed herein, such substitution is within the scope presented herein. Thus any element expressed herein as a means or a method for performing a specified function is intended to encompass any way of performing that function including, for example, a combination of elements that performs that function. Therefore, any means or method that can provide such functionalities may be considered equivalents to the means or methods shown herein.
(644) While I have developed this embodiment on a personal computer, it can be appreciated that the “data analysis computer system” may be, for example, a wireless or wire line variety of a microcomputer, minicomputer, server, mainframe, laptop, personal data assistant (PDA), wireless e-mail device (e.g., “BlackBerry” trade-designated devices), phone, smart phone, cellular phone, cable box, pager, processor, fax machine, scanner, or any programmable device configured to transmit and receive data over a network. Computer devices disclosed herein may include memory for storing certain software applications used in obtaining, processing and communicating data. It can be appreciated that such memory may be internal or external to the disclosed embodiments. The memory may also include any means or method for storing software, including a hard disk, an optical disk, floppy disk, ROM (read only memory), RAM (random access memory), PROM (programmable ROM), EEPROM (electrically erasable PROM), and other computer-readable media.
(645) While various embodiments have been described herein, it should be apparent, however, that various modifications, alterations and adaptations to those embodiments may occur to persons skilled in the art with the attainment of some or all of the advantages described herein. The disclosed embodiments are therefore intended to include all such modifications, alterations and adaptations without departing from the scope and spirit of the embodiments presented herein as set forth in the appended claims.
(646) Accordingly, the scope should be determined not by the embodiments illustrated, but by the appended claims and their legal equivalents.
CONCLUSIONS, RAMIFICATIONS, AND SCOPE
(647) From the description above, a number of advantages of some embodiments of my Lead-In Analytics Engine 200 and its supporting processes become evident:
(648) By having the Lead-In Analytics Engine 200 load (a) the video asset viewing device identifier, and (b) channel viewing activity identifying the channel viewed by that video asset viewing device for every second of the day for multiple days, this produces the result that the Lead-In Analytics Engine 200 can produce longitudinal metrics that were not previously possible.
(649) By having the Lead-In Analytics Engine 200 load (a) the video asset viewing device identifier, (b) a Demographic identifier, and (c) channel viewing activity identifying the channel viewed by that video asset viewing device for every second of the day for multiple days, this produces the result that the Lead-In Analytics Engine 200 can produce longitudinal metrics at a demographic level that were not previously possible.
(650) By having the Lead-In Analytics Engine 200 load (a) the video asset viewing device identifier, (b) a Geographic identifier, and (c) channel viewing activity identifying the channel viewed by that video asset viewing device for every second of the day for multiple days, this produces the result that the Lead-In Analytics Engine 200 can produce longitudinal metrics at a geographic level that were not previously possible.
(651) This method of tracking viewing activity on a second-by-second basis is contrary to the teaching of those who work with start time and duration (seconds viewed) in a relational data base model. Thus I am able to solve problems previously found insolvable when limited to using the existing techniques. I am able to provide metrics that could not be produced using existing techniques.
(652) In regard to video asset viewing on all manner of devices, I have provided numerous metrics showing a level of detailed analytics not previously possible. For example, the Lead-In Analytics Engine 200 allows me to measure viewing of ads and/or programs during a Lead-in period down to a granularity of one-second for both lightly viewed channels and more heavily viewed channels; traditional survey methods do not allow this. The Lead-In Analytics Engine 200 allows me to provide deeper insight into viewership of highly viewed channels. The Lead-In Analytics Engine 200 is able to provide the detailed information that industry researchers urgently need. There are many other examples contained herein.
(653) I will now provide an in-depth discussion of the various advantages.
(654) Lead In Content Viewership Analysis
(655) The Lead-In Analytics Engine 200 has the advantage of allowing me to produce detailed metrics on the actual viewing of content during one or more lead-in periods. These metrics can provide insight into the demographic and geographic information about the viewers of the lead-in content. By measuring at the one second level the Lead-In Analytics Engine 200 is able to provide the data needed to compare the effectiveness of the various Lead-In content. For example, if the same lead-in asset on one channel earns a lower relative quantity of viewing seconds than that asset when aired on another channel, this indicates that the viewers on the second channel often tune away when the ad appears. These metrics can also provide insight into viewing patterns and human behavior.
(656) These metrics are applicable to each individual airing of a lead-in video asset as described in the Lead In Video Asset Schedule. Thus if a lead-in video asset airs multiple times in one day, such as a commercial often does, the Lead-In Analytics Engine 200 produces metrics for each airing.
(657) The Lead-In Analytics Engine 200 produces the following metrics for each unique airing of each lead-in video asset (i.e. the lead-in content): Set Top Box count which measures the aggregate number of set-top boxes (video asset viewing devices) that were tuned to at least some part of the lead-in asset. If the Lead-in is an advertisement, this provides a measure of how many viewers viewed at least some part of the ad. If the Lead-in is a program, this provides a measure of how many viewers viewed at least some part of the program. Aggregate Viewing Seconds count which measures the aggregate number of viewing seconds for those set-top boxes (video asset viewing devices) that were tuned to the lead-in asset. From an advertiser's perspective, this measures the amount of viewing that the ad earned. From a programmer's perspective, this measures the amount of viewing that the program earned. Exposures count which measures the aggregate number of set-top boxes (video asset viewing devices) that were tuned for at least the required number of seconds to be counted as an exposure to the lead-in asset. For example, a viewing instance may count as an exposure only when the set-top box (video asset viewing device) was tuned to the lead-in for at least 20 seconds. From an advertiser's perspective, this measures useful exposures to the ad. If the lead-in is a program, then the exposure could be increased to perhaps 300 seconds before it is counted as an exposure. Set Top Boxes Tuned in at the beginning of the lead-in period count which measures the number of video asset viewing devices that were tuned in at the start of the lead-in period. This can be used to measure size of viewing audience at the start of the lead-in period to then compare it with viewing audience at the end of the lead-in period. Set Top Boxes Tuned in at the end of the lead-in period count which measures the number of video asset viewing devices that were tuned in at the end of the lead-in period. This can be used to measure size of viewing audience at the end of the lead-in period to then compare it with viewing audience at the start of the lead-in period. Set Top Boxes Tuned in for all of the lead-in period count which measures the number of video asset viewing devices that were tuned in for the entire lead-in period. This can be used to measure size of viewing audience that viewed the entire lead-in period.
(658) In addition, the Lead-In Analytics Engine 200 provides a finer granularity of break-out for the lead-in viewing by producing the following metrics for each unique airing of each lead-in video asset for each combination of Demographic-Geographic-Histogram index: Set Top Box count which measures the aggregate number of set-top boxes (video asset viewing devices) identified by this combination of Demographic-Geographic-Histogram index identifier that were tuned to at least some part of the lead-in asset. If the Lead-in is an advertisement, this provides a measure of how many viewers having this Demographic-Geographic code combination viewed the required percentage of the ad to fit into the indicated Histogram bucket. If the Lead-in is a program, this provides a measure of how many viewers having this Demographic-Geographic code combination viewed the required percentage of the program to fit into the indicated Histogram bucket. Aggregate Viewing Seconds count which measures the aggregate number of viewing seconds for those set-top boxes (video asset viewing devices) that were tuned to the lead-in asset and were identified by this combination of Demographic-Geographic-Histogram index identifier. If the Lead-in is an advertisement, this provides a measure the aggregate viewing seconds of the viewers having this Demographic-Geographic code combination that viewed the required percentage of the ad to fit into the indicated Histogram bucket. If the Lead-in is a program, this provides a measure the aggregate viewing seconds of the viewers having this Demographic-Geographic code combination that viewed the required percentage of the program to fit into the indicated Histogram bucket. Exposures count which measures the aggregate number of set-top boxes (video asset viewing devices) identified by this combination of Demographic-Geographic-Histogram index identifier that were tuned to at least the required number of seconds to be counted as an exposure to the lead-in asset. If the Lead-in is an advertisement, this provides a measure of how many viewers having this Demographic-Geographic code combination and who met the minimum viewing threshold then viewed the required percentage of the ad to fit into the indicated Histogram bucket. From an advertiser's perspective, this measures useful exposures to the ad by this Demographic-Geographic group. If the Lead-in is a program, this provides a measure of how many viewers having this Demographic-Geographic code combination and who met the minimum viewing threshold then viewed the required percentage of the program to fit into the indicated Histogram bucket. From a programmer's perspective, this measures how many people saw at least a given amount of a program. Set Top Boxes Tuned in at the beginning of the lead-in period count which measures the number of video asset viewing devices identified by this combination of Demographic-Geographic-Histogram index identifier that were tuned in at the start of the lead-in period. This can be used to measure size of viewing audience at the start of the lead-in period to then compare it with viewing audience at the end of the lead-in period. Set Top Boxes Tuned in at the end of the lead-in period count which measures the number of video asset viewing devices identified by this combination of Demographic-Geographic-Histogram index identifier that were tuned in at the end of the lead-in period. This can be used to measure size of viewing audience at the end of the lead-in period to then compare it with viewing audience at the start of the lead-in period. Set Top Boxes Tuned in for all of the lead-in period count which measures the number of video asset viewing devices identified by this combination of Demographic-Geographic-Histogram index identifier that were tuned in for the entire lead-in period. This can be used to measure size of viewing audience that viewed the entire lead-in period.
(659) Advertising Placement
(660) The Lead-In Analytics Engine 200 has the advantage of allowing advertisers to identify optimal times during which to place various ads. As a nonlimiting example, in general, once we are able to determine how much of the advertisement was viewed by each set-top box within the viewing group to which the advertisement was presented, advertisers can determine where to place ads. More specifically, by defining lead-in periods that identify the times when various ads aired, the Lead-In Analytics Engine 200 allows us to measure actual viewing seconds of each ad when it plays. This data can be used as input to actual ad placement. As nonlimiting examples, an advertiser could: 1. Identify whether a particular ad earns more viewing seconds when played during the morning news or the evening news. Such information would also be useful in negotiating advertising rates. Example: Does the same car commercial earn more viewing seconds during the morning news or the evening news? 2. Identify whether a particular ad earns more viewing seconds when played during a movie or a football game. Such information would be useful in choosing the program type in which to advertise. Example: Does the same toothpaste commercial earn more viewing seconds during a movie or a football game? 3. Identify what type of product is likely to earn the most viewing seconds during a particular type of program. Example: Does the car commercial or the toothpaste commercial earn more viewing seconds during the movie?
(661) Such metrics would be very helpful to advertisers in identifying the most suitable programs in which to run various ads. Also, beyond simply identifying viewing time, the Lead-In Analytics Engine 200 allows the analyst to identify which demographic group viewed each ad along with the geographic area in which the viewing took place.
(662) Advertising Cost Based on Viewership of Ad
(663) The Lead-In Analytics Engine 200 has the advantage of allowing us to support charging for advertising based on actual viewership metrics. The Lead-In Analytics Engine 200 is able to measure the actual viewing seconds of whatever video asset is defined by the Lead-in analysis period. When this defines the time when an advertisement was run, then we are able to determine how much of the advertisement was viewed by each set-top box (video asset viewing device) represented in the channel tuning data. We are able to further break this out by demographic and geographic identifiers. Thus, as a non-limiting example, the Lead-In Analytics Engine 200 will calculate the aggregate viewing seconds of all the set-top boxes (video asset viewing devices) in the channel tuning file for each combination of demographic and geographic code that the analyst has defined in the job input. This data can be used as input to pricing of advertising based on actual viewing seconds for each demographic-geographic group.
(664) As nonlimiting examples, a cable television provider or programming network could: 1. Charge the advertiser based on actual viewing seconds earned by the ad. Example: The base rate to run the advertisement on channel x during the 5:00 pm hour on Monday is amount $y; if the ad earns more than 500,000 viewing seconds, the advertiser is billed a premium of z cents per additional 10,000 viewing seconds. 2. Credit the advertiser based on actual viewing seconds earned by the ad. Example: The base rate to run the advertisement on channel x during the 5:00 pm hour on Monday is amount $y; if the ad earns less than 400,000 viewing seconds, the advertiser is given a credit of z cents for each 10,000 viewing seconds short of 400,000. 3. Charge the advertiser based on actual viewing seconds earned by the ad for a target demographic group. Example: The ad is targeted to the demographic group of families with children and the base rate to run the advertisement on channel x during the 5:00 pm hour on Monday is amount $y; if the ad earns more than 500,000 viewing seconds for the demographic identifier of families with children, the advertiser is billed a premium of z cents per additional 10,000 viewing seconds. 4. Credit the advertiser based on actual viewing seconds earned by the ad for the target demographic group. Example: The base rate to run the advertisement on channel x during the 5:00 pm hour on Monday is amount $y; if the ad earns less than 400,000 viewing seconds by the target demographic group, the advertiser is given a credit of z cents for each 10,000 viewing seconds by that demographic group short of 400,000.
(665) Such metrics would be very helpful to advertisers in knowing how to allocate their advertising dollars.
(666) Advertising Agency Grading
(667) The Lead-In Analytics Engine 200 has the advantage of allowing us to produce metrics needed to grade or measure the effectiveness of the advertising agency. When the lead-in is period defines an advertisement, the Lead-In Analytics Engine 200 allows us to measure (a) set-top boxes (video asset viewing devices) tuned at the start of the lead-in period, (b) set-top boxes tuned at the end of the lead-in period, (c) actual aggregate viewing seconds for the entire lead-in period, (d) impressions greater than a minimum number of seconds during the lead-in period, and (e) how many set-top boxes were tuned for the entire lead-in period. This data can be used as input to valuing the services of the advertising agency allowing us to reward or penalize the advertising agency based on the ability of their ad to retain viewers.
(668) As nonlimiting examples, a company whose product is being advertised could: 1. Reward the advertising agency based on the number of set-top boxes (video asset viewing devices) that remain tuned for the entire duration of the ad. Example: If at the point in time when the advertisement begins to play there are x (150) set-top boxes viewing the ad, and the number of set-top boxes that continue to view the ad until the end of the ad is y (120), then for each percentage point of set-top boxes above base threshold a % (75%) that view the ad to the end, reward the advertising agency a bonus of $z ($1.05) per set-top box that views the ad to the end. In this case, 75% of 150 is 112.5; since 120 were viewing at the end of the ad, the reward is [(120−112)*$1.05=$8.40). 2. Penalize the advertising agency based on the number of set-top boxes that tune away from the ad. Example: If at the point in time when the advertisement begins to play there are x (150) set-top boxes viewing the ad and the drop off rate by the end of the advertisement is more than y % (30%), then for each percentage of drop off below base threshold of y % (30%) penalize the advertising agency a fee of $z ($0.90) per set-top box that drops off above the 30% threshold. In this case, 150*(1−0.30)=105 is the minimum STB's tuned in at the end to avoid penalty; assume there were 88 set-top boxes at the end of the ad, the penalty would be 105−88=17*$0.90=$15.30.
(669) Similar metrics could be developed based on aggregate viewing seconds or impressions.
(670) Demographics Analysis
(671) The Lead-In Analytics Engine 200 is able to merge demographic data with detailed viewing patterns. As the Lead-In Analytics Engine 200 analyzes the channel tuning data, it is able to group the viewers into buckets based on the demographic code associated with the set-top box. This allows us to collect detailed viewing patterns for each demographic group. This allows much deeper levels of analysis.
(672) By combining the viewing data with demographic data, additional information can be determined.
(673) As a nonlimiting example, where the lead-in period defines an advertisement, compare viewing behavior of the lead-in period based on demographic group to identify the group from which the ad earned more viewing seconds. Examples: a. Did the clothing ad earn more viewing seconds with the white viewers or the Hispanic viewers? b. Did the jewelry ad earn more viewing seconds with the male viewers or the female viewers? c. Did the fast food ad earn more viewing seconds with the teen viewers or the adult viewers? d. Did the fast food ad earn more viewing seconds with the low income viewers or the middle income viewers? e. Did the car rental ad earn more viewing seconds with the single viewers or the married viewers?
(674) Geographic Analysis
(675) The Lead-In Analytics Engine 200 is able to merge geographic data with detailed viewing patterns. As the Lead-In Analytics Engine 200 analyzes the channel tuning data, it is able to group the viewers into buckets based on the geographic code associated with the set-top box (video asset viewing device). This allows us to collect detailed viewing patterns for each geographic group. This allows much deeper levels of analysis.
(676) By combining the viewing data with geographic data, additional information can be determined.
(677) As a nonlimiting example, where the lead-in period defines an advertisement, compare viewing behavior of the lead-in period based on geographic group to identify the group from which the ad earned more viewing seconds. Examples: a. Did the clothing ad earn more viewing seconds with the viewers in ad zone x or ad zone y? b. Did the jewelry ad earn more viewing seconds with the viewers in zip code x or zip code y? c. Did the golf ad earn more viewing seconds with the viewers in census tract x or census tract y?
(678) Combination Demographics and Geographic Analysis
(679) Besides these examples, numerous additional examples can be readily imagined simply by combining the demographic and geographic attributes. As nonlimiting examples, one could combine: a. Demographic and geographic identifiers to determine whether a lead-in period that defines an advertisement earns more viewing seconds with white males in zip code x or zip code y. b. Demographic and geographic identifiers to determine whether a lead-in period that defines an advertisement earns more viewing seconds with families with children or retirees in zip code x.
(680) A person skilled in data analysis could readily envision numerous other combinations for investigation.
(681) Benefits for Content Providers
(682) While much of the prior discussion of benefits focused on lead-in segments that defined advertisements, the lead-in period could also identify viewing results for any other video asset such as a news cast, a movie, a pilot program, a sports event, or a regularly scheduled program.
(683) As nonlimiting examples, consider: 1. The content provider has been asked to carry a new program and the analyst desires to get accurate audience measurements. The analyst could define multiple lead-in viewing segments and measure viewership during each lead-in segment. The lead-in segments could be five minutes, ten minutes, fifteen minutes, or the entire hour. The analyst could even run the tuning data through the system with fifteen minute segments and then rerun it with 1 minute segments if desired. The Lead-In Analytics Engine 200 allows us to measure (a) set-top boxes tuned at the start of the lead-in period, (b) set-top boxes tuned at the end of the lead-in period, (c) actual aggregate viewing seconds for the entire lead-in period, (d) impressions greater than a minimum number of seconds during the lead-in period, and (e) how many set-top boxes were tuned for the entire lead-in period. Such metrics could be very useful to a content provider seeking to understand audience behavior. 2. The content provider needs exact viewership metrics to assist in negotiating rates to charge a studio (producer) for carrying a program. This may happen in the case of a low viewership program. The Lead-In Analytics Engine 200 allows the analyst to define a lead-in period of the entire program to measure aggregate viewing seconds for the program. 3. The content provider needs exact viewership metrics to assist in negotiating rates which will be paid by the content provider to the studio (producer) to carry a program. This may happen in the case of a high viewership program. The Lead-In Analytics Engine 200 allows the analyst to define a lead-in period of the entire program to measure aggregate viewing seconds for the program. 4. The content provider needs to know whether a certain video asset earns more viewing minutes during the day or the evening. The Lead-In Analytics Engine 200 allows the analyst to define a lead-in period for the morning show and for the evening show and measure aggregate viewing seconds for each showing. 5. The content provider needs to understand the demographics of the viewing audience for a program. The Lead-In Analytics Engine 200 allows the analyst to define a lead-in period that covers the program of interest and also to define multiple demographic groups and then to measure viewing by each group for that program. 6. The content provider needs accurate audience measurements to assist in negotiating advertising rates for the ads that play during a specific program. The Lead-In Analytics Engine 200 allows the analyst to define multiple lead-in segments and then measure viewing during each segment. These detailed audience measurements can be used to set advertising rates. 7. The content provider needs to know whether a certain video asset earns any viewing minutes. This is instrumental in developing programming schedules. This is very important in managing lightly viewed channels. By defining a lead-in segment for that program, the analyst can use the Lead-In Analytics Engine 200 to measure program viewership. 8. The content provider needs to provide detailed audience measurements for the morning news compared to the evening news. The Lead-In Analytics Engine 200 allows the analyst to define one lead-in segments for the morning news and one for the evening news and then measure viewing during each segment. 9. The content provider needs to provide detailed audience measurements for the local evening news compared to the national evening news. The Lead-In Analytics Engine 200 allows the analyst to define one lead-in segment for the local news and one for the national news and then measure viewing during each segment.
(684) In each of the cases, the Lead-In Analytics Engine 200 produces the metrics needed to answer the question.
(685) Lead-in to Target Viewing Analysis
(686) The Lead-In Analytics Engine 200 also allows the analyst to measure longitudinal viewing behavior. In this case, the lead-in segment defines one or more viewing segments that precede the target segment. The analyst is interested in answering questions such as: 1. If the set-top box (video asset viewing device) is tuned to channel x during a first period of time, does the set-top box stayed tuned to the same channel during a subsequent period of time? 2. Do promotions of an upcoming show increase viewership of that show?
(687) Longitudinal Viewing Analysis
(688) Using Longitudinal Viewing Analysis the analyst can use the Lead-In Analytics Engine 200 to determine viewing habits across a period of time. For example, if a viewer views the 7 PM show, do they also view the 8 PM show. Or, if the viewer views the 6:00 PM news, do they stayed tuned for the next show in the schedule. In this case, the lead-in segment is defined as the 6:00 PM news. The analyst may define one lead-in period for the entire news cast, or multiple lead-in periods. The Lead-In Analytics Engine 200 will measure viewership for each lead-in segment. Then the analyst also defines a target period for analysis. In this example, the target period is the next show. The analyst can define one or many viewing segments for the target show. The Lead-In Analytics Engine 200 will measure viewership for each target segment. Additionally, it will group the viewership into buckets based on how much of the aggregate lead-in viewing the set-top box tuned to. This allows the engine to categorize the viewers based on how much of the lead-in they tuned to.
(689) By grouping target viewers based on how much of the lead-in they tuned to, the Lead-In Analytics Engine 200 is able to differentiate viewers based on viewing during the lead-in period. It can compare target viewing for those who tuned to a small part of the lead-in video with those who tuned to a large part of the lead-in video. This then indicates whether or not the lead-in viewing was effective in drawing various demographic groups to view the target program.
(690) In addition to measuring whether or not the set-top box viewed the target program, the Lead-In Analytics Engine 200 also measures any other viewing by that set-top box. Thus the analyst is able to determine what the viewer watched instead of the target program. This also is done in the context of demographic and geographic identifiers.
(691) Promotional Viewing Analysis
(692) Promotional Viewing Analysis may be used when a content provider want to measure the effectiveness of ads promoting an upcoming program. Each ad promoting the program is treated as a lead-in segment. The promoted program is the target. The Lead-In Analytics Engine 200 then measures viewing for each such lead-in segment on a set-top by set-top basis and for all of the lead-in segments in aggregate for that set-top box. The Engine then measures viewership of the target segment by that set-top box. For Target viewership measurement, the set-top boxes are grouped into histogram groups to identify what part of the total lead-in video the set-top box tuned to. This grouping enables the analyst to compare like to like target viewing. The Lead-In Analytics Engine 200 compares target viewing by set-top boxes that saw perhaps 1 to 10% of the lead-in viewing to determine what percentage of the target they saw.
(693) If a demographic group saw comparatively little of the lead-in video but watched a great deal of the target video, then we could assume that either the lead-in video had very little effect on the customer's viewing choice or that a very small exposure was all that was needed to generate interest in viewing the target program. In either case, the analyst has learned that there is no need to promote that target program very heavily to that demographic.
(694) On the other hand, if a demographic group viewed very little of the target program after heavy exposure to the lead-in video (ads) promoting it, then the analyst has learned that promoting that program to that demographic is wasteful since they are not interested in viewing it.
(695) Additionally, the Lead-In Analytics Engine 200 measures what the viewer watched instead thus allowing the analyst to gain additional insight into the customer behavior.
(696) Subsequent Usage of the Metrics
(697) The metrics produced by the Lead-In Analytics Engine 200 readily lend themselves to dimensional analysis using contemporary data warehouse methods. A Fact table in such an application may contain viewing data for an ad or a program. Multiple Dimension tables can readily be envisioned by those skilled in the art. As non-limiting examples, various values including demographic group, geographic group, industry asset id, industry program id, etc. could be Dimensions. Additionally, other attributes regarding the program content could be included in such an analysis by using the industry program id to join to other reference data that may be available to the analyst.
(698) The metrics produced by the Lead-In Analytics Engine 200 can be loaded to a data warehouse to support additional longitudinal analysis beyond what is done by the Engine. Thus we can readily envision a myriad of uses for the metrics produced by the Lead-In Analytics Engine 200.
(699) Several nonlimiting examples will be reviewed: By analyzing viewer counts of a weekly program from week to week, a program producer can get an early indication of whether a program's viewership is trending up or down and then adjust accordingly. By analyzing commercial viewing trends an advertiser can determine whether an ad has reached a saturation point and people tune away from the ad when they see it, this would suggest the need to run a different ad.
(700) To further expand upon the second example, recognize that advertisers need to know both the audience reach and the viewing frequency of the ads they pay to air. In regard to audience reach, the advertisers want to know how many unique households or set-top boxes have been exposed to an ad. In regard to viewing frequency, the advertisers want to know how many times the household or set-top box has been exposed to the ad.
(701) For audience reach, the Lead-In Analytics Engine 200 can identify at a set-top box (video asset viewing device) level how many unique set-top boxes have been exposed to an ad and the aggregate viewing seconds from those set-top boxes. As this information is tracked over a period of time, the advertiser gains valuable insight into the exposure of the ad and whether interest in the ad is diminishing.
(702) For viewing frequency, the Lead-In Analytics Engine 200 can identify at a set-top box level each time that a set-top box views a particular ad or video asset along with the viewing time in seconds. This information could easily be written to a file and then loaded into a data warehouse in order to support queries showing how many times each set-top box viewed an ad. Along with the viewing counts such a system could also track viewing seconds to determine whether average viewing seconds are declining as ad exposure increases.
(703) All of this could be done using anonymous and/or encrypted set-top box identifiers to protect viewer privacy.
(704) Numerous additional metrics can readily be identified by those skilled in the art. Additionally, numerous additional uses for the metrics identified herein will be readily evident to those skilled in the art.
(705) Other Ramifications
(706) In today's world where the number of media viewing choices is vast, it is often difficult for the viewer to locate the content that he or she might be most interested in receiving. To assist in solving this problem, a content provider could develop viewing profiles that could then be used to suggest content to a viewer. Such profiles can be developed by tracking the viewing history of various groups of viewers. As an example, the Lead-In Analytics Engine 200 can produce metrics which identify the viewing behavior of various groups of people. Perhaps a lead-in video asset that represents a classic movie earns very high viewing rates with one group while a lead-in video asset that represents a mystery movie earns very high viewing rates with another group. Then a system could be setup to suggest candidate movies based on the viewer's viewing group so that a viewer in the first viewing group may be presented with a list of classic movie titles while a viewer in the second group would be presented with a list of mystery movies. The viewer is thus assisted in choosing content.
(707) One can envision an embodiment of the Lead-In Analytics Engine 200 which runs on the set top box, with the viewer's permission, to perform second-by-second analysis of the viewing activity during a program. At the end of a program the Lead-In Analytics Engine 200 could analyze the viewer's activity related to that program. Based on that analysis, an interactive application could ask any number of questions to the viewer such as:
(708) For Identifying Future Programs of Interest:
(709) We noticed that you viewed the entire program. Would you like us to recommend similar programs in the future? Perhaps additional questions could be asked to identify what the viewer liked (the actor/actress, the genre, the setting, etc.) to assist in making viewing recommendations in the future.
(710) For Product Information Requests:
(711) We noticed that you are interested in outdoor programs. Would you like to have a product brochure for the (tent, cook stove, hiking boots, etc.) that were used by (actor name/actress name) sent to your home or email address?
(712) We noticed that you are interested in gourmet cooking. Would you like to have a product brochure for the (brand name) cookware that (actor name/actress name) used on the program?
(713) Actress (actress name) was wearing clothes from (clothing provider). Would you like to receive a coupon for 25% off on the line of clothing that (actress name) was wearing?
(714) Actress (actress name) uses hair care products from (hair care product company). Would you like to receive a coupon for 25% off hair care products from (hair care product company)?
(715) For Product Purchases:
(716) We noticed that you are interested in outdoor programs. Would you like to purchase the (tent, cook stove, knife, etc.) that were used by (actor name/actress name)?
(717) We noticed that you are interested in gourmet cooking. Would you like to purchase a set of the (brand name) cookware that (actor name/actress name) used on the program?
(718) The soundtrack featured in this movie was an original creation. Would you like to purchase this soundtrack for only $1.95 on (music download service)?
(719) In each of the above examples, by having a more complete understanding of what programs the viewer viewed, one could pose relevant marketing questions to the viewer. A set-top box marketing application could be structured around the increased understanding of what the viewer likes to watch.
(720) Summary
(721) I have shown numerous benefits produced by analyzing channel tuning data from a video asset viewing device connected to a network at a second-by-second level of granularity. I have also shown numerous benefits of tracking viewing during one or more lead-in periods and then correlating that with viewing during a target period. These viewing metrics meet pressing needs for detailed audience viewership information that is not presently available.