# US 2019/0294722 A1 · Change management system for data synchronization within an enterprise portal application

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

- Number: US 2019/0294722 A1
- Document ID: US20190294722A1
- Status: Published application
- Kind: A1
- Application number: 15/926,714
- Filed: 2018-03-20
- Published: 2019-09-26
- Earliest claimed: 2018-03-20
- Assignees: Locus Robotics Corp.
- Applicants: Locus Robotics Corp.
- Inventors: Vijay Mohan
- Web page: https://patentgrep.com/patent/US20190294722A1

## CPC

- G06F 16/27: Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
- G06F 16/212: {with details for data modelling support}
- G06F 16/2365: {Ensuring data consistency and integrity}
- G06F 16/24552: {Database cache management}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A system and method for synchronizing database changes in an enterprise portal application. The system has a cache storing cache data having table data and index data of one or more databases. A schema layer generates schema objects representing the schema of the databases of the cache data. A change management system and a schema layer validates a cache of one or more databases and synchronizes the cache data to the databases by receiving a changeset, comparing the changeset to the schema data, verifying that the changeset is compatible with the cache data and the schema data, and passing the changeset to the cache for updating the cache data or for refreshing the schema data by the schema layer.

## Claims

### Claim 1

A system for maintaining a cache in an enterprise portal application, comprising:
a cache including cache data comprising table data and index data of one or more databases of the enterprise portal application;
a schema layer comprising database schema objects for representing the schema of the one or more databases, wherein the schema layer is configured to generate schema data representing the cache data;
a change management system in communication with the schema layer, the cache, and the one or more databases, wherein the change management system is configured to:
validate, by the schema layer, that the cache data and data of the one or more databases are synchronized; and
synchronize, in response to an indication that the cache is invalid, the cache data to the one or more databases by:
receiving a changeset comprising changes to the one or more databases,
comparing the changeset to the schema data for verifying that the changeset is compatible with the cache data and the schema data, and
at least one of passing the changeset to the cache for updating the cache data or refreshing the schema data by the schema layer.

### Claim 2 (depends on 1)

The system of claim 1, wherein the change management system is further configured to periodically validate the cache.

### Claim 3 (depends on 1)

The system of claim 1, wherein the indication that the cache is invalid includes receiving a message sent via a message queue from a data access layer.

### Claim 4 (depends on 1)

The system of claim 1, wherein the indication that the cache is invalid results from validating the cache.

### Claim 5 (depends on 1)

The system of claim 1, wherein validating the cache comprises comparing a total database row count of the one or more databases with a cache row count.

### Claim 6 (depends on 1)

The system of claim 1, wherein validating the cache comprises comparing a maximum time stamp of the one or more databases to a maximum time stamp of the cache.

### Claim 7 (depends on 1)

The system of claim 1, wherein validating the cache comprises comparing table data columns and table data types of the one or more database tables to table data columns and table data types for a corresponding table in the cache.

### Claim 8 (depends on 1)

The system of claim 1, wherein the schema layer is further configured to generate the schema data in the change management system that is identical to schema data of a data access layer of the enterprise portal application.

### Claim 9 (depends on 1)

The system of claim 1, further comprising one or more table schema custom index definitions for specifying additional indexes within the cache to optimize cache data retrieval.

### Claim 10 (depends on 1)

The system of claim 1, further comprising search indexes for ensuring validity of the search index for access by an enterprise portal application search engine.

### Claim 11 (depends on 1)

The system of claim 1, wherein the change management system is further configured to synchronize a remote database with the one or more databases for the purpose of replication and backup.

### Claim 12

A method for maintaining a cache in an enterprise portal application, comprising:
synchronizing, by a change management system, a cache including cache data comprising table data and index data of one or more databases of an enterprise portal application, the synchronizing, in response to an indication that the cache is invalid, including:
receiving a changeset comprising changes to the one or more databases,
comparing the changeset to schema data, generated by a schema layer in communication with the change management system, to verify that the changeset is compatible with the cache data and the schema data, and
at least one of passing the changeset to the cache for updating the cache data or refreshing the schema data by the schema layer.

### Claim 13 (depends on 12)

The method of claim 12, wherein the synchronizing further comprises updating at least one of the cache table data or the cache index data.

### Claim 14 (depends on 12)

The method of claim 12, wherein refreshing of the schema data includes updating the schema data to the changed schema of the one or more databases.

### Claim 15 (depends on 12)

The method of claim 12, wherein the schema layer of the data access layer and the schema layer of the change management system generates identical schema data.

### Claim 16 (depends on 12)

The method of claim 12, further comprising validating the cache to determine if the cache data and the one or more databases are synchronized.

### Claim 17 (depends on 16)

The method of claim 16, wherein validating the cache comprises comparing a total database row count of the one or more databases with a cache row count.

### Claim 18 (depends on 16)

The method of claim 16, wherein validating the cache comprises comparing a maximum time stamp of the one or more databases to a maximum time stamp of the cache.

### Claim 19 (depends on 16)

The method of claim 16, wherein validating the cache comprises comparing table data columns and table data types of the one or more database tables to table data columns and table data types for a corresponding table in the cache.

### Claim 20

A non-transitory computer readable medium including program instructions for execution by a processor of an enterprise portal application, the instructions causing the processor to:
provide a cache including cache data comprising table data and index data of one or more databases of the enterprise portal application;
provide a schema layer comprising database schema objects for representing the schema of the one or more databases, wherein the schema layer is configured to generate schema data representing the cache data;
provide a change management system in communication with the schema layer and the cache and the one or more databases, wherein the change management system is configured to:
validate, by the schema layer, that the cache data and data of the one or more databases are synchronized; and
synchronize, in response to an indication that the cache is invalid, the cache data to the one or more databases by:
receiving a changeset comprising changes to the one or more databases,
comparing the changeset to the schema data for verifying that the changeset is compatible with the cache data and the schema data, and
at least one of pass the changeset to the cache for updating the cache data or refresh the schema data by the schema layer.

### Claim 21

A system for maintaining a maintained system in an enterprise portal application, comprising:
at least one maintained system including maintained data comprising table data and index data of one or more source systems of the enterprise portal application;
a schema layer comprising database schema objects for representing the schema of the one or more source systems, wherein the schema layer is configured to generate schema data representing the maintained data;
a change management system in communication with the schema layer, the maintained system, and the one or more source systems, wherein the change management system is configured to:
validate, by the schema layer, that the maintained data and source data of the one or more source systems are synchronized; and
synchronize, in response to an indication that the maintained system is invalid, the maintained data to the source data by:
receiving a changeset comprising changes to the one or more source systems,
comparing the changeset to the schema data for verifying that the changeset is compatible with the maintained data and the schema data, and
at least one of passing the changeset to the maintained system for updating the maintained data or refreshing the schema data by the schema layer.

### Claim 22 (depends on 21)

The system of claim 21, wherein:
the one or more source systems each further comprise at least one of a database, a cache, a search index, a cloud, a server, or combinations thereof; and
the at least one maintained system further comprises at least one of a database, a cache, a search index, a cloud, a server, or combinations thereof.
