A server-side recycle bin system for retaining computer files and information is disclosed. The system comprises a local computer system, and a server including a server-side recycle bin. One or more persistent storage devices, providing the files and directories to be protected, are present either as part of the local computer system or as part of the server. The local computer system and the server may be connected via a wide area computer network, a local area network, the Internet, of any other method or combination of methods. A file manager application running on the local computer system interacts with a file serving application on the server such that there is generated a retained file in the server-side recycle bin.
|
0. 21. A server for use with a local computer system used by a user, with a file manager application running on the local computer system which provides an indication that a file has been indicated for deletion, the server comprising:
a persistent storage device including a server-side user recycle bin and files; and
a file serving application which responds to the indication from the file manager application by generating a retained file residing in the server-side user recycle bin, which retained file is a copy of the file indicated for deletion.
0. 31. A server for use with a local computer system used by a user, the local computer system including a persistent storage device for storing files and a file manager application which provides an indication that a file in the local computer system persistent storage device has been indicated for deletion and provides a copy of the indicated file, the server comprising:
a persistent storage device including a server-side recycle bin and files; and
a file serving application which responds to the indication from the file manager application by generating a retained file residing in the server-side recycle bin by receiving the copy of the indicated file and storing the received file in the server-side recycle bin.
0. 1. A server-side recycle bin system for retaining computer files and information, comprising:
a) a local computer system; and
b) a server connected to the local computer system, the server comprising a persistent storage device;
the server further comprising a server-side recycle bin located within the persistent storage device; and
wherein a file manager application running on the local computer system and a file serving application running on the server interact to generate a retained file residing in the server-side recycle bin.
0. 2. The server-side recycle bin system of
0. 3. The server-side recycle bin system of
0. 4. The server-side recycle bin system of
0. 5. The server-side recycle bin system of
0. 6. The server-side recycle bin system of
0. 7. The server-side recycle bin system of
0. 8. The server-side recycle bin system of
0. 9. The server-side recycle bin system of
0. 10. The server-side recycle bin system of
0. 11. A server-side recycle bin system for retaining computer files and information, comprising:
a) a local computer system comprising a persistent storage device; and
b) a server connected to the local computer system, the server comprising a server-side recycle bin;
wherein a file manager application running on the local computer system and a file serving application running on the server interact to generate a retained file residing in the server-side recycle bin.
0. 12. The server-side recycle bin system of
0. 13. The server-side recycle bin system of
0. 14. The server-side recycle bin system of
0. 15. The server-side recycle bin system of
0. 16. The server-side recycle bin system of
0. 17. A server-side recycle bin system for retaining computer files and information, comprising:
a) a local computer system;
b) a server computer comprising at least one server-side recycle bin;
c) means for retaining deleted files and information; and
d) a connection means for allowing communication between the local computer system and the server computer system.
0. 18. The server-side recycle bin system of
0. 19. The server-side recycle bin system of
0. 20. The server-side recycle bin system of
0. 22. The server of claim 21, wherein the file manager application provides an indication to restore the retained file and wherein the file serving application responds to the indication from the file manager application to restore the retained file to a location on the persistent storage device of the server but outside the server-side user recycle bin.
0. 23. The server of claim 21, wherein the file serving application generates a user recycle bin index viewable from the local computer system.
0. 24. The server of claim 21, wherein the file manager application provides an indication to delete an item stored in the user recycle bin and wherein the file serving application deletes the item stored in the user recycle bin in response to the indication.
0. 25. The server of claim 21, the server further comprising:
an interface for connection to the Internet for allowing the file serving application to interact with the file manager application.
0. 26. The server of claim 25, wherein the local computer comprises a personal computer.
0. 27. The server of claim 25, where the local computer comprises a handheld computer.
0. 28. The server of claim 25, wherein the local computer comprises an Internet enabled device.
0. 29. The server of claim 21, the server further comprising:
an interface for connection to a local area network for allowing the file serving application to interact with the file manager application.
0. 30. The server of claim 21, the server further comprising:
an interface for connection to a wide area network for allowing the file serving application to interact with the file manager application.
0. 32. The server of claim 31, wherein the file manager application provides an indication to restore the retained file to a location on the local computer system and wherein the file serving application responds to the indication from the file manager application by providing the retained file to the file manager application.
0. 33. The server of claim 31, wherein the file serving application generates a recycle bin index viewable from the local computer system.
0. 34. The server of claim 31, wherein the file manager application provides an indication to delete an item stored in the recycle bin and wherein the file serving application deletes the item stored in the recycle bin in response to the indication.
0. 35. The server of claim 31, the server further comprising:
an interface for connection to the Internet for allowing the file serving application to interact with the file manager application.
0. 36. The server of claim 35, wherein the local computer system comprises a personal computer.
0. 37. The server of claim 35, wherein the local computer system comprises a handheld computer.
0. 38. The server of claim 35, wherein the local computer system comprises an Internet enabled device.
0. 39. The server of claim 31, the server further comprising:
an interface for connection to a local area network for allowing the file serving application to interact with the file manager application.
0. 40. The server of claim 31, the server further comprising:
an interface for connection to a wide area network for allowing the file serving application to interact with the file manager application.
|
|||||||||||||||||||||||||||||||
Notice: More than one reissue application has been filed for the reissue of U.S. Pat. No. 6,611,836. The reissue applications are application Ser. Nos. 12/469,879 (the present application) and 11/212,139, all of which are divisional reissues of U.S. Pat. No. 6,611,836.
In recent years, the computer files generated by many software applications have become larger and larger. This is especially the case for the computer files generated by applications that involve the storage and manipulation of photographs, motion pictures, and/or sound recordings. At the same time, whether because of the Internet, more complex operating systems, or otherwise, computers now tend to generate and store a much greater number of individual computer files. To save valuable storage space, and perhaps to reduce the appearance of unnecessary clutter, a user will often desire to delete computer files and/or directories from the user's hard disk drive or other assessable persistent storage devices. Unfortunately, oftentimes a user will delete these files or directories, only to find out later that the deleted data was desired or necessary. For example, a deleted file or directory may contain information that the user actually desired to retain, or the deleted file or directory, unbeknownst to the user, may have been necessary to the proper operation of one or more of the software applications used by the user.
One partial solution to this problem has been the use of a local “recycle bin” system. A “recycle bin” is an object that serves as a means of temporarily storing and protecting data that has been marked for deletion, but has not yet been removed from the computer system. Recycle bins typically reside on the hard disk drive of a user's local computer. In the case of the various Microsoft Windows® operating systems, a local recycle bin temporarily stores and protects data residing on the local computer's hard disk drive only. The Windows® operating systems do not protect the data residing on any of the other persistent storage devices that may be a part of the user's local computer system, such as the computer's floppy diskettes, tape drives, rewriteable compact disks (CDRW's) or other removable media, or non-volatile random access memory. Likewise, these operating systems do not protect a user's data when the local computer user wishes to delete files and directories located on a server, as when the local computer is networked to a server.
Under this conventional approach, the local recycle bin is represented as an object on the user's desktop. When the user drags a file or directory to the recycle bin, or “deletes” a file or directory via graphical user interface commands, the file or directory is “moved” to the recycle bin. The file or directory has not yet been deleted. It still takes up valuable space on the user's local computer hard disk drive. The user may view the contents of the local recycle bin. The user has the ability to restore a file or directory in the recycle bin, thus returning the “deleted” file or directory to its former location.
Only when the user decides to “empty” the local recycle bin are the contents of the recycle bin are deleted. That is, when the local recycle bin is emptied, the operating system reclaims the physical space formerly occupied by the contents of the recycle bin. At this point, a deleted file or directory may be recovered, if at all, only by the use of difficult-to-use third party disk utility applications, such as Norton Utilities®, and the like.
Thus, the computer user may have two options. The user may empty the recycle bin to reclaim the physical disk space occupied by the contents of the recycle bin, and thereby risk not ever being able to recover the recycle bin's contents. Alternatively, the user may preserve the data contained in the recycle bin by allowing the unemptied recycle bin to fill up. Under this alternative, the remaining space available on the user's hard disk drive continues to be depleted. Neither option may be satisfactory. Thus, there exists a need for a recycle bin system where the recycle bin does not physically reside or take up significant space on the user's local computer.
The recycle bin system of the present invention makes use of a recycle bin that resides on a server. The system includes at least one local computer system and at least one server. The local computer system and the server may be connected in a variety of ways, including via a local area network (LAN), a wide area network, the Internet, various wireless methods, or other methods or combinations of methods. There is also included at least one persistent storage device storing the files and directories to be protected. This persistent storage device may reside either within the local computer system or on the server. When a user deletes a file and/or directory, either from a persistent storage device located within the user's local computer system, or from persistent storage device located on the server, a file manager application running on the user's local computer system interacts with a file serving application running on the server, resulting in the generation of a retained file and/or directory in the server-side recycle bin.
The server-side recycle bin system of the present invention comprises (1) a local computer system; (2) a server computer having a server-side recycle bin; (3) a persistent storage device, residing either within the local computer system or on the server, that provides files and directories to be protected; and (4) a file manager application running on the local computer that interacts with a file serving application running on the server such that there is generated a retained file and/or directory in the server-side recycle bin.
The local computer system and the server in the present invention may be connected via a local area network (LAN), a wide area network, the Internet, various wireless methods, or other methods. The connection between the local computer system and the server may make use of combinations of the above previously-mentioned methods, and the connection may take place over physical, wired connections or fiber-optic cables, or via various known wireless connection methods, or the like.
The local computer system of the present invention may include a Microsoft Windows®-based personal computer or other type of personal computer. Other suitable local computer systems include other types of computing devices, such as handheld computers, handheld mobile communication computers, and disk-driveless computers that rely upon a server for their storage or other functions. Still other suitable local computer systems include any of the various “web appliance” computers specifically designed to facilitate a user's access to the range of content available or soon to be available on the Internet.
The present invention includes at least one persistent storage device that stores the files and directories to be protected. The persistent storage device may physically reside within the local computer system, as in the case of a hard disk drive within or attached to a personal computer. Alternatively, the persistent storage device may reside within the server so long as it may be accessed from the local computer. It will be understood by those of ordinary skill in the art that a server may include a plurality of persistent storage devices and logical connections thereto. Suitable persistent storage devices include hard disk drives, floppy diskette drives, tape drives, rewriteable compact disks (CDRWs) or other removable media, non-volatile random access memory, or the like.
The present invention includes a file manager application running on the local computer. This local file manager application is a software program responsible for communicating various requests to the server. It will be understood that while the local file manager runs on the local computer, the application itself may be physically stored at any location accessible to the local computer, for example, on a hard disk drive within the local computer system or on the server.
The present invention also includes a file serving application running on the server computer. This server-side file serving application is a software program responsible for receiving various requests from the local computer, for generating a retained file and/or directory in the server-side recycle bin, and for the various other tasks associated with the server-side recycle bin. The file manager application and the file serving application may be coded using any suitable commonly-available programming languages, for example, Visual Basic, C, Delphi, or the like.
According to the present invention, when a user on a local computer wishes to delete one or more files or directories accessible to the user, the user inputs such a command through any of various methods. The user may issue this command, for example, by dragging the file or directory to be deleted to a special recycle bin icon displayed on the desktop of the local computer; by “right clicking” on the icon representing the file or directory to be deleted, followed by a selection of a “delete” option; or by other methods. Upon doing so, the local file manager application and server-side file serving application interact so as to effectively generate the file and/or directory within the server-side recycle bin.
The “deleted” file and/or directory thereafter no longer appears to the user to be within the file directory from which the user intended to delete it. In the case of a file or directory to be deleted from a persistent storage device physically residing within the local computer system, the user may have the option of disabling any local recycle bin system that may be present, as for example, in a Windows®-based operating system. If the local recycle bin system is disabled, then upon the deletion of the targeted file or directory, the physical space formerly occupied by the deleted file or directory becomes freed up for other use by the local computer.
As part of the interaction between the local file manager application and the server-side file serving application, there is generated a retained file having a unique name that may be different from the name of the deleted file or directory. Certain relevant information about the file or directory, such as its original name, size, location, file creation access and edit times and dates, etc., may also be retained.
In one aspect of the present invention, the local file manager application and server-side file serving application interact, upon an appropriate command from a user or other authority, to allow for the viewing of the contents of the server-side recycle bin. Other relevant information, such file or directory name, size, former location, deletion date, etc. of the recycle bin contents, may also be displayed.
In another aspect of the present invention, the local file manager application and server-side file serving application interact, upon an appropriate command from a user or other authority, to “restore” the deleted file or directory. The restored file or directory is thus placed back into its former location, or to another designated location. The relevant data in the server-side recycle bin may or may not be thereafter retained.
In still another aspect of the present invention, upon an appropriate command from the user or other authority, the local file manager application and server-side file serving application interact to “empty,” or delete the contents in, the server-side recycle bin.
It will be appreciated that a directory is conceptually different from a file, in that a directory is basically a placeholder that contains information and data about the structure and relationships between files. Thus, when a user according to the present invention recycles a directory, the information and data that constitute that directory is retained in one or more files within the server-side recycle bin.
It will also be appreciated that the size of recycle bin may be limited in several ways. For example, the user or a system administrator may specify a finite size (or maximum number of bytes) for the user's server-side recycle bin. The size of the recycle bin may also be fixed as a percentage of the total space available.
Moreover, various recycle bin procedures may be implemented when the size of a file or directory to be recycled exceeds the space allocated to the server-side recycle bin. For example, the oldest pre-existing file or files in the recycle bin may be deleted to free up space in the recycle bin for a newly recycled file or directory. Alternatively, the ability of the user to delete files or directories may be suspended or curtailed. In any event, various indications that the recycle bin's storage capacity has been exceeded may be sent to the user or other authority.
One embodiment of the server-side recycle bin system of the present invention will now be described with greater particularity and with reference to
The server and the local computer system are connected via the Internet. Communication between the applications may be performed using Transaction Control Protocol via the Internet Protocol (TCP/IP), or User Datagram Protocol via the Internet Protocol (UDP/IP). These protocols have been commonly used for communication across the Internet since the inception of the Internet.
When a user operating from the local computer wishes to delete, or recycle, a file or directory located within the user's file space (18), the user inputs any of several file/directory deletion commands available on the user interface of the local file manager application (14). The file manager application (14) thereafter notifies (1) the file serving application (16). In response, file serving application moves (2) the file or directory to be deleted from its original location within the user's file space (18) to the recycle bin space (19) and renames it to a unique name to prevent any potential name conflict with any of the files and/or directories preexisting within the recycle bin space. An entry is added to the index of the recycle bin, including the original location of the file and/or directory, as well as the time and date it was recycled. The size of the recycle bin is regulated at this point. If the addition of the file and/or directory to the recycle bin will cause the recycle bin to exceed its size limit, the files and/or directories which were recycled earlier are removed in the order in which they were recycled, until there is enough space for the new file and/or directory to be stored. If the file and/or directory is too large for the recycle bin, it will still be placed in the recycle bin, but all other content in the recycle bin will have been discarded first. The file serving application (16) responds (3) with a success or failure status for the recycle operation.
When a user operating from the local computer wishes to view the contents of the recycle bin, the user inputs an appropriate command, and the local file manager application (14) requests (4) a listing of the content of the recycle bin (19). In response, the file serving application (16) reads (5) the recycle bin index and sends (6) the recycle bin index to the local file manager application (14), which interprets the data and presents it to the user.
Should the user wish to restore a deleted file and/or directory from the server-side recycle bin, the user inputs such a command and the file manager (14) sends a request (7) to the file serving application (16) to restore the file. The file serving application then moves (8) the file and/or directory from the recycle bin to its previous or other location and renames it to its original name. The file and/or directory is logically removed from the recycle bin index. The file serving application responds (9) with a status which indicates the success or failure of the operation.
A user wishing to empty the recycle bin specifies so by means of the user interface of the local file manager application. The file manager application (14) sends a request (10) to the file serving application, which discards (11) the files and/or directories contained in the recycle bin and clears the recycle bin index. The file serving application responds (12) to the request (10) with a status which indicates the success or failure of the operation.
Of course, it will be understood by one skilled in the art that the above-described embodiment may easily be modified when the local computer system (13) and the server (15) are connected via a local area network or similar network. In such an embodiment, the local file manager application (14) and file serving application (16) would communicate via any one of several well-known protocols, including TCP/IP, UDP/IP, Apple Talk, NetBEUI, DLC, IPX/SPX, or the like. Moreover, the above-described embodiment may also be easily modified when the local computer system (13) and the server (15) are connected via a wide area network or similar network. In such an embodiment, the local file manager application (14) and file serving application (16) would also communicate via any one of several well-known protocols, including ATM, Frame Relay, or the like.
Another embodiment of the server-side recycle bin system of the present invention will now be described with greater particularity and with reference to
The server (115) and the local computer system (120) are once again connected via the Internet. Communication between the applications may be performed using TC/IP, UDP/IP, or other suitable protocols.
When a user operating from the local computer (120) wishes to delete a file or directory located within the user's local persistent storage device (122), the user inputs any of several deletion commands available on the user interface of the local file manager application (121). The file manager application reads (101) the file and/or directory from the local storage device, and sends it (102) to the file serving application (116), along with a request that the file and/or directory be placed in the user's recycle bin (119). The file serving application (116) writes (103) the transferred file into the recycle bin (119) and renames it to a unique name to prevent any potential name conflict with any of the files and/or directories preexisting within the recycle bin space. As with the first embodiment, an entry is added to the directory of the recycle bin, including the original location of the file and/or directory, as well as the time and date it was recycled. The size of the recycle bin is then regulated: If the addition of the file and/or directory to the recycle bin will cause the recycle bin to exceed its size limit, the files and/or directories which were recycled earlier are removed in the order in which they were recycled, until there is enough space for the new file and/or directory to be stored. If the file and/or directory is too large for the recycle bin, it will still be placed in the recycle bin, but all other content in the recycle bin will have been discarded first. The file serving application (116) responds (104) with a success or failure status for the recycle operation. When the local file manager application (121) receives a success status, the recycled file and/or directory is removed from the local persistent storage device (122), or alternatively, transferred to a preexisting local recycle bin (not shown) within the local persistent storage device (122), as for example, in standard Windows®-based operating systems.
When a user from the local computer wishes to view the contents of the server-side recycle bin (119), the user inputs an appropriate command, and the file manager application (121) requests (105) a listing of the content of the recycle bin (119). In response, the file serving application (116) reads (106) the recycle bin index and sends (107) the recycle bin index to the local file manager application (121), which interprets the data and presents it to the user.
Should the user wish to restore a deleted file and/or directory from the server-side recycle bin, the user inputs such a command, and the file manager (121) sends a request (108) to the file serving application (116) to restore the file. The file serving application (116) then reads (109) the specified file and/or directory from the recycle bin (119), and sends (110) it to the local file manager application (121), along with a request that the file and/or directory be placed in its previous or other location within the user's local persistent storage device (122) and be renamed it to its original name. Following this request, the file manager application (121) writes (111) the file and/or directory to this appropriate space. Optionally, the file serving application (116) logically removes the restored file and/or directory from the recycle bin (119), upon receipt of a status message from the file manager application indicating the success of the restoration operation (not shown in figure).
As in the previously-detailed embodiments, a user wishing to empty the recycle bin (119) specifies so by means of the user interface of the local file manager application (121). The file manager application (121) sends a request (112) to the file serving application (116), which discards (113) the files and/or directories contained in the recycle bin (119) and clears the recycle bin index. The file serving application responds (114) to the request (112) with a status which indicates the success or failure of the operation.
Still another embodiment of the server-side recycle bin system of the present invention will now be described with greater particularity and with reference to
Running on the server (215) is a file serving application (216). The server (215) also includes at least one persistent storage device (217). Contained within such persistent storage device (217) is a file space (218) accessible to the user's local computer system. Also contained within the persistent storage device (217) is the user's server-side recycle bin (219). Various other applications and files, located on the server (215), may also be made available to the local computer system. The server (215) and the web serving machine (213) are connected via the Internet and communicate via TCP/IP, UDP/IP, or other suitable protocols.
A user operating from the Internet enabling device (222) initiates the deletion (recycling) of a file or directory residing in the user's file space (218) by inputting any one of several deletion commands available on the web browser or custom application (221). A message is sent (201) from web browser or custom application to the web server application (220), which relays it to the file manager application (214). The file manager application relays the message to the file serving application (216) running on the server (215). The file serving application responds by moving (202) the file or directory to be deleted from its original location within the user's file space (218) to the recycle bin space (219) and renaming it to a unique name. It also adds an entry to the directory of the recycle bin, including the original location of the file and/or directory and the time and date it was recycled, and it regulates the size of the recycle bin. Finally, the file serving application (216) responds (203) with the success or failure status for the recycle operation, this responds being relayed back to the web browser or custom application (221).
In a similar fashion, a user wishing to view the contents of the server-side recycle bin inputs an appropriate command to web browser or custom application (221), which sends a request (204) to the web server application (220). The web server application relays the request to the file manager application (214), which in turn relays the request to the file serving application (216) running on the server (215). The file serving application reads (205) the recycle bin index and sends (206) the index to the file manager application (214). The file manager application interprets the data and presents it to the user through the web server application (220) and web browser or custom application (221).
Restoration of a deleted file and/or directory from the server-side recycle bin is initiated by the user through an appropriate command on the web browser or custom application (221). A request (207) is relayed to the web application (220), which send the appropriate information to the file manager application (214). The file manager application relays the request to the file serving application (216). The file serving application then moves (208) the file and/or directory from the recycle bin to its previous or other location and renames it to its original name. The file and/or directory is logically removed from the recycle bin index, and the file serving application responds (209) to the file manager application (214) with a status which indicates the success or failure of the operation. This response is relayed to the web server application (220), which in turn relays it to the web browser or custom application (221).
The process of emptying recycle bin is initiated when the user so specifies so by means of the user interface on the Internet enabled device (222). This results in a request (210) being sent to the web server application (220), which relays it to the file manager application (214). The file manager application relays the request (210) to the file serving application (216), which discards (211) the files and/or directories contained in the recycle bin (219) and clears the recycle bin index. The file serving application then responds (212) to the request (210) with a status which indicates the success or failure of the operation. The response is relayed from the file manager application (214) to the web server application (220), which relays it to web browser or custom application (221) on the Internet enabled device (222).
Those skilled in the art will appreciate that still other embodiments are possible according to the present invention, and that the scope of the present invention is not limited to the specific embodiments disclosed herein.
The following references, to the extent that they provide exemplary procedural or other details supplementary to those set forth herein, are specifically incorporated herein by reference.
Not Applicable
Not Applicable.
Blythe, Bobby Ernest, Davis, Ray Charles
| Patent | Priority | Assignee | Title |
| Patent | Priority | Assignee | Title |
| 5625818, | Sep 30 1994 | Apple Inc | System for managing local database updates published to different online information services in different formats from a central platform |
| 5727203, | Mar 31 1995 | Sun Microsystems, Inc. | Methods and apparatus for managing a database in a distributed object operating environment using persistent and transient cache |
| 5737737, | May 22 1992 | Canon Kabushiki Kaisha | Data management method and apparatus |
| 5813017, | Oct 24 1994 | International Business Machines Corporation | System and method for reducing storage requirement in backup subsystems utilizing segmented compression and differencing |
| 5838319, | Dec 13 1994 | Microsoft Technology Licensing, LLC | System provided child window control for displaying items in a hierarchical fashion |
| 5905492, | Dec 06 1996 | Microsoft Technology Licensing, LLC | Dynamically updating themes for an operating system shell |
| 5977971, | Dec 13 1994 | Microsoft Technology Licensing, LLC | Tree view control |
| 5983240, | Dec 15 1995 | Microsoft Technology Licensing, LLC | Method and system of converting data from a source file system to a target file system |
| 6044405, | Apr 12 1996 | COLORADO WSC, LLC | Service network incorporating geographically-remote hubs linked by high speed transmission paths |
| 6091411, | Dec 06 1996 | Microsoft Technology Licensing, LLC | Dynamically updating themes for an operating system shell |
| 6108651, | Sep 09 1997 | Meta Platforms, Inc | Heuristic co-identification of objects across heterogeneous information sources |
| 6147687, | Oct 02 1998 | International Business Machines Corporation; IBM Corporation | Dynamic and selective buffering tree view refresh with viewable pending notification |
| 6295355, | Mar 31 1999 | Microsoft Technology Licensing, LLC | Learned speed dialing |
| 6345318, | Oct 07 1998 | International Business Machines Corporation | System for maintaining a user-modifiable confirmation message configuration record that specifying with respect to a plurality of operations whether to communicate a confirmation message |
| 6356863, | Sep 08 1998 | DAYLIGHT CHEMICAL INFORMATION SYSTEMS, INC | Virtual network file server |
| 6366988, | Jul 18 1997 | STORACTIVE, INC | Systems and methods for electronic data storage management |
| 6380957, | Dec 15 1998 | International Business Machines Corporation | Method of controlling view of large expansion tree |
| 6411685, | Jan 29 1999 | Microsoft Technology Licensing, LLC | System and method for providing unified messaging to a user with a thin web browser |
| 6417869, | Apr 15 1998 | CITICORP CREDIT SERVICES, INC USA | Method and system of user interface for a computer |
| 6446091, | Jul 29 1999 | HEWLETT-PACKARD DEVELOPMENT COMPANY, L P | Method and apparatus for undeleting files in a computer system |
| 6886030, | Aug 18 1998 | Rovi Guides, Inc; UV CORP ; TV GUIDE, INC | Electronic mail system employing a low bandwidth link for e-mail notifications |
| 20020016750, | |||
| 20020056031, | |||
| EP735473, |
| Executed on | Assignor | Assignee | Conveyance | Frame | Reel | Doc |
| May 21 2009 | Synacor, Inc. | (assignment on the face of the patent) | / | |||
| Jun 23 2010 | SIMDESK TECHNOLOGIES, INC | SIMDESK ACQUISITION CORP | ASSET PURCHASE AGREEMENT | 029485 | /0641 | |
| Oct 05 2010 | SIMDESK ACQUISITION CORP | MEZEO SOFTWARE CORP | CHANGE OF NAME SEE DOCUMENT FOR DETAILS | 029485 | /0690 | |
| Jun 27 2014 | MEZEO SOFTWARE CORPORATION | ZIMBRA, INC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 033726 | /0215 | |
| Aug 04 2015 | ZIMBRA, INC | NXT CAPITAL SBIC, LP | SECURITY INTEREST SEE DOCUMENT FOR DETAILS | 036256 | /0135 | |
| Aug 08 2015 | SIMDESK TECHNOLOGIES, INC | SIMDESK ACQUISITION CORP | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 036756 | /0205 | |
| Sep 10 2015 | ZIMBRA, INC | SYNACOR, INC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 036756 | /0302 | |
| Sep 25 2015 | SYNACOR, INC | Silicon Valley Bank | FIRST AMENDMENT TO INTELLECTUAL PROPERTY SECURITY AGREEMENT | 036688 | /0352 | |
| Aug 07 2019 | SYNACOR, INC | Silicon Valley Bank | INTELLECTUAL PROPERTY SECURITY AGREEMENT | 049999 | /0701 | |
| Mar 29 2021 | NXT CAPITAL, LLC SUCCESSOR IN INTEREST BY MERGER TO NXT CAPITAL SBIC, LP | ZIMBRA, INC | RELEASE BY SECURED PARTY SEE DOCUMENT FOR DETAILS | 055762 | /0875 | |
| Nov 19 2021 | SYNACOR, INC | Silicon Valley Bank | SECURITY INTEREST SEE DOCUMENT FOR DETAILS | 058181 | /0469 |
| Date | Maintenance Fee Events |
| Date | Maintenance Schedule |
| Feb 23 2019 | 4 years fee payment window open |
| Aug 23 2019 | 6 months grace period start (w surcharge) |
| Feb 23 2020 | patent expiry (for year 4) |
| Feb 23 2022 | 2 years to revive unintentionally abandoned end. (for year 4) |
| Feb 23 2023 | 8 years fee payment window open |
| Aug 23 2023 | 6 months grace period start (w surcharge) |
| Feb 23 2024 | patent expiry (for year 8) |
| Feb 23 2026 | 2 years to revive unintentionally abandoned end. (for year 8) |
| Feb 23 2027 | 12 years fee payment window open |
| Aug 23 2027 | 6 months grace period start (w surcharge) |
| Feb 23 2028 | patent expiry (for year 12) |
| Feb 23 2030 | 2 years to revive unintentionally abandoned end. (for year 12) |