# US 2021/0243033 A1 · Blockchain network interaction controller

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

- Number: US 2021/0243033 A1
- Document ID: US20210243033A1
- Status: Published application
- Kind: A1
- Application number: 17/238,027
- Filed: 2021-04-22
- Published: 2021-08-05
- Earliest claimed: 2019-11-14
- Assignees: Visa International Service Association
- Applicants: Visa International Service Association
- Inventors: Quan Wang
- Web page: https://patentgrep.com/patent/US20210243033A1

## CPC

- G06Q 20/06: Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme
- G06Q 20/065: {using e-cash}
- G06Q 20/36: using electronic wallets or electronic money safes
- G06Q 20/3827: {Use of message hashing}
- G06Q 20/3829: {involving key management}
- G06Q 20/389: {Keeping log of transactions for guaranteeing non-repudiation of a transaction}
- H04L 9/3218: {using proof of knowledge, e.g. Fiat-Shamir, GQ, Schnorr, ornon-interactive zero-knowledge proofs}
- H04L 9/3236: {using cryptographic hash functions}
- H04L 9/3297: {involving time stamps, e.g. generation of time stamps}
- H04L 9/50: {using hash chains, e.g. blockchains or hash trees}
- G06Q 2220/00: Business processing using cryptography
- H04L 9/0637: {Modes of operation, e.g. cipher block chaining [CBC], electronic codebook [ECB] or Galois/counter mode [GCM]}
- H04L 9/3239: {involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD}
- H04L 2209/56: Financial cryptography, e.g. electronic payment or e-cash
- 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
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Described herein are systems and methods for virtualizing policy enforcement amongst participants of an overlay network. In some embodiments, each of the participants may maintain a separate blockchain network. The overlay network may receive smart contracts or other policy documents that include information on interactions with a particular participant or between participants. A controller, which may be implemented on any node of the overlay network, may then extract an interaction algorithm from that smart contract that may be stored in policy data to be used in completing transactions between two participants of the overlay network. In some embodiments, the policy data may include cost data which may be used to determine how two entities may interact.

## Claims

### Claim at position 1

-18. (canceled)

### Claim 19

A computer-implemented method, comprising:
receiving, from a first entity associated with a first blockchain network, a request to conduct a transaction;
identifying a first set of policies associated with the first entity;
identifying a second set of policies associated with a second entity associated with a second blockchain network; and
facilitating the transaction between the first entity and the second entity using the first set of policies and the second set of policies.

### Claim 20 (depends on 19)

The computer-implemented method of claim 19, wherein at least one of the first set of policies or the second set of policies indicates whether the first entity and the second entity may interact.

### Claim 21 (depends on 19)

The computer-implemented method of claim 19, wherein at least one of the first set of policies or the second set of policies indicates access rights for the first entity with respect to data stored in the second blockchain network.

### Claim 22 (depends on 19)

The computer-implemented method of claim 19, wherein at least one of the first set of policies or the second set of policies indicates write permissions by the first entity to the second blockchain network.

### Claim 23 (depends on 19)

The computer-implemented method of claim 19, wherein at least one of the first entity or the second entity is an individual or a computer network.

### Claim 24 (depends on 19)

The computer-implemented method of claim 19, wherein the first set of policies is identified based on a network address associated with the first entity.

### Claim 25 (depends on 19)

The computer-implemented method of claim 19, wherein the transaction relates to at least one of trust management, fraud and disputes, underwriting, data routing, policy enforcement, or member services.

### Claim 26 (depends on 19)

The computer-implemented method of claim 19, wherein the first set of policies is generated from a policy document received in relation to the first entity.

### Claim 27 (depends on 26)

The computer-implemented method of claim 26, wherein the policy document received in relation to the first entity comprises a smart contract.

### Claim 28 (depends on 19)

The computer-implemented method of claim 19, wherein the first set of policies includes at least an interaction algorithm.

### Claim 29 (depends on 19)

The method of claim 19, wherein the first set of policies and the second set of policies are used for multiple transactions conducted with the first and second blockchain networks.

### Claim 30 (depends on 19)

The method of claim 19, wherein the first set of policies and the second set of policies pertain to specific transaction types.

### Claim 31 (depends on 19)

The method of claim 19, wherein the first set of policies and the second set of policies pertain to routing of the transaction.

### Claim 32

A blockchain node server comprising:
a processor, and
a computer readable medium coupled to the processor, the computer readable medium comprising code for causing the processor to:
receive, from a first entity associated with a first blockchain network, a request to conduct a transaction;
identify a first set of policies associated with the first entity;
identify a second set of policies associated a second entity associated with a second blockchain network; and
facilitate the transaction between the first entity and the second entity using the first set of policies and the second set of policies.

### Claim 33 (depends on 32)

The blockchain node server of claim 32, wherein the first set of policies indicates a first data file format associated with the first entity and the second set of policies indicates a second data file format associated with the second entity.

### Claim 34 (depends on 33)

The blockchain node server of claim 33, wherein facilitating the transaction between the first entity and the second entity comprises translating between the first data file format and the second data file format.

### Claim 35 (depends on 34)

The blockchain node server of claim 34, wherein translating between the first data file format and the second data file format comprises using an intermediary data file format.

### Claim 36 (depends on 32)

The blockchain node server of claim 32, wherein the first set of policies is generated from a policy document received in relation to the first entity, and wherein the policy document received in relation to the first entity comprises a smart contract.

### Claim 37 (depends on 32)

The blockchain node server of claim 32, wherein the first set of policies and the second set of policies are used for multiple transactions conducted with the first and second blockchain networks.