# US 2016/0253364 A1 · System for linking diverse data systems

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2016/0253364 A1
- Document ID: US20160253364A1
- Status: Published application
- Kind: A1
- Application number: 14/870,671
- Filed: 2015-09-30
- Published: 2016-09-01
- Earliest claimed: 2015-02-26
- Assignees: Accenture Global Services Limited
- Applicants: Accenture Global Services Limited
- Inventors: Karthik Gomadam; Teresa Sheausan Tung
- Web page: https://patentgrep.com/patent/US20160253364A1

## CPC

- G06F 16/353: into predefined classes
- G06F 16/22: Indexing; Data structures therefor; Storage structures
- G06F 16/256: {in federated or virtual databases}
- G06F 16/26: Visual data mining; Browsing structured data
- G06F 16/3344: {using natural language analysis}
- G06F 16/9024: {Graphs; Linked lists (G06F16/9027 takes precedence)}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A system creates an abstraction layer surrounding a diverse data system including multiple different databases. Data is received from data sources and ingested into the various databases according to a core model. New instances of the core model are created and added to a larger linked data model (LDM) when new data sources are added to the system. The LDM captures the linkages between different linked data objects and links across different databases. Accordingly, applications are able to access or explore the linked data stored in different databases without prior knowledge of the linking relationships.

## Claims

### Claim 1

A method comprising:
receiving a dataset at a communication interface, the dataset including dataset context information comprising metadata for the dataset;
determining by a processor a core model correlating to the dataset based on the dataset context information, the core model comprising a first dataset type node, a first database node, and a relationship edge establishing a relationship property for storage of the first dataset type in the first database node, the first database node corresponding to a first database of a plurality of databases in a diverse data system;
determining by the processor that a first portion of the dataset correlates to the first dataset type node;
determining by the processor the first database as a destination for storage of the first portion of the dataset based on the relationship edge between the first dataset type node and the first database node in the core model;
transmitting by the communication interface the first portion of the dataset to the first database for storage therein; and
instantiating, by linked data model (LDM) control circuitry, a first LDM instance in an LDM, the first LDM instance comprising:
definitional structure that mimics the core model;
a representation of the first portion of the dataset as an instance of the first dataset type node of the core model; and
a representation of the first database as an instance of the first database node of the core model.

### Claim 2 (depends on 1)

The method of claim 1 wherein the core model includes a second dataset type node, a second database node, and a second relationship edge establishing a relationship property for storage of the second dataset type in the second database node, the second database node corresponding to a second database of the plurality of databases in the diverse data system, the method further comprising:
determining by the processor that a second portion of the dataset correlates to the second dataset type node;
determining by the processor the second database as a destination for storage of the second portion of the dataset based on the second relationship edge;
transmitting by the communication interface the second portion of the dataset to the second database for storage therein; and
wherein instantiating, by the LDM control circuitry, the first LDM instance in the LDM further comprises including a representation of the second portion of the dataset as an instance of the second dataset type node and a representation of the second database as an instance of the second database node.

### Claim 3 (depends on 1)

The method of claim 1 further comprising:
receiving by the communication interface a query for at least the first portion of the dataset from a querying entity;
referencing, by the LDM control circuitry, the first LDM instance to determine the first database as the database in which the first portion of the dataset is stored;
contacting by the processor via the communication interface the first database to retrieve the first portion of the dataset;
receiving by the communication interface the first portion of the dataset from the first database; and
transmitting by the communication interface the first portion of the dataset to the querying entity.

### Claim 4 (depends on 3)

The method of claim 3 further comprising:
determining by the processor a semantic query response to the query by referencing, via the LDM control circuitry, the first LDM instance to determine a link between a second portion of the dataset and the first portion of the dataset within the first LDM instance; and
transmitting by the communication interface an identification of the second portion of the dataset to the querying entity.

### Claim 5 (depends on 3)

The method of claim 3 further comprising:
determining by the processor a semantic query response to the query by referencing, via the LDM control circuitry, a domain knowledge graph of the LDM, the domain knowledge graph including the first LDM instance as an LDM instance node related to a second LDM instance node in the domain knowledge graph; and
transmitting by the communication interface an identification of the second LDM instance node to the querying entity.

### Claim 6 (depends on 5)

The method of claim 5 further comprising:
receiving, at the communication interface, a second dataset, the second dataset including second dataset context information comprising metadata associated with the second dataset;
determining by the processor that the core model correlates to the second dataset based on the second dataset context information;
determining by the processor that a first portion of the second dataset correlates to the first dataset type node of the core model;
determining by the processor the first database as a destination for storage of the first portion of the second dataset based on the relationship edge between the first dataset type node and the first database node in the core model;
transmitting by the communication interface the first portion of the second dataset to the first database for storage therein; and
instantiating, by the LDM control circuitry, a second LDM instance in the LDM, the second LDM instance having at least partially a same structure as the core model and including a representation of the first portion of the second dataset as an instance of the first dataset type node of the core model and a representation of the first database as an instance of the first database node of the core model.

### Claim 7 (depends on 6)

The method of claim 6 further comprising:
updating, by the LDM control circuitry, a domain knowledge graph of the LDM to include the second LDM instance as an LDM instance node in relation to at least one other LDM instance node in the domain knowledge graph.

### Claim 8 (depends on 1)

The method of claim 1 further comprising:
receiving an update to the core model, the update including a third database node and a relationship edge establishing a relationship property for storage of the first dataset type in the third database node, the third database node corresponding to a third database of the plurality of databases in the diverse data system; and
updating, by the LDM control circuitry, the first LDM instance to link the first portion of the dataset to the third database.

### Claim 9 (depends on 8)

The method of claim 8 further comprising:
updating, by the LDM control circuitry, a plurality of LDM instances to link the first portion of the dataset to the third database, the plurality of LDM instances being instances of the core model.

### Claim 10

A method comprising:
executing, by a processor, a data explorer tool;
receiving, by the data explorer tool, from a user, a selection of a first node of a plurality of nodes of a domain knowledge graph of a linked data model (LDM), the first node corresponding to a first LDM instance of a core model, the domain knowledge graph including the plurality of nodes and a plurality of relationship edges between various ones of the plurality of nodes establishing a plurality of relationship properties between the various ones of the plurality of nodes;
referencing, by the data explorer tool, the first LDM instance to determine a first database associated with the first node based on a relationship edge coupling the first node to a first database node corresponding to the first database, the first database determined from a plurality of databases in a diverse data system;
retrieving a first portion of a dataset corresponding to the first node from the first database;
referencing, by the data explorer tool, the first LDM instance to determine a second database associated with the first node based on a second relationship edge coupling the first node to a second database node corresponding to the second database, the second database determined from the plurality of databases in the diverse data system and being distinct from the first database, the second database including a second portion of the dataset; and
providing the first portion of the dataset and an indication of an availability of the second portion of the dataset to the user via the data explorer tool.

### Claim 11 (depends on 10)

The method of claim 10 further comprising:
referencing, by the data explorer tool, the domain knowledge graph to determine a second node therein related to the first node based on an existence of a relationship edge connecting the first node and the second node in the domain knowledge graph, the second node corresponding to a second instance of a core model; and
providing a representation of the second node to the user via the data explorer tool.

### Claim 12 (depends on 10)

The method of claim 10 further comprising providing the second portion of the dataset to the user via the data explorer tool.

### Claim 13 (depends on 11)

The method of claim 11 further comprising:
receiving, by the data explorer tool, from the user, a selection of the second node;
referencing, by the data explorer tool, the LDM to determine the first database as being associated with the second node based on a relationship edge coupling the second node to a database node corresponding to the first database, the first database including a second dataset;
retrieving the second dataset corresponding to the second node from the first database; and
providing the second dataset to the user via the data explorer tool.

### Claim 14

A system comprising:
a communication interface configured to receive a dataset including dataset context information comprising metadata associated with the dataset;
a first core model including a first dataset type node, a first database node, and a relationship edge establishing a relationship property for storage of the first dataset type in the first database node, the first database node corresponding to a first database of a plurality of databases in a diverse data system;
data ingestion circuitry in communication with the communication interface and configured to:
determine the core model as correlating to the dataset based on the dataset context information;
determine that a first portion of the dataset correlates to the first dataset type node; and
determine the first database as a destination for storage of the first portion of the dataset based on the relationship edge between the first dataset type node and the first database node in the core model;
the communication interface further configured to transmit the first portion of the dataset to the first database for storage therein; and
linked data model (LDM) maintenance circuitry in communication with the data ingestion circuitry and configured to:
instantiate a first LDM instance in an LDM, the first LDM instance having, at least partially, a same structure as the core model and including a representation of the first portion of the dataset as an instance of the first dataset type node of the core model and a representation of the first database as an instance of the first database node of the core model.

### Claim 15 (depends on 14)

The system of claim 14 wherein:
the first core model further includes a second dataset type node, a second database node, and a second relationship edge establishing a relationship property for storage of the second dataset type in the second database node, the second database node corresponding to a second database of the plurality of databases in the diverse data system;
the data ingestion circuity is further configured to:
determine that a second portion of the dataset correlates to the second dataset type node; and
determine the second database as a destination for storage of the second portion of the dataset based on the second relationship edge between the second dataset type node and the second database node in the core model;
the communication interface is further configured to transmit the second portion of the dataset to the second database for storage therein; and
the LDM maintenance circuitry is further configured to:
instantiate the first LDM instance by including a representation of the second portion of the dataset as an instance of the second dataset type node and a representation of the second database as an instance of the second database node.

### Claim 16 (depends on 15)

The system of claim 15 further comprising:
data consumption circuitry in communication with the communication interface and the LDM maintenance circuitry, the data consumption circuitry configured to:
receive a query via the communication interface for at least the first portion of the dataset from a querying entity;
communicate with the LDM maintenance circuitry to reference the first LDM instance to determine the first database as the database in which the first portion of the dataset is stored; and
contact, via the communication interface, the first database to retrieve the first portion of the dataset;
determine a semantic query response to the query by communicating with the LDM maintenance circuitry to reference the first LDM instance to determine a link between the second portion of the dataset and the first portion of the dataset within the first LDM instance; and
effect transmission via the communication interface of the first portion of the dataset and an identification of the second portion of the dataset to the querying entity.

### Claim 17 (depends on 15)

The system of claim 15 wherein:
the LDM maintenance circuitry is further configured to maintain a domain knowledge graph of the LDM including a domain knowledge graph including a first node corresponding to the first LDM instance;
the system further comprising:
data exploration circuitry in communication with the communication interface and the LDM maintenance circuitry, the data exploration circuitry configured to:
provide a data explorer tool to a user;
receive, via the data explorer tool, from a user, a selection of the first node corresponding to the first LDM instance;
communicate with the LDM maintenance circuitry to reference the first LDM instance to determine the first portion of the data set, the first database, the second portion of the data set, and the second database as associated with the first node;
contact, via the communication interface, the first database to retrieve the first portion of the dataset; and
provide to the user, via the data exploration tool, the first portion of the dataset and an indication of an availability of the second portion of the dataset.

### Claim 18 (depends on 17)

The system of claim 17 wherein:
the domain knowledge graph further includes:
a second node corresponding to a second LDM instance of the core model, and
a relationship edge coupling the first node to the second node;
the data exploration circuitry is further configured to:
communicate with the LDM maintenance circuitry to reference the domain knowledge graph to determine the second node as associated with the first node based on the relationship edge coupling the first node to the second node; and
provide to the user, via the data exploration tool, a representation of the indication of the second node.

### Claim 19 (depends on 18)

The system of claim 18 wherein the second LDM instance indicates a second dataset is linked to the first database, wherein the data exploration circuitry is further configured to:
receive from the user, via the data explorer tool, a selection of the second node;
communicate with the LDM maintenance circuitry to reference the second LDM instance to determine the second dataset and the first database as associated with the second node;
contact, via the communication interface, the first database to retrieve the second dataset; and
provide to the user, via the data exploration tool, the second dataset.

### Claim 20 (depends on 17)

The system of claim 17 wherein the data explorer tool comprises a graphical user interface (GUI).
