The following relates to electronic content delivery and more specifically relates to systems and methods for audience targeting based on a performance history of invitational content, such as advertisements.
Computer applications, websites, or other electronic content including offers for products and services generally require a user to explicitly select and/or interact with one or more portions of the content being presented to generate a conversion (e.g., completion a sale or purchase, submission of information to a content provider, causing delivery of additional information to the user or any other pre-defined response for the content). For example, an advertisement for a product or service can require the user to select the advertisement content and navigate to the online store offering the product for sale. At the online store, the user can then enter information to purchase or obtain additional information regarding the product or service.
In many types of electronic content maintained by (primary) content providers, invitational content (i.e., the portions of the content offering products and services) is generally provided other (secondary) content providers. That is, primary content providers typically offer portions for inserting such invitational content, directly or via an agent, for use by one or more other secondary content providers. Accordingly, the invitational content in these portions varies over time, depending on the various arrangements between the primary content provider and the various secondary content providers. For example, each of the secondary content providers may arrange for a number of impressions of their invitational content. Further, secondary content providers may also arrange to have their invitational content associated only with a particular context.
The present technology provides systems and methods for audience targeting based on a performance history of invitational content from secondary content providers, such as advertisements. In operation, responsive to request from a user for content package associated with a context, a queue of invitational content is retrieved. Such a queue can be, for example, the queue established according to the predefined arrangement between a primary content provider and a group of secondary content providers. This queue is then adjusted to generate an adjusted queue for requesting user. The invitational content for content package can then be selected based on this adjusted queue. In some embodiments, a premium pricing or bidding process can be used to select the invitational content.
The adjusted queue can be generated by applying queue adjustment factors to adjust the positions of the invitational content in the queue. In particular, at least one of overall rank scores, content rank scores, and covariance scores can be computed and combined to generate the queue adjustment factors. These factors can then be used to adjust a position of invitational content in the retrieved queue. In some cases, the queue adjustment factors consist of weighted or un-weighted sums of these scores.
In the present technology, the overall rank scores specify an overall performance of the invitational content in the queue with respect to other invitational content previously presented to users. Effectively, the overall rank scores specify an overall performance of users' responsiveness in regards to the invitational content in the queue, based on a correlation between the behavior of all users and the requesting user with respect to previously presented invitational content. The content rank scores specify a performance of the invitational content in the queue, in the context of the request, with respect to other invitational content previously presented to users. The covariance scores specify an interest in the invitational content in the queue, based on a correlation between the behavior of all users and the requesting user with respect to previously presented invitational content.
Various embodiments of the disclosed methods and arrangements are discussed in detail below. While specific implementations are discussed, it should be understood that this is done for illustration purposes only. A person skilled in the relevant art will recognize that other components, configurations, and steps may be used without parting from the spirit and scope of the disclosure.
With reference to
Although the exemplary environment described herein employs a hard disk, it should be appreciated by those skilled in the art that other types of computer readable media which can store data that is accessible by a computer, such as magnetic cassettes, flash memory cards, digital versatile disks, cartridges, random access memories (RAMs), read only memory (ROM), a cable or wireless signal containing a bit stream and the like, may also be used in the exemplary operating environment.
To enable user interaction with the computing device 100, an input device 190 represents any number of input mechanisms, such as a microphone for speech, a touch-sensitive screen for gesture or graphical input, keyboard, mouse, motion input, speech and so forth. The device output 170 can also be one or more of a number of output mechanisms known to those of skill in the art. For example, video output or audio output devices which can be connected to or can include displays or speakers are common. Additionally, the video output and audio output devices can also include specialized processors for enhanced performance of these specialized functions. In some instances, multimodal systems enable a user to provide multiple types of input to communicate with the computing device 100. The communications interface 180 generally governs and manages the user input and system output. There is no restriction on the disclosed methods and devices operating on any particular hardware arrangement and therefore the basic features may easily be substituted for improved hardware or firmware arrangements as they are developed.
For clarity of explanation, the illustrative system embodiment is presented as including individual functional blocks (including functional blocks labeled as a “processor”). The functions these blocks represent may be provided through the use of either shared or dedicated hardware, including, but not limited to, hardware capable of executing software. For example the functions of one or more processors presented in
The logical operations of the various embodiments are implemented as: (1) a sequence of computer implemented steps, operations, or procedures running on a programmable circuit within a general use computer, (2) a sequence of computer implemented steps, operations, or procedures running on a specific-use programmable circuit; and/or (3) interconnected machine modules or program engines within the programmable circuits.
The present system and method is particularly useful for assembling and delivering content packages to the user terminals, where an invitational content from secondary content providers, such as advertisements, announcements, and other types of propaganda and inducements, is selected for the content package is based on past user interactions with invitational content. A system 200 is illustrated in
In system 200, a content package is delivered to user terminals 2021 . . . 202n (collectively “202”) connected to a network 204 by direct and/or indirect communications with a content delivery system 206. In particular, the content delivery system 206 receives a request for an electronic content, such as a web page, from one of user terminals 202. Thereafter, the content delivery system 206 assembles a content package in response to the request and transmits the assembled content package to the requesting one of user terminals 202. The content in the assembled content package can include text, graphics, audio, video, or any combination thereof. Further, the assembled content packages can includes invitational content designed to inform or elicit a pre-defined response from the user and that can vary over time, such as advertisements. The content delivery system can include a communications interface 207 to facilitate communications with the user terminals 202 and any other components in system 200.
The content delivery system 206 includes a content management module 208 that facilitates generation of the assembled content package that includes invitational content. Specifically, the content management module can combine content from one or more one or more primary content providers 2101 . . . 210n (collectively “210”) and content from one or more secondary content providers 2141 . . . 214n (collectively “214”) to generate the assembled content package for the user terminals 202.
Although, primary and secondary providers 210, 214 are presented herein as discrete, separate entities, this is for illustrative purposes only. In some cases, the primary and secondary providers 210, 214 can be the same entity. Thus, a single entity may define and provide both static and time-varying content.
For example, in the case of a web page being delivered to a requesting one of user terminals 202, the content management module 208 can assemble a content package by requesting the data for the web page from one of the primary content providers 210 maintaining the web page. For the time-varying invitational content on the web page provided by the secondary content providers 214, the content management module 208 can request the appropriate data generally according to the arrangement between the primary and secondary content providers 210 and 214. For example, the invitational content from the secondary providers 214 can be selected based on a guaranteed number of impressions. Alternatively, the invitational content from the secondary providers 214 can also be selected based on the context of the web page. However, any other arrangements and configuration for selecting invitational content from the secondary providers 210 can also be used.
Although the content management module 208 can be configured to request that data be sent directly from content providers 210 and 214, a cached arrangement can also be used to improve performance of the content delivery system 206 and improve overall user experience. That is, the content delivery system 206 can include a content database 212 for locally storing/caching content maintained by content providers 210 and 214. The data in the content database 212 can be refreshed or updated on a regular basis to ensure that the content in the database 212 is up to date at the time of a request from a user terminal. However, in some cases, the content management module 208 can be configured to retrieve data directly from content providers 210 and 214 if the metadata associated with the data in content database 212 appears to be outdated or corrupted.
In the various embodiments, the one or more databases described herein can be implemented any type of data structures. Such data structures include, but are not limited to data structures for relational databases, key/value stores, graph databases, hierarchical databases, and distributed or columnar stores. Accordingly, although the various embodiments described herein may refer to specific data structures in some embodiments, in other embodiments such data structures can be substituted for any other type of database structure.
In the various embodiments, the content delivery 206 can also include a unique user identifier (UUID) database 215 that can be used for managing sessions with the various user terminal devices 202. The UUID database 215 can be used with a variety of session management techniques. For example, the content delivery system 206 can implement an HTTP cookie or other conventional session management methods (e.g., IP address tracking, URL query strings, hidden form fields, window name tracking, authentication methods, and local shared objects) for user terminals 202 connected to content delivery system 206 via a substantially persistent network session. However, other methods can be used as well. For example, in the case of mobile devices or other types of user terminals connecting using multiple or non-persistent network sessions, multiple requests for content from such devices may be assigned to a same entry in the UUID database 215. Such an assignment can be provided by analyzing requesting device attributes in order to determine whether such requests can be attribute to a same device. Such attributes can include device or group-specific attributes.
As described above, content maintained by the content providers 210 and 214 can be combined and/or presented according a predefined arrangement between the two content providers, which can be embodied as a set of rules. In an arrangement where the content delivery system assembles the content package from multiple content providers, these rules can be stored in a rules database 216 in content delivery system 206 and content management module 208 can be configured to assemble the content package for user terminals 202 based on these rules. The rules can specify how to select content from secondary content providers 214 and the primary content providers 210 in response to a request from one of user terminals 202. For example, in the case of a web page maintained by one of primary providers 210 and including variable advertisement portions, the rules database 216 can specify rules for selecting one of the secondary providers 214. The rules can also specify how to select specific content from the selected one of secondary providers 214 to be combined with the content provided by one of primary providers 210. Once assembled, the assembled content package can be sent to a requesting one of user terminals. However, the content package is not limited to the content from content providers 210 and 214. Rather, the content package can include other data generated at the content delivery system 206.
As described above, arrangements between the content providers 210 and 214 can result in content from one of primary content providers 210 being combined with invitational content from multiple ones of secondary content providers 214, based on the rules database 216. Although the rules database 216 can be accessed each time a request is received from one of user terminals 202, such a configuration can limit performance. Therefore, in many cases, the rules in rules database 216 are used to define at least one queue of invitational content from the secondary providers 214. Thus, when a content package is being assembled by the content management module 208, the content management module 208 first constructs and/or retrieves the queue. Thereafter, the content management module 208 can select an invitational content from one of the secondary content providers according to the queue and form the assembled content package. For example, in one configuration, an invitational content at the top of the queue can be selected. In another configuration, an invitational content associated with a set of contextual characteristics and that is highest positioned in the queue can be selected.
As used herein, the term “contextual characteristics” refers to the characteristics of a particular audience in the network 204 associated with one or more of user terminals 202. Contextual characteristics can include channel characteristics, demographic characteristics, behavioral characteristics, and spatial-temporal characteristics. Channel characteristics can define the specific delivery channel being used to deliver a content package. For example, channel characteristics can include a type of electronic content, a type of device or user terminal, a carrier or network provider, or any other characteristic that defines a specific delivery channel for the content package. Spatial-temporal characteristics can define a location, a date, a time, or any other characteristic that defines a geographic location and/or a time for delivery of the content package. Demographic characteristics can define personal and/or socio-economic characteristics of the user requesting the content package. Behavioral characteristics can define user behaviors for one or more different types of content, separately or in combination with any other contextual characteristics. That is, different behavioral characteristics may be associated with different channel, demographic, or spatial temporal characteristics. For example, users may be associated with higher conversion or response rates for some types of delivery channels.
One concern with the arrangements typically entered into by secondary content providers 214 is that they can result in invitational content of little or no interest being presented to users at many times. As a result, even though a desired number of impressions can be achieved, the rate of response to such invitational content may be low and/or the resulting targeted audience may be incorrect or suboptimal. As a result, content providers 210 and 214 can be negatively impacted. For example, if the primary content providers 210 receive compensation based a number or rate of conversions of advertisements provided by secondary content providers 214, the resulting low conversion rate will result in lower revenues for the primary content providers 210. At the same time, the lower number or rate of conversions of advertisements can result in lower exposure or sales for the secondary content provider 214. In the case of an arrangement based on the number of impressions, the primary content provider 210 would be compensated, but the lower number or rate of conversions of advertisements can result in lower exposure or sales for the secondary content provider 214, as described above. As a result, such secondary content providers 214 may opt to pursue relationships with other primary content providers 210, resulting in potential loss of revenues for primary content providers 210.
The various embodiments therefore provide systems and methods for improving audience targeting by managing the presentation of invitational content from such secondary content providers 214. In particular, systems and methods are provided for adjusting a queue of invitational content at content delivery system 206 in order to provide invitational content at a user terminal that is of greater interest to an associated user. As a result, improved targeting of users is provided, which generally correlates to an increase in desired responses or conversions. In the various embodiments, the positions of invitational content in the queue are adjusted based on the performance history of previously invitational content. As a result, an adjusted queue is generated in which invitational content that is likely of greater interest to the requesting user or is more likely to elicit a response from the requesting user is pushed towards the top.
In operation, system 200 can provide a queue processing module 222 for providing such an adjustment of the queue. In operation, a queue processing module 222 receives the queue, a context associated with the request, and identifying information for the user associated with the request. For example, such information can be received from the content management module 208 or other components in system 200. Thereafter, the queue processing module can access a performance history database 224 to retrieve a performance history of previously presented invitational content and adjust the queue accordingly. The updated queue can then be provided, for example, to the content management module 208, which can thereafter assemble and deliver a content package to the requesting user terminal. Such a method is described in greater detail below with respect to
In the various embodiments, the performance history database 224 can be updated using a performance history update module 226. In some cases, the performance history update module 226 can be configured to add additional history data to the history database 224. However, in other cases, an extended history of user interactions with invitational content may not accurately reflect a current interest of users. Accordingly, update module 226 can also be configured to maintain the history database 224 to include only more recently acquired data. For example, the update module 226 can be configured to maintain in the history database 224 to include only data from the last two to three months. However, the update module 226 can be configured to adjust the data in history database 224 to cover any span of time.
After the request is received at step 304, a user associated with the user terminal is identified at step 306. This identification can be performed in a variety of ways. For example, as described above, the request can include some identifying information, associated with the requesting user terminal or the associated user, which can then be correlated to an entry in the UUID database 215 to retrieve an identity of the user. In other configurations, the user can be identified based analyzing requesting device attributes in order to determine whether such requests can be attribute to a same device, also as described above. Other methods can also be used.
Together or separately with step 306, a context for the content package can be determined by the content management module 208. Thereafter, based on the context identified at step 308, a queue of available invitational content from secondary providers 214 can be obtained at step 310. For example, as described above, a queue can be constructed from the rules database 216 by the content management module 208. However, in some embodiments, the queue can be generated a priori for specific contexts. For example, for specific devices, electronic content from a particular network location, or other known or common contexts, the queue can be generated beforehand and stored. Thereafter, the content management module 208 can access the queue as needed.
Once the queue is obtained at step 310, a user-specific queue can be generated and used for assembling a content package for the user starting at step 312. At step 312, queue adjustment factors can be calculated for the invitational content in the queue. The queue adjustment factors can specify a value for adjusting a position of an invitational content in the queue. In some cases, the queue adjustment factor can specify an absolute amount of change in position in the queue. For example, the queue adjustment factor can specify a minimum number of positions that a secondary content should be moved up or down in the queue. In other cases, the queue adjustment factor can specify a relative position or portion of the queue to which an invitational content should be moved. For example, the queue adjustment factor can specify that a particular invitational content should be moved to the top or bottom of the queue. In yet another example, the queue adjustment factor can be used to categorize the invitational content in the queue into one a plurality of queue groups, each with different priority or positions in the adjusted queue. Thereafter, the invitational content in these groups can be ordered according to the relative order they had in the original queue or using a different order based on other factors.
In the various embodiments, the queue adjustment factor for invitational content is calculated based on at least one of an overall rank score, a context rank score, and covariance score for the invitational content. The overall rank score is a score related to the likelihood of the invitational content resulting in a conversion as compared to other invitational content, irrespective of other factors. Thus, the overall rank score is provided by constructing a model or table of values that correlates performance of previously presented invitational content to specific scores in a range. For example, the previously presented invitational content in the performance history database 224 can be arranged in a table according to the increasing number or rate of responses or conversions in the performance history. Thereafter, increasingly larger scores can be associated with the ordered entries in the table. An overall rank score for an invitational content of interest can then be obtained by a lookup operation to retrieve an associated score. In another example, a model or lookup table can be generated that associates different score values to different numbers or rates of responses or conversions. Thus, the overall rank score can be obtained by retrieving a performance history of an invitational content of interest to obtain some measure of the relative number or rate of conversions or responses for the invitational content as compared to other invitational content in the performance history. Such a measure can be a total number of responses, conversions, and/or impressions. This total number can then be used to retrieve or compute the overall rank score from the model or lookup table.
The context rank score is a score related to the likelihood of an invitational content resulting in a conversion as compared to other invitational content. Specifically, the content rank score is related to the likelihood of conversion for particular contexts. In some cases, the content rank scores can be separated by behavioral contextual characteristics. For example, a content rank score can be related to the likelihood of conversion with respect to a group of users generally associated with high or low conversion rates. In another example, the content rank score can be related the likelihood of conversion with respect to a group of users generally associated with high or low conversion rates for a specific context.
Thus, the context rank score can be provided by constructing a model or table of values that correlates performance of invitational content, previously presented in a particular context and/or presented to specific groups of users, to specific scores in a range. For example, the previously presented invitational content in the performance history database 224 can be arranged in a table according to the increasing number or rate of responses or conversions in the performance history for a particular context and/or group of users. Thereafter, increasingly larger scores can be associated with the ordered entries in the table. Thus, the context rank score can be obtained by looking up the invitational content of interest in the table and retrieving the associated score. In another example, a model or lookup tables can be generated that associates different score values for different numbers or rates of responses or conversions, depending on the context and/or group of users. Thus, the context rank score can be obtained by retrieving a performance history of an invitational content of interest to obtain some measure of the relative number or rate of conversions or responses for the invitational content as compared to other invitational content. Such a measure can be a total number of responses, conversions, and/or impressions. This total number can then be used to retrieve or compute the context rank score from the model or lookup table.
The covariance score is a score related to the likelihood of an invitational content resulting in at conversion when presented to user based on the performance of invitational content previously presented to the user and other users. More generally, the covariance score can be used to identify invitational content which may be of interest to the user. The covariance score is provided by first generating a covariance matrix that indicates the overall relationship or covariance between different invitational content previously presented to all users based on the performance history. Thereafter, the performance history associated with the requesting user is used to perform lookups against the covariance matrix to determine the covariance score.
For example, the performance history for the requesting user can be analyzed to determine invitational content associated with a response or conversion. Thereafter, if the covariance matrix indicates that there is a strong relationship between an invitational content in the queue and invitational content previously presented to the requesting user and resulting in a response or conversion, a high score can be provided. In contrast, if the covariance matrix indicates that there is a weaker or no relationship between an invitational content in the queue and invitational content previously presented to the requesting user and resulting in a response or conversion, a lower score can be provided. For example, in one configuration, the covariance values for the invitational content in the user performance history can be combined to estimate an overall covariance with the invitational content of interest. Thereafter, based on a model or table, a covariance score can be generated.
In another example, the covariance matrix can be analyzed to determine previously presented content strongly associated with the invitational content in the queue. Thereafter, the performance history for the requesting user can be analyzed to determine whether the requesting user also converted or otherwise responded to such previously presented content. If the requesting user generally converted or responded to such previously presented content, a higher score can be provided. In contrast, if the requesting user generally failed to convert or respond to such previously presented content, a low score can be provided. For example, a score can be generated on the proportion of responses or conversions or any other measure of the requesting user's response to the previously presented invitational content associated with invitational content in queue.
Once the scores described above are computed, these scores can be combined to obtain the queue adjustment factors. In the various embodiments, these scores can be combined in a variety of ways. For example, weights can be defined for each of the scores and the weighted sum of the scores can be used to obtain the queue adjustment factor for an invitational content of interest. In another example, an un-weighted sum (i.e., no weights or weights equal to 1) of these scores can be used to obtain the queue adjustment factors.
In some embodiments, one or more of the scores can be excluded for the queue adjustment factor based on the goal for the invitational content. For example, some advertisers may be more interested in delivering impressions than obtaining conversions for their advertisements. Therefore, content and context rank scores may be irrelevant with respect to determining the basic interest of the user in the products or services being advertised. Accordingly, the queue adjustment factor can be based simply on the covariance score. Accordingly, such a queue adjustment factor is indicative of the basic interest of the user in the goods in services in the advertisement, based on the user's past performance and the relationship with different invitational content.
Referring back to
In the systems and methods and methods described above, the queue processing module 222, the history database 224, and the update module 226 are shown to be incorporated into content delivery system 206, as shown in
During, before, and after such processes, the content delivery system 206 can be configured to forward raw performance history data to the queue reordering system 400. Such a process can occur as a continuous background process, allowing the update module 226 to continuously update the history database 224. Alternatively, the update module 226 can request the raw data as needed or according to a pre-defined schedule. Further, although the update module 226 and the history database 224 are shown as being incorporated in to system 400, these components can be deployed in separate systems as queue processing module 222.
As shown above, the systems and method described herein provide a means for delivering targeted invitational content to requesting users. However, the reverse occurs. That is, the systems and methods described herein also provide an identification of an audience for specific types of invitational content. That is, the systems and methods described herein are essentially generating leads and identifying potential customers for the goods and services. Accordingly, a bidding or premium pricing process can be used in conjunction with the various method described above to generate additional revenues for an operator of a content delivery system. Accordingly, referring back to
Alternatively, the engine 228 can send a request for bids to the various content providers offering the same goods or services and selected the invitational content for the content package from the highest bidding content provider. Thus, the engine 228 facilitates the generation of additional revenue for the content delivery system 206.
In the various embodiments, content delivery system 206 can be configured to permit users to adjust the operation and configuration of the various components of content delivery system 206. Accordingly, a user interface can be provided for communicating with a user interface (UI) module 230 for performing such tasks. Further, the UI module 230 can be configured to provide different levels of access based on authenticating different types of users. For example, administrative users can utilize the user interface and UI module 230 for specifying and/or modifying information regarding the primary content providers 210, the secondary content providers 214, user terminals 202, and end users. Administrative users can also utilize the user interface and UI module 230 for specifying operating parameters for the various interfaces, modules, engines, or databases of content delivery system 206. Further, administrative users can also utilize the user interface and UI module 230 for manually or directly adjusting any of the entries in the databases of content delivery system 206.
In addition to providing access to administrative users, the user interface and UI module 230 can also be configured to provide access to end users associated with primary content providers 210 and end users associated with secondary content providers. In the case of end users associated with primary content providers 210, the user interface and UI module 230 can be configured to allow such end users to, for example, update existing content from primary content providers 210 with the content delivery system 206, register new content or new primary content providers with the content delivery system 206, and/or specify preferences for selecting content from secondary content providers 214. In another example, the user interface and UI module 230 can include analysis tools for evaluating performance of content from the primary content providers 210, such as the performance of content with respect to the user terminals and/or content from the secondary content providers 214. In the case of end users associated with secondary content providers 214, the user interface and UI module 230 can be configured to allow these end users to, for example, update existing content from secondary content providers 214 with the content delivery system 206, register new content or new secondary content providers with the content delivery system 206, or specify preferences for selecting primary content providers 214. In another example, the user interface and UI module 230 can include analysis tools for evaluating performance of content from the secondary content providers 214, such as the performance of content with respect to the user terminals 202 and/or content from the primary content providers 210.
In the various embodiments, the user interface for the UI module 230 can be accessed via an end user terminal in communication with the content delivery system 206. For example, the end user terminal can be one of user terminals 202, a user interface device associated with any of content providers 210 and 214, or any user interface device or system locally or remotely connected to content delivery system 206. The user interface and UI module 230 can be configured to operate in a variety of client modes, including a fat client mode, a thin client mode, or a hybrid client mode, depending on the storage and processing capabilities of the content delivery system 206 and/or the end user terminal. Therefore, a user interface for UI module 230 can be implemented as a standalone application operating at the end user terminal in some embodiments. In other embodiments, web browser-based portal can also be used to provide the user interface for UI module 230. Any other configuration to remotely or locally accessing content delivery system 206 can also be used in the various embodiments.
Although the user interface and UI interface 230 are described above as providing specific types of functionality for specific types of end users, the user interface and UI module 230 can also be configured to allow other interactions between end users and the content delivery system 206. For example, the user interface and UI module 230 can be used to specify any of the parameters, weights, or any other variables for the systems and methods described herein. In another example, the user interface can also be user to view, analyze, and/or modify any final or intermediate results or data generated by any of the systems and methods described herein. In yet another example, the user interface and UI module 230 can also provide a reporting/analysis interface area designed for mining/analyzing performance of content from the secondary providers in terms of CTR, eCPM, cost measures, revenue measures, etc. Additionally, UI module 230 can be configured to sends notifications and alerts to users associated with primary content providers 210 (via email, messaging, etc.) when a campaign runs low, a budget runs low, or any other event of interest occurs. Additionally, the UI module 230 can also send daily/weekly/monthly reports of campaign delivery performance and suggestions for optimization to the content providers 210 and 214.
Other implementations according to these examples include non-transitory computer-readable media for carrying or having computer-executable instructions or data structures stored thereon. Such computer-readable media can be any available media that can be accessed by a general purpose or special purpose computer. By way of example, and not limitation, such tangible computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to carry or store desired program code means in the form of computer-executable instructions or data structures.
Computer-executable instructions include, for example, instructions and data which cause a general purpose computer, special purpose computer, or special purpose processing device to perform a certain function or group of functions. Computer-executable instructions also include program modules that are executed by computers in stand-alone or network environments. Generally, program modules include routines, programs, objects, components, and data structures that perform particular tasks or implement particular abstract data types. Computer-executable instructions, associated data structures, and program modules represent examples of the program code means for executing steps of the methods disclosed herein. The particular sequence of such executable instructions or associated data structures represent examples of corresponding acts for implementing the functions described in such steps.
Those of skill in the art will appreciate that other embodiments of the invention may be practiced in network computing environments with many types of computer system configurations, including personal computers, hand-held devices, multi-processor systems, microprocessor-based or programmable consumer electronics, network PCs, minicomputers, mainframe computers, and the like. Embodiments may also be practiced in distributed computing environments where tasks are performed by local and remote processing devices that are linked (either by hardwired links, wireless links, or by a combination thereof) through a communications network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.
Communication at various stages of the described system can be performed through a local area network, a token ring network, the Internet, a corporate intranet, 802.11 series wireless signals, fiber-optic network, radio or microwave transmission, etc. Although the underlying communication technology may change, the fundamental principles described herein are still applicable.
The various embodiments described above are provided by way of illustration only and should not be construed as limiting. Those skilled in the art may recognize various modifications and changes that may be made while following the example embodiments and applications illustrated and described herein, and without departing from the true spirit and scope of the present disclosure.
Number | Name | Date | Kind |
---|---|---|---|
5408519 | Pierce et al. | Apr 1995 | A |
5459306 | Stein et al. | Oct 1995 | A |
5600364 | Hendricks et al. | Feb 1997 | A |
5613213 | Naddell et al. | Mar 1997 | A |
5636346 | Saxe | Jun 1997 | A |
5678179 | Turcotte et al. | Oct 1997 | A |
5724521 | Dedrick | Mar 1998 | A |
5848396 | Gerace | Dec 1998 | A |
5948061 | Merriman et al. | Sep 1999 | A |
5978775 | Chen | Nov 1999 | A |
5978833 | Pashley et al. | Nov 1999 | A |
6006197 | d'Eon et al. | Dec 1999 | A |
6009410 | LeMole et al. | Dec 1999 | A |
6012051 | Sammon et al. | Jan 2000 | A |
6023700 | Owens et al. | Feb 2000 | A |
6055512 | Dean et al. | Apr 2000 | A |
6055513 | Katz et al. | Apr 2000 | A |
6057872 | Candelore | May 2000 | A |
6085229 | Newman et al. | Jul 2000 | A |
6097942 | Laiho | Aug 2000 | A |
6119098 | Guyot et al. | Sep 2000 | A |
6161127 | Cezar et al. | Dec 2000 | A |
6216129 | Eldering | Apr 2001 | B1 |
6236975 | Boe et al. | May 2001 | B1 |
6285987 | Roth et al. | Sep 2001 | B1 |
6286005 | Cannon | Sep 2001 | B1 |
6334145 | Adams et al. | Dec 2001 | B1 |
6338044 | Cook et al. | Jan 2002 | B1 |
6345279 | Li et al. | Feb 2002 | B1 |
6353849 | Linsk | Mar 2002 | B1 |
6381465 | Chern et al. | Apr 2002 | B1 |
6393407 | Middleton, III et al. | May 2002 | B1 |
6405243 | Nielsen | Jun 2002 | B1 |
6408309 | Agarwal | Jun 2002 | B1 |
6421683 | Lamburt | Jul 2002 | B1 |
6442529 | Krishan et al. | Aug 2002 | B1 |
6446261 | Rosser | Sep 2002 | B1 |
6453347 | Revashetti et al. | Sep 2002 | B1 |
6470079 | Benson | Oct 2002 | B1 |
6477575 | Koeppel et al. | Nov 2002 | B1 |
6513052 | Binder | Jan 2003 | B1 |
6560578 | Eldering | May 2003 | B2 |
6591248 | Nakamura et al. | Jul 2003 | B1 |
6647257 | Owensby | Nov 2003 | B2 |
6684249 | Frerichs et al. | Jan 2004 | B1 |
6690394 | Harui | Feb 2004 | B1 |
6698020 | Zigmond et al. | Feb 2004 | B1 |
6718551 | Swix et al. | Apr 2004 | B1 |
6738978 | Hendricks et al. | May 2004 | B1 |
6886000 | Aggarwal et al. | Apr 2005 | B1 |
6907566 | McElfresh et al. | Jun 2005 | B1 |
6915271 | Meyer et al. | Jul 2005 | B1 |
6920326 | Agarwal et al. | Jul 2005 | B2 |
6925441 | Jones et al. | Aug 2005 | B1 |
6990462 | Wilcox et al. | Jan 2006 | B1 |
7010497 | Nyhan et al. | Mar 2006 | B1 |
7039599 | Merriman et al. | May 2006 | B2 |
7072947 | Knox et al. | Jul 2006 | B1 |
7149537 | Kupsh et al. | Dec 2006 | B1 |
7168084 | Hendricks et al. | Jan 2007 | B1 |
7203684 | Carobus et al. | Apr 2007 | B2 |
7243082 | Forlai | Jul 2007 | B1 |
7356477 | Allan et al. | Apr 2008 | B1 |
7370002 | Heckerman et al. | May 2008 | B2 |
7403904 | Abe et al. | Jul 2008 | B2 |
7519566 | Prigogin et al. | Apr 2009 | B2 |
7539652 | Flinn et al. | May 2009 | B2 |
7558559 | Alston | Jul 2009 | B2 |
7669212 | Alao et al. | Feb 2010 | B2 |
7685019 | Collins | Mar 2010 | B2 |
7730017 | Nance et al. | Jun 2010 | B2 |
7734632 | Wang | Jun 2010 | B2 |
7747676 | Nayfeh et al. | Jun 2010 | B1 |
7822636 | Ferber et al. | Oct 2010 | B1 |
7870576 | Eldering | Jan 2011 | B2 |
7882518 | Finseth et al. | Feb 2011 | B2 |
7903099 | Baluja | Mar 2011 | B2 |
7912843 | Murdock et al. | Mar 2011 | B2 |
7987182 | Slothouber et al. | Jul 2011 | B2 |
8019645 | Mattingly et al. | Sep 2011 | B2 |
8046797 | Bentolila et al. | Oct 2011 | B2 |
8060406 | Blegen | Nov 2011 | B2 |
8108895 | Anderson et al. | Jan 2012 | B2 |
8112308 | Ho et al. | Feb 2012 | B1 |
8229786 | Cetin et al. | Jul 2012 | B2 |
8380562 | Toebes et al. | Feb 2013 | B2 |
20010044739 | Bensemana | Nov 2001 | A1 |
20010047272 | Frietas et al. | Nov 2001 | A1 |
20010051925 | Kang | Dec 2001 | A1 |
20020006803 | Mendiola et al. | Jan 2002 | A1 |
20020016736 | Cannon et al. | Feb 2002 | A1 |
20020019829 | Shapiro | Feb 2002 | A1 |
20020052781 | Aufricht et al. | May 2002 | A1 |
20020052925 | Kim et al. | May 2002 | A1 |
20020072965 | Merriman et al. | Jun 2002 | A1 |
20020075305 | Beaton et al. | Jun 2002 | A1 |
20020077130 | Owensby | Jun 2002 | A1 |
20020078147 | Bouthors et al. | Jun 2002 | A1 |
20020082923 | Merriman et al. | Jun 2002 | A1 |
20020083411 | Bouthors et al. | Jun 2002 | A1 |
20020099842 | Jennings et al. | Jul 2002 | A1 |
20020137507 | Winkler | Sep 2002 | A1 |
20020138291 | Vaidyanathan et al. | Sep 2002 | A1 |
20020161770 | Shapiro et al. | Oct 2002 | A1 |
20020164977 | Link, II et al. | Nov 2002 | A1 |
20020165773 | Natsuno et al. | Nov 2002 | A1 |
20020175935 | Wang et al. | Nov 2002 | A1 |
20030003935 | Vesikivi et al. | Jan 2003 | A1 |
20030023489 | McGuire et al. | Jan 2003 | A1 |
20030040297 | Pecen et al. | Feb 2003 | A1 |
20030083931 | Lang | May 2003 | A1 |
20030101454 | Ozer et al. | May 2003 | A1 |
20030126015 | Chan et al. | Jul 2003 | A1 |
20030126146 | Van Der Riet | Jul 2003 | A1 |
20030130887 | Nathaniel | Jul 2003 | A1 |
20030154300 | Mostafa | Aug 2003 | A1 |
20030171990 | Rao et al. | Sep 2003 | A1 |
20030182567 | Barton et al. | Sep 2003 | A1 |
20030188017 | Nomura | Oct 2003 | A1 |
20030191689 | Bosarge et al. | Oct 2003 | A1 |
20030197719 | Lincke et al. | Oct 2003 | A1 |
20040003398 | Donian et al. | Jan 2004 | A1 |
20040043777 | Brouwer et al. | Mar 2004 | A1 |
20040045029 | Matsuura | Mar 2004 | A1 |
20040054576 | Kanerva et al. | Mar 2004 | A1 |
20040068435 | Braunzell | Apr 2004 | A1 |
20040133480 | Domes | Jul 2004 | A1 |
20040136358 | Hind et al. | Jul 2004 | A1 |
20040158858 | Paxton et al. | Aug 2004 | A1 |
20040185883 | Rukman | Sep 2004 | A1 |
20040192359 | McRaild et al. | Sep 2004 | A1 |
20040203761 | Baba et al. | Oct 2004 | A1 |
20040203851 | Vetro et al. | Oct 2004 | A1 |
20040204133 | Andrew et al. | Oct 2004 | A1 |
20040204983 | Shen et al. | Oct 2004 | A1 |
20040209649 | Lord | Oct 2004 | A1 |
20040259526 | Goris et al. | Dec 2004 | A1 |
20050010472 | Quatse et al. | Jan 2005 | A1 |
20050010641 | Staack | Jan 2005 | A1 |
20050021397 | Cui et al. | Jan 2005 | A1 |
20050027587 | Latona et al. | Feb 2005 | A1 |
20050028188 | Latona et al. | Feb 2005 | A1 |
20050060425 | Yeh et al. | Mar 2005 | A1 |
20050091106 | Reller et al. | Apr 2005 | A1 |
20050125397 | Gross et al. | Jun 2005 | A1 |
20050138140 | Wen et al. | Jun 2005 | A1 |
20050228680 | Malik | Oct 2005 | A1 |
20050228797 | Koningstein et al. | Oct 2005 | A1 |
20050239495 | Bayne | Oct 2005 | A1 |
20050239504 | Ishii et al. | Oct 2005 | A1 |
20050249216 | Jones | Nov 2005 | A1 |
20050273384 | Fraser | Dec 2005 | A1 |
20050273465 | Kimura | Dec 2005 | A1 |
20050273833 | Soinio | Dec 2005 | A1 |
20050289000 | Chiang et al. | Dec 2005 | A1 |
20050289113 | Bookstaff | Dec 2005 | A1 |
20060031327 | Kredo | Feb 2006 | A1 |
20060040642 | Boris et al. | Feb 2006 | A1 |
20060048059 | Etkin | Mar 2006 | A1 |
20060059133 | Moritani | Mar 2006 | A1 |
20060068845 | Muller et al. | Mar 2006 | A1 |
20060069616 | Bau | Mar 2006 | A1 |
20060075425 | Koch et al. | Apr 2006 | A1 |
20060095511 | Munarriz et al. | May 2006 | A1 |
20060117378 | Tam et al. | Jun 2006 | A1 |
20060123014 | Ng | Jun 2006 | A1 |
20060129455 | Shah | Jun 2006 | A1 |
20060141923 | Goss | Jun 2006 | A1 |
20060161520 | Brewer et al. | Jul 2006 | A1 |
20060168616 | Candelore | Jul 2006 | A1 |
20060194595 | Myllynen et al. | Aug 2006 | A1 |
20060200460 | Meyerzon et al. | Sep 2006 | A1 |
20060200461 | Lucas et al. | Sep 2006 | A1 |
20060206586 | Ling et al. | Sep 2006 | A1 |
20060259358 | Robinson et al. | Nov 2006 | A1 |
20060276170 | Radhakrishnan et al. | Dec 2006 | A1 |
20060276213 | Gottschalk et al. | Dec 2006 | A1 |
20060277103 | Fujita et al. | Dec 2006 | A1 |
20060282328 | Gerace et al. | Dec 2006 | A1 |
20060286963 | Koskinen et al. | Dec 2006 | A1 |
20060286964 | Polanski et al. | Dec 2006 | A1 |
20060288124 | Kraft et al. | Dec 2006 | A1 |
20070004333 | Kavanti | Jan 2007 | A1 |
20070011344 | Paka et al. | Jan 2007 | A1 |
20070016743 | Jevans | Jan 2007 | A1 |
20070022021 | Walker et al. | Jan 2007 | A1 |
20070027703 | Hu et al. | Feb 2007 | A1 |
20070027760 | Collins et al. | Feb 2007 | A1 |
20070027762 | Collins et al. | Feb 2007 | A1 |
20070037562 | Smith-Kerker et al. | Feb 2007 | A1 |
20070047523 | Jiang | Mar 2007 | A1 |
20070061195 | Liu et al. | Mar 2007 | A1 |
20070061300 | Ramer et al. | Mar 2007 | A1 |
20070072631 | Mock et al. | Mar 2007 | A1 |
20070074262 | Kikkoji et al. | Mar 2007 | A1 |
20070083602 | Heggenhougen et al. | Apr 2007 | A1 |
20070088609 | Reller et al. | Apr 2007 | A1 |
20070088687 | Bromm et al. | Apr 2007 | A1 |
20070088801 | Levkovitz et al. | Apr 2007 | A1 |
20070088851 | Levkovitz et al. | Apr 2007 | A1 |
20070094066 | Kumar et al. | Apr 2007 | A1 |
20070100651 | Ramer et al. | May 2007 | A1 |
20070100805 | Ramer et al. | May 2007 | A1 |
20070105536 | Tingo, Jr. | May 2007 | A1 |
20070113243 | Brey | May 2007 | A1 |
20070117571 | Musial | May 2007 | A1 |
20070118592 | Bachenberg | May 2007 | A1 |
20070136457 | Dai et al. | Jun 2007 | A1 |
20070149208 | Syrbe et al. | Jun 2007 | A1 |
20070180147 | Leigh | Aug 2007 | A1 |
20070192409 | Kleinstern et al. | Aug 2007 | A1 |
20070198485 | Ramer et al. | Aug 2007 | A1 |
20070214470 | Glasgow et al. | Sep 2007 | A1 |
20070233671 | Oztekin et al. | Oct 2007 | A1 |
20070260624 | Chung et al. | Nov 2007 | A1 |
20070276537 | Walker et al. | Nov 2007 | A1 |
20070288950 | Downey et al. | Dec 2007 | A1 |
20070290787 | Fiatal et al. | Dec 2007 | A1 |
20080004046 | Mumick et al. | Jan 2008 | A1 |
20080013537 | Dewey et al. | Jan 2008 | A1 |
20080032703 | Krumm et al. | Feb 2008 | A1 |
20080032717 | Sawada et al. | Feb 2008 | A1 |
20080065476 | Klein et al. | Mar 2008 | A1 |
20080065491 | Bakman | Mar 2008 | A1 |
20080070579 | Kankar et al. | Mar 2008 | A1 |
20080071875 | Koff et al. | Mar 2008 | A1 |
20080071929 | Motte et al. | Mar 2008 | A1 |
20080082686 | Schmidt et al. | Apr 2008 | A1 |
20080091796 | Story | Apr 2008 | A1 |
20080133344 | Hyder et al. | Jun 2008 | A1 |
20080140476 | Anand et al. | Jun 2008 | A1 |
20080140508 | Anand et al. | Jun 2008 | A1 |
20080140524 | Anand et al. | Jun 2008 | A1 |
20080147495 | Bal et al. | Jun 2008 | A1 |
20080228568 | Williams et al. | Sep 2008 | A1 |
20080243619 | Sharman et al. | Oct 2008 | A1 |
20080249832 | Richardson et al. | Oct 2008 | A1 |
20080262927 | Kanayama et al. | Oct 2008 | A1 |
20080271068 | Ou et al. | Oct 2008 | A1 |
20080281606 | Kitts et al. | Nov 2008 | A1 |
20080288476 | Kim et al. | Nov 2008 | A1 |
20080319836 | Aaltonen et al. | Dec 2008 | A1 |
20090006194 | Sridharan et al. | Jan 2009 | A1 |
20090029721 | Doraswamy | Jan 2009 | A1 |
20090049090 | Shenfield et al. | Feb 2009 | A1 |
20090063249 | Tomlin et al. | Mar 2009 | A1 |
20090106111 | Walk et al. | Apr 2009 | A1 |
20090125377 | Somji et al. | May 2009 | A1 |
20090132395 | Lam et al. | May 2009 | A1 |
20090138304 | Aharoni et al. | May 2009 | A1 |
20090197619 | Colligan et al. | Aug 2009 | A1 |
20090216847 | Krishnaswamy et al. | Aug 2009 | A1 |
20090240677 | Parekh et al. | Sep 2009 | A1 |
20090275315 | Alston | Nov 2009 | A1 |
20090286520 | Nielsen et al. | Nov 2009 | A1 |
20090298483 | Bratu et al. | Dec 2009 | A1 |
20100030647 | Shahshahani | Feb 2010 | A1 |
20100057548 | Edwards | Mar 2010 | A1 |
20100082397 | Blegen | Apr 2010 | A1 |
20100082423 | Nag et al. | Apr 2010 | A1 |
20100088152 | Bennett | Apr 2010 | A1 |
20100114654 | Lukose et al. | May 2010 | A1 |
20100125505 | Puttaswamy | May 2010 | A1 |
20100138271 | Henkin | Jun 2010 | A1 |
20100161424 | Sylvain | Jun 2010 | A1 |
20100169157 | Muhonen et al. | Jul 2010 | A1 |
20100169176 | Turakhia | Jul 2010 | A1 |
20100257053 | Ferber et al. | Oct 2010 | A1 |
20100262487 | Edwards et al. | Oct 2010 | A1 |
20110106840 | Barrett et al. | May 2011 | A1 |
20110209067 | Bogess et al. | Aug 2011 | A1 |
20110276401 | Knowles et al. | Nov 2011 | A1 |
Number | Date | Country |
---|---|---|
1015704 | Jul 2005 | BE |
19941461 | Mar 2001 | DE |
10061984 | Jun 2002 | DE |
0749081 | May 1996 | EP |
1061465 | Dec 2000 | EP |
1073293 | Jan 2001 | EP |
1107137 | Jun 2001 | EP |
1109371 | Jun 2001 | EP |
1220132 | Jul 2002 | EP |
1239392 | Sep 2002 | EP |
1280087 | Jan 2003 | EP |
1365604 | Nov 2003 | EP |
1408705 | Apr 2004 | EP |
1455511 | Sep 2004 | EP |
1509024 | Feb 2005 | EP |
1528827 | May 2005 | EP |
1542482 | Jun 2005 | EP |
1587332 | Oct 2005 | EP |
1615455 | Jan 2006 | EP |
1633100 | Mar 2006 | EP |
1677475 | Jul 2006 | EP |
1772822 | Apr 2007 | EP |
2343051 | Apr 2000 | GB |
2369218 | May 2002 | GB |
2372867 | Sep 2002 | GB |
2406996 | Apr 2005 | GB |
2414621 | Nov 2005 | GB |
2424546 | Sep 2006 | GB |
2002-140272 | May 2002 | JP |
2007087138 | Apr 2007 | JP |
2007199821 | Aug 2007 | JP |
20060011760 | Jul 2004 | KR |
9624213 | Aug 1996 | WO |
WO 9707656 | Mar 1997 | WO |
9821713 | May 1998 | WO |
WO 9858334 | Dec 1998 | WO |
0000916 | Jan 2000 | WO |
0030002 | May 2000 | WO |
0044151 | Jul 2000 | WO |
0122748 | Mar 2001 | WO |
0131497 | May 2001 | WO |
0144977 | Jun 2001 | WO |
0152161 | Jul 2001 | WO |
0157705 | Aug 2001 | WO |
0158178 | Aug 2001 | WO |
0163423 | Aug 2001 | WO |
0165411 | Sep 2001 | WO |
0169406 | Sep 2001 | WO |
0171949 | Sep 2001 | WO |
0172063 | Sep 2001 | WO |
0191400 | Nov 2001 | WO |
0193551 | Dec 2001 | WO |
0197539 | Dec 2001 | WO |
0209431 | Jan 2002 | WO |
0231624 | Apr 2002 | WO |
0244989 | Jun 2002 | WO |
02054803 | Jul 2002 | WO |
02069585 | Sep 2002 | WO |
02069651 | Sep 2002 | WO |
02075574 | Sep 2002 | WO |
02084895 | Oct 2002 | WO |
02086664 | Oct 2002 | WO |
02096056 | Nov 2002 | WO |
03015430 | Feb 2003 | WO |
03019845 | Mar 2003 | WO |
03024136 | Mar 2003 | WO |
03049461 | Jun 2003 | WO |
03088690 | Oct 2003 | WO |
2004084532 | Sep 2004 | WO |
2004086791 | Oct 2004 | WO |
2004100470 | Nov 2004 | WO |
2004100521 | Nov 2004 | WO |
2004102993 | Nov 2004 | WO |
2004104867 | Dec 2004 | WO |
WO 2005013092 | Feb 2005 | WO |
2005020578 | Mar 2005 | WO |
2005029769 | Mar 2005 | WO |
2005073863 | Aug 2005 | WO |
2005076650 | Aug 2005 | WO |
2006002869 | Jan 2006 | WO |
2006005001 | Jan 2006 | WO |
2006016189 | Feb 2006 | WO |
2006024003 | Mar 2006 | WO |
2006027407 | Mar 2006 | WO |
2006040749 | Apr 2006 | WO |
2006093284 | Sep 2006 | WO |
2006119481 | Sep 2006 | WO |
2007001118 | Jan 2007 | WO |
2007002025 | Jan 2007 | WO |
2007060451 | May 2007 | WO |
2007091089 | Aug 2007 | WO |
2007103263 | Sep 2007 | WO |
2008013437 | Jan 2008 | WO |
2008024852 | Feb 2008 | WO |
2008045867 | Apr 2008 | WO |
2008147919 | Dec 2008 | WO |
2009009507 | Jan 2009 | WO |
2009032856 | Mar 2009 | WO |
2009061914 | May 2009 | WO |
2009077888 | Jun 2009 | WO |
2009099876 | Aug 2009 | WO |
2009158097 | Dec 2009 | WO |
Entry |
---|
AdWords Reference Guide Google, 2004. |
Karuga, Gilber G. et al., AdPalette: an algorithm for customizing online advertisements on the fly Decision Support Systems, vol. 32, 2001. |
Ghose, Anindya et al., An Empirical Analysis of Search Enginer Advertising: Sponsored Search in Electronic Markets Managemetn Science, Informs, 2009. |
“Advertisement System, Method and Computer Program Product”, IP.com Prior Art Database Disclosure, Pub No. IPCOM000138557D, dated Jul. 24, 2006, IP.com, Amherst, NY (Available online at http://priorartdatabase.com/IPCOM/000138557, last visited Aug. 30, 2010). |
“Combined Search and Examination Report”, for United Kingdom Patent Application No. GB 0816228.1 dated Jan. 2009, Jan. 6, 2009,. |
“Combined Search and Examination Report dated Mar. 7, 2008”, for United Kingdom Patent Application No. GB 0721863.9, Mar. 7, 2008. |
“Communication (Combined Search and Examination Report under Sections 17 and 18(3)) dated Jan. 30, 2009 issued from the United Kingdom Patent Office”, in related United Kingdom Application No. GB 0818145.5 (8 pages). |
“Communication (European Search Report) dated Jun. 26, 2008”, in European Patent Application No. EP 08101394. |
“Communication (European Search Report) dated Oct. 17, 2008 issued by the European Patent Office”, in counterpart European Patent Application EP 08156763. |
“Communication (International Search Report along with Written Opinion of International Searching Authority) mailed Oct. 8, 2008 issued by the International Searching Authority”, in counterpart International Application PCT/EP 2008/056342. |
“Communication (Notification Concerning Transmittal of International Preliminary Report on Patentability, International Preliminary Report on Patentability, and Written Opinion of the International Searching Authority)”, issued in connection with related International Application PCT/EP 2008/051489 and mailed on Sep. 24, 2009 (6 pages). |
“Communication (Search Report under Section 17 along with Examination Report under Section 18(3)) dated Oct. 6, 2008 issued by the United Kingdom Intellectual Property Office”, in counterpart U.K. Application GB 0809321.3. |
“Communication Pursuant to Article 94(3) EPC (European Examination Report) dated Oct. 23, 2008”, issued in counterpart European Patent Application No. EP 08101394.8-1238. |
“Examination Report”, for counterpart European Patent Applicaiton No. 08153257.4 issued Jun. 2, 2009. |
“Examination Report dated Nov. 9, 2009”, for European Patent Application No. EP 08159355.0. |
“Examination Report dated Jun. 17, 2009”, issued in counterpart U.K. Application No. GB 0803273.2 by U.K. Intellectual Property Office (4 pages). |
“International Preliminary Report on Patentability and Written Opinion issued Nov. 24, 2009”, in International Application PCT/EP 2008/056342 (1 page). |
“International Search Report”, for International Application No. PCT/FI 2006/050455, dated Jul. 25, 2007. |
“International Search Report and Written Opinion mailed on Aug. 26, 2011”, for PCT/US 2011/034927 titled “Content Delivery Based on User Terminal Events,” to Apple Inc. |
“International Search Report and Written Opinion of the International Search Authority mailed Jun. 19, 2009”, for International Application No. PCT/EP 2008/056069. |
“International Search Report and Written Opinion of the International Searching Authority mailed Feb. 11, 2009, issued by the International Searching Authority”, in related International Application PCT/EP 2008/063839 (11 pages). |
“International Search Report mailed Mar. 24, 2009”, in related PCT International Application No. PCT/EP 2008/063326 (4 pages). |
“Notice of Allowance dated Apr. 29, 2011”, U.S. Appl. No. 11/888,680, Apr. 29, 2011, 13 pages. |
“Office Action dated Mar. 31, 2011 issue by the U.S. Patent Office”, in related U.S. Appl. No. 12/080,124 (29 pages). |
“Office Action issued from the USPTO dated Aug. 20, 2009”, issued in related U.S. Appl. No. 12/075,593 (14 pages). |
“Office Action issued Mar. 17, 2010”, in related U.S. Appl. No. 12/075,593 (11 pages). |
“Office Action Issued Oct. 15, 2010 by the U.S. Patent Office”, in related U.S. Appl. No. 12/080,124 (28 pages). |
“Search Report under Section 17 dated Jul. 7, 2008”, in related U.K. Application GB 0803273.2. |
“U.K. Search Report under Section 17 dated Oct. 23, 2007”, in U.K. Application No. 0712280.7. |
“Written Opinion of the International Searching Authority mailed Mar. 24, 2009 issued from the International Searching Authority”, in related PCT International Application No. PCT/EP 2008/063326 (5 pages). |
“XP002456252—Statement in Accordance with the Notice from the European Patent Office dated Oct. 1, 2007”, concerning business methods (OJ Nov. 2007; p. 592-593), 592-593. |
Hillard, Dustin et al., “Improving Ad Relevance in Sponsored Search”, Proceedings of the third ACM international conference on Web search and data mining, WSDNR10, Feb. 4-6, 2010, Session: Ads, pp. 361-369, ACM, New York, New York, USA, 2010, 361-369. |
Internet Reference, “Specific Media Behavioral Targeting Index”, Specific Media, Inc., Irvine, CA, 2010, Available online at http://www.specificmedia.com/behavioral-targeting.php. |
Langheinrich, Marc et al., “Unintrusive Customization Techniques for Web Advertising”, Computer Networks: the International Journal of Computer and Telecommunications Networking, vol. 31, No. 11, May 1999, pp. 1259-1272, Elsevier North-Holland, Inc., New York, NY, 1999, 1259-1272. |
Mueller, Milton , “Telecommunication Access in Age of Electronic Commerce: Toward a Third-Generation Service Policy”, Nov. 1996, HeinOnline, 49. Fed. Comm L.J., 655-665. |
Perkins, Ed , “When to buy airfare”, http://www.smartertrael.com/travel-advice/when-to-buy-airfare.html?id=1628038, Nov. 21, 2006 (4 pages). |
Regelson, Moira et al., “Predicting Click-Through Rate Using Keyword Clusters”, Proceedings of the Second Workshop on Sponsored Search Auctions, EC'06, SSA2, Jun. 11, 2006, ACM, 2006. |
Richardson, Matthew et al., “Predicting Clicks: Estimating the Click-Through Rate for New Ads”, Proceedings of the 16th international conference on World Wide Web, Banff, Alberta, Canada, May 8-12, 2007, Session: Advertisements & click estimates, pp. 521-529, ACM, 2007., 521-529. |
Shaikh, Baber M. et al., “Customized User Segments for Ad Targeting”, IP.com Prior Art Database Disclosure, Pub No. IPCOM000185640D, dated Jul. 29, 2009 UTC, IP.com, Amherst, NY (Available online at http://priorartdatabase.com/IPCOM/000185640, last visited Aug. 30, 2010). |
Number | Date | Country | |
---|---|---|---|
20110295628 A1 | Dec 2011 | US |