Background of the Invention
The present invention generally pertains to data processing and is particularly directed to an improvement in governing the delivery of files from object data bases to a user terminal via a network interface.
In the prior art, an object data base includes objects in a format of information content components, context information pertaining to linkages between the information content components and processing instructions for manipulating the information content components and the context information in such a manner as to facilitate efficient retrieval of the information content components and the context information from the object data base. The context information (a) identifies the information content components that are linked, (b) defines the relationship between the linked content components, such as relationships analogous to parent, child, sibling, external or contained, (c) identifies the defined relationship, and (d) identifies the locations in the object data base of the content components having the defined relationship. Accordingly, objects may be organized in an object data base for retrieval in an abstract manner that resembles the way in which the information content components thereof are realized in the real world. An object data base is well suited for complex objects, such as bill-of-materials hierarchies and multimedia BLOBS (binary large objects).
Object data bases contained in prior art information servers may be accessed indirectly or directly by a user terminal through a communication network, such as the Internet or a private communication network, and a file-delivery-governing system that connects the information server to a network interface for the communication network. A prior art system for governing delivery of object files to a user terminal via a network interface from an object data base contained in an information server responds to receipt of a user-terminal request for delivery of a selected object file containing at least one selected information content component and the context information pertaining to the linkages of the selected information content component(s) by providing to the user terminal via the network interface a pointer to the selected object file that enables the user terminal to obtain delivery of the selected object file from the information server via the network interface.
Summary of the Invention
The present invention provides a system for governing delivery of files from object data bases, comprising first means containing at least one set of object data bases with each set including a first object data base containing information content components and a separate second object data base containing context information pertaining to linkages between the information content components of the first object data base of said set; second means for delivering a selected information content object file containing at least one selected information content component from the first object data base; and third means for delivering a selected context information object file containing context information pertaining to the linkages of a selected category of information content components from the second object data base.
More specifically, in a preferred embodiment, the first means comprises at least one remote information server containing at least one said set of object data bases; the third means comprise a plurality of broker/servers coupled to each remote information server, with each broker/server being adapted (a) for receiving delivery of the second object data base(s) of context information from the remote information server to which the broker/server is coupled, (b) for maintaining the delivered second object data base(s) of context information, and (c) for responding to receipt of a request for delivery of a selected context information object file containing context information pertaining to the linkages of a selected category of information content components by delivering the selected context information object file from a said second object data bases maintained in the broker/server; the second means comprises a plurality of sets of local information servers respectively coupled to the plurality of broker/servers and to the remote information server to which the respective broker/server is coupled, with the local information servers being respectively adapted (d) for receiving delivery of information content object files respectively containing at least one information content component from the first object data base(s) in the remote information server to which the local information server is coupled and (e) for caching the delivered information content object files; and said broker/servers, which are respectively adapted (f) for responding to receipt of a request for delivery of a selected information content object file containing at least one selected information content component by requesting a selected one of the local information servers that are coupled to the recipient broker/server to deliver the selected information content object file; and the local information servers are respectively adapted (g) for responding to said request from the recipient broker/server to deliver the selected information content object file by delivering the selected information content object file from the selected local information server.
The present invention further provides respectively the broker/server, the remote information server, the local information server and a delivery network including at least one broker/server and a set of local information servers included in the system of the present invention and methods related to use of the system of the present invention.
By separating storage and delivery of the context information object files from storage and delivery of the information content object files, the present invention facilitates agile accessibility to the selected context information files and the selected information content files respectively. For example, a relatively small selected context information object file can be readily retrieved and delivered to a user terminal for use in searching for selected information content components without having to also retrieve and/deliver the much larger portion of information content components that are related to the selected context information.
By individually governing the delivery of the context information object files and the information content object files from a remote information server to a specifiable user terminal through a plurality of delivery networks of broker/servers having sets of local information servers respectively coupled thereto, the present invention enables efficient delivery of these object files through delivery networks of relatively small computers such that the number and the respective sizes of the delivery networks may be adapted readily to meet the relative frequency of user requests for delivery of the selected object files.
By providing autonomous redundant capability for delivery of the context information object files and the information content object files from a remote information server through a plurality of delivery networks of broker/servers having sets of local information servers respectively coupled thereto, the present invention reduces the likelihood of an overall system failure.
Additional features of the present invention are described with reference to the detailed description of the preferred embodiments.
Brief Description of the Drawing
FIG. 1 is a block diagram of a preferred embodiment of a file-delivery-governing system according to the present invention.
FIG. 2 is a block diagram of a remote information server coupled to a communication network interface by a delivery network that includes a broker/server and a set of local information servers coupled to the broker/server, as included in a preferred embodiment of the system of FIG. 1.
FIG. 3 is a flow diagram for the delivery of a selected information content object file from the remote information server in a "pumped" mode of operation.
FIG. 4 is a flow diagram for the delivery of a selected information content object file from the remote information server in an "adaptive" mode of operation.
FIG. 5 is a flow diagram for the delivery of a selected information content object file from the remote information server in a "predictive" mode of operation.
FIG. 6 is a flow diagram for the delivery of selected information content object files from the remote information server in accordance with an established priority.
FIG. 7 is a flow diagram for regulating the caching of a selected information content object file within a set of local information servers.
Detailed Description
Referring to FIG. 1, a preferred embodiment of a file-delivery-governing system according to the present invention includes a plurality of remote information servers 10a, . . . , 10n and a plurality of delivery networks 12a, . . . , 12n coupled to each remote information server 10a, . . . , 10n. Each delivery network 12a, . . . , 12n includes at least one (preferably two or more) broker/servers 14 and a set 15 of local information servers 16a, . . . , 16n respectively coupled to each broker/server 14 and to the remote information server 10, . . . , 10n to which the broker/server(s) 14 is connected. A plurality of network interfaces 18 respectively couple the broker/server(s) 14 and the local information servers 16a, . . . , 16n of the respective delivery networks 12, . . . , 12n to any number of user terminals 20 via a communication network 22, such as the Internet or a private network.
The remote information servers 10a, . . . , 10n are interconnected for communicating object data bases from one another so that common sets of object data bases may be stored in a plurality of the remote information servers 10a, . . . , 10n. Preferably, most of the sets of object data bases stored in one remote information server 10a, . . . , 10n are stored in all of the remote information servers 10a, . . . , 10n, with only those sets of object data bases that are of only local interest being stored in only one of the remote information servers 10a, . . . , 10n. The use of a plurality of remote information servers 10a, . . . , 10n is based upon geographical and/or network topological disbursement considerations.
Referring to FIG. 2, each remote information server 10 is embodied in a separate computer and includes an object data base memory device 24, a separate second memory device 26 and a processor 28. Each object data base memory device 24 contains one or more sets 30a, . . . , 30n of object data bases, with each set 30 including a first object data base 31 containing information content components and a separate second object data base 32 containing context information pertaining to linkages between the information content components of the first object data base 31 of the same set 30 of object data bases. The size of the context information in a typical object data base is an order of magnitude less than the typical size of the related information content components, in that the combined context information usually requires a storage capacity in a range of 100 to 400 kilobytes and the related information content components usually require a combined storage capacity in a range of 1 to 75 megabytes.
The object data base memory device 24 is a random access memory device, such as a recording disk, rather than a sequential access memory device. The second memory device 26 is a non-volatile random access memory, such as a recording disk, for use in storing data other than the object data bases, such as data pertaining to the operation of the remote information server 10 for delivering files from the first object data bases 31 and the second object data bases 32. The processor 28 processes the data pertaining to such operation of the remote information server 10 and executes various routines pertaining to delivery of object files from the remote information server 10.
Each broker/server 14 is embodied in a multi-processor computer or in a plurality of computers and includes an object data base random access memory device 34, such as a recording disk, a separate second memory device 36 and a plurality of processors 38. The second memory device 36 is a non-volatile random access memory, such as a recording disk, for use in storing data other than object data bases, such as data pertaining to the operation of the broker/server 14 for controlling the delivery of selected information content object files to and from the local information servers 16a, . . . , 16n connected to the respective broker/server 14. The processors 38 process the data pertaining to such operation of the broker/server 10 and execute various routines pertaining to identification and delivery of context information object files from the broker/server 14 to the user terminal 20 via the network interface 18 and of delivery of selected information content object files to and from the local information servers 16a, . . . , 16n connected to the respective broker/server 14.
Each local information server 16a, . . . , 16n is embodied in a separate autonomous computer, such as an IBM-compatible personal computer or a dedicated single-board computer, and includes an object data base random access memory device 40, such a recording disk, a separate second memory device 42 and a processor 44. The second memory device 42 is a non-volatile random access memory, such as a recording disk, for use in storing data other than object data bases, such as data pertaining to the operation of the local information server 16a, . . . , 16n for controlling the delivery of information content object files to and from the local information server 16a, . . . , 16n. The processor 44 processes the data pertaining to such operation of the local information server 16a, . . . , 16n and executes various routines pertaining to delivery of selected information content object files to and from the local information server 16a, . . . , 16n.
The broker/server 14 receives delivery of the second object data bases 32 of context information from the object data base memory device 24 in the remote information server 10 to which the broker/server 14 is coupled. Such delivery occurs when the system is initialized; and the remote information server 10 causes such a delivery to recur from time to time after the second object data bases 32 of context information in the object data base memory device 24 in remote information server 10 are changed.
The broker/server 14 maintains the most recently delivered second object data bases 32 of context information in the object data base memory device 34. Maintaining the entirely of the relatively small second object data bases 32 of context information in each broker/server 14 from the object data base memory device 24 in the remote information server 10 makes such context information more readily accessible for searches for specific information content components. Such a search is accomplished at a user terminal 20 within a selected context information object file 46 containing context information pertaining to the linkages of a selected category of information content components after such a selected context information object file 46 has been delivered to the user terminal 20 via the network interface 18.
The broker/server 14 responds to receipt from a user terminal 20 via the network interface 18 of a request 48 for delivery to the user terminal 20 via the network interface 18 of a selected context information object file 46 by delivering the selected context information object file 46 to the user terminal 20 via the network interface 18 from the second object data bases 32 maintained in its object data base memory device 34. Upon delivering the selected context information object file 46 to the user terminal 20 via the network interface 18, the broker/server 14 also delivers therewith a browser software program that enables the user terminal 20 to display the context information from the selected context information object file 46.
Each of the local information servers 16a, . . . , 16n is respectively coupled to the remote information server 10 to which the broker/server 14 is coupled by a switched access connection (not shown) and is respectively adapted for receiving delivery of information content object files 50 respectively containing at least one information content component from the first object data bases 31 in the remote information server 10. Each of the local information servers 16a, . . . , 16n is also respectively adapted for caching the delivered information content object files 50 in its object data base memory device 40. Each of the local information servers 16a, . . . , 16n is capable of retaining a plurality of cached information content object files 50 in the object data base memory device 40.
Each local information server 16a, . . . , 16n maintains in its second memory 42 its own record of data 52 identifying the information content object files 50 then cached therein and data 54 indicating various characteristics of the information content object files 50 then cached therein, such as the general subject matter of the information content object files 50. Whenever, an information content object file 50 is cached in or deleted from the object data base memory device 40 of a local information server 16a, . . . , 16n, the respective local information server 16a, 16n . . . , updates the record of the file-identifying data 52 and the file-characteristic-indicating data 54 in its second memory 42 and provides the current file-identifying data 52 and the current file-characteristic-indicating data 54 to the broker/server 14 coupled thereto, and the broker/server 14 records the current file-identifying data 52 and the current file-characteristic-indicating data 54 in its second memory 36.
Referring to FIGS. 2 and 3, the broker/server 14 responds to receipt of a request 56 from the user terminal 20 for delivery of a selected information content object file 50 containing at least one selected information content component by executing a routine 60 of reviewing the file-identifying data 52 recorded in its second memory 36 to determine whether the requested selected information content object file 50 file has been cached in at least one of the local information servers 16a, . . . , 16n coupled to the broker/server 14, and if so, to identify the local information server(s) 16a, . . . , 16n in which the selected information content object file 50 is presently cached. When it is determined that the requested selected information content object file 50 file is presently cached in one of the local information servers 16a, . . . , 16n, the broker/server 14 sends a request 58 to a selected one of the local information servers 16a, . . . , 16n in which the selected information content object file 50 is presently cached to deliver the selected information content object file 50 to the user terminal 20 via the network interface 18. The request 58 to the local information server 16a, . . . , 16n also identifies a delivery channel of the network interface 18 over which the selected file is to be delivered by the selected local information server 16a, . . . , 16n to the user terminal 22.
When it is determined that the requested selected information content object file 50 file is not presently cached in one of the local information servers 16a, . . . , 16n, the broker/server 14 selects one of the local information servers 16a, . . . , 16n to receive the selected information content object file 50 from the remote information server 10 in accordance with a "pumped" mode of operation. For the pumped mode of operation, the broker/server 14 selects the local information server 16a, . . . , 16n to which the selected information content object file 50 is to be delivered in accordance with the file-characteristic-indicating data 54 recorded in its second memory 36 so as to cause information content object files 50 having a common characteristic to be cached in the same local information server 16a, . . . , 16n.
In accordance with the pumped mode of operation, the broker/server 14 sends a request 62 to the remote information server 10 to the which the broker/server 14 is coupled to deliver the selected information content object file 50 to the selected local information server 16a, . . . , 16n from one of the first object data bases 31 in the remote information server 10. Upon sending the request 62 to the remote information server 10, the broker/server 14 also sends the file delivery request 58 to the selected local information server 16a, . . . , 16n.
The local information server 16a, . . . , 16n that receives the file delivery request 58 responds thereto by delivering the selected information content object file 50 from the object data base memory device 40 of the local information server 16a, . . . , 16n to the user terminal 20 via the identified channel of the network interface 18.
Upon determining that the requested selected information content object file 50 file is presently cached in one of the local information servers 16a, . . . , 16n, the broker/server 14 sends to the user terminal 20 via the network interface 18 a message 70 informing, the user terminal 20 of the impending delivery of the requested selected information content object file 50 together with a short-term security file receipt token for validating the selected local information server 16a, . . . , 16n as the server of the object file 50 to be delivered. If the delivered selected information content object file 50 is encrypted, the message 70 also includes a transmittal security token, such as an encryption key, for use in decrypting the encrypted file. Upon sending the delivery request 62 to the remote information server 10 and the message 70 to the user terminal 20 via the network interface 18, the broker/server 10, the broker/server 14 records data indicating that the selected information content object file 50 has been delivered to an identified user terminal 20; and from time to time the broker/server 14 transmits such data to one or more other terminals (not shown), where such data is further recorded and processed for the purposes of demographic data compilation and/or of billing for delivery of the selected information content object file 50 to the identified user terminal 20.
Selected information content object files 50 are also delivered from the remote information server 10 to the local information servers 16a, . . . , 16n in accordance with an "adaptive" mode of operation, which is described with reference to FIGS. 2 and 4. The broker/server 14 provides to the remote information server 10 data 72 indicating when messages pertaining to each selected information content object file 50, such as the delivery requests 48, 56 and other inquires, are received by the broker/server 14; and the remote information server 10 executes a routine 74 of recording the provided when-received-indication data 72 in its second memory 26. Periodically, the remote information server 10 executes a routine 76 of processing the provided when-received-indication data 72 to determine whether there is a pattern in which messages 48, 56 pertaining to any of the selected information content object files 50 are received by the broker/server 14. When it is determined upon periodic re-execution of the routine 76 of processing the when-received-indication data 72 that the previously determined pattern is no longer valid, the pattern may be modified by such re-execution of the data processing routine 76. When it is determined upon such periodic re-execution of the data processing routine 76 that there no longer is a valid pattern in which messages 48, 56 pertaining to a given selected information content object file 50 are received by the broker/server 14, the given selected information content object file 50 is no longer delivered from the remote information server 10 to a selected local information server 16a, . . . , 16n in accordance with the adaptive mode.
When it is determined that there is such a request pattern for a given selected information content object file 50, the remote information server 10 executes a routine 78 of scheduling the delivery of the given selected information content object file 50 to a selected local information server 16a, . . . , 16n so that the given selected information content object file 50 is delivered to the selected local information server 16a, . . . , 16n before such time as it is anticipated that a request for delivery of the given information content object file 50 to the user terminal 20 via the network interface 18 will be received in accordance with such determined pattern. Subsequently, the remote information server 10 executes a routine 80 of delivering the given selected information content object file 50 to the selected local information server 16a, . . . , 16n from one of the first object data bases 31 in the remote information server 10 in accordance with such schedule.
Selected information content object files 50 are also delivered from the remote information server 10 to the local information servers 16a, . . . , 16n in accordance with a "predictive" mode of operation, which is described with reference to FIGS. 2 and 5. When it is known that a request 56 for delivery a given selected information content object file 50 will be received at a given time, the remote information server 10 is programmed to execute a routine 82 of scheduling delivery of the given selected information content object file 50 to a selected local information server 16a, . . . , 16n at a predetermined time prior to the given time; and the remote information server 10 subsequently executes a routine 84 of delivering the given selected information content object file 50 to the selected local information server 16a, . . . , 16n from one of the first object data bases 31 in the remote information server 10 in accordance with such schedule.
The file-delivery-governing system of the present invention thus has the versatile capability of being able to deliver selected information content object files 50 to the local information servers 16a, . . . , 16n from the remote information server 10 pursuant to (a) the pumped mode, wherein a first selected information content file 50 is delivered from the remote information server 10 to a selected local information server 16a, . . . , 16n in response to receipt of a request 56 for delivery to the user terminal 20 via the network interface 18 of a selected information content file 50 when the selected information content file 50 is not presently cached in any of the local information servers 16a, . . . , 16n, (b) the adaptive mode, wherein a second selected information content file 50 is delivered from the remote information server 10 to a selected local information server 16a, . . . , 16n in accordance with a schedule determined by processing data 72 indicating when messages 48, 56 pertaining to the second selected information content file 50 are received; and (c) the predictive mode, wherein a third selected information content file 50 is delivered from the remote information server 10 to a selected local information server 16a, . . . , 16n at a predetermined time. The terms "first", "second" and "third" do not indicate sequence. The pumped, adaptive and predictive modes of operation are independent of one another and may overlap and/or be competitive with one another.
Referring to FIGS. 2 and 6, the broker/server 14 executes a routine 86 of processing the received information-content-object-file-delivery requests 56 to establish a priority classification for the delivery of the requested information content object files 50. Such classification is based in part upon delivery parameters included within the delivery request 56 received from the user terminal 20. The broker/server 14 executes a routine 88 of providing to the selected local information server 16a, . . . , 16n. Data indicating the priority classification established for delivery of a selected information content object file 50 to a selected local information server 16a, . . . , 16n pursuant to the file delivery request 58. The priority classification data is provided to the selected local information server 16a, . . . , 16n as a part of the file delivery request 58. The local information server 16a, . . . , 16n executes a routine 90 of delivering the selected information content object file 50 to the network interface 18 in accordance with the established priority classification data.
Referring to FIGS. 2 and 7, the local information servers 16a, . . . , 16n of at least one set 15 of local information servers respectively execute a routine 92 of recording internally provided data indicating when the respective local information server 16a, . . . , 16n is requested to deliver each selected information content object file 50 to the user terminal 20 via the network interface. A respective local information server 16a periodically executes a routine 93 of processing the recorded file-delivery-request-indication data to determine the frequency at which the respective local information server 16a is requested to deliver the selected information content object file 50 to the user terminal 20 via the network interface 18.
When it is determined that the frequency at which the respective local information server 16a is requested to deliver a given selected information content object file 50 to the user terminal 20 via the network interface 18 is greater than a first given frequency, the local information server executes a routine 94 of asynchronously broadcasting to the other local information servers 16a, . . . , 16n of the same set 15 of local information servers 16a, . . . , 16n a request 95 that any of the other local information servers . . . , 16n also cache the given selected information content object file 50. The asynchronous mode of communication only minimally loads the local information servers 16a, . . . , 16n inasmuch as no acknowledgment is required to the asynchronous broadcast.
When another local information server 16n receiving the request 95 is not then busy and has the capacity to cache the given selected information content object file 50, the other local information server 16n responds to the cache request 95 by executing a routine 96 of providing to the remote information server 10 a further request 97 that the remote information server 10 deliver the given selected information content object file 50 to the other local information server 16n. The remote information server 10 responds to the further request 97 by executing a routine 98 of delivering the given selected information content object file 50 to the other local information server 16n.
By caching selected information content object files 50 in more than one local information server 16a, . . . , 16n of a set 15 of information servers in accordance with the frequency at which given local information servers 16a, . . . , 16n are requested to deliver respective selected information content object files 50 to one or more user terminals 20 via the network interface 18, the file-delivery-governing system of the present invention is able to dynamically adjust its capacity for making the respective selected information content object files 50 readily available for access in accordance with user demand.
Still referring to FIG. 7, when it is determined pursuant to the execution of the above-described processing routine 93 that the frequency at which the respective local information server 16a, . . . , 16n is requested to deliver a given selected information content object file 50 to the user terminal 20 via the network interface 18 is less than a second given frequency, the local information server 16a, . . . , 16n executes a routine 99 of deleting the given selected information content object file 50 from the local information server 16a, . . . , 16n.
Each local information server 16a, . . . , 16n is further adapted for deleting information content object files 50 from its object data base memory device 40 in accordance with other internally stored criteria in order to achieve a capacity for caching new selected information content object files 50 delivered thereto, such as by deleting such files 50 in accordance with a first-in-first-out criteria. The local information server 16a, . . . , 16n also deletes selected information content object files 50 from its object data base memory device 40 pursuant to directives embedded in the respective selected information content object files 50 that are delivered to the local information server 16a, . . . , 16n.
In various alternative embodiments (not shown), (a) records of the file-identifying data 52 and the file-characteristic-indicating data 54 for each of the respective local information servers 16a, . . . , 16n is provided by and stored in the remote information server 10, with updated data 52, 54 being provided whenever the remote information server 10 sends a selected information content object file 50 to a respective selected local information server 16a, . . . , 16n ; (b) selection of a given local information server 16a, . . . , 16n for receipt of a selected information content object file 50 delivered from the remote information server is made by the remote information server 10 in accordance with file-characteristic-indicating-data 54 stored in the remote information server 10; (c) delivery by the remote information server 10 of the selected information content object files 50 to the local information servers 16a, . . . , 16n is scheduled by the broker/server 14; and/or (e) the broker/server 14 monitors the frequency of the requests 58 to each local information server 16a, . . . , 16n to deliver each selected information content object file 50 and causes a given selected information content object files 50 to be cached in a second local information server 16a, . . . , 16n when the frequency of such requests is greater than a given frequency.
The file-delivery-governing system of the present invention is well suited for simultaneously delivering a large number of relatively large (greater than one Megabyte) information content object files to various user terminals in a high bandwidth environment in a manner that is transparent to a user of the system.
The advantages specifically stated herein do not necessarily apply to every conceivable embodiment of the present invention. Further, such stated advantages of the present invention are only examples and should not be construed as the only advantages of the present invention.
While the above description contains many specificities, these should not be construed as limitations on the scope of the present invention, but rather as examples of the preferred embodiments described herein. Other variations are possible and the scope of the present invention should be determined not by the embodiments described herein but rather by the claims and their legal equivalents.