IP Library › Granted Patent US 12681919
Granted Patent B2
US 12681919 · App. 18/493,345 · Granted Jul 14, 2026

Systems and methods of transaction identification generation for transaction-based environment

Inventor: Baohua Yang (Foster City, CA)
Assignee: ORACLE INTERNATIONAL CORPORATION
G06F16/2379G06F16/245G06F16/27
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12681919
App. No.
18/493,345
Granted
Jul 14, 2026
Kind
B2
Abstract

Described herein are systems and methods for transaction identification (ID) generation in transaction-based environments. The systems and methods provided generated transaction IDs which inherently define a range of values (a range of blockchain heights) within which the transaction is valid. This obviates problems associated with traditional transaction ID databases where a transaction ID only comprises a hashed value. That is, the presently disclosed systems and methods are an improvement over traditional hashing schemes as in traditional hashing schemes, a server must traverse an entire transaction ID database to determine if an incoming transaction is valid.

Claims (52)

1 . A system for transaction identification (ID) generation in transaction-based environments, comprising:

a computer comprising a microprocessor, wherein the computer is configured to perform a method comprising:

receiving, at a server running on the computer, the server comprising a distributed ledger, a request to commit a transaction to the distributed ledger, the request further comprising a transaction identifier (transaction ID) generated at a client device and being associated with the transaction, the transaction ID associated with the transaction comprising a hash value, an anchor value, and an offset value;

wherein generation of the transaction ID at the client device comprises periodically querying, by the client device, a current height of the distributed ledger at the server, and storing, at the client device, height values received as responses to the periodic queries, for use in determining the anchor value and the offset value;

providing, at the server, a plurality of transaction ID databases comprising a blockchain run within a sharded data store, the plurality of transaction ID databases storing valid transaction IDs of the distributed ledger;

parsing, by the server, the transaction ID associated with the transaction;

verifying, by the server, the transaction ID according to a content of the transaction;

determining, by a database manager and based upon the parsed transaction ID associated with the transaction, a transaction ID database of the plurality of transaction ID databases;

checking, by the database manager, the determined transaction ID database to determine, based upon the parsed transaction ID associated with the transaction, that the transaction is validly directed to a range of the distributed ledger; and

upon determining that the transaction is validly directed to a range of the distributed ledger, committing the transaction to the distributed ledger.

2 . The system of claim 1 , wherein upon the transaction being committed to the distributed ledger, the transaction ID associated with the transaction is committed to the blockchain at the determined transaction ID database.

3 . The system of claim 1 , wherein the transaction ID associated with the transaction is generated at the client device.

4 . The system of claim 3 , wherein the anchor value of the transaction ID is generated based upon a response to the periodic queries from a ledger tracker, wherein the ledger tracker stores responses to the period queries at a local memory of the client device.

5 . The system of claim 1 , wherein the distributed ledger is provisioned as a blockchain cloud service, the blockchain cloud service comprising one or more peer containers, ordering containers, and chaincode containers.

6 . The system of claim 1 , wherein each valid transaction ID stored at the plurality of transaction ID databases is associated with a transaction recorded at the distributed ledger.

7 . The system of claim 1 , wherein checking, by a database manager, the transaction ID database to determine that the transaction is validly directed to a range of the distributed ledger defined by the anchor value and the offset value of the transaction ID associated with the transaction comprises:

assessing the transaction while the distributed ledger undergoes an update for a time period;

upon the time period elapsing, determining that the transaction ID is validly directed to the range of the distributed ledger, wherein the range is defined by the anchor value and offset value, prior to committing the requested transaction.

8 . A method for transaction identification (ID) generation in transaction-based environments, comprising:

providing a computer comprising a microprocessor;

receiving, at a server running on the computer, the server comprising a distributed ledger, a request to commit a transaction to the distributed ledger, the request further comprising a transaction identifier (transaction ID) generated at a client device and being associated with the transaction, the transaction ID associated with the transaction comprising a hash value, an anchor value, and an offset value;

wherein generation of the transaction ID at the client device comprises periodically querying, by the client device, a current height of the distributed ledger at the server, and storing, at the client device, height values received as responses to the periodic queries, for use in determining the anchor value and the offset value;

providing, at the server, a plurality of transaction ID databases comprising a blockchain run within a sharded data store, the plurality of transaction ID databases storing valid transaction IDs of the distributed ledger;

parsing, by the server, the transaction ID associated with the transaction;

verifying, by the server, the transaction ID according to a content of the transaction;

determining, by a database manager and based upon the parsed transaction ID associated with the transaction, a transaction ID database of the plurality of transaction ID databases;

checking, by the database manager, the determined transaction ID database to determine, based upon the parsed transaction ID associated with the transaction, that the transaction is validly directed to a range of the distributed ledger; and

upon determining that the transaction is validly directed to a range of the distributed ledger, committing the transaction to the distributed ledger.

9 . The method of claim 8 , wherein upon the transaction being committed to the distributed ledger, the transaction ID associated with the transaction is committed to the blockchain at the determined transaction ID database.

10 . The method of claim 8 , wherein the transaction ID associated with the transaction is generated at the client device.

11 . The method of claim 10 , wherein the anchor value of the transaction ID is generated based upon a response to the periodic queries from a ledger tracker, wherein the ledger tracker stores responses to the period queries at a local memory of the client device.

12 . The method of claim 8 , wherein the distributed ledger is provisioned as a blockchain cloud service, the blockchain cloud service comprising one or more peer containers, ordering containers, and chaincode containers.

13 . The method of claim 8 , wherein each valid transaction ID stored at the transaction ID database is associated with a transaction recorded at the distributed ledger.

14 . The method of claim 8 , wherein checking, by a database manager, the transaction ID database to determine that the transaction is validly directed to a range of the distributed ledger defined by the anchor value and the offset value of the transaction ID associated with the transaction comprises:

assessing the transaction while the distributed ledger undergoes an update for a time period;

upon the time period elapsing, determining that the transaction ID is validly directed to the range of the distributed ledger, wherein the range is defined by the anchor value and offset value, prior to committing the requested transaction.

15 . A non-transitory computer readable storage medium having instructions thereon for transaction identification (ID) generation in transaction-based environments, which when read and executed cause one or more computers to perform steps comprising:

receiving, at a server running on the computer, the server comprising a distributed ledger, a request to commit a transaction to the distributed ledger, the request further comprising a transaction identifier (transaction ID) generated at a client device and being associated with the transaction, the transaction ID associated with the transaction comprising a hash value, an anchor value, and an offset value;

wherein generation of the transaction ID at the client device comprises periodically querying, by the client device, a current height of the distributed ledger at the server, and storing, at the client device, height values received as responses to the periodic queries, for use in determining the anchor value and the offset value;

providing, at the server, a plurality of transaction ID databases comprising a blockchain run within a sharded data store, the plurality of transaction ID databases storing valid transaction IDs of the distributed ledger;

parsing, by the server, the transaction ID associated with the transaction;

verifying, by the server, the transaction ID according to a content of the transaction;

determining, by a database manager and based upon the parsed transaction ID associated with the transaction, a transaction ID database of the plurality of transaction ID databases;

checking, by the database manager, the determined transaction ID database to determine, based upon the parsed transaction ID associated with the transaction, that the transaction is validly directed to a range of the distributed ledger; and

upon determining that the transaction is validly directed to a range of the distributed ledger, committing the transaction to the distributed ledger.

16 . The non-transitory computer readable storage medium of claim 15 , wherein upon the transaction being committed to the distributed ledger, the transaction ID associated with the transaction is committed to the blockchain at the determined transaction ID database.

17 . The non-transitory computer readable storage medium of claim 15 , wherein the transaction ID associated with the transaction is generated at the client device.

18 . The non-transitory computer readable storage medium of claim 17 , wherein the anchor value of the transaction ID is generated based upon a response to the periodic queries from a ledger tracker, wherein the ledger tracker stores responses to the period queries at a local memory of the client device.

19 . The non-transitory computer readable storage medium of claim 15 , wherein the distributed ledger is provisioned as a blockchain cloud service, the blockchain cloud service comprising one or more peer containers, ordering containers, and chaincode containers.

20 . The non-transitory computer readable storage medium of claim 15 , wherein checking, by a database manager, the transaction ID database to determine that the transaction is validly directed to a range of the distributed ledger defined by the anchor value and the offset value of the transaction ID associated with the transaction comprises:

assessing the transaction while the distributed ledger undergoes an update for a time period;

upon the time period elapsing, determining that the transaction ID is validly directed to the range of the distributed ledger, wherein the range is defined by the anchor value and offset value, prior to committing the requested transaction.