This disclosure relates generally to audience measurement and, more particularly, to methods and apparatus to obtain anonymous audience measurement data from network server data for particular demographic and usage profiles.
Media content is provided to audiences using a variety of non-traditional techniques, such as via the Internet and various mobile telephone networks. Accordingly, content providers and advertisers are eager to extend audience measurement of media content consumption beyond traditional broadcast television markets. However, conventional panel-based techniques for audience measurement in traditional television markets can be expensive to implement due to challenges encountered in recruiting a panel that yields a representative sample of the desired demographic profile. Additionally, because such panels typically include only a small subset of all audience members, the conventional panel-based techniques often do not capture content accessed by relatively few audience members (e.g., such as niche content). Although allowing an audience measurement entity to access gateway and other network server logs tracking data traffic (including access to media content), as well as customer relationship databases storing customer data that may be used to determine customer demographics, would avoid requiring a panel, such access is generally not feasible due to privacy concerns.
Methods and apparatus to obtain anonymous audience measurement data from network server data for particular demographic and usage profiles are disclosed herein. Although the following discloses example methods and apparatus including, among other components, software executed on hardware, it should be noted that such methods and apparatus are merely illustrative and should not be considered as limiting. For example, it is contemplated that any or all of these hardware and software components could be implemented exclusively in hardware, exclusively in software, exclusively in firmware, or in any combination of hardware, software, and/or firmware. Additionally, though described in connection with example implementations using mobile/wireless networks, access points and other network structures and devices, the example methods and apparatus described herein are not limited thereto. Accordingly, while the following describes example methods and apparatus, persons having ordinary skill in the art will readily appreciate that the examples provided are not the only way to implement such methods and apparatus.
As used herein, the term customer generally refers to any person or entity able to consume media content provided by any provider, source, technology, etc. As such, a customer can be an audience member, a subscriber, a user, a viewer, a listener, etc. Furthermore, a customer as referred to herein is not limited to a paying customer and includes a customer able to access content without any exchange of payment or without having any other relationship with the provider of the content.
In an example disclosed technique to provide anonymous audience measurement data to an audience measurement entity, an example representative sampling unit is included in a service provider's network and obtains a demographic profile and a network usage profile from the audience measurement entity, which is separate from the service provider. In an example implementation, the demographic profile includes a set of demographic categories, with each demographic category including a set of target segments associated respectively with a set of target population percentages. Similarly, the network usage profile in such an example implementation includes a set of usage categories associated respectively with another set of target population percentages.
Given the demographic profile and the network usage profile specified by the audience measurement entity, the representative sampling unit then samples customer data stored in a customer database not accessible by the audience measurement entity to generate, without customer intervention, a customer sample representative of the demographic profile and the network usage profile. In an example implementation, the generated customer sample includes customer identification information, such as phone numbers, Internet protocol (IP) addresses, usernames, personal identification numbers (PINs), cookie identifiers, etc., as well as other demographic information, for a subset of customers representative of the demographic profile and the network usage profile. Using the customer identification information included in the generated customer sample, the representative sampling unit is able to retrieve and process log data from a network server, such as a gateway or other network server, not accessible by the audience measurement entity to determine audience measurement data associated with customers in the customer sample. To render the audience measurement data anonymous, the representative sampling unit scrubs the audience measurement data to remove any customer identification information (e.g., and to replace such removed information with anonymous identifiers incapable of identifying particular customers) before providing the data to the audience measurement entity. However, the anonymous measurement data retains other demographic information to enable classification of the data according to the specified demographic and network usage profiles.
Unlike many conventional audience measurement techniques, the example anonymous server sampling techniques described herein do not utilize customer/audience panels. Instead, the example techniques described herein determine anonymous audience measurement data directly from (1) a service provider's customer relationship database(s) storing customer information records/data that include identification and demographic data, and (2) the service provider's network server logs that track data traffic/events associated with, for example, media server and/or media content access. Additionally, the anonymous audience measurement data is determined by the representative sampling unit to be representative of demographic and usage profiles initially specified by an audience measurement entity, unlike many conventional techniques in which the demographic composition is unknown until after the measurement data is processed. Furthermore, in the disclosed example anonymous server sampling techniques, the audience measurement entity is separate from the service provider, in contrast with other measurement techniques in which the service provider also acts as the measurement entity. However, because the audience measurement data is anonymous when exported to the audience measurement entity, privacy is maintained despite the fact that the audience measurement entity is separate from the service provider.
Turning to the figures, a block diagram of an example environment of use 100 in which an example representative sampling unit 105 may obtain anonymous audience measurement data from network server data for particular (e.g., specified) demographic and usage profiles is illustrated in
The provider network 110 includes one or more example customer databases 115 storing customer records containing customer data associated with customers of the service provider. A customer database 115 can correspond to, for example, a customer relationship management (CRM) database, a RADIUS server, etc., or any other type of database or server storing customer-related information to enable the service provider to provide media content and other communication services to its customers. In examples in which the provider network 110 includes multiple customer databases 115, some or all of the multiple customer databases 115 may be co-located or reside in separate locations. In the illustrated example, the customer data stored in the customer records of the customer database(s) 115 includes customer identification and other demographic information. Examples of the customer identification information stored in the customer database(s) 115 can include, but is not limited, customer device identification information, such as any, some or all of phone numbers of mobile and/or other phones used by customers to access the provider network 110, IP addresses, medium access control (MAC) addresses and/or other device identifying information for customer devices used to access the provider network 110, etc. Customer identification information can also include personal identification information, such as any, some or all of customer names, addresses, identification numbers, account numbers, etc. Examples of other demographic information stored in the customer database(s) 115 can include, but is not limited, information regarding any, some or all of a customer's age, ethnicity, income, education, etc., (e.g., provided voluntarily by customers in applications for service, in response to one or more customer surveys, etc.) as well as information concerning services, products, subscriptions, etc., purchased by the customer from the service provider.
The provider network 110 also includes one or more example networks servers 120 to route and otherwise process data traffic within the provider network 110. A network server 120 can correspond to, for example, a gateway, such as a wireless access point (WAP) gateway, a router, a customer access server (CAS), an IP probe, a proxy server, a content adaptation server, etc. In examples in which the provider network 110 includes multiple networks servers 120, some or all of the multiple networks servers 120 may be co-located or reside in separate locations. Additionally, the networks server(s) 120 may be co-located with or reside in locations separate from the customer database(s) 115. The network server(s) 120 maintain server logs that track data traffic and other network events associated with customer use of the provider network 110. For example, the server logs may track the addresses of particular media content and/or other content servers, hosts, etc., accessed by customer devices, the names of particular media or other content accessed, the times when the servers/hosts and/or the content was accessed, etc. Additionally, the server log data is indexed by customer device identification information (e.g., such as device phone numbers, IP addresses, etc.) to enable association of data traffic and network events with particular customer devices and, thus, particular customers.
The provider network 110 is a secure and private network protected by an example firewall 125, which may be implemented by any type of firewall device or application. Because the provider network is secure and private, the representative sampling unit 105 is included in the provider network 110 to allow an audience measurement entity that is separate from the service provider to obtain audience measurement data derived from the customer data stored in the customer database(s) 115 and the server logs stored by the network server(s) 120, even though the customer database(s) 115 and the network server(s) 120 are inaccessible by the audience measurement entity. Furthermore, to maintain customer privacy, the audience measurement data provided by the representative sampling unit 105 to the audience measurement entity is anonymous and, thus, does not contain personal identification information, but can include other demographic information.
In the illustrated example, the representative sampling unit 105 generates the anonymous measurement data for a subset of customers having a particular demographic profile and a particular network usage profile specified by the audience measurement entity. For example, given specified demographic and network usage profiles, the representative sampling unit 105 samples (e.g., once or via several iterations) the customer data stored in the customer database(s) 115 to generate, without customer intervention, a customer sample containing a subset of customers representative of the specified demographic and network usage profiles. Additionally or alternatively, the customer database(s) 115 may already determine and track the demographics and/or network usage of the customers of the provider network 110. In such an example, the representative sampling unit 105 may interrogate the customer database(s) 115 to obtain the demographic and/or network usage profiles as determined and tracked by the customer database(s) 115 (e.g., instead of receiving the demographic and/or usage profiles from the audience measurement entity). The representative sampling unit 105 may also interrogate the customer database(s) 115 to obtain a customer sample representative of these demographic and/or network usage profiles as determined and tracked by the customer database(s) 115. Then, in any of these examples, using customer identification information (e.g., customer device identification information) included in the generated customer sample (e.g., generated from the demographic and/or usage profiles provided by the audience measurement entity or determined and tracked by the customer database(s) 115), the representative sampling unit 105 retrieves and processes log data from the network server(s) 120 to determine audience measurement data associated with the customers in the customer sample. The representative sampling unit 105 removes any customer identification information from the audience measurement data determined from the server logs to maintain privacy (e.g., and replaces such removed information with anonymous identifiers), but retains other demographic information to enable classification of the anonymous audience measurement data according to the specified demographic and network usage profiles. An example implementation of the representative sampling unit 105 is illustrated in
In the illustrated example, the representative sampling unit 105 communicates with one or more example measurement servers 130 included in an example measurement entity network 135 using an example secure communication link 140 carried via an example communication network 145, such as the Internet, a dedicated network, or any other type of communication network. The measurement entity network 135 is also a secure, private network, and is protected by an example firewall 150, which may be implemented by any type of firewall device or application. The secure communication link 140 can be implemented by, for example, a virtual private network (VPN), a secure file transfer protocol (FTP) session, etc.
The measurement server(s) 130 accept profile configuration file(s) 155 specifying a particular demographic profile and a particular network usage profile for which audience measurement data is to be determined by the representative sampling unit 105. The measurement server(s) 130 convey the demographic and network usage profiles specified via the profile configuration file(s) 155 to the representative sampling unit 105 via the secure communication link 140. Examples of a demographic profile and a network usage profile that could be specified using the profile configuration file(s) 155 are illustrated in
The measurement server(s) 130 also generate report(s) 160 from the anonymous audience measurement data determined by the representative sample unit 105 and downloaded to the measurement server(s) 130 via the secure communication link 140. The report(s) 160 utilize any appropriate reporting format and include, for example, audience ratings, media content access metrics (e.g., such as popularity rankings). Furthermore, the report(s) 160 can report the audience measurement data for the entire specified demographic and network usage profiles, or some subset (e.g., classification stratum or strata) of the specified demographic and/or network usage profiles.
While an example manner of implementing the environment of use 100 has been illustrated in
A block diagram of an example implementation of the representative sampling unit 105 of
Turning to
The example network usage profile 310 includes three (3) usage categories (or strata) 352-356 (although more or fewer categories could be included in an example implementation). For example, the first usage category (or stratum) 352 corresponds to customers that exhibit low network usage, the second usage category 354 corresponds to customers that exhibit medium network usage, and the third usage category 352 corresponds to customers that exhibit high network usage. Network usage can be characterized in terms of, for example, network accesses during a time period, bandwidth used during a time period, bandwidth purchased during a time period, etc. For example, a low network user could be a customer who accesses content via the provider network 110 approximately one time per week, a medium network user could be a customer who accesses content from one to five times per week, and a high network user could be a customer who accesses content greater than five times per week. As another example, a low network user could be a customer who accesses or purchases less than one megabyte of content per week, a medium network user could a customer who accesses or purchase from one to five megabytes of content per week, and a high network user could be a customer who accesses or purchases greater than five megabytes of content per week. These preceding values are exemplary and not meant to be limiting. Similar to the demographic profile 305, each category (or stratum) 352-356 in the network usage profile 310 is associated with a respective target population percentage 362-366, which can be a particular percentage value or a range of percentage values.
Returning to
In at least some example implementations, customer network usage information is also stored in the customer database(s) 115 (e.g., such as when network usage corresponds to purchased network bandwidth). In such examples, the customer sample generator 210 can use the customer database interface 215 as described above to generate another customer sample representative of the obtained network usage profile by indexing the customer data stored in the customer database according to the set of network categories included in the obtained network usage profile, and then randomly sampling (e.g., selecting) the indexed customer data according to the target population percentages included in the obtained network usage profile to randomly select a subset of customers representative of the network usage profile. Additionally or alternatively, the customer sample generator 210 can use the customer database interface 215 to generate a single customer sample representative of both the obtained demographic and network usage profiles. With reference to the example demographic profile 305 and the example network usage profile 310 of
The customer sample generator 210 can employ any type of random or pseudorandom sampling technique to sample the customer data included in the customer database(s) 115. After generating customer sample(s) representative of the obtained demographic profile (and/or the obtained network usage profile if network usage information is stored in the customer database(s) 115), the customer sample generator 210 stores the generated customer sample(s) in a customer sample storage 220. The customer sample storage 220 may be implemented by any type or memory or storage device or technology, such as the mass storage device 730 and/or the volatile memory 718 included in the example processing system 700 illustrated in
The representative sampling unit 105 also includes an example measurement data sampler 225 to obtain and process server log data for the customers included in the customer sample(s) stored in the customer sample storage 220. For example, the measurement data sampler 225 uses an example server log interface 230 to retrieve server log data from the network server(s) 120 for customers included in a customer sample generated by the customer sample generator 210, but not for customers not included in the customer sample. Alternatively, in an example real-time sampling implementation, the measurement data sampler 225 configures the network server(s) 120 to automatically provide (e.g., via a push mechanism) the server log data for customers included in the customer sample generated by the customer sample generator 210, but not for customers not included in the customer sample. In an example implementation, customer identification information and, in particular, customer device identification information (e.g., such as phone numbers, IP addresses, usernames, PINs, cookie identifiers, etc.) included in the customer sample is used to retrieve the server log data for those customers included in the customer sample, or configure the network server(s) 120 to automatically provide (e.g., push) the server log data for those customers included in the customer sample. Thus, for each customer in the customer sample, server log data that includes or is otherwise associated with customer identification information (e.g., such as a phone numbers IP address, etc.) representative of that particular customer is retrieved or otherwise obtained (e.g., automatically via a push mechanism) by the measurement data sampler 225 from the network server(s) 120.
To generate audience measurement data (e.g., offline using the retrieved server log data or in real-time using the automatically provided/pushed server log data), the measurement data sampler 225 then classifies the server log data for each customer in the customer sample into the particular demographic category or categories into which the particular customer belongs (as well as into the particular customer's network usage category if known from the customer data stored in the customer database(s) 115). Additionally or alternatively, such as in example implementations in which customer network usage information is not stored in the customer database(s) 115, the measurement data sampler 225 processes the server log data to determine the network usage category for each customer in the customer sample, thereby allowing the measurement data sampler 225 to classify the particular customer's server log data into a particular network usage category. For example, the measurement data sampler 225 may analyze the server log data to determine the network accesses during a time period, bandwidth used during a time period, etc., to determine the network usage category for each customer included in the customer sample and, thus, the actual network usage profile of the customer sample.
The representative sampling unit 105 further includes an example profile verifier 240 to determine whether the server log data retrieved and processed by the measurement data sampler 225 corresponds to (e.g., is representative of) the demographic and network usage profiles obtained by the profile specifier 205 as specified by the audience measurement entity. For example, in operating scenarios in which the customer databases(s) 115 do not store network usage information for each customer, the customer sample generated by the customer sample generator 210 will be representative of the obtained demographic profile, but may or may not be representative of the obtained network usage profile. In such operating scenarios, the profile verifier 240 compares the actual network usage profile for the customer sample (e.g., as determined by the measurement data sampler 225 from the server log data) with the obtained network usage profile to determine whether the profiles match or substantially match within some tolerance limit for each network usage category. If the profiles do not match, the profile verifier 240 causes the customer sample generator 210 to update the customer sample by, for example, (1) randomly removing customers from the sample belonging to each network usage category whose actual percentage of customers exceeds the specified percentage, and (2) replacing the removed customers with new, randomly sampled customers belonging to the same demographic categories as the removed customers. The measurement data sampler 225 then obtains server log data for these newly sampled customers and recomputes the actual network usage profile for the updated customer sample. This profile verifier 240 iteratively repeats this procedure until the actual network usage profile of the customer sample matches the specified network usage and demographic profiles and/or a specified number of iterations is performed.
To render the resulting audience measurement data determined by the measurement data sampler 225 and verified by the profile verifier 240 private, the representative sampling unit 105 includes an example privacy unit 245. The privacy unit 245 removes any customer identification information that could be used to identify particular customers, such as customer device identification information (e.g., phone numbers, IP addresses, etc.) included in the audience measurement data (e.g., as part of the retrieved server log data). In some examples, the privacy unit 245 replaces the removed customer identification information with anonymous identifiers that can be used to group associated data without actually identifying any of the customers. However, the privacy unit 245 retains any demographic and usage classification information included in the audience measurement data (e.g., as determined by the measurement data sampler 225). The representative sampling unit 105 includes a data transmission unit 250 to transmit the anonymous audience measurement data to the measurement server(s) of the audience measurement entity for subsequent processing.
While an example manner of implementing the representative sampling unit 105 of
Flowcharts representative of example machine readable instructions that may be executed to implement the example environment of use 100, the example representative sampling unit 105, the example provider network 110, example customer database(s) 115, the example networks server(s) 120, the example firewall 125, the example measurement server(s) 130, the example measurement entity network 135, the example secure communication link 140, the example communication network 145, the example firewall 150, the example profile specifier 205, the example customer sample generator 210, the example customer database interface 215, the example customer sample storage 220, the example measurement data sampler 225, the example server log interface 230, the example profile verifier 240, the example privacy unit 245 and/or the example data transmission unit 250 are shown in
For example, any or all of the example environment of use 100, the example representative sampling unit 105, the example provider network 110, example customer database(s) 115, the example networks server(s) 120, the example firewall 125, the example measurement server(s) 130, the example measurement entity network 135, the example secure communication link 140, the example communication network 145, the example firewall 150, the example profile specifier 205, the example customer sample generator 210, the example customer database interface 215, the example customer sample storage 220, the example measurement data sampler 225, the example server log interface 230, the example profile verifier 240, the example privacy unit 245 and/or the example data transmission unit 250 could be implemented by any combination of software, hardware, and/or firmware. Also, some or all of the machine readable instructions represented by the flowchart of
Example machine readable instructions 400 that may be executed to implement the example representative sampling unit 105 of
With reference to
After customer sample generation is performed at block 420, at block 424 the customer sample generator 210 determines whether the customer sample generated at block 420 needs to be updated. For example, the profile verifier 240 included in the representative sampling unit 105 may indicate that that the customer sample needs to be updated if an actual network usage profile for the customer sample (e.g., as determined from sample server log data) and the specified network usage profile obtained at block 416 fail to match or substantially match within a specified tolerance. If the customer sample needs to be updated (block 424), processing returns to block 420 at which the customer sample is updated. However, if the customer sample does not need to be updated (block 424), at block 428 the profile specifier 205 determines whether there has been an update to the specified demographic and/or network usage profiles. If one or both of the profiles are to be updated (block 428), processing returns to block 412. Otherwise, execution of the customer sample generation thread 404 ends until it is time to be invoked to generate a new customer sample.
The measurement data sampling thread 408 of the machine readable instructions 400 of
After measurement data sampling is performed at block 432, at block 436 the profile verifier 240 determines whether the actual network usage profile determined by the measurement data sampler 225 from the retrieved server logs corresponds to the specified network usage profile obtained at block 416. If the actual and specified network usage profiles do not correspond (block 436), the profile verifier 240 invokes block 424 of the customer sample generation thread 404 with an indication that the customer sample needs to be updated. However, if the actual and specified network usage profiles do correspond (block 436), then at block 440 the privacy unit 245 included in the representative sampling unit 105 scrubs the audience measurement data determined at block 432 to remove any customer identification information, but to retain any other demographic and/or network usage classifications. Then, at block 444 the data transmission unit 250 included in the representative sampling unit 105 transmits the resulting anonymous measurement data to the audience measurement entity's measurement server(s) 130. Then, at block 448 the measurement data sampler 225 determines whether it is time to update the measurement data sample. If it is time to update the measurement data (block 448), then processing returns to block 432 at which the measurement data sampler 225 retrieves and processes new server log data to determine updated audience measurement data. Otherwise, execution of the measurement data sampling thread 408 ends until it is time to be invoked to generate new anonymous audience measurement data.
Example machine readable instructions 420 that may be used to implement the customer sample generation processing at block 420 of
Next, at block 516 the customer sample generator 210 generates a random customer sample matching the target population percentage specified for each category in the demographic profile. For example, at block 516 the customer sample generator 210 determines an effective population percentage for each index group determined at block 512 by multiplying the target population percentages for each category's constituent population segment included in the particular index group. Then, for each index group, the customer sample generator 210 randomly samples (e.g., selects) a number of customers from each index group such that the ratio of the number of customers sampled from each index group to the total number of customer included in the customer sample corresponds to the determined effective population percentage for that particular item group. The result is a subset of customers whose actual demographic profile corresponds to the specified demographic profile obtained at block 504.
Next, at block 520 the customer sample generator 210 determines whether the customer database(s) 115 contain network usage information. If so, at block 524 the customer sample generator 210 begins generating another customer sample having the specified network usage profile obtained by the profile specifier 205. In particular, at block 524 the customer sample generator 210 uses the network usage data and associated customer identification information stored in the customer database(s) 115 to index (e.g., sort) the customers the different network usage categories included in the demographic profile retrieved at block 504. Then, at block 528 the customer sample generator 210 generates a random customer sample matching the target population percentage specified for each category in the network usage profile. For example, the customer sample generator 210 randomly samples (e.g., selects) a number of customers from each network usage category such that the ratio of the number of customers sampled from each network usage category to the total number of customer included in the customer sample corresponds to the target population for that particular network usage category. The result is a subset of customers whose actual network usage profile corresponds to the specified network usage profile obtained at block 504.
Alternatively, if the customer database(s) 115 contain network usage information, the processing at blocks 512 through 528 can be combined to generate a customer sample representative of both the obtained demographic and network usage profiles. In such an example, the set of network usage categories in the specified network usage profile is treated as another dimension (e.g., as another demographic category) of the specified demographic profile, as described above, when indexing and sampling the customers (e.g., at blocks 512 and 516) to generate the customer sample.
Next, at block 532 the customer sample generator 210 stores the customer sample or samples generated at blocks 516 and 528 in the customer sample storage 220. Execution of the example machine readable instructions 420 then ends.
Example machine readable instructions 432 that may be used to implement the measurement data sampling processing at block 432 of
Next, at block 616 the measurement data sampler 225 determines whether the customers included in the customer sample need to be classified into the network usage categories of the obtained network usage profile (e.g., such as when network usage information is not included in the customer database(s) 115 and, thus, a customer sample having the specified network usage profile cannot be determined a priori). If network usage classification is needed (block 616), at block 620 the measurement data sampler 225 processes the server log data retrieved at block 612 to classify each customer in the customer sample into a particular network usage category, as described above. Then, at block 624 the measurement data sampler 225 associates (e.g., classifies) each customer's server log data (e.g., which is already associated with the customer's identification information) with the demographic classification and network usage classification (e.g., the latter if known from customer data stored in the customer database(s)) into which the particular customer belongs. The measurement data sampler 225 stores the retrieved server log data and associated customer identification information, demographic classifications and network usage classifications as audience measurement data at block 628. Execution of the machine readable instructions 432 then ends.
The system 700 of the instant example includes a processor 712 such as a general purpose programmable processor. The processor 712 includes a local memory 714, and executes coded instructions 716 present in the local memory 714 and/or in another memory device. The processor 712 may execute, among other things, the machine readable instructions represented in
The processor 712 is in communication with a main memory including a volatile memory 718 and a non-volatile memory 720 via a bus 722. The volatile memory 718 may be implemented by Static Random Access Memory (SRAM), Synchronous Dynamic Random Access Memory (SDRAM), Dynamic Random Access Memory (DRAM), RAMBUS Dynamic Random Access Memory (RDRAM) and/or any other type of random access memory device. The non-volatile memory 720 may be implemented by flash memory and/or any other desired type of memory device. Access to the main memory 718, 720 is typically controlled by a memory controller (not shown).
The processing system 700 also includes an interface circuit 724. The interface circuit 724 may be implemented by any type of interface standard, such as an Ethernet interface, a universal serial bus (USB), and/or a third generation input/output (3GIO) interface.
One or more input devices 726 are connected to the interface circuit 724. The input device(s) 726 permit a user to enter data and commands into the processor 712. The input device(s) can be implemented by, for example, a keyboard, a mouse, a touchscreen, a track-pad, a trackball, an isopoint and/or a voice recognition system.
One or more output devices 728 are also connected to the interface circuit 724. The output devices 728 can be implemented, for example, by display devices (e.g., a liquid crystal display, a cathode ray tube display (CRT)), by a printer and/or by speakers. The interface circuit 724, thus, typically includes a graphics driver card.
The interface circuit 724 also includes a communication device such as a modem or network interface card to facilitate exchange of data with external computers via a network (e.g., an Ethernet connection, a digital subscriber line (DSL), a telephone line, coaxial cable, a cellular telephone system, etc.).
The processing system 700 also includes one or more mass storage devices 730 for storing software and data. Examples of such mass storage devices 730 include floppy disk drives, hard drive disks, compact disk drives and digital versatile disk (DVD) drives. The mass storage device 730 may implement the customer sample storage 220. Alternatively, the volatile memory 718 may implement the customer sample storage 220.
As an alternative to implementing the methods and/or apparatus described herein in a system such as the processing system of
Finally, although certain example methods, apparatus and articles of manufacture have been described herein, the scope of coverage of this patent is not limited thereto. On the contrary, this patent covers all methods, apparatus and articles of manufacture fairly falling within the scope of the appended claims either literally or under the doctrine of equivalents.
This patent arises from a continuation of U.S. patent application Ser. No. 13/649,794 (now U.S. Pat. No. 8,903,864), which is entitled “Methods and Apparatus to Obtain Anonymous Audience Measurement Data from Network Server Data for Particular Demographic and Usage Profiles,” and was filed on Oct. 11, 2012, and which is a continuation of U.S. patent application Ser. No. 12/827,865 (now U.S. Pat. No. 8,307,006), which is entitled “Methods and Apparatus to Obtain Anonymous Audience Measurement Data from Network Server Data for Particular Demographic and Usage Profiles,” and was filed on Jun. 30, 2010. U.S. patent application Ser. Nos. 12/827,865 and 13/649,794 are hereby incorporated by reference in their respective entireties.
Number | Name | Date | Kind |
---|---|---|---|
3540003 | Murphy | Nov 1970 | A |
3818458 | Deese | Jun 1974 | A |
3906450 | Prado, Jr. | Sep 1975 | A |
3906454 | Martin | Sep 1975 | A |
T955010 | Ragonese et al. | Feb 1977 | I4 |
4168396 | Best | Sep 1979 | A |
4230990 | Lert, Jr. et al. | Oct 1980 | A |
4232193 | Gerard | Nov 1980 | A |
4306289 | Lumley | Dec 1981 | A |
4319079 | Best | Mar 1982 | A |
4361832 | Cole | Nov 1982 | A |
4367525 | Brown et al. | Jan 1983 | A |
4558413 | Schmidt et al. | Dec 1985 | A |
4588991 | Atalla | May 1986 | A |
4590550 | Eilert et al. | May 1986 | A |
4595950 | Lofberg | Jun 1986 | A |
4658093 | Hellman | Apr 1987 | A |
4672572 | Alsberg | Jun 1987 | A |
4685056 | Barnsdale, Jr. et al. | Aug 1987 | A |
4696034 | Wiedemer | Sep 1987 | A |
4703324 | White | Oct 1987 | A |
4718005 | Feigenbaum et al. | Jan 1988 | A |
4720782 | Kovalcin | Jan 1988 | A |
4734865 | Scullion et al. | Mar 1988 | A |
4740890 | William | Apr 1988 | A |
4747139 | Taaffe | May 1988 | A |
4757533 | Allen et al. | Jul 1988 | A |
4791565 | Dunham et al. | Dec 1988 | A |
4821178 | Levin et al. | Apr 1989 | A |
4825354 | Agrawal et al. | Apr 1989 | A |
4827508 | Shear | May 1989 | A |
4866769 | Karp | Sep 1989 | A |
4914689 | Quade et al. | Apr 1990 | A |
4926162 | Pickell | May 1990 | A |
4940976 | Gastouniotis et al. | Jul 1990 | A |
4956769 | Smith | Sep 1990 | A |
4977594 | Shear | Dec 1990 | A |
5023907 | Johnson et al. | Jun 1991 | A |
5032979 | Hecht et al. | Jul 1991 | A |
5086386 | Islam | Feb 1992 | A |
5182770 | Medveczky et al. | Jan 1993 | A |
5204897 | Wyman | Apr 1993 | A |
5233642 | Renton | Aug 1993 | A |
5283734 | Von Kohorn | Feb 1994 | A |
5287408 | Samson | Feb 1994 | A |
5341216 | Hoffart | Aug 1994 | A |
5343239 | Lappington et al. | Aug 1994 | A |
5355161 | Bird et al. | Oct 1994 | A |
5355484 | Record et al. | Oct 1994 | A |
5374951 | Welsh | Dec 1994 | A |
5377269 | Heptig et al. | Dec 1994 | A |
5388211 | Hornbuckle | Feb 1995 | A |
5406269 | Baran | Apr 1995 | A |
5410598 | Shear | Apr 1995 | A |
5440738 | Bowman et al. | Aug 1995 | A |
5444642 | Montgomery et al. | Aug 1995 | A |
5450122 | Keene | Sep 1995 | A |
5450134 | Legate | Sep 1995 | A |
5481294 | Thomas et al. | Jan 1996 | A |
5481296 | Cragun et al. | Jan 1996 | A |
5483658 | Grube et al. | Jan 1996 | A |
5485518 | Hunter et al. | Jan 1996 | A |
5488408 | Maduzia et al. | Jan 1996 | A |
5497479 | Hornbuckle | Mar 1996 | A |
5499340 | Barritz | Mar 1996 | A |
5521631 | Budow et al. | May 1996 | A |
5535209 | Glaser et al. | Jul 1996 | A |
5539822 | Lett | Jul 1996 | A |
5584050 | Lyons | Dec 1996 | A |
5594934 | Lu et al. | Jan 1997 | A |
5636346 | Saxe | Jun 1997 | A |
5675510 | Coffey et al. | Oct 1997 | A |
5697844 | Von Kohorn | Dec 1997 | A |
5701582 | DeBey | Dec 1997 | A |
5724521 | Dedrick | Mar 1998 | A |
5734720 | Salganicoff | Mar 1998 | A |
5758257 | Herz et al. | May 1998 | A |
5793409 | Tetsumura | Aug 1998 | A |
5796952 | Davis et al. | Aug 1998 | A |
5872588 | Aras et al. | Feb 1999 | A |
5892826 | Brown et al. | Apr 1999 | A |
5956716 | Kenner et al. | Sep 1999 | A |
5974299 | Massetti | Oct 1999 | A |
6002393 | Hite et al. | Dec 1999 | A |
6005561 | Hawkins et al. | Dec 1999 | A |
6025837 | Matthews, III et al. | Feb 2000 | A |
6052730 | Felciano et al. | Apr 2000 | A |
6055573 | Gardenswartz et al. | Apr 2000 | A |
6061451 | Muratani et al. | May 2000 | A |
6088722 | Herz et al. | Jul 2000 | A |
6098093 | Bayeh et al. | Aug 2000 | A |
6102406 | Miles et al. | Aug 2000 | A |
6108637 | Blumenau | Aug 2000 | A |
6138155 | Davis et al. | Oct 2000 | A |
6164975 | Weingarden et al. | Dec 2000 | A |
6166730 | Goode et al. | Dec 2000 | A |
6189008 | Easty et al. | Feb 2001 | B1 |
6216265 | Roop et al. | Apr 2001 | B1 |
6223215 | Hunt et al. | Apr 2001 | B1 |
6226618 | Downs et al. | May 2001 | B1 |
6247050 | Tso et al. | Jun 2001 | B1 |
6253238 | Lauder et al. | Jun 2001 | B1 |
6286104 | Buhle et al. | Sep 2001 | B1 |
6289514 | Link et al. | Sep 2001 | B1 |
6356945 | Shaw et al. | Mar 2002 | B1 |
6415323 | McCanne et al. | Jul 2002 | B1 |
6434614 | Blumenau | Aug 2002 | B1 |
6460079 | Blumenau | Oct 2002 | B1 |
6490587 | Easty et al. | Dec 2002 | B2 |
6529952 | Blumenau | Mar 2003 | B1 |
6748427 | Drosset et al. | Jun 2004 | B2 |
6839680 | Liu et al. | Jan 2005 | B1 |
6877007 | Hentzel et al. | Apr 2005 | B1 |
6983478 | Grauch et al. | Jan 2006 | B1 |
6988108 | Bernhardt et al. | Jan 2006 | B2 |
6993590 | Gauthier et al. | Jan 2006 | B1 |
7039699 | Narin et al. | May 2006 | B1 |
7080136 | Duffield et al. | Jul 2006 | B2 |
7092926 | Cerrato | Aug 2006 | B2 |
7124938 | Marsh | Oct 2006 | B1 |
7130778 | Connell et al. | Oct 2006 | B1 |
7139723 | Conkwright et al. | Nov 2006 | B2 |
7150030 | Eldering et al. | Dec 2006 | B1 |
7159023 | Tufts | Jan 2007 | B2 |
7181412 | Fulgoni et al. | Feb 2007 | B1 |
7260837 | Abraham et al. | Aug 2007 | B2 |
7343417 | Baum | Mar 2008 | B2 |
7386473 | Blumenau | Jun 2008 | B2 |
7406516 | Davis et al. | Jul 2008 | B2 |
7444655 | Sardera | Oct 2008 | B2 |
7526538 | Wilson | Apr 2009 | B2 |
7546370 | Acharya et al. | Jun 2009 | B1 |
7590568 | Blumenau | Sep 2009 | B2 |
7600014 | Russell et al. | Oct 2009 | B2 |
7613635 | Blumenau | Nov 2009 | B2 |
7644156 | Blumenau | Jan 2010 | B2 |
7650407 | Blumenau | Jan 2010 | B2 |
7653724 | Blumenau | Jan 2010 | B2 |
7716326 | Blumenau | May 2010 | B2 |
7720963 | Blumenau | May 2010 | B2 |
7720964 | Blumenau | May 2010 | B2 |
7756974 | Blumenau | Jul 2010 | B2 |
7788216 | Li et al. | Aug 2010 | B2 |
7882242 | Chen | Feb 2011 | B2 |
7925694 | Harris | Apr 2011 | B2 |
7941525 | Yavilevich | May 2011 | B1 |
7949565 | Eldering et al. | May 2011 | B1 |
7958234 | Thomas et al. | Jun 2011 | B2 |
7962603 | Morimoto | Jun 2011 | B1 |
8032626 | Russell et al. | Oct 2011 | B1 |
8046255 | Bistriceanu et al. | Oct 2011 | B2 |
8060601 | Brown et al. | Nov 2011 | B1 |
8131861 | Butler et al. | Mar 2012 | B2 |
8229780 | Davidow et al. | Jul 2012 | B2 |
8234408 | Jungck | Jul 2012 | B2 |
8266687 | Baldry | Sep 2012 | B2 |
8271886 | Lee et al. | Sep 2012 | B2 |
8302120 | Ramaswamy | Oct 2012 | B2 |
8307006 | Hannan et al. | Nov 2012 | B2 |
8370489 | Mazumdar et al. | Feb 2013 | B2 |
8381241 | Ramaswamy et al. | Feb 2013 | B2 |
8495198 | Sim et al. | Jul 2013 | B2 |
8504411 | Subasic et al. | Aug 2013 | B1 |
8543454 | Fleischman et al. | Sep 2013 | B2 |
8631122 | Kadam et al. | Jan 2014 | B2 |
8707340 | Ramaswamy et al. | Apr 2014 | B2 |
8713168 | Heffernan et al. | Apr 2014 | B2 |
8751461 | Abraham et al. | Jun 2014 | B2 |
8843626 | Mazumdar et al. | Sep 2014 | B2 |
8909771 | Heath | Dec 2014 | B2 |
8954536 | Kalus et al. | Feb 2015 | B2 |
9055122 | Grecco et al. | Jun 2015 | B2 |
20010023436 | Srinivasan et al. | Sep 2001 | A1 |
20010034708 | Walker et al. | Oct 2001 | A1 |
20010049620 | Blasko | Dec 2001 | A1 |
20010051996 | Cooper et al. | Dec 2001 | A1 |
20020010919 | Lu et al. | Jan 2002 | A1 |
20020019769 | Barritz et al. | Feb 2002 | A1 |
20020031224 | Basawapatna et al. | Mar 2002 | A1 |
20020044225 | Rakib | Apr 2002 | A1 |
20020053078 | Holtz et al. | May 2002 | A1 |
20020056086 | Yuen | May 2002 | A1 |
20020056087 | Berezowski et al. | May 2002 | A1 |
20020059637 | Rakib | May 2002 | A1 |
20020078441 | Drake et al. | Jun 2002 | A1 |
20020110360 | Potrebic | Aug 2002 | A1 |
20020112048 | Gruyer et al. | Aug 2002 | A1 |
20020120925 | Logan | Aug 2002 | A1 |
20020129368 | Schlack et al. | Sep 2002 | A1 |
20020191810 | Fudge et al. | Dec 2002 | A1 |
20020194592 | Tsuchida et al. | Dec 2002 | A1 |
20030001880 | Holtz et al. | Jan 2003 | A1 |
20030005430 | Kolessar | Jan 2003 | A1 |
20030037131 | Verma | Feb 2003 | A1 |
20030037333 | Ghashghai et al. | Feb 2003 | A1 |
20030041143 | Ronald et al. | Feb 2003 | A1 |
20030046385 | Vincent | Mar 2003 | A1 |
20030149975 | Eldering et al. | Aug 2003 | A1 |
20030149991 | Reidhead et al. | Aug 2003 | A1 |
20030154128 | Liga et al. | Aug 2003 | A1 |
20030177488 | Smith et al. | Sep 2003 | A1 |
20030208763 | McElhatten et al. | Nov 2003 | A1 |
20030208767 | Williamson et al. | Nov 2003 | A1 |
20030220901 | Carr et al. | Nov 2003 | A1 |
20030229892 | Sardera | Dec 2003 | A1 |
20040019900 | Knightbridge et al. | Jan 2004 | A1 |
20040039914 | Barr et al. | Feb 2004 | A1 |
20040088212 | Hill | May 2004 | A1 |
20040098229 | Error et al. | May 2004 | A1 |
20050033657 | Herrington et al. | Feb 2005 | A1 |
20050055316 | Williams | Mar 2005 | A1 |
20050138674 | Howard et al. | Jun 2005 | A1 |
20050166233 | Beyda et al. | Jul 2005 | A1 |
20050223093 | Hanson et al. | Oct 2005 | A1 |
20050267750 | Steuer et al. | Dec 2005 | A1 |
20050278731 | Cameron et al. | Dec 2005 | A1 |
20060178996 | Matsushima et al. | Aug 2006 | A1 |
20060271641 | Stavrakos et al. | Nov 2006 | A1 |
20060294259 | Matefi et al. | Dec 2006 | A1 |
20070106787 | Blumenau | May 2007 | A1 |
20070106792 | Blumenau | May 2007 | A1 |
20070156532 | Nyhan et al. | Jul 2007 | A1 |
20070157262 | Ramaswamy et al. | Jul 2007 | A1 |
20070186228 | Ramaswamy et al. | Aug 2007 | A1 |
20080004958 | Ralph et al. | Jan 2008 | A1 |
20080126420 | Wright et al. | May 2008 | A1 |
20080201427 | Chen | Aug 2008 | A1 |
20080201472 | Bistriceanu et al. | Aug 2008 | A1 |
20080235243 | Lee et al. | Sep 2008 | A1 |
20080276179 | Borenstein et al. | Nov 2008 | A1 |
20090030780 | York et al. | Jan 2009 | A1 |
20090055241 | Chen et al. | Feb 2009 | A1 |
20090070443 | Vanderhook et al. | Mar 2009 | A1 |
20090076899 | Gbodimowo | Mar 2009 | A1 |
20090171762 | Alkove et al. | Jul 2009 | A1 |
20090282430 | Gupta et al. | Nov 2009 | A1 |
20090307084 | Monighetti et al. | Dec 2009 | A1 |
20090327026 | Bistriceanu et al. | Dec 2009 | A1 |
20100004977 | Marci et al. | Jan 2010 | A1 |
20100010866 | Bal et al. | Jan 2010 | A1 |
20100070621 | Urdan et al. | Mar 2010 | A1 |
20100088152 | Bennett | Apr 2010 | A1 |
20100088373 | Pinkham | Apr 2010 | A1 |
20100121676 | Jackson | May 2010 | A1 |
20100153544 | Krassner et al. | Jun 2010 | A1 |
20100191723 | Perez et al. | Jul 2010 | A1 |
20100205057 | Hook et al. | Aug 2010 | A1 |
20100211967 | Ramaswamy et al. | Aug 2010 | A1 |
20100241745 | Offen et al. | Sep 2010 | A1 |
20100262498 | Nolet et al. | Oct 2010 | A1 |
20100268540 | Arshi et al. | Oct 2010 | A1 |
20100268573 | Jain et al. | Oct 2010 | A1 |
20100299604 | Blumenau | Nov 2010 | A1 |
20100312854 | Hyman | Dec 2010 | A1 |
20100313009 | Combet et al. | Dec 2010 | A1 |
20110087519 | Fordyce, III et al. | Apr 2011 | A1 |
20110087919 | Deshmukh et al. | Apr 2011 | A1 |
20110088052 | Ramaswamy et al. | Apr 2011 | A1 |
20110093327 | Fordyce, III et al. | Apr 2011 | A1 |
20110106620 | Setiawan et al. | May 2011 | A1 |
20110131596 | Amsterdam et al. | Jun 2011 | A1 |
20110137733 | Baird et al. | Jun 2011 | A1 |
20110153391 | Tenbrock | Jun 2011 | A1 |
20110191184 | Blackhurst et al. | Aug 2011 | A1 |
20110191664 | Sheleheda et al. | Aug 2011 | A1 |
20110191831 | Chan et al. | Aug 2011 | A1 |
20110196735 | Von Sydow et al. | Aug 2011 | A1 |
20110208860 | Sim et al. | Aug 2011 | A1 |
20110231240 | Schoen et al. | Sep 2011 | A1 |
20110246297 | Buchalter et al. | Oct 2011 | A1 |
20110246306 | Blackhurst et al. | Oct 2011 | A1 |
20110246641 | Pugh et al. | Oct 2011 | A1 |
20110288907 | Harvey et al. | Nov 2011 | A1 |
20120005213 | Hannan et al. | Jan 2012 | A1 |
20120030037 | Carriero | Feb 2012 | A1 |
20120072469 | Perez et al. | Mar 2012 | A1 |
20120109709 | Fordyce, III et al. | May 2012 | A1 |
20120110027 | Falcon | May 2012 | A1 |
20120143713 | Dittus et al. | Jun 2012 | A1 |
20120151079 | Besehanic et al. | Jun 2012 | A1 |
20120151322 | Lindsay et al. | Jun 2012 | A1 |
20120158954 | Heffernan et al. | Jun 2012 | A1 |
20120166520 | Lindsay et al. | Jun 2012 | A1 |
20120173701 | Tenbrock | Jul 2012 | A1 |
20120192214 | Hunn et al. | Jul 2012 | A1 |
20120215621 | Heffernan et al. | Aug 2012 | A1 |
20120239407 | Lynch et al. | Sep 2012 | A1 |
20120239809 | Mazumdar et al. | Sep 2012 | A1 |
20120254466 | Jungck | Oct 2012 | A1 |
20120310729 | Dalto et al. | Dec 2012 | A1 |
20120311017 | Sze et al. | Dec 2012 | A1 |
20130014144 | Bhatia et al. | Jan 2013 | A1 |
20130046615 | Liyanage | Feb 2013 | A1 |
20130097312 | Mazumdar et al. | Apr 2013 | A1 |
20130124628 | Weerasinghe | May 2013 | A1 |
20130138506 | Zhu et al. | May 2013 | A1 |
20130138743 | Amento et al. | May 2013 | A1 |
20130145022 | Srivastava et al. | Jun 2013 | A1 |
20130152117 | Ramaswamy et al. | Jun 2013 | A1 |
20130159499 | Besehanic | Jun 2013 | A1 |
20130212188 | Duterque et al. | Aug 2013 | A1 |
20130246389 | Osann, Jr. | Sep 2013 | A1 |
20130246609 | Topchy et al. | Sep 2013 | A1 |
20130282898 | Kalus et al. | Oct 2013 | A1 |
20130297411 | Van Datta et al. | Nov 2013 | A1 |
20140033317 | Barber | Jan 2014 | A1 |
20150019327 | Mazumdar et al. | Jan 2015 | A1 |
Number | Date | Country |
---|---|---|
2013205736 | May 2013 | AU |
1346571 | Apr 2002 | CN |
1898662 | Jan 2007 | CN |
101077014 | Nov 2007 | CN |
101593210 | Dec 2009 | CN |
101673304 | Mar 2010 | CN |
0325219 | Jul 1989 | EP |
0703683 | Mar 1996 | EP |
0744695 | Nov 1996 | EP |
0817486 | Jan 1998 | EP |
1166555 | Oct 2000 | EP |
2176639 | Dec 1986 | GB |
19920155707 | Dec 1993 | JP |
H05324352 | Dec 1993 | JP |
2001282982 | Oct 2001 | JP |
2002-091852 | Mar 2002 | JP |
2002163562 | Jun 2002 | JP |
2002373152 | Dec 2002 | JP |
2006127320 | May 2006 | JP |
2006127321 | May 2006 | JP |
2010-501939 | Jan 2010 | JP |
2010039845 | Feb 2010 | JP |
20020037980 | May 2002 | KR |
20110023293 | Mar 2011 | KR |
9600950 | Jan 1996 | WO |
9617467 | Jun 1996 | WO |
9628904 | Sep 1996 | WO |
9632815 | Oct 1996 | WO |
9637983 | Nov 1996 | WO |
9641495 | Dec 1996 | WO |
9831155 | Jul 1998 | WO |
9959275 | Nov 1999 | WO |
0033565 | Jun 2000 | WO |
0033578 | Jun 2000 | WO |
0041115 | Jul 2000 | WO |
0131497 | May 2001 | WO |
0147257 | Jun 2001 | WO |
0147273 | Jun 2001 | WO |
0152168 | Jul 2001 | WO |
0176248 | Oct 2001 | WO |
03071737 | Aug 2003 | WO |
2004051997 | Jun 2004 | WO |
2005013072 | Feb 2005 | WO |
2005079501 | Sep 2005 | WO |
2005107110 | Nov 2005 | WO |
2006130658 | Dec 2006 | WO |
2010088372 | Aug 2010 | WO |
2010104285 | Sep 2010 | WO |
2011097624 | Aug 2011 | WO |
2012040371 | Mar 2012 | WO |
2012087954 | Jun 2012 | WO |
2012128895 | Sep 2012 | WO |
2013122907 | Aug 2013 | WO |
2014059319 | Apr 2014 | WO |
Entry |
---|
Canadian Intellectual Property Office, “Office Action” issued in connection with Canadian Patent Application No. 2,563,834, dated Dec. 23, 2014 (4 pages). |
El Emam, Khaled, “Data Anonymizatlon Practices in Clinical Research,” XP55008028, retrieved on Sep. 26, 2011 from <http://lwww.ehealthinformation.caldocumentslHealthCanadaAnonymizationReport.pdf>, dated May 8, 2006 (16 pages). |
McCaa et al., “IPUMS-International High Precision Population Census Microdata Samples: Balancing the Privacy-Quality Tradeoff by Means of Restricted Access Extracts,” Privacy in Statistical Databases Lecture Notes in Computer Science (LNCS), vol. 4302, Springer-Verlag, 2006 (8 pages). |
Riphagen et al., “In Search of the Elusive User: Gathering Information on the Web Server Access,” NCSA, Oct. 14, 1996 (14 pages). |
Samarati, Pierangela, “Protecting Respondents' Identities in Microdata Release,” IEEE Transactions on Knowledge and Data Engineering, vol. 13, No. 6, Nov./Dec. 2001 (18 pages). |
Canadian Intellectual Property Office, “Office Action,” issued in connection with Canadian Application No. 2,556,553, on Jun. 15, 2010 (10 pages). |
EPO, “Extended European Search Report,” issued in connection with EP Patent Application No. 11005351.9, on Oct. 7, 2011 (7 pages). |
International Bureau, “International Preliminary Report on Patentability,” in connection with PCT Application No. PCT/US2005/005271, mailed Aug. 22, 2006 (4 pages). |
International Bureau, “International Preliminary Report on Patentability,” issued in connection with PCT Application No. PCT/US2005/013765, mailed Feb. 13, 2007 (4 pages). |
PCT, “International Search Report,” issued by the International Searching Authority in connection with PCT Application No. PCT/US2005/005271, mailed Mar. 23, 2006 (1 page). |
PCT, “Written Opinion of the International Searching Authority,” issued by the International Searching Authority in connection with PCT Application No. PCT/US2005/005271, mailed Mar. 23, 2006 (4 pages). |
PCT, “International Search Report,” issued by the International Searching Authority in connection with PCT Application No. PCT/US2005/013765, mailed Jan. 26, 2007 (4 pages). |
PCT, “Written Opinion of the International Searching Authority,” issued by the International Searching Authority in connection with PCT Application No. PCT/US2005/013765, mailed Jan. 26, 2007 (3 pages). |
USPTO, “Election/Restriction Requirement,” issued in connection with U.S. Appl. No. 10/589,149, on Feb. 6, 2009 (7 pages). |
USPTO, “Office Action,” issued in connection with U.S. Appl. No. 10/589,149, on Jun. 9, 2009 (27 pages). |
USPTO, “Office Action,” issued in connection with U.S. Appl. No. 10/589,149, on Jan. 6, 2010 (30 pages). |
USPTO, “Office Action,” issued in connection with U.S. Appl. No. 10/589,149, on Mar. 12, 2010 (3 pages). |
USPTO, “Final Office Action,” issued in connection with U.S. Appl. No. 10/589,149, on Jul. 19, 2010 (33 pages). |
USPTO, “Election/Restriction Requirement,” issued in connection with U.S. Appl. No. 11/550,261, on Feb. 24, 2009 (6 pages). |
USPTO, “Office Action,” issued in connection with U.S. Appl. No. 11/550,261, on Apr. 16, 2009 (16 pages). |
USPTO, “Office Action,” issued in connection with U.S. Appl. No. 11/550,261, on Oct. 28, 2009 (19 pages). |
USPTO, “Office Action,” issued in connection with U.S. Appl. No. 12/769,163, on Sep. 23, 2010 (16 pages). |
USPTO, “Final Office Action,” issued in connection with U.S. Appl. No. 12/769,163, on Apr. 5, 2011 (22 pages). |
USPTO, “Notice of Allowance,” issued in connection with U.S. Appl. No. 12/827,865, on Feb. 22, 2012 (9 pages). |
USPTO, “Notice of Allowance,” issued in connection with U.S. Appl. No. 12/827,865, on Jul. 5, 2012 (8 pages). |
United States Patent and Trademark Office, “Notice of Allowance”, issued in connection with U.S. Appl. No. 12/769,163, dated Oct. 15, 2012 (9 pages). |
United States Patent and Trademark Office, “Notice of Allowance”, issued in connection with U.S. Appl. No. 13/762,025, dated Nov. 27, 2013 (10 pages). |
United States Patent and Trademark Office, “Non-Final Office Action”, issued in connection with U.S. Appl. No. 12/970,710, dated Aug. 13, 2012 (24 pages). |
United States Patent and Trademark Office, “Final Office Action”, issued in connection with U.S. Appl. No. 12/970,710, dated Apr. 12, 2013 (28 pages). |
Canadian Intellectual Property Office, “Office Action”, issued in connection with Canadian Patent Application No. 2,556,553, dated Jun. 27, 2011 (3 pages). |
Canadian Intellectual Property Office, “Office Action”, issued in connection with Canadian Patent Application No. 2,556,553, dated Aug. 23, 2012 (3 pages). |
Canadian Intellectual Property Office, “Office Action”, issued in connection with Canadian Patent Application No. 2,556,553, dated Feb. 14, 2014 (2 pages). |
Canadian Intellectual Property Office, “Office Action”, issued in connection with Canadian Patent Application No. 2,563,834, dated Jan. 7, 2014 (3 pages). |
Canadian Intellectual Property Office, “Office Action”, issued in connection with Canadian Patent Application No. 2,744,580, dated Jul. 24, 2013 (3 pages). |
IP Australia, “Examination Report”, issued in connection with Australian Patent Application No. 2011203053, dated Jul. 24, 2012 (3 pages). |
IP Australia, “Notice of Acceptance”, issued in connection with Australian Patent Application No. 2011203053, dated Aug. 13, 2013 (2 pages). |
The State Intellectual Property Office of China, “First Office Action”, issued in connection with Chinese Patent Application No. 201110230823, dated Nov. 26, 2012 (13 pages). |
The State Intellectual Property Office of China, “Second Office Action”, issued in connection with Chinese Patent Application No. 201110230823, dated Aug. 6, 2013 (10 pages). |
United States Patent and Trademark Office, “Non-Final Office Action”, issued in connection with U.S. Appl. No. 113/649,794, dated Apr. 7, 2014 (8 pages). |
United States Patent and Trademark Office, “Notice of Allowance”, issued in connection with U.S. Appl. No. 113/649,794, dated Jul. 24, 2014 (5 pages). |
United States Patent and Trademark Office, “Non-Final Office Action,” issued in connection with U.S. Appl. No. 13/239,005, on Jun. 4, 2013 (28 pages). |
United States Patent and Trademark Office, “Non-Final Office Action,” issued in connection with U.S. Appl. No. 13/691,175, on Sep. 9, 2013 (35 pages). |
United States Patent and Trademark Office, “Notice of Allowance,” issued in connection with U.S. Appl. No. 13/239,005, on Nov. 27, 2013, 46 pages. |
United States Patent and Trademark Office, “Notice of Allowance,” issued in connection with U.S. Appl. No. 13/513,148, on Nov. 5, 2012 (27 pages). |
United States Patent and Trademark Office, “Notice of Allowance,” issued in connection with U.S. Appl. No. 13/691,175, on Jan. 27, 2014, 15 pages. |
United States Patent and Trademark Office, “Notice of Allowance,” issued in connection with U.S. Appl. No. 13/691,175, on May 9, 2014, 6 pages. |
Vega, Tanzina, “Nielsen Introduces New Ad Measurement Product,” The New York Times, Sep. 27, 2010 (7 pages). |
Vranica, “Nielsen Testing a New Web-Ad Metric,” The Wall Street Journal, Sep. 23,2010,2 pages. |
United States Patent and Trademark Office, “Non-Final Office Action,” issued in connection with U.S. Appl. No. 13/756,493, on Jan. 17, 2014, 32 pages. |
Japan Patent Office, “Notice of Reasons for Rejection,” issued in connection with Application No. 2013-529435, Aug. 20, 2013, 4 pages. |
United States Patent and Trademark Office, “Non-Final Office Action,” issued in connection with U.S. Appl. No. 13/396,071, May 9, 2014, 35 pages. |
United States Patent and Trademark Office, “Notice of Allowance,” issued in connection with U.S. Appl. No. 13/756,493, on May 20, 2014, 32 pages. |
Canadian Intellectual Property Office, “Examination Search Report,” issued in connection with Application No. 2,810,541 on Jan. 20, 2015. |
The State Intellectual Property Office of China, “First Notification of Office Action,” issued in connection with Application No. 201180045957.2, on Nov. 15, 2014 (20 pages). |
Japanese Patent Office, “Final Rejection,” issed in connection with Japanese Patent Application No. P2014-005867 on Aug. 26, 2014, (8 pages). |
Japanese Patent Office, “Notice of Reasons for Rejection,” issued in connection with Japanese Patenet Application No. P2014-005867 on Apr. 15, 2014, (10 pages). |
United States Patent and Trademark Office, “Office Action Summary,” issued in connection with U.S. Appl. No. 14/500,297, on Jan. 5, 2015, (7 pages). |
Australian Government, IP Australia, “Patent Examination Report No. 1,” issued in connection with Australian Patent Application No. 2013203898, Nov. 27, 2014 (4 pages). |
Australian Government, IP Australia, “Patent Examination Report No. 1,” issued in connection with. |
International Searching Authority, “International Search Report,” issued in connection with International Application No. PCT/US2013/025687 on Jun. 2, 2013, 5 pages. |
International Searching Authority, “Written Opinion of the International Searching Authority,” issued in issued in connection with International Application No. PCT/US2013/025687 on Jun. 2, 2013, 5 pages. |
Japanese Patent Office, “Notice of Reasons for Rejection,” issued in connection with Japanese Patent Application No. P2014-005867 on Feb. 17, 2015, (6 pages). |
Adam et al., “Privacy Preserving Integration of Health Care Data,” AMIA 2007 Symposium Proceedings, 6 pages. |
Australian Government, IP Australia, “Examination Report,” issued in connection with application No. AU 2012231667, on Mar. 18, 2014, 2 pages. |
Australian Government, IP Australia, “Examination Report,” issued in connection with application No. AU 2013205736, on Jun. 18, 2013, 2 pages. |
Chloe Albanesius, Facebook Issues Fix for Several Tracking Cookies, internet article, www.pcmag.com, Sep. 28, 2011, 2 pages. |
Emil Protalinski, Facebook denies cookie tracking allegations, internet article, www.zdnet.com, Sep. 25, 2011, 2 pages. |
Emil Protalinski, Facebook fixes cookie behavior after logging out, internet article, www.zdnet.com, Sep. 27, 2011, 2 pages. |
Emil Protalinski, US congressmen ask FTC to investigate Facebook cookies, internet article, www.zdnet.com, Sep. 28, 2011, 2 pages. |
Fliptop, “Fliptop Person API Documentation,” https://developer.fliptop.com/documentation, retrieved on May 7, 2013(6 pages). |
Fliptop, “Get, Keep and Grow Customers with Fliptop's Customer Intelligence Application,” www.fliptop.com/features#social—matching, retrieved on May 7, 2013 (3 pages). |
Fliptop, “What is Fliptop?”, www.fliptop.com/about—us, retrieved on May 7, 2013 (1 page). |
International Bureau, “International Preliminary Report on Patentability,” issued in connection with PCT application Serial No. PCT/US2011/052623, issued Mar. 26, 2013 (5 pages). |
International Searching Authority, “International Preliminary Report on Patentability,” issued in connection with application No. PCT/US2012/026760, on Sep. 24, 2013 (4 pages). |
International Searching Authority, “International Search Report,” issued in connection with application No. PCT/US2011/052623, mailed on Mar. 8, 2012 (3 pages). |
International Searching Authority, “International Search Report,” issued in connection with application No. PCT/US2012/026760, mailed on Jan. 2, 2013 (3 pages). |
International Searching Authority, “Written Opinion,” issued in connection with application No. PCT/US2011/052623, mailed on Mar. 8, 2012 (4 pages). |
International Searching Authority, “Written Opinion,” issued in connection with application No. PCT/US2012/026760, mailed on Jan. 2, 2013 (3 pages). |
JavaScript and AJAX Forum, Sep. 28, 2005, [retrieved from Internet at http://www.webmasterworld.com/forum9l/4465.htm on Jun. 29,2011] 4 pages. |
Launder, “Media Journal: Nielsen to Test Online-TV Viewing Tool,” The Wall Street Journal, Apr. 30, 2013, 2 pages. |
Mental Poker, Wikipedia, Jan. 12, 2010, [retrieved from Internet at p://en.wikipedia.org/wiki/Mental—poker on Sep. 21, 2010] 5 pages. |
Nielsen Unveils New Online Advertising Measurement, The Nielsen Company, Sep. 27,2010, [retrieved from Internet at http://nielsen.com/us/en/insights/press-room/2010/nielsen—unveils—newonlineadvertisingmeasurement.html on May 31, 2012] 3 pages. |
Nik Cubrilovic, Logging out of Facebook is not enough, internet article, www.nikcub.appspot.com, Sep. 25, 2011, 3 pages. |
Rainier, Maria, “Why Businesses Should Use Google Plus,” The Social Media Guide, thesocialmediaguide.com/social—media/why-businesses-should-use-google-plus, retrieved on May 7, 2013 (9 pages). |
Rapleaf, “Fast. Simple. Secure,” www.rapleaf.com/why-rapleaf/, retrieved on May 7, 2013 (3 pages). |
Rapleaf, “Frequently Asked Questions,” www.rapleaf.com/about-us/faq/#where, retrieved on May 7, 2013 (3 pages). |
Rapleaf, “The Consumer Data Marketplace,” www.rapleaf.com/under-the-hood/, retrieved on May 7, 2013 (2 pages). |
Sharma, “Nielsen Gets Digital to Track Online TV Viewers,” All Things, Apr. 30, 2013, 1 page. |
Steve Coffey, “Internet Audience Measurement: A Practitioner's View,” Journal of Interactive Advertising, vol. 1, No. 2, Spring 2001, pp. 10-17. |
United States Patent and Trademark Office, “Notice of Allowance,” issued in connection with U.S. Appl. No. 14/500,297, May 21, 2015, (31 pages). |
United States Patent and Trademark Office, “Notice of Allowance,” issued in connection with U.S. Appl. No. 13/690,915, on Jun. 24, 2014 (6 pages). |
United States Patent and Trademark Office, “Supplemental Notice of Allowability,” issued in connection with U.S. Appl. No. 13/690,915, on Jul. 8, 2014 (3 pages). |
United States Patent and Trademark Office, “Corrected Notice of Allowability,” issued in connection with U.S. Appl. No. 13/690,915, on Nov. 6, 2014 (6 pages). |
United States Patent and Trademark Office, “Notice of Allowance,” issued in connection with U.S. Appl. No. 13/690,915, on Jun. 5, 2015, (64 pages). |
Japanese Patent Office, “Notice of Allowance,” issued in connection with Japanese Patent Application No. 2014-005867 on Jun. 9, 2015 (3 pages). |
Australian Government, IP Australia, “Notice of Acceptance,” issued in connection with Application No. 2013203898, Jun. 17, 2015 (2 pages). |
Australian Government, IP Australia, “Notice of Acceptance,” issued in connection with Application No. 2011305429, Jul. 15, 2015 (2 pages). |
State Intellectual Property Office of China, “Second Office Action,” issued in connection with Chinese Patent Application No. 201180045957.2, on Jul. 29, 2015 (7 pages). |
United States Patent and Trademark Office, “Final Office Action”, issued in connection with U.S. Appl. No. 14/223,560, dated Apr. 30, 2015 (17 pages). |
European Patent Office, “Examination Report”, issued in connection with European Patent Application No. 11005351.9, dated Feb. 29, 2016 (9 pages). |
Slagell, Adam, “Sharing Computer Network Logs for Security and Privacy: A Motivation for New Methodologies of Anonymization”, NCSA, Sep. 5, 2005 (10 pages). |
Number | Date | Country | |
---|---|---|---|
20150081704 A1 | Mar 2015 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 13649794 | Oct 2012 | US |
Child | 14553334 | US | |
Parent | 12827865 | Jun 2010 | US |
Child | 13649794 | US |