WO2001043375A1 - Procede et systeme de transmission de messages publicitaires aux dispositifs clients - Google Patents

Procede et systeme de transmission de messages publicitaires aux dispositifs clients Download PDF

Info

Publication number
WO2001043375A1
WO2001043375A1 PCT/US2000/029156 US0029156W WO0143375A1 WO 2001043375 A1 WO2001043375 A1 WO 2001043375A1 US 0029156 W US0029156 W US 0029156W WO 0143375 A1 WO0143375 A1 WO 0143375A1
Authority
WO
WIPO (PCT)
Prior art keywords
software
set forth
playlist
advertisements
function
Prior art date
Application number
PCT/US2000/029156
Other languages
English (en)
Inventor
Paul E. Jacobs
Franklin P. Antonio
Steven Dorner
John W. Noerenberg
Jeffrey K. Belk
Benjamin P. Ogdon
Jeffrey D. Beckley
Alan Bird
John D. Boyd
John S. Purlia
William J. Rhodes
David J. Ross
Matthew J. Dudziak
Original Assignee
Qualcomm Incorporated
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Qualcomm Incorporated filed Critical Qualcomm Incorporated
Priority to AU12235/01A priority Critical patent/AU1223501A/en
Priority to JP2001531747A priority patent/JP2003524230A/ja
Publication of WO2001043375A1 publication Critical patent/WO2001043375A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/02—Marketing; Price estimation or determination; Fundraising
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G06Q10/107—Computer-aided management of electronic mailing [e-mailing]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/07—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail characterised by the inclusion of specific contents
    • H04L51/18—Commands or executable codes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/42—Mailbox-related aspects, e.g. synchronisation of mailboxes

Definitions

  • the present invention relates generally to the field of electronic mail ("e- mail") software and systems. More particularly, the present invention is related to advertiser-supported e-mail software for delivering advertisements to client computers having this advertiser-supported e-mail software installed thereon.
  • e- mail electronic mail
  • E-mail Electronic mail
  • a client device e.g., a personal computer (PC)
  • PC personal computer
  • Access to the communications network can be provided by a communications network service provider, e.g., an Internet Service Provider (ISP) and /or a proprietary network e-mail service provider, with whom the user establishes one or more e-mail accounts, each identified by a unique e-mail address, e.g., president@whitehouse.gov.
  • ISP Internet Service Provider
  • a proprietary network e-mail service provider with whom the user establishes one or more e-mail accounts, each identified by a unique e-mail address, e.g., president@whitehouse.gov.
  • the e-mail software e.g., the e-mail client, enables a user of the client device to compose e-mail messages, to send e-mail messages to other client devices via the communications network, and to read e-mail messages received from other client devices via the communications network.
  • a user can send e-mail messages to multiple recipients at a time, which capability is sometimes referred to using a mailing list or, in extreme cases, bulk mailing.
  • the typical e- mail client supports Post Office Protocol Version 3 (POP3), Simple Mail Transfer Protocol (SMTP), Internet Mail Access Protocol, Version 4 (IMAP4), and/or Multipurpose Internet Mail Extensions (MIME).
  • POP3 Post Office Protocol Version 3
  • SMTP Simple Mail Transfer Protocol
  • IMAP4 Internet Mail Access Protocol
  • MIME Multipurpose Internet Mail Extensions
  • Each ISP and each proprietary network e-mail service provider independently operates and controls an e-mail communication system (or, simply, "e-mail system").
  • e-mail system or, simply, "e-mail system”
  • These independently-operated e-mail systems are bidirectional store-and-forward communication systems that are interconnected to one another via the Internet.
  • Each e-mail system generally includes a number of e-mail servers that store inbound and outbound e-mail messages and then forward them, route them, or simply make them available to the users /intended recipients.
  • Different e-mail systems are operated and controlled by independent control entities.
  • e-mail clients other than proprietary e-mail systems such as AOL and JUNO, can be configured to receive e-mail from an incoming e-mail server (cluster) controlled by a first entity and an outgoing email server (cluster) controlled by a second, totally independent entity. It will be appreciated that most casual email users download from and upload to respective servers operated by a single entity.
  • the e-mail software when a user desires to send e-mail messages, or to check for received messages (which operations can occur automatically according to a prescribed schedule), the e-mail software is activated. Upon being activated, the e-mail software:
  • ⁇ electronically transmits or transports any e-mail messages desired to be sent to the e-mail server system operated by the host ISP or e-mail service provider, e.g., via an SMTP server;
  • Exemplary e-mail software is the commercially available e-mail software marketed by the present assignee, QUALCOMM INCORPORATED, under the registered trademarks EUDORA PRO® and EUDORA LIGHT® (hereinafter sometimes referred to generically as "Eudora").
  • EUDORA PRO e-mail software provides the user with a "full feature set”
  • EUDORA LIGHT e-mail software provides the user with a "reduced feature set” that is a subset of the "full feature set” provided by the EUDORA PRO e-mail software.
  • the EUDORA PRO e-mail software (the previous version of which is referred to as "EP4" in this document) must be paid for by the user (or by someone else on behalf of the user), and can thus be regarded as "Payware”, whereas the EUDORA LIGHT e-mail software is provided free of charge to registered users, and thus, can be regarded as "Freeware.”
  • Each of the client devices that has any version of Eudora installed thereon can be regarded as a "Eudora client.”
  • Eudora client Presently, there is a very large installed base of Eudora clients.
  • the present assignee, QUALCOMM INCORPORATED has recently released a new version of its popular EUDORA e-mail software that is popularly known as EUDORA Adware (hereinafter sometimes referred to simply as "Adware").
  • This new Adware version of Eudora is contained within, i.e., is an integral part of, a new Eudora software product that contains the previously-referenced Payware and Freeware versions of Eudora.
  • each version of Eudora contained within this Eudora product release constitutes a separate operating mode of a single software product.
  • the Adware Version of Eudora Pro® can be activated or switched between modes either automatically, in accordance with prescribed criteria or conditions, or manually, in accordance with prescribed user actions, e.g., registration, payment, selection, etc.
  • This new Adware version of Eudora and the multi- moded Eudora e-mail software product that contains the same were motivated by a desire on the part of the present assignee to provide users with the "full feature set" afforded by the Payware version of Eudora free of charge to the users, by means of distributing advertisements paid for by advertisers to Eudora clients, thereby effectively shifting the source of payment /revenue from the users to the advertisers.
  • this new Eudora software product can be regarded as "advertiser-supported” or “advertiser-subsidized” or simply “sponsored” software.
  • ISPs Internet service providers
  • e-mail service providers charge users a flat monthly subscription fee, although some providers still charge users based on usage, e.g., additional charges for on-line time beyond a prescribed level.
  • ISPs Internet service providers
  • e-mail service providers charge users a flat monthly subscription fee, although some providers still charge users based on usage, e.g., additional charges for on-line time beyond a prescribed level.
  • a few companies have addressed the needs of this market segment by providing free e-mail service to users/subscribers who agree to receive advertisements along with their received e-mail messages. In this way, the advertisers support or sponsor the free e-mail service.
  • FreeMark Communications (a.k.a. "Product View Interactive”).
  • the FreeMark system and method for providing free e-mail service is disclosed in PCT published patent application International Publication Number WO 96/24213, having a priority date of February 1, 1995, based on U.S. Application Serial Number 08/382,118, naming as inventors Marv Goldschmitt and Robert A. Young.
  • the disclosure of this published PCT patent application is expressly incorporated herein by reference.
  • this free e-mail system was subsidized by advertisers that appended advertisements as attachments, e.g., graphical interchange format (GIF) image file attachments, to e-mail messages transmitted to subscribers.
  • GIF graphical interchange format
  • the advertisements were stored on the subscriber's computer for viewing while the subscriber was off-line reading the received e-mail messages.
  • FreeMark referred to the appended advertisements as "postage stamps".
  • each message received by the subscriber was depicted as an envelope bearing a postage stamp; the postage stamp was the advertisement.
  • JUNO Juno Online Services
  • a plurality of advertisements are downloaded to subscribers when they connect to the proprietary JUNO e-mail server system to send and /or receive e-mail messages, with the advertisements being stored locally on the subscriber's computer for display when the subscriber is off-line composing or reading e-mail messages, i.e., when the subscriber activates Juno e-mail software previously installed on the subscriber's computer.
  • the locally stored advertisements are displayed under the control of a display scheduler resident on the subscriber's computer, to thereby enable the advertisements to be rotated or changed in a dynamic manner. This results in a continuously- changing display of advertisements being presented to the subscriber.
  • both the advertisements and the e-mail messages are stored on a single e-mail system (e.g., JUNO stores both on a single, unique server which is assigned (bound) to the user when he/she first signs up for service), and are distributed to subscribers under the direction of a common control entity that is controlling all part of the e-mail system.
  • JUNO stores both on a single, unique server which is assigned (bound) to the user when he/she first signs up for service
  • this may be a desirable system architecture for providing free e-mail service, it is not a suitable system architecture for a system whose purpose is to distribute advertiser-supported e-mail software that is e- mail system-independent, i.e., which is not tied to a particular proprietary e- mail service provider but, rather, supports public standards, e.g., POP3, SMTP, IMAP4, etc.
  • the free e-mail system architecture is not suitable for the many people who maintain multiple e-mail accounts, e.g., business and personal e-mail accounts.
  • the present inventors were motivated by a desire to provide a system and method for distributing advertisements to Eudora clients in order to generate advertising revenues that would allow a fully-featured version of the Eudora e-mail software to be widely distributed free of charge to end-users. Moreover, the present inventors were motivated by a desire to provide e-mail software that is both universal and e- mail system-independent, i.e., it is not tied to any particular proprietary e-mail service or service provider.
  • the present inventors have developed a novel multi-moded Eudora e-mail software product that contains the Payware, Freeware and Adware, and have also devised a novel system and method for distributing advertisements to clients equipped with this new software product.
  • the purpose and architecture of this novel system are radically different than that of the proprietary FreeMark and JUNO e-mail systems.
  • the multi-moded Eudora e-mail software product, and the novel system and method for distributing advertisements to clients equipped with this new software product embraces a number of different inventions that will become fully apparent from the following disclosure and the documents referenced therein.
  • the present invention encompasses e-mail software which incorporates an automatic advertisement download function for automatically downloading advertisements to be displayed when the e-mail software is activated, for the purpose of subsidizing the full e-mail software product (e.g., to provide a "Freeware" version of the e-mail software product to end-users), wherein the e-mail software is e-mail system-independent.
  • the e-mail software is a stand-alone product which is universal, i.e., works in conjunction with virtually any e-mail service provider or e-mail system, including those service which comply with open standards.
  • the present invention also encompasses a system and method for automatically distributing advertisements to a multiplicity of client devices which have this e- mail software installed thereon.
  • the present invention provides an e-mail client for receiving and sending e-mail messages to at least one of a plurality of e-mail servers operated by respective e-mail operators, wherein the e-mail client receives at least one ad from an ad server operated by a control entity different than the control entity operating the one or more e-mail systems.
  • the present invention provides a recording medium storing e-mail client software for instantiating an e-mail client which receives e-mail messages from and sends e-mail messages to at least one of a plurality of e-mail servers operated by their respective e-mail operators, wherein the e-mail client automatically receives ads from an ad server which operates independent of the e-mail servers.
  • the present invention encompasses a method of operating an e-mail client, provided by an ad server operator, compatible with a plurality of independently operated e-mail servers, including ones based on open e-mail standards.
  • the method includes steps for periodically at least one of sending and receiving e-mail from selected ones of the e-mail servers, periodically receiving ads from the ad server operator, and displaying the received ads responsive to instructions provided by the ad server operator.
  • the present invention provides an e- mail system including an incoming e-mail server storing incoming e-mail messages addressed to a plurality of users, an outgoing e-mail server for forwarding or routing outgoing e-mail messages generated by the users, and an ad server operating independently of the e-mail server, and a plurality of e-mail clients operated by respective users.
  • each of the e-mail clients checks for respective e-mail messages stored on the incoming e-mail server, transmits any outgoing e-mail messages stored on the e-mail client to the outgoing e-mail server, and downloads available ads from the ad server while the e-mail client is online.
  • the present invention provides software for use on a client device that is configured for communications with at least one remote source via a communications network, the software instantiating a custom installer function that installs the software on the client device, and that generates a distributor identifier that identifies a distributor that distributed the software, and an ad download function that downloads advertisements from the at least one remote source, via the communications network.
  • the present invention provides software for use on a client device that is configured for communications with a multiplicity of other client devices via a communications network.
  • the software instantiates a custom installer function that installs the software on the client device, and that generates a distributor identifier that identifies a distributor that distributed the software, an ad download function that downloads advertisements from at least one remote source, via the communications network, an e-mail composition function for enabling a user of the client device to compose e-mail messages, an e-mail send function that enables the user to send e-mail messages to other client devices via the communications network, and an e-mail receive function that enables the user to receive e-mail messages from other client devices via the communications network.
  • the present invention provides software, for use on a client device that is configured for communications via a communications network, instantiating a custom installer function that installs the software on the client device, and that generates a distributor identifier that identifies a distributor that distributed the software, a playlist request function that generates a playlist request that includes the distributor identifier, and that transmits the playlist request to at least one playlist server, via the communications network, a playlist response handling function that receives and processes a playlist response transmitted to the client device by the at least one playlist server in response to the playlist request, wherein the playlist response includes a playlist(s) that identifies advertisements to be downloaded, an ad download function that downloads at least selected ones of the advertisements identified in the playlist(s) from at least one remote source, via the communications network, over one or more advertisement download sessions, an advertisement storage function for storing the downloaded advertisements on a storage medium associated with the client device, and an advertisement display function that effects display of at least selected ones of the stored advertisements on a display associated with the client device.
  • Fig. 1 is a high-level diagram of a computer system including a plurality of client devices connected to a plurality of independently-operated server devices via a network, which computer system is suitable for implementing various functions according to the present invention
  • Fig. 2 is a high-level diagram of a representative one of the client devices illustrated in Fig. 1;
  • Figs. 3A and 3B illustrate alternative and non-limiting placement of ads in the main navigation screen of an exemplary e-mail software application according to the present invention
  • Fig. 4A depicts state transitions when a version of the software is installed by one of a new user, an old user, and an EP4 user;
  • Fig. 4B illustrates a dialog box associated with the state flow diagram illustrated in Fig. 4A;
  • Fig. 5A illustrates an exemplary state flow diagram of a process by which the Ad user becomes a registered Ad user while Figs. 5B through 5G illustrate several dialog boxes associated with Fig. 5A;
  • Fig. 6A illustrates an exemplary state flow diagram of a process by which a Free user can become a registered Free user while Fig. 6B illustrates an additional dialog box associated with Fig. 6A;
  • Fig. 7A illustrates an exemplary state flow diagram of a process by which all users are reminded to update the software according to the present invention while Fig. 7B depicts an exemplary dialog box corresponding to an Update Nag;
  • Fig. 8 illustrates an exemplary state flow diagram of a process by which a Box user can become a Paid user
  • Fig. 9 illustrates an exemplary state flow diagram of a process by which the Paid User becomes an Unpaid user
  • Fig. 10 illustrates an exemplary Nag Window display timeline for MacOS versions of the Eudora e-mail software according to an exemplary embodiment of the present invention
  • Fig. 11 illustrates a Nag Schedule employed by the software according to the present invention
  • Fig. 12A is a simulated screen capture of a link history window employed in an exemplary software embodiment of the present invention while Fig. 12B is a dialog box reminding the user that the e-mail client according to the present invention is off-line;
  • Fig. 13A illustrates the assumptions used in determining the impact of ad transmission on e-mail program operations while Fig. 13B is a table listing the bandwidth requirements in terms of subscriber base versus the number of new ads to be downloaded each day;
  • Fig. 14 is a state flow diagram of an exemplary ad fetch process according to the present invention.
  • Figs. 15A - 15H collectively illustrate an algorithm controlling ad scheduling in an exemplary embodiment according to the present invention
  • Figs. 16A and 16B illustrate parameter variations in alternative modes of ad display possible in an exemplary embodiment according to the present invention
  • Figs. 17A through 17C illustrate additional dialog boxes which advantageously can be generated by the e-mail client software according to one aspect of the present invention
  • Fig. 18A illustrates an exemplary dialog box associated with auditing the operation of the Adware software according to the present invention while Figs.
  • Fig. 19 is a table summarizing the features of a plurality of web pages that advantageously can be employed in conjunction with an exemplary e-mail system according to one aspect of the present invention
  • Fig. 20 is a class diagram illustrating the mapping of XML code to objects and the task flow when another exemplary embodiment according to the present invention is operating in accordance with doPost methodology;
  • Figs. 21A and 21B collectively constitute a pseudo code listing which can be employed by the server 302 in Fig. 1 in generating a PlayList in accordance with the present invention;
  • Fig. 22 is another class diagram illustrating handling of requests and writes between a server and at least one of the client computers depicted in Fig. 1;
  • Fig. 23 illustrates database accesses in accordance with another aspect of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
  • Fig. 1 illustrates an exemplary system configuration 10 which is suitable for carrying out the functions according to representative embodiments of the present invention.
  • the representative embodiment will be generally described with respect to an electronic mail (e-mail) system where a number of users can create, send, receive and read e-mail messages, the present invention is not so limited.
  • the present invention is equally applicable to a personal digital assistant (PDA) incorporating specialized software for receiving stock quotations via a wireless network.
  • PDA personal digital assistant
  • the principles of the present invention should not be regarded as limited solely to e-mail systems; the principles of the present invention apply to on-line services where a provider, e.g., a software provider, desires to make its software available to users using a variety of payment options for a core set of software functions.
  • a provider e.g., a software provider
  • the system 10 includes a plurality of client computers 100a, 100b, ..., lOOn, where n denotes any positive integer.
  • each of the client computers generally denoted 100 can be either a workstation or a personal computer executing a client program according to the present invention.
  • the client computers 100a, 100b, ..., lOOn advantageously can be connected to a plurality of servers 301 - 304, which servers will be described in greater detail below, via a network 200, e.g., the Internet.
  • the network 200 can be one of a local area network (LAN), a wide area network (WAN), an Intranet, or a wireless network, or some combination thereof.
  • LAN local area network
  • WAN wide area network
  • Intranet or a wireless network, or some combination thereof.
  • Fig. 2 illustrates in further detail the hardware configuration of an exemplary one of the client computers 100a, 100b, ..., lOOn illustrated in Fig. 1.
  • the client computer 100a includes a central processing unit 209 for executing computer programs (including the client program according to one exemplary embodiment of the present invention) and managing and controlling the operation of the client computer 100a.
  • a storage device 205 such as a floppy disk drive, is coupled to the central processing unit 209 for, e.g., reading and writing data and computer programs to and from removable storage media such as floppy disks.
  • Storage device 206 coupled to the central processing unit 209, also provides a mechanism for storing computer programs and data.
  • Storage device 206 is preferably a hard disk having a high storage capacity.
  • a dynamic memory device 207 such as a RAM, is also coupled to the central processing unit 209. It will be noted that storage devices 205 and 206, as well as dynamic memory device 207, are non-limiting examples of a memory, which term was defined previously.
  • the client computer 100a includes typical input/output devices, such as, for example, a keyboard 203, a mouse 204, a monitor 208, and a communications device 201. It will be appreciated that the communications device advantageously can be a modem, an ethernet interface card, etc.
  • each of the client computers 100a, 100b, ..., lOOn can selectively communicate with any of the servers, e.g., servers 301 - 304, via the network 200.
  • each of the servers performs a specialized function.
  • server 301 performs a registration function, i.e., accepts registration information from each client computer (as discussed in greater detail below), server 302 provides PlayLists to the client computers 100a, 100b, ..., lOOn, server 303 provides the advertisements designated in the PlayLists, and server 304 acts as a conventional e-mail system server system, i.e., provides both the incoming e-mail server and the outgoing e-mail server.
  • server 301 and 302 need actually be under the direct control of the software provider, e.g., QUALCOMM INCORPORATED in the preferred embodiment, although server
  • 303 advantageously may be under the control of the software provider as well.
  • the "software” advantageously can be provided as a single binary (per client device) file containing the software, e.g., the Eudora software, which can be employed by all users.
  • This binary file will operate in one of three major modes of operation: Payware; Freeware; and Adware.
  • Payware In the Payware mode of operation, the user must pay the software provider to use the software. Freeware is free for all to use, but has fewer features than either Payware or Adware.
  • Payware users will prove their payment by a registration code that the software provider will provide to them at time of payment. This code will be self-validating, and contain enough data to identify what version(s) the user is entitled to operate.
  • the software preferably polls a predetermined site, e.g., a site maintained by QUALCOMM INCORPORATED, on a periodic basis in order to determine if an update for the software is available; if an update is available, the software advantageously can present the user with a small web page of options for obtaining the software update, as discussed in greater detail below.
  • a predetermined site e.g., a site maintained by QUALCOMM INCORPORATED
  • Adware has all the features of Payware, but does not require payment from the user. What Adware does require is that the user display and view ads, which the user will download from the software provider's site and /or one or more sites designated by the software provider. It will also be noted that the initial state of the software is Adware.
  • each client computer downloads ads from the ad server 303 unobtrusively and without drawing significant bandwidth, as discussed in greater detail below.
  • the ads advantageously can be displayed in a manner that doesn't significantly detract from the use of the software, e.g., Eudora.
  • Figs. 3A and 3B illustrate advertisements integrated into the main screen of the exemplary Eudora e-mail software.
  • a schedule of [0,5,2] means the user will be nagged on the first day, the sixth day, and every other day thereafter.
  • the "software” advantageously can be provided as a single binary file containing the software, e.g., the Eudora software, which can be installed (if required) and employed by all users.
  • This binary file will operate in one of three major modes of operation: Payware; Freeware; and Adware.
  • Fig. 4 depicts state transitions when a version of the software is installed by one of a new user, an old user, and an EP4 user.
  • the software provider doesn't give the user the options to pay for the full feature set or to accept the software with a reduced feature set in the intro dialog. While the software provider will explain those options, e.g., via a dialog box similar to that illustrated in Fig. 4B, as well as the fact that the user can obtain these alternative versions of the software feature set by going through the Help menu, the software defaults to the Adware version.
  • the Code Generator referred to in Fig. 4A advantageously is instantiated by the installer module of the binary file, not in the Eudora e-mail program itself. If the user is using the software's 4.x -> 4.3 update function, the software searches for a copy of EP4 and, on finding a copy of the software, the Code Generator permits the user to generate a RegCode file. If the user is running the installer out of the box, the installer permits RegCode generation without looking for a copy of EP4 first.
  • the RegCode file so generated is special in that it contains a line saying "Eudora- Needs-Registration: YES.”
  • the Eudora e-mail software will notice this line of text, put the user into the unregistered state, and then nag the user to register the software. Once the user registers, the same registration code will be retransmitted to the user, and the Eudora e-mail software will silently accept it (since it will be the same as the current code), and turn off the need to register flag in the e-mail software.
  • Fig. 5A illustrates a state flow diagram of the process by which the Adware user becomes a registered Adware user.
  • the registration process necessitates interaction between client computer 100a and a registration server 301, which are connected to one another via network 200.
  • the Adware user indicated in Fig. 4A registers with the software provider through several alternative mechanisms. For example, the Ad user may wish to register, and simply activates the "HELP" pulldown menu, which is available from the tool bar illustrated at the top of Fig. 3A, and selects the Payment & Registration option, as depicted in Fig. 5B.
  • the Adware user may receive a Nag box, i.e., a Nag dialog box, generated by the software at a predetermined time, as discussed more fully below.
  • the Ad user may receive a registration via e-mail, i.e., a registration code generated by server 301 and transmitted to the client computer 100a by way of e-mail server 304.
  • the Payment & Registration Window provides several selection buttons, which allow the Ad user to register the Adware, pay for the software, list all versions available to the user, customize or modify the ad stream by providing demographic information, enter a received registration code, and downgrade to the reduced feature set offered to Freeware users.
  • Figs. 5C - 5G It should be mentioned that the user can enter a registration code to become one of a registered Adware user, a registered Freeware user, and a registered Payware user.
  • Fig. 5F It will be appreciated that the software operates in accordance with the same state flow diagram for Registered Adware Users, except that the Registered Adware User is not subjected to the Registration Nag.
  • the software provider advantageously can use a registration scheme with a self-validating registration code, so that databases do not need to be used to validate registrations.
  • the algorithm for verification is intended to satisfy several conflicting constraints, i.e., it needs to be secure, yet easy to implement and not unduly burdensome for the user.
  • the Eudora e-mail software checks its registration code at startup for validity. If the registration code is invalid, the user should be considered unregistered. If the user is a paid mode user, this will involve a switch to Sponsored mode, about which the user should be warned using a dialog box (not shown). This alert will be followed by an opportunity to reenter the code.
  • the necessary inputs to generate the registration code are as follows:
  • the software provider takes the inputs listed above, checksums them, mixes the inputs (including the RegName) and the checksum together in according to any one of a variety of algorithms, and encodes the result as a 16- bit number string. It will also be appreciated that the encoding and bit-mixing can be reversed and then, together with the RegName, the checksum can be used to verify the validity of the registration code.
  • the software provider will store registration codes separately for Freeware (Eudora Light), Adware (Sponsored) and Payware (Eudora Pro) software modes. Acceptance of a registrations code for one mode of operation does not imply that the registration codes for the other modes should be destroyed.
  • the software provider will allow a special-case MIME part to be mailed to the Eudora e-mail client.
  • the user receiving this part will automatically be asked to verify and enter the information. He/she can also execute the attachment again later. However, he/she cannot forward the attachment to anyone else using the Eudora e-mail client, because a special Content-Type attribute ("regCode") is required to activate the part, and the Eudora e-mail client can't send those.
  • regCode Content-Type attribute
  • the format of the MIME part (and the RegCode file) is that of a text file containing RFC822-header-style fields. It has a registered MIME type of application/vnd.eudora.data.
  • the fields included in the part are:
  • Eudora-File-Type field must be present.
  • the other fields listed above may or may not be present.
  • RegCodes mailed to the user should be validated prior to use. In order to be used, a RegCode should meet the following tests: ( Validity - An invalid RegCode should be ignored.
  • Fig. 5F An exemplary acceptance dialog box is illustrated in Fig. 5F.
  • the registration code is self- validating, since one part is a function of the other.
  • there is another sense of “validation” to be considered i.e., whether or not the registration code is "valid” for use with a particular version of Eudora. This is accomplished by comparing the ExpMonth in the registration code with a BuildMonth field the software provider will put into the application (in a place that cannot be overwritten by plug-ins, settings, etc.). If the ExpMonth and the BuildMonth correspond, the registration is deemed valid by the e-mail client.
  • Fig. 6A illustrates a state flow diagram of the process by which a Freeware user can become a Registered Free User. It will be appreciated that the state flow diagrams of Figs. 5 A and 6 A are similar in many respects.
  • Fig. 6A allows for an additional Nag dialog box, i.e., the so-called Feature Nag dialog box pictured in Fig. 6B, to remind both the Free User and the Registered Free User of the enhanced features available to Adware and Payware users.
  • Nag dialog box i.e., the so-called Feature Nag dialog box pictured in Fig. 6B
  • Fig. 6A the state flow diagram illustrated in Fig. 6A is very similar to that applicable to the Adware Users (Fig. 5A), with the exception that Freeware Users are given the option to try the full features rather than enter their demographic information. It should also be mentioned at this point that all users will receive an Update Nag dialog box (not shown) at a predetermined interval. Eudora checks the Update Page once per week during an e-mail session. If the Update page has changed, the user is nagged to update the Eudora e-mail software. Even if the page hasn't changed, the user is nagged on a 30-day schedule to check for updates, to ensure that he/she has the latest software version.
  • the Update Nag presents the user with versions to which he/she is entitled to upgrade (if any). See Fig. 7B.
  • the Nag itself is an HTML document with links to versions of the Eudora e-mail software for the user to download.
  • Fig. 8 illustrates an exemplary state flow diagram of the process by which a Box user can become a Paid user, i.e., a Payware user.
  • a Box user can become a Paid user, i.e., a Payware user.
  • the only Nag the software provider presents specifically to the Box users is the Registration Nag.
  • the Box user is converted into a normal Paid user.
  • the payment date for the Box user is set to a specific value by the software provider, so that the software provider can control what versions of the software the Box user will receive, e.g., the period of time for which the user will receive updates from the software provider for free going forward.
  • Nag Windows are modeless windows. The user can close them using close boxes, or dismiss them by taking one of their action items, or simply leave them open and let them drift wherever they will in the window list. Due to implementation constraints, Windows Nag Windows will be slightly different in behavior than MacOS Nag Windows, which are discussed below. The Nag Windows are floating windows; the software provider expects that the user will probably dismiss the Nag Window in fairly short order. It will be appreciated that the Nag Windows will not, however, stop background tasks from executing.
  • Nag Windows will be opened on top of all other windows, and no automatically opened windows, including, for example "Tip of the Day" and other dialog boxes and excluding other Nag Windows, will ever be placed above them until the user has manually brought another, non-Nag Window above them.
  • MDI Multiple Document Interface
  • MDI interface is also part of the Common User Access (CUA) standard set by IBM.
  • CUA Common User Access
  • Each MDI- compliant application enables you to open child windows for file-specific tasks such as editing text, managing a database, or working with a spreadsheet, to name but a few of the possible tasks.
  • Fig. 10 illustrates a flow chart for Nag Window display in MacOS versions of the Eudora e-mail software according to an exemplary embodiment of the present invention.
  • the software presents just the In mailbox, as denoted by the symbol (1), i.e., time (1).
  • the Eudora e-mail software determines that it needs to nag the user, and places the Nag atop the mailbox, as denoted by the symbol (2).
  • Some mail arrives in the "Fresh Meat" mailbox. Ordinarily, this would open on top.
  • the "Fresh Meat” instead opens below the Nag, as denoted by symbol (3).
  • the user manually brings Fresh Meat to the front, as denoted by symbol (4).
  • the Nag is no longer new, and More Meat can be opened on top in the normal manner, as denoted by the symbol (5).
  • the placement of Nag Windows in any of the Windows environments is, in general, considerably simpler. Nag Windows simply float outside the MDI box, above other floating windows, until the user closes them.
  • the exception to this rule is the Update Nag, which acts like a MacOS Nag Window, if the user assumes that the entire Macintosh diagram takes place inside an MDI box. Note particularly that this indicates that the Update Nag may be maximized in the Windows environment.
  • each schedule is a set of numbers representing (save for the last) the number of days since a given date (the Nag base).
  • the software provider further must keep track of the last time the user was nagged (the last lag). Note that both the Nag base and last Nag should be tracked separately for each type of Nag; the software provider must not mix values for Registration Nags and
  • the last number of the Nag Schedule is a repeat interval. Once the other Nags are all exhausted, the user is nagged each time this last number of days passes.
  • a Nag Schedule is to view the schedule as a timeline, as illustrated in Fig. 11. This particular timeline is for a Nag Schedule of [0,4,9,12,3]. Note that the Nags which will occur at the 15 and 18 day points are there because of the final number, the repeat interval (of 3 days). Thus, in Fig. 11, the user is due to be nagged if there is a Nag day greater than the last Nag and less than or equal to the current day. If more than one Nag day has passed, the user is still nagged only once.
  • the Eudora e-mail software advantageously includes a software subroutine which determines whether any Nags are due at application startup and at the completion of each mail check. With respect to the latter case, the software checks the modification date on the Update Page once per week during a mail check. If the Update Page has been modified during the past week, the software provider will download update information during the mail check, and nag the user to update his/her software, e.g., the Eudora e-mail software. See Fig. 7B. Finally, it will be noted that when a user's state changes so that an open Nag is no longer relevant, that Nag is closed and no longer displayed.
  • the major client issues involving ads are how the software displays the ads, when the software displays the ads, how the software obtains the ads, how the software provider obtains and transmits demographic information, and how the software provider verifies that ads are actually being displayed.
  • the main window of the Eudora e-mail software shows a squarish ad and three ad buttons in opposite corners of the main window.
  • this particular squarish ad isl44 pixels high by 128 pixels wide; the software will accommodate ads as large as 144 pixels by 144 pixels.
  • the area of the window usable by the mailboxes has been reduced approximately 38%; however, it will also be appreciated that the content area has been left untouched.
  • Fig. 3B illustrates an alternative main window where a small graphic or placard is employed, e.g., in the lower right corner, to indicate that the main window is sponsored.
  • the ad will consist of an image file, e.g., a GIF file, a PNG file, a JPEG file, etc., of not more than 15K, and not more thanl44 pixels tall by 144 pixels wide.
  • this image file will employ the Web Safe Color Palette.
  • This palette which is sometimes to as the Browser-Safe Palette, contains only 216 colors out of a possible 256 colors definable by 8-bits. The remaining 40 colors vary on Macs and PCs. By eliminating the 40 variable colors, this palette is optimized for cross-platform use.
  • the image file advantageously will be associated with a single uniform resource name (URN) to which users who click on the ad will be directed.
  • URN uniform resource name
  • Each advertiser will also specify the desired scheduling information for the ad, as discussed in greater detail below.
  • the advertiser may wrap the ad in HTML.
  • the software provider advantageously can also employ HTML-wrapped ads, since this will allow the software provider to include ad parameters as META tags in the HTML page, specify the link address, etc.
  • Toolbar icons will be requested in GIF format as well, but will actually be delivered to the client in a composite format and transformed into standard icons.
  • placards for sponsors of the Freeware version illustrated in Fig. 3B should be no more than 31 pixels tall, and on the order of 88 pixels wide, though the precise width can be varied at runtime.
  • the software provider when the user clicks on an ad, the software provider will normally take the user to the software provider's click- through counter and then redirect the user's browser to the link listed with the ad.
  • the click- through counter advantageously can be one of the software provider's servers, e.g., one of servers 302 and 303. It will be appreciated that this will require that the software provider will compose a URN which includes a server name, some tracking information, and the ultimate destination URN, and then the server will redirect the user's browser to the destination URN.
  • the software could initiate an online session.
  • the software could simply flag the link using the link history facility. See Fig. 12, which depicts a window/menu that the software maintains, similar to the history lists maintained by most browsers.
  • the software advantageously adds the link to the link history window, and flags this link so that the user knows he/she had wanted, but was unable, to visit that site during a previous e-mail session.
  • the software advantageously may be constructed to permit the user's browser respond to the click-through. It will be appreciated that some browsers have sophisticated features of their own for dealing with offline conditions, and the software provider shouldn't discount the idea that the user might wish to rely on them.
  • the software may permit transmission of the link to the browser for subsequent handling by the browser when it is online, i.e., the software can allow the user to tell the software provider to send the link to the user's browser the next time he/she is online.
  • the software provider will, in an exemplary and non- limiting case, mandate that the following standard for all advertisements submitted by advertisers:
  • the software provider advantageously can convert the GIF file to a PhotoShop (PNG) file, but this is transparent. It should be noted that the software provider will not presently accept PNG ads directly, because of the gamma bugs in PhotoShop.
  • URN A single URN of not more than 900 characters. There are suspected limits of IK on URN size. Limiting the customer's URN to 900 characters will allow the software provider to annotate the URN and still stay within the IK limit.
  • Toolbar buttons i.e., the buttons in the upper right-hand corner of Fig. 3A have the same requirement as standard ads, except for the following: ( Both 16x16 and 32x32 sizes required. These are the sizes the client supports, the software provider needs them both.
  • the spot has the same requirement as standard ads, except for the following:
  • the software performs a check to determine that the ad is both onscreen and uncovered. If the screen state does not satisfy both of these criteria, the software will either nag the user to uncover the ad or automatically re-order the windows so that the ad is uncovered. If the user persists in covering the ad for a predetermined period of time, the software will automatically devolve to freeware mode.
  • the software provider is clearly motivated to ensure that all Eudora users are actually looking at the ads. Stated another way, displaying an ad on the screen of the client computer 100a, for example, while the user is in another room does not justify the expense of the ad for the advertiser. For that reason, the software includes functions which permit measurement of the actual time that the user is in front of the computer while the ad is present.
  • the best thing the software can do to measure user attention is to monitor for user input to the client computer 100a, thus verifying the user's presence in front of the display device 208.
  • the primary user input devices to the client computer 100a are the mouse 204 and the keyboard 203
  • the e-mail client will monitor for both mouse and keyboard operation by the user when the Adware version of the Eudora e-mail client is frontmost, and periodically report this activity back to, for example, the software provider.
  • the user will be considered "present and accounted for” if the mouse moves significantly, if a mouse button states change, or if keys are pressed or released.
  • the software will consider a period before and after such an event as "face time" for the ad.
  • the software measures the period and refers to the total length of this period as kFacelnterval. There is no need to be overly precise about this value, e.g., a kFacelnterval of sixty (60 )seconds, which begins with a user event, is employed in the exemplary, non-limiting case being discussed.
  • the general methodology for obtaining ads for display is to connect to a QUALCOMM INCORPORATED site during a mail check, or some other time when the software senses a live network connection, and download ads into a local cache. It will be appreciated that the act of downloading the ad can be the trigger for billing the advertiser, in order to avoid the necessity of collecting billing information from individual clients. In contrast, proprietary systems such as that provided by JUNO, upload ad display data to the designated e-mail server whenever the user accesses his/her e-mail account for any reason.
  • Fig. 13A is a table listing the assumptions used in determining the impact of ad transmission on e-mail program operations; Fig.
  • FIG. 13B is a table listing the bandwidth requirements in terms of the subscriber base versus of the number of new ads to be downloaded each day to the subscribers. The implications of these calculations are as follows. Given that the goal is for an average turnover of an ad is, for example, three days, the top line in the table illustrated in Fig. 13B would be the one used by the software provider. The worst-case, i.e., maximum bandwidth, scenario would be to turn over, for example, 25 ads a day. These values are highlighted in the table of Fig. 13B.
  • the software provider advantageously employs a PlayList.
  • the PlayList is in its essence a list of URNs from which to fetch the actual ads as well as a set of attribute-value pairs, on a per-ad basis. The exact format of the PlayList is discussed in greater detail shortly. PlayLists will specify the complete set of ads the client should have, along with parameters for displaying those ads, as discussed immediately below. It should be noted that ads may appear in a PlayList but not be scheduled for display for a long time (or even at all). The presence of such ads in the PlayList will cause the client to retrieve the ads for storage on the client for future display.
  • the general requirements for the PlayList are as follows:
  • the request for a PlayList will contain information to help the PlayList server determine what ads a copy of Eudora is required to fetch.
  • the PlayList can also contain parameters for Eudora as a whole, including the ability to modify how often New PlayLists are checked for.
  • PlayLists are allowed to specify whether or not they should replace all older PlayLists or merely be merged with them. It should be mentioned that the merge function will allow a more web-like advertising model, e.g., a model employing a rotating ad pool, should the software provider choose to employ such a model.
  • Fig. 14 is a state flow diagram of an exemplary ad fetch process according to the present invention, and Fig. 1.
  • the client software running on client computer 100a identifies itself to the PlayList server 302, e.g., ads.eudora.com.
  • the client software e.g., the Eudora software, provides to the PlayList server 302 basic client information and the ID of the PlayList the client software currently has installed.
  • the ads.eudora.com server responds with either an indication that the current PlayList is still valid, uses an Hyper Text Transfer Protocol (HTTP) redirect to send the client to a different PlayList server, e.g., another PlayList server 302', or responds directly with the New PlayList from PlayList server 302. See Fig. 14.
  • HTTP Hyper Text Transfer Protocol
  • the client software compares the New PlayList with its current set of ads, and begins fetching ads not resident in the e-mail client's ad cache from one of more ad servers, e.g., the ad server 303 illustrated in Fig. 1, according to URNs included in the PlayList.
  • the client software also deletes ads not currently appearing in the PlayList.
  • the client software performs a check for a New PlayList every three days. It should be mentioned that the 3 day interval between PlayList checks is arbitrary and applicable only to the exemplary preferred embodiments of the present invention being discussed. It should also be mentioned that the ads preferably will be fetched as needed to fill the PlayList, possibly over many mail checks. Moreover, the ad fetch process will be limited to one minute per mail check, irrespective of the tasking of either the e-mail client software or the client computer 100a. After one minute, the client software will disconnect from the ad server 303. This will often mean that the e- mail client software has not filled the PlayList when the ad fetch operation is terminated. This is acceptable. The software will utilize the available ads while the remaining ads are being downloaded.
  • the software provider advantageously can provide for multiple servers on a peer with ads.eudora.com server 303. It will be appreciated that these servers will provide extra ads for some Eudora user communities, e.g., all of the users at a company serviced by one ISP, etc. Stated another way, an ISP which provides additional services such as local and long distance telephone access may wish to cross promote these services to its own customer base. Thus, the ISP advantageously can contract for such localized promotion.
  • the PlayLists transmitted to the ISP's branded Adware e-mail clients would be linked to an ad server 303" maintained by the ISP in that instance.
  • the PlayLists provide certain global inputs to the ad scheduling algorithm, including the parameters listed in the table immediately following.
  • the software also keeps track of and reports these values to the software provider for every ad:
  • the software provider implements three major states of the ad scheduler, the regularState, the runoutState, and the rerunState.
  • the regularState the e-mail client software advantageously is showing regular ads and accounting for them. It will be appreciated that this is what actually generates charges for the bulk of the ads displayed on the e-mail client.
  • the runoutState is selected when the e-mail client software has shown enough regular ads to fill the assigned faceTimeQuota, and the ad cache includes one or more runout ads available for showing.
  • the e-mail client software has exhausted both its regular ad quota and the runout ads, i.e., the e-mail client software is now reshowing the regular ads, but the software provider is not charging for them.
  • the software provider advantageously can provide a custom installer to various ISPs, book publishers, etc., that will label or brand the copies of Eudora that they have distributed.
  • the software provider will then credit these distributors with a percentage of the ad revenue generated by the clients they distribute. It will be appreciated that these credits may be offset by cross promotional activities associated with each branded version of the Adware e-mail client, for the reasons previously discussed.
  • the PlayList is a way to control the fetching and display of ads in software, e.g., in the Eudora e-mail client.
  • the primary benefits associated with the PlayList are the separation of ad parameters from ad images, insulation of the Eudora client from intimate knowledge of ad image servers, and centralized server intelligence in ad distribution, without requiring user registration or centralized user databases.
  • PlayLists are extremely malleable objects.
  • the PlayLists can exert varying degrees of control over how the Eudora client behaves, from specifying the exact set of ads Eudora runs to simply transmitting abstract URNs which will choose their own ads.
  • PlayLists are used to their fullest advantage, they will give the software provider a powerful tool in controlling ad display in software such as Eudora; if PlayLists are later deemed irrelevant, the PlayLists cost the software provider one extra, brief network connection per day.
  • the client computer 100a connects to a PlayList server 302 (which may redirect to a different server 302') via a network 200. Then, the PlayList server 302 returns a PlayList to the client computer 100a via the network 200. Subsequently, the e-mail client software on the client computer fetches the ads specified in the PlayList.
  • the PlayList Request which is sent by the Eudora client to the PlayList server 302 in order to initiate the ad fetch process, is not a simple burst of binary code.
  • the PlayList Request is a block of extensible markup language (XML) code employed to provide the server 302 with sufficient information to build or select the proper New PlayList for the user.
  • the information in the PlayList Request is shown in the following table.
  • PlayList server 302 preferably ignores requests that fail checksum verification.
  • the server 302 replies with a
  • PlayList Response is divided into two major sections; the Clientlnfo section, which updates general client behavior regarding ads, i.e., speed with which the ads turn over, and the New PlayList itself, which describes the ads the client should fetch.
  • the PlayList Server e.g., server 302
  • every PlayList Response is checksummed with MD5, just as the PlayList Request is.
  • the MD5 digest is encoded in hexadecimal and put in a "CheckSum" header in the PlayList Response.
  • the e-mail clients ignore PlayLists that fail checksum verification.
  • the e-mail client sometimes becomes, for lack of a better term, befuddled due to old client bugs, server bugs, etc.
  • the bad data inherited by even an updated client is too garbled for the system to function properly.
  • the client could be programmed to detect this condition, it is preferable to leave the task, i.e., error detection, to the server, which can be changed more easily.
  • the PlayList server 302 responds with just a single command: reset. No Clientlnfo should follow, no PlayList should follow, just the reset command.
  • the client On receiving the reset command, the client discards its accumulated ad databases and records, including PlayLists, faceTime history, ad history, ad caches, etc. Everything is reset to the pristine condition that the e-mail client software had before the Adware software was run for the very first time. It should be mentioned that Link History is exempted from the reset command, both for reasons of practicality and because it is so user-visible. The only other item of ad data that reset does not affect is the ad failure counter, which should be retained across a reset. The client should then recognize that it has no PlayList, and make another request to the PlayList Server for the needed PlayList.
  • the Clientlnfo section updates various client parameters. The parameters are listed immediately below.
  • the Clientlnfo section is a powerful feature of PlayLists. It allows the software provider to control the application in a global way, including segueing smoothly from one ad model to another. It will be appreciated that if this were the only benefit the software provider derived from PlayLists, it alone would make implementation of PlayLists worthwhile.
  • the PlayList Response is divided into two major sections; the Clientlnfo section, which updates general client behaviors, and the New PlayList itself, which describes the ads the client should fetch.
  • the New PlayList itself has one global value, PlayListlD.
  • This id is the id value that the client returns to the PlayList server the next time the client computer 100a connects to the PlayList server 302. It will be appreciated that this PlayListlD advantageously can be included in the PlayList Request, or can be separately uploaded to the PlayList server in a myriad of forms, e.g., as a cookie.
  • the remainder of the PlayList is a list of ads.
  • the parameters include the scheduling parameters, which are described in detail above, and ad information, which includes the information listed immediately below.
  • URN Uniform Resource Name
  • URL Uniform Resource Locator
  • URI Uniform Resource Identifier
  • PlayLists are flexible enough to support many ad models. PlayLists are crucial to some ad models, to others they are helpful but not central, to still others they are marginally useful, but do not present significant impediments.
  • the use of PlayLists does not predispose the software provider towards any specific ad model; the PlayLists advantageously can be used to support any ad models that the software provider chooses. Indeed, PlayLists permit the software provider to switch between ad models midstream, should the software provider decide to do so.
  • Figs. 16A and 16B in an effort to illustrate how PlayLists would be used for each ad model. It will be appreciated that this will demonstrate the essential neutrality of the PlayList concept to the ad model.
  • Fig. 16A illustrates the ad model associated with persistent ads while Fig.
  • 16B depicts the parameters associated with a short-lived ad model.
  • One thing to notice here is how few of the parameters from any of the sections appear in the chart. It will be appreciated that varying as few as five parameters advantageously causes the Adware to shift between these two distinct ad modes. That's because they are largely not relevant to the choice of ad model.
  • the parameters will either be used or not, irrespective of the ad model.
  • the software provider can implement blank space after an ad in any model, and the software provider can eschew blank space after an ad in any model. Most of the parameters fall into this it-just-doesn't-matter category.
  • the software provider accepts many ads; either from many advertisers or only a few advertisers. Ads do not persist for many days; they're used up and discarded at a relatively rapid rate.
  • PlayLists will be used additively. Each time the client runs low on ads, it will ask for another PlayList which will describe a few more ads to mix with the clients' existing ads. When ads exceed their allotted time, the ads are discarded.
  • the PlayList server really only serves to transmit parameters for ads. However, that is acceptable, since the parameters have to be transmitted somehow, after all.
  • the software provider wants to mix ad models, e.g., desires to provide a mix of long-running ads and short-lived ads. How this situation is handled depends on the stoichiometry. If the cache is or will be filled with mostly persistent ads and only a few short-lived ones, the software provider can merely increase the reqlnterval and use PlayLists as in the Persistent Ad Model. In other words, the software provider merely picks a few random ads to go on each PlayList, and picks a few more random ads to go on the next PlayList, which the client will fetch the next day. If, on the other hand, the cache will contain mostly short-lived ads and only a few persistent ads, the computer system 10 will use multiple PlayLists. One PlayList will list the persistent ads, as discussed above; the remaining facetime will be filled using PlayLists of short-lived ads.
  • PlayLists can be used to support widely differing ad models.
  • the reason PlayLists can do this is that they're really only an extra level of server control and in between Eudora and its ads.
  • the software provider will distinguish between these two situations by asking a simple question, i.e., is the user sending or receiving mail? If the answer is yes, the software provider will assume that the blocking of ads is something the software provider needs to address. The way the software provider addresses this issue is with an escalating series of Ad Failure Nags. These will continue for two weeks or until the software receives ads. For every two days the software does receive ads, the software will decrement the Ad Failure Nag timer by one day. If the timer runs out, the software will display an apology to the user, revert to the Freeware version, and mark the user's software as owned by a Deadbeat User.
  • Deadbeat Users will only be allowed to return to Adware if the ad server can be connected to at the time the user attempts to return to Adware. See Figs. 17A -17C. It should be noted that if the software provider should ever decide to retire Eudora and wish to let people use it without ads, the software provider can simply publish a permanent registration code.
  • the e-mail client advantageously includes several more sophisticated functions for determining that an ad failure condition requires the employment of the Ad Failure Nag discussed above.
  • the client device can identify an ad download failure condition when a corresponding ad download function has failed to downloads during a predetermined period of time.
  • the e-mail client device can identify an ad display failure condition when a corresponding ad display function has failed to display ads for a predetermined time period, e.g., the time(s) specified in the New PlayList received from the PlayList server and /or the current PlayList(s) stored for use by the e-mail client device. Either condition invokes the Ad Failure Nag function discussed above.
  • An exemplary audit scheme contains the following features:
  • the software provider will also, at random, ask particular users for their permission to audit transactions in detail with the server. This will allow the software provider to correlate client and server behavior. Additional details on instrumentation applicable to the exemplary Eudora e-mail client software is provided in Figs. 18B -18E.
  • Figs. 5 A, 6 A, 7A, 8 and 9 referred to a plurality of web pages, i.e., HTML pages that can be accessed and retrieved from one of the software provider's servers, e.g., registration server 301. See Fig. 1.
  • the software provider's servers e.g., registration server 301.
  • Fig. 1 The general purposes of these pages and the URNs which the software uses to access these pages will now be described in greater detail below.
  • the client it will be appreciated that it will be helpful for the client to give the server information to help the server direct the user to the proper location or to assist the user by prefilling certain items on Web page based forms. That is the function of the query part of the URNs.
  • the elements that might go in query parts are listed below. It will be noted that the query parts are divided into two groups. The first group includes items which are considered personal, and great care should be taken to transmit them only when appropriate; the second group includes items which are not considered to be privacy-sensitive.
  • the PLS is a server side program which services HTTP requests and returns HTTP responses. It will be appreciated that each request launches a different thread, and that the data format of communications between the client and the PLS is XML-encoded in the exemplary embodiment.
  • the PLS advantageously can be instantiated using the following Java ® packages.
  • the PLS parses the XML request and builds objects that represents the client update request. It will be noted that data access is performed using SAX.
  • the PLS stores the client request information in a so-called ClientUpdate table (not shown).
  • the PlayList Request can be received from a plurality of e-mail clients residing on the client computers generally denoted lOOn through any given day.
  • the software provider advantageously can employ the following semantic to avoid repetitive Statement generation:
  • PreparedStatement ps conn.prepareStatement("INSERT INTO ClientUpdate (date, userAgent, PlayListldN) values (?, ?, ?, ?,..)");
  • Servlet advantageously can employ both SQL queries and programming filtering. It will also be appreciated that these processes are synchronized in order to prevent conflicts when accessing the database.
  • Appropriate pseudo code of generating a PlayList is depicted in Figs. 21 A and 21B.
  • the first block of pseudo code in Fig. 21A generates an ad list. It will be appreciated that the ad list generated by the first block of pseudo code holds all the image ads that are active and can be delivered within a predetermined time frame.
  • the second block of pseudo code listed in Fig. 21 A calculates the time needed to deliver the ads.
  • the third block of pseudo code which is illustrated in Fig.
  • the package XP Writer provides a set of methods for creating specific kinds of nodes in the output XML code, i.e., file.
  • the PLS stores the information generated in response to a request in two tables, a PlayList general response table, which holds the client info section and
  • PlayList general information and a PlayList specific response, which holds the entry section. It will be appreciated that the PLS advantageously can use the prepared statement API to optimize performance in response to a query.
  • FIG. 20 that figure illustrates a class diagram which advantageously describes the representation and rendering of the PlayList, as will as the PlayList Response. It will be appreciated that this class diagram includes repeated XML Write method calls; these method calls are employed by
  • Fig. 22 that figure illustrates the major PlayList Servlet Classes, which collectively define the PlayList Servlet. More specifically, the PlayList Request class handles the request and subsequently maps the XML request to the ClientUpdate object while the PlayListResponse class handles the response and writes the clientUpdateResponse back to the client. In addition, the PlayListsGenerate class generates the PlayLists while the DBManager class handles the Data Base connection pool. Additional details are readily apparent from Fig. 22.
  • one exemplary embodiment of the present invention encompasses software for converting a general purpose computer into a specialized PlayList server for supplying a PlayList Response to a client device for exchanging information with an information server system over a communications network and storing ads.
  • the software instantiates a PlayList Response generation function for generating a PlayList Response identifying a plurality of selected ads to be presented by the client device, and a first communications function that completes a PlayList Response send communication link with the client device via the communications network over which the PlayList Response is transmitted to the client device, wherein the information server system and the PlayList server are independently controlled.
  • the PlayList directs the presentation, e.g., display, of ads on the client device, e.g., an e-mail client
  • the ads advantageously may be delivered to or retrieved by the client device in any number of ways in this preferred embodiment.
  • the PlayList Request preferably includes ad identifiers and ad presentation instructions; corresponding uniform resource names (URNs) can be included but may be omitted.
  • the present invention encompasses software for converting a general purpose computer into a specialized PlayList server for supplying a PlayList Response to a client device exchanging information with an information server system and receiving ads from an ad server over a communications network.
  • the software advantageously includes a PlayList Response generation function for generating a PlayList Response identifying a plurality of selected ads to be presented by the client device, and a first communications function that effects a PlayList Response send communication link with the client device via the communications network over which the PlayList Response is transmitted to the client device.
  • the information server system and the PlayList server are independently controlled.
  • this exemplary and non-limiting embodiment of the present invention contemplates a specific communications channel between the client device and a dedicated ad server (system) for delivery of ads defined by the PlayList.
  • the PlayList Request employed by this exemplary embodiment includes both information dictating presentation of the ads and /or operation of the client device with respect to ad presentation functions, and the name and URN for ads included in a New PlayList.
  • the present invention provides software for converting a general purpose computer into a specialized
  • PlayList server for supplying a PlayList Response to a client device exchanging information with an information server system and receiving ads from an ad server over a communications network, including:
  • PlayList Response generation function for generating a PlayList Response identifying a plurality of selected ads to be presented by the client device
  • a PlayList Request parsing function for extracting selected information from the PlayList Request
  • PlayList generation function receiving an output of the database driver function for generating a PlayList for inclusion in the PlayList Response which identifies a plurality of selected ads to be presented by the client device in response to receipt of a PlayList Request
  • the PlayList Request parsing function includes an extensible markup language (XML) parsing function for verifying the wellformedness of the PlayList Request, a PlayList analysis function receiving the PlayList Request after verification by the XML parsing function for generating an object, and a database driver function receiving the object for building a query from the object and applying the query to a PlayList server database.
  • XML extensible markup language
  • PlayList Response generation function is initiated by receipt of a PlayList Request, which, in an exemplary case, includes the name of the current PlayList(s) employed by the client device providing the
  • PlayList Request While each of the numerous client devices connected to an information server generate a PlayList Request, the discussion of this specific aspect of the present invention, i.e., the PlayList server, can best be understood from the point of view of a system including only one client device; the actual implementation of the, for example, e-mail client device contemplates the use of thousands of client devices.
  • the PlayList Request advantageously can include information regarding the currently running PlayList(s) on the client device, and user data fields that store data regarding the progress made by the client device in presenting, e.g., displaying, the ads stored by the client device.
  • An exemplary and non-limiting list of the information that can be provided to the PlayList server via the PlayList Request includes:
  • the PlayList Request parsing function can extract selected information from the PlayList Request and employ the selected information and other information, e.g., information provided by the entity controlling the PlayList server, in generating the PlayList Response.
  • the PlayList Request may include all or a subset of the information listed immediately above; the PlayList Request parsing function extracts information contained in at least one of the user data fields.
  • the receipt of the PlayList Request by the PlayList server initiates generation of the PlayList Response.
  • the PlayList Response generation function In response to the PlayList Request, the PlayList Response generation function generates one of an action command and the PlayList Response. With respect to the former, the PlayList Response generation function advantageously can generate the action command in response to receipt of a garbled PlayList Request. This can be generally thought of as an error code directing the client device to send a New PlayList Request. It will be appreciated that the action command can include an associated error message, which is presentable to the user by the client device. Alternatively, the action command may cause the client device to delete all of the ads received and /or stored by the client device responsive to a command issued to the PlayList server by an entity controlling the PlayList server.
  • the entity controlling the PlayList server e.g., the software provider
  • specific PlayList Requests e.g., PlayList Requests generated by a particular software version, of all PlayList Requests.
  • the PlayList Response advantageously includes both client information, information regarding how the client device, e.g., a PDA device, is to present, e.g., display, the selected ads, i.e., the ads that during the time period following receipt of the PlayList Response by the client device, and a New PlayList.
  • client information can, in an exemplary case:
  • the client information when the ads available to the client device include both current ads (paid ads) and expired ads (free ads), the client information includes a minimum time period during which the client device presents the current ads before the client device presents the expired ads.
  • the client information may also establish a maximum time period during which the client device is permitted to present the expired ads.
  • the PlayList Response advantageously may include commands or selected parameters which direct the client device to either concatenate the New PlayList to the current PlayList(s) or discard the current PlayList(s) in favor of the New PlayList.
  • the command, or the selected parameters, controlling this facet of the client device operation is executed upon receipt of the PlayList Response by the client device over the effected communications link.
  • the New PlayList included in the PlayList Response includes a name and a corresponding Uniform Resource Name (URN) for each of the selected ads.
  • URN Uniform Resource Name
  • the URN can correspond to one of a storage location of the respective named ad on an ad server or a location on the ad server redirecting the client device to a location on another storage device for the respective named ad.
  • the URN specifies a location on the ad server redirecting the client device to an ad storage location collocated on the ad server for the respective named ad.
  • the New PlayList may also include information identifying an ad type, i.e., postage stamp ad, toolbar ad, or placard ad, for each one of the respective selected ads.
  • an ad type i.e., postage stamp ad, toolbar ad, or placard ad
  • the PlayList server instantiated by software stored on the server computer 302 advantageously responds to a PlayList Request written, i.e., coded, in extensible markup language (XML).
  • XML extensible markup language
  • the PlayList Request advantageously can have an associated document type definition (DTD).
  • DTD document type definition
  • the PlayList server should have the DTD available, i.e., available to the PlayList Request parsing function. There are several options for ensuring that the DTD is available to the
  • the DTD for each of different types of client devices e.g., e-mail client device or PDA
  • the PlayList Request need only include a DTD tag, which identifies the particular
  • DTD advantageously can be embedded in the PlayList Request. In either case, both the PlayList server and the client device implicitly use the same DTD. It should be mentioned that the software provider should make provisions with respect to ad security. There are really two security issues to consider. One is whether or not the client is getting valid ads (call this client security), and the second is whether or not a valid client is fetching ads (call this server security).
  • PlayLists and ads advantageously can be checksummed with MD5 (or another mechanism), and the checksums recorded in the PlayList. Then the client can checksum the PlayList and ads using the same secret seed, and compare its checksums to those in the PlayList. If it fails to get the proper ads, this will be treated as a failure to get ads at all.
  • Server-side security is potentially a much bigger problem.
  • the software provider intends to charge advertisers for ads, based on the understanding that the software provider's users will actually see the ads the software provider is charging for. To do this with confidence, the software provider should ascertain that it is actually Eudora that is downloading the ads, and not some rogue process written to fetch many ads. Why would someone bother to fetch ads? While the software provider can't discount the "because they can" motivation of the amateur hacker, the real issue is the ad revenue, i.e., ad bounty. Because every ad fetch can generate revenue for a third party, there is a very significant financial incentive for that third party to cause a lot of ad fetches.
  • Statistical analysis has some significant benefits, but also significant drawbacks.
  • the benefits include minimal work in the client (and hence no vulnerability to disassembly, etc.), no run-time burdens on either the client or the server, i.e., everything can be done "after the fact" during accounting runs, easily changeable from the software provider's end, ability to be applied retroactively, etc.
  • the drawbacks to statistical analysis include that statistical analysis will never be entirely certain, and that the software provider may not collect the proper statistics, etc.
  • the software provider Before the software provider gathers or transmits any data that might identify the user to the advertiser, the software provider should obtain the user's explicit (See Fig. 18A) or near-explicit permission.
  • the term near-explicit is employed to denote that the software provider may, for example, put a special privacy warning in the web page where the user registers a software program such as Eudora.
  • Eudora a software program
  • the user is clearly taking an action to submit data to the software provider; as such, explicit permission shouldn't be needed.
  • the software provider should go out of its way to identify areas where an unreasonable user might be able to claim that he/she didn't know he/she was giving information to the software provider, and ask for explicit permission there, even if it seems relatively obvious to the software provider.
  • the software provider should maintain payment information separate from registration information, and both types of information should be maintained separate from demographic information, etc. While it may be very helpful to correlate databases, the software provider faces potential crucifixion if the databases are actually correlated. Moreover, since the software provider can still deliver very targeted advertising without database correlation, the software provider should maintain separate databases.
  • the present invention encompasses a multi-moded software product, e.g., e-mail software, which includes three "self-contained” different versions (or, “modes"), including a "first full feature set” version which is activated when the software product is paid for by the user (i.e., a "Payware version”), a "second full feature set” version which is activated when the user agrees (e.g., either by default or by explicit agreement) to accept advertisements delivered to the client device in order to subsidize the software product (i.e., an "Adware” version), and a "reduced feature set” version which is activated when the software product is not paid for (i.e., a "freeware” version) and the "second full feature set” version is not activated.
  • a multi-moded software product e.g., e-mail software
  • three “self-contained” different versions or, "modes”
  • a first full feature set” version which is activated when the software product is
  • the present invention also encompasses a system and method for automatically distributing advertisements to a multiplicity of client devices that have such multi-moded software installed thereon.
  • the first and second full feature sets are identical with respect to e-mail support features; it will also be appreciate that the second full feature set includes PlayList and ad fetching and display features which are dormant in the first full feature set.
  • the present invention further encompasses multi-moded software as set forth above, wherein the multi-moded software includes a mode switching function which automatically switches from the "Adware" version to the "freeware” version upon detecting a prescribed condition (e.g., based upon monitored user activity level, and /or less than a prescribed number of ads having been downloaded, i.e., "deadbeat user” criterion).
  • a prescribed condition e.g., based upon monitored user activity level, and /or less than a prescribed number of ads having been downloaded, i.e., "deadbeat user” criterion.
  • the present invention also encompasses a system and method for automatically distributing advertisements to a multiplicity of client devices that have such multi-moded software installed thereon.
  • the present invention further encompasses multi-moded software as set forth above, wherein the multi-moded software includes a mode switching function which automatically switches from the "Adware" version to the "freeware” version upon detecting occurrence of a prescribed "ad failure condition", e.g., less than a prescribed number of ads having been received and /or displayed by the client device within a prescribed time period, and an "Ad Failure Nag” function which monitors "time since last Nag” and which generates an "Ad Failure Nag” according to a "Nag Schedule” which is dynamically varied based on the monitored "time since last Nag” information and/or based on cumulative ad download /display statistics or information.
  • the present invention also encompasses a system (and method) for automatically distributing advertisements to a multiplicity of client devices that have this multi-moded software product installed thereon.
  • the present invention further encompasses multi-moded software as set forth above, wherein the multi- moded software includes a Nag function which generates different types of Nags dependent upon the current mode of the software product which is currently activated, and/or based upon time since the last Nag was generated, and/or based on cumulative ad download /display statistics or information, and/or based on other monitored conditions.
  • the different types of Nags could include a "Registration Nag”, a "Payware Nag”, an "Adware Nag”, an "Update Nag”, and an "Ad Failure Nag”.
  • the present invention also encompasses a system (and method) for automatically distributing advertisements to a multiplicity of client devices that have this multi-moded software product installed thereon.
  • the present invention encompasses a software product (e.g., e-mail software) that incorporates an automatic advertisement download function for automatically downloading advertisements to be displayed when the software is activated, and a control function for monitoring user activity levels and for controlling the display of downloaded advertisements at the client device based upon the monitored user activity levels (e.g., based upon "discrete” and /or "cumulative" ad display parameters).
  • a software product e.g., e-mail software
  • an automatic advertisement download function for automatically downloading advertisements to be displayed when the software is activated
  • a control function for monitoring user activity levels and for controlling the display of downloaded advertisements at the client device based upon the monitored user activity levels (e.g., based upon "discrete" and /or "cumulative" ad display parameters).
  • the present invention also encompasses a system and method for automatically distributing advertisements to a multiplicity of client devices that have this software product installed thereon.
  • the present invention also encompasses an e-mail software product that incorporates a control function for automatically downloading advertisements from a remote server system which is separate and independent from the e-mail server system, as well as the system and method for automatically distributing the advertisements to client devices which have this e-mail software product installed thereon.
  • the system includes an ad server system that manages, administers, and controls the distribution of advertisements, and which is controlled by a control entity (e.g., one operated by the present assignee, QUALCOMM INCORPORATED) which is separate and independent from the control entity which controls the e-mail server system which provides e-mail services to any particular client device which has this e-mail software product installed thereon.
  • ad server system and the e-mail server system are operated independently, i.e., under the control of separate and independent control entities.
  • the present invention also encompasses a software product, e.g., e-mail software, which incorporates an automatic advertisement files download function for automatically downloading advertisements from a remote server system to a client device on which the software product is installed, and a control function for locally controlling the display of downloaded advertisements at the client device based upon ad parameters included in the downloaded advertisement files, e.g., including (for each ad), various combinations and sub-combinations of the following ad parameters, namely, the maximum ad display time, or face time, for any given display of that particular ad, the maximum total /cumulative ad display time, or face time, for that particular ad, the maximum number of times to display that particular ad per day, the date /time before which that particular ad should not run, and the date /time after which that particular ad should not run.
  • the present invention also encompasses a system and method for automatically distributing advertisements to a multiplicity of client devices that have this software product installed thereon.
  • the present invention also encompasses a software product, e.g., e-mail software, which incorporates an automatic advertisement download function which fetches a PlayList from a remote server system (e.g., a PlayList server system) which specifies the advertisements to be fetched by the client device on which the software product is installed and the source addresses (e.g., URNs) of the ad servers on which the specified advertisements are stored, fetches the advertisements specified in the fetched
  • a software product e.g., e-mail software, which incorporates an automatic advertisement download function which fetches a PlayList from a remote server system (e.g., a PlayList server system) which specifies the advertisements to be fetched by the client device on which the software product is installed and the source addresses (e.g., URNs) of the ad servers on which the specified advertisements are stored, fetches the advertisements specified in the fetched
  • a remote server system e.g., a PlayList server system
  • the present invention further encompasses a system and method for distributing advertisements to client devices which have this software product installed thereon, including a PlayList server (or PlayList server system) which, in response to a PlayList Request from a particular client device that includes a client PlayList identifier, compares a client PlayList identified by the client
  • PlayList identifier with a current PlayList (which may optionally be customized to that particular client device) stored on the PlayList server, and then sends back to the client device a New PlayList which specifies the new advertisements to be fetched by the client device, and the source addresses of the ad servers on which the specified new advertisements are stored.
  • the above-described automatic advertisement download function of the software product installed on the client device can delete (discard) all or PlayList server-specified ones of the advertisements which are currently stored on the client device, e.g., those which are not specified in the current PlayList; and/or the above-described automatic advertisement download function of the software product installed on the client device can merge the New PlayList with the current client PlayList.
  • the present invention also encompasses several variations and details of implementation of this novel PlayList/ad fetch process utilized in the Eudora Adware scheme.
  • the present invention encompasses a software product, e.g., e- mail software, which incorporates a custom installer which identifies the specific software product distributor that distributed that software product.
  • the present invention further encompasses a software product, e.g., e-mail software, which incorporates an automatic advertisement download function for automatically downloading advertisements from a remote server system to a client device on which the software product is installed, and a custom installer which identifies the specific software product distributor which distributed that software product, for the purpose of facilitating apportionment of advertising revenue the software product vendor receives from advertisers to specific software product distributors.
  • the present invention also encompasses a system (and method) for automatically distributing advertisements to a multiplicity of client devices which have this software product installed thereon, wherein the system includes a centralized control facility which receives software product distributor ID information from the client devices and uses this software product distributor ID information to facilitate apportionment of advertising revenue the software product vendor receives from advertisers to specific software product distributors.
  • a central database function which identifies (e.g., by means of cross-referencing and /or correlation tables) the software product distributor ID for each software product distributed by the software vendor, e.g., based on a serial number or reference code associated with each copy of the software product, can be utilized.
  • the present invention encompasses a software product, e.g., e-mail software, that incorporates an automatic advertisement download function for automatically downloading advertisements from a remote server system to a client device on which the software product is installed, and a control function which utilizes a built-in "deadman timer" to impose a time limit for each particular advertisement download session, e.g., the client device will be disconnected from the remote server system upon expiration of the time limit imposed by the "deadman timer".
  • the present invention also encompasses a system (and method) for automatically distributing advertisements to a multiplicity of client devices that have this software product installed thereon.
  • the present invention can be characterized as a software product, e.g., e-mail software, that incorporates an automatic advertisement download function for automatically downloading advertisements from a remote server system to a client device on which the software product is installed, and an instrumentation and auditing module having various novel features /functions, e.g., maintaining a rotating log of ad- related statistics and /or performing random and /or statistically -based ad effectiveness audits with user permission.
  • a software product e.g., e-mail software
  • an automatic advertisement download function for automatically downloading advertisements from a remote server system to a client device on which the software product is installed
  • an instrumentation and auditing module having various novel features /functions, e.g., maintaining a rotating log of ad- related statistics and /or performing random and /or statistically -based ad effectiveness audits with user permission.
  • the present invention also encompasses a system (and method) for automatically distributing advertisements to a multiplicity of client devices that have this software product installed thereon, wherein the system includes a centralized control facility for obtaining ad-related statistical information from selected client devices, in a random or statistical manner, e.g., for the purpose of monitoring the integrity and /or effectiveness of the advertisement distribution system.
  • the present invention encompasses a software product, e.g., e- mail software, that incorporates an automatic advertisement download function for automatically downloading advertisements from a remote server system to a client device on which the software product is installed, and a "link history" function which enables the user to review previously-viewed advertisements, e.g., by providing a graphical user interface (GUI) which includes a link history window that lists links the user has previously visited and ads that have been previously displayed to the user, along with some status information on each.
  • GUI graphical user interface
  • a mechanism will be provided to enable the user to select an ad listed in the link history window for display, e.g., by single-clicking the appropriate ad link, and to enable the user to visit the source Web site of any given ad listed in the link history window, e.g., by double-clicking the appropriate ad link.
  • the present invention also encompasses a system (and method) for automatically distributing advertisements to a multiplicity of client devices that have this software product installed thereon.
  • the present invention encompasses a software product, e.g., e-mail software, which incorporates a "Nag” function that monitors "time since last Nag” and that "nags” the user according to a "Nag Schedule” which is dynamically varied based on the monitored "time since last Nag” information.
  • a software product e.g., e-mail software
  • e-mail software which incorporates a "Nag” function that monitors "time since last Nag” and that "nags” the user according to a "Nag Schedule” which is dynamically varied based on the monitored "time since last Nag” information.
  • the present invention encompasses a software product, e.g., e- mail software, that incorporates a download function that downloads separate file portions representing a single image during separate communication sessions with a remote server (e.g., separate file portions of an advertisement file, e.g., a GIF file).
  • a remote server e.g., separate file portions of an advertisement file, e.g., a GIF file.
  • the present invention further encompasses a system (and method) for automatically distributing advertisements to a multiplicity of client devices that have this software product installed thereon.

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Strategic Management (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Human Resources & Organizations (AREA)
  • Theoretical Computer Science (AREA)
  • Accounting & Taxation (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Finance (AREA)
  • Development Economics (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • Tourism & Hospitality (AREA)
  • Computer Hardware Design (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Mining & Analysis (AREA)
  • Quality & Reliability (AREA)
  • Operations Research (AREA)
  • Game Theory and Decision Science (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

Dans cette invention, un logiciel devant être utilisé dans un dispositif client configuré pour communiquer avec au moins une source éloignée via un réseau de communications, instancie une fonction d'installateur client qui installe le logiciel sur le dispositif client, et qui produit un identificateur de distributeur qui identifie le distributeur qui a mis a disposition le logiciel, et une fonction de téléchargement de messages publicitaires qui télécharge des messages publicitaires à partir de la source éloignée, via le réseau de communications.
PCT/US2000/029156 1999-12-08 2000-10-20 Procede et systeme de transmission de messages publicitaires aux dispositifs clients WO2001043375A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
AU12235/01A AU1223501A (en) 1999-12-08 2000-10-20 Method and system for distributing advertisements to client devices
JP2001531747A JP2003524230A (ja) 1999-12-08 2000-10-20 クライアント装置に広告を配布するためのｅメールソフトウェアおよびその方法とシステム

Applications Claiming Priority (8)

Application Number Priority Date Filing Date Title
US16962299P 1999-12-08 1999-12-08
US60/169,622 1999-12-08
US20939200P 2000-06-01 2000-06-01
US60/209,392 2000-06-01
US60912300A 2000-06-30 2000-06-30
US09/609,123 2000-06-30
US66833100A 2000-09-22 2000-09-22
US09/668,331 2000-09-22

Publications (1)

Publication Number Publication Date
WO2001043375A1 true WO2001043375A1 (fr) 2001-06-14

Family

ID=27496846

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2000/029156 WO2001043375A1 (fr) 1999-12-08 2000-10-20 Procede et systeme de transmission de messages publicitaires aux dispositifs clients

Country Status (3)

Country Link
JP (1) JP2003524230A (fr)
AU (1) AU1223501A (fr)
WO (1) WO2001043375A1 (fr)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8738418B2 (en) 2010-03-19 2014-05-27 Visa U.S.A. Inc. Systems and methods to enhance search data with transaction based data
US8639567B2 (en) 2010-03-19 2014-01-28 Visa U.S.A. Inc. Systems and methods to identify differences in spending patterns

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1997040514A1 (fr) * 1996-04-19 1997-10-30 Juno Online Services, L.P. Systeme de courrier electronique avec affichage de communiques
WO1999059097A1 (fr) * 1998-05-11 1999-11-18 Creative Edge Internet Services Pty. Ltd. Systeme publicitaire sur internet

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1997040514A1 (fr) * 1996-04-19 1997-10-30 Juno Online Services, L.P. Systeme de courrier electronique avec affichage de communiques
WO1999059097A1 (fr) * 1998-05-11 1999-11-18 Creative Edge Internet Services Pty. Ltd. Systeme publicitaire sur internet

Also Published As

Publication number Publication date
JP2003524230A (ja) 2003-08-12
AU1223501A (en) 2001-06-18

Similar Documents

Publication Publication Date Title
US8712848B2 (en) Method for distributing advertisements to client devices using an obscured ad monitoring function
US20070005429A1 (en) Method for controlling the distribution of advertisements to informational client devices using a plurality of operating modes
US20070038728A1 (en) A system for controlling the distribution of advertisements to informational client devices using a playlist
US20010034763A1 (en) System for distributing advertisements to client devices
US20010044736A1 (en) E-mail software and method and system for distributing advertisements to client devices that have such e-mail software installed thereon
US20020072967A1 (en) System for controlling the distribution of advertisements to informational client devices
US20020029166A1 (en) E-mail software and method and system for distributing advertisements to client devices that have such e-mail software installed thereon
US20040039642A1 (en) E-mail software and method and system for distributing advertisements to client devices that have such e-mail software installed thereon
WO2001043018A1 (fr) Procede de distribution de publicites aupres de dispositifs clients
WO2001042959A2 (fr) Logiciel de messagerie e-mail et procede et systeme de distribution d'annonces publicitaires a des dispositifs clients sur lesquels est installe ce logiciel de messagerie e-mail
US20040249708A1 (en) E-mail software and method and system for distributing advertisements to client devices that have such e-mail software installed thereon
US20030149738A1 (en) E-mail software and method and system for distributing advertisements to client devices that have such e-mail software installed thereon
US20010047408A1 (en) E-mail software and method and system for distributing advertisements to client devices that have such E-mail software installed thereon
US20030050832A1 (en) E-mail software and method and system for distributing advertisements to client devices that have such E-mail software installed thereon
WO2001042957A2 (fr) Logiciel de courrier electronique et procede et systeme de diffusion d'annonces publicitaires aupres de dispositifs clients deja equipe d'un tel logiciel de courrier electronique
WO2001043017A9 (fr) Procede et systeme de distribution d'annonces publicitaires a des dispositifs clients
WO2001043376A1 (fr) Procede et systeme de distribution de publicite a des dispositifs clients
WO2001043014A1 (fr) Procede et systeme servant a distribuer des messages publicitaires a des dispositifs client
WO2001043377A1 (fr) Procede et systeme destines a distribuer des publicites a des appareils client
WO2001043375A1 (fr) Procede et systeme de transmission de messages publicitaires aux dispositifs clients
WO2001042961A2 (fr) Logiciel de courrier electronique et procede et systeme de diffusion d'annonces publicitaires aupres de dispositifs clients possedant un tel logiciel de courrier electronique
WO2001043019A1 (fr) Procede et systeme de diffusion d'annonces publicitaires aupres de dispositifs clients
WO2001043015A9 (fr) Procede et dispositif destines a distribuer des publicites a des appareils clients
WO2001043013A9 (fr) Procede et systeme de distribution d'annonces publicitaires a des dispositifs clients
WO2001043374A9 (fr) Procede et systeme de distribution de publicites a des dispositifs clients

Legal Events

Date Code Title Description
ENP Entry into the national phase

Ref country code: JP

Ref document number: 2001 531747

Kind code of ref document: A

Format of ref document f/p: F

AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CR CU CZ DE DK DM DZ EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG US UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

122 Ep: pct application non-entry in european phase