US 7,165,071 B2Grant
Real-time search engine
Issue Date:2007-01-16
•23 Claims
•5 Drawing Sheets
Abstract
A search engine operates substantially in real time through instant updates by the servers on a file sharing network. A server coming on-line in the network and comprising a first data object such as an audio file, video file, executable file, or text file, is configured to upload a description, such as a song title or file name, of the first data object, to the search engine during the log-in process. The search engine comprises a data-object description table for storing and correlating various data object descriptions to respective server identifiers identifying servers currently on line that store the data objects defined by the data object descriptions. During the log-in process, the search engine is configured to correlate the identifier of the server coming on-line with a data-object description of a data object stored in the server coming on-line. A requesting server seeking a specific data file is configured to identify a data object description of the requested data file in a request transmitted to the search engine. In response to a request, the search engine is configured to download to the requesting server the server-identifiers that are stored within the data-object description table in a relationship with the data-object-description of the request. The requesting server is configured to select a source server from among the server identifiers provided by the search engine, and to download the requested data file from the select source server. A server notifies the search engine when the download is complete. The search engine is configured to update the relationships within the data-object description table to reflect that the requested file is now within the requesting server. The search engine is further configured to purge from the data-object description table any relationships between a server and a data-object or data file when that server has gone off line, or when that data file has been removed from the server.
Metadata
Assignee
- Napster, Inc.
Inventors
- Shawn Fanning
- John Fanning
- Edward Kessler
Application Information
Application Number:US 10/025,443
Filing Date:2001-12-19
Priority Date:1999-12-15
Art Unit:2161
Classifications
IPC:
G06F17/30G06F15/167G06F15/16
Patent Drawings (5 sheets)
Description
Related Applications
[0001] This Patent Application is a continuation of U.S. patent application Ser. No. 09/464,653, filed on Dec. 15, 1999 now U.S. Pat. No. 6,366,907 and entitled REAL-TIME SEARCH ENGINE.
Background
[0002] Search engines as they currently exist on the Internet are used by people all over the world to find and download data objects of interest that reside on servers. Typically, these search engines periodically examine many servers on the Internet to see what data objects each server contains. Thereafter, the search engine constructs an index of each server's contents, and links the contents to that server's location.
[0003] The construction of the index is a time consuming task, and because of the relative cost involved to the servers and the search engine, it cannot be done very often. The timeliness of the information created by the search engine is sacrificed in order to reduce the burden on the index builder of the search engines and the servers that contain the data being searched.
[0004] This means that the search engine index is quickly out of date. For some types of data objects, this matters very little, since the data objects are created and modified relatively slowly. However, for data objects that are created and removed relatively often, the search engine indices are impractical, and for data objects that are added and removed daily, the standard search engines are practically useless. In addition, the current paradigm assumes a relatively static server environment, but in an environment where servers come up and go down relatively frequently and data objects are added and deleted hourly or more frequently, the standard search engine methodology is not useful at all.
[0005] Thus, it can be seen that there is a need for an Internet search engine that maintains an up-to-date index of data content residing on servers that are currently connected to the Internet.
[0006] There is a further need for a real-time search engine that significantly reduces the cost of constructing a search engine index using methods employed by the prior art.
Summary
[0007] The present invention satisfies these needs by providing a method for creating a real-time search engine over the Internet that provides a search response containing data object descriptions and server descriptions 34 of data objects that are currently available for transfer from a provider server directly to a recipient client in response to a recipient client search request. This method comprises the provider server connecting to a real-time search engine through the Internet, the provider server providing the real-time search engine with data object descriptions of data objects residing on the provider server, and the real-time search engine indexing data object descriptions associated with the data object of the provider server, wherein the data object descriptions provided by the provider server are purged from the real-time search engine when the provider server is disconnected from the real-time search engine.
[0008] The method further comprises the provider server automatically, in real-time, providing the real-time search engine with data object descriptions of data objects that are added to the provider server.
[0009] The method preferably further comprises the provider server automatically, in real-time, notifying the real-time search engine of data objects that are removed from the provider server, wherein the real-time search engine then purges the data object descriptions.
[0010] The data object descriptions comprise any of the following: a title of the data object, the size of the data object, the type of data object, any text associated with the data object, the creator of the data object, the quality rating of the data object, and the provider server on which the data object resides. The server description 34 comprises any of the following: the server Internet Protocol address, the number of simultaneous connections allowed by the server, the server's reliability, and the server's name.
[0011] Preferably, a client search command is used, wherein a recipient client searches the data object descriptions to find the best data object and selects the most optimal provider server that the data object resides on.
[0012] Furthermore, the recipient client search request further comprises a provider server limitation criteria, wherein the search engine prunes the search response of all provider servers that do not meet the server limitation criteria.
[0013] In a preferred embodiment, the provider server limitation criteria comprises a bandwidth limitation, wherein the search engine prunes the search response of provider servers that have a bandwidth capability that is below the bandwidth limitation.
[0014] Optionally, the real-time search engine purges from the search response provider servers that cannot accept additional recipient client download requests.
[0015] Also in a preferred embodiment, an automated search response sort by the client. The automated search response is sorted by the responsiveness value, wherein the responsiveness value is determined by measuring the amount of time an echo reply message takes to be returned by the provider server to the recipient client. Preferably, the provider server is pruned from the search response if the provider server did not respond to the recipient client's echo request within a specified period of time.
[0016] The data object is of the type selected from the group comprising: an audio data object, a text data object, a image data object, a video data object, and a software executable data object.
[0017] In a preferred embodiment, the real-time search engine further comprises the recipient selecting one of the provider servers in the search response, and then the recipient client downloading the data object from the selected provider server. Additionally, the recipient client simultaneously operates as a provider server to other recipient clients, making data objects that have been downloaded by the recipient client available to other recipient clients on the Internet.
Brief Description of the Drawings
[0018] FIG. 1 is an overview diagram of a preferred embodiment of the system of the present invention;
[0019] FIG. 2 is an overview diagram of a preferred embodiment of the real-time search engine with its search engine, index builder and gateway components;
[0020] FIG. 3 is a flow chart of an embodiment of the process when a new data object is downloaded from the Internet, or otherwise added to the provider server, or during the initial scan of the data object collection during the log-in process; and
[0021] FIG. 4 is a flow chart of an embodiment of a search request constructed by a recipient client.
Detailed Description
[0022] The invention provides a method for creating a real-time search engine over the Internet that provides a search response containing data object descriptions and server descriptions of data objects that are currently available for transfer from a provider server directly to a recipient client in response to a recipient client search request. It is the essence of this invention that data object descriptions provided by the provider server are purged from the real-time search engine when the provider server is disconnected from the real-time search engine. This provides the recipient client with search results that include only those server sources that are currently available to provide and transfer any data to the recipient client.
[0023] Turning now to the figures, the overall configuration of the invention and its components are shown in FIG. 1 . Essentially the components of a real-time search includes at least one recipient client 16 which connects to the real-time search engine 10 to locate a desired data object 24. At least one provider server 12 connects to the real-time search engine and provides one or more data object descriptions 22 to the real-time search engine. If the provider server 12 is disconnected from the real-time search engine, the data object descriptions 22 are purged from the real-time search engine, indicating that those data objects 24 are no longer available for download from the provider server to the recipient client 16.
[0024] Preferably, the provider server automatically, in real-time, provides the real-time search engine with data object descriptions 22 of data objects 24 that are added to the provider server 12.
[0025] Also, preferably, the provider server also automatically, in real-time, notifies the real-time search engine 10 of data objects 24 that are removed from the provider server 12, wherein the real-time search engine then purges the data object descriptions 22.
Recipient Client
[0026] Recipient clients connect to the real-time search engine 10 to find the best provider server that contains the particular data object that the recipient client 16 wishes to download from a provider server. The recipient client preferably uses a recipient browser 18 for communicating with the real-time search engine 10 and for making search requests from the real-time search engine. Examples of these browsers include the Nescape Communicator or the Microsoft Explorer or other custom interfaces.
[0027] Connections are typically software protocols that provide a method for transmitting information between entities that are connected; an example of such a protocol is TCP, which is the preferred connection protocol for the invention. However, other protocols that fulfill the same basic functionality as TCP (such as a UDP protocol with retransmits, and a disconnection timeout) will also suffice. These protocols are well known in the art.
[0028] In another embodiment, where the data object 24 is a text file, the search request contains any one of the following: a partial filename, keywords, author, the size of the file, the category, and the description of the text.
[0029] In one embodiment, where the data object 24 is an audio data file, the search request contains any one of the following: a partial filename, a bitrate (bps), a sample rate (Hz) of the data, the size of the file, the duration, the name of the author or artist, the song title, the genre, and the title of the album.
[0030] In another embodiment, where the data object 24 is an image or video file, the search request contains any one of the following: a partial filename, the amount and type of compression, the size of the file, the category, and the description of the image or video.
[0031] When a search response is returned to the recipient, the recipient browser 18 displays the results of the search request for the recipient to examine.
[0032] In a preferred embodiment, the recipient client 16 determines a response time of each of the provider servers returned in the search response. The response time is measured by the recipient client 16 sending an ICMP echo packet to each provider server, and measuring the amount of time it takes to receive a reply from the provider server. The recipient client browser 18 uses the response time to sort the data object descriptions 22, which then displays the data object descriptions of the provider servers in order of their response time.
[0033] In an embodiment, the recipient may choose a search parameter for the real-time search engine 10 to provide a search response 38 that includes only data object descriptions on provider servers that have a minimum data transfer bandwidth capability.
[0034] In another embodiment, the recipient directs the search engine to return a search response 38 containing only data object descriptions for provider servers that are not currently too busy to accept additional download requests.
[0035] In one embodiment, the provider server is not located behind a firewall. The recipient client 16 downloads a data object 24 from the provider server by connecting directly to the provider server, requesting a data object, and then storing the data object in the recipient's data object collection.
[0036] In one embodiment, an optimal provider server is automatically selected from among at least two provider servers that are able to supply a desired data object using a scoring mechanism. The scoring mechanism comprises the roundtrip response time from the recipient client to the provider server, the Internet connection line speed (data transfer speed) of the provider server, the size of the file, and the reliability of the provider server. The best score is usually from a provider server that has a high line speed and high provider server reliability. The provider server with the best score is preferably selected by the recipient client for download.
[0037] In another embodiment, in order to determine the best score, the recipient client or the provider server uploads to the real time search engine the actual transfer rate for each data object transfer which is used to calculate of the effective line speed of the provider server.
Provider Server
[0038] Each provider server contains a data object collection of data objects 24 that may be downloaded from the provider server. When the provider server is prepared to provide data objects to any requesting recipient client 16, the provider server connects to the real-time search engine, and uploads descriptions of each data object in the data object collection. The real-time search engine is updated immediately. The data object descriptions 22 comprise any of the following: a title of the data object, the size of the data object, the type of data object, any text associated with the data object, the creator of the data object, the quality rating of the data object, and the provider server on which the data object resides.
[0039] In the preferred embodiment, the connection between provider server and real-time search engine 10 is accomplished using the TCP protocol. Occasional messages are sent between provider server 12 and the real-time search engine to assert that the connection between the two is valid. If no message is received from the provider server for several minutes, the connection is closed and the connection to the provider server is broken.
[0040] In one embodiment, the provider server authenticates itself to the real-time search engine using a login process, in immediately after connecting to the real-time search engine, by transmitting a login name and a password.
[0041] In another embodiment, a determination is made if the provider server 12 is protected by a firewall, and this determination is transmitted to the real-time search engine 10 during the initial login.
[0042] In yet another embodiment, when the provider server scans the data objects in the data object collection, each data object's type is ascertained by examining the extension on the filename (.mp3, jpg, mpg, .doc are a few examples). Files without extensions are ignored. Each file is validated as to the proper formatting of the data contained within. Data objects that fail validation do not have their descriptions uploaded to the real-time search engine.
[0043] When data objects are added to the provider server, the provider server transmits the new data object's description to the real-time search engine. Likewise, when a data object 24 is deleted, the provider server 12 notifies the real-time search engine of the deletion.
[0044] In one embodiment, during the login process the provider server only transmits the changes that were made in its data object collection since the last connection to the real-time search engine. Both the real-time search engine 10 and the provider server store a copy of the data object descriptions that have been uploaded to the real-time search engine, and all of the successfully acknowledged changes to those descriptions. In this way, the initial information transmitted from the provider server to the real-time search engine is minimized for large data object collections.
[0045] In the preferred embodiment, the data object collection is at least one directory on the provider server. The data object collection alternatively contains other directories that themselves contain other data objects or more directories.
[0046] In another embodiment, the data object collection is stored on a computer remote from the provider server 12, but is accessible by the provider server. A data object collection is optionally data objects in a database, files in a directory, data objects in memory, on CD-ROM, flash memory, etc.
[0047] In one embodiment, the provider server also contains a server description, which comprises its own data transfer line bandwidth to the Internet, and it uploads this server description during the initial connection to the real-time search engine.
[0048] In a preferred embodiment, both the provider server and recipient client 16 are located within the same executable image. Thus, whenever a recipient runs a recipient browser, he also simultaneously runs a provider server.
[0049] In one embodiment, data objects downloaded by the recipient client from other provider servers are immediately added to the data object collection, making these data objects instantly available to other recipient clients on the Internet. In this embodiment, the rapid spread of data objects throughout the network of provider servers and recipient clients is greatly facilitated.
[0050] In a preferred embodiment, a data object fingerprint is constructed by performing a checksum of the data object. Each data object is uniquely identifiable by the fingerprint of the data object's data.
[0051] In a preferred embodiment, if the provider server 12 is not behind a firewall, recipient clients connect directly to the provider server, and request that a chosen data object be transferred from the provider server and downloaded to the recipient client 16. If the provider server is behind a firewall, then the recipient client 16 asks the real-time search engine 10 to pass the download request to the provider server. When the provider server receives this download request, it then connects to the recipient client 16 and then the download occurs. If both the provider server 12 and the recipient client are protected by firewalls, a proxy server is used to facilitate the transfer. The recipient client informs the real-time search engine of the download request, the real-time search engine transmits the request to the provider server, the recipient client and the provider server both connect to the proxy server, which then allows data to flow and hence the download to occur between the recipient client and the provider server through the proxy server.
Real-Time Search Engine
[0052] As shown in FIG. 2 , in a preferred embodiment, the real-time search engine has the following components: at least one search engine Gateway, at least one search engine, at least one search engine Index Builder, and a search engine Index.
Search Engine Gateway
[0053] In the preferred embodiment, each provider server that connects to the real-time search engine connects to the search engine gateway 44 component. When a provider server uploads information about the data objects it contains, the search engine gateway 44 takes this information and passes it to the search engine index builder 42, which uses it to update the search engine index. When an provider server disconnects, or is disconnected by a network error, or otherwise fails to communicate with the real-time search engine, the search engine gateway detects this, and informs the search engine index builder 42, which in turn removes the data object descriptions uploaded by that provider server 12 from the search engine index.
[0054] Alternatively, when a particular provider server is disconnected, the search engine index builder 42 does not actually remove the data object, but instead marks the data object descriptions as “Not Available.” When that provider server re-connects, instead of transmitting the entire list of data object descriptions, it transmits only changes to its data object collection that may have occurred during the disconnected period. During searches, the search engine 40 ignores all data object descriptions that are marked as “Not Available.”
[0055] In one embodiment, each recipient client 16 also connects to a search engine gateway. In this embodiment, each search engine gateway 44 connects in turn to a search engine 40. All search requests from recipient clients are transmitted to the search engine gateway, and the search engine gateway then transmits the search requests to the connected search engine. The search engine executes the search request, and transmits the search response 38 back to the search engine gateway, which in turn transmits the search response back to the originating Recipient client.
[0056] In another embodiment, the search engine gateway tracks data object downloads initiated by recipient clients. The recipient client transmits a request to download a particular data object from a provider server. If the download is successful, the recipient client 16 informs the search engine gateway 44 that the download was completed. Using this information, the search engine gateway tracks the reliability of the provider server, as well as the current number of recipient clients downloading data objects from a particular provider server.
Search Engine
[0057] The search engine receives search requests 36 from recipient clients, executes the search requests, and constructs search responses. The search responses are transmitted back to the recipient clients.
[0058] In another embodiment, the search engine also receives search requests from search engine gateways, that are simply relaying the search requests from recipient clients.
[0059] In the preferred embodiment, a Search request contains: a partial data object name, an optional minimum data object quality rating, an optional minimum provider server connection bandwidth, and an optional maximum number of data object descriptions to be retrieved.
[0060] Each search response contains a list of data object descriptions as well as a list of server descriptions. In the preferred embodiment, a subset of the fields in the data object descriptions and server descriptions are returned in the search response, including: a provider server name and Internet Protocol (IP) Address, a provider server bandwidth description (56 k modem, DSL, T1, etc), a data object name (in the audio embodiment, the song title and artist name), a data object fingerprint, a data object size (in bytes), and a data object quality rating.
[0061] To execute the search, the search engine uses the fields in the search request to scan the records stored in the search engine index. If a particular data object description is marked as “Not Available” it is ignored by the search engine.
[0062] In one embodiment, the search engine gateway and the search engine exist in the same process. In another embodiment, the search engine gateway and the search engine exist on different processes, but run on the same machine. Many configurations of machines, search engine gateways, and search engines are possible.
Search Engine Index
[0063] In a preferred embodiment, the search engine index has two internal tables. These tables include a data object description table and a provider server description table. These tables are managed by the search engine index builder.
[0064] The provider server description table contains a collection of provider server descriptions 34. Some of these fields are uploaded by the provider servers during the initial connection to the search engine gateway. Others are calculated as events occur. In the preferred embodiment, entries in this table contain the following fields:
-
- [0065] server name & IP Address
- [0066] password
- [0067] connection bandwidth (T1, 56 k modem, DSL, etc)
- [0068] must push data objects to recipient client?
- [0069] list of data object descriptions for this server
- [0070] remaining available connections allowed by Provider server
- [0071] site reliability (% of successful transfers)
[0072] The data object description table contains a collection of data object descriptions 22. These are uploaded by the provider server 12. As data objects are added, new data object descriptions are uploaded. As data objects are removed, existing data object descriptions are removed or optionally marked for removal. In a preferred embodiment, entries in this table contain the following fields:
-
- [0073] filename
- [0074] metadata (in the audio embodiment, song name, artist name, song description)
- [0075] the data object fingerprint
- [0076] size (in bytes)
- [0077] quality rating (in the audio embodiment, the encoding bit rate and sampling frequency)
- [0078] a link to the Provider server Description record
Execution Processes
[0079] Five different execution processes are serviced by the system: data object added, data object removed, search request, provider server connect, provider server disconnect.
Data Object Added
[0080] In an embodiment as shown in FIG. 3 , when a new data object is created on a provider server, when a new data object is downloaded from the Internet, or during the initial scan of the data object collection during the log-in process, the following processes occur:
[0081] a) the data object fingerprint is calculated,
[0082] b) the data object is given a name, a source name, size, and a quality rating, forming an data object description,
[0083] c) the data object description is uploaded to the search engine Gateway, and passed to the search engine index builder,
[0084] d) The search engine index builder creates a new data object description entry in the search engine index, and
[0085] e) the search engine Index Builder updates the Provider server Description entry for this server to reflect the new data object description Entry.
Data Object Removed
[0086] In an embodiment, when an existing data object is removed, the following occurs:
[0087] a) the data object fingerprint is retrieved,
[0088] b) the data object fingerprint is transmitted to the search engine gateway, and passed to the search engine index builder,
[0089] c) the search engine index builder removes the data object description entry for that provider server, and
[0090] d) the search engine index builder updates the provider server description entry for that provider server to reflect the removal of the data object description.
Search Request
[0091] In an embodiment as shown in FIG. 4 , when a search request is constructed by a recipient client 16, the following occurs:
[0092] a) the search request is uploaded to the search engine,
[0093] b) the search engine searches the name column of the data object description table for all matches on the data object name,
[0094] c) the search engine prunes the resulting data object description list using the provider server bandwidth limitation and the minimum quality rating limitation,
[0095] d) if at any time the number of data object descriptions returned exceeds the maximum number of data object descriptions limitation, the search terminates and no further data object descriptions are retrieved, and
[0096] e) the resulting list of data object descriptions and related server descriptions are sent to the recipient client.
Provider Server Connect
[0097] In an embodiment, when a provider server first connects to the real-time search engine, the following occurs:
[0098] a) a provider server description record is created for the provider server,
[0099] b) data object descriptions for all data objects in the provider server's data object collection are uploaded to the search engine gateway, and passed to the search engine index builder, and
[0100] c) the search engine index builder treats each uploaded data object description as a data object added process.
Provider Server Disconnect
[0101] In an embodiment, when an provider server disconnects from the real-time search engine, the following occurs:
[0102] a) the search engine index builder removes all data object descriptions referring to this Provider server as in the data object removed process, and
[0103] b) the search engine index builder deletes or optionally marks for deletion the provider server description record.
Alternate Embodiments
[0104] In one embodiment, the data objects are audio files, and the data object descriptions comprise the filename, the bit rate, sampling frequency, and size obtained from the audio file itself. In this embodiment, preferably the recipient client 16 also incorporates an audio player, for playing the audio file. Also, the provider server contains a mechanism for constructing an audio file from a CD or other audio media source, that deposit newly-created audio files into the data object collection.
[0105] In another embodiment, the data objects are image and video files, and the data object descriptions include the filename, the compression detail and other information obtained from the jpg file itself, as well as a short description of the image. In this embodiment, preferably the recipient client 16 application also incorporates a means for displaying the image or video file, and the provider server incorporates a means for generating an image or video file from a photo or other visual image source.
[0106] In yet another embodiment, the data objects may be text, audio, image, and video data objects. Example formats include HTML text, MP3 audio, JPEG still image, and MPEG video data. Each different type of data object is also then distinguishable by type, as well as by name, and the other attributes mentioned previously.
[0107] As new image sources, and image compression and storage mechanisms become available, data object generation methods for these protocols and storage formats can be added to the recipient client and provider server without deviating from the spirit of this invention.
Claims
What is claimed is:
1. A file sharing network for sharing files among a plurality of servers comprising:
a. a search engine comprising a data object description table;
b. a plurality of servers including a first server defined according to a first server identifier, the first server comprising a first data object defined according to a first data object description; and
c. a communication link coupling the search engine to the first server, wherein the first server is configured to transmit the first data object description that has changed to the search engine during a log-in process through a client of the first server with the search engine since a last connection of the first server to the search engine, and wherein the search engine is further configured to store the transmitted first data object description in the data object description table and configured to correlate the transmitted first data object description to the first server identifier within the data object description table during the log-in process.
2. The file sharing network according to claim 1 further comprising:
a. a second data object description stored within the data object description table in correlation with a second server identifier, wherein the second server identifier describes a second server and the second data object description describes a second data object; and
b. a first data object request stored within the search engine, wherein the first data object request was received from the first server, wherein the first data object request is for the second data object.
3. The file sharing network according to claim 2 wherein the search engine is configured to transmit the second server identifier to the first server in response to the first data object request.
4. The file sharing network according to claim 3 wherein the second server identifier defines a server from among a first set of potential server identifiers related to the second data object in the data object description table, wherein the search engine is configured to transmit, in response to the first data object request, the first set of potential server identifiers representing a first set of potential servers capable of transmitting the second data object to the first server, and wherein the first server is configured to select an optimal data source from which to receive the first data object from among a first set of potential servers, wherein a selection of the optimal data source is based upon a comparison of operational parameters respectively associated with each server among the first set of potential servers.
5. The file sharing network according to claim 4 wherein the operational parameters are selected from a group consisting of roundtrip response time between the first server and a potential server, internet connection line speed (bandwidth) of a potential server, a reliability of a potential provider server, a number of requests already queued to a potential server, and a size of a file requested for downloading.
6. The file sharing network according to claim 3 wherein the second server is configured to transmit the second data object to the first server upon a valid request by the first server.
7. The file sharing network according to claim 6 wherein the second server is configured to notify the search engine that the download of the second data object is complete.
8. The file sharing network according to claim 7 wherein the search engine is configured to correlate, within the data object description table, the second data object description to the first server identifier when the download of the second data object is complete.
9. The file sharing network according to claim 6 wherein the second server is configured to transmit data files to multiple servers in a time-multiplexed format.
10. The file sharing network according to claim 6 wherein the first server is configured to notify the search engine that a download of the second data object is complete.
11. The file sharing network according to claim 10 wherein the search engine is configured to correlate the second data object description to the first server identifier within the data object description table when the download of the second data object is complete.
12. The file sharing network according to claim 1 wherein the first server identifier is selected from a group consisting of a first internet protocol address, a first quantity of simultaneous connections that can be sustained by the first server, a reliability rating of the first server and a server name.
13. The file sharing network according to claim 1 wherein the first data object description is selected from a group consisting of a title of the first data object, a size of the first data object, a type of the first data object, a text associated with the first data object, and a creator of the first data object.
14. The file sharing network according to claim 1 wherein the first server is further configured to detect when the first data object is removed from a predetermined file location and to notify the search engine of the removal.
15. The file sharing network according to claim 14 wherein the search engine is configured to purge the relationship between the transmitted first data object description and the first server within the data object description table when the first server notifies the search engine of a removal of the first data object.
16. The file sharing network of claim 1 wherein the search engine is configured to periodically poll the first server to determine if any data objects have been removed from a predetermined file location within the first server.
17. The file sharing network according to claim 16 wherein the search engine is configured to purge the relationship between the transmitted first data object description and the first server within the data object description table when the search engine determines that the first data object has been removed from the predetermined file location within the first server.
18. The file sharing network according to claim 1 wherein the search engine is configured to send a periodic ping message between the search engine and the first server, and wherein the first server is configured to respond to the ping message.
19. The file sharing network according to claim 18 wherein the search engine is configured to purge the relationship between the first server identifier and the transmitted first data object description within the data object description table when the first server fails to respond to the ping message within a predetermined time.
20. The file sharing network according to claim 1 wherein the first server is configured to send a periodic ping message to the search engine following the log-in process.
21. The file sharing network according to claim 20 wherein the search engine is configured to purge the relationship between the first server identifier and the transmitted first data object description within the data object description table when the first server fails to send a ping message within a predetermined time.
22. The file sharing network according to claim 1 wherein the first server identifier comprises an IP address for accessing the first server over the internet.
23. The file sharing network according to claim 1 wherein the first data object is selected from a group comprising audio data, text data, video data, image data and software executable data.
Patent Citations (119)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US4506387(A) | 1985-03-01 | Walter | Applicant |
| US4616263(A) | 1986-10-01 | Eichelberger | Applicant |
| US4648123(A) | 1987-03-01 | Schrock | Applicant |
| US4745559(A) | 1988-05-01 | Willis et al. | Applicant |
| US4766581(A) | 1988-08-01 | Korn et al. | Applicant |
| US4769833(A) | 1988-09-01 | Farleigh et al. | Applicant |
| US4844679(A) | 1989-07-01 | Teranishi | Applicant |
| US4867628(A) | 1989-09-01 | Ammon et al. | Applicant |
| US4891720(A) | 1990-01-01 | Grant et al. | Applicant |
| US4893307(A) | 1990-01-01 | McKay et al. | Applicant |
| US4961139(A) | 1990-10-01 | Hong et al. | Applicant |
| US5014125(A) | 1991-05-01 | Pocock et al. | Applicant |
| US5093718(A) | 1992-03-01 | Hoarty et al. | Applicant |
| US5101488(A) | 1992-03-01 | Rosenthal et al. | Applicant |
| US5132789(A) | 1992-07-01 | Ammon et al. | Applicant |
| US5133065(A) | 1992-07-01 | Cheffetz et al. | Applicant |
| US5133079(A) | 1992-07-01 | Ballantyne et al. | Applicant |
| US5192999(A) | 1993-03-01 | Graczyk et al. | Applicant |
| US5220420(A) | 1993-06-01 | Hoarty et al. | Applicant |
| US5224205(A) | 1993-06-01 | Dinkin et al. | Applicant |
| US5233346(A) | 1993-08-01 | Minerd et al. | Applicant |
| US5357276(A) | 1994-10-01 | Banker et al. | Applicant |
| US5392400(A) | 1995-02-01 | Berkowitz et al. | Applicant |
| US5410343(A) | 1995-04-01 | Coddington et al. | Applicant |
| US5497502(A) | 1996-03-01 | Castille | Applicant |
| US5528281(A) | 1996-06-01 | Grady et al. | Applicant |
| US5544352(A) | 1996-08-01 | Egger | Applicant |
| US5570126(A) | 1996-10-01 | Blahut et al. | Applicant |
| US5608447(A) | 1997-03-01 | Farry et al. | Applicant |
| US5617539(A) | 1997-04-01 | Ludwig et al. | Applicant |
| US5625404(A) | 1997-04-01 | Grady et al. | Applicant |
| US5635979(A) | 1997-06-01 | Kostreski et al. | Applicant |
| US5675819(A) | 1997-10-01 | Schuetze | Applicant |
| US5701469(A) | 1997-12-01 | Brandli et al. | Applicant |
| US5712906(A) | 1998-01-01 | Gradys et al. | Applicant |
| US5715395(A) | 1998-02-01 | Brabson et al. | Applicant |
| US5734961(A) | 1998-03-01 | Castille | Applicant |
| US5737532(A) | 1998-04-01 | DeLair et al. | Applicant |
| US5754784(A) | 1998-05-01 | Garland et al. | Applicant |
| US5754938(A) | 1998-05-01 | Herz et al. | Applicant |
| US5764982(A) | 1998-06-01 | Madduri | Applicant |
| US5778185(A) | 1998-07-01 | Gregerson et al. | Applicant |
| US5778363(A) | 1998-07-01 | Light | Applicant |
| US5778368(A) | 1998-07-01 | Hogan et al. | Applicant |
| US5784562(A) | 1998-07-01 | Diener | Applicant |
| US5794178(A) | 1998-08-01 | Caid et al. | Applicant |
| US5794249(A) | 1998-08-01 | Orsolini et al. | Applicant |
| US5796393(A) | 1998-08-01 | MacNaughton et al. | Applicant |
| US5806065(A) | 1998-09-01 | Lomet | Applicant |
| US5845070(A) | 1998-12-01 | Ikudome | Applicant |
| US5848410(A) | 1998-12-01 | Walls et al. | Applicant |
| US5857179(A) | 1999-01-01 | Vaithyanathan et al. | Applicant |
| US5870744(A) | 1999-02-01 | Sprague | Applicant |
| US5877755(A) | 1999-03-01 | Hellhake | Applicant |
| US5878410(A) | 1999-03-01 | Zbikowski et al. | Applicant |
| US5884035(A) | 1999-03-01 | Butman et al. | Applicant |
| US5884046(A) | 1999-03-01 | Antonov | Examiner |
| US5884305(A) | 1999-03-01 | Kleinburg et al. | Applicant |
| US5903892(A) | 1999-05-01 | Hoffert et al. | Applicant |
| US5920854(A) | 1999-07-01 | Kirsch et al. | Applicant |
| US5920859(A) | 1999-07-01 | Li | Applicant |
| US5926811(A) | 1999-07-01 | Miller et al. | Applicant |
| US5931907(A) | 1999-08-01 | Davies et al. | Applicant |
| US5956711(A) | 1999-09-01 | Sullivan et al. | Applicant |
| US5960194(A) | 1999-09-01 | Choy et al. | Applicant |
| US5960404(A) | 1999-09-01 | Chaar et al. | Applicant |
| US5963957(A) | 1999-10-01 | Hoffberg | Applicant |
| US5964834(A) | 1999-10-01 | Crutcher | Examiner |
| US5966139(A) | 1999-10-01 | Anupam et al. | Applicant |
| US5966703(A) | 1999-10-01 | Burrows | Applicant |
| US5970464(A) | 1999-10-01 | Apte et al. | Applicant |
| US5974409(A) | 1999-10-01 | Sanu et al. | Applicant |
| US5974412(A) | 1999-10-01 | Hazlehurst et al. | Applicant |
| US5983218(A) | 1999-11-01 | Syeda-Mahmood | Applicant |
| US5987376(A) | 1999-11-01 | Olson et al. | Applicant |
| US5987454(A) | 1999-11-01 | Hobbs | Applicant |
| US5987464(A) | 1999-11-01 | Schneider | Applicant |
| US6003041(A) | 1999-12-01 | Wugofski | Applicant |
| US6005860(A) | 1999-12-01 | Anderson et al. | Applicant |
| US6006221(A) | 1999-12-01 | Liddy et al. | Applicant |
| US6006223(A) | 1999-12-01 | Agrawal et al. | Applicant |
| US6006225(A) | 1999-12-01 | Bowman et al. | Applicant |
| US6012096(A) | 2000-01-01 | Link et al. | Applicant |
| US6026409(A) | 2000-02-01 | Blumenthal | Applicant |
| US6029195(A) | 2000-02-01 | Herz | Applicant |
| US6032129(A) | 2000-02-01 | Greef et al. | Applicant |
| US6038560(A) | 2000-03-01 | Wical | Applicant |
| US6044374(A) | 2000-03-01 | Nesamoney et al. | Applicant |
| US6044376(A) | 2000-03-01 | Kurtzman, II | Applicant |
| US6052784(A) | 2000-04-01 | Day | Applicant |
| US6055513(A) | 2000-04-01 | Katz et al. | Applicant |
| US6055568(A) | 2000-04-01 | Adams | Applicant |
| US6064980(A) | 2000-05-01 | Jacobi et al. | Applicant |
| US6070158(A) | 2000-05-01 | Kirsch et al. | Examiner |
| US6076108(A) | 2000-06-01 | Courts et al. | Applicant |
| US6078892(A) | 2000-06-01 | Anderson et al. | Applicant |
| US6078913(A) | 2000-06-01 | Aoki et al. | Applicant |
| US6085223(A) | 2000-07-01 | Carino, Jr. et al. | Applicant |
| US6092074(A) | 2000-07-01 | Rodkin et al. | Applicant |
| US6094676(A) | 2000-07-01 | Gray et al. | Applicant |
| USRE36840(E) | 2000-08-01 | Mihalisin et al. | Applicant |
| US6128599(A) | 2000-10-01 | Walker et al. | Applicant |
| US6128647(A) | 2000-10-01 | Haury | Applicant |
| US6144944(A) | 2000-11-01 | Kurtzman, II et al. | Applicant |
| US6154739(A) | 2000-11-01 | Wrobel | Applicant |
| US6169988(B1) | 2001-01-01 | Asakura | Examiner |
| US6169989(B1) | 2001-01-01 | Eichstaedt et al. | Applicant |
| US6175829(B1) | 2001-01-01 | Li et al. | Applicant |
| US6182050(B1) | 2001-01-01 | Ballard | Applicant |
| US6189008(B1) | 2001-02-01 | Easty et al. | Applicant |
| US6192372(B1) | 2001-02-01 | Yamaura et al. | Applicant |
| US6212494(B1) | 2001-04-01 | Boguraev | Applicant |
| US6212527(B1) | 2001-04-01 | Gustman | Applicant |
| US6223575(B1) | 2001-05-01 | Agrawal et al. | Applicant |
| US6308172(B1) | 2001-10-01 | Agrawal et al. | Applicant |
| US6366907(B1) | 2002-04-01 | Fanning et al. | Examiner |
| US6397209(B1) | 2002-05-01 | Reed et al. | Examiner |
| JP9288608(A) | 1997-11-01 | Examiner | |
| WO9103024(A1) | 1991-03-01 | Examiner |
Non-Patent Literature (8)
- “Gnutella News—Gnutella News and Information,” Aug. 10, 2000, www.gnutella.com.Applicant
- “Gnotella Help Page,” Aug. 10, 2000, www.gnotella.nerdherd.net/help.html.Applicant
- SourceForge, “The Free Network Project Horn,” Aug. 10, 2000, www.freenet.sourceforge.net/.Applicant
- Bob Schmidt, “nguCache—Connecting the world,” Aug. 10, 2000, www.gnucache.backroomwarehouse.com/.Applicant
- Ian Clarke. et al. “A Distributed Decentralized Information Storage and Retrieval System”. Division of Informatics, XP-002177459, 1999, pp. 1-43.Applicant
- Brian Copperman, “Search and Destroy: iMesh Goes Hunting”, XP-002177453, Nov. 19, 1999, p. 1-2.Applicant
- “Technology Overview”, Mojo Nation, XP-002177454, Feb. 14, 2000, p. 1-5.Applicant
- “LimeWire is Free and Contains no SpyWare!”, XP-002177455, Sep. 14, 2001, p. 1-3.Applicant