Source: https://patents.google.com/patent/US9635404B2/en
Timestamp: 2019-07-16 17:22:04
Document Index: 580095703

Matched Legal Cases: ['Application No. 2', 'Application No. 2', 'Application No. 14787754', 'Application No. 14787754', 'Application No. 14787754', 'Application No. 2014257017', 'Application No. 2014257017', 'Application No. 2014257017']

US9635404B2 - Methods and apparatus to correlate census measurement data with panel data - Google Patents
Methods and apparatus to correlate census measurement data with panel data Download PDF
US9635404B2
US9635404B2 US14/132,626 US201314132626A US9635404B2 US 9635404 B2 US9635404 B2 US 9635404B2 US 201314132626 A US201314132626 A US 201314132626A US 9635404 B2 US9635404 B2 US 9635404B2
US14/132,626
US20140325551A1 (en
2013-04-24 Priority to US201361815544P priority Critical
2013-12-18 Application filed by Nielsen Co (US) LLC filed Critical Nielsen Co (US) LLC
2013-12-18 Priority to US14/132,626 priority patent/US9635404B2/en
2014-04-17 Assigned to THE NIELSEN COMPANY (US), LLC reassignment THE NIELSEN COMPANY (US), LLC ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: MCMILLAN, F. Gavin
2014-10-30 Publication of US20140325551A1 publication Critical patent/US20140325551A1/en
2017-04-25 Publication of US9635404B2 publication Critical patent/US9635404B2/en
Methods, apparatus and systems for tagging media in the manner described above are disclosed in U.S. Pat. No. 6,108,637, by Blumenau, entitled “Content Display Monitor,” which is hereby incorporated by reference in its entirety. Because a tag is embedded in the HTML defining a webpage and/or referenced by a pointer in the HTML of a webpage, the tag is executed whenever a web browser renders the corresponding media (e.g., the webpage). Typically, a tag will cause the browser to send a request (sometimes referred to herein as a beacon) to a data collection facility such as an audience measurement entity server that is associated with the audience measurement entity. In some examples, the beacon is an HTTP request (e.g., an HTML GET request, an HTML POST request, etc.). The beacon enables monitoring data reflecting information about the media access to be tracked. To this end, the beacon carries identification information to be collected, compiled and/or analyzed at the audience measurement entity. The identification information may include a user agent string to identify the user device on which the media is requested, a media identifier to identify the media with which the tag is associated (e.g., a website address), a host identifier to identify the host (e.g., web server) with which the requested media is associated (e.g., a vendor identifier (VID)), a timestamp to identify the dates/times at which the media is requested, accessed and/or received, one or more command identifiers identifying control commands (e.g., pause, play, stop, etc.) acted upon the media, etc.
Tags such as those described above may facilitate the collection of census like data. In other words, because every (or nearly every) browser that accesses the tagged media will respond to the tag by sending the beacon (or communication) to the audience measurement entity, every (or nearly every) access to the online media (even to cached media using such tags) will be known by the audience measurement entity. Moreover, the collection of this data does not require the use of a special browser, or of special metering software, at the user devices. Rather, because a beacon may appear to a conventional commercially available browser (e.g., Mozilla® Firefox®, Microsoft® Internet Explorer®, Google Chrome™ browser, etc.) as any other request to retrieve Internet media (e.g., as a request to obtain content or advertisement material to be displayed as part of the webpage) or transmit data, any such browser will participate in the audience measurement process without requiring modification. As a result, tagging enables collection of data from panelists and non-panelists alike. Therefore, data collected via a tagging approach such as that described above, is described herein as census data or census measurement data. Although examples disclosed herein are described in connection with browser-based interfaces used to present online media, disclosed techniques may also be used in connection with non-browser based applications that render media such as service-specific applications (e.g., client applications to stream media).
To address this issue, audience measurement entities (sometimes referred to herein as “ratings entities”) traditionally determine online media reach and frequency based on registered panel members. That is, an audience measurement entity enrolls people that consent to being monitored into a panel. In such panelist-based systems, demographic information is obtained from a user when, for example, the user joins and/or registers for the panel. The demographic information (e.g., race, age or age range, gender, income, home location, education level, etc.) may be obtained from the user, for example, via a telephone interview, an in-person interview, by having the user complete a survey (e.g., an online survey), etc. In some examples, demographic information may be collected for a home. For example, demographic information for a panel home may indicate age ranges of members in a panel home without identifying the number of members in each of the age ranges. Thus, the granularity of the demographic information may depend on whether the demographic information is for a panelist or multiple individuals in a panel home. As used herein, the term “panelist” is generic to both a panelist and a panel home.
Companies such as The Nielsen Company (US), LLC utilize on-device meters to monitor usage of cellphones, tablets (e.g., iPads™) and/or other computing devices (e.g., PDAs, laptop computers, etc.). An on-device meter (ODM) is typically implemented by software that collects data of interest concerning usage of the monitored device. For example, the ODM may collect data indicating media access activities (e.g., website names, dates/times of access, clickstream data and/or other media identifying information (e.g., webpage content, advertisements, etc.)) to which the panelist is exposed. This data is uploaded, periodically or aperiodically, to a data collection facility such as the audience measurement entity server. The data collected by a meter is referred to herein as ODM data or panelist data. ODM data is advantageous in that it can be linked to demographic information because the panelist has provided their demographics as part of the registration and the activity data collected by the ODM can, thus, be associated with that demographic information via, for example, a panelist identifier included in the ODM data transmitted to the audience measurement entity.
FIG. 1 is an illustration of an example environment 100 in which examples disclosed herein may be implemented to correlate census measurement data with panel data. The example environment 100 of FIG. 1 includes an audience measurement entity (AME) server 102, a media hosting server 104 and a client device 106. In some examples, the AME server 102 is implemented using multiple devices and/or the media hosting server 104 is implemented using multiple devices. For example, the AME server 102 and/or the media hosting server 104 may include disk arrays or multiple workstations (e.g., desktop computers, workstation servers, laptops, etc.) in communication with one another. In the illustrated example, the AME server 102 is in selective communication with the media hosting server 104 and/or the client device 106 via one or more wired and/or wireless networks represented by network 108. Example network 108 may be implemented using any suitable wired and/or wireless network(s) including, for example, one or more data buses, one or more Local Area Networks (LANs), one or more wireless LANs, one or more cellular networks, the Internet, etc. As used herein, the phrase “in communication,” including variances thereof, encompasses direct communication and/or indirect communication through one or more intermediary components and does not require direct physical (e.g., wired) communication and/or constant communication, but rather additionally includes selective communication at periodic or aperiodic intervals, as well as one-time events.
In the illustrated example of FIG. 1, the client device 106 is a smartphone (e.g., an Apple® iPhone®, a Motorola™ Moto X™, a Nexus 5, an Android™ platform device, etc.). However, any other type of device may additionally or alternatively be used such as, for example, a tablet (e.g., an Apple® iPad™, a Motorola™ Xoom™, etc.), a laptop computer, a desktop computer, a camera, an Internet compatible television, a smart TV, etc. The client device 106 of FIG. 1 (sometimes referred to herein as a “user device” or “mobile device”) is used to access (e.g., request, receive, render and/or present) online media that is tagged and returned by the media hosting server 104. For example, the user may execute a web browser on the client device 106 to request streaming media (e.g., via an HTTP request) from the media hosting server 104. In response to accessing the tagged media, media impression information, including device location information, is sent to the AME server 102.
FIG. 2 is a diagram of an example message path illustrating metering of tagged media. In the illustrated example of FIG. 2, the example client device 106 transmits a media request 202 for media to the example media hosting server 104 via a browser 200. In some examples, the media request 202 includes a user agent identifying characteristics of the browser 200 and/or the client device 106 such as a browser identifier, a device identifier, etc. The media hosting server 104 of the illustrated example includes media (e.g., a website, an image, a video, etc.) that, when requested by the browser 200, causes the media hosting server 104 to respond with media 204 including a tag 206. The tagged media 204 of the illustrated example includes executable instructions such as an applet (e.g., the tag 206) that, when executed by the browser 200, cause the browser 200 to send a communication (or beacon) including monitoring information (e.g., census measurement data) to the AME server 102. The tag 206 may be included in the requested media in accordance with the teachings of Blumenau, U.S. Pat. No. 6,108,637. Accordingly, the browser 200 transmits an example beacon 210 to the AME server 102. In some such examples, the beacon 210 is a “dummy request” in that it is not actually intended to return data. Instead, the beacon 210 is used to carry monitoring information to the AME server 102. In some examples, the beacon 210 is implemented as an HTTP POST message, an HTTP GET message, or similar message used in present and/or future HTTP protocols. In the illustrated example, the beacon 210 includes a location identifier 212 (e.g., data specifying a device location corresponding to the geographic location at which the media was accessed), a media identifier 214 (e.g., data specifying the media 204) and a timestamp 216 corresponding to the date and/or time for when the media was accessed (e.g., data specifying when the media 204 was received).
In the illustrated example of FIG. 2, the client device 106 includes the positioning system 208 to enable identification of the geographic location of the client device 106. The positioning system 208 of the illustrated example is implemented by a global positioning system (GPS). In some examples, the positioning system 208 uses the Wide Area Augmentation System (WAAS) and may accurately determine the location of the client device 106 between three and five feet. In some examples, the positioning system 208 determines the geographic location (e.g., GPS coordinates) based on signals received from satellites representative of the positions of the satellites in relation to the location of the client device 106. However, in some other examples, the positioning system 208 determines location based on positions of cellular radio towers in relation to the location of the client device 106 (e.g., using a triangulation method). However, any other past, present and/or future method for determining the device location of the client device 106 (e.g., cellular tower triangulation, Wi-Fi data, GPS data sent from another device using a wired and/or wireless network interface such as Bluetooth®, etc.) may be used by the client device 106 to provide location information of the client device 106 when accessing the requested media.
In a similar manner, in response to presenting the requested media including the tag 311, the client device 107 executes the tag 311, which causes the client device 107 to send a beacon 313 to the AME server 102. In addition, executing the executable instructions 311 causes the client device 107 to identify a geographic location of the client device 107. In the illustrated example of FIG. 3, the client device 107 does not include a positioning system, but may receive location information from a proximate device. In the illustrated example, the metering equipment 302 broadcasts geographic location information 315 that may be received by nearby devices. For example, the metering equipment 302 of the illustrated example broadcasts the geographic location information 315 via a Bluetooth® interface. In some such examples, if the client device 107 also includes a Bluetooth interface, the client device 107 receives the geographic location information 315 from the metering equipment 302 and transmits the geographic location information 315 to the AME 102 as a location identifier in the beacon 313.
FIG. 5 is an example data table 500 storing data representing tagged media impressions that may be collected by the example AME server 102 of FIGS. 1-4. In the illustrated example of FIG. 5, the data table 500 identifies a requested website 502, a device location 504, a timestamp from the client device of the request 506 and a possible panel data flag 508 indicating whether an impression is panel data or is census data. In the illustrated example, the AME server 102 extracts the device location from the location identifier 212 of the beacon 210 when the location identifier is present. For example, the impression entry 510 indicates that a user requested the website (Host1.com) at 9:15:00 AM on Nov. 10, 2013, from a device location with GPS coordinates (41.87989, −87.637158). Further, since the impression entry 510 includes a device location, the impression entry 510 is flagged as possible panel data, depending on whether the device location satisfies a threshold (e.g., the calculated distance between the device location and a reference location is within the threshold) and/or the device location is positioned within a reference area. In contrast, in the impression entry 512, the user who accessed the website (Host2.com) at 9:45:05 AM on Nov. 10, 2013, did so with a client device that did not provide device location information for the client device when it provided the beacon. As a result, the impression entry 512 is flagged as census data (e.g., not possible panel data). In some examples, the data table 500 may include additional information such as device identifiers (e.g., a telephone number of the client device, a media access control (MAC) address of the client device, a serial number of the client device, etc.), a vendor identifier (e.g., the person/entity to which the website 502 is registered), a browser identifier, a control action identifier (e.g., a control action such as play, stop, pause, etc. that triggers a media request), a cookie, etc.
FIG. 6 is an example data table 600 that may be stored by the example AME server 102 of FIGS. 1-4 to facilitate associating monitoring information with panelist information. In the illustrated example of FIG. 6, the data table 600 associates a panelist identifier 602 with a reference type 603 (e.g., a house, an apartment, an office building, etc.) and a reference location 604. For example, in row 616, the panelist identifier (10001) is associated with the reference location provided by the GPS coordinates (41.87989, −87.637158). Further, in row 616, the reference location 604 corresponds to a duplex apartment. As discussed above, the reference location 604 may be obtained by, for example, a technician visiting a panelist home, metering equipment included in the panelist home and/or metering hardware (e.g., a portable meter) or software (e.g., an on-device meter included in a monitored device) that is in possession of the panelist. In addition, the example data table 600 includes a reference area 605 that corresponds to the reference type 603. For example, the radius may vary based on whether the reference type is a house, an apartment, a gym, etc. Further, the example data table 600 includes demographic information associated with the registered panelists. For example, the data table 600 of FIG. 6 includes a gender identifier 606, an age range 608, a city of residence 610 and a relationship status 612 for the panelists included in the data table 600. Thus, for example, in row 620, a registered panelist with the panelist identifier (10003) is associated with the reference location provided by GPS coordinates (39.739166, −104.984720), and is also a female between the ages of 18 and 34, who lives in Denver, Colo., and is single. In some examples, a panelist is associated with two or more reference locations. In some such examples, the different reference locations may correspond to known locations where the panelists accesses media. For example, in row 620, the reference location 604 is associated with an apartment the panelist may live at; in row 622, the reference location 604 is associated with a gym the panelist frequents; and, in row 624, the reference location 604 is associated with a vacation home that the panelists owns. In this manner, correlating census data with panel data is not limited to a single location. Rather, census data collected at different locations may be correlated with the same panel data. In some examples, the data table 600 may include additional information associated with the reference location such as the type of residence (e.g., an apartment unit, a house, etc.), whether the metering equipment is located near an external wall, etc. In some examples, the data table 600 may include more demographic information associated with the registered panelists such as, for example, race, income, level of education completed, occupation, etc. By using geographic locations for the tagged media system and the panelists log, user privacy of the panelist is protected. For example, personally-identifying information is not revealed while transmitting information (e.g., the monitoring information) to the AME server 102 and/or the client device 106. Further, in some examples, the location identifiers, the monitoring information and/or the beacon 210 may be encrypted for increased privacy.
As mentioned above, the example processes of FIGS. 8, 9, 11 and/or 12 may be implemented using coded instructions (e.g., computer and/or machine readable instructions) stored on a tangible computer readable storage medium such as a hard disk drive, a flash memory, a read-only memory (ROM), a compact disk (CD), a digital versatile disk (DVD), a cache, a random-access memory (RAM) and/or any other storage device or storage disk in which information is stored for any duration (e.g., for extended time periods, permanently, for brief instances, for temporarily buffering, and/or for caching of the information). As used herein, the term tangible computer readable storage medium is expressly defined to include any type of computer readable storage device and/or storage disk and to exclude propagating signals and to exclude transmission media. As used herein, “tangible computer readable storage medium” and “tangible machine readable storage medium” are used interchangeably. Additionally or alternatively, the example processes of FIGS. 8, 9, 11 and/or 12 may be implemented using coded instructions (e.g., computer and/or machine readable instructions) stored on a non-transitory computer and/or machine readable medium such as a hard disk drive, a flash memory, a read-only memory, a compact disk, a digital versatile disk, a cache, a random-access memory and/or any other storage device or storage disk in which information is stored for any duration (e.g., for extended time periods, permanently, for brief instances, for temporarily buffering, and/or for caching of the information). As used herein, the term non-transitory computer readable medium is expressly defined to include any type of computer readable storage device and/or storage disk and to exclude propagating signals and to exclude transmission media. As used herein, when the phrase “at least” is used as the transition term in a preamble of a claim, it is open-ended in the same manner as the term “comprising” is open ended.
FIG. 10 is an example applet 1000 including pseudo code that may be executed to generate a beacon in response to accessing tagged media at a client device. For example, the applet 1000 may be embedded in the media 204. In the illustrated example of FIG. 10, the applet 1000 includes an example monitoring information retrieval section 1002 and an example beacon transmission section 1004. In the illustrated example, the monitoring information retrieval section 1002 defines the values of the monitoring information (e.g., the location identifier 212, the media identifier 214, the timestamp 216) included in the beacon 210. For example, the monitoring information retrieval section 1002 includes an example location identifier defining block 1006, an example media identifier defining line 1008 and an example timestamp defining line 1010. The example location identifier defining block 1006 of FIG. 10 determines whether the client device 106 has access to a location application programming interface (API) and defines the value for the location identifier 212 accordingly. For example, when the client device 126 has access to the location API, line 1006A retrieves device location information via the location API and stores the value for the location identifier 212. Otherwise, if the client device 126 does not have access to the location API, line 1006B stores a value indicating that no device location is provided (e.g., a null or empty value, “False,” “N/A,” “0,” etc.). In the illustrated example, the media identifier defining line 1008 retrieves media identification information from the media 204 and stores the value for the media identifier 214. In the illustrated example, the timestamp defining line 1010 retrieves date and time information for the media request and stores the value for the timestamp 216.
FIG. 13 is a block diagram of an example processor platform 1300 capable of executing the instructions of FIGS. 8, 9, 11 and/or 12 to implement the example AME server 102 of FIGS. 1-4. The processor platform 1300 can be, for example, a server, a personal computer, a mobile device (e.g., a cell phone, a smart phone, a tablet such as an iPad™), a personal digital assistant (PDA), an Internet appliance, a DVD player, a CD player, a digital video recorder, a Blu-ray player, a gaming console, a personal video recorder, a set top box, or any other type of computing device.
instructing, via a first computing device of a monitoring entity, a media provider to associate a tag with media, the tag to cause a requesting device accessing the media to send a message to the monitoring entity when the media is accessed by the requesting device, the message to identify a geographic location of the requesting device and media identifying information, wherein the message does not include a registered panelist identifier;
accessing the message with a second computing device of the monitoring entity;
determining, with the second computing device of the monitoring entity, locations of a plurality of panelist homes;
comparing, with the second computing device of the monitoring entity, the geographic location of the requesting device with the locations of the plurality of panelist homes, the plurality of panelist homes having Flail reference areas associated therewith; and
when the geographic location of the requesting device is within a reference area of a first one of the plurality of panelist homes:
identifying an unknown user of the requesting device as a panelist residing at the first one of the panelist homes; and
associating the media identifying information with panelist data associated with the first one of the panelist homes.
a tag handler to instruct a media provider to associate a tag with media, the tag to cause a device accessing the media to send a message to a monitoring entity who does not provide or deliver the media when the media is accessed by the device, the message to identify a geographic location of the device and media identifying information, wherein the message does not include a registered panelist identifier;
a beacon handler to access the message;
a location handler to identify locations of a plurality of panelist homes;
the location handler to compare the geographic location of the device with the locations of the plurality of panelist homes, the plurality of panelist homes having reference areas associated therewith;
a comparator to determine whether the geographic location of the device is within a reference area of a first one of the plurality of panelist homes; and
a panelist associator to identifying an unknown user of the device as a panelist residing at the first one of the panelist homes and associate the media identifying information to panelist data associated with the first panelist home when an output of the comparator indicates the geographic location of the device is within the reference area of a first one of the plurality of panelist homes.
19. A tangible computer readable storage medium comprising instructions that, when executed, cause a processor to at least:
instruct a media provider to associate a tag with media, the tag to cause a device accessing the media to send a message to a monitoring entity when the media is accessed by the device, the message to identify a geographic location of the device and media identifying information, wherein the message does not include a registered panelist identifier;
determine locations of a plurality of panelist homes;
compare the geographic location of the device with the locations of the plurality of panelist homes; and
when the geographic location of the device is within a reference area of a first one of the plurality of panelist homes:
identifying an unknown user of the device as a panelist residing at the first one of the panelist homes; and
associate the media identifying information with panelist data associated with the first one of the panelist homes.
21. The tangible computer readable storage medium as defined in claim 19, wherein the instructions further cause the processor to:
determine a portion of the message is encrypted; and
US14/132,626 2013-04-24 2013-12-18 Methods and apparatus to correlate census measurement data with panel data Active US9635404B2 (en)
US201361815544P true 2013-04-24 2013-04-24
US14/132,626 US9635404B2 (en) 2013-04-24 2013-12-18 Methods and apparatus to correlate census measurement data with panel data
PCT/US2014/035332 WO2014176443A1 (en) 2013-04-24 2014-04-24 Methods and apparatus to correlate census measurement data with panel data
JP2015524518A JP5924720B2 (en) 2013-04-24 2014-04-24 Method and apparatus for associating a census measurement data and panel data
AU2014257017A AU2014257017B2 (en) 2013-04-24 2014-04-24 Methods and apparatus to correlate census measurement data with panel data
EP14787754.2A EP2989801B1 (en) 2013-04-24 2014-04-24 Methods and apparatus to correlate census measurement data with panel data
MX2014014736A MX343495B (en) 2013-04-24 2014-04-24 Methods and apparatus to correlate census measurement data with panel data.
CA2875431A CA2875431C (en) 2013-04-24 2014-04-24 Methods and apparatus to correlate census measurement data with panel data
CN201480001436.0A CN104584565B (en) 2013-04-24 2014-04-24 Make census data measurement method and apparatus survey data related
IN10165/DELNP/2014A IN2014DN10165A (en) 2013-04-24 2014-11-28 Methods and apparatus to correlate census measurement data with panel data
US15/458,399 US10148987B2 (en) 2013-04-24 2017-03-14 Methods and apparatus to correlate census measurement data with panel data
US16/167,014 US20190058911A1 (en) 2013-04-24 2018-10-22 Methods and apparatus to correlate census measurement data with panel data
US15/458,399 Continuation US10148987B2 (en) 2013-04-24 2017-03-14 Methods and apparatus to correlate census measurement data with panel data
US20140325551A1 US20140325551A1 (en) 2014-10-30
US9635404B2 true US9635404B2 (en) 2017-04-25
ID=51790485
US14/132,626 Active US9635404B2 (en) 2013-04-24 2013-12-18 Methods and apparatus to correlate census measurement data with panel data
US15/458,399 Active US10148987B2 (en) 2013-04-24 2017-03-14 Methods and apparatus to correlate census measurement data with panel data
US16/167,014 Pending US20190058911A1 (en) 2013-04-24 2018-10-22 Methods and apparatus to correlate census measurement data with panel data
US (3) US9635404B2 (en)
EP (1) EP2989801B1 (en)
JP (1) JP5924720B2 (en)
CN (1) CN104584565B (en)
AU (1) AU2014257017B2 (en)
CA (1) CA2875431C (en)
IN (1) IN2014DN10165A (en)
MX (1) MX343495B (en)
WO (1) WO2014176443A1 (en)
US20090106362A1 (en) 2007-10-23 2009-04-23 Cisco Technology, Inc. Wirelessly-enabled identification of digital media generated at an event
KR20110026300A (en) 2009-09-07 2011-03-15 엘지전자 주식회사 Method for receiving advertisement based on user activity patterns, and mobile device using the same
EP2512150A2 (en) 2011-04-12 2012-10-17 The Nielsen Company (US), LLC Methods and apparatus to generate a tag for media content
KR20120126101A (en) 2010-03-12 2012-11-20 알까뗄 루슨트 Method for automatically tagging media content, media server and application server for realizing such a method
US20130072150A1 (en) 2011-05-27 2013-03-21 Ralph K. Williamson Methods and apparatus to associate a mobile device with a panelist profile
CN102665110A (en) * 2012-05-11 2012-09-12 北京海尔集成电路设计有限公司 Ground television monitoring method, system, wireless set top box and monitoring server
2013-12-18 US US14/132,626 patent/US9635404B2/en active Active
2014-04-24 JP JP2015524518A patent/JP5924720B2/en active Active
2014-04-24 EP EP14787754.2A patent/EP2989801B1/en active Active
2014-04-24 CA CA2875431A patent/CA2875431C/en active Active
2014-04-24 AU AU2014257017A patent/AU2014257017B2/en active Active
2014-04-24 MX MX2014014736A patent/MX343495B/en active IP Right Grant
2014-04-24 CN CN201480001436.0A patent/CN104584565B/en active IP Right Grant
2014-04-24 WO PCT/US2014/035332 patent/WO2014176443A1/en active Application Filing
2014-11-28 IN IN10165/DELNP/2014A patent/IN2014DN10165A/en unknown
2017-03-14 US US15/458,399 patent/US10148987B2/en active Active
2018-10-22 US US16/167,014 patent/US20190058911A1/en active Pending
Canadian Intellectual Property Office, "Office Action," issued in connection with Application No. 2,875,431, Dec. 2, 2015, 5 pages.
Canadian Intellectual Property Office, "Office Action," issued in connection with Canadian Patent Application No. 2,875,431, mailed Dec. 21, 2016, 4 pages.
European Patent Office, "Communication pursuant to Rules 161(2) and 162 EPC," issued in connection with Application No. 14787754.2, Dec. 1, 2015, 2 pages.
European Patent Office, "Communication Pursuant to Rules 70(2) and 70a(2) EPC," issued in connection with European Patent Application No. 14787754.2, mailed Jan. 20, 2017, 1 page.
European Patent Office, "Extended Search Report," issued in connection with European Patent Application No. 14787754.2, mailed Jan. 3, 2017, 7 pages.
Instituto Mexicano De La Propiedad Industrial, "Notice of Allowance," issued in connection with Mexican Patent Application No. MX/a/2014/014736, Jul. 13, 2016, 2 pages.
International Searching Authority, "International Search Report and Written Opinion of the International Searching Authority," issued in connection with corresponding International Patent Application No. PCT/US2014/035332, mailed Aug. 22, 2014 (11 pages).
IP Australia, "Notice of Acceptance," issued in connection with Application No. 2014257017, Oct. 28, 2015, 2 pages.
IP Australia, "Notice of Grant," issued in connection with Application No. 2014257017, Feb. 25, 2016, 1 page.
IP Australia, "Patent Examination Report No. 1," issued in connection with Application No. 2014257017, May 20, 2015, 2 pages.
Patent Cooperation Treaty, "International Preliminary Report on Patentability," issued in connection with Application No. PCT/US2014/035332, Nov. 5, 2015, 8 pages.
CA2875431C (en) 2018-03-06
EP2989801B1 (en) 2018-01-31
IN2014DN10165A (en) 2015-08-21
AU2014257017A1 (en) 2014-12-18
WO2014176443A1 (en) 2014-10-30
MX343495B (en) 2016-11-07
US20140325551A1 (en) 2014-10-30
US20170188068A1 (en) 2017-06-29
MX2014014736A (en) 2015-08-12
EP2989801A1 (en) 2016-03-02
US20190058911A1 (en) 2019-02-21
CN104584565A (en) 2015-04-29
US10148987B2 (en) 2018-12-04
CN104584565B (en) 2017-11-28
JP5924720B2 (en) 2016-05-25
EP2989801A4 (en) 2017-01-25
JP2015532029A (en) 2015-11-05
CA2875431A1 (en) 2014-10-30
AU2014257017B2 (en) 2015-11-12
CN103984762A (en) 2014-08-13 Content rendering control system and method
US20150237395A1 (en) 2015-08-20 Systems and methods for enhancing audience measurement data
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MCMILLAN, F. GAVIN;REEL/FRAME:032696/0480