# US 2022/0284423 A1 · Architecture of Immutable Database for Bitemporal Analysis

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

- Number: US 2022/0284423 A1
- Document ID: US20220284423A1
- Status: Published application
- Kind: A1
- Application number: 17/516,436
- Filed: 2021-11-01
- Published: 2022-09-08
- Earliest claimed: 2021-03-05
- Assignees: Capital One Services, LLC
- Applicants: Capital One Services, LLC
- Inventors: Philip Austin KEDY; Kenneth J. SCHNEIDER; Aaron ZHANG
- Web page: https://patentgrep.com/patent/US20220284423A1

## CPC

- G06Q 20/389: {Keeping log of transactions for guaranteeing non-repudiation of a transaction}
- G06F 16/215: Improving data quality; Data cleansing, e.g. de-duplication, removing invalid entries or correcting typographical errors
- G06F 16/219: {Managing data history or versioning (querying versioned data G06F16/2474; querying temporal data G06F16/2477)}
- G06F 16/2308: {Concurrency control (transaction processing G06F9/466)}
- G06F 16/2358: {Change logging, detection, and notification (replication G06F16/27)}
- G06F 16/2365: {Ensuring data consistency and integrity}
- G06F 16/2379: {Updates performed during online database operations; commit processing}
- G06F 16/2477: {Temporal data queries}
- G06F 16/9024: {Graphs; Linked lists (G06F16/9027 takes precedence)}
- G06Q 20/08: Payment architectures
- G06Q 20/382: {insuring higher security of transaction}
- H04L 9/3297: {involving time stamps, e.g. generation of time stamps}
- H04L 9/50: {using hash chains, e.g. blockchains or hash trees}
- H04L 41/0806: for initial configuration or provisioning, e.g. plug-and-play
- H04L 41/0816: the condition being an adaptation, e.g. in response to network events
- H04L 41/0856: {by backing up or archiving configuration information}
- H04L 41/0866: Checking the configuration
- H04L 63/123: {received data contents, e.g. message integrity}
- H04L 67/34: {involving the movement of software or configuration parameters (network booting or remote initial program loading [RIPL] G06F9/4416)}
- H04L 69/02: {Protocol performance}
- H04L 69/08: Protocols for interworking; Protocol conversion
- G06Q 40/00: Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- H04L 41/0894: Policy-based network configuration management
- H04L 63/20: {for managing network security; network security policies in general (filtering policies H04L63/0227)}
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Embodiments disclosed are directed to implementing an immutable database. Several embodiments are directed to an architecture for implementing the immutable database as a data processing system with a real-time interface for buffering a plurality of transactions and a bitemporal ledger for storing the plurality of transactions and a processor. New transactions may be appended to the transaction to the plurality of transactions and processed in a temporal order which includes identifying a sequence of transactions in the bitemporal ledger associated with the transaction and incorporating the transaction into the sequence of transactions in the bitemporal ledger according to temporal metadata associated with the transaction to form an updated sequence of transactions.

## Claims

### Claim 1

A data processing system comprising:
a real-time interface unit configured to implement a transaction stream for buffering a plurality of transactions, the real-time interface unit configured to receive a transaction and a retroactive transaction to be processed by the data processing system, wherein the transaction and the retroactive transaction are associated with a user account managed by the data processing system;
a bitemporal ledger configured to store the plurality of transactions; and
a processor configured to:
append the transaction to the plurality of transactions in the transaction stream;
receive the transaction in temporal order from the transaction stream;
process the transaction, wherein processing the transaction further comprises:
identifying a sequence of transactions in the bitemporal ledger associated with the transaction; and
incorporating the transaction into the sequence of transactions in the bitemporal ledger according to temporal metadata associated with the transaction to form an updated sequence of transactions, wherein the processor and the bitemporal ledger are configured to prevent any transactions in the sequence of transactions from being overwritten, wherein the updated sequence of transactions reflects a current state of the user account;
process the retroactive transaction, wherein processing the retroactive transaction comprises:
generating an alternate sequence of transactions comprising the sequence of transactions and the retroactive transaction, wherein the retroactive transaction replaces one transaction in the sequence of transactions and wherein the alternate sequence of transactions reflects an alternate state of the user account based on the retroactive transaction; and
replacing the current state of the user account with the alternate state of the user account.

### Claim 2 (depends on 1)

The data processing system of claim 1, the processor further configured to:
store, in the bitemporal ledger, the updated sequence of transactions and a second sequence of transactions, wherein the second sequence of transactions is associated with a second user account managed by the data processing system

### Claim 3 (depends on 1)

The data processing system of claim 1, wherein the sequence of transactions is implemented as a graph comprising a plurality of nodes with each node of the plurality of nodes having a corresponding transaction in the sequence of transactions.

### Claim 4 (depends on 1)

The data processing system of claim 1, the processor further configured to:
identify a processing module configured to further process the transaction; and
pass the transaction to the processing module for further processing.

### Claim 5 (depends on 4)

The data processing system of claim 4, wherein the alternate sequence of transactions further includes alternate transactions that are in temporal order subsequent to the sequence of transactions.

### Claim 6 (depends on 5)

The data processing system of claim 5, wherein at least one alternate transaction of the alternate transactions reflects a change to the sequence of transactions and is based on the transaction.

### Claim 7 (depends on 4)

The data processing system of claim 4, the processing module further configured to:
record results of the further processing in the bitemporal ledger.

### Claim 8 (depends on 1)

The data processing system of claim 1, wherein the transaction includes an identifier associated with the sequence of transactions and wherein identifying the sequence of transaction events is based on the identifier.

### Claim 9

A computer-implemented method for processing a transaction in a data processing system that includes a real-time interface, a processing engine, and a bitemporal ledger, the method comprising:
receiving, via the real-time interface, a transaction and a retroactive transaction to be processed by the data processing system, wherein the real-time interface comprises a transaction stream for buffering a plurality of transactions and wherein the transaction and the retroactive transaction are associated with a user account managed by the data processing system;
appending the transaction to the plurality of transactions in the transaction stream;
providing the transaction in temporal order from the transaction stream to the processing engine;
processing, by the processing engine, the transaction wherein processing the transaction further comprises:
identifying, by the processing engine, a sequence of transactions in the bitemporal ledger associated with the transaction, wherein the sequence of transactions is associated with the user account and wherein the sequence of transactions includes transactions that were previously processed by the processing engine; and
incorporating, by the processing engine, the transaction into the sequence of transactions in the bitemporal ledger according to temporal metadata associated with the transaction to form an updated sequence of transactions, wherein the processing engine and the bitemporal ledger are configured to prevent any transactions in the sequence of transactions from being overwritten, wherein the updated sequence of transactions reflects a current state of the user account;
processing the retroactive transaction, wherein processing the retroactive transaction comprises:
generating an alternate sequence of transactions comprising the sequence of transactions and the retroactive transaction, wherein the retroactive transaction replaces one transaction in the sequence of transactions and wherein the alternate sequence of transactions reflects an alternate state of the user account based on the retroactive transaction; and
replacing the current state of the user account with the alternate state of the user account.

### Claim 10 (depends on 9)

The method of claim 9, further comprising:
storing, in the bitemporal ledger, the updated sequence of transactions and a second sequence of transactions, wherein the second sequence of transactions is associated with a second user account managed by the data processing system.

### Claim 11 (depends on 9)

The method of claim 9, wherein the sequence of transactions is implemented as a graph comprising a plurality of nodes with each node of the plurality of nodes having a corresponding transaction in the sequence of transactions.

### Claim 12 (depends on 9)

The method of claim 9, further comprising:
identifying, by the processing engine, a processing module configured to further process the transaction; and
passing, by the processing engine, the transaction to the processing module for further processing.

### Claim 13 (depends on 12)

The method of claim 12, wherein the alternate sequence of transactions further includes alternate transactions that are in temporal order subsequent to the sequence of transactions.

### Claim 14 (depends on 13)

The method of claim 13, wherein at least one alternate transaction of the alternate transactions reflects a change to the sequence of transactions and is based on the transaction.

### Claim 15 (depends on 12)

The method of claim 12, further comprising:
recording, by the processing engine, results of the further processing by the processing module in the bitemporal ledger.

### Claim 16 (depends on 9)

The method of claim 9, wherein the transaction includes an identifier associated with the sequence of transactions and wherein identifying the sequence of transactions is based on the identifier.

### Claim 17

A non-transitory computer-readable medium storing instructions, the instructions, when executed by a processing engine in a data processing system that includes a real-time interface and a bitemporal ledger, cause the processing engine to perform operations comprising:
receiving, via the real-time interface, a transaction and a retroactive transaction to be processed by the data processing system, wherein the real-time interface comprises a transaction stream for buffering a plurality of transactions and wherein the transaction and the retroactive transaction are associated with a user account managed by the data processing system;
appending the transaction to the plurality of transactions in the transaction stream;
receiving the transaction in temporal order from the transaction stream;
processing the transaction wherein processing the transaction further comprises:
identifying a sequence of transactions in the bitemporal ledger associated with the transaction to form an updated sequence of transactions, wherein the sequence of transactions is associated with the user account and wherein the sequence of transactions includes transactions that were previously processed by the processing engine; and
incorporating the transaction into the sequence of transactions in the bitemporal ledger according to temporal metadata associated with the transaction to form an updated sequence of transactions, wherein the processing engine and the bitemporal ledger are configured to prevent any transactions in the sequence of transactions from being overwritten, wherein the updated sequence of transactions reflects a current state of the user account
processing the retroactive transaction, wherein processing the retroactive transaction comprises:
generating an alternate sequence of transactions comprising the sequence of transactions and the retroactive transaction, wherein the retroactive transaction replaces one transaction in the sequence of transactions and wherein the alternate sequence of transactions reflects an alternate state of the user account based on the retroactive transaction; and
replacing the current state of the user account with the alternate state of the user account.

### Claim 18 (depends on 17)

The non-transitory computer-readable medium of claim 17, the operations further comprising:
storing, in the bitemporal ledger, the updated sequence of transactions and a second sequence of transactions, wherein the second sequence of transactions is associated with a second user account managed by the data processing system.

### Claim 19 (depends on 17)

The non-transitory computer-readable medium of claim 17, wherein the sequence of transactions is implemented as a graph comprising a plurality of nodes with each node of the plurality of nodes having a corresponding transaction in the sequence of transactions.

### Claim 20 (depends on 17)

The non-transitory computer-readable medium of claim 17, the operations further comprising:
identifying, by the processing engine, a processing module configured to further process the transaction; and
passing, by the processing engine, the transaction to the processing module for further processing.
