EP1091295B1 - Système de gestion de données avec plusieurs modules d'exploitation de données - Google Patents

Système de gestion de données avec plusieurs modules d'exploitation de données Download PDF

Info

Publication number
EP1091295B1
EP1091295B1 EP00308108A EP00308108A EP1091295B1 EP 1091295 B1 EP1091295 B1 EP 1091295B1 EP 00308108 A EP00308108 A EP 00308108A EP 00308108 A EP00308108 A EP 00308108A EP 1091295 B1 EP1091295 B1 EP 1091295B1
Authority
EP
European Patent Office
Prior art keywords
data
module
operation modules
application program
operations
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Expired - Lifetime
Application number
EP00308108A
Other languages
German (de)
English (en)
Other versions
EP1091295A2 (fr
EP1091295A3 (fr
Inventor
Kanai Tatsunori
Kizu Toshiki
Maeda Seiji
Yao Hiroshi
Torii Osamu
Yano Hirokuni
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Toshiba Corp
Original Assignee
Toshiba Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Toshiba Corp filed Critical Toshiba Corp
Publication of EP1091295A2 publication Critical patent/EP1091295A2/fr
Publication of EP1091295A3 publication Critical patent/EP1091295A3/fr
Application granted granted Critical
Publication of EP1091295B1 publication Critical patent/EP1091295B1/fr
Anticipated expiration legal-status Critical
Expired - Lifetime legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F17/00—Digital computing or data processing equipment or methods, specially adapted for specific functions
    • G06F17/40—Data acquisition and logging
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
    • G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
    • G06F9/5055—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals considering software capabilities, i.e. software resources associated or available to the machine
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
    • G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2209/00—Indexing scheme relating to G06F9/00
    • G06F2209/50—Indexing scheme relating to G06F9/50
    • G06F2209/5018—Thread allocation
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00—Data processing: database and file management or data structures
    • Y10S707/99941—Database schema or data structure
    • Y10S707/99944—Object-oriented database structure
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00—Data processing: database and file management or data structures
    • Y10S707/99941—Database schema or data structure
    • Y10S707/99944—Object-oriented database structure
    • Y10S707/99945—Object-oriented database structure processing
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00—Data processing: database and file management or data structures
    • Y10S707/99941—Database schema or data structure
    • Y10S707/99948—Application of database or data structure, e.g. distributed, multimedia, or image

Definitions

  • the present invention relates to a data management system and a data management method for providing data management and operation functions in a computer.
  • Data to be handled in a computer are usually managed by using a file system or a database management system.
  • the file system manages very basic data called byte sequences by attaching names to them.
  • the data of the byte sequences managed by the file systems are called files.
  • the application program can carry out basic operations for writing new data into files or reading already written data from files.
  • the file system provides a data model called byte sequences which are both basic and flexible.
  • the byte sequences is a data model that is conceptually at very low level, so that it is necessary for the application program to define and use data management structure and operations unique to that application program on the byte sequences in order to use this data model for solving various problems actually encountered in the computer. For this reason, the data independency is low and it is difficult to share data among a plurality of application programs.
  • the database management system provides more sophisticated functions specific to a specific data model by presupposing the use of the specific data model.
  • the most widely used database management system is the relational database management system based on the relational data model.
  • the relational database management system manages all data by expressing them on tables, and provides functions for searching data stored in the table by specifying a key, or searching related data in a plurality of tables using an operation called JOIN.
  • the application program can carry out the processing using various operation functions provided by the relational database management system if the necessary data can be defined in forms of tables.
  • There are also database management systems using data models other than the relational data model such as the network data model and the object data model.
  • the data management and operation are separated from the application program and carried out at the database management system side. Namely, the independency of data can be realized so that it becomes easier to utilize one data by sharing it among a plurality of application programs.
  • the database management system provides functions such as the management of consistency required for the transaction processing, the exclusive control in the case of processing by sharing data among a plurality of application programs, and the recovery processing at a time of a fault occurrence.
  • the database management system provides various management and operation functions by specifying the specific data model which is conceptually at high level, so that the data independency is high and it is easy to share data among a plurality of application programs.
  • an application program that matches with the data model provided by the database management system can be designed easily and a high performance can be achieved easily, an application program that does not match the data model is difficult to design and it is hard to achieve a high performance. From a viewpoint of the flexibility of data, the available degrees of freedom are limited compared with the file system, and the expandability of the management and operation functions for new data or data model is also poor.
  • US 5 727 158 relates to an information processing system particularly for storing and facilitating the retrieval of large amounts of data by a variety of computing tools.
  • a data management system for applying operations on data outputted from a data storage system and providing data to a processing of an application program, the data management system comprising:
  • a data management method in a data management system for applying operations on data outputted from a data storage system and providing data to a processing of an application program, the data management method comprising the steps of:
  • a computer usable medium having computer readable program codes embodied therein for causing a computer to function as a data management system for applying operations on data outputted from a data storage system and providing data to a processing of an application program
  • the computer readable program codes include:
  • Fig. 1 to Fig. 30 one embodiment of a data management system according to the present invention will be described in detail.
  • WebDAV For such a data management method, it is possible to use WebDAV, but the present invention is not limited to that case.
  • the specification of WebDAV is disclosed in "HTTP Extensions for Distributed Authoring -- WEBDAV” (RFC 2518).
  • a hierarchical structure of names is managed by directories.
  • the directory can have arbitrary number of other directories and data at its lower hierarchical levels.
  • three data “data1", “data2” and “data3” and three directories “dir1", "dir2” and “dir3” are shown, where three data are managed by names such as "/dir1/dir2/data1", “/dir1/dir2/data2” and "/dir1/dir3/data3”.
  • data and directories are referred to as resources, and directories are also referred to as collections.
  • the data managed by the data management system of this embodiment can be any of binary data as in the file system, structured data such as XML documents, and database-like data to be accessed by specifying a value of a key. Besides these it is also possible to manage data based on various extended data models. Details of XML are disclosed in "Extensible Markup Language (XML) 1.0" (World Wide Web Consortium).
  • each directory (201) or data (202) has a property (203) which is a set of a pair formed by an attribute name and an attribute value.
  • the property is used for recording various information such as its directory, a file creation date, access rights, an owner, etc.
  • the directories and properties are also managed as data.
  • the data management structure in the example of Fig. 1 can be viewed as shown in Fig. 2 from a viewpoint of the implementation, where data that are entities of the directories (302 and 304, for example) have information indicating properties of their children directories or data (303 and 307, for example), and data of properties (303 and 307, for example) have information indicating entities of the corresponding directories or data (304 and 308, for example).
  • data that are entities of the directories (302 and 304, for example) have information indicating properties of their children directories or data (303 and 307, for example)
  • data of properties 303 and 307, for example
  • the data model expressing directories and the data model expressing properties are provided.
  • Fig. 3 shows a general exemplary configuration of the data management system according to this embodiment.
  • the file system 3 manages files in the stable memory devices such as hard disks 31, for example.
  • the stable memory device is a memory device such as hard disk, for example, in which the stored content will not disappear even when the power is turned off.
  • the data management system 1 carries out file operations for managing the file system 3 upon receiving requests from the application programs 2.
  • the data model conversion conversion from the binary data recorded in the file to XML, for example
  • the operation functions in some data model are provided with respect to the application programs 2.
  • rectangles depicted inside each dashed line enclosure represent the data operation modules of the identical function (this also applies to Fig. 4 described below).
  • three rectangles depicted inside a dashed line enclosure corresponding to the first data operation module manager 12-1 all represent the data operation modules 112-1 of the identical function (this also applies similarly to the other data operation modules 112-2 and 112-3.)
  • the data operation module 112-i provides some data management and operation functions with respect to its user (the application program 2 or the resource manager 11). For example, as will be described below, a function for enabling management and operation of binary files as XML documents or an associative memory function using a pair of a key and a value on the XML documents is provided. Namely, the role of the data operation module is to make the lower level data or data models appear as other types of data or data models, and provide management and operation functions with respect to these other types of data or data models at the same time.
  • a set of one or more data operation modules 112-i provide management and operation functions for one data, with respect to the application program 2 or the resource manager 11. Namely, in the case where the application program 2 or the resource manager 11 carries out the processing with respect to data, directories and properties in the file system 3 by utilizing the data management system 1, one or more data operation modules 112-i are used in combination according to the data model, the operation content, etc., as in an exemplary case shown in Fig. 3 .
  • an entity of the data operation module 112-i exists for each operation target data. Consequently, when a plurality of operation entities (the application programs 2 or the resource manager 11) are operated simultaneously, in practice there can be cases where a plurality of data operation modules 112-i of the identical function are existing (or used) simultaneously as in the exemplary case shown in Fig. 3 , cases where only one data operation module 112-i is existing (or used), and cases where no data operation module 112-i is existing (or used).
  • the data operation modules 112-i of the identical function are managed by the corresponding one data operation module manager 12-i.
  • data operation modules 112-i to be managed by each data operation module manager 12-i may be plural, one or none.
  • the data operation module manager (1) is managing three data operation modules (1)
  • the data operation module manager (2) is managing five data operation modules (2)
  • the data operation module manager (n) is managing seven data operation modules (n).
  • a relationship between the data operation module manager 12-i and the data operation modules 112-i is equivalent to a relationship between a class and instances in the object-oriented programming language.
  • the data operation module manager 12-i alone is to be programmed, and the data operation modules 112-i can be created or deleted according to the need during the operation.
  • the resource manager 11 has a function for making a set up to enable a desired operation by combining necessary data operation modules 112-i upon receiving a data operation request from the application program 2.
  • the resource manager 11 has a name management table 22 for managing correspondences between names of currently used data and the data operation modules, and a data operation module management table 21 to be used at a time of combining the data operation modules.
  • Fig. 4 shows a more specific exemplary configuration of this data management system.
  • This data management system 1 has five types of data operation module managers including a file system module manager 12, an XML module manager 13, a Key-Value module manager 14, a directory module manager 15 and a property module manager 16. Also, in correspondence to them, five types of data operation modules 112-116 will be used according to the need. Note that the state of existence (the state of utilization) of the data operation modules shown in Fig. 4 represents only an example at some moment, and will be changed according to the data operation state by the data operation subject. Also, in Fig. 4 , the reference numerals 112-114 for the corresponding modules are partially omitted for the sake of simplicity.
  • Fig. 5 shows an exemplary structure of the data operation module management table 21 in the resource manager 11.
  • the data operation module management table 21 records a correspondence between a name of each data operation module and a pointer to the data operation module manager that manages that data operation module.
  • the names of the data operation module is specified by the XML elements such as ⁇ Propm/> and ⁇ xmlm/>. These names of the data operation modules will be used in describing "a manner of combination" of the data operation modules necessary in accessing respective data.
  • Fig. 6 shows an exemplary structure of the name management table 22 managed by the resource manager 11.
  • the name management table 22 records a correspondence among a name of each currently used directory or data, a pointer to a property module for its property, and a pointer to a directory module for its directory in the case of the directory.
  • the property module 116 is a data operation module expressing the property
  • the directory module 115 is a data operation module expressing the directory.
  • Fig. 6 the names are given by "/dir1", “/dir1/dir2/data1”, etc. Also, in Fig. 6 , the column for a pointer to the property module and a column for a pointer to the directory module are depicted as empty, but appropriate pointers to the property modules and pointers to the directory modules will be entered in these columns in practice.
  • the first data operation module is the file system module.
  • the file system module 112 is a data operation module which has a role of abstracting the file system 3 provided below the data management system 1. Its main function is to provide read/write operations with respect to binary data recorded in the file system 3.
  • Examples of the operations to be provided by the file system module 112 with respect to binary data include the following.
  • the file system module 112 In the case of accessing binary data by using the file system module 112, usually the file system module 112 alone is used as shown in Fig. 7 . In this example, the content of a file with a name "f2468" that is recorded in the lower level file system 3 is exhibited to the upper level application program 2 as binary data.
  • the second data operation module is the XML module.
  • the XML module 113 stores a tree structure data for the XML documents in an internal representation, on binary data provided by the file system module 112 provided below this XML module 113, and enables operations with respect to the tree structure data, such as reading of a document in the tree structure and addition/deletion of a partial tree.
  • Examples of the operations to be provided by the XML module 113 with respect to XML documents include the following.
  • the XML module 113 In the case of accessing data of the XML document by using the XML module 113, usually the XML module 113 and the file system module 112 are used in combination as shown in Fig. 9 .
  • the third data operation module is the Key-Value module.
  • the Key-Value module 114 is a data operation module for storing a plurality of pairs of a key and a value, and enabling associative access by specifying a key with respect to the stored set of pairs of a key and a value.
  • the Key-Value module 114 stores the set of pairs of a key and a value in forms of XML documents. Consequently, the Key-Value module 114 provides an associative memory function on XML documents provided by the XML module 113.
  • Examples of the operations to be provided by the Key-Value module 114 include the following.
  • the Key-Value module 114 manages the set of pairs of a key and a value as XML documents in a format as shown in Fig. 11 .
  • each ⁇ entry> element has one pair of a key and a value
  • each ⁇ key> element has a key
  • each ⁇ value> element has a value.
  • This example records a state in which a key "OSAKA” has a value "TAKOYAKI", and a key "HAKATA” has a value "KARASHIMENTAIKO”.
  • the pairs of a key and a value are managed by arranging them serially, but it is also possible to use an implementation for enabling faster search by using the well known data structure such as binary tree or B-TREE.
  • One of the features of the present invention is that such an internal implementation of the Key-Value module 114 can be changed without affecting the other data operation modules and the application program 2 that uses the Key-Value module 114.
  • the Key-Value module 114 In the case of accessing data by using the Key-Value module 114, usually the Key-Value module 114, the XML module 113 and the file system module 112 are used in combination as shown in Fig. 12 .
  • the fourth data operation module is the property module.
  • the property module 116 is used by the data management system 1 (the resource manager 11) for internal management.
  • the data management system 1 manages a set of pairs of an attribute name and an attribute value of the property on the associative memory function provided by the Key-Value module 114.
  • Examples of the operations of the property to be provided by the property module 116 include the following.
  • Fig. 14 shows an example of an XML document in the case where the property module 116 manages pairs of an attribute name and an attribute value of the property as an XML document by using the Key-Value module 114.
  • Fig. 14 is an example for the property of the data "data1".
  • each ⁇ key> element indicates an attribute name of the property
  • each ⁇ value> element indicates an attribute value of the property.
  • there are three attributes including "creationdate” indicating creation date and time of the data, "owner” indicating an owner of the data, and "module” for describing a manner of combination of the data operation modules that is necessary in accessing the entity of this data.
  • the respective ⁇ value> elements indicate their attribute values.
  • the "module” attribute has a role for connecting the property of the data to the entity of the data in the data management system 1 of this embodiment.
  • the resource manager 11 selects and combined the necessary data operation modules according to the information written in this "module" attribute.
  • the property module 116 In the case of accessing data by using the property module 116, usually the property module 116, the Key-Value module 114, the XML module 113 and the file system module 112 are used in combination as shown in Fig. 15 .
  • the fifth data operation module is the directory module.
  • the directory module 115 is used by the data management system 1 (the resource manager 11) for internal management, similarly as the property module 116.
  • the data management system 1 is managing the directory as a correspondence between a key given by a directory name or a data name that is existing below that directory and a value given by information on a manner of combination of the data operation modules necessary in accessing its property.
  • the correspondences are managed on the associative memory function provided by the Key-Value module 114.
  • Examples of the operations of the directory to be provided by the directory module 115 include the following.
  • Fig. 17 shows an example of an XML document in the case where the directory module 115 manages pairs of a directory name or a data name that exists below the directory and information on a manner of combination of the data operation modules necessary in accessing its property, as an XML document by using the Key-Value module 114.
  • Fig. 17 is an example for the entity of the directory "dir2" shown in Fig. 1 .
  • each ⁇ key> element indicates a name of a directory or a data that is a child
  • each ⁇ value> element indicates information on a manner of combination of the data operation modules necessary in accessing its property.
  • two data "data1" and "data2" are managed as children.
  • the resource manager 11 In the case where the application program 2 requests an access to data "data1", the resource manager 11 first searches ⁇ value> of the entry having "data1" as ⁇ key> from the entity of the directory "dir2" shown in Fig. 17 , and selects and combines the data operation modules for accessing data of the property of "data1” according to the description written in that ⁇ value>.
  • the property module 116 that manages information as shown in Fig. 14 is created so that this is recorded in the name management table 22, while a value of the "module” attribute is extracted from data of the property, and the data operation modules necessary in accessing data of the XML document corresponding to the entity of "data1" are selected and combined using the extracted value of the "module” attribute.
  • a pointer of the XML module 113 that is created as a result of this is then given to the application program 2.
  • the directory module 115 In the case of accessing data by using the directory module 115, usually the directory module 115, the Key-Value module 114, the XML module 113 and the file system module 112 are used in combination as shown in Fig. 18 .
  • the resource manager 11 selects and combines the data operation modules necessary in accessing data specified by the description recorded in data of the property or the directory. This operation will now be described for an exemplary case shown in Fig. 20 .
  • the specific examples shown in Fig. 1 and Fig. 14 will be used.
  • Fig. 20 shows the internal operation of the data management system 1 in the case where the application program 2 commanded the resource manager 11 of the data management system 1 to open the data "/dir1/dir2/data1". In the following, the flow of the processing will be described along the numbers indicated in Fig. 20 .
  • the category of data is a name indicating a type of data, and in this embodiment, it is assumed that the following category names are available.
  • ⁇ property/> a category name of properties
  • ⁇ directory/> a category name of directories
  • association/> a category name of associative memories
  • ⁇ document/> a category name of XML documents
  • ⁇ binary/> a category name of binary data
  • ⁇ file/> a category name of files
  • FIG. 21 shows an example of such rules.
  • the rule describes data of which category can be realized by which data operation module.
  • the rule that begins with ⁇ rule> contains a category description section that begins with ⁇ category> and a data operation module description section that begins with ⁇ expand>.
  • the first rule specifies that the property module (116) indicated by ⁇ propm/> should be used in order to operate data of the property category ⁇ property/>.
  • the directory module (115) indicated by ⁇ dirm/> should be used for data of the directory category ⁇ directory/>
  • the XML module (113) indicated by ⁇ xmlm/> should be used for data of the XML document category ⁇ document/>, and so on.
  • At least one rule is managed for each category in this manner.
  • the rule for ⁇ file/> category is used for describing parameters regarding the file system 3.
  • the data operation module description section of the rule corresponding to ⁇ file/> category merely describes ⁇ file/> so that no special information is provided in this case.
  • the file system 3 has a plurality of partitions, for example, it is possible to provide an element ⁇ partition/> below ⁇ file/> that corresponds to ⁇ file/> category as shown in Fig. 22 , such that a file is created in the first partition if its value is "1". If this rule is encountered when the file system module 112 attempts to create data of ⁇ file/> category, i.e., a file, the file is created in the first partition. If this rule is absent, the file system 3 will create the file in a default partition.
  • Fig. 23 shows an exemplary operation in the case where the application program 2 commanded the data management system 1 by a CREATE command to create data of the XML document type with a name "/dir1/dir3/data3". In the following, the flow of the processing will be described along the numbers indicated in Fig. 23 .
  • a portion enclosed by ⁇ context/> is the context.
  • the rule that has the context indicates that the data operation module in the ⁇ expand> section is to be used in the case where not only the category is the same but also a position at which the data operation module corresponding to that category will be used (a position or an order of a combination of the data operation modules in the hierarhical structure, for example) is a correct position specified by the context.
  • a position at which the data operation module corresponding to that category will be used a position or an order of a combination of the data operation modules in the hierarhical structure, for example
  • the example shown in Fig. 24 indicates that the data operation module indicated by ⁇ dtdm/> is to be used only in the case where the category is ⁇ document/> and the data operation module indicated by ⁇ dtdm/> does not exist in upper levels.
  • the data operation module indicated by ⁇ dtdm/> is a DTD module 117 which is data operation module for monitoring whether a structure given by DTD (a definition of a structure of an XML document) is satisfied or not with respect to XML documents.
  • the lower level modules used by ⁇ dtdm/> are those that can operate data of the XML document category, and ⁇ dtdm/> itself behaves as if it is the data operation module that operates on data of the XML document category when viewed from the user.
  • the data operation modules will be combined such that the XML module 113 is placed over the file system module 112, and the DTD module 117 is placed over that in the case of accessing data of the XML document category.
  • DTD module manager will be provided in the case of using the DTD module 117.
  • the directories (hierarchical levels of data) are sequentially (according to priority levels defined in accordance with the hierarchical levels of data) traced from that data toward the root (steps S11, S13), and the data operation module is determined by using a rule (a selection method for selecting data operation modules) satisfying the conditions of the category and the context that is found first in the course of tracing (steps S12, S14).
  • a rule as shown in Fig. 28B is provided for "dir1"
  • a rule as shown in Fig. 28C is provided for "dir2”.
  • ⁇ xmls/> is a name of a sequential XML module
  • ⁇ xmlr/> is a name of a random XML module.
  • the sequential XML module and the random XML module are both a data operation module for storing a tree structure data of XML documents in an expanded form on the binary data provided by the file system module and providing operations with respect to the tree structure data.
  • the operation functions provided by these data operation modules with respect to the application program or the like that uses them are the same as the XML module.
  • the sequential XML module uses an internal data structure by which the sequential accesses to XML documents become faster while the random XML module uses a data structure by which random accesses to XML documents become faster.
  • the selection rule can be set such that different data operation modules are selected for different directories, or alternatively such that different data operation modules are selected for different conditions in the ⁇ context/> section of the rules.
  • a manner of combination of the data operation modules necessary in accessing data is a simple stacking of the data operation modules.
  • Fig. 29 shows an example of such a data operation module.
  • the expanded Key-Value module 118 is similar to the Key-Value module in that it has correspondences between a key and a value as XML documents, but differs in that it also has an index in a form of binary data such that the fast search is possible using this index.
  • ⁇ kva/> is a name indicating the expanded Key-Value module 118.
  • a description of the lower level data operation modules to be used by that data operation module is placed below the name of the data operation module, but here information ⁇ kvainfo/> specific to ⁇ kva/> is provided.
  • ⁇ data/> records a manner of combination of the data operation modules necessary for accessing the XML document recording a key and a value
  • ⁇ index/> records a manner of combination of the data operation modules necessary for accessing the binary data recording the index.
  • the data operation modules that should be selected and the order in which they should be used are specified in the data management system 1, but it is also possible for the application program 2 to specify a manner of combination of the data operation modules, and it is possible to use both of these schemes together.
  • the application program 2 acquires by its independent operation an information for specifying the data operation modules that should be selected and the order in which operations should be applied to data (such as information of Fig. 14 , for example), and the application program 2 notifies a manner of combination of the data operation modules to the data management system 1 according to this information.
  • a plurality of data operation modules having different operation functions are provided for the purpose of operating data, and when a request for a processing with respect to a desired data is received from the application program, the operations are applied to this data by selecting the data operation modules that should carry out the operations with respect to that data such that this data will be in compliance with the data model (a data structure that can be interpreted by the application program, data with attached functions that can be used by the application program, etc.) suitable for the processing that the application program wishes to carry out, so that it is possible to provide a data management system and a data management method capable of realizing improved flexibility, independency and expandability together.
  • the data model a data structure that can be interpreted by the application program, data with attached functions that can be used by the application program, etc.
  • the data management and operation using arbitrary data model become possible by combining the necessary data operation modules on some data model provided by some data storage system (a general file system for outputting binary data such as a system for outputting data exactly as read out from the hard disk, a special file system with an additional function for outputting data after converting the binary data into XML data for example, etc.), e.g., on the binary data provided by the file system, so that the flexible data management function can be provided.
  • some data storage system a general file system for outputting binary data such as a system for outputting data exactly as read out from the hard disk, a special file system with an additional function for outputting data after converting the binary data into XML data for example, etc.
  • the application programs and the data operation modules are separated so that there is an advantage that there is no need to describe a processing necessary for the data operation in the application program, unlike the case of using the conventional file system. For this reason, even in the case of sharing data by a plurality of application programs, the sharing can be realized easily because the processing necessary for the data operation is provided by the data operation modules. Moreover, it is possible to expand the function or exchange the data operation modules, without making any change in the application program. In other words, it is possible to realize a high data independency.
  • the data management function with an improved expandability that enables the addition of a data operation module with a new function, the upgrading of the function of the existing data operation module independently from the application program, and the addition of variations for providing the data operation modules with a variety of characteristics even among the data operation modules for handling data of the same category.
  • the data management system of the above described embodiments can be conveniently implemented in a form of a software package.
  • Such a software package can be a computer program product which employs a storage medium including stored computer code which is used to program a computer to perform the disclosed function and process of the present invention.
  • the storage medium may include, but is not limited to, any type of conventional floppy disks, optical disks, CD-ROMs, magneto-optical disks, ROMs, RAMs, EPROMs, EEPROMs, magnetic or optical cards, or any other suitable media for storing electronic instructions.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Hardware Design (AREA)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • Mathematical Physics (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Stored Programmes (AREA)

Claims (10)

  1. Système de gestion de données (1) pour réaliser des opérations sur des données délivrées en sortie à partir d'un système de stockage de données, et pour transférer des données vers une procédure d'un programme d'application (2), le système de gestion de données (1) comprenant :
    un module de mémoire (31) configuré pour stocker une pluralité de modules de réalisation d'opérations sur des données pour réaliser des opérations sur des données qui ont des fonctions de commande différentes ; et
    une unité de commande (11) configurée pour lire des données requises par le programme d'application (2) à partir du système de stockage de données, qui sélectionne les modules de réalisation d'opérations sur des données (112-116) qui doivent réaliser les opérations par rapport aux données de telle sorte que les données soient conformes à un modèle de données approprié pour le traitement que le programme d'application (2) souhaite réaliser, parmi la pluralité de modules de réalisation d'opérations sur des données (112-116), de façon à ce que les données sur lesquelles les opérations sont réalisées par des modules de réalisation d'opérations sur des données sélectionnés soient transférées vers le programme d'application (2),
    dans lequel l'unité de commande (11) enregistre également des informations pour spécifier les modules de réalisation d'opérations sur des données (112-116) qui doivent être sélectionnés, ainsi qu'un ordre dans lequel les opérations doivent être réalisées sur les données au moment de transférer les données vers le programme d'application (2), en relation avec les données enregistrées dans le système de stockage de données, de telle sorte que l'unité de commande (11) soit amenée à fonctionner conformément auxdites informations enregistrées en relation avec les données lues à partir du système de stockage de données.
  2. Système de gestion de données selon la revendication 1, dans lequel quand l'unité de commande (11) sélectionne deux ou plusieurs modules de réalisation d'opérations sur des données (112-116), l'un des modules de réalisation d'opérations sur des données (112-116) qui correspond à un niveau hiérarchique moins élevé parmi les modules de réalisation d'opérations sur des données sélectionnés (112-116) réalisant des opérations sur les données délivrées en sortie à partir du système de stockage de données et transférant les données vers un module de réalisation d'opérations sur des données (112-116) qui correspond à un niveau hiérarchique plus élevé dudit un module de réalisation d'opérations sur des données (112-116), et un autre module de réalisation d'opérations sur des données (112-116) qui correspond à un niveau hiérarchique plus élevé parmi les modules de réalisation d'opérations sur des données sélectionnés (112-116) réalisant des opérations sur les données délivrées en sortie à partir d'un module de réalisation d'opérations sur des données qui correspond à un niveau hiérarchique moins élevé dudit un autre module de réalisation d'opérations sur des données (112-116) et transférant les données vers le programme d'application (2).
  3. Système de gestion de données selon la revendication 1, dans lequel quand le module de mémoire (31) contient deux ou plusieurs modules de réalisation d'opérations sur des données (112-116) qui correspondent à un niveau hiérarchique identique, l'unité de commande (11) prend l'un desdits deux ou plusieurs modules de réalisation d'opérations sur des données (112-116) en tant qu'un candidat au moment de sélectionner les modules de réalisation d'opérations sur des données (112-116) qui doivent réaliser les opérations par rapport aux données.
  4. Système de gestion de données selon la revendication 1, dans lequel l'unité de commande (11) détermine également les modules de réalisation d'opérations sur des données sélectionnés (112-116) qui sont nécessaires pour les opérations des données dans une catégorie spécifiée, ainsi qu'une façon de combiner les modules de réalisation d'opérations sur des données sélectionnés (112-116) en accord avec des règles prescrites définies à l'avance quand une catégorie des données est spécifiée.
  5. Système de gestion de données selon la revendication 1, dans lequel l'unité de commande (11) sélectionne les modules de réalisation d'opérations sur des données (112-116) qui doivent réaliser les opérations par rapport à de nouvelles données créées par le programme d'application (2) dans le but de stocker les nouvelles données dans le système de stockage de données en accord avec le modèle de données, parmi la pluralité de modules de réalisation d'opérations sur des données (112-116), et écrit les nouvelles données sur lesquelles les opérations sont réalisées par des modules de réalisation d'opérations sur des données sélectionnés (112-116) dans le système de stockage de données.
  6. Système de gestion de données selon la revendication 1, dans lequel, quand le programme d'application (2) crée de nouvelles données, l'unité de commande (11) sélectionne au moins un des modules de réalisation d'opérations sur des données (112-116) qui doivent être utilisés par l'unité de commande (11) conformément à une catégorie des nouvelles données spécifiée par le programme d'application (2), et ledit au moins un de modules de commande de donnée (112-116) sélectionne d'autres modules de réalisation d'opérations sur des données (112-116) ou une catégorie qui peut spécifier les autres modules de réalisation d'opérations sur des données (112-116).
  7. Système de gestion de données selon la revendication 1, comprenant par ailleurs :
    une unité de gestion configurée pour gérer une pluralité de données hiérarchiquement, à l'intérieur du système de stockage de données ;
    dans lequel l'unité de commande (11) utilise un procédé de sélection déterminé conformément à un niveau de priorité défini en accord avec un niveau hiérarchique des données parmi des procédés de sélection enregistrés en relation avec le niveau hiérarchique des données, au moment de sélectionner les modules de réalisation d'opérations sur des données (112-116) qui doivent réaliser les opérations par rapport aux données.
  8. Procédé de gestion de données dans un système de gestion de données pour réaliser des opérations sur des données délivrées en sortie à partir d'un système de stockage de données, et pour transférer des données vers une procédure d'un programme d'application (2), le procédé de gestion de données comprenant les étapes consistant à :
    enregistrer des informations pour spécifier des modules de réalisation d'opérations sur des données qui doivent être sélectionnés, ainsi qu'un ordre dans lequel les opérations doivent être réalisées sur les données au moment de transférer les données vers le programme d'application (2) en relation avec des données enregistrées dans le système de stockage de données ;
    lire des données requises par le programme d'application (2) à partir du système de stockage de données à réception d'une demande de traitement par rapport à des données souhaitées enregistrées dans le système de stockage de données, émanant du programme d'application (2) ;
    sélectionner les modules de réalisation d'opérations sur des données (112-116) qui doivent réaliser les opérations par rapport aux données de telle sorte que les données soient conformes à un modèle de données approprié pour le traitement que le programme d'application (2) souhaite réaliser, parmi une pluralité de modules de réalisation d'opérations sur des données (112-116) pour réaliser des opérations sur des données qui ont des fonctions de commande différentes, qui sont définies à l'avance, conformément auxdites informations enregistrées en relation aux données lues à partir du système de stockage de données ; et
    réaliser les opérations sur les données par des modules de réalisation d'opérations sur des données sélectionnés (112-116) en accord avec lesdites informations enregistrées en relation avec les données lues à partir du système de stockage de données, et transférer les données sur lesquelles les opérations sont réalisées par les modules de réalisation d'opérations sur des données sélectionnés (112-116) vers le programme d'application (2).
  9. Procédé de gestion de données selon la revendication 8, comprenant par ailleurs les étapes consistant à :
    réaliser les opérations par les modules de réalisation d'opérations sur des données sélectionnés (112-116) par rapport à de nouvelles données créées par le programme d'application (2), dans le but de stocker les nouvelles données à l'intérieur du système de stockage de données conformément au modèle de données ; et
    écrire les nouvelles données sur lesquelles les opérations sont réalisées par les modules de réalisation d'opérations sur des données sélectionnés (112-116) dans le système de stockage de données.
  10. Support utilisable par un ordinateur, comprenant, mis en oeuvre en lui, des codes de programme lisibles par un ordinateur pour amener un ordinateur à fonctionner en tant qu'un système de gestion de données pour réaliser des opérations sur des données délivrées en sortie à partir d'un système de stockage de données, et pour transférer les données vers une procédure d'un programme d'application (2), les codes de programme lisibles par un ordinateur comprenant :
    un premier code de programme lisible par un ordinateur pour amener ledit ordinateur à enregistrer des informations pour spécifier des modules de réalisation d'opérations sur des données (112-116) qui doivent être sélectionnés ainsi qu'un ordre dans lequel les opérations doivent être réalisées sur les données au moment de transférer les données vers le programme d'application (2) en relation avec des données enregistrées dans le système de stockage de données ;
    un deuxième code de programme lisible par un ordinateur pour amener ledit ordinateur à lire des données requises par le programme d'application (2) à partir du système de stockage de données à réception d'une demande de traitement par rapport à des données souhaitées enregistrées dans le système de stockage de données en provenance du programme d'application (2) ;
    un troisième code de programme lisible par un ordinateur pour amener ledit ordinateur à sélectionner les modules de réalisation d'opérations sur des données (112-116) qui doivent réaliser les opérations par rapport aux données de telle sorte que les données soient conformes à un modèle de données approprié pour le traitement que le programme d'application (2) souhaite réaliser, parmi une pluralité de modules de réalisation d'opérations sur des données (112-116) pour réaliser des opérations sur des données qui ont des fonctions de commande différentes, qui sont définies à l'avance, conformément auxdites informations enregistrées en relation aux données lues à partir du système de stockage de données ; et
    un quatrième code de programme lisible par un ordinateur pour amener ledit ordinateur à réaliser les opérations sur les données par des modules de réalisation d'opérations sur des données sélectionnés (112-116) conformément auxdites information enregistrées en relation avec les données lues à partir du système de stockage de données, et transférer les données sur lesquelles les opérations sont réalisées par les modules de réalisation d'opérations sur des données sélectionnés vers le programme d'application (2).
EP00308108A 1999-09-30 2000-09-18 Système de gestion de données avec plusieurs modules d'exploitation de données Expired - Lifetime EP1091295B1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP27826199 1999-09-30
JP27826199A JP4167359B2 (ja) 1999-09-30 1999-09-30 データ管理システム及びデータ管理方法

Publications (3)

Publication Number Publication Date
EP1091295A2 EP1091295A2 (fr) 2001-04-11
EP1091295A3 EP1091295A3 (fr) 2003-09-03
EP1091295B1 true EP1091295B1 (fr) 2008-05-21

Family

ID=17594885

Family Applications (1)

Application Number Title Priority Date Filing Date
EP00308108A Expired - Lifetime EP1091295B1 (fr) 1999-09-30 2000-09-18 Système de gestion de données avec plusieurs modules d'exploitation de données

Country Status (7)

Country Link
US (2) US6714946B1 (fr)
EP (1) EP1091295B1 (fr)
JP (1) JP4167359B2 (fr)
KR (1) KR100405745B1 (fr)
CN (1) CN1203430C (fr)
DE (1) DE60038933D1 (fr)
TW (1) TW486634B (fr)

Families Citing this family (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP4378029B2 (ja) * 1999-04-27 2009-12-02 キヤノン株式会社 データ処理方法及び装置及び記憶媒体
DE60141583D1 (de) * 2001-10-18 2010-04-29 Sun Microsystems Inc Verfahren zur Dateiverarbeitung mit einem Plug-in
US7617502B2 (en) * 2002-11-06 2009-11-10 Scientific-Atlanta, Llc Managing peripheral device drivers
EP1570322B1 (fr) * 2002-12-11 2007-03-14 Fraysen Systems Limited Gestion de donnees de traitement
FR2849568B1 (fr) * 2002-12-26 2005-04-29 Orange France Systeme et procede de gestion de ressources dans un terminal relie a un reseau de communication
US20040215747A1 (en) * 2003-04-11 2004-10-28 Jonathan Maron System and method for a configuration repository
US20060069774A1 (en) * 2004-06-17 2006-03-30 International Business Machine Corporation Method and apparatus for managing data center using Web services
US7516122B2 (en) * 2004-12-02 2009-04-07 Computer Associates Think, Inc. System and method for implementing a management component that exposes attributes
JP4804836B2 (ja) * 2005-08-31 2011-11-02 三菱電機株式会社 データ生成装置及びデータ生成プログラム
CN102026147A (zh) * 2009-09-17 2011-04-20 中兴通讯股份有限公司 业务用户数据管理系统及其实现业务用户数据管理的方法
CN101739292B (zh) * 2009-12-04 2016-02-10 曙光信息产业(北京)有限公司 基于应用特征的异构集群作业自适应调度方法和系统
US20120094600A1 (en) 2010-10-19 2012-04-19 Welch Allyn, Inc. Platform for patient monitoring
JP5762878B2 (ja) 2011-08-08 2015-08-12 株式会社東芝 ｋｅｙ−ｖａｌｕｅストアを有するメモリシステム
JP5524144B2 (ja) 2011-08-08 2014-06-18 株式会社東芝 ｋｅｙ−ｖａｌｕｅストア方式を有するメモリシステム
CN104216729B (zh) * 2013-06-05 2017-10-13 阿里巴巴集团控股有限公司 应用系统的逻辑模块更新实现方法及装置
US10915507B1 (en) * 2014-08-21 2021-02-09 Amazon Technologies, Inc. Data conversion handler for a run-time execution environment
CN105786491A (zh) * 2016-02-23 2016-07-20 浪潮通信信息系统有限公司 一种基于数据描述的命令式智能数据管理系统
CN110019254A (zh) * 2017-07-17 2019-07-16 中兴通讯股份有限公司 规划区增量记录的处理方法、装置及计算机可读存储介质

Family Cites Families (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5261080A (en) * 1987-08-21 1993-11-09 Wang Laboratories, Inc. Matchmaker for assisting and executing the providing and conversion of data between objects in a data processing system storing data in typed objects having different data formats
JP2644554B2 (ja) * 1988-11-15 1997-08-25 株式会社日立製作所 情報処理システム
US5113522A (en) * 1989-05-17 1992-05-12 International Business Machines Corporation Data processing system with system resource management for itself and for an associated alien processor
KR940004389B1 (ko) * 1989-10-13 1994-05-23 인터내셔널 비지네스 머신즈 코포레이션 관계형 데이타베이스에 대한 액세스플랜 발생 방법 및 시스템
JPH05342179A (ja) * 1992-06-11 1993-12-24 Kobe Nippon Denki Software Kk データベースクライアント・サーバ分散処理システムのデータ処理方法
US5446880A (en) * 1992-08-31 1995-08-29 At&T Corp. Database communication system that provides automatic format translation and transmission of records when the owner identified for the record is changed
JPH0695935A (ja) * 1992-09-11 1994-04-08 Shikoku Nippon Denki Software Kk データベースのレコードフォーマット変更方式
US5504886A (en) * 1993-07-02 1996-04-02 International Business Machines Corporation System and method for applying user supplied relation definitions to application files for a relational database
US5581797A (en) * 1993-10-22 1996-12-03 Lucent Technologies Inc. Method and apparatus for displaying hierarchical information of a large software system
US5727158A (en) * 1995-09-22 1998-03-10 Integra Soft, Inc. Information repository for storing information for enterprise computing system
WO1998055908A2 (fr) * 1997-06-04 1998-12-10 Pangea Systems, Inc. Procede et dispositif permettant d'obtenir des resultats a partir d'applications informatiques multiples
US6167564A (en) * 1998-09-17 2000-12-26 Unisys Corp. Software system development framework
US6523027B1 (en) * 1999-07-30 2003-02-18 Accenture Llp Interfacing servers in a Java based e-commerce architecture
US20020194251A1 (en) * 2000-03-03 2002-12-19 Richter Roger K. Systems and methods for resource usage accounting in information management environments
US6502102B1 (en) * 2000-03-27 2002-12-31 Accenture Llp System, method and article of manufacture for a table-driven automated scripting architecture
AU2003273853A1 (en) * 2002-08-13 2004-03-03 International Business Machines Corporation An adaptive management method and system with automatic dependency resolution

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
NAGAR; RAJEEV: "Windows NT File System Internals: A Developer's Guide passage", September 1997, O'REILLY, SEBASTOPOL, CA, USA, XP002284839 *

Also Published As

Publication number Publication date
EP1091295A2 (fr) 2001-04-11
CN1290899A (zh) 2001-04-11
DE60038933D1 (de) 2008-07-03
JP4167359B2 (ja) 2008-10-15
CN1203430C (zh) 2005-05-25
KR100405745B1 (ko) 2003-11-15
US20040139122A1 (en) 2004-07-15
JP2001101042A (ja) 2001-04-13
US6714946B1 (en) 2004-03-30
EP1091295A3 (fr) 2003-09-03
KR20010067262A (ko) 2001-07-12
TW486634B (en) 2002-05-11

Similar Documents

Publication Publication Date Title
EP1091295B1 (fr) Système de gestion de données avec plusieurs modules d'exploitation de données
JP2708331B2 (ja) ファイル装置およびデータファイルアクセス方法
US5412808A (en) System for parsing extended file names in an operating system
EP0801773B1 (fr) Organisation plane de stockage et systemes de stockage utilisant cette architecture
US5628007A (en) Methods for storing a database in extended attributes of a file system
US6029170A (en) Hybrid tree array data structure and method
US7676526B1 (en) System, method and computer program product for multi-level file-sharing by concurrent users
US7496586B1 (en) Method and apparatus for compressing data in a file system
EP1265152B1 (fr) Système de fichiers pour des pages web générés de manière dynamique
US7617250B2 (en) Semantic file system
US7325017B2 (en) Method of implementation of data storage quota
US6647391B1 (en) System, method and article of manufacture for fast mapping from a propertied document management system to a relational database
JPH10198587A (ja) ファイル・システムの間接アドレシング方法及び装置
US7483905B2 (en) Database access device and method of accessing a database
KR101689782B1 (ko) 메타 데이터에 따라 파일 시스템의 파일들을 액세스하는 방법 및 상기 방법을 구현하는 디바이스
US7225314B1 (en) Automatic conversion of all-zero data storage blocks into file holes
US7958097B1 (en) Method and system for implementation of data storage quota
US7424574B1 (en) Method and apparatus for dynamic striping
JPH0358249A (ja) フアイルのアクセス方法
US6760713B2 (en) Method, computer program product, and system for file and record selection utilizing a fuzzy data record pointer
US7533225B1 (en) Method and apparatus for enabling adaptive endianness
CN109918355A (zh) 实现基于对象存储服务的nas的虚拟元数据映射系统和方法
Deppisch et al. Managing complex objects in the Darmstadt database kernel system
JPH09305449A (ja) データベース管理システム
Choy et al. A database management system for office systems and advanced workstations

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20001004

AK Designated contracting states

Kind code of ref document: A2

Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE

AX Request for extension of the european patent

Free format text: AL;LT;LV;MK;RO;SI

PUAL Search report despatched

Free format text: ORIGINAL CODE: 0009013

AK Designated contracting states

Kind code of ref document: A3

Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE

AX Request for extension of the european patent

Extension state: AL LT LV MK RO SI

RIC1 Information provided on ipc code assigned before grant

Ipc: 7G 06F 17/30 B

Ipc: 7G 06F 9/50 A

AKX Designation fees paid

Designated state(s): DE FR GB

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): DE FR GB

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REF Corresponds to:

Ref document number: 60038933

Country of ref document: DE

Date of ref document: 20080703

Kind code of ref document: P

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20080915

Year of fee payment: 9

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20081002

Year of fee payment: 9

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

26N No opposition filed

Effective date: 20090224

GBPC Gb: european patent ceased through non-payment of renewal fee

Effective date: 20080918

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: GB

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20080918

REG Reference to a national code

Ref country code: FR

Ref legal event code: ST

Effective date: 20100531

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: FR

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20090930

Ref country code: DE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20100401