Mapping architecture for arbitrary data models

• US 7,739,223 B2
• Filed: 08/29/2003
• Issued: 06/15/2010
• Est. Priority Date: 08/29/2003
• Status: Expired due to Fees

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Suver, Chris, Burugapalli, Srinivasa R., White, Steven D., Pfleiger, Todd F., Laskos, Alex, Wiener, Adam J., Ari, Bertan, Vaschillo, Alexander, Aharoni, Avner Y., Bolognese, Luca, Conrad, Andrew J., Zhu, Jason Z., Schach, David, Cengiz, Ilker
• Primary Examiner(s): Pham; Khanh B
• Application Number:
  US10/652,214
• Publication Number:
  US 20050050068A1
• Time in Patent Office: 2,482 Days
• Field of Search: 707/2, 707/3, 707100-102, 707/103.R
• US Class Current: 1/1
• CPC Class Codes: G06F 16/25 Integrating or interfacing systems involving database management systems
• CPC Class Codes: G06F 16/258 Data format conversion from or to a database
• CPC Class Codes: G06F 16/84 Mapping; Conversion
• CPC Class Codes: Y10S 707/99942 Manipulating data structure, e.g. compression, compaction, compilation

Abstract

A data mapping architecture for mapping between two or more data sources without modifying the metadata or structure of the data sources themselves. Data mapping also supports updates. The architecture also supports at least the case where data sources that are being mapped, are given, their schemas predefined, and cannot be changed. The architecture includes a mapping component that receives respective metadata from at least two arbitrary data models, and maps expressions between the data models.

Claims

1. A system that facilitates mapping arbitrary data models and is recorded on a computer-readable storage medium, comprising a mapping component that receives respective metadata from at least two arbitrary data models, and maps expressions comprising at least one of a structure, field, and relationship between the data models;

wherein the mapping component performs the mapping between the data models is directional and the data models include a source domain and a target domain, wherein the directionality of the mapping influences mapping implementation and semantics for each of the arbitrary data models including data models of the source domain and the target domain such that models mapped as the source have one or more different characteristics than models mapped as the target, wherein the target domain comprises a structure and a field that can only be mapped once while the source domain comprises a structure and a field that can be mapped multiple times, and wherein the mapping between the data models is stackable, such that multiple stages of mappings occur from the source domain to the target domain, the stackable mapping allowing a user to implement data processing between any two arbitrary data models;

wherein the mapping component allows a user to operate on the data models through a query language of the target domain and provides use of other languages in combination with the mapping to transform the target or source domain;

wherein the mapping between the data models translates a query written in a query language of the target domain into a query language of the source domain; and

wherein the mapping component facilitates automatically synchronizing updates, wherein the updates allow the user to specify different behavior for the mapping by including a user-specified structured query language statement that is to be executed when a query, update, insert or delete command is called based on the mapping, and wherein when a user creates, deletes, or modifies a structure in the target domain, these changes are automatically persisted to the source domain.

2. The system of claim 1, wherein the data models are query languages.

3. The system of claim 1, wherein the data models are data access languages.

4. The system of claim 1, wherein the data models are data manipulation languages.

5. The system of claim 1, wherein the data models are data definition languages.

6. The system of claim 1, wherein the data models include at least an object model and at least one relational model where the object model is mapped to at least one of the relational models.

7. The system of claim 1, wherein the data models include object models where one of the object models is mapped to at least one of the other object models.

8. The system of claim 1, wherein the data models include an XML model and at least one relational model where the XML model is mapped to at least one of the relational models.

9. The system of claim 1, wherein the data models are XML models where one of the XML models is mapped to at least one of the other XML models.

10. The system of claim 1, wherein the data models include an XML model and at least one object model where the XML model is mapped to at least one of the object models.

11. The system of claim 1, wherein the data models are relational models where one relational model is mapped to at least one of the other relational models.

12. The system of claim 1, wherein the data models include an XML model and an object model where the object model is mapped to at least one of the XML models.

13. The system of claim 1, wherein the data models are of the same structure.

14. The system of claim 1, wherein the mapping component receives topology data that is derived from the metadata.

15. The system of claim 1, wherein the data models are read-only.

16. The system of claim 1, wherein the expressions mapped between the data models are at least one of the same, different, and a combination of the same and different.

17. The system of claim 1, wherein the mapping component creates structural transformations on the data of a data model by at least one of creating or collapsing hierarchies, moving attributes from one element to another, and introducing new relationships.

18. The system of claim 1, wherein the mapping component relates and connects the same mappable concepts between the data models.

19. The system of claim 1, wherein the data models include a source domain and a target domain such that the source domain is the persistent location of the data.

20. The system of claim 1, wherein the mapping component includes a mapping file that maps like concepts of the respective metadata.

21. A system that facilitates mapping arbitrary data models and is recorded on a computer-readable storage medium, comprising:

source metadata that represents source concepts of a source data source;

target metadata that represents target concepts of at least one target data source;

a mapping component that receives the source metadata and the target metadata and maps the concepts from the source data source to the target metadata associated with one or more of the target data sources;

wherein the data models are mapped without modifying the metadata or structure of the data models themselves;

wherein the mapping of the concepts between the source data source to the target data source is directional, and wherein the mapping between the data models is stackable, such that multiple stages of mappings occur from the source domain to the target domain, the stackable mapping allowing a user to implement data processing between any two arbitrary data models, wherein the directionality of the mapping influences mapping implementation and semantics for each of the arbitrary data models including data models of the source domain and the target domain such that models mapped as the source have one or more different characteristics than models mapped as the target, wherein the target domain comprises a structure and a field that can only be mapped once while the source domain comprises a structure and a field that can be mapped multiple times;

wherein the mapping component allows a user to operate on the source data source and the target data source through a query language of the target data source; and

wherein the mapping component facilitates automatically synchronizing updates, wherein the updates allow the user to specify different behavior for the mapping by including a user-specified structured query language statement that is to be executed when a query, update, insert or delete command is called based on the mapping, and wherein such that when a user creates, deletes, or modifies a structure in the target domain, these changes are automatically persisted to the source domain.

22. The system of claim 21, wherein the mapped concepts are at least one of the same, different, and a combination of the same and different.

23. The system of claim 21, wherein the data sources are of the same structure.

24. The system of claim 21, wherein the source concepts and the target concepts are the same in both of the data sources.

25. The system of claim 21, wherein the mapping component relates and maps the same concepts between the data sources.

26. The system of claim 21, wherein the source and target concepts include a relationship element that is a link and association between two structures in the same data source.

27. The system of claim 26, wherein the relationship element defines how a first structure relates to a second structure in the same data source.

28. The system of claim 21, wherein the source data source and the target data source are disposed on a network remote from the mapping component.

29. The system of claim 21, wherein the mapping component is local to at least one of the source data source and the target data source.

30. A computer implemented method of mapping data between data models, comprising the following computer executable acts:

receiving respective metadata from at least two arbitrary data models;

mapping expressions comprising at least one of a structure, field, and relationship between at least two of the data models based upon the metadata, wherein the expressions are directionally mapped between the data models, wherein the directionality of the mapping influences mapping implementation and semantics for each of the arbitrary data models including data models of the source domain and the target domain such that models mapped as the source have one or more different characteristics than models mapped as the target, wherein the target domain comprises a structure and a field that can only be mapped once while the source domain comprises a structure and a field that can be mapped multiple times;

creating a source domain and a target domain from the data models via the directional mapping;

stacking multiple stages of mappings from the source domain to the target domain, wherein stackable mapping allows a user to implement data processing between any two arbitrary data models;

allowing a user to operate on the data models through a query language of the target domain;

translating a query written in a query language of the target domain into a query language of the source domain;

automatically synchronizing updates and persisting changes to the source domain, wherein the updates allow the user to specify different behavior for the mapping by including a user-specified structured query language statement that is to be executed when a query, update, insert or delete command is called based on the mapping; and

transforming data during a mapping of a source data model to a target data model using a function.

31. The method of claim 30, wherein the expressions mapped between the two data models are the same expressions.

32. The method of claim 30, further comprising defining a source data schema and a target data schema and information missing in the schemas.

33. A computer implemented method for mapping arbitrary data models, comprising the following computer executable acts:

receiving source metadata that represents source concepts of a source data source and target metadata that represents target concepts of a target data source;

directionally mapping the concepts between the source and target data sources based upon the source metadata and the target metadata, wherein the directionality of the mapping influences mapping implementation and semantics for each of the arbitrary data models including data models of the source domain and the target domain such that models mapped as the source have one or more different characteristics than models mapped as the target, wherein the target domain comprises a structure and a field that can only be mapped once while the source domain comprises a structure and a field that can be mapped multiple times;

stacking multiple stages of mappings from the source domain to the target domain, wherein stackable mapping allows a user to implement data processing between any two arbitrary data models;

mapping the data models without modifying the metadata or structure of the data models themselves;

allowing a user to operate on the source and target data sources through a query language of the target data source;

automatically synchronizing updates and persisting changes to the source domain, wherein the updates allow the user to specify different behavior for the mapping by including a user-specified structured query language statement that is to be executed when a query, update, insert or delete command is called based on the mapping; and

selecting an optimal path for mapping between the source and the target.

34. The method of claim 33, wherein the data sources are of the same structure.

35. The method of claim 33, further comprising,

creating a variable in a source domain;

restricting the variable with conditions; and

mapping the variable to the target concept.

36. The method of claim 35, wherein the variable is created at least one of implicitly and explicitly.

37. The method of claim 35, wherein the variable represents an empty result set.

38. The method of claim 33, wherein the mapping is stackable between the source and target data via one or more intermediate mapping stages.

39. The method of claim 33, wherein the optimal path is selected with a central control entity based on at least one of available bandwidth and interruptions in the path.

40. The method of claim 33, further comprising accessing a mapping algorithm in response to selecting an optimal path between a plurality of the data sources and plurality of the data targets.

41. The method of claim 40, wherein the mapping algorithm is associated with a structure of the source data and the target data.

42. A system that facilitates mapping data between arbitrary data models and is recorded on a computer-readable storage medium, comprising:

means for receiving source metadata that represents source concepts of a source data source and target metadata that represents target concepts of a target data source;

means for mapping the concepts between the source and target data sources based upon the source metadata and the target metadata, wherein the mapping between the data models is stackable and directional, such that multiple stages of mappings occur from the source domain to the target domain, the stackable mapping allowing a user to implement data processing between any two arbitrary data models, wherein the directionality of the mapping influences mapping implementation and semantics for each of the arbitrary data models including data models of the source domain and the target domain such that models mapped as the source have one or more different characteristics than models mapped as the target, wherein the target domain comprises a structure and a field that can only be mapped once while the source domain comprises a structure and a field that can be mapped multiple times;

means for mapping the source and target data sources without modifying the metadata or structure of the data sources themselves;

means for allowing a user to operate on the source and target data sources through a query language of the target data source;

means for translating a query written in a query language of the target data source into a query language of the source data source; and

means for automatically synchronizing updates and persisting changes to the source domain, wherein the updates allow the user to specify different behavior for the mapping by including a user-specified structured query language statement that is to be executed when a query, update, insert or delete command is called based on the mapping.

43. The system of claim 42, wherein the means for mapping includes a mapping means that relates and maps the same concepts between the data sources.