A method is provided for preventing the delivery of unwanted electronic mail messages to a destination client. An original electronic mail message is first received from a source client at a destination server. Next, a reply electronic mail message is sent from the destination server to the source client requesting the source client to complete a registration process to register the source client's electronic mail address with the destination server. The original electronic mail message is only sent from the destination server to the destination client when the source client properly registers the source client's electronic mail address.
|
1. A method for preventing the delivery of unwanted electronic mail messages to a destination client, said method comprising the steps of:
receiving an original electronic mail message from a source client at a destination server, said original electronic mail message including an email address for said source client;
comparing said electronic mail address of said source client to at least one of an accept list or a reject list of electronic mail addresses;
holding said original electronic mail message in a first memory that is distinct from a second memory where deleted messages are stored if said electronic mail address of said source client is not on at least one of said accept list or said reject list;
sending a reply electronic mail message from said destination server to said source client requesting that said source client complete a registration process, if said electronic mail address of said source client is not on at least one of said accept list or said reject list,
wherein said registration process comprises completing a form at an internet address, and
wherein said form includes a query that is designed to be answered by a human rather than a machine;
monitoring the a response of said source client to said request to complete a registration process to determine whether said source client properly responds to said request; and
sending said original electronic mail message from said destination server to said destination client only if said source client properly responds to said request to complete a registration process.
0. 41. A method for preventing the delivery of unwanted electronic mail messages to a destination client, said method comprising the steps of:
receiving an original electronic mail message from a source client at a destination server, said original electronic mail message including an email address for said source client;
comparing said electronic mail address of said source client to at least one of an accept list or a reject list of electronic mail addresses;
holding said original electronic mail message in a first memory that is distinct from a second memory where deleted messages are stored if said electronic mail address of said source client is not on at least one of said accept list or said reject list;
allowing said destination client to access said first memory to determine content of said original electronic mail message;
sending a reply electronic mail message from said destination server to said source client requesting that said source client complete a registration process, if said electronic mail address of said source client is not on at least one of said accept list or said reject list;
said registration process includes a query that is designed to be answered by a human rather than a machine;
monitoring a response of said source client to said request to complete a registration process to determine whether said source client properly responds to said request; and
sending said original electronic mail message from said destination server to said destination client if said source client properly responds to said request to complete a registration process.
0. 32. A method for preventing the delivery of unwanted electronic mail messages to a destination client, said method comprising the steps of:
receiving an original electronic mail message from a source client at a destination server, said original electronic mail message including an email address from said source client;
comparing said electronic mail address of said source client to at least one of an accept list or a reject list of electronic mail addresses;
holding said original electronic mail message in a first memory that is distinct from a second memory where deleted messages are stored if said electronic mail address of said source client is not on at least one of said accept list or said reject list;
sending a reply electronic mail message from said destination server to said source client requesting that said source client complete a registration process, if said electronic mail address of said source client is not on at least one of said accept list or said reject list;
said registration process includes a query that is designed to be answered by a human rather than a machine;
monitoring a response of said source client to said request to complete a registration process to determine whether said source client properly responds to said request;
sending said original electronic mail message from said destination server to said destination client if said source client properly responds to said request to complete a registration process; and
deleting said original electronic mail message from said first memory when a predetermined period of time has lapsed without receiving a response to said request that said source client complete a registration process.
12. A method for preventing the delivery of unwanted electronic mail messages to a destination client comprising the steps of:
receiving an original electronic mail message addressed to a destination client from a source client having an electronic mail address at a destination server;
comparing said electronic mail address of said source client to an accept list of electronic mail addressees;
sending said original electronic mail message to said destination client when said electronic mail address of said source client is on said accept list;
comparing said electronic mail address of said source client to a reject list of electronic mail addresses when said electronic address of said source client is not on said accept list;
deleting said original message when said electronic mail address of said source client is on said reject list;
holding said original electronic mail message in a first memory that is distinct from a second memory where deleted messages are stored if said electronic mail address of said source client is not on said accept list or said reject list;
sending a reply electronic mail message from said destination server to said source client requesting that said source client complete a registration process when said electronic mail address of said source client is not on said accept list or said reject list;
said registration process includes a query that is designed to be answered by a human rather than a machine;
monitoring the response of said source client to said request to complete a registration process to determine whether said source client properly responds to said request; and
sending said original electronic mail message from said destination server to said destination client only if said source client properly responds to said request to complete a registration process; and
deleting said original electronic mail message from said first memory when a predetermined period of time has lapsed without receiving a response to said request that said source client completed a registration process.
2. The method for preventing the delivery of unwanted electronic mail messages according to
0. 3. The method for preventing the delivery of unwanted electronic mail messages according to
4. The method for preventing the delivery of unwanted electronic mail messages according to
0. 5. A method for preventing the delivery of unwanted electronic mail messages to a destination client comprising the steps of:
receiving an original electronic mail message addressed to a destination client from a source client having an electronic mail address at a destination server;
comparing said electronic mail address of said source client to an accept list of electronic mail addresses;
sending said original electronic mail message to said destination client when said electronic mail address of said source client is on said accept list;
sending a reply electronic mail message from said destination server to said source client requesting that said source client complete a registration process when said electronic mail address of said source client is not on said accept list;
monitoring the response of said source client to said request to complete a registration process to determine whether said source client properly responds to said request; and
sending said original electronic mail message from said destination server to said destination client only if said source client properly responds to said request to complete a registration process.
0. 6. The method for preventing the delivery of unwanted electronic mail messages according to
0. 7. The method for preventing the delivery of unwanted electronic mail messages according to
0. 8. The method for preventing the delivery of unwanted electronic mail messages according to
0. 9. The method for preventing the delivery of unwanted electronic mail messages according to
storing electronic mail addresses of clients to which said destination client has sent electronic mail messages; and
automatically updating said accept list to include said electronic mail addresses of clients to which said destination client has sent electronic mail messages.
0. 10. The method for preventing the delivery of unwanted electronic mail messages according to
holding said original electronic mail message in a memory if said source client does not properly respond to said request to complete a registration process;
allowing said destination client to access said memory to determine the content of said original electronic mail message.
0. 11. The method for preventing the delivery of unwanted electronic mail messages according to
automatically adding said electronic mail address of said source client to said accept list if said source client properly responds to said request to complete a registration process.
13. The method for preventing the delivery of unwanted electronic mail messages according to
14. The method for preventing the delivery of unwanted electronic mail messages according to
15. The method for preventing the delivery of unwanted electronic mail messages according to
16. The method for preventing the delivery of unwanted electronic mail messages according to
storing electronic mail addresses of clients to which said destination client has sent electronic mail messages; and
automatically updating said accept list to include said electronic mail addresses of clients to which said destination client has sent electronic mail messages.
17. The method for preventing the delivery of unwanted electronic mail messages according to
holding said original electronic mail message in a said first memory if said source client does not properly respond to said request to complete a registration process; and
allowing said destination client to access said first memory to determine the content of said original electronic mail message.
18. The method for preventing the delivery of unwanted electronic mail messages according to
automatically adding said electronic mail address of said source client to said accept list if said source client properly responds to said request to complete a registration process.
0. 19. The claim as recited in
0. 20. The claim as recited in
0. 21. The claim as recited in
0. 22. The claim as recited in
0. 23. The claim as recited in
0. 24. The claim as recited in
0. 25. The claim as recited in
0. 26. The claim as recited in
0. 27. The claim as recited in
0. 28. The claim as recited in
0. 29. The claim as recited in
0. 30. The claim as recited in
0. 31. The claim as recited in
0. 33. The claim as recited in
0. 34. The claim as recited in
0. 35. The claim as recited in
0. 36. The claim as recited in
0. 37. The claim as recited in
0. 38. The claim as recited in
0. 39. The claim as recited in
0. 40. The claim as recited in
0. 42. The claim as recited in
0. 43. The claim as recited in
0. 44. The claim as recited in
0. 45. The claim as recited in
0. 46. The claim as recited in
0. 47. The claim as recited in
0. 48. The claim as recited in
0. 49. The claim as recited in
0. 50. The claim as recited in
|
|||||||||||||||||||||||||
1. Field of the Invention
The present invention relates to methods used to reduce the amount of unwanted electronic mail (e-mail) received by a user of an e-mail service.
2. Related Art
The problem of unwanted, i.e. “junk,” e-mail is well known and has received considerable attention. However, some background is thought to be of help in understanding the problem and the solutions that have been previously used or proposed, as well as the basic e-mail process. Referring to
Attempts have been made to reduce the number of junk e-mail messages received by the destination clients. Some methods require the source client to add descriptive information to the e-mail message so that the destination SMTP server can prevent undesired e-mail messages from being sent to the destination client. These methods are basically ineffective because the senders of junk e-mail messages will not add the descriptive information which will allow destination clients to block the junk e-mail messages.
Filter-out methods have also been developed. With such filter-out methods, a database of known sources (source clients) of junk e-mail messages is compiled. The destination SMTP server compares the source client's e-mail address to the e-mail addresses in the database and does not sent undesired e-mail messages to the destination client. These methods have also proven to be ineffective because the development of robotic delivery programs. These robotic delivery programs sent out thousands of junk e-mail messages and create nonexistent source client e-mail addresses. Thus, when one source client e-mail address is blocked, a new address is created. As a consequence, the database of known sources of junk e-mail messages can not keep up with changing e-mail addresses created by the robotic delivery programs.
According to the invention, a method for preventing delivery of unwanted electronic mail is provided which overcomes the problems of prior art methods discussed above. The method of the invention thwarts conventional robotic delivery programs and, in preferred implementations, includes features which will counteract the anticipated use of more sophisticated robotic delivery systems.
In accordance with a first preferred embodiment of the invention, a method for preventing the delivery of unwanted electronic mail messages to a destination client is provided which comprises the steps of: receiving an original electronic mail message from a source client at a destination server; sending a reply electronic mail message from the destination server to the source client requesting that the source client complete a registration process; monitoring the response of the source client to the request to complete a registration process to determine whether the source client properly responds to the request; and sending the original electronic mail message from the destination server to the destination client only if the source client properly responds to the request to complete a registration process.
In another preferred embodiment, a method for preventing the delivery of unwanted electronic mail messages to a destination client is provided which comprises the steps of: receiving an original electronic mail message addressed to a destination client from a source client having an electronic mail address at a destination server; comparing the electronic mail address of the source client to an accept list of electronic mail addresses; sending the original electronic mail message to the destination client when the electronic mail address of the source client is on the accept list; sending a reply electronic mail message from the destination server to the source client requesting that the source client complete a registration process when the electronic mail address of the source client is not on the accept list; monitoring the response of the source client to the request to complete a registration process to determine whether the source client properly responds to the request; and sending the original electronic mail message from the destination server to the destination client only if the source client properly responds to the request to complete a registration process.
In accordance with yet another preferred embodiment of the invention, a method for preventing the delivery of unwanted electronic mail messages to a destination client is provided which comprises the steps of: receiving an original electronic mail message addressed to a destination client from a source client having an electronic mail address at a destination server; comparing the electronic mail address of the source client to an accept list of electronic mail addresses; sending the original electronic mail message to the destination client when the electronic mail address of the source client is on the accept list; comparing the electronic mail address of the source client to a reject list of electronic mail addresses when the electronic address of the source client is not on the accept list; deleting the original message when the electronic mail address of the source client is on the reject list; sending a reply electronic mail message from the destination server to the source client requesting that the source client complete a registration process when the electronic mail address of the source client is not on the reject list; monitoring the response of the source client to the request to complete a registration process to determine whether the source client properly responses to the request; and sending the original electronic mail message from the destination server to the destination client only if the source client properly responds to the request to complete a registration process.
Preferred implementations for the registration process include: answering a question included in the reply electronic mail message; completing a form at an Internet address; and following instructions via a telephone system.
Other features and advantages of the invention will be set forth in, or apparent from, the following detailed description of the preferred embodiments of the invention.
Referring to
If the source client is not on the reject list, the destination SMTP server holds the e-mail message in memory and requests that the source client proceed with a registration process, as indicated in step 120. There are many different ways in which the source client can register its e-mail address. In one advantageous implementation, the destination SMTP server sends a reply message to the source client and requests that the source client send back a reply message. When the destination SMTP server receives the reply message, the original e-mail message is “filtered-in” and released to the destination client. However, if the original message is junk e-mail produced by a robotic delivery program, the destination SMTP server will never receive a response to its reply message because the source client e-mail address does not exist.
As robotic delivery programs become more sophisticated, it will become necessary to make the registration process more complex. For example, the destination SMTP server can send a reply message to the source client with instructions or a question that only a human can follow or answer, respectively. The registration process is successfully completed when the source client responds correctly. In a preferred implementation, each destination client is allowed to compose their own question and answer or instructions, in order to maximize the amount of effort required by a source of junk e-mail to send messages to multiple destination clients. In general, it will be cost prohibitive for the source of junk e-mail messages to go through and response to each destination SMTP server reply message. In other embodiments, the registration process is completed by filling out an Internet web page form or by following instructions via a telephone system. Although these embodiments have particular benefit, those skilled in the art will appreciate that there are many different ways in which the registration process can be performed. One advantage of including such a registration process is that it requires the source client to make an effort to filter-in a desired message, instead of requiring the destination client to filter-out undesired messages.
In step 130, the destination SMTP server determines whether the source client properly registered its e-mail address within a predetermined time period. The length of the predetermined time period may be selected either by the destination client or the destination SMTP server. If the e-mail address is properly registered, the original e-mail message is sent to the destination client and the source client's e-mail address is added to the accept list, as indicated in step 150. At any time, the destination client can add e-mail addresses and remove e-mail addresses from the accept and reject lists. Therefore, if the source client does properly register its e-mail address and the destination client wishes to not receive any more e-mail messages from that source client, the destination client can remove that entry from the accept list and add it to the reject list.
In the illustrated embodiment, if the registration process is not successfully completed within the predetermined period of time, the destination SMTP server holds the original e-mail message in a memory, as indicated in step 140. The destination client may access the e-mail messages stored in the memory. The destination SMTP server may delete the e-mail messages from the memory when a preselected event occurs, i.e., when instructed to do so by the destination client, or when a predetermined time period has lapsed, or when the memory is full or when a predetermined number of e-mail messages has been exceeded. Either the destination SMTP server, or the destination client can determine the manner in which the e-mail messages will be deleted from the memory.
In another embodiment (not shown), the destination SMTP server automatically deletes the original e-mail message if the registration process is not completed within the predetermined period of time.
One of ordinary skill in the art will appreciate that the software necessary to carry out the present invention may operate either from the destination server or the destination client.
Although the invention has been described in detail with respect to preferred embodiments thereof, it will be apparent to those skilled in the art that variations and modifications can be effected in these embodiments without departing from the spirit and scope of the invention.
| Patent | Priority | Assignee | Title |
| Patent | Priority | Assignee | Title |
| 4977520, | Feb 03 1988 | Genesys Telecommunications Laboratories, Inc | Method to facilitate a reply to electronic meeting invitation in an interactive multi-terminal system employing electronic calendars |
| 5040141, | Nov 25 1986 | Hitachi, Ltd. | Method for administrating reply mail in electronic mail system |
| 5093918, | Dec 22 1988 | INTERNATIONAL BUSINESS MACHINES CORPORATION, ARMONK, NY 10504, A CORP OF NY | System using independent attribute lists to show status of shared mail object among respective users |
| 5159673, | Mar 22 1990 | SCHNEIDER AUTOMATION INC | Apparatus for networking programmable logic controllers to host computers |
| 5204961, | Jun 25 1990 | HEWLETT-PACKARD DEVELOPMENT COMPANY, L P | Computer network operating with multilevel hierarchical security with selectable common trust realms and corresponding security protocols |
| 5245532, | Jun 16 1988 | International Business Machines Corporation | Electronic mail follow-up system |
| 5283856, | Oct 04 1991 | Banyan Systems Incorporated | Event-driven rule-based messaging system |
| 5319776, | Apr 19 1990 | Symantec Corporation | In transit detection of computer virus with safeguard |
| 5333266, | Mar 27 1992 | International Business Machines Corporation | Method and apparatus for message handling in computer systems |
| 5377354, | Aug 15 1989 | HTC Corporation | Method and system for sorting and prioritizing electronic mail messages |
| 5423042, | Oct 23 1992 | International Business Machines Corporation | Remote procedure execution |
| 5448734, | Sep 30 1991 | International Business Machines Corporation | Selective distribution of messages using named pipes |
| 5471519, | Feb 26 1993 | BELLSOUTH INTELLECTUAL PROPERTY GROUP, INC ; Bellsouth Intellectual Property Corporation | Communications monitoring and control system |
| 5473671, | Mar 11 1994 | AT&T IPM Corp | Selective screening of incoming calls for cellular telephone systems |
| 5539828, | May 31 1994 | Intel Corporation | Apparatus and method for providing secured communications |
| 5548789, | Jan 24 1991 | Canon Kabushiki Kaisha | Message communication processing apparatus for selectively converting storing and transmitting messages of different lengths |
| 5600799, | Apr 27 1990 | National Semiconductor Corporation | Status batching and filtering in a media access control/host system interface unit |
| 5604803, | Jun 03 1994 | Sun Microsystems, Inc. | Method and apparatus for secure remote authentication in a public network |
| 5608786, | Dec 23 1994 | PayPal, Inc | Unified messaging system and method |
| 5619648, | Nov 30 1994 | Alcatel Lucent | Message filtering techniques |
| 5627764, | Jan 29 1993 | Unisys Corporation | Automatic electronic messaging system with feedback and work flow administration |
| 5630123, | Sep 28 1994 | JDA SOFTWARE GROUP, INC | Software system utilizing a filtered priority queue and method of operation |
| 5632018, | Jan 18 1993 | Fujitsu Limited | Electronic mail system |
| 5655079, | Jul 31 1989 | Hitachi, Ltd. | Data processing system and data transmission and processing method |
| 5721779, | Aug 28 1995 | Juniper Networks, Inc | Apparatus and methods for verifying the identity of a party |
| 5734903, | May 13 1994 | Apple Computer, Inc.; Apple Computer, Inc | System and method for object oriented message filtering |
| 5742668, | Sep 14 1994 | ACCESS CO , LTD | Electronic massaging network |
| 5742769, | May 06 1996 | SWITCHBOARD LLC | Directory with options for access to and display of email addresses |
| 5781857, | Jun 28 1996 | Google Technology Holdings LLC | Method of establishing an email monitor responsive to a wireless communications system user |
| 5796840, | May 31 1994 | Intel Corporation | Apparatus and method for providing secured communications |
| 5826022, | Apr 05 1996 | Oracle America, Inc | Method and apparatus for receiving electronic mail |
| 5832227, | Dec 14 1992 | The Commonwealth of Australia of Anzak Park | Method for providing message document security by deleting predetermined header portions and attaching predetermined header portions when seal is validly associated with message or document |
| 5835722, | Jun 27 1996 | TW SECURITY CORP ; TRUSTWAVE HOLDINGS, INC | System to control content and prohibit certain interactive attempts by a person using a personal computer |
| 5859967, | Jul 09 1996 | WELLS FARGO FOOTHILL, INC | Method and system for relaying communications from authorized users |
| 5884033, | May 15 1996 | OPENTV, INC | Internet filtering system for filtering data transferred over the internet utilizing immediate and deferred filtering actions |
| 5893911, | Apr 17 1996 | SYBASE, INC | Method for defining and applying rules for message distribution for transaction processing in a distributed application |
| 5909589, | Nov 12 1996 | Lance T., Parker | Internet based training |
| 5917489, | Jan 31 1997 | Microsoft Technology Licensing, LLC | System and method for creating, editing, and distributing rules for processing electronic messages |
| 5930479, | Oct 21 1996 | CALLAHAN CELLULAR L L C | Communications addressing system |
| 5937162, | Apr 06 1995 | GOOGLE LLC | Method and apparatus for high volume e-mail delivery |
| 5999600, | Oct 14 1996 | Samsung Electronics Co., Ltd.; SAMSUNG ELECTRONICS CO , LTD , A CORPORATION ORGANIZED UNDER THE LAWS OF THE REPUBLIC OF KOREA | Facsimile mail system and method for controlling the same |
| 5999932, | Jan 13 1998 | Symantec Corporation | System and method for filtering unsolicited electronic mail messages using data matching and heuristic processing |
| 5999967, | Aug 17 1997 | BARRACUDA NETWORKS, INC | Electronic mail filtering by electronic stamp |
| 6014634, | Dec 26 1995 | Catalina Marketing Corporation | System and method for providing shopping aids and incentives to customers through a computer network |
| 6023723, | Dec 22 1997 | Comcast IP Holdings I, LLC | Method and system for filtering unwanted junk e-mail utilizing a plurality of filtering mechanisms |
| 6052709, | Dec 23 1997 | Symantec Corporation | Apparatus and method for controlling delivery of unsolicited electronic mail |
| 6055510, | Oct 24 1997 | AT&T Corp | Method for performing targeted marketing over a large computer network |
| 6057841, | Jan 31 1997 | Microsoft Technology Licensing, LLC | System and method for processing electronic messages with rules representing a combination of conditions, actions or exceptions |
| 6092101, | Jun 16 1997 | GOOGLE LLC | Method for filtering mail messages for a plurality of client computers connected to a mail service system |
| 6154765, | Mar 18 1998 | JACOB, CHARLES | Distributed digital rule processor for single system image on a clustered network and method |
| 6173322, | Jun 05 1997 | Hewlett Packard Enterprise Development LP | Network request distribution based on static rules and dynamic performance data |
| 6182118, | May 08 1995 | Cranberry Properties, LLC | System and method for distributing electronic messages in accordance with rules |
| 6189026, | Jun 16 1997 | GOOGLE LLC | Technique for dynamically generating an address book in a distributed electronic mail system |
| 6195698, | Apr 13 1998 | GOOGLE LLC | Method for selectively restricting access to computer systems |
| 6199102, | Aug 26 1997 | GOOGLE LLC | Method and system for filtering electronic messages |
| 6199106, | Apr 19 1996 | D E SHAW & CO , L P | Electronic mail system with advertising |
| 6205432, | Jun 05 1998 | Creative Internet Concepts, LLC | Background advertising system |
| 6237027, | Jun 20 1996 | Sony Corporation | Electronic mail system, computer device, and remote notification method |
| 6373950, | Jun 17 1996 | Hewlett Packard Enterprise Development LP | System, method and article of manufacture for transmitting messages within messages utilizing an extensible, flexible architecture |
| 6393465, | Nov 25 1997 | Nixmail Corporation | Junk electronic mail detector and eliminator |
| 6421709, | Dec 22 1997 | Comcast IP Holdings I, LLC | E-mail filter and method thereof |
| 6484197, | Nov 07 1998 | TREND MICRO INCORPORATED | Filtering incoming e-mail |
| 6546416, | Dec 09 1998 | GOOGLE LLC | Method and system for selectively blocking delivery of bulk electronic mail |
| 6625257, | Jul 31 1997 | Toyota Jidosha Kabushiki Kaisha | Message processing system, method for processing messages and computer readable medium |
| 6678704, | Jun 23 1998 | Oracle International Corporation | Method and system for controlling recovery downtime by maintaining a checkpoint value |
| 6883095, | Dec 19 2000 | VMWARE, INC | System and method for password throttling |
| 7194515, | Dec 09 1998 | GOOGLE LLC | Method and system for selectively blocking delivery of bulk electronic mail |
| 7383433, | Jul 31 2001 | Oracle America, Inc | Trust spectrum for certificate distribution in distributed peer-to-peer networks |
| 20020199095, | |||
| 20050081059, | |||
| DE19708856, | |||
| EP463252, | |||
| EP651533, | |||
| EP686327, | |||
| EP721268, | |||
| EP725523, | |||
| EP760565, | |||
| EP883271, | |||
| WO116695, | |||
| WO2077768, | |||
| WO3044617, | |||
| WO9406236, | |||
| WO9609714, | |||
| WO9624213, | |||
| WO9714234, | |||
| WO9720423, | |||
| WO9723082, | |||
| WO9724825, | |||
| WO9726709, | |||
| WO9837675, | |||
| WO9910817, |
| Executed on | Assignor | Assignee | Conveyance | Frame | Reel | Doc |
| Sep 30 2002 | VIRTUAL GATE TECHNOLOGIES, LLC | MAILBLOCKS, INC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 023834 | /0456 | |
| Oct 02 2002 | HEINER, JEFFREY NELSON | MAILBLOCKS, INC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 023834 | /0510 | |
| Nov 01 2004 | MAILBLOCKS, INC | MBLX LLC | MERGER SEE DOCUMENT FOR DETAILS | 023834 | /0567 | |
| Mar 31 2005 | MBLX LLC | AMERICA ONLINE, INC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 023834 | /0612 | |
| Apr 03 2006 | AMERICA ONLINE, INC | AOL LLC | CHANGE OF NAME SEE DOCUMENT FOR DETAILS | 023834 | /0648 | |
| Jun 07 2006 | AOL LLC | (assignment on the face of the patent) | / | |||
| Dec 04 2009 | AOL LLC | AOL Inc | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 023720 | /0509 | |
| Dec 09 2009 | YEDDA, INC | BANK OF AMERICAN, N A AS COLLATERAL AGENT | SECURITY AGREEMENT | 023649 | /0061 | |
| Dec 09 2009 | TRUVEO, INC | BANK OF AMERICAN, N A AS COLLATERAL AGENT | SECURITY AGREEMENT | 023649 | /0061 | |
| Dec 09 2009 | Tacoda LLC | BANK OF AMERICAN, N A AS COLLATERAL AGENT | SECURITY AGREEMENT | 023649 | /0061 | |
| Dec 09 2009 | SPHERE SOURCE, INC | BANK OF AMERICAN, N A AS COLLATERAL AGENT | SECURITY AGREEMENT | 023649 | /0061 | |
| Dec 09 2009 | Quigo Technologies LLC | BANK OF AMERICAN, N A AS COLLATERAL AGENT | SECURITY AGREEMENT | 023649 | /0061 | |
| Dec 09 2009 | AOL Inc | BANK OF AMERICAN, N A AS COLLATERAL AGENT | SECURITY AGREEMENT | 023649 | /0061 | |
| Dec 09 2009 | AOL ADVERTISING INC | BANK OF AMERICAN, N A AS COLLATERAL AGENT | SECURITY AGREEMENT | 023649 | /0061 | |
| Dec 09 2009 | BEBO, INC | BANK OF AMERICAN, N A AS COLLATERAL AGENT | SECURITY AGREEMENT | 023649 | /0061 | |
| Dec 09 2009 | ICQ LLC | BANK OF AMERICAN, N A AS COLLATERAL AGENT | SECURITY AGREEMENT | 023649 | /0061 | |
| Dec 09 2009 | GOING, INC | BANK OF AMERICAN, N A AS COLLATERAL AGENT | SECURITY AGREEMENT | 023649 | /0061 | |
| Dec 09 2009 | Lightningcast LLC | BANK OF AMERICAN, N A AS COLLATERAL AGENT | SECURITY AGREEMENT | 023649 | /0061 | |
| Dec 09 2009 | MAPQUEST, INC | BANK OF AMERICAN, N A AS COLLATERAL AGENT | SECURITY AGREEMENT | 023649 | /0061 | |
| Dec 09 2009 | Netscape Communications Corporation | BANK OF AMERICAN, N A AS COLLATERAL AGENT | SECURITY AGREEMENT | 023649 | /0061 | |
| Sep 30 2010 | BANK OF AMERICA, N A | YEDDA, INC | TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENT RIGHTS | 025323 | /0416 | |
| Sep 30 2010 | BANK OF AMERICA, N A | TRUVEO, INC | TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENT RIGHTS | 025323 | /0416 | |
| Sep 30 2010 | BANK OF AMERICA, N A | Tacoda LLC | TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENT RIGHTS | 025323 | /0416 | |
| Sep 30 2010 | BANK OF AMERICA, N A | SPHERE SOURCE, INC | TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENT RIGHTS | 025323 | /0416 | |
| Sep 30 2010 | BANK OF AMERICA, N A | AOL Inc | TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENT RIGHTS | 025323 | /0416 | |
| Sep 30 2010 | BANK OF AMERICA, N A | AOL ADVERTISING INC | TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENT RIGHTS | 025323 | /0416 | |
| Sep 30 2010 | BANK OF AMERICA, N A | GOING INC | TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENT RIGHTS | 025323 | /0416 | |
| Sep 30 2010 | BANK OF AMERICA, N A | Lightningcast LLC | TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENT RIGHTS | 025323 | /0416 | |
| Sep 30 2010 | BANK OF AMERICA, N A | MAPQUEST, INC | TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENT RIGHTS | 025323 | /0416 | |
| Sep 30 2010 | BANK OF AMERICA, N A | Netscape Communications Corporation | TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENT RIGHTS | 025323 | /0416 | |
| Sep 30 2010 | BANK OF AMERICA, N A | Quigo Technologies LLC | TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENT RIGHTS | 025323 | /0416 | |
| Jun 14 2012 | AOL Inc | Facebook, Inc | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 028487 | /0466 | |
| Oct 28 2021 | Facebook, Inc | Meta Platforms, Inc | CHANGE OF NAME SEE DOCUMENT FOR DETAILS | 058961 | /0436 |
| Date | Maintenance Fee Events |
| Apr 18 2011 | ASPN: Payor Number Assigned. |
| Feb 01 2012 | M1553: Payment of Maintenance Fee, 12th Year, Large Entity. |
| Date | Maintenance Schedule |
| Jun 23 2012 | 4 years fee payment window open |
| Dec 23 2012 | 6 months grace period start (w surcharge) |
| Jun 23 2013 | patent expiry (for year 4) |
| Jun 23 2015 | 2 years to revive unintentionally abandoned end. (for year 4) |
| Jun 23 2016 | 8 years fee payment window open |
| Dec 23 2016 | 6 months grace period start (w surcharge) |
| Jun 23 2017 | patent expiry (for year 8) |
| Jun 23 2019 | 2 years to revive unintentionally abandoned end. (for year 8) |
| Jun 23 2020 | 12 years fee payment window open |
| Dec 23 2020 | 6 months grace period start (w surcharge) |
| Jun 23 2021 | patent expiry (for year 12) |
| Jun 23 2023 | 2 years to revive unintentionally abandoned end. (for year 12) |