US 7,844,488 B2Grant

Method of delivery, targeting, and measuring advertising over networks

Issue Date:2010-11-30

•17 Claims

•3 Drawing Sheets

Abstract

Methods and apparatuses for targeting the delivery of advertisements over a network such as the Internet are disclosed. Statistics are compiled on individual users and networks and the use of the advertisements is tracked to permit targeting of the advertisements of individual users. In response to requests from affiliated sites, an advertising server transmits to people accessing the page of a site an appropriate one of the advertisement based upon profiling of users and networks.

Metadata

Assignees

DoubleClick Inc.
Google Inc.

Inventors

Dwight Allen Merriman
Kevin Joseph O'Connor

Application Information

Application Number:US 10/798,342

Filing Date:2004-03-12

Priority Date:1996-10-29

Art Unit:3714

Classifications

IPC:

G06Q30/00

Patent Drawings (3 sheets)

Description

Cross-Reference to Related Applications

[0001] This is a divisional of U.S. patent application Ser. No. 10/254,923, filed on Sep. 26, 2002, pending, which is a continuation of U.S. patent application Ser. No. 09/293,463, filed on Apr. 15, 1999, abandoned, which is a continuation of U.S. patent application Ser. No. 08/738,634, filed on Oct. 29, 1996, issued as U.S. Pat. No. 5,948,061, currently in reissue under Reissue application Ser. No. 09/577,798, filed May 24, 2000.

Background of the Invention

[0002] 1. Area of the Art

[0003] This invention relates to methods of delivery of advertisements and measuring responses to those delivered advertisements and in particular relates to the targeting of advertisements delivered over networks such as the Internet.

[0004] 2. Description of the Prior Art

[0005] In advertising, it is considered highly desirable to target advertisements to the appropriate potential customer base, rather than to broadcast advertisements in general. It has long been known that, for example, advertisements for computers should generally not appear in magazines on gardening and, conversely, advertisements for gardening tools should not appear in magazines on computers. Similarly, advertisers have generally targeted their advertisements on television to programs appropriate for the desired customer base.

[0006] It has also long been known that an advertisement that is repeated too often will eventually become ignored by consumers. Therefore, an advertiser typically wishes to eliminate duplication and reach as many individuals in the advertiser's target group as possible.

[0007] The recent development of on-line networks, such as America On-Line, Compuserve, and the Internet, has led to “on-line” advertising. For example, on the Internet, often such on-line advertisements will appear on a web page, such as a banner on the top or the bottom of the page. When the user views a web page using a browser such as Internet Explorer 3 or Netscape 3, the banner appears at the appropriate location and the user may then try to find out more information regarding the advertisement by selecting the advertisement (clicking through on that banner) through the use of the mouse or other pointing device. This will cause a HTTP message to be generated by the browser using the information encapsulated in association with the banner to send a request for an object with a given URL address to a different appropriate web site to access, for example, the advertiser's home page.

[0008] Nonetheless, such advertising has had, so far, a poor rate of response because it is untargeted advertising. Thus, someone who is totally uninterested in computers other than they happen to be on the Internet, may continually see advertisements for computers. On the other hand, someone who is interested in computers may continually see advertisements for gardening tools when browsing through a particular web site. Thus it would be highly desirable to have a method of targeting the advertising to the appropriate user.

[0009] In addition, if a user of such computer networks is continuously exposed to the same advertisement, the response rate to the advertisement will generally decline. Therefore, it is highly desirable to have a system that controls the frequency of exposure of advertisements to particular users. In addition, it is also important for the advertisers to track response to the advertisements and to acquire as much information about those people responding to the advertisements for targeting those same people at later dates.

[0010] Therefore, it is a first object of this invention to provide targeting of advertising over networks such as the Internet. It is a second object of this invention to provide control over frequency of exposure to users for advertisements appearing on web pages over time. It is a third object of the invention to provide the capability to gather information about recipients of the advertisement.

Summary of the Invention

[0011] These and other objects of the invention are achieved by the disclosed system and methods. Information about networks and subnetworks is routinely collected. In addition, information about individual users is also gathered when users select (click on) different advertisements. Also, data is tracked on how often a given advertisement has been displayed, how often a given user has seen a given advertisement, and other information regarding the user and the frequency of the display of the advertisement

[0012] To effect such a capability, an advertising server process is provided as a node on the network. The various advertisements are stored on the network of the server and preferably on the server. When, for example, a user using a web browser accesses a web page that is affiliated with the advertising server process, the affiliated page's encoding includes an embedded reference to an object provided by the advertising server process. That causes the user's browser to contact the advertising server process to provide the advertising image or information that will appear on the accessed web page as displayed by the user's browser. Using the address information and/or other information passed by the browser for the user, including the page being accessed by the user, the advertising server process determines an appropriate advertisement to select for the particular user. In addition, the advertising server process will use information such as the number of times the user has seen various advertisements, how often the advertisement has been seen by any user and the start and stop date for the various advertisements to select which advertisement to transmit to the user's web page for display.

[0013] If the user decides to respond to the advertisement selected by the web server by clicking on the advertisement, the advertising server process logs that fact and to have more information about the given user. A derive profile process is used for compiling information on TCP/IP networks for use by the advertising server process. By compiling the information on networks and user selections, the advertising server process is able to compile information that can be used for targeting advertising.

Description of the Figures

[0014] FIG. 1 is diagram for explaining a first embodiment of the invention.

[0015] FIG. 2 is a diagram explaining the processes performed in the preferred embodiments.

[0016] FIGS. 3A, 3B and 3C are diagrams showing the basic structure of some of the databases kept by the advertising server.

Detailed Description of the Invention

[0017] The basic architecture of the network 10 comprises at least one affiliate web site 12, an advertisement (ad) server web site 19 and one or more individual advertiser's web sites 18. Affiliates are one or more entities that generally for a fee contract with the entity providing the advertisement server permit third party advertisements to be displayed on their web sites. When a user using a browser accesses or “visits” a web site of an affiliate, an advertisement provided by the advertisement server 19 will be superimposed on the display of the affiliate's web page displayed by the user's browser. Examples of appropriate affiliates include locator services, service providers, and entities that have popular web sites such as museums, movie studios, etc.

[0018] The basic operation of the system is as follows in the preferred embodiment. When a user browsing on the Internet accesses an affiliate's web site 12, the user's browser generates an HTTP message 20 to get the information for the desired web page. The affiliate's web site in response to the message 20 transmits one or more messages back 22 containing the information to be displayed by the user's browser. In addition, an advertising server process 19 will provide additional information comprising one or more objects such as banner advertisements to be displayed with the information provided from the affiliate web site. Normally, the computers supporting the browser, the affiliate web site and the advertising server process will be at entirely different nodes on the Internet. Upon clicking through or otherwise selecting the advertisement object, which may be an image such as an advertisement banner, an icon, or a video or an audio clip, the browser ends up being connected to the advertiser's server or web site 18 for that advertisement object.

[0019] In FIG. 1, a user operates a web browser, such as Netscape or Microsoft Internet Explorer, on a computer or PDA or other Internet capable device 16 to generate through the hypertext transfer protocol (HTTP) 14 a request 20 to any one of preferably a plurality of affiliate web sites 12. The affiliate web site sends one or more messages back 22 using the same protocol. Those messages 22 preferably contain all of the information available at the particular web site 12 for the requested page to be displayed by the user's browser 16 except for one or more advertising objects such as banner advertisements. These objects preferably do not reside on the affiliate's web server. Instead, the affiliate's web server sends back a link including an IP address for a node running an advertiser server process 19 as well as information about the page on which the advertisement will be displayed. The link by way of example may be a hypertext markup language (HTML) <img> tag, referring to, for example, an inline image such as a banner. The user's browser 16 then transmits a message 23 using the received IP address to access such an object indicated by the HTML tag from the advertisement server 19. Included in each message 23 typically to the advertising server 19 are: (i) the user's IP address, (ii) a cookie if the browser 16 is cookie enabled and stores cookie information, (iii) a substring key indicating the page in which the advertisement to be provided from the server is to be embedded, and (iv) MIME header information indicating the browser type and version, the operating system of the computer on which the browser is operating and the proxy server type. Upon receiving the request in the message 23, the advertising server process 19 determines which advertisement or other object to provide to user's browser and transmits the messages 24 containing the object such as a banner advertisement to the user's browser 16 using the HTTP protocol. Preferably contained within the HTTP message is a unique identifier for the advertiser's web page appropriate for the advertisement. That advertisement object is then displayed on the image created by the web user's browser as a composite of the received affiliate's web page plus the object transmitted back by the advertising web server.

[0020] As part of the “click through” process, when the user clicks on the banner or other advertising object displayed by the user's browser 16, the user's browser again transmits a message to the ad server. The ad server notes the address of the computer of the browser (or any other identifier such as a cookie or a digital signature) that generated the message 23 and transmits back the URL of the advertiser's web page so that the user's web browser 16 generates a message 26 to contact the advertiser's web site. 18. The ad server process 19 also notes that a “click through” for an advertisement has occurred and updates the various databases in the manner described below. In the above scenario for the click through process, the ad server process must remember which advertisement was sent to the user's browser in order to know where to redirect the user's browser.

[0021] While in the above embodiments, the user is a computer on an IP network using a browser, the affiliate web sites are web pages of affiliates located somewhere on the Internet and the ad server is a particular node on the Internet, other setups are also possible. The affiliates may be ISP's or may be actual dedicated web servers and the users may be an entire network instead of an individual browsing on a single computer with a browser.

[0022] FIG. 2 shows the ad server architecture. The ad server, which may comprise one or more servers uses a database 54 that will be described below and performs reporting processes 59, management processes 58, derivation of profile processes 52 and advertisement processes 19. The derive profile process 52 is how the advertisement server gathers information about individual users or TCP/IP networks for individual users. Advertisements, which may be advertisement banners are stored within the ad server process 19 as part of the advertising server process 19 and are periodically updated and refreshed. The advertisement server process 19 is used for responding to requests from advertisements provided by the user's as described above. The management process 58 is used for updating the various advertisements and overall control of the advertising server process 19 and also permits the advertisers to interface with the database to obtain up to the date reports on the placement of the advertisements. The report process 59 is used for generating online reports about the success rate of the advertisement and statistics on the users that are viewing and clicking through on various advertisements and also updating the counters in the database that store how often an advertisement has been displayed.

[0023] The basic database structure is shown in FIG. 3. For each user identified by the system as shown in FIG. 3A, a user identification, IP address, domain type, time zone, location of the user, standard industrial code for the user's network, the particular advertisements seen and the number of times each such advertisement is seen, the advertisements that were selected or “clicked on” and the pages on which the various users' advertisements were seen is collected. By using the information such as which advertisements a user has expressed interest in and which pages the user was viewing when the user clicked through along with other information, targeted Internet advertising is possible.

[0024] FIG. 3B shows a database structure for the advertisements. Included in the information for an advertisement are an identifier for the advertisement, the start date for the advertisement being carried, the last date the advertisement is to be carried, the total number of people who have viewed the advertisements, the target or the minimum number of times the advertisement is to be viewed, acceptable viewers by their web site's SICS (Standard Industry Codes), clicked through and pages that the advertisements are seen on.

[0025] Also, as noted above, to enhance the process of identifying information about various users, information on domains or networks is also tracked. This information includes the domain name and type (e.g., military, government, commerce, foreign countries), the IP address, the standard industrial code, the time zone and the address as shown in FIG. 3C. This information can be used in developing information about users. Through the use of these three databases and other appropriate databases that may be kept, the various processes of the advertising server process 19 are performed.

Advertising Server Processes 19

[0026] In response to an incoming message to the advertising server process 19, the advertising server processes 19 first attempts to identify the user in FIG. 2. This can be accomplished by at least one of two means. First, any incoming request for an image or a multimedia object is examined to determined the IP address of the requesting browser. The advertising server then notes whether a cookie was received in the MIME heading of the request. From these two pieces of information, a user identification is determined. If a cookie was detected, then the cookie contains the user's identification number that can be accessed in the database. If the user's browser is cookie enabled but no cookie is detected, then the request is from a new user so a user identification must be assigned to the user and that user's new identification number will be transmitted back to the users browser along with a write cookie instruction that causes the browser to write a cookie containing that unique identification number on the user's local drive for future accesses to affiliate sites. The cookie instruction is transmitted back with the advertisement messages 24. Alternatively, instead of using cookies, digital signatures or certificates or log ins uniquely identifying the user accessing the affiliate page may be used.

[0027] If the user's browser does not support cookies, the advertising server process looks up the user's IP address in a table that stores identification numbers that correspond to IP addresses for the users who have previously contacted the advertising server process. If the IP address is not found in the table, then the user is a new user and is assigned an unused identification number. Also, for each new user, that user's identification number will be marked for further processing under the derive profile process 52 described below. Also, if the domain for the new user has not previously been processed in the domain profile process, it may not be possible to target the advertisement for the new user and rather the new user should be shown a generic advertisement. Also, for new users, a promotional advertisement may be shown to get the new user to provide information about him or herself and his or her employer.

[0028] If the user is an existing user, the ad server 19 obtains from a database all of the information known about the user including the user's geographic location, the domain type (commercial educational, governmental, the Internet service provided), the organization type where the user works (for example a SIC code), the company size, the number of employees in that company, the particular types of advertisements that the user has clicked on by SIC or other appropriate coding and the number of times that the user has been exposed to each advertisement currently in the system as described in FIG. 3A. Also, the relative time of day for the user is calculated based upon either the user's country code or the user's IP access provider or the location of their domain.

[0029] Each advertisement along with a table of the targeting profile criteria for the advertisement and other data regarding the advertisement currently available is stored in a database such as shown in FIG. 3B. The actual advertising object, which may be a banner image in a GIF or JPEG file format, an icon for an audio or video clip or some other object is kept as part of the advertising server process. This information may include targeted consumers by SIC, country, organization type and type of advertisements previously selected by the user. For any of the advertisements currently provided for which there is a match (for example there may be several advertisements targeted at people interested in computers), the next step is to determine which of the advertisements for which there is a match should be selected.

[0030] The preferred embodiment also includes determining which advertising object should be selected if two or more advertising object have criteria matching the user. selecting from the matched advertisements by determining how often the particular user has been exposed to the given advertisement. For each user, data is kept about the number of times that a user has seen a given advertisement based upon the user ID. For each advertisement where the user matches the criteria, if the number of times that the user has seen the advertisement is less than a predetermined threshold, the advertisement is retained as one of the possible matches. If the number of times that the user has seen a given advertisement exceeds the threshold, the advertisement is discarded as a possible candidate for transmitting back to the user.

[0031] From the advertisements for which the user matches the criteria and for which the user has seen the advertisement less than the threshold, any of number of algorithms may be used to select the particular advertisement to transmit back to the user. In an embodiment, the formula used is based upon a satisfaction index (SI) according to the following formula:

[0032]

SI = \frac{n}{N} * \frac{end - start}{now - start}

Where:

- [0033] n: the number of times the particular advertisement has been viewed by anyone
- [0034] N: the number of times the advertisement is to be see by anyone
- [0035] end-start: the total number of days that the advertisement is scheduled to run
- [0036] now-start: the number of days that the advertisement has run to date

[0037] The satisfaction index (SI) is 1.0 when the advertisement is on schedule. If the advertisement is running behind schedule (i.e., the current rate of display means that the advertisement will not be viewed the targeted number of times by the end date so that the SI is less than 1.0) while if the SI is greater than 1.0, the advertisement is running ahead of schedule. Therefore, the advertisement that is to be selected for viewing is the one that has a matched profile and has the smallest SI. Upon selecting the advertisement, the selected advertisement object is then transmitted to the user's browser over the Internet by transmitting the GIF stored in RAM in one or more messages.

[0038] After delivery of the advertisement to the user, additional processing needs to be done both for tracking the exposure of the advertisement and for having more information about the user. First, the system stores the fact that the advertisement was sent to the user by storing that information in the database based upon the user ID. This information is used for processing the user's response to the advertisement when the user “clicks” on the advertisement. Also, the advertising processor updates the advertisements satisfaction index and logs the advertisement delivery for providing reports. Also, if the advertisement that has been sent has a limit on the number of times that the advertisement can be sent, the count of the number of times that the advertisement has been transmitted is incremented. This limit can be the overall limit for the number of times that the advertisement is viewed and/or the limit that any specific user can view the advertisement. If the limit on the number of times the advertisement can be sent is reached, then the particular advertisement is removed from the list of those that can be transmitted. In addition, even if an advertisement has not been transmitted recently, the SI is updated to reflect the passage of time.

[0039] If the user then decides that he wants to respond to the advertisement and then clicks on the advertisement, the advertisement server 19 receives an HTTP request 23 for a click through which it will recognize by receiving the same IP address (and optionally, the user ID specified by the cookie, digital signature or certificate or log in identification) in the request from the same affiliate's web page within a predetermined period. Since the advertisement server previously recorded which advertisement was sent to that IP address, it sends the redirect message causing the user's browser to receive the URL for the advertiser's web site based upon data stored in the server. In addition, the server logs that the advertisement was clicked through, which user selected the advertisement based upon the IP address, and the page on which the advertisement was seen based upon the click through. This information can then be logged in later reporting processes 59.

[0040] As an alternative to using a satisfaction index, the selection of the particular advertisement object to be sent back to the viewer's browser by the advertising server process 19 can be made by different criteria. For example, models can be created to maximize the likelihood of a click through. Such models for maximizing the likelihood of a click through may be based upon empirically gathered information about either types of advertisements or individual advertisements actually on the system correlated to the compiled information on a user or the user's network and the specific page through which the user is accessing the advertising server process 19.

Derivative Profile Process 52

[0041] In addition, as part of the profiling process for gathering information about users and IP addresses needs to be done. First, appropriate “networks” need to be identified based upon the TCP/IP network address of the user. Periodically, the derive profiles process searches the user database for the address of additional users that have addresses for unknown networks, indicating that they are new users. Then the server does a reverse domain name search to locate the domain name of the user. The server also queries Internet Whols databases to find information about the network, which will often include the domain name.

[0042] Alternatively, a reverse form of look up can be used independent of people accessing the network. When a domain is discovered, the server will check common DNS names for the name, such as those starting with “www” and “ftp”. These resolve to IP addresses in most cases. From the IP addresses, the network number can be extracted and if the network does not yet have a domain name associated with the network number or address, the new domain associated with the network. A reverse domain name look up (A Whois lookup) will then usually provide the name, address and phone number of the organization, thereby providing the geographic location and the time zone of the network. Once the domain name is acquired, the server will determine whether the domain is an educational, military, governmental network and for non-U.S. based networks what country the network is located in through the extension.

[0043] However, it should be noted that some networks cover broad geographic areas and that further checking needs to be done to ensure that the data may be inaccurate. This can be done by performing a trace route operation to trace the network topology back to the network being examined. If the last two or three nodes on the trace show as being from a given region, the chances are high that the specific user on a network is located in that geographic area. Thus, reverse traces can be used to confirm location with a database for geographic locations. By checking telephone directories and other sources, the specific location for such users may be found by looking up the locations where the owner of the domain name has facilities and using the one closest to the outcome of the trace back step If the information for a given user is different than the location of the domain based upon the trace back, it is this address and location information that is then used.

[0044] Further for each domain that is found, a determination must be made as to whether the domain is an Internet Service Provider (ISP). A list of domains that are ISP's is compiled manually. For any user having a domain name of an ISP, the user is presumed to be an individual and so only information relating to that individual are used for the profiling process.

Reporting Process

[0045] The reporting process uses standard database techniques for generating any desired reports. For example, reports showing the number of viewings and click throughs of various advertisements may be generated along with reports showing the click through rates relative to the matching criteria. Also, reports on the SI can be readily generated.

[0046] In addition to using the domain profiling process and logging advertisement clicked on by individual users and the pages being accessed by users of affiliate web sites, in addition surveying may be used. Further, for those survey respondents who are responding for non-ISP users discussed above, the results of the survey can be attributed to others on the same network. This provides further information for targeting the display of the advertisements.

[0047] Of course, those of skill in the field will understand that the disclosed techniques need not just be confined to Internet advertising but will work on other communication networks and private on line services such as CompuServe and America On Line. In addition, while specific user and domain profile information and matching criteria are discussed, it will be obvious to those of ordinary skill in the field that the specific type of user and domain name information profiled and used as matching criteria may include other or different criteria. In addition, while the specific examples are for IP networks, the same concepts can be applied to virtual LAN's such that a VLAN is the equivalent of a domain or on IPX based protocols or other network protocols.

[0048] Still further, rather than using cookies or IP addresses or other network addresses to identify the users, digital signatures or certificates may be used. In addition, a log in technique may be used whereby when users first access an affiliated web site, the user is assigned through a log in procedure a unique identifier and a log in name. When the user subsequently accesses either the same or a different affiliated web site, the user logs in using the unique identifier, thereby ensuring that users can be identified notwithstanding proxy servers or different users using the same computer.

[0049] Still further, those of ordinary skill in the field will also understand that while the advertising server, the affiliate web site and the advertiser's web site are described as being in different geographic locations, that is not required. Still further, while the advertising server process, reporting process, derive profile process and management process are described as being implemented on one computer platform performing all of the above described functions, it is readily understood by those of skill that any or all of these functions may be implemented on one or more different computers and further that these processes may be performed at different nodes on the network.

Claims

We claim:

1. A method for advertising, comprising:

receiving, by an advertising server, an advertisement request from a user node, wherein said advertisement request is automatically transmitted based upon a link sent from an affiliate node to said user node in response to a content request sent from said user node to said affiliate node; and

selecting, in response to said advertisement request, an advertisement for delivery to the user node based upon stored information about said user node,

wherein selecting an advertisement includes:

determining whether selection criteria associated with advertisements are satisfied based upon the stored information; and

calculating, if the selection criteria associated with more than one advertisement are satisfied, a satisfaction index for each advertisement; and

selecting the advertisement with the lowest satisfaction index,

wherein the satisfaction index for an advertisement is at least one of:

directly proportional to the number of times the advertisement has been sent to a user node and the total amount of time over which the advertisement is permitted to be sent to a user node, and

inversely proportional to the amount of time expired since the advertisement was first permitted to be sent to a user node and inversely proportional to the maximum number of times the advertisement is permitted to be sent to a user node.

2. The method of claim 1, wherein selecting an advertisement based upon stored information about said user node comprises selecting an advertisement based upon a prior content request sent from said user node to an affiliate node.

3. The method of claim 1, wherein selecting an advertisement based upon stored information about said user node comprises selecting an advertisement based upon a prior selection of an advertisement for said user node.

4. The method of claim 1, wherein selecting an advertisement based upon stored information about said user node comprises selecting an advertisement based upon a prior advertisement request from said user node.

5. The method of claim 1, wherein selecting an advertisement based upon stored information about said user node comprises selecting an advertisement based upon information in a cookie associated with said user node.

6. The method of claim 1, wherein selecting an advertisement based upon stored information about said user node comprises selecting an advertisement based upon at least one of the network address of said user node, the domain type of said user node, the time zone of said user node, the geographical location of said user node, and an industry code.

7. The method of claim 1, wherein selecting an advertisement based upon stored information about said user node comprises selecting an advertisement based upon the number of times an advertisement has been sent to said user node.

8. The method of claim 1, wherein selecting an advertisement is further based upon at least one of a browser type, a browser version, an operating system type, and a proxy server, each associated with said user node.

9. The method of claim 1, wherein said advertisement request includes an Internet Protocol address associated with said user node.

10. The method of claim 9, further comprising performing a reverse domain name lookup based upon said Internet Protocol address, and selecting said advertisement based upon the results of said reverse domain name lookup.

11. The method of claim 10, wherein said reverse domain name lookup includes a whois search.

12. The method of claim 10, further comprising performing a trace route operation, and selecting said advertisement based upon the results of said trace route operation.

13. The method of claim 1, further comprising sending said selected advertisement to said user node for display.

14. The method of claim 13, further comprising receiving from said user node a click through request for information about the advertiser associated with said selected advertisement.

15. The method of claim 14, further comprising sending a network address for said advertiser to said user node in response to said click-though request.

16. The method of claim 14, wherein said stored information includes information about a prior click-through request received from said user node.

17. A method for advertising, comprising:

receiving, by an advertising server, an advertisement request from a user node, wherein the advertisement request is automatically transmitted based upon a link sent from an affiliate node to the user node in response to a content request sent from the user node to the affiliate node; and

selecting, in response to the advertisement request, an advertisement for delivery to the user node based upon stored information about the user node,

wherein selecting an advertisement includes:

determining whether selection criteria associated with advertisements are satisfied based upon the stored information; and

selecting, if the selection criteria associated with more than one advertisement are satisfied, an advertisement from among the more than one advertisement an advertisement based on the selected advertisement having one or more of a lesser amount of time remaining in which the advertisement can be selected for delivery, a greater number of impressions of the advertisement remaining to be delivered, a smaller ratio of the number of times the advertisement has been delivered to any user to the total number of impressions of the advertisement scheduled to be delivered, and a greater ratio of the total amount of time in which the advertisement can be delivered to an amount of time expired since the advertisement has become available for delivery.

Patent Citations (219)

Patent	Date	Inventor	Cited By
US4602279(A)	1986-07-01	Freeman	Applicant
US4703423(A)	1987-10-01	Bado et al.	Applicant
US4775935(A)	1988-10-01	Yourick	Applicant
US4789235(A)	1988-12-01	Borah et al.	Applicant
US4850007(A)	1989-07-01	Marino et al.	Applicant
US4870579(A)	1989-09-01	Hey	Applicant
US4996642(A)	1991-02-01	Hey	Applicant
US5027400(A)	1991-06-01	Baji et al.	Applicant
US5099422(A)	1992-03-01	Foresman et al.	Applicant
US5105184(A)	1992-04-01	Pirani et al.	Applicant
US5155591(A)	1992-10-01	Wachob	Applicant
US5166866(A)	1992-11-01	Kim et al.	Applicant
US5191410(A)	1993-03-01	McCalley et al.	Applicant
US5220501(A)	1993-06-01	Lawlor et al.	Applicant
US5253341(A)	1993-10-01	Rozmanith et al.	Applicant
US5260778(A)	1993-11-01	Kauffman et al.	Applicant
US5261094(A)	1993-11-01	Everson et al.	Applicant
US5283731(A)	1994-02-01	Lalonde et al.	Applicant
US5305195(A)	1994-04-01	Murphy	Applicant
US5347632(A)	1994-09-01	Filepp et al.	Applicant
US5355327(A)	1994-10-01	Stent et al.	Applicant
US5361393(A)	1994-11-01	Rossillo	Applicant
US5377354(A)	1994-12-01	Scannell et al.	Applicant
US5412416(A)	1995-05-01	Nemirofsky	Applicant
US5442771(A)	1995-08-01	Filepp et al.	Applicant
US5446891(A)	1995-08-01	Kaplan et al.	Applicant
US5446919(A)	1995-08-01	Wilkins	Applicant
US5448625(A)	1995-09-01	Lederman	Applicant
US5459656(A)	1995-10-01	Fields et al.	Applicant
US5469206(A)	1995-11-01	Strubbe et al.	Applicant
US5475819(A)	1995-12-01	Miller et al.	Applicant
US5477451(A)	1995-12-01	Brown et al.	Applicant
US5499046(A)	1996-03-01	Schiller et al.	Applicant
US5504744(A)	1996-04-01	Adams et al.	Applicant
US5504894(A)	1996-04-01	Ferguson et al.	Applicant
US5515098(A)	1996-05-01	Carles	Applicant
US5515270(A)	1996-05-01	Weinblatt	Applicant
US5537542(A)	1996-07-01	Eilert et al.	Applicant
US5550746(A)	1996-08-01	Jacobs	Applicant
US5559548(A)	1996-09-01	Davis et al.	Applicant
US5566353(A)	1996-10-01	Cho et al.	Applicant
US5568612(A)	1996-10-01	Barrett et al.	Applicant
US5572643(A)	1996-11-01	Judson	Examiner
US5584025(A)	1996-12-01	Keithley et al.	Applicant
US5594910(A)	1997-01-01	Filepp et al.	Applicant
US5598536(A)	1997-01-01	Slaughter, III et al.	Applicant
US5600364(A)	1997-02-01	Hendricks et al.	Applicant
US5621812(A)	1997-04-01	Deaton et al.	Applicant
US5636346(A)	1997-06-01	Saxe	Applicant
US5638457(A)	1997-06-01	Deaton et al.	Applicant
US5649114(A)	1997-07-01	Deaton et al.	Applicant
US5675662(A)	1997-10-01	Deaton et al.	Applicant
US5692132(A)	1997-11-01	Hogan	Applicant
US5696965(A)	1997-12-01	Dedrick	Applicant
US5704017(A)	1997-12-01	Heckerman et al.	Applicant
US5704018(A)	1997-12-01	Heckerman et al.	Applicant
US5708780(A)	1998-01-01	Levergood et al.	Applicant
US5710887(A)	1998-01-01	Chelliah et al.	Applicant
US5712979(A)	1998-01-01	Graber et al.	Applicant
US5717860(A)	1998-02-01	Graber et al.	Applicant
US5717923(A)	1998-02-01	Dedrick	Applicant
US5721827(A)	1998-02-01	Logan et al.	Applicant
US5724424(A)	1998-03-01	Gifford	Applicant
US5724521(A)	1998-03-01	Dedrick	Applicant
US5727156(A)	1998-03-01	Herr-Hoyman et al.	Applicant
US5734720(A)	1998-03-01	Salganicoff	Applicant
US5734828(A)	1998-03-01	Pendse et al.	Applicant
US5737619(A)	1998-04-01	Judson	Applicant
US5740252(A)	1998-04-01	Minor et al.	Applicant
US5740549(A)	1998-04-01	Reilly et al.	Examiner
US5745681(A)	1998-04-01	Levine et al.	Applicant
US5751956(A)	1998-05-01	Kirsch	Applicant
US5752022(A)	1998-05-01	Chiu et al.	Applicant
US5752238(A)	1998-05-01	Dedrick	Applicant
US5754772(A)	1998-05-01	Leaf	Applicant
US5754938(A)	1998-05-01	Herz et al.	Applicant
US5754939(A)	1998-05-01	Herz et al.	Applicant
US5757917(A)	1998-05-01	Rose et al.	Applicant
US5761601(A)	1998-06-01	Nemirofsky et al.	Applicant
US5768521(A)	1998-06-01	Dedrick	Applicant
US5774170(A)	1998-06-01	Hite et al.	Applicant
US5778367(A)	1998-07-01	Wesinger, Jr. et al.	Applicant
US5781894(A)	1998-07-01	Petrecca et al.	Applicant
US5787253(A)	1998-07-01	McCreery et al.	Applicant
US5790426(A)	1998-08-01	Robinson	Applicant
US5790935(A)	1998-08-01	Payton	Applicant
US5794210(A)	1998-08-01	Goldhaber et al.	Examiner
US5796945(A)	1998-08-01	Tarabella	Applicant
US5796952(A)	1998-08-01	Davis et al.	Applicant
US5809242(A)	1998-09-01	Shaw et al.	Applicant
US5812769(A)	1998-09-01	Graber et al.	Applicant
US5812776(A)	1998-09-01	Gifford	Applicant
US5815148(A)	1998-09-01	Tanaka	Applicant
US5819285(A)	1998-10-01	Damico et al.	Applicant
US5838790(A)	1998-11-01	McAuliffe et al.	Applicant
US5842199(A)	1998-11-01	Miller et al.	Applicant
US5848396(A)	1998-12-01	Gerace	Applicant
US5848397(A)	1998-12-01	Marsh et al.	Applicant
US5855008(A)	1998-12-01	Goldhaber et al.	Applicant
US5870724(A)	1999-02-01	Lawlor et al.	Applicant
US5873068(A)	1999-02-01	Beaumont et al.	Applicant
US5893075(A)	1999-04-01	Plainfield et al.	Applicant
US5913040(A)	1999-06-01	Rakavy et al.	Applicant
US5918014(A)	1999-06-01	Robinson	Applicant
US5933811(A)	1999-08-01	Angles et al.	Applicant
US5933827(A)	1999-08-01	Cole et al.	Applicant
US5937162(A)	1999-08-01	Funk et al.	Examiner
US5937392(A)	1999-08-01	Alberts	Applicant
US5946646(A)	1999-08-01	Schena et al.	Applicant
US5948061(A)	1999-09-01	Merriman et al.	Applicant
US5950173(A)	1999-09-01	Perkowski	Applicant
US5956024(A)	1999-09-01	Strickland et al.	Applicant
US5960409(A)	1999-09-01	Wexler	Examiner
US5960429(A)	1999-09-01	Peercy et al.	Applicant
US5963915(A)	1999-10-01	Kirsch	Examiner
US5990927(A)	1999-11-01	Hendricks et al.	Applicant
US5999912(A)	1999-12-01	Wodarz et al.	Applicant
US6002393(A)	1999-12-01	Hite et al.	Applicant
US6005566(A)	1999-12-01	Jones et al.	Applicant
US6005567(A)	1999-12-01	Nielsen	Applicant
US6006197(A)	1999-12-01	D'Eon et al.	Applicant
US6006252(A)	1999-12-01	Wolfe	Applicant
US6016509(A)	2000-01-01	Dedrick	Applicant
US6020887(A)	2000-02-01	Loring et al.	Applicant
US6026368(A)	2000-02-01	Brown et al.	Applicant
US6029141(A)	2000-02-01	Bezos et al.	Examiner
US6029195(A)	2000-02-01	Herz	Applicant
US6049777(A)	2000-04-01	Sheena et al.	Applicant
US6049878(A)	2000-04-01	Caronni et al.	Applicant
US6052554(A)	2000-04-01	Hendricks et al.	Applicant
US6061659(A)	2000-05-01	Murray	Applicant
US6119101(A)	2000-09-01	Peckover	Applicant
US6182050(B1)	2001-01-01	Ballard	Applicant
US6185586(B1)	2001-02-01	Judson	Applicant
US6223215(B1)	2001-04-01	Hunt et al.	Applicant
US6247047(B1)	2001-06-01	Wolff	Applicant
US6269361(B1)	2001-07-01	Davis et al.	Examiner
US6434614(B1)	2002-08-01	Blumenau	Applicant
US6466970(B1)	2002-10-01	Lee et al.	Applicant
US6615251(B1)	2003-09-01	Klug et al.	Applicant
US6718551(B1)	2004-04-01	Swix et al.	Examiner
US6757662(B1)	2004-06-01	Greenwald et al.	Examiner
US6757710(B2)	2004-06-01	Reed	Applicant
US6782369(B1)	2004-08-01	Carrott	Examiner
US7039599(B2)	2006-05-01	Merriman et al.	Applicant
US7136853(B1)	2006-11-01	Kohda et al.	Applicant
US7496943(B1)	2009-02-01	Goldberg et al.	Examiner
US2001/0037205(A1)	2001-11-01	Joao	Examiner
US2001/0056374(A1)	2001-12-01	Joao	Examiner
US2002/0013785(A1)	2002-01-01	Miyazaki et al.	Examiner
US2002/0019831(A1)	2002-02-01	Wade	Examiner
US2002/0046118(A1)	2002-04-01	Minte	Examiner
US2002/0082923(A1)	2002-06-01	Merriman et al.	Applicant
US2002/0099600(A1)	2002-07-01	Merriman et al.	Examiner
US2002/0103698(A1)	2002-08-01	Cantrell	Examiner
US2002/0120507(A1)	2002-08-01	Chanos et al.	Applicant
US2003/0023489(A1)	2003-01-01	McGuire et al.	Examiner
US2005/0033855(A1)	2005-02-01	Moradi et al.	Applicant
US2005/0197164(A1)	2005-09-01	Chan	Applicant
US2008/0276271(A1)	2008-11-01	Anderson et al.	Examiner
US2009/0044246(A1)	2009-02-01	Sheehan et al.	Examiner
DE19528911(A1)	1997-02-01		Applicant
EP216535(A2)	1987-04-01		Applicant
EP216535(A3)	1987-04-01		Applicant
EP355697(A2)	1990-02-01		Applicant
EP355697(A3)	1990-02-01		Applicant
EP355697(B1)	1990-02-01		Applicant
EP643359(A2)	1995-03-01		Applicant
EP643359(A3)	1995-03-01		Applicant
EP749081(A1)	1996-12-01		Applicant
EP875843(A1)	1997-11-01		Applicant
EP814419(A2)	1997-12-01		Applicant
EP818742(A1)	1998-01-01		Applicant
EP834822(A2)	1998-04-01		Applicant
EP834822(A3)	1998-04-01		Applicant
EP837407(A1)	1998-04-01		Applicant
EP838769(A2)	1998-04-01		Applicant
EP849689(A2)	1998-06-01		Applicant
EP849689(A3)	1998-06-01		Applicant
EP864990(A2)	1998-09-01		Applicant
EP864990(A3)	1998-09-01		Applicant
EP869448(A1)	1998-10-01		Applicant
EP749081(B1)	1998-11-01		Applicant
EP877314(A1)	1998-11-01		Applicant
EP897158(A1)	1999-02-01		Applicant
EP897158(A4)	1999-02-01		Applicant
JPH5143653(A)	1993-06-01		Applicant
JP9091215	1997-04-01		Applicant
JP10049591(A)	1998-02-01		Applicant
JP10320336	1998-12-01		Applicant
WO84/01382(A1)	1984-04-01		Applicant
WO84/01382(A4)	1984-10-01		Applicant
WO84/01382(B1)	1984-10-01		Applicant
WO93/16443(A1)	1993-08-01		Applicant
WO93/19427(A1)	1993-09-01		Applicant
WO94/23383(A1)	1994-10-01		Applicant
WO95/12176(A2)	1995-05-01		Applicant
WO95/12176(A3)	1995-05-01		Applicant
WO95/12176(A4)	1995-05-01		Applicant
WO95/13587(A1)	1995-05-01		Applicant
WO95/16971(A1)	1995-06-01		Applicant
WO95/16971(A4)	1995-06-01		Applicant
WO96/31848(A2)	1996-09-01		Applicant
WO96/31848(A3)	1996-09-01		Applicant
WO96/30864(A1)	1996-10-01		Applicant
WO96/36926(A1)	1996-11-01		Applicant
WO96/38796(A1)	1996-12-01		Applicant
WO96/39668(A1)	1996-12-01		Applicant
WO97/07656(A2)	1997-03-01		Applicant
WO97/07656(A3)	1997-03-01		Applicant
WO97/21183(A1)	1997-06-01		Applicant
WO97/41673(A2)	1997-11-01		Applicant
WO97/41673(A3)	1997-11-01		Applicant
WO96/38796(B1)	1998-03-01		Applicant
WO98/34189(A1)	1998-09-01		Applicant
WO98/57285(A1)	1998-12-01		Applicant
WO98/57275(A2)	1998-12-01		Applicant
WO98/57275(A3)	1998-12-01		Applicant
WO1/65747(A1)	2001-09-01		Applicant

Non-Patent Literature (209)

17625888; Java and Blackbird: extending the Web . . . ; Seybold Reoport on Publishing Systems; Oct. 23, 1995.Applicant
17497026; Look who's surfing . . . ; Schurr; PC Week; Oct. 30, 1995.Applicant
17594025; HotWired and Neilsem team to verify usage data; Electronic Marketplace Report; Jul. 4, 1995.Applicant
17225819; Write once, publish many times; Ratcliffe; Digital Media; Aug. 7, 1995.Applicant
17189959; Product View seeks funding for 3Q launch of ad-supported . . . ; Electronic Marketplace Report; May 16, 1995.Applicant
17244186; Free E-Mail with Postage Stamp “Ads”; Newsbytes; Jul. 3, 1995.Applicant
CWK19951009S0006; Search-engine advertising; Frook; Communications Week; Nov. 9, 1995.Applicant
www5conf.inria.fr; Ubiquitous Advertising on the WWW; Kohda et al; Fifth International WWW Conference; May 6-10, 1996.Applicant
Bounty Quest home page article titled DoubleClick Bounty Paid Ad Pioneer Turned Online Porn Mogul Wins $10,000; (<http://www.bountyquestcom/>; printed on Mar. 9, 2001).Applicant
Bounty Quest Web page displaying article titled Bounty Collected Double Click Banner Ad Patent; (http://www.bountyquest.com/bounties/displayBounty.php?bountyName=1019 ; printed on Mar. 9, 2001).Applicant
Bounty Quest Web page displaying article titled Digital Porn Mogul Wins Silver Bullet Award; (http://www.bountyquest.com/winner/bschuster.htm; printed on Mar, 9, 2001).Applicant
Bounty Quest Web page displaying article titled DoubleClick Piror Art; (http://www.bountyquest.com/patentinfo/doucleclickart. htm; printed on Mar, 9, 2001).Applicant
Business Plan posted on Bounty Quest Website titled Summary of Proposed Business Activities for the World Wide Internet Network (WWIN); (http://www.bountyquest.com/images/doubleclickPage9.gif; printed on Mar. 9, 2001).Applicant
Sales Literature posted on Bounty Quest Website titled What You Get with WWIN; (http://bountyquest.com/images/doubleclickGetgif; printed on Mar. 9, 2001).Applicant
CNET Press Release titled About CNET; (http://www.canada.cnet.com/aboutcnet/0-13613-7-808022.html; printed on Mar. 9, 2001).Applicant
ADMedium Newsletter linked from Bounty Quest Website; (http://uts.cc.utexas.edu/tecas/nl9—2—96.html; printed on Apr. 4, 2001).Applicant
Booker, Ellis “Seeing a Gap, A Palo Alto Startup Will Debut Advertising Server for the Net”, Web Week, v.2 iss. 2. Available online at http://internetworld.com. Feb. 1996.Applicant
Metcalf, Bob “From the Ether”, InfoWorld, v.18 iss.3. Available at http://infoworld.com, Aug. 1996.Applicant
NetGravity AdServer 2.0 Announcement. Available at http://netgravity.com, Oct. 1996.Applicant
Kohda Yet al: Ubiquitous advertising on the WWW: Merging Advertising on the Browser, Computer Networks and ISDN Systems, vol. 28, No. 11, May 1996, pp. 1493-1499.Applicant
Cashing in: The rush is on to buy and sell on the Internet, Interactive Media & Marketing, Adv. Age, p. 11, Dec. 19, 1994.Applicant
Improved Internet security enabling . . . , PC Week, v12, n11, p. 1(2), Mar. 20, 1995.Applicant
Internet access: Internet marketing revolution . . . , EDGE Work-Group Computing Report, v7, n316, p. 2(1), Jun. 3, 1996.Applicant
“MediaLink: Bell Laboratories unveils sophisticated information insertion technology for broadcast and cable advertising,” EDGE, v11, p. 43(1), Dec. 16, 1996.Applicant
“Infoseek Offers Web Advertisers Customized Delivery of Ads,” Newsbytes, pNEW05270111, May 27, 1997.Applicant
Blankenhorn, Dana; “Sites experiment with advertising to offer free service,” Advertising Age's Business Marketing, v82, p. 29, Jul. 1997.Applicant
Lockard, Meredith; “Advertising done your way,” Target Marketing, v20, n10, p. 40, ISSN: 0889-5333, Oct. 1997.Applicant
“Ericsson Introduces New Intelligent Network-Based Internet Advertiser At Internet World '98,” Business Wire, p. 0240, Oct. 7, 1998.Applicant
Chat Transcript; Topic: Ad Measurement and Management; Oct. 15, 1998; (http://www.zeff.com/learn/zdu/advertising/zinman.html; printed on Feb. 7, 2000).Applicant
CNET Press Release titled “CNET Online Signs Up More Than a Quarter of a Million Members Through Voluntary Registration after Only Five Months”; (http://home.cnet.com/aboutcnet/0-13613-7-808021.html; printed on Nov. 26, 1999).Applicant
Hypertext Markup Language—2.0; Nov. 1995 (Draft HTML 2.0 Specification; Sep. 22, 1995).Applicant
Webster's Third New International Dictionary of the English Language Unabridged, 1967, p. 2171 “some”.Applicant
Microsoft Press Computer Dictionary Third Edition, 1997, p. 387 “proxy server”.Applicant
Bill Harvey, The Expanded ARF Model: Bridge to the Accountable Advertising Future, Journal of Advertising Research, Mar./Apr. 1997, pp. 11-20.Applicant
Cespedes & Smith, Database Marketing: New Rules for Policy and Practice, Sloan Management Review, Summer, 1993, pp. 7-22.Applicant
Preston Gralla, How the Internet Works, Aug. 1999, Millennium Edition, 202-204 and 243-247.Applicant
Miller, B., “GroupLens: An Open Architecture for Collaborative Filtering,” ftp://ftp.cs.umn.edu/users/bmiller/prop.ps, Univ. of Minn., pp. 1-18, Oct. 1995.Applicant
Upendra Shardanand, “Social Information Filtering for Music Recommendation” Sep. 1994, pp. 1-93, Massachusetts Institute of Technology, Thesis.Applicant
“WWW.barnesandnoble.com” (“WWW.firefly.com”), web site pages, 12 pages, printed out on Jan. 21, 1998 (origination date unknown).Applicant
“WWW.amazon.com”, web site pages, 15 pages, printed out on Jan. 21, 1998 (origination date unknown).Applicant
Microsoft Press Computer Dictionary Third Edition, 1997, pp. 271 (“junction”), 285 (“link”), 331 (“node”).Applicant
51st IETF—Whois enhancement BOF (whoisfix), Aug. 1, 2001.Applicant
Doubleclick Measures Beyond the Click With New “Spotlight” Software, Sep. 4, 1996, Doubleclick.Applicant
Doubleclick Unveils Internet Ad Tracking Product, Sep. 4, 1996, Reuter Financial Report.Applicant
Doubleclick Shines Its Spotlight, Sep. 5, 1996, Advertising Age—Interactive Daily.Applicant
Spotlight on Doubleclick, Sep. 13, 1996, Information & Interactive Services Report.Applicant
Tracking Services Tallies Ad Response, Online Orders, Sep. 16, 1996, DMNews.Applicant
Luring in Customers Via Web Advertising, Oct. 1996, Business Strategies.Applicant
LinkMarket Business Plan; David Zinman et al.; SD005545-SD005569.Applicant
LinkMarket; David Zinman et al.; SD005573-SD005574.Applicant
“Online Marketing: . . . ”; Internet Week, vol. 1, Issue 36; Dec. 18, 1995; SD005584-SD005585.Applicant
David Zinman; http://www.focalink.com/dzinman/bio.html; SD005586.Applicant
“Seeing A Gap . . . ”; Ellis Booker; http://www.internetworld.corn/print/1996/02/01/industry/ad-server.html; Feb. 1996; SD005587.Applicant
“readme. 1st; . . . ”; David Evans; Marketing Computers, No. 2, vol. 16, p. 12; Feb. 1996; SD005588-SD005589.Applicant
“Focalink Will Monitor . . . ”; Julia Angwin; San Francisco Chronicle; Feb. 7, 1996; SD005590.Applicant
“Media Daily Special: . . . ”; Sean Butterbaugh; Media Daily, No. 5, vol. 4; Feb. 7, 1996; SD005591-SD005592.Applicant
“Internet Access: Major Companies . . . ”; Edge: Work-Group Computing Report; Feb. 12, 1996; SD005593-SD005594.Applicant
“Internet Access: First Advertising . . . ”; Edge: Work-Group Computing Report; Feb. 12, 1996; SD005595-SD005596.Applicant
“Internet Access: Major Companies . . . ”; Edge: Work-Group Computing Report; Feb. 12, 1996; SD005597-SD005598.Applicant
“Another Media-Buying Firm . . . ”; Media Daily, No. 5, vol. 4; Feb. 14, 1996; SD005599-SD005601.Applicant
“Working the Web; . . . ”; Jennifer Reese; Executive Female, No. 2, vol. 19, p. 24; Mar. 13, 1996; SD005602-SD005604.Applicant
“Web ad-management software . . . ”; John Evan Frook; InternetWeek; Mar. 18, 1996; SD005605-SD005607.Applicant
“Unraveling a tangled Web; . . . ”; Ken Siegmann; PC Week, No. 15, vol. 13, p. A4; Apr. 15, 1996; SD005608-SD005610.Applicant
“Web Site Links: . . . ”; Electronic Marketplace Report, No. 16, vol. 9; Aug. 22, 1995; SD005611-SD005613.Applicant
“Interactive Media & Marketing . . . ”; Advertising Age; Dec. 11, 1995; SD005614-SD005615.Applicant
“Major Companies, Ad Agencies . . . ”; Business Wire; Feb. 5, 1996; SD005616-SD005617.Applicant
“First Advertising Server Launched . . . ”; Business Wire; Feb. 5, 1996; SD005618-SD005619.Applicant
“Interactive; Focalink and Doubleclick . . . ”; Kim Cleland; Advertising Age, p. 30; Feb. 5, 1996, SD005620-SD005621.Applicant
“First Advertising Server Launched . . . ”; Business Wire; Feb. 5, 1996; SD005622-SD005623.Applicant
“Major Companies, Ad Agencies . . . ”; Business Wire; Feb. 5, 1996; SD005624-SD005625.Applicant
Web Personals Report; Oct. 12, 1995; Z00001-Z00009 / SD027072-SD027080.Applicant
FocaLink Technology; Aug. 30, 1995; Z00010-Z00011 / SD027081-SD027082.Applicant
Web Personals stats; Aug. 22, 1995; Z00012-Z00013 / SD027083-SD027084.Applicant
For Immediate Release; Hyperlink Advertising Explodes on the World Wide Web; http://link.w3.com; Z00014 / SD027085.Applicant
Interactive Age; The Newspaper for Electronic Commerce; Z00015-Z00019 / SD027086-SD027090.Applicant
Link Marketing, LLP; Z00020-Z00021 / SD027091-SD027092.Applicant
Link Marketing; Z00022-Z00027 / SD027093-SD027098.Applicant
LinkMarket; David Zinman et al.; Z00028-Z00030 / SD027099-SD027101.Applicant
LinkMarket; David Zinman et al.; Z00031-Z00032 / SD027102-SD027103.Applicant
LinkMarket; David Zinman et al.; Z00033-Z00056 / SD027104-SD027127.Applicant
FocalLink Media Services, Inc.; David Zinman et al.; Aug. 2, 1995; Z00057-Z00070 / SD027128-SD027141.Applicant
Saturn Banner Ad Placement; Aug. 25, 1995; Z00071 / SD027142.Applicant
Sponsorable Site—Riddle du Jour; Aug. 26, 1995; Z00072-Z00074 / SD027143-SD027145.Applicant
Saturn Banner Ad Placement; Aug. 27, 1995; Z00075 / SD027146.Applicant
FocaLink Technology; Aug. 30, 1995; Z00076-Z00077 / SD027147-SD027148.Applicant
Question for you; Sep. 7, 1995; Z00078-Z00079 / SD027149-SD027150.Applicant
Information Request; Sep. 12, 1995; Z00080 / SD027151.Applicant
Update and Miscellaneous; Sep. 22, 1995; Z00081-Z00083 / SD027152-SD027154.Applicant
FocalLink: request for ISN ad traffic data (fwd); Sep. 26, 1995; Z00084-Z00085 / SD027155-SD027156.Applicant
Saturn Ad Placements; Sep. 28, 1995; David Zinman; Z00086 / SD027157.Applicant
Re> Saturn Ad Placements; Sep. 29, 1995; [email protected]; Z00087 / SD027158.Applicant
Re: Advertising Update; Oct. 3, 1995; Eric Ver Ploeg; Z00088-Z00089 / SD027159-SD027160.Applicant
Re>>Saturn Ad Placements; Sep. 29, 1995; [email protected]; Z00090 / SD027161.Applicant
Re: Test Parameters (fwd); Oct. 23, 1995; Jason Strober; Z00091-Z00092 / SD027162-SD027163.Applicant
Re: Rest Parameters; Oct. 23, 1995; Jason Strober; Z00093-Z00094 / SD027164-SD027165.Applicant
Proposal (fwd); Oct. 23, 1995; Jason Strober; Z00095-Z00096 / SD027166-SD027167.Applicant
Advertising advisory board; Oct. 25, 1995; David Zinman; Z00097-Z00099 / SD027168-SD027170.Applicant
Contact at Netcom; Oct. 26, 1995; David Zinman; Z00100 / SD027171.Applicant
CMP Technical Contact; Oct. 30, 1995; Jason Strober; Z00104 / SD027172.Applicant
from ad age today . . . ; Oct. 30, 1995; Karen Johnson; Z00105-Z00106 / SD027173-SD027174.Applicant
We need to get on this; Oct. 31, 1995; David Zinman; Z00107 / SD027175.Applicant
Web site pricing draft; Nov. 7, 1995; Jason Strober; Z00108 / SD027176.Applicant
Heads up . . . (fwd); Nov. 8, 1995; David Zinman; Z00109-Z00110 / SD027177-SD027178.Applicant
Proposal to Intel; Nov. 13, 1995; Jason Strober; Z00111-Z00114 / SD027179-SD027182.Applicant
FocaLink white paper; Nov. 13, 1995; Jason Strober; Z00115-Z00116 / SD027183-SD027184.Applicant
FocaLink Media Services; Nov. 14, 1995; David Zinman; Z00117-Z00119 / SD027185-SD027187.Applicant
I/Traffic & Dave Carlick; Nov. 14, 1995; David Zinman; Z00120 / SD027188.Applicant
FocaLink white paper; Nov. 15, 1995; David Zinman; Z00121-Z00123 / SD027189-SD027191.Applicant
Re: FocaLink Meeting (fwd); Nov. 20, 1995; Karen Johnson; Z00124-Z00125 / SD027192-SD027193.Applicant
Microsoft ads through FocaLink; Nov. 21, 1995; Jason Strober; Z00126 / SD027194.Applicant
Re: Who's in and who's out (fwd); Nov. 21, 1995; Jason Strober; Z00127-Z00128 / SD027195-SD027196.Applicant
Intel update (fwd); Nov. 23, 1995; Jason Strober; Z00129-Z00130 / SD027197-SD027198.Applicant
Saturn reports; Dec. 5, 1995; Jennifer Ratner; Z00134-Z00140 / SD027199-SD027205.Applicant
November Report; Dec. 5, 1995; Jennifer Ratner; Z00141-Z00146 / SD027206-SD027211.Applicant
FocaLink Media Services; Dec. 6, 1995; David Zinman; Z00147 / SD027212.Applicant
FocaLink Media Services; Dec. 6, 1995; David Zinman; Z00148 / SD027213.Applicant
FocaLink Media Services; Dec. 6, 1995; David Zinman; Z00149 / SD027214.Applicant
FocaLink for the Layman; Dec. 6, 1995; David Zinman; Z00150 / SD027215.Applicant
Microtargeting; Dec. 7, 1995; David Zinman; Z00151 / SD027216.Applicant
Info on FocaLink Media Services; Dec. 11, 1995; David Zinman; Z00152-Z00154 / SD027217-SD027219.Applicant
FocaLink Media Services; Dec. 11, 1995; David Zinman; Z00155-Z00156 / SD027220-SD027221.Applicant
Catch-up time; Dec. 11, 1995; David Zinman; Z00157 / SD027222.Applicant
Info on FocaLink; Dec. 13, 1995; David Zinman; Z00158-Z00160 / SD027223-SD027225.Applicant
Intel Ad on Dilbert Site; Dec. 13, 1995; David Zinman; Z00161 / SD027226.Applicant
Re: Intel Ad on Dilbert Site; Dec. 13, 1995; David Zinman; Z00162 / SD027227.Applicant
FocaLink Beta Test on SmartBanner; Dec. 14, 1995; David Zinman; Z00163 / SD027228.Applicant
I/Pro Mtg Today; Dec. 19, 1995; David Zinman; Z00164 / SD027229.Applicant
Eric Smith Quote (fwd); Jan. 10, 1996; David Zinman; Z00165 / SD027230.Applicant
FocaLink Communications, Inc.; Jan. 10, 1996; David Zinman; Z00166 / SD027231.Applicant
Re: Advertisers for wyp.net; Jan. 12, 1996; David Zinman; Z00167 / SD027232.Applicant
Quote for Press Release; Jan. 15, 1996; David Zinman; Z00168 / SD027233.Applicant
Re: Quote for Press Release; Jan. 16, 1996; “thomas mark”; Z00169 / SD027234.Applicant
Re: Quote for Press Release (fwd); Jan. 16, 1996; David Zinman; Z00170-Z00171 / SD027235-SD027236.Applicant
Re> **Ad Placement Notific; Jan. 19, 1996; Dan—[email protected]; Z00172-Z00173 / SD027237-SD027238.Applicant
Invitation; Jan. 25, 1996; [email protected]; Z00174 / SD027239.Applicant
Focalink; Jan. 25, 1996; David Zinman; Z00175 / SD027240.Applicant
SmartBanner Reports; Jan. 25, 1996; David Zinman; Z00176 / SD027241.Applicant
Re: Focalink; Jan. 26, 1996; Rick Vorhaus; Z00177 / SD027242.Applicant
Comments; Jan. 29, 1996; David Zinman; Z00178-Z00182 / SD027243-SD027247.Applicant
Poppe Tyson/Internet Advertising Network Alliance; Feb. 26, 1996; Ron Kovas; Z00183 / SD27248.Applicant
fyi; Feb. 5, 1996; “Roger Follis”; Z00184-Z00185 / SD027249-SD027250.Applicant
Focalink Communications; Feb. 5, 1996; David Zinman; Z00186-Z00188 / SD027251-SD027253.Applicant
Microsoft Update; Feb. 5, 1996; Margaret Bond; Z00189 / SD027254.Applicant
Focalink Communications; Feb. 6, 1996; David Zinman; Z00190-Z00192 / SD027255-SD027257.Applicant
Focalink Communications; Feb. 6, 1996; David Zinman; Z00193-Z00195 / SD027258-SD027260.Applicant
Focalink Communications; Feb. 6, 1996; David Zinman; Z00196-Z00198 / SD027261-SD027263.Applicant
[Fwd: Re: DoubleClick and IAN]; Feb. 6, 1996; Jason Strober; Z00199 / SD027264.Applicant
Focalink Communications; Feb. 6, 1996; David Zinman; Z00200-Z00202 / SD027265-SD027267.Applicant
Test With Focalink; Feb. 7, 1996; David Zinman; Z00203 / SD027268.Applicant
Urgent—Microsoft Ad Placement; Feb. 7, 1996; David Zinman; Z00204 / SD027269.Applicant
Test for Microsoft Banner; Feb. 8, 1996; Joel Bassuk; Z00205 / SD027270.Applicant
ZDNet Test; Margaret Bond; Feb. 8, 1996; Z00206 / SD027271.Applicant
URLs; Feb. 8, 1996; Dan Stoller; Z00207-Z00208 / SD027272-SD027273.Applicant
HeadsUp Feb. 9, 1996 (20 stories)<CD58M010>; Feb. 9, 1996; An Information Service of Individual Inc.; Z00209-Z00212 / SD027274-SD027277.Applicant
Focalink Communications; Feb. 13, 1996; David Zinman; Z00213 / SD027278.Applicant
Targeting; Feb. 13, 1996; Michael Wang; Z00214 / SD027279.Applicant
Re: Cookies!; Feb. 15, 1996; David Zinman; Z00215 / SD027280.Applicant
Focalink; Feb. 22, 1996; Jason Strober; Z00216 / SD027281.Applicant
Focalink/Microsoft I.E.; Feb. 23, 1996; Margee Bond; Z00217-Z00218 / SD027282-SD027283.Applicant
Cookies; Mar. 6, 1996; David Zinman; Z00219 / SD027284.Applicant
Did I send this 2x; Apr. 3, 1996; Z00220-Z00222 / SD027285-SD027287.Applicant
Answer to your request; Apr. 8, 1996; Z00223 / SD027288.Applicant
Site Letter; Apr. 10, 1996; Z00224-Z00225 / SD027289-SD027290.Applicant
Oracle and Intel; Apr. 12, 1996; Z00226 / SD027291.Applicant
Doubleclick; Apr. 16, 1996; Z00227 / SD027292.Applicant
Open Market Licenses With NetGravity; May 6, 1996; Z00228 / SD027293.Applicant
Fact check; May 12, 1996; Z00229 / SD027294.Applicant
IDG; May 17, 1996; Z00230-Z00231 / SD027295-SD027296.Applicant
Daily Spectrum; May 20, 1996; Z00232-Z00242 / SD027297-SD027307.Applicant
Fact check; May 20, 1996; Z00243 / SD027308.Applicant
Cookie FAQ; May 21, 1996; Z00244 / SD027309.Applicant
Focalink Communications; May 21, 1996; Z00245-Z00246 / SD027310-SD027311.Applicant
Network World Fusion; May 22, 1996; Z00247 / SD027312.Applicant
Looming issue; Jul. 13, 1996; Z00248-Z00249 / SD027313-SD027314.Applicant
Cookies & privacy ? / Gernan Press; Jul. 15, 1996; Z00250 / SD027315.Applicant
Cookies & privacy ? / German Press; Jul. 16, 1996; Z00251 / SD027316.Applicant
DoubleClick; Sep. 5, 1996; Z00252-Z00253 / SD027317-SD027318.Applicant
Infoseek Business Terms; Sep. 7, 1996; Z00254-Z00256 / SD027319-SD027321.Applicant
SmartBanner ads on HotWired; Sep. 11, 1996; Z00257 / SD027322.Applicant
Statement of Work; Sep. 23, 1996; Z00258-Z00259 / SD027323-SD027324.Applicant
NetGravity Releases Adserver 2.0; Oct. 21, 1996; Z00260-Z00263 / SD027325-SD027328.Applicant
“Focalink”; DC004278A.Applicant
“FocaLink Services”; FocaLink Media Services, Inc.; DC004278B-DC004278C.Applicant
“Welcome to Focalink!”; Focalink Communications; DC004278D-DC004278CC.Applicant
“Welcome to Focalink!”; Focalink Communications; DC004278DD-DC004278XX.Applicant
“Link Marketing”; handwritten page; MA0001.Applicant
“Link Marketing”; LinkMarket; MA0002-MA0007.Applicant
“LinkMarket”; David Zinman et al.; MA0008-MA0027.Applicant
“Link Marketing, LLP”; MA0028-MA0029.Applicant
“Link Marketing LLP”; MA0030-MA0038.Applicant
“Escapes”; Web page; MA0039-MA0040.Applicant
“Industry Overview”; FocaLink Media Services, Inc.; MA0041-MA0053.Applicant
“Executive Summary”; Focalink Communications Confidential; printed Jul. 30, 1997; MA0054-MA0109.Applicant
“Focalink Communications”; Feb. 1996; MA0110-MA0149.Applicant
Business Wire (New York, Nov. 17, 1998), “i33 Communications Links Personal Finance Sites with Dynamic Investment Research Banners; Quote.com and Multex Partner Using i33's AdMaximize Technology”.Applicant
Link Marketing Business Plan, dated May 11, 1995, 2 pages.Applicant
E-mail re Web site pricing draft, dated Tuesday, Nov. 7, 1995, 10:55 a.m., 1 page.Applicant
E-mail re Microsoft ads through FocaLink, dated Tuesday, Nov. 21, 1995, 14:02 p.m., 1 page.Applicant
E-mail re November Report, dated Tuesday, Dec. 5, 1995, 12:55 p.m., 6 pages.Applicant
E-mail re Saturn Reports, dated Tuesday, Dec. 5, 1995, 12:40 p.m., 7 pages.Applicant
E-mail re Intel Report Nov. 27, 1995 - Dec. 3, 1995, mailed Tuesday Dec. 12, 1995, 5:35 p.m., 15 pages.Applicant
Brochure: Welcome to Focalink!, dated Mar. 14, 1996, 24 pages.Applicant
E-mail re FYI, mailed Feb. 5, 1996, 7:08 a.m., 2 pages.Applicant
E-mail re Proposal to Intel, mailed Monday, Nov. 13, 1995, 22:56 p.m., 4 pages.Applicant
Declaration of Dwight Allen Merriman, signed Feb. 9, 2001, 10 pages.Applicant
Google's Preliminary Invalidity Contentions, dated Jun. 26, 2009, 12 pages.Applicant
Exhibits A and B, 60 pages, dated Jun. 26, 2009.Applicant
Link Marketing Business Plan, dated May 28, 1995, 6 pages.Applicant
Link Marketing Business Plan, dated Jun. 6, 1995, 24 pages.Applicant

Abstract

Description

Cross-Reference to Related Applications

Background of the Invention

[0002] 1. Area of the Art

[0004] 2. Description of the Prior Art

Summary of the Invention

Description of the Figures

[0014] FIG. 1 is diagram for explaining a first embodiment of the invention.

[0015] FIG. 2 is a diagram explaining the processes performed in the preferred embodiments.

[0016] FIGS. 3A, 3B and 3C are diagrams showing the basic structure of some of the databases kept by the advertising server.

Detailed Description of the Invention

Advertising Server Processes 19

[0032]

SI = \frac{n}{N} * \frac{end - start}{now - start}

Where:

- [0033] n: the number of times the particular advertisement has been viewed by anyone
- [0034] N: the number of times the advertisement is to be see by anyone
- [0035] end-start: the total number of days that the advertisement is scheduled to run
- [0036] now-start: the number of days that the advertisement has run to date