Method and apparatus for bi-directional communication and data replication between multiple locations during intermittent connectivity

• US 9,973,582 B2
• Filed: 06/13/2017
• Issued: 05/15/2018
• Est. Priority Date: 10/19/2009
• Status: Active Grant

• Current Assignee: Tritan Software International, Co.
• Original Assignee: Tritan Software International, Co.
• Inventors: Carricarte, Andrew L., Va, Dario, Almeida, Abel Jose
• Primary Examiner(s): Bayard, Djenane
• Application Number:
  US15/621,617
• Publication Number:
  US 20170279901A1
• Time in Patent Office: 336 Days
• CPC Class Codes: G06F 16/273 Asynchronous replication or reconciliation
• CPC Class Codes: G06F 16/275 Synchronous replication
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• CPC Class Codes: H04L 67/148 Migration or transfer of sessions
• CPC Class Codes: H04W 76/11 Allocation or use of connection identifiers
• CPC Class Codes: H04W 76/19 Connection re-establishment

Abstract

A method and database server for synchronizing contents of a local database with contents of a remote database. The method includes writing data transactions to a local transaction log file, assigning bin numbers to the data transactions, and determining if the assigned bin numbers have changed due to receipt of subsequent data transactions and if the bin numbers have changed, inserting the subsequent data transactions into a local sequence log file and assigning the subsequent data transactions a first sequence number. The method includes providing, to a remote replicator service, access to the first sequence number, the remote replicator service having access to a second sequence number, and if the first sequence number does not match the second sequence number, providing to the remote replicator service access to the subsequent data transactions, the remote replication service updating a remote database to include the subsequent data transactions.

Claims

1. A method for synchronizing contents of a local database with contents of a remote database, the method comprising:

writing at least one data transaction received from a user terminal from the local database to a local transaction log file;

assigning a bin number to each of the at least one data transaction;

determining, by a local replicator service, if the assigned bin number has changed due to receipt of at least one subsequent data transaction;

if the bin number has changed, inserting, by the local replicator service, the at least one subsequent data transaction into a local sequence log file and assigning the at least one subsequent data transaction a first sequence number;

in response to a request by a remote replicator service, providing, to the remote replicator service, access to the first sequence number, the remote replicator service having access to a second sequence number stored in the remote database; and

if the first sequence number does not match the second sequence number,

providing, to the remote replicator service, access to the at least one subsequent data transaction associated with the first sequence number, the remote replication service updating the remote database to include the at least one subsequent data transaction.

2. The method of claim 1, further comprising assigning a universal unique identifier (UUID) to each data record received from the user terminal.

3. The method of claim 1, further comprising monitoring changes in the transaction log file using the assigned bin number.

4. The method of claim 1, wherein the local database is located on a vessel and the remote database is located on shore.

5. The method of claim 1, wherein the local replicator service and the remote replicator service communicate with each other via a satellite connection.

6. The method of claim 1, wherein the local replicator service and the remote replicator service are in operation at the same time.

7. A local database server configured to synchronize contents of a local database with contents of a remote database, the local database server comprising:

a local transaction log file;

processing circuitry including a memory and a processor, the memory in communication with the processor, the memory having instructions that, when executed by the processor, configure the processor to;

write at least one data transaction received from a user terminal from the local database to the local transaction log file;

assign a bin number to each of the at least one data transaction;

determine, by a local replicator service, if the assigned bin number has changed due to receipt of at least one subsequent data transaction;

if the bin number has changed, insert, by the local replicator service, the at least one subsequent data transaction into a local sequence log file and assign the at least one subsequent data transaction a first sequence number; and

a communication interface configured to receive a request from a remote replicator service,

in response to the request from the remote replicator service, the processor is further configured to;

provide, to the remote replicator service, access to the first sequence number, the remote replicator service having access to a second sequence number stored in the remote database; and

if the first sequence number does not match the second sequence number,

provide, to the remote replicator service, access to the at least one subsequent data transaction associated with the first sequence number, the remote replication service updating the remote database to include the at least one subsequent data transaction.

8. The database server of claim 7, wherein the processor is further configured to assign a universal unique identifier (UUID) to each data record received from the user terminal.

9. The database server of claim 7, wherein the processor is further configured to monitor changes in the transaction log file using the assigned bin number.

10. The database server of claim 7, wherein the local database is located on a vessel and the remote database is located on shore.

11. The database server of claim 7, wherein the local replicator service and the remote replicator service communicate with each other via a satellite connection.

12. The database server of claim 7, wherein the local replicator service and the remote replicator service are in operation at the same time.

13. A remote database server configured to synchronize contents of a local database with contents of a remote database, the remote database comprising:

a communications interface configured to;

receive, from a local replicator service, a first sequence number, the first sequence number associated with at least one data transaction, the local replicator service configured to assign the at least one data transaction the first sequence number upon determining if a bin number assigned to each of the at least one data transaction has changed due to receipt of at least one subsequent data transaction; and

processing circuitry including a memory and a processor, the memory in communication with the processor, the memory having instructions that, when executed by the processor, configure the processor to;

compare, by a remote replicator service, the first sequence number received from the local replicator service to a second sequence number, the second sequence number associated with a latest data transaction stored in the remote database; and

if the first sequence number does not match the second sequence number,

obtain from the local replicator service, via the communications interface, the at least one data transaction associated with the first sequence number; and

the processor is further configured to write the at least one data transaction to the remote database.

14. The remote database server of claim 13, wherein the local database is located on a vessel and the remote database is located on shore.

15. The remote database server of claim 13, wherein the local replicator service and the remote replicator service are in operation at the same time.

16. A system for synchronizing data transactions stored in a local database with data transactions stored in a remote database, the system comprising:

a local database server comprising;

a local transaction log file;

processing circuitry including a memory and a processor, the memory in communication with the processor, the memory having instructions that, when executed by the processor, configure the processor to;

write at least one data transaction received from a user terminal from the local database to the local transaction log file;

assign a bin number to each of the at least one data transaction;

determine, by a local replicator service, if the assigned bin number has changed due to receipt of at least one subsequent data transaction;

if the bin number has changed, insert, by the local replicator service, the at least one subsequent data transaction into a local sequence log file and assign the at least one subsequent data transaction a first sequence number; and

a local communication interface configured to communicate with a remote replicator service,

a remote database server comprising;

a remote communications interface configured to receive, from the local replicator service, the first sequence number; and

processing circuitry including a memory and a processor, the memory in communication with the processor, the memory having instructions that, when executed by the processor, configure the processor to;

compare, by the remote replicator service, the first sequence number received from the local replicator service to a second sequence number, the second sequence number associated with a latest data transaction stored in the remote database; and

if the first sequence number does not match the second sequence number,

obtain from the local replicator service, via the remote communications interface, the at least one data transaction associated with the first sequence number; and

the processor further configured to write the at least one data transaction to the remote database.

17. The system of claim 16, wherein the local database is located on a vessel and the remote database is located on shore.

18. The system of claim 16, wherein the local replicator service and the remote replicator service communicate with each other via a satellite connection.

19. The system of claim 16, wherein the local replicator service and the remote replicator service are in operation at the same time.

20. The system of claim 16, wherein the local database server further comprises a sequence log file for storing the first sequence number.