Patent Grant
11563994
This disclosure relates generally to measuring media exposure, and, more particularly, to methods and apparatus to measure exposure to streaming media.
In recent years, media devices have been provided with Internet connectivity and the ability to retrieve media from the Internet. As such, media exposure has shifted away from conventional methods of presentation, such as broadcast television, towards presentation via consumer devices accessing the Internet to retrieve media for display.
Media providers and/or other entities such as, for example, advertising companies, broadcast networks, etc. are often interested in the viewing, listening, and/or media behavior of audience members and/or the public in general. The media usage and/or exposure habits of audience members as well as demographic data about the audience members is collected and used to statistically determine the size and demographics of an audience of interest.
Traditionally, audience measurement entities determine audience engagement levels for media programming and/or advertisements based on registered panel members. That is, an audience measurement entity enrolls people who consent to being monitored into a panel. The audience measurement entity then monitors those panel members to determine media (e.g., television programs, radio programs, movies, DVDs, etc.) presented to those panel members. In this manner, the audience measurement entity can determine exposure measures for different media (e.g., content and/or advertisements) based on the collected media measurement data.
Wherever possible, the same reference numbers will be used throughout the drawing(s) and accompanying written description to refer to the same or like parts.
Monitoring companies desire to gain knowledge on how users interact with media devices such as smartphones, tablets, laptops, smart televisions, etc. In particular, the media monitoring companies want to monitor media presentations made at the media devices to, among other things, monitor exposure to advertisements, determine advertisement effectiveness, determine user behavior, identify purchasing behavior associated with various demographics, determine popularity ratings for content, etc. Monitoring companies enlist panelists and collect demographic information about the panelists. Media presentation information is then collected in association with the panelists. However, it is difficult for monitoring companies to collect detailed demographic information from every user to whom media is presented (e.g., non-panelists). In examples disclosed herein, monitoring companies cooperate with database proprietors (e.g., Facebook, Twitter, Experian, etc.) that have large databases of demographic information to extend media monitoring capabilities to non-panelists.
In examples disclosed herein, the presented media is identified using transcoded watermarks. The transcoded watermarks are transmitted as metadata (e.g., an ID3 tag) that is sent in association with and/or as part of the media. The media presentation device (e.g., an iPad, a smart TV, etc.) extracts the metadata and transmits the metadata to the database proprietor along with information that identifies the media device and/or a user of the media device to the database proprietor. If the database proprietor cannot identify the media device and/or a user of the media device, the database proprietor redirects the media device to a different database proprietor and/or the audience measurement entity, so that the media device and/or a user of the media device can be identified. If the database proprietor can identify the media device and/or a user of the media device, the database proprietor reports demographic information associated with the media device and/or user of the media device to the audience measurement entity for association with the media and/or the metadata identifying the media. In some examples, the metadata is not transmitted to the database proprietor to prevent the database proprietor from identifying the media accessed by the media device and/or the user.
Traditionally, audience measurement entities (also referred to herein as “ratings entities”) determine demographic reach for advertising and/or media programming based on registered panel members. That is, an audience measurement entity enrolls people that consent to being monitored into a panel. During enrollment, the audience measurement entity receives demographic information from the enrolling people so that subsequent correlations may be made between media exposure to those panelists and different demographic markets. The audience measurement entity then sets and/or retrieves a user and/or device identifier so that subsequent impressions related to the panelist can be associated with the panelist and/or the demographics of the panelist. In some examples, the user and/or device identifier is cookie data or another identifier that is used by a media device (e.g., an iPad) when communicating with the audience measurement entity. Based on the user and/or device identifier, the audience measurement entity identifies demographic information provided by the panelist. In exchange for providing detailed demographic information, panelists are sometimes provided with incentives (e.g., apps, gift cards, cash, entry into a raffle and/or drawing, etc.). Accordingly, having a large panel can sometimes become cost prohibitive.
To alleviate the costs of constructing and/or maintaining a large panel, the audience measurement entity cooperates with other entities to obtain demographic information associated with media presentations. Example methods, apparatus, and/or articles of manufacture disclosed herein enable an audience measurement entity to request demographic information from other entities that operate based on user registration models. Cooperation with other entities that operate based on user registration models enables the audience measurement entity to effectively increase the size of the panel of users.
As used herein, a user registration model is a model in which users subscribe to services of those entities by creating an account and providing demographic-related information about themselves. Sharing of demographic information associated with registered users of database proprietors enables an audience measurement entity to receive audience measurement information from external sources (e.g., database proprietors), thus extending the coverage, accuracy, and/or completeness of their demographics-based audience measurements. Such access also enables the audience measurement entity to monitor persons who would not otherwise have joined an audience measurement panel.
Any entity having a database identifying demographics of a set of individuals may cooperate with the audience measurement entity. Such entities may be referred to as “database proprietors” and include entities such as wireless service carriers, mobile software/service providers, social networking sites (e.g., Facebook, Twitter, LinkedIn, Google, etc.), online retailer sites (e.g., Amazon.com, Buy.com, etc.), and/or any other Internet site that maintains user registration records (e.g., Yahoo!, MSN, Apple iTunes, Experian, etc.) There are many database proprietors operating on the Internet. Database proprietors provide services to large numbers of subscribers. In exchange for the provision of the service, the subscribers register with the proprietor. As part of this registration, the subscribers provide detailed demographic information. The database proprietors, as part of the use of the provided service (e.g., a social networking service, a shopping service, a news service, etc.) have access to set and/or collect cookies and/or other identifiers stored by a browser.
The database proprietor(s) report media presentation information and demographic information associated with the media presentation to the audience measurement entity. In traditional panelist-based systems, the panelist is aware that they are sharing demographic information with the audience measurement entity. However, in examples disclosed herein, demographic information is retrieved from a database proprietor and, accordingly, comes with data privacy concerns (because users may be unaware of the sharing of their demographic information). To that end, users may approve or prevent the sharing of demographic information on the part of the database proprietor. For example, when creating an account with the database proprietor(s), a user may be asked for their permission to share demographic information with other entities (e.g., the audience measurement entity).
In further contrast to demographic information received when enrolling panelists (where the panelist is requested to provide very detailed demographic information to the audience measurement entity), the demographic information collected by the database proprietor may not be as detailed as demographic information that would otherwise be collected by the audience measurement entity. For example, the database proprietor might not request demographic information related to the user's income, the user's interests, the user's race, etc. Furthermore, different database proprietors may request and/or store different information from the user. For example, a social media database proprietor may store demographic information related to user's race, interests, location, etc. while a credit reporting database proprietor may store demographic information related to a user's financial information (e.g., income, credit score, etc.).
In examples disclosed herein, database proprietors provide demographic information concerning users to the audience measurement entity (e.g., The Nielsen Company of Schaumburg, Ill., United States of America) in association with particular pieces of media. The demographic information, in some examples, is provided in the aggregate. In some examples, a database proprietor transmits demographic information on an aggregate basis when a threshold number of users to whom a particular piece of media was presented is reached. For example, aggregated demographic information may be provided only when there are more than one hundred users associated with the media. However, any other threshold amount of users may additionally or alternatively be used. In contrast, demographic information may be provided to the ratings entity on an individual basis when a single user is identified in association with the demographic information. Whether to provide the demographic information to the ratings entity in the aggregate or individually may be determined by the database proprietor for any reason such as, for example, privacy laws in the jurisdiction of the database proprietor, business factors, technical limitations, etc.
In some examples, to more accurately associate media presentations with the correct demographics, example methods, apparatus, and/or articles of manufacture disclosed herein leverage user information located in the audience measurement entity's records (e.g., panelist information) as well as user information located at one or more database proprietors (e.g., web service providers) that maintain records or profiles of users having accounts therewith. In some examples, multiple database proprietors may report demographic information to the media monitoring entity in association with the same media. Multiple sources (e.g., demographic information from the panels of an audience measurement company and/or registered user data of web service providers) may be useful because the additional data results in improved accuracy of demographic metrics for content and/or advertising campaigns. Example techniques disclosed herein use online registration data to identify demographics of users to track quantities of impressions attributable to demographics associated with those users. As used herein, an impression refers to an exposure to media (e.g., content and/or an advertisement). In Internet advertising, a quantity of impressions or impression count is the total number of times an advertisement or advertisement campaign has been accessed by a population. Impressions do not take into account multiple exposures to the same individual (i.e., two exposures to the same person count as two impressions). In contrast, unique impression counts eliminate duplicate exposures and, thus, only count one exposure per person irrespective of how many times that person may actually experience an exposure.
As used herein, the term “media” includes any type of content and/or advertisement delivered via any type of distribution medium. Thus, media includes television programming or television advertisements, radio programming or radio advertisements, movies, web sites, streaming media, etc. Example methods, apparatus, and articles of manufacture disclosed herein monitor media presentations at media devices. Such media devices may include, for example, Internet-enabled televisions, personal computers, Internet-enabled mobile handsets (e.g., a smartphone such as an Apple iPhone®, a Samsung Galaxy S® 4, etc.), video game consoles (e.g., Xbox®, PlayStation® 3), tablet computers (e.g., an iPad®), digital media players (e.g., AppleTV®, a Roku® media player, a Slingbox®, etc.), etc. In some examples, media monitoring information is aggregated to determine ownership and/or usage statistics of media devices, relative rankings of usage and/or ownership of media devices, types of uses of media devices (e.g., whether a device is used for browsing the Internet, streaming media from the Internet, etc.), and/or other types of media device information. In examples disclosed herein, monitoring information includes, but is not limited to, media identifying information (e.g., media-identifying metadata, codes, signatures, watermarks, and/or other information that may be used to identify presented media), application usage information (e.g., an identifier of an application, a time and/or duration of use of the application, a rating of the application, etc.), and/or device and/or user-identifying information (e.g., a username, a media access control (MAC) address, an Internet Protocol (IP) address, an Apple ID, a panelist identifier, a Google ID, any other type of identifier, etc.).
Media devices such as tablet computers (e.g., an Apple iPad®, an Asus Transformer™, etc.) present media using apps and/or browsers that access, retrieve, request, and/or present media (e.g., Internet media). Many different browsers exist such as, for example, Google Chrome®, Mozilla Firefox, Apple Safari®, Dolphin, etc. Apps and/or browser(s) can be downloaded by users through app stores such as, for example, Apple iTunes®, Google Play®, etc.
Operating systems of the media devices and/or browsers operated by the media devices are often closed platforms. That is, the operating systems and/or browsers provide a limited set of functions that can be accessed. In some examples, browsers have access to a limited set of functionality for sharing data outside of the media device. For example, browsers may have access to a limited set of user information (e.g., cookies), and/or may not allow programmatic access to audio and/or video of media presented by the device. Cookies can be used to store information related to a user of the media device in association with an accessed domain (e.g., Facebook.com, twitter.com, Nielsen.com, etc.). For example, a username may be stored in association with a particular domain, display settings may be stored in association with the domain, etc. Traditionally, cookies are of limited use for identifying users across domains. For example, browsers are only permitted to transmit cookies when accessing a site having a domain name matching the cookies. For example, browsers are not allowed to transmit cookies associated with the domain “xyz.com” when accessing the domain “abc.com.”
While cookies and/or other identifiers can be used to identify the media device and/or a user of the media device to the audience measurement entity and/or the database proprietor, it is equally important to properly identify the media presented via the media device. Media is traditionally identified using codes, signatures, watermarks, etc. embedded in audio and/or video of the media. However, identification of an audio and/or video watermark at media devices presents difficulties. For example, some media devices do not allow programmatic access to the audio and/or video of the media, processing audio and/or video watermarks may quickly drain a battery of the media device, etc. Examples disclosed herein address this problem through transcoding. In some such examples, a service provider (e.g., a streaming media provider) transcodes the watermark into a format which is readily ascertainable by the media device.
In some examples, media-identifying metadata having a first format is extracted from the presented media. The media-identifying metadata may indicate, for example, a watermark associated with the media, a universal resource locator (URL) (e.g., a URL of a database proprietor, etc.) indicating where to transmit a notification of the media presentation. In some such examples, the transport stream corresponds to a Moving Picture Experts Group (MPEG) 2 transport stream sent according to a hypertext transfer protocol (HTTP) live streaming (HLS) protocol. In some examples, the watermark is an audio watermark that is embedded in an audio portion of the media using a first metadata format. In some examples, the watermark having the first format is transcoded into media-identifying metadata having a second format. The media-identifying metadata having the second format may correspond to, for example, a textual representation of the watermark, such as a base-64 hexadecimal string of characters. In some examples, the media-identifying metadata is transmitted in a metadata transport stream associated with the media.
In some disclosed examples, streaming media is delivered to the media device using HTTP Live Streaming (HLS). However, any other past, present, and/or future method of streaming media to the media device may additionally or alternatively be used such as, for example, an HTTP Secure (HTTPS) protocol. HLS transport streams allow metadata to be included in and/or associated with, for example, a media stream, a timed text track, etc. In some disclosed examples, a media device uses a browser to display media received via HLS. Additionally or alternatively, in some disclosed examples the media device uses a media presenter (e.g., a browser plugin, an app, a framework, an application programming interface (API), etc.) to display media received via HLS.
Some example methods disclosed herein include decoding the HLS transport stream carrying the media-identifying metadata streamed to a media device to obtain the media. Some such example methods also include extracting metering data from the media and/or receiving metering data from an independent metering data source (e.g., a timed text track file sent in association with the media, a manifest file, etc.). In some examples, in addition to identifying the media, the media-identifying metadata may additionally or alternatively identify a source of the media. Additionally, some such example methods further include decoding media-identifying metadata (e.g., such as electronic guide (EPG) data, playlist data, etc.) already accompanying the transport stream carrying the media. Some such example methods further include verifying the media identifying metadata using the metering data (e.g., the transcoded watermark) extracted from the media.
In examples disclosed herein, media exposure metrics are monitored by retrieving metadata embedded in or otherwise transported with the media presented via a media presenter of the media device. In some examples, the metadata is stored in a Document Object Model (DOM) object. The DOM is a cross-platform and language-independent convention for representing and interacting with objects in Hypertext Markup Language (HTML). In some examples, media presenters (e.g., media plugins) such as, for example, the QuickTime player, emit DOM events that can be captured via JavaScript. By capturing the DOM events triggered by the media presenter, it is possible to extract metadata via the DOM. Once extracted, the metadata may be combined with other information such as, for example, cookie or other user identifying data associated with the user of the device, and transmitted to, for example, a database proprietor, and/or the audience measurement entity for analysis and/or computation with data collected from other devices.
In some examples, the metadata is stored in an ID3 tag format, although any other past, present, and/or future metadata format may additionally or alternatively used. An ID3 tag is a metadata container that may be appended to and/or transmitted in association with media. In the examples disclosed herein, an ID3v2 format is used. In particular, the media-identifying metadata is stored in a private frame of the ID3 tag. However, any other past, present, or future way of storing media-identifying metadata may additionally or alternatively be used.
In examples disclosed herein, a software development kit (SDK) is provided to website developers from, for example, an audience measurement entity or other entity. The SDK facilitates instrumenting and/or otherwise enabling websites (e.g., media websites (such as streaming video websites), news websites, image websites, social media websites, online gaming websites, etc.) with monitoring functionalities which collect and transmit monitoring information (e.g., a cookie and/or other user or device identifier, a media identifier (the ID3 tag), etc.) to a database proprietor and/or the audience measurement entity. In particular, the website developers create websites that include media monitoring instructions using the SDK. Accordingly, rather than relying on a dedicated monitoring application installed on a computer (e.g., a tablet, a laptop, a smartphone, etc.), websites disclosed herein are instrumented with monitoring instructions such that the browser transmits monitoring information to the database proprietor and/or the monitoring entities (e.g., the audience measurement entity). In some examples, monitoring instructions provided by the SDK are implemented using JavaScript instructions. However, any other language or type of script or instructions may additionally or alternatively be used. The monitoring instructions enable the browser to notify the database proprietor and/or the monitoring entities (e.g., the audience measurement entity) when a website and/or media associated with the website is presented, notify the database proprietor and/or the monitoring entities (e.g., the audience measurement entity) what media and/or website(s) are presented, notify the database proprietor and/or the monitoring entities (e.g., the audience measurement entity) how the website and/or media is being presented (e.g. via a tablet display, via a television, etc.), notify the database proprietor and/or the monitoring entities (e.g., the audience measurement entity) of a duration of exposure of a website and/or media associated with the website, etc. In some examples, the media monitoring instructions may be triggered by, for example presentation of a media element such as, for example, a video, audio, an image, etc.
Example methods, apparatus and/or articles of manufacture disclosed herein enable reporting of media impressions and corresponding demographics from the database proprietor to the ratings entity, also referred to herein as an audience measurement entity (AME.) In this manner, the AME can track media impressions on media devices, and/or create reports of media impressions broken down by different demographic statistics.
Example methods, apparatus, and articles of manufacture disclosed herein can be used to determine media impressions, content impressions, advertisement impressions, content exposure, and/or advertisement exposure using user information, which is distributed across different databases (e.g., different website owners, service providers, etc.) on the Internet. Not only do example methods, apparatus, and articles of manufacture disclosed herein enable more accurate correlation of Internet media exposure to user (e.g., demographics) information, but they also effectively extend panel sizes and compositions beyond persons participating in the panel of a monitoring entity (e.g., an audience measurement entity and/or a ratings entity) to persons registered in Internet databases such as the databases of wireless service carriers, mobile software/service providers, social medium sites (e.g., Facebook, Twitter, Google, etc.), and/or any other Internet sites such as Yahoo!, MSN, Apple iTunes, Experian, etc. This extension effectively leverages the media exposure tracking capabilities of a monitoring entity (e.g., the audience measurement entity) and the databases of non-AME entities such as social media and/or other websites to create an enormous, demographically accurate panel that results in accurate, reliable measurements of exposures to media such as advertising and/or content (e.g., programming).
The example media provider 110 of the illustrated example of
The service provider 120 of the illustrated example of
The media identifier 125 of the illustrated example of
The example media identifier 125 of
The example transcoder 130 of the illustrated example of
The metadata embedder 135 of the illustrated example of
In the illustrated example, the metadata embedder 135 embeds the metadata determined by the media identifier 125 into the transport stream(s) carrying the streaming media. In the illustrated example, the metadata embedder 135 embeds the metadata into an internal metadata channel, such as by encoding metadata that is in a binary and/or other appropriate data format into one or more data fields of the transport stream(s) that is(are) capable of carrying metadata. For example, the metadata embedder 135 can insert ID3 tag metadata corresponding to the metering metadata into the transport stream(s) that is (are) to stream the media in accordance with the HLS or other appropriate streaming protocol. Additionally or alternatively, the metadata embedder 135 may embed the metadata into an external metadata channel, such as by encoding the metadata into an M3U8 or other data file that is to be associated with (e.g., included in, appended to, sent prior to, etc.) the transport stream(s) that are to provide the streaming media to the client device 160.
The media transmitter 140 of the illustrated example of
The media transmitter 140 of the illustrated example employs any appropriate technique(s) to select and/or stream the media to a requesting device, such as the client device 160. For example, the media transmitter 140 of the illustrated example selects media that has been identified by the media identifier 125, transcoded by the transcoder 130 and undergone metadata embedding by the metadata embedder 135. The media transmitter 140 then streams the media to the client device 160 via the network 150 using HLS or any other streaming protocol.
In some examples, the media identifier 125, the transcoder 130, and/or the metadata embedder 130 prepare media for streaming regardless of whether (e.g., prior to) a request is received from the client device 160. In such examples, the already-prepared media is stored in a data store of the service provider 120 (e.g., such as in a flash memory, magnetic media, optical media, etc.). In such examples, the media transmitter 140 prepares a transport stream for streaming the already-prepared media to the client device 160 when a request is received from the client device 160. In other examples, the media identifier 125, the transcoder 130, and/or the metadata embedder 130 prepare the media for streaming in response to a request received from the client device 160.
The example network 150 of the illustrated example is the Internet. Additionally or alternatively, any other network(s) communicatively linking the service provider 120 and the client device such as, for example, a private network, a local area network (LAN), a virtual private network (VPN), etc. may be used. The network 150 may comprise any number of public and/or private networks using any type(s) of networking protocol(s).
The client device 160 of the illustrated example of
Client devices such as the client device 160 of
The example database proprietor 180, 182 of the illustrated example of
The central facility 170 of the audience measurement entity of the illustrated example of
In the illustrated example, the central facility 170 instructs the metadata embedder 135 and/or, more generally, the service provider 120 to embed a tag in media to be streamed. In the illustrated example, the tag is formatted as an ID3 tag. For example, the tag may be formatted as a JavaScript instruction. However, any other format of tag and/or instructions may additionally or alternatively be used. In some examples, the metadata embedder 135 is provided to the service provider 120 by the audience measurement entity.
In the illustrated example, the central facility 170 stores and analyzes metering information received from a plurality of different client devices and/or from the database proprietor(s) 180, 182. For example, the central facility 170 may sort and/or group metering information by media provider 110 (e.g., by grouping all metering data associated with a particular media provider 110). Any other processing of metering information may additionally or alternatively be performed. In the illustrated example, the central facility 170 is associated with an audience measurement company and is not involved with the delivery of media to the client device.
Although the following examples refer to an audience measurement entity, any monitoring entity may fill this role.
As disclosed herein, the media monitoring instructions include instructions (e.g., Java, JavaScript, or any other computer language or script) that, when executed by the browser 165 and/or, more generally, the client device 160, cause the client device 160 to collect and/or otherwise identify the media presented by the browser 165 and/or the client device 160, and to collect one or more user identifiers 166A, 166B (e.g., cookies). The user identifiers 166A, 166B of the illustrated example include identifiers that can be used by corresponding ones of the partner database proprietors 180, 182 to identify the user or users of the client device 160, and to locate user information corresponding to the user(s). For example, the user identifiers 166A, 166B may include hardware identifiers (e.g., an international mobile equipment identity (IMEI), a mobile equipment identifier (MEID), a media access control (MAC) address, etc.), an app store identifier (e.g., a Google Android ID, an Apple ID, an Amazon ID, etc.), an open source unique device identifier (OpenUDID), an open device identification number (ODIN), a login identifier (e.g., a username), an email address, user agent data (e.g., application type, operating system, software vendor, software revision, etc.), third-party service identifiers (e.g., advertising service identifiers, device usage analytics service identifiers, demographics collection service identifiers), cookies, etc. In some examples, fewer or more user identifiers 166A, 166B may be used. The user identifiers 166A, 166B and the media identifying metadata are transmitted in a request to a database proprietor 180, 182. The request is referred to as a dummy request in that it is not actually requesting information (e.g., a webpage), but rather is a vehicle for conveying monitoring information (e.g., the user identifier(s) 166A, 166B, the media-identifying metadata, etc.). In addition, although only two database proprietors 180, 182 are shown in
In the illustrated example, the client device 160 requests media from the service provider 120 (line 185). The media may be an advertisement, video, audio, text, a graphic, a web page, news, educational media, entertainment media, or any other type of media. In the illustrated example, service provider 120 replies to the request with the media (line 186). The reply from the service provider 120 (e.g., the media) includes monitoring instructions that cause the browser to identify the media to, for example, a third party. The browser 165 then displays the media and identifies the media by accessing a media ID provided in and/or in association with the media. In examples disclosed herein, the media ID is an ID3 tag including media-identifying metadata, source-identifying metadata, a watermark, etc. At the direction of the monitoring instructions, the browser 165 then transmits a dummy request to the database proprietor 180 (line 187). In the illustrated example, a user identifier 166A (e.g., a cookie associated with the database proprietor 180) has previously been stored by the browser 165. The request to the database proprietor 180 (line 187) includes the user identifier 166A and the media identifier. In some examples, the media identifier is encrypted to prevent the database proprietor 180, 182 from identifying the media. The encrypted media identifier may later be decrypted by the central facility 170. The database proprietor 180 then determines that it can identify the user based on the user identifier 166A, stores a record of the media presentation, and sends an acknowledgement to the client device 160 (line 188). At a later time, the database proprietor 180 transmits the record of the media presentation to the central facility 170 (line 194) and, in return, receives an acknowledgement message (line 195). The record of the media presentation includes the media-identifying metadata (which may be encrypted). In some examples, the media identifying metadata of the record is formatted as an ID3 tag. Based on the received record, the central facility 170 and/or, more generally, the AME, may report on presentation metrics for different media.
In the illustrated example of
Like the example database proprietor 180 of
While in the illustrated examples of
The media presenter 310 of the illustrated example of
The example event listener 320 of the illustrated example of
The metadata retriever 330 of the illustrated example of
The metadata converter 340 of the illustrated example of
The metadata transmission location determiner 345 of the illustrated example of
In some examples, different service providers implement the monitoring instructions to specify the destination (e.g., the specific database proprietor) where the media-identifying information is to be transmitted. Different service providers may, accordingly, be associated with different database proprietors. Associations with different database proprietors may result in a more efficient and/or more accurate recordation of media impressions and association of those impressions with demographic information. For example, users who view media at a financial website may be more readily identifiable by a database proprietor associated with financial services (e.g., a stock broker, a credit bureau, Experian, etc.) than a database proprietor associated with social media (e.g., Facebook, Twitter, etc.). Therefore, a service provider may create the monitoring instructions to cause the client device to send a dummy request to a specific database proprietor (e.g., Experian) that matches the media to be annotated.
In the illustrated example, a destination field of the ID3 tag conveying the media-identifying metadata includes a destination field that, when interpreted by the monitoring instructions, causes the monitoring instructions to send the dummy request to the specified destination (e.g., a URL). In such an example, at the direction of the monitoring instructions, the client device determines the location to send the dummy request based on the destination field of the ID3 tag. Such an example of determining where to send the dummy request based on the destination field of the ID3 tag is disclosed in connection with blocks 810 and 815 of
The transmitter 350 of the illustrated example of
The user-identifying information store 355 of the illustrated example is implemented by a memory for storing information (e.g., user-identifying information, cookies, etc.) The example user-identifying information store 355 of the illustrated example of
The HTTP server 410 of the illustrated example of
The user registration data receiver 420 of the illustrated example of
The demographic information database 430 of the illustrated example is implemented by a memory for storing user registration data (e.g., demographic information associated with users). The example demographic information database 430 of the illustrated example of
The user ID comparator 440 of the illustrated example of
The metadata processor 450 of the illustrated example of
The metadata database 460 is implemented by a memory for storing media-identifying metadata received from the browser via the dummy request (e.g., the request represented by line 187 of
The metadata transmitter 470 of the illustrated example of
The HTTP server 171 of the illustrated example of
The user registration data receiver 421 of the illustrated example of
The demographic information database 431 of the illustrated example is implemented by a memory for storing user registration data (e.g., demographic information associated with users). The example demographic information database 431 of the illustrated example of
The user ID comparator 441 of the illustrated example of
The metadata processor 451 of the illustrated example of
The metadata database 461 is implemented by a memory for storing media-identifying metadata received from the browser via the dummy request (e.g., the request represented by line 197 of
The metadata instructor 480 of the illustrated example of
The data receiver 481 of the illustrated example of
HLS is an adaptive format, in that, although multiple devices retrieve the same manifest 510, different transport streams may be displayed depending on one or more factors. For example, devices having different bandwidth availabilities (e.g., a high speed Internet connection, a low speed Internet connection, etc.) and/or different display abilities (e.g., a small size screen such as a cellular phone, a medium size screen such as a tablet and/or a laptop computer, a large size screen such as a television, etc.) select an appropriate transport stream for their display and/or bandwidth abilities. In some examples, a cellular phone having a small screen and limited bandwidth uses a low resolution transport stream. Alternatively, in some examples, a television having a large screen and a high speed Internet connection uses a high resolution transport stream. As the abilities of the device change (e.g., the device moves from a high speed Internet connection to a low speed Internet connection) the device may switch to a different transport stream.
In the illustrated example of
In the illustrated example, each transport stream 520, 521, 522, 530, 531, 532, 540, 541, and/or 542 includes a video stream 550, 551, 552, an audio stream 555, 556, 552, and a metadata stream 560, 561, 562. The video stream 550, 551, and/or 552 includes video associated with the media at different resolutions according to the resolution of the transport stream with which the video stream is associated. The audio stream 555, 556, and/or 557 includes audio associated with the media. The metadata stream 560, 561, and/or 562 includes metadata such as, for example, an ID3 tag associated with the media.
In examples disclosed herein, the ID3 tag is formatted as an ID3v2 tag. However, any other type and/or format of metadata and/or metadata container may additionally or alternatively be used. In the illustrated example, the media-identifying information is stored in a private frame of the ID3 tag. However, the media-identifying information may be stored in any other location. The media-identifying information of the illustrated example includes a destination domain name and a textual version of the audio watermark identified by the media identifier 125 of
While an example manner of implementing the example service provider 120 of
Flowcharts representative of example machine readable instructions for implementing the example service provider 120 of
As mentioned above, the example processes of
The media identifier 125 of the illustrated example then identifies the media (block 620). The media identifier 125 identifies the media by extracting metering data (e.g., signatures, watermarks, etc.) from the media. Based on the extracted metering data, the media identifier 125 generates metadata (block 630). In the illustrated example, the metadata is generated in an ID3 format. However, any other metadata format may additionally or alternatively be used. Further, in the illustrated example, the metadata is generated based on the extracted metering data. However, in some examples, the metadata may be generated by querying an external source using some or all of the extracted metering data.
The media is then transcoded by the transcoder 130 of the service provider 120 (block 640). In the illustrated example, the media is transcoded into an MPEG2 transport stream that may be transmitted via HTTP live streaming (HLS). The metadata embedder 135 of the service provider 120 embeds the metadata into the media (block 650). In some examples, the metadata is encrypted prior to being embedded into the media. In the illustrated example, the metadata is embedded into a metadata channel of the media. However, in some examples, the metadata may be embedded in an ancillary data document, file, etc. that may be associated with the media. For example, the metadata may be embedded in a manifest file (e.g., an M3U8 file), in a text track associated with the media, etc.
The media is then transmitted by the media transmitter 140 of the service provider 120 (block 660). In the illustrated example, the media is transmitted using HTTP live streaming (HLS). However, any other format and/or protocol for transmitting (e.g., broadcasting, unicasting, multicasting, etc.) media may additionally or alternatively be used.
The event listener 320 of the browser 165 begins listening for an event (block 720). In the illustrated example, the event listener 320 listens for a JavaScript event triggered by the media presenter 210. However, in some examples, the event listener 320 listens for any other event(s) such as, for example, a media change event, a user interaction event (e.g., when a user clicks on an object), a display event (e.g., a page load), etc. If the event listener 320 does not detect an event, the event listener 320 continues to listen for the event until, for example, the browser 165 is closed, a different webpage is loaded, etc.
If the event listener 320 detects an event, the metadata retriever 330 of the browser 165 retrieves the metadata (block 730). In the illustrated example, the event listener 320 passes an event object to the metadata retriever 330, which inspects the event object to retrieve the metadata. However, in some examples, the event listener 320 passes an identifier of an object (e.g., the media presenter 310 display object), which indicates the object from which the metadata retriever 330 is to retrieve metadata. In the illustrated example, the metadata retriever 330 inspects a document object module (DOM) object to retrieve the metadata. However, in some examples, the metadata retriever 330 inspects, for example, a timed text track, a metadata stream of the HLS media, etc. to retrieve the metadata. In the illustrated example, the metadata is formatted as an ID3 tag. However, any other format of metadata may additionally or alternatively be used. In some examples, the metadata retriever 330 retrieves operational information about the media presenter 310 and/or, more generally, the browser 165. The retrieved operational information may include, for example, information about whether the media presenter 310 is fully or partially visible (e.g., the media presenter 310 is fully viewable, the media presenter 310 is 50% viewable, the media presenter 310 is not viewable, etc.), information about whether the media presenter 310 is in the foreground or background, etc.
The metadata converter 340 of the browser 165 then converts the metadata (block 740) into a format for use by the transmitter 350 of the browser 165. In the illustrated example, the metadata is converted from a binary data format into a text format. In some examples, the metadata is parsed to identify portions (e.g., fields, sections, etc.) of interest of the metadata (e.g., a genre, an artist, a song title, an album name, a transmitting station/server site, etc.). In some examples, the metadata converter 340 encrypts the metadata. Encrypting the metadata prevents third parties (e.g., the database proprietor) from identifying the media, while still permitting logging of impressions for association with demographics. In the illustrated example, the metadata converter 340 adds a timestamp to the metadata prior to transmitting the metadata to the database proprietor 180, 182. Timestamping (e.g., recording a time that an event occurred) enables accurate identification and/or correlation of media that was presented and/or the time that it was presented with the user(s) of the presentation device.
In some examples, the metadata may not undergo conversion before transmission by the transmitter (e.g., the metadata may be sent in the format in which it is retrieved by the metadata retriever 330). In such examples, the database proprietor 180, 182, and/or the central facility 170 converts the metadata by, for example, converting the metadata to a different format, parsing the metadata to identify portions of interest of the metadata, decrypting the metadata, etc. Conversion of the metadata by the database proprietor 180, 182, and/or the central facility 170 facilitates correlation of the media that was presented with an identifier identifying to whom the media was presented. In some examples, the database proprietor 180, 182, and/or the central facility 170 timestamps the metadata upon receipt. Timestamping the metadata enables accurate identification and/or correlation of media that was presented and/or the time that it was presented with the user(s) of the presentation device.
The metadata transmission location determiner 345 of the browser 165 then determines a location to which the metadata should be transmitted (block 750). In the illustrated example, the location is determined based on a domain name included in the ID3 tag. However, any other way of determining a location to transmit metadata may additionally or alternatively be used. An example process for determining the location to transmit the metadata is disclosed in connection with
The transmitter 350 then transmits the metadata to the location identified by the metadata transmission location determiner 345 (block 750). In the illustrated example, the metadata is transmitted using an HTTP Post request. However, any other method of transmitting data and/or metadata may additionally or alternatively be used. For example, a file transfer protocol (FTP) instruction, an HTTP Get request, an Asynchronous JavaScript and extensible markup language (XML) (AJAX) message, etc., may be used to transmit the metadata. In some examples, the metadata is not transmitted to the database proprietor 180, 182, and/or the central facility 170. For example, the metadata may be transmitted to a display object of the client device 160 for display to a user. In the illustrated example, the metadata is transmitted in real-time (e.g., streamed) to the database proprietor 180, 182. However, in some examples, the metadata may be stored (e.g., cached, buffered, etc.) for a period of time before being transmitted to the database proprietor 180, 182. In some examples, the transmitter 350 transmits the operational data retrieved by the metadata retriever 330 from the media presenter 310. Transmitting the operational information enables the audience measurement entity to compute additional media presentation metrics (e.g., whether users listen to streaming audio with the media presenter 310 in the background, etc.).
However, in some examples, the ID3 tag does not identify the location to transmit the metadata. If the ID3 tag does not identify the location to transmit the metadata (block 810), the example metadata transmission location determiner 345 determines whether the service provider identifies the location transmit the metadata (block 820). In some examples, the service provider 120, when implementing the SDK associated with the monitoring instructions implemented by the browser 165, specifies a database proprietor to which the metadata should be transmitted. In such an example, the metadata transmission location determiner 345 uses the location identified by the service provider (block 825) to determine the destination of the dummy request.
In some examples, neither the metadata nor the service provider may identify the location where the metadata should be transmitted (blocks 810, 820). In such an example, the metadata transmission location determiner 345 uses a default location to transmit the metadata (block 830) to determine the destination of the dummy request. The default location may be, for example, a preferred database proprietor such as, for example Facebook, Twitter, Experian, etc. In some examples, the default location may be the central facility 170. The example machine-readable instructions 800 of
If the user identifier data can be used to identify the user (block 920), the user ID comparator 440 determines the user identifier (block 950). The metadata processor 450 then stores the received metadata and the associated user identifier in the metadata database 460. (block 960). In the illustrated example, the metadata processor 450 stores the media identifying metadata (e.g., the ID3 tag) and the user identifier. When storing the metadata and the user identifier, the metadata processor 450 may store an impression record in a similar fashion to, for example, the table 1070 of
The HTTP server 410 then transmits an acknowledgment message to the requesting client (block 970). Transmitting the acknowledgment message notifies the requesting client (e.g., the browser 165) that no further action need be taken with respect to the dummy request. In some examples, the database proprietor 180 sends a redirect message instructing the browser 165 to contact a second database proprietor 182 even if the database proprietor 180 was able to identify the user. Such redirection may enable different database proprietors, who may store different types of demographic data (e.g., financial data, geographic data, etc.), to collect a larger data set of demographic data than could be collected by a single database proprietor.
In the illustrated example of
In the illustrated example, four user records are shown. A first user record 1085 represents user A. A second user record 1086 represents user B. A third user record 1087 represents user C. A fourth record 1087 represents user D. While in the illustrated example of
The example table 1089 of
In the illustrated example of
If data has been received from a sufficient number of database proprietors (block 1120), the metadata processor 451 aggregates the demographic data from the database proprietor(s) (block 1130). The metadata processor 451 then generates a media presentation report based on the metadata and the aggregated demographic information (block 1140).
The processor platform 1200 of the illustrated example includes a processor 1212. The processor 1212 of the illustrated example is hardware. For example, the processor 1212 can be implemented by one or more integrated circuits, logic circuits, microprocessors or controllers from any desired family or manufacturer.
The processor 1212 of the illustrated example includes a local memory 1213 (e.g., a cache). The processor 1212 of the illustrated example is in communication with a main memory including a volatile memory 1214 and a non-volatile memory 1216 via a bus 1218. The volatile memory 1214 may be implemented by 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 1216 may be implemented by flash memory and/or any other desired type of memory device. Access to the main memory 1214, 1216 is controlled by a memory controller.
The processor platform 1200 of the illustrated example also includes an interface circuit 1220. The interface circuit 1220 may be implemented by any type of interface standard, such as an Ethernet interface, a universal serial bus (USB), and/or a PCI express interface.
In the illustrated example, one or more input devices 1222 are connected to the interface circuit 1220. The input device(s) 1222 permit(s) a user to enter data and commands into the processor 1212. The input device(s) can be implemented by, for example, an audio sensor, a microphone, a camera (still or video), a keyboard, a button, a mouse, a touchscreen, a track-pad, a trackball, isopoint and/or a voice recognition system.
One or more output devices 1224 are also connected to the interface circuit 1220 of the illustrated example. The output devices 1224 can be implemented, for example, by display devices (e.g., a light emitting diode (LED), an organic light emitting diode (OLED), a liquid crystal display, a cathode ray tube display (CRT), a touchscreen, a tactile output device, a light emitting diode (LED), a printer and/or speakers). The interface circuit 1220 of the illustrated example, thus, typically includes a graphics driver card, a graphics driver chip or a graphics driver processor.
The interface circuit 1220 of the illustrated example also includes a communication device such as a transmitter, a receiver, a transceiver, a modem and/or network interface card to facilitate exchange of data with external machines (e.g., computing devices of any kind) via a network 1226 (e.g., an Ethernet connection, a digital subscriber line (DSL), a telephone line, coaxial cable, a cellular telephone system, etc.).
The processor platform 1200 of the illustrated example also includes one or more mass storage devices 1228 for storing software and/or data. Examples of such mass storage devices 1228 include floppy disk drives, hard drive disks, compact disk drives, Blu-ray disk drives, RAID systems, and digital versatile disk (DVD) drives.
The coded instructions 1232 of
From the foregoing, it will be appreciated that the above disclosed methods, apparatus and articles of manufacture enable monitoring of media presentations and association of demographic information provided by one or more database proprietors with the same. In particular, media identifying metadata (which may be encrypted and/or formatted as an ID3 tag) and user identifying information is transmitted to database proprietors by client devices in response to detecting a media presentation. The database proprietors aggregate demographic information (based on the user identifying information) in association with the presented media, and report the demographic information and the media-identifying information to an audience measurement entity.
Although certain example methods, apparatus, and articles of manufacture have been disclosed 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 claims of this patent.
This patent arises from a continuation of U.S. patent application Ser. No. 16/902,065, filed on Jun. 15, 2020, and entitled “METHODS AND APPARATUS TO MEASURE EXPOSURE TO STREAMING MEDIA”, which is a continuation of U.S. patent application Ser. No. 16/436,476, filed on Jun. 10, 2019, and entitled “METHODS AND APPARATUS TO MEASURE EXPOSURE TO STREAMING MEDIA”, which is a continuation of U.S. patent application Ser. No. 15/299,884, filed on Oct. 21, 2026, and entitled “METHODS AND APPARATUS TO MEASURE EXPOSURE TO STREAMING MEDIA”, now U.S. Pat. No. 10,356,455, which is a continuation of U.S. patent application Ser. No. 15/082,991, filed on Mar. 28, 2016, and entitled “METHODS AND APPARATUS TO MEASURE EXPOSURE TO STREAMING MEDIA”, now U.S. Pat. No. 9,503,784, which is a continuation of U.S. patent application Ser. No. 14/144,352, filed on Dec. 30, 2013 and entitled “METHODS AND APPARATUS TO MEASURE EXPOSURE TO STREAMING MEDIA,” now U.S. Pat. No. 9,332,035, which claims the benefit of U.S. Provisional Patent Application Ser. No. 61/889,505, which was filed on Oct. 10, 2013 and of U.S. Provisional Patent Application Ser. No. 61/890,176, which was filed on Oct. 11, 2013. Priority to U.S. patent application Ser. No. 16/902,065, U.S. patent application Ser. No. 16/436,476, U.S. patent application Ser. No. 15/299,884, U.S. patent application Ser. No. 15/082,991, U.S. patent application Ser. No. 14/144,352, U.S. Provisional Patent Application Ser. No. 61/889,505, and U.S. Provisional Patent Application Ser. No. 61/890,176 is hereby claimed. U.S. patent application Ser. No. 16/902,065, U.S. patent application Ser. No. 16/436,476, U.S. patent application Ser. No. 15/299,884, U.S. patent application Ser. No. 15/082,991, U.S. patent application Ser. No. 14/144,352, U.S. Provisional Patent Application Ser. No. 61/889,505, and U.S. Provisional Patent Application Ser. No. 61/890,176 are hereby incorporated herein by reference in their 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 |
| 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 | Löfberg | 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 |
| 5343239 | Lappington et al. | Aug 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 |
| 5450134 | Legate | Sep 1995 | A |
| 5483658 | Grube et al. | Jan 1996 | A |
| 5497479 | Hornbuckle | Mar 1996 | A |
| 5499340 | Barritz | Mar 1996 | A |
| 5584050 | Lyons | Dec 1996 | A |
| 5594934 | Lu et al. | Jan 1997 | A |
| 5675510 | Coffey et al. | Oct 1997 | A |
| 5793409 | Tetsumura | Aug 1998 | A |
| 5796952 | Davis et al. | Aug 1998 | A |
| 5841978 | Rhoads | Nov 1998 | A |
| 5848396 | Gerace | Dec 1998 | A |
| 5910987 | Ginter et al. | Jun 1999 | A |
| 5956716 | Kenner et al. | Sep 1999 | A |
| 5974396 | Anderson et al. | Oct 1999 | A |
| 6052730 | Felciano et al. | Apr 2000 | A |
| 6055573 | Gardenswartz | Apr 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 |
| 6216129 | Eldering | Apr 2001 | B1 |
| 6223215 | Hunt et al. | Apr 2001 | B1 |
| 6247050 | Tso et al. | Jun 2001 | B1 |
| 6286036 | Rhoads et al. | Sep 2001 | B1 |
| 6286140 | Ivanyi | Sep 2001 | B1 |
| 6298348 | Eldering | Oct 2001 | B1 |
| 6415323 | McCanne et al. | Jul 2002 | B1 |
| 6434614 | Blumenau | Aug 2002 | B1 |
| 6460079 | Blumenau | Oct 2002 | B1 |
| 6463445 | Suzuki et al. | Oct 2002 | B1 |
| 6505160 | Levy et al. | Jan 2003 | B1 |
| 6529952 | Blumenau | Mar 2003 | B1 |
| 6642966 | Limaye | Nov 2003 | B1 |
| 6651253 | Dudkiewicz et al. | Nov 2003 | B2 |
| 6658410 | Sakamaki et al. | Dec 2003 | B1 |
| 6714683 | Tian et al. | Mar 2004 | B1 |
| 6829368 | Meyer et al. | Dec 2004 | B2 |
| 6839680 | Liu et al. | Jan 2005 | B1 |
| 6877007 | Hentzel et al. | Apr 2005 | B1 |
| 6970886 | Conwell et al. | Nov 2005 | B1 |
| 6993590 | Gauthier et al. | Jan 2006 | B1 |
| 7039699 | Narin et al. | May 2006 | B1 |
| 7058697 | Rhoads | Jun 2006 | B2 |
| 7092926 | Cerrato | Aug 2006 | B2 |
| 7095871 | Jones et al. | Aug 2006 | B2 |
| 7127305 | Palmon | Oct 2006 | B1 |
| 7150030 | Eldering et al. | Dec 2006 | B1 |
| 7159023 | Tufts | Jan 2007 | B2 |
| 7171018 | Rhoads et al. | Jan 2007 | B2 |
| 7181412 | Fulgoni et al. | Feb 2007 | B1 |
| 7215280 | Percy et al. | May 2007 | B1 |
| 7260837 | Abraham et al. | Aug 2007 | B2 |
| 7323991 | Eckert et al. | Jan 2008 | B1 |
| 7343417 | Baum | Mar 2008 | B2 |
| 7363278 | Schmelzer et al. | Apr 2008 | B2 |
| 7363643 | Drake et al. | Apr 2008 | B2 |
| 7386473 | Blumenau | Jun 2008 | B2 |
| 7406516 | Davis et al. | Jul 2008 | B2 |
| 7444388 | Svendsen | Oct 2008 | B1 |
| 7526538 | Wilson | Apr 2009 | B2 |
| 7546370 | Acharya et al. | Jun 2009 | B1 |
| 7590568 | Blumenau | Sep 2009 | B2 |
| 7593576 | Meyer et al. | Sep 2009 | B2 |
| 7600014 | Russell et al. | Oct 2009 | B2 |
| 7613635 | Blumenau | Nov 2009 | B2 |
| 7634786 | Knee et al. | Dec 2009 | B2 |
| 7644156 | Blumenau | Jan 2010 | B2 |
| 7650407 | Blumenau | Jan 2010 | B2 |
| 7653724 | Blumenau | Jan 2010 | B2 |
| 7712114 | Ramaswamy | May 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 |
| 7827312 | Ramaswamy et al. | Nov 2010 | B2 |
| 7882242 | Chen | Feb 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 |
| 7962934 | Eldering et al. | Jun 2011 | B1 |
| 8006259 | Drake et al. | Aug 2011 | B2 |
| 8032626 | Russell et al. | Oct 2011 | B1 |
| 8046255 | Bistriceanu | Oct 2011 | B2 |
| 8060601 | Brown et al. | Nov 2011 | B1 |
| 8117193 | Svendsen et al. | Feb 2012 | B2 |
| 8131861 | Butler et al. | Mar 2012 | B2 |
| 8229780 | Davidow et al. | Jun 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 |
| 8387084 | Klappert et al. | Feb 2013 | B1 |
| 8495198 | Sim et al. | Jul 2013 | B2 |
| 8543454 | Fleischman et al. | Sep 2013 | B2 |
| 8578272 | Pantos et al. | Nov 2013 | B2 |
| 8626084 | Chan et al. | Jan 2014 | B2 |
| 8631122 | Kadam et al. | Jan 2014 | B2 |
| 8713168 | Heffernan et al. | Apr 2014 | B2 |
| 8839338 | Eyer | Sep 2014 | B2 |
| 8843626 | Mazumdar et al. | Sep 2014 | B2 |
| 8856869 | Brinskelle | Oct 2014 | B1 |
| 8909771 | Heath | Dec 2014 | B2 |
| 8910195 | Barney et al. | Dec 2014 | B1 |
| 8954536 | Kalus et al. | Feb 2015 | B2 |
| 9332035 | Ramaswamy et al. | May 2016 | B2 |
| 9503784 | Ramaswamy et al. | Nov 2016 | B2 |
| 10356455 | Ramaswamy et al. | Jul 2019 | B2 |
| 10687100 | Ramaswamy et al. | Jun 2020 | B2 |
| 10924347 | Narsian | Feb 2021 | B1 |
| 11197046 | Ramaswamy et al. | Dec 2021 | B2 |
| 20010031066 | Meyer et al. | Oct 2001 | A1 |
| 20010044851 | Rothman et al. | Nov 2001 | A1 |
| 20020016969 | Kimble | Feb 2002 | A1 |
| 20020032734 | Rhoads | Mar 2002 | A1 |
| 20020033842 | Zetts | Mar 2002 | A1 |
| 20020053078 | Holtz et al. | May 2002 | A1 |
| 20020059218 | August et al. | May 2002 | A1 |
| 20020062382 | Rhoads et al. | May 2002 | A1 |
| 20020069037 | Hendrickson et al. | Jun 2002 | A1 |
| 20020099609 | Nascenzi et al. | Jul 2002 | A1 |
| 20020111934 | Narayan | Aug 2002 | A1 |
| 20020112002 | Abato | Aug 2002 | A1 |
| 20020120925 | Logan | Aug 2002 | A1 |
| 20020124246 | Kaminsky et al. | Sep 2002 | A1 |
| 20020138852 | Reynolds et al. | Sep 2002 | A1 |
| 20020144262 | Plotnick et al. | Oct 2002 | A1 |
| 20020157112 | Kuhn | Oct 2002 | A1 |
| 20020162118 | Levy et al. | Oct 2002 | A1 |
| 20020194592 | Tsuchida et al. | Dec 2002 | A1 |
| 20030006911 | Smith et al. | Jan 2003 | A1 |
| 20030021441 | Levy et al. | Jan 2003 | A1 |
| 20030037131 | Verma | Feb 2003 | A1 |
| 20030046385 | Vincent | Mar 2003 | A1 |
| 20030065770 | Davis et al. | Apr 2003 | A1 |
| 20030088674 | Ullman et al. | May 2003 | A1 |
| 20030093810 | Taniguchi | May 2003 | A1 |
| 20030105870 | Baum | Jun 2003 | A1 |
| 20030115598 | Pantoja | Jun 2003 | A1 |
| 20030177488 | Smith et al. | Sep 2003 | A1 |
| 20030220901 | Carr et al. | Nov 2003 | A1 |
| 20040003394 | Ramaswamy | Jan 2004 | A1 |
| 20040025181 | Addington et al. | Feb 2004 | A1 |
| 20040037271 | Liscano et al. | Feb 2004 | A1 |
| 20040073916 | Petrovic et al. | Apr 2004 | A1 |
| 20040088212 | Hill | May 2004 | A1 |
| 20040107125 | Guheen et al. | Jun 2004 | A1 |
| 20040128514 | Rhoads | Jul 2004 | A1 |
| 20040137929 | Jones et al. | Jul 2004 | A1 |
| 20040254887 | Jacoby | Dec 2004 | A1 |
| 20050033657 | Herrington et al. | Feb 2005 | A1 |
| 20050033758 | Baxter | Feb 2005 | A1 |
| 20050058319 | Rhoads | Mar 2005 | A1 |
| 20050138179 | Encamacion et al. | Jun 2005 | A1 |
| 20050152287 | Yokomitsu et al. | Jul 2005 | A1 |
| 20050166233 | Beyda et al. | Jul 2005 | A1 |
| 20050192933 | Rhoads et al. | Sep 2005 | A1 |
| 20050193425 | Sull et al. | Sep 2005 | A1 |
| 20050223093 | Hanson et al. | Oct 2005 | A1 |
| 20060056625 | Nakabayashi et al. | Mar 2006 | A1 |
| 20060089754 | Mortenson | Apr 2006 | A1 |
| 20060107195 | Ramaswamy et al. | May 2006 | A1 |
| 20060161635 | Lamkin et al. | Jul 2006 | A1 |
| 20060178996 | Matsushima et al. | Aug 2006 | A1 |
| 20060184617 | Nicholas et al. | Aug 2006 | A1 |
| 20060190616 | Mayerhofer et al. | Aug 2006 | A1 |
| 20060242325 | Ramaswamy et al. | Oct 2006 | A1 |
| 20060271641 | Stavrakos et al. | Nov 2006 | A1 |
| 20060294259 | Matefi et al. | Dec 2006 | A1 |
| 20070043769 | Kasahara et al. | Feb 2007 | A1 |
| 20070055987 | Lu et al. | Mar 2007 | A1 |
| 20070074020 | Nishimura | Mar 2007 | A1 |
| 20070083611 | Farago et al. | Apr 2007 | A1 |
| 20070094304 | Homer et al. | Apr 2007 | A1 |
| 20070106787 | Blumenau | May 2007 | A1 |
| 20070106792 | Blumenau | May 2007 | A1 |
| 20070112837 | Houh et al. | May 2007 | A1 |
| 20070118873 | Houh et al. | May 2007 | A1 |
| 20070136777 | Hasek et al. | Jun 2007 | A1 |
| 20070156532 | Nyhan et al. | Jul 2007 | A1 |
| 20070162927 | Ramaswamy et al. | Jul 2007 | A1 |
| 20070186228 | Ramaswamy et al. | Aug 2007 | A1 |
| 20070198327 | Yazdani et al. | Aug 2007 | A1 |
| 20070198353 | Behringer | Aug 2007 | A1 |
| 20070208711 | Rhoads et al. | Sep 2007 | A1 |
| 20070244985 | Svendsen | Oct 2007 | A1 |
| 20070250901 | McIntire et al. | Oct 2007 | A1 |
| 20070271580 | Tischer et al. | Nov 2007 | A1 |
| 20070276925 | La Joie et al. | Nov 2007 | A1 |
| 20070276926 | LaJoie et al. | Nov 2007 | A1 |
| 20070288476 | Flanagan, III et al. | Dec 2007 | A1 |
| 20070294057 | Crystal et al. | Dec 2007 | A1 |
| 20070294132 | Zhang et al. | Dec 2007 | A1 |
| 20070294705 | Gopalakrishnan et al. | Dec 2007 | A1 |
| 20070294706 | Neuhauser et al. | Dec 2007 | A1 |
| 20080004958 | Ralph et al. | Jan 2008 | A1 |
| 20080028223 | Rhoads | Jan 2008 | A1 |
| 20080040354 | Ray et al. | Feb 2008 | A1 |
| 20080046499 | Cabrera et al. | Feb 2008 | A1 |
| 20080059160 | Saunders et al. | Mar 2008 | A1 |
| 20080082510 | Wang et al. | Apr 2008 | A1 |
| 20080083003 | Biniak et al. | Apr 2008 | A1 |
| 20080086356 | Glassman et al. | Apr 2008 | A1 |
| 20080120661 | Ludvig et al. | May 2008 | A1 |
| 20080126420 | Wright et al. | May 2008 | A1 |
| 20080139182 | Levy et al. | Jun 2008 | A1 |
| 20080140573 | Levy et al. | Jun 2008 | A1 |
| 20080201427 | Chen | Aug 2008 | A1 |
| 20080201472 | Bistriceanu et al. | Aug 2008 | A1 |
| 20080209491 | Hasek | Aug 2008 | A1 |
| 20080235077 | Harkness et al. | Sep 2008 | A1 |
| 20080235243 | Lee et al. | Sep 2008 | A1 |
| 20080240490 | Finkelstein et al. | Oct 2008 | A1 |
| 20080249961 | Harkness et al. | Oct 2008 | A1 |
| 20080250136 | Izrailevsky | Oct 2008 | A1 |
| 20080276179 | Borenstein et al. | Nov 2008 | A1 |
| 20090015599 | Bennett et al. | Jan 2009 | 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 |
| 20090083417 | Hughes et al. | Mar 2009 | A1 |
| 20090106202 | Mizrahi | Apr 2009 | A1 |
| 20090119723 | Tinsman | May 2009 | A1 |
| 20090125934 | Jones et al. | May 2009 | A1 |
| 20090133093 | Hodge | May 2009 | A1 |
| 20090158318 | Levy | Jun 2009 | A1 |
| 20090164564 | Willis | Jun 2009 | A1 |
| 20090171715 | Conley | Jul 2009 | A1 |
| 20090171762 | Alkove et al. | Jul 2009 | A1 |
| 20090217315 | Malik et al. | Aug 2009 | A1 |
| 20090254633 | Olive | Oct 2009 | A1 |
| 20090276313 | Wilhelm | Nov 2009 | A1 |
| 20090307061 | Monighetti et al. | Dec 2009 | A1 |
| 20090307084 | Monighetti et al. | Dec 2009 | A1 |
| 20090327026 | Bistriceanu et al. | Dec 2009 | A1 |
| 20100004977 | Marci et al. | Jan 2010 | A1 |
| 20100008586 | Meyer et al. | Jan 2010 | A1 |
| 20100009722 | Levy et al. | Jan 2010 | A1 |
| 20100010866 | Bal et al. | Jan 2010 | A1 |
| 20100070621 | Urdan et al. | Mar 2010 | A1 |
| 20100076814 | Manning | Mar 2010 | A1 |
| 20100088152 | Bennett | Apr 2010 | A1 |
| 20100088373 | Pinkham | Apr 2010 | A1 |
| 20100088583 | Schachter | Apr 2010 | A1 |
| 20100094897 | Sumrall et al. | Apr 2010 | A1 |
| 20100114739 | Johnston | May 2010 | A1 |
| 20100121676 | Jackson | May 2010 | A1 |
| 20100125567 | Morris | May 2010 | A1 |
| 20100153175 | Pearson et al. | Jun 2010 | A1 |
| 20100153207 | Roberts et al. | Jun 2010 | A1 |
| 20100153544 | Krassner et al. | Jun 2010 | A1 |
| 20100174774 | Kern et al. | Jul 2010 | A1 |
| 20100191723 | Perez et al. | Jul 2010 | A1 |
| 20100198911 | Zhang | Aug 2010 | A1 |
| 20100205057 | Hook et al. | Aug 2010 | A1 |
| 20100241745 | Offen et al. | Sep 2010 | A1 |
| 20100241963 | Kulis et al. | Sep 2010 | A1 |
| 20100262498 | Nolet et al. | Oct 2010 | A1 |
| 20100262711 | Bouazizi | Oct 2010 | A1 |
| 20100268540 | Arshi et al. | Oct 2010 | A1 |
| 20100268573 | Jain et al. | Oct 2010 | A1 |
| 20100280641 | Harkness et al. | Nov 2010 | A1 |
| 20100299604 | Blumenau | Nov 2010 | A1 |
| 20100306257 | Levy | Dec 2010 | A1 |
| 20100312854 | Hyman | Dec 2010 | A1 |
| 20100318600 | Furbeck | Dec 2010 | A1 |
| 20100325051 | Etchegoyen | Dec 2010 | A1 |
| 20110016231 | Ramaswamy et al. | Jan 2011 | A1 |
| 20110016482 | Tidwell et al. | Jan 2011 | A1 |
| 20110030031 | Lussier et al. | Feb 2011 | A1 |
| 20110055314 | Rosenstein et al. | Mar 2011 | A1 |
| 20110087519 | Fordyce, III et al. | Apr 2011 | A1 |
| 20110087919 | Deshmukh 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 |
| 20110154185 | Kern et al. | Jun 2011 | A1 |
| 20110158016 | Rimondi et al. | Jun 2011 | A1 |
| 20110173200 | Yang et al. | Jul 2011 | A1 |
| 20110185016 | Kandasamy | Jul 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 |
| 20110238520 | Selley | Sep 2011 | A1 |
| 20110246297 | Buchalter et al. | Oct 2011 | A1 |
| 20110246306 | Blackhurst et al. | Oct 2011 | A1 |
| 20110246641 | Pugh et al. | Oct 2011 | A1 |
| 20110252118 | Pantos et al. | Oct 2011 | A1 |
| 20110276627 | Blechar | Nov 2011 | A1 |
| 20110288907 | Harvey et al. | Nov 2011 | A1 |
| 20110296048 | Knox | Dec 2011 | A1 |
| 20110321003 | Doig et al. | Dec 2011 | A1 |
| 20120005213 | Harman et al. | Jan 2012 | A1 |
| 20120030037 | Carriero | Feb 2012 | A1 |
| 20120042005 | Papakostas et al. | Feb 2012 | A1 |
| 20120072469 | Perez et al. | Mar 2012 | A1 |
| 20120096546 | Dilley et al. | Apr 2012 | A1 |
| 20120109709 | Fordyce, III et al. | May 2012 | A1 |
| 20120109882 | House 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 |
| 20120206331 | Gandhi | Aug 2012 | A1 |
| 20120209918 | Shah et al. | Aug 2012 | A1 |
| 20120215621 | Heffernan et al. | Aug 2012 | A1 |
| 20120221559 | Kidron | Aug 2012 | A1 |
| 20120239407 | Lynch et al. | Sep 2012 | A1 |
| 20120239809 | Mazumdar | Sep 2012 | A1 |
| 20120254466 | Jungck | Oct 2012 | A1 |
| 20120265735 | McMillan et al. | Oct 2012 | A1 |
| 20120302222 | Williamson et al. | Nov 2012 | A1 |
| 20120310729 | Dalto et al. | Dec 2012 | A1 |
| 20120311017 | Sze et al. | Dec 2012 | A1 |
| 20120311126 | Jadallah et al. | Dec 2012 | A1 |
| 20130007298 | Ramaswamy | Jan 2013 | A1 |
| 20130007794 | Besehanic et al. | Jan 2013 | A1 |
| 20130014144 | Bhatia et al. | Jan 2013 | A1 |
| 20130014223 | Bhatia et al. | Jan 2013 | A1 |
| 20130019262 | Bhatia et al. | Jan 2013 | A1 |
| 20130046615 | Liyanage | Feb 2013 | A1 |
| 20130060629 | Rangsikitpho et al. | Mar 2013 | A1 |
| 20130061275 | Seo et al. | Mar 2013 | A1 |
| 20130080268 | Gordon et al. | Mar 2013 | A1 |
| 20130097285 | van Zwol et al. | Apr 2013 | A1 |
| 20130097311 | Mazumdar et al. | Apr 2013 | A1 |
| 20130097312 | Mazumdar et al. | Apr 2013 | A1 |
| 20130124628 | Weersinghe | May 2013 | A1 |
| 20130138506 | Zhu et al. | May 2013 | A1 |
| 20130138743 | Amento et al. | May 2013 | A1 |
| 20130145022 | Srivastava et al. | Jun 2013 | A1 |
| 20130159499 | Besehanic | Jun 2013 | A1 |
| 20130198125 | Oliver et al. | Aug 2013 | A1 |
| 20130198383 | Tseng et al. | Aug 2013 | A1 |
| 20130202150 | Sinha et al. | Aug 2013 | A1 |
| 20130212188 | Duterque et al. | Aug 2013 | A1 |
| 20130231931 | Kulis et al. | Sep 2013 | A1 |
| 20130246389 | Osann, Jr. | Sep 2013 | A1 |
| 20130246609 | Topchy et al. | Sep 2013 | A1 |
| 20130247078 | Nikankin et al. | Sep 2013 | A1 |
| 20130254897 | Reedy et al. | Sep 2013 | A1 |
| 20130268623 | Besehanic et al. | Oct 2013 | A1 |
| 20130268630 | Besehanic et al. | Oct 2013 | A1 |
| 20130282898 | Kalus et al. | Oct 2013 | A1 |
| 20130290508 | Besehanic et al. | Oct 2013 | A1 |
| 20130291001 | Besehanic et al. | Oct 2013 | A1 |
| 20130297411 | van Datta et al. | Nov 2013 | A1 |
| 20130297467 | Kidron et al. | Nov 2013 | A1 |
| 20130304777 | Bilinski | Nov 2013 | A1 |
| 20130311478 | Frett | Nov 2013 | A1 |
| 20130311776 | Besehanic | Nov 2013 | A1 |
| 20130311780 | Besehanic | Nov 2013 | A1 |
| 20130332604 | Seth et al. | Dec 2013 | A1 |
| 20140033317 | Barber | Jan 2014 | A1 |
| 20140040171 | Segalov et al. | Feb 2014 | A1 |
| 20140046777 | Markey | Feb 2014 | A1 |
| 20140082220 | Ramaswamy et al. | Mar 2014 | A1 |
| 20140123253 | Davis et al. | May 2014 | A1 |
| 20140156761 | Heffernan et al. | Jun 2014 | A1 |
| 20140173746 | Armstrong-Muntner et al. | Jun 2014 | A1 |
| 20140229629 | Besehanic | Aug 2014 | A1 |
| 20140229970 | Besehanic | Aug 2014 | A1 |
| 20140244828 | Besehanic | Aug 2014 | A1 |
| 20140280896 | Papakostas et al. | Sep 2014 | A1 |
| 20140298365 | Matsubara et al. | Oct 2014 | A1 |
| 20140301386 | Harrenstien et al. | Oct 2014 | A1 |
| 20140324544 | Donato et al. | Oct 2014 | A1 |
| 20140324545 | Splaine et al. | Oct 2014 | A1 |
| 20140337104 | Splaine et al. | Nov 2014 | A1 |
| 20150019322 | Alla et al. | Jan 2015 | A1 |
| 20150019327 | Mazumdar et al. | Jan 2015 | A1 |
| 20150046248 | Ben-Yaacov et al. | Feb 2015 | A1 |
| 20150046579 | Perez et al. | Feb 2015 | A1 |
| 20150052217 | Benguerah | Feb 2015 | A1 |
| 20150070585 | Sharif-Ahmadi et al. | Mar 2015 | A1 |
| 20150106505 | Ramaswamy | Apr 2015 | A1 |
| 20160212481 | Ramaswamy et al. | Jul 2016 | A1 |
| Number | Date | Country |
|---|---|---|
| 2013205736 | May 2013 | AU |
| 2014331927 | Oct 2014 | AU |
| 1898662 | Jan 2007 | CN |
| 101077014 | Nov 2007 | CN |
| 103189856 | Jul 2013 | CN |
| 105814901 | Jul 2016 | CN |
| 0325219 | Jul 1989 | EP |
| 0703683 | Mar 1996 | EP |
| 2176639 | Dec 1986 | GB |
| 1227592 | Aug 2020 | HK |
| H05324352 | Dec 1993 | JP |
| 2000041115 | Feb 2000 | JP |
| 2001282982 | Oct 2001 | JP |
| 2002163562 | Jun 2002 | JP |
| 2002373152 | Dec 2002 | JP |
| 2006127320 | May 2006 | JP |
| 2006127321 | May 2006 | JP |
| 2010039845 | Feb 2010 | JP |
| 2010104285 | Sep 2010 | JP |
| 2010282319 | Dec 2010 | JP |
| 2013524319 | Jun 2013 | JP |
| 20020037980 | May 2002 | 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 |
| 0041115 | Jul 2000 | WO |
| 2005013072 | Feb 2005 | WO |
| 2010088372 | Aug 2010 | WO |
| 2011097624 | Aug 2011 | WO |
| 2012040371 | Mar 2012 | WO |
| 2012087954 | Jun 2012 | WO |
| 2012128895 | Sep 2012 | WO |
| 2012177866 | Dec 2012 | WO |
| 2012177870 | Dec 2012 | WO |
| 2012177874 | Dec 2012 | WO |
| 2013122907 | Aug 2013 | WO |
| 2014172472 | Oct 2014 | WO |
| 2015054445 | Apr 2015 | WO |
| Entry |
|---|
| European Patent Office, “Extended European Search Report”, issued in connection with European Patent Application No. 22155005.6 dated Jul. 6, 2022, 8 pages. |
| “ID3”, published on Wikipedia, on Apr. 16, 2015, from en.wikipedia.org/wiki/ID3, 15 pages. |
| “Software development kit”, published on Wikipedia, on Apr. 16, 2015, from en.wikipedia.org/wiki/Software_development_kit, 2 pages. |
| “Video: timed text tracks”, published by Windows Internet Explorer, Microsoft, 2012, from http://msdn.microsoft.com/en-us/library/ie/hh673566(v=vs.85).aspx, 6 pages. |
| Adam, et al., “Privacy Preserving Integration of Health Care Data,” published by AMIA, 2007 Symposium Proceedings, 6 pages. |
| Apple Inc. “HTTP Live Streaming Overview”, Apr. 1, 2011, 36 pages. |
| Apple Inc. “Timed Metadata for HTTP Live Streaming”, Apr. 28, 2011, 12 pages. |
| Buyya, et al., “Cloudbus Toolkit for Market-Oriented Cloud Computing”, published by CloudCom 2009, LNCS 5931, Springer-Verlag, Berlin, Germany,© 2009, 21 pages. |
| Albanesius, “Facebook Issues Fix for Several Tracking Cookies”, published by PC Magazine, on Sep. 28, 2011, from www.pcmag.com, 2 pages. |
| Dhillon, et al., “Leveraging Consumer Sensing Devices for Telehealth”, published in Chinz '12, Dunedin, New Zealand, on Jul. 2-3, 2012, 7 pages. |
| Protalinski, “Facebook denies cookie tracking allegations”, from www.zdnet.com, on Sep. 25, 2011, 2 pages. |
| Protalinski, “Facebook fixes cookie behavior after logging out”, from www.zdnet.com, on Sep. 27, 2011, 2 pages. |
| Protalinski, “US congressmen ask FTC to investigate Facebook cookies”, from www.zdnet.com, on Sep. 28, 2011, 2 pages. |
| Winkelman, “Timed Text Tracks and TV Services”, published by CableLabs, on Aug. 15, 2011, 5 pages. |
| Evensen, et al., “AdScorer: An Event-Based System for Near Real-Time Impact Analysis of Television Advertisements”, published by DEBS '12, Berlin, Germany, on Jul. 16-20, 2012, 22 pages. |
| “Fliptop Person API Documentation”, published by Fliptop, on May 7, 2013, from https://developer.fliptop.com/documentation, 6 pages. |
| “Get, Keep and Grow Customers with Fliptop's Customer Intelligence Application”, published by Fliptop, on May 7, 2013, from www.fliptop.com/features#social matching, 3 pages. |
| “What is Fliptop?”, published by Fliptop, on May 7, 2013, from www.fliptop.com/about us, 1 page. |
| International Searching Authority, “International Search Report &Written Opinion”, issued in International Patent Application No. PCT/US2014/034389, dated Sep. 5, 2014, 15 pages. |
| IP Australia, “Examination Report”, issued in connection with Australian Patent Application No. 2014254014, dated Jun. 17, 2015, 3 pages. |
| “JavaScript and AJAX Forum”, from http://www.webmasterworld.com/ forum91/4465.him, on Jun. 29, 2011, 4 pages. |
| Launder, “Media Journal: Nielsen to Test Online-TV Viewing Tool,” published in The Wall Street Journal, on Apr. 30, 2013, 2 pages. |
| Liu, et al., “Socialize Spontaneously with Mobile Applications”, published in INFOCOM 2012, Orlando, FL, on Mar. 25-30, 2012, 9 pages. |
| “Mental Poker”, published on Wikipedia, on Sep. 21, 2010, from http://en.wikipedia.org/wiki/Mental_poker, 5 pages. |
| “Nielsen Unveils New Online Advertising Measurement”, The Nielsen Company, on May 31, 2012, from http://nielsen.com/us/en/insights/press-room/201O/nielsen_unveils_newonlineadvertisingmeasurement.html, 3 pages. |
| Cubrilovic, “Logging out of Facebook is not enough”, published by New Web Order, on Sep. 25, 2011, from www.nikcub.appspot.com, 3 pages. |
| Pantos, et al., “HTTP Live Streaming: draft-pantos-http-live-streaming-07”, published by Apple Inc., on Sep. 30, 2011, 33 pages. |
| Rainier, “Why Businesses Should Use Google Plus”, published by The Social Media Guide, on May 7, 2013, fromthesocialmediaguide.com/social_media/why-businesses-should-use-google-plus, 9 pages. |
| “Fast. Simple. Secure”, published on Rapleaf, on May 7, 2013, from www.rapleaf.com/why-rapleaf/, 3 pages. |
| “Frequently Asked Questions”, published on Rapleaf, on May 7, 2013, from www.rapleaf.com/about-us/faq/#where, 3 pages. |
| “The Consumer Data Marketplace”, published on Rapleaf, on May 7, 2013, from www.rapleaf.com/under-the-hood/, 2 pages. |
| Sharma, “Nielsen Gets Digital to Track Online TV Viewers”, published by Wall Street Journal, on Apr. 30, 2013, 3 pages. |
| Coffey, “Internet Audience Measurement: A Practitioner's View”, published by Journal of Interactive Advertising, vol. 1, No. 2, on Spring 2001, 8 pages. |
| Vega, “Nielsen Introduces New Ad Measurement Product”, published by The New York Times, on Sep. 27, 2010, 7 pages. |
| Vranica, “Nielsen Testing a New Web-Ad Metric”, published by The Wall Street Journal, on Sep. 23, 2010, 2 pages. |
| Whiting, et al., “Creating an I Phone Application for Collecting Continuous ABC Data”, published by Journal of Applied Behavior Analysis, vol. 45, No. 3, on Fall 2012, 14 pages. |
| Japanese Patent Office, “Office Action”, issued in connection with Application No. 2015-525656, on Dec. 1, 2015, 6 pages. |
| International Searching Authority, “International Search Report and Written Opinion”, issued in connection with International Application No. PCT/US2014/059809, dated Jan. 13, 2015, 12 pages. |
| Korean Intellectual Property Office, “Notice of Preliminary Rejection”, issued in connection with Application 10-2014-7034045, dated Mar. 22, 2016, 7 pages. |
| United States Patent Office, “Non-Final Office Action”, issued in connection with U.S. Appl. No. 13/963,737, dated May 17, 2016, 15 pages. |
| United States Patent Office, “Notice of Allowance”, issued in connection with U.S. Appl. No. 14/144,352, dated Dec. 23, 2015, 16 pages. |
| European Patent Office, “Extended European Search Report”, issued in connection with European Patent Application No. 14851645.3-1908, dated Mar. 31, 2017, 11 pages. |
| Nilsson, “ID3 tag version 2.3.0”, published on Feb. 3, 1999, from http://www.id3.org/id3v2.3.0.txt, 35 pages. |
| IP Australia, “Examination report No. 1”, issued in connection with Australian Application No. 2014331927, dated Mar. 28, 2017, 2 pages. |
| IP Australia, “Notice of grant for patent”, issued in connection with Australian Application No. 2014331927, dated Oct. 5, 2017, 1 pages. |
| IP Australia, “Certificate of Grant”, issued in connection with Australian Application No. 2014331927, dated Oct. 5, 2017, 1 pages. |
| IP Australia, “Notice of acceptance”, issued in connection with Australian Application No. 2014331927, dated Jun. 9, 2017, 3 pages. |
| United States Patent Office, “Notice of Allowance and Fee(s) Due”, issued in connection with U.S. Appl. No. 15/082,991, dated Jul. 14, 2016, 30 pages. |
| The State Intellectual Property Office of China, “First Notification of Office Action”, dated May 28, 2018 in relation to application No. 201480065971.2, 11 pages (including English translation). |
| United States Patent and Trademark Office, “Non-Final Office Action,” issued in connection with U.S. Appl. No. 15/299,884, dated Jul. 16, 2018, 5 pages. |
| United States Patent and Trademark Office, “Notice of Allowance,” issued in connection with U.S. Appl. No. 15/299,884, dated Jan. 24, 2019, 5 pages. |
| European Patent Office, “Examination Report,” issued in connection with European Patent Application No. 14851645.3-1208, dated May 8, 2019, 6 pages. |
| European Patent Office, “Communication pursuant to Article 94(3) EPC,” issued in connection with European Patent Application No. 14851645.3, dated Mar. 17, 2020, 6 pages. |
| United States Patent and Trademark Office, “Non-Final Office Action,” issued in connection with U.S. Appl. No. 16/436,476, dated Oct. 4, 2019, 7 pages. |
| United States Patent and Trademark Office, “Notice of Allowance and Fee(s),” issued in connection with U.S. Appl. No. 16/436,476, dated Feb. 10, 2020, 8 pages. |
| European Patent Office, “Summons to attend oral proceedings pursuant to Rule 115(1) EPC,” issued in connection with European Patent Application No. 14 851 645.3 dated Feb. 23, 2021, 8 pages. |
| European Patent Office, “Communcation under Rule 71(3) EPC,” issued in connection with European Patent Application No. 14 851 645.3 dated Sep. 9, 2021, 7 pages. |
| United States Patent and Trademark Office, “Notice of Allowance,” issued in connection with U.S. Appl. No. 16/902,065, dated Aug. 3, 2021, 8 pages. |
| China National Intellectual Property Administration, “Office Action”, issued in connection with CN Patent Application No. 201910227898.9 dated Oct. 24, 2022, 20 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20220086512 A1 | Mar 2022 | US |
| Number | Date | Country | |
|---|---|---|---|
| 61890176 | Oct 2013 | US | |
| 61889505 | Oct 2013 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16902065 | Jun 2020 | US |
| Child | 17456538 | US | |
| Parent | 16436476 | Jun 2019 | US |
| Child | 16902065 | US | |
| Parent | 15299884 | Oct 2016 | US |
| Child | 16436476 | US | |
| Parent | 15082991 | Mar 2016 | US |
| Child | 15299884 | US | |
| Parent | 14144352 | Dec 2013 | US |
| Child | 15082991 | US |
