FUTURE REMINDER AND E-MAIL REQUEST SYSTEM
RELATED APPLICATIONS
This application claims the benefit of U.S. Provisional Application No. 60/181,811 and U.S. Provisional Application No. 60/181,837, filed February 11, 2000.
FIELD OF THE INVENTION
This invention relates generally to online computer transactions, and more particularly, to computerized future reminder and e-mail request systems.
COPYRIGHT NOTICE/PERMISSION
A portion of the disclosure of this patent document may contain material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever. The following notice applies to the software and data as described below and in the drawings hereto: Copyright © 1999, Sony Electronics Inc., All Rights Reserved.
BACKGROUND OF THE INVENTION
Consumers are increasingly using the Internet for routine transactions over the Internet. As is well known in the art, consumer shopping and stock purchases are two of many types of transactions currently available. Many service providers are tracking purchases and online activity to provide consumers customized content and to improve customer satisfaction.
While tracking systems for consumer purchases are common for many e- commerce transactions, there are no systems for tracking other types of cyclical transactions.
SUMMARY OF THE INVENTION
An online future reminder and e-mail request system automatically creates messages based on key dates, such as holidays or prior user transactions, over the Internet. When a user conducts an online transaction, an online future reminder and e- mail request system stores the transaction information and assigns a key date based on the initial transaction date. On the assigned key date, the future reminder and e-mail
request system creates an e-mail message offering the user appropriate transaction options similar to that of the original transaction. Alternatively, the future reminder and e-mail request system message may be initiated by the arrival of designated key dates such as holidays, birthdays, or anniversary dates. In another aspect of the invention, the holidays may be selected based upon the nationality of the user. The message is automatically sent to the user requesting selection of one of the transaction options. The future reminder and e-mail request system receives a transaction option selection from the user. The future reminder and e-mail request system processes the transaction. A fee may be required for processing the selected transaction option. Alternatively, a single fee may be required for the use of the future reminder and e-mail request system. The future reminder and e-mail request system may also customize uploaded transactions.
A future reminder and e-mail request system provides consumers with a new service for reminding users of key dates and for automatically repeating cyclical transactions on the Internet.
The present invention describes systems, clients, servers, methods, and computer- readable media of varying scope. In addition to the aspects and advantages of the present invention described in this summary, further aspects and advantages of the invention will become apparent by reference to the drawings and by reading the detailed description that follows.
BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 A is a diagram illustrating an overview of the operation of an embodiment of a networked future reminder and e-mail request system according to the invention;
FIGs. IB and 1C are diagrams of a computer environment suitable for practicing the invention; and
FIGs. 2A - 2D are flow diagrams of methods to be performed by a server computer to administer a future reminder and e-mail request system according to an embodiment of the invention.
DETAILED DESCRIPTION OF THE INVENTION
In the following detailed description of embodiments of the invention, reference is made to the accompanying drawings in which like references indicate similar elements, and in which is shown by way of illustration specific embodiments in which
the invention may be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice the invention, and it is to be understood that other embodiments may be utilized and that logical, mechanical, electrical and other changes may be made without departing from the scope of the present invention. The following detailed description is, therefore, not to be taken in a limiting sense, and the scope of the present invention is defined only by the appended claims.
Beginning with an overview of the operation of the invention, FIG. 1A illustrates one embodiment of a networked future reminder and e-mail request system having a future reminder and e-mail request system server 101 that processes online transactions supplied from a client computer 103 by a user. The transactions may consist of sending electronic birthday cards, viewing photographs on a website, purchases on holidays, etc. The client computer 103 initiates a transaction 105 such as making a purchase on the server computer 101. In response, the server 101 stores the transaction information such as the item purchased and assigns a key date based on the date the transaction was initiated. Upon the arrival of the key date, the server creates a message 107 containing several transaction options illustrated as transaction option A109 and transaction option Bill. For example, for a transaction involving the purchase of an item, the message may offer an option to purchase the same item and an option to purchase other similar items. In response to receiving the message 107, the client designates a selection 113 from the transaction options, e.g. transaction C115. Transaction C115 corresponds to the transaction option A109. It will be appreciated that more than one transaction option may be selected by the user. Upon receiving the user selection 113, the server 101 processes the selection 113. The server 101 posts the selection on a web site and publishes the selection 119 on the web for public viewing on the client computer 121. Alternatively, the user selection may be published on the web site, but in such as manner as to limit the display to private viewing on a client computer 121. In yet another aspect, the server 101 may send an e-mail message to a client computer 119 containing the selection 113.
In one embodiment of a future reminder and e-mail request system, as shown in FIG. IB, the future reminder and e-mail request system server 101 hosts a future reminder and e-mail request system web site and is part of, or coupled to, an ISP
(Internet Service Provider) 135 to provide future reminders and e-mail requests over the Internet. The client computer 103 executes a conventional Internet browsing application to exchange data with the server 101. It is readily apparent that the present invention is not limited to Internet access and Internet web-based sites; directly coupled and private networks are also contemplated.
One embodiment of a computer system suitable for use as the future reminder and e-mail request system server 101 is illustrated in FIG. lC. The computer system 140, includes a processor 150, a memory 155 and input/output capability 160 coupled to a system bus 165. The memory 155 is configured to store instructions which, when executed by the processor 150, performs the methods described herein. The memory 155 may also store content for the future reminder and e-mail request system. Input/output 160 provides for the delivery and display of the messages and transaction options or portions or representations thereof. Input/output 160 also encompasses various types of computer-readable media, including any type of storage device that is accessible by the processor 150. One of skill in the art will immediately recognize that the term "computer-readable medium/media" further encompasses a carrier wave that encodes a data signal. It will also be appreciated that the server 101 is controlled by operating system software executing in memory 155. Input/output and related media 160 store the computer-executable instructions for the operating system and methods of the present invention as well as the information required for future messages.
The description of FIGs. IB and 1C are intended to provide an overview of computer hardware and other operating components suitable for implementing the' invention, but is not intended to limit the applicable environments. It will be appreciated that the computer system 140 is one example of many possible computer systems that have different architectures. A typical computer system will usually include at least a processor, memory, and a bus coupling the memory to the processor. One of skill in the art will immediately appreciate that the invention can be practiced with other computer system configurations, including microprocessor systems, minicomputers, mainframe computers, and the like. The invention can also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network.
Next, the particular methods of the invention are described in terms of computer software with reference to flow diagrams. FIGs. 2A - 2D illustrate examples of embodiments of an E-mail Request System method 200, a Future Reminder System method 220, and the supporting methods executed by a computer, such as the server 101 of FIG. 1 A. The methods constitute computer programs made up of computer- executable instructions illustrated as blocks (acts) 201 until 220 in FIG. 2A, blocks 221 until 235 in FIG. 2B, blocks 251 until 255 in FIG. 2C, and blocks 261 until 277 in FIG. 2D. It will be appreciated that not all of the blocks depicted in the flow diagrams are required to practice the invention. Furthermore, the functions represented by blocks may be performed in a different order without departing from the scope of the invention. Describing the computerized methods by reference to flow diagrams enables one skilled in the art to develop programs including instructions to carry out the methods on a suitable computer (the processor of the computer executing the instructions from computer-readable media). If written in a programming language conforming to a recognized standard, such instructions can be executed on a variety of hardware platforms and for interface to a variety of operating systems. In addition, the present invention is not described with reference to any particular programming language. It will be appreciated that a variety of programming languages may be used to implement the teachings of the invention as described herein. Furthermore, it is common in the art to speak of software, in one form or another (e.g. program, procedure, process, application, module, logic, etc.), as taking an action or causing a result. Such expressions are merely a shorthand way of saying that execution of the software by a computer causes the processor of the computer to perform an action or produce a result. An e-mail request system method 200 shown in FIG. 2A begins by identifying and storing key dates in memory at block 201. The dates are created by the server. In another embodiment, a user may enter key dates into the e-mail request system. In yet another embodiment, the server may select key dates based upon a user's nationality. Upon reaching a key date, a message is sent to a user at block 203 requesting a response by the user. The message may be sent utilizing known electronic mail systems. If the user responds to the message, the server receives the transaction at block 207. The user may respond to the message by sending a return e-mail message. In another
embodiment, the user may access a future reminder and e-mail request system web site and post the response on the web site in a user area. If the user fails to respond, the server sends another message in accordance with a pre-determined schedule until a response is received. In response to a received transaction, the server processes the transaction at block 209. In one embodiment, the transaction may also be used to initiate the future reminder system at block 220. Once the transaction is processed, the e-mail request system ends at block 211.
An embodiment of a future reminder system method 220 is illustrated in the FIG. 2B flow diagram. The server receives a user transaction at block 221. The server assigns at least one key date based on the date the user online transaction was received at block 223. The server stores the transaction information and the key date in memory at block 225. When the assigned key date is reached, the server creates a message at block 227. The server sends the message at block 229. The server determines if a response has been received at block 231. If a response has been received, the transaction is processed at block 233. If no response is received, the server sends additional messages in accordance with a pre-determined schedule at block 229. Once the transaction has been processed, the process repeats at block 235.
Turning now to FIG. 2C, one embodiment of a method 250 for creating a message is illustrated. A message may consist of a plurality of transaction options. The server identifies the type of transaction previously stored in memory at block 251. The server associates similar transaction options and duplicates the original transaction in the message at block 253. It will be appreciated that the message may contain further unrelated transaction options without departing form the scope of the invention. The server publishes the message at block 255. The message may be posted in an area on a web site suitable for public viewing. In another aspect of the invention, the message may be contained in an area accessible for private viewing only. In yet another aspect of the invention, the message may be sent to a client using electronic mail.
One embodiment of a method 260 for processing transactions is illustrated in flow diagram FIG. 2D. The server receives an identifier for the user selected transaction option at block 261. The server determines whether compensation is required at block 263. The server may request a payment from the user when a type of transaction is
selected or the user may subscribe to a plan that allows use of the future reminder and e- mail request system for a single fee. If compensation is required, the server receives compensation information at block 265. The server may validate the compensation received from the user at block 267 and may disallow access to the future reminder and e-mail request system by the user until the validated compensation is received. In another embodiment, the owner of the server requires compensation from an advertiser upon displaying an advertisement as part of the online future reminder and e-mail system. In yet another embodiment, the owner of the server requires compensation to incorporate an advertiser's product into the transaction options as part of an online future reminder and e-mail system. It will be appreciated that other compensation schemes can be implemented on the server without exceeding the scope of the invention.
Once compensation has been validated or if no compensation is required, the server receives the uploaded transaction at block 269. Uploaded transactions may contain digital images such as digital photograph files, greeting card content, etc. The server determines whether the transaction requires customization at block 271. If customization is required, the server customizes the transaction at block 273. Customizing may consist of creating customized messages, customized borders, creating photo albums, digitally processing photograph files to resize, digitally processing photograph files to improve image quality, and customizing greeting cards. In another embodiment, transaction processing may consist of cataloging uploaded digital images by date, time, keywords, etc. It will be appreciated that other processing schemes can be implemented on the server without exceeding the scope of the invention. When the transaction has been processed, the server completes the transaction at block 275. In another aspect of the invention, an electronic greeting card or electronic message may be sent by the server to a plurality of recipients. Once the server has completed the transaction, the process is terminated at block 277.
An online future reminder and e-mail request system has been described that uses transaction tracking for routine cyclical transactions. Samples of embodiments of future reminder and e-mail request system methods have been described including an online e- mail request system and an online future reminder system. Additionally, the future
-1-
reminder and e-mail request system includes examples of methods for creating messages and for processing transactions.
Although specific embodiments have been illustrated and described herein, it will be appreciated by those of ordinary skill in the art that any arrangement which is calculated to achieve the same purpose may be substituted for the specific embodiments shown. This application is intended to cover any adaptations or variations of the present invention.
The terminology used in this application with respect to network architecture is meant to include all client-server environments. Therefore, it is manifestly intended that this invention be limited only by the following claims and equivalents thereof.