BACKGROUND OF THE INVENTION 
     1. Field of the Invention 
     The present invention relates to a new inverted index storage structure for dynamic document databases that can maintain document identifier (docID) order in the posting list upon frequent insertion, deletion, and modification of documents and that enables fast search for the posting of a specific document from a long posting list. 
     The invented storage structure uses large objects and subindexes. A large object stores a database object whose size exceeds one disk page and dynamically adjusts the storage space upon insertion and deletion. A large object typically employs a tree structure for dynamic allocation of space. We store each posting list in a large object and create a subindex on each posting list. A large object manages variable storage space of its posting list upon document addition and deletion. A subindex having docID as the key is used for docID-order preservation of a posting list upon document addition and for removal of a posting from a posting list upon document deletion. 
     2. Description of the Prior Art 
     A document can have several attributes such as the document number, modification date, authors, abstract, and body. Some of these attributes have a structured data type such as integer and character string, while others have an unstructured data type such as text, image, audio, and video. Document retrieval based on the attributes of the text data type is traditionally well performed by an information retrieval system, while document retrieval based on the attributes of structured data types by a database management system. Thus, for document retrieval based on the attributes of both text and structured data types, tight coupling of the database management system and information retrieval is necessary. In addition, the database management system can provide consistent management of documents and their indexes upon document addition, deletion, and modification. 
     Inverted index is an index used for information retrieval, which retrieves documents containing keywords given by a user. Inverted index keeps a list of postings for each keyword extracted from documents. A posting of a keyword consists of a document identifier (docID) and a list of locations in the document where the keyword occurs[Frakes, W. B. and Baeza-Yates, R.,  Information Retrieval—Data Structures  &amp;  Algorithms , Prentice Hall, Englewood Cliffs, N.J., 1992.; Salton G.,  Automatic Text Processing—The Transformation, Analysis,  and  Retrieval of Information by Computer , Addison-Wesley Press, 1988.]. The number of postings of a keyword, i.e., the number of documents containing the keyword, is called the document frequency, and the number of occurrences of a keyword in a document is called the term frequency. The document frequency indicates the length of the posting list of a keyword, and the term frequency the length of a posting. Information retrieval using inverted index is done by retrieving the posting list of the keyword given by a user. Thus, inverted index needs a storage structure to find the posting list of a keyword fast. 
     The storage space for the posting list increases when new postings of an added document are inserted into the posting list, while it decreases when old postings of a deleted document are removed from the posting list. Document modification also affects the length of the posting list because the old document is deleted and the modified document is added. Thus, inverted index needs a storage structure for managing variable storage space of the posting list efficiently. 
     If posting lists are kept in the order of docIDs, the boolean expression containing more than one keyword can be efficiently processed by sequentially scanning and merging the posting lists of the keywords only once. The query “find the documents about multimedia and database,” for example, contains two keywords of “multimedia” and “database,” and is processed by sequentially scanning and merging the posting lists of “multimedia” and “database.” 
     In document databases where document addition or modification is frequent, inverted index is dynamically updated on adding or modifying documents. On updating the inverted index, new postings of the added document should be inserted into the posting list in the order of docIDs. Thus, inverted index needs a storage structure to insert new postings efficiently into the posting list in the order of docIDs. 
     Document deletion is frequent because modifying a document requires deleting the old document before adding the modified document. If a document is deleted from a document database, all the postings of the deleted document should also be removed from the inverted index. Thus, the inverted index needs the following two storage structures: one for finding all the posting lists where the postings of the deleted document are included; the other for searching the posting list to find the posting of the deleted document. Because many keywords having long posting lists are contained in most documents, searching a long posting list or a specific posting is an important part of the performance in document deletion. 
     The simplest method for storing an inverted index is to store a table of records consisting of a keyword and a posting in a database. This method, however, is known to have low query performance and to require excessive storage space due to redundancy of keywords [Stonebraker, M., “Document Processing in a Relational Database System,”  ACM Trans. on Office Information Systems,  Vol. 1, No. 1, pp. 143-158, 1983; DeFazio, S., Daoud, A., Smith, L. A., and Srinivasan, J., “Integrating IR and RDBMS Using Cooperative Indexing,”  In Proc. Int&#39;l Conf. on Information Retrieval,  ACM SIGIR, pp. 84-92, Seattle, 1995.]. 
     Therefore, a lot of studies have been done on the method using tree structures instead of database tables for storing inverted indexes. FIG. 1 shows such a conventional inverted index storage structure. The reference numeral  10  shows a B+-tree having the keywords as the key. A pointer to a posting list is stored at the pointer field of the index entry in the leaf node of the tree. The reference numeral  11  shows the storage space for the posting list. Samuel DeFazio et al. [DeFazio, S., Daoud, A., Smith, L. A., and Srinivasan, J., “Integrating IR and RDBMS Using Cooperative Indexing,” In  Proc. Int&#39;l Conf. on Information Retrieval,  ACM SIGIR, pp. 84-92, Seattle, 1995.] argued through experiments that this storage structure out performs the database table method in query performance and storage space. Doug Cutting [Cutting, D. and Pedersen, J., “Optimizations for Dynamic Inverted Index Maintenance,” In  Proc. Int&#39;l Conf. on Information Retrieval,  ACM SIGIR, pp. 405-411, Brussels, 1990.], Christos Faloutsos [Faloutsos, C. and Jagadish, H. V., “On B-tree Indices for Skewed Distribution,” In  Proc. Int&#39;l Conf. on Very Large Data Bases,  pp. 363-374, Vancouver, 1992.], and Anthony Tomasic [Tomasic, A., Garcia-Molina, H., and Shoens, K., “Incremental Updates of Inverted Lists for Text Document Retrieval,” In  Proc. Int&#39;l Conf. on Management of Data,  ACM SIGMOD, pp. 289-300, Minneapolis, 1994.] studied the problem of storage space allocation for the reference numeral  11  when the posting list continuously increases due to document addition. 
     The conventional storage structures for the inverted index, however, have the following drawbacks: 1) They do not consider maintaining the docID-order in the posting list when inserting a new posting into the posting list upon document addition. Thus, boolean expressions involving more than one keyword are not evaluated efficiently. 2) They consider only adding but not removing the postings from the posting lists. Thus, document deletion is not properly handled. 3) They do not provide fast access to the posting for a specific document in a posting list. They simply assume sequential search, which requires reading half of the posting list on the average. 
     SUMMARY OF THE INVENTION 
     The inverted index is an index used for information retrieval (IR), i.e., for retrieving documents containing the keywords given by the user. The inverted index maintains a list of postings for each keyword extracted from the documents. Insertion, deletion, and modification of documents entail dynamic update of the inverted index. Thus, the inverted index needs a storage structure for effectively managing the posting lists, which is of variable size and is potentially long. We also need an inverted index structure to support integrated database and information retrieval queries by processing the IR part of the query using the result of the database part of the query and vice versa in a database management system (DBMS) tightly coupled with information retrieval. In this patent, we solve these problems by inventing an inverted index structure using the subindex and the large object management scheme. 
     First, we store a long posting list in a large object and manage storage space using the large object management scheme. Thus, when a new posting is inserted in a long posting list or when an existing posting is deleted, there is no physical movement of other postings, which results in effective extension and shrinkage of the long posting list and thus in enhanced update performance. 
     Second, we construct the subindex on document identifiers (docID) for long posting lists. The subindex is used for finding fast the locations of postings that have a given docID in a long posting list. Thus, we can enhance the performance when storing new postings into the posting list in the order of docID&#39;s, or when deleting postings of the deleted documents from the posting list. The performance of inserting and deleting postings in/from a long posting list is of importance since most documents contain keywords having long posting lists. Moreover, if postings are stored in a posting list in the order of docID&#39;s, Boolean queries consisting of more than one keyword can be efficiently processed. Last, we store the database object ID together with docID in each posting. An object ID points to the database object that has attribute data of the document. Then, integrated processing is possible of the IR part of the query and of the database part of the query using the docId and the object ID. That is, when we process the IR part of the query first, we can process the database part of the query by accessing the desired database object through the object ID stored in the posting. Likewise, when we process the database part of the query first, we can process the IR part of the query by looking for the desired posting through the subindex—using the docID stored in the database object—in the posting list of the given keyword. The IR part of the query in the latter checks whether a designated document (with docID) has the given keyword. 
    
    
     BRIEF DESCRIPTION OF THE DRAWINGS 
     The above and other objects, features and advantages of the present invention will be more clearly understood from the following detailed description taken in conjunction with the accompanying drawings, in which: 
     FIG. 1 is a diagram of the conventional inverted index storage structure; 
     FIG. 2 is the overall structure of the new storage structure of inverted index; 
     FIG. 3 is the detailed structure of the subindex illustrating the offset array technique; 
     FIG. 4 is the algorithm for inserting a new posting into a posting list on adding a new document; 
     FIG. 5 is the algorithm for removing a posting from a posting list on deleting a document; 
     FIG. 6 is the algorithm for retrieving a posting or a posting list for information retrieval; and 
     FIG. 7 is the method of tightly coupling information retrieval with a database management system. 
    
    
     DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS 
     The objects, characteristics and advantages of the present invention will be more clearly understood through the preferable embodiments referring to the attached drawings. 
     Since the terms mentioned later are judged based upon the function of the present invention and they can be changed according to the technician&#39;s intention or a usual practice, the terms should be judged considering the overall contents of the specification of the present invention. 
     First, the technical principle of the present invention will be briefly described. Electronic documents must be consistently managed under environments where the dynamic addition, deletion and modification thereof are frequently made. This requires database management system functions such as concurrent control, damage recovery, etc. 
     The retrieval of a document is classified into the retrieval of structured data and the retrieval of unstructured data, i.e., the structured data retrieval is well supported by a database management system, and the text data retrieval is well supported by an information retrieval system. As a result, for the consistent management and integrated retrieval of documents, it is necessary to tightly couple information retrieval with a database management system. 
     In a tightly coupled system, an inverted index structure must be able to be efficiently updated when documents are dynamically added to, deleted from and modified in a database. Further, an information retrieval based on the inverted index structure and a database retrieval of structured data must be able to be processed by in an integrated manner. 
     FIG. 2 shows an overall picture of the new inverted index storage structure. The reference numeral  20  is a B+-tree index having keyword as the key. It is used for retrieving the large object  21  that stores the posting list of a given keyword. A large object is a database object whose size exceeds one disk page. An object containing full text, image, audio, or video typically becomes a large object. We store each posting list as a large object and manage the storage space of the posting list using the large object management technique. The advantage of this method is the small number of disk page movement needed to insert a new posting into the posting list or to remove a posting from the posting list. Biliris [Biliris, A., “The Performance of Three Database Storage Structures for Managing Large Objects,” In  Proc. Int&#39;l Conf. on Management of Data,  ACM SIGMOD, pp. 276-285, New York, 1992.] shows in his paper that the large object management technique of the EXODUS storage system [Carey, M. et al., “Object and File Management in the EXODUS Extensible Database System,” In  Proc. Intl. Conf. on Very Large Data Bases,  pp. 91-106, Kyoto, Japan, August 1986.] can handle the size variation of large objects most efficiently. We adopted the techniques of the EXODUS system, but we can adopt any other techniques developed for large object management. 
     The reference numeral  22  in FIG. 2 is the subindex created on each large object that stores a posting list. The subindex is used for maintaining the docID-order in the posting list, and for locating a specific posting with a given docID within a posting list. Using subindexes, a new posting is quickly inserted into the posting list in the order of docIDs upon document addition, and an existing posting is quickly deleted from the posting list upon document deletion. Thus, the subindex enhances the performance of document addition or deletion. In practice, however, the subindex is not always created. It is created only for those posting lists exceeding certain size to avoid additional storage overhead of the subindex. 
     FIG. 3 shows the detailed storage structure of a subindex. A subindex has docID as the primary key and each leaf entry points to each posting of the posting list stored in a large object. If a leaf entry points directly to a posting, when a posting is inserted into or deleted from the middle of a large object, to keep the posting list in the order of docID, the locations of all the postings located after the affected posting must be changed. In this case, the update cost of the subindex can be high because a posting&#39;s insertion or deletion requires update of all the pointers of the subindex to the postings located after the posting inserted or deleted. We use a technique of the offset array to solve this problem. In FIG. 3, the offset array is positioned at the head of each posting list. Each element of the array contains the offset of its posting. The offset of a posting is the byte offset from the end of the offset array to the start of the posting and is not affected by the size of the offset array. When a posting&#39;s location is changed, only the corresponding element of the offset array is updated, but the subindex is not affected because it now points to the offset array&#39;s element that knows the actual location of the posting. 
     FIG. 4 shows the algorithm of inserting a new posting of an added document into the posting list. In step  100 , we check the offset array to see if there is a free element for the new posting. If there is no such element, we expand the size of the offset array in step  110 . Otherwise, we allocate a free element in step  120 . In step  130 , we compare the docID of the new posting with the docIDs of existing postings. If the former is larger, we append the new posting at the end of the posting list in step  140 . Otherwise, we insert the new posting into posting list at the location determined by traversing the subindex in step  150 . The insertion changes the locations of all the postings stored after the inserted posting, but there are no physical movements of postings owing to the large object management technique [Biliris, A., “The Performance of Three Database Storage Structures for Managing Large Objects,” In  Proc. Int&#39;l Conf. on Management of Data,  ACM SIGMOD, pp. 276-285, New York, 1992.]. In step  160 , the location of the posting is written in the offset array element allocated in step  120 , and all the elements of the offset array affected by the insertion are updated. Finally, in step  170 , the subindex is updated to point to the offset array element of the new posting. 
     FIG. 5 shows the algorithm of removing a posting of a deleted document from the posting list. In step  200 , we traverse the subindex to find the location of the deleted document&#39;s posting. In step  210 , we remove the posting found from the posting list. The removal changes the locations of all the postings stored after the removed posting, but there are no physical movements of postings due to the large object management technique [Biliris, A., “The Performance of Three Database Storage Structures for Managing Large Objects,” In  Proc. Int&#39;l Conf. on Management of Data,  ACM SIGMOD, pp. 276-285, New York, 1992.]. In step  220 , the offset array element corresponding to the deleted posting is removed and freed, and all the elements of the offset array affected by the removal are updated. Finally, in step  230 , the subindex is updated to delete the pointer to the offset array element deleted. The offset array element freed is managed by a free list and reused later. 
     FIG. 6 shows the algorithm of retrieving a posting or a posting list for information retrieval. In step  300 , we traverse the keyword index to find the large object containing the posting list of the keyword. If a specific docID is not given in step  310 , the large object is sequentially read to return all the postings of the given keyword in step  320 . If a specific docID is given in step  310 , we traverse the subindex to locate that specific docID&#39;s postings in step  330 , and return the postings found in step  340 . 
     FIG. 7 shows the method of processing the integrated database and information retrieval queries using the logical document identifier (called docID) and the database object identifier(OID) . The docID is used for ordering postings in the posting list, and the OID managed by the DBMS is the identifier of the database object containing the document&#39;s attributes. We hold both a docID and an OID in each posting. We illustrate the process using an example. In FIG. 7, there are two postings, posting- 1  (the reference numeral  410 ) and posting- 2  (the reference numeral  420 ), and two database objects, obj- 1  (the reference numeral  440 ) and obj- 2  (the reference numeral  450 ). The reference numeral  400  shows the structure of postings, and the reference numeral  430  shows the schema of database objects having the document&#39;s attribute data. Posting- 1  is the posting for the document obj- 1 ., and posting- 2  is the posting for the document obj- 2 . Posting- 1  and posting- 2  contain the OID&#39;s of obj- 1  and obj- 2 , respectively. Obj- 1  and obj- 2  contain the docID&#39;s of posting- 1  and posting- 2 , respectively. If we get a posting after processing the information retrieval part of the query, we can process the database part of the query by accessing the database objects directly with the OID contained in the posting. If we get a database object after processing the database part of the query, we can process the information retrieval part of the query by retrieving the posting with the docID contained in the database object. The posting is retrieved by searching the subindex defined on the posting list of the specified keyword using the docID as the key. As a result, we can process the integrated query. 
     As apparent from the above description, the present invention provides the inverted index storage structure using the subindexes and large objects, which can obtain the following advantages. 
     First, we can support efficient update of the posting list upon document addition, deletion, and modification. We treat each posting list as a large object and manage the storage space by the large object management techniques to efficiently handle the size variation of the posting list when updating an inverted index. Although a posting is inserted into or removed from the middle of a posting list, the postings located after that posting need not be physically moved owing to the large object management scheme. In conventional inverted index structures, postings move due to storage space expansion upon document addition. Shrinkage upon document deletion has not been considered in these structures. 
     Second, we can enhance the performance of updating the inverted index upon document addition, deletion, and modification. Using the subindex, we can efficiently maintain the docID-order in the posting list by quickly locating the slot in the posting list for the posting of the added document. Similarly, we can quickly locate the posting of the deleted document in the posting list using the subindex. As most documents contain keywords with a long posting list, quick addition and removal of postings in a long posting list is important for the performance of updating the inverted index. 
     Third, we can enhance performance of checking whether a specific document contains a specific keyword. This is done by checking through the subindex the existence of the docID of the document in the posting list of the keyword. Fourth, by maintaining the docID order in the posting list, we can efficiently process arbitrary boolean expressions containing more than one keyword. This is done by sequentially scanning and merging the posting lists of the keywords only once. 
     Fifth, we can process the integrated query of database retrieval and information retrieval in a tightly coupled manner as descibed above. Conventional inverted index dealt with only information retrieval, but did not address the problem of processing integrated queries of database retrieval and information retrieval. 
     Although the preferred embodiments of the present invention have been disclosed for illustrative purposes, those skilled in the art will appreciate that various modifications, additions and substitutions are possible, without departing from the scope and spirit of the invention as disclosed in the accompanying claims.
This invention relates to an inverted index storage structure that indexes keyword inputs into the storage space for the corresponding posting lists. In particular, the invention relates to the index structure that enables fast retrieval of the posting of the specific document from the posting list and enables efficient arrangement and maintenance of the posting list in document identifier (docID) order, so that fast addition, deletion, modification, and retrieval of documents are possible in environments where a database management system is tightly coupled with information retrieval. The technical solution is to store the posting list in a large object and map to each posting list a subindex that indexes the docID into the postings containing the docID.