Database management system

• US 20040243595A1
• Filed: 03/25/2004
• Published: 12/02/2004
• Est. Priority Date: 09/28/2001
• Status: Abandoned Application

• Current Assignee: British Telecommunications PLC (BT Group PLC)
• Original Assignee: British Telecommunications PLC (BT Group PLC)
• Inventors: Jones, Dean, Cui, Zhan
• Application Number:
  US10/490,706
• Publication Number:
  US 20040243595A1
• Time in Patent Office: Days
• US Class Current: 707/100
• CPC Class Codes: G06F 16/2471 Distributed queries
• CPC Class Codes: G06F 16/25 Integrating or interfacing systems involving database management systems

Abstract

A database management system comprising a plurality of database resources (12, 14, 16) includes a query engine (30) which parses incoming queries into sub-queries directed at respective resources, (12, 14, 16) and compiles the sub-results into a final result. A node and a link representation is used to associate values from a different resources to address problems of semantic mismatch. In addition, ontologies are compiled for each resource against a shared ontology and a user/application ontology. As a result of the system, problems of semantic mismatch and query integration against distributed resources is overcome.

Claims

1. A database management system comprising a plurality of resources and a database manager having a respective resource ontology for each resource, the manager further comprising a client ontology and a shared ontology.

2. A system as claimed in claim 1 in which the manager further includes a plurality of respective first stores each containing a mapping of a resource ontology to its respective resource contents.

3. A system as claimed in claim 1 in which the manager further includes a directory of the respective resource contents.

4. A system as claimed in claim 1 in which the manager further includes at least one second store containing mappings between terms in the ontologies.

5. A system as claimed in claim 1 in which the database manager comprises a query engine.

6. A system as claimed in claim 1 in which the manager stores information concerning ontology terminologies and relationships therebetween.

7. A system as claimed in claim 6 in which the manager is arranged to provide said terminology/relationship information in response to a query.

8. A system as claimed in claim 1 in which the resource comprises at least one of a database resource or a semi-structured web resource.

23. A computer program configured to implement a system as in claim 1.

24. A computer readable medium comprising instructions for implementing a system as in claim 1.

25. A server or distributed server supporting a system as in claim 1.

9. A method of managing a database comprising a database manager, a plurality of resources comprising the steps of creating a resource ontology for each database resource and storing the resource ontology on the database manager.

10. A method as claimed in claim 9 further including the step of creating a mapping of each resource ontology to its respective resource contents, and storing the mapping in a respective first store.

11. A method as claimed in claim 10 further including the steps of generating queries to each of the first stores to obtain the respective resource contents and compiling therefrom a directory in the manager of the respective resource contents.

12. A method as claimed in claim 9 further including the steps of creating mappings of the resource ontologies onto a pre-defined application ontology and storing the mapping in at least one second store.

13. A method as claimed in claim 9 in which the resource ontology is created based on the respective resource.

14. A method as claimed in claim 9 in which the database manager further comprises a client and the shared ontology is based on the client ontology.

15. A method as claimed in claim 9 in which ontology creation comprises a top-down/bottom-up development process where ontology, database schemas and metadata are connected and differentiated for their roles.

16. A method of managing a database having a plurality of resources and respective ontologies and an intermediate ontology comprising the step of performing mappings between terms in the ontologies.

17. A methods as claimed in claim 16 in which the intermediate ontology comprises at least one of a user ontology, a shared ontology and an application ontology.

18. A method of creating an ontology for a database or database resource comprising a top-down/bottom-up development process where ontology, database schemas and metadata are connected and differentiated for that role.

19. An engineering client for a database management system having a plurality of resources, at least one client, a shared ontology and respective resource ontologies, the engineering client including an ontology creation tool for defining a client driven shared ontology and a resource driven resource ontology.

20. A client as claimed in claim 19 in which the ontology creation tool comprises a wizard which provides a step-by-step guide for creating a resource ontology from a shared ontology and for creating mappings between a resource and a database schemer.

21. An ontology creation tool arranged to provide a step-by-step guide for creating a resource ontology from a shared ontology and for creating mappings between a resource and a database schemer.

22. A tool as claimed in claim 21 comprising a wizard.

26. A database management system comprising a plurality of resources, a respective content description store representative of each resource content and a content description store manager arranged to receive and store content information from each content description store in which the content description store manager is arranged to update content information as resources are added or deleted from the system.

27. A system as claimed in claim 26 in which each resource is associated with a resource ontology and the content description of each resource content is in terms of the respective resource ontology.

28. A system as claimed in claim 27 further comprising a shared ontology wherein each resource ontology is a specialisation of the shared ontology through constraining types defined in the shared ontology or having fixed values.

29. A system as claimed in claim 26 in which at least one of the resources comprises either a database resource or a semi-structured web resource.

30. A system as claimed in claim 26 in which the content description store comprises a resource wrapper.

31. A system as claimed in claim 26 further arranged to compare received content information against stored content information and only update if the content information is not already stored.

36. A computer program configured to implement a system as in claim 26.

37. A computer readable medium comprising instructions for implementing a system as in claim 26.

38. A server or distributed server supporting a system as in claim 26.

32. A database management system comprising a plurality of resources, a respective resource ontology and a shared ontology, the system further comprising an engine for retrieving resource based term semantics as defined in the ontologies.

33. A method of updating a database having a plurality of resources, a respective content description store representative of each resource content and a content description store manager in which each content description store provides content information to the content description store manager and the content description store manager updates content information as resources are added to or deleted from the system.

34. A method as claimed in claim 33 in which the content information provided by the content description store is compared against stored content information and update takes place only if the content information is not already stored.

35. A method of managing a database having a plurality of resources, respective resource strategies and a shared ontology comprising the step of retrieving resource based term semantics as defined in the ontologies.

39. A database management system comprising a database manager including a query engine and a plurality of resources each containing database elements, in which the query engine is arranged to parse an incoming query to identify the elements required for a result, construct a node and link representation of resources including as nodes resources containing the required element and as links elements common to individual nodes and corn an integrated result from the representation.

40. A system as claimed in claim 39 in which the query engine is arranged to compile the integrated result from the data stored as links in the representation.

41. A system as claimed in claim 39 in which the query engine is arranged to identity intermediate links between indirectly linked nodes via intermediate, commonly linked nodes.

42. A system as claimed in claim 41 in which indirectly linked nodes represent resources containing elements other than required elements common with elements in existing nodes.

43. A system as claimed in claim 41 in which the query engine is arranged to create all available intermediate links prior to compilation of an integrated result.

44. A system as claimed in claim 39 in which the query engine is operable to recursively search through the available resources until it is able to construct a node and link representation of resources which cumulatively include all of the elements required by the query, the representation including links between all of the required resources such that the query engine is able to compile an integrated result.

45. A system as claimed in claim 39 in which the resources include at least one of a database resource or a semi-structured web resource.

52. A computer program configured to implement a system as in claim 39.

53. A carrier medium carrying instructions for implementing a system as in claim 39.

54. A server or distributed server supporting a system as in claim 39.

46. A method of managing a database comprising a database manager including a query engine and a plurality of resources each containing database elements comprising the steps of parsing an incoming query to identify the elements required for a result, constructing a node and link representation of resources including as nodes resources containing the required element and as links elements common to individual nodes and compiling an integrated result from the representation.

47. A method as claimed in claim 46 further including the step of compiling the integrated result from the data stored as links in the representation.

48. A method as claimed in claim 46 further including the step of identifying intermediate links between indirectly linked nodes via intermediate, commonly linked nodes.

49. A method as claimed in claim 48 in which intermediate links are identified between nodes representing resources containing elements other than required elements common with elements in existing nodes.

50. A method as claimed in claim 48 in which all available intermediate links are created prior to compilation of an integrated result.

51. A method as claimed in claim 46 wherein the query engine is operable to recursively search through the available resources until it is able to construct a node and link representation of resources which cumulatively include all of the elements required by the query, the representation including links between all of the required resources such that the query engine is able to compile an integrated result.

55. A database management system comprising a database manager and a plurality of resources in which the database manager includes a client ontology having a plurality of client instances, a respective resource ontology for each resource having resource defined instances and a mapping manager having mapping rules between ontologies in which the database manager is arranged to map a client instance and a resource instance to each other according to each mapping rule and validate the mapping rule if the instances match.

56. A system as claimed in claim 55 in which the resource defined instance is marked incompatible if there is no match.

57. A system as claimed in claim 55 further comprising a shared ontology in which the mapping manager has mapping rules between the client ontology and the shared ontology and between the shared ontology and the resource ontology.

58. A system as claimed in claim 56 in which marked incompatible instances are reconciled or transformed through the mapping rules from a client ontology to the shared ontology and from the shared ontology to resource ontologies.

59. A system as claimed in claim 57 in which the client ontology comprises a user ontology which is specialised from the shared ontology instances.

60. A system as claimed in claim 55 in which the resource comprises at least one of a database resource and a semi-structured web resource.

61. A system as claimed in claim 55 in which each instance comprises a specialisation through constraining types or fixed values.

65. A computer program configured to implement a system as in claim 55.

66. A computer readable medium comprising instructions for implementing a system as in claim 55.

67. A server or distributed server supporting a system as in claim 55.

62. A method of managing a database having a plurality of resources, a client ontology having a plurality of client defined instances, a respective resource ontology for each resource having resource defined instances and a mapping manager having mapping rules between ontologies comprising the steps of mapping a client instance and resource instance to each other according to each mapping rule and validating the mapping rule if the instances match.

63. A method as claimed in claim 62 further comprising the step of marking the resource defined instance incompatible if there is no match.

64. A method as claimed in claim 62 further comprising the step of reconciling or transforming an instance marked incompatible through the mapping rules from a client ontology to a shared ontology and from the shared ontology to a resource ontology.

68. A database management system comprising a database manager and a plurality of resources, in which the manager includes a query manager arranged to parse an incoming query for sub-queries, establish a sub-result for each sub-query from a respective resource and integrate the sub-results to obtain an overall query result.

69. A system as claimed in claim 68 in which the query engine contains a resource ontology for each resource and the sub-result is established via the resource ontologies.

70. A system as claimed in claim 68 in which the query engine is arranged to parse a query to identify the elements required for a sub-query sub-result, construct a node and link representation of resources including as nodes resources containing the required element and as links elements common to individual nodes and compile an integrated sub-result from the representation.

71. A system as claimed claim 68 in which the resource comprises at east one of a database resource or a semi-structured web resource.

75. A computer program configured to implement a system in claim 68.

76. A computer readable medium comprising instructions for implementing a system as in claim 68.

77. A server or distributed server supporting a system as in claim 68.

72. A method of managing a database comprising a database manager and a plurality of database resources comprising the steps of parsing an incoming query for sub-queries, establishing a sub-result for each sub-query from a respective resource and integrating the sub-results to obtain an overall query result.

73. A method as claimed in claim 72 in which the query engine contains a resource ontology for each database resource and in which the step of establishing the sub-result is carried out via the resource ontologies.

74. A method as claimed in claim 72 further including the steps of parsing a query to identify the elements required for a sub-query sub-result, constructing a node and link representation of database resources including as nodes resources containing the required element and as links elements common to individual nodes and compiling an integrated sub-result from the representation.