# US 2025/0062923 A1 · Distributed ledger for internet of things

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

- Number: US 2025/0062923 A1
- Document ID: US20250062923A1
- Status: Published application
- Kind: A1
- Application number: 18/709,377
- Filed: 2022-11-11
- Published: 2025-02-20
- Earliest claimed: 2021-11-12
- Applicants: Newsouth Innovations Pty Limited; The University of Sydney
- Inventors: Abubakar Sadiq SANI; Zhao Yang DONG; Dong YUAN; Ke MENG
- Web page: https://patentgrep.com/patent/US20250062923A1

## CPC

- G06F 21/64: Protecting data integrity, e.g. using checksums, certificates or signatures
- H04L 9/50: {using hash chains, e.g. blockchains or hash trees}
- G06F 21/6218: {to a system of files or objects, e.g. local or distributed file system or database}
- G06Q 20/065: {using e-cash}
- G16Y 10/50: Finance; Insurance
- H04L 9/0841: {involving Diffie-Hellman or related key agreement protocols}
- G06Q 2220/00: Business processing using cryptography
- H04L 2209/56: Financial cryptography, e.g. electronic payment or e-cash
- 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)
- 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
- G16Y: INFORMATION AND COMMUNICATION TECHNOLOGY SPECIALLY ADAPTED FOR THE INTERNET OF THINGS [IoT]

## Abstract

A method, system and computer readable storage medium for controlling a state of accounts. In one aspect, the method uses a data structure storing a plurality of transactions representing the state of accounts. The method comprises receiving a request by a node of a plurality of nodes to create a transaction and determining a type of the transaction based on the request. The determined type of the transaction is used to determine whether to add the transaction to a data structure storing a plurality of transactions representing a state of accounts. In response to determining that the transaction is to be added to the data structure, storing the transaction in the data structure based on the determined type to control the state of accounts. The transaction may by stored in the data structure using a link corresponding to the determined type. The determined type corresponds to a type from a plurality of types comprising a retractable transaction and a non-retractable transaction.

## Claims

### Claim 1

A method of controlling a state of accounts using a data structure storing a plurality of transactions representing the state of accounts, the method comprising:
receiving a request by a node of a plurality of nodes to create a transaction;
determining a type of the transaction based on the request;
determining, based on the determined type, whether to add the transaction to a data structure storing a plurality of transactions representing a state of accounts; and
in response to determining that the transaction is to be added to the data structure, storing the transaction in the data structure based on the determined type to control the state of accounts,
wherein the transaction is stored in the data structure using a link corresponding to the determined type, the determined type corresponding to a type from a plurality of types comprising a retractable transaction and a non-retractable transaction.

### Claim 2 (depends on 1)

The method according to claim 1, wherein the transaction is added to the data structure in association with the determined type to control the state of accounts, wherein the transaction is added to the data structure using a Distributed Consensus-based Key Establishment protocol if the transaction is either a retractable transaction or a non-retractable transaction.

### Claim 3 (depends on 1)

The method according to claim 1, further comprising utilizing the transaction without being added to the data structure if the determined type is a non-payment functionality transaction, wherein the non-payment functionality transaction is utilised using a Non-Consensus-based Key Establishment protocol.

### Claim 4 (depends on 2)

The method according to claim 2, further comprising:
receiving a further request by the node to convert a retractable transaction from the plurality of transactions in the data structure to a non-retractable transaction;
identifying the retractable transaction in the data structure using the received further request;
adding a further non-retractable transaction associated with the identified transaction to the data structure using the Distributed Consensus-based Key Establishment protocol.

### Claim 5 (depends on 1)

The method according to claim 1, further comprising:
receiving a retracting request by the node to retract a transaction in the data structure;
identifying a transaction in the data structure based on the retracting request;
determining if the identified transacting is retractable;
retracting the transaction from the data structure if the transaction is retractable; and
providing feedback to indicate to the node that the transaction is not retractable if the transaction is non-retractable.

### Claim 6 (depends on 1)

The method according to claim 1, wherein a non-retractable transaction is associated with a directional link in the data structure and a retractable transaction is associated with a non-directional link in the data structure.

### Claim 7 (depends on 1)

The method according to claim 1, wherein each transaction from the plurality of transactions is associated with a transaction weight value and each link connecting two transactions is associated with a link weight value.

### Claim 8 (depends on 7)

The method according to claim 7, wherein the transaction weight value represents a total amount of work carried to process the respective transaction; and wherein the link weight value is based on the transaction weight value associated with at least one the transactions connected by said link.

### Claim 9 (depends on 1)

The method according to claim 1, further comprising determining a tip of the data structure to attach the transaction.

### Claim 10 (depends on 9)

The method according to claim 9, wherein the tip is determined based on Fuzzy Analytic Hierarchy Process (AHP).

### Claim 11 (depends on 1)

The method according to claim 1, wherein each request comprises generating a mutually authenticated key based on a key establishment protocol selected based on the determined type of the transaction.

### Claim 12 (depends on 1)

The method according to claim 1, wherein the data structure is an Acyclic Mixed Graph.

### Claim 13 (depends on 1)

The method according to claim 1, wherein at least one of the plurality of nodes is an Internet of Things node.

### Claim 14 (depends on 1)

The method according to claim 1, wherein the plurality of transactions comprises at least one payment-related transaction and at least one of identity creation transaction and identity revocation transaction.

### Claim 15 (depends on 1)

A computer implemented system for controlling a state of accounts using a data structure storing a plurality of transactions representing the state of accounts, wherein the computer implemented system includes one or more processors configured to perform the method of claim 1.

### Claim 16 (depends on 1)

A computer readable medium including executable instructions which configured one or more processors of a computer implemented system to control a state of accounts using a data structure storing a plurality of transactions representing the state of accounts, wherein execution of the executable instructions by the one or more processors configure the computerised system to perform the method of claim 1.

### Claim 17

A computer readable storage medium storing a data structure for storing a plurality of transactions representing the state of accounts, the data structure comprising:
a root; and
a plurality of tips, each tip corresponding to a transaction from the plurality of transactions, the plurality of tips comprising a non-retractable tip representing a non-retractable transaction and a retractable tip representing a retractable transaction,
wherein the non-retractable tip is linked, using a non-retractable link to a first further tip from the plurality of tips and the retractable tip is linked using an retractable link to a second further tip from the plurality of tip, wherein the data structure is configured to enable establishment of a further non-retractable link for the retractable link associated with the retractable tip in response to a request to convert the retractable transaction to a non-retractable transaction.

### Claim 18 (depends on 17)

The computer readable storage medium of claim 17, wherein a Distributed Consensus-based Key Establishment Protocol is used for adding transactions to the data structure based on a transaction type and a Non-Consensus-based Key Establishment protocol is used for exchanging transaction without adding to the data structure.

### Claim 19 (depends on 17)

The computer readable storage medium of claim 17, wherein each tip is configured to have up to two child tips.

### Claim 20

A method of controlling a state of accounts using a data structure storing a plurality of transactions representing the state of accounts, the method comprising:
receiving a request by a node of a plurality of nodes to add a transaction to a data structure storing a plurality of transactions representing a state of accounts;
determining a type of the transaction based on the request; and
adding the transaction in the data structure based on the determined type to control the state of accounts, wherein the transaction is added to the data structure using a link corresponding to the determined type, the determined type corresponding to a type from a plurality of types comprising a retractable transaction and a non-retractable transaction.
