# US 2014/0195478 A1 · Detecting data omissions for an intermittently-connected application

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

- Number: US 2014/0195478 A1
- Document ID: US20140195478A1
- Status: Published application
- Kind: A1
- Application number: 13/737,732
- Filed: 2013-01-09
- Published: 2014-07-10
- Earliest claimed: 2013-01-09
- Assignees: International Business Machines Corporation
- Applicants: International Business Machines Corporation
- Inventors: Avraham Leff; James T. Rayfield
- Web page: https://patentgrep.com/patent/US20140195478A1

## 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/156: {Query results presentation}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A system, method and computer program product for detecting data omissions between intermittently-connected devices. An example system includes a client device configured to execute client queries on a client data set, and generate client result sets. The client queries and client result sets are stored on a query queue as queued queries and queued result sets. The system includes a server device with a data omission detector and server database. The data omission detector receives the queued queries and queued result sets after detecting a network connection, executes server queries on the server database and generates server result sets. The server queries are based on the queued queries. The data omission detector compares the server result sets with queued result sets to determine if there are data omissions. Data omissions include data absent in the queued result set that is present in a server result set.

## Claims

### Claim 1

A method for detecting data omissions between intermittently-connected devices comprising:
executing a client query on a client data set stored on a client device;
generating a client result set based on the client query;
storing the client query and client result set in a client queue as a queued query and queued result set, the client queue located on the client device;
detecting a network connection between the client device and a server device;
after detecting the network connection, reading the query queue and executing a server query on a server database, the server database stored on the server device, the server query based on the queued query;
generating a server result set based on the server query;
comparing the server result set and queued result set to at least determine if there is data omission, the data omission including data absent in the queued result set that is present in the server result set.

### Claim 2 (depends on 1)

The method of claim 1, wherein the client query is executed when the client device is disconnected from the server device.

### Claim 3 (depends on 1)

The method of claim 1, wherein the client data set includes data replicated from the server database.

### Claim 4 (depends on 3)

The method of claim 3, wherein if there is data omission, the method further comprises modifying a replication algorithm based on the data omission.

### Claim 5 (depends on 3)

The method of claim 3, wherein if there is data omission, the method further comprises replicating the data absent in the client data set from the server database.

### Claim 6 (depends on 1)

The method of claim 1, wherein if there is data omission, the method further comprises flagging the queued result set and displaying an error message.

### Claim 7 (depends on 1)

The method of claim 1, wherein if there is data omission, the method further comprises notifying an application developer of the data omission.

### Claim 8 (depends on 1)

The method of claim 1, wherein the client query is executed by one or more applications on the client device.

### Claim at position 9

9-24. (canceled)