The described technology relates generally to terms that are related to an item and specifically to search terms for use in placing advertisements for the item. Many search engine services, such as Google and Overture, provide for searching for information that is accessible via the Internet. These search engine services allow users to search for web pages and other Internet-accessible resources that may be of interest to users. After a user submits a search request that includes search terms, the search engine service identifies web pages that may be related to those search terms. To quickly identify related web pages, the search engine services may maintain a mapping of keywords to web pages. This mapping may be generated by “crawling” the web (i.e., the World Wide Web) to identify the keywords of each web page. To crawl the web, a search engine service may use a list of root web pages to identify all web pages that are accessible through those root web pages. The keywords of any particular web page can be identified using various well-known information retrieval techniques, such as identifying the words of a headline, the words supplied in the metadata of the web page, the words that are highlighted, and so on. Some search engine services can even search information sources that are not accessible via the Internet. For example, a book publisher may make the content of its books available to a search engine service. The search engine may generate a mapping between the keywords and books. When a search engine service receives a search request that includes one or more search terms, it uses its mapping to identify those information sources (e.g., web pages or books) whose keywords most closely match the search terms. The collection of information sources that most closely matches the search terms is referred to as the “search result.” The search engine service then ranks the information sources of the search result based on the closeness of each match, web page popularity (e.g., Google's page ranking), and so on. The search engine service then displays to the user links to those information sources in an order that is based on their rankings.
Some search engine services do not charge a fee to the providers of web pages for including links to their web pages in search results. Rather, the search engine services obtain revenue by placing advertisements along with search results. These paid-for advertisements are commonly referred to as “sponsored links,” “sponsored matches,” or “paid-for search results.” An advertiser who wants to place an advertisement for an item along with certain search results provides a search engine service with an advertisement and search terms. When a search request is received, the search engine service identifies the advertisements whose search terms most closely match those of the search request. The search engine services can either charge for placement of each advertisement along with search results (i.e., cost per impression) or charge only when a user actually selects a link associated with an advertisement (i.e., cost per click).
Advertisers would like to maximize the effectiveness of advertising dollars used to pay for advertisements placed along with search results. Those advertisers try to identify search terms for items being advertised that result in the highest benefit (e.g., most profit) to the advertiser. It would be desirable to have techniques that would allow advertisers to maximize the effectiveness of their advertising dollars by identifying search terms that are more targeted to or related to the item being advertised.
A method and system for identifying search terms for placing advertisements along with search results is provided. In one embodiment, the advertisement system selects a description of an item that is to be advertised. For example, if the item is a book, then the description may be the title of the book; or if the item is an electronic device, then the description may be a brief summary of the device. The advertisement system then retrieves documents or other information sources that match (e.g., are most closely related to the subject of) the selected description from a corpus of information sources. For example, the advertisement system may submit the selected description to a search engine service with the web pages of the search results being the retrieved documents. The advertisement system then generates a score for each word of the retrieved documents that indicates relatedness of the word to the item to be advertised. In one embodiment, the advertisement system may generate a high score for words that are used much more frequently within the retrieved documents than within the corpus of the information sources. For example, if the item is a Harry Potter book, then words such as “Hogwarts,” “Fluffy,” “three-headed,” “dog,” “Hermione,” and “Granger” may have a relatively high score because those words appear more frequently in discussions of Harry Potter than in unrelated discussions. After generating the scores for the words, the advertisement system identifies phrases of the words within the documents that are likely to be related to the item. For example, the advertisement system may identify that the phrases “Fluffy the three-headed dog” and “Hermione Granger” are likely related to the book. The advertisement system then generates search terms for the item to be advertised from the identified phrases. The advertisement system submits the search terms and an advertisement to a search engines service for placement of a paid-for advertisement for the item. For example, the advertisement system may place an advertisement for the Harry Potter book with the search term “Hermione Granger.” When someone submits a search request of “Hermione Granger” to the search engine service, it will display that advertisement along with the search results. In this way, the advertisement system can identify search terms based on phrases used in information sources that are known to be related to the item that is to be advertised.
In one embodiment, the advertisement system identifies phrases that are likely to be related to the item to be advertised. Because the number of phrases within a document is O(n2), when n is the number of words within a document and the number of possible phrases in a corpus of documents is kl where k is the number of distinct words and l is the length of the phrase, it would be computationally very expensive to evaluate and track every possible phrase. To reduce the number of phrases that are evaluated, the advertisement system evaluates groups of words with high scores that are in close proximity to each other. The advertisement system initially generates a score for the words within documents that are related to the item. The score indicates the likelihood that the word is related to the item. The advertisement system may then identify highly related words and related words. A highly related word has a very high score such as a score in the top 10%, and a related word has a high score such as a score in the top 25%. The advertisement system searches the documents for the highly related words. Each highly related word within a document is considered the “anchor word” of a phrase. The advertisement system tries to extend the phrase to include nearby related words. In one embodiment, the advertisement system may extend the phrase by any contiguous related words that follow the anchor word. For example, if “Hermione” is a highly related word and “Granger” is a related word, the phrase “Hermione Granger” would be identified as a phrase when “Hermione” is followed by “Granger” in a document. Alternatively, the advertisement system may extend the phrase to also include words before the anchor word. For example, if “Granger” is a highly related word and “Hermione” is only a related word, then the phrase “Hermione Granger” would still be identified. The advertisement system may calculate a phrase score and continue extending a phrase so long as the score of the extended phrase increases regardless of whether all the words of the phrase are related words. One skilled in the art will appreciate that the technique for identifying such phrases may be used in contexts other than generating search terms for advertisements. For example, a search engine service may use the phrases identified in the search results as search requests for locating additional related information sources to present to a user. Alternatively, the advertisement system could identify more phrases from the additional related information sources. More generally, given a corpus of information sources, the technique for identifying phrases can be used to identify topics of the information sources. For example, if the information sources are chat discussions, then the identified phrases may represent the most popular topics of the chat discussions.
The advertisement system includes a create advertisement sets component 111, a score words component 112, an identify best phrases component 113, a find phrases component 114, a score common phrases component 115, an item data store 116, a search results store 117, and a score store 118. The item data store contains an identifier (e.g., SKU) of each item to be advertised along with a description of the item. For example, the item data store may be an electronic catalog of books that are to be advertised. Each catalog entry may include an item identifier, a title, an author name, a summary, and so on. The search results store contains the matching web pages for the item for which search terms are being identified. The score store contains the score for the words and phrases of the search results store. The create advertisement sets component is provided with an item identifier and identifies search terms (e.g., keywords) to be used when advertising that item. The create advertisement sets component requests a search engine service to provide search results, retrieves the web pages of those search results, invokes the score words component and the identify best phrases component, and then generates the advertisement sets. The score words component generates a score for each word of the search results that indicates a likelihood that the word is related to the item. The identify best phrases component invokes the find phrases component and the score common phrases component to identify phrases that are likely to be related to the item.
The advertisement system may be implemented on computer systems and servers that include a central processing unit, a memory, input devices (e.g., keyboard and pointing devices), output devices (e.g., display devices), and storage devices (e.g., disk drives). The memory and storage devices are computer-readable media that may contain instructions that implement the advertisement system. In addition, the data structures and message structures may be stored or transmitted via a data transmission medium, such as a signal on a communications link. Various communications links may be used, such as the Internet, a local area network, a wide area network, or a point-to-point dial-up connection.
where
where Sf is the frequency score for the word, {tilde over (f)} is the normal frequency of the word, and atan is the arc tangent function. One skilled in the art will appreciate that this equation is just one of many equations that can be used to generate the frequency score. The particular equation used can be selected based on the weight to be given to the difference between the average and normal frequencies of a word. In block 306, the component calculates the number of documents of the search results that contain the selected word. In block 307, the component calculates a “contain score” that indicates the fraction of the documents of the search results that contain the selected word. The contain score may be represented by the following equation:
where Sc is the contain score and n′ is the number of documents of the search results that contain the selected word. In block 308, the component calculates the score for the selected word. In one embodiment, the word score is a linear combination of the frequency score and the contain score. The weight of the frequency score and the contain score can be set to reflect whether the frequency score or the contain score is considered to be a more accurate representation of the likelihood that the word is related to the item. The word score may be represented by the following equation:
S=α*Sf+(1−∝)*Sc (4)
where S is the word score and ∝ varies from zero to one and represents the weight given to the frequency score. The component then loops to block 301 to select the next word in the search results.
One skilled in the art will appreciate that although specific embodiments of the advertisement system have been described herein for purposes of illustration, various modifications may be made without deviating from the spirit and scope of the invention. The term “item” includes any product, service, or concept that can be advertised. For example, a political party can place advertisements relating to a particular candidate or cause. In addition, an advertisement set may not have a link associated with it. An advertiser may want to simply display the information of an advertisement to users who submit requests using a certain search term. For example, a candidate may want an advertisement displayed when a user submits a search request with the name of their opponent as a search term. One skilled in the art will appreciate that various equations and techniques for calculating scores can be used. Also, if the search results contain documents that are duplicates (or very similar), the advertising system may disregard the duplicate documents. The advertisement system may maintain a list of words that should not be added to phrases, such as a word that is very common on all web pages (e.g., “next page” or “privacy policy”). Accordingly, the invention is not limited except by the appended claims.
This application is a continuation of U.S. patent application Ser. 12/783,819, filed May 20, 2010, which is a divisional of U.S. patent application Ser. 10/914,722, filed on Aug. 9, 2004, of which the full disclosure of this application is incorporated herein by reference for all purposes.
Number | Name | Date | Kind |
---|---|---|---|
4992940 | Dworkin | Feb 1991 | A |
5283639 | Esch et al. | Feb 1994 | A |
5319544 | Schmerer et al. | Jun 1994 | A |
5471382 | Tallman et al. | Nov 1995 | A |
5500514 | Veeneman et al. | Mar 1996 | A |
5615109 | Eder | Mar 1997 | A |
5745602 | Chen | Apr 1998 | A |
5845278 | Chang et al. | Dec 1998 | A |
5845527 | Hoffmann et al. | Dec 1998 | A |
5937392 | Alberts | Aug 1999 | A |
6078866 | Buck et al. | Jun 2000 | A |
6112021 | Brand | Aug 2000 | A |
6128651 | Cezar | Oct 2000 | A |
6169999 | Kanno | Jan 2001 | B1 |
6269361 | Davis et al. | Jul 2001 | B1 |
6424963 | Ito et al. | Jul 2002 | B1 |
6449657 | Stanbach et al. | Sep 2002 | B2 |
6591248 | Nakamura et al. | Jul 2003 | B1 |
6606644 | Ford et al. | Aug 2003 | B1 |
6751621 | Calistri-Yeh et al. | Jun 2004 | B1 |
6763362 | McKeeth | Jul 2004 | B2 |
6826572 | Colace et al. | Nov 2004 | B2 |
6915294 | Singh et al. | Jul 2005 | B1 |
6920464 | Fox | Jul 2005 | B2 |
6963863 | Bannon | Nov 2005 | B1 |
6978263 | Soulanille | Dec 2005 | B2 |
7031932 | Lipsky et al. | Apr 2006 | B1 |
7035812 | Meisel et al. | Apr 2006 | B2 |
7043450 | Velez et al. | May 2006 | B2 |
7076443 | Emens et al. | Jul 2006 | B1 |
7076479 | Cheung et al. | Jul 2006 | B1 |
7080073 | Jiang et al. | Jul 2006 | B1 |
7127408 | Rosen | Oct 2006 | B2 |
7225182 | Paine et al. | May 2007 | B2 |
7346606 | Bharat | Mar 2008 | B2 |
7346839 | Acharya et al. | Mar 2008 | B2 |
7363254 | Skinner | Apr 2008 | B2 |
7376588 | Gregov et al. | May 2008 | B1 |
7467349 | Bryar et al. | Dec 2008 | B1 |
7752200 | Scholl et al. | Jul 2010 | B2 |
7873640 | Chang | Jan 2011 | B2 |
8335719 | Quraishi et al. | Dec 2012 | B1 |
8429184 | Ismalon | Apr 2013 | B2 |
8655727 | Scholl et al. | Feb 2014 | B2 |
8781888 | Snyder et al. | Jul 2014 | B1 |
8788320 | Snyder et al. | Jul 2014 | B1 |
9489449 | Scholl et al. | Nov 2016 | B1 |
20010053999 | Feinberg | Dec 2001 | A1 |
20020010757 | Granik et al. | Jan 2002 | A1 |
20020024532 | Fables et al. | Feb 2002 | A1 |
20020094868 | Tuck et al. | Jul 2002 | A1 |
20020103698 | Cantrell | Jul 2002 | A1 |
20020111847 | Smith, III | Aug 2002 | A1 |
20020116291 | Grasso et al. | Aug 2002 | A1 |
20030018501 | Shan | Jan 2003 | A1 |
20030055816 | Paine et al. | Mar 2003 | A1 |
20030078913 | McGreevy | Apr 2003 | A1 |
20030105677 | Skinner | Jun 2003 | A1 |
20030120626 | Piotrowski | Jun 2003 | A1 |
20030120641 | Pelletier | Jun 2003 | A1 |
20030208394 | Burris et al. | Nov 2003 | A1 |
20030216930 | Dunham et al. | Nov 2003 | A1 |
20040030556 | Bennett | Feb 2004 | A1 |
20040044571 | Bronnimann et al. | Mar 2004 | A1 |
20040044574 | Cochran et al. | Mar 2004 | A1 |
20040054677 | Mueller et al. | Mar 2004 | A1 |
20040088241 | Rebane et al. | May 2004 | A1 |
20040103070 | Joseph et al. | May 2004 | A1 |
20040133469 | Chang | Jul 2004 | A1 |
20040162757 | Pisaris-Henderson et al. | Aug 2004 | A1 |
20040181520 | Imaichi et al. | Sep 2004 | A1 |
20040186831 | Hiratsuka | Sep 2004 | A1 |
20040243581 | Weissman et al. | Dec 2004 | A1 |
20040267806 | Lester | Dec 2004 | A1 |
20050065806 | Harik | Mar 2005 | A1 |
20050065909 | Musgrove | Mar 2005 | A1 |
20050071325 | Bem | Mar 2005 | A1 |
20050097024 | Rainey | May 2005 | A1 |
20050114198 | Koningstein et al. | May 2005 | A1 |
20050120311 | Thrall | Jun 2005 | A1 |
20050137939 | Calabria et al. | Jun 2005 | A1 |
20050144064 | Calabria et al. | Jun 2005 | A1 |
20050144068 | Calabria et al. | Jun 2005 | A1 |
20050144069 | Wiseman et al. | Jun 2005 | A1 |
20050144158 | Capper et al. | Jun 2005 | A1 |
20050149388 | Scholl | Jul 2005 | A1 |
20050149390 | Scholl et al. | Jul 2005 | A1 |
20050160002 | Roetter et al. | Jul 2005 | A1 |
20050197829 | Okumura | Sep 2005 | A1 |
20050216230 | Gunzert et al. | Sep 2005 | A1 |
20050216335 | Fikes et al. | Sep 2005 | A1 |
20050216516 | Calistri-Yeh et al. | Sep 2005 | A1 |
20050228797 | Koningstein et al. | Oct 2005 | A1 |
20050246230 | Murray | Nov 2005 | A1 |
20050267872 | Galai et al. | Dec 2005 | A1 |
20060004628 | Axe et al. | Jan 2006 | A1 |
20060041480 | Briggs | Feb 2006 | A1 |
20060041536 | Scholl et al. | Feb 2006 | A1 |
20060161635 | Lamkin et al. | Jul 2006 | A1 |
20070162379 | Skinner | Jul 2007 | A1 |
20070266020 | Case et al. | Nov 2007 | A1 |
20100005094 | Poltorak | Jan 2010 | A1 |
Number | Date | Country |
---|---|---|
2550853 | Jul 2005 | CA |
2575734 | Jan 2017 | CA |
1269897 | Oct 2000 | CN |
1306258 | Aug 2001 | CN |
101023408 | Aug 2007 | CN |
102708115 | Dec 2015 | CN |
1776648 | Jan 2011 | EP |
24260902 | Nov 2006 | GB |
2002-278949 | Sep 2002 | JP |
4672726 | Jan 2011 | JP |
10-0904787 | Jun 2009 | KR |
9722066 | Jun 1997 | WO |
2005065400 | Jul 2005 | WO |
2006020576 | Feb 2006 | WO |
Entry |
---|
International Search Report issued for International Application No. PCT/US05/028148 dated Jun. 23, 2006. |
Written Opinion issued for International Application No. PCT/US05/028148 dated Jun. 23, 2006. |
International Preliminary Report on Patentability issued for International.Application No. PCT/US05/028148 dated Feb. 13, 2007. |
International Search Report issued for International Application No. PCT/US04/044021 dated Nov. 22, 2006. |
Written Opinion issued for International Application No. PCT/USO4/044021 dated Nov. 22, 2006. |
International Preliminary Report on Patentability issued for International Application No. PCT/USO4/044021 dated Jan. 30, 2007. |
Non-Final Office Action issued in connection with co-related U.S. Appl. No. 10/748,694 dated Mar. 21, 2016. |
Final Office Action issued in connection with co-related U.S. Appl. No. 10/748,694 dated Mar. 6, 2015. |
Non-Final Office Action issued in connection with co-related U.S. Appl. No. 10/748,694 dated Sep. 29, 2014. |
Final Office Action issued in connection with co-related U.S. Appl. No. 10/748,694 dated Jan. 31, 2014. |
Non-Final Office Action issued in connection with co-related U.S. Appl. No. 10/748,694 dated Aug. 27, 2013. |
Final Office Action issued in connection with co-related U.S. Appl. No. 10/748,694 dated Jan. 31, 2013. |
Non-Final Office Action issued in connection with co-related U.S. Appl. No. 10/748,694 dated Aug. 29, 2012. |
Final Office Action issued in connection with co-related U.S. Appl. No. 10/748,694 dated Apr. 9, 2010. |
Non-Final Office Action issued in connection with co-related U.S. Appl. No. 10/748,694 dated Oct. 29, 2009. |
Final Office Action issued in connection with co-related U.S. Appl. No. 10/748,694 dated Jun. 30, 2009. |
Non-Final Office Action issued in connection with co-related U.S. Appl. No. 10/748,694 dated Dec. 19, 2008. |
Non-Final Office Action issued in co-related U.S. Appl. No. 10/748,759 dated Apr. 4, 2007. |
Final Office Action issued in co-related U.S. Appl. No. 10/748,759 dated Oct. 31, 2007. |
Non-Final Office Action issued in co-related U.S. Appl. No. 10/748,759 dated Jul. 1, 2008. |
Final Office Action issued in co-related U.S. Appl. No. 10/748,759 dated Jan. 5, 2009. |
Non-Final Office Action issued in co-related U.S. Appl. No. 10/748,759 dated Jun. 1, 2009. |
Final Office Action issued in co-related U.S. Appl. No. 10/748,759 dated Dec. 11, 2009. |
Non-Final Office Action issued in co-related U.S. Appl. No. 10/748,759 dated Feb. 19, 2010. |
Final Office Action issued in co-related U.S. Appl. No. 10/748,759 dated Jul. 13, 2010. |
Final Office Action issued in co-related U.S. Appl. No. 10/748,759 dated Aug. 10, 2010. |
Notice of Allowance issued in co-related U.S. Appl. No. 10/748,759 dated Oct. 25, 2013. |
Restriction Requirement issued in connection with co-related U.S. Appl. No. 10/914,722 dated Apr. 20, 2007. |
Non-Final Rejection issued in connection with co-related U.S. Appl. No. 10/914,722 dated Jun. 4, 2007. |
Final Rejection issued in connection with co-related U.S. Appl. No. 10/914,722 dated Jan. 10, 2008. |
Non-Final Rejection issued in connection with co-related U.S. Appl. No. 10/914,722 dated Aug. 20, 2008. |
Final Rejection issued in connection with co-related U.S. Appl. No. 10/914,722 dated Jan. 28, 2009. |
Non-Final Rejection issued in connection with co-related U.S. Appl. No. 10/914,722 dated Jul. 1, 2009. |
Notice of Allowance issued in connection with co-related U.S. Appl. No. 10/914,722 dated Jan. 26, 2010. |
Notice of Allowance issued in connection with co-related U.S. Appl. No. 10/914,722 dated Apr. 14, 2010. |
Non-Final Office Action issued in connection with co-related U.S. Appl. No. 10/917,227 dated Feb. 27, 2009. |
Final Office Action issued in connection with co-related U.S. Appl. No. 10/917,227 dated Jul. 29, 2009. |
Non-Final Office Action issued in connection with co-related U.S. Appl. No. 10/917,227 dated Nov. 24, 2009. |
Final Office Action issued in connection with co-related U.S. Appl. No. 10/917,227 dated May 20, 2010. |
Non-Final Office Action issued in connection with co-related U.S. Appl. No. 10/917,227 dated Mar. 1, 2013. |
Final Office Action issued in connection with co-related U.S. Appl. No. 10/917,227 dated Aug. 13, 2013. |
Non-Final Office Action issued in connection with co-related U.S. Appl. No. 10/917,227 dated Jan. 27, 2014. |
Non-Final Office Action issued in connection with co-related U.S. Appl. No. 10/917,227 dated Jul. 23, 2014. |
Final Office Action issued in connection with co-related U.S. Appl. No. 10/917,227 dated Jan. 8, 2015. |
Non-Final Office Action issued in connection with co-related U.S. Appl. No. 10/917,227 dated Nov. 10, 2015. |
Non-Final Office Action issued in co-related U.S. Appl. No. 11/274,486 dated Aug. 1, 2008. |
Non-Final Office Action issued in co-related U.S. Appl. No. 11/274,486 dated Aug. 5, 2008. |
Final Office Action issued in co-related U.S. Appl. No. 11/274,486 dated Jan. 7, 2009. |
Non-Final Office Action issued in connection with co-related U.S. Appl. No. 11/274,486 dated Oct. 29, 2009. |
Non-Final Office Action issued in connection with co-related U.S. Appl. No. 11/274,486 dated Nov. 10, 2010. |
Final Office Action issued in connection with co-related U.S. Appl. No. 11/274,486 dated Apr. 1, 2011. |
Non-Final Office Action issued in connection with co-related U.S. Appl. No. 11/274,486 dated May 15, 2014. |
Non-Final Office Action issued in connection with co-related U.S. Appl. No. 11/274,486 dated Dec. 1, 2014. |
Final Office Action issued in connection with co-related U.S. Appl. No. 11/274,486 dated Mar. 20, 2015. |
Non-Final Office Action issued in connection with co-related U.S. Appl. No. 11/274,486 dated Jun. 13, 2016. |
Final Office Action issued in connection with co-related U.S. Appl. No. 11/274,486 dated Mar. 31, 2017. |
Non-Final Office Action issued in connection with co-related U.S. Appl. No. 11/692,634 dated Jul. 7, 2010. |
Final Office Action issued in connection with co-related U.S. Appl. No. 11/692,634 dated Nov. 10, 2010. |
Non-Final Office Action issued in connection with co-related U.S. Appl. No. 11/692,634 dated Sep. 15, 2011. |
Final Office Action issued in connection with co-related U.S. Appl. No. 11/692,634 dated Jan. 25, 2012. |
Non-Final Office Action issued in connection with co-related U.S. Appl. No. 11/692,634 dated Oct. 25, 2013. |
Notice of Allowance issued in connection with co-related U.S. Appl. No. 11/692,634 dated Mar. 27, 2014. |
Non-Final Office Action issued in co-related U.S. Appl. No. 12/783,819 dated Sep. 10, 2010. |
Final Rejection issued in connection with co-related U.S. Appl. No. 12/783,819 dated Feb. 18, 2011. |
Non-Final Rejection issued in connection with co-related U.S. Appl. No. 12/783,819 dated May 12, 2011. |
Final Rejection issued in connection with co-related U.S. Appl. No. 12/783,819 dated Oct. 19, 2011. |
Non-Final Rejection issued in connection with co-related U.S. Appl. No. 12/783,819 dated Jul. 26, 2012. |
Final Rejection issued in connection with co-related U.S. Appl. No. 12/783,819 dated Feb. 25, 2013. |
Non-Final Rejection issued in connection with co-related U.S. Appl. No. 12/783,819 dated Jun. 12, 2013. |
Final Rejection issued in connection with co-related U.S. Appl. No. 12/783,819 dated Jan. 2, 2014. |
Non-Final Rejection issued in connection with co-related U.S. Appl. No. 12/783,819 dated Apr. 11, 2014. |
Final Rejection issued in connection with co-related U.S. Appl. No. 12/783,819 dated Nov. 14, 2014. |
Non-Final Rejection issued in connection with co-related U.S. Appl. No. 12/783,819 dated Mar. 5, 2015. |
Final Rejection issued in connection with co-related U.S. Appl. No. 12/783,819 dated Aug. 26, 2015. |
Notice of Allowance issued in connection with co-related U.S. Appl. No. 12/783,819 dated Jul. 1, 2016. |
Non-Final Office Action issued in co-related U.S. Appl. No. 13/024,238 dated Aug. 15, 2011. |
Final Office Action issued in co-related U.S. Appl. No. 13/024,238 dated Mar. 6, 2012. |
Non-Final Office Action issued in co-related U.S. Appl. No. 13/024,238 dated Oct. 29, 2013. |
Notice of Allowance issued in co-related U.S. Appl. No. 13/024,238 dated Mar. 18, 2014. |
Canadian First Office Action issued in co-related Canadian Application No. 2,575,734 dated Dec. 22, 2011. |
Canadian Second Office Action issued in co-related Canadian Application No. 2,575,734 dated Nov. 19, 2013. |
Canadian Third Office Action issued in co-related Canadian Application No. 2,575,734 dated Mar. 23, 2015. |
Notice of Allowance issued in co-related Canadian Application No. 2,575,734 dated Oct. 24, 2016. |
Canadian Office Action issued in co-related Canadian Application No. 2,550,853 dated Dec. 8, 2011. |
Canadian Office Action issued in co-related Canadian Application No. 2,550,853 dated Jan. 31, 2014. |
Canadian Examiner's Report issued in co-related Application No. 2,550,853 dated Mar. 20, 2015. |
Canadian Office Action issued in co-related Canadian Application No. 2,550,853 dated Mar. 24, 2016. |
Canadian Office Action issued in co-related Canadian Application No. 2,550,853 dated Dec. 30, 2016. |
Canadian Office Action issued in co-related Canadian Application No. 2,550,853 dated Feb. 8, 2018. |
Canadian Office Action issued in co-related Canadian Application No. 2,550,853 dated Jan. 30, 2019. |
First Office Action issued in co-related Chinese Application No. 200580026931.8 dated Oct. 24, 2008. |
Second Office Action issued in co-related Chinese Application No. 200580026931.8 dated Jun. 12, 2009. |
Decision on Rejection issued in co-related Chinese Application No. 200580026931.8 dated Oct. 23, 2009. |
Notice on Acceptance for Request for Reexamination issued in co-related Chinese Application No. 200580026931.8 dated Sep. 26, 2010. |
Notice on Reexamination issued in Chinese Application No. 200580026931.8 dated Nov. 12, 2010. |
First Office Action issued in connection with co-related Chinese Application No. 20120031669.8 dated Jan. 17, 2014. |
Second Office Action issued in connection with co-related Chinese Application No. 20120031669.8 dated Sep. 22, 2014. |
Third Office Action issued in connection with co-related Chinese Application No. 20120031669.8 dated Apr. 3, 2015. |
Notice of Grant issued in connection with co-related Chinese Application No. 20120031669.8 dated Sep. 8, 2015. |
Supplementary European Search Report issued in co-related European Application No. 05784894.7 dated Dec. 28, 2010. |
Communication Pursuant to Rules 70(2) and 70a(2) EPC issued in co-related European Application No. 05784894.7 dated Jan. 11, 2014. |
Office Action issued in co-related European Application No. 05784894.7 dated Mar. 11, 2016. |
Office Action issued in co-related Indian Application No. 1087/DELNP/2007 dated Aug. 7, 2012. |
Refusal Decision issued in co-related Indian Application No. 1087/DELNP/2007 dated Dec. 17, 2018. |
Notice of Rejection issued in co-related Japanese Application No. 2007-525710 dated Dec. 18, 2009. |
Final Office Action issued in co-related Japanese Application No. 2007-525710 dated Apr. 20, 2010. |
Office Action issued in co-related Japanese Application No. 2007-525710 dated Sep. 3, 2010. |
Decision to Grant issued in co-related Japanese Application No. 2007-525710 dated Jan. 7, 2011. |
Preliminary Rejection issued in co-related Korean Application No. 10-2007-7005484 dated Apr. 29, 2008. |
Final Office Action issued in co-related Korean Application No. 10-2007-7005484 dated Nov. 24, 2008. |
Notice of Allowance issued in co-related Korean Application No. 10-2007-7005484 dated Mar. 26, 2009. |
Examination Report issued in co-related UK Application No. GB0613377.1 dated Nov. 29, 2006. |
Examination Report issued in co-related Uk Application No. GB0613377.1 dated Jul. 24, 2007. |
Charlwood, W., “AdWords bid price; Facts about AdSense.com—Publishers and Advertisers; Vickrey Auctions and AdWords; Vickrey Second Price Auctions”, located at http://www.factsaboutadsense.com/vickrey.htm, last accessed Feb. 24, 2009, 6 pages. |
Lee, K., “Overture's Auto Bid Shifts the Gap”, DMNews, Did-it.com, Aug. 22, 2002, located at http://www.dmnews.com/Overtures-Auto-Bid-Shifts-the-Gap/article/78442, last accessed on Feb. 25, 2009, 5 pages. |
Seda, C., “Perfecting Paid Search Engine Listings-Search”, Engine Watch (SEW), SearchEngineWatch.com, Oct. 17, 2002, located at http://www.searchenginewatch.com/2161001, last accessed on Feb. 25, 2009, 7 pages. |
Sherman, C., “A Closer Look at Overture's Auto Bid System”, Oct. 28, 2002, located at http://www.searchengingwatch.com/2161071/print, last accessed on Feb. 25, 2009, 3 pages. |
Submit Express, “Google reindexes/partners with Ask Jeeves, Overture's Auto Bidding Tool, Teoma Toolbar, FTC” Submit Express Newsletter #56, Jul. 19, 2002, located at http://www.submitexpress.com/newsletters/July_19_02.html, last accessed on Feb. 25, 2009, 9 pages. |
Garcia, E., “Matrix Tutorial 3: Eigenvalues and Eigenvectors; A Tutorial on Eigenvalues, Eigenvectors and Their Properties; Includes Step by Step How-To Calculations; An Introduction to Vector Itiration, the Power Method and the Deflation Method is Provided”, 2006, last accessed Oct. 17, 2011, 11 pages. |
Number | Date | Country | |
---|---|---|---|
20170103122 A1 | Apr 2017 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 10914722 | Aug 2004 | US |
Child | 12783819 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 12783819 | May 2010 | US |
Child | 15344200 | US |